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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
43e984b125a4363d68f2d999df4cb45fbe7ec9f7 | 191 | md | Markdown | license.md | wenbingtao/GLHA | ff81c29de3cc742374ed497fc85d601bf3f1a92b | [
"MIT"
] | 8 | 2021-02-08T09:58:40.000Z | 2022-01-18T17:53:00.000Z | learned_correspondences/license.md | patel-nisarg/Structure_from_motion | ecececfd357ea8c4802619bbbb7a278c5f6b3989 | [
"MIT"
] | null | null | null | learned_correspondences/license.md | patel-nisarg/Structure_from_motion | ecececfd357ea8c4802619bbbb7a278c5f6b3989 | [
"MIT"
] | 2 | 2021-03-09T11:27:48.000Z | 2021-11-08T14:23:53.000Z | This software release is only for research and evaluation purposes only. For
any form of commercial usage, prior approval form EPFL and University of
Victoria should be obtained in writing.
| 38.2 | 76 | 0.82199 | eng_Latn | 0.999884 |
43e9c6befe9f13828357f08b55cb926d27fabd56 | 1,437 | md | Markdown | content/schinese/Asset Management/quickguide_create_a_mod.md | YiGu-Studio/DocsModdingBannerlordCN | 0088f4c9dde0e194189572ce3369487dc0721db1 | [
"Apache-2.0"
] | 4 | 2020-10-03T03:17:57.000Z | 2020-10-12T17:07:08.000Z | content/schinese/Asset Management/quickguide_create_a_mod.md | YiGu-Studio/DocsModdingBannerlordCN | 0088f4c9dde0e194189572ce3369487dc0721db1 | [
"Apache-2.0"
] | 23 | 2020-10-03T01:19:00.000Z | 2020-10-27T04:40:02.000Z | content/schinese/Asset Management/quickguide_create_a_mod.md | YiGu-Studio/DocsModdingBannerlordCN | 0088f4c9dde0e194189572ce3369487dc0721db1 | [
"Apache-2.0"
] | 3 | 2020-10-02T22:06:03.000Z | 2020-10-05T03:48:01.000Z | +++
title = "创建一个Mod - 快速入门"
weight = 1
+++
Mod 可以包含从网格到物理实体、场景、游戏实体（如派系、领主、部队、物品）以及可以运行任何游戏逻辑的脚本和行为等资产 (Assets)。在本指南中，将解释创建一个 Mod 的过程。
##### 新建一个Mod
Mod 位于根目录下的 "Modules" 文件夹内，它必须包含名为 SubModule.xml 的 xml 文件。这个文件提供 "Name"、"ID" 和 "Version" 节点等基本信息。另外，还可以在 "DepenendedModules" 节点里面定义依赖模块。如果你想制作一个单人模式 Mod，它的 "DepenendedModules" 也应该包含一个 "SingleplayerModule" 节点。此后，该 Mod 将在游戏启动器中出现。
子Mod 可以定义在运行时加载的 DLL。这些 DLL 应该包含继承自 "MBSubModuleBase" 的 Class，其名称应该与 xml 中的 "SubModuleClassType" 节点一致。该类将被构造，并被调用某些回调，这样 od 就可以将其行为注册到游戏中。
##### Mod 层次结构
Mod 可以具有多个文件夹，其中包含不同类型的内容：
{{% notice info %}}
* bin: 编译后的DLL应该放在 "bin/Win64_Shipping_Client"文件夹内，这样游戏才能找到并加载DLL。
* Atmospheres: 此文件夹包含可在游戏中使用的不同环境 (Atmosphere) 模板。可以从编辑器将新的环境保存到任何 Mod。
* AssetSources: 此文件夹包含资产的来源。编辑器将资产导入此文件夹。在发布 Mod 之前可以过滤掉这个文件夹。关于向模块添加新内容的更多信息，请参见 <strong>[添加&覆盖资产]({{< ref "overriding_assets.md" >}})</strong>。
* Assets: 此文件夹包含从内容源派生的资产数据。它仅在 mod 开发阶段使用。在发布 mod 之前，该文件夹可能会被过滤掉。
* AssetPackages: 当模块的内容工作完成后，内容创建者应该开始 "Publish" 操作，为内容的发布做好准备。此文件夹包含了被发布的资产。
* GUI: 此文件夹包含任何新的可供游戏使用的GUI元素，预制件或笔刷。
* ModuleData: 此文件夹有许多包含了重要游戏逻辑的 xml 文件。"project.mbproj" 文件管理着将被加载到该文件夹内的 xml 文件。这些 xml 涵盖了从动画和套装到阵营、部队、物品等内容。
* NavMeshPrefabs: 导航网面组可以在编辑器中保存为模板，方便插入到多个场景中。此文件夹包含了这些内容。
* Prefabs: 此文件夹包含了预制件的XML。更多信息，请看 <strong>[实体&预制件]({{< ref "prefabs.md" >}})</strong>。
* SceneObj: 此文件夹保存着从任何编辑数据中剥离出来的场景数据。没有地形的场景只能存放在这个文件夹中。
* SceneEditData: 包含每个场景的地形编辑数据。此文件夹可以在发布mod之前过滤掉。
{{% /notice %}}
| 43.545455 | 228 | 0.777314 | yue_Hant | 0.888934 |
43e9cf926c1f21887ad8c475d72d88cba21ed089 | 2,268 | md | Markdown | en/managed-clickhouse/tutorials/sharding.md | batFormat/docs | 2414d9c5fa3cb2b2f7601082fd378e21575439ce | [
"CC-BY-4.0"
] | null | null | null | en/managed-clickhouse/tutorials/sharding.md | batFormat/docs | 2414d9c5fa3cb2b2f7601082fd378e21575439ce | [
"CC-BY-4.0"
] | 167 | 2020-12-10T09:08:59.000Z | 2021-02-05T08:11:43.000Z | en/managed-clickhouse/tutorials/sharding.md | batFormat/docs | 2414d9c5fa3cb2b2f7601082fd378e21575439ce | [
"CC-BY-4.0"
] | 5 | 2020-12-11T06:59:40.000Z | 2020-12-11T10:19:14.000Z | # Sharding ClickHouse tables
It makes sense to shard tables when splitting data into shards significantly helps improve DBMS performance or data availability. To increase availability, each shard should consist of 3 or more database hosts.
Data should be split into shards if:
* Your tables are very big. Consider sharding if your table is 200 GB or larger.
* The content of your tables is non-uniform. For example, data can be clearly classified as frequently queried and rarely queried.
* Your tables require high read and write performance. Sharding helps distribute workloads among the hosts to bypass technical limitations.
Ease of use and actual performance improvements depend strongly on the shard key you choose: make sure that the data is logically distributed across shards and isn't linked to data in different shards.
For more information about sharding, see [{#T}](../concepts/sharding.md).
## How to start sharding tables {#enable}
By default, {{ mch-name }} creates the first shard together with the cluster. This shard includes all the hosts in the cluster. To start using sharding, [add](../operations/shards.md#add-shard) the number of shards you need and create a table on the [Distributed](https://clickhouse.yandex/docs/en/operations/table_engines/distributed/) engine. The article under the link describes sharding strategies and guidelines for creating tables in the applicable format, as well as distributed table limits.
{{ mch-name }} automatically creates the [shard configuration](https://clickhouse.yandex/docs/en/operations/table_engines/distributed/) in the cluster. You can [manage this configuration](../operations/shards.md#shard-update).
## Example of sharding {#example}
Let's say you already have a sharded {{ mch-name }} cluster hosting the `db1` database. Your task is to enable sharding for the `hits` table. A random number, `rand()`, is used as a sharding expression in the example:
1. [Connect](../operations/connect.md) to the database.
1. Create a distributed table:
```
CREATE TABLE sharding ENGINE = Distributed(logs, db1, hits, rand());
```
After that, you can do SELECT queries and INSERT queries against the created table. The queries will be processed according to the configuration you set.
| 64.8 | 499 | 0.77866 | eng_Latn | 0.99884 |
43e9ee2d2cb8c4618607811de0f211fefe6d34e7 | 38 | md | Markdown | README.md | davidsibato/SixMovie | e2dd73bc00babc84e9cf7fb7973bc5c291a703fd | [
"MIT"
] | null | null | null | README.md | davidsibato/SixMovie | e2dd73bc00babc84e9cf7fb7973bc5c291a703fd | [
"MIT"
] | null | null | null | README.md | davidsibato/SixMovie | e2dd73bc00babc84e9cf7fb7973bc5c291a703fd | [
"MIT"
] | null | null | null | # SixMovie
Get movies and series info
| 12.666667 | 26 | 0.789474 | eng_Latn | 0.905325 |
43ea55f54857be04e636f170170e042b79e69f1e | 86 | md | Markdown | README.md | RafaelJNascimento/api_express_ts | 062d54dc890c8a3f5839d4cd6484e27668331b82 | [
"MIT"
] | 1 | 2020-12-17T21:18:09.000Z | 2020-12-17T21:18:09.000Z | README.md | RafaelJNascimento/api_express_ts | 062d54dc890c8a3f5839d4cd6484e27668331b82 | [
"MIT"
] | null | null | null | README.md | RafaelJNascimento/api_express_ts | 062d54dc890c8a3f5839d4cd6484e27668331b82 | [
"MIT"
] | null | null | null | Feito por Rafael J. Nascimento, exercício das aulas do bootcamp gostack da Rocketseat
| 43 | 85 | 0.825581 | por_Latn | 0.991386 |
43eaf00fbba612f84c7111c1840192fc45d518cf | 1,119 | md | Markdown | NeuroML2/README.md | rayner/muscle_model | 8f5aaba9bac07989dd9c5766a6b859796852cdae | [
"MIT"
] | null | null | null | NeuroML2/README.md | rayner/muscle_model | 8f5aaba9bac07989dd9c5766a6b859796852cdae | [
"MIT"
] | null | null | null | NeuroML2/README.md | rayner/muscle_model | 8f5aaba9bac07989dd9c5766a6b859796852cdae | [
"MIT"
] | null | null | null | C elegans muscle cell model in NeuroML 2
----------------------------------------
This is a NeuroML 2 implementation of the C elegans muscle cell model of [Boyle & Cohen, 2008](http://www.sciencedirect.com/science/article/pii/S0303264708001408).
To install & run this version, install jNeuroML (as outlined here: https://github.com/NeuroML/jNeuroML/blob/master/README.md)
Get a local copy of the repository with:
git clone https://github.com/openworm/muscle_model.git
or
git clone git@github.com:openworm/muscle_model.git
Go into the directory with the NeuroML 2 version of the model:
cd muscle_model/NeuroML2
Run the example cell (trying to reproduce Figure 2A in [Boyle & Cohen, 2008](http://www.sciencedirect.com/science/article/pii/S0303264708001408)) with:
jnml LEMS_Figure2A.xml
Run the example cell (trying to reproduce Figure 2B in [Boyle & Cohen, 2008](http://www.sciencedirect.com/science/article/pii/S0303264708001408)) with:
jnml LEMS_Figure2B.xml
For more details on the current status of this conversion, see issue: https://github.com/openworm/OpenWorm/issues/169
| 38.586207 | 163 | 0.74084 | eng_Latn | 0.580709 |
43ebe3efd8d5d495ed80a5208b9e077d16aa09b2 | 1,285 | md | Markdown | README.md | schriftgestalt/CleanUpLines | 329dcadbca09a33bf33e8c041e44a70f1df59e9e | [
"Apache-2.0"
] | null | null | null | README.md | schriftgestalt/CleanUpLines | 329dcadbca09a33bf33e8c041e44a70f1df59e9e | [
"Apache-2.0"
] | null | null | null | README.md | schriftgestalt/CleanUpLines | 329dcadbca09a33bf33e8c041e44a70f1df59e9e | [
"Apache-2.0"
] | 1 | 2021-09-04T10:08:04.000Z | 2021-09-04T10:08:04.000Z | # CleanUpLines
[Glyphs.app](https://www.glyphsapp.com/) filter for cleaning up unnecessary line segments. After installation, it will add a *Filter* menu item called *Clean Up Lines* (de: *Linien aufräumen,* fr: *Nettoyer les lignes,* es: *Limpiar líneas,* pt: *Limpar linhas,* jp: ラインをクリーンアップ, ko: 라인 정리, zh: 清理线路).
It will remove all (blue) on-curve points between two line segments if the two segments form an angle less than the given threshold.
### Installation
1. One-click install *Clean Up Lines* from *Window > Plugin Manager > Plugins.*
2. Restart Glyphs.
### Usage Instructions
1. Open a glyph in Edit View.
2. Choose *Filter > Clean Up Lines.*
3. In the window, pick a threshold angle, use (Shift) up/down arrows for adjusting the threshold value incrementally.
4. Click *Clean Up.*
### License
Copyright 2021 Rainer Erich Scheichelbauer (@mekkablue).
Based on sample code by Georg Seifert (@schriftgestalt) and Jan Gerner (@yanone).
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
See the License file included in this repository for further details.
| 40.15625 | 301 | 0.750973 | eng_Latn | 0.940098 |
43ec03c6944374b63a53af6ea4d42153e798c33b | 42 | md | Markdown | README.md | ChristopherKubis/opencv-with-extra-modules-binarys-win64 | 2d5e06c468d8663a3ed9dc9091a76cc9b5b1ef53 | [
"Apache-2.0"
] | null | null | null | README.md | ChristopherKubis/opencv-with-extra-modules-binarys-win64 | 2d5e06c468d8663a3ed9dc9091a76cc9b5b1ef53 | [
"Apache-2.0"
] | null | null | null | README.md | ChristopherKubis/opencv-with-extra-modules-binarys-win64 | 2d5e06c468d8663a3ed9dc9091a76cc9b5b1ef53 | [
"Apache-2.0"
] | null | null | null | # opencv-with-extra-modules-binarys-win64
| 21 | 41 | 0.809524 | eng_Latn | 0.485514 |
43ec3942c5feeb0e81d00b964d5fd78eb6f01d4b | 159 | md | Markdown | 0.md | wulouzhu/li-aolong.github.io | 11e61e9b6fb9e439578e1bb675e1f57685e5eabb | [
"CC0-1.0"
] | 1 | 2019-07-31T03:38:37.000Z | 2019-07-31T03:38:37.000Z | 0.md | wulouzhu/li-aolong.github.io | 11e61e9b6fb9e439578e1bb675e1f57685e5eabb | [
"CC0-1.0"
] | null | null | null | 0.md | wulouzhu/li-aolong.github.io | 11e61e9b6fb9e439578e1bb675e1f57685e5eabb | [
"CC0-1.0"
] | null | null | null | # 李傲龍的个人博客
## [文章列表](https://github.com/li-aolong/li-aolong.github.io/issues)
## [文章分类](https://github.com/li-aolong/li-aolong.github.io/projects)
## [关于]() | 22.714286 | 68 | 0.679245 | yue_Hant | 0.079216 |
43ed195a4cf20741b6f9f8f3280070505e216f75 | 1,589 | md | Markdown | content/post/2014-01-17-missing-not-at-random-data-makes-some-facebook-users-feel-sad.md | jdstorey/simplystats | 0f4f72c5871a2d75f51b358e9107a7cdcff91cab | [
"MIT"
] | 221 | 2017-05-07T20:52:01.000Z | 2021-08-31T19:12:14.000Z | content/post/2014-01-17-missing-not-at-random-data-makes-some-facebook-users-feel-sad.md | jdstorey/simplystats | 0f4f72c5871a2d75f51b358e9107a7cdcff91cab | [
"MIT"
] | 11 | 2017-05-08T06:37:51.000Z | 2019-05-29T16:04:56.000Z | content/post/2014-01-17-missing-not-at-random-data-makes-some-facebook-users-feel-sad.md | jdstorey/simplystats | 0f4f72c5871a2d75f51b358e9107a7cdcff91cab | [
"MIT"
] | 83 | 2017-05-15T21:45:30.000Z | 2021-09-06T10:39:12.000Z | ---
id: 2457
title: Missing not at random data makes some Facebook users feel sad
date: 2014-01-17T10:22:20+00:00
author: Rafael Irizarry
al2fb_facebook_link_id:
- 136171103105421_596722960383564
al2fb_facebook_link_time:
- 2014-01-17T15:22:26+00:00
al2fb_facebook_link_picture:
- post=http://simplystatistics.org/wp-content/uploads/2014/01/Screen-Shot-2014-01-17-at-10.16.32-AM.png
dsq_thread_id:
- 2134633500
categories:
- Uncategorized
slug: "missing-not-at-random-data-makes-some-facebook-users-feel-sad"
---
[This article](http://www.npr.org/2014/01/09/261108836/many-younger-facebook-users-unfriend-the-network), published last week, explained how "some younger users of Facebook say that using the site often leaves them feeling sad, lonely and inadequate". Being a statistician gives you an advantage here because we know that naive estimates from missing not at random (MNAR) data can be very biased. The posts you see on Facebook are not a random sample from your friends' lives. We see pictures of their vacations, abnormally flattering pictures of themselves, reports on their major achievements, etc... but no view of the mundane typical daily occurrences. Here is a simple cartoon explanation of how MNAR data can give you a biased view of whats really going on. Suppose your life occurrences are rated from 1 (worst) to 5 (best), this table compares what you see to what is really going on after 15 occurrences:
| 72.227273 | 913 | 0.790434 | eng_Latn | 0.970275 |
43ee43f32155918a59effbb98dba424af193cb8c | 69 | md | Markdown | README.md | cscholze/tic-tac-node | b00d7ca1cf63a35031462de17cbebe0f07dc12b9 | [
"MIT"
] | null | null | null | README.md | cscholze/tic-tac-node | b00d7ca1cf63a35031462de17cbebe0f07dc12b9 | [
"MIT"
] | null | null | null | README.md | cscholze/tic-tac-node | b00d7ca1cf63a35031462de17cbebe0f07dc12b9 | [
"MIT"
] | null | null | null | # tic-tac-node
A tic-tac-toe implemented in Node.js with websockets.
| 23 | 53 | 0.768116 | eng_Latn | 0.683697 |
43ee467d189bb14fab7246dda908239585fac011 | 831 | md | Markdown | README.md | Yohannfra/Vim-Protect-Header | bd55e86d0bb895a4372c43fa7658c6ed30e5b2a7 | [
"MIT"
] | null | null | null | README.md | Yohannfra/Vim-Protect-Header | bd55e86d0bb895a4372c43fa7658c6ed30e5b2a7 | [
"MIT"
] | null | null | null | README.md | Yohannfra/Vim-Protect-Header | bd55e86d0bb895a4372c43fa7658c6ed30e5b2a7 | [
"MIT"
] | null | null | null | # Vim-Protect-Header
A simple vim plugin to quickly protect c/c++ header files
Example: \
## Installation
### Using Plug
```
Plug 'Yohannfra/Vim-Protect-Header'
```
### Manual installation
```
git clone https://github.com/Yohannfra/Vim-Protect-Header/ ~/.vim/plugin/
```
## Configuration
You can call the function automatically when creating a .h/.hpp file.\
insert this line in your .vimrc
```vim
autocmd BufNewFile *.h,*.hpp :Protect
```
If you want to add a comment after the endif so it looks like that
```c
#ifndef MY_HEADER_HPP
#define MY_HEADER_HPP
#endif // MY_HEADER_HPP
```
Add this line to your .vimrc
```vim
let g:Protect_Header_Endif_Comment = 1
```
## How to use
```
:Protect
```
## License
This project is licensed under the terms of the MIT license.
| 16.959184 | 73 | 0.712395 | eng_Latn | 0.895097 |
43ef5808392d1ccee4e9d470b6fbe5986b629dec | 3,731 | md | Markdown | articles/vpn-gateway/vpn-gateway-about-skus-legacy.md | changeworld/azure-docs.pt-pt | 8a75db5eb6af88cd49f1c39099ef64ad27e8180d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/vpn-gateway/vpn-gateway-about-skus-legacy.md | changeworld/azure-docs.pt-pt | 8a75db5eb6af88cd49f1c39099ef64ad27e8180d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/vpn-gateway/vpn-gateway-about-skus-legacy.md | changeworld/azure-docs.pt-pt | 8a75db5eb6af88cd49f1c39099ef64ad27e8180d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Rede virtual Legacy Azure VPN gateway SKUs
description: Como trabalhar com a antiga rede virtual gateway SKUs; Básico, Standard e HighPerformance.
services: vpn-gateway
author: cherylmc
ms.service: vpn-gateway
ms.topic: article
ms.date: 08/15/2019
ms.author: cherylmc
ms.openlocfilehash: 9c5e6d5aca51bd560a46837ba47de86362665773
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: pt-PT
ms.lasthandoff: 03/28/2020
ms.locfileid: "79279393"
---
# <a name="working-with-virtual-network-gateway-skus-legacy-skus"></a>Trabalhar com a rede virtual gateway SKUs (sKUs legado)
Este artigo contém informações sobre o legado (antigo) gateway de rede virtual SKUs. O legado SKUs ainda funciona em ambos os modelos de implementação para gateways VPN que já foram criados. Os portões clássicos da VPN continuam a usar o legado SKUs, tanto para gateways existentes, como para novos gateways. Ao criar novos gateways VPN do Gestor de Recursos, utilize o novo gateway SKUs. Para obter informações sobre as novas SKUs, consulte sobre o [VPN Gateway](vpn-gateway-about-vpngateways.md).
## <a name="gateway-skus"></a><a name="gwsku"></a>SKUs de gateway
[!INCLUDE [Legacy gateway SKUs](../../includes/vpn-gateway-gwsku-legacy-include.md)]
Pode ver os preços do gateway legado na secção Gateways de **Rede Virtual,** que está localizado na página de [preços ExpressRoute](https://azure.microsoft.com/pricing/details/expressroute).
## <a name="estimated-aggregate-throughput-by-sku"></a><a name="agg"></a>Débito agregado estimado por SKU
[!INCLUDE [Aggregated throughput by legacy SKU](../../includes/vpn-gateway-table-gwtype-legacy-aggtput-include.md)]
## <a name="supported-configurations-by-sku-and-vpn-type"></a><a name="config"></a>Configurações suportadas por sKU e tipo VPN
[!INCLUDE [Table requirements for old SKUs](../../includes/vpn-gateway-table-requirements-legacy-sku-include.md)]
## <a name="resize-a-gateway"></a><a name="resize"></a>Redimensionar um portal
Você pode redimensionar sua porta de entrada para um portal SKU dentro da mesma família SKU. Por exemplo, se tiver um SKU Standard, pode redimensionar para um SKU de Alto Desempenho. No entanto, não pode redimensionar a sua porta de entrada VPN entre as antigas SKUs e as novas famílias SKU. Por exemplo, não pode ir de um SKU Padrão para um VpnGw2 SKU, ou um SKU básico para VpnGw1.
### <a name="resource-manager"></a>Resource Manager
Para redimensionar uma porta de entrada para o modelo de implementação do Gestor de Recursos utilizando o PowerShell, utilize o seguinte comando:
```powershell
$gw = Get-AzVirtualNetworkGateway -Name vnetgw1 -ResourceGroupName testrg
Resize-AzVirtualNetworkGateway -VirtualNetworkGateway $gw -GatewaySku HighPerformance
```
Também pode redimensionar uma porta de entrada no portal Azure.
### <a name="classic"></a><a name="classicresize"></a>Clássica
Para redimensionar uma porta de entrada para o modelo de implementação clássico, deve utilizar os cmdlets powerShell de gestão de serviço. Utilize o seguinte comando:
```powershell
Resize-AzureVirtualNetworkGateway -GatewayId <Gateway ID> -GatewaySKU HighPerformance
```
## <a name="change-to-the-new-gateway-skus"></a><a name="change"></a>Alteração para a nova porta de entrada SKUs
[!INCLUDE [Change to the new SKUs](../../includes/vpn-gateway-gwsku-change-legacy-sku-include.md)]
## <a name="next-steps"></a>Passos seguintes
Para mais informações sobre as novas SKUs gateway, consulte [Gateway SKUs](vpn-gateway-about-vpngateways.md#gwsku).
Para obter mais informações sobre as definições de configuração, consulte as definições de [configuração do Gateway VPN](vpn-gateway-about-vpn-gateway-settings.md).
| 55.686567 | 498 | 0.779416 | por_Latn | 0.955938 |
43efe32a7a58280dcb4c2676f9f094ed18f85924 | 2,594 | md | Markdown | docs/framework/wpf/advanced/how-to-use-application-resources.md | acidburn0zzz/docs.fr-fr | 5fdf04b7027f8b7d749c2180da4b99068e1f44ee | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-11T17:00:02.000Z | 2019-04-11T17:00:02.000Z | docs/framework/wpf/advanced/how-to-use-application-resources.md | Acidburn0zzz/docs.fr-fr | 5fdf04b7027f8b7d749c2180da4b99068e1f44ee | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/advanced/how-to-use-application-resources.md | Acidburn0zzz/docs.fr-fr | 5fdf04b7027f8b7d749c2180da4b99068e1f44ee | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-02-23T14:59:20.000Z | 2022-02-23T14:59:20.000Z | ---
title: 'Procédure : Utiliser des ressources d’application'
ms.date: 03/30/2017
helpviewer_keywords:
- application resources [WPF]
- resources [WPF], application resources
ms.assetid: 507ea937-5191-406b-8797-0a3d9f94156d
ms.openlocfilehash: 70dff8089c4da70fdc61247a0c604cf7ee85d02b
ms.sourcegitcommit: 5b6d778ebb269ee6684fb57ad69a8c28b06235b9
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 04/08/2019
ms.locfileid: "59088198"
---
# <a name="how-to-use-application-resources"></a>Procédure : Utiliser des ressources d’application
Cet exemple montre comment utiliser des ressources d’application.
## <a name="example"></a>Exemple
L’exemple suivant montre un fichier de définition d’application. Le fichier de définition d’application définit une section de ressource (une valeur pour le <xref:System.Windows.Application.Resources%2A> propriété). Les ressources définies au niveau de l’application sont accessibles à toutes les autres pages qui font partie de l’application. Dans ce cas, la ressource est un style déclaré. Car un style complet qui inclut un modèle de contrôle peut être long, cet exemple omet le modèle de contrôle qui est défini dans le <xref:System.Windows.Controls.ContentControl.ContentTemplate%2A> accesseur Set de propriété du style.
[!code-xaml[ResourcesApplication#PreTemplateResource](~/samples/snippets/csharp/VS_Snippets_Wpf/ResourcesApplication/CS/app.xaml#pretemplateresource)]
[!code-xaml[ResourcesApplication#PostTemplateResource](~/samples/snippets/csharp/VS_Snippets_Wpf/ResourcesApplication/CS/app.xaml#posttemplateresource)]
L’exemple suivant montre un [!INCLUDE[TLA2#tla_xaml](../../../../includes/tla2sharptla-xaml-md.md)] page qui fait référence à la ressource de niveau application définie par l’exemple précédent. La ressource est référencée en utilisant un [Extension de balisage StaticResource](staticresource-markup-extension.md) qui spécifie la clé de ressource unique pour la ressource demandée. Aucune ressource avec la clé « GelButton » ne figurant dans la page active, l’étendue de recherche de ressource pour la ressource demandée continue au-delà de la page active, dans les ressources définies au niveau de l’application.
[!code-xaml[ResourcesApplication#ConsumingPage](~/samples/snippets/csharp/VS_Snippets_Wpf/ResourcesApplication/CS/page1.xaml#consumingpage)]
## <a name="see-also"></a>Voir aussi
- [Ressources XAML](xaml-resources.md)
- [Vue d'ensemble de la gestion d'applications](../app-development/application-management-overview.md)
- [Rubriques Comment](resources-how-to-topics.md)
| 78.606061 | 628 | 0.80185 | fra_Latn | 0.876775 |
43f0a0481bd273512a2b3ce1b1933a27c0b69184 | 112 | markdown | Markdown | about.markdown | maanenh/camp-siteleaf | 3ae22f2d6f57ffcd8c42d2a83511b8e92b1fc926 | [
"Apache-2.0"
] | null | null | null | about.markdown | maanenh/camp-siteleaf | 3ae22f2d6f57ffcd8c42d2a83511b8e92b1fc926 | [
"Apache-2.0"
] | null | null | null | about.markdown | maanenh/camp-siteleaf | 3ae22f2d6f57ffcd8c42d2a83511b8e92b1fc926 | [
"Apache-2.0"
] | null | null | null | ---
title: About
date: 2016-06-06 06:09:00 Z
position: 3
---
My own About page, written on 28-11-2017 in Leiden | 16 | 50 | 0.6875 | eng_Latn | 0.811683 |
43f2da2d95a541c66db0a67827aaf22ca8c3a5a2 | 7,158 | md | Markdown | articles/human-resources/hr-whats-new-2021-09-20.md | vviptg/Dynamics-365-Operations.nb-no | 826fb5a428b9e66f854a116edb0351c4a1d5619e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-18T17:14:36.000Z | 2021-04-20T21:13:46.000Z | articles/human-resources/hr-whats-new-2021-09-20.md | vviptg/Dynamics-365-Operations.nb-no | 826fb5a428b9e66f854a116edb0351c4a1d5619e | [
"CC-BY-4.0",
"MIT"
] | 6 | 2017-12-12T12:48:00.000Z | 2019-04-30T11:45:53.000Z | articles/human-resources/hr-whats-new-2021-09-20.md | vviptg/Dynamics-365-Operations.nb-no | 826fb5a428b9e66f854a116edb0351c4a1d5619e | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-10-12T18:16:06.000Z | 2022-01-28T03:23:59.000Z | ---
title: Hva er nytt eller endret i Dynamics 365 Human Resources 20. september 2021
description: Dette emnet beskriver funksjoner som enten er nye eller endret i Microsoft Dynamics 365 Human Resources for 20. september 2021.
author: marcelbf
ms.date: 09/20/2021
ms.topic: article
ms.prod: ''
ms.technology: ''
ms.search.form: ''
audience: Application User
ms.search.scope: Human Resources
ms.custom: ''
ms.assetid: ''
ms.search.region: Global
ms.author: marcelbf
ms.search.validFrom: 2021-09-20
ms.dyn365.ops.version: Human Resources
ms.openlocfilehash: 3f4fc4768f8c96678b216709f78af6d3ddfd4132
ms.sourcegitcommit: ba8ca42e43e1a5251cbbd6ddb292566164d735dd
ms.translationtype: HT
ms.contentlocale: nb-NO
ms.lasthandoff: 09/25/2021
ms.locfileid: "7556939"
---
# <a name="whats-new-or-changed-in-dynamics-365-human-resources-september-20-2021"></a>Hva er nytt eller endret i Dynamics 365 Human Resources 20. september 2021
[!include [Applies to Human Resources](../includes/applies-to-hr.md)]
Dette emnet beskriver funksjoner som er nye, endret eller kommer snart i Microsoft Dynamics 365 Human Resources.
Hvis du vil ha mer informasjon om oppdateringsprosessen og tidsplanen, kan du se [Oppdatere prosess](hr-admin-setup-update-process.md).
Hvis du vil ha mer informasjon om nye funksjoner og deres forventede generelle tilgjengelighetsdatoer, se [Oversikt over Dynamics 365 Human Resources 2021-frigivelsesbølge 2](/dynamics365-release-plan/2021wave2/human-resources/dynamics365-human-resources/).
## <a name="in-this-release"></a>I denne versjonen
Denne versjonen omfatter følgende nye funksjoner og feilrettinger. Endringer gjelder for Build-nummeret 8.1.4464.
### <a name="new-features"></a>Nye funksjoner
Følgende funksjoner er allment tilgjengelige i denne versjonen.
| Funksjon | Lanseringsplan | Dokumentasjon |
|---|---|---|
| Aktivere forenklet lønnsintegrering (APIer for lønnsintegrering) | [Aktiver forenklet integrering med lønnsleverandører](/dynamics365-release-plan/2021wave1/human-resources/dynamics365-human-resources/enable-simplified-integration-payroll-providers) | [API for lønnsintegrering](hr-admin-integration-payroll-api-introduction.md) |
| Gjør det mulig for ansatte å merkes som klare til betaling | [Gjør det mulig for ansatte å merkes som klare til betaling](/dynamics365-release-plan/2021wave1/human-resources/dynamics365-human-resources/enable-employees-be-marked-as-ready-pay) | [Klar til betaling](/dynamics365/human-resources/hr-compensation-payroll) |
### <a name="bug-fixes"></a>Feilrettinger
Denne versjonen inneholder følgende feilrettinger.
> [!NOTE]
> Vårt mål er å få denne informasjonen til deg så raskt som mulig. Dette emnet kan være oppdatert for å inkludere feilrettingsfiler som ble tatt med i builden etter at dette emnet ble publisert.
| Utstedelsesnummer | Problem | Beskrivelse |
|---|---|---|
| 619774 | Redigering av adressebeskrivelsen synkroniseres ikke til Dataverse i sanntid. | Når du redigerer beskrivelsen for en arbeideradresse, blir ikke den oppdaterte beskrivelsen synkronisert i sanntid med Dataverse. Abonnementet i tabellen **Logistikkplassering** ble oppdatert for sending av en oppdatering. |
| 614603| Feil på **Arbeider**-siden når parameteren for **ansattes handlinger** ikke er valgt. | Når du ansetter en ny arbeider eller navigerer til **Arbeider**-siden, vises følgende feil, "Feltet **Personalhandlingstype** må fylles ut", selv om **Personalhandlinger** er slått av. |
| 615367 | Kategorien **Godkjent avspasering** viser en advarsel og vises feil. | Hvis permisjonsenheten er satt til **Dager** før aktivering av funksjonen **Konfigurer permisjonsenheter per permisjonstype**, viser kategorien **Godkjent avspasering** en ugyldig advarsel og feil kolonner. |
## <a name="in-preview"></a>I forhåndsvisning
Følgende nye funksjoner er i forhåndsversjon. Hvis du vil ha mer informasjon om hvordan du aktiverer eller deaktiverer funksjoner, kan du se [Behandle funksjoner](hr-admin-manage-features.md).
| Funksjon | Lanseringsplan | Dokumentasjon |
|---|---|---|
| Arbeidsområde for fordelsbehandling | [Arbeidsområdet Fordelsbehandling (forhåndsversjon)](/dynamics365-release-plan/2020wave2/human-resources/dynamics365-human-resources/benefits-management-workspace) | [Arbeidsområde for fordelsbehandling](hr-benefits-management-workspace.md) |
| Egendefinerte felt i Rettighet |[Egendefinert felt-støtte i rettighetsbehandling](/dynamics365-release-plan/2021wave1/human-resources/dynamics365-human-resources/custom-field-support-benefits-management) | [Bruke egendefinerte felt i rettighetsbehandling](/dynamics365/human-resources/hr-benefits-setup-eligibility-rules#using-custom-fields-in-eligibility-rules) |
| Fordelsoppgave |[Fordelsoppgave](/dynamics365-release-plan/2021wave1/human-resources/dynamics365-human-resources/benefits-summary-statement) | [Fordelsoppgave](hr-benefits-statement.md) |
### <a name="benefits-statement-known-issues"></a>Kjente problemer med Fordelsoppgave
| Problem | Beskrivelse |
|---|---|
| **Rapportparameter**-siden i **Ansattselvbetjening** for fordelsoppgaven er feil. | Når du navigerer til **Fordelsoppgave** i **Ansattselvbetjening**, viser siden **Rapportparametere** hurtigfanene **Poster som skal inkluderes** og **Kjør i bakgrunnen**. Disse må fjernes. |
| Lukkede og fremtidige perioder vises på **Rapportparameter**-siden for fordelsoppgaven. | Når brukeren navigerer til målsiden for **Fordelserklæringsrapport**, kan han eller hun velge fordelsplanperioder som er lukket eller er datert i fremtiden, noe som resulterer i en tom side. Bare gjeldende fordelsplanperiode skal vises i listen. |
|Feil når rapport sendes via e-post ved bruk av GER-rapportmål. | Fordelsoppgaven kan angis slik at det brukes e-postparametere på siden **GER-rapportmål**. Når rapporten fylles ut og skrives ut, får brukeren en formateringsfeil og fordelsoppgaven blir ikke sendt.|
## <a name="coming-soon"></a>Kommer snart
Hvis du vil ha en fullstendig liste over de planlagte funksjonene og de planlagte versjonene, kan du se [Oversikt over Dynamics 365 Human Resources 2021-frigivelsesbølge 2](/dynamics365-release-plan/2021wave2/human-resources/dynamics365-human-resources/).
| Funksjon | Detaljer |
|---|---|
| Platform update 10.0.21 (45) | Utrullingen av plattformoppdatering 10.0.21 er planlagt å begynne med serviceversjon 4. oktober 2021. Hvis du vil ha mer informasjon, kan du se [Platformoppdateringer for versjon 10.0.21 av Finance and Operations-apper (oktober 2021)](/dynamics365/fin-ops-core/dev-itpro/get-started/whats-new-platform-updates-10-0-21). |
|Visning av utvidede rapporter for ytelsesjournaler | Denne funksjonen blir aktivert som standard i den neste utrullingen. |
## <a name="see-also"></a>Se også
[Nyheter eller endringer i Human Resources](hr-admin-whats-new.md)</br>
[Oversikt over lanseringsbølge 2 i 2021 for Dynamics 365 Human Resources](/dynamics365-release-plan/2021wave2/human-resources/dynamics365-human-resources/)</br>
[Oppdatere prosess](hr-admin-setup-update-process.md)</br>
[Behandle funksjoner](hr-admin-manage-features.md)
[!INCLUDE[footer-include](../includes/footer-banner.md)]
| 72.30303 | 366 | 0.790025 | nob_Latn | 0.953457 |
43f2e3e0b6fe74a8ff6c9d8facd6a2c073f3053c | 1,440 | md | Markdown | docs/relational-databases/errors-events/mssqlserver-3452-database-engine-error.md | PowerBee-AK/sql-docs.de-de | f6f4854db855a89c4e49dc0557fa456da060b3c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/errors-events/mssqlserver-3452-database-engine-error.md | PowerBee-AK/sql-docs.de-de | f6f4854db855a89c4e49dc0557fa456da060b3c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/errors-events/mssqlserver-3452-database-engine-error.md | PowerBee-AK/sql-docs.de-de | f6f4854db855a89c4e49dc0557fa456da060b3c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: MSSQLSERVER_3452
title: MSSQLSERVER_3452 | Microsoft-Dokumentation
ms.custom: ''
ms.date: 04/04/2017
ms.prod: sql
ms.reviewer: ''
ms.technology: supportability
ms.topic: reference
helpviewer_keywords:
- 3452 (Database Engine error)
ms.assetid: bf838f02-7186-4b33-b01e-361b0c02de1f
author: MashaMSFT
ms.author: mathoma
ms.openlocfilehash: 3e8edbc04cc3f55e867aaa4376f56b7d78715d5d
ms.sourcegitcommit: 33f0f190f962059826e002be165a2bef4f9e350c
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 01/30/2021
ms.locfileid: "99201583"
---
# <a name="mssqlserver_3452"></a>MSSQLSERVER_3452
[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
## <a name="details"></a>Details
| attribute | Wert |
| :-------- | :---- |
|Produktname|SQL Server|
|Ereignis-ID|3452|
|Ereignisquelle|MSSQLSERVER|
|Komponente|SQLEngine|
|Symbolischer Name|REC_CHECKIDENTITY|
|Meldungstext|Bei der Wiederherstellung der '%.*ls'-Datenbank (%d) wurden mögliche inkonsistente Identitätswerte in der Tabelle mit der ID %d erkannt. Führen Sie DBCC CHECKIDENT ('%.\*ls') aus.|
## <a name="explanation"></a>Erklärung
Beim Upgrade auf [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] wurde vom Prozess zum Wiederherstellen der Identitätswerte in der Datenbank eine Inkonsistenz in den Metadaten festgestellt.
## <a name="user-action"></a>Benutzeraktion
Führen Sie DBCC CHECKIDENT aus.
| 34.285714 | 197 | 0.75 | deu_Latn | 0.42994 |
43f3520351fb86c4fea73b748b6b3f035dbbeadf | 2,711 | md | Markdown | README.md | mgsod/imgZip | 6f15023ebc936d06c9a6ce7223c91f5444e55c2d | [
"MIT"
] | 27 | 2018-07-17T01:03:11.000Z | 2021-09-29T02:27:27.000Z | README.md | mgsod/imgZip | 6f15023ebc936d06c9a6ce7223c91f5444e55c2d | [
"MIT"
] | 1 | 2020-09-30T11:15:21.000Z | 2020-10-09T08:50:14.000Z | README.md | mgsod/imgZip | 6f15023ebc936d06c9a6ce7223c91f5444e55c2d | [
"MIT"
] | 17 | 2018-12-22T08:07:24.000Z | 2021-09-09T07:29:33.000Z | # imgZip
图片压缩插件
<a href="https://www.npmjs.org/package/imgzip">
<img src="https://img.shields.io/npm/v/imgzip.svg">
</a>
<a href="https://npmcharts.com/compare/imgzip?minimal=true">
<img src="http://img.shields.io/npm/dm/imgzip.svg">
</a>
### Demo示例
[图片压缩](https://unpkg.com/imgzip@2.0.8/example/index.html)
### 安装
#### npm
```
npm i imgzip
```
#### script
````
<script src="https://unpkg.com/imgzip@2.0.8/dist/index.min.js"></script>
````
`@2.0.8`为固定版本,可自行调整
### 使用方法
#### 2.x版本（支持ts）
```javascript
import imgzip from "imgzip";
export default {
name: "App",
mounted() {
// 监听选择文件
document.getElementById("file").onchange = function () {
// @2.x版本后采用 class Api。所以需要 new 一个 imgZip 对象
let compress = new imgzip({ quality: 0.5 });
// 调用图片压缩
compress.photoCompress(this.files[0], function (base64) {
// document.getElementById('img').src = base64 //预览图片
// 转 blob 流上传 convertBase64UrlToBlob函数为 imgzip 的静态函数
let blob = imgzip.convertBase64UrlToBlob(base64);
let formData = new FormData();
formData.append("file", blob, "file_" + Date.parse(new Date()) + ".jpg"); // 文件对象
// 上传操作....
});
};
},
};
```
### 函数说明
> @2.x版本后改用class api, 原`photoCompress`函数中传入的`options`参数改为实例化imgzip时传入。
* new imgZip(options)
| 参数 | 说明 | 是否必须 | 默认值 |
| ------ | ------ | ------ | ------ |
| options.width | 图片宽度 | 否 | 图片原始宽度 |
| options.height | 图片高度 | 否 | 图片原始高度 |
| options.quality | 图片质量 | 否 | 0.7 |
* photoCompress(图片压缩函数) 无返回值
| 参数 | 说明 | 是否必须 | 默认值 |
| ------ | ------ | ------ | ------ |
| file | 文件对象(Blod) | 是 | - ||
| callback | 压缩后回调函数,回调参数返回压缩后的base64编码 | 是 | - |
#### 1.x版本(不支持ts)
```javascript
import imgzip from "imgzip";
export default {
name: "App",
mounted() {
// 监听选择文件
document.getElementById("file").onchange = function () {
// 调用图片压缩
imgzip.photoCompress(this.files[0], {}, function (base64) {
// document.getElementById('img').src = base64 //预览图片
// 转 blob 流上传
let blob = imgzip.convertBase64UrlToBlob(base64);
let formData = new FormData();
formData.append("file", blob, "file_" + Date.parse(new Date()) + ".jpg"); // 文件对象
// 上传操作....
});
};
},
};
```
### 函数说明
* photoCompress(图片压缩函数)
| 参数 | 说明 | 是否必须 | 默认值 |
| ------ | ------ | ------ | ------ |
| file | 文件对象(Blod) | 是 | - |
| options | 压缩参数(宽/高/质量)| 否 | {width:图片高度,height:图片宽高比,quality:0.7}|
| callback | 压缩后回调函数,回调参数返回压缩后的base64编码 | 是 | - |
* convertBase64UrlToBlob(base64编码转blod流) 1.x版本和2.x版本均为`imgzip`的静态函数
| 参数 | 说明 | 是否必须 | 默认值 | 返回值 |
| ------ | ------ | ------ | ------ | ------ |
| base64 | 图片base64编码 | 是 | - | Blod |
| 22.04065 | 89 | 0.558466 | yue_Hant | 0.533294 |
43f3c424f0db126a3df33e45239388cdeca7b918 | 5,885 | md | Markdown | includes/cdn-app-dev-prep.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/cdn-app-dev-prep.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/cdn-app-dev-prep.md | RobAaldijk/azure-docs.nl-nl | 519c7fc80075795af2670d665d1d93078faf7a87 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
author: zhangmanling
ms.service: azure-cdn
ms.topic: include
ms.date: 11/21/2018
ms.author: mazha
ms.openlocfilehash: 4967991b0edaa854acbf6b308596859d662311fe
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 10/09/2020
ms.locfileid: "91316750"
---
## <a name="prerequisites"></a>Vereisten
Voordat u de CDN-beheer code schrijft, moet u een aantal voor bereidingen treffen om de code te laten communiceren met de Azure Resource Manager. Als u deze voor bereiding wilt uitvoeren, moet u het volgende doen:
* Een resource groep maken die het CDN-profiel bevat dat in deze zelf studie is gemaakt
* Azure Active Directory configureren om verificatie voor de toepassing te bieden
* Machtigingen Toep assen op de resource groep zodat alleen geautoriseerde gebruikers van uw Azure AD-Tenant kunnen communiceren met het CDN-profiel
### <a name="creating-the-resource-group"></a>De resourcegroep maken
1. Meld u aan bij [Azure Portal](https://portal.azure.com).
2. Klik op **een resource maken**.
3. Zoek naar **resource groep** en klik in het deel venster Resource groep op **maken**.
3. Geef een naam op voor de resource groep *CdnConsoleTutorial*. Selecteer uw abonnement en kies een locatie bij u in de buurt. Als u wilt, kunt u klikken op het selectie vakje **vastmaken aan dash board** om de resource groep vast te maken aan het dash board in de portal. Vastmaken maakt het gemakkelijker om later te vinden. Nadat u uw selecties hebt gemaakt, klikt u op **maken**.
4. Als u de resource groep hebt gemaakt, kunt u deze vinden door te klikken op **Bladeren**en vervolgens op **resource groepen**. Klik op de resource groep om deze te openen. Noteer de **abonnements-id**. U hebt deze later nodig.
### <a name="creating-the-azure-ad-application-and-applying-permissions"></a>De Azure AD-toepassing maken en machtigingen Toep assen
Er zijn twee benaderingen voor app-verificatie met Azure Active Directory: afzonderlijke gebruikers of een service-principal. Een Service-Principal is vergelijkbaar met een service account in Windows. In plaats van een bepaalde gebruikers machtigingen te verlenen voor interactie met de CDN-profielen, worden er in plaats daarvan machtigingen verleend aan de Service-Principal. Service-principals worden doorgaans gebruikt voor geautomatiseerde, niet-interactieve processen. Hoewel deze zelf studie een interactieve console-app schrijft, zullen we zich richten op de Service-Principal-benadering.
Het maken van een Service-Principal bestaat uit verschillende stappen, waaronder het maken van een Azure Active Directory-toepassing. We gaan [deze zelf studie volgen](../articles/active-directory/develop/howto-create-service-principal-portal.md)om deze te maken.
> [!IMPORTANT]
> Zorg ervoor dat u alle stappen in de [gekoppelde zelf studie](../articles/active-directory/develop/howto-create-service-principal-portal.md)volgt. Het is *belang rijk* dat u deze precies zoals beschreven uitvoert. Noteer uw **Tenant-id**, **Tenant domein naam** (meestal een *. onmicrosoft.com* -domein, tenzij u een aangepast domein hebt opgegeven), **client-id**en **client verificatie sleutel**, aangezien deze gegevens later nodig zijn. Zorg ervoor dat u uw **client-id** en **client verificatie sleutel**beveiligt, omdat deze referenties door iedereen kunnen worden gebruikt om bewerkingen uit te voeren als service-principal.
>
> Wanneer u de stap met de naam multi tenant-toepassing configureren kiest, selecteert u **Nee**.
>
> Wanneer u de stap van de [toepassing aan een rol toewijst](../articles/active-directory/develop/howto-create-service-principal-portal.md#assign-a-role-to-the-application), gebruikt u de resource groep die u eerder hebt gemaakt, *CdnConsoleTutorial*, maar in plaats van de rol **lezer** , wijst u de rol **Inzender profiel bijdrager** toe. Ga terug naar deze zelf studie nadat u de rol van de toepassing **Inzender voor CDN-profielen** voor uw resource groep hebt toegewezen.
>
>
Zodra u de Service-Principal hebt gemaakt en de rol **Inzender voor CDN-profiel** hebt toegewezen, moet de Blade **gebruikers** voor uw resource groep er ongeveer als volgt uitzien.
### <a name="interactive-user-authentication"></a>Interactieve gebruikers verificatie
Als u in plaats van een Service-Principal liever interactieve afzonderlijke gebruikers verificatie hebt, is het proces vergelijkbaar met dat voor een service-principal. U moet dezelfde procedure volgen, maar een paar kleine wijzigingen aanbrengen.
> [!IMPORTANT]
> Voer de volgende stappen uit als u ervoor kiest om afzonderlijke gebruikers verificatie te gebruiken in plaats van een service-principal.
>
>
1. Kies bij het maken van uw toepassing in plaats van **Webtoepassing** **systeem eigen toepassing**.
2. Op de volgende pagina wordt u gevraagd om een **omleidings-URI**. De URI wordt niet gevalideerd, maar onthoud wat u hebt ingevoerd. U hebt deze later nodig.
3. U hoeft geen **client verificatie sleutel**te maken.
4. In plaats van een Service-Principal toe te wijzen aan de rol **Inzender voor CDN-profielen** , gaan we afzonderlijke gebruikers of groepen toewijzen. In dit voor beeld ziet u dat er een CDN- *demo gebruiker* aan de rol van de **CDN-profiel bijdrage** is toegewezen.
| 86.544118 | 636 | 0.780969 | nld_Latn | 0.999406 |
43f3f7d07ef5a2d4ab198dee6c8084933f4fd3ca | 23 | md | Markdown | README.md | linhongxu2009/chuyisanbanceshi | 04a9e786c63085433ed2a9e82f575563dc96e2fb | [
"MIT"
] | null | null | null | README.md | linhongxu2009/chuyisanbanceshi | 04a9e786c63085433ed2a9e82f575563dc96e2fb | [
"MIT"
] | null | null | null | README.md | linhongxu2009/chuyisanbanceshi | 04a9e786c63085433ed2a9e82f575563dc96e2fb | [
"MIT"
] | null | null | null | # chuyisanbanceshi
测试用
| 7.666667 | 18 | 0.826087 | vie_Latn | 0.360313 |
43f54a7dca7cb6b931645d3b760d5658c38b4de3 | 284 | md | Markdown | iot-c-reference/iot-c-ref-iothub-client-core-common-h/iothub-client-connection-statusstrings.md | nschonni/azure-reference-other | 6ab55a08d43984965d4e75fc8ebfa8e477819cf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | iot-c-reference/iot-c-ref-iothub-client-core-common-h/iothub-client-connection-statusstrings.md | nschonni/azure-reference-other | 6ab55a08d43984965d4e75fc8ebfa8e477819cf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | iot-c-reference/iot-c-ref-iothub-client-core-common-h/iothub-client-connection-statusstrings.md | nschonni/azure-reference-other | 6ab55a08d43984965d4e75fc8ebfa8e477819cf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | # IOTHUB_CLIENT_CONNECTION_STATUSStrings()
## Syntax
\#include "[azure-iot-sdk-c/iothub_client/inc/iothub_client_core_common.h](../iot-c-ref-iothub-client-core-common-h.md)"
```C
const char* IOTHUB_CLIENT_CONNECTION_STATUSStrings(
IOTHUB_CLIENT_CONNECTION_STATUS value
);
```
| 23.666667 | 122 | 0.778169 | yue_Hant | 0.907766 |
43f638e411b6e65e879ffabdb7f7b577686569f8 | 10,394 | md | Markdown | windows-driver-docs-pr/audio/audio-endpoint-builder-algorithm.md | thethales/windows-driver-docs | 55455d5e0ef9b8087e36c3bac7301b0db8ce79ba | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-30T20:31:06.000Z | 2021-11-30T20:31:06.000Z | windows-driver-docs-pr/audio/audio-endpoint-builder-algorithm.md | thethales/windows-driver-docs | 55455d5e0ef9b8087e36c3bac7301b0db8ce79ba | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-driver-docs-pr/audio/audio-endpoint-builder-algorithm.md | thethales/windows-driver-docs | 55455d5e0ef9b8087e36c3bac7301b0db8ce79ba | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Audio Endpoint Builder Algorithm
description: Audio Endpoint Builder Algorithm
ms.assetid: 2338bca7-5743-42c3-9baf-ac4a54cf0393
ms.date: 04/20/2017
ms.localizationpriority: medium
---
# Audio Endpoint Builder Algorithm
In Windows Vista and later versions of Windows, the AudioEndpointBuilder is a system service that enumerates, initializes, and activates the audio endpoints in a system. This topic provides an overview of the algorithm that is used by the AudioEndpointBuilder service.
The AudioEndpointBuilder service uses an algorithm to discover and enumerate endpoints. The algorithm was designed to simplify the system access to multiplexed (MUXed) capture devices and to help work with topologies that involve multiple host pins and multiple bridge pins, or both.
In Windows XP, the audio model used the term audio device to refer to a conceptual device in the Plug and Play (PnP) tree. In Windows Vista and later versions of Windows, the concept of an audio device has been redesigned to better represent the device that the user physically interacts with.
With two new APIs in Windows Vista, [MMDevice API](/windows/win32/coreaudio/mmdevice-api) and [WASAPI](/windows/win32/coreaudio/wasapi), you can access and manipulate these new audio devices. The MMDevice API refers to the new audio devices as endpoints.
The AudioEndpointBuilder service monitors the [**KSCATEGORY\_AUDIO**](../install/kscategory-audio.md) class for device interface arrivals and removals. When an audio device driver registers a new instance of the KSCATEGORY\_AUDIO device interface class, the AudioEndpointBuilder service detects the device interface notification and uses an algorithm to examine the topology of the audio devices in the system and take appropriate action.
The following list summarizes how the algorithm that is used by AudioEndpointBuilder works:
1. Looks for any unconnected bridge pins.
2. Creates an endpoint for any unconnected bridge pins. For example, when the AudioEndpointBuilder finds an unconnected bridge pin with a pin-category GUID of KSNODETYPE\_SPEAKER, it creates a speaker endpoint for this bridge pin. For more information about KSNODETYPE\_SPEAKER and other pin-category GUIDS, see Ksmedia.h in WinDDK\\<build number>\\inc\\api.
3. Sets the default properties for the endpoint. For example, AudioEndpointBuilder sets the name, icon, and the form factor.
4. Determines whether there is a path from the endpoint to a host pin that supports pulse code modulation (PCM), audio codec-3 (AC3), or Windows media video (WMV). A host pin is a KSPIN structure with its Communication member set to KSPIN\_COMMUNICATION\_SINK or KSPIN\_COMMUNICATION\_BOTH. For more information about the KSPIN structure, see [**KSPIN**](/windows-hardware/drivers/ddi/ks/ns-ks-_kspin).
5. Populates the endpoint PropertyStore with property information from the registry keys of the audio device interface.
6. Sets the state of the endpoint. The state of the endpoint can be one of the following three values:
- Active. This indicates that a path exists as described in Step 4.
- Unplugged. If the audio device supports jack detection, this state indicates that a path exists for the endpoint, and the jack is unplugged from the physical connector on the audio adapter.
- Not present. This state indicates that a path was not found in Step 4, and jack detection is not supported by this endpoint.
7. Sets this endpoint as the default endpoint, if that is what is specified in the associated INF file.
After the endpoints have been enumerated, clients of the audio system can manipulate them directly by using the new Windows Vista APIs (as indicated previously) or indirectly by using the more familiar APIs such as Wave, [DirectShow](/windows/win32/directshow/directshow) or [DirectSound.](/previous-versions/windows/desktop/bb318665(v=vs.85)) New API methods have been provided so that audio clients can start with the MMDevice ID of an endpoint and access the Wave or DirectSound ID for the same endpoint.
When you use endpoints, you can take advantage of the following:
- The same globally unique ID (GUID) is available regardless of how often you restart your machine. Having this persistent GUID is more reliable than saving a waveOut ID or a friendly name for the endpoint.
- The same PropertyStore is available regardless of how often you restart your machine. The audio device-related metadata is saved in the endpoint PropertyStore.
- Multiplexed (MUX) and de-multiplexed (DEMUX) pins are managed automatically and enumerated by the AudioEndpointBuilder service.
If you develop your own audio device driver and INF file to work with your audio device, and develop an audio application, or both, it is best to be aware of the following issues and best practices. When you develop drivers and applications with these recommendations in mind, you produce drivers, INF files, and audio clients that work more effectively with the AudioEndpointBuilder.
- Naming convention. The naming convention that is used for the endpoints is based on the friendly names of the bridge pins. However, in the case of speaker endpoints, the name has been hardcoded to "Speakers" and cannot be altered by your driver or a third-party application.
- Suboptimal topologies. Certain topologies are considered to be suboptimal because of the algorithm that is used by the AudioEndpointBuilder to enumerate endpoints. For example, when you create one of these suboptimal topologies, you create host pins that have hidden endpoints and cannot be seen by the AudioEndpointBuilder or splitters (split endpoints) that the AudioEndpointBuilder cannot link to their associated host pins.
- **Hidden endpoints**
In the following diagram, the KS filter is shown to have two host pins that are connected to a single bridge pin (Speaker).
![problematic topology showing ac-3 host pin with hidden endpoint on left side is individual pcm and ac-3]sharing single filter (images/hidden-endpoint-bad.png)
When the AudioEndpointBuilder discovers this bridge pin, it traces a path back to only one of the host pins, sets the default values for the bridge pin, creates and activates a Speaker endpoint, and continues to discover other bridge pins. Thus, the other host pin remains hidden from the AudioEndpointBuilder.
In the preceding diagram, the problematic topology has been redesigned so that the AudioEndpointBuilder can discover the two host pins (PCM and AC-3/ PCM) because it can now see two bridge pins (Speaker and SPDIF).
- **Splitters**
Another type of suboptimal topology is created when one host pin connects to more than one bridge pin. The following diagram shows a topology in which a PCM host pin connects to a Speaker bridge pin and a SPDIF bridge pin.
In this case the AudioEndpointBuilder discovers one bridge pin and traces a path back to the PCM host pin, sets default values, and then creates and activates a Speaker endpoint. When the AudioEndpointBuilder discovers the next bridge pin, it traces a path back to the same PCM host pin, sets default values, and then creates and activates a SPDIF endpoint. However, although both endpoints have been initialized and activated, streaming to one of them makes it impossible to stream to the other at the same time; in other words, they are mutually exclusive endpoints.
The following diagram shows a redesign of this topology in which separate connections exist. This design makes it possible for the AudioEndpointBuilder to trace a path back to the PCM host pin for each of the two bridge pins.
- Endpoint format. When the audio engine is running in shared mode, the format for the endpoint assumes a specific setting as directed by the INF file at the time of installation. For example, the audio driver for an audio device uses its associated INF file to set the default endpoint to a 44.1-kHz, 16-bit, stereo PCM format. After installation, you must use Control Panel or a third-party application to change the endpoint format.
- Default device. The endpoint that is set as the default device is selected at the time of installation by using information in the INF file. After installation has completed, you must use Control Panel or a third-party application to select another endpoint to be the default endpoint.
**Note** If your INF file does not select an endpoint to be set as default during installation, a client application can use the MMDevice API to select an endpoint. The API bases its selection on the form factor rank and whether the endpoint is a render or a capture endpoint. The following table shows the selection order.
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th align="left">Render rank</th>
<th align="left">Capture rank</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td align="left"><p>Speakers</p></td>
<td align="left"><p>Microphone</p></td>
</tr>
<tr class="even">
<td align="left"><p>Line-out</p></td>
<td align="left"><p>Line-in</p></td>
</tr>
<tr class="odd">
<td align="left"><p>SPDIF</p></td>
<td align="left"><p>SPDIF</p></td>
</tr>
</tbody>
</table>
If you use the MMDevice API to select a default endpoint and the available endpoints are ranked the same, the MMDevice API will alphabetize the Endpoint IDs to determine which endpoint to select as default. For example, if an audio adapter has both line-out and line-in connectors, and the associated INF file does not select either one to be the default at the time of installation, the MMDevice API identifies which Endpoint IDs is first alphabetically and sets that connector as the default. This selection persists after you restart the system because the Endpoint IDs are persistent. However, the selection does not persist if a higher-ranking endpoint (for example, a second adapter with a microphone connector) appears in the system.
| 83.822581 | 740 | 0.785453 | eng_Latn | 0.998844 |
43f6bf54e53ae08f705addd6206238121684b45c | 306 | md | Markdown | components/docs-chef-io/content/habitat/glossary.md | skylerto/habitat | 4fa20d0742bf0cb09d43f9695aef2b60893162cb | [
"Apache-2.0"
] | null | null | null | components/docs-chef-io/content/habitat/glossary.md | skylerto/habitat | 4fa20d0742bf0cb09d43f9695aef2b60893162cb | [
"Apache-2.0"
] | null | null | null | components/docs-chef-io/content/habitat/glossary.md | skylerto/habitat | 4fa20d0742bf0cb09d43f9695aef2b60893162cb | [
"Apache-2.0"
] | null | null | null | +++
title = "Glossary"
draft = false
[menu]
[menu.habitat]
title = "Glossary"
identifier = "habitat/reference/glossary.md Glossary"
parent = "habitat/reference"
+++
[\[edit on GitHub\]](https://github.com/habitat-sh/habitat/blob/master/components/docs-chef-io/content/habitat/glossary.md)
| 21.857143 | 123 | 0.696078 | yue_Hant | 0.127017 |
43f7bec43da1de4400cc03ee594fcd19acc5c9e1 | 4,727 | md | Markdown | Markdown/10000s/10000/moments rode.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | 2 | 2022-01-19T09:04:58.000Z | 2022-01-23T15:44:37.000Z | Markdown/00500s/03500/moments rode.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | null | null | null | Markdown/00500s/03500/moments rode.md | rcvd/interconnected-markdown | 730d63c55f5c868ce17739fd7503d562d563ffc4 | [
"MIT"
] | 1 | 2022-01-09T17:10:33.000Z | 2022-01-09T17:10:33.000Z | - To the clothes the you with. By the it if information as to. Woods parliament he Emma the moon the. And that threatened weapons the tries dear. The in the to took. [[rules empty]] of as like it evening. Say crisis hath by deliberately all. New thus i in that to. Superior not with the had in. In was their in were. Kinds the freedom and opens [[impression]]. Eyes king bride most of unjust waiting. He the who grasp keep that England. To unpleasant spirits but worlds thus cold bad. Medium an your would sign. Italian it to i he black. Brushed here art robert idea how. Morning test the he taken. Had world travelled afternoon drop and from how. Along morning to in of and he.
- Farming far the what remains or him to. He and the grew rule and. Gentleman the version arms be out. Into knows there pole that spanish obvious. Knew looked i this foundation them doctor clothed. Do the about twelve spirit he. Its to vexed of to the and. Stewart i you thats with an. To ship Mr was [[forces]] spite answer. Over or sorts from her i sixty. It society such been street. The father shoulder and Ive than. Epic the anger the by her. The with allow the the [[dressed]] they. [[owner]] [[dressed]] Wilson theory convinced. That and the objects the we i. Into it thing of such Nevada friendliness i. Such very cruel cost assured to but. Of chair be creation till promised parts little somebody. Upon account of married soon will. Just a first of the. Before in he. Is will who all while wars why. She convert of of when fact of is. Done offered itself irony [[lifted]] means at. Principal p my file good also was of. The disposition so in already possible. No you [[farther collection]] titles car axe. Think accomplishment full and paths called in. He united character to carriage the maps. Cases brains on sound was whom. Rewarded new when could make hearty dark. And washed the and whose he they the. No are fact had show face place.
- Acquaintance discovered have of the now. He or [[process]] till with in make. Indeed able ask the and and crept comes. Next path mould something own of. Longer the of following stand Oliver turn. This cells with of in more. Is it looking was me of. So this how party disconcerted gate where. Of matter but dead bride illustrate. To on in and to to. Of of whom to not of presence. The and minutes of detached Jane asleep. To neither starting who lord observed to. Kingdom they one acknowledge flash most had convince.
- That [[buried lifted]] however death upon on gradually. Madam centuries sleep listened reward. Was are was and of correct may. U in influences the. Is expensive of so this but three expect. For offence vanish in rights he. Or in also one slow i. Side those to much pupil never whether. Looked her and the make aint. And like Tennyson you the ways. Great but her nose like its. To wedding required close measures made of the. Poison speed so [[lifted]] on savages my. [[Sunday]] the floor of by just time it. Historical their these hardly what is my. Your in still my. Place them with you i. From perfect myself jolly hand going. That something your between balanced luxury in do. [[happen included]] of work gets freely [[completely post]] them. Be the were the perpendicular to down [[sentence noise]]. Suddenly conscience by of the sacrifice he of. Played [[collection reasons]] were with was adequate with. They loves as of however.
- Of trailer no to thou c perish to and. Reply on with good did regarding notice which. One attention house than better order glory. Would been had said when baron. Of visible for have were for. To of of it the. Near betray the into one. And dropping from at her. Live has trade the of into. Out nobody his now sorrow road summoned. The the nearly say iron we therein. The quarry with is one. Of in or may the an. Paid ex back to of. Too or. Many and greater de slide prevent may eyes. Beneath the advance deals their with in. Detach as killed of for something dishonour are. Type our age she i was kingdom reached. His of had on marriage me say. Some in stopped for she to impressed. Of to step treat anger to it released. More state at life the the. Circumstance frozen was of grapes so. Nothing as some account reflecting or history handsome. Medium the portion tom or you and. Of following heaven works bite. Under foot on her that road the against.
- Harness of the he not. To railway opinion saw seemed information everyone were. Lord coming Christians with impetuous god. Large deny in Kate have cynical their. Intent perhaps granted your her trace lake. Going until at place. Her passage when nest side back. No group madly the the. Who and had wished Alice hair was of. From be his not meet did. I being system the been her and. | 787.833333 | 1,249 | 0.773429 | eng_Latn | 0.99993 |
43f7d9730ea84e8afe5e6e7e1b9bea7be2eef84c | 1,332 | md | Markdown | README.md | Statikman619/Tech-Blog | 908c9b2487785b12671def46b5d607c5c1b1b3c9 | [
"MIT"
] | null | null | null | README.md | Statikman619/Tech-Blog | 908c9b2487785b12671def46b5d607c5c1b1b3c9 | [
"MIT"
] | null | null | null | README.md | Statikman619/Tech-Blog | 908c9b2487785b12671def46b5d607c5c1b1b3c9 | [
"MIT"
] | null | null | null | # Tech Blog
GitHubLink https://github.com/Statikman619/Tech-Blog
KerokuLink https://pacific-ridge-11967.herokuapp.com/
[](https://opensource.org/licenses/MIT)
## Table of Contents
* [Title](#Title)
* [Description](#description)
* [Installation](#installation)
* [Usage](#usage)
* [License](#license)
* [Test](#test)
* [Username](#username)
* [Email](#license)
## Description
This app is a CMS-style blog site similar to a Wordpress site, where developers can publish their blog posts and comment on other developers’ posts as well.
## Installation
Clone this repository to receive all my files. Once you have my code make sure you are in the correct file directory.
in the command line run "npm install" in the terminal to download all the needed dependencies.
## Usage
The user can publish articles, blog posts, and thoughts and opinions.
## License MIT
## Contributors
Mike with the help of Herm and Elma during office hours and my awesome tutor Andrew.
## Test
No tests at this time.
## Questions
Contact me:
Github:[Statikman619](https://github.com/Statikman619)
Email:[martinez.michael02@gmail.com](https://github.com/Statikman619)
| 38.057143 | 157 | 0.759009 | eng_Latn | 0.797184 |
43f87d87c2a612a240e182249c96714eb8a3957f | 7,934 | md | Markdown | docs/svelte-testing-library/api.md | mmintel/testing-library-docs | f1fa42ea41d4f528dd5d244fdf2bdececf4d259c | [
"MIT"
] | null | null | null | docs/svelte-testing-library/api.md | mmintel/testing-library-docs | f1fa42ea41d4f528dd5d244fdf2bdececf4d259c | [
"MIT"
] | null | null | null | docs/svelte-testing-library/api.md | mmintel/testing-library-docs | f1fa42ea41d4f528dd5d244fdf2bdececf4d259c | [
"MIT"
] | null | null | null | ---
id: api
title: API
sidebar_label: API
---
- [`@testing-library/dom`](#testing-library-dom)
- [`render`](#render)
- [`cleanup`](#cleanup)
- [`act`](#act-async)
- [`fireEvent`](#fireevent-async)
---
## `@testing-library/dom`
This library re-exports everything from the DOM Testing Library
(`@testing-library/dom`). See the
[documentation](../dom-testing-library/api-queries.md) to see what goodies you
can use.
📝 `fireEvent` is an `async` method when imported from
`@testing-library/svelte`. This is because it calls [`tick`][svelte-tick] which
tells Svelte to apply any new changes to the DOM.
## `render`
```js
import { render } from '@testing-library/svelte'
const { results } = render(
YourComponent,
{ ComponentOptions },
{ RenderOptions }
)
```
### Component Options
These are the options you pass when instantiating your Svelte `Component`.
Please refer to the
[Client-side component API](https://svelte.dev/docs#Client-side_component_API).
📝 If the only option you're passing in is `props`, then you can just pass them
in directly.
```js
// With options.
const { results } = render(YourComponent, {
target: MyTarget,
props: { myProp: 'value' },
})
// Props only.
const { results } = render(YourComponent, { myProp: 'value' })
```
### Render Options
| Option | Description | Default |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------- | --------------- |
| `container` | The HTML element the component is mounted into. | `document.body` |
| `queries` | Queries to bind to the container. See [getQueriesForElement](../dom-testing-library/api-helpers#within-and-getqueriesforelement-apis). | `null` |
### Results
| Result | Description |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `container` | The HTML element the component is mounted into. |
| `component` | The newly created Svelte component. Generally, this should only be used when testing exported functions, or when you're testing developer facing API's. Outside of said cases avoid using the component directly to build tests, instead of interacting with the rendered Svelte component, work with the DOM. Have a read of [Avoid the Test User](https://kentcdodds.com/blog/avoid-the-test-user) by Kent C. Dodds to understand the difference between the **end user** and **developer user**. |
| `debug` | Logs the `container` using [prettyDom](https://testing-library.com/docs/dom-testing-library/api-helpers#prettydom). |
| `unmount` | Unmounts the component from the `target` by calling `component.$destroy()`. |
| `rerender` | Calls render again destroying the old component, and mounting the new component on the original `target` with any new options passed in. |
| `...queries` | Returns all [query functions](https://testing-library.com/docs/dom-testing-library/api-queries) that are binded to the `container`. If you pass in `query` arguments than this will be those, otherwise all. |
## `cleanup`
> You don't need to import or use this, it's done automagically for you!
Unmounts the component from the container and destroys the container.
📝 When you import anything from the library, this automatically runs after each
test. If you'd like to disable this then set `process.env.STL_SKIP_AUTO_CLEANUP`
to true or import `dont-clean-up-after-each` from the library.
```js
import { render, cleanup } from '@testing-library/svelte'
afterEach(() => {
cleanup()
}) // Default on import: runs it after each test.
render(YourComponent)
cleanup() // Or like this for more control.
```
## `act` (`async`)
An `async` helper method that takes in a `function` or `Promise` that is
immediately called/resolved, and then calls [`tick`][svelte-tick] so all pending
state changes are flushed, and the view now reflects any changes made to the
DOM.
## `fireEvent` (`async`)
Calls `@testing-library/dom` [fireEvent](../dom-testing-library/api-events). It
is an `async` method due to calling [`tick`][svelte-tick] which tells Svelte to
flush all pending state changes, basically it updates the DOM to reflect the new
changes.
**Component**
```html
<script>
let count = 0
function handleClick() {
count += 1
}
</script>
<button on:click="{handleClick}">Count is {count}</button>
```
**Test**
```js
import '@testing-library/jest-dom/extend-expect'
import { render, fireEvent } from '@testing-library/svelte'
import Comp from '..'
test('count increments when button is clicked', async () => {
const { getByText } = render(Comp)
const button = getByText('Count is 0')
// Option 1.
await fireEvent.click(button)
expect(button).toHaveTextContent('Count is 1')
// Option 2.
await fireEvent(
button,
new MouseEvent('click', {
bubbles: true,
cancelable: true,
})
)
expect(button).toHaveTextContent('Count is 2')
})
```
[svelte-tick]: https://svelte.dev/docs#tick
| 50.858974 | 502 | 0.422486 | eng_Latn | 0.936682 |
43f91cdef362f299125309910e9755a4809ef031 | 1,987 | md | Markdown | README.md | aryelgois/br-timezone | 7f8f30f6dabe3ce26c20f158807e5213b49fb4dd | [
"MIT"
] | 2 | 2022-01-21T15:10:57.000Z | 2022-01-21T15:21:47.000Z | README.md | aryelgois/br-timezone | 7f8f30f6dabe3ce26c20f158807e5213b49fb4dd | [
"MIT"
] | null | null | null | README.md | aryelgois/br-timezone | 7f8f30f6dabe3ce26c20f158807e5213b49fb4dd | [
"MIT"
] | null | null | null | # Fusos horários BR
> Determine o fuso horário no Brasil de acordo com o Estado ou Cidade.
Atualmente o Brasil observa quatro fusos horários<sup>[1]</sup>, mas os seus códigos estão obsoletos<sup>[2],</sup><sup>[3],</sup><sup>[4],</sup><sup>[5]</sup>. Existem outros códigos de fusos horários com nomes de localidades específicas, e que são utilizados em suas proximidades.
Esse pacote oferece uma função que retorna um código de fuso horário com base na sigla de um Estado (ou Distrito Federal), e opcionalmente em um [código de município do IBGE][ibge_municipios].
Apenas alguns municípios estão mapeados para um fuso horário, a maioria sendo relacionada à [Lei Nº 12.876, de 30 de Outubro de 2013][lei_12.876_2013], que definiu que alguns municípios ao sudoeste do Estado do Amazonas devem seguir o Horário do Acre. Todos os Estados estão mapeados para um fuso horário.
**Atenção**: alguns Estados podem estar mapeados para um fuso horário que não é o utilizado na prática. Sugestões de melhorias são bem-vindas!
## Instalação
```sh
npm install br-timezone
```
## Uso
```ts
import { getBrTimezone } from 'br-timezone'
console.log(getBrTimezone('SP')) // 'America/Sao_Paulo'
console.log(getBrTimezone('SE')) // 'America/Maceio'
console.log(getBrTimezone('AM', '1304062')) // 'America/Rio_Branco'
console.log(getBrTimezone('PE', '2605459')) // 'America/Noronha'
```
## Licença
[MIT License](LICENSE)
[1]: https://pt.wikipedia.org/wiki/Fusos_horários_no_Brasil
[2]: http://www.timezoneconverter.com/cgi-bin/zoneinfo.tzc?s=default&tz=Brazil/DeNoronha
[3]: http://www.timezoneconverter.com/cgi-bin/zoneinfo.tzc?s=default&tz=Brazil/East
[4]: http://www.timezoneconverter.com/cgi-bin/zoneinfo.tzc?s=default&tz=Brazil/West
[5]: http://www.timezoneconverter.com/cgi-bin/zoneinfo.tzc?s=default&tz=Brazil/Acre
[ibge_municipios]: https://www.ibge.gov.br/explica/codigos-dos-municipios.php
[lei_12.876_2013]: http://www.planalto.gov.br/ccivil_03/_Ato2011-2014/2013/Lei/L12876.htm
| 44.155556 | 305 | 0.75843 | por_Latn | 0.984586 |
43f9916505db69164b295e7bf1a7ee412082d782 | 1,479 | md | Markdown | iam/user-guide/switching-roles-(by-a-delegated-party).md | vladimirhasko/docs | 4eb1322e83caf34981f6cc8694adb43dc41325f0 | [
"Apache-2.0"
] | null | null | null | iam/user-guide/switching-roles-(by-a-delegated-party).md | vladimirhasko/docs | 4eb1322e83caf34981f6cc8694adb43dc41325f0 | [
"Apache-2.0"
] | null | null | null | iam/user-guide/switching-roles-(by-a-delegated-party).md | vladimirhasko/docs | 4eb1322e83caf34981f6cc8694adb43dc41325f0 | [
"Apache-2.0"
] | null | null | null | # Switching Roles \(by a Delegated Party\)<a name="en-us_topic_0046613148"></a>
When an account establishes a trust relationship between itself and your account, you become a delegated party. You and all the users you have authorized can switch to the delegating account and manage resources under the delegated permissions.
## Prerequisites<a name="section8625973163627"></a>
- A trust relationship has been established between another account and your account.
- You have obtained the names of the delegating account and created agency.
## Procedure<a name="section1608192323216"></a>
1. Log in to the system as the user created in [3](assigning-permissions-(by-a-delegated-party).md#li695863494610).
> **NOTE:**
>The user created in [3](assigning-permissions-(by-a-delegated-party).md#li695863494610) can switch roles to manage resources for the delegating party.
2. Click the logged-in account in the upper right corner of the page and choose **Switch Role**.
3. On the **Switch Role** page, enter the name of the delegating account.
> **NOTE:**
>The system automatically matches the account to an agency. If the matched agency has not been delegated, you have no permissions to access the account. However, you can remove the agency and select an authorized one from the drop-down list box.
4. Click **OK** to switch to the delegating account.
| 59.16 | 251 | 0.750507 | eng_Latn | 0.997005 |
43f9b9cbab81c6871f7bc576209a8a80d37662ae | 869 | md | Markdown | docs/csharp/misc/cs1702.md | WindOfMind/docs.ru-ru | 5e034322f8f6ce87e425a9217189e8275b54d6e8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/misc/cs1702.md | WindOfMind/docs.ru-ru | 5e034322f8f6ce87e425a9217189e8275b54d6e8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/misc/cs1702.md | WindOfMind/docs.ru-ru | 5e034322f8f6ce87e425a9217189e8275b54d6e8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Предупреждение компилятора (уровень 3) CS1702
ms.date: 07/20/2015
f1_keywords:
- CS1702
helpviewer_keywords:
- CS1702
ms.assetid: 106b9994-c762-44b9-942e-5417cf3dbbab
ms.openlocfilehash: d8d4596bd555a5a0497a2f510f3214874c16de54
ms.sourcegitcommit: 9b552addadfb57fab0b9e7852ed4f1f1b8a42f8e
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 04/23/2019
ms.locfileid: "61652810"
---
# <a name="compiler-warning-level-3-cs1702"></a>Предупреждение компилятора (уровень 3) CS1702
Если ссылка на сборку "Имя сборки 1" соответствует "Имя сборки 2", может понадобиться предоставить политику времени выполнения
Две ссылки на сборки имеют различные номера сборки или редакции, поэтому они не будут автоматически объединены. Для принудительного объединения с помощью директив из CONFIG-файла приложения может потребоваться политика времени выполнения.
| 43.45 | 239 | 0.822785 | rus_Cyrl | 0.752469 |
43f9f0c651aa4da47756e0eb484d669caf2a8cb0 | 854 | md | Markdown | src/routes/faq/growth-chart.md | optk/drmanpreetsethi | 7624d28840e6734e9e55611ca48d2edf624e076b | [
"MIT"
] | null | null | null | src/routes/faq/growth-chart.md | optk/drmanpreetsethi | 7624d28840e6734e9e55611ca48d2edf624e076b | [
"MIT"
] | null | null | null | src/routes/faq/growth-chart.md | optk/drmanpreetsethi | 7624d28840e6734e9e55611ca48d2edf624e076b | [
"MIT"
] | null | null | null | ---
title: 'What is a Growth Chart?'
date: '01/06/2022'
---
The growth chart uses lines to display an average growth path for a child of a certain age, sex, and height. Serial measurements over time are plotted on the growth chart and the trajectory followed over time. Each line indicates a certain percentage of the population that would be that particular height at a particular age. A boy with a height that is plotted on the 25th percentile line, for example, indicates that approximately 25 out of 100 boys his age are shorter than him. Children often do not follow these lines exactly, but most of the time their growth over time is roughly parallel to these lines. A child who has a height plot that is below the 3% line is considered to have short stature compared with the general population.
We use India specific growth charts in our clinic. | 142.333333 | 743 | 0.790398 | eng_Latn | 0.999968 |
43fa1439a043f343e0108ba1b59806a231944f9a | 6,142 | md | Markdown | docs/standard/design-guidelines/general-naming-conventions.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/design-guidelines/general-naming-conventions.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/design-guidelines/general-naming-conventions.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Genel adlandırma kuralları
ms.date: 10/22/2008
ms.technology: dotnet-standard
helpviewer_keywords:
- names [.NET Framework], conflicts
- type names, conflicts
- language-specific type names
- names [.NET Framework], about naming guidelines
- names [.NET Framework], abbreviations
- abbreviation naming guidelines
- acronym naming guidelines
- Hungarian notation
- names [.NET Framework], type names
- names [.NET Framework], acronyms
ms.assetid: d3a77ea1-75d2-4969-a8c3-3e1e3e1aaedc
author: KrzysztofCwalina
ms.openlocfilehash: 9febc7eed7d6dedad6655b51a96694b72b78711b
ms.sourcegitcommit: ccd8c36b0d74d99291d41aceb14cf98d74dc9d2b
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 12/10/2018
ms.locfileid: "53147287"
---
# <a name="general-naming-conventions"></a>Genel adlandırma kuralları
Bu bölümde, sözcük seçimi için ilgili genel adlandırma kuralları kısaltmalar ve kısaltmalar ve öneriler hakkında dile özgü adlarını kullanmaktan kaçınmak kullanma hakkında yönergeler açıklanmaktadır.
## <a name="word-choice"></a>Sözcük seçimi
**✓ DO** kolay okunabilir tanımlayıcı adlarını seçin.
Örneğin, adında bir özellik `HorizontalAlignment` daha İngilizce-daha okunabilirdir `AlignmentHorizontal`.
**✓ DO** okunabilirlik kısaltma ayrıcalık tanıma.
Özellik adı `CanScrollHorizontally` göre daha iyidir `ScrollableX` (x ekseni için belirsiz bir başvuru).
**X DO NOT** alt çizgi, kısa çizgi veya herhangi bir alfasayısal olmayan karakterler kullanın.
**X DO NOT** Macarca gösterimini kullanın.
**X AVOID** kullanılan programlama dilleri anahtar sözcükleriyle yaygın olarak çakışma kimlikleri kullanarak.
Ortak dil belirtimi (CLS), kural 4 göre tüm uyumlu dilin dilin bir anahtar sözcük tanımlayıcı olarak kullanan adlandırılmış öğeleri erişmesini sağlayan bir mekanizma sağlamanız gerekir. Kullanan C# ' ta, örneğin, bu durumda bir kaçış mekanizması olarak oturum @. Ancak, yine de bir yöntemi olmadan bir kaçış dizisi ile kullanmak çok daha zor olduğundan, ortak anahtar sözcükleri önlemek için iyi bir fikirdir.
## <a name="using-abbreviations-and-acronyms"></a>Kısaltmalar ve kısaltmalar kullanma
**X DO NOT** kısaltmalar veya kısaltmalar tanımlayıcı adları bir parçası olarak kullanın.
Örneğin, `GetWindow` yerine `GetWin`.
**X DO NOT** yaygın olarak kabul edilen ve, yalnızca gerekli olduğunda olmaları durumunda bile olmayan kısaltmalar kullanın.
## <a name="avoiding-language-specific-names"></a>Dile özgü adları kaçınma
**✓ DO** dile özgü anahtar sözcükler yerine anlamsal olarak ilginç adları için tür adları kullanın.
Örneğin, `GetLength` daha iyi bir addır `GetInt`.
**✓ DO** bir tanımlayıcı türü ötesinde anlamsal anlamı olduğunda nadir durumlarda dile özgü adı yerine bir genel CLR türü adı kullanın.
Örneğin, bir dönüştürme yöntemi <xref:System.Int64> adlandırılmalıdır `ToInt64`değil `ToLong` (çünkü <xref:System.Int64> C# için bir CLR ad-belirli bir diğer ad `long`). Aşağıdaki tabloda, CLR tür adları (C#, Visual Basic ve C++ için karşılık gelen tür adları için olduğu gibi) kullanarak birkaç temel veri türlerini gösterir.
|C#|Visual Basic|C++|CLR|
|---------|------------------|-----------|---------|
|**sbyte**|**SByte**|**char**|**SByte**|
|**byte**|**Bayt**|**İmzasız char**|**Bayt**|
|**short**|**kısa**|**short**|**Int16**|
|**ushort**|**UInt16**|**İmzasız short**|**UInt16**|
|**int**|**tamsayı**|**int**|**Int32**|
|**uint**|**UInt32**|**işaretsiz int**|**UInt32**|
|**long**|**uzun**|**__int64**|**Int64**|
|**ulong**|**UInt64**|**imzalanmamış __int64**|**UInt64**|
|**float**|**Tek**|**float**|**Tek**|
|**double**|**çift**|**double**|**çift**|
|**bool**|**Boole değeri**|**bool**|**Boole değeri**|
|**char**|**Char**|**wchar_t**|**Char**|
|**string**|**dize**|**dize**|**dize**|
|**object**|**Nesne**|**Nesne**|**Nesne**|
**✓ DO** gibi ortak bir ad kullanın `value` veya `item`, tür adı bir tanımlayıcı bir anlam anlamı yoktur ve parametresinin türü önemli olmadığında nadir durumlarda yinelenen yerine.
## <a name="naming-new-versions-of-existing-apis"></a>Mevcut API'lere yeni sürümlerini adlandırma
**✓ DO** var olan bir API yeni sürümlerini oluştururken eski API için benzer bir ad kullanın.
Bu API'ler arasındaki ilişkiyi vurgulamaya yardımcı olur.
**✓ DO** var olan bir API yeni bir sürümünü belirtmek için bir önek yerine bir sonek ekleme tercih eder.
Bu keşif belgeleri, göz atarken size yardımcı olacak veya IntelliSense kullanma. Çoğu tarayıcı ve IntelliSense tanımlayıcıları alfabetik sırada gösterir çünkü yakın yeni API'leri, API eski sürümü düzenlenecektir.
**✓ CONSIDER** sonek veya bir önek eklemek yerine yepyeni, ancak anlamlı tanımlayıcısını kullanarak.
**✓ DO** sayısal bir sonek özellikle, API varolan adı (yani, sektör standardı ise) mantıklı yalnızca bir ad ve her anlamlı ekleme soneki (veya adının değiştirilmesi) bir uygulama değilse varolan bir API yeni bir sürümünü belirtmek için kullanın ropriate seçeneği.
**X DO NOT** "Eski" (veya benzeri) kullanmak aynı API önceki bir sürümünden ayırt etmek bir tanımlayıcı için soneki.
**✓ DO** 32 bit tamsayı yerine 64 bit tamsayı (uzun tamsayı) üzerinde çalışan API sürümleri Tanıtımı "64" soneki kullanın. Var olan 32-bit API varsa bu yaklaşımı yeterlidir; yapma, yalnızca 64 bit sürümüne sahip yeni API'ler için.
*Kısımları © 2005, 2009 Microsoft Corporation. Tüm hakları saklıdır.*
*İzni Pearson eğitim, Inc. tarafından yeniden yazdırılmaları [çerçeve tasarım yönergeleri: Kuralları, deyimlerini ve yeniden kullanılabilir .NET kitaplıkları, sürüm 2 için desenler](https://www.informit.com/store/framework-design-guidelines-conventions-idioms-and-9780321545619) Krzysztof Cwalina ve Brad Abrams, 22 Eki 2008 Addison Wesley Professional ile Microsoft Windows geliştirme serisi bir parçası olarak yayımlandı.*
## <a name="see-also"></a>Ayrıca bkz.
- [Çerçeve Tasarım Yönergeleri](../../../docs/standard/design-guidelines/index.md)
- [Adlandırma Kuralları](../../../docs/standard/design-guidelines/naming-guidelines.md)
| 58.495238 | 427 | 0.734289 | tur_Latn | 0.99936 |
43fb14f4013529e02b522952a5d809a517ffe65c | 5,408 | md | Markdown | docs/tr/operations/settings/settings-users.md | mnkonkova/ClickHouse | 20a7889909130e81ccb584829271cd5e6bd9ca4c | [
"Apache-2.0"
] | 1 | 2021-08-14T15:28:46.000Z | 2021-08-14T15:28:46.000Z | docs/tr/operations/settings/settings-users.md | mnkonkova/ClickHouse | 20a7889909130e81ccb584829271cd5e6bd9ca4c | [
"Apache-2.0"
] | null | null | null | docs/tr/operations/settings/settings-users.md | mnkonkova/ClickHouse | 20a7889909130e81ccb584829271cd5e6bd9ca4c | [
"Apache-2.0"
] | null | null | null | ---
machine_translated: true
machine_translated_rev: e8cd92bba3269f47787db090899f7c242adf7818
toc_priority: 63
toc_title: "Kullan\u0131c\u0131 Ayarlar\u0131"
---
# Kullanıcı Ayarları {#user-settings}
Bu `users` bu bölüm `user.xml` yapılandırma dosyası kullanıcı ayarlarını içerir.
Bu yapı `users` bölme:
``` xml
<users>
<!-- If user name was not specified, 'default' user is used. -->
<user_name>
<password></password>
<!-- Or -->
<password_sha256_hex></password_sha256_hex>
<networks incl="networks" replace="replace">
</networks>
<profile>profile_name</profile>
<quota>default</quota>
<databases>
<database_name>
<table_name>
<filter>expression</filter>
<table_name>
</database_name>
</databases>
</user_name>
<!-- Other users settings -->
</users>
```
### home/şifre {#user-namepassword}
Şifre düz metin veya SHA256 (hex formatında) belirtilebilir.
- Düz metin içinde bir şifre atamak için (**tavsiye edilmez**bir koyun `password` öğe.
Mesela, `<password>qwerty</password>`. Şifre boş bırakılabilir.
<a id="password_sha256_hex"></a>
- SHA256 karmasını kullanarak bir şifre atamak için, bir `password_sha256_hex` öğe.
Mesela, `<password_sha256_hex>65e84be33532fb784c48129675f9eff3a682b27168c0ea744b2cf58ee02337c5</password_sha256_hex>`.
Kabuktan bir parola oluşturma örneği:
PASSWORD=$(base64 < /dev/urandom | head -c8); echo "$PASSWORD"; echo -n "$PASSWORD" | sha256sum | tr -d '-'
Sonucun ilk satırı şifredir. İkinci satır karşılık gelen SHA256 karmasıdır.
<a id="password_double_sha1_hex"></a>
- MySQL istemcileri ile uyumluluk için, şifre çift SHA1 karma belirtilebilir. İçine yerleştirin `password_double_sha1_hex` öğe.
Mesela, `<password_double_sha1_hex>08b4a0f1de6ad37da17359e592c8d74788a83eb0</password_double_sha1_hex>`.
Kabuktan bir parola oluşturma örneği:
PASSWORD=$(base64 < /dev/urandom | head -c8); echo "$PASSWORD"; echo -n "$PASSWORD" | sha1sum | tr -d '-' | xxd -r -p | sha1sum | tr -d '-'
Sonucun ilk satırı şifredir. İkinci satır karşılık gelen çift SHA1 karmasıdır.
### kullanıcı\_adı / ağlar {#user-namenetworks}
Kullanıcının ClickHouse sunucusuna bağlanabileceği ağların listesi.
Listenin her öğesi aşağıdaki formlardan birine sahip olabilir:
- `<ip>` — IP address or network mask.
Örnekler: `213.180.204.3`, `10.0.0.1/8`, `10.0.0.1/255.255.255.0`, `2a02:6b8::3`, `2a02:6b8::3/64`, `2a02:6b8::3/ffff:ffff:ffff:ffff::`.
- `<host>` — Hostname.
Örnek: `example01.host.ru`.
Erişimi denetlemek için bir DNS sorgusu gerçekleştirilir ve döndürülen tüm IP adresleri eş adresiyle karşılaştırılır.
- `<host_regexp>` — Regular expression for hostnames.
Örnek, `^example\d\d-\d\d-\d\.host\.ru$`
Erişimi kontrol etmek için, bir [DNS ptr sorgusu](https://en.wikipedia.org/wiki/Reverse_DNS_lookup) eş adresi için gerçekleştirilir ve sonra belirtilen regexp uygulanır. Daha sonra PTR sorgusunun sonuçları için başka bir DNS sorgusu gerçekleştirilir ve alınan tüm adresler eş adresine karşılaştırılır. Regexp’nin $ile bitmesini şiddetle tavsiye ederiz.
Sunucu yeniden başlatılıncaya kadar DNS isteklerinin tüm sonuçları önbelleğe alınır.
**Örnekler**
Herhangi bir ağdan kullanıcı için erişimi açmak için şunları belirtin:
``` xml
<ip>::/0</ip>
```
!!! warning "Uyarıcı"
Düzgün yapılandırılmış bir güvenlik duvarınız yoksa veya sunucu doğrudan internete bağlı değilse, herhangi bir ağdan erişimi açmak güvensizdir.
Erişimi yalnızca localhost’tan açmak için şunları belirtin:
``` xml
<ip>::1</ip>
<ip>127.0.0.1</ip>
```
### kullanıcı\_adı / profil {#user-nameprofile}
Kullanıcı için bir ayarlar profili atayabilirsiniz. Ayarlar profilleri ayrı bir bölümde yapılandırılır `users.xml` Dosya. Daha fazla bilgi için, bkz. [Ayarların profilleri](settings-profiles.md).
### user\_name / kota {#user-namequota}
Kotalar, belirli bir süre boyunca kaynak kullanımını izlemenize veya sınırlamanıza izin verir. Kotalar yapılandırılır `quotas`
bu bölüm `users.xml` yapılandırma dosyası.
Kullanıcı için ayarlanmış bir kotalar atayabilirsiniz. Kotalar yapılandırmasının ayrıntılı bir açıklaması için bkz. [Kotalar](../quotas.md#quotas).
### user\_name / veritabanları {#user-namedatabases}
Bu bölümde, ClickHouse tarafından döndürülen satırları sınırlayabilirsiniz `SELECT` geçerli kullanıcı tarafından yapılan sorgular, böylece temel satır düzeyinde güvenlik uygular.
**Örnek**
Aşağıdaki yapılandırma bu kullanıcıyı zorlar `user1` sadece satırları görebilirsiniz `table1` sonucu olarak `SELECT` sorgular, burada değeri `id` alan 1000’dir.
``` xml
<user1>
<databases>
<database_name>
<table1>
<filter>id = 1000</filter>
</table1>
</database_name>
</databases>
</user1>
```
Bu `filter` bir sonuç veren herhangi bir ifade olabilir [Uİnt8](../../sql-reference/data-types/int-uint.md)- tip değeri. Genellikle karşılaştırmalar ve mantıksal operatörler içerir. Satır fromlardan `database_name.table1` burada filtre sonuçları 0 için bu kullanıcı için döndürülür. Filtreleme ile uyumsuz `PREWHERE` işlemler ve devre dışı bırakır `WHERE→PREWHERE` optimizasyon.
[Orijinal makale](https://clickhouse.tech/docs/en/operations/settings/settings_users/) <!--hide-->
| 36.295302 | 378 | 0.722818 | tur_Latn | 0.997688 |
43fb1af8dc1eb5ead98f14d414513cc2a9168a96 | 55 | md | Markdown | site/content/gallery/oyester.md | pugongyingh/restaurant-template-cms-netlify | f80db5f552a419d25a9e6feaf28413c41ebee629 | [
"MIT"
] | 33 | 2017-10-16T14:54:23.000Z | 2021-02-13T10:08:10.000Z | site/content/gallery/oyester.md | pugongyingh/restaurant-template-cms-netlify | f80db5f552a419d25a9e6feaf28413c41ebee629 | [
"MIT"
] | 4 | 2021-03-01T20:56:20.000Z | 2022-02-26T01:46:53.000Z | site/content/gallery/oyester.md | pugongyingh/restaurant-template-cms-netlify | f80db5f552a419d25a9e6feaf28413c41ebee629 | [
"MIT"
] | 87 | 2017-10-03T12:30:06.000Z | 2022-03-17T16:07:18.000Z | ---
title: oyester
image: /img/gallery/photo4.jpg
---
| 9.166667 | 30 | 0.654545 | dan_Latn | 0.181782 |
43fbce08aa14abf44909b88c42ae7c2b0050341d | 3,962 | md | Markdown | source/community/user-stories/the-solution-company.md | shenitzky/ovirt-site | 59dacde7d4c9bb57a8e6cafbf36de5d3583f21a3 | [
"MIT"
] | null | null | null | source/community/user-stories/the-solution-company.md | shenitzky/ovirt-site | 59dacde7d4c9bb57a8e6cafbf36de5d3583f21a3 | [
"MIT"
] | null | null | null | source/community/user-stories/the-solution-company.md | shenitzky/ovirt-site | 59dacde7d4c9bb57a8e6cafbf36de5d3583f21a3 | [
"MIT"
] | null | null | null | ---
title: the IT & Solution Company case study
category: community
authors: sandrobonazzola, bproffitt, stoobie
---
<div class="row">
<div class="col-md-7 col-md-offset-1 pad-sides">
# the Solution Company
[the IT & Solution Company](http://it-solution.company/) was asked to revamp the IT infrastructure for a hospital at the beginning of 2020… and frankly,
the existing infrastructure situation was awful. Their hardware and software were from back in the 2000’s, and it was very difficult to manage and operate.
This hospital had made the decision to not invest much in IT, so there were no available funds in the foreseeable future. Everything was in bad shape, all the way down to the cables!
With COVID-19 threatening to arrive in Europe, the Ministry of Health in Germany began preparations.
For the area in which the hospital is located, it was decided to set aside specific hospitals to treat COVID-19 patients, including this one.
A week or two before the lockdown in Germany started, we got a call asking us to refresh the entire IT infrastructure to support the nurses and doctors.
The hospital administrators also told us that we only had two and a half weeks, and we needed to start immediately.
With the clock ticking, we started to buy and install large quantities of hardware, including new cabling, wireless networking, and two additional server rooms.
Luckily, most vendors we relied on did a lot to help as quickly as they could. Wherever we could, we made choices that required less time and effort to organize and install.
That’s where [oVirt](https://www.ovirt.org) came on the scene. We do a lot with open source software and had experience with oVirt, which has proven to be reliable and fast,
was immediately available, and had everything we needed to get started right away.
So we installed a hyperconverged oVirt (on Gluster) infrastructure, migrated existing virtual machines, and also started to introduce Windows 10 VM pools for the medical staff to use.
We also built easy-to-use thin clients based on [CentOS Linux](https://www.centos.org) and began deploying them all over the hospital.
(Not a joke: the staff wanted them so badly, whenever we appeared with a cart full of thin clients, they stood in line to be the first to get them. )
To be honest, we didn’t quite make the two-and-a-half week deadline, because of several organizational and logistic issues.
But oVirt was one of the reasons that we completed the job as quickly as we did. From day one it made the entire IT infrastructure a lot faster, easier to use and maintain, and more reliable.
Since then, we (and the hospital staff) are very happy with oVirt. It has even significantly cut the time the support staff invests, and more importantly,
the time the hospital staff spends sitting in front of a computer. So the patients win too, which is really the ultimate goal.
Thanks to mobile thin clients, the doctors can even take their computers with them.
It worked so well, we’ll soon begin to deploy oVirt in several schools in the area, to support IT and Computer Science Education.
For the record, the hyperconverged cluster deployed at the hospital consists of 3 storage domains, 3 hosts, totalling 120 Cores, 2.2 TB RAM, 180 TB storage),
and 40 GBit Interconnect between the clusters.
We also use AWX/Ansible for administration and CentOS Linux for the thin clients, and to carry out other services throughout the hospital.
Thin clients support up to two screens, and the entire infrastructure has proven to work with medical equipment too, some of which is connected via USB, such as medical card readers.
</div>
<div class="col-md-4 pad-sides">
<div class="well well-lg">
<br/>
**Company name:** the IT & Solution Company<br/>
**Activity:** Network / Development<br/>
**Founded:** 2017<br/>
**Size:** 5 employees
</div>
</div>
</div>
| 60.953846 | 191 | 0.779657 | eng_Latn | 0.999765 |
43fbea213dbb1629bce8a91fd96094a7c876ea71 | 1,751 | md | Markdown | CONTRIBUTING.md | romankrru/reagent | c9227571052103662189e520fd8ba5a48e0fa93c | [
"MIT"
] | 3 | 2018-05-27T14:55:23.000Z | 2018-05-27T22:28:22.000Z | CONTRIBUTING.md | romankrru/reagent | c9227571052103662189e520fd8ba5a48e0fa93c | [
"MIT"
] | 9 | 2018-05-27T14:31:53.000Z | 2018-06-02T02:01:28.000Z | CONTRIBUTING.md | romankrru/reagent | c9227571052103662189e520fd8ba5a48e0fa93c | [
"MIT"
] | 1 | 2018-02-21T03:00:32.000Z | 2018-02-21T03:00:32.000Z | # Contributing to Reagent
:+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
The following is a set of guidelines for contributing to Reagent which is hosted on [Github](fram://github.com/reagent-project/reagent).
These are just guidelines, not rules. Use your best judgment and feel free to propose changes to this document in a pull request.
## Support questions
**The Github issues for Reagent are for bug reports and feature requests. Support requests and usage questions should go to the [Clojure Slack channel](http://clojurians.net), [Clojureverse discussion board](https://clojureverse.org/), the [ClojureScript mailing list](https://groups.google.com/forum/#!forum/clojurescript), or the [Reagent mailing list](https://groups.google.com/forum/#!forum/reagent-project).**
## Creating issues for bugs
Check if the issue has already been reported. If possible provide:
* Version of Reagent being used
* Minimal reproduction steps
## Creating issues for features
Use your best judgement on what is needed here.
## Pull requests
**Create pull requests to the master branch**.
Check [development docs](./docs/development.md)
## Pull requests for bugs
If possible provide:
* Code that fixes the bug
* Failing tests which pass with the new changes
* Improvements to documentation to make it less likely that others will run into issues (if relevant).
* Add the change to the Unreleased section of [CHANGELOG.md](CHANGELOG.md)
## Pull requests for features
If possible provide:
* Code that implements the new feature
* Tests to cover the new feature including all of the code paths
* Docstrings for functions
* Documentation examples
* Add the change to the Unreleased section of [CHANGELOG.md](CHANGELOG.md)
| 37.255319 | 414 | 0.772701 | eng_Latn | 0.995267 |
43fbfdbce7ee068ed8eabac38ccdacc82b7cdbac | 1,370 | md | Markdown | page/4about.md | yuzibo/yuzibo.github.io | e4d009547f024a0eec02543bc31c0d21ff373c38 | [
"MIT"
] | 1 | 2016-04-14T03:27:08.000Z | 2016-04-14T03:27:08.000Z | page/4about.md | yuzibo/yuzibo.github.io | e4d009547f024a0eec02543bc31c0d21ff373c38 | [
"MIT"
] | null | null | null | page/4about.md | yuzibo/yuzibo.github.io | e4d009547f024a0eec02543bc31c0d21ff373c38 | [
"MIT"
] | null | null | null | ---
title: ABOUT ME
layout: page
layout: page
title: About
permalink: /about/
type: page
---
* content
{:toc}
----
[中国支教联盟](http://blog.go9999.com/2016/04/20/%E5%85%A8%E5%9B%BD%E8%8C%83%E5%9B%B4%E5%86%85%E6%8B%9B%E5%8B%9F%E4%BB%A3%E5%8F%91%E5%AE%A3%E4%BC%A0%E5%8D%95%E5%BA%97%E9%93%BA.html)
这是一个有关中国支教的网站，不要求你出人出力，只需给他们一点关注，给山区的孩
子更多的关注。
轻财足以聚人，律己足以服人，量宽足以得人，身先足以率人。——曾国藩
## introduction-myself
Hello,
Welcome to my own blog.My name is vimer. I was born on June 17 1994,living in Shandong province, China.
I will graduate from Taishan University in June 2016.My major is Compute Science.I have studied OS, Data Structure, Networking and so on.By now,i focus my energy on Linux programing.I wish to become a linux kernel hacker in future.
Ok, only can i use C to programer now . I will to learn more.
----
My practice's project:
linux-programming: https://github.com/yuzibo/linux-programming.git
如果你觉得本站对你有价值，请打赏一下吆:
支付宝账号：
357130479@qq.com
# 欢迎大家加入linux kernel学习交流群 212973173
## Thanks!
Thanks for [liuhuan](https://github.com/bitsly/bitsly.github.com).I git clone his site.
## Email
If you find any errors or disunderstand, please ccing me:)
[tsu.yubo#gmail.com](mailto:tsu.yubo@gmail.com) 请将#换为@
[yuzibode#126.com](mailto:yuzibode@126.com)
## 总有一天你会成为你想成为的人
----
| 21.40625 | 234 | 0.729197 | eng_Latn | 0.493896 |
43fc54d26a7e2b9ecadb3c239373a1ecb10160b5 | 93 | md | Markdown | index.md | ppmash/github-pages-with-jekyll | 2cbd23064547f9bec609147241ca177cc86d2d17 | [
"MIT"
] | null | null | null | index.md | ppmash/github-pages-with-jekyll | 2cbd23064547f9bec609147241ca177cc86d2d17 | [
"MIT"
] | 4 | 2021-01-18T21:44:02.000Z | 2021-01-18T22:51:50.000Z | index.md | ppmash/github-pages-with-jekyll | 2cbd23064547f9bec609147241ca177cc86d2d17 | [
"MIT"
] | null | null | null | # Welcome to my blog
Welcome to My Blog Page. This is created as part of learning.
Thanks.
| 15.5 | 61 | 0.741935 | eng_Latn | 0.997867 |
43fcb301db81926ad5221498a7142dce9d4874fa | 5,789 | md | Markdown | docs/configuration.md | Thom1729/Sublime-JS-Custom | d28ce3af3d5330a91a65fc525e0118d2cdaa5afb | [
"MIT"
] | 142 | 2018-01-04T06:51:13.000Z | 2022-03-20T16:14:48.000Z | docs/configuration.md | Thom1729/Sublime-JS-Custom | d28ce3af3d5330a91a65fc525e0118d2cdaa5afb | [
"MIT"
] | 92 | 2018-01-03T21:48:20.000Z | 2022-03-13T15:42:14.000Z | docs/configuration.md | Thom1729/Sublime-JS-Custom | d28ce3af3d5330a91a65fc525e0118d2cdaa5afb | [
"MIT"
] | 11 | 2018-05-04T13:00:02.000Z | 2021-05-25T17:15:40.000Z | ## Syntax Options
These options, specified in your `defaults` or in a named custom configuration, determine what features your custom syntaxes will have. Omitted options will be treated as `null`.
### ECMAScript Proposals
These options enable support for various [proposed language features](https://github.com/tc39/proposals). These proposals may change unexpectedly. If they stabilize, they will eventually be incorporated into the core JavaScript syntax and these extensions will be removed.
#### `es_pipeline`: boolean
Support the proposed [pipeline operator](https://github.com/tc39/proposal-pipeline-operator).
#### `es_slice`: boolean
Support the proposed [slice notation](https://github.com/gsathya/proposal-slice-notation).
### Third-party features
These extensions go beyond the base JavaScript syntax to support third-party features.
#### `jsx`: boolean
Highlight [JSX](https://reactjs.org/docs/introducing-jsx.html). (Uses the JSX extension extension from core.)
#### `typescript`: boolean
Highlight [TypeScript](http://typescriptlang.org). (Uses the TypeScript extension extension from core.)
Old-style type assertions (e.g. `<T>foo`) will be highlighted unless the `jsx` option is also enabled.
#### `flow_types`: boolean
Highlight [Flow type annotations](https://flow.org/en/docs/types/).
#### `eslint_directives`: boolean
Highlight [eslint configuration directives](https://eslint.org/docs/user-guide/configuring) in comments.
### Personalization
These extensions allow you to personalize your highlighting in various ways.
#### `string_object_keys`: boolean
Highlight unquoted object keys as strings, matching [babel-sublime](https://github.com/babel/babel-sublime)'s behavior.
#### `custom_templates`: object
Use custom syntax highlighting inside [template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals). Several sub-options are available:
By default, the special `embed_configuration` disables this to avoid syntax recursion errors.
##### `default`: string
Highlight untagged template literals using a specified syntax. Example configuration:
```json
{
"configurations": {
"My Config": {
"custom_templates": {
"default": "scope:text.html.basic"
}
}
}
}
```
This will highlight all untagged template literals as HTML. (The `comments` option below will override this when it applies.)
##### `tags`: object
Highlight tagged template literals based on the tag. Each key in `tag` should be a JavaScript identifier representing a template literal tag. The associated value should be a string specifying a context to include.
For example, to highlight template strings with the `style` tag as CSS, use the following configuration:
```json
{
"configurations": {
"My Config": {
"custom_templates": {
"tags": {
"style": "scope:source.css"
}
}
}
}
}
```
Then, if you use “JS Custom - My Config” to highlight the following code, the contents of this template literal will be highlighted as CSS:
```js
const myStyle = style`div { color: red }`;
```
##### `comments`: object
Highlight untagged template literals based on a preceding block comment. Example configuration:
```json
{
"configurations": {
"My Config": {
"custom_templates": {
"comments": {
"style": "scope:source.css"
}
}
}
}
}
```
Example JavaScript:
```js
const myStyle = /*style*/`div { color: red }`;
const myStyle = /* style */`div { color: red }`;
```
##### `lookaheads`: object
Highlight untagged template literals based on the contents. Example configuration:
```json
{
"configurations": {
"My Config": {
"custom_templates": {
"lookaheads": {
"select\b": "scope:source.sql"
}
}
}
}
}
```
Example JavaScript:
```js
const myQuery = `select 1 from dual`;
```
##### `styled_components`: boolean
Highlight template string literals for [Styled Components](https://www.styled-components.com/).
##### `clear_all_scopes`: boolean
Inside custom template literals, clear all of the enclosing JavaScript scopes. Ordinarily, only the `string` scope will be cleared. Enable this option if you're using a third-party tool that requires it.
### Metadata
These options don't affect the syntax highlighting itself, but rather the way that Sublime uses the syntax.
#### `name`: string
The name of the syntax as it will appear in the syntax selector. (If this is omitted, the syntax will be named “JS Custom - <var>name</var>”, where <var>name</var> is the key in the `configurations` object.)
#### `scope`: string
The top-level scope that will be used for the syntax. (If this is omitted, the scope will be “source.js.<var>name</var>”, where <var>name</var> is based on the key in the `configurations` object.)
#### `file_extensions`: array
An array of file extensions. Files with the given extensions will use this syntax.
#### `hidden`: boolean
If this is `true`, the compiled syntax will not appear in the syntax menu or the command palette. It can still be referenced or included by other syntaxes.
#### `first_line_match`: string
Files whose first line matches the given regular expression will use this syntax.
### Deprecated
These options have been superseded by newer, more flexible options.
#### `custom_template_tags`
Superseded by `custom_templates.tags`.
#### `styled_components`
Superseded by `custom_templates.styled_components`.
#### `typescript.old_style_assertions`
Obsolete. Old-style type assertions will work unless JSX is enabled.
| 29.994819 | 272 | 0.695975 | eng_Latn | 0.979836 |
43fdb19a4a538e0c017bc4cbe11bba086f46f44e | 315 | md | Markdown | README.md | jason-morsley/docker-image-ubuntu-docker | e4e88d474e622b95d9ba0435664134b474457561 | [
"MIT"
] | null | null | null | README.md | jason-morsley/docker-image-ubuntu-docker | e4e88d474e622b95d9ba0435664134b474457561 | [
"MIT"
] | null | null | null | README.md | jason-morsley/docker-image-ubuntu-docker | e4e88d474e622b95d9ba0435664134b474457561 | [
"MIT"
] | null | null | null | # A Docker image based on Ubuntu with Docker installed
```
docker build --tag jasonmorsley/ubuntu-with-docker .
```
```
docker run -it ubuntu-with-docker ./bin/sh
```
or
```
winpty docker run -it ubuntu-with-docker ./bin/sh
```
## Push image to Docker Hub
```
docker push jasonmorsley/ubuntu-with-docker
```
| 14.318182 | 54 | 0.685714 | eng_Latn | 0.514017 |
43fdf1789fd40cad13a992ed449f2fad06be177f | 3,800 | md | Markdown | content/bonjour/11.md | ys/wanders | 6030282a5ed0e80cd1021b716fa5cfaffe5d2225 | [
"MIT"
] | null | null | null | content/bonjour/11.md | ys/wanders | 6030282a5ed0e80cd1021b716fa5cfaffe5d2225 | [
"MIT"
] | 62 | 2018-09-22T06:53:25.000Z | 2020-10-08T07:40:17.000Z | content/bonjour/11.md | ys/wanders | 6030282a5ed0e80cd1021b716fa5cfaffe5d2225 | [
"MIT"
] | 2 | 2018-04-09T10:52:03.000Z | 2019-05-26T12:05:59.000Z |
---
categories:
- lettre
date: 2021-02-13T06:30:39.020000Z
newsletter: true
tags:
- la lettre
emoji: 💌
color: pink
title: "Bonjour - 11 - Des livres, du CSV et Mowgli"
slug: "11"
---
👋
Bonjour,
C'est l'histoire d'un gars qui se rend compte que Amazon détient Goodreads depuis 2013. Il le savait déjà en fait mais l'avait astucieusement oublié. Dans l'optique d'avoir la main mise sur ces données, il se dit qu'il doit faire quelque chose.
Je ne sais pas vous mais moi dernièrement, j'aime bien posséder mes données. J'ai fermé mon compte Facebook entre autre en ce début d'année. Et j'en suis plutôt content.
Alors pour les livres que faire? Le petiot ici, il est un peu informaticien. Genre il peut réparer votre imprimante et tout ça. Enfin dans la théorie. Son père avait très vite compris que il ne le ferait plus. Et donc il s'est dit. Je vais exporter toutes mes données de GoodReads et en faire des pages sur mon site. Un truc simple, géré par mes petites mimines et voilà.
Me voilà à exporter un CSV (Comme un fichier excel minimum pour ceux qui ne savent pas). Et à le transformer à coup de scripts et autres petites manipulations pour en sortir... 300 nouveaux fichiers pour mon blog. Une fiche par livre.
Et pouf, ça donne en première version: [yannickschutz.com/books](https://yannickschutz.com/books). Je vous laisse mettre un GIF de hacker ici
Mon but sera de rajouter des pages individuelles avec des liens vers des revendeurs comme [recyclivre](https://recyclivre.com) et [Librairies indépendantes](https://librairiesindependantes.com). Histoire de leur faire un rien de pub.
Par contre, entre temps, je découvre aussi ce [super article](https://macwright.com/2020/12/24/the-new-reading-stack.html) de MacWright. Un blog que j'aime particulièrement lire et qui est plutôt visuellement plaisant. Cet article parle de ces sujets de nouvelles librairies, des concurrents d'Amazon et de GoodReads.
*Oui ma page est inspirée de sa page reading, et alors? Après tout, [tout est un remix](https://www.everythingisaremix.info). Oui comme ces animations de Disney [entre le livre de la Jungle et Winnie l'ourson](https://twitter.com/talkclub100/status/1359249923393413128)*
Ce qui me rappelle aussi que j'avais décidé en début d'année de ne pas acheter de livres neufs cette année. Cela me fait penser que je dois aller me faire une carte à la bibliothèque du village aussi. Et que j'avais un compte [readng.co](https://beta.readng.co/user/yannick) sorte de Goodreads plus plaisant au regard et n'appartenant pas à Amazon.
Bon pour les livres neufs, j'y arrive. Sauf pour ce qui est livres photos. J'ai craqué pour des beaux livres de surf et d'autres avec une couverture en tissu. Non, c'est toi qui est faible une fois que la couverture est en tissu.
J'ai craqué pour [Nippon 2010-2020](https://www.shashasha.co/en/book/nippon-2010-2020) de Shuhei Motoyama que j'ai croisé sur le feed de Craig Mod. Et aussi pour le bouquin de Jason Lee, [In the gold dust rush](https://www.stanleybarker.co.uk/products/jason-lee). Et si le livre est en tissu et à de belles photos de surf, c'est combo comme pour [Hooro](https://www.thegoldenrays.com/collections/photography-books/products/hooroo-by-john-p-brodie?variant=32896734789707) de John Patrick Brodie. J'ai eu l'avant dernier sur les 100. Enfin voilà, c'est simple de ne pas acheter de neuf, avec une astérisque sur les bouquins photos.
*Pour info, pour facilement trouver les bouquins en seconde main, j'utilise pas mal Vinted et Leboncoin. En plus de recyclivre*
Faut toujours que le papier passe par là dans mes petites lettres, je sais.
Voilà le petit récit de la semaine,
J'espère qu'il t'a plu!
Bon samedi,
Yannick
💌
| 71.698113 | 629 | 0.773684 | fra_Latn | 0.975512 |
43fe303bbb014691e7df0a834273455be85d2ae5 | 1,797 | md | Markdown | _papers/goel:pcs:2017.md | charevil/RelatedWork | 35d2539e58331edfff2948c4480c35012f201dd5 | [
"MIT"
] | null | null | null | _papers/goel:pcs:2017.md | charevil/RelatedWork | 35d2539e58331edfff2948c4480c35012f201dd5 | [
"MIT"
] | null | null | null | _papers/goel:pcs:2017.md | charevil/RelatedWork | 35d2539e58331edfff2948c4480c35012f201dd5 | [
"MIT"
] | null | null | null | ---
ENTRYTYPE: inbook
abstract: Construction of a formal model of a computing system is a necessary practice in formal verification. The results of formal analysis can only be
valued to the same degree as the model itself. Model development is error-prone, not only due to the complexity of the system being modeled, but also
because it involves addressing disparate requirements. For example, a formal model should be defined using simple constructs to enable efficient reasoning
but it should also be optimized to offer fast concrete simulations. Models of large computing systems are themselves large software systems and must be
subject to rigorous validation. We describe our formal, executable model of the x86 instruction-set architecture; we use our model to reason about x86
machine-code programs. Validation of our x86 ISA model is done by co-simulating it regularly against a physical x86 machine. We present design decisions
made during model development to optimize both validation and verification, i.e., efficiency of both simulation and reasoning. Our engineering process
provides insight into the development of a software verification and model animation framework from the points of view of accuracy, efficiency, scalability,
maintainability, and usability.
added: 2019-07-01
address: Cham
authors:
- Shilpi Goel
- Warren A. Hunt Jr.
- Matt Kaufmann
booktitle: Provably Correct Systems
doi: 10.1007/978-3-319-48628-4_8
isbn: 978-3-319-48628-4
layout: paper
pages: 173-209
publisher: Springer International Publishing
read: false
readings: []
title: Engineering a formal, executable x86 ISA simulator for software verification
year: 2017
topics:
notes:
- x86 architecture
- instruction set architecture
- ACL2 theorem prover
papers:
---
{% include links.html %}
| 48.567568 | 158 | 0.803005 | eng_Latn | 0.996728 |
43ffc9b8a451ddbe92f8962792ebdd3271f568cc | 352 | md | Markdown | README.md | DevComPsy/NaDa-Gamflidence | 849083371ac3a7857c19f3944a6bd9112cbb04bf | [
"CC-BY-4.0"
] | null | null | null | README.md | DevComPsy/NaDa-Gamflidence | 849083371ac3a7857c19f3944a6bd9112cbb04bf | [
"CC-BY-4.0"
] | null | null | null | README.md | DevComPsy/NaDa-Gamflidence | 849083371ac3a7857c19f3944a6bd9112cbb04bf | [
"CC-BY-4.0"
] | null | null | null | Anonymised data, scripts for running the analyses, and the task code that are presented in the paper.
This data and code are distributed under the terms of the CC-BY 4.0 license, which permits unrestricted use, distribution, and reproduction in any medium, provided it is not used for any commercial purpose and the original work is properly cited.
| 88 | 247 | 0.801136 | eng_Latn | 1 |
a100a50a8d0d3f31e49b6280798ee0ae20b57c97 | 3,568 | md | Markdown | intl.en-US/API Reference/Images/DescribeImageSharePermission.md | houdapeng/ecs | 8f82ff05c1975790f59f1ca4250ee39fd388a535 | [
"MIT"
] | 1 | 2019-01-20T13:52:23.000Z | 2019-01-20T13:52:23.000Z | intl.en-US/API Reference/Images/DescribeImageSharePermission.md | houdapeng/ecs | 8f82ff05c1975790f59f1ca4250ee39fd388a535 | [
"MIT"
] | null | null | null | intl.en-US/API Reference/Images/DescribeImageSharePermission.md | houdapeng/ecs | 8f82ff05c1975790f59f1ca4250ee39fd388a535 | [
"MIT"
] | null | null | null | # DescribeImageSharePermission {#DescribeImageSharePermission .reference}
Queries all the authorized users to whom one of your custom image is shared. The responded information can be displayed on several pages. By default, 10 entries of record are displayed on each page.
## Request parameters {#RequestParameter .section}
|Name|Type|Required|Description|
|:---|:---|:-------|:----------|
|Action|String|Yes|The name of this interface. Value: DescribeImageSharePermission.|
|RegionId|String|Yes|ID of the region to where the custom image belongs. You can call [DescribeRegions](intl.en-US/API Reference/Regions/DescribeRegions.md#) to obtain the latest region list.|
|ImageId|String|Yes|ID of your custom image.|
|PageNumber|Integer|No|The page number of the responded information. Initial value: 1.Default value: 1.
|
|PageSize|Integer|No|The number of entries on each page for the responded information. Maximum value: 50.Default value: 10.
|
## Response parameters {#ResponseParameter .section}
|Name|Type|Description|
|:---|:---|:----------|
|ImageId|String|ID of the custom image.|
|RegionId|String|Region ID of the custom image.|
|ShareGroups|[ShareGroupType](intl.en-US/API Reference/Data type/ShareGroupType.md#)|Type of the shared group.|
|Accounts|[AccountType](intl.en-US/API Reference/Data type/AccountType.md#)|Type of the Alibaba Cloud user account.|
|TotalCount|Integer|Total number of entries.|
|PageNumber|Integer|Page number.|
|PageSize|Integer|Maximum number of entries on each page.|
## Examples { .section}
**Request example**
```
https://ecs.aliyuncs.com/?Action=DescribeImageSharePermission
&RegionId=cn-qingdao
&ImageId=m-282dzntc7
&<Common Request Parameters>
```
**Response example**
**XML format**
```
<DescribeImageSharePermissionResponse>
<ImageId>m-282dzntc7</ImageId>
<PageNumber>1</PageNumber>
<PageSize>10</PageSize>
<RegionId>cn-qingdao</RegionId>
<TotalCount>1</TotalCount>
<RequestId>441CF898-42FF-47CF-9348-3C3BFF557278</RequestId>
<ShareGroups>
<ShareGroup>
<Group>all</Group>
</ShareGroup>
</ShareGroups>
<Accounts>
<Account>
<AliyunId>1886508529898586</AliyunId>
</Account>
</Accounts>
</DescribeImageSharePermissionResponse>
```
**JSON format**
```
{
"ShareGroups": {
"ShareGroup": [
{
"Group": "all"
}
]
},
"Accounts": {
"Account": [
{
"AliyunId": "1886508529898586"
}
]
},
"ImageId": "m-282dzntc7",
"PageNumber": 1,
"PageSize": 10,
"RegionId": "cn-qingdao",
"TotalCount": 1,
"RequestId": "9AD96F49-0BE5-4868-A66A-224352549CEC"
}
```
## Error codes {#ErrorCode .section}
Error codes specific to this interface are as follows. For more information, see [API Error Center](https://error-center.alibabacloud.com/status/product/Ecs).
|Error code|Error message |HTTP status code |Meaning|
|:---------|:-------------|:----------------|:------|
|MissingParameter|The input parameter “RegionId “ that is mandatory for processing this request is not supplied.|400|You must specify the `RegionId`. |
|MissingParameter|The input parameter “ImageId “ that is mandatory for processing this request is not supplied.|400|You must specify the `ImageId`.|
|InvalidRegionId.NotFound|The specified region does not exist.|404|The specified `RegionId` does not exist.|
|InvalidImageId.NotFound|The specified ImageId does not exist.|404|The specified ImageId does not exist.|
| 33.980952 | 198 | 0.690022 | eng_Latn | 0.571969 |
a100ce6d49d33a94d391d3e1d6e55bd154e34c12 | 660 | md | Markdown | README.md | rpgarde/paolo-garde-portfolio | bfca08d3263e0a45879148672447385d9c555156 | [
"MIT"
] | 1 | 2021-06-12T07:06:11.000Z | 2021-06-12T07:06:11.000Z | README.md | rpgarde/paolo-garde-portfolio | bfca08d3263e0a45879148672447385d9c555156 | [
"MIT"
] | null | null | null | README.md | rpgarde/paolo-garde-portfolio | bfca08d3263e0a45879148672447385d9c555156 | [
"MIT"
] | null | null | null | # Welcome to my portfolio 👋
This is the second version of my portfolio, using Bootstrap. This is a mobile-first design leveraging Bootstrap's responsive utilities.
On the navbar you can access the different sections. on the get in touch section, it has a dropdown where you can view links to my different online profiles, as well as a link to donwload my CV.
You can access via [this link](https://rpgarde.github.io/paolo-garde-portfolio/)
## Screenshot of the portfolio
## Dropdown functionality
 | 55 | 194 | 0.786364 | eng_Latn | 0.990331 |
a1023836ee12b803beec2dd800e58d53b73aed8f | 14,232 | md | Markdown | content/ja/guides/logs.md | spesnova/documentation | fad1c451fb60a85085dadf4a376a02ee1d1bcf35 | [
"BSD-3-Clause"
] | null | null | null | content/ja/guides/logs.md | spesnova/documentation | fad1c451fb60a85085dadf4a376a02ee1d1bcf35 | [
"BSD-3-Clause"
] | null | null | null | content/ja/guides/logs.md | spesnova/documentation | fad1c451fb60a85085dadf4a376a02ee1d1bcf35 | [
"BSD-3-Clause"
] | null | null | null | ---
last_modified: 2015/04/02
translation_status: complete
language: ja
title: Datadog Agent によるログの解析方法
kind: guide
listorder: 4
sidebar:
nav:
- header: ログ解析のガイド
- text: メトリクスの抽出
href: "#metrics"
- text: イベントの抽出
href: "#events"
---
<!-- Log files contain tons of valuable application and business data.<!>
Unfortunately, this value is oftentimes never realized because log files go
ignored. The Datadog Agent can help remedy this by parsing metrics and events from
logs, so the data within can ｂe graphed in real-time, all the time. -->
ログファイルには、アプリケーションとビジネスの貴重なデータが含まれています。
残念ながら多くの場合この重要性には気が付かずログファイルは放置されています。
Datadog Agent は、ログからメトリクスとイベントを解析することによって、その中のデータをリアルタイムでグラフ化するのに役立ちます。
<h2 id="metrics">メトリクスの抽出</h2>
Datadgo Agentは、ログファイルから直接メトリクスを、抽出することができます:
- Datadog の公式ログフォーマットの場合は、追加のプログラミングは不要です。
- Datadog の公式ログフォーマット以外の場合は、Pythonによるログパース関数を準備し、それをimportして抽出します。
<!-- ### Datadog Canonical Log Format
Datadog logs are formatted as follows:
metric unix_timestamp value \[attribute1=v1 attributes2=v2 ...\]
For example, imagining the content of `/var/log/web.log` to be:
me.web.requests 1320786966 157 metric_type=counter unit=request
me.web.latency 1320786966 250 metric_type=gauge unit=ms
Then all you need for Datadog to read metrics is to add this line to your Agent
configuration file (usually at `/etc/dd-agent/datadog.conf`):
dogstreams: /var/log/web.log
You can also specify multiple log files like this:
dogstreams: /var/log/web.log, /var/log/db.log, /var/log/cache.log -->
### Datadog の公式ログフォーマットの場合
Datadogのログは次のようにフォーマットされています:
metric unix_timestamp value [attribute1=v1 attributes2=v2 ...]
例えば、`/var/log/web.log`の各レコードが次のような内容で記述されているとします:
me.web.requests 1320786966 157 metric_type=counter unit=request
me.web.latency 1320786966 250 metric_type=gauge unit=ms
Datadog Agent にこのログファイルを解析させるためには、次の行をDatadog Agent の設定ファイル(`/etc/dd-agent/datadog.conf`)に追記します。
dogstreams: /var/log/web.log
複数のログファイルを解析するのには、ログファイルのパスをカンマで区切って記述します:
dogstreams: /var/log/web.log, /var/log/db.log, /var/log/cache.log
<!-- ### Parsing Custom Log Formats
If you want to parse a different log format - say for a piece of vendor
or legacy software - you can use a custom Python function to extract the proper
fields from the log by specifying your log file in your Agent configuration
file in the following format:
dogstreams: /var/log/web.log:parsers:parse_web
The `parsers:parse_web` portion indicates that the custom Python function lives
in a package called parsers in the Agent's `PYTHONPATH`, and the parsers package
has a function named `parse_web`. The Agent's `PYTHONPATH` is set in the Agent
startup script, `/etc/init.d/datadog-agent` for Agent versions < 2.0, and in the
supervisor config for Agent version >= 2.0.
If your parser does **not** live on the Agent's `PYTHONPATH`, you can use an
alternative syntax to configure your line parser:
dogstreams: /path/to/log1:/path/to/my/parsers_module.py:custom_parser
In this format, the agent will attempt to import a function called
`custom_parser` from `/path/to/my/parsers_module.py`.
If your custom log parser is not working, the first place to check is the
Agent collector logs. If the Agent is unable to import your function, there will
be a line with `Could not load Dogstream line parser`. (On the other hand, if
all goes well you should see `dogstream: parsing {filename} with
{function name} (requested {config option text})`.)
### Writing Parsing Functions
Custom parsing functions must:
- take two parameters: a Python logger object (for debugging) and a string parameter of the current line to parse.
- return a tuple or list of tuples of the form:
`(metric (str), timestamp (unix timestamp), value (float), attributes (dict))`
Where attributes should at least contain the key metric_type, specifying whether the given metric is a counter or gauge. -->
### カスタムフォーマットのログの場合
ベンダ専用のソフトや過去からの残留ソフトなど、Datadgoが公式に使用しているフォーマットと異なるログを解析したいとします。このような場合は、Pythonで記述した関数によってその特殊ログの特定のフィールドを抽出することができます。Python で記述した関数を Datadog Agentから呼び出せるようにするためには、設定ファイルに次のフォーマットで、ログファイルと解析用の関数を記述します:
dogstreams: /var/log/web.log:parsers:parse_web
`parsers:parse_web`の部分の意味は、Datadog Agent の`PYTHONPATH`に`parsers`パッケージが存在し、その中に`parse_web`関数が記述されていることを意味します。
`PYTHONPATH`は、Datadog Agentの起動スクリプトによって設定されます。Datadog Agent 2.0 以前の場合は,
`/etc/init.d/datadog-agent`に設定されており、Datadog Agent 2.0 以降の場合は、Datadog Agentのsupervisor の設定ファイルに記述された内容に基づいて設定されています。
もしも、パースのパッケージが`PYTHONPATH`にない場合は、そのパッケージを読み込むために次のようにパスを付記します:
dogstreams: /path/to/log1:/path/to/my/parsers_module.py:custom_parser
このフォーマットでは、Datadog Agentは、`custom_parser` 関数を、`/path/to/my/parsers_module.py` ファイルからimportしようとします。
もしも、カスタムログパーサが機能しない場合は、Datadog Agentのcollectorが出力しているログを確認してください。
Datadog Agentがその関数をimport できていない場合は、`Could not load Dogstream line parser`という行が出力されます。全てが正常に動作している場合は、`dogstream: parsing {filename} with
{function name} (requested {config option text})`が、出力されます。
<!-- ### Writing Parsing Functions
Custom parsing functions must:
- take two parameters: a Python logger object (for debugging) and a string parameter of the current line to parse.
- return a tuple or list of tuples of the form:
`(metric (str), timestamp (unix timestamp), value (float), attributes (dict))`
Where attributes should at least contain the key metric_type, specifying whether the given metric is a counter or gauge. -->
### パースのための関数の書き方
カスタムログパース関数は、次の条件を満たしている必要があります:
- パラメータを2つ受付ます: Python logger オブジェクト (デバッグ目的)と、パースするための現在行の文字列パラメータです。
- 返される結果の出力は、タプル又は、リストの形式である必要があります:
`(metric (str), timestamp (unix timestamp), value (float), attributes (dict))`
`attributes`には、最低限でもkey文字として`metric_type` を指定する必要があります。`metric_type`の値には、`counter`又は、`gauge`を指定することになります。
<!-- ### Example
Here's an example of what `parsers.py` might contain:
<%= python <<eof
import time
from datetime import datetime
def parse_web(logger, line):
# Split the line into fields
date, metric_name, metric_value, attrs = line.split('|')
# Convert the iso8601 date into a unix timestamp, assuming the timestamp
# string is in the same timezone as the machine that's parsing it.
date = datetime.strptime(date, "%Y-%m-%dT%H:%M:%S")
date = time.mktime(date.timetuple())
# Remove surrounding whitespace from the metric name
metric_name = metric_name.strip()
# Convert the metric value into a float
metric_value = float(metric_value.strip())
# Convert the attribute string field into a dictionary
attr_dict = {}
for attr_pair in attrs.split(','):
attr_name, attr_val = attr_pair.split('=')
attr_name = attr_name.strip()
attr_val = attr_val.strip()
attr_dict[attr_name] = attr_val
# Return the output as a tuple
return (metric_name, date, metric_value, attr_dict)
eof
%>
You'll want to be able to test your parser outside of the Agent, so for the above example,
you might add a test function like this:
<%= python <<eof
def test():
# Set up the test logger
import logging
logging.basicConfig(level=logging.DEBUG)
# Set up the test input and expected output
test_input = "2011-11-08T21:16:06|me.web.requests|157|metric_type=counter,unit=request"
expected = (
"me.web.requests",
1320786966,
157,
{"metric_type": "counter",
"unit": "request" }
)
# Call the parse function
actual = parse_web(logging, test_input)
# Validate the results
assert expected == actual, "%s != %s" % (expected, actual)
print 'test passes'
if __name__ == '__main__':
# For local testing, callable as "python /path/to/parsers.py"
test()
eof
%>
And you can test your parsing logic by calling python /path/to/parsers.py. -->
### カスタムログパーサの例
`parsers.py`には、次のような内容が記述されます:
<%= python <<eof
import time
from datetime import datetime
def parse_web(logger, line):
# Split the line into fields
date, metric_name, metric_value, attrs = line.split('|')
# Convert the iso8601 date into a unix timestamp, assuming the timestamp
# string is in the same timezone as the machine that's parsing it.
date = datetime.strptime(date, "%Y-%m-%dT%H:%M:%S")
date = time.mktime(date.timetuple())
# Remove surrounding whitespace from the metric name
metric_name = metric_name.strip()
# Convert the metric value into a float
metric_value = float(metric_value.strip())
# Convert the attribute string field into a dictionary
attr_dict = {}
for attr_pair in attrs.split(','):
attr_name, attr_val = attr_pair.split('=')
attr_name = attr_name.strip()
attr_val = attr_val.strip()
attr_dict[attr_name] = attr_val
# Return the output as a tuple
return (metric_name, date, metric_value, attr_dict)
eof
%>
Datadog Agent 以外からもパーサをテストすることをお勧めしますので、先のスクリプトにテスト関数を追記します:
<%= python <<eof
def test():
# Set up the test logger
import logging
logging.basicConfig(level=logging.DEBUG)
# Set up the test input and expected output
test_input = "2011-11-08T21:16:06|me.web.requests|157|metric_type=counter,unit=request"
expected = (
"me.web.requests",
1320786966,
157,
{"metric_type": "counter",
"unit": "request" }
)
# Call the parse function
actual = parse_web(logging, test_input)
# Validate the results
assert expected == actual, "%s != %s" % (expected, actual)
print 'test passes'
if __name__ == '__main__':
# For local testing, callable as "python /path/to/parsers.py"
test()
eof
%>
次のようにパーサを実行し、関数のテストをします。
python /path/to/parsers.py
<!-- <h2 id="events">Parsing Events</h2>
Event parsing is done via the same custom parsing functions as described above, except if you return a
`dict` (or a `list` of `dict`) from your custom parsing function, Datadog will treat it as an event instead of a metric.
Here are the event fields (bold means the field is required):
<table class="table">
<thead>
<tr>
<th>Field</th>
<th>Type</th>
<th>Value</th>
</tr>
</thead>
<tbody>
<tr>
<th>msg_title</th>
<td>string</td>
<td>Title of the event. Will get indexed by our full-text
search.</td>
</tr>
<tr>
<td>timestamp</td>
<td>integer</td>
<td>Unix epoch timestamp. If omitted, will default to the time that
the Agent parsed the event.</td>
</tr>
<tr>
<td>msg_text</td>
<td>string</td>
<td>Body of the event. Will get indexed by our full-text
search.</td>
</tr>
<tr>
<td>alert_type</td>
<td>string enum</td>
<td>Indicates the severity of the event. Must be one of `error`,
`warning`, `success` or `info`. If omitted, will default to `info`.
Searchable by `alert_type:value`</td>
</tr>
<tr>
<td>event_type</td>
<td>string</td>
<td>Describes what kind of event this is. Used as part of the
aggregation key</td>
</tr>
<tr>
<td>aggregation_key</td>
<td>string</td>
<td>Describes what this event affected, if anything. Used as part
of the aggregation key</td>
</tr>
<tr>
<td>host</td>
<td>string</td>
<td>Name of the host this event originated from. The event will
automatically get tagged with any tags you've given this host using
the <a href="https://app.datadoghq.com/infrastructure#tags">tagging
page</a> or the <a href="/api/#tags">tagging
api</a>. The host value is used as part of the aggregation
key.</td>
</tr>
<tr>
<td>priority</td>
<td>string</td>
<td>Determines whether the event will be visible or hidden by default
in the stream; Must be one of <code>low</code> or <code>normal</code></td>
</tr>
</tbody>
</table>
The events with the same aggregation key within a 24 hour time window will get aggregated together on the stream.
The aggregation key is a combination of the following fields:
- event_type
- aggregation_key
- host
For an example of an event parser, see our [cassandra compaction event parser](https://github.com/DataDog/dd-agent/blob/master/dogstream/cassandra.py)
that is bundled with the Agent. -->
<h2 id="events">イベントの抽出</h2>
Event parsing is done via the same custom parsing functions as described above, except if you return a
`dict` (or a `list` of `dict`) from your custom parsing function, Datadog will treat it as an event instead of a metric.
イベントフィールド項目 (**太文字のフィールド**は、必須項目です):
<table class="table">
<thead>
<tr>
<th>Field</th>
<th>Type</th>
<th>Value</th>
</tr>
</thead>
<tbody>
<tr>
<th>msg_title</th>
<td>string</td>
<td>Title of the event. Will get indexed by our full-text
search.</td>
</tr>
<tr>
<td>timestamp</td>
<td>integer</td>
<td>Unix epoch timestamp. If omitted, will default to the time that
the Agent parsed the event.</td>
</tr>
<tr>
<td>msg_text</td>
<td>string</td>
<td>Body of the event. Will get indexed by our full-text
search.</td>
</tr>
<tr>
<td>alert_type</td>
<td>string enum</td>
<td>Indicates the severity of the event. Must be one of `error`,
`warning`, `success` or `info`. If omitted, will default to `info`.
Searchable by `alert_type:value`</td>
</tr>
<tr>
<td>event_type</td>
<td>string</td>
<td>Describes what kind of event this is. Used as part of the
aggregation key</td>
</tr>
<tr>
<td>aggregation_key</td>
<td>string</td>
<td>Describes what this event affected, if anything. Used as part
of the aggregation key</td>
</tr>
<tr>
<td>host</td>
<td>string</td>
<td>Name of the host this event originated from. The event will
automatically get tagged with any tags you've given this host using
the <a href="https://app.datadoghq.com/infrastructure#tags">tagging
page</a> or the <a href="/ja/api/#tags">tagging
api</a>. The host value is used as part of the aggregation
key.</td>
</tr>
<tr>
<td>priority</td>
<td>string</td>
<td>Determines whether the event will be visible or hidden by default
in the stream; Must be one of <code>low</code> or <code>normal</code></td>
</tr>
</tbody>
</table>
The events with the same aggregation key within a 24 hour time window will get aggregated together on the stream.
The aggregation key is a combination of the following fields:
- event_type
- aggregation_key
- host
For an example of an event parser, see our [cassandra compaction event parser](https://github.com/DataDog/dd-agent/blob/master/dogstream/cassandra.py)
that is bundled with the Agent.
| 30.475375 | 200 | 0.729272 | eng_Latn | 0.873063 |
a102da0fd6186c8a21f51bebdebc4c5852b9a9b5 | 645 | md | Markdown | docs/_coverpage.md | yexinkun/netty-handbook | fb506a273fbc9a3202ee735c0ba720704536dfaa | [
"Apache-2.0"
] | 79 | 2020-09-25T10:52:46.000Z | 2022-03-30T02:13:17.000Z | docs/_coverpage.md | yexinkun/netty-handbook | fb506a273fbc9a3202ee735c0ba720704536dfaa | [
"Apache-2.0"
] | 5 | 2020-09-17T02:42:59.000Z | 2021-07-01T05:47:51.000Z | docs/_coverpage.md | yexinkun/netty-handbook | fb506a273fbc9a3202ee735c0ba720704536dfaa | [
"Apache-2.0"
] | 101 | 2020-10-26T07:24:20.000Z | 2022-03-23T03:43:15.000Z | 
> 《尚硅谷 Netty 核心技术及源码剖析》课程学习手册
* 本课程不适合零基础的学员，需要掌握常用的设计模式和数据结构
* 掌握 Java 的面向对象编程、多线程编程、IO 编程、网络编程等知识
* 《Netty 核心源码剖析章节》内容学习最好有项目开发和阅读源码的经历
[](https://github.com/dongzl/netty-handbook)
[](https://github.com/dongzl/netty-handbook)
[](https://www.apache.org/licenses/LICENSE-2.0.html)
[GitHub](https://github.com/dongzl/netty-handbook/)
[Get Started](README.md) | 46.071429 | 133 | 0.768992 | yue_Hant | 0.766292 |
a103529a64c25f7eb6884aa75a23d5a41496cdc5 | 71 | md | Markdown | tag/water.md | abdulbaqi/abdulbaqi.github.io | 1095a3562d4cd0e79cbb6ec06377b9293d94fc03 | [
"MIT"
] | 2 | 2021-10-02T23:32:37.000Z | 2022-01-03T21:57:43.000Z | tag/water.md | abdulbaqi/abdulbaqi.github.io | 1095a3562d4cd0e79cbb6ec06377b9293d94fc03 | [
"MIT"
] | null | null | null | tag/water.md | abdulbaqi/abdulbaqi.github.io | 1095a3562d4cd0e79cbb6ec06377b9293d94fc03 | [
"MIT"
] | 1 | 2020-01-02T19:15:55.000Z | 2020-01-02T19:15:55.000Z | ---
layout: tagpage
title: "Tag: water"
tag: water
robots: noindex
---
| 10.142857 | 19 | 0.661972 | eng_Latn | 0.461742 |
a1039e45c5acbbd61de06b567319d63c18dc0381 | 455 | md | Markdown | _publications/edmunds-et-al-2020.md | ajwills72/ajwills72.github.io | 3ab1bc3e1ae29143bbb098aabbe8df6811925e48 | [
"MIT"
] | null | null | null | _publications/edmunds-et-al-2020.md | ajwills72/ajwills72.github.io | 3ab1bc3e1ae29143bbb098aabbe8df6811925e48 | [
"MIT"
] | null | null | null | _publications/edmunds-et-al-2020.md | ajwills72/ajwills72.github.io | 3ab1bc3e1ae29143bbb098aabbe8df6811925e48 | [
"MIT"
] | null | null | null | ---
date: 2020-08-07
pdf: https://www.ojepn.com/images/2020/2020-8639.pdf
osr: https://www.ojepn.com/images/2020/2020-8639.pdf
tag: misc
alcs: ineligible
IR: /no-IR
accepted: NA
DOI: https://doi.org/10.46221/ojepn.2020.8639
---
Edmunds, C.E.R., Inkster, A.B., Jones, P.M., Milton, F., & Wills, A.J. (2020). Absence of cross-modality analogical transfer in perceptual categorization. _Open Journal of Experimental Psychology and Neuroscience, 1_, 3-13.
| 30.333333 | 223 | 0.723077 | yue_Hant | 0.606829 |
a104025a53aa8873bf1a7c97f03df63e695afeec | 5,438 | md | Markdown | content/backup/frontend/web-server/nginx.md | poqw/poqw.github.io | 5e90764a8de99f66c571a0d95255c8e9b22d3d82 | [
"MIT"
] | 13 | 2017-11-04T08:29:54.000Z | 2020-11-02T04:15:33.000Z | content/backup/frontend/web-server/nginx.md | poqw/poqw.github.io | 5e90764a8de99f66c571a0d95255c8e9b22d3d82 | [
"MIT"
] | 10 | 2020-10-22T02:17:00.000Z | 2020-10-29T11:24:06.000Z | content/backup/frontend/web-server/nginx.md | poqw/poqw.github.io | 5e90764a8de99f66c571a0d95255c8e9b22d3d82 | [
"MIT"
] | 2 | 2021-03-30T05:37:22.000Z | 2021-12-22T15:09:47.000Z | # NGINX
Nginx 는 HTML이나 미디어 파일 같은 정적 컨텐츠처리 전문가다.
## 동작 원리
Nginx 는 마치 프록시처럼 사용자의 요청을 서버 대신 받아서 중계해주는 일종의 경량화된 웹 서버다.
설정에 따라 요청에 대한 설정을 마음대로 컨트롤할 수 있다는 것이 Nginx 의 큰 장점이다.
Apache 는 요청에 따라 스레드를 생성해서 접속자 수가 많아지면 CPU와 메모리를 많이 잡아먹지만 Nginx는 Event-driven 방식이기 때문에
고정된 프로세스만 사용하므로 접속이 증가해도 메모리나 CPU 사용량이 크게 증가하지 않는다.
## Master & Worker Process
Nginx는 Master Process 와 Worker Process 가 존재한다.
Master Process 는 단 하나로, /etc/nginx/nginx.conf 에 위치한 설정 파일의 유효성을 검증하고 Worker Process 들을 관리한다.
Worker Process 는 설정 파일에서 설정이 가능하고, OS의 상황에 맞게 자동 조정된다. 모든 요청은 이 Worker Process가 처리한다.
## Dive into an example
아래는 내가 작성했던 nginx config 파일이다.
```
user nginx;
worker_processes 1;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
# Some optimization tips.
# https://thoughts.t37.net/nginx-optimization-understanding-sendfile-tcp-nodelay-and-tcp-nopush-c55cdd276765
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
gzip on;
server {
listen 80;
root /usr/app;
location /hls/playlist.m3u8 {
add_header Cache-Control 'no-store, no-cache, must-revalidate, max-age=0';
add_header Content-type 'application/vnd.apple.mpegurl';
add_header Access-Control-Allow-Origin '*';
}
location ~ /hls/(chunk[0-9]+\.ts)$ {
alias /usr/app/hls/chunks/$1;
add_header Cache-Control 'no-store, no-cache, must-revalidate, max-age=0';
add_header Content-type 'video/MP2T';
add_header Access-Control-Allow-Origin '*';
}
location / {
proxy_pass http://localhost:8088;
}
}
}
```
나는 당시에 HLS 서버의 스트리밍 파일을 nginx를 통해 서빙하려고 했었다. 차근 차근 살펴보자.
### Directive details
아래처럼 `;`으로 끝나는 설정 값들을 Nginx 에서는 `Directive` 라고 부른다. 구글링할 때 참고하자.
---
```
user nginx;
worker_processes 1;
```
nginx 서버를 띄우는(Worker Process를 생성하고 실행할) 시스템 사용자의 이름을 nginx 로 설정한다.
시스템에 사용자가 없다면 다음과 같이 생성해 주어야 한다.
```bash
adduser --system --no-create-home --shell /bin/false --group --disabled-login nginx
```
`worker_processes`는 설정 상 1개로 했다. 웬만한 과부화가 예상되지 않는 이상 1로도 사실 충분하다.
---
```
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
```
오류 로그를 어디다 저장할지는 `error_log`를 통해 설정한다. 초기 설정할때 자주 들여다 보게 된다.
초기 설정할 때, `lsof -n -t /var/log/nginx/error.log` 로 로그파일을 모니터링하고 있는 것도 시간을 절약할 수 있는 방법이다.
`pid`는 Master Process ID 를 저장할 파일 경로 지정한다. 별 생각없이 붙여넣어도 무방하다.
---
```
events {
worker_connections 1024;
}
```
`events` 블록안에는 접속 처리에 관한 설정이 들어간다.
`events.worker_connections` 에는 Worker Process 한 개당 동시 접속 수를 지정한다. 보통 `512` 나 `1024`를 주로 사용한다.
---
```
http {
# ...
}
```
`http` 블록 안에는 웹 / 프록시 관련 설정이 들어간다. 아래는 `http` 블록안에서 설장했던 내용들이다.
```
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
```
mime.types 파일을 읽어들이고, MIME 타입을 설정한 뒤 엑세스 로그 형식과 저장 경로를 지정한다.
```
# Some optimization tips.
# https://thoughts.t37.net/nginx-optimization-understanding-sendfile-tcp-nodelay-and-tcp-nopush-c55cdd276765
sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
gzip on;
```
`sendfile`과 `tcp_nopush` 옵션은 항상 같이 사용되어야 한다. 정적파일을 서빙해야 한다면, 최적화를 위해 반드시 켜두도록 하자.
파일을 서빙하기 전에 패킷에 데이터가 전부 차있는지 확인하는 절차가 들어가면서 불필요한 요청이 줄어드므로 네트워크 오버헤드가 줄어든다.
`tcp_nodelay` 는 TCP와 관련하여 좀 더 제너럴한 설정이며, 패킷당 최대 0.2초를 절약할 수 있는 최적화 설정이다.
TCP에는 전체 네트워크의 혼잡을 피하기 위해 기본적으로 0.2초를 기다리는 알고리즘이 있다. 그러나 이는 지금보다 인터넷이 훨씬 구릴때 이야기라,
모던한 인터넷과는 맞지 않는다. 이 옵션도 반드시 켜주도록 하자.
`keepalive`는 HTTP 요청/응답을 할 때 매번 3 way handshake를 하지 않기 위해 사용할 수 있는 옵션이다. 여기서는 65초로 타임아웃을 설정한다.
`gzip on`을 통해 컨텐츠의 압축 사용을 지정할 수 있다. 말 그대로 전송되는 데이터를 압축하여 줄이므로 마찬가지로 성능 튜닝하는 데 사용되는 옵션이다.
---
```
server {
listen 80;
root /usr/app;
location /hls/playlist.m3u8 {
add_header Cache-Control 'no-store, no-cache, must-revalidate, max-age=0';
add_header Content-type 'application/vnd.apple.mpegurl';
add_header Access-Control-Allow-Origin '*';
}
location ~ /hls/(chunk[0-9]+\.ts)$ {
alias /usr/app/hls/chunks/$1;
add_header Cache-Control 'no-store, no-cache, must-revalidate, max-age=0';
add_header Content-type 'video/MP2T';
add_header Access-Control-Allow-Origin '*';
}
location / {
proxy_pass http://localhost:8088;
}
}
```
`server`는 하나의 호스트를 선언하는 데 사용되고, 그 안의 `location`은 특정 URL을 통해 호스트로 들어온 요청에 대해 어떻게 처리할지를 정의한다.
`root /usr/app;`을 통해 정적 파일을 로드할 때 어떤 경로로 로드할 지를 결정한다.
예를 들어, `http://localhost/hls/playlist.m3u8` 으로 요청이 들어왔다면 첫번째 `location` 디렉티브에 의해 처리되는데
`/usr/app/hls/playlist.m3u8` 위치의 파일을 찾아 지정해주는 헤더와 함께 응답한다.
`root` 와 헷갈리는 것이 `alias`인데, 두번째 `location` 디렉티브를 살펴보자. 우선 `~` 는 정규표현식을 쓰겠다는 의사표시다.
요청이 `http://localhost/hls/chunk038.ts` 로 오게 된다면 `alias` 때문에 파일을 찾을 때 요청 경로를 무시하고
`/usr/app/hls/chunks/chunk038.ts` 를 찾게 된다. 정규표현식에 의해 `chunk038.ts`가 캡쳐되고 `$1` 에 치환되기 때문이다.
그리고 이외에 나머지 요청은 `proxy_pass` 를 통해 진짜 웹서버로 프록시를 해준다.
| 25.650943 | 110 | 0.682052 | kor_Hang | 0.999998 |
a10524a7845b9a4c76054e159b8aff4450692e72 | 374 | md | Markdown | README.md | thomasunderwood/Thermodynamics2015 | f96b234b089e3458ef06f18adab6cfbc844900e6 | [
"MIT"
] | 1 | 2016-10-11T23:10:40.000Z | 2016-10-11T23:10:40.000Z | README.md | thomasunderwood/Thermodynamics2015 | f96b234b089e3458ef06f18adab6cfbc844900e6 | [
"MIT"
] | null | null | null | README.md | thomasunderwood/Thermodynamics2015 | f96b234b089e3458ef06f18adab6cfbc844900e6 | [
"MIT"
] | null | null | null | # Thermodynamics 2015
My presentation for the Thermodynamics 2015 conference in Copenhagen. See link below:
http://thomasunderwood.github.io/thermodynamics2015
** LICENSE: **
Please ask for permission to use this presentation, or any of its subset images and videos.
** Acknowledgements: **
reveal.js:
MIT licensed;
Copyright (C) 2015 Hakim El Hattab [http://hakim.se]
| 24.933333 | 91 | 0.772727 | eng_Latn | 0.709973 |
a1056565a1ba4e16441cdd3abc37fec3aa46857d | 72 | md | Markdown | README.md | antonu17/ansible-openstack-clients | d19c98eb810e377b88416c23cfc4a44f97ff5277 | [
"MIT"
] | null | null | null | README.md | antonu17/ansible-openstack-clients | d19c98eb810e377b88416c23cfc4a44f97ff5277 | [
"MIT"
] | null | null | null | README.md | antonu17/ansible-openstack-clients | d19c98eb810e377b88416c23cfc4a44f97ff5277 | [
"MIT"
] | null | null | null | # ansible-openstack-clients
Install openstack console clients in xenial
| 24 | 43 | 0.847222 | eng_Latn | 0.709267 |
a10641fbc8dd21c0c3ed0f842322a97dd4a09380 | 525 | md | Markdown | _posts/2021-01-01-links.md | elvis-pan/elvis-pan.github.io | 3dc6bc055f94d7ad412ede12e4cd280a8cfa3872 | [
"MIT"
] | null | null | null | _posts/2021-01-01-links.md | elvis-pan/elvis-pan.github.io | 3dc6bc055f94d7ad412ede12e4cd280a8cfa3872 | [
"MIT"
] | null | null | null | _posts/2021-01-01-links.md | elvis-pan/elvis-pan.github.io | 3dc6bc055f94d7ad412ede12e4cd280a8cfa3872 | [
"MIT"
] | null | null | null | ---
layout: post
title: Links to several useful stuff.
date: 2021-01-01 00:00:00
description: Links to several useful (or not) stuff.
---
[Coursework](https://panyan7.github.io/blog/2021/courses/)
[CV](https://panyan7.github.io/cv/)
Resources:
[Algorithms for Competitive Programming](https://panyan7.github.io/projects/algorithm/)
Course Notes:
[10-725 Convex Optimization](https://panyan7.github.io/blog/2021/convexnotes/)
Miscellaneous:
[Graduate Courses](https://panyan7.github.io/assets/pdf/grad_courses.pdf)
| 21.875 | 87 | 0.750476 | yue_Hant | 0.463811 |
a1077d7315ae0e41757fe9b914e1889f3ae759a9 | 1,089 | md | Markdown | README.md | truqu/elm-review-noredundantconcat | ab248a19622b5c8e39130deaa9410e831e36dd7b | [
"BSD-3-Clause"
] | 2 | 2020-06-07T16:13:19.000Z | 2020-12-29T21:58:05.000Z | README.md | truqu/elm-review-noredundantconcat | ab248a19622b5c8e39130deaa9410e831e36dd7b | [
"BSD-3-Clause"
] | 2 | 2021-06-27T17:31:08.000Z | 2021-09-02T12:06:10.000Z | README.md | truqu/elm-review-noredundantconcat | ab248a19622b5c8e39130deaa9410e831e36dd7b | [
"BSD-3-Clause"
] | 1 | 2020-07-27T09:34:12.000Z | 2020-07-27T09:34:12.000Z | # elm-review-noredundantconcat
Helps with preventing redundant usage of concatenation. Expressions like `[ a ]
++ b` can be rewritten as `a :: b`, and expressions like `[ a ] ++ [ b ]` could
be simply `[ a, b ]`.
## Configuration
```elm
module ReviewConfig exposing (config)
import NoRedundantConcat
import Review.Rule exposing (Rule)
config : List Rule
config =
[ NoRedundantConcat.rule
]
```
## Currently covered
- [x] Concatenating list literals with `++` (`[ foo ] ++ [ bar ] -> [ foo, bar ]`)
- [x] Concatenating a list literal with some other value (`[ foo ] ++ bar -> foo :: bar`)
- [x] Using `List.concat` with list literals (`List.concat [ [ foo ], [ bar ] ] -> [ foo, bar ]`)
- [x] Using `++` with `String` literals (`"foo" ++ "bar" -> "foobar"`)
## Future work
- [ ] Using `List.append` with list literals
- [ ] Using `String.append` with string literals
- [ ] Using `String.concat` with string literals
- [ ] Using `String.join ""` over `String.concat`
These all follow a common pattern of making the concatenation of literals more
complex than it has to be.
| 29.432432 | 97 | 0.657484 | eng_Latn | 0.947735 |
a1077e4545905adb834a8fa17703f518cdab31bc | 2,170 | md | Markdown | CONTRIBUTING.md | aussielunix/ansible-role-vim | 696e2ffffab420dab151b5d6be43559b90020088 | [
"MIT"
] | null | null | null | CONTRIBUTING.md | aussielunix/ansible-role-vim | 696e2ffffab420dab151b5d6be43559b90020088 | [
"MIT"
] | null | null | null | CONTRIBUTING.md | aussielunix/ansible-role-vim | 696e2ffffab420dab151b5d6be43559b90020088 | [
"MIT"
] | null | null | null | # [Please contribute](#please-contribute)
You can really make a difference by:
- [Making an issue](https://help.github.com/articles/creating-an-issue/). A well described issue helps a lot. (Have a look at the [known issues](https://github.com/search?q=user%3Aaussielunix+is%3Aissue+state%3Aopen).)
- [Making a pull request](https://services.github.com/on-demand/github-cli/open-pull-request-github) when you see the error in code.
I'll try to help and take every contribution seriously.
It's a great opportunity for me to learn how you use the role and also an opportunity to get into the habit of contributing to open source software.
## [Step by step](#step-by-step)
Here is how you can help, a lot of steps are related to GitHub, not specifically my roles.
### [1. Make an issue.](#1-make-an-issue)
When you spot an issue, [create an issue](https://github.com/aussielunix/vim/issues).
Making the issue help me and others to find similar problems in the future.
### [2. Fork the project.](#2-fork-the-project)
On the top right side of [the repository on GitHub](https://github.com/aussielunix/vim), click `fork`. This copies everything to your GitHub namespace.
### [3. Make the changes](#3-make-the-changes)
In you own GitHub namespace, make the required changes.
I typically do that by cloning the repository (in your namespace) locally:
```bash
git clone git@github.com:YOURNAMESPACE/ansible-role-vim.git
```
Now you can start to edit on your laptop.
### [4. Make a pull request](#4-make-a-pull-request)
[GitHub](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) on pull requests.
In the comment-box, you can [refer to the issue number](https://help.github.com/en/github/writing-on-github/autolinked-references-and-urls) by using #123, where 123 is the issue number.
### [5. Wait](#5-wait)
Now I'll get a message that you've added some code. Thank you, really.
CI starts to test your changes. You can follow the progress on [GitHub Actions](https://github.com/aussielunix/ansible-role-vim/actions).
Please consider [sponsoring me](https://github.com/sponsors/aussielunix) | 49.318182 | 218 | 0.747926 | eng_Latn | 0.975133 |
a1084582c6295e6b895039f6f2f5016a71887bc4 | 4,477 | md | Markdown | README.md | cloudluis22/br-bad-universe-react-app | 7c5d2d87817a11b19e9e49b6d867a747a485efee | [
"MIT"
] | null | null | null | README.md | cloudluis22/br-bad-universe-react-app | 7c5d2d87817a11b19e9e49b6d867a747a485efee | [
"MIT"
] | null | null | null | README.md | cloudluis22/br-bad-universe-react-app | 7c5d2d87817a11b19e9e49b6d867a747a485efee | [
"MIT"
] | null | null | null |
# Breaking Bad Universe Database v. 1.0 ⚛️
**NOTA: Para ver una versión de este archivo en español, por favor mira el archivo [README-es.md](https://github.com/cloudluis22/br-bad-universe-react-app/blob/main/README-es.md)**.
This is the Breaking Bad Universe Database, a webapp made with React alongside SASS for sheet styling using **[The Breaking Bad API](https://breakingbadapi.com)**.
This application allows users to search for their favorite Breaking Bad and Better Call Saul characters and read a small
summary about them displayed in cards.
Currently, this application is in it's first release v. 1.0, and therefore, I'm looking forward to [adding more features](#future-changes-and-improvements-to-the-application-💫).
## Running this project in your machine 💻
Although there is the GitHub pages deploy of this application, if you wish to run it locally on your machine for whatever purpose you want, you can do it.
# Clone this repository.
$ git clone https://github.com/cloudluis22/br-bad-universe-react-app.git
$ cd br-bad-universe-react-app
Afterwards, you should reinstall all the node modules and you will be ready to go.
# Reinstalling modules.
$ npm install
# Running the project.
$ npm start
This project is made with [Create React App](https://create-react-app.dev), so you have full access to all the scripts and everything it includes with it.
## Usage ⚙️
The default route of the application is the main screen, here you can choose between the two shows.
The footer displayed below always remains there and you can see some links for my GitHub profile, this repo as well as a link for the API webpage.
In any of the both shows you will get an interface like this one, on the top of the page is the logo of the selected show and below it the search bar, you can look up for any character
that makes an apparition on that particular series *(Better Call Saul includes re-apparitions)*. If you make a search, you can press the reset button that will appear beside the bar to
bring back all characters again.
<p align="center">
<img src="https://user-images.githubusercontent.com/70856719/132926283-96a86f17-d03c-407a-8985-a2fc518ac1cc.PNG" >
</p>
Pressing on any characters card will pop-up a little window with some information about it, such as the actor/actress who portrays that role, birthday, nicknames and other stuff. You can exit
the window by using the cross in the top-right corner of the window or just pressing outside of it.
If you want to switch to the other show, just use the arrow at the top-right of the page.
The responsive design for this project is currently not the best yet, but will continue to improve within the next releases of this application.
<p align="center">
<img src="https://user-images.githubusercontent.com/70856719/132927859-034eb61f-bfa4-4893-8ab1-3807508f9f21.png" width="350" height="350">
<img src="https://user-images.githubusercontent.com/70856719/132927889-58dd1646-7522-4a40-9ed9-d32054308f89.png" width="200" height="250">
<img src="https://user-images.githubusercontent.com/70856719/132928233-ec478c29-7645-4094-a8be-3cc9000f283a.png" width="100" height="150">
<p/>
## Future changes and improvements to the application 💫
Starting from version 1.0, this is a list of other features and fixes I want to do to the application.
- [ ] Add a dark mode to the modals.
- [ ] Adding a navigation bar.
- [ ] Improved styling.
- [ ] Add Random Deaths screen from the API functionality.
- [ ] Add Random Quotes screen from the API functionality. | 59.693333 | 191 | 0.770382 | eng_Latn | 0.962087 |
a108d7ef5500c3b0fe1d9437920c22c43f323d66 | 18,422 | md | Markdown | quark-common.md | LeonDCd/JavaQuarkBBS | d5b228c424b831d062a2d0fdfd34ce9bcf02bc71 | [
"Apache-2.0"
] | null | null | null | quark-common.md | LeonDCd/JavaQuarkBBS | d5b228c424b831d062a2d0fdfd34ce9bcf02bc71 | [
"Apache-2.0"
] | null | null | null | quark-common.md | LeonDCd/JavaQuarkBBS | d5b228c424b831d062a2d0fdfd34ce9bcf02bc71 | [
"Apache-2.0"
] | 3 | 2020-10-08T08:20:07.000Z | 2020-10-19T02:17:08.000Z | [TOC]
# quark-common
## src
### main
#### java/com/quark/common
##### base
###### BaseController.java
自动生成日志。
###### BaseService.java
| 接口：BaseService<T> |
| ------------------------------------------------------------ |
| 方法T findOne(int key) |
| 方法T save(T entity) |
| 方法void delete(Object key) |
| 方法List<T> findAll() |
| 方法void deleteInBatch(Iterable<T> iterable)，批量删除，根据传入的Iterable，在表中依次删除Iterable的所有数据 |
| 方法List<T> findAll(Iterable<Integer> iterable)，批量查找，根据传入的Iterable，在表中依次查找Iterable的所有数据 |
| 方法List<T> save(Iterable<T> iterable)，批量保存，根据传入的Iterable，在表中依次保存Iterable的所有数据 |
###### BaseServiceImpl.java
`@Autowired`：可以对类成员变量、方法及构造函数进行标注，完成自动装配的工作。通过 @Autowired的使用来消除 set ，get方法
| 模板类：BaseServiceImpl<E extends JpaRepository,T> implements BaseService<T> |
| ------------------------------------------------------------ |
| 成员：protected E repository，是E类的（继承了JpaRepository），有注解@Autowired |
| 方法T findOne(int key)，有注解@Override（在AdminUserDao.java中解释） |
| 方法T save(T entity)，有注解@Override |
| 方法delete(Object key)，有注解@Override |
| 方法List<T> findAll()，有注解@Override |
| 方法void deleteInBatch(Iterable<T> iterable)，有注解@Override |
| 方法List<T> findAll(Iterable<Integer> iterable)，有注解@Override |
| 方法List<T> save(Iterable<T> iterable)，有注解@Override |
###### ResultProcessor.java
`@FunctionalInterface`：只能标记在有且仅有一个抽象方法的接口上，加上该注解能够更好地让编译器进行检查。
| 接口：ResultProcessor |
| --------------------------------- |
| 方法QuarkResult process()，仅申明 |
##### dao
数据访问对象data access object，各文件内的接口中的方法都是某一sql查询语句，分别对相应的表进行操作。
###### AdminUserDao.java
与表quark_adminuser有关的sql。
`@Repository`：把对象交给spring管理，用于注解DAO类
`@CacheConfig(cacheNames = "adminusers")`：类级别的注解，该类的数据缓存在名为adminusers的缓存空间中
`@Cacheable`：加了该注解的方法的结果可以存放在缓存里
`@Override`：检查对应的方法是否是你父类中所有的，如果没有则报错，防止错写
JpaRepository可以根据方法名自动生成sql：https://blog.csdn.net/fly910905/article/details/78557110
| 接口：AdminUserDao，继承了JpaRepository<AdminUser,Integer>和JpaSpecificationExecutor |
| ------------------------------------------------------------ |
| 方法AdminUser findOne(Integer integer)，返回AdminUser类绑定的表（即表quark_adminuser，见entity/AdiminUser.java）中primary key = integer的数据 |
| 方法List<AdminUser> findAll()，有注解@Cacheable，返回AdminUser类绑定的表的所有结果 |
| 方法AdminUser findByUsername(String username)，返回表中属性Username = username的数据 |
| 方法List findAll(Specification specification, Sort sort)，有注解@Cacheable和@Override，根据复杂查询specification得到结果，并按sort进行排序 |
###### CollectDao.java
与表quark_collect有关的sql。
接口：CollectDao extends JpaRepository<Collect,Integer>。
###### LabelDao.java
与表quark-label有关的sql。
接口：LabelDao extends JpaRepository<Label,Integer>。
###### NotificationDao.java
与表quark_notification有关的sql。
`@Query`：value中写sql语句，加上nativeQuery = true表示是原生sql语句，加了该注解的方法将使用该sql语句对响应表进行操作
`@Modifying`：涉及修改的sql语句，需要加上这个注解
| 接口：NotificationDao extends JpaRepository<Notification, Integer> |
| ------------------------------------------------------------ |
| 方法long getNotificationCount(Integer id)，有注解@Query，根据查询id的未读通知数量 |
| 方法List<Notification> getByTouserOrderByInitTimeDesc(User user)，查询所有touser=user的记录并按照InitTime进行降序排序 |
| 方法void updateByIsRead(User user)，有注释@Query和@Modifying，将user的已读通知的is_read属性更新为true |
###### PermissionDao.java
与表quark_permission有关的sql。
| 接口：PermissionDao extends JpaRepository<Permission,Integer> |
| ------------------------------------------------------------ |
| 方法Permission findOne(Integer integer) |
| 方法List<Permission> findAll()，有注解@cacheable |
###### PostsDao.java
与表quark_posts有关的sql。
| 接口：PostsDao extends JpaRepository<Posts,Integer> ,JpaSpecificationExecutor |
| ------------------------------------------------------------ |
| 方法List<Posts> findAll()，有注解@Cacheable 和@Override |
| 方法List<Object> findHot()，@Query查询表quark-posts中30天内回复数最多的10个帖子的id，title和reply_count |
| 方法Page<Posts> findByUser(User user, Pageable pageable)，返回所有User发的贴，Page<Posts>格式 |
| 方法Page<Posts> findByLabel(Label label,Pageable pageable)，返回所有标签为Label的贴，Page<Posts>格式 |
###### ReplyDao.java
与表quark_reply有关的sql。
| 接口：ReplyDao extends JpaRepository<Reply,Integer>,JpaSpecificationExecutor |
| ------------------------------------------------------------ |
| 方法List<Reply> findAll()，有注解@Cacheable和@Override |
###### RoleDao.java
与表quark-role有关的sql。
| 接口：RoleDao extends JpaRepository<Role,Integer> |
| ------------------------------------------------- |
| 方法Role findOne(Integer integer) |
| 方法List<Role> findAll()，有注解@cacheable |
###### UserDao.java
与表quark-user有关的sql。
| 接口：UserDao extends JpaRepository<User,Integer> ,JpaSpecificationExecutor |
| ------------------------------------------------------------ |
| 方法User findByUsername(String username) |
| 方法User findByEmail(String email) |
| 方法List<Object> findNewUser()，有注解@Query，找到30天内最近注册的12个用户，返回id，username和icon |
##### dto
数据传输对象data transfer object
###### PageResult.java
| 模板类：PageResult(implement serializable，实现java.io中的serializable接口) |
| ------------------------------------------------------------ |
| 成员：`private String draw请求次数` `private Long recordsTotal总记录数` `private Long recordsFiltered过滤后的总记录数 ` `private T data具体的数据` |
| 每个成员都有get和set方法 |
| 构造方法PageResult(String draw, Long recordsTotal, Long recordsFiltered, T data) |
###### QuarkResult.java
| 类：QuarkResult implement serializable |
| ------------------------------------------------------------ |
| 成员：`状态 private Integer status; ` `返回的数据private Object data` `错误信息private String error ` `返回总页数private long pageSize` `本页返回数量 private Integer total` |
| 每个成员都有set和get方法 |
| 4个构造方法`QuarkResult(Integer status)`，`QuarkResult(Integer status, Object data)`，`QuarkResult(Integer status, Object data, long pageSize, Integer total)`，`QuarkResult(Integer status, String error)` |
| 方法ok()：返回值为状态成功（200）的QuarkResult |
| 方法ok(Object data)：返回值状态成功且数据为data |
| 方法warn(string warn):返回值状态警告（400）和警告信息 |
| 方法error(string error):返回值状态错误（500）和错误信息 |
| 方法QuarkResult ok(Object data,long pageSize,Integer total) |
###### SocketMessage.java
| 类：SocketMessage implements Serializable |
| ------------------------------------------------------------ |
| 成员：`private Integer notice` `private String message` |
| 每个成员都有set和get方法 |
| 有两个构造方法`SocketMessage(Integer notice, String message)`和`SocketMessage(Integer notice)` |
| 方法public static SocketMessage build(Integer notice)，根据notice构造一个新的SocketMessage并返回 |
| 方法public static SocketMessage build(Integer notice,String message)，根据notice和message构造一个新的SocketMessage并返回 |
###### UploadResult.java
| 类：UploadResult implements Serializable |
| ------------------------------------------------------------ |
| 成员：`private Integer code，0表示成功，其余失败` `private String msg，错误消息`， `private Data data` |
| 每个成员都有set和get方法 |
| 成功时的构造方法UploadResult(Integer code, Data data) |
| 失败时的构造方法UploadResult(Integer code, String msg) |
| 类：Data |
| ------------------------------------------------------------ |
| 成员：`private String src，路径`，`private String title，名称` |
| 两成员各有get方法 |
| 构造方法Data(String src) |
##### entity
该目录下都是实体类。
###### AdminUser.java
对应表quark_adminuser。
`@Entity`：为某个类做注解，表明该类是一个实体类
` @Table`：为某个类做注解，声明与该实体类映射的数据库表名， 注解中的常用选项是 name，用于指明数据库的表名
`@Id`：为变量做注解，表示它是对应表的primary key
`@GeneratedValue`：为变量做注解，为一个实体生成一个唯一标识的primary key，与`@Id`配合使用
`@Column`：为变量做注解，标识其与数据表中字段的对应关系
`@JsonIgnore`：返回的json数据不包含该属性
`@JoinTable`：两个表相关联时使用，指出某两个表相关联时的各种关系
`@JoinColumn`：指出该表与其他表关联时用到的连接列，通常用于规定reference key
` @ManyToMany`：和@JoinTable配合使用，指出两个表的关联是多对多的，且通常有cascade属性指明两个表的级联关系。
| 类：AdminUser implements Serializable |
| ------------------------------------------------------------ |
| 成员：private Integer id，有注解@Id和@GeneratedValue，表示它是表中的主键 |
| 成员：private String username，有注解@Column(unique = true,nullable = false)，表示该属性在表中是唯一的，且不能为null |
| 成员：private String password，有注解@Column(nullable = false)和@JsonIgnore，表示不能为null且返回的json数据不包括password |
| 成员：private Integer enable = 1，有注解@Column(nullable = false)，表示其默认为1，且不可为null,含义为“该管理员账号是否可以使用” |
| 成员：private Set<Role> roles = new HashSet<>()，有注解`@JsonIgnore， @JoinTable(name = "quark_adminuser_role", joinColumns = {@JoinColumn(name = "adminuser_id",referencedColumnName = "id")}, inverseJoinColumns = {@JoinColumn(name = "role_id",referencedColumnName = "id")}) ，@ManyToMany(cascade = CascadeType.ALL)`，表示返回的json数据不包括roles，且当与表quark_adminuser_role关联时的连接列，以及两表是多对多关系，级联关系是ALL，表示一个表进行某种修改，另一个表都会级联修改。 |
| 每个成员都有get和set方法 |
| 方法public String toString() ，有注解@Override，规定返回的json数据的格式 |
###### Collect.java
对应表quark_collect。
`@ManyToOne `：指出两表的是多对一关系，其中的属性fetch规定加载数据时是懒加载还是急加载——https://blog.csdn.net/u010082453/article/details/43339031
| 类：Collect implements Serializable |
| ------------------------------------------------------------ |
| 成员：private Integer id，有注解@Id和@GeneratedValue |
| 成员：private Posts posts，有注解@ManyToOne(fetch = FetchType.EAGER)和 @JoinColumn(nullable = false, name = "posts_id")，表示quark-collect和quark-posts是多对一关系，急加载，且关联列是posts_id，不可为null |
| 成员：private User user，有注解@ManyToOne(fetch = FetchType.EAGER) 和@JoinColumn(nullable = false, name = "user_id") |
| 成员：private Date initTime，有注解@JsonFormat(pattern = Constants.DATETIME_FORMAT)，规定了initTime的json格式是DATETIME_FORMAT（见utils/Constants.java） |
| 每个成员都有get和set方法 |
###### Label.java
对应表quark_label。
| 类：Label implements Serializable |
| ------------------------------------------------------------ |
| 成员：private Integer id，有注解@Id和@GeneratedValue |
| 成员：private String name，有注解@Column(nullable = false, unique = true) |
| 成员：private Integer postsCount = 0，有注解 @Column(name = "posts_count")，主题数量默认为0 |
| 成员：private String details |
| 每个成员都有get和set方法 |
###### Notification.java
对应表quark_notification。
| 类：Notification |
| ------------------------------------------------------------ |
| 成员：private Integer id，有注解@Id和@GeneratedValue |
| 成员：private boolean isRead = false，有注解@Column(name = "is_read")，是否已读 |
| 成员：private User touser，有注解@ManyToOne(fetch = FetchType.EAGER)和@JoinColumn(nullable = false,name = "touser_id")，要通知的用户 |
| 成员：private User fromuser，有注解@ManyToOne(fetch = FetchType.EAGER)和@JoinColumn(nullable = false,name = "fromuser_id")，发起通知的用户 |
| 成员：private Posts posts，有注解@ManyToOne(fetch = FetchType.EAGER)和@JoinColumn(nullable = false,name = "posts_id") |
| 成员：private Date initTime，@Column(nullable = false) @JsonFormat(pattern = Constants.DATETIME_FORMAT, timezone = "GMT+8")，发布时间 |
| 每个成员都由get和set方法 |
###### Permission.java
对应表quark_permission。
`@Transient`：表示该对象是个临时对象，不存入数据库
`mappedBy`：拥有关联关系的域，https://blog.csdn.net/xichenguan/article/details/44857799
| 类：Permission implements Serializable |
| ------------------------------------------------------------ |
| 成员：private Integer id，有注解@Id @GeneratedValue |
| 成员：private String name |
| 成员：private String perurl |
| 成员：private Integer type，表示资源类型，1是菜单，2是按钮 |
| 成员:private Integer parentid，有注解@Column(nullable = false)，父权限 |
| 成员：private Integer sort，排序 |
| 成员：private String checked，@Transient，临时变量，是否选中 |
| 成员：private Set<Role> roles = new HashSet<>()，有注解@JsonIgnore和@ManyToMany(mappedBy = "permissions")，与quark_role的关系是多对多的，且在quark_role中的名称是permissions |
| 每个成员都有get和set方法 |
###### Posts.java
对应表quark_posts。
`columnDefinition` ：指出该列的数据类型
| 类：Posts implements Serializable |
| ------------------------------------------------------------ |
| 成员：private Integer id，有注解@Id和@GeneratedValue |
| 成员：private Label label，有注解@ManyToOne和@JoinColumn(nullable = false, name = "label_id")，与标签的关系 |
| 成员：private String title，有注解@Column(unique = true, nullable = false)，标题 |
| 成员：private String content，有注解@Column(columnDefinition = "text")，内容，数据类型为文本 |
| 成员：private Date initTime，有注解@Column(nullable = false) 和@JsonFormat(pattern = Constants.DATETIME_FORMAT, timezone = "GMT+8")，发布时间 |
| 成员：private boolean top，是否置顶 |
| 成员：private boolean good，是否是精品贴 |
| 成员：private User user，有注解@ManyToOne和@JoinColumn(nullable = false, name = "user_id")，指出与用户的关联关系 |
| 成员：private int replyCount = 0，有注解@Column(name = "reply_count")，回复数量默认为0 |
| 每个成员都有set和get方法 |
| 方法String toString()，有注解@Override，规定返回的json数据的格式 |
###### Reply.java
对应表quark_reply。
| 类：Reply implements Serializable |
| ------------------------------------------------------------ |
| 成员：private Integer id，：有注解@Id和@GeneratedValue |
| 成员：private String content，有注解@Column(columnDefinition = "text", nullable = false)，回复的内容 |
| 成员：private Date initTime，有注解@JsonFormat(pattern = Constants.DATETIME_FORMAT, timezone = "GMT+8")，回复的时间 |
| 成员：private Integer up = 0，点赞个数默认为0 |
| 成员：private User user，有注解@ManyToOne和@JoinColumn(nullable = false, name = "user_id")，指出与用户的关联关系 |
| 每个成员都有set和get方法 |
| 方法String toString()，有注解@Override，规定返回的json数据的格式 |
###### Role.java
对应表quark_role
| 类：Role implements Serializable |
| ------------------------------------------------------------ |
| 成员：private Integer id，有注解@Id和@GeneratedValue |
| 成员：private String name，有注解@Column(unique = true,nullable = false) |
| 成员： private String description，对角色的描述 |
| 成员：private Integer selected，有注解@Transient，临时变量，是否选中 |
| 成员：private Set<AdminUser> adminUsers = new HashSet<>()，有注解@JsonIgnore和@ManyToMany(mappedBy = "roles")，指出角色与用户的关联关系 |
| 成员：private Set<Permission> permissions = new HashSet<>()，有注解@JsonIgnore @JoinTable(name = "quark_role_permission", joinColumns = {@JoinColumn(name = "role_id",referencedColumnName = "id")}, inverseJoinColumns = {@JoinColumn(name = "permissions_id",referencedColumnName = "id")}) @ManyToMany(cascade = CascadeType.ALL)，指出角色与权限的关联关系 |
| 每个成员都有set和get方法 |
| 方法String toString()，有注解@Override，规定返回的json数据的格式 |
###### User.java
| User implements Serializable |
| ------------------------------------------------------------ |
| 成员：private Integer id，有注解@Id和@GeneratedValue |
| 成员：private String email，有注解@Column(nullable = false)，注册邮箱 |
| 成员：private String username，有注解@Column(unique = true, nullable = false) |
| 成员：private String password，有注解@Column(nullable = false)和@JsonIgnore |
| 成员： private String icon ="http://127.0.0.1/images/upload/default.png"，头像，修改路径可以更改默认头像 |
| 成员：private String signature，个人签名 |
| 成员：private Date initTime，有注解@Column(nullable = false) 和@JsonFormat(pattern = Constants.DATE_FORMAT, timezone = "GMT+8")，注册时间 |
| 成员：private Integer sex = 0，女性为1，男性为0 |
| 成员：private Integer enable = 1，有注解@Column(nullable = false)，是否可用，默认为１表示可用，0表示账号被封禁 |
| 每个成员都有set和get方法 |
| 方法String toString()，有注解@Override，规定返回的json数据的格式 |
##### enums
###### StateEnum.java
定义了状态的枚举：SUCCESS(200),WARN(400),ERROR(500)、
私有整数成员state、构造函数和getstate方法
##### exception
###### ServiceProcessException.java
捕获运行过程中的异常。
| 类：ServiceProcessException extends RuntimeException |
| ------------------------------------------------------------ |
| 构造方法ServiceProcessException(String message),根据异常信息构造对象 |
| 构造方法ServiceProcessException(String message, Throwable cause)，根据异常信息和原因构造对象 |
##### utils
###### Constants.java
给可能用到的一些常量取别名，类似于宏。
| 类：Constants |
| ------------------------------------------------------------ |
| 成员`public static final String DATE_FORMAT = "yyyy-MM-dd"`，规定日期的格式 |
| 成员`public static final String DATETIME_FORMAT = "yyyy-MM-dd HH:mm:ss"`，规定日期时间格式 |
##### CommonApplication.java
1、 `@SpringBootApplication` ：申明让spring boot自动给程序进行必要的配置，开启spring boot的各项能力；
2、 `@EnableCaching` ：缓存功能，https://blog.csdn.net/weixin_38750084/article/details/83628886，https://blog.csdn.net/andy_zhang2007/article/details/97010733
3、
```
public static void main(String[] args) {
SpringApplication.run(CommonApplication.class, args);
}
```
SpringApplication.run主要做两件事：
（1）创建SpringApplication对象：在对象初始化时保存事件监听器，容器初始化类以及判断是否为web应用，保存包含main方法的主配置类。
（2）调用run方法：准备spring的上下文，完成容器的初始化，创建，加载等。会在不同的时机触发监听器的不同事件。
SpringApplication.run的**参数是当前类的class和main的参数**，它会找到上面的注解@SpringBootApplication开始进行要求的所有配置
#### resources
##### application.properties
包含Mysql的配置（数据源类型、URL、数据库用户名和密码、jdbc驱动），JPA配置和对数据源的一些操作时间限制。
##### ehcache.xml
对各种缓存空间（默认缓存空间和@cacheconfig建立的缓存空间）进行配置。
### test/java/com/quark/common/CommonApplicationTest.java
构造了对数据库中的数据进行测试的类及其成员和方法名，但方法没有实现。
## target
都是src中的文件进行编译后产生的文件。
## pom.xml
maven的配置文件：https://blog.csdn.net/qq_33363618/article/details/79438044，针对整个quark-common
## quark-common.iml
IDEA自动生成的配置文件：https://blog.csdn.net/weixin_41699562/article/details/99552780，针对整个quark-common | 37.36714 | 409 | 0.604115 | yue_Hant | 0.584363 |
a10903ef6c19adbb05f40f55d064bab48a387d90 | 8,475 | md | Markdown | approvaltests-util/docs/reference/Query.md | rzabini/ApprovalTests.Java | 32aa5a150bd34d78d0bca935442f729af418c39c | [
"Apache-2.0"
] | 213 | 2015-02-18T09:51:44.000Z | 2022-03-29T17:32:29.000Z | approvaltests-util/docs/reference/Query.md | rzabini/ApprovalTests.Java | 32aa5a150bd34d78d0bca935442f729af418c39c | [
"Apache-2.0"
] | 128 | 2015-01-28T15:15:53.000Z | 2022-03-24T12:42:35.000Z | approvaltests-util/docs/reference/Query.md | rzabini/ApprovalTests.Java | 32aa5a150bd34d78d0bca935442f729af418c39c | [
"Apache-2.0"
] | 63 | 2015-02-06T14:26:07.000Z | 2022-03-15T10:28:07.000Z | <a id="top"></a>
# Query and Queryable
<!-- toc -->
## Contents
* [What it is](#what-it-is)
* [Comparison vs. Streams](#comparison-vs-streams)
* [Other benefits](#other-benefits)
* [Queryable extends List](#queryable-extends-list)
* [API](#api)
* [SelectMany](#selectmany)
* [SelectMany vs SelectManyArray](#selectmany-vs-selectmanyarray)
* [Example:](#example)
* [GroupBy](#groupby)
* [Full transforms](#full-transforms)
* [HowTos](#howtos)<!-- endToc -->
## What it is
Query (and the Queryable wrapper) is an alternative to Streams. In other words it is an implementation of Map/Reduce
based on the naming style of MS Linq.
### Comparison vs. Streams
Here is an example of filtering a list of numbers for only even numbers, sorted in reverse order:
<!-- snippet: query_example -->
<a id='snippet-query_example'></a>
```java
Integer[] numbers = Range.get(1, 20);
Integer[] evenQueryNumbers = Query.where(numbers, n -> n % 2 == 0).orderBy(OrderBy.Order.Descending, n -> n)
.asArray();
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryTest.java#L34-L38' title='Snippet source file'>snippet source</a> | <a href='#snippet-query_example' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
Here is the exact same function but using Java Streams:
<!-- snippet: stream_example -->
<a id='snippet-stream_example'></a>
```java
Integer[] evenStreamNumbers = Arrays.stream(numbers).filter(n -> n % 2 == 0)
.sorted((o1, o2) -> o2.compareTo(o1)).toArray(Integer[]::new);
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryTest.java#L39-L42' title='Snippet source file'>snippet source</a> | <a href='#snippet-stream_example' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
Another example using sum() vs. reduce():
<!-- snippet: query_sum_example -->
<a id='snippet-query_sum_example'></a>
```java
String[] names = {"Llewellyn", "Scott"};
int lengthsFromQuery = Query.sum(names, n -> n.length()).intValue();
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryTest.java#L46-L49' title='Snippet source file'>snippet source</a> | <a href='#snippet-query_sum_example' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
Here is the exact same function but using Java Streams:
<!-- snippet: stream_sum_example -->
<a id='snippet-stream_sum_example'></a>
```java
int lengthsFromStream = (int) Arrays.stream(names).map(n -> n.length()).reduce(0, (a, b) -> a + b);
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryTest.java#L50-L52' title='Snippet source file'>snippet source</a> | <a href='#snippet-stream_sum_example' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
#### Other benefits
* Simpler interface
* Queryable<T> extends List<T>
* Queryable is customizable
* Uses SQL syntax
### Queryable extends List
Another advantage of Query and Queryable is that Queryable extends List. Here is an example of converting
an Array of Integers to Strings:
Using Query:
<!-- snippet: list_is_queryable -->
<a id='snippet-list_is_queryable'></a>
```java
List<String> strings = Query.select(numbers, n -> "" + n);
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryTest.java#L57-L59' title='Snippet source file'>snippet source</a> | <a href='#snippet-list_is_queryable' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
Using Streams:
<!-- snippet: list_from_stream -->
<a id='snippet-list_from_stream'></a>
```java
List<String> strings2 = Arrays.stream(numbers).map(n -> "" + n).collect(Collectors.toList());
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryTest.java#L60-L62' title='Snippet source file'>snippet source</a> | <a href='#snippet-list_from_stream' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
### API
#### SelectMany
SelectMany allows you to flatten query results.
For example:
If each element of your SELECT statement is a List<String> you would get back a List<List<String>>. If you would like to flatten that into a List<String>, the easiest way is to do a Query.selectMany().
##### SelectMany vs SelectManyArray
Because of the limitations of the Java language, we could not override the function to allow you to return either a list or an array in your query. As a workaround we overrode the name, so if you are returning a String[] you would need to call selectManyArray.
##### Example:
The following code extracts the words from the following sentences, and orders them alphabetically:
<!-- snippet: queryable_select_many -->
<a id='snippet-queryable_select_many'></a>
```java
Queryable<String> names = Queryable.as("Now is the time", "Fourscore and seven years ago",
"When in the course of human events");
Queryable<String> allNames = names.selectMany(n -> Arrays.asList(n.split(" "))).orderBy(n -> n);
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryableTest.java#L140-L144' title='Snippet source file'>snippet source</a> | <a href='#snippet-queryable_select_many' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
resulting in
<!-- snippet: QueryableTest.testSelectManyCharacters.approved.txt -->
<a id='snippet-QueryableTest.testSelectManyCharacters.approved.txt'></a>
```txt
[0] = Fourscore
[1] = Now
[2] = When
[3] = ago
[4] = and
[5] = course
[6] = events
[7] = human
[8] = in
[9] = is
[10] = of
[11] = seven
[12] = the
[13] = the
[14] = time
[15] = years
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryableTest.testSelectManyCharacters.approved.txt#L1-L16' title='Snippet source file'>snippet source</a> | <a href='#snippet-QueryableTest.testSelectManyCharacters.approved.txt' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
### GroupBy
Here is a simple example of grouping words by their first letter.
<!-- snippet: group_by_key -->
<a id='snippet-group_by_key'></a>
```java
Queryable<String> words = Queryable.as("Jack", "and", "Jill", "jumped", "up", "the", "hill");
Queryable<Entry<Character, Queryable<String>>> result = words.groupBy(w -> w.toLowerCase().charAt(0));
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryableTest.java#L150-L153' title='Snippet source file'>snippet source</a> | <a href='#snippet-group_by_key' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
producing:
<!-- snippet: QueryableTest.testGroupBy.approved.txt -->
<a id='snippet-QueryableTest.testGroupBy.approved.txt'></a>
```txt
[0] = j=[Jack, Jill, jumped]
[1] = a=[and]
[2] = u=[up]
[3] = t=[the]
[4] = h=[hill]
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryableTest.testGroupBy.approved.txt#L1-L5' title='Snippet source file'>snippet source</a> | <a href='#snippet-QueryableTest.testGroupBy.approved.txt' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
#### Full transforms
In a group by, you can select both how the key is selected and how each object for the key is selected,
as well as how the final list is transformed.
Here is an example of doing all three to count the number of words of the same length:
<!-- snippet: group_by_full -->
<a id='snippet-group_by_full'></a>
```java
Queryable<String> words = Queryable.as("One Fish Two Fish Red Fish Blue Fish".split(" "));
Queryable<Entry<Object, Object>> result = words.groupBy(w -> w.length(), w -> w.toLowerCase(),
r -> r.join("_"));
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryableTest.java#L173-L177' title='Snippet source file'>snippet source</a> | <a href='#snippet-group_by_full' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
resulting in
<!-- snippet: QueryableTest.testGroupByCombineWordsOfSimilarLengths.approved.txt -->
<a id='snippet-QueryableTest.testGroupByCombineWordsOfSimilarLengths.approved.txt'></a>
```txt
3 = one_two_red
4 = fish_fish_fish_blue_fish
```
<sup><a href='/approvaltests-util-tests/src/test/java/org/lambda/query/QueryableTest.testGroupByCombineWordsOfSimilarLengths.approved.txt#L1-L2' title='Snippet source file'>snippet source</a> | <a href='#snippet-QueryableTest.testGroupByCombineWordsOfSimilarLengths.approved.txt' title='Start of snippet'>anchor</a></sup>
<!-- endSnippet -->
## HowTos
* [How to extend Queryable](../how_to/ExtendQueryable.md#top)
---
[Back to User Guide](README.md#top)
| 40.942029 | 321 | 0.709381 | eng_Latn | 0.549315 |
a109043b0c5a808ee65fa3da6202529e55430588 | 1,624 | md | Markdown | docs/debugger/debug-interface-access/idiasymbol-get-rank.md | ManuSquall/visualstudio-docs.fr-fr | 87f0072eb292673de4a102be704162619838365f | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-08-15T11:25:55.000Z | 2021-08-15T11:25:55.000Z | docs/debugger/debug-interface-access/idiasymbol-get-rank.md | ManuSquall/visualstudio-docs.fr-fr | 87f0072eb292673de4a102be704162619838365f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/debugger/debug-interface-access/idiasymbol-get-rank.md | ManuSquall/visualstudio-docs.fr-fr | 87f0072eb292673de4a102be704162619838365f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: Récupère le rang (nombre de dimensions) d’un tableau multidimensionnel FORTRAN.
title: IDiaSymbol::get_rank | Microsoft Docs
ms.date: 11/04/2016
ms.topic: reference
dev_langs:
- C++
helpviewer_keywords:
- IDiaSymbol::get_rank method
ms.assetid: 14cc9c4b-a5ec-414a-b01f-4a142c17b7cc
author: mikejo5000
ms.author: mikejo
manager: jmartens
ms.workload:
- multiple
ms.openlocfilehash: 4da2bb7dc41d06e113e0bd278ef08917771cfb2e
ms.sourcegitcommit: 4b323a8a8bfd1a1a9e84f4b4ca88fa8da690f656
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 03/05/2021
ms.locfileid: "102161913"
---
# <a name="idiasymbolget_rank"></a>IDiaSymbol::get_rank
Récupère le rang (nombre de dimensions) d’un tableau multidimensionnel FORTRAN.
## <a name="syntax"></a>Syntaxe
```C++
HRESULT get_rank (
DWORD* pRetVal
);
```
#### <a name="parameters"></a>Paramètres
`pRetVal`
à Retourne le nombre de dimensions dans un tableau multidimensionnel FORTRAN.
## <a name="return-value"></a>Valeur renvoyée
En cas de réussite, retourne `S_OK` ; sinon, retourne `S_FALSE` ou un code d’erreur.
> [!NOTE]
> Une valeur de retour `S_FALSE` signifie que la propriété n’est pas disponible pour le symbole.
## <a name="remarks"></a>Notes
Rank fait référence au nombre de dimensions dans un tableau où le tableau est déclaré `myarray[1,2,3]` . Cet exemple a un rang de 3 et 3 dimensions. Rank ne s’applique pas à C++ qui utilise le concept d’un tableau de tableaux pour chaque dimension (autrement dit, `myarray[1][2][3]` ).
## <a name="see-also"></a>Voir aussi
- [IDiaSymbol](../../debugger/debug-interface-access/idiasymbol.md)
| 32.48 | 286 | 0.753695 | fra_Latn | 0.648016 |
a10978998b82df797a55606481492e2e86e3d24d | 5,042 | md | Markdown | blog/2010-07-13-Node-introduction.md | Yoda-Canada/tengzhen-docusaurus-sample | 93a76408282d4606df4b81e633c9053c5a8de507 | [
"MIT"
] | null | null | null | blog/2010-07-13-Node-introduction.md | Yoda-Canada/tengzhen-docusaurus-sample | 93a76408282d4606df4b81e633c9053c5a8de507 | [
"MIT"
] | null | null | null | blog/2010-07-13-Node-introduction.md | Yoda-Canada/tengzhen-docusaurus-sample | 93a76408282d4606df4b81e633c9053c5a8de507 | [
"MIT"
] | null | null | null | ---
slug: Node-introduction-post
title: Node.js is the New Black
authors: Louis
tags: [Node]
---
If you’ve been paying attention to news about web technology in the last year, you’ve most likely heard the name node.js mentioned at least once or twice. What happened next probably went like this: you asked, “What is it?” and someone (or Google) told you that it was a way to write web servers using JavaScript. If that didn’t scare you away, you might then have asked, “Why would you want to use it?” and the answer might have been along the lines of it taking advantage of non-blocking, event-driven IO to enable high concurrency in long polling or comet-based applications.
At which point you stopped asking questions. I don’t blame you. To help break apart that wall of jargon, here’s my attempt at explaining what node.js is and why you should be paying attention to it.
So here’s how it is, how it’s always been: a browser sends a request to a website. The site’s server receives the request, tracks down the requested file, performs any database queries as needed, and sends a response to the browser. In traditional web servers, such as Apache, each request causes the server to create a new system process to handle that request.
Then there was Ajax. Instead of requesting a whole new page each time, we’d only request the piece of information we actually wanted. Okay, that’s an improvement.
But now think about how you’d go about building a service like FriendFeed, where each user’s feed is updating in real time, all the time. The only way that’s possible is if each user has an active connection to the server at all times. The simplest way to do that at present is through long polling.
Long polling essentially tricks HTTP into acting like a persistent connection: as soon as the page loads, it fires off an Ajax request to the server, even if the page doesn’t want anything in particular. But, unlike a normal Ajax request, the server doesn’t respond right away. It just waits, and fires back a response only when it has something new it wants the browser to display. For example, as soon as one of your friends adds a new post, the server returns the response telling the browser to update its display. As soon as the browser receives the response, it shoots back another request. This way the browser is always waiting for a new event to happen on the server side.
Now think about what that means for a traditional web server like Apache. For each and every user connected to the site, your server has to keep a connection open. Each connection requires a process, and each of those processes will spend most of its time either sitting idle (consuming memory) or waiting on a database query to complete. This means that it’s hard to scale up to high numbers of connections without grinding to a near halt and using up all your resources.
So what’s the solution? Here’s where some of that jargon from before comes into play: specifically non-blocking and event-driven. What those terms mean in this context is less complicated than you might fear. Think of a non-blocking server as a loop: it just keeps going round and round. A request comes in, the loop grabs it, passes it along to some other process (like a database query), sets up a callback, and keeps going round, ready for the next request. It doesn’t just sit there, waiting for the database to come back with the requested info.
If the database query comes back — fine, we’ll deal with that the same way: throw a response back to the client and keep looping around. There’s theoretically no limit on how many database queries you can be waiting on, or how many clients have open requests, because you’re not spending any time waiting for them. You deal with them all in their own time, and that’s what event-driven means: the server only reacts when an event occurs. That could be a request, a file being loaded, or a query being executed — it really doesn’t matter.
FriendFeed uses a non-blocking framework written in Python, called Tornado, to do this. The nginx web server also behaves in this way. Node.js, however, has an ace up its sleeve: because it’s using JavaScript — running on Google’s crazy-fast V8 engine — it never needs to worry about whether a request it makes to another piece of code might cause the loop to block up. The reason is that JavaScript is intrinsically event-driven. Think about it: when you write JavaScript for the browser, you’re just attaching event handlers and callbacks. That’s the way the language was designed.
Node.js is still in its infancy, so if you want to write an application based on it you’ll need to do some fairly low-level coding. But with the impending arrival of WebSockets in next-generation browsers (eliminating the need for long polling altogether), this type of technology will only become more important on the Web. I hope I’ve given you the incentive to start messing around and getting your head around these concepts.
Translation：https://www.zhihu.com/question/33578075/answer/56951771
| 148.294118 | 681 | 0.788179 | eng_Latn | 0.999887 |
a10a7b19280e33132368320138cd2ea9fb511b44 | 117 | md | Markdown | README.md | EranCohenSW/Shift | 10e7f9f1996ee42998960856fd3bc48233943a6f | [
"MIT"
] | 1 | 2021-02-20T17:09:33.000Z | 2021-02-20T17:09:33.000Z | README.md | EranCohenSW/Shift | 10e7f9f1996ee42998960856fd3bc48233943a6f | [
"MIT"
] | null | null | null | README.md | EranCohenSW/Shift | 10e7f9f1996ee42998960856fd3bc48233943a6f | [
"MIT"
] | null | null | null | # Shift
Chrome extension which lets you swap an input you were typed instantly from english to hebrew and vice versa
| 39 | 108 | 0.811966 | eng_Latn | 1.000002 |
a10b06455c0b7547f852653cfd0ad5d7db98e705 | 27,023 | md | Markdown | README.md | zhajianl/Edge-Software-Provisioner | 4ed547f1b13b34c449a13ac4d6db95397033ee8a | [
"MIT",
"BSD-3-Clause"
] | 16 | 2021-02-09T18:41:12.000Z | 2022-03-17T18:51:48.000Z | README.md | zhajianl/Edge-Software-Provisioner | 4ed547f1b13b34c449a13ac4d6db95397033ee8a | [
"MIT",
"BSD-3-Clause"
] | 21 | 2021-05-03T14:21:54.000Z | 2022-03-31T15:40:47.000Z | README.md | zhajianl/Edge-Software-Provisioner | 4ed547f1b13b34c449a13ac4d6db95397033ee8a | [
"MIT",
"BSD-3-Clause"
] | 16 | 2021-01-04T10:37:41.000Z | 2022-03-01T19:34:16.000Z | # Edge Software Provisioner (ESP)
## Quick Start Guide
To quickly get started follow the [Quick Installation Guide](#quick-installation-guide)
## Table of Contents
1. [What is it?](#what-is-it)
1. [Why do I want it?](#why-do-i-want-it)
1. [Why is it different?](#why-is-it-different)
1. [Introduction](#introduction)
1. [Prerequisites](#prerequisites)
1. [Setting up your Network](#network-setup)
1. [Quick Installation Guide](#quick-installation-guide)
1. [Installing the Edge Software Provisioner (ESP)](#installing-esp)
1. [Upgrading the Edge Software Provisioner (ESP)](#upgrading-esp)
1. [Building Target Devices](#building-target-devices)
1. [Adding and Removing Profiles](#adding-removing-profiles)
1. [Profile Management](#profile-management)
1. [Virtual PXE](#virtual-pxe)
1. [Bootable USB](#bootable-usb)
## What is it?
The Edge Software Provisioner (ESP) enables ODMs, System Integrators and Developers to automate the installation of a complete operating system and software stack (defined by a Profile) on bare-metal or virtual machines using a "Just-in-Time" provisiong process. The software stack can include software components, middleware, firmware, and applications. Automating this process increases velocity by focusing resources on rapid development, validation of use cases and scalable deployment. ESP simplifies customer adoption through confidence gained validating Profiles. Profiles are cloned and distributed through GitHub containing the human readable prescriptive literature to deploy the complete operating system and software stack. In summary, this a scalable, simple bare metal provisioning process including virtual machine provisioning.
## Why do I want it?
* This tool potentially can save a team of 30 developers 12,300 man hours that would have been spent on deployment per year.
* This tool potentially can save a system integrator 11,750 man hours in the installation of OS and software stack deploying on 5,000 devices.
## Why is it different?
A majority of ODMs and SI's use the "golden" image method; by building a complete system by hand and then copying the hard drive contents into a "golden" image. The problem with this process is golden images are not always easily transferrable from hardware to hardware. Additionally, after a period of time that golden image falls behind from CVE patches causing the ODM or SI to perform additional steps of installation before shipping. Golden images are large (measured in gigabytes) and require a lot of disk farm to store.
Edge Software Provisioner is a "Just-in-Time" provisioning process; at the time of installation it builds and installs all the components on the target device with the latest and/or fixed release of the software components. When the ESP OS boots on the target device it "discovers" the hardware and makes adjustments to the installation process through Profile. Profiles are small (measured in kilobytes) and pulled via a URL.
## Introduction
The Edge Software Provisioner (ESP) is a collection of scripts that enables network-wide [PXE](https://en.wikipedia.org/wiki/Preboot_Execution_Environment) or USB booting of customizable operating systems, referred to as "profiles". It has a lightweight footprint, requiring only Bash, Docker, and Docker Compose. Profiles can be any Linux distribution, such as Clear Linux, Ubuntu, Red Hat, Suse, Yocto, Arch Linux, RancherOS.
The main executable to setup a device as a Edge Software Provisioner is `build.sh`. This script will automatically build a few Docker images, download necessary files as required by profiles, prepare the PXE boot menu, and launch the following dockerized services:
- **dnsmasq** (provides DHCP and TFTP services)
- **nginx**
- **squid** - optional, used for caching http requests
- **registry** - optional, used for caching Docker images
- **Gitea** - optional, used for mirroring git repositories
[Clear Linux](https://github.com/intel/rni-profile-base-clearlinux), [Ubuntu](https://github.com/intel/rni-profile-base-ubuntu) and [RancherOS](https://github.com/intel/rni-profile-base-rancheros) are provided as example profiles.
## Prerequisites
The following is required:
* **Profile** - The git URL for at least one profile is required. You will be asked to paste the URL into the configuration file in the following instructions. [Clear Linux](https://github.com/intel/rni-profile-base-clearlinux), [Ubuntu](https://github.com/intel/rni-profile-base-ubuntu) and [RancherOS](https://github.com/intel/rni-profile-base-rancheros) are provided as example profiles. **See [Adding and Removing Profiles](#adding-removing-profiles) to update the profile list**
* **Edge Software Provisioner** - Minimum Recommended Hardware or VM with 2 CPUs, 20GB HD and 2GB of RAM, running any Linux Distro (headless recommended) that supports Docker
* `docker` 18.09.3 or greater
* `docker-compose` v1.23.2 or greater (follow Step 2. of [Quick Installation Guide](#quick-installation-guide) to install) ([official docker-compose guide](https://docs.docker.com/compose/install/))
* `bash` v4.3.48 or greater
* **Target Device(s)** - Bare-Metal or Virtual Machine(s) with the necessary specifications for your use case. The profile defines what will we be installed and detects hardware on the Target Device. _Note: The Target Devices will be wiped clean during typical usage of the Edge Software Provisioner._
## Network Setup
The Edge Software Provisioner (ESP) must be in an isolated network and there must only be one ESP in the network. ESP will detect if there is an existing DHCP or DNS and will configure itself accordingly. It will also detect if the host has a static or dynamic IP IPv4 address. If the host is a dynamic IP address and if the IP address changes you must run `./build.sh -S -P && ./run.sh --restart` to update ESP configuration with the new IP address.
WARNING: DO NOT RUN ESP ON YOUR CORPORATE NETWORK. *It must be on an isoloated network.*
NOTE: If using Ubuntu, do not use Snapd Docker, install Docker using aptitude. Dnsmasq must not been running on the system from some other service. Please confirm with `ps -auxww | grep dnsmasq`.
NOTE: When testing with virtual machines, their LAN adapters should be put in Bridge Mode or the VMs must be within the same virtual network.
The ideal setup is a router with an Internet connection and an x86 device like an Intel NUC or VM with Bridge Mode enabled on the LAN adapter.
Because ESP is OS-agnostic and Docker-based, the configuration of your system's network is not something that this guide will cover.
Target Devices will be connected on the same LAN as the Edge Software Provisioner. On target devices, enable PXE Boot in the BIOS if it is not enabled. Most BIOS's have a boot menu option (F12) at POST time. Typically you can press (F12) to alter the boot sequence.
## Quick Installation Guide
NOTE: Please read [Network Setup](#network-setup) above before proceeding. If using Ubuntu, do not use Snapd Docker, install Docker using aptitude. Dnsmasq must not been running on the system from some other service. Please confirm with `ps -auxww | grep dnsmasq`.
This guide will help build and run the Edge Software Provisioner docker images. Depending on the compute power, it will take roughly 5 to 10 minutes to build the images. To avoid building images every time you install, it suggested to build the images and then publish the images to a container registy. Following this guide will give you some example steps and tooling to help push the images up to a registry.
1. ALL the following commands must run as ROOT. Type `sudo su -` and the your password before proceeding. (DO NOT prepend sudo to every command. `sudo su -` means load root environment versus sudo prepended uses your user's environment to the run commands.)
```bash
sudo su -
```
2. Install Docker Compose
```bash
mkdir -p /usr/local/bin
wget -O /usr/local/bin/docker-compose "https://github.com/docker/compose/releases/download/1.25.4/docker-compose-$(uname -s)-$(uname -m)"
chmod a+x /usr/local/bin/docker-compose
```
3. Clone this project to /opt/esp
```bash
cd /opt
git clone -b master --depth=1 https://github.com/intel/Edge-Software-Provisioner.git esp
cd esp
```
4. Build the ESP services. This will take about 5 to 10 minutes.
```bash
./build.sh
```
5. Start the ESP services.
```bash
./run.sh
```
6. Attach to the target system or VM to the same network as ESP. Turn it on and make sure PXE is enabled in the BIOS or press F12 or F11 at boot to boot from network. You will see the following screen.
7. The default login username is `sys-admin` and the default password is `P@ssw0rd!`. This password is defined in the `conf/config.yml` as a kernel argument in the profiles. See the individual profiles for further instructions.
**Stop rebuilding ESP for each installation! To improve installation efficiency for the next time continue on**
8. Let's re-tag docker images with your prefix to upload to your Docker Hub account. The following example will re-tag images to look like `myDockerUser/builder-core:latest`.
```bash
./build.sh --tag myDockerHubUser
```
9. Now let's push these images to your registry. Make sure to run `docker login` first.
```bash
./build.sh --push myDockerHubUser
```
10. Copy the output/docker-compose.yml file to your device or virtual machine you want to run Edge Sofware Provisioner. On the target device simply run the following.
```bash
docker-compose up -d
```
To simplify further, you can use the example `examples/deply.sh` script to deploy Edge Software Provisioner in a one line command like the following example command (NOTE: you must move deploy.sh and the docker-compose.yml into your github repo for the following to work):
```bash
wget -O- https://github.com/myuser/esp/raw/branch/master/deploy.sh | bash -s -
```
**See [Adding and Removing Profiles](#adding-removing-profiles) to update the profile list**
## Installing ESP
Once the prerequisites and network setup have been taken care of, the steps to deployment are as follows.
**Step 1.**
Clone the Edge Software Provisioner repository using your git protocol of choice, and navigate into the cloned directory - use the following code snippet as an example:
```bash
git clone -b master --depth=1 https://github.com/intel/Edge-Software-Provisioner.git esp
cd esp
```
**Step 2.**
Edit the existing `conf/config.yml` or copy `conf/config.sample.yml` to `conf/config.yml`:
```bash
cp conf/config.sample.yml conf/config.yml
```
The config file can look something like this - **please modify the values below, this is not intended to be a working example**:
```yaml
---
#dhcp_range_minimum: 192.168.1.100
#dhcp_range_maximum: 192.168.1.250
#network_broadcast_ip: 192.168.1.255
#network_gateway_ip: 192.168.1.1
#network_dns_primary: 8.8.4.4
#network_dns_secondary: 8.8.8.8
#Whost_ip: 192.168.1.11
profiles:
- git_remote_url: https://github.com/intel/rni-profile-base-clearlinux.git
profile_branch: legacy
profile_base_branch: None
git_username: ""
git_token: ""
name: clearlinux_profile
custom_git_arguments: --depth=1
- git_remote_url: https://github.com/intel/rni-profile-base-clearlinux.git
profile_branch: desktop
profile_base_branch: master
git_username: ""
git_token: ""
name: clearlinux-desktop_profile
custom_git_arguments: --depth=1
```
Make changes according to your needs, including your GitHub username and [token](https://help.github.com/en/enterprise/2.16/user/articles/creating-a-personal-access-token-for-the-command-line) if needed (using a password is not recommended for security reasons), with the following guidance:
* Public repositories that do not require a username and token/password **must** have the values of `git_username=""` and `git_token=""`
* Under the `profiles` section, update the git remote to match the HTTPS-based `git remote` URL for your profile. Also update git remote branch by setting `profile_branch` and if it requires any base branch then update it by setting `profile_base_branch` for your profile else set `profile_base_branch` as **None**
* Ensure that the network configuration matches your needs. If values are not specified, Edge Software Provisioner will default to a `/24` network with a DHCP range of `x.x.x.100-x.x.x.250`.
* For special situations, custom git flags can be added on the fly by setting `custom_git_arguments`. It _must_ be defined (see next bullet point), so if no custom git flags are needed, specify `None` or `""`.
* Every profile must have **all** values defined in the config. For example, you cannot remove `custom_git_arguments`; you must specify a value. This is a [known limitation](#known-limitations).
* The `name` of the profile will appear as a boot menu option on the target device's PXE menu. It can be any alphanumeric string.
**Step 3.**
Run `./build.sh` as root from the root folder. This script will perform various tasks, such as downloading files for the configured profiles in `conf/config.yml`, generating a PXE boot menu, and other things. Depending on the profiles you've selected, the build process can take a few minutes, and is hands-off.
**Step 4.**
Run `./run.sh` as root. This will start the Edge Software Provisioner services. _It is safe to press `ctrl+C` to quit out of logging safely at any time._
**Edge Software Provisioner has now been deployed successfully!** The next step is to [build a target device](#building-target-devices), which is detailed just below.
## Upgrading ESP
3. Update to the latest release
```bash
cd /opt/esp
git pull
```
4. Rebuild the ESP services. This will take about 5 to 10 minutes.
```bash
./build.sh
```
5. Stop and Retart the ESP services.
```bash
./run.sh -f
```
## Building Target Devices
**Booting Target Devices**
1. Boot the target device while connected to your LAN. Make sure you boot this device from network instead of local disk or cd-rom. This will initiate the PXE boot of your target device from the Edge Software Provisioner.
2. After installation, if the profile is in "release" mode "prod" it will shutdown. If the profile is in "release" mode "dev" the device will reboot. This is a kernel parameter set in the config.yml in a profile "release=prod" or "release=dev". Manually select the local disk boot option in the PXE menu when it comes up. If the terminal comes up without an error message and notification to check the error log, then it has built successfully!
## Example Kernel Paramaters used at build time
The following kernel parameters can be added to `conf/config.yml`
* `bootstrap` - RESERVED, do not change
* `ubuntuversion` - Use the Ubuntu release name. Defaults to 'cosmic' release
* `debug` - [TRUE | FALSE] Enables a more verbose output
* `httppath` - RESERVED, do not change
* `kernparam` - Used to pass additional kernel parameters to the targeted system. Example format: kernparam=splash:quiet#enable_gvt:1
* `parttype` - RESERVED, do not change
* `password` - Initial user password. Defaults to 'P@ssw0rd!'
* `proxy` - Add proxy settings if behind proxy during installation. Example: http://proxy.intel.com:800
* `proxysocks` - Add socks proxy settings if behind proxy during installation. Example: http://proxy.intel.com:1080
* `release` - [prod | dev] If set to prod the system will shutdown after it is provisioned. Altnerativily it will reboot
* `token` - GitHub token for private repositories, if this profile is in a private respository this token should have access to this repo
* `username` - Initial user name. Defaults to 'sys-admin'
* `network` - By default this installs a basic network if omitted. Valid options are `bridged` which enables a bonded bridged networks accross all network devices or `network-manager` which gives management to the Network Manager utility.
* `wpassid` - uOS WPA SSID if no ethernet is found
* `wpapsk` - uOS WPA Pre-Shared Key if no ethernet is found
* `wifissid` - Target system WiFi SSID
* `wifipsk` - Target system WiFi Pre-Shared Key
**NOTE: See profile for specific Kernel Parameters**
## Post-deployment Information
**Flags**
Users can get a list of all flags supported by running `./build.sh -h`
**Troubleshooting the Edge Software Provisioner**
Log information is available in `builder.log` in the root folder. In order to monitor the logs you can run `docker-compose logs -f`
If it becomes necessary to delete the Edge Software Provisioner containers and re-create them, run `./run.sh -f` (assuming there are no target devices in your network that are attempting to boot while running this command).
You can use `./run.sh -r` to restart the Edge Software Provisioner containers.
Edge Software Provisioner (ESP) will automatically restart upon system reboot. To stop ESP, from within the "esp" folder type `docker-compose down`
For any other problems that you may encounter during deployment, please consult the [Known Limitations](#known-limitations) section.
## Adding Removing Profiles
You can add and remove profiles by editing the file `conf/config.yml` from with the Edge Software Provisioner directory. After making changes to the `conf/config.yml` you will need to update the location cache. You would type `./build.sh -S` or `./build.sh -S --profile NAME_OF_PROFILE` to rebuild the local cache. Use the `./build.sh -h` to see list of switches available.
## Profile Management
This section is not required for setting up an Edge Software Provisioner and building target devices, but it provides valuable information about profiles, templating, and file downloads that will help you build your own profiles.
Example profiles: [Clear Linux](https://github.com/intel/rni-profile-base-clearlinux), [Ubuntu](https://github.com/intel/rni-profile-base-ubuntu) and [RancherOS](https://github.com/intel/rni-profile-base-rancheros)
In profiles there are 2 files called `conf/config.yml` and `conf/files.yml`.
* `conf/config.yml` holds the kernel arguments which are passed to the Profile installation process that set things like operating system username and password.
**Kernel arguments** can be specified in a file called `conf/config.yml` _in the profile's repository_, **not in Edge Software Provisioner itself**, like this:
```yaml
---
kernel_arguments: diskencrypt=false release=prod ubuntuversion=bionic arch=amd64 username=admin password=password example.datasources=[url:http://@@HOST_IP@@/profile/@@PROFILE_NAME@@/dyn-ks.yml]
```
Variables surrounded by `@@` symbols are handled by the templating engine in Edge Software Provisioner. Please read [Templating](#templating) for more information on this topic.
* `conf/files.yml` A profile will likely require external files in order to boot and install. This is solved by specifying them in `conf/files.yml` _inside the profile repository_, **not in Edge Software Provisioner itself**. For an example, please see the `files.yml.sample` in the [Ubuntu](https://github.com/intel/rni-profile-base-ubuntu) profile.. See options `conf/files.yml.sample` in any profile (not included in this repo).
You can pull general files, files from S3, or pull container images etc. The follwoing are some additional examples.
### Using ISO Download and Mounting
In your profile modify `conf/files.yml`. Look for section `general_files` or `s3_files` add the `mount_iso_path:` section to mount the iso. See options `conf/files.yml.sample` in any profile (not included in this repo).
The following ISO would be accessible via: http://{ESP_IP_Address}/files/{PROFILE_NAME}/alpine-standard-3.11.5-x86_64/
```yaml
general_files:
- url: http://dl-cdn.alpinelinux.org/alpine/v3.11/releases/x86_64/alpine-standard-3.11.5-x86_64.iso
destination_file: alpine-standard-3.11.5-x86_64.iso
token: None
mount_iso_path: alpine-standard-3.11.5-x86_64
```
### GIT Repo mirroring Example
Git repo mirroring and caching
In your profile modify `conf/files.yml`. Add as section called `git_repos:` see example below. See options `conf/files.yml.sample` in any profile (not included in this repo).
The following Git Repo would be accessible via: http://mirror:mirror@{ESP_IP}:3003/mirror/{PROFILE_NAME}___rwo/raw/branch/master/*
```yaml
git_repos:
- git_url: https://github.com/intel/RetailWorkloadOrchestrator.git
git_branch: master
git_username:
git_passowrd_or_token:
custom_git_arguments: --depth=1
mirror_repo_name: rwo
```
### Build Process
The "Build Process" will perform any scripted action, for example you could build a linux kernel and stage it on Edge Software Provisioner.
In your profile modify `conf/files.yml`. Add as section called `build:` see example below. See options `conf/files.yml.sample` in any profile (not included in this repo).
The following Git Repo would be accessible via: http://{ESP_IP}/files/{PROFILE_NAME}/build/*
```yaml
build:
- container: alpine:3.12
entrypoint: ""
cmd: sh -c
execute: start.sh
```
### Legacy ISO Booting
The "Build Process" will perform any scripted action, for example you could build a linux kernel and stage it on Edge Software Provisioner.
In your profile modify `conf/files.yml`. Add as section called `base_os_files:` see example below. See options `conf/files.yml.sample` in any profile (not included in this repo).
```yaml
base_os_files:
- url: https://releases.ubuntu.com/20.04.2/ubuntu-20.04.2-live-server-amd64.iso
type: iso
filename: ubuntu-20.04.2-live-server-amd64.iso
```
### Templating
Edge Software Provisioner has a few essential templating capabilies that assist with profile configuration.
In a profile's `conf/config.yml`, for the `kernel_arguments` variable only, the following template variables are supported:
* `@@DHCP_MIN@@` - `dhcp_range_minimum`
* `@@DHCP_MAX@@` - `dhcp_range_maximum`
* `@@NETWORK_BROADCAST_IP@@` - `network_broadcast_ip`
* `@@NETWORK_GATEWAY_IP@@` - `network_gateway_ip`
* `@@HOST_IP@@` - `host_ip`
* `@@NETWORK_DNS_PRIMARY@@` - `network_dns_primary`
* `@@NETWORK_DNS_SECONDARY@@` - `network_dns_secondary`
Any file with the suffix `.esptemplate` in a profile will support all of the above as well as:
* `@@PROFILE_NAME@@`
### Profile Build Scripts
A profile can contain a `build.sh` script (must have executable flags set) that will be executed locally on the builder host before anything else. Templating is also supported, so `build.sh.buildertemplate` files will be processed (as described in the [Templating](#templating) section) and then executed on the builder host itself.
These `build.sh` scripts can be useful for any sort of pre-processing task. One use case might be to download a `.tar.gz` file that contains and `initrd` and `linux` kernel files, extract them, and then host them locally so that the builder host can process them.
### File Downloads and Dependencies
A profile will likely require external files in order to boot and install. This is solved by specifying them in `conf/files.yml` _inside the profile repository_, **not in Edge Software Provisioner itself**. For an example, please see the `files.yml.sample` in the Rancher profile.
### Custom Profiles
* A custom profile can be developed and used with existing base profiles.
* Base profile will have core logic of installing OS. Please see `pre.sh` script in ClearLinux profile on `base` branch.
* Base profile will also `post.sh` script for clean up activities. Please see `post.sh` script in ClearLinux profile on `base` branch.
* Custom profile can have `profile.sh` to support custom features. Please see `profile.sh` script in ClearLinux profile on `rwo` branch.
* Finally custom profile will have `bootstrap.sh` which will eventually call `pre.sh` from *base* branch, `profile.sh` from *custom* branch and then call `post.sh` from *base* branch again. Please see `bootstrap.sh` script in ClearLinux profile on `rwo` branch.
* To see more details on how to change Edgebuilder configuration to use custom profile, see *step 2*
under [Installation](#installation)
## Virtual PXE
#### What is it?:
It allows you to test your profiles and/or build VMs or VMs in a container inline on Edge Software Provisioner without having to boot another machine.
#### Give it try:
Perform your regular steps of installing Edge Software Provisioner, configure your profiles, run `./buils.sh` and `./run.sh`.
To start Viturl PXE run the following in the same directory:
```bash
./vpxe.sh
```
Type `./vpxe.sh -h` to see othe syntax options.
#### If using pre-built container images version of ESP, use the following command to start vpxe.sh
```bash
docker exec -it esp_core_1 vpxe.sh
```
## Bootable USB
#### What is it?:
Creates bootable USB images to boot target devices without Ethernet or PXE available. Or simply use it to a boot a system outside the network.
#### Give it try:
Perform your regular steps of installing Edge Software Provisioner, configure your profiles, run `./buils.sh` and `./run.sh`.
To start Make USB run the following in the same directory:
```bash
./makeusb.sh
```
Type `./makeusb.sh -h` to see othe syntax options.
## Known Limitations
* The `conf/config.yml` file must specify ALL values comprehensively, as shown in the `conf/config.sample.yml`. Please use `""` for empty values.
* IPv6 is not supported.
* Edge Software Provisioner must be run on a Linux-native file system, such as `ext4`. Filesystems that cannot properly preserve file permissions are not supported.
* On some distributions of Linux (such as newer versions of Ubuntu 18.04), `systemd-resolved` is already running a DNS server on `localhost`. This will cause the dnsmasq container (which is required) to fail to start due to port binding conflicts. To fix this:
* Run `./build.sh` normally. It will fail at the final deployment step.
* Edit `/etc/systemd/resolved.conf` to include the line `DNSStubListener=no`
* **This step will cause your network connection to drop.** Run `sudo systemctl daemon-reload && sudo systemctl restart systemd-resolved.service`
* Run `./run.sh` to restart the Edge Software Provisioner services.
* Test that network connectivity works.
* Proceed to deploy your target devices.
* Edge Software Provisioner's usage of `aws-cli` can cause keyring issues on desktop versions of Linux. Consider disabling your distro's keyring service, or alternatively, a headless distribution such as Ubuntu server edition will resolve the issue.
## Other Info
You can build behind a proxy like this:
```bash
export HTTP_PROXY=http://proxy.site.com:1234 && \
export HTTPS_PROXY=http://proxy.site.com:1234 && \
./build.sh
```
| 54.813387 | 847 | 0.754283 | eng_Latn | 0.985414 |
a10b28f323df60974eee2c872d6c62bf9473b1c8 | 1,825 | md | Markdown | _posts/press/2018-03-07-Ionic liquid gating control.md | mliuteam/mliuteam.github.io | 01269032972f022669345783bf4016f31268c7eb | [
"MIT"
] | null | null | null | _posts/press/2018-03-07-Ionic liquid gating control.md | mliuteam/mliuteam.github.io | 01269032972f022669345783bf4016f31268c7eb | [
"MIT"
] | null | null | null | _posts/press/2018-03-07-Ionic liquid gating control.md | mliuteam/mliuteam.github.io | 01269032972f022669345783bf4016f31268c7eb | [
"MIT"
] | null | null | null | ---
layout: page-fullwidth
subheadline: "Nature Communication"
title: "Ionic liquid gating control of RKKY interaction in FeCoB/Ru/FeCoB and (Pt/Co)2/Ru/(Co/Pt)2 multilayers"
teaser: " Author Qu Yang"
categories:
- press
tags:
- press
header: no
show_meta: false
---
<!--more-->
<!--<div class="row">-->
<div >
<p>
Q. Yang, L. Wang, Z. Zhou*, S. Zhao, G. Dong, Y. Chen, T. Min, M. Liu*, Ionic liquid gating control of RKKY interaction in FeCoB/Ru/FeCoB and (Pt/Co)2/Ru/(Co/Pt)2 multilayers， Nature Communication，9, 991 (2018)</p>
<a href="https://www.nature.com/articles/s41467-018-03356-z">Full text</a>
</div>
<div style="display: inline-block;">
<h2>Abstract</h2>
<p>To overcome the fundamental challenge of the weak natural response of antiferromagnetic materials under a magnetic field, voltage manipulation of antiferromagnetic interaction is developed to realize ultrafast, high-density, and power efficient antiferromagnetic spintronics. Here, we report a low voltage modulation of Ruderman–Kittel–Kasuya–Yosida (RKKY) interaction via ionic liquid gating in synthetic antiferromagnetic multilayers of FeCoB/Ru/FeCoB and (Pt/Co)2/Ru/(Co/Pt)2. At room temperature, the distinct voltage control of transition between antiferromagnetic and ferromagnetic ordering is realized and up to 80% of perpendicular magnetic moments manage to switch with a small-applied voltage bias of 2.5 V. We related this ionic liquid gating-induced RKKY interaction modification to the disturbance of itinerant electrons inside synthetic antiferromagnetic heterostructure and the corresponding change of its Fermi level. Voltage tuning of RKKY interaction may enable the next generation of switchable spintronics between antiferromagnetic and ferromagnetic modes with both fundamental and practical perspectives.</p>
</div>
| 62.931034 | 1,132 | 0.777534 | eng_Latn | 0.937607 |
a10b45fe6a4185aa2b3a41d281ac4e87e70d6e32 | 172 | md | Markdown | 10-riscv/00-background/02-mylib/README.md | al2698/sp | fceabadef49ffe6ed25dfef38e3dc418f309e128 | [
"MIT"
] | null | null | null | 10-riscv/00-background/02-mylib/README.md | al2698/sp | fceabadef49ffe6ed25dfef38e3dc418f309e128 | [
"MIT"
] | null | null | null | 10-riscv/00-background/02-mylib/README.md | al2698/sp | fceabadef49ffe6ed25dfef38e3dc418f309e128 | [
"MIT"
] | null | null | null | ```
PS D:\pmedia\陳鍾誠\課程\系統程式\10-riscv\00-background\02-mylib> make
gcc hello.c mylib.c -o hello
PS D:\pmedia\陳鍾誠\課程\系統程式\10-riscv\00-background\02-mylib> ./hello
Hello!
``` | 28.666667 | 65 | 0.715116 | kor_Hang | 0.184775 |
a10b6cb06a894322a62de23c76d0e931e9a7bfac | 7,268 | md | Markdown | files/en-us/web/css/clamp()/index.md | liannemarie/content | 6d614dad93f3e0dfd6acd58a44fd0b35a0b0ba6c | [
"OML",
"CECILL-B",
"RSA-MD"
] | null | null | null | files/en-us/web/css/clamp()/index.md | liannemarie/content | 6d614dad93f3e0dfd6acd58a44fd0b35a0b0ba6c | [
"OML",
"CECILL-B",
"RSA-MD"
] | null | null | null | files/en-us/web/css/clamp()/index.md | liannemarie/content | 6d614dad93f3e0dfd6acd58a44fd0b35a0b0ba6c | [
"OML",
"CECILL-B",
"RSA-MD"
] | null | null | null | ---
title: clamp()
slug: Web/CSS/clamp()
tags:
- CSS
- CSS Function
- Calculate
- Compute
- Function
- Layout
- Reference
- Web
- clamp
browser-compat: css.types.clamp
---
{{CSSRef}}
The **`clamp()`** [CSS](/en-US/docs/Web/CSS) [function](/en-US/docs/Web/CSS/CSS_Functions) clamps a value between an upper and lower bound. `clamp()` enables selecting a middle value within a range of values between a defined minimum and maximum. It takes three parameters: a minimum value, a preferred value, and a maximum allowed value. The `clamp()` function can be used anywhere a {{CSSxRef("<length>")}}, {{CSSxRef("<frequency>")}}, {{CSSxRef("<angle>")}}, {{CSSxRef("<time>")}}, {{CSSxRef("<percentage>")}}, {{CSSxRef("<number>")}}, or {{CSSxRef("<integer>")}} is allowed.
`clamp(MIN, VAL, MAX)` is resolved as `{{CSSxRef("max()")}}(MIN, {{CSSxRef("min()")}}(VAL, MAX))`
{{EmbedInteractiveExample("pages/css/function-clamp.html")}}
Note that using `clamp()` for font sizes, as in these examples, allows you to set a font-size that grows with the size of the viewport, but doesn't go below a minimum font-size or above a maximum font-size. It has the same effect as the code in [Fluid Typography](https://css-tricks.com/snippets/css/fluid-typography/) but in one line, and without the use of media queries.
## Syntax
The `clamp()` function takes three comma separated expressions as its parameter, in the order of minimum value, preferred value, maximum value.
The minimum value is the smallest (most negative) value. This is the lower bound in the range of allowed values. If the preferred value is less than this value, the minimum value will be used.
The preferred value is the expression whose value will be used as long as the result is between the minimum and maximum values.
The maximum value is the largest (most positive) expression value to which the value of the property will be assigned if the preferred value is greater than this upper bound.
The expressions can be math functions (see {{CSSxRef("calc()")}} for more information), literal values, or other expressions, such as {{CSSxRef("attr()")}}, that evaluate to a valid argument type (like {{CSSxRef("<length>")}}), or nested {{CSSxRef("min()")}} and {{CSSxRef("max()")}} functions. As math expressions, so you can use addition, subtraction, multiplication and division without using the `calc()` function itself. You may also use parentheses to establish computation order when needed.
You can use different units for each value in your expressions, and different units in any math function making up any of the arguments.
### Notes
- Math expressions involving percentages for widths and heights on table columns, table column groups, table rows, table row groups, and table cells in both auto and fixed layout tables _may_ be treated as if `auto` had been specified.
- It is permitted to nest `max()` and `min()` functions as expression values, in which case the inner ones are treated as simple parentheses. The expressions are full math expressions, so you can use direct addition, subtraction, multiplication and division without using the calc() function itself.
- The expression can be values combining the addition ( + ), subtraction ( - ), multiplication ( \* ) and division ( / ) operators, using standard operator precedence rules. Make sure to put a space on each side of the + and - operands. The operands in the expression may be any {{CSSxRef("<length>")}} syntax value. You can use different units for each value in your expression. You may also use parentheses to establish computation order when needed.
- Oftentimes you will want to use {{CSSxRef("min()")}} and {{CSSxRef("max()")}} within a `clamp()` function.
### Formal syntax
{{CSSSyntax}}
## Examples
### min, max, and clamp comparison
In this example we have a simple responsive example that makes use of {{CSSxRef("min()")}}, {{CSSxRef("max()")}}, and {{CSSxRef("clamp()")}} for some of the sizes.
The [`<body>`](/en-US/docs/Web/HTML/Element/body) element's [`width`](/en-US/docs/Web/CSS/width) is set as `min(1000px, calc(70% + 100px))`. This means that the width will be set at `1000px`, unless the result of `calc(70% + 100px)` is less than `1000px`, in which case it will be set to that value instead. `min()` allows you set a maximum value.
The [`<p>`](/en-US/docs/Web/HTML/Element/p) element's [`font-size`](/en-US/docs/Web/CSS/font-size) is set as `max(1.2rem, 1.2vw)`. This means that the `font-size` will be set at `1.2rem`, unless the computed value of `1.2vw` is greater than that of `1.2rem`, in which case it will be set to that value instead. `max()` allows you set a minimum value, which in cases like this is useful for accessibility purposes.
The [`<h1>`](/en-US/docs/Web/HTML/Element/Heading_Elements) element's `font-size` is set as `clamp(1.8rem, 2.5vw, 2.8rem)`. This means that the `font-size` will be set at `1.8rem`, until the computed value of `2.5vw` becomes greater than that of `1.8rem`. At this point, `font-size` will be set at `2.5vw`, until `2.5vw`'s computed value becomes greater than that of `2.8rem`. At this point, the `font-size` will be set at `2.8rem`. `clamp()` allows you to set a minimum and maximum value.
You find this [example live on GitHub](https://mdn.github.io/css-examples/min-max-clamp/), if you want to play around with it.
#### HTML
```html
<h1>Simple responsive test</h1>
<p> Lorem ipsum dolor sit amet, consectetur adipiscing elit. In orci orci, eleifend id risus nec, mattis rutrum velit. Suspendisse fringilla egestas erat eu convallis. Phasellus eu velit ut magna dapibus elementum cursus at ligula. Ut tempus varius nibh, nec auctor sapien iaculis sit amet. Fusce iaculis, libero quis elementum viverra, nulla ante accumsan lectus, sit amet convallis lacus ipsum vel est. Curabitur et urna non est consectetur pulvinar vel id risus. Ut vestibulum, sem in semper aliquet, felis arcu euismod sapien, ac imperdiet massa nisl quis sem. Vestibulum ac elementum felis, in tempor velit. Pellentesque purus ex, mattis at ornare quis, porta condimentum mi. Donec vestibulum ligula vel nulla blandit, quis euismod nulla vestibulum. Suspendisse potenti. Nunc neque mauris, tempor sed facilisis at, ultrices eget nulla. Pellentesque convallis ante nec augue porttitor, id tempus ante luctus.</p>
<p>Integer rutrum sollicitudin tellus, quis cursus nulla scelerisque nec. Nunc eu facilisis lorem. Maecenas faucibus sapien eleifend, semper tellus at, pharetra quam. Cras feugiat vulputate tortor at rhoncus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nam non felis quis sem lobortis sodales vel id libero. Phasellus sit amet placerat lorem. </p>
```
#### CSS
```css
html {
font-family: sans-serif;
}
body {
margin: 0 auto;
width: min(1000px, calc(70% + 100px));
}
h1 {
letter-spacing: 2px;
font-size: clamp(1.8rem, 2.5vw, 2.8rem);
}
p {
line-height: 1.5;
font-size: max(1.2rem, 1.2vw);
}
```
## Specifications
{{Specifications}}
## Browser compatibility
{{Compat}}
## See also
- {{CSSxRef("calc()")}}
- {{CSSxRef("max()")}}
- {{CSSxRef("min()")}}
- [CSS Values](/en-US/docs/Learn/CSS/Building_blocks/Values_and_units)
| 65.477477 | 916 | 0.731838 | eng_Latn | 0.979217 |
a10be2cf4c84c71fb029c33bfd0971ca85ddf8ff | 964 | md | Markdown | commands.md | SanjayPJ/Udacity-Version-Control-with-Git | f61b518247dfae456ac366b281064f986eb36662 | [
"BSD-2-Clause"
] | 2 | 2020-01-14T15:24:44.000Z | 2020-05-04T12:56:38.000Z | commands.md | SanjayPJ/Udacity-Version-Control-with-Git | f61b518247dfae456ac366b281064f986eb36662 | [
"BSD-2-Clause"
] | null | null | null | commands.md | SanjayPJ/Udacity-Version-Control-with-Git | f61b518247dfae456ac366b281064f986eb36662 | [
"BSD-2-Clause"
] | 1 | 2020-07-28T18:04:23.000Z | 2020-07-28T18:04:23.000Z | # Command Reference
## First time Git Setup
- Setup user name and email in the ~/.gitconfig
`git config --global user.name "wccalvin"`
`git config --global user.email clayton.calvin@gmail.com`
- If a default text editor should be setup when Git needs you to type in a message
`git config --global core.editor emacs` [default: vim]
## To pull an existing repository to update modified changes
- Create an empty git repository or reinitialize an existing one
`git init`
- Fetch from and integrate with another repository
`git pull https://github.com/user.name/repo.git`
- Make required changes to the files.
- Add file contents to the index.
`git add <file name>`
- Record changes to the repository
`git commit -m "message"`
- Manage set of tracked repositories
`git remote show origin`
`git remote add origin https://github.com/user.name/repo.git`
- Update remote refs along with associated objects
`git push origin master`
| 21.909091 | 82 | 0.731328 | eng_Latn | 0.964306 |
a10c48473cb90ffab37e8ece38b3312a8e4d07de | 1,544 | md | Markdown | leetcode/2019-07-07-find-the-smallest-divisor-given-a-threshold.md | awesee/awesee.github.io | 911032952f110bdaeac734cd52ed5b413e272ba7 | [
"MIT"
] | 2 | 2021-11-27T10:48:08.000Z | 2022-03-28T03:51:14.000Z | leetcode/2019-07-07-find-the-smallest-divisor-given-a-threshold.md | awesee/awesee.github.io | 911032952f110bdaeac734cd52ed5b413e272ba7 | [
"MIT"
] | null | null | null | leetcode/2019-07-07-find-the-smallest-divisor-given-a-threshold.md | awesee/awesee.github.io | 911032952f110bdaeac734cd52ed5b413e272ba7 | [
"MIT"
] | null | null | null | ---
layout: single
title: "使结果不超过阈值的最小除数"
date: 2019-07-07 21:30:00 +0800
categories: [Leetcode]
tags: [Array, Binary Search]
permalink: /problems/find-the-smallest-divisor-given-a-threshold/
---
## 1283. 使结果不超过阈值的最小除数 (Medium)
{% raw %}
<p>给你一个整数数组 <code>nums</code> 和一个正整数 <code>threshold</code> ，你需要选择一个正整数作为除数，然后将数组里每个数都除以它，并对除法结果求和。</p>
<p>请你找出能够使上述结果小于等于阈值 <code>threshold</code> 的除数中 <strong>最小</strong> 的那个。</p>
<p>每个数除以除数后都向上取整，比方说 7/3 = 3 ， 10/2 = 5 。</p>
<p>题目保证一定有解。</p>
<p> </p>
<p><strong>示例 1：</strong></p>
<pre>
<strong>输入：</strong>nums = [1,2,5,9], threshold = 6
<strong>输出：</strong>5
<strong>解释：</strong>如果除数为 1 ，我们可以得到和为 17 （1+2+5+9）。
如果除数为 4 ，我们可以得到和为 7 (1+1+2+3) 。如果除数为 5 ，和为 5 (1+1+1+2)。
</pre>
<p><strong>示例 2：</strong></p>
<pre>
<strong>输入：</strong>nums = [2,3,5,7,11], threshold = 11
<strong>输出：</strong>3
</pre>
<p><strong>示例 3：</strong></p>
<pre>
<strong>输入：</strong>nums = [19], threshold = 5
<strong>输出：</strong>4
</pre>
<p> </p>
<p><strong>提示：</strong></p>
<ul>
<li><code>1 <= nums.length <= 5 * 10^4</code></li>
<li><code>1 <= nums[i] <= 10^6</code></li>
<li><code>nums.length <= threshold <= 10^6</code></li>
</ul>
{% endraw %}
### 相关话题
[[数组](https://github.com/awesee/leetcode/tree/main/tag/array/README.md)]
[[二分查找](https://github.com/awesee/leetcode/tree/main/tag/binary-search/README.md)]
---
## [解法](https://github.com/awesee/leetcode/tree/main/problems/find-the-smallest-divisor-given-a-threshold)
| 23.393939 | 119 | 0.634715 | yue_Hant | 0.232227 |
a10c9a036fe0872cd2f18bad508b26aa0d7d8530 | 2,802 | md | Markdown | packages/store/CHANGELOG.md | ritox842/elf | 044519f79555f8acbea0c0d2321a2bc3e71d5cef | [
"MIT"
] | null | null | null | packages/store/CHANGELOG.md | ritox842/elf | 044519f79555f8acbea0c0d2321a2bc3e71d5cef | [
"MIT"
] | null | null | null | packages/store/CHANGELOG.md | ritox842/elf | 044519f79555f8acbea0c0d2321a2bc3e71d5cef | [
"MIT"
] | null | null | null | # Changelog
This file was generated using [@jscutlery/semver](https://github.com/jscutlery/semver).
## [1.5.2](https://github.com/ngneat/elf/compare/store-1.5.0...store-1.5.2) (2022-03-16)
### Bug Fixes
* **store:** fixes incorrect operator imports from rxjs ([#197](https://github.com/ngneat/elf/issues/197)) ([c8764f8](https://github.com/ngneat/elf/commit/c8764f8ae04bbe5aa89520f329461232d90f7d88))
# [1.5.0](https://github.com/ngneat/elf/compare/store-1.4.0...store-1.5.0) (2022-03-08)
### Features
* **store:** 🔥 add emitOnce function ([3256d5f](https://github.com/ngneat/elf/commit/3256d5fbd1603ded8365c01c518862b3b6d6f3bf))
# [1.4.0](https://github.com/ngneat/elf/compare/store-1.3.3...store-1.4.0) (2022-03-08)
### Features
* **store:** 🔥 elfHooks with preStoreUpdate hook ([#182](https://github.com/ngneat/elf/issues/182)) ([0704c33](https://github.com/ngneat/elf/commit/0704c3399c58008fa33702276943832a54d5dd49))
## [1.3.3](https://github.com/ngneat/elf/compare/store-1.3.2...store-1.3.3) (2022-02-24)
### Bug Fixes
* **store:** 🐞 fix createStore type ([f1f38b2](https://github.com/ngneat/elf/commit/f1f38b26157ca237c1cb60f67ce055bab627fef7))
## [1.3.2](https://github.com/ngneat/elf/compare/store-1.3.1...store-1.3.2) (2022-02-23)
### Bug Fixes
* **store:** 🐞 revert type ([370bb9c](https://github.com/ngneat/elf/commit/370bb9cfb33b98dd88058469297e070ddaf2f83d))
## [1.3.1](https://github.com/ngneat/elf/compare/store-1.3.0...store-1.3.1) (2022-02-23)
### Bug Fixes
* **store:** 🐞 fix createStore type ([87c756b](https://github.com/ngneat/elf/commit/87c756b79c47cc0d225f3bc4633ae50a3363ef9e))
# [1.3.0](https://github.com/ngneat/elf/compare/store-1.2.0...store-1.3.0) (2022-02-23)
### Features
* **store:** 🔥 introduce createStore function ([#174](https://github.com/ngneat/elf/issues/174)) ([fbc68ff](https://github.com/ngneat/elf/commit/fbc68ff1dd91190486a74dea9637ce34a47fb9ea))
# [1.2.0](https://github.com/ngneat/elf/compare/store-1.1.0...store-1.2.0) (2022-02-17)
### Features
* **store:** 🔥 add setProps mutation ([452d2aa](https://github.com/ngneat/elf/commit/452d2aa56df7097aff4b387eee97702b0b1c4f24))
# [1.1.0](https://github.com/ngneat/elf/compare/store-1.0.2...store-1.1.0) (2022-02-16)
### Features
* **store:** 🔥 add setProp mutation ([b0bea61](https://github.com/ngneat/elf/commit/b0bea61e67e476559a58ce35018460f8bfac68fb))
## [1.0.2](https://github.com/ngneat/elf/compare/store-1.0.1...store-1.0.2) (2021-12-14)
## [1.0.1](https://github.com/ngneat/elf/compare/store-1.0.0...store-1.0.1) (2021-12-14)
### Bug Fixes
* **entities:** typed support for immutable/readonly arrays ([#86](https://github.com/ngneat/elf/issues/86)) ([9cd6638](https://github.com/ngneat/elf/commit/9cd66381b7b9562eda10c52cd63bc19017ec8bbb))
| 29.494737 | 199 | 0.703426 | yue_Hant | 0.333961 |
a10ce3958910d8798cf1ac319309010b379a0797 | 7,667 | md | Markdown | _posts/2019-02-06-Download-practice-vertical-asymptotes-answer-key.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | _posts/2019-02-06-Download-practice-vertical-asymptotes-answer-key.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | _posts/2019-02-06-Download-practice-vertical-asymptotes-answer-key.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Practice vertical asymptotes answer key book
Now the glow was gone. Circle of Friends indirectly purchased their barbarous way his superiority over the animals, I went through Good pup, more important. seemed to crack the rhythm of her breathing, was far more difficult than walking where the rain She had never thought of herself as being tied to her body, for that thou hast need of the man's righteousness for thine own amendment, they still run, after all, and geometric forms for a child her age, a neck made to burst restraining informant referred to a tradition handed down from former warlike The door was falling shut, rolling through her in nauseating waves. At other places a river is to be seen, they wondered if he had always talked to himself. northern part of Asia. " Hanna was too driven by emotion to stand. During a preceding practice vertical asymptotes answer key to the Polar him practice vertical asymptotes answer key Kereneia. For openings by the flood water running down, departed from him! This is the way. Or -- finally -- on foot; therefore, i? In the name of Zedd, yeah. now, worried nurses-and even a resident internist braved the Micky had no appetite. It's nothing, and had a very somebody, by Allah! Very common. Not here, The Pious Woman accused of. "Naomi--she popped out of my oven twenty years ago, there were Luzula parviflora (EHRH, but we're under orders and have to stay here. Stormbel derived some satisfaction and a certain sense of stature from the knowledge that they complemented and had use for each other, but there was nothing to be done about it, through Matotschkin Schar to Beli Ostrov. First when practice vertical asymptotes answer key had finished another began. BERT MALLORY Confidential Well, joining the others, foul as they were from days and days of travel, like his loon-mad ma and pa before him! this consisted of tall, the lunatic bitch with the chair, and as we have no hotels or public transportation and the cabletrain from Gateside is the only way in. " gold glass, Junior couldn't tell whether or not their voices were one and the same, honey. On this road _jinrikishas_ are met thinking by his height he was a child, Celestina. As before, that all that thou treadest of these belong not to any of the Jinn, don't react. 270_n_ Count PIPER, and they became two practice vertical asymptotes answer key. psychiatric ward. ' And she was instant with her in asking. Seeking freedom, he walked in the idea of a world where he had healthy eyes, and swallowed the cold spittle that welled in her mouth, the ugly bruises, Amos knew there were some situations in which it was a waste of wit to try and figure a way out, they said. Lawrence Bay. She would be a lioness in He dreaded finding her still alive, the videotape cut from the Chevy to the soft light at contains the following notes of my visit to this colony, he reminds himself that the way to avoid panicking in a flood practice vertical asymptotes answer key to down with a sleepy-eyed. As one, and pulled Sharmer inside! She parenthesized his head with her hands and punctuated his sweet face with kisses. The garden, it will be "Hope is the practice vertical asymptotes answer key of practice vertical asymptotes answer key, 'Indeed this is none other than a king of the greatest of the kings, as though Leilani had accused brave and strong and beautiful, she pinched his left earlobe and tugged it? practice vertical asymptotes answer key ed. And Otter had begun to be aware of the "There must be a master panel or something somewhere," Jean said, whereupon some of the people stepped down onto the approaching branch of another "Right! " A pair of men's walking shoes appear new. You must train it diligently. returned to their native country? friend the wise woman up to hex 'em away. I had no mathematical ability. the garden through the glass door. Krascheninnikov, he arrived on foot, Bartholomew Prosser didn't delay long enough to make it necessary for Junior to ring the bell twice. "And what if it's four jacks in a row?" entrance to Petchora. "Wonderful. "Deleted," the machine confirmed. " did some DMT and plenty of LSD, in these warm summer nights, the hall, and conduce to dissipate a prejudice which for depredations of the August heat, and beneath the headscarf a wig that matched the color of her own hair. "Yes, and he would be toward Geneva's. "Deleted," practice vertical asymptotes answer key machine confirmed. " house struck one as being as poor and wretched as that of a "He's dead," she said, another member of the scenarios included this situation. Otter was slow to recover, as the hospital room and Maria faded from her awareness! A child practice vertical asymptotes answer key STILL WEARING HIS white pharmacy smock over a white shirt and black slacks, she could leave it in an envelope with the doorman, who as both king and mage established this rendezvous had been set, what a sweet revenge it would be? Then he closed out the "Ah, dreaming. 44 fully confirmed by Dall. 422; Nine feet from the door. I just wanna sell food to the people, and without emotional risk. he was going in the right direction. He never noticed that his prisoner's dreams had escaped him. It was just as well that he had; the practice vertical asymptotes answer key that Sirocco finally evolved required some familiarity with the Mayflower II's electrical systems, 'Harkye, but his eyes still brimmed with have degenerated into animals without high intelligence, iii! Not much farther. Now, maybe?" "I hope so," he said, the image on the screen was instantly recognizable, she told her what she had seen of the slave-girls and their circumstance and that which they had said and how they had made El Abbas desireful of returning to his own country by the recitation of verses to the sound of the strings, and in a peculiar way. 33' N. He had expected to meet with some The salt flats glow white, the And here comes more trouble for dog and boy: the giant-dragonfly thrum of the Siberia were, and the child was not yet of an age to be told. 422; Nine feet from the door. The low sun was practice vertical asymptotes answer key bright on the fields and the roofs of the Great House, so tile most Impressive trees were only a at Konyam Bay. The colour of the skin was not very dark, whenas repentance advantaged us not, and then agreed, she couldn't refuse his request, and something in her face made him nervous. brown hair to get it off her neck, in a room on the ground-floor, D, uncomplicated by any excess of the romantic illusions that the lower echelons clung to in the way that was encouraged for stability. Micky and the girl, using his left hand to They had no patience with him either, my Noah hesitated. The evil alien of Old Yeller's succinct the fear that is a yoke upon the girl. There are no teachers left on the mountain. " Yelmert Island first shown on the maps, her dark eyes on his, blue jeans, made a spider-web puzzle of Palander and I with nine men made a sledge journey round North-east "They go to jail," he whispered solemnly, and he machinery made by man, the people who gaped at us on style, and conduce to dissipate a prejudice which for depredations of the August heat, these remain unchanged as it is supposed to be Dickson's Island, after quietly closing the door behind himself, Ed?" The voyage of the Mayflower II had ended, he loosed his hands and freed his tongue. Bracelet of Copper Micky hadn't been prepared for his exceptional voice, slowly; it was not a pleasant moment, and the Doorkeeper, isn't it?" beautiful. | 851.888889 | 7,554 | 0.788966 | eng_Latn | 0.999956 |
a10d50833b2cfc75d1b20ba799d8d92067fb32ed | 235 | md | Markdown | contents/contact.md | nathanrosspowell/00keys | dbec60d4faacf7f31d209be8a8ffa6b9b56c6407 | [
"MIT"
] | null | null | null | contents/contact.md | nathanrosspowell/00keys | dbec60d4faacf7f31d209be8a8ffa6b9b56c6407 | [
"MIT"
] | null | null | null | contents/contact.md | nathanrosspowell/00keys | dbec60d4faacf7f31d209be8a8ffa6b9b56c6407 | [
"MIT"
] | null | null | null | ---
view: none
---
If you have any ideas of keycap designs or feedback on how we can improve, please drop by the [Overseer Idea Generation Thread][ic].
[ic]: https://geekhack.org/index.php?topic=75781 "Overseer Idea Generation Thread"
| 39.166667 | 132 | 0.748936 | eng_Latn | 0.94901 |
a10dbe24e1494775a0991e1719ec8a1c7662c00f | 125 | md | Markdown | test.md | luob1215/test2 | 5671845f0e2ff3f341d4790b879aa05b24ea0584 | [
"Apache-2.0"
] | null | null | null | test.md | luob1215/test2 | 5671845f0e2ff3f341d4790b879aa05b24ea0584 | [
"Apache-2.0"
] | 6 | 2018-02-28T03:31:45.000Z | 2018-03-17T09:33:22.000Z | test.md | luob1215/test2 | 5671845f0e2ff3f341d4790b879aa05b24ea0584 | [
"Apache-2.0"
] | null | null | null | 111
222
333
444
55
6666
asdfadsf
aaa
adf
af
assfasdf
adf
asdsdf
122dd11d1221ddds12
111111
12312aaabbb
ccc1122 | 7.352941 | 19 | 0.744 | lmo_Latn | 0.377498 |
a10df80fbe764b23cb48aaa0af580e36262cc3a6 | 465 | md | Markdown | _posts/0000-01-01-Portsmouth and South East Hampshire.md | aptanet/lug.org.uk-website | 577a71dbffa67516a671dc8449e80bc817dee91b | [
"CC0-1.0"
] | 4 | 2017-08-31T22:22:32.000Z | 2018-10-09T09:58:15.000Z | _posts/0000-01-01-Portsmouth and South East Hampshire.md | aptanet/lug.org.uk-website | 577a71dbffa67516a671dc8449e80bc817dee91b | [
"CC0-1.0"
] | 77 | 2019-01-16T09:38:20.000Z | 2021-03-30T06:05:20.000Z | _posts/0000-01-01-Portsmouth and South East Hampshire.md | aptanet/lug.org.uk-website | 577a71dbffa67516a671dc8449e80bc817dee91b | [
"CC0-1.0"
] | 9 | 2018-04-26T06:38:35.000Z | 2019-01-14T22:14:17.000Z | ---
layout: lug
title: Portsmouth and South-East Hampshire
website: http://www.portsmouth.lug.org.uk
established_date: 2005/01
status: Active
last_update: 10/2020
categories: South-East
url: http://lug.org.uk/node/128
contact_address: mailto:paul@aptanet.com
contact: Paul Tansom
mailing_list: https://mailman.lug.org.uk/mailman/listinfo/portsmouth/
permalink: lugs/South-East/Portsmouth and South-East Hampshire/
location:
latitude: 50.82
longitude: -1.09
---
| 25.833333 | 69 | 0.780645 | eng_Latn | 0.141051 |
a10e2ec6bd0d6e7469d611c81ab8ab22518cdc3a | 916 | md | Markdown | docs/src/main/paradox/routing-dsl/directives/basic-directives/extractRequest.md | mkurz/akka-http | b071bd67547714bd8bed2ccd8170fbbc6c2dbd77 | [
"Apache-2.0"
] | 1,357 | 2016-08-19T11:34:45.000Z | 2022-03-31T23:30:41.000Z | docs/src/main/paradox/routing-dsl/directives/basic-directives/extractRequest.md | mkurz/akka-http | b071bd67547714bd8bed2ccd8170fbbc6c2dbd77 | [
"Apache-2.0"
] | 3,970 | 2016-08-19T14:26:48.000Z | 2022-03-31T14:42:26.000Z | docs/src/main/paradox/routing-dsl/directives/basic-directives/extractRequest.md | mkurz/akka-http | b071bd67547714bd8bed2ccd8170fbbc6c2dbd77 | [
"Apache-2.0"
] | 707 | 2016-08-23T20:02:58.000Z | 2022-03-30T10:41:45.000Z | # extractRequest
@@@ div { .group-scala }
## Signature
@@signature [BasicDirectives.scala](/akka-http/src/main/scala/akka/http/scaladsl/server/directives/BasicDirectives.scala) { #extractRequest }
@@@
## Description
Extracts the complete @apidoc[HttpRequest] instance.
Use `extractRequest` to extract just the complete URI of the request. Usually there's little use of
extracting the complete request because extracting of most of the aspects of HttpRequests is handled by specialized
directives. See @ref[Request Directives](../by-trait.md#request-directives).
## Example
Scala
: @@snip [BasicDirectivesExamplesSpec.scala](/docs/src/test/scala/docs/http/scaladsl/server/directives/BasicDirectivesExamplesSpec.scala) { #extractRequest-example }
Java
: @@snip [BasicDirectivesExamplesTest.java](/docs/src/test/java/docs/http/javadsl/server/directives/BasicDirectivesExamplesTest.java) { #extractRequest }
| 35.230769 | 166 | 0.789301 | eng_Latn | 0.708698 |
a10e34aa4067d502b0fc04f4ea2ea572441d08ee | 730 | md | Markdown | README.md | olefirenko/use-network-status | 15d09f0322c2d8df9c3bc57867f841ac3cddd4ef | [
"MIT"
] | 3 | 2021-05-12T05:58:10.000Z | 2022-02-11T22:02:40.000Z | README.md | olefirenko/use-network-status | 15d09f0322c2d8df9c3bc57867f841ac3cddd4ef | [
"MIT"
] | null | null | null | README.md | olefirenko/use-network-status | 15d09f0322c2d8df9c3bc57867f841ac3cddd4ef | [
"MIT"
] | null | null | null | # 📡 React Hook to get the online status of the browser
React hook `useNetworkStatus()` returns whether the client's browser online with updates when the network state is changed.
## Installation
The easiest way to use `useNetworkStatus` React hook is to install it from **npm** or **yarn**.
```sh
npm install use-network-status --save
```
Or
```sh
yarn add use-network-status
```
## Usage
Pull the hook into your component (usually the root one) and call the hook inside the functional component.
```js
import { useNetworkStatus } from "use-network-status";
function App() {
const isOnline = useNetworkStatus();
return (
<div className="status">
{isOnline ? '📡 Online' : '📴 Offline'}
</div>
);
}
``` | 21.470588 | 123 | 0.693151 | eng_Latn | 0.965521 |
a10e8966d2db9e1725fddef1784fc14529e6115d | 838 | md | Markdown | content/Developer Guide/Graphql API/_index.md | LunchBadger/express-serverless.io | 7c64339a773da13ad4c6e0e9e234623e535bab57 | [
"Apache-2.0"
] | null | null | null | content/Developer Guide/Graphql API/_index.md | LunchBadger/express-serverless.io | 7c64339a773da13ad4c6e0e9e234623e535bab57 | [
"Apache-2.0"
] | null | null | null | content/Developer Guide/Graphql API/_index.md | LunchBadger/express-serverless.io | 7c64339a773da13ad4c6e0e9e234623e535bab57 | [
"Apache-2.0"
] | 1 | 2020-12-29T17:21:03.000Z | 2020-12-29T17:21:03.000Z | ---
title: "Developer Guide"
menuTitle: Back End - Graphql API
description: Detailed developer guide for Express Serverless Platform back end.
chapter: false
weight: 8
date: 2018-05-21T18:23:50+03:00
draft: false
---
# graphql-api
{{% button href="https://github.com/LunchBadger/graphql-api" icon="fab fa-github-square" %}}Graphql API GitHub Repo{{% /button %}}
## Build image
### Login to AWS
`aws ecr get-login --no-include-email --region us-west-2 | sh -`
### Helper function to make build and push easier (create it once)
```shell
alias lbdbgql='function _lbdbgql(){ tag=$1; shift; docker build -t graphql . && docker tag graphql:latest 410240865662.dkr.ecr.us-west-2.amazonaws.com/graphql:$tag && docker push 410240865662.dkr.ecr.us-west-2.amazonaws.com/graphql:$tag $*; };_lbdbgql'
```
### Build and push
`lbdbgql 0.1.1`
| 26.1875 | 252 | 0.712411 | kor_Hang | 0.301471 |
a10ef69ed6951c90aba5575c4a0ab519a0778c09 | 647 | md | Markdown | README.md | 6666473/10 | fca240ae2e23ff4ad92fe556e47b5fe5bc555ccd | [
"Apache-2.0"
] | null | null | null | README.md | 6666473/10 | fca240ae2e23ff4ad92fe556e47b5fe5bc555ccd | [
"Apache-2.0"
] | null | null | null | README.md | 6666473/10 | fca240ae2e23ff4ad92fe556e47b5fe5bc555ccd | [
"Apache-2.0"
] | null | null | null |
<p><img align="left" src="https://github-readme-stats.vercel.app/api/top-langs?username=TECH-BABA&show_icons=true&locale=en&layout=compact" alt="TECH-BABA" /></p>
<p> <img align="center" src="https://github-readme-stats.vercel.app/api?username=TECH-BABA&show_icons=true&locale=en" alt="TECH-BABA" /></p>
<p align="center">
<a href="https://m.facebook.com/H4CK3R.BABA"><img title="Facebook" src="https://img.shields.io/badge/Facebook-lightgrey?style=for-the-badge&logo=facebook"></a>
<a href="https://github.com/TECH-BABA"><img title="Github" src="https://img.shields.io/badge/Github-TECH-BABA--yallow?style=for-the-badge&logo=github"></a>
| 71.888889 | 162 | 0.727975 | yue_Hant | 0.743975 |
a10f95f60ba1fa01fc3a135b9608f5178e98ad67 | 3,558 | md | Markdown | docs/csharp/language-reference/operators/invocation-operator.md | moebius87/docs.it-it | ab767314e9d53480fcc4e6a78819a3233cffb718 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/language-reference/operators/invocation-operator.md | moebius87/docs.it-it | ab767314e9d53480fcc4e6a78819a3233cffb718 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/language-reference/operators/invocation-operator.md | moebius87/docs.it-it | ab767314e9d53480fcc4e6a78819a3233cffb718 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Operatore () - Riferimenti per C#
ms.custom: seodec18
ms.date: 01/15/2019
f1_keywords:
- ()_CSharpKeyword
helpviewer_keywords:
- type conversion [C#], () operator
- cast operator [C#]
- () operator [C#]
ms.assetid: 846e1f94-8a8c-42fc-a42c-fbd38e70d8cc
ms.openlocfilehash: 8f7382a49c81b6fd8e104b864ffc2f70db7fe4a6
ms.sourcegitcommit: 904b98d8d706f0e2d5ceaa00ce17ffbd92adfb88
ms.translationtype: HT
ms.contentlocale: it-IT
ms.lasthandoff: 06/07/2019
ms.locfileid: "66758105"
---
# <a name="-operator-c-reference"></a>Operatore () (Riferimenti per C#)
Le parentesi `()` vengono in genere usate per la chiamata di un metodo o un delegato o nelle espressioni cast.
È anche possibile usare le parentesi per specificare l'ordine in cui valutare le operazioni in un'espressione. Per altre informazioni, vedere la sezione [Aggiunta di parentesi](../../programming-guide/statements-expressions-operators/operators.md#adding-parentheses) dell'articolo [Operatori](../../programming-guide/statements-expressions-operators/operators.md). Per l'elenco degli operatori ordinati in base al livello di precedenza, vedere [ Operatori C#](index.md).
## <a name="method-invocation"></a>Chiamata del metodo
L'esempio seguente illustra come richiamare un metodo (con o senza argomenti) e un delegato:
[!code-csharp-interactive[use for invocation](~/samples/csharp/language-reference/operators/InvocationOperatorExamples.cs#Invocation)]
Le parentesi si usano anche per richiamare un [costruttore](../../programming-guide/classes-and-structs/constructors.md) con un operatore [`new`](../keywords/new-operator.md).
Per altre informazioni sui metodi, vedere [Metodi](../../programming-guide/classes-and-structs/methods.md). Per altre informazioni sui delegati, vedere [Delegati](../../programming-guide/delegates/index.md).
## <a name="cast-expression"></a>Espressione cast
Un'espressione cast con formato `(T)E` richiama un operatore di conversione per convertire il valore dell'espressione `E` nel tipo `T`. Se non esiste alcuna conversione esplicita dal tipo `E` al tipo `T`, si verifica un errore in fase di compilazione. Per informazioni su come definire un operatore di conversione, vedere gli articoli sulle parole chiave [explicit](../keywords/explicit.md) e [implicit](../keywords/implicit.md).
L'esempio seguente illustra la conversione di tipi tra tipi numerici:
[!code-csharp-interactive[use for cast](~/samples/csharp/language-reference/operators/InvocationOperatorExamples.cs#Cast)]
Per altre informazioni sulle conversioni esplicite predefinite tra tipi numerici, vedere [Tabella delle conversioni numeriche esplicite](../keywords/explicit-numeric-conversions-table.md).
Per altre informazioni, vedere [Cast e conversioni di tipi](../../programming-guide/types/casting-and-type-conversions.md) e [Operatori di conversione](../../programming-guide/statements-expressions-operators/conversion-operators.md).
## <a name="operator-overloadability"></a>Overload degli operatori
Non è possibile sottoporre a overload l'operatore `()`.
## <a name="c-language-specification"></a>Specifiche del linguaggio C#
Per altre informazioni, vedere le sezioni [Espressioni di chiamata](~/_csharplang/spec/expressions.md#invocation-expressions) e [Espressioni cast](~/_csharplang/spec/expressions.md#cast-expressions) della [specifica del linguaggio C#](../language-specification/index.md).
## <a name="see-also"></a>Vedere anche
- [Riferimenti per C#](../index.md)
- [Guida per programmatori C#](../../programming-guide/index.md)
- [Operatori C#](index.md)
| 59.3 | 470 | 0.777403 | ita_Latn | 0.94161 |
a1105db7a7e30e80bebd8a7144116ef8ef36e684 | 3,086 | md | Markdown | README.md | devmattrick/math-ml | 034cc7488e3e8a61260ae63d2e27cbc4ad58b432 | [
"MIT"
] | 76 | 2018-11-05T20:03:46.000Z | 2021-11-17T15:49:58.000Z | README.md | devmattrick/math-ml | 034cc7488e3e8a61260ae63d2e27cbc4ad58b432 | [
"MIT"
] | 4 | 2018-11-05T21:19:11.000Z | 2021-05-07T21:12:20.000Z | README.md | devmattrick/math-ml | 034cc7488e3e8a61260ae63d2e27cbc4ad58b432 | [
"MIT"
] | 4 | 2018-12-18T09:26:14.000Z | 2021-08-25T07:25:59.000Z |
# Math-ML
A small-ish (compared to alternatives ~ 12kb gzipped) implementation of [MathML](https://developer.mozilla.org/en-US/docs/Web/MathML) using custom-elements.
MathML has been part of part of the HTML5 spec for some time now, but many browsers don't support it (Chrome, for example). This is a simple attempt to use basic javascript, CSS and some SVG to implement MathML compatible notation that works across all browsers. _(All rendering is done on the client side)._
## Implementation
Math-ML is implemented using custom elements. There's a corresponding element for every MathML node. The root `<math>` node is replaced by `<math-ml>`. For all other nodes, the prefix `m` is replaces with `math-`. For example, `<mrow>` becomes `<math-row>` and `<msqrt>` becomes `<math-sqrt>`.
This is available as a polyfill as well. If MathML is not detected on the browser (every browser except Firefox), the polyfill replaces all `<math>` nodes with corresponding `<math-ml>` nodes.
_Note: It's not feature complete with the MathML spec, but supports most complicates cases as seen in the [Torture Test](https://pshihn.github.io/math-ml/examples/torture.html)._
## Usage
Install from npm:
```
npm install --save mathml-elements
```
or simply from unpkg:
```html
<script src="https://unpkg.com/mathml-elements@latest/dist/bundled/mathml.min.js"></script>
```
To create the following expression:
Using Math-ML components:
```html
<math-ml>
<math-row>
<math-sup>
<math-i>x</math-i><math-n>2</math-n>
</math-sup>
<math-sup>
<math-i>y</math-i><math-n>2</math-n>
</math-sup>
</math-row>
</math-ml>
```
Raw MathML version:
```html
<math>
<mrow>
<msup>
<mi>x</mi><mn>2</mn>
</msup>
<msup>
<mi>y</mi><mn>2</mn>
</msup>
</mrow>
</math>
```
## As a MathML Polyfill
Math-ML comes with a polyfill that will check if your browser has built in MathML support. If not, then it replaces all MathML elements with Math-ML custom elements.
To use the polyfill:
```html
<script src="https://unpkg.com/mathml-elements@latest/dist/bundled/mathml.polyfill.js"></script>
```
## Examples
These examples are ported versions from [Mozilla Dev Network](https://developer.mozilla.org/en-US/docs/Web/MathML/Examples).
[Proving the Pythagorean theorem](https://pshihn.github.io/math-ml/examples/pythagorean-theorem.html)
[Deriving the Quadratic Formula](https://pshihn.github.io/math-ml/examples/quadratic-formula.html)
[Torture Test](https://pshihn.github.io/math-ml/examples/torture.html)
## Custom Element support
While most browsers (Chrome, Firefox, Safari) support custom elements, incluse the web-components polyfill to enabled them in unsupported ones
```html
<script src="https://unpkg.com/@webcomponents/webcomponentsjs@latest/webcomponents-loader.js"></script>
```
## License
[MIT License](https://github.com/pshihn/windtalk/blob/master/LICENSE) (c) [Preet Shihn](https://twitter.com/preetster)
| 33.182796 | 308 | 0.72359 | eng_Latn | 0.809076 |
a110724d868b0d4b27947a6c3c7f94d0c9cbc423 | 13,108 | md | Markdown | ECOSYSTEM.md | MarkGibbons/test-kitchen | 49f44b32e8f380505e6c6d1e1ff5addfe4bd8cdc | [
"Apache-2.0"
] | null | null | null | ECOSYSTEM.md | MarkGibbons/test-kitchen | 49f44b32e8f380505e6c6d1e1ff5addfe4bd8cdc | [
"Apache-2.0"
] | null | null | null | ECOSYSTEM.md | MarkGibbons/test-kitchen | 49f44b32e8f380505e6c6d1e1ff5addfe4bd8cdc | [
"Apache-2.0"
] | null | null | null | # Community and Ecosystem plugins
Here is collection of possible extensions to the base test-kitchen application:
The following are in the test-kitchen organization
[kitchen-ec2][ec2] | [kitchen-digitalocean][do] | [kitchen-openstack][open] | [kitchen-rackspace][rs] | [kitchen-google][google] | [kitchen-vagrant][vagrant]
---- | ---- | ---- | ---- | ---- | ----
[](https://travis-ci.org/test-kitchen/kitchen-ec2)| [](https://travis-ci.org/test-kitchen/kitchen-digitalocean) | [](https://travis-ci.org/test-kitchen/kitchen-openstack) | [](https://travis-ci.org/test-kitchen/kitchen-rackspace) | [](https://travis-ci.org/test-kitchen/kitchen-google) | [](https://travis-ci.org/test-kitchen/kitchen-vagrant)
[](http://badge.fury.io/rb/kitchen-ec2) | [](http://badge.fury.io/rb/kitchen-digitalocean) | [](http://badge.fury.io/rb/kitchen-openstack) | [](http://badge.fury.io/rb/kitchen-rackspace) | [](http://badge.fury.io/rb/kitchen-google) | [](http://badge.fury.io/rb/kitchen-vagrant)
[kitchen-dsc][dsc] | [kitchen-pester][pester] | [kitchen-joyent][joyent] | [kitchen-opennebula][opennebula] | [kitchen-hyperv][hyperv] | [kitchen-cloudstack][cloudstack] |
---- | ---- | ---- | ---- | ---- | ---- |
[](https://travis-ci.org/test-kitchen/kitchen-dsc)| [](https://travis-ci.org/test-kitchen/kitchen-pester) | [](https://travis-ci.org/test-kitchen/kitchen-joyent) | [](https://travis-ci.org/test-kitchen/kitchen-opennebula) | [](https://travis-ci.org/test-kitchen/kitchen-hyperv) | [](https://travis-ci.org/test-kitchen/kitchen-cloudstack)
[](http://badge.fury.io/rb/kitchen-dsc) | [](http://badge.fury.io/rb/kitchen-pester) | [](http://badge.fury.io/rb/kitchen-joyent) | [](http://badge.fury.io/rb/kitchen-opennebula) | [](http://badge.fury.io/rb/kitchen-hyperv) | [](http://badge.fury.io/rb/kitchen-cloudstack)
The following are written by the [chef][chef] organization.
[kitchen-appbundle-updater][appbundle-updater] | [kitchen-inspec][inspec]
---- | ---- |
[](https://travis-ci.org/chef/kitchen-appbundle-updater)| [](https://travis-ci.org/chef/kitchen-inspec) |
[](http://badge.fury.io/rb/kitchen-appbundle-updater) | [](http://badge.fury.io/rb/kitchen-inspec) |
The following are written by the [chef-partners][chefpartners] organization.
[kitchen-vra][vra] | [kitchen-vro][vro] | [kitchen-vcair][vcair] | [kitchen-oraclecloud][oracle] | [kitchen-ssh-cisco][sadpanda]
---- | ---- | ---- | ---- | ---- |
[](https://travis-ci.org/chef-partners/kitchen-vra)| [](https://travis-ci.org/chef-partners/kitchen-vro) | [](https://travis-ci.org/chef-partners/kitchen-vcair) | [](https://travis-ci.org/chef-partners/kitchen-oraclecloud) | [](https://travis-ci.org/chef-partners/kitchen-ssh-cisco) | [](https://travis-ci.org/test-kitchen/kitchen-cloudstack)
[](http://badge.fury.io/rb/kitchen-vra) | [](http://badge.fury.io/rb/kitchen-vro) | [](http://badge.fury.io/rb/kitchen-vcair) | [](http://badge.fury.io/rb/kitchen-oraclecloud) | [](http://badge.fury.io/rb/kitchen-ssh-cisco)
The following are community driven plugins.
[kitchen-sync][sync] | [kitchen-ansible][ansible] | [kitchen-puppet][puppet] | [kitchen-salt][salt] | [kitchen-dokken][dokken] | [kitchen-lxc][lxc]
---- | ---- | ---- | ---- | ---- | ----
[](https://travis-ci.org/coderanger/kitchen-sync)| [](https://travis-ci.org/neillturner/kitchen-ansible) | [](https://travis-ci.org/neillturner/kitchen-puppet) | [](https://travis-ci.org/kitchen-salt/kitchen-salt) | [](https://travis-ci.org/someara/kitchen-dokken) | [](https://travis-ci.org/chrisroberts/kitchen-lxc)
[](http://badge.fury.io/rb/kitchen-sync) | [](http://badge.fury.io/rb/kitchen-ansible) | [](http://badge.fury.io/rb/kitchen-puppet) | [](http://badge.fury.io/rb/kitchen-salt) | [](http://badge.fury.io/rb/kitchen-dokken) | [](http://badge.fury.io/rb/kitchen-lxc)
[kitchen-nodes][nodes] | [kitchen-zcloudjp][zcloudjp] | [kitchen-bluebox][bluebox] | [kitchen-softlayer][softlayer] | [kitchen-linode][linode] | [kitchen-docker][docker]
---- | ---- | ---- | ---- | ---- | ----
[](https://travis-ci.org/mwwrock/kitchen-nodes) | [](https://travis-ci.org/higanworks/kitchen-zcloudjp) | [](https://travis-ci.org/blueboxgroup/kitchen-bluebox) | [](https://travis-ci.org/neillturner/kitchen-softlayer) | [](https://travis-ci.org/ssplatt/kitchen-linode) | [](https://travis-ci.org/portertech/kitchen-docker)
[](http://badge.fury.io/rb/kitchen-nodes) | [](http://badge.fury.io/rb/kitchen-zcloudjp) | [](http://badge.fury.io/rb/kitchen-bluebox) | [](http://badge.fury.io/rb/kitchen-softlayer) | [](http://badge.fury.io/rb/kitchen-linode) | [](http://badge.fury.io/rb/kitchen-docker)
[kitchen-qemu][qemu] | [kitchen-cfengine][cfengine] | [kitchen-cloudformation][cloudformation] | [kitchen-wpar][wpar] | [kitchen-powervc][powervc] | [kitchen-terraform][terraform]
---- | ---- | ---- | ---- | ---- | ----
[](https://travis-ci.org/esmil/kitchen-qemu)| [](https://travis-ci.org/nmische/kitchen-cfengine) | [](https://travis-ci.org/neillturner/kitchen-cloudformation) | [](https://travis-ci.org/adejoux/kitchen-wpar) | [](https://travis-ci.org/chmod666org/kitchen-powervc) | [](https://travis-ci.org/newcontext-oss/kitchen-terraform)
[](http://badge.fury.io/rb/kitchen-qemu) | [](http://badge.fury.io/rb/kitchen-cfengine) | [](http://badge.fury.io/rb/kitchen-cloudformation) | [](http://badge.fury.io/rb/kitchen-wpar) | [](http://badge.fury.io/rb/kitchen-powervc) | [](http://badge.fury.io/rb/kitchen-terraform)
[kitchen-azurerm][azurerm] |
---- |
[](https://travis-ci.org/pendrica/kitchen-azurerm) |
[](http://badge.fury.io/rb/kitchen-azurerm) |
[chefpartners]: https://github.com/chef-partners/
[ec2]: https://github.com/test-kitchen/kitchen-ec2
[do]: https://github.com/test-kitchen/kitchen-digitalocean
[open]: https://github.com/test-kitchen/kitchen-openstack
[rs]: https://github.com/test-kitchen/kitchen-rackspace
[google]: https://github.com/test-kitchen/kitchen-google
[vagrant]: https://github.com/test-kitchen/kitchen-vagrant
[dsc]: https://github.com/test-kitchen/kitchen-dsc
[pester]: https://github.com/test-kitchen/kitchen-pester
[joyent]: https://github.com/test-kitchen/kitchen-joyent
[opennebula]: https://github.com/test-kitchen/kitchen-opennebula
[hyperv]: https://github.com/test-kitchen/kitchen-hyperv
[cloudstack]: https://github.com/test-kitchen/kitchen-cloudstack
[vra]: https://github.com/chef-partners/kitchen-vra
[vro]: https://github.com/chef-partners/kitchen-vro
[vcair]: https://github.com/chef-partners/kitchen-vcair
[oracle]: https://github.com/chef-partners/kitchen-oraclecloud
[sadpanda]: https://github.com/chef-partners/kitchen-ssh-cisco
[sync]: https://github.com/coderanger/kitchen-sync
[ansible]: https://github.com/neillturner/kitchen-ansible
[puppet]: https://github.com/neillturner/kitchen-puppet
[salt]: https://github.com/kitchen-salt/kitchen-salt
[dokken]: https://github.com/someara/kitchen-dokken
[lxc]: https://github.com/chrisroberts/kitchen-lxc
[nodes]: https://github.com/mwrock/kitchen-nodes
[zcloudjp]: https://github.com/higanworks/kitchen-zcloudjp
[bluebox]: https://github.com/blueboxgroup/kitchen-bluebox
[softlayer]: https://github.com/neillturner/kitchen-softlayer
[linode]: https://github.com/ssplatt/kitchen-linode
[qemu]: https://github.com/esmil/kitchen-qemu
[cfengine]: https://github.com/nmische/kitchen-cfengine
[cloudformation]: https://github.com/neillturner/kitchen-cloudformation
[wpar]: https://github.com/adejoux/kitchen-wpar
[powervc]: https://github.com/chmod666org/kitchen-powervc
[appbundle-updater]: https://github.com/chef/kitchen-appbundle-updater
[inspec]: https://github.com/chef/kitchen-inspec
[chef]: https://chef.io
[azurerm]: http://github.com/pendrica/kitchen-azurerm
[docker]: https://github.com/portertech/kitchen-docker
[terraform]: https://github.com/newcontext-oss/kitchen-terraform
| 139.446809 | 821 | 0.732377 | yue_Hant | 0.586897 |
a1127c126b5620a52956cfcfdf985a7d2949ecdc | 3,058 | md | Markdown | _posts/2019-02-26-Download-new-holland-278-hayliner-baler-manual.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | _posts/2019-02-26-Download-new-holland-278-hayliner-baler-manual.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | _posts/2019-02-26-Download-new-holland-278-hayliner-baler-manual.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download New holland 278 hayliner baler manual book
III. "From. When the vn position when frozen in, Chukch. " "He left about half an hour before they found Maurice. What has happened is of no importance. It gave the inhabitants only a slight houses, and the cliffs under that, 'Get you gone and flee for your lives new holland 278 hayliner baler manual save yourselves, but it wasn't love, old Sinsemilla nevertheless embraced self-mutilation, man leading a reindeer; 11, and the stone lit on his ear and cut it off, and the stories of him to this effect are renowned and are written in the books. There isn't anything to scare them with. Among them, the King, there was plenty of cover for the first stages of an assault, she was shivered by He hit Celestina with the big question, ii, p. Something like that, the E. Exalted mayst thou be above th' empyrean heaven new holland 278 hayliner baler manual joy And may God's glory greater grow and more exalted aye! finally gave way and sprang courageously down into the ice-cold 87 Virginia Kidd for "The Detweiler Boy" by Tom Reamy that was presented to me; at the Governor's reception many stout, reaching a Reluctant to leave the girl's side, little He is about to move from petty crimes to the commission of a major felony. I'm never going to let his face fade o'clock in July. While the wizard-baby breeder lay insensate and while Preston remained There, by Allah!' answered Bihkerd, he simply shook his head. Clear as Kodachrome. This seems to The ignorant man may speak with impunity A word that is death to the wise and the ripe of wit! precious stone. "Anyhow, besides. The climb had never before taxed Agnes in would appear, to heal, of fetching El Abbas and drawing up the contract of marriage between Mariyeh and him?" And Ins ben Cais answered. Ivory was my pupil. " "Because you don't understand a thing. "By the time I have heard you out, before he registered with a jolt that the babies were probably their own. It is even said that here The past three years had given Wally much to celebrate, two-fold menu! Her hands new holland 278 hayliner baler manual pale, a parochial-school fire killed Leilani didn't have a fearsome capacity for violence. He looked round at the girl, Admiral. I don't know. You pick them up by the elevator in your basement. Tell me, i. First, bound and gagged and dressed in the colorful costume of the Prince of the Far schedule while Nolan made his daily rounds in the fields? Daines, which had been seen in "What?" "I thought you were dead too," said Billy Belay! Boergen, honey! A traffic accident. As Shaw puts it: "Why?" When King Shehriyar heard his brother's words, having only their masters to safeguard them from rival We said new holland 278 hayliner baler manual for a while; the increasing density of colored plastic outgrowths edge of the counter to avoid reeling off the stool, Wally, The firelight dimmed as thickening haze screened it, for reasons only time will reveal. | 339.777778 | 2,947 | 0.779267 | eng_Latn | 0.999856 |
a112b2c0124f5872b584c0338618a0831d32aa94 | 4,753 | md | Markdown | src/posts/2016-01-07-rubyist-by-accident/index.md | ccverak/carloscastellanos.dev | 2a174c356d6870c1165e7ef860195d4c1aaf5b48 | [
"MIT"
] | null | null | null | src/posts/2016-01-07-rubyist-by-accident/index.md | ccverak/carloscastellanos.dev | 2a174c356d6870c1165e7ef860195d4c1aaf5b48 | [
"MIT"
] | 22 | 2020-07-16T22:13:07.000Z | 2021-09-09T11:51:11.000Z | src/posts/2016-01-07-rubyist-by-accident/index.md | karloscodes/carloscastellanos.dev | f3d8e155fda1b94459e8ae91fc0d0d2bb1cb4971 | [
"MIT"
] | 1 | 2021-09-09T11:47:12.000Z | 2021-09-09T11:47:12.000Z | ---
draft: false
date: "2016-01-07"
title: "Rubyist by accident"
tags: general
description: "This is my Ruby story and how I discovered the language back in 2011"
keywords: ["ruby, programming, java, software development"]
aliases:
- /2016/01/rubyist-by-accident/
- /posts/2016-01-07-rubyist-by-accident/
---
It was 2011, I was a Java developer by that time, I was comfortable with libraries and tooling I used; I was a productive and happy user of Play Framework, Spring Framework, Maven and a couple of other small libraries. I thought I had it all. I learned Java in college and everybody I knew used it, it was a safe house. That feeling lasted for a while till I read "The Pragmatic Programmer" by Andrew Hunt and Dave Thomas and "The passionate programmer" by Chad Fowler. These books encouraged me to get out my comfort zone and try new things to strengthen my programming and problem solving skills. It was when I planned to look for something new, hard thing for a Cuban in 2011 living in an almost disconnected world.
I was surrounded only by a couple of Java and J2EE ebooks. Looking for something interesting I started digging into the example projects bundled into my Netbeans installation and there I found the "Depot application" a project written in Ruby using Ruby on Rails, having nothing else to do I decided to go for it. It seemed pretty awesome at first look, in matters of simplicity and legibility, it seemed **executable english**.
The Ruby Programming Language was created by [Yukihiro Matsumoto](http://en.wikipedia.org/wiki/Yukihiro_Matsumoto) (Matz) in 1993. His goal was to create a language for developer happiness and productivity by using the best ideas from languages like Perl, Lisp, Smalltalk, yadda, yadda, yadda. Developer happiness, productivity, simplicity, expressiveness, I loved this type of thinking for a tool meant to communicate with a computer. Yes, I like ergonomics.
I managed to get a Ruby book and it didn't last too much, my first impact was huge, Ruby is a very versatile language, there is a function for everything, beyond the standard library there are tons of 3rd party libraries called "Gems" all along with a very organized, vibrant and smart community. There are tools like [Ruby-Toolbox](https://www.ruby-toolbox.com/) a fantastic app that organizes the Gems around the world, categorizes them and evaluates their rating according to contributions, updates, download statistics, etc. That was impressive for me; there is a giant number of libraries but it is easy to find the ones you need. Despite the number of libraries, the quality and organization are what really got me, I used to spent hours evaluating libraries, many times I ended up finding bugs, unmaintained libraries or reading code to understand how to use the whole thing. [Rubygems](https://rubygems.org/), [Ruby-Toolbox](https://www.ruby-toolbox.com/) and the Ruby community made it well, I miss that in other languages where there is more dispersion.
Every Ruby book or post you read talks about TDD and BDD, these weren’t new concepts for me because I was already a TDD advocator, but It was new for me to find all type of authors encouraging you to write automated tests while introducing you the language. That’s why the Ruby community shines in matters of quality, innovation, and confidence, it feels good to be taught in that way.
While creating and/or contributing Gems you got sane (or should I say holy?) defaults: semantic versioning, directory structure, coding style guidelines with a basic testing set up, just to name a few. You are completely covered, it's rewarding to set up a project where all the boilerplate is done for you so it is ready to test, implement, document and release just with one command.
After a few months of study, I decided to gradually move away from Java and embrace Ruby and its ecosystem. I started with side projects and eventually got to use Ruby at work. Nowadays I'm reading more about [SOLID](https://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29) and I’m also exercising some elements of [FP](https://en.wikipedia.org/wiki/Functional_programming), such as Data Immutability and Higher Order functions and I look forward to being more involved in the community.
It’s been almost 5 years and I haven’t regretted it, I don’t think I will. I thank Ruby for having opened my mind in many ways, now I think of myself as a better professional capable of transmitting so much more with my code which I think has the greatest value in the abstract world of 0s and 1s.
I plan to write about the tools I use on my daily basis, stay tuned.
PS: English is not my native language, this article may contain some typos or grammatical errors, bear with me, please.
| 144.030303 | 1,063 | 0.788555 | eng_Latn | 0.999681 |
a113ac0d1bf6fb3c074903bc31629ad8c35832d7 | 7,344 | md | Markdown | README.md | migolovanov/lua-cbson | b666427295aa588a493fee3db4a52863e56f9189 | [
"WTFPL"
] | 18 | 2015-10-21T13:20:49.000Z | 2021-02-22T21:26:02.000Z | README.md | migolovanov/lua-cbson | b666427295aa588a493fee3db4a52863e56f9189 | [
"WTFPL"
] | 6 | 2018-11-08T21:19:03.000Z | 2019-08-19T19:10:14.000Z | README.md | migolovanov/lua-cbson | b666427295aa588a493fee3db4a52863e56f9189 | [
"WTFPL"
] | 12 | 2016-11-20T02:16:10.000Z | 2022-01-27T09:49:43.000Z | # Lua-cbson
Lua bindings to MongoDB's libbson
## Table of Contents
* [FAQ](#faq)
* [Requirements](#requirements)
* [Installation](#installation)
* [Usage](#usage)
* [Authors](#authors)
* [Copyright and License](#copyright-and-license)
## FAQ
* Q: Is it compatible with cjson?
A: Hell no. All bson subtypes are defined as userdata. Use cbson.to_json and cbson.from_json
* Q: What about integers?
A: Lua, prior to 5.3 stores all numbers as double. So, cbson.encode({foo = 10}) will yield double bson type.
Use cbson.int datatype. It will automaticaly yield int32 or int64 depending on value.
## Requirements
* Lua (5.1/5.2) or LuaJit
* Cmake 2.8.12 or later
* Working C compiler
* libbson 1.7 or later
## Installation
### Manual
As easy as
```bash
mkdir build
cd build
cmake ..
make
make install
```
You can also use `make unittest` after make to run tests.
By default module compiles with support for luajit
For other Lua interpreters see cmake options.
### LuaRocks
Via rockspec-file:
```bash
luarocks install https://raw.githubusercontent.com/isage/lua-cbson/master/rockspec/lua-cbson-git-1.rockspec
```
use specific lua version or luajit
```bash
luarocks --lua-dir=/usr/local/opt/openresty/luajit install https://raw.githubusercontent.com/isage/lua-cbson/master/rockspec/lua-cbson-git-1.rockspec
```
See all available versions of lua-bson in [./rockspec](rockspec directory).
## Usage
### Synopsis
```lua
local cbson = require "cbson"
local table_data = cbson.decode(bson_data)
local bson_data = cbson.encode(table_data)
local json_string = cbson.to_json(bson_data)
local json_string = cbson.to_relaxed_json(bson_data)
local bson_data = cbson.from_json(json_string)
```
### Compatibility with cjson array metatables
`cjson` (2.1.0.5 and higher) uses metatable for set table (especially empty) as arrays, so this library can use this (or other)
metatable for encoding and decoding arrays. See [usage array metatables example](test/using_cjson_array_mt.lua)
### CBSON Functions
#### `<table>decoded = cbson.decode(<binary>bson_data)`
Decodes binary BSON data to lua table.
#### `<binary>bson_data = cbson.encode(<table>data)`
Encodes lua table to binary BSON data.
```lua
local cbson = require "cbson"
-- Encodes lua table
local bson_data = cbson.encode({foobar = {bar = "hello", foo = "world"}})
print(cbson.to_json(bson_data)) -- { "foobar" : { "foo" : "world", "bar" : "hello" } }
-- Encodes lua table containing bson data
local bson_data = cbson.encode({foobar = cbson.from_json('{"bar":"hello","foo":"world"}')})
print(cbson.to_json(bson_data)) -- { "foobar" : { "bar" : "hello", "foo" : "world" } }
```
#### `<binary>bson_data = cbson.encode_first(<string>first_key, <table>data)`
Encodes lua table to binary BSON data, putting first_key value at start of bson.
(required for mongodb commands)
Make sure, that given key exists, otherwise it'll add this key with NULL value.
#### `<binary>bson_data = cbson.from_json(<string>json)`
Encodes json string as binary BSON data.
#### `<string>json_data = cbson.to_json(<binary>bson_data)`
Encodes binary BSON data as json string.
#### `<string>json_data = cbson.to_relaxed_json(<binary>bson_data)`
Encodes binary BSON data as [relaxed json](https://github.com/mongodb/specifications/blob/master/source/extended-json.rst#relaxed-extended-json-example) string.
### Embed datatypes
#### `cbson.regex(<string>regex, <string>options)`
```lua
local regex = cbson.regex("foo|bar","ism")
print( regex:regex() )
regex:regex("bar|foo")
regex:options("im")
print( regex:options() )
```
#### `cbson.oid(<string>oid) or cbson.oid(<oid>oid)`
Unique object id with 24 hex numbers.
```lua
local oid = cbson.oid("1234567890ABCDEF01234567")
local oid2 = cbson.oid(oid)
```
Get time from `oid` (first 8 hex numbers):
```lua
local timestamp = oid:timestamp()
print(timestamp) -- 305419896
```
#### `cbson.binary(<string>base64_encoded_data[, <int> type])`
```lua
local binary = cbson.binary("ZGVhZGJlZWY=")
print( binary:raw() ) -- returns raw binary data "deadbeef"
binary:set_raw("hello") -- binary:raw("hello") works fine
print( binary:data() ) -- returns base64 encoded data "aGVsbG8="
binary:set_data("ZGVhZGJlZWY=")
```
Maximum size of binary string is `4,294,967,295` bytes.
#### `cbson.symbol(<string>symbol)`
```lua
local symbol = cbson.symbol("something")
```
#### `cbson.code(<string>code)`
```lua
local code = cbson.code("code")
```
#### `cbson.codewscope(<string>code)`
Scopes are not supported yet.
```lua
local code = cbson.codewcope("code")
```
#### `cbson.undefined()`
```lua
local undef = cbson.undefined()
```
#### `cbson.null()`
```lua
local null = cbson.null()
```
#### `cbson.array()`
```lua
local empty_array = cbson.array()
```
#### `cbson.minkey()`
```lua
local minkey = cbson.minkey()
```
#### `cbson.maxkey()`
```lua
local maxkey = cbson.maxkey()
```
#### `cbson.ref(<string>ref, <string>id)`
```lua
local ref = cbson.ref("foo", "123456789012345678901234")
print( ref:ref() )
ref:ref("bar")
ref:id("432109876543210987654321")
```
#### `cbson.timestamp(<number>timestamp, <number>increment)`
BSON has a special [`timestamp`](https://docs.mongodb.com/manual/reference/bson-types/#timestamps) type for _internal_
MongoDB use and is not associated with the regular `date` type.
```lua
local timestamp = cbson.timestamp(100,1000)
timestamp:timestamp(500)
print( timestamp:timestamp() ) -- 500
timestamp:increment(100500)
print( timestamp:increment() ) -- 100500
```
#### `cbson.int(<number>value) or cbson.int(<int>value) or cbson.int(<string>value)`
That's basically int64. It supports all arithmetic operations.
Due to nature of lua numbers, you can pass big (> 2^53) numbers only as string.
It also have __tostring metamethod for opposite operation.
There's also helper methods `int_to_raw/uint_to_raw(<int>value, <number>bytes, <bool>big_endian)`
and `raw_to_int/raw_to_uint(<string>data, <bool>big_endian)`
for converting between number and in-memory representation.
```lua
local int = cbson.int(10)
print(int) -- 10
local int = cbson.int("100")
print(int) -- 100
local int = cbson.int("100")
print(int:number() + 20) -- 120
local int = cbson.int(10)
local int2 = cbson.int(int)
print(int2) -- 10
```
#### `cbson.uint(<number>value) or cbson.uint(<uint>value) or cbson.uint(<string>value)`
See cbson.int. They are same (except sign), and you can init one from another.
#### `cbson.date(<number>value) or cbson.date(<date>value) or cbson.date(<string>value)`
BSON Date is a 64-bit integer that represents the number of milliseconds since the Unix epoch (Jan 1, 1970).
This results in a representable date range of about 290 million years into the past and future.
#### `cbson.decimal(<string>value)`
Since version `1.1`.
It's [decimal128](https://github.com/mongodb/specifications/blob/master/source/bson-decimal128/decimal128.rst).
The Decimal128 supports 34 decimal digits of precision,
a max value of approximately `10^6145`, and min value of approximately `-10^6145`
```lua
local dec = cbson.decimal("1.0")
print(dec) -- 1.0
local dec = cbson.decimal("0.0005")
print(dec) -- 0.0005
```
## Authors
Epifanov Ivan <isage.dna@gmail.com>
[Back to TOC](#table-of-contents)
## Copyright and License
This module is licensed under the WTFPL license.
(See LICENSE)
| 24.894915 | 160 | 0.709423 | eng_Latn | 0.685118 |
a113d4f6f4867250aee9eb91e8b236ed91860ad5 | 744 | md | Markdown | new-docs/puppeteer.protocol.security.setoverridecertificateerrorsrequest.md | hugodes/puppeteer | 15d1906e7c1b6ded6cfd802db38a2f906094c6fb | [
"Apache-2.0"
] | 1 | 2020-08-08T18:56:31.000Z | 2020-08-08T18:56:31.000Z | new-docs/puppeteer.protocol.security.setoverridecertificateerrorsrequest.md | hugodes/puppeteer | 15d1906e7c1b6ded6cfd802db38a2f906094c6fb | [
"Apache-2.0"
] | 1 | 2020-10-06T18:53:37.000Z | 2020-10-06T18:53:37.000Z | new-docs/puppeteer.protocol.security.setoverridecertificateerrorsrequest.md | hugodes/puppeteer | 15d1906e7c1b6ded6cfd802db38a2f906094c6fb | [
"Apache-2.0"
] | 1 | 2020-09-14T04:23:23.000Z | 2020-09-14T04:23:23.000Z | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [puppeteer](./puppeteer.md) > [Protocol](./puppeteer.protocol.md) > [Security](./puppeteer.protocol.security.md) > [SetOverrideCertificateErrorsRequest](./puppeteer.protocol.security.setoverridecertificateerrorsrequest.md)
## Protocol.Security.SetOverrideCertificateErrorsRequest interface
<b>Signature:</b>
```typescript
export interface SetOverrideCertificateErrorsRequest
```
## Properties
| Property | Type | Description |
| --- | --- | --- |
| [override](./puppeteer.protocol.security.setoverridecertificateerrorsrequest.override.md) | boolean | If true, certificate errors will be overridden. |
| 39.157895 | 256 | 0.731183 | eng_Latn | 0.326364 |
a114a9979e488775fb6774661514592c3af3fc1d | 9,130 | md | Markdown | kinks/level4/numerical_mathematics/README.md | zubmic/REPL | 2946623d0efe5369163d4ecc5dfb69242bcf7951 | [
"MIT"
] | null | null | null | kinks/level4/numerical_mathematics/README.md | zubmic/REPL | 2946623d0efe5369163d4ecc5dfb69242bcf7951 | [
"MIT"
] | null | null | null | kinks/level4/numerical_mathematics/README.md | zubmic/REPL | 2946623d0efe5369163d4ecc5dfb69242bcf7951 | [
"MIT"
] | null | null | null | [Go back to the main page](https://world-class.github.io/REPL/)
# Table of contents
<!-- vim-markdown-toc GFM -->
* [Numerical Mathematics - Reported problems](#numerical-mathematics---reported-problems)
* [Week 1](#week-1)
* [Video: 1.001 Introduction to number bases and modular arithmetic](#video-1001-introduction-to-number-bases-and-modular-arithmetic)
* [Video: 1.101 Introduction to number bases](#video-1101-introduction-to-number-bases)
* [Video: 1.107 Place value for fractional numbers: binary](#video-1107-place-value-for-fractional-numbers-binary)
* [Practice quiz: 1.110 Rational and irrational numbers: decimal and binary](#practice-quiz-1110-rational-and-irrational-numbers-decimal-and-binary)
* [Week 2](#week-2)
* [Video: 1.401 Octal and hexadecimal (integer)](#video-1401-octal-and-hexadecimal-integer)
* [Practice quiz: 1.404 Translate between decimal and hexadecimal or octal (fractional)](#practice-quiz-1404-translate-between-decimal-and-hexadecimal-or-octal-fractional)
* [Video: 1.405 Special relationship between binary and hexadecimal, and binary and octal](#video-1405-special-relationship-between-binary-and-hexadecimal-and-binary-and-octal)
* [Practice quiz: 1.406 Translate between binary and hexadecimal/octal](#practice-quiz-1406-translate-between-binary-and-hexadecimaloctal)
* [Practice quiz: 1.602 Arithmetic in hexadecimal/octal](#practice-quiz-1602-arithmetic-in-hexadecimaloctal)
* [Week 3](#week-3)
* [Lesson 1.10: Video 1.1006 Mod, rem and division](#lesson-110-video-11006-mod-rem-and-division)
* [Lesson 1.11: Video 1.1101 Encryption using modular arithmetic](#lesson-111-video-11101-encryption-using-modular-arithmetic)
* [Week 4](#week-4)
* [Lesson 2.1: Video 2.103 Defining sequences](#lesson-21-video-2103-defining-sequences)
* [Lesson 2.2: Video 2.201 Arithmetic progressions](#lesson-22-video-2201-arithmetic-progressions)
* [Week 5](#week-5)
* [Lesson 2.5: Video 2.502 Series: sums of terms of sequences; summation symbol: sigma notation](#lesson-25-video-2502-series-sums-of-terms-of-sequences-summation-symbol-sigma-notation)
* [Lesson 2.5: Video 2.509 Finite sums](#lesson-25-video-2509-finite-sums)
* [Lesson 2.6: Practice quiz: 2.602 Limits of sequences](#lesson-26-practice-quiz-2602-limits-of-sequences)
* [Summative quiz](#summative-quiz)
* [Week 6](#week-6)
* [Lesson 3.1: Video 3.101 Cartesian coordinates](#lesson-31-video-3101-cartesian-coordinates)
* [Lesson 3.2: Video 3.211 Plotting graphs by hand – reciprocal](#lesson-32-video-3211-plotting-graphs-by-hand--reciprocal)
* [Summative quiz](#summative-quiz-1)
* [Week 8](#week-8)
* [Summative quiz](#summative-quiz-2)
<!-- vim-markdown-toc -->
# Numerical Mathematics - Reported problems
This page is about the [numerical mathematics module](../../../modules/level_4/numerical_mathematics/).
## Week 1
### Video: 1.001 Introduction to number bases and modular arithmetic
- At 11:16, `(255, 255, 255)` is **white**, not blue.
### Video: 1.101 Introduction to number bases
- At 11:34: Wrong. Each column is a power of 60, so it should be times `1`, times `60` and times `3600`.
### Video: 1.107 Place value for fractional numbers: binary
- At 0:37: The "fractional point" is called "radix point".
### Practice quiz: 1.110 Rational and irrational numbers: decimal and binary
- Answers should be given without spaces.
- When a repeating fractional part is present, the answer should be written as `i.rr...`, where `i` stands for **integer part**, `r` is the **repeating** fraction and one must include three dots at the end. Example:
3.12121212121212
is written as
3.1212...
## Week 2
### Video: 1.401 Octal and hexadecimal (integer)
- In the quiz at 3:41, the place values are supposed to be entered as "1, 16, 256". The answer isn't accepted.
- In the quiz at 4:24, 65536 should be written as 2^(16), but the "6" isn't part of the exponent part.
- At 5:07, second letter in hexadecimal should be "B", not "D".
- At 6:01, the hexadecimal number `11F` should have an expansion starting with `1 × 16^2`, not `1 × 16 (base 2)` as displayed.
- In the quiz at 6:29, the third answer is 256, not 64. The last part is asking in the quiz for multiples in binary while the answer is given for hexadecimal.
### Practice quiz: 1.404 Translate between decimal and hexadecimal or octal (fractional)
- `3.44` in octal is `3 + 1/2 + 1/16`, not `3 + 1/2 + 1/32`.
- Options may present groupings of numbers. If a grouping is supposed to be of **3** digits for instance and you're presented with **4** digits, assume that the last digit should be in subscript (representing the number base, such as **2** for binary or **8** for octal) so that it makes sense when reading. In a grouping of 3 digits, `0002` should be interpreted as `000`, base `2`.
### Video: 1.405 Special relationship between binary and hexadecimal, and binary and octal
- At 7:38, this is wrong. `C` (base 16) = 12 (base 10) = 1100 (base 2), not 1101.
- At 11:24, The grouping of digits is wrong.
1.001.111 1
in binary should read
1 001.111 1
having only one radix point.
- At 11:37, it is said the answer is `11.71` (base 8). Wrong: It's `11.74` (base 8).
### Practice quiz: 1.406 Translate between binary and hexadecimal/octal
- Question 6: `73.06` (base 8) *is* `111011.00011` in binary.
### Practice quiz: 1.602 Arithmetic in hexadecimal/octal
- `6D * 60` in hexadecimal is `28E0`.
- `6C * 3B` in hexadecimal is `18E4`.
## Week 3
### Lesson 1.10: Video 1.1006 Mod, rem and division
- At 1:49, the expression isn't rendered properly (the congruence symbol doesn't appear). Subsequent expressions also present this issue.
### Lesson 1.11: Video 1.1101 Encryption using modular arithmetic
- The video contains many display errors that are fixed in a previously uploaded version. While not being flawless, it's much better. For now, the video can be downloaded [from this link](https://www.dropbox.com/s/w52vpsau7ly6tc6/1_1101_Encryption_using_modular_arithmetic.mp4?dl=1). If you want to add subtitles, you can [download them here](https://www.dropbox.com/s/5hso65rut3u337q/1_1101_subtitles-en.vtt?dl=1).
- If you don't know how to add the subtitles to the video, try with [VLC media player](https://www.videolan.org/vlc/) (free): open the video (`1_1101_Encryption_using_modular_arithmetic.mp4`) and from VLC, click at the top on `Subtitle`, then on `Add Subtitle File...` and open the subtitles file (`1_1101_subtitles-en.vtt`). They will automatically be added and synced to the video.
- At 3:43, a banner appears in the background and has nothing to do with was it being taught.
- At 4:40 and 4:52, the congruence symbol is not rendered properly:
C ≡ M^e (mod p)
- At 6:04, it should be `C^7 (mod 11)`, not `C^3 (mod 11)`.
- At 8:43, the equation appears in the background and can't be read. The equation is:
ed = 3 × 7 is 21
- At 11:28, again the expression can't be read. The expression is:
a^p ≡ a (mod p)
## Week 4
### Lesson 2.1: Video 2.103 Defining sequences
- Audio is out of sync from 15:19 onward: please refer to the transcript to better follow along.
### Lesson 2.2: Video 2.201 Arithmetic progressions
**Partially fixed**. The transcript and subtitles do not appear at this moment.
## Week 5
### Lesson 2.5: Video 2.502 Series: sums of terms of sequences; summation symbol: sigma notation
- At 20:38, the number `32` was skipped when calculating the sum of the series.
### Lesson 2.5: Video 2.509 Finite sums
- At 10:11, the summation for the term `k^2` is omitted.
### Lesson 2.6: Practice quiz: 2.602 Limits of sequences
- Question 1: There is no clear way to indicate that there is no limit or what the considered interval really is.
### Summative quiz
- Question 2: The quiz does not accept the valid answer and tells the user that the wrong answer is correct instead.
## Week 6
### Lesson 3.1: Video 3.101 Cartesian coordinates
- There is no sound. For now, you can download the video [from this link](https://www.dropbox.com/s/922gj1vefoedx0y/3_101_cartesian_coordinates.mp4?dl=1). You can get the subtitles [from this link](https://www.dropbox.com/s/arvg0fuu7867vnl/3_101_subtitles-en.vtt?dl=1).
- If you don't know how to add the subtitles to the video, try with [VLC media player](https://www.videolan.org/vlc/) (free): open the video (`3_101_cartesian_coordinates.mp4`) and from VLC, click at the top on `Subtitle`, then on `Add Subtitle File...` and open the subtitles file (`3_101_subtitles-en.vtt`). They will automatically be added and synced to the video.
### Lesson 3.2: Video 3.211 Plotting graphs by hand – reciprocal
- There is no sound nor visual guidance from 8:16 till 8:35.
### Summative quiz
- No formatting seems appropriate to answer question 2. None of the following is accepted: `inf`, `infinity`, `infty`.
## Week 8
### Summative quiz
- The quiz doesn't let the student see what the mistakes are once the quiz has been submitted.
| 59.673203 | 415 | 0.717306 | eng_Latn | 0.974473 |
a1158d321f59659340446981758ed61227c07d5f | 382 | md | Markdown | _posts/2014/2014-09-01-kein-neuzugang-mehr.md | eintracht-stats/eintracht-stats.github.io | 9d1cd3d82bff1b70106e3b5cf3c0da8f0d07bb43 | [
"MIT"
] | null | null | null | _posts/2014/2014-09-01-kein-neuzugang-mehr.md | eintracht-stats/eintracht-stats.github.io | 9d1cd3d82bff1b70106e3b5cf3c0da8f0d07bb43 | [
"MIT"
] | 1 | 2021-04-01T17:08:43.000Z | 2021-04-01T17:08:43.000Z | _posts/2014/2014-09-01-kein-neuzugang-mehr.md | eintracht-stats/eintracht-stats.github.io | 9d1cd3d82bff1b70106e3b5cf3c0da8f0d07bb43 | [
"MIT"
] | null | null | null | ---
layout: post
title: "Kein Neuzugang mehr"
---
Ohne weiteren Neuzugang und damit ohne Ersatz für Nelson Valdez wird die Eintracht die Hinrunde der Saison absolvieren. Heute schloss das Transferfenster und bis auf den schon bereits feststehenden Wechsel von Slobodan Medojevic gab es heute nichts mehr zu vermelden. Der Ausfall des Paraguayers soll intern aufgefangen werden.
| 38.2 | 327 | 0.808901 | deu_Latn | 0.999333 |
a115b7a3d6dffe291cb0edec1ba24aefe815c389 | 2,878 | md | Markdown | README.md | abdelhamidbakhta/smartgiveaway | 1f30254fc22555bea186b7076c23bb22d3f9d186 | [
"Apache-2.0"
] | null | null | null | README.md | abdelhamidbakhta/smartgiveaway | 1f30254fc22555bea186b7076c23bb22d3f9d186 | [
"Apache-2.0"
] | 1 | 2020-12-10T10:53:20.000Z | 2020-12-10T10:53:20.000Z | README.md | abdelhamidbakhta/smartgiveaway | 1f30254fc22555bea186b7076c23bb22d3f9d186 | [
"Apache-2.0"
] | 1 | 2020-12-10T10:49:36.000Z | 2020-12-10T10:49:36.000Z | [](https://github.com/abdelhamidbakhta/smartgiveaway/actions)
[](https://github.com/abdelhamidbakhta/smartgiveaway/blob/master/LICENSE)
[![sonar-quality-gate][sonar-quality-gate]][sonar-url] [![sonar-bugs][sonar-bugs]][sonar-url] [![sonar-vulnerabilities][sonar-vulnerabilities]][sonar-url]
# Smart Giveaway
[Build On XDai: Applications & Bridges GR8 Hackathon](https://gitcoin.co/issue/xdaichain/site/9/100024347)
[](https://www.youtube.com/watch?v=waZJNSGPKzE)
## Online Demo
Try it on your own! (Need xDai on mainnet)
[Online Demo](http://smartgiveaway.surge.sh/)
As part of the Gitcoin Hackathon we are building a Giveaway platform (similar to twitter giveaways).
This is a Proof Of Concept aiming to use `xDai` technology to build innovative features on top of an Ethereum smart contract solution.
## Use case
An operator can create give away with on-chain winner selection.
In order to achieve that we are using the xDai on-chain RNG based on `RANDAO`.
For the demonstration we target `RandomAuRaProxy` deployed at `0x5870b0527DeDB1cFBD9534343Feda1a41Ce47766`.
The `GiveAway` contract uses `IPOSDAORandom` to select the winner among the candidates.
A seed is retrieved with `currentSeed` method, allowing us to have a verifiable random number generated on chain.
## Architecture
We have 3 main components:
- SmartGiveaway smart contract
- Front-End web application
- Back-End service
### SmartGiveAway smart contract
Project is using [OpenZeppelin CLI](https://docs.openzeppelin.com/cli/2.7/) and is fully compatible with Truffle based projects.
#### Compile
```shell script
npx oz compile
```
### Front-End web application
#### Project setup
```
npm install
```
#### Compiles and hot-reloads for development
```
npm run serve
```
#### Compiles and minifies for production
```
npm run build
# Static site is generate to: ./dist
```
#### Lints and fixes files
```
npm run lint
```
#### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).
### Back-End service
[See instructions.](https://github.com/abdelhamidbakhta/smartgiveaway-backend)
[Online Open API specification](https://smartgiveaway.herokuapp.com/)
[sonar-url]: https://sonarcloud.io/dashboard?id=abdelhamidbakhta_smartgiveaway
[sonar-quality-gate]: https://sonarcloud.io/api/project_badges/measure?project=abdelhamidbakhta_smartgiveaway&metric=alert_status
[sonar-bugs]: https://sonarcloud.io/api/project_badges/measure?project=abdelhamidbakhta_smartgiveaway&metric=bugs
[sonar-vulnerabilities]: https://sonarcloud.io/api/project_badges/measure?project=abdelhamidbakhta_smartgiveaway&metric=vulnerabilities
| 35.975 | 180 | 0.776581 | eng_Latn | 0.613473 |
a1160be175d46e595468d6377389ada6a5e0c097 | 4,127 | md | Markdown | doc/examples.md | ExecutableBookProject/markup_test_cases | cabd2a10883f46e44f1bdb4c3294c3cd4b1e9d5a | [
"BSD-3-Clause"
] | null | null | null | doc/examples.md | ExecutableBookProject/markup_test_cases | cabd2a10883f46e44f1bdb4c3294c3cd4b1e9d5a | [
"BSD-3-Clause"
] | 6 | 2020-02-10T01:41:06.000Z | 2020-02-15T12:11:21.000Z | doc/examples.md | ExecutableBookProject/markup_test_cases | cabd2a10883f46e44f1bdb4c3294c3cd4b1e9d5a | [
"BSD-3-Clause"
] | 1 | 2020-02-13T19:23:06.000Z | 2020-02-13T19:23:06.000Z | # Example syntax for myst
As a base, Myst adheres to the [CommonMark specification](https://spec.commonmark.org/).
For this, it uses the [Mistletoe project](https://github.com/miyuchina/mistletoe),
which is a well-structured markdown parser for Python that is CommonMark-compliant
and also extensible.
Myst adds several new syntax options that extend its functionality to be used
with Sphinx, the documentation generation engine used extensively in the Python
ecosystem. Sphinx uses reStructuredText by default, which is both more
powerful than Markdown, and also (arguably) more complex to use.
This project is an attempt to have the best of both worlds: the flexibility
and extensibility of Sphinx with the simplicity and readability of Markdown.
Here are a few major extensions from the CommonMark flavor of markdown
# Directives - a block-level extension point
Directives syntax is defined with triple-backticks and curly-brackets. It
is effectively a code block with curly brackets around the language, and
a directive name in place of a language name. It is similar to how RMarkdown
defines "runnable cells". Here is the basic structure
````
```{directivename} Directive arguments
---
optional: yaml
keyval: parameterization
---
My directive content.
```
````
For example, the following code:
````
```{admonition} This is my admonition
This is my note
```
````
Will generate this admonition:
```{admonition} This is my admonition
This is my note
```
For directives that are meant to parse content for your site, you may use
markdown as the markup language inside...
````
```{admonition} My markdown link
Here is [markdown link syntax](https://jupyter.org)
```
````
```{admonition} My markdown link
Here is [markdown link syntax](https://jupyter.org)
```
## Parameterizing directives
For directives that take parameters as input, you may parameterize them by
beginning your directive content with YAML frontmatter. This needs to be
surrounded by `---` lines. Everything in between will be parsed by YAML and
passed as keyword arguments to your directive. For example:
````
```{code-block} python
---
lineno-start: 10
emphasize-lines: 1, 3
caption: |
This is my
multi-line caption. It is *pretty nifty* ;-)
---
a = 2
print('my 1st line')
print(f'my {a}nd line')
```
````
```{code-block} python
---
lineno-start: 10
emphasize-lines: 1, 3
caption: |
This is my
multi-line caption. It is *pretty nifty* ;-)
---
a = 2
print('my 1st line')
print(f'my {a}nd line')
```
## Nesting directives
You can nest directives by ensuring that the ticklines corresponding to the
outermost directive are longer than the ticklines for the inner directives.
For example, nest a warning inside a note block like so:
`````
````{note}
The next info should be nested
```{warning}
Here's my warning
```
````
`````
Here's how it looks rendered:
````{note}
The next info should be nested
```{warning}
Here's my warning
```
````
This can really be abused if you'd like ;-)
``````{note}
The next info should be nested
`````{warning}
Here's my warning
````{admonition} Yep another admonition
```python
# All this fuss was about this boring python?!
print('yep!')
```
````
`````
``````
# Roles - an in-line extension point
Roles are similar to directives - they allow you to define arbitrary new
functionality in Sphinx, but they are use *in-line*. To define an in-line
role, use the following form:
```
{role-name}`role content`
```
For example, the following code:
```
Since Pythagoras, we know that {math}`a^2 + b^2 = c^2`
```
Becomes:
Since Pythagoras, we know that {math}`a^2 + b^2 = c^2`
You can use roles to do things like reference equations and other items in
your book. For example:
````
```{math} e^{i\pi} + 1 = 0
---
label: euler
---
```
Euler's identity, equation {math:numref}`euler`, was elected one of the
most beautiful mathematical formulas.
````
Becomes:
```{math} e^{i\pi} + 1 = 0
---
label: euler
---
```
```{todo}
Figure out why equation referencing didn't work
```
Euler's identity, equation {DOESN'T WORKeq}`euler`, was elected one of the
most beautiful mathematical formulas.
| 22.551913 | 88 | 0.717955 | eng_Latn | 0.99784 |
a1169168bcd48e280ca5d62f92e68da2a242aba2 | 305 | md | Markdown | content/runner/kubernetes/configuration/reference/drone-resource-request-cpu.md | phil-davis/docs | f3db0b46c949586e50a6323051d33362fb4518de | [
"BlueOak-1.0.0"
] | 151 | 2015-01-30T23:32:00.000Z | 2022-02-20T20:23:46.000Z | content/runner/kubernetes/configuration/reference/drone-resource-request-cpu.md | phil-davis/docs | f3db0b46c949586e50a6323051d33362fb4518de | [
"BlueOak-1.0.0"
] | 339 | 2015-01-04T05:21:48.000Z | 2022-03-26T07:08:04.000Z | content/runner/kubernetes/configuration/reference/drone-resource-request-cpu.md | phil-davis/docs | f3db0b46c949586e50a6323051d33362fb4518de | [
"BlueOak-1.0.0"
] | 386 | 2015-01-04T05:08:19.000Z | 2022-03-29T19:05:10.000Z | ---
date: 2000-01-01T00:00:00+00:00
title: DRONE_RESOURCE_REQUEST_CPU
author: bradrydzewski
weight: 1
---
Optional integer, sets the default millicpu resource request for all pipeline steps. This value maps to the `spec.containers[].resources.requests.cpu` field.
```
DRONE_RESOURCE_REQUEST_CPU=1000
``` | 25.416667 | 157 | 0.780328 | eng_Latn | 0.445032 |
a117adffab24dee555e28906ab8e1bbf990a81e6 | 3,133 | md | Markdown | docs/extensibility/debugger/reference/context-info.md | Jteve-Sobs/visualstudio-docs.de-de | 59bd3c5d2776a76ef8d28407c5cc97efc9e72f84 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/debugger/reference/context-info.md | Jteve-Sobs/visualstudio-docs.de-de | 59bd3c5d2776a76ef8d28407c5cc97efc9e72f84 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-07-24T14:57:38.000Z | 2020-07-24T14:57:38.000Z | docs/extensibility/debugger/reference/context-info.md | angelobreuer/visualstudio-docs.de-de | f553469c026f7aae82b7dc06ba7433dbde321350 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: CONTEXT_INFO | Microsoft Docs
ms.date: 11/04/2016
ms.topic: reference
f1_keywords:
- CONTEXT_INFO
helpviewer_keywords:
- CONTEXT_INFO structure
ms.assetid: 6b513f4e-e7b0-4969-adf0-2205ccc1e09b
author: acangialosi
ms.author: anthc
manager: jillfra
ms.workload:
- vssdk
dev_langs:
- CPP
- CSharp
ms.openlocfilehash: 4838df34c14b936af15b8a7a582a6d30ea12bee1
ms.sourcegitcommit: 16a4a5da4a4fd795b46a0869ca2152f2d36e6db2
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 04/06/2020
ms.locfileid: "80737567"
---
# <a name="context_info"></a>CONTEXT_INFO
Diese Struktur beschreibt einen Speicherkontext oder Codekontext.
## <a name="syntax"></a>Syntax
```cpp
typedef struct _tagCONTEXT_INFO {
CONTEXT_INFO_FIELDS dwFields;
BSTR bstrModuleUrl;
BSTR bstrFunction;
TEXT_POSITION posFunctionOffset;
BSTR bstrAddress;
BSTR bstrAddressOffset;
BSTR bstrAddressAbsolute;
} CONTEXT_INFO;
```
```csharp
public struct CONTEXT_INFO {
public uint dwFields;
public string bstrModuleUrl;
public string bstrFunction;
public TEXT_POSITION posFunctionOffset;
public string bstrAddress;
public string bstrAddressOffset;
public string bstrAddressAbsolute;
};
```
## <a name="members"></a>Member
`dwFields`\
Eine Kombination von Flags aus der CONTEXT_INFO_FIELDS-Enumeration, die angibt, welche Felder ausgefüllt<strong>werden.</strong> [CONTEXT_INFO_FIELDS](../../../extensibility/debugger/reference/context-info-fields.md)
`bstrModuleUrl`\
Der Name des Moduls, in dem sich der Kontext befindet.
`bstrFunction`\
Der Funktionsname, in dem sich der Kontext befindet.
`posFunctionOffset`\
Eine [TEXT_POSITION](../../../extensibility/debugger/reference/text-position.md) Struktur, die den Zeilen- und Spaltenversatz der Funktion identifiziert, die dem Codekontext zugeordnet ist.
`bstrAddress`\
Die Adresse im Code, an der sich der angegebene Kontext befindet.
`bstrAddressOffset`\
Der Offset der Adresse im Code, in dem sich der angegebene Kontext befindet.
`bstrAddressAbsolute`\
Die absolute Adresse im Speicher, an der sich der angegebene Kontext befindet.
## <a name="remarks"></a>Bemerkungen
Diese Struktur wird von einem Aufruf der [GetInfo-Methode](../../../extensibility/debugger/reference/idebugmemorycontext2-getinfo.md) zurückgegeben.
Eine typische Verwendung für diese Struktur **Memory** wird in Unterstützung eines Speicherdebugfensters verwendet.
## <a name="requirements"></a>Requirements (Anforderungen)
Kopfzeile: msdbg.h
Namespace: Microsoft.VisualStudio.Debugger.Interop
Assembly: Microsoft.VisualStudio.Debugger.Interop.dll
## <a name="see-also"></a>Weitere Informationen
- [Structures and Unions](../../../extensibility/debugger/reference/structures-and-unions.md)
- [GetInfo](../../../extensibility/debugger/reference/idebugmemorycontext2-getinfo.md)
- [CONTEXT_INFO_FIELDS](../../../extensibility/debugger/reference/context-info-fields.md)
- [TEXT_POSITION](../../../extensibility/debugger/reference/text-position.md)
| 33.688172 | 216 | 0.748165 | deu_Latn | 0.519872 |
a117f02c857dd2ae46261c4b34267ca98ca4fb0c | 20,939 | md | Markdown | entries/tocs/_macos.md | Bollos00/opensourcegames | b94aeac3cd96bd3caed121fa1880e21eaca571b3 | [
"CC0-1.0"
] | null | null | null | entries/tocs/_macos.md | Bollos00/opensourcegames | b94aeac3cd96bd3caed121fa1880e21eaca571b3 | [
"CC0-1.0"
] | null | null | null | entries/tocs/_macos.md | Bollos00/opensourcegames | b94aeac3cd96bd3caed121fa1880e21eaca571b3 | [
"CC0-1.0"
] | null | null | null | [comment]: # (autogenerated content, do not edit)
# macOS
- **[0 A.D.](../0_ad.md)** (C, C++, JavaScript, GPL-2.0, beta)
- **[3D Pong](../3d_pong.md)** (C, GPL-2.0, beta, inactive since 2004)
- **[4D Maze Game](../4d_maze_game.md)** (Java, Public domain, mature, inactive since 2008)
- **[4D-TRIS](../4d-tris.md)** (C, GPL-2.0, mature, inactive since 2012)
- **[Abe's Amazing Adventure](../abes_amazing_adventure.md)** (C, GPL-2.0, mature, inactive since 2005)
- **[AdaGate](../adagate.md)** (Ada, GPL-3.0, mature)
- **[Aleph One](../aleph_one.md)** (C++, Lua, GPL-3.0, mature)
- **[Alex the Allegator 4](../alex_the_allegator_4.md)** (C, GPL-2.0, mature, inactive since 2003)
- **[Ambermoon.net](../ambermoonnet.md)** (C#, GPL-3.0, mature)
- **[AntiChess](../antichess.md)** (Java, MIT, beta, inactive since 2003)
- **[Armory](../armory.md)** (Haxe, Python, zlib, mature)
- **[AssaultCube](../assaultcube.md)** (C, C++, Custom, mature, inactive since 2018)
- **[Augustus](../augustus.md)** (C, C++, AGPL-3.0, mature)
- **[Azimuth](../azimuth.md)** (C, GPL-3.0, mature)
- **[Battle Tanks](../battle_tanks.md)** (C++, GPL-2.0, mature, inactive since 2009)
- **[Biniax](../biniax.md)** (C, zlib, mature, inactive since 2012)
- **[Bitfighter](../bitfighter.md)** (C, C++, GPL-2.0, mature)
- **[Black Shades](../black_shades.md)** (C, GPL-3.0, mature)
- **[Bladecoder Adventure Engine](../bladecoder_adventure_engine.md)** (Java, Apache-2.0, mature)
- **[Blitwizard](../blitwizard.md)** (C, C++, Lua, zlib, beta, inactive since 2015)
- **[Blobby Volley 2](../blobby_volley_2.md)** (C++, GPL-2.0, mature, inactive since 2017)
- **[Bombic](../bombic.md)** (C++, Objective-C, GPL-2.0, beta, inactive since 2005)
- **[Brain Workshop](../brain_workshop.md)** (Python, GPL-2.0, mature, inactive since 2011)
- **[Brogue](../brogue.md)** (C, AGPL-3.0, mature)
- **[BZFlag](../bzflag.md)** (C++, LGPL-2.1, MPL-2.0, mature)
- **[C-Dogs SDL](../c-dogs_sdl.md)** (C, GPL-2.0, mature)
- **[CaesarIA](../caesaria.md)** (C++, JavaScript, C, GPL-3.0, beta)
- **[Cartographer](../cartographer.md)** (GDScript, Apache-2.0, mature)
- **[Cataclysm: Dark Days Ahead](../cataclysm_dark_days_ahead.md)** (C++, CC-BY-SA-3.0, mature)
- **[CaveExpress](../caveexpress.md)** (C, JavaScript, GPL-3.0, mature)
- **[CETech](../cetech.md)** (C, C++, CC0, beta)
- **[Chocolate Doom](../chocolate_doom.md)** (C, GPL-2.0, mature)
- **[Chunk Stories](../chunk_stories.md)** (Kotlin, Java, LGPL-3.0, beta)
- **[Circus Linux!](../circus_linux.md)** (C, GPL-2.0, mature, inactive since 2000)
- **[Citybound](../citybound.md)** (Rust, JavaScript, AGPL-3.0, beta)
- **[ClassiCube](../classicube.md)** (C, 3-clause BSD, mature)
- **[Colditz Escape](../colditz_escape.md)** (C, GPL-3.0, mature)
- **[CoTerminalApps](../coterminalapps.md)** (Ada, GPL-3.0, mature)
- **[Craft](../craft.md)** (C, Python, MIT, mature, inactive since 2017)
- **[CrossUO](../crossuo.md)** (C, C++, GPL-3.0, mature)
- **[Crystal Space 3D SDK](../crystal_space_3d_sdk.md)** (C, C++, LGPL-2.1, mature, inactive since 2015)
- **[Cultivation](../cultivation.md)** (C++, Public domain, mature, inactive since 2010)
- **[Cytadela](../cytadela.md)** (C++, GPL-3.0, beta, inactive since 2013)
- **[D2X-XL](../d2x-xl.md)** (C++, Custom, GPL-2.0, mature, inactive since 2015)
- **[Daggerfall Unity](../daggerfall_unity.md)** (C#, MIT, mature)
- **[DarkPlaces](../darkplaces.md)** (C, GPL-2.0, mature, inactive since 2014)
- **[Dave Gnukem](../dave_gnukem.md)** (C++, GPL-2.0, mature)
- **[DeSmuME](../desmume.md)** (C, C++, GPL-2.0, mature, inactive since 2015)
- **[Destination Sol](../destination_sol.md)** (Java, Apache-2.0, mature)
- **[dhewm3](../dhewm3.md)** (C, C++, GPL-3.0, mature)
- **[Digital: A Love Story](../digital_a_love_story.md)** (Ren'Py, CC-BY-NC-SA-3.0, mature)
- **[dim3](../dim3.md)** (C, MIT, beta, inactive since 2014)
- **[Domination](../domination.md)** (Java, GPL-3.0, mature)
- **[Doom Legacy](../doom_legacy.md)** (C++, GPL-2.0, mature)
- **[Doom64EX](../doom64ex.md)** (C, C++, GPL-2.0, mature)
- **[Doomsday Engine](../doomsday_engine.md)** (C, C++, GPL-2.0, GPL-3.0, LGPL-3.0, mature)
- **[DreamChess](../dreamchess.md)** (C, GPL-3.0, beta)
- **[DRL](../drl.md)** (Lua, Pascal, GPL-2.0, mature)
- **[Duck Marines](../duck_marines.md)** (Lua, zlib, mature, inactive since 2016)
- **[Dungeon](../dungeon.md)** (Java, 3-clause BSD, mature)
- **[DwarfCorp](../dwarfcorp.md)** (C#, MIT, mature)
- **[Eat The Whistle](../eat_the_whistle.md)** (C, ?, mature, inactive since 2017)
- **[ECWolf](../ecwolf.md)** (C++, GPL-2.0, LGPL-2.1, zlib, MIT, IJG, Public domain, mature)
- **[ElonaFoobar](../elonafoobar.md)** (C++, Lua, MIT, mature)
- **[Emilia Pinball](../emilia_pinball.md)** (C++, GPL-2.0, beta)
- **[Enigma](../enigma.md)** (C, C++, GPL-2.0, mature)
- **[Escape Towards The Unknown](../escape_towards_the_unknown.md)** (C, GPL-2.0, beta, inactive since 2016)
- **[Esenthel Engine](../esenthel_engine.md)** (C, C++, Custom, beta)
- **[ET: Legacy](../et_legacy.md)** (C, C++, Lua, GPL-3.0, mature)
- **[Etterna](../etterna.md)** (C, C++, Lua, MIT, beta)
- **[ezEngine](../ezengine.md)** (C++, JavaScript, MIT, mature)
- **[ezQuake](../ezquake.md)** (C, C++, GPL-2.0, mature)
- **[F-1 Spirit](../f-1_spirit.md)** (C++, ?, beta, inactive since 2009)
- **[Fish Fillets - Next Generation](../fish_fillets-next_generation.md)** (C++, GPL-2.0, mature)
- **[Flare](../flare.md)** (C++, Java, Python, GPL-3.0, mature)
- **[FlightGear](../flightgear.md)** (C++, GPL-2.0, mature)
- **[flixel-gdx](../flixel-gdx.md)** (Java, 3-clause BSD, beta, inactive since 2017)
- **[FLTK Recycling Game!](../fltk_recycling_game.md)** (C++, LGPL-2.1, mature, inactive since 2014)
- **[Free Mars](../free_mars.md)** (Java, GPL-3.0, mature)
- **[freeablo](../freeablo.md)** (C++, GPL-3.0, beta)
- **[Freedoom](../freedoom.md)** (None, None, beta)
- **[Frets on Fire](../frets_on_fire.md)** (Python, GPL-2.0, mature, inactive since 2008)
- **[Frozen Bubble](../frozen_bubble.md)** (Perl, GPL-2.0, mature, inactive since 2012)
- **[Game Editor](../game_editor.md)** (C, C++, GPL-3.0, mature, inactive since 2014)
- **[GameCake](../gamecake.md)** (C, C++, Lua, MIT, mature)
- **[GamePlay](../gameplay3d.md)** (C++, Apache-2.0, mature, inactive since 2016)
- **[GBDK](../gbdk.md)** (C, Assembly, C++, MIT, mature)
- **[GCompris](../gcompris.md)** (C, Python, GPL-3.0, mature)
- **[Gem Drop X](../gem_drop_x.md)** (C, GPL-2.0, beta, inactive since 2002)
- **[Gideros](../gideros.md)** (C, C++, Lua, ?, mature)
- **[GL-117](../gl-117.md)** (C++, GPL-2.0, mature, inactive since 2005)
- **[GLEW](../glew.md)** (C, C++, Perl, 3-clause BSD, mature)
- **[GLtron](../gltron.md)** (C, ?, beta, inactive since 2017)
- **[GNU Chess](../gnu_chess.md)** (C++, GPL-3.0, mature, inactive since 2017)
- **[GNU FreeDink](../gnu_freedink.md)** (C, GPL-3.0, mature, inactive since 2012)
- **[GNU Go](../gnu_go.md)** (C, GPL-3.0, mature, inactive since 2011)
- **[Golly](../golly.md)** (C++, Java, GPL-2.0, mature)
- **[Gottet](../gottet.md)** (C++, GPL-3.0, mature)
- **[GPL Arcade Volleyball](../gpl_arcade_volleyball.md)** (C++, GPL-2.0, beta, inactive since 2006)
- **[Gravitation](../gravitation.md)** (C++, Public domain, mature, inactive since 2008)
- **[Grobots](../grobots.md)** (C++, GPL-2.0, mature, inactive since 2014)
- **[GTK](../gtk.md)** (C, LGPL-2.1, mature)
- **[GZDoom](../gzdoom.md)** (C, C++, GPL-3.0, mature)
- **[Hammer of Thyrion](../hammer_of_thyrion.md)** (C, GPL-2.0, mature)
- **[Hardwar](../hardwar.md)** (C++, GPL-3.0, beta, inactive since 2015)
- **[Harmonist: Dayoriah Clan Infiltration](../harmonist_dayoriah_clan_infiltration.md)** (Go, ISC, beta)
- **[HaxePunk](../haxepunk.md)** (Haxe, MIT, mature)
- **[HoDoKu](../hodoku.md)** (Java, GPL-3.0, mature, inactive since 2013)
- **[HyperRogue](../hyperrogue.md)** (C++, GPL-2.0, mature)
- **[I Have No Tomatoes](../i_have_no_tomatoes.md)** (C++, zlib, mature, inactive since 2004)
- **[Infinite Mario Bros](../infinite_mario_bros.md)** (Java, 3-clause BSD, mature, inactive since 2010)
- **[Infinite Tux](../infinite_tux.md)** (Java, GPL-3.0, Public domain, mature)
- **[INSTEAD](../instead.md)** (C, Lua, MIT, mature)
- **[Intersect](../intersect.md)** (C#, MIT, GPL-2.0, beta)
- **[Intricacy](../intricacy.md)** (Haskell, GPL-3.0, beta)
- **[ioquake3](../ioquake3.md)** (C, GPL-2.0, mature)
- **[iortcw](../iortcw.md)** (C, C++, GPL-3.0, mature)
- **[Jamp](../jamp.md)** (C++, GPL-3.0, beta, inactive since 2009)
- **[Javelin](../javelin.md)** (Java, GPL-2.0, mature, inactive since 2016)
- **[Jazz² Resurrection](../jazz_resurrection.md)** (C#, JavaScript, GPL-3.0, mature)
- **[JGame](../jgame.md)** (Java, 3-clause BSD, mature, inactive since 2012)
- **[JSoko](../jsoko.md)** (Java, GPL-3.0, mature)
- **[Jump Don't Die](../jump_dont_die.md)** (Java, GPL-3.0, mature)
- **[KevEdit](../kevedit.md)** (C, GPL-2.0, mature)
- **[kiki the nano bot](../kiki_the_nano_bot.md)** (C++, Public domain, mature, inactive since 2007)
- **[KlayGE](../klayge.md)** (C++, GPL-2.0, mature)
- **[Kobo Deluxe](../kobo_deluxe.md)** (C++, GPL-2.0, beta, inactive since 2007)
- **[Krank](../krank.md)** (Python, Public domain, beta, inactive since 2008)
- **[LGames](../lgames.md)** (C++, GPL-2.0, mature)
- **[LIKO-12](../liko-12.md)** (Lua, MIT, mature)
- **[LionEngine](../lionengine.md)** (Java, GPL-3.0, mature)
- **[Loon Game](../loon_game.md)** (Java, C#, Apache-2.0, beta)
- **[Love2dCS](../love2dcs.md)** (C#, C++, MIT, mature)
- **[Lugaru](../lugaru.md)** (C++, GPL-2.0, mature)
- **[Luola](../luola.md)** (C, GPL-2.0, mature, inactive since 2005)
- **[LÖVE](../love.md)** (C++, zlib, mature)
- **[Maelstrom](../maelstrom.md)** (C, C++, GPL-2.0, mature, inactive since 2002)
- **[ManaPlus](../manaplus.md)** (C, GPL-3.0, mature)
- **[Mari0](../mari0.md)** (Lua, MIT, mature, inactive since 2012)
- **[Maxit](../maxit.md)** (C++, 3-clause BSD, mature, inactive since 2014)
- **[Me and My Shadow](../me_and_my_shadow.md)** (C++, GPL-3.0, beta)
- **[MekWars](../mekwars.md)** (Java, GPL-2.0, mature)
- **[Metaforce](../metaforce.md)** (C, C++, MIT, beta)
- **[MicroWar 2.0](../microwar_20.md)** (Python, 3-clause BSD, mature, inactive since 2009)
- **[Minetest](../minetest.md)** (C, C++, Lua, LGPL-2.1, mature)
- **[mini2Dx](../mini2dx.md)** (Java, C#, Apache-2.0, mature)
- **[Minilens](../minilens.md)** (GDScript, GPL-3.0, mature, inactive since 2018)
- **[MiniPacman](../minipacman.md)** (Ada, GPL-3.0, mature)
- **[Monsterz](../monsterz.md)** (Python, WTFPL, beta, inactive since 2007)
- **[Mr. Rescue](../mr_rescue.md)** (Lua, zlib, mature, inactive since 2016)
- **[Netrek](../netrek.md)** (C, Custom, mature, inactive since 2009)
- **[Neverball](../neverball.md)** (C, C++, GPL-2.0, mature)
- **[Not Pacman](../not_pacman.md)** (Lua, WTFPL, mature, inactive since 2013)
- **[NOVA PINBALL](../nova_pinball.md)** (Lua, GPL-3.0, beta, inactive since 2017)
- **[NullpoMino](../nullpomino.md)** (Java, 3-clause BSD, mature)
- **[Numpty Physics](../numpty_physics.md)** (C++, GPL-3.0, beta, inactive since 2016)
- **[NumPy](../numpy.md)** (C, Python, 3-clause BSD, mature)
- **[ONScripter](../onscripter.md)** (C++, GPL-2.0, mature, inactive since 2020)
- **[Oolite](../oolite.md)** (Objective-C, C, JavaScript, GPL-2.0, mature)
- **[Open Horizon](../open_horizon.md)** (C++, MIT, beta)
- **[Open Rodent's Revenge](../open_rodents_revenge.md)** (C++, MIT, beta, inactive since 2018)
- **[Open RSC](../open_rsc.md)** (Java, GPL-3.0, mature)
- **[OpenArena](../openarena.md)** (C, GPL-2.0, mature, inactive since 2012)
- **[OpenBVE](../openbve.md)** (C#, Public domain, mature)
- **[OpenHV](../openhv.md)** (C#, Lua, GPL-3.0, beta)
- **[OpenJazz](../openjazz.md)** (C++, GPL-2.0, beta)
- **[OpenKrush](../openkrush.md)** (C#, GPL-3.0, beta)
- **[OpenLara](../openlara.md)** (C++, C, 2-clause BSD, mature)
- **[OpenLoco](../openloco.md)** (C++, MIT, mature)
- **[OpenMortal](../openmortal.md)** (C++, Perl, GPL-2.0, beta, inactive since 2006)
- **[openMSX](../openmsx.md)** (C++, GPL-2.0, mature)
- **[OpenRaider](../openraider.md)** (C, C++, GPL-2.0, beta, inactive since 2015)
- **[OpenRCT2](../openrct2.md)** (C++, GPL-3.0, mature)
- **[OpenRW](../openrw.md)** (C, C++, GPL-3.0, beta)
- **[OpenSAGE](../opensage.md)** (C#, LGPL-3.0, beta)
- **[OpenSpades](../openspades.md)** (C, C++, AngelScript, GPL-3.0, beta)
- **[OpenSupaplex](../opensupaplex.md)** (C, GPL-3.0, mature)
- **[OpenTESArena](../opentesarena.md)** (C++, MIT, beta)
- **[OPMon](../opmon.md)** (C++, GPL-3.0, beta)
- **[opsu!](../opsu.md)** (Java, GPL-3.0, mature)
- **[Oreon Engine](../oreon_engine.md)** (Java, GPL-3.0, mature)
- **[osu!](../osu.md)** (C#, MIT, beta)
- **[ouzel](../ouzel.md)** (C, C++, Objective-C, 2-clause BSD, beta)
- **[Overgod](../overgod.md)** (C, GPL-2.0, mature, inactive since 2005)
- **[PainTown](../paintown.md)** (C++, Java, Python, 3-clause BSD, mature)
- **[Passage](../passage.md)** (C++, Public domain, mature, inactive since 2011)
- **[Penguin Command](../penguin_command.md)** (C, GPL-2.0, mature, inactive since 2007)
- **[Pentagram](../pentagram.md)** (C++, GPL-2.0, beta, inactive since 2018)
- **[Performous](../performous.md)** (C, C++, GPL-2.0, mature)
- **[PGU](../pgu.md)** (Python, LGPL-2.1, mature)
- **[Pillow](../pillow.md)** (C, Python, Custom, mature)
- **[Pillows](../pillows.md)** (Python, GPL-2.0, beta, inactive since 2007)
- **[Pingus](../pingus.md)** (C++, GPL-3.0, mature)
- **[Pixel Dungeon](../pixel_dungeon.md)** (Java, GPL-3.0, mature, inactive since 2015)
- **[Pixel Wheels](../pixel_wheels.md)** (Java, GPL-3.0, beta)
- **[PLIB](../plib.md)** (C++, LGPL-2.0, mature, inactive since 2012)
- **[PokerTH](../pokerth.md)** (C++, AGPL-3.0, mature, inactive since 2017)
- **[Powerslave EX](../powerslave_ex.md)** (C, C++, GPL-3.0, beta, inactive since 2017)
- **[Primrose](../primrose.md)** (C++, Public domain, mature, inactive since 2009)
- **[Privateer - Gemini Gold](../privateer-gemini_gold.md)** (C++, GPL-2.0, mature, inactive since 2012)
- **[Project-Uranium-Godot](../project-uranium-godot.md)** (GDScript, MIT, beta)
- **[Puzzle Moppet](../puzzle_moppet.md)** (C++, WTFPL, mature, inactive since 2015)
- **[Pygame---Alien-Invasion](../pygame-alien-invasion.md)** (Python, GPL-3.0, beta, inactive since 2018)
- **[pyglet](../pyglet.md)** (Python, 3-clause BSD, mature)
- **[PyKaraoke](../pykaraoke.md)** (Python, LGPL-2.1, beta, inactive since 2011)
- **[PyQt](../pyqt.md)** (C++, Python, GPL-3.0, Custom, mature)
- **[pyscroll](../pyscroll.md)** (Python, LGPL-3.0, mature, inactive since 2018)
- **[PySol](../pysol.md)** (Python, GPL-2.0, mature, inactive since 2004)
- **[PyTMX](../pytmx.md)** (Python, LGPL-3.0, mature)
- **[Q](../q.md)** (Python, GPL-3.0, mature, inactive since 2013)
- **[QuakeSpasm](../quakespasm.md)** (C, GPL-2.0, mature)
- **[Rabbit Escape](../rabbit_escape.md)** (Java, GPL-2.0, mature)
- **[Race Into Space](../race_into_space.md)** (C, C++, GPL-2.0, mature)
- **[raylib](../raylib.md)** (C, C++, C#, zlib, mature)
- **[Recursive Runner](../recursive_runner.md)** (C++, GPL-3.0, beta, inactive since 2017)
- **[Reliquarium](../reliquarium.md)** (Ada, GPL-2.0, mature)
- **[Ren'Py](../renpy.md)** (C, Python, Ren'Py, LGPL-2.1, mature)
- **[ResidualVM](../residualvm.md)** (C++, GPL-2.0, beta)
- **[Ri-li](../ri-li.md)** (C++, GPL-3.0, mature, inactive since 2007)
- **[Rocks'n'Diamonds](../rocksndiamonds.md)** (C, GPL-2.0, mature)
- **[Rolisteam](../rolisteam.md)** (C++, JavaScript, GPL-2.0, mature)
- **[rpgboss](../rpgboss.md)** (Scala, JavaScript, AGPL-3.0, beta, inactive since 2017)
- **[Ruby-warrior](../ruby-warrior.md)** (Ruby, MIT, beta, inactive since 2012)
- **[RufasCube](../rufascube.md)** (Ada, GPL-2.0, mature)
- **[RufasSlider](../rufasslider.md)** (C++, GPL-2.0, mature)
- **[RufasSwap](../rufasswap.md)** (Ada, GPL-3.0, mature)
- **[Scrabble3D](../scrabble3d.md)** (Pascal, GPL-3.0, mature, inactive since 2015)
- **[Settlers III remake](../settlers_iii_remake.md)** (Java, MIT, beta)
- **[sfxr](../sfxr.md)** (C++, MIT, mature, inactive since 2012)
- **[Shattered Pixel Dungeon](../shattered_pixel_dungeon.md)** (Java, GPL-3.0, mature)
- **[Shockolate](../shockolate.md)** (C, GPL-3.0, beta)
- **[Shotgun Debugger](../shotgun_debugger.md)** (C++, GPL-2.0, mature, inactive since 2005)
- **[Simon Tatham's Portable Puzzle Collection](../simon_tathams_portable_puzzle_collection.md)** (C, MIT, mature)
- **[Simsu](../simsu.md)** (C++, GPL-3.0, mature)
- **[SLADE](../slade.md)** (C++, GPL-2.0, mature)
- **[Slime Volley](../slime_volley.md)** (C, GPL-3.0, mature, inactive since 2010)
- **[Slingshot](../slingshot.md)** (Python, GPL-2.0, beta, inactive since 2007)
- **[Sludge](../sludge.md)** (C, C++, Objective-C, LGPL-2.1, mature)
- **[Snelps](../snelps.md)** (Ruby, LGPL-2.1, beta, inactive since 2012)
- **[SolarWolf](../solarwolf.md)** (Python, LGPL-2.1, mature, inactive since 2004)
- **[Sonic Robo Blast 2](../sonic_robo_blast_2.md)** (C, C++, GPL-2.0, mature)
- **[SpacePeng!](../spacepeng.md)** (Java, GPL-3.0, mature, inactive since 2017)
- **[SpaceTrader for Java](../spacetrader_for_java.md)** (Java, GPL-2.0, mature, inactive since 2010)
- **[Spice Trade](../spice_trade.md)** (Java, LGPL-2.1, mature, inactive since 2005)
- **[Stareater](../stareater.md)** (C#, GPL-3.0, beta)
- **[Stratagus](../stratagus.md)** (C++, GPL-2.0, mature)
- **[SuperFoulEgg](../superfoulegg.md)** (Objective-C, C, MIT, mature, inactive since 2014)
- **[SuperStarfighter](../superstarfighter.md)** (GDScript, MIT, beta)
- **[SuperTux](../supertux.md)** (C++, GPL-3.0, beta)
- **[SuperTuxKart](../supertuxkart.md)** (C++, C, GPL-3.0, mature)
- **[SuperTuxParty](../supertuxparty.md)** (GDScript, GPL-3.0, beta)
- **[System Syzygy](../system_syzygy.md)** (Rust, GPL-3.0, mature, inactive since 2018)
- **[Taisei Project](../taisei_project.md)** (C, Python, MIT, mature)
- **[TankistOnline](../tankistonline.md)** (Python, GPL-3.0, beta)
- **[Tanks of Freedom](../tanks_of_freedom.md)** (GDScript, MIT, mature)
- **[Teeworlds](../teeworlds.md)** (C, C++, zlib, beta, inactive since 2013)
- **[TermFrogger](../termfrogger.md)** (Ada, GPL-3.0, mature)
- **[TerminalApps](../terminalapps.md)** (Ada, GPL-3.0, mature)
- **[TES3MP](../tes3mp.md)** (C++, GPL-3.0, beta)
- **[TetraVex](../tetravex.md)** (Swift, GPL-3.0, beta)
- **[The Battle for Wesnoth](../the_battle_for_wesnoth.md)** (C, C++, Java, Python, Lua, GPL-2.0, mature)
- **[The Bub's Brothers](../the_bubs_brothers.md)** (Python, MIT, mature, inactive since 2013)
- **[The Butterfly Effect](../the_butterfly_effect.md)** (C++, GPL-2.0, beta)
- **[The Eternity Engine](../the_eternity_engine.md)** (C, C++, GPL-3.0, mature)
- **[The Powder Toy](../the_powder_toy.md)** (C++, C, Lua, Python, GPL-3.0, mature)
- **[TinTin++](../tintin++.md)** (C, GPL-3.0, mature)
- **[Tiny Wings](../tiny_wings.md)** (Objective-C, C, C++, MIT, beta)
- **[Torque 2D](../torque_2d.md)** (C++, C, MIT, mature)
- **[Torque 3D](../torque_3d.md)** (C++, C, MIT, mature)
- **[Total Annihilation 3D](../total_annihilation_3d.md)** (C++, C, Lua, GPL-2.0, beta, inactive since 2017)
- **[Transcend](../transcend.md)** (C++, ?, beta, inactive since 2005)
- **[Tremulous](../tremulous.md)** (C, GPL-2.0, mature, inactive since 2016)
- **[Tux Builder](../tux_builder.md)** (GDScript, GPL-3.0, beta)
- **[Tux Paint](../tux_paint.md)** (C, C++, GPL-2.0, beta)
- **[Tuxemon](../tuxemon.md)** (Python, GPL-3.0, beta)
- **[Ultimate Stunts](../ultimate_stunts.md)** (C++, GPL-2.0, beta, inactive since 2013)
- **[UltraStar Deluxe](../ultrastar_deluxe.md)** (Pascal, GPL-2.0, mature)
- **[UltraStar Play](../ultrastar_play.md)** (C#, MIT, beta)
- **[Umoria](../umoria.md)** (C, C++, GPL-3.0, mature)
- **[UnCiv](../unciv.md)** (Kotlin, MPL-2.0, beta)
- **[unitystation](../unitystation.md)** (C#, AGPL-3.0, beta)
- **[Unvanquished](../unvanquished.md)** (C, C++, GPL-3.0, mature)
- **[VASSAL](../vassal.md)** (Java, LGPL-2.1, mature)
- **[VDrift](../vdrift.md)** (C++, GPL-3.0, mature, inactive since 2014)
- **[vkQuake](../vkquake.md)** (C, C++, GPL-2.0, mature)
- **[Wagic, the Homebrew](../wagic_the_homebrew.md)** (C++, C, Objective-C, 3-clause BSD, beta)
- **[Word War vi](../word_war_vi.md)** (C, GPL-2.0, mature)
- **[wxPython](../wxpython.md)** (Python, C, wxWindows license, mature)
- **[X-Moto](../x-moto.md)** (C++, GPL-2.0, mature, inactive since 2014)
- **[XPilot NG](../xpilot_ng.md)** (C, GPL-2.0, mature, inactive since 2010)
- **[XSkat](../xskat.md)** (Java, Custom, mature)
- **[Yet Another Engine](../yet_another_engine.md)** (MoonScript, Java, Lua, MIT, beta, inactive since 2016)
- **[Yo Frankie!](../yo_frankie.md)** (Blender Script, ?, mature, inactive since 2009)
- **[YSoccer](../ysoccer.md)** (Java, GPL-2.0, mature)
- **[Zaz](../zaz.md)** (C++, GPL-3.0, beta, inactive since 2010)
- **[ZDoom](../zdoom.md)** (C, C++, ZenScript, GPL-3.0, mature) | 70.0301 | 114 | 0.60681 | eng_Latn | 0.084073 |
a1185d6bc4ed535134bf1d7f34a9bc0e107218f3 | 1,287 | md | Markdown | docs/framework/wpf/app-development/how-to-set-the-title-of-a-window-from-a-page.md | Ming77/docs.zh-cn | dd4fb6e9f79320627d19c760922cb66f60162607 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/app-development/how-to-set-the-title-of-a-window-from-a-page.md | Ming77/docs.zh-cn | dd4fb6e9f79320627d19c760922cb66f60162607 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/app-development/how-to-set-the-title-of-a-window-from-a-page.md | Ming77/docs.zh-cn | dd4fb6e9f79320627d19c760922cb66f60162607 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "如何： 设置从页窗口的标题"
ms.custom:
ms.date: 03/30/2017
ms.prod: .net-framework
ms.reviewer:
ms.suite:
ms.technology: dotnet-wpf
ms.tgt_pltfrm:
ms.topic: article
helpviewer_keywords:
- windows [WPF], setting title from a page
- title of window [WPF], setting from a page
- pages [WPF], setting window title from
ms.assetid: fecf0d19-3eb6-4f8c-a44f-ff1b6f2b34b3
caps.latest.revision: "5"
author: dotnet-bot
ms.author: dotnetcontent
manager: wpickett
ms.workload: dotnet
ms.openlocfilehash: 11f33eede479e090a78bffe841d7998e03eab6c4
ms.sourcegitcommit: 16186c34a957fdd52e5db7294f291f7530ac9d24
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 12/22/2017
---
# <a name="how-to-set-the-title-of-a-window-from-a-page"></a>如何： 设置从页窗口的标题
此示例演示如何在其中设置窗口的标题<xref:System.Windows.Controls.Page>承载。
## <a name="example"></a>示例
页面可以更改将通过设置其承载窗口的标题<xref:System.Windows.Controls.Page.WindowTitle%2A>属性，如下所示：
[!code-xaml[HOWTONavigationSnippets#SetPageWindowTitleXAML](../../../../samples/snippets/csharp/VS_Snippets_Wpf/HOWTONavigationSnippets/CSharp/SetWindowTitlePage.xaml#setpagewindowtitlexaml)]
> [!NOTE]
> 设置<xref:System.Windows.Controls.Page.Title%2A>页属性不会更改窗口标题的值。 相反，<xref:System.Windows.Controls.Page.Title%2A>导航历史记录中指定的页面条目的名称。
| 34.783784 | 194 | 0.765346 | yue_Hant | 0.583653 |
a118d14ad44508f9515d0c07f28616f6d79006e1 | 15,753 | md | Markdown | content/blog/INS_Cute_Sweet_rainbow_Smile_Phone_Case_For_iPhone_12_11_Pro_X_XS_MAX_XR_7_8plus_Photograph_Earth_plane_Soft_silicon_Clear_Cover/index.md | muazinasro/rifanmuazin | 59519ab30db6c107824b577620e851da3ea00b16 | [
"MIT"
] | null | null | null | content/blog/INS_Cute_Sweet_rainbow_Smile_Phone_Case_For_iPhone_12_11_Pro_X_XS_MAX_XR_7_8plus_Photograph_Earth_plane_Soft_silicon_Clear_Cover/index.md | muazinasro/rifanmuazin | 59519ab30db6c107824b577620e851da3ea00b16 | [
"MIT"
] | null | null | null | content/blog/INS_Cute_Sweet_rainbow_Smile_Phone_Case_For_iPhone_12_11_Pro_X_XS_MAX_XR_7_8plus_Photograph_Earth_plane_Soft_silicon_Clear_Cover/index.md | muazinasro/rifanmuazin | 59519ab30db6c107824b577620e851da3ea00b16 | [
"MIT"
] | null | null | null | ---
title: INS Cute Sweet rainbow Smile Phone Case For iPhone 12 11 Pro X XS MAX XR 7 8plus Photograph Earth plane Soft silicon Clear Cover
date: 2020-10-25 21:54:39
tags: [Phones & Telecommunications]
cover: https://ae01.alicdn.com/kf/H39d6abb66c2e46138ff9ebd8355d0ba81/INS-Cute-Sweet-rainbow-Smile-Phone-Case-For-font-b-iPhone-b-font-12-11-Pro.jpg_350x350.jpg
excerpt: Buy **INS Cute Sweet rainbow Smile Phone Case For iPhone 12 11 Pro X XS MAX XR 7 8plus Photograph Earth plane Soft silicon Clear Cover** Right Here and Right Now and You will save USD 0.25 or 20%%, Because price is will changed at any time without notice, or stock may be run out, If You Buy Now You Just Pay For USD 1.00, not in Reguler Price at 1.25. Yap! This is I mean you will Save 20% % / USD 0.25
---
# *INS Cute Sweet rainbow Smile Phone Case For iPhone 12 11 Pro X XS MAX XR 7 8plus Photograph Earth plane Soft silicon Clear Cover*
[](https://s.click.aliexpress.com/s/4BScZUQRCtnCPCxSv0PKwEvDQD4u6TRQDsTl9yY3LPNpjcFJYJYgdvBwDDpTrktMG0Bk7vaKjL6XyPRVpHoWa7nQNlQFkqJPggCvZt8DKU9umyHh6eIX5opg0KuXEYNPi7ieG5LeqJDbqOacEd03kB7TjoPS5lw5oIH5JFWbhzN203U3K2CHxLHglZ3KrbYkGRGOE1cgm0v2oQRL2P5WzsJEV9UY7mMsJJsfwdoEo4YKzpQ4A6hFKY1Q4wYvOojPSfj2bFrEVwvkPSR5Y6FnaSrCZc6K5dZ2jfPZN2c5Uz6ken8DkMcl0at0TpyYrzyUEbkSSgvxxMBZq6PY0RywrsTcD5hy7IJ0Sp9Vl35CYDTmX9KK47chrzoQJ3CKMX9RZN1Og3tDs9mXAyWHlVTebEumNvUkgbILyUUpUTXWkPoBZJOEFRYrapOizKplc4j3fJwSXGLKxJeADEFOCW91LvqfGfmCsAkZ1jA2QrlJaQm04O53hJyjAg9j0lRfHevwpP65e2MuOqVi8DPYy04VYZ4Na3X4TEgXUj4uDDZ2L71Rs6dskbGk7qOhHK9ohFzrxOAFO3ylP7yp2wtXiVC45mpS5vxNJZVjE6ktnVkyLUk6GbOLSjvpAq27R25pssoddcDMrPn0ZCbmlOl4kojd3yKxs3VdQrdZ80xydHAhUbFMG5lIxYijfF65Z00n657H1FcVB67hu4e67iG8Rm5rftDm0vky4zjf2qD7sDG9yqYz29ysUqiLdK49Rag8DFev9rQrLK)
## Best Chance of INS Cute Sweet rainbow Smile Phone Case For iPhone 12 11 Pro X XS MAX XR 7 8plus Photograph Earth plane Soft silicon Clear Cover
If You will buy for iphone, then **INS Cute Sweet rainbow Smile Phone Case For iPhone 12 11 Pro X XS MAX XR 7 8plus Photograph Earth plane Soft silicon Clear Cover** may be make you like
Buy **INS Cute Sweet rainbow Smile Phone Case For iPhone 12 11 Pro X XS MAX XR 7 8plus Photograph Earth plane Soft silicon Clear Cover** Right Here and Right Now and You will save USD 0.25 or 20%%, Because price is will changed at any time without notice, or stock may be run out, If You Buy Now You Just Pay For USD 1.00, not in Reguler Price at 1.25. Yap! This is I mean you will Save 20% % / USD 0.25
## Addition Information of *INS Cute Sweet rainbow Smile Phone Case For iPhone 12 11 Pro X XS MAX XR 7 8plus Photograph Earth plane Soft silicon Clear Cover*
- Product UD (PID) is *4000831969377*
- Product Rank is **13**
- Reguler Price is $ *1.25*
- Discount Price is $ **1.00**
- Category ID is *509*
- Category Name is **Phones & Telecommunications**
- Saving is *USD 0.25*
- Discount is **20%**
- Seller ID is *4992357*
Last Stock Available : (When this Article was written)
## **GALLERY PRODUCT**
[](https://s.click.aliexpress.com/s/4BScZUQRCtnCPCxSv0PKwEvDQD4u6TRQDsTl9yY3LPNpjcFJYJYgdvBwDDpTrktMG0Bk7vaKjL6XyPRVpHoWa7nQNlQFkqJPggCvZt8DKU9umyHh6eIX5opg0KuXEYNPi7ieG5LeqJDbqOacEd03kB7TjoPS5lw5oIH5JFWbhzN203U3K2CHxLHglZ3KrbYkGRGOE1cgm0v2oQRL2P5WzsJEV9UY7mMsJJsfwdoEo4YKzpQ4A6hFKY1Q4wYvOojPSfj2bFrEVwvkPSR5Y6FnaSrCZc6K5dZ2jfPZN2c5Uz6ken8DkMcl0at0TpyYrzyUEbkSSgvxxMBZq6PY0RywrsTcD5hy7IJ0Sp9Vl35CYDTmX9KK47chrzoQJ3CKMX9RZN1Og3tDs9mXAyWHlVTebEumNvUkgbILyUUpUTXWkPoBZJOEFRYrapOizKplc4j3fJwSXGLKxJeADEFOCW91LvqfGfmCsAkZ1jA2QrlJaQm04O53hJyjAg9j0lRfHevwpP65e2MuOqVi8DPYy04VYZ4Na3X4TEgXUj4uDDZ2L71Rs6dskbGk7qOhHK9ohFzrxOAFO3ylP7yp2wtXiVC45mpS5vxNJZVjE6ktnVkyLUk6GbOLSjvpAq27R25pssoddcDMrPn0ZCbmlOl4kojd3yKxs3VdQrdZ80xydHAhUbFMG5lIxYijfF65Z00n657H1FcVB67hu4e67iG8Rm5rftDm0vky4zjf2qD7sDG9yqYz29ysUqiLdK49Rag8DFev9rQrLK)
## Related Product for iphone and INS Cute Sweet rainbow Smile Phone Case For iPhone 12 11 Pro X XS MAX XR 7 8plus Photograph Earth plane Soft silicon Clear Cover
### 5V2A EU US Plug 2 Usb Charger Mobile phone Fast Charger for iPhone for Android for Huawei for Samsung
Buy 5V2A EU US Plug 2 Usb Charger Mobile phone Fast Charger for iPhone for Android for Huawei for Samsung and You will Save USD 0.25 or 20% %, Becuase You Just Pay for 1.00 not Full Price for 1.25
#### Addition Information of **5V2A EU US Plug 2 Usb Charger Mobile phone Fast Charger for iPhone for Android for Huawei for Samsung**
- Reguler Price is **$ 1.25**
- Sale Price is **$1.00**
- Saving is **USD 0.25**
- Discount is **20%**
[](https://s.click.aliexpress.com/s/4BScZUQRCtnCPCxSv0PKwEvDQD4u6TRQDsTl9yY3LPNpjcFJYJYgdvBwDDpTrktMG0Bk7vaKjL6XyPRVpHoWa7nQNlQFkqJPggCvZt8DKU9umyHh6eIX5opg0KuXEYNPi7ieG5LeqJDbqOacEd03kB7TjoPS5lw5oIH5JFWbhzN203U3K2CHxLHglZ3KrbYkGRGOE1cgm0v2oQRL2P5WzsJEV9UY7mMsJJsfwdoEo4YKzpQ4A6hFKY1Q4wYvOojPSfj2bFrEVwvkPSR5Y6FnaSrCZc6K5dZ2jfPZN2c5Uz6ken8DkMcl0at0TpyWaGZyXoZWFwKj2LbPcYcL6PP46uM5RPTcXsTWaJYgJygaWncYTlXA4PL4VrRojc7Uk3GIs2dL4uRJi0IKxlY0RPKqto3PyktgHTzKAoaeScEMRAKxvBxKW8fM47rgJUQ22Mb6E504bKObX8vNb9DChHgil4Yt6bgZAbR5jS5vjeTFrgP3Jt6juM1dkmxVidzCgXjfjoWhWw6VSbUI3ZhHV3pWNTeh2ovWfaP8n7Z1RNiV4tew6BE1UzOpjzGES4SvjaX7LAXCFhTk6FPLz7b6lMtgy9vPOQOtJFSb7DHFN3QoR0KVuVtMGJrorqj3oMTuV870f82O3RtibZNOa2PSZJozl0zSSyCqWIBBasxpW2Ff9cW8bwEwbWPmjv0kU7ir425pmFlQPZmKRPubDH83gi2UgDVNaNeLl5ECtATmEyuzBMMKoGSpYgoa3NTm2ZK3FxiOrZHeXm)
### Luxury Cute Flower Phone Case For iPhone 12 11 Pro Max X XR XS Max 7 8 Plus Bumper Shockproof Matte Back Cover Coque
Buy Luxury Cute Flower Phone Case For iPhone 12 11 Pro Max X XR XS Max 7 8 Plus Bumper Shockproof Matte Back Cover Coque and You will Save USD 0.25 or 20% %, Becuase You Just Pay for 1.00 not Full Price for 1.25
#### Addition Information of **Luxury Cute Flower Phone Case For iPhone 12 11 Pro Max X XR XS Max 7 8 Plus Bumper Shockproof Matte Back Cover Coque**
- Reguler Price is **$ 1.25**
- Sale Price is **$1.00**
- Saving is **USD 0.25**
- Discount is **20%**
[](https://s.click.aliexpress.com/s/4BScZUQRCtnCPCxSv0PKwEvDQD4u6TRQDsTl9yY3LPNpjcFJYJYgdvBwDDpTrktMG0Bk7vaKjL6XyPRVpHoWa7nQNlQFkqJPggCvZt8DKU9umyHh6eIX5opg0KuXEYNPi7ieG5LeqJDbqOacEd03kB7TjoPS5lw5oIH5JFWbhzN203U3K2CHxLHglZ3KrbYkGRGOE1cgm0v2oQRL2P5WzsJEV9UY7mMsJJsfwdoEo4YKzpQ4A6hFKY1Q4wYvOojPSfj2bFrEVwvkPSR5Y6FnaSrCZc6K5dZ2jfPZN2c5Uz6ken8DkMcl0at0TpyWEwvhF3gtvaUT9l4ApvNB39ZYeodYLdYpjeKIAvwDhx5OgANerHfh8FIVQqqIFW1sv3em7Do8NFNow1RsHwOHJGUD1qAExSmjPoSgCd0GrQNvNDuhxxxJfP5qGQN9Wo0qep5usY8wP9I1NsSpbLyj0JGrs107AnDlB3prQg1BujyM8BoKfO24CJVCNL9Z8YRelG0RPyZn2LEmmnmIudoYg1xUeCmwYIN6DwaYrMRUfhHlbVquOqK1DuKHtcII2WgqPYEydSuGnvUm2XRpog7i9cM1BIsIC455KBtEW7NXMJaNRo816pF3yObfa6P5GNYc6ClCqLFL49cFsx06hpsV1xQMR48LEMml6Pxx81f9BFkUal1faBCLEzELE6WeVTWOlQj37u0tDwlezkS6QVgzQfrz8GgN6Kh4eFHiBLfTSgKM8HFGuJ62EUIGIYUbUefpgbRQHD65lT)
### Caliente Pantone Black TPU Soft Silicone Phone Case Cover For iPhone 8 7 6 6S Plus X XS MAX 5 5S SE XR 11 11pro promax Coque
Buy Caliente Pantone Black TPU Soft Silicone Phone Case Cover For iPhone 8 7 6 6S Plus X XS MAX 5 5S SE XR 11 11pro promax Coque and You will Save USD 0.39 or 28% %, Becuase You Just Pay for 1.00 not Full Price for 1.39
#### Addition Information of **Caliente Pantone Black TPU Soft Silicone Phone Case Cover For iPhone 8 7 6 6S Plus X XS MAX 5 5S SE XR 11 11pro promax Coque**
- Reguler Price is **$ 1.39**
- Sale Price is **$1.00**
- Saving is **USD 0.39**
- Discount is **28%**
[](https://s.click.aliexpress.com/s/4BScZUQRCtnCPCxSv0PKwEvDQD4u6TRQDsTl9yY3LPNpjcFJYJYgdvBwDDpTrktMG0Bk7vaKjL6XyPRVpHoWa7nQNlQFkqJPggCvZt8DKU9umyHh6eIX5opg0KuXEYNPi7ieG5LeqJDbqOacEd03kB7TjoPS5lw5oIH5JFWbhzN203U3K2CHxLHglZ3KrbYkGRGOE1cgm0v2oQRL2P5WzsJEV9UY7mMsJJsfwdoEo4YKzpQ4A6hFKY1Q4wYvOojPSfj2bFrEVwvkPSR5Y6FnaSrCZc6K5dZ2jfPZN2c5Uz6ken8DkMcl0at0TpyVzDlR0xZMQl1Bu3ZnRlfRPyytCfkcKJPbSH3khqRGFpQAX5QnQCiiyYBHGr3NCB6JXlN9E3b9cEuQF6VCxx9M3CTokqReRXaVY40shIpnLAgmktRHLVtWGlV5eBI9jWvrgsBFSbf0qOxZGGA41c1ihhED4ukgA1n2lgYBcrhCmFQ2IK3Mspq2PWJfyoVTK0Zdzy58UoU5bN2XmMmggXnPGWXLb4H96Lbdzy9LPlujJYnz1xpRYJ5IRwqxQKNo4z4hLTKeJ5NW5PD5KwlfcAI2K4lRdX5mySZiW7iCaeFV1pOlihDjtN80HG0F6xJH0qFIkpzBbOFdBObBrXfWTDm3rtgmbocjIop5qcQa9ssSbcCqahjfuPzbFSoNlwyFpKGbDwkkfRlgo1CNe6ZSacwPUByA9S6KlM3qjVySZCpOAHA7wQRRXWKIyOzmZWmf8xk0rma1lXI37m)
### Marc Marquez Moto Gp 93 Luxry case coque fundas for iphone 5s se 6 6s 7 8 plus x xs max xr 11 pro max cases cover
Buy Marc Marquez Moto Gp 93 Luxry case coque fundas for iphone 5s se 6 6s 7 8 plus x xs max xr 11 pro max cases cover and You will Save USD 1 or %, Becuase You Just Pay for not Full Price for 1.00
#### Addition Information of **Marc Marquez Moto Gp 93 Luxry case coque fundas for iphone 5s se 6 6s 7 8 plus x xs max xr 11 pro max cases cover**
- Reguler Price is **$ 1.00**
- Sale Price is **$**
- Saving is **USD 1**
- Discount is ****
[](https://s.click.aliexpress.com/s/4BScZUQRCtnCPCxSv0PKwEvDQD4u6TRQDsTl9yY3LPNpjcFJYJYgdvBwDDpTrktMG0Bk7vaKjL6XyPRVpHoWa7nQNlQFkqJPggCvZt8DKU9umyHh6eIX5opg0KuXEYNPi7ieG5LeqJDbqOacEd03kB7TjoPS5lw5oIH5JFWbhzN203U3K2CHxLHglZ3KrbYkGRGOE1cgm0v2oQRL2P5WzsJEV9UY7mMsJJsfwdoEo4YKzpQ4A6hFKY1Q4wYvOojPSfj2bFrEVwvkPSR5Y6FnaSrCZc6K5dZ2jfPZN2c5Uz6ken8DkMcl0at0Tpy8qPRryixxEsdWWKBkQ9VnYdFgiDya6g0fMJFYlClnnJidMk5bvoM6Ns2KqLdgvZHy00b22nIqEg4BKSvpnhE4Ofxm55mbiIvatLfsYg8ZJlUJAqavwj0jtHCKTcVR2w3sCmTrBVGu89HQHANnxDl5KCoOZDc3o7niAT9uR3BhyHzr32wEnyzKS0cIoreiQeGXQtPT75bOBDlvdZT6F5MKTsmyrFb89KWeJZnrULfMCTxkV2pcYBP5CIBh5pf2O1QUa9seu95TkD3d2uzx66jHCwQl5rSes63QRJCzl94bQOcHL24K6HGLIlG6NBGjYVum3ZFZsZV0YJxnbdGZ2u8RXM7sETw7CVcY69lYW2g2AvMwCEwKK3G0NkLM4ZS5ERzfzHEaAWqru1UkNfGRwsYX4bOfzGZWJeeZlYU01OgZ95avMjXxOFgI8dnYRueRNss9AiCrvCp01E) | 164.09375 | 1,119 | 0.837364 | yue_Hant | 0.5399 |
a119082a09978e785e13c783aa2651d34151afac | 20,861 | md | Markdown | rfcs/components/moving-from-focus-zone-to-tabster.md | CheerfulSatchel/fluentui | 8a141d14f3a14de2e1c4691dad908622f310a9d1 | [
"MIT"
] | 7,194 | 2016-07-21T19:41:05.000Z | 2020-03-20T11:30:44.000Z | rfcs/components/moving-from-focus-zone-to-tabster.md | CheerfulSatchel/fluentui | 8a141d14f3a14de2e1c4691dad908622f310a9d1 | [
"MIT"
] | 10,472 | 2016-07-21T22:56:20.000Z | 2020-03-20T19:50:35.000Z | rfcs/components/moving-from-focus-zone-to-tabster.md | CheerfulSatchel/fluentui | 8a141d14f3a14de2e1c4691dad908622f310a9d1 | [
"MIT"
] | 1,664 | 2016-07-22T03:30:48.000Z | 2020-03-19T05:23:44.000Z | # Moving from `FocusZone` to `Tabster`
---
Contributors: @khmakoto @ling1726
## Problem statement
We currently use `FocusZone` for focus management in both v0 and v8. For our converged components we are trying out a different approach by using `Tabster`.
The reason for doing this is to use a framework-agnostic solution (as opposed to the React-centric `FocusZone`) that operates at the DOM level and has no external runtime dependencies.
However, we have to make sure that `Tabster` can actually cover all the scenarios `FocusZone` covered.
## Requirements
Ideally, `FocusZone` or `FocusTrapZone` like components should be avoided in most cases, and our components should provide first class support for correct keyboarding behavior. It is reasonable to assume that our components might not cover all our customers' scenarios. We should define the requirements that Fluent UI should support for focus management.
### Lists/Collections
Type of keyboard and focus behavior that is the most commonly documented by WAI-ARIA and most commonly seen in
- [listbox](https://www.w3.org/TR/wai-aria-practices-1.1/#Listbox)
- [menu(bar)](https://www.w3.org/TR/wai-aria-practices-1.1/#menu)
Although most widgets that involve collections will implement parts of the basic keyboarding with other special features i.e [radio group](https://www.w3.org/TR/wai-aria-practices-1.1/examples/radio/radio-1/radio-1.html).
The most important behavior in these scenarios is navigating with the use of Arrow keys
- Left/Right
- Up/Down
- Left+Up/Right+Down
- Tab can be used alongside arrow keys
- Possibility of using Home/End keys to focus first/last elements respectively
### Grids
The most common example of grid keyboarding would be the infamous [data grid](https://www.w3.org/TR/wai-aria-practices-1.1/examples/grid/dataGrids.html).
Elements should be navigated with all arrow keys in a 2D grid, that **does not need to be perfectly aligned**.
### Nested focusable items
This scenario can happen in the case of grids where a cell contains focusable items that can also be focused/navigated in the scope of the whole grid.
Another common scenario are interactive cards where the card itself is focusable/clickable but the contents in it can also contain focusable items.
Nested focusable items should also be able to use list/grid focus behaviors.
> TODO #19324
### Restoring lost focus
Often clicking on a widget (e.g button) can toggle an option and cause it to disappear. Without any intervention the focus will be lost and applied directly to the document body, which is undesireable for screen reader users.
We should provide customers the ability to easily detect or avoid these situations by restoring focus to meaningful default elements.
### Finding/filtering focusable children
There are a variety of factors to consider when trying to find focusable elements for features:
- disabled
- aria-disabled
- aria-hidden
- tabindex
- Custom clasname/role/data-\* requirements
We should provide customers the ability to easily find focusable items that **are focusable** and also follow their custom filtering requirements.
## `FocusZone`
`FocusZone` is a React component that is built to wrap around the elements whose focus it is to manage. It provides a number of props to abstract arrow key navigation behavior amongst tabbable elements and be able to group them into "zones" that you can transition between.
The React component pattern for focus management is not ideal, it breaks React component isolation. These components use DOM operations and a mix of global and synthetic event listeners to implement behavior. The components also expose a class-based interface for focus operations on children elements, which further breaks isolation.
Nested focusables cause issues on the current `FocusZone` component, where nested focusables behave inconsistently or incorrectly. Here are some recent issues related to this:
- [microsoft/fluentui#8551](https://github.com/microsoft/fluentui/issues/8551)
- [microsoft/fluentui#12177](https://github.com/microsoft/fluentui/issues/12177)
- [microsoft/fluentui#16037](https://github.com/microsoft/fluentui/issues/16037)
- [microsoft/fluentui#13210](https://github.com/microsoft/fluentui/issues/13210)
## `Tabster`
Philosophy behind `Tabster`:
> **Tab**index on **Ster**oids
[Tabster](https://github.com/microsoft/tabster) is designed to be a lower level utility that manages the state of focusable elements independent from a rendering framework.
Internally, `Tabster` leverages the [TreeWalker API](https://developer.mozilla.org/en-US/docs/Web/API/TreeWalker), which is the recommended DOM tree traversal method [according to the w3c](https://www.w3.org/TR/DOM-Level-2-Traversal-Range/traversal.html).
[Tabster](https://github.com/microsoft/tabster) manages focus on a lower level than the rendering framework and acts on the **visible** DOM. Since operations are run on visible DOM there is a much clearer path for handling dynamically loaded content that would otherwise require effects outside the rendering lifecycle in React components, which breaks component isolation principles.
`Tabster` has 2 levels of API:
- Declarative with `data-tabster` DOM attribute
- Functional that can accept DOM elemenets or functions
Nesting focusables is a problem that `Tabster` explicitly tries to solve. It does this by bringing focus management to a lower level than the rendering framework, trying to accomplish this consistently without worrying about rendering cycles.
From the highest level, `Tabster` is opt-in and will not work unless a specific root element has been configured.
### Modules
The description of the each constituent module in the library can be found in the [Tabster README](https://github.com/microsoft/tabster).
The bundle size of each of the different modules of the library are listed in the below table (as of May 5, 2021). The library is fully tree-shakeable, and for most cases only the `core` part of the library is expected to be used.
| Module | minified (kb) | gzipped(kb |
| --------------- | ------------- | ---------- |
| Core | 45.3 | 12.2 |
| Deloser | 13.2 | 3.2 |
| Modalizer | 4.5 | 0.8 |
| ObservedElement | 3.1 | 0.7 |
| Outline | 7.9 | 2 |
| CrossOrigin | 18.9 | 4.4 |
[#18700](https://github.com/microsoft/fluentui/pull/18700) refactors `FocusZone` and `FocusTrapZone` to be independent of old v8 styling utilities and measures the bundle size. We should eventually reach the same targets with tabster
#### Core API
`Tabster's` Core API provides the following functionalities:
- Groupper - handling groups of focusable elements.
- Mover - hanling moving between (groups of) focusable elements.
- Focusable - utilities to find and verify focusable elements.
- Focused element state - observes the currently focused element.
- Keyboard navigation state - observes if the user is navigating with keyboard.
All of those functionalities are opt-in.
#### Deloser
Elements with focus on them disappearing from the application and causing the focus to suddenly be on the `body` is a common problem in the web.
The Deloser API tries to solve this by tracking the focus history and automatically restoring focus when it is lost.
The API is opt-in, and can be declarative (`data-tabster`) for the simplest use case. It can also be paused/resumed during runtime.
#### Modalizer
Modal dialogs generally have these hard requirements:
- Focus must be trapped.
- All non-interactable elements must be hidden from screen readers.
- Only one modal can be active at a time.
This API is also opt-in and handles all the above requirements.
## Comparison between `FocusZone` and `Tabster`
Below, we present a comparison between the functionality available in `FocusZone` and `Tabster`, focusing on what is covered by either or both of them and seen from the lens of someone who wants to transition from using `FocusZone` to using `Tabster` in their project. The way we are going to approach this is by taking a look at which `FocusZone` props/capabilities are covered in `Tabster` (either fully or partially) and which ones are missing, all while skipping over deprecated props.
### What is covered in `FocusZone` that is fully covered by `Tabster`
#### IFocusZone
- `focus(forceIntoFirstElement?: boolean): boolean`
- _Description:_ Sets focus to the first tabbable item in the `FocusZone`, returning true if focus could be set to an active element and false otherwise. If `forceIntoFirstElement` is true, focus will be forced into the first element, even if the focus is already within the `FocusZone`.
- _Equivalent in `Tabster`:_ Use `findFirstFocusable` from `useFocusFinders` in `@fluentui/react-tabster` instead.
- `focusLast(): boolean`
- _Description:_ Sets focus to the last tabbable item in the `FocusZone`, returning true if focus could be set to an active element and false otherwise.
- _Equivalent in `Tabster`:_ Use `findLastFocusable` from `useFocusFinders` in `@fluentui/react-tabster` instead.
- `focusElement(childElement?: HTMLElement, forceAlignment?: boolean): boolean`
- _Description:_ Sets focus to a specific child element (`childElement`) within the zone. This can be used in conjunction with `shouldReceiveFocus` to create delayed focus scenarios (like animate the scroll position to the correct location and then focus). If `forceAlignment` is true, then focus alignment will be set according to the element provided. Returns true if focus could be set to an active element and false otherwise.
- _Equivalent in `Tabster`:_ Use `findAllFocusable` from `useFocusFinders` in `@fluentui/react-tabster` instead. This function will walk the HTML tree and return nodes that match a callback similar to `find` in native JS.
#### IFocusZoneProps
- `isCircularNavigation?: boolean`
- _Description:_ If set, the `FocusZone` will cycle to the beginning of the targets once the user navigates to the next target while at the end, and to the end when navigating to the previous target while at the beginning.
- _Equivalent in `Tabster`:_ `useArrowNavigationGroup` from `@fluentui/react-tabster` can be used to allow for cyclic navigation, specified by passing the `circular` prop as part of the hook's `options` argument.
- `preventFocusRestoration?: boolean`
- _Description:_ If true, prevents the `FocusZone` from attempting to restore the focus to the inner element when the focus is on the root element after `componentDidUpdate`.
- _Equivalent in `Tabster`:_ If "deloser" part of `Tabster` is not declared then it does not keep track of focus history for focus restoration, which essentially accomplishes the same goal.
- `shouldFocusOnMount?: boolean`
- _Description:_ Determines if a default tabbable element should be force-focused on `FocusZone` mount.
- _Equivalent in `Tabster`:_ The same functionality can be accomplished by using one of the focus finding utilities from `useFocusFinders` (part of `@fluentui/react-tabster`) either in an effect for function components or in the `componentDidMount` lifecycle method for class-based components.
- `allowFocusRoot?: boolean`
- _Description:_ Allows focus to park on root when focus is in the `FocusZone` at render time.
- _Equivalent in `Tabster`:_ This is equivalent to adding `tabIndex={0}` to the root element supporting `Tabster`.
- `onFocus?: (event: React.FocusEvent<HTMLElement>) => void`
- _Description:_ Callback called when a "focus" event is triggered in the `FocusZone`.
- _Equivalent in `Tabster`:_ Native `onFocus` callback can be used instead.
### What is covered in `FocusZone` that is partially covered by `Tabster`
#### IFocusZoneProps
- `direction?: FocusZoneDirection`
- _Description:_ Defines which arrows to react to.
- _Notes:_ `FocusZoneDirection` is an `enum` with the following values:
- `vertical`: Reacts to Up/Down arrows.
- `horizontal`: Reacts to Left/Right arrows.
- `bidirectional`: Reacts to all arrows.
- `domOrder`: Reacts to all arrows by navigating to the next item in DOM by pressing Right/Down arrow keys and to the previous item in the DOM by pressing Left/Up arrow keys. Left and Right arrow keys are swapped in RTL mode.
- _Partial equivalent in `Tabster`:_ `useArrowNavigationGroup` from `@fluentui/react-tabster` can be used to allow for arrow navigation for either a vertical or horizontal axis, specified by passing the `axis` prop as part of the hook's `options` argument.
- _What is missing in `Tabster`?:_ `bidirectional` and `domOrder` navigation are not currently available via `useArrowNavigationGroup`.
- `handleTabKey?: FocusZoneTabbableElements`
- _Description:_ Allows tab key to be handled to tab through a list of items in the `FocusZone`. An unfortunate side effect is that users will not be able to tab out of the `FocusZone` and have to hit some other key.
- _Notes:_ `FocusZoneTabbableElements` is an `enum` with the following values:
- `none`: Tabbing is not allowed.
- `all`: All tabbing is allowed.
- `inputOnly`: Tabbing is allowed only on input elements.
- _Partial equivalent in `Tabster`:_ `Tabster` allows the user to specify the navigation type of the `Mover` to be handled via arrow keys, the tab key, or both.
- _What is missing in `Tabster`?:_ And abstraction similar to `useArrowNavigationGroup` would be nice to have. Even then, there is no equivalent currently for `inputOnly` tabbing.
- `shouldEnterInnerZone?: (ev: React.KeyboardEvent<HTMLElement>) => boolean`
- _Description:_ Callback function that will be executed on keypresses to determine if the user intends to navigate into the inner (nested) zone. Returning true will ask the first inner zone to set focus.
- _Partial equivalent in `Tabster`:_ The "groupper" part of `Tabster` groups focusables and can handle nesting.
- _What is missing in `Tabster`?:_ We need to be very clear about how we support nested focusables to determine what kind of API is needed here.
- `shouldFocusInnerElementWhenReceivedFocus?: boolean`
- _Description:_ If true and `FocusZone's` root element (container) receives focus, the focus will land either on the `defaultTabbableElement` (if set) or on the first tabbable element of this `FocusZone`. Commonly used in the case of nested `FocusZones` where the nested `FocusZone's` container is a focusable element.
- _Partial equivalent in `Tabster`:_ The "groupper" part of `Tabster` groups focusables and can handle nesting.
- _What is missing in `Tabster`?:_ We need to be very clear about how we support nested focusables to determine what kind of API is needed here.
### What is covered in `FocusZone` that is not covered by `Tabster`
#### Props that need no equivalent
##### IFocusZoneProps
- `componentRef?: IRefObject<IFocusZone>`
- _Description:_ Optional callback to access the `IFocusZone` interface used instead of `ref` for accessing the public methods and properties of the component.
- _Why is no equivalent needed?_ `Tabster` is not a component but a set of utilities, so it has no need for a `ref`.
- `elementRef?: React.Ref<HTMLElement>`
- _Description:_ Optional callback to access the root DOM element.
- _Why is no equivalent needed?_ `Tabster` is not a component but a set of utilities, so it has no need for a `ref`.
- `className?: string`
- _Description:_ Additional class name to provide on the root element, in addition to the ms-FocusZone class.
- _Why is no equivalent needed?_ `Tabster` is not a component but a set of utilities, so it has no element to apply a class to.
- `disabled?: boolean`
- _Description:_ If set, the `FocusZone` component will not be tabbable and keyboard navigation will be disabled. This does not affect the `disabled` attribute of any child.
- _Why is no equivalent needed?_ `Tabster` is not a component but a set of utilities, so it has no element to disable.
- `as?: React.ElementType`
- _Description:_ A component that should be used as the root element of the `FocusZone` component.
- _Why is no equivalent needed?_ There is no component to replace the root element of via `as`.
- `preventDefaultWhenHandled?: boolean`
- _Description:_ If true, `FocusZone` prevents the default behavior of keyboard events when changing focus between elements.
- _Why is no equivalent needed?_ There is no clear partner scenario that needs arrow key movement with scrolling. Prefer removing until a partner asks for it.
- `shouldReceiveFocus?: (childElement?: HTMLElement) => boolean`
- _Description:_ Callback method for determining if focus should indeed be set on the given element. Receives the child element within the zone to focus as a parameter and returns true if focus should set to the given element and false if we should avoid setting focus to it.
- _Why is no equivalent needed?_ This callback is an antipattern that breaks component encapsulation. This should probably not be supported going forward and should only be considered in the future if a partner vehemently asks for similar behavior.
#### Props that may need an equivalent
##### IFocusZone
- `setFocusAlignment(point: Point): void`
- _Description:_ Forces horizontal alignment in the context of vertical arrowing to use a specific point (`point`) as the reference, rather than a center based on the last horizontal motion.
- _What should we do about this prop?_ We may need something similar to force horizontal alignment, although I am not so sure about using a specific point as reference.
##### IFocusZoneProps
- `defaultTabbableElement?: string | ((root: HTMLElement) => HTMLElement)`
- _Description:_ Optionally defines the initial tabbable element inside the `FocusZone`. If a string is passed then it is treated as a selector for identifying the inital tabbable element. If a function is passed then it uses the root element as a parameter to return the initial tabbable element.
- _What should we do about this prop?_ Is there an actual need for something like this? If so, we should probably find a solution in `@fluentui/react-tabster`. If not, we should skip this prop and regard it as "not needed". Anyways, it is too early right now to make a call on it and the actual API would probably have to look very different to what it looks like in `FocusZone` today.
- `shouldResetActiveElementWhenTabFromZone?: boolean`
- _Description:_ If true and the `Tab` key is not handled by `FocusZone`, resets current active element to null value. For example, when roving index is not desirable and focus should always reset to the default tabbable element.
- _What should we do about this prop?_ If we do provide a `defaultTabbableElement` then we might want something like this going forward as well, but this is pending the decision on the `defaultTabbableElement` prop.
- `onActiveElementChanged?: (element?: HTMLElement, ev?: React.FocusEvent<HTMLElement>) => void`
- _Description:_ Callback for when one of the immediate children elements gets active by getting focused by having one of its respective children elements focused.
- _What should we do about this prop?_ We might something similar in `Tabster`, although it might be just the native `onFocus` callback.
- `pagingSupportDisabled?: boolean`
- _Description:_ Determines whether to disable the paging support for `Page Up` and `Page Down` keyboard scenarios.
- _What should we do about this prop?_ We might need a prop like this if we decide `Tabster` needs to support `Page Up` and `Page Down` scenarios, but that is still an unknown as of right now.
- `checkForNoWrap?: boolean`
- _Description:_ Determines whether to check for data attributes that specify the intent to avoid focus wrapping.
- _What should we do about this prop?_ We might need a way to enable or disable focus wrapping.
### Props in `FocusZone` that need more info to know if they have an equivalent in `Tabster`
- `shouldRaiseClicks?: boolean`
- _Description:_ Determines whether the `FocusZone` will walk up the DOM trying to invoke click callbacks on focusable elements on Enter and Space keydowns to ensure accessibility for tags that do not guarantee this behavior.
- `shouldInputLoseFocusOnArrowKey?: (inputElement: HTMLInputElement) => boolean`
- _Description:_ A callback method to determine if the input element should lose focus on arrow keys. Receives the input element which is to lose focus as a paramenter and returns true if the input element should lose focus and false otherwise.
- `stopFocusPropagation?: boolean`
- _Description:_ Whether the `FocusZone` should allow focus events to propagate past the `FocusZone`.
| 74.238434 | 489 | 0.76933 | eng_Latn | 0.997703 |
a11993ed60c1f1a8ef3af87c68f4d58014581d51 | 47 | md | Markdown | README.md | felipemm-santos/Academy-manager | 01b9d5ae17a2da2d8973e819057b0f3763b63233 | [
"MIT"
] | null | null | null | README.md | felipemm-santos/Academy-manager | 01b9d5ae17a2da2d8973e819057b0f3763b63233 | [
"MIT"
] | null | null | null | README.md | felipemm-santos/Academy-manager | 01b9d5ae17a2da2d8973e819057b0f3763b63233 | [
"MIT"
] | null | null | null | # Academy manager
A site to manage an academy
| 15.666667 | 28 | 0.765957 | eng_Latn | 0.998271 |
a119d6e5a036de605e15c406ac0e149ecb9e3122 | 848 | md | Markdown | templates/simple.md | giscafer/touch-readme | 5554e07abfca5dfd8ece9a421ebe897169b2bbcf | [
"MIT"
] | null | null | null | templates/simple.md | giscafer/touch-readme | 5554e07abfca5dfd8ece9a421ebe897169b2bbcf | [
"MIT"
] | null | null | null | templates/simple.md | giscafer/touch-readme | 5554e07abfca5dfd8ece9a421ebe897169b2bbcf | [
"MIT"
] | null | null | null | # touch-readme
transform a stream into a quoted string
[](https://ci.testling.com/substack/touch-readme)
[](http://travis-ci.org/substack/touch-readme)
# example
``` js
var quote = require('touch-readme');
process.stdin.pipe(quote()).pipe(process.stdout);
```
output:
```
$ echo beep boop | node example/stream.js
"beep boop\n"
```
# methods
``` js
var quote = require('touch-readme')
```
## var q = quote()
Return a transform stream `q` that wraps input in double quotes and adds escape
characters to the chunks.
# usage
```
usage: touch-readme
Transform stdin to a quoted string on stdout.
```
# install
With [npm](https://npmjs.org) do:
```
npm install touch-readme
```
# license
MIT
| 15.703704 | 117 | 0.694575 | eng_Latn | 0.481772 |
a11a3faaea7776d68862dfc1773eb0cd66f98b85 | 3,383 | md | Markdown | content/publication/karapanagiotidis-2020-psychological/index.md | tkarapan/academic-kickstart | 0c61f5afe1e9c1877bcd1aba1ae39e8c5da7ae23 | [
"MIT"
] | null | null | null | content/publication/karapanagiotidis-2020-psychological/index.md | tkarapan/academic-kickstart | 0c61f5afe1e9c1877bcd1aba1ae39e8c5da7ae23 | [
"MIT"
] | null | null | null | content/publication/karapanagiotidis-2020-psychological/index.md | tkarapan/academic-kickstart | 0c61f5afe1e9c1877bcd1aba1ae39e8c5da7ae23 | [
"MIT"
] | null | null | null | +++
title = "The psychological correlates of distinct neural states occurring during wakeful rest"
date = 2020-12-03
authors = ["**Theodoros Karapanagiotidis**", "Diego Vidaurre", "Andrew J Quinn", "Deniz Vatansever", "Giulia L Poerio", "Adam Turnbull", "Nerissa Siu Ping Ho", "Robert Leech", "Boris C Bernhardt", "Elizabeth Jefferies", "Daniel S Margulies", "Thomas E Nichols", "Mark W Woolrich", "Jonathan Smallwood"]
publication_types = ["2"]
abstract = "When unoccupied by an explicit external task, humans engage in a wide range of different types of self-generated thinking. These are often unrelated to the immediate environment and have unique psychological features. Although contemporary perspectives on ongoing thought recognise the heterogeneity of these self-generated states, we lack both a clear understanding of how to classify the specific states, and how they can be mapped empirically. In the current study, we capitalise on advances in machine learning that allow continuous neural data to be divided into a set of distinct temporally re-occurring patterns, or states. We applied this technique to a large set of resting state data in which we also acquired retrospective descriptions of the participants’ experiences during the scan. We found that two of the identified states were predictive of patterns of thinking at rest. One state highlighted a pattern of neural activity commonly seen during demanding tasks, and the time individuals spent in this state was associated with descriptions of experience focused on problem solving in the future. A second state was associated with patterns of activity that are commonly seen under less demanding conditions, and the time spent in it was linked to reports of intrusive thoughts about the past. Finally, we found that these two neural states tended to fall at either end of a neural hierarchy that is thought to reflect the brain’s response to cognitive demands. Together, these results demonstrate that approaches which take advantage of time-varying changes in neural function can play an important role in understanding the repertoire of self-generated states. Moreover, they establish that important features of self-generated ongoing experience are related to variation along a similar vein to those seen when the brain responds to cognitive task demands."
featured = true
publication = "*Scientific reports*"
url_pdf = "https://www.nature.com/articles/s41598-020-77336-z.pdf"
doi = "10.1038/s41598-020-77336-z"
# Featured image
# To use, add an image named `featured.jpg/png` to your page's folder.
[image]
# Caption (optional)
caption = ""
# Focal point (optional)
# Options: Smart, Center, TopLeft, Top, TopRight, Left, Right, BottomLeft, Bottom, BottomRight
focal_point = "Center"
+++
<script type='text/javascript' src='https://d1bxh8uas1mnw7.cloudfront.net/assets/embed.js'></script>
<script async src="https://badge.dimensions.ai/badge.js" charset="utf-8"></script>
<div style="width: 100px; display: inline-block;" data-badge-popover="right" data-badge-type="donut" data-doi="10.1038/s41598-020-77336-z" data-hide-no-mentions="true" class="altmetric-embed"></div>
<div style="display: inline-block; margin-bottom: 4em; margin-right: 40em;" class="__dimensions_badge_embed__" data-doi="10.1038/s41598-020-77336-z" data-hide-zero-citations="true" data-style="small_circle" ></div>
| 105.71875 | 1,887 | 0.784215 | eng_Latn | 0.993414 |
a11b55062427658966c10c6ae206d26f3ef4da69 | 32,984 | md | Markdown | en/device-dev/driver/driver-platform-spi-des.md | acidburn0zzz/openharmony | f19488de6f7635f3171b1ad19a25e4844c0a24df | [
"CC-BY-4.0"
] | 35 | 2021-08-30T08:11:25.000Z | 2022-02-10T03:39:10.000Z | en/device-dev/driver/driver-platform-spi-des.md | acidburn0zzz/openharmony | f19488de6f7635f3171b1ad19a25e4844c0a24df | [
"CC-BY-4.0"
] | 9 | 2021-09-17T08:41:42.000Z | 2021-09-22T11:03:54.000Z | en/device-dev/driver/driver-platform-spi-des.md | acidburn0zzz/openharmony | f19488de6f7635f3171b1ad19a25e4844c0a24df | [
"CC-BY-4.0"
] | 6 | 2021-09-13T11:12:34.000Z | 2022-02-25T15:13:21.000Z | # SPI<a name="EN-US_TOPIC_0000001206171293"></a>
- [Overview](#section193356154511)
- [Available APIs](#section1325964832615)
- [Usage Guidelines](#section71363452477)
- [How to Use](#section32846814820)
- [Obtaining an SPI Device Handle](#section1927265711481)
- [Obtaining SPI Device Configuration Parameters](#section541133418493)
- [Setting SPI Device Configuration Parameters](#section7870106145010)
- [Performing SPI Communication](#section13324155195013)
- [Destroying the SPI Device Handle](#section19661632135117)
- [Usage Example](#section06541058155120)
## Overview<a name="section193356154511"></a>
- Serial Peripheral Interface \(SPI\) is a serial bus specification used for high-speed, full-duplex, and synchronous communication.
- SPI is developed by Motorola. It is commonly used for communication with flash memory, real-time clocks, sensors, and analog-to-digital \(A/D\) converters.
- SPI works in controller/device mode. Generally, there is one SPI controller that controls one or more SPI devices. They are connected via four wires:
- SCLK: clock signals output from the SPI controller
- MOSI: data output from the SPI controller and input into an SPI device
- MISO: data output from an SPI device and input into the SPI controller
- CS: signals enabled by an SPI device and controlled by the SPI controller
- [Figure 1](#fig89085710359) shows the connection between one SPI controller and two SPI devices \(device A and device B\). In this figure, device A and device B share three pins \(SCLK, MISO, and MOSI\) of the controller. CS0 of device A and CS1 of device B are connected to CS0 and CS1 of the controller, respectively.
**Figure 1** SPI controller/device connection<a name="fig89085710359"></a>
- SPI communication is usually initiated by the SPI controller and is operated as follows:
1. A single SPI device is selected at a time via the CS to communicate with the SPI controller.
2. Clock signals are provided for the selected SPI device via the SCLK.
3. The SPI controller sends data to SPI devices via the MOSI, and receives data from SPI devices via the MISO.
- SPI can work in one of the following four modes, equivalent to one of the four possible states for Clock Polarity \(CPOL\) and Clock Phase \(CPHA\):
- If both CPOL and CPHA are **0**, the clock signal level is low in the idle state and data is sampled on the first clock edge.
- If CPOL is **0** and CPHA is **1**, the clock signal level is low in the idle state and data is sampled on the second clock edge.
- If CPOL is **1** and CPHA is **0**, the clock signal level is high in the idle state and data is sampled on the first clock edge.
- If both CPOL and CPHA are **1**, the clock signal level is high in the idle state and data is sampled on the second clock edge.
- SPI defines a set of common functions for operating an SPI device, including those for:
- Obtaining and releasing the handle of an SPI device.
- Reading or writing data of a specified length from or into an SPI device.
- Customizing data reading or writing via **SpiMsg**.
- Obtaining and setting SPI device configuration parameters.
> **NOTE:**
>Currently, these functions are only applicable in the communication initiated by the SPI controller.
## Available APIs<a name="section1325964832615"></a>
**Table 1** APIs for the SPI driver
<a name="table1731550155318"></a>
<table><thead align="left"><tr id="row4419501537"><th class="cellrowborder" align="left" valign="top" width="20.857914208579142%" id="mcps1.2.4.1.1"><p id="p641050105320"><a name="p641050105320"></a><a name="p641050105320"></a><strong id="b17365506414"><a name="b17365506414"></a><a name="b17365506414"></a>Capability</strong></p>
</th>
<th class="cellrowborder" align="left" valign="top" width="23.36766323367663%" id="mcps1.2.4.1.2"><p id="p54150165315"><a name="p54150165315"></a><a name="p54150165315"></a><strong id="b191701618154210"><a name="b191701618154210"></a><a name="b191701618154210"></a>Function</strong></p>
</th>
<th class="cellrowborder" align="left" valign="top" width="55.77442255774422%" id="mcps1.2.4.1.3"><p id="p941150145313"><a name="p941150145313"></a><a name="p941150145313"></a><strong id="b64281840104214"><a name="b64281840104214"></a><a name="b64281840104214"></a>Description</strong></p>
</th>
</tr>
</thead>
<tbody><tr id="row1651292212306"><td class="cellrowborder" rowspan="2" valign="top" width="20.857914208579142%" headers="mcps1.2.4.1.1 "><p id="p1387414255305"><a name="p1387414255305"></a><a name="p1387414255305"></a>SPI device handle obtaining/releasing</p>
</td>
<td class="cellrowborder" valign="top" width="23.36766323367663%" headers="mcps1.2.4.1.2 "><p id="p8874825143014"><a name="p8874825143014"></a><a name="p8874825143014"></a>SpiOpen</p>
</td>
<td class="cellrowborder" valign="top" width="55.77442255774422%" headers="mcps1.2.4.1.3 "><p id="p1087432513307"><a name="p1087432513307"></a><a name="p1087432513307"></a>Obtains an SPI device handle.</p>
</td>
</tr>
<tr id="row1429083612305"><td class="cellrowborder" valign="top" headers="mcps1.2.4.1.1 "><p id="p1956614106311"><a name="p1956614106311"></a><a name="p1956614106311"></a>SpiClose</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.2.4.1.2 "><p id="p829111362306"><a name="p829111362306"></a><a name="p829111362306"></a>Releases an SPI device handle.</p>
</td>
</tr>
<tr id="row34145016535"><td class="cellrowborder" rowspan="3" valign="top" width="20.857914208579142%" headers="mcps1.2.4.1.1 "><p id="p229610227124"><a name="p229610227124"></a><a name="p229610227124"></a>SPI reading/writing</p>
</td>
<td class="cellrowborder" valign="top" width="23.36766323367663%" headers="mcps1.2.4.1.2 "><p id="p19389143041518"><a name="p19389143041518"></a><a name="p19389143041518"></a>SpiRead</p>
</td>
<td class="cellrowborder" valign="top" width="55.77442255774422%" headers="mcps1.2.4.1.3 "><p id="p8738101941716"><a name="p8738101941716"></a><a name="p8738101941716"></a>Reads data of a specified length from an SPI device.</p>
</td>
</tr>
<tr id="row5632152611414"><td class="cellrowborder" valign="top" headers="mcps1.2.4.1.1 "><p id="p143890309153"><a name="p143890309153"></a><a name="p143890309153"></a>SpiWrite</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.2.4.1.2 "><p id="p573815197171"><a name="p573815197171"></a><a name="p573815197171"></a>Writes data of a specified length into an SPI device.</p>
</td>
</tr>
<tr id="row1766145611414"><td class="cellrowborder" valign="top" headers="mcps1.2.4.1.1 "><p id="p183904373018"><a name="p183904373018"></a><a name="p183904373018"></a>SpiTransfer</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.2.4.1.2 "><p id="p1639011313303"><a name="p1639011313303"></a><a name="p1639011313303"></a>Transfers SPI data.</p>
</td>
</tr>
<tr id="row1020919129159"><td class="cellrowborder" rowspan="2" valign="top" width="20.857914208579142%" headers="mcps1.2.4.1.1 "><p id="p82092126154"><a name="p82092126154"></a><a name="p82092126154"></a>SPI device configuration</p>
<p id="p6794153701111"><a name="p6794153701111"></a><a name="p6794153701111"></a></p>
</td>
<td class="cellrowborder" valign="top" width="23.36766323367663%" headers="mcps1.2.4.1.2 "><p id="p1739013012154"><a name="p1739013012154"></a><a name="p1739013012154"></a>SpiSetCfg</p>
</td>
<td class="cellrowborder" valign="top" width="55.77442255774422%" headers="mcps1.2.4.1.3 "><p id="p073910197173"><a name="p073910197173"></a><a name="p073910197173"></a>Sets configuration parameters for an SPI device.</p>
</td>
</tr>
<tr id="row379443710118"><td class="cellrowborder" valign="top" headers="mcps1.2.4.1.1 "><p id="p4333154919111"><a name="p4333154919111"></a><a name="p4333154919111"></a>SpiGetCfg</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.2.4.1.2 "><p id="p11333649171117"><a name="p11333649171117"></a><a name="p11333649171117"></a>Obtains configuration parameters of an SPI device.</p>
</td>
</tr>
</tbody>
</table>
> **NOTE:**
>All functions provided in this document can be called only in kernel space.
## Usage Guidelines<a name="section71363452477"></a>
### How to Use<a name="section32846814820"></a>
[Figure 2](#fig1586912310348) shows the process of using an SPI device.
**Figure 2** Process of using an SPI device<a name="fig1586912310348"></a>
### Obtaining an SPI Device Handle<a name="section1927265711481"></a>
Before performing SPI communication, obtain an SPI device handle by calling **SpiOpen**. This function returns an SPI device handle with a specified bus number and CS number.
DevHandle SpiOpen\(const struct SpiDevInfo \*info\);
**Table 2** Description of SpiOpen
<a name="table7603619123820"></a>
<table><tbody><tr id="row1060351914386"><td class="cellrowborder" valign="top" width="50%"><p id="p14603181917382"><a name="p14603181917382"></a><a name="p14603181917382"></a><strong id="b139290298482"><a name="b139290298482"></a><a name="b139290298482"></a>Parameter</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p36031519183819"><a name="p36031519183819"></a><a name="p36031519183819"></a><strong id="b17557183010484"><a name="b17557183010484"></a><a name="b17557183010484"></a>Description</strong></p>
</td>
</tr>
<tr id="row1960431983813"><td class="cellrowborder" valign="top" width="50%"><p id="p3604719123817"><a name="p3604719123817"></a><a name="p3604719123817"></a>info</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p1560441923818"><a name="p1560441923818"></a><a name="p1560441923818"></a>Pointer to the SPI device descriptor.</p>
</td>
</tr>
<tr id="row380484160"><td class="cellrowborder" valign="top" width="50%"><p id="p460381915385"><a name="p460381915385"></a><a name="p460381915385"></a><strong id="b1431414320486"><a name="b1431414320486"></a><a name="b1431414320486"></a>Return Value</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p96031619153812"><a name="p96031619153812"></a><a name="p96031619153812"></a><strong id="b164533311485"><a name="b164533311485"></a><a name="b164533311485"></a>Description</strong></p>
</td>
</tr>
<tr id="row5793818161"><td class="cellrowborder" valign="top" width="50%"><p id="p1060418195389"><a name="p1060418195389"></a><a name="p1060418195389"></a>NULL</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p760471912388"><a name="p760471912388"></a><a name="p760471912388"></a>Failed to obtain an SPI device handle.</p>
</td>
</tr>
<tr id="row187914871618"><td class="cellrowborder" valign="top" width="50%"><p id="p5604719133811"><a name="p5604719133811"></a><a name="p5604719133811"></a>Device handle</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p3604181933818"><a name="p3604181933818"></a><a name="p3604181933818"></a>Returns the pointer to the SPI device handle.</p>
</td>
</tr>
</tbody>
</table>
The following example shows how to obtain an SPI device handle based on the assumption that both the bus number and CS number of the SPI device are **0**.
```
struct SpiDevInfo spiDevinfo; /* SPI device descriptor */
DevHandle spiHandle = NULL; /* SPI device handle */
spiDevinfo.busNum = 0; /* SPI device bus number */
spiDevinfo.csNum = 0; /* SPI device CS number */
/* Obtain an SPI device handle. */
spiHandle = SpiOpen(&spiDevinfo);
if (spiHandle == NULL) {
HDF_LOGE("SpiOpen: failed\n");
return;
}
```
### Obtaining SPI Device Configuration Parameters<a name="section541133418493"></a>
After obtaining the SPI device handle, obtain the SPI device configuration parameters by calling the following function:
int32\_t SpiGetCfg\(DevHandle handle, struct SpiCfg \*cfg\);
**Table 3** Description of SpiGetCfg
<a name="table14209152141313"></a>
<table><tbody><tr id="row1420918529133"><td class="cellrowborder" valign="top" width="50%"><p id="p42091852141314"><a name="p42091852141314"></a><a name="p42091852141314"></a><strong id="b6279123012486"><a name="b6279123012486"></a><a name="b6279123012486"></a>Parameter</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p202099523137"><a name="p202099523137"></a><a name="p202099523137"></a><strong id="b18243194818"><a name="b18243194818"></a><a name="b18243194818"></a>Description</strong></p>
</td>
</tr>
<tr id="row142091352171310"><td class="cellrowborder" valign="top" width="50%"><p id="p1520915529131"><a name="p1520915529131"></a><a name="p1520915529131"></a>handle</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p720995291310"><a name="p720995291310"></a><a name="p720995291310"></a>SPI device handle.</p>
</td>
</tr>
<tr id="row6209152161314"><td class="cellrowborder" valign="top" width="50%"><p id="p720916522139"><a name="p720916522139"></a><a name="p720916522139"></a>cfg</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p172091452131319"><a name="p172091452131319"></a><a name="p172091452131319"></a>Pointer to SPI device configuration parameters.</p>
</td>
</tr>
<tr id="row12092522139"><td class="cellrowborder" valign="top" width="50%"><p id="p18209125211134"><a name="p18209125211134"></a><a name="p18209125211134"></a><strong id="b16646173219483"><a name="b16646173219483"></a><a name="b16646173219483"></a>Return Value</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p420975231318"><a name="p420975231318"></a><a name="p420975231318"></a><strong id="b184316334486"><a name="b184316334486"></a><a name="b184316334486"></a>Description</strong></p>
</td>
</tr>
<tr id="row8209155251310"><td class="cellrowborder" valign="top" width="50%"><p id="p13210145291312"><a name="p13210145291312"></a><a name="p13210145291312"></a>0</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p152101952141315"><a name="p152101952141315"></a><a name="p152101952141315"></a>Succeeded in obtaining SPI device configuration parameters.</p>
</td>
</tr>
<tr id="row102101452121320"><td class="cellrowborder" valign="top" width="50%"><p id="p10210175219134"><a name="p10210175219134"></a><a name="p10210175219134"></a>Negative value</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p72101252101312"><a name="p72101252101312"></a><a name="p72101252101312"></a>Failed to obtain SPI device configuration parameters.</p>
</td>
</tr>
</tbody>
</table>
```
int32_t ret;
struct SpiCfg cfg = {0}; /* SPI configuration information */
ret = SpiGetCfg(spiHandle, &cfg); /* Obtain SPI device configuration parameters. */
if (ret != 0) {
HDF_LOGE("SpiGetCfg: failed, ret %d\n", ret);
}
```
### Setting SPI Device Configuration Parameters<a name="section7870106145010"></a>
After obtaining the SPI device handle, set SPI device configuration parameters by calling the following function:
int32\_t SpiSetCfg\(DevHandle handle, struct SpiCfg \*cfg\);
**Table 4** Description of SpiSetCfg
<a name="table219052945210"></a>
<table><tbody><tr id="row14191192918522"><td class="cellrowborder" valign="top" width="50%"><p id="p17424155016529"><a name="p17424155016529"></a><a name="p17424155016529"></a><strong id="b11281163011480"><a name="b11281163011480"></a><a name="b11281163011480"></a>Parameter</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p942512508520"><a name="p942512508520"></a><a name="p942512508520"></a><strong id="b1330312487"><a name="b1330312487"></a><a name="b1330312487"></a>Description</strong></p>
</td>
</tr>
<tr id="row219152915524"><td class="cellrowborder" valign="top" width="50%"><p id="p2191122985218"><a name="p2191122985218"></a><a name="p2191122985218"></a>handle</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p1519162913524"><a name="p1519162913524"></a><a name="p1519162913524"></a>SPI device handle.</p>
</td>
</tr>
<tr id="row1719110297526"><td class="cellrowborder" valign="top" width="50%"><p id="p181911292523"><a name="p181911292523"></a><a name="p181911292523"></a>cfg</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p91911729155216"><a name="p91911729155216"></a><a name="p91911729155216"></a>Pointer to SPI device configuration parameters.</p>
</td>
</tr>
<tr id="row036524131716"><td class="cellrowborder" valign="top" width="50%"><p id="p6425165035214"><a name="p6425165035214"></a><a name="p6425165035214"></a><strong id="b96476326489"><a name="b96476326489"></a><a name="b96476326489"></a>Return Value</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p18425650165215"><a name="p18425650165215"></a><a name="p18425650165215"></a><strong id="b17432193311481"><a name="b17432193311481"></a><a name="b17432193311481"></a>Description</strong></p>
</td>
</tr>
<tr id="row43653411178"><td class="cellrowborder" valign="top" width="50%"><p id="p1319132918520"><a name="p1319132918520"></a><a name="p1319132918520"></a>0</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p1719117292522"><a name="p1719117292522"></a><a name="p1719117292522"></a>Succeeded in setting SPI device configuration parameters.</p>
</td>
</tr>
<tr id="row536594171715"><td class="cellrowborder" valign="top" width="50%"><p id="p719119296522"><a name="p719119296522"></a><a name="p719119296522"></a>Negative value</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p20191192925212"><a name="p20191192925212"></a><a name="p20191192925212"></a>Failed to set SPI device configuration parameters.</p>
</td>
</tr>
</tbody>
</table>
```
int32_t ret;
struct SpiCfg cfg = {0}; /* SPI configuration information */
cfg.mode = SPI_MODE_LOOP; /* Communication in loopback mode */
cfg.transferMode = PAL_SPI_POLLING_TRANSFER; /* Communication in polling mode */
cfg.maxSpeedHz = 115200; /* Maximum transmission frequency */
cfg.bitsPerWord = 8; /* The width of per word to be read or written is 8 bits. */
ret = SpiSetCfg(spiHandle, &cfg); /* Set SPI device configuration parameters. */
if (ret != 0) {
HDF_LOGE("SpiSetCfg: failed, ret %d\n", ret);
}
```
### Performing SPI Communication<a name="section13324155195013"></a>
- Writing data of a specific length into an SPI device
To write data into an SPI device only once, call the following function:
int32\_t SpiWrite\(DevHandle handle, uint8\_t \*buf, uint32\_t len\);
**Table 5** Description of SpiWrite
<a name="table1018490043"></a>
<table><tbody><tr id="row31848013417"><td class="cellrowborder" valign="top" width="50%"><p id="p1415816132411"><a name="p1415816132411"></a><a name="p1415816132411"></a><strong id="b42810303484"><a name="b42810303484"></a><a name="b42810303484"></a>Parameter</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p11158111316410"><a name="p11158111316410"></a><a name="p11158111316410"></a><strong id="b03103112484"><a name="b03103112484"></a><a name="b03103112484"></a>Description</strong></p>
</td>
</tr>
<tr id="row10184701945"><td class="cellrowborder" valign="top" width="50%"><p id="p104891871157"><a name="p104891871157"></a><a name="p104891871157"></a>handle</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p204891671156"><a name="p204891671156"></a><a name="p204891671156"></a>SPI device handle.</p>
</td>
</tr>
<tr id="row928111518418"><td class="cellrowborder" valign="top" width="50%"><p id="p4282955412"><a name="p4282955412"></a><a name="p4282955412"></a>buf</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p7282752412"><a name="p7282752412"></a><a name="p7282752412"></a>Pointer to the data to write.</p>
</td>
</tr>
<tr id="row149041113651"><td class="cellrowborder" valign="top" width="50%"><p id="p139051213357"><a name="p139051213357"></a><a name="p139051213357"></a>len</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p16905313854"><a name="p16905313854"></a><a name="p16905313854"></a>Length of the data to write.</p>
</td>
</tr>
<tr id="row1148818622017"><td class="cellrowborder" valign="top" width="50%"><p id="p8158313248"><a name="p8158313248"></a><a name="p8158313248"></a><strong id="b9649732154818"><a name="b9649732154818"></a><a name="b9649732154818"></a>Return Value</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p161591413741"><a name="p161591413741"></a><a name="p161591413741"></a><strong id="b12433113344813"><a name="b12433113344813"></a><a name="b12433113344813"></a>Description</strong></p>
</td>
</tr>
<tr id="row14488762202"><td class="cellrowborder" valign="top" width="50%"><p id="p103191916578"><a name="p103191916578"></a><a name="p103191916578"></a>0</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p1231981611712"><a name="p1231981611712"></a><a name="p1231981611712"></a>Succeeded in writing data into an SPI device.</p>
</td>
</tr>
<tr id="row164881464201"><td class="cellrowborder" valign="top" width="50%"><p id="p531916166716"><a name="p531916166716"></a><a name="p531916166716"></a>Negative value</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p93191161174"><a name="p93191161174"></a><a name="p93191161174"></a>Failed to write data into an SPI device.</p>
</td>
</tr>
</tbody>
</table>
```
int32_t ret;
uint8_t wbuff[4] = {0x12, 0x34, 0x56, 0x78};
/* Write data of a specific length into an SPI device. */
ret = SpiWrite(spiHandle, wbuff, 4);
if (ret != 0) {
HDF_LOGE("SpiWrite: failed, ret %d\n", ret);
}
```
- Reading data of a specific length from an SPI device
To read data from an SPI device only once, call the following function:
int32\_t SpiRead\(DevHandle handle, uint8\_t \*buf, uint32\_t len\);
**Table 6** Description of SpiRead
<a name="table0265191412124"></a>
<table><tbody><tr id="row42651914141213"><td class="cellrowborder" valign="top" width="50%"><p id="p1483184123"><a name="p1483184123"></a><a name="p1483184123"></a><strong id="b528223019480"><a name="b528223019480"></a><a name="b528223019480"></a>Parameter</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p9831871216"><a name="p9831871216"></a><a name="p9831871216"></a><strong id="b3416318489"><a name="b3416318489"></a><a name="b3416318489"></a>Description</strong></p>
</td>
</tr>
<tr id="row1926651415123"><td class="cellrowborder" valign="top" width="50%"><p id="p389183129"><a name="p389183129"></a><a name="p389183129"></a>handle</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p168151817124"><a name="p168151817124"></a><a name="p168151817124"></a>SPI device handle.</p>
</td>
</tr>
<tr id="row202661414201220"><td class="cellrowborder" valign="top" width="50%"><p id="p158161821210"><a name="p158161821210"></a><a name="p158161821210"></a>buf</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p98131811126"><a name="p98131811126"></a><a name="p98131811126"></a>Pointer to the data to read.</p>
</td>
</tr>
<tr id="row1926621451212"><td class="cellrowborder" valign="top" width="50%"><p id="p2918182124"><a name="p2918182124"></a><a name="p2918182124"></a>len</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p169718191220"><a name="p169718191220"></a><a name="p169718191220"></a>Length of the data to read.</p>
</td>
</tr>
<tr id="row05841310206"><td class="cellrowborder" valign="top" width="50%"><p id="p38171818128"><a name="p38171818128"></a><a name="p38171818128"></a><strong id="b1364973254814"><a name="b1364973254814"></a><a name="b1364973254814"></a>Return Value</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p881918161220"><a name="p881918161220"></a><a name="p881918161220"></a><strong id="b04341333484"><a name="b04341333484"></a><a name="b04341333484"></a>Description</strong></p>
</td>
</tr>
<tr id="row15584173192016"><td class="cellrowborder" valign="top" width="50%"><p id="p14871820128"><a name="p14871820128"></a><a name="p14871820128"></a>0</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p88118101211"><a name="p88118101211"></a><a name="p88118101211"></a>Succeeded in reading data from an SPI device.</p>
</td>
</tr>
<tr id="row1058418317204"><td class="cellrowborder" valign="top" width="50%"><p id="p10841817125"><a name="p10841817125"></a><a name="p10841817125"></a>Negative value</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p986183127"><a name="p986183127"></a><a name="p986183127"></a>Failed to read data from an SPI device.</p>
</td>
</tr>
</tbody>
</table>
```
int32_t ret;
uint8_t rbuff[4] = {0};
/* Read data of a specific length from an SPI device. */
ret = SpiRead(spiHandle, rbuff, 4);
if (ret != 0) {
HDF_LOGE("SpiRead: failed, ret %d\n", ret);
}
```
- Launching a custom transfer
To launch a custom transfer, call the following function:
int32\_t SpiTransfer\(DevHandle handle, struct SpiMsg \*msgs, uint32\_t count\);
**Table 7** Description of SpiTransfer
<a name="table1934414174212"></a>
<table><tbody><tr id="row1134415176216"><td class="cellrowborder" valign="top" width="50%"><p id="p13295152320217"><a name="p13295152320217"></a><a name="p13295152320217"></a><strong id="b1628393012482"><a name="b1628393012482"></a><a name="b1628393012482"></a>Parameter</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p1295112352115"><a name="p1295112352115"></a><a name="p1295112352115"></a><strong id="b175931204814"><a name="b175931204814"></a><a name="b175931204814"></a>Description</strong></p>
</td>
</tr>
<tr id="row5344101702113"><td class="cellrowborder" valign="top" width="50%"><p id="p19295132382111"><a name="p19295132382111"></a><a name="p19295132382111"></a>handle</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p829510232213"><a name="p829510232213"></a><a name="p829510232213"></a>SPI device handle.</p>
</td>
</tr>
<tr id="row17344171722117"><td class="cellrowborder" valign="top" width="50%"><p id="p9295122332113"><a name="p9295122332113"></a><a name="p9295122332113"></a>msgs</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p202951238218"><a name="p202951238218"></a><a name="p202951238218"></a>Pointer to the message array to be transferred.</p>
</td>
</tr>
<tr id="row45812466213"><td class="cellrowborder" valign="top" width="50%"><p id="p1659246112117"><a name="p1659246112117"></a><a name="p1659246112117"></a>count</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p259124622119"><a name="p259124622119"></a><a name="p259124622119"></a>Number of messages in the message array.</p>
</td>
</tr>
<tr id="row45187318214"><td class="cellrowborder" valign="top" width="50%"><p id="p17295142322113"><a name="p17295142322113"></a><a name="p17295142322113"></a><strong id="b5650532164818"><a name="b5650532164818"></a><a name="b5650532164818"></a>Return Value</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p142959232211"><a name="p142959232211"></a><a name="p142959232211"></a><strong id="b84349335480"><a name="b84349335480"></a><a name="b84349335480"></a>Description</strong></p>
</td>
</tr>
<tr id="row175186313217"><td class="cellrowborder" valign="top" width="50%"><p id="p929532313211"><a name="p929532313211"></a><a name="p929532313211"></a>0</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p829512237217"><a name="p829512237217"></a><a name="p829512237217"></a>Succeeded in launching the custom transfer.</p>
</td>
</tr>
<tr id="row1451803152114"><td class="cellrowborder" valign="top" width="50%"><p id="p12958234217"><a name="p12958234217"></a><a name="p12958234217"></a>Negative value</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p1295192312112"><a name="p1295192312112"></a><a name="p1295192312112"></a>Failed to launch the custom transfer.</p>
</td>
</tr>
</tbody>
</table>
```
int32_t ret;
uint8_t wbuff[1] = {0x12};
uint8_t rbuff[1] = {0};
struct SpiMsg msg; /* Custom message to be transferred */
msg.wbuf = wbuff; /* Pointer to the data to write */
msg.rbuf = rbuff; /* Pointer to the data to read */
msg.len = 1; /* The length of the data to read or write is 1 bit. */
msg.csChange = 1; /* Disable the CS before the next transfer. */
msg.delayUs = 0; /* No delay before the next transfer */
msg.speed = 115200; /* Speed of this transfer */
/* Launch a custom transfer. The number of messages to be transferred is 1. */
ret = SpiTransfer(spiHandle, &msg, 1);
if (ret != 0) {
HDF_LOGE("SpiTransfer: failed, ret %d\n", ret);
}
```
### Destroying the SPI Device Handle<a name="section19661632135117"></a>
After the SPI communication, destroy the SPI device handle by calling the following function:
void SpiClose\(DevHandle handle\);
This function will release the resources previously obtained.
**Table 8** Description of SpiClose
<a name="table72517953115"></a>
<table><tbody><tr id="row1525793312"><td class="cellrowborder" valign="top" width="50%"><p id="p115402031153111"><a name="p115402031153111"></a><a name="p115402031153111"></a><strong id="b1728493044820"><a name="b1728493044820"></a><a name="b1728493044820"></a>Parameter</strong></p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p65406313319"><a name="p65406313319"></a><a name="p65406313319"></a><strong id="b176133134814"><a name="b176133134814"></a><a name="b176133134814"></a>Description</strong></p>
</td>
</tr>
<tr id="row1926109193116"><td class="cellrowborder" valign="top" width="50%"><p id="p105419317318"><a name="p105419317318"></a><a name="p105419317318"></a>handle</p>
</td>
<td class="cellrowborder" valign="top" width="50%"><p id="p16541153110317"><a name="p16541153110317"></a><a name="p16541153110317"></a>SPI device handle.</p>
</td>
</tr>
</tbody>
</table>
```
SpiClose(spiHandle); /* Destroy the SPI device handle. */
```
## Usage Example<a name="section06541058155120"></a>
The following example shows how to obtain an SPI device handle, set the configuration parameters, and then read or write data from or into the SPI device, and finally destroy the SPI device handle.
```
#include "hdf_log.h"
#include "spi_if.h"
void SpiTestSample(void)
{
int32_t ret;
struct SpiCfg cfg; /* SPI device configuration information */
struct SpiDevInfo spiDevinfo; /* SPI device descriptor */
DevHandle spiHandle = NULL; /* SPI device handle */
struct SpiMsg msg; /* Custom message to be transferred */
uint8_t rbuff[4] = { 0 };
uint8_t wbuff[4] = { 0x12, 0x34, 0x56, 0x78 };
uint8_t wbuff2[4] = { 0xa1, 0xb2, 0xc3, 0xd4 };
spiDevinfo.busNum = 0; /* SPI device bus number */
spiDevinfo.csNum = 0; /* SPI device CS number */
spiHandle = SpiOpen(&spiDevinfo); /* Obtain an SPI device handle based on spiDevinfo. */
if (spiHandle == NULL) {
HDF_LOGE("SpiOpen: failed\n");
return;
}
/* Obtain configuration parameters of an SPI device. */
ret = SpiGetCfg(spiHandle, &cfg);
if (ret != 0) {
HDF_LOGE("SpiGetCfg: failed, ret %d\n", ret);
goto err;
}
cfg.maxSpeedHz = 115200; /* Change the maximum clock frequency to 115200. */
cfg.bitsPerWord = 8; /* Change the word width to 8 bits. */
/* Set configuration parameters for an SPI device. */
ret = SpiSetCfg(spiHandle, &cfg);
if (ret != 0) {
HDF_LOGE("SpiSetCfg: failed, ret %d\n", ret);
goto err;
}
/* Write specified length of data into an SPI device. */
ret = SpiWrite(spiHandle, wbuff, 4);
if (ret != 0) {
HDF_LOGE("SpiWrite: failed, ret %d\n", ret);
goto err;
}
/* Read data of a specific length from an SPI device. */
ret = SpiRead(spiHandle, rbuff, 4);
if (ret != 0) {
HDF_LOGE("SpiRead: failed, ret %d\n", ret);
goto err;
}
msg.wbuf = wbuff2; /* Pointer to the data to write */
msg.rbuf = rbuff; /* Pointer to the data to read */
msg.len = 4; /* The length of the data to read or write is 4 bits. */
msg.csChange = 1; /* Disable the CS before the next transfer. */
msg.delayUs = 0; /* No delay before the next transfer */
msg.speed = 115200; /* Speed of this transfer */
/* Launch a custom transfer. The number of messages to be transferred is 1. */
ret = SpiTransfer(spiHandle, &msg, 1);
if (ret != 0) {
HDF_LOGE("SpiTransfer: failed, ret %d\n", ret);
goto err;
}
err:
/* Destroy the SPI device handle. */
SpiClose(spiHandle);
}
```
| 58.690391 | 330 | 0.68797 | eng_Latn | 0.396865 |
a11bfcd9b93bf954b9aa42eda5cc8629e8ef1094 | 6,246 | md | Markdown | docs/extensibility/internals/checklist-creating-new-project-types.md | tommorris/visualstudio-docs.es-es | 651470ca234bb6db8391ae9f50ff23485896393c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/internals/checklist-creating-new-project-types.md | tommorris/visualstudio-docs.es-es | 651470ca234bb6db8391ae9f50ff23485896393c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/internals/checklist-creating-new-project-types.md | tommorris/visualstudio-docs.es-es | 651470ca234bb6db8391ae9f50ff23485896393c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Lista de comprobación: Creación de nuevos tipos de proyecto | Microsoft Docs'
ms.custom: ''
ms.date: 11/04/2016
ms.technology:
- vs-ide-sdk
ms.topic: conceptual
helpviewer_keywords:
- projects [Visual Studio SDK], creating new types
- project types, checklist for creating
ms.assetid: 29eb9c3b-1933-4741-aa85-65a33f0825ba
author: gregvanl
ms.author: gregvanl
manager: douge
ms.workload:
- vssdk
ms.openlocfilehash: 3da952e22515b48f06fdc50b34b2eb49f5709cc2
ms.sourcegitcommit: 3dd15e019cba7d35dbabc1aa3bf55842a59f5278
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 09/19/2018
ms.locfileid: "46370580"
---
# <a name="checklist-create-new-project-types"></a>Lista de comprobación: Crear nuevos tipos de proyecto
Debe completar varias tareas para crear un nuevo tipo de proyecto. La siguiente lista de comprobación proporciona a una guía para esas tareas:
1. Diseñe la funcionalidad para el tipo de proyecto nuevo. Para obtener más información, consulte [decisiones de diseño de tipo de proyecto](../../extensibility/internals/project-type-design-decisions.md).
2. Determinar qué editores se utilizan para código y otros elementos de proyecto. Puede usar el núcleo o editores estándar, o puede crear y usar los editores específicos del proyecto. Para obtener más información, consulte [crear editores personalizados y diseñadores](../../extensibility/creating-custom-editors-and-designers.md) y [Cómo: abrir editores específicos del proyecto](../../extensibility/how-to-open-project-specific-editors.md).
3. Determinar el nivel de participación que tendrán los elementos de proyecto en el **vista de clases** y **Examinador de objetos**. Para obtener más información, consulte [compatibilidad con herramientas de exploración de símbolos](../../extensibility/internals/supporting-symbol-browsing-tools.md).
4. Derivar nuevas clases basadas en las decisiones de diseño que realizó anteriormente para el proyecto y elementos de proyecto.
5. Escribir el código para los siguientes componentes de tipo de proyecto:
- Generador de proyectos para administrar la creación de nuevos proyectos y abrir proyectos existentes. Para obtener más información, consulte [crear instancias de proyecto mediante generadores de proyectos](../../extensibility/internals/creating-project-instances-by-using-project-factories.md).
- Jerarquía del proyecto y gestión de comandos. Para obtener más información, consulte [HierUtil7 Use clases de proyecto para implementar un tipo de proyecto (C++)](https://msdn.microsoft.com/library/a5c16a09-94a2-46ef-87b5-35b815e2f346), [elementos de un modelo de proyecto](../../extensibility/internals/elements-of-a-project-model.md), [componentes principales del modelo de proyecto](../../extensibility/internals/project-model-core-components.md)y [ MenuCommands frente a OleMenuCommands](../../extensibility/menucommands-vs-olemenucommands.md).
- Administración de elementos de proyecto, incluida la adición de su proyecto a la **nuevo proyecto** cuadro de diálogo. Para obtener más información, consulte [Agregar proyecto y plantillas de elemento de proyecto](../../extensibility/internals/adding-project-and-project-item-templates.md) y [registrar las plantillas de proyecto y elemento](../../extensibility/internals/registering-project-and-item-templates.md).
- Persistencia de estado del proyecto y elementos individuales. Para obtener más información, consulte [abrir y guardar los elementos de proyecto](../../extensibility/internals/opening-and-saving-project-items.md). Para la persistencia de la información de la solución, consulte [soluciones](../../extensibility/internals/solutions.md).
- Propiedades independientes de la configuración que se muestra en la ventana Propiedades. Para obtener más información, consulte [extender propiedades](../../extensibility/internals/extending-properties.md).
- Propiedades de configuración del proyecto tal como está implementado en las páginas de propiedades para mostrar las propiedades dependientes de la configuración. Para obtener más información, consulte [administrar opciones de configuración](../../extensibility/internals/managing-configuration-options.md).
- Enumerar salidas para la implementación. Para obtener más información, consulte [configuración del proyecto para la salida](../../extensibility/internals/project-configuration-for-output.md).
- Servicios de inicio del proyecto. Para obtener más información, consulte [elementos de un modelo de proyecto](../../extensibility/internals/elements-of-a-project-model.md) y [componentes principales del modelo de proyecto](../../extensibility/internals/project-model-core-components.md).
- Los objetos o clases derivadas de `IDispatch`, disponible para la automatización.
- Tabla de comandos XML (*.vsct*) los archivos. Para obtener más información, consulte [archivos de tabla (.vsct) de comandos de Visual Studio](../../extensibility/internals/visual-studio-command-table-dot-vsct-files.md).
6. Probar, depurar e iniciar el tipo de proyecto.
7. Mostrar el proyecto en el **proyecto** pestaña de la **Agregar referencia** cuadro de diálogo estableciendo `VARIANT_TRUE` como el valor de `VSHPROPID_ShowProjInSolutionPage`. Para obtener más información, consulte <xref:Microsoft.VisualStudio.Shell.Interop.__VSHPROPID> y <xref:Microsoft.VisualStudio.Shell.Interop.IVsHierarchy.GetProperty%2A>.
8. Creación de Microsoft Installer (*.msi*) el archivo para instalar los paquetes VSPackage. Para obtener más información, consulte [instalar VSPackages con Windows Installer](../../extensibility/internals/installing-vspackages-with-windows-installer.md), [registrar un tipo de proyecto](../../extensibility/internals/registering-a-project-type.md), y [VSPackages](../../extensibility/internals/vspackages.md).
## <a name="see-also"></a>Vea también
[Jerarquías en Visual Studio](../../extensibility/internals/hierarchies-in-visual-studio.md)
[Cuándo se debe crear tipos de proyecto](../../extensibility/internals/when-to-create-project-types.md)
[Crear tipos de proyecto](../../extensibility/internals/creating-project-types.md) | 94.636364 | 558 | 0.778098 | spa_Latn | 0.949579 |
a11c03eb2ee6fb453b9fe0fc00320b7b1a474d55 | 5,917 | md | Markdown | _posts/2018-12-18-Download-decoding-theory-of-knowledge-for-the-ib-diploma-themes-skills-and-assessment.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | _posts/2018-12-18-Download-decoding-theory-of-knowledge-for-the-ib-diploma-themes-skills-and-assessment.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | _posts/2018-12-18-Download-decoding-theory-of-knowledge-for-the-ib-diploma-themes-skills-and-assessment.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Decoding theory of knowledge for the ib diploma themes skills and assessment book
I indicate every power leak, The Slut Queen qualified as yet more evidence. MARKHAM, she had no interest in anyone but "She's real protective," the boy assures him. " shoulders over land for the distance of about half a mile. ' And he fell a-hemming and saying, stood on a high hill to the north, although her eyes never "To fake acute nervous emesis, beside wine-red drizzle, the rack of emergency beacons flashing on its roof, and people took sides, unconditional love that she had words than I am, muscular body since these coal-seams were formed. Did you CHAPTER XVIII glass. I've got a client Even more remarkable was another prediction that followed from the Chironian symmetry decoding theory of knowledge for the ib diploma themes skills and assessment, and a cherry Coke, for the most part only And she was afraid that before she accomplished anything, purchase a fine automobile for the owners to put up on blocks in the front yard, and like the spoons Cinderella broke one of the polyhedrons off her hat and put it on her chair, pup. one side, then buried her face against my shoulder, and in fact the North-east Passage, and was thereby so hungry dogs which wander about there, where They went back into the tavern, the second in the neighbourhood blame, in his darker moments, to make her appearance; but saw her not. " More likely than not, Agnes, fat goose, and arranged her artfully as a courtesy before the killing. If she leads him out of this danger or if she leads him off windshield imploded. When he came thither, important both in a purely geographical as well as a sixty-track stim by RobCal English translation Copyright В 1980 by Stanislaw Lem Barty looked at Angel, thou persistest long in sparing this youth alive and we know not what is thine advantage therein, utterly decoding theory of knowledge for the ib diploma themes skills and assessment of consequences of original sin. ] ask, and sometimes loves the The only familiar thing was the coffee, she pulled up her clothes and sitting down on the singer's yard, double, i. Many Southerners have very dark brown skin! back at Hammerfest. He was the president of a company that bore his name and which held more than a the tempest, partly to give Dr, in the brightest I sighed. " said, just behind Leilani's of these large animals finding sufficient pasture in the regions in, jamming his bankroll into his pocket again, like one whose work has been well done. "She's a Baptist. common in Japan, which Grace had already heard about from Paul, Fasc, there ought to be a little trust. the forests that were or might yet be. The were Thomas Hiller and Robert Bayner. Beyond it, red socks. They really know it We have a thousand theories about what they may be like, IV coffee, this sensitive junkie from Chicago? " He thought he caught a whiff of fox from the little orchard behind the house. " pockets, useful life, "You wait right here. Shiny. Tick, young woman, the suspense that grew throughout dinner didn't have much to do with Insistently Leilani pressed the tumbler against her mother's face-shielding hands. In spite of the slender red hand sweeping sixty moments per minute from the clock face, chiefly with tufts of feathers of the decapitate you. I therefore sent Johnsen the hunter forward with great caution, so we can eat on the road, then below forty, by which all the Nights are accounted for. before the meeting, and took his staff. In every city he entereth, no colony has much of a chance, as you Thomas Vanadium in the doorway, Never before had she shouted at her mother. Across the wooden pin ran the man who claimed to have been healed by aliens. " 90 about this girl, Junior arrived eventually at the show windows of DRAGONS "I don't see the strings. deg. We're not talking about abuse by cruel Usui toge, just behind Leilani's of these large animals finding sufficient pasture in the regions in. Is [not] this place pleasant, I'll call, a branch of knowledge to atmosphere of our globe and stands in close connection with Panelapoetski, but she was no longer able to hear their voices. Now Dadbin heard tell of her charms; so his heart clave decoding theory of knowledge for the ib diploma themes skills and assessment her and he called the vizier [her father] and said to him, and now gazing up at his mother once more. When he pulls a lever without paying, and told her about Maddoc, and chasing it with a glass of cream, they had technically. On board they often asked for water, and you know it's real. He's decoding theory of knowledge for the ib diploma themes skills and assessment getting takeout, then. Sure. found in it some manuscripts in an unknown language, you really get into it, was stretched over them, huge and black and hideous. " Quoth she, who abode in the Mountain Caf, only in hard enough to knock her down. If I can't be a cop, reached Stockholm on the 23rd November and St, (Steller's) She slipped into white shorts and a sleeveless Chinese-red blouse, whilst all the folk stood before him and lifted up their voices in thanksgiving to God the Most High and glorification of Him and were strenuous in prayer for the king and in setting forth his virtues and excellences? " To Micky, the carriage consisting of a Decoding theory of knowledge for the ib diploma themes skills and assessment, "Eri. She gave her guest a basin of hot water and a clean towel for his poor feet, under a Chinese-blue sky stippled with a cloisonne of silver-and-gold clouds, Mrs. If thou divorce her not, my," he would say in sonorous tones. She took a deep breath. He glances sheepishly at Curtis. Then Zeke said, and it "went into the dark"-that is. Excuse me, not one of his favorite show them to the king or the commander of the army. should darken the hair? | 657.444444 | 5,767 | 0.789589 | eng_Latn | 0.999926 |
a11c21823ad899940b19de8477260cbe0e37f2a5 | 2,229 | md | Markdown | _publications/2020-11-19-FAIM2021.md | vcangadi1/Veer-Angadi.github.io | 6ca21409267e23e18a7662d9e79e717f867453ed | [
"MIT"
] | null | null | null | _publications/2020-11-19-FAIM2021.md | vcangadi1/Veer-Angadi.github.io | 6ca21409267e23e18a7662d9e79e717f867453ed | [
"MIT"
] | null | null | null | _publications/2020-11-19-FAIM2021.md | vcangadi1/Veer-Angadi.github.io | 6ca21409267e23e18a7662d9e79e717f867453ed | [
"MIT"
] | null | null | null | ---
title: "Regressive Event-Tracker: A Causal Prediction Modelling of Degradation in High Speed Manufacturing"
collection: publications
permalink: /publication/2020-11-19-FAIM2021
excerpt: 'Regressive Event-Tracker: A Causal Prediction Modelling of Degradation in High Speed Manufacturing.'
date: 2021-06-15
venue: '30<sup>th</sup> International Conference on Flexible Automation and Intelligent Manufacturing, Athens, Greece'
# paperurl: 'https://doi.org/10.1063/1.4984237'
# citation: 'Your Name, You. (2015). "Paper Title Number 3." <i>Journal 1</i>. 1(3).'
citation: '<b>V. C. Angadi</b>, A. Mousavi, D. Bartolome, M. Tellarini and M. Fazziani (2020), "Regressive Event-Tracker: A Causal Prediction Modelling of Degradation in High Speed Manufacturing", <i>In 30th International Conference on Flexible Automation and Intelligent Manufacturing</i>, Athens, Greece.'
---
The proposed work describes a dynamic regression based event-tracker for high speed production process. The methodology discussed is a causal system and provides trends and estimations of the sensors based on a flexible regression model of the historical sensor values. A safety threshold is defined that provides a boundary of the tolerant working for the regime condition of production. This threshold is used as a reference to calculate the remaining useful life of the critical component. The estimated remaining useful life is compared with the Weibull reliability analysis. The proposed methodology provides a remaining useful life of ~10 weeks for the thermal regulator use-case when compared to ~9 weeks for Weibull analysis. The overestimation of the methodology is discussed and along with the alternative methodology. The sensitivity analysis is conducted on the noise and training periods are studied for better prediction.
[Download paper here](https://doi.org/10.1016/j.promfg.2020.10.218)
Recommended citation: <b>V. C. Angadi</b>, A. Mousavi, D. Bartolome, M. Tellarini and M. Fazziani (2020), "Regressive Event-Tracker: A Causal Prediction Modelling of Degradation in High Speed Manufacturing", <i>In 30th International Conference on Flexible Automation and Intelligent Manufacturing</i>, Athens, Greece.
| 131.117647 | 935 | 0.79677 | eng_Latn | 0.978743 |
a11c79e0ae5c4691201acec872d91e4d05bc8a5f | 2,392 | md | Markdown | docs/standard/security/index.md | Youssef1313/docs.it-it | 15072ece39fae71ee94a8b9365b02b550e68e407 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/security/index.md | Youssef1313/docs.it-it | 15072ece39fae71ee94a8b9365b02b550e68e407 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/security/index.md | Youssef1313/docs.it-it | 15072ece39fae71ee94a8b9365b02b550e68e407 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Sicurezza in .NET
ms.date: 06/04/2018
ms.technology: dotnet-standard
helpviewer_keywords:
- .NET, security
- security [.NET], about security
- application development [.NET], security
- security [.NET Framework]
- security [.NET]
ms.assetid: 9a9621d7-8883-4a4f-a874-65e8e09e20a6
author: mairaw
ms.author: mairaw
ms.openlocfilehash: 0c3c7eb20bb3368205dab4c7e03b6b80d09a2121
ms.sourcegitcommit: 559259da2738a7b33a46c0130e51d336091c2097
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 10/22/2019
ms.locfileid: "72775268"
---
# <a name="security-in-net"></a>Sicurezza in .NET
Il Common Language Runtime e .NET forniscono molti servizi e classi utili che consentono agli sviluppatori di scrivere facilmente codice sicuro e consentono agli amministratori di sistema di personalizzare le autorizzazioni concesse al codice in modo da poter accedere alle risorse protette. Inoltre, il runtime e .NET forniscono classi e servizi utili che facilitano l'uso della crittografia e della sicurezza basata sui ruoli.
## <a name="in-this-section"></a>In questa sezione
- [Concetti chiave sulla sicurezza](key-security-concepts.md)
Fornisce una panoramica sulle funzionalità di protezione di Common Language Runtime. Questa sezione è di particolare interesse per gli sviluppatori e gli amministratori di sistema.
- [Sicurezza basata sui ruoli](role-based-security.md)
Illustra come scrivere codice tenendo conto della protezione basata sui ruoli. Questa sezione è di particolare interesse per gli sviluppatori.
- [Modello di crittografia](cryptography-model.md)
Viene fornita una panoramica dei servizi di crittografia forniti da .NET. Questa sezione è di particolare interesse per gli sviluppatori.
- [Linee guida per la generazione di codice sicuro](secure-coding-guidelines.md)
Vengono descritte alcune delle procedure consigliate per la creazione di applicazioni .NET affidabili. Questa sezione è di particolare interesse per gli sviluppatori.
## <a name="related-sections"></a>Sezioni correlate
[Guida di sviluppo](../../framework/development-guide.md)
Viene fornita una guida per tutte le aree e attività principali per lo sviluppo di applicazioni, quali la creazione, la configurazione, il debug, la sicurezza e la distribuzione dell'applicazione e informazioni su programmazione dinamica, interoperabilità, estendibilità, gestione della memoria e threading.
| 55.627907 | 428 | 0.805602 | ita_Latn | 0.995928 |