hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
249855402f90eea45a30d6469eb0e3fcdfb113b8 | 321 | md | Markdown | aboutme.md | LuHiCosmetics/LuHiCosmetics.github.io | ab80bd0ae7c3f218631f46d413f7485ac744446f | [
"MIT"
] | null | null | null | aboutme.md | LuHiCosmetics/LuHiCosmetics.github.io | ab80bd0ae7c3f218631f46d413f7485ac744446f | [
"MIT"
] | null | null | null | aboutme.md | LuHiCosmetics/LuHiCosmetics.github.io | ab80bd0ae7c3f218631f46d413f7485ac744446f | [
"MIT"
] | null | null | null | ---
layout: page
title: Giới thiệu về Luhi Cosmetics
meta-title: About me
subtitle: "For a start, my favorite quote is, <br> Do what you love, love what you do. "
bigimg:
- "/imgMy_Picture/avarta.jpg"
---
Với phương châm khách hàng là trên hết, LuHi Cosmetics luôn đem đến những sản phẩm chất lượng hàng đầu. | 35.666667 | 114 | 0.707165 | vie_Latn | 0.999819 |
24989488616e7c7ff3b0298924b22efb01f0f353 | 280 | md | Markdown | CHANGELOG.md | micgro42/browserslist-config-wikimedia | 2322415295ef1efc918707c7ff370f5bad771099 | [
"MIT"
] | 1 | 2021-05-16T11:17:37.000Z | 2021-05-16T11:17:37.000Z | CHANGELOG.md | micgro42/browserslist-config-wikimedia | 2322415295ef1efc918707c7ff370f5bad771099 | [
"MIT"
] | 1 | 2021-05-14T23:52:20.000Z | 2021-05-15T10:12:57.000Z | CHANGELOG.md | micgro42/browserslist-config-wikimedia | 2322415295ef1efc918707c7ff370f5bad771099 | [
"MIT"
] | 1 | 2022-01-10T19:28:45.000Z | 2022-01-10T19:28:45.000Z | # Changelog
Versions and bullets are arranged contextually chronologically from latest to oldest.
## v0.2.0 / 2021-05-16
* Replace single config file with separate files (Volker E.)
## v0.1.0 / 2021-05-14
* Add initial browserslist and 'package.json' configuration (Volker E.)
| 28 | 85 | 0.75 | eng_Latn | 0.953568 |
24998c38533aad7053a089012408d97c2627e42a | 4,663 | md | Markdown | act-4.md | uviclibraries/internet-of-things | be7fd463ffdad68dcb129c8d48a3594abe9a01bb | [
"CC-BY-4.0"
] | 1 | 2021-09-20T20:44:44.000Z | 2021-09-20T20:44:44.000Z | act-4.md | richmccue/internet-of-things | be7fd463ffdad68dcb129c8d48a3594abe9a01bb | [
"CC-BY-4.0"
] | null | null | null | act-4.md | richmccue/internet-of-things | be7fd463ffdad68dcb129c8d48a3594abe9a01bb | [
"CC-BY-4.0"
] | null | null | null | ---
layout: default
title: 4 - Send a Message
nav_order: 5
parent: Workshop Activities
---
# Press a Button to Send a Message (Facebook, Twitter, Email)
<br> **Materials Needed**
- 1 Adafruit Feather Huzzah (a type of Arduino board)
- 1 pushbutton
- 1 breadboard
- 1 LED
<img src="images/act-4/1-breadboard.png" alt="breadboard" style="float:right;width:360px;">
<br> **Hardware Setup**
1. Connect parts as in the diagram:
- The long leg of the LED should be placed with the long leg in the same row as 13 on the adafruit board and the short leg grounded
- The push button should be connected to ground on one side and pin 4 on the adafruit on the other side
2. Go to [https://bit.ly/2SOyZjC](https://bit.ly/2SOyZjC){:target="_blank"} and copy/paste the code into Arduino
3. Plug your USB cable into your computer. Go to **Tools -> Port** and select the port your Feather Huzzah is on. Now compile and upload code and watch the light turn on as you press the button!
<br>
**Triggering an Action: Create an Adafruit IO Web Feed**
<img src="images/act-4/3-serial.png" alt="serial monitor" style="float:right;width:480px;margin-left:10px;">
4. Click the magnifying glass in the top-right corner to open the serial monitor. The serial (named for serial communication) monitor shows you the values that the Feather is reading from the button. Now press the button and watch the output change!
5. Exit out of all of your Arduino IDE windows, and shutdown the program
6. Go to [http://bit.ly/2JSBlMY](http://bit.ly/2JSBlMY){:target="_blank"}. A download of an Arduino program (called a “sketch”) will automatically start. In your Arduino code editor, go to **File > Open** and select the file. Save it
<img src="images/act-4/6-view.png" alt="view" style="float:right;width:360px;margin-left:10px;">
- Edit the code to add your **IO_Username**, **IO_Key**, along with the **wifi username** and **password**. You can find your IO credentials at [https://io.adafruit.com](https://io.adafruit.com){:target="_blank"} by clicking on the **IO** tab in the top menu, then clicking the yellow **My Key** option in the top menu
- Now compile and upload code by clicking the **Upload** arrow on the top navigation bar
- After the code is loaded, go to in Adafruit IO. Click **Feeds** and then click **view all** and open your **feed** (that will be created by your IOT device).
- Click on the button on your Feather Huzzah, and you’ll see the graph on the Adafruit IO website update. Great job!
<br>
**Connecting to an IFTTT Applet**
<img src="images/act-4/7-applet.png" alt="applet" style="float:right;width:480px;margin-left:10px;margin-top:10px;">
7. Go to [ifttt.com](https://ifttt.com/){:target="_blank"} and log in or setup an account if you haven’t already. Create a new applet on IFTTT by clicking **My Applets** and then **Get more**
8. Search for “Adafruit”
- Select the **Adafruit** service
- Press the **Connect** button. A new window will prompt you for authorization. Press the **AUTHORIZE** button at the bottom
- Click **Create** and you should be presented with this screen:
<img src="" alt="" style="">
- Click the **Add** button next to the "If This" text
- Search for Adafruit and select the option that appears
- Select **Monitor a feed on Adafruit IO**
- Select **command !!!!!!!!!!!!!!!** from the drop down box, select **equal to** from the Relationship drop down, and in the value field, enter **1**. Now press **Create Trigger**
9. Click on the **Add** button next to the "Then That" text
<img src="images/act-4/12-review.png" alt="resistor" style="float:right;width:360px;">
10. Click on an output device to your liking (e.g. text, twitter, facebook, etc.). Some ideas:
- Spotify - save a track, or add track to playlist
- Facebook messenger / sms - receive a text
- Email/Gmail
- Twitter/facebook - make a status update
- The list goes on! Browse around until you find something to your liking
11. You will be asked if you want to connect to the service. Click **Connect**, and then **Accept**
12. Click through to customize the message, and click on **Create action**
13. Click **Finish**. Now every time you press the button, you should receive a text, email, message, or call (depending on how you’ve configured it!)
<img src="images/act-4/12-send.png" alt="resistor" style="width:360px;">
Great job!
[NEXT STEP: Motion Sensor to Send a Message](act-5.html){: .btn .btn-blue }
| 60.558442 | 324 | 0.695046 | eng_Latn | 0.971678 |
2499e3740fb22d2b42c1449f923536f7b1067f09 | 12,160 | markdown | Markdown | README.markdown | kupferk/puppet-hive | 48e69fa9e9a8cd5d9f00b8ccd6cd1dba3ac170d9 | [
"Apache-2.0"
] | null | null | null | README.markdown | kupferk/puppet-hive | 48e69fa9e9a8cd5d9f00b8ccd6cd1dba3ac170d9 | [
"Apache-2.0"
] | null | null | null | README.markdown | kupferk/puppet-hive | 48e69fa9e9a8cd5d9f00b8ccd6cd1dba3ac170d9 | [
"Apache-2.0"
] | null | null | null | ####Table of Contents
1. [Overview](#overview)
2. [Module Description - What the module does and why it is useful](#module-description)
3. [Setup - The basics of getting started with Hive](#setup)
* [What cesnet-hive module affects](#what-hive-affects)
* [Setup requirements](#setup-requirements)
* [Beginning with hive](#beginning-with-hive)
4. [Usage - Configuration options and additional functionality](#usage)
* [Enable Security](#security)
* [Multihome Support](#multihome)
5. [Reference - An under-the-hood peek at what the module is doing and how](#reference)
* [Classes](#classes)
* [Module Parameters](#parameters)
6. [Limitations - OS compatibility, etc.](#limitations)
7. [Development - Guide for contributing to the module](#development)
<a name="overview"></a>
##Overview
Management of Apache Hive data warehouse software. Puppet 3.x is required. Supported is the Debian (Cloudera distribution).
<a name="module-description"></a>
##Module Description
This module installs and setups Apache Hive data warehouse software running on the top of Hadoop cluster. Hive services can be collocated or separated across the hosts in the cluster. Optionally security based on Kerberos can be enabled. Security should be enabled if Hadoop cluster security is enabled.
Supported are:
* Fedora 21: only hive and hcatalog clients, native packages (tested on Hive 0.12.0)
* Debian 7/wheezy: Cloudera distribution (tested on Hive 0.13.1)
<a name="setup"></a>
##Setup
<a name="what-hive-affects"></a>
###What cesnet-hive module affects
* Packages: installs Hive packages (common packages, subsets for requested services, hcatalog, and/or hive client)
* Files modified:
* */etc/hive/\** (or */etc/hive/conf/\**)
* */usr/local/sbin/hivemanager* (not needed, only when administrator manager script is requested by *features*)
* Alternatives:
* alternatives are used for */etc/hive/conf* in Cloudera
* this module switches to the new alternative by default, so the Cloudera original configuration can be kept intact
* Services: only requested Hive services are setup and started
* metastore
* server2
* Helper Files:
* */var/lib/hadoop-hdfs/.puppet-hive-dir-created* (created by cesnet-hadoop module)
* Secret Files (keytabs): permissions are modified for hive service keytab (*/etc/security/keytab/hive.service.keytab*)
<a name="setup-requirements"></a>
###Setup Requirements
There are several known or intended limitations in this module.
Be aware of:
* **Repositories** - see cesnet-hadoop module Setup Requirements for details
* **No inter-node dependencies**: running HDFS namenode is required for Hive metastore server startup
* **Secure mode**: keytabs must be prepared in /etc/security/keytabs/ (see *realm* parameter)
* **Database setup not handled here**: basic database setup and database creation needs to be handled externally; tested are puppetlabs-mysql ad puppetlabs-postgresql modules (see examples), but it is not limited to these modules
* **Hadoop**: it should be configured locally or you should use *hdfs\_hostname* parameter (see [Module Parameters](#parameters))
<a name="beginning-with-hive"></a>
###Beginning with Hive
Let's start with brief examples.
**Example**: The simplest setup without security nor zookeeper, with everything on single machine:
class{"hive":
hdfs_hostname => $::fqdn,
metastore_hostname => $::fqdn,
server2_hostname => $::fqdn,
# security needs to be disabled explicitly by using empty string
realm => '',
}
node <HDFS_NODEMANAGER> {
# HDFS initialization must be done on the namenode
# (or /user/hive on HDFS must be created)
include hive::hdfs
}
node default {
# server
include hive::metastore
include hive::server2
# client
include hive::frontend
include hive::hcatalog
}
Modify *$::fqdn* and node(s) section as needed.
It is recommended:
* using zookeeper and set hive parameter *zookeeper\_hostnames* (cesnet-zookeeper module can be used for installation of zookeeper)
* if collocated with HDFS namenode, add dependency *Class['hadoop::namenode::service'] -> Class['hive::metastore::service']*
* if not collocated, it is needed to have HDFS namenode running first, or restart Hive metastore later
<a name="usage"></a>
##Usage
It is highly recommended to use real database backends instead of Derby. Also security can be enabled.
See the examples:
**Example 1**: Setup with security:
Additional permissions in Hadoop cluster are needed: add hive proxy user.
class{"hadoop":
...
properties => {
'hadoop.proxyuser.hive.groups' => 'hive,users',
'hadoop.proxyuser.hive.hosts' => '*',
},
...
}
class{"hive":
group => 'users',
metastore_hostname => $::fqdn,
realm => 'MY.REALM',
}
Use nodes sections from the initial **Example**, modify *$::fqdn* and nodes sections as needed.
**Example 2**: MySQL database, puppetlabs-mysql puppet module is used here.
Add this to the initial example:
class{"hive":
...
db => 'mysql',
db_password => 'hivepassword',
}
node default {
...
class { 'mysql::server':
root_password => 'strongpassword',
}
mysql::db { 'metastore':
user => 'hive',
password => 'hivepassword',
host => 'localhost',
grant => ['SELECT', 'INSERT', 'UPDATE', 'DELETE'],
sql => '/usr/lib/hive/scripts/metastore/upgrade/mysql/hive-schema-0.13.0.mysql.sql',
}
class { 'mysql::bindings':
java_enable => true,
}
Class['hive::metastore::install'] -> Mysql::Db['metastore']
Mysql::Db['metastore'] -> Class['hive::metastore::service']
Class['mysql::bindings'] -> Class['hive::metastore::config']
}
As you can see, between *hive::metastore::install* and *hive::metastore::service* is included creation of the metastore MySQL database. The reason is the required schema SQL file goes from Hive packages, and the database is then needed for running Hive metastore.
The JDBC jar-file is also needed for metastore.
**Example 3**: PostgreSQL database, puppetlabs-postgresql puppet module is used here.
Add this to the initial example:
class{"hive":
...
db => 'postgresql',
db_password => 'hivepassword',
}
node default {
...
class { 'postgresql::server':
postgres_password => 'strongpassword',
}
postgresql::server::db { 'metastore':
user => 'hive',
password => postgresql_password('hive', 'hivepass'),
}
->
exec { 'metastore-import':
command => 'cat /usr/lib/hive/scripts/metastore/upgrade/postgres/hive-schema-0.13.0.postgres.sql | psql metastore && touch /var/lib/hive/.puppet-hive-schema-imported',
path => '/bin/:/usr/bin',
user => 'hive',
creates => '/var/lib/hive/.puppet-hive-schema-imported',
}
include postgresql::lib::java
Class['postgresql::lib::java'] -> Class['hive::metastore::config']
Class['hive::metastore::install'] -> Postgresql::Server::Db['metastore']
Postgresql::Server::Db['metastore'] -> Class['hive::metastore::service']
Exec['metastore-import'] -> Class['hive::metastore::service']
}
Like with MySQL, between *hive::metastore::install* and *hive::metastore::service* is included creation of the metastore database, now PostgreSQL. The raeson is the required schema SQL file goes from Hive packages, and the database is then needed for running Hive metastore.
The JDBC jar-file is also needed for metastore.
<a name="security"></a>
###Enable Security
Security in Hadoop (and Hive) is based on Kerberos. Keytab files needs to be prepared on the proper places before enabling the security.
Following parameters are used for security (see also hive class):
* *realm* (required parameter, empty string disables the security)<br />
Enable security and Kerberos realm to use. Empty string disables the security.
To enable security, there are required:
* installed Kerberos client (Debian: krb5-user/heimdal-clients; RedHat: krb5-workstation)
* configured Kerberos client (*/etc/krb5.conf*, */etc/krb5.keytab*)
* */etc/security/keytab/hive.service.keytab* (on all server nodes)
<a name="multihome"></a>
###Multihome Support
Multihome is supported by Hive out-of-the-box.
<a name="reference"></a>
##Reference
<a name="classes"></a>
###Classes
* **hbase** - Client Support for HBase
* **hdfs** - HDFS initialiations
* init
* params
* service
* common:
* config
* daemon
* postinstall
* **frontend** - Client
* config
* install
* **hcatalog** - HCatalog Client
* config
* install
* **metastore** - Metastore
* config
* install
* service
* **server2** - Server2
* config
* install
* service
<a name="parameters"></a>
###Module Parameters
####`group` 'users'
Group where all users belong. It is not updated when changed, you should remove the /var/lib/hadoop-hdfs/.puppet-hive-dir-created file when changing or update group of /user/hive on HDFS.
####`hdfs_hostname` undef
HDFS hostname (or defaultFS value), if different from core-site.xml Hadoop file. It is recommended to have the *core-site.xml* file instead. *core-site.xml* will be created when installing any Hadoop component or if you include *hadoop::common::config* class.
####`metastore_hostname` undef
Hostname of the metastore server. When specified, remote mode is activated (recommended).
####`server2_hostname` undef
Hostname of the Hive server. Used only for hivemanager script.
####`zookeeper_hostnames` undef
Array of zookeeper hostnames quorum. Used for lock management (recommended).
####`zookeeper_port` undef
Zookeeper port, if different from the default (2181).
###`realm` undef
Kerberos realm. Use empty string if Kerberos is not used.
When security is enabled, you may also need to add these properties to Hadoop cluster:
* hadoop.proxyuser.hive.groups => 'hadoop,users' (where 'users' is the group in *group* parameter)
* hadoop.proxyuser.hive.hosts => '\*'
####`properties` undef
Additional properties.
####`descriptions` undef
Descriptions for the additional properties.
####`alternatives` 'cluster' or undef
Use alternatives to switch configuration. Use it only when supported (like with Cloudera for example).
####`db` undef
Database behind the metastore. The default is embeded database (*derby*), but it is recommended to use proper database.
Values:
* *derby* (default): embeded database
* *mysql*: MySQL/MariaDB,
* *postgresql*: PostgreSQL
####`db_host`: 'localhost'
Database hostname for *mysql*, *postgresql*, and *oracle*'. Can be overriden by *javax.jdo.option.ConnectionURL* property.
####`db_name`: 'metastore'
Database name for *mysql* and *postgresql*. For *oracle* 'xe' schema is used. Can be overriden by *javax.jdo.option.ConnectionURL* property.
####`db_user`: 'hive'
Database user for *mysql*, *postgresql*, and *oracle*.
####`db_password`: undef
Database password for *mysql*, *postgresql*, and *oracle*.
####`features` ()
Enable additional features:
* manager - script in /usr/local to start/stop Hive daemons relevant for given node
<a name="limitations"></a>
##Limitations
Idea in this module is to do only one thing - setup Hive SW - and don't limit generic usage of this module by doing other stuff. You can have your own repository with Hadoop SW, you can use this module just by *puppet apply*. You can select which Kerberos implementation, Java version, or database puppet module to use.
On other hand this leads to some limitations as mentioned in [Setup Requirements](#setup-requirements) section and you may need site-specific puppet module together with this one.
<a name="development"></a>
##Development
* Repository: [https://github.com/MetaCenterCloudPuppet/cesnet-hive](https://github.com/MetaCenterCloudPuppet/cesnet-hive)
* Testing: [https://github.com/MetaCenterCloudPuppet/hadoop-tests](https://github.com/MetaCenterCloudPuppet/hadoop-tests)
* Email: František Dvořák <[email protected]>
| 33.59116 | 319 | 0.703454 | eng_Latn | 0.931046 |
249bcea16f352830c32e6597fbc6021a88d9d67f | 112 | md | Markdown | _team/shaoshi.md | ErasmusMC-Bioinformatics/erasmusmc-bioinformatics.github.io | a4b0e047944adef967853d48f80578d7b3bb75f0 | [
"MIT"
] | 1 | 2021-01-12T15:30:52.000Z | 2021-01-12T15:30:52.000Z | _team/shaoshi.md | ErasmusMC-Bioinformatics/erasmusmc-bioinformatics.github.io | a4b0e047944adef967853d48f80578d7b3bb75f0 | [
"MIT"
] | 14 | 2020-12-04T15:39:29.000Z | 2022-02-13T21:27:31.000Z | _team/shaoshi.md | ErasmusMC-Bioinformatics/erasmusmc-bioinformatics.github.io | a4b0e047944adef967853d48f80578d7b3bb75f0 | [
"MIT"
] | 1 | 2020-12-11T14:13:55.000Z | 2020-12-11T14:13:55.000Z | ---
name: Shaoshi Zhang
position: PhD student
email: [email protected]
github_username: StringofUniverse
---
| 16 | 33 | 0.776786 | deu_Latn | 0.364119 |
249c13b57a5b5852ea0771001c694a970c4e39e4 | 1,041 | md | Markdown | README.md | gaoyongzong/marble | d34e1fcd5036fb072dec0bbd1e71bb7c524fd246 | [
"Apache-2.0"
] | 1 | 2019-04-28T00:45:56.000Z | 2019-04-28T00:45:56.000Z | README.md | gaoyonggege/marble | c0960af1c17dc2c10483a3a9b1db285a4942089d | [
"Apache-2.0"
] | null | null | null | README.md | gaoyonggege/marble | c0960af1c17dc2c10483a3a9b1db285a4942089d | [
"Apache-2.0"
] | null | null | null | # marble
前端接口数据模拟服务
轻量，简洁，自更新 的解决方案
1期支持本地化数据模拟
2期支持服务器+UI模拟
关于本地化模拟
支持json文件和js文件,且js的话支持自定义路径对应的钩子函数(👏👏👏)
## cli installation
```
npm install --save-dev marblejs
```
## cli使用方法
cli认为项目的mock数据应该和项目本身的代码放在一起，这样是最合理的。开发者可以在项目的
本目录下新建一个marble目录来存放模拟数据，您可以在其中随意新建子目录。cli会将marble目录下的所有文件[.js/.json]都认为是数据文件。文件格式应当是:
data.js:
module.exports = {
'/a': {
method: 'get',
timeout: 1,
data: {
code: 0,
msg: ''
}
}
};
data.json:
{
"/a": {
"method": "get",
"timeout": 1,
"data:" {
"code": 0,
"msg": ''s
}
}
}
当开发者写完所有数据文件后,还需要在项目的package.json文件中新建一个npm命令:
script: {
...
"mock": "marble-cli"
}
执行命令 npm run mock，则工具会启动并加载全部的数据文件，然后开发者就可以访问自定义的
接口数据了。每当改变了数据文件的内容后工具会自动热加载数据，保证接口数据永远是最新的。
## License
Apache-2.0
| 18.263158 | 85 | 0.48511 | yue_Hant | 0.557912 |
249cc92978f2b0fdf2545df7adf1a4d3775512ae | 1,972 | md | Markdown | README.md | iampavangandhi/WordCompositionProblem | efd56caa9fcd46699ee2faa768eb90fd986317f7 | [
"MIT"
] | null | null | null | README.md | iampavangandhi/WordCompositionProblem | efd56caa9fcd46699ee2faa768eb90fd986317f7 | [
"MIT"
] | null | null | null | README.md | iampavangandhi/WordCompositionProblem | efd56caa9fcd46699ee2faa768eb90fd986317f7 | [
"MIT"
] | 1 | 2022-01-16T15:36:16.000Z | 2022-01-16T15:36:16.000Z | # Word Composition Problem
To find words constructed by concatenating shorter words also found in the file.
## Input (files)
- words.txt
- words1.txt
## Output
```
ratcatdogcat catsdogcats
ethylenediaminetetraacetates ethylenediaminetetraacetate
```
## Approach
Used Trie data structure its a special tree that stores strings. Maximum number of children of a node is equal to size of alphabet. Trie supports search, insert and delete operations in O(k) time where k is length of key/word. This is obviously faster than BST and Hashing. and we can efficiently do Prefix search.
First `searchConcatWords` function read the file text and constructed Trie from the text/words using insert method present inside `trie.js` then used `findLongestString` function inside a loop to find the longest strings. Then `prefixChecker` function checks the string whether it was constructed using small words found in the Trie or not by checking the length of the result using find method present inside `trie.js` if greater than 1 increment the index and after loop ends return `true` If not there are two cases: (1) If the index is equal to 1 that means concat word is not found in the Trie and return `false` (2) Else it cuts the previous part and recursively call `prefixChecker` function again.
### Example of `prefixChecker` :
| Calling word | Output | Result |
| ------------------ | ---------------------------------------------------- | ------------------------------------------------ |
| trie.find("c") | `[ 'catxdogcatsrat', 'catsdogcats', 'cats', 'cat' ]` | Increment index and return `true` after loop |
| trie.find("catsd") | `[ 'catsdogcats' ]` and `index !== 1` | Recursive call to `prefixChecker` with `dogcats` |
| trie.find("hippo") | `[ 'hippopotamuses' ]` and `index === 1` | Concat word not found and returns `false` |
| 63.612903 | 705 | 0.65213 | eng_Latn | 0.994836 |
249e8c32431714caf69fcf2bf4e70e9206eda013 | 3,899 | md | Markdown | README.md | Joungkyun/nginx-module-krisp | fdd3a2c35768234b5800ab41383f63f648d3e4f6 | [
"BSD-2-Clause"
] | 2 | 2016-06-30T03:01:21.000Z | 2019-02-27T04:40:58.000Z | README.md | Joungkyun/nginx-module-krisp | fdd3a2c35768234b5800ab41383f63f648d3e4f6 | [
"BSD-2-Clause"
] | null | null | null | README.md | Joungkyun/nginx-module-krisp | fdd3a2c35768234b5800ab41383f63f648d3e4f6 | [
"BSD-2-Clause"
] | 1 | 2020-08-15T06:04:52.000Z | 2020-08-15T06:04:52.000Z | Nginx krisp(korea isp) module
==========
[](https://github.com/vozlt/nginx-module-krisp/blob/master/LICENSE)
Nginx krisp(korea isp) module
## Dependencies
* [nginx](http://nginx.org)
* [libkrisp](https://github.com/Joungkyun/libkrisp)
* [libipcalc](https://github.com/Joungkyun/libipcalc)
* [sqlite3](http://www.sqlite.org)
## Compatibility
* 1.7.x (last tested: 1.7.8)
* 1.6.x (last tested: 1.6.2)
Earlier versions is not tested.
## Installation
1. Clone the git repository.
```
shell> git clone git://github.com/vozlt/nginx-module-krisp.git
```
2. Add the module to the build configuration by adding
`--add-module=/path/to/nginx-module-krisp`
3. Build the nginx binary.
4. Install the nginx binary.
## Synopsis
```Nginx
http {
krisp_database /usr/share/krisp/krisp.dat;
krisp_database_interval 3600;
krisp_realip_from 10.10.10.0/24;
krisp_realip_header X-Forwarded-For;
krisp_realip_recursive on;
}
```
## Description
This is an Nginx module that create new variables with values depending on
the client IP address, using the precompiled libkrisp databases(libkrisp-data).
Krisp data is combined data that is geoip(country + city + organization) and more detail korea's isp information.
This module is mixed with ngx_http_realip_module.c from nginx-1.7.8.
If use the krisp_realip_* setting, does not need to load the builtin module(ngx_http_realip_module.c).
## Directives
### krisp_database
| - | - |
| --- | --- |
| **Syntax** | krisp_database *\<path-to-krisp-database-file\>* |
| **Default** | - |
| **Context** | http |
Description: The path of krisp database.
The following variables are available when using this database:
* $krisp_check_ip
* requested ip address.
* $krisp_isp_code
* isp(organization) code, for example, "KORNET", "BORANET".
* $krisp_isp_name
* isp(organization) name, for example, "주식회사 케이티", "주식회사 엘지유플러스"
* $krisp_country_code
* two-letter country code, for example, "KR", "US".
* $krisp_country_name
* country name, for example, "Korea, Republic of", "United States".
* $krisp_original_ip
* original client ip address.
### krisp_database_interval
| - | - |
| --- | --- |
| **Syntax** | krisp_database_interval \<*second*\> |
| **Default** | 0 |
| **Context** | http |
Description: The krisp database's reload interval second.
### krisp_realip_from
| - | - |
| --- | --- |
| **Syntax** | krisp_realip_from [*address\|CIDR\|*unix:] |
| **Default** | - |
| **Context** | http, server, location |
Description: Defines trusted addresses that are known to send correct replacement addresses. If the special value unix: is specified, all UNIX-domain sockets will be trusted.(=set_real_ip_from)
### krisp_realip_header
| - | - |
| --- | --- |
| **Syntax** | krisp_realip_header [*field*\|X-Real-IP\|X-Forwarded-For\|proxy_protocol] |
| **Default** | - |
| **Context** | http, server, location |
Description: Defines a request header field used to send the address for a replacement.(=real_ip_header)
The following variables are available when using this header field:
* $krisp_original_ip
* original client ip address.
### krisp_realip_recursive
| - | - |
| --- | --- |
| **Syntax** | krisp_realip_recursive [on\|off] |
| **Default** | - |
| **Context** | http, server, location |
Description: If recursive search is disabled, the original client address that matches one of the trusted addresses is replaced by the last address sent in the request header field defined by the real_ip_header directive. If recursive search is enabled, the original client address that matches one of the trusted addresses is replaced by the last non-trusted address sent in the request header field.(=real_ip_recursive)
## Author
YoungJoo.Kim(김영주) [<[email protected]>]
| 30.460938 | 421 | 0.693511 | eng_Latn | 0.685323 |
24a09138e434523e0c16a08795ac6fe17ed5265f | 41 | md | Markdown | README.md | Harshan164/helloworldprograms | 46ff09812b9e9a15172d332c1db9f5ac7731a355 | [
"Apache-2.0"
] | null | null | null | README.md | Harshan164/helloworldprograms | 46ff09812b9e9a15172d332c1db9f5ac7731a355 | [
"Apache-2.0"
] | null | null | null | README.md | Harshan164/helloworldprograms | 46ff09812b9e9a15172d332c1db9f5ac7731a355 | [
"Apache-2.0"
] | null | null | null | # helloworldprograms
Innovative projects
| 13.666667 | 20 | 0.878049 | eng_Latn | 0.954117 |
24a0c1a6a4f9a0ee40f53404c2dc9cbf2050357c | 376 | md | Markdown | README.md | xxxDeveloper/ts-tmpl | ef9d0e696fbc8d87d667d1b7d9aa1f488bf3d02e | [
"MIT"
] | null | null | null | README.md | xxxDeveloper/ts-tmpl | ef9d0e696fbc8d87d667d1b7d9aa1f488bf3d02e | [
"MIT"
] | null | null | null | README.md | xxxDeveloper/ts-tmpl | ef9d0e696fbc8d87d667d1b7d9aa1f488bf3d02e | [
"MIT"
] | null | null | null | <h1 align="center">
<samp style="color: #3178c6"> TS </samp>
<samp>Template</samp>
</h1>
<p align="center">
<samp>纯 TypeScript 项目的启动模版</samp>
</p>
## Features
- ⚡️ [Cli - Vite](https://vitejs.dev/)
- ⚡️ [ESLint - Antfu](https://github.com/antfu/eslint-config)
- 🛠 [Test - Vitest](https://vitest.dev/)
- 📦 [Build - Tsup](https://github.com/eghttps://tsup.egoist.sh/)
| 22.117647 | 64 | 0.619681 | yue_Hant | 0.82902 |
24a12cec3e48ee04eb216979d8a47b88c88affad | 124 | md | Markdown | README.md | madR2R/Youtube-Scraper | 666229ebd273a24f0a3e02b85ae78e9bb288b9ad | [
"MIT"
] | null | null | null | README.md | madR2R/Youtube-Scraper | 666229ebd273a24f0a3e02b85ae78e9bb288b9ad | [
"MIT"
] | null | null | null | README.md | madR2R/Youtube-Scraper | 666229ebd273a24f0a3e02b85ae78e9bb288b9ad | [
"MIT"
] | null | null | null | # Youtube-Scraper
Before running the script make sure that the latestUpload.txt and ytVidLinks.txt is empty to avoid errors
| 41.333333 | 105 | 0.822581 | eng_Latn | 0.997127 |
24a2e3f6c37814ba9552c3ff9ab39b965c13c8ca | 2,239 | md | Markdown | guides/getting-started.md | APixelVisuals/aeracord | 8abb77b6bfaeb4ff3f72dad77c74aaed9eb941aa | [
"MIT"
] | 3 | 2021-04-24T20:33:47.000Z | 2022-02-18T18:56:14.000Z | guides/getting-started.md | aeracord/aeracord | 8abb77b6bfaeb4ff3f72dad77c74aaed9eb941aa | [
"MIT"
] | null | null | null | guides/getting-started.md | aeracord/aeracord | 8abb77b6bfaeb4ff3f72dad77c74aaed9eb941aa | [
"MIT"
] | null | null | null | # Installation
Aeracord can be installed from [NPM](https://npmjs.com/package/aeracord). You can install it with the NPM CLI tool or with Yarn. Aeracord has TypeScript support built in.
NPM:
```
npm install aeracord
```
Yarn:
```
yarn add aeracord
```
Once installed, you can import it into your project as usual:
```js
// CommonJS
const aeracord = require("aeracord");
// or ES6 imports
import aeracord from "aeracord";
```
Or if you'd prefer, you can destruct the imports:
```js
// CommonJS
const { Client, Guild, User, ... } = require("aeracord");
// or ES6 imports
import { Client, Guild, User, ... } from "aeracord";
```
---
# Connecting to the Gateway
To connect to the gateway, you need to construct a new [Client](https://aeracord.pranav.page/docs/classes/Client):
```js
import { ActivityTypes, Client } from "aeracord";
// Create client
const client = new Client({
token: process.env.TOKEN,
presence: {
activities: [{
name: "say /help",
type: ActivityTypes.PLAYING
}]
},
membersIntent: true,
presencesIntent: true
});
// Event listeners
...
// Connect to the gateway
client.connect();
```
Before interacting with the API, you need to wait for the [`ready` event](https://aeracord.pranav.page/docs/classes/Client#ready). This event is fired when the client has connected to the gateway:
```js
// Ready
client.on("ready", (data) => {
// Log
console.log("Bot online");
});
```
You can also listen for various other [events](https://aeracord.pranav.page/docs/classes/Client#events), such as the [`interactionCreate` event](https://aeracord.pranav.page/docs/classes/Client#interactionCreate) for when an interaction is created:
```js
// Interaction create
client.on("interactionCreate", (interaction) => {
// Ping
if (interaction.data.name === "ping") {
// Respond
interaction.respond("Pong!");
}
});
```
---
# Other Guides
We recommend learning about how you can control what the client caches with the [caching guide](https://aeracord.pranav.page/guides/caching) as well as how you can use Aeracord's different ways of modeling data with the [Data Models](https://aeracord.pranav.page/guides/data-models) guide. | 23.819149 | 289 | 0.683787 | eng_Latn | 0.934091 |
24a335eccf05d926808fb07d624eacf7a602c2d1 | 2,097 | md | Markdown | README.md | RazaChohan/airport-reviews-api | 836504408b68782fbe4aa344725a2761c17d017c | [
"MIT"
] | null | null | null | README.md | RazaChohan/airport-reviews-api | 836504408b68782fbe4aa344725a2761c17d017c | [
"MIT"
] | null | null | null | README.md | RazaChohan/airport-reviews-api | 836504408b68782fbe4aa344725a2761c17d017c | [
"MIT"
] | null | null | null | # Airport Reviews API
Kindly follow the below given instructions in order to setup this code. Moreover the requirements
are also mentioned below together with API endpoint documentations
## System Requirements
- PHP version 5.5.9 or higher
- MySQL
- Apache or Nginx Server
## Configuration
Open a file named .env and update the configuration following conguration
```
DB_CONNECTION=mysql
DB_HOST=<HOST>
DB_PORT=3306
DB_DATABASE=<DATABASENAME>
DB_USERNAME=<DATABASE USERNAME>
DB_PASSWORD=<DATABASE PASSWORD>
```
Example
```
DB_CONNECTION=mysql
DB_HOST=localhost
DB_PORT=3306
DB_DATABASE=airport-reviews2
DB_USERNAME=root
DB_PASSWORD=password
```
## Installation
Open terminal or command prompt and execute the following command by changing your path to directory of this api
```
php composer.phar install
```
Create a database with same name as the one mentioned in .env file DB_DATABASE=<DATABASENAME> and execute following command
in terminal/command prompt
```
php artisan migrate
```
It will show the migrations that have executed successfully
## Loading Data
Use the following command for loading data from CSV file
```
php artisan load:csv
```
By default the above command with check in current folder and filename "airport.csv" but using following option is can be
overriden
```
php artisan load:csv --filename=/path/to/file/file.csv
```
## Depoying API
In order to deploy the application use the following command
```
php artisan serve
```
By default the above command will use localhost host and 8000 port but one can override it as following
```
php artisan serve --host=127.0.0.1 --port=8001
```
## Endpoints
- **[<code>GET</code> All Airport Statistics](https://github.com/RazaChohan/airport-reviews-api/blob/development/api-documentation/AllStatsEndpoint.md)**
- **[<code>GET</code> Airport Statistics](https://github.com/RazaChohan/airport-reviews-api/blob/development/api-documentation/AirportStats.md)**
- **[<code>GET</code> Airport Reviews](https://github.com/RazaChohan/airport-reviews-api/blob/development/api-documentation/AirportReviews.md)**
| 23.561798 | 153 | 0.773486 | eng_Latn | 0.938346 |
24a417a938b8c7aae406bd45eb42e8166bcc3d2e | 3,121 | md | Markdown | docs/designers/keyboard-shortcuts-for-xaml-designer.md | tommorris/visualstudio-docs.cs-cz | 92c436dbc75020bc5121cc2c9e4976f62c9b13ca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/designers/keyboard-shortcuts-for-xaml-designer.md | tommorris/visualstudio-docs.cs-cz | 92c436dbc75020bc5121cc2c9e4976f62c9b13ca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/designers/keyboard-shortcuts-for-xaml-designer.md | tommorris/visualstudio-docs.cs-cz | 92c436dbc75020bc5121cc2c9e4976f62c9b13ca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Klávesové zkratky pro Návrhář XAML
ms.date: 11/04/2016
ms.prod: visual-studio-dev15
ms.technology: vs-ide-designers
ms.topic: conceptual
ms.assetid: 40211cc7-294a-4943-85a4-941ad6418dad
author: gewarren
ms.author: gewarren
manager: douge
ms.workload:
- uwp
ms.openlocfilehash: 6eda8e27f5fbb6132027eeca87a0e6872be2415f
ms.sourcegitcommit: e5a382de633156b85b292f35e3d740f817715d47
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 07/12/2018
ms.locfileid: "38978151"
---
# <a name="keyboard-shortcuts-for-xaml-designer"></a>Klávesové zkratky pro Návrhář XAML
Klávesové zkratky v Návrháři XAML může urychlit práci díky snížení akce, které by vyžadovaly více kliknutí tlačítkem myši na jednu klávesovou zkratku.
## <a name="element-shortcuts"></a>Klávesové zkratky – element
Tato tabulka uvádí klávesové zkratky, které jsou k dispozici pro práci s elementy na návrhové ploše.
|**K provedení této akce**|**To udělat**|
|--------------------------------|-----------------|
|Vytvořit element|Stisknutím klávesy **Ctrl**+**N**|
|Duplicitní element|Podržte stisknutou klávesu **Alt** a stiskněte klávesu se šipkou.|
|Úprava textu v ovládacím prvku|Stisknutím klávesy **F2** (stiskněte **Esc** ukončíte)|
|Vyberte jeden element|Stisknutím klávesy **kartu** k výběru elementů v pořadí, jsou uvedeny v dokumentu. (Můžete také vybrat prvky pomocí kláves se šipkami.)|
|Vyberte více elementů|Stiskněte a podržte **Shift** při výběru jednotlivých prvků|
|Vybrat víc nesousedících elementy|Stiskněte a podržte **Ctrl** při výběru elementů jméno a příjmení|
|Přesunout vybrané elementy|Stisknutím klávesy se šipkami (můžete podržet **Shift** zvýšit vzdálenost přesunout na stisknutí klávesy.)|
|Otočit element v přírůstcích po 15 stupňů|Podržte stisknutou klávesu **Shift** při otáčení elementu|
|Vybrat všechny elementy|Stisknutím klávesy **Ctrl**+**A**|
|Zrušte výběr všech elementů|Stisknutím klávesy **Ctrl**+**Shift**+**A**|
|Zobrazení nebo skrytí elementu popisovačů|Stisknutím klávesy **F9**|
|Vyberte vlastnost pro daný element|Vybraný prvek a fokusu v okně Vlastnosti, stiskněte klávesu **kartu**. (Použití **Ctrl**+**kartu** změnit fokus do okna Vlastnosti.) Vyberte hodnoty vlastností z rozevíracích seznamech můžete použít klávesy se šipkami.|
## <a name="document-outline-window-shortcuts"></a>Zkratky používané v okně osnovy dokumentu
Následující tabulka uvádí klávesové zkratky, která je k dispozici při práci s elementy v okně osnovy dokumentu.
|**K provedení této akce**|**To udělat**|
|--------------------------------|-----------------|
|Skrýt objektů na návrhové ploše, když je fokus na okno osnovy dokumentu|**CTRL**+**H**|
|Zobrazit objekty na návrhové ploše, když je fokus na okno osnovy dokumentu|**SHIFT**+**Ctrl**+**H**|
|Zamknout objekty na návrhové ploše, když je fokus na okno osnovy dokumentu|**CTRL**+**L**|
|Odemknout objektů na návrhové ploše, když je fokus na okno osnovy dokumentu|**SHIFT**+**Ctrl**+**L**|
## <a name="see-also"></a>Viz také:
- [Vytvoření uživatelského rozhraní pomocí návrháře XAML](../designers/creating-a-ui-by-using-xaml-designer-in-visual-studio.md) | 58.886792 | 255 | 0.747517 | ces_Latn | 0.998501 |
24a49aaa5c9eed642145f8f25ee7ea22ae5cb511 | 1,326 | md | Markdown | README.md | 5mattmatt1/voxport | 9bfee1098f980f5c833e597c583c6b4e4fb41ccb | [
"Apache-2.0",
"MIT"
] | null | null | null | README.md | 5mattmatt1/voxport | 9bfee1098f980f5c833e597c583c6b4e4fb41ccb | [
"Apache-2.0",
"MIT"
] | null | null | null | README.md | 5mattmatt1/voxport | 9bfee1098f980f5c833e597c583c6b4e4fb41ccb | [
"Apache-2.0",
"MIT"
] | null | null | null | # Voxport
[](https://github.com/5mattmatt1/voxport/actions?query=workflow%3ARust)
[](https://opensource.org/licenses/Apache-2.0)
[](https://opensource.org/licenses/MIT)
Simple tool for converting MagicaVoxel files
## Usage
USAGE:
voxport [FLAGS] [OPTIONS] --stl --dae
FLAGS:
-d, --dae Exports in the Collada DAE format. Good for importing
-h, --help Prints help information
-s, --stl Exports in the STL (STereoLithography) format. Good for 3D Printing
-V, --version Prints version information
OPTIONS:
-i, --input <input> Input MagicaVoxel file to convert
-o, --output <output> Output file of specified export format
#### License
<sup>
Licensed under either of <a href="LICENSE-APACHE">Apache License, Version
2.0</a> or <a href="LICENSE-MIT">MIT license</a> at your option.
</sup>
<br>
<sub>
Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in this crate by you, as defined in the Apache-2.0 license, shall
be dual licensed as above, without any additional terms or conditions.
</sub> | 37.885714 | 150 | 0.717949 | eng_Latn | 0.719128 |
24a50034a879dfb892d30495b7404cd5337d184b | 11,648 | md | Markdown | Data/Job list.md | mems/calepin | 6e0554aafead895638785a270afb947062271c94 | [
"MIT"
] | 22 | 2019-02-04T15:52:33.000Z | 2022-02-21T02:31:13.000Z | Data/Job list.md | mems/calepin | 6e0554aafead895638785a270afb947062271c94 | [
"MIT"
] | 3 | 2018-12-09T14:38:59.000Z | 2019-03-23T18:54:52.000Z | Data/Job list.md | mems/calepin | 6e0554aafead895638785a270afb947062271c94 | [
"MIT"
] | 6 | 2019-12-15T16:35:52.000Z | 2021-09-23T01:53:34.000Z | - Actor, entertainer or presenter
- Actuary, economist or statistician
- Advertising accounts manager or creative director
- Advertising and public relations director
- Agricultural machinery driver
- Agriculture or fishing professional
- Air traffic controller
- Air transport operative
- Air travel assistant
- Air-conditioning and refrigeration engineer
- Aircraft maintenance and related trades
- Aircraft pilot or flight engineer
- Ambulance staff (excluding paramedics)
- Animal care services worker (other)
- Architect
- Architectural or town planning technician
- Archivist or curator
- Artist
- Arts officer, producer or director
- Assembler (electrical and electronic products)
- Assembler (vehicles and metal goods)
- Assembler and routine operative (other)
- Author, writer or translator
- Baker and flour confectioner
- Bank or post office clerk
- Bar worker
- Barrister or judge
- Beautician
- Biological scientist or biochemist
- Boat and ship builders and repairers
- Book-keeper, payroll manager or wages clerk
- Bricklayer and mason
- Broker
- Building and civil engineering technician
- Bus and coach driver
- Business and financial project management professional
- Business and related associate professional (other)
- Business and related research professional
- Business sales executive
- Business, research and administrative professional (other)
- Butcher
- Buyer and procurement officer
- Call and contact centre worker
- Care escort
- Care worker and home carer
- Careers adviser and vocational guidance specialist
- Caretaker
- Carpenter and joiner
- Catering or bar manager
- Chartered and certified accountant
- Chartered architectural technologist
- Chartered surveyor
- Chef
- Chemical and related process operative
- Chemical scientist
- Chief executive or senior official
- Child and early years officer
- Childminder
- Civil engineer
- Cleaner (non-domestic other)
- Cleaner or domestic helper
- Cleaning and housekeeping manager and supervisor
- Clergy member
- Clerical and administrative worker (other)
- Coal mine operative
- Collector salesperson or credit agent
- Communication operator
- Company secretary
- Conference and exhibition manager or organiser
- Conservation and environmental associate professional
- Conservation professional
- Construction and building trades supervisor
- Construction and building worker
- Construction operative (other)
- Construction project manager or related professional
- Construction worker
- Cook
- Counsellor
- Crane driver
- Credit controller
- Customer service manager and supervisor
- Customer service worker (other)
- Dancer or choreographer
- Debt, rent and other cash collector
- Dental nurse
- Dental practitioner
- Design and development engineer
- Dispensing optician
- Draughtsperson
- Driver and transport operative (other)
- Driving instructor
- Education adviser and school inspector
- Educational support assistant
- Electrical and electronic trades (other)
- Electrical engineer
- Electrical or electronic technician
- Electricians and electrical fitters
- Electronics engineer
- Electroplater
- Elementary services worker (other)
- Energy plant operative
- Engineering professional (other)
- Engineering technician
- Environment professional
- Environmental health professional
- Estate agent or auctioneer
- Estimator, valuer or assessor
- Farm worker
- Farmer
- Finance and investment analyst and adviser
- Finance officer
- Financial accounts manager
- Financial administrative worker (other)
- Financial and accounting technician
- Financial institution manager or director
- Financial manager or director
- Fire service officer (watch manager and below)
- Fishing or agricultural manual worker
- Fishmonger or poultry dresser
- Fitness instructor
- Floorer or wall tiler
- Florist
- Food, drink and tobacco process operative
- Footwear or leather worker
- Forestry worker
- Fork-lift truck driver
- Functional manager or director
- Furniture maker or other craft woodworker
- Further education teaching professional
- Garage manager or owner
- Gardener
- Glass and ceramics maker, decorator or finisher
- Glass and ceramics process operative
- Glazier, window fabricator or fitter
- Graphic designer
- Groundsman or greenkeeper
- Hairdresser or barber
- Hairdressing and beauty salon manager
- Health and safety officer
- Health associate professional (other)
- Health care practice manager
- Health professional (other)
- Health services and public health manager or director
- Higher education teaching professional
- Horticultural professional
- Hospital porter
- Hotel and accommodation manager or owner
- Housekeeper
- Houseparent and residential warden
- Housing officer
- Human resource manager or director
- Human resources administrative worker
- Human resources and industrial relations officer
- IT and telecoms director
- IT and telecoms professionals (other)
- IT business analyst, architect and system designer
- IT engineers
- IT operations technician
- IT project and programme manager
- IT specialist manager
- IT user support technician
- Importer and/or exporter
- Industrial cleaning process worker
- Inspector of standards and regulations
- Insurance underwriter
- Journalist, newspaper or periodical editor
- Kitchen and catering assistant
- Laboratory technician
- Large goods vehicle driver
- Launderer, dry cleaner or presser
- Legal associate professional
- Legal professional (other)
- Legal secretary
- Leisure and sports manager
- Leisure and theme park attendant
- Leisure and travel service worker (other)
- Librarian
- Library clerk
- Local government administrative worker
- Management consultant and business analyst
- Manager in agriculture and horticulture
- Manager in forestry, fishing or related services
- Manager or director in retail and wholesale
- Manager or director in storage and warehousing
- Manager or director in transport and distribution
- Manager or owner in other services
- Marine and waterways transport operative
- Market and street trader
- Market research interviewer
- Marketing and sales director
- Marketing associate professional
- Mechanical engineer
- Medical and dental technician
- Medical practitioner
- Medical radiographer
- Medical secretary
- Merchandiser and window dresser
- Metal machining setter and setter-operator
- Metal making and treating process operative
- Metal plate worker or riveter
- Metal working machine operative
- Metal working production and maintenance fitter
- Midwife
- Mobile machine driver and operative (other)
- Moulder, core maker or die caster
- Musician
- National government administrative worker
- Natural and social science professional (other)
- Non-governmental organisation (NGO) officer
- Nurse
- Nursery nurse or assistant
- Nursing auxiliary and assistant
- Occupational therapist
- Office manager
- Office supervisor
- Ophthalmic optician
- Other administrative worker
- Packer, bottler, canner or filler
- Painter and/or decorator
- Paper and wood machine operative
- Paramedic
- Parking or civil enforcement worker
- Pensions and insurance clerk
- Personal assistant or other secretary
- Pest control officer
- Pharmaceutical technician
- Pharmacist
- Pharmacy and other dispensing assistant
- Photographer or audio-visual and broadcasting equipment operator
- Physical scientist
- Physiotherapist
- Pipe fitter
- Planning, process and production technician
- Plant and machine operative (other)
- Plasterer
- Plastics process operative
- Playworker
- Plumber, heating or ventilating engineer
- Podiatrist
- Police community support officer
- Police officer (sergeant and below)
- Postal worker, mail sorter, messenger or courier
- Pre-press technician
- Precision instrument maker and repairer
- Primary and nursery education teaching professional
- Print finishing and binding worker
- Printer
- Printing machine assistant
- Prison service officer (below principal officer)
- Probation officer
- Process operative (other)
- Process plant worker (other)
- Product or clothing designer
- Production and process engineer
- Production manager or director in construction
- Production manager or director in manufacturing
- Production manager or director in mining and energy
- Programmer and software development professional
- Property, housing and estate manager
- Protective service associate professional (other)
- Psychologist
- Public relations professional
- Public services associate professional
- Publican or manager of licensed premises
- Purchasing manager or director
- Quality assurance and regulatory professional
- Quality assurance technician
- Quality control and planning engineer
- Quantity surveyor
- Quarry worker and related operative
- Rail and rolling stock builders and repairers
- Rail construction and maintenance operative
- Rail transport operative
- Rail travel assistant
- Receptionist
- Records clerk
- Refuse and salvage worker
- Research and development manager
- Residential, day and domiciliary care managers
- Restaurant and catering establishment manager or owner
- Retail and sales worker (other)
- Retail cashier and check-out operator
- Road construction operative
- Roofer, roof tiler and slater
- Roundsperson or van salesperson
- Routine inspector and tester
- Rubber process operative
- Sales accounts and business development manager
- Sales administrator
- Sales and retail assistant
- Sales related worker (other)
- Sales supervisor
- Scaffolder, stager or rigger
- School midday and crossing patrol worker
- School secretary
- Science, engineering and production technician (other)
- Secondary education teaching professional
- Security guard
- Security worker (other)
- Senior care worker
- Senior officer in fire, ambulance, prison or related services
- Senior police officer
- Senior professional at educational establishment
- Sewing machinist
- Sheet metal worker
- Shelf filler
- Ship or hovercraft officer
- Shopkeeper or store owner in wholesale and retail
- Skilled metal, electrical and electronic trades supervisor
- Skilled trader (other)
- Smith and forge worker
- Social and humanities scientist
- Social services manager or director
- Social worker
- Solicitor
- Special needs education teaching professional
- Speech and language therapist
- Sports and leisure assistant
- Sports coach, instructor or official
- Sports player
- Steel erector
- Stock control clerk
- Storage worker
- Street cleaner
- TV, video and audio engineers
- Tailor and dressmaker
- Taxation expert
- Taxi and cab driver or chauffeur
- Teaching and educational professional (other)
- Teaching assistant
- Telecommunications engineers
- Telephone salesperson
- Telephonist
- Textile process operative
- Textiles, garments and related worker (other)
- Therapy professional (other)
- Tool maker and tool fitter
- Town planning officer
- Train and tram driver
- Transport and distribution clerk
- Travel agency manager
- Travel agent
- Typist or related keyboard worker
- Tyre, exhaust and windscreen fitter
- Undertaker, mortuary and crematorium assistant
- Upholsterer
- Van driver
- Vehicle and parts salesperson and adviser
- Vehicle body builders and repairers
- Vehicle paint technicians
- Vehicle technician, mechanic or electrician
- Vehicle valeter and/or cleaner
- Veterinarian
- Veterinary nurse
- Vocational and industrial instructor
- Waiter or waitress
- Waste disposal and environmental services manager
- Water and sewerage plant operative
- Weaver and knitter
- Web design and development professional
- Weigher, grader or sorter
- Welding trader
- Welfare and housing associate professional (other)
- Welfare professional (other)
- Window cleaner
- Youth and community worker | 31.825137 | 66 | 0.807692 | eng_Latn | 0.997292 |
24a50c338db390ced3252b1fda48bf20b4dd6f81 | 2,248 | md | Markdown | README.md | eHarmony/fourie | 5a3de38ddb2fbd2fad00f2e07b54fac4039e314e | [
"BSD-3-Clause"
] | 1 | 2017-08-24T03:19:17.000Z | 2017-08-24T03:19:17.000Z | README.md | eHarmony/fourie | 5a3de38ddb2fbd2fad00f2e07b54fac4039e314e | [
"BSD-3-Clause"
] | null | null | null | README.md | eHarmony/fourie | 5a3de38ddb2fbd2fad00f2e07b54fac4039e314e | [
"BSD-3-Clause"
] | null | null | null | Author: Will Dabney (@amarack) during his internship at eHarmony.
# Example feature exppansions
nvars - number of variables/attributes to expand/interact
order - how much to expand
We get (order +1) ^ nvars variables
For expansion of 1 variable:
```
nvars=1 order=0 const
nvars=1 order=1 const, cos(1* pi * x)
nvars=1 order=2 const, cos(2* pi * x)
```
For 2 variables we get this expansion:
nvars=2
```
const
cos pi y
cos pi x
cos pi (x+y)
cos pi (2y)
cos pi (2x)
cos pi (x + 2y)
cos pi (x + 2y)
cos pi (2x + 2y)
```
need to scale x between 0 and 1
or -1,1 and need to include sin() features
```
./fourie order
./fourie 3
-1,-2
1,2
0.1,1
[expanded feats]
./fourie 3 --vw
FOO,BAR
WDABNEYMacBookPro15:fourie wdabney$ ./fourie 3
-1,-1
1,1
0.5232,-0.232
1,0.356412,-0.745941,-0.888136,-0.7324,-0.897197,0.0928573,0.963388,0.0728206,0.957802,0.609924,-0.523034,0.625733,-0.505793,-0.986274,-0.197246
-0.0232,-0.123213
1,0.192336,-0.926013,-0.548549,0.0364344,-0.97367,-0.410979,0.815577,-0.997345,-0.263287,0.896066,0.607979,-0.10911,0.954484,0.476274,-0.771275
^C
WDABNEYMacBookPro15:fourie wdabney$ ./fourie 3 --nonorm
0.53,0.2323,0.71232
1,-0.61865,-0.234545,0.908852,0.745313,-0.984903,0.473307,0.39928,0.110983,-0.849473,0.940069,-0.313674,-0.579879,-0.281343,0.927985,-0.866852,-0.0941084,-0.72396,0.989864,-0.500798,-0.733896,-0.079649,0.832446,-0.950336,-0.999856,0.605233,0.251002,-0.915797,-0.756516,0.981825,-0.458296,-0.414776,-0.982287,0.754911,0.0482359,-0.814593,-0.607182,0.999895,-0.629988,-0.220411,0.0772064,0.735558,-0.987312,0.486043,0.722268,0.0965474,-0.841726,0.944919,0.278991,0.581873,-0.998943,0.654118,0.848178,-0.108548,-0.713871,0.991821,0.985325,-0.743677,-0.0651729,0.824316,0.620573,-0.999997,0.616723,0.236926
WDABNEYMacBookPro15:fourie wdabney$ ./fourie 3 --vw
FOO,BAR
-1,-1
1,1
0.02343324 |namespace X:0.3423 Y:9343.234324 FOO:0.234 BAR:-0.343 Z:2.3434
0.02343324 |namespace X:0.3423 Y:9343.234324 Z:2.3434 FOURIER0:1 FOURIER1:0.513092 FOURIER2:-0.473473 FOURIER3:-0.998963 FOURIER4:-0.359345 FOURIER5:-0.985378 FOURIER6:-0.651834 FOURIER7:0.316477 FOURIER8:-0.741742 FOURIER9:0.19509 FOURIER10:0.94194 FOURIER11:0.771513 FOURIER12:0.892428 FOURIER13:0.845168 FOURIER14:-0.0251303 FOURIER15:-0.870957
```
| 35.125 | 602 | 0.725534 | yue_Hant | 0.425509 |
24a607b5c092726fe43915d20d385c6aedbb9987 | 280 | md | Markdown | information_plane_CNN/readme.md | mrtnoshad/EDGE | 42bfc272355719ebe7e3384399c7be1d3ac5c867 | [
"BSD-4-Clause-UC"
] | 32 | 2018-12-19T15:39:12.000Z | 2022-03-24T02:53:13.000Z | information_plane_CNN/readme.md | mrtnoshad/EDGE | 42bfc272355719ebe7e3384399c7be1d3ac5c867 | [
"BSD-4-Clause-UC"
] | 6 | 2019-06-06T11:36:09.000Z | 2021-10-12T14:30:20.000Z | information_plane_CNN/readme.md | mrtnoshad/EDGE | 42bfc272355719ebe7e3384399c7be1d3ac5c867 | [
"BSD-4-Clause-UC"
] | 6 | 2019-06-24T10:59:14.000Z | 2021-01-30T12:31:12.000Z | # Codes for the Information Plane Based on EDGE MI Estimator for the CNN Model.
#### Step 1: First run main.py in order to compate the mutual information calculations which are saved in all.npy
#### Step 2: Run plot_MI.ipynb to plot the information plane of the neural network
| 40 | 113 | 0.764286 | eng_Latn | 0.991607 |
24a6ce4d1723d0fe99a5e8fecede57ba4bcb946b | 9,357 | md | Markdown | _posts/2019-12-08-titanic_2.md | Leejigun/GitHubPageMaker | 37377a32cba6b8289e766dc6ae32c6b4272b9306 | [
"MIT"
] | null | null | null | _posts/2019-12-08-titanic_2.md | Leejigun/GitHubPageMaker | 37377a32cba6b8289e766dc6ae32c6b4272b9306 | [
"MIT"
] | null | null | null | _posts/2019-12-08-titanic_2.md | Leejigun/GitHubPageMaker | 37377a32cba6b8289e766dc6ae32c6b4272b9306 | [
"MIT"
] | null | null | null | ---
layout: post
current: post
navigation: True
title: "[Kaggle] titanic 데이터 가공"
date: 2019-12-08 00:00:03
cover: assets/images/ml/titanic/titanic_2/background.jpg
description: 케글 타이타닉 데이터 분석.
tags: [ ml ]
class: post-template
subclass: 'post tag-getting-started'
author: jglee
---
# 데이터 가공
앞서 데이터 세트와 요구사항에 대해서 몇 가지 가정을 확인헀다. 지금까지 데이터의 패턴을 파악하기 위해서 차트를 만들었지만 데이터를 변경할 필요는 없었다. 이제는 일반 데이터에서 보이지 않는 패턴을 확인하고 모델에 사용하기 위해서 데이터를 가공해본다.
## Correcting by dropping features
불필요한 특성을 제거함으로 데이터 포인트 수를 줄일 수 있다. 모델의 속도를 높이고 데이터 분석을 용이하게 한다.
우리는 우리의 가정과 결정에 근거하여 Carbin(호실 번호 - 빈 데이터가 많음) Ticket (티켓 번호 - 사용자를 구분하는 유일값) 데이터를 제거한다.
- 학습 데이터와 테스트 데이터 모든 곳에서 같은 작업을 해 일관성을 유지해야 합니다.
```python
train_df = train_df.drop(['Ticket', 'Cabin'], axis=1)
test_df = test_df.drop(['Ticket', 'Cabin'], axis=1)
```
## Creating new feature extracting from existing
이름 특성을 제거하기 전에 이름 특성에서 타이틀을 뽑아 타이틀 특성을 만들 수 있다.
타이틀로 생존 여부를 확인할 때 다음 부분을 주목해야 한다.
- 타이틀은 특정 나이대를 대표하는 경우가 많다. 예를 들어 master 타이틀을 가진 사람들의 평균 연령은 5세 이다.
- 생존율은 타이틀 나이대마다 차이가 있다.
- 대부분이 죽거나 사는 특정 타이틀들이 있다.
```python
for dataset in combine:
dataset['Title'] = dataset.Name.str.extract(' ([A-Za-z]+)\.', expand=False)
pd.crosstab(train_df['Title'], train_df['Sex'])
```
타이틀 특성과 성별의 상관 관계 - 특정 타이틀은 특정 성별을 대표한다.
```python
for dataset in combine:
dataset['Title'] = dataset['Title'].replace(['Lady', 'Countess','Capt', 'Col',\
'Don', 'Dr', 'Major', 'Rev', 'Sir', 'Jonkheer', 'Dona'], 'Rare')
dataset['Title'] = dataset['Title'].replace('Mlle', 'Miss')
dataset['Title'] = dataset['Title'].replace('Ms', 'Miss')
dataset['Title'] = dataset['Title'].replace('Mme', 'Mrs')
train_df[['Title', 'Survived']].groupby(['Title'], as_index=False).mean()
```
같은 의미를 가진 타이틀은 함치고 타이틀별 생존율을 비교한다. Mrs, Miss는 높은 생존율 보여준다.
```python
title_mapping = {"Mr": 1, "Miss": 2, "Mrs": 3, "Master": 4, "Rare": 5}
for dataset in combine:
dataset['Title'] = dataset['Title'].map(title_mapping)
dataset['Title'] = dataset['Title'].fillna(0)
train_df.head()
```
이제 이 특정 타이틀들을 가중치르를 적용 시킬 수 있도록 숫자값으로 매핑한다.
Name 특성과 PassengerId 특성을 다 사용했으니 제거해준다.
```python
train_df = train_df.drop(['Name', 'PassengerId'], axis=1)
test_df = test_df.drop(['Name'], axis=1)
combine = [train_df, test_df]
train_df.shape, test_df.shape
```
## Converting a categorical feature
이제 문자열이 포함된 특성을 숫자 값으로 변환할 수 있다. 이것은 대부분의 알고리즘 모델에 필요하다.
먼저 성별을 여성 = 1, 남성 = 0이라는 숫자로 변경해본다.
```python
for dataset in combine:
dataset['Sex'] = dataset['Sex'].map( {'female': 1, 'male': 0} ).astype(int)
train_df.head()
```
## Completing a numerical continuous feature
이제 null 값을 가진 특성을 추정 및 완료(보완)해야 한다.
1. 가장 간단한 방법은 평균과 표준 사이의 랜덤 값을 생성해 채워 넣는 것이다.
2. 더 정확한 방법은 다른 상관 특성을 사용해 추측하는 것이다. 우리는 나이, 성별, 그리고 pClass 사이의 상관 관계를 주목한다. pclass와 성별을 조합하면 평균 적인 나이를 추측할 수 있다.
3. 방법 1과 2를 결합한다. 무작위 값을 추측하는 대신에 pclass와 성별을 조합한 합성 특성에 기반해 평균과 표준 편차 사이의 무작위 숫자를 사용할 수 있다.
```python
# grid = sns.FacetGrid(train_df, col='Pclass', hue='Gender')
grid = sns.FacetGrid(train_df, row='Pclass', col='Sex', size=2.2, aspect=1.6)
grid.map(plt.hist, 'Age', alpha=.5, bins=20)
grid.add_legend()
```
먼저 위의 6가지 경우에 대한 추측값을 정할 수 있도록 빈 배열을 준비한다.
```python
guess_ages = np.zeros((2,3))
guess_ages
====
array([[0., 0., 0.],
[0., 0., 0.]])
```
이제 우리는 성별(0 또는 1)과 P클래스(1, 2, 3)에 대해 반복하여 6가지 조합에 대한 연령의 추측 값을 계산한다.
```python
for dataset in combine:
for i in range(0, 2):
for j in range(0, 3):
guess_df = dataset[(dataset['Sex'] == i) & \
(dataset['Pclass'] == j+1)]['Age'].dropna()
# age_mean = guess_df.mean()
# age_std = guess_df.std()
# age_guess = rnd.uniform(age_mean - age_std, age_mean + age_std)
age_guess = guess_df.median()
# Convert random age float to nearest .5 age
guess_ages[i,j] = int( age_guess/0.5 + 0.5 ) * 0.5
for i in range(0, 2):
for j in range(0, 3):
dataset.loc[ (dataset.Age.isnull())
& (dataset.Sex == i)
& (dataset.Pclass == j+1),\
'Age'] = guess_ages[i,j]
dataset['Age'] = dataset['Age'].astype(int)
train_df.head()
```
나이대(age band) 특성을 만들고 생존율과 상관 관계를 추측한다.
```python
train_df['AgeBand'] = pd.cut(train_df['Age'], 5)
train_df[['AgeBand', 'Survived']].groupby(['AgeBand'], as_index=False)
.mean()
.sort_values(by='AgeBand', ascending=True)
```
이제 band가 표시되는 튜플 형태인 데이터를 수정해 순차적 데이터로 만든다.
```python
for dataset in combine:
dataset.loc[ dataset['Age'] <= 16, 'Age'] = 0
dataset.loc[(dataset['Age'] > 16) & (dataset['Age'] <= 32), 'Age'] = 1
dataset.loc[(dataset['Age'] > 32) & (dataset['Age'] <= 48), 'Age'] = 2
dataset.loc[(dataset['Age'] > 48) & (dataset['Age'] <= 64), 'Age'] = 3
dataset.loc[ dataset['Age'] > 64, 'Age']
train_df.head()
```
age값을 수정했으니 age band 특성은 이제 제거해준다.
```python
train_df = train_df.drop(['AgeBand'], axis=1)
combine = [train_df, test_df]
train_df.head()
```
## Create new feature combining existing features
우리는 Parch 특성과 SibSp 특성을 합쳐 FamilySize 특성을 만들 수 있다.
```python
for dataset in combine:
dataset['FamilySize'] = dataset['SibSp'] + dataset['Parch'] + 1
train_df[['FamilySize', 'Survived']].groupby(['FamilySize'], as_index=False)
.mean()
.sort_values(by='Survived', ascending=False)
```
그리고 가족이 없는 사람은 따로 가중치를 적용할 수 있도록 isAlone 이라는 특성을 만든다.
```python
for dataset in combine:
dataset['IsAlone'] = 0
dataset.loc[dataset['FamilySize'] == 1, 'IsAlone'] = 1
train_df[['IsAlone', 'Survived']].groupby(['IsAlone'], as_index=False).mean()
```
그리고 다시 Parch, SibSp 특성을 제거한다.
```python
train_df = train_df.drop(['Parch', 'SibSp', 'FamilySize'], axis=1)
test_df = test_df.drop(['Parch', 'SibSp', 'FamilySize'], axis=1)
combine = [train_df, test_df]
train_df.head()
```
이제 pclass 와 나이를 합친 혼합 특성을 만들 수 있다.
```python
for dataset in combine:
dataset['Age*Class'] = dataset.Age * dataset.Pclass
train_df.loc[:, ['Age*Class', 'Age', 'Pclass']].head(10)
```
## Completing a categorical feature
Embarked 특성은 S, Q, C 의 데이터를 가진 범주형 특성이다. 그리고 Embarked 특성은 빈 데이터가 상당히 많은데, 가장 많이 발견되는 데이터인 S로 채운다.
```python
freq_port = train_df.Embarked.dropna().mode()[0]
freq_port
======
'S'
for dataset in combine:
dataset['Embarked'] = dataset['Embarked'].fillna(freq_port)
train_df[['Embarked', 'Survived']].groupby(['Embarked'], as_index=False)
.mean()
.sort_values(by='Survived', ascending=False)
```
## Converting categorical feature to numeric
Embarked 특성이 이제 빈 자리가 없으니 다시 숫자형 데이터로 바꿔주자.
```python
for dataset in combine:
dataset['Embarked'] = dataset['Embarked'].map( {'S': 0, 'C': 1, 'Q': 2} ).astype(int)
train_df.head()
```
## Quick completing and converting a numeric feature
우리는 이제 누락이 많은 Fare 퀄럼 데이터에 대해서 값을 채워넣을 수 있다.
```python
test_df['Fare'].fillna(test_df['Fare'].dropna().median(), inplace=True)
test_df.head()
```
이제 이 Fare 데이터를 다시 범위형 데이터로 변경한다.
```python
train_df['FareBand'] = pd.qcut(train_df['Fare'], 4)
train_df[['FareBand', 'Survived']].groupby(['FareBand'], as_index=False)
.mean()
.sort_values(by='FareBand', ascending=True)
```
그리고 그 범위형 데이터를 순서형 데이터로 다시 변경하고 이제 범위형 데이터 퀄럼을 제거한다.
```python
for dataset in combine:
dataset.loc[ dataset['Fare'] <= 7.91, 'Fare'] = 0
dataset.loc[(dataset['Fare'] > 7.91) & (dataset['Fare'] <= 14.454), 'Fare'] = 1
dataset.loc[(dataset['Fare'] > 14.454) & (dataset['Fare'] <= 31), 'Fare'] = 2
dataset.loc[ dataset['Fare'] > 31, 'Fare'] = 3
dataset['Fare'] = dataset['Fare'].astype(int)
train_df = train_df.drop(['FareBand'], axis=1)
combine = [train_df, test_df]
train_df.head(10)
```
| 29.51735 | 140 | 0.669766 | kor_Hang | 0.987785 |
24a7359508a654d02bd58f642a10f9fd74b55ada | 84 | md | Markdown | README.md | douglasduteil/bar-jumbotron | b935f2fed9c4d1440f2c624ee1e9f0c9c18e7f0d | [
"MIT"
] | null | null | null | README.md | douglasduteil/bar-jumbotron | b935f2fed9c4d1440f2c624ee1e9f0c9c18e7f0d | [
"MIT"
] | null | null | null | README.md | douglasduteil/bar-jumbotron | b935f2fed9c4d1440f2c624ee1e9f0c9c18e7f0d | [
"MIT"
] | null | null | null | # bar-jumbotron
> Dummy bar-jumbotron ( AssemblyLine/ng-component-machinery demo )
| 21 | 66 | 0.77381 | ind_Latn | 0.146551 |
24a791fc13cf2c5d7a4aad0447166e63a296aee7 | 39,660 | markdown | Markdown | _posts/2009-02-27-systems-and-methods-for-providing-a-library-of-virtual-images-in-a-software-provisioning-environment.markdown | LizetteO/Tracking.virtually.unlimited.number.tokens.and.addresses | 89c6b0fa3defa14758d6794027cc15150d005bbd | [
"Apache-2.0"
] | null | null | null | _posts/2009-02-27-systems-and-methods-for-providing-a-library-of-virtual-images-in-a-software-provisioning-environment.markdown | LizetteO/Tracking.virtually.unlimited.number.tokens.and.addresses | 89c6b0fa3defa14758d6794027cc15150d005bbd | [
"Apache-2.0"
] | null | null | null | _posts/2009-02-27-systems-and-methods-for-providing-a-library-of-virtual-images-in-a-software-provisioning-environment.markdown | LizetteO/Tracking.virtually.unlimited.number.tokens.and.addresses | 89c6b0fa3defa14758d6794027cc15150d005bbd | [
"Apache-2.0"
] | 2 | 2019-10-31T13:03:55.000Z | 2020-08-13T12:57:08.000Z | ---
title: Systems and methods for providing a library of virtual images in a software provisioning environment
abstract: A provisioning server can maintain a library of virtual images. The virtual images can be a disk image of software that has been previously installed according to metadata. The metadata can represent parameters utilized to create the virtual image and the parameters required to provision the virtual image on a target machine. The provisioning server can maintain the metadata for a virtual image in a virtual image record associated with the virtual image. The provisioning server can provision a virtual image to one or more target machines. To provision the virtual image, the provisioning server can copy the virtual image to a storage device on the one or more target machines and configure the target machine according to metadata in the associated virtual image record.
url: http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-adv.htm&r=1&f=G&l=50&d=PALL&S1=08572587&OS=08572587&RS=08572587
owner: Red Hat, Inc.
number: 08572587
owner_city: Raleigh
owner_country: US
publication_date: 20090227
---
This invention relates generally to software provisioning. In particular the invention relates to systems and methods for providing maintaining and provisioning virtual images in a software provisioning environment.
Software provisioning is the process of selecting a target machine such as a server loading the appropriate software operating system device drivers middleware and applications and customizing and configuring the system and the software to make it ready for operation. Software provisioning can entail a variety of tasks such as creating or changing a boot image specifying parameters e.g. IP address IP gateway to find associated network and storage resources and then starting the machine and its newly loaded software. Typically a system administrator will perform these tasks using various tools because of the complexity of these tasks. Unfortunately there is a lack of provisioning control tools that can adequately integrate and automate these tasks.
For most software provisioning the software being installed must be customized and configured for each system in order to make it ready for operation. This installation processes must be repeated multiple times for a large network of systems. Often the same or identical software is the subject of the installation process and must be installed in and configured for each system.
For simplicity and illustrative purposes the principles of the present invention are described by referring mainly to exemplary embodiments thereof. However one of ordinary skill in the art would readily recognize that the same principles are equally applicable to and can be implemented in all types of information and systems and that any such variations do not depart from the true spirit and scope of the present invention. Moreover in the following detailed description references are made to the accompanying figures which illustrate specific embodiments. Electrical mechanical logical and structural changes may be made to the embodiments without departing from the spirit and scope of the present invention. The following detailed description is therefore not to be taken in a limiting sense and the scope of the present invention is defined by the appended claims and their equivalents.
Embodiments of the present teachings relate to systems and methods for providing and provisioning virtual images in a software provisioning environment. More particularly a provisioning server can maintain a library of virtual images and perform provisioning process on target machines utilizing the virtual images.
According to embodiments the provisioning server can be configured to maintain a library of virtual images. The virtual images can be a disk image of software that has been previously installed according to metadata. The metadata can represent parameters utilized to create the virtual image and the parameters required to provision the virtual image on a target machine. The provisioning server can be configured to maintain the metadata for a virtual image in a virtual image record associated with the virtual image.
According to embodiments the provisioning server can be configured to provision a virtual image to one or more target machines. To provision the virtual image the provisioning server can be configured to copy the virtual image to a storage device on the one or more target machines and configure the target machine according to metadata in the associated virtual image record. The provisioning server can be configured to provision and instantiate the virtual image directly or instruct a helper client to provision and instantiate the virtual image.
According to embodiments the provisioning server can be configured to generate the virtual images and store the virtual images in the library of virtual images. Additionally the provisioning server can be configured to create the virtual image record from the metadata associated with the virtual image. Likewise the provisioning server can be configured to receive the virtual image metadata and or virtual image record from an external source.
By utilizing a virtual image to deliver software the provisioning server can install an instance of software once create the virtual image and clone the virtual image on any number of target machines. Because the virtual image includes the software in an installed state the time for provisioning duplicate or similar software can be reduced by copying the virtual image to a target machine thereby eliminating the need to re install duplicate or similar software on each target machine.
In particular the provisioning environment can manage software provisioning using a hierarchy of commands. In exemplary embodiments the hierarchy can include at least four levels of commands. The lowest level in the hierarchy can comprise distribution commands which primarily handle base operating system specific tasks of provisioning. The second level can comprise profile commands which associate a configuration file such as a kickstart file for Linux or other operating system with a distribution and optionally allow for customization. The third level comprises system commands which associate remote systems that are involved with the provisioning of the software. The fourth level comprises repository commands which address configurations and tasks related to updating the software remote installation procedures and optionally customizing the software.
The provisioning environment provides several capabilities and advantages over the known provisioning solutions. For example the present invention is capable of handling a variety of forms of installations such as preboot execution environment PXE virtualization re installations and image installations.
In exemplary aspects the provisioning environment enables integrating virtualization into a PXE provisioning infrastructure and provides several options to reinstall running machines as well. The provisioning environment can integrate mirroring of package repositories with the provisioning process so that a provisioning server may serve as a central mirror point of contact for all of an organization s software needs. In aspects a set of remote mirrored repositories can automatically be used by provisioned systems without additional setup.
Reference will now be made in detail to the exemplary aspects the provisioning environment . The provisioning environment can be applied to provisioning any form of software such as Windows systems UNIX systems and Linux systems. In the exemplary description that follows is presented to explain the provisioning environment for provisioning software such as Linux and Linux based software such as Fedora and Red Hat Enterprise Linux by Red Hat Inc.
In provisioning of software such as Linux many system administrators use what is known as the kickstart installation method. Kickstart files are files that specify the intended configuration of the software being provisioned. Kickstart files can be kept on a server and can be read by individual computers during the installation. This installation method allows the use of a single or relatively few standard kickstart files to install Linux on multiple machines making it ideal for network and system administrators.
The kickstart file can be a simple text file containing a list of items each identified by a keyword. In general a kickstart file can be edited with any text editor or word processor that can save files as ASCII text. One skilled in the art will recognize that the present invention may be applied to non kickstart files in software provisioning. For example configuration files such as AutoYAST Answer files used in Novell SuSe Linux and Sun Solaris Jumpstart files may also be used by the provisioning environment .
Typically a kickstart file can be copied to the boot disk or made available on the network. The network based approach is most commonly used as most kickstart installations for software provisioning such as Linux systems tend to be performed via a network using NES FTP or HTTP on networked computers. Administrators also find it desirable that kickstart installations can be performed using a local CD ROM or a local hard drive.
Using kickstart files a system administrator can create a single file containing the parameters that are needed to complete a typical software installation. For example kickstart files specify parameters related to language selection mouse configuration keyboard selection boot loader installation disk partitioning network configuration NIS LDAP Kerberos Hesiod and Samba authentication firewall configuration and package selection.
According to exemplary aspects illustrated in the provisioning environment can include a provisioning server a code repository which provides access to distributions and a set of installation templates a set of exception plugins a helper client running on target machines in a network a provisioning database which comprises a distribution tree list and template list . Each of these components will now be further described.
The provisioning server from herein referred to as a cobbler is responsible for serving as an extensible markup language remote procedure call XMLRPC handler linking to or mirroring install distribution trees and a configuration database hosting kickstart templates hosting plugins generating installation images and the like. The cobbler server can be implemented as software such as Python code installed on a boot server machine and provide a command line interface for configuration of the boot server. In addition the cobbler server can make itself available as a Python application programming interface API for use by higher level management software not shown . The cobbler server supports provisioning via PXE image ISO installation virtualization re provisioning. As will be described later the last two modes are performed with the assistance of a helper client .
The code repository is responsible for hosting distributions and . The code repository can be implemented using well known components of hardware and software. Additionally the code repository can include one or more repositories hosting distributions. The distributions and can include bundles of software that are already compiled and configured. The distributions and may be in the form of either rpm deb tgz msi exe formats and the like. For example as Linux distributions the distributions and are bundles of software that comprise the Linux kernel the non kernel parts of the operating system and assorted other software. The distributions and can take a variety of forms from fully featured desktop and server operating systems to minimal environments.
In exemplary aspects the installation templates are any data structure or processing element that can be combined with a set of installation configurations and processed to produce a resulting configuration file such as a kickstart file.
In exemplary aspects exception plugins are software that interact with cobbler server to customize the provisioning of software. In general the exception plugins are intended to address infrequent customization needs.
In exemplary aspects the helper client known as koan which stands for kickstart over a network can assist the cobbler server during the provisioning processes. The koan can allow for both network provisioning of new virtualized guests and destructive provisioning of any existing system. When invoked the koan can request profile information from a remote boot server that has been configured with the cobbler server . In some aspects what the koan does with the profile data depends on whether it was invoked with virt or replace self.
In exemplary aspects the koan can enable replacing running systems as well as installing virtualized profiles. The koan can also be pushed out to systems automatically from the boot server. In some aspects the koan client is also written in Python code to accommodate a variety of operating systems machine architectures etc.
In exemplary aspects the network can include a number of the target machines . The target machines can represent the particular machines to which software provisioning is directed. The target machines can represent a wide variety of computing devices such as personal computers servers laptop computers personal mobile devices and the like. In some aspects the target machines can represent distributed computing environments such as cloud computing environments. Although shows several of the target machines the provisioning environment can be capable of managing a wide range environments such as datacenters with thousands of machines or server pools with just a few machines. Additionally the cobbler server can be connected to multiple networks .
In exemplary aspects the provisioning database can serve as a data storage location for holding data used by the cobbler server . For example as shown the provisioning database can comprise the distribution tree list and the template list . The distribution tree list can provide an inventory of the distributions and that are hosted or mirrored by the cobbler server . The template list can provide an inventory of the templates that are hosted by the cobbler server .
As noted above the cobbler server can manage provisioning using a hierarchical concept of distribution commands profile commands system commands and repository commands. This framework enables the cobbler server to abstract the differences between multiple provisioning types installation reinstallation and virtualization and allows installation of all three from a common platform. This hierarchy of commands also permits the cobbler server to integrate software repositories with the provisioning process thus allowing systems to be configured as a mirror for software updates and third party content as well as distribution content.
Distributions can contain information about base operating system tasks such as what kernel and initial ramdisk initrd are used in the provisioning along with other information such as required kernel parameters. Profiles associate one of the distributions and with a kickstart file and optionally customize it further for example using plugins . System commands associate a hostname IP or machine access control MAC with a distribution and optionally customize the profile further. Repositories contain update information such as yum mirror information that the cobbler server uses to mirror repository . The cobbler server can also manage generate dynamic host configuration protocol DHCP configuration files using the templates .
In exemplary aspects the cobbler server can use a provisioning environment that is fully templated allowing for kickstarts and PXE files to be customized by the user. The cobbler server uses the concept of profiles as an intermediate step between the operating system and the installed system. A profile is a description of what a system does rather than the software to be installed. For instance a profile might describe a virtual web server with X amount of RAM Y amounts of disk space ruling a Linux distribution Z and with an answer file W.
In exemplary aspects the cobbler server can provide a command line interface to configure a boot server in which it is installed. For example the format of the cobbler server commands can be generally in the format of cobbler command subcommand arg1 arg2 . Thus a user can specify various aspects of software provisioning via a single interface such as a command line interface or other known interface. Examples of exemplary cobbler commands can be found in U.S. patent application Ser. No. 11 763 315 U.S. Patent Application Publication No. 2008 0288938 and U.S. patent application Ser. No. 11 763 333 U.S. Patent Publication No. 2008 0288939 all assigned to Red Hat Corporation the disclosures of which are incorporated herein in their entirety by reference.
According to exemplary aspects a user can use various commands of the provisioning environment to specify distributions and install trees hosted by the code repository such as a distribution from the distributions or . A user can add or import a distribution or import it from installation media or an external network location.
According to exemplary aspects in order to import a distribution the cobbler server can auto add distributions and profiles from remote sources whether this is an installation media such as a DVD an NFS path or an rsync mirror. When importing an rsync mirror the cobbler server can try to detect the distribution type and automatically assign kickstarts. By default in some embodiments the cobbler server can provision by erasing the hard drive setting up eth0 for DHCP and using a default password. If this is undesirable an administrator may edit the kickstart files in etc cobbler to do something else or change the kickstart setting after the cobbler server creates the profile.
According to exemplary aspects a user may map profiles to the distributions and map systems to the profiles using profile commands and systems commands of the provisioning environment . A profile associates a distribution to additional specialized options such as a kickstart automation file. In the cobbler server profiles are the unit of provisioning and at least one profile exists for every distribution to be provisioned. A profile might represent for instance a web server or desktop configuration.
According to exemplary aspects a user can map systems to profiles using system commands. System commands can assign a piece of hardware with cobbler server to a profile. Systems can be defined by hostname Internet Protocol IP address or machine access control MAC address. When available use of the MAC address to assign systems can be preferred.
According to exemplary aspects the user can map repositories and profiles using repository commands. Repository commands can address configurations and tasks related to updating the software remote installation procedures and optionally customizing the software. These repository commands can also specify mirroring of the provisioned software to remote servers. Repository mirroring can allow the cobbler server to mirror not only the trees and but also optional packages third party content and updates. Mirroring can be useful for faster more up to date installations and faster updates or providing software on restricted networks. The cobbler server can also include other administrative features such as allowing the user to view their provisioning configuration or information tracking the status of a requested software installation.
According to exemplary aspects a user can utilize commands to create a provisioning infrastructure from a distribution mirror. Then a default PXE configuration is created so that by default systems will PXE boot into a fully automated install process for that distribution. The distribution mirror can be a network rsync mirror or a mounted DVD location.
According to exemplary aspects the administrator uses a local kernel and initrd file already downloaded and shows how profiles would be created using two different kickstarts one for a web server configuration and one for a database server Then a machine can be assigned to each profile.
According to exemplary aspects a repo mirror can be set up for two repositories and create a profile that will auto install those repository configurations on provisioned systems using that profile.
According to exemplary aspects in addition to normal provisioning the cobbler server can support yet another option called enchant . Enchant takes a configuration that has already been defined and applies it to a remote system that might not have the remote helper program installed. Users can use this command to replace a server that is being repurposed or when no PXE environment can be created. Thus the enchant option allows the remote the koan client to be executed remotely from the cobbler server .
According to aspects if the cobbler server is configured to mirror certain repositories the cobbler server can then be used to associate profiles with those repositories. Systems installed under those profiles can be auto configured to use these repository mirrors in commands and if supported these repositories can be leveraged. This can be useful for a large install base when fast installation and upgrades for systems are desired or software not in a standard repository exists and provisioned systems desire to know about that repository.
According to exemplary aspects the cobbler server can also keep track of the status of kickstarting machines. For example the cobbler status will show when the cobbler server thinks a machine started kickstarting and when it last requested a file. This can be a desirable way to track machines that may have gone inactive during kickstarts. The cobbler server can also make a special request in the post section of the kickstart to signal when a machine is finished kickstarting.
According to exemplary aspects for certain commands the cobbler server will create new virtualized guests on a machine in accordance with orders from the cobbler server . Once finished an administrator can use additional commands on the guest or other operations. The cobbler server can automatically name domains based on their MAC addresses. For re kickstarting the cobbler server can reprovision the system deleting any current data and replacing it with the results of a network install.
According to exemplary aspects the cobbler server can configure boot methods for the provisioning requested by the user. For example the cobbler server can configure a PXE environment such as a network card BIOS. Alternatively the cobbler server can compile and configure information for koan client . The cobbler server can also optionally configure DHCP and DNS configuration information.
According to exemplary aspects the cobbler server can serve the request of the koan client . The koan client can acknowledge the service of information of the cobbler server and can then initiate installation of the software being provisioned. Additionally the koan client can either install the requested software e.g. replace the existing operating system or install a virtual machine.
As shown in the network can include a number of target machines . For example the target machines can include a group of server computers such as blade servers. The target machines can include computing systems such as servers personal computers laptop computers etc. In embodiments the target machines can include hardware typically found in conventional computing systems processors memory video cards network interface cards storage devices and the like .
In embodiments the cobbler server can be configured to provide provisioning processes for software distributions utilizing provisioning objects as described above. In the provisioning processes for software distributions the cobbler server installs a particular software distribution on a target machine utilizing the provisioning objects such as profiles and templates.
In embodiments the provisioning objects can include all the data required by a cobbler server to perform the software provisioning processes such as the process described above supported by the cobbler server For example the provisioning objects can include software distributions configuration templates templates for generating configuration files such as kickstart files distribution profile information mapping a distribution to profile a configuration template or a configuration file and additional preferences such as kernel options template variables or virtual machine settings target machine information information representing the mapping of a physical piece of hardware plus hardware specific customizations to a profile that it should run repos information information representing external or internal software repositories stored on the cobbler server images such as distributions representing an undefined executable image like memtest a virtual machine to be cloned or an ISO file for use in installing a virtual machine and the like.
In embodiments the cobbler server can be configured to maintain a library of virtual images and configured to perform provisioning processes utilizing virtual images from the library on the target machines . Each virtual image can be a disk image of software that has been previously installed according to metadata. As such the virtual image can consist of the bits of the installed software. The software contained in the virtual image can include any number and type of applications and portions of an OS to support the applications. The cobbler server can be configured to maintain the virtual images in the library a location of the virtual images in the library if the virtual images are stored remotely or combinations thereof. The cobbler server can be configured to maintain the library in any type of storage device or system CD DVD hard drive portable storage memory database etc. whether local to the cobbler server or remotely located.
In embodiments the metadata associated with a virtual image can include parameters such as types of hardware or resources associated with the virtual image processors memory storage network interfaces etc. amount of hardware or resources associated with the virtual image the amount of memory associated with the virtual image the amount storage associated with the virtual image etc. configuration of the hardware or resources the network settings for the virtual image etc. and the like. These parameters contained in the metadata can represent the parameters utilized to create the virtual image and the parameters required to provision the virtual image on a target machine .
In embodiments to support provisioning the virtual images the cobbler server can be configured to maintain a set of virtual image records . The set of virtual image records contains one or more virtual image records associated with each virtual image in the library . A virtual image record can be configured to contain an identification of a particular virtual image with which it is associated and the metadata associated with the particular virtual image . Additionally a particular virtual image can be associated with multiple virtual image records . Each of the multiple virtual image records associated with a particular virtual image can contain different metadata representing different parameters utilized to create the particular virtual image and the different parameters required to provision the particular virtual image on a target machine . The cobbler server can be configured to utilize the set of virtual image records for provisioning the virtual image on the target machines .
In embodiments the virtual images contained in the library can originate from a variety of sources. The cobbler server can be configured to generate the virtual images and the virtual image records associated with the generated virtual images . For example the cobbler server can be configured to communicate with a storage device . The storage device can be any type of storage device or system CD DVD hard drive portable storage memory database etc. whether local to the cobbler server or remotely located. To generate the virtual image the cobbler server can be configured to select a particular software distribution to install and determine the metadata for the virtual image . The metadata can be based on the parameters required by the particular software distribution. Once selected the cobbler server can be configured to install the particular software distribution on the storage device according to the metadata.
In embodiments after installation of the particular software distribution the cobbler server can be configured to copy the data e.g. image of the bits for the installed software distribution and configured to store the copy in the library as the virtual image . Alternatively the cobbler server can be configured to store a location of the virtual image in the library if the virtual image is stored remotely. Likewise the cobbler server can be configured to store the metadata as a virtual image record in the set of virtual image records .
In the embodiments as described above the cobbler server can generate the virtual image . Also the cobbler server can be configured to receive a virtual image from an external source and store the virtual image in the library . Also the cobbler server can be configured to receive metadata or a virtual image record from an external source in order to generate a virtual image or to associate with a received virtual image .
In embodiments the cobbler server can be configured to provision any of the virtual images stored in the library to any of the target machines . To achieve this the cobbler server can be configured to select a virtual image from the library . After selecting the virtual image the cobbler server can be configured to determine the associated virtual image record from the set of virtual image records . To determine the associated virtual image record the cobbler server can be configured to search the set of virtual image records in order to locate the virtual image records that contain the identification of the selected virtual image .
In embodiments after selecting the virtual image and determining the associated virtual image record the cobbler server can be configured to provided the selected virtual image and the associated virtual image record to the target machine subject to the provisioning. To provide both the cobbler server can be configured to instruct the koan client to retrieve the virtual image and the associated image record . Likewise the cobbler server can be configured to provide the virtual image and associated virtual image record directly to the koan client .
In embodiments after the virtual image and the associated virtual image record has been provided the cobbler server can be configured to instruct the koan client to instantiate the virtual image on the target machine . The koan client can be configured to examine the associated virtual image record to determine the metadata for the virtual image . Then the koan client can be configured to copy the virtual image to a storage device that meets the parameters of the metadata. Additionally the koan client can configure the target machine as necessary according to the metadata of the virtual image record in order to facilitate proper operation of the virtual image .
In the embodiments as described above the cobbler server can be configured to operate in conjunction with the koan client to provision the virtual image . Additionally the cobbler server can be configured to provision the virtual image independently. To achieve this the cobbler server can be configured to examine the associated virtual image record to determine the metadata for the virtual image . Then the cobbler server can be configured to copy the virtual image to a storage device that meets the parameters of the metadata. Additionally the cobbler server can configure the target machine as necessary according to the metadata of the virtual image record in order to facilitate proper operation of the virtual image .
In embodiments as described above the virtual image can be instantiated according to the virtual image record as stored in the set of virtual image records . Additionally the cobbler server can be configured to alter the metadata of the virtual image record prior to instantiating the virtual image . As such the cobbler server can tailor the instantiation of the virtual image for the target machines .
In embodiments the cobbler server can initiate provisioning a virtual image upon the occurrence of a number of events. The cobbler server can be configured to receive a request to provision a particular virtual image . The request can originate from any source such as a target machine a user of a target machine an operator of the cobbler server or any other source. Additionally the cobbler server can be configured to automatically initiate provisioning a virtual image . For example the cobbler server can initiate provisioning of a virtual image when a new target machine is added to the network when a target machine experiences errors or catastrophic failure and the like. For instance the cobbler server can provide a virtual image comprising a basic OS and applications so that the new target machine will include basic software to operate.
In embodiments the cobbler server can be configured to associate the virtual images and the associated virtual image records with other provisioning objects. For example the cobbler server can be configured to associate a particular virtual image and associated virtual image records with the a system record for a particular target machine . As such when a provisioning process is initiated for the virtual image associated with the system record the cobbler server can be configured to utilize the information in the system record identification of the target machine resources of the target machine etc. in the provisioning process.
Processor further communicates with network interface such as an Ethernet or wireless data connection which in turn communicates with one or more networks such as the Internet or other public or private networks. Processor also communicates with the provisioning database and the cobbler server to execute control logic and perform the virtual image processes described above and below.
As illustrated the cobbler server can be implemented as a software application or program capable of being executed by a conventional computer platform. Likewise the cobbler server can also be implemented as a software module or program module capable of being incorporated in other software applications and programs. In either case the cobbler server can be implemented in any type of conventional proprietary or open source computer language.
After installation of the particular software distribution the cobbler server can copy the data e.g. image of the bits for the installed software distribution and store the copy in the library as the virtual image . Likewise the cobbler server can store the metadata as a virtual image record in the set of virtual image records .
In the cobbler server can optionally receive one or more virtual images from external sources and store the virtual images in the library . For example the cobbler server can receive a virtual image from an external source and store the virtual image in the library . Also the cobbler server can receive metadata or a virtual image record from an external source in order to generate a virtual image or associate with a received virtual image .
In the cobbler server can initiate provisioning a virtual image on a target machine . The cobbler server can initiate provisioning a virtual image upon the occurrence of a number of events. For example the cobbler server can receive a request to provision a particular virtual image . The request can originate from any source such as a target machine a user of a target machine an operator of the cobbler server or any other source. Additionally the cobbler server can automatically initiate provisioning a virtual image .
In the cobbler server can determine a virtual image record associated with the virtual image to be provisioned. For example to determine the associated virtual image record the cobbler server can search the set of virtual image records in order to locate the virtual image records that contain the identification of the virtual image .
In the cobbler server can provide the virtual image to the target machine . For example the cobbler server can instruct the koan client to retrieve the virtual image and associated virtual image record . Likewise the cobbler server can be configured to provide the virtual image and associated virtual image record directly to the koan client . Additionally the cobbler server can provide the virtual image to the target machine without utilizing the koan client .
In the cobbler server can instantiate the virtual image on the target machine . For example the cobbler server can instruct the koan client to instantiate the virtual image on the target machine . The koan client can examine the associated virtual image record to determine the metadata for the virtual image . Then the koan client can copy the virtual image to a storage device that meets the parameters of the metadata. Additionally the koan client can configure the target machine as necessary according to the metadata of the virtual image record in order to facilitate proper operation of the virtual image .
Additionally the cobbler server can instantiate the virtual image independently. The cobbler server can examine the associated virtual image record to determine the metadata for the virtual image . Then the cobbler server can to copy the virtual image to a storage device that meets the parameters of the metadata. Additionally the cobbler server can configure the target machine as necessary according to the metadata of the virtual image record in order to facilitate proper operation of the virtual image .
While the invention has been described with reference to the exemplary embodiments thereof those skilled in the art will be able to make various modifications to the described embodiments without departing from the true spirit and scope. The terms and descriptions used herein are set forth by way of illustration only and are not meant as limitations. In particular although the method has been described by examples the steps of the method may be performed in a different order than illustrated or simultaneously. Furthermore to the extent that the terms including includes having has with or variants thereof are used in either the detailed description and the claims such terms are intended to be inclusive in a manner similar to the term comprising. As used herein the term one or more of with respect to a listing of items such as for example A and B means A alone B alone or A and B. Those skilled in the art will recognize that these and other variations are possible within the spirit and scope as defined in the following claims and their equivalents.
| 260.921053 | 1,062 | 0.830131 | eng_Latn | 0.999754 |
24a89b2e99692492062602ca1c3e2ff633cb4afe | 447 | md | Markdown | demo/README.md | yixiaosi1314/react-i18n-auto | 0f753f0358d38a3df70381749d80f10647d84e3e | [
"MIT"
] | 19 | 2020-03-28T03:52:43.000Z | 2022-02-16T12:12:51.000Z | demo/README.md | yixiaosi1314/react-i18n-auto | 0f753f0358d38a3df70381749d80f10647d84e3e | [
"MIT"
] | 10 | 2020-06-09T09:03:01.000Z | 2022-01-18T08:43:23.000Z | demo/README.md | yixiaosi1314/react-i18n-auto | 0f753f0358d38a3df70381749d80f10647d84e3e | [
"MIT"
] | 7 | 2020-03-31T10:42:39.000Z | 2021-12-14T02:34:31.000Z | # 1
`npm i`
# 2
`npm run build`
运行结果输出: `待翻译内容.xlsx`
将 `待翻译内容.xlsx` 翻译到新的 excel 中，格式如下(`key`列 与 `text`列保持一一对应)，并在 i18n.config.js 中加入 translation 配置项
# END
****
## 翻译文件示例
## 最终效果
> ps: 该插件不影响源代码，无痕开发，具体结果可查看编译后的代码
| 17.192308 | 110 | 0.731544 | yue_Hant | 0.227006 |
24a8c96ffaa4e94d88139a31549be0d4c079e0ec | 16,206 | md | Markdown | CHANGELOG.md | abhik-99/rust-lightning | 7aa2caccd884cd7d40ee146323c2a65b7ea39407 | [
"Apache-2.0",
"MIT"
] | null | null | null | CHANGELOG.md | abhik-99/rust-lightning | 7aa2caccd884cd7d40ee146323c2a65b7ea39407 | [
"Apache-2.0",
"MIT"
] | null | null | null | CHANGELOG.md | abhik-99/rust-lightning | 7aa2caccd884cd7d40ee146323c2a65b7ea39407 | [
"Apache-2.0",
"MIT"
] | null | null | null | # 0.0.101 - 2021-09-23
## API Updates
* Custom message types are now supported directly in the `PeerManager`,
allowing you to send and receive messages of any type that is not natively
understood by LDK. This requires a new type bound on `PeerManager`, a
`CustomMessageHandler`. `IgnoringMessageHandler` provides a simple default
for this new bound for ignoring unknown messages (#1031, #1074).
* Route graph updates as a result of failed payments are no longer provided as
`MessageSendEvent::PaymentFailureNetworkUpdate` but instead included in a
new field in the `Event::PaymentFailed` events. Generally, this means route
graph updates are no longer handled as a part of the `PeerManager` but
instead through the new `EventHandler` implementation for
`NetGraphMsgHandler`. To make this easy, a new parameter to
`lightning-background-processor::BackgroundProcessor::start` is added, which
contains an `Option`al `NetGraphmsgHandler`. If provided as `Some`, relevant
events will be processed by the `NetGraphMsgHandler` prior to normal event
handling (#1043).
* `NetworkGraph` is now, itself, thread-safe. Accordingly, most functions now
take `&self` instead of `&mut self` and the graph data can be accessed
through `NetworkGraph.read_only` (#1043).
* The balances available on-chain to claim after a channel has been closed are
now exposed via `ChannelMonitor::get_claimable_balances` and
`ChainMonitor::get_claimable_balances`. The second can be used to get
information about all closed channels which still have on-chain balances
associated with them. See enum variants of `ln::channelmonitor::Balance` and
method documentation for the above methods for more information on the types
of balances exposed (#1034).
* When one HTLC of a multi-path payment fails, the new field `all_paths_failed`
in `Event::PaymentFailed` is set to `false`. This implies that the payment
has not failed, but only one part. Payment resolution is only indicated by an
`Event::PaymentSent` event or an `Event::PaymentFailed` with
`all_paths_failed` set to `true`, which is also set for the last remaining
part of a multi-path payment (#1053).
* To better capture the context described above, `Event::PaymentFailed` has
been renamed to `Event::PaymentPathFailed` (#1084).
* A new event, `ChannelClosed`, is provided by `ChannelManager` when a channel
is closed, including a reason and error message (if relevant, #997).
* `lightning-invoice` now considers invoices with sub-millisatoshi precision
to be invalid, and requires millisatoshi values during construction (thus
you must call `amount_milli_satoshis` instead of `amount_pico_btc`, #1057).
* The `BaseSign` interface now includes two new hooks which provide additional
information about commitment transaction signatures and revocation secrets
provided by our counterparty, allowing additional verification (#1039).
* The `BaseSign` interface now includes additional information for cooperative
close transactions, making it easier for a signer to verify requests (#1064).
* `Route` has two additional helper methods to get fees and amounts (#1063).
* `Txid` and `Transaction` objects can now be deserialized from responses when
using the HTTP client in the `lightning-block-sync` crate (#1037, #1061).
## Bug Fixes
* Fix a panic when reading a lightning invoice with a non-recoverable
signature. Further, restrict lightning invoice parsing to require payment
secrets and better handle a few edge cases as required by BOLT 11 (#1057).
* Fix a panic when receiving multiple messages (such as HTLC fulfill messages)
after a call to `chain::Watch::update_channel` returned
`Err(ChannelMonitorUpdateErr::TemporaryFailure)` with no
`ChannelManager::channel_monitor_updated` call in between (#1066).
* For multi-path payments, `Event::PaymentSent` is no longer generated
multiple times, once for each independent part (#1053).
* Multi-hop route hints in invoices are now considered in the default router
provided via `get_route` (#1040).
* The time peers have to respond to pings has been increased when building
with debug assertions enabled. This avoids peer disconnections on slow hosts
when running in debug mode (#1051).
* The timeout for the first byte of a response for requests from the
`lightning-block-sync` crate has been increased to 300 seconds to better
handle the long hangs in Bitcoin Core when it syncs to disk (#1090).
## Serialization Compatibility
* Due to a bug in 0.0.100, `Event`s written by 0.0.101 which are of a type not
understood by 0.0.100 may lead to `Err(DecodeError::InvalidValue)` or corrupt
deserialized objects in 0.100. Such `Event`s will lead to an
`Err(DecodeError::InvalidValue)` in versions prior to 0.0.100. The only such
new event written by 0.0.101 is `Event::ChannelClosed` (#1087).
* Payments that were initiated in versions prior to 0.0.101 may still
generate duplicate `PaymentSent` `Event`s or may have spurious values for
`Event::PaymentPathFailed::all_paths_failed` (#1053).
* The return values of `ChannelMonitor::get_claimable_balances` (and, thus,
`ChainMonitor::get_claimable_balances`) may be spurious for channels where
the spend of the funding transaction appeared on chain while running a
version prior to 0.0.101. `Balance` information should only be relied upon
for channels that were closed while running 0.0.101+ (#1034).
* Payments failed while running versions prior to 0.0.101 will never have a
`Some` for the `network_update` field (#1043).
In total, this release features 67 files changed, 4980 insertions, 1888
deletions in 89 commits from 12 authors, in alphabetical order:
* Antoine Riard
* Devrandom
* Galder Zamarreño
* Giles Cope
* Jeffrey Czyz
* Joseph Goulden
* Matt Corallo
* Sergi Delgado Segura
* Tibo-lg
* Valentine Wallace
* abhik-99
* vss96
# 0.0.100 - 2021-08-17
## API Updates
* The `lightning` crate can now be built in no_std mode, making it easy to
target embedded hardware for rust users. Note that mutexes are replaced with
no-ops for such builds (#1008, #1028).
* LDK now supports sending and receiving "keysend" payments. This includes
modifications to `lightning::util::events::Event::PaymentReceived` to
indicate the type of payment (#967).
* A new variant, `lightning::util::events::Event::PaymentForwarded` has been
added which indicates a forwarded payment has been successfully claimed and
we've received a forwarding fee (#1004).
* `lightning::chain::keysinterface::KeysInterface::get_shutdown_pubkey` has
been renamed to `get_shutdown_scriptpubkey`, returns a script, and is now
called on channel open only if
`lightning::util::config::ChannelConfig::commit_upfront_shutdown_pubkey` is
set (#1019).
* Closing-signed negotiation is now more configurable, with an explicit
`lightning::util::config::ChannelConfig::force_close_avoidance_max_fee_satoshis`
field allowing you to select the maximum amount you are willing to pay to
avoid a force-closure. Further, we are now less restrictive on the fee
placed on the closing transaction when we are not the party paying it. To
control the feerate paid on a channel at close-time, use
`ChannelManager::close_channel_with_target_feerate` instead of
`close_channel` (#1011).
* `lightning_background_processor::BackgroundProcessor` now stops the
background thread when dropped (#1007). It is marked `#[must_use]` so that
Rust users will receive a compile-time warning when it is immediately
dropped after construction (#1029).
* Total potential funds burn on force-close due to dust outputs is now limited
to `lightning::util::config::ChannelConfig::max_dust_htlc_exposure_msat` per
channel (#1009).
* The interval on which
`lightning::ln::peer_handler::PeerManager::timer_tick_occurred` should be
called has been reduced to once every five seconds (#1035) and
`lightning::ln::channelmanager::ChannelManager::timer_tick_occurred` should
now be called on startup in addition to once per minute (#985).
* The rust-bitcoin and bech32 dependencies have been updated to their
respective latest versions (0.27 and 0.8, #1012).
## Bug Fixes
* Fix panic when reading invoices generated by some versions of c-lightning
(#1002 and #1003).
* Fix panic when attempting to validate a signed message of incorrect length
(#1010).
* Do not ignore the route hints in invoices when the invoice is over 250k
sats (#986).
* Fees are automatically updated on outbound channels to ensure commitment
transactions are always broadcastable (#985).
* Fixes a rare case where a `lightning::util::events::Event::SpendableOutputs`
event is not generated after a counterparty commitment transaction is
confirmed in a reorg when a conflicting local commitment transaction is
removed in the same reorg (#1022).
* Fixes a remotely-triggerable force-closure of an origin channel after an
HTLC was forwarded over a next-hop channel and the next-hop channel was
force-closed by our counterparty (#1025).
* Fixes a rare force-closure case when sending a payment as a channel fundee
when overdrawing our remaining balance. Instead the send will fail (#998).
* Fixes a rare force-closure case when a payment was claimed prior to a
peer disconnection or restart, and later failed (#977).
## Serialization Compatibility
* Pending inbound keysend payments which have neither been failed nor claimed
when serialized will result in a `ChannelManager` which is not readable on
pre-0.0.100 clients (#967).
* Because
`lightning::chain::keysinterface::KeysInterface::get_shutdown_scriptpubkey`
has been updated to return a script instead of only a `PublicKey`,
`ChannelManager`s constructed with custom `KeysInterface` implementations on
0.0.100 and later versions will not be readable on previous versions.
`ChannelManager`s created with 0.0.99 and prior versions will remain readable
even after the a serialization roundtrip on 0.0.100, as long as no new
channels are opened. Further, users using a
`lightning::chain::keysinterface::KeysManager` as their `KeysInterface` will
have `ChannelManager`s which are readable on prior versions as well (#1019).
* `ChannelMonitorUpdate`s created by 0.0.100 and later for channels when
`lightning::util::config::ChannelConfig::commit_upfront_shutdown_pubkey` is
not set may not be readable by versions prior to 0.0.100 (#1019).
* HTLCs which were in the process of being claimed on-chain when a pre-0.0.100
`ChannelMonitor` was serialized may generate `PaymentForwarded` events with
spurious `fee_earned_msat` values. This only applies to payments which were
unresolved at the time of the upgrade (#1004).
* 0.0.100 clients with pending `Event::PaymentForwarded` events at
serialization-time will generate serialized `ChannelManager` objects which
0.0.99 and earlier clients cannot read. The likelihood of this can be reduced
by ensuring you process all pending events immediately before serialization
(as is done by the `lightning-background-processor` crate, #1004).
In total, this release features 59 files changed, 5861 insertions, and 2082
deletions in 95 commits from 6 authors.
# 0.0.99 - 2021-07-09
## API Updates
* `lightning_block_sync::poll::Validate` is now public, allowing you to
implement the `lightning_block_sync::poll::Poll` trait without
`lightning_block_sync::poll::ChainPoller` (#956).
* `lightning::ln::peer_handler::PeerManager` no longer requires that no calls
are made to referencing the same `SocketDescriptor` after
`disconnect_socket` returns. This makes the API significantly less
deadlock-prone and simplifies `SocketDescriptor` implementations
significantly. The relevant changes have been made to `lightning_net_tokio`
and `PeerManager` documentation has been substantially rewritten (#957).
* `lightning::util::message_signing`'s `sign` and `verify` methods now take
secret and public keys by reference instead of value (#974).
* Substantially more information is now exposed about channels in
`ChannelDetails`. See documentation for more info (#984 and #988).
* The latest best block seen is now exposed in
`ChannelManager::current_best_block` and
`ChannelMonitor::current_best_block` (#984).
* Feerates charged when forwarding payments over channels is now set in
`ChannelConfig::fee_base_msat` when the channel is opened. For existing
channels, the value is set to the value provided in
`ChannelManagerReadArgs::default_config::channel_options` the first time the
`ChannelManager` is loaded in 0.0.99 (#975).
* We now reject HTLCs which are received to be forwarded over private channels
unless `UserConfig::accept_forwards_to_priv_channels` is set. Note that
`UserConfig` is never serialized and must be provided via
`ChannelManagerReadArgs::default_config` at each start (#975).
## Bug Fixes
* We now forward gossip messages to peers instead of only relaying
locally-generated gossip or sending gossip messages during initial sync
(#948).
* Correctly send `channel_update` messages to direct peers on private channels
(#949). Without this, a private node connected to an LDK node over a private
channel cannot receive funds as it does not know which fees the LDK node
will charge.
* `lightning::ln::channelmanager::ChannelManager` no longer expects to be
persisted spuriously after we receive a `channel_update` message about any
channel in the routing gossip (#972).
* Asynchronous `ChannelMonitor` updates (using the
`ChannelMonitorUpdateErr::TemporaryFailure` return variant) no longer cause
spurious HTLC forwarding failures (#954).
* Transaction provided via `ChannelMonitor::transactions_confirmed`
after `ChannelMonitor::best_block_updated` was called for a much later
block now trigger all relevant actions as of the later block. Previously
some transaction broadcasts or other responses required an additional
block be provided via `ChannelMonitor::best_block_updated` (#970).
* We no longer panic in rare cases when an invoice contained last-hop route
hints which were unusable (#958).
## Node Compatibility
* We now accept spurious `funding_locked` messages sent prior to
`channel_reestablish` messages after reconnect. This is a
[known, long-standing bug in lnd](https://github.com/lightningnetwork/lnd/issues/4006)
(#966).
* We now set the `first_blocknum` and `number_of_blocks` fields in
`reply_channel_range` messages to values which c-lightning versions prior to
0.10 accepted. This avoids spurious force-closes from such nodes (#961).
## Serialization Compatibility
* Due to a bug discovered in 0.0.98, if a `ChannelManager` is serialized on
version 0.0.98 while an `Event::PaymentSent` is pending processing, the
`ChannelManager` will fail to deserialize both on version 0.0.98 and later
versions. If you have such a `ChannelManager` available, a simple patch will
allow it to deserialize. Please file an issue if you need assistance (#973).
# 0.0.98 - 2021-06-11
0.0.98 should be considered a release candidate to the first alpha release of
Rust-Lightning and the broader LDK. It represents several years of work
designing and fine-tuning a flexible API for integrating lightning into any
application. LDK should make it easy to build a lightning node or client which
meets specific requirements that other lightning node software cannot. As
lightning continues to evolve, and new use-cases for lightning develop, the API
of LDK will continue to change and expand. However, starting with version 0.1,
objects serialized with prior versions will be readable with the latest LDK.
While Rust-Lightning is approaching the 0.1 milestone, language bindings
components of LDK available at https://github.com/lightningdevkit are still of
varying quality. Some are also approaching an 0.1 release, while others are
still much more experimental. Please note that, at 0.0.98, using Rust-Lightning
on mainnet is *strongly* discouraged.
| 57.468085 | 89 | 0.76737 | eng_Latn | 0.997769 |
24a8d1b87cd64488055dbdb6225020f6c5182324 | 1,573 | md | Markdown | docs/framework/unmanaged-api/fusion/iassemblyname-getversion-method.md | felipealbuquerq/docs.pt-br | 6808f7d63212e650a0ecadd7f5cd058594fd0d38 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/fusion/iassemblyname-getversion-method.md | felipealbuquerq/docs.pt-br | 6808f7d63212e650a0ecadd7f5cd058594fd0d38 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/fusion/iassemblyname-getversion-method.md | felipealbuquerq/docs.pt-br | 6808f7d63212e650a0ecadd7f5cd058594fd0d38 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Método IAssemblyName::GetVersion
ms.date: 03/30/2017
api_name:
- IAssemblyName.GetVersion
api_location:
- fusion.dll
api_type:
- COM
f1_keywords:
- IAssemblyName::GetVersion
helpviewer_keywords:
- IAssemblyName::GetVersion method [.NET Framework fusion]
- GetVersion method, IAssemblyName interface [.NET Framework fusion]
ms.assetid: 42230928-2c33-41fd-9519-d96efef6c7af
topic_type:
- apiref
author: rpetrusha
ms.author: ronpet
ms.openlocfilehash: 58919936bdc62d52437f429146f04c66d49294b2
ms.sourcegitcommit: d2e1dfa7ef2d4e9ffae3d431cf6a4ffd9c8d378f
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 09/07/2019
ms.locfileid: "70796575"
---
# <a name="iassemblynamegetversion-method"></a>Método IAssemblyName::GetVersion
Obtém as informações de versão para o assembly referenciado por este objeto [IAssemblyName](iassemblyname-interface.md) .
## <a name="syntax"></a>Sintaxe
```cpp
HRESULT GetVersion (
[out] LPDWORD pdwVersionHi,
[out] LPDWORD pdwVersionLow
);
```
## <a name="parameters"></a>Parâmetros
`pdwVersionHi`
fora Os bits de 32 altos da versão.
`pdwVersionLow`
fora Os bits de 32 baixos da versão.
## <a name="requirements"></a>Requisitos
**Compatíveis** Confira [Requisitos de sistema](../../get-started/system-requirements.md).
**Cabeçalho:** Fusion. h
**Versões do .NET Framework:** [!INCLUDE[net_current_v20plus](../../../../includes/net-current-v20plus-md.md)]
## <a name="see-also"></a>Consulte também
- [Interface IAssemblyName](iassemblyname-interface.md)
| 28.089286 | 123 | 0.737444 | yue_Hant | 0.666011 |
24a97a60426158ff121dd090c6d44f35d59f1a18 | 150 | md | Markdown | _posts/2014-11-22-Designing-Plan-9.md | mburns/mburns.github.io | 8062e237cd86c1ad7aa7cc4414f2f926d312bc3d | [
"MIT"
] | null | null | null | _posts/2014-11-22-Designing-Plan-9.md | mburns/mburns.github.io | 8062e237cd86c1ad7aa7cc4414f2f926d312bc3d | [
"MIT"
] | null | null | null | _posts/2014-11-22-Designing-Plan-9.md | mburns/mburns.github.io | 8062e237cd86c1ad7aa7cc4414f2f926d312bc3d | [
"MIT"
] | null | null | null | ---
layout: post
title: "Designing Plan 9"
tags:
- pocket
date: "2014-11-22 17:53:10"
---
http://doc.cat-v.org/plan_9/1st_edition/designing_plan_9
| 13.636364 | 56 | 0.693333 | kor_Hang | 0.127024 |
24abd305a5298d449de736cec57551fbac797f66 | 697 | md | Markdown | content/movies/the-little-shop-of-horrors.md | bradp/horror.watch | 7d6aff54738a85d6bae2f220bd7c9d192971a349 | [
"MIT"
] | 2 | 2021-02-03T22:20:32.000Z | 2022-01-05T09:40:56.000Z | content/movies/the-little-shop-of-horrors.md | bradp/horror.watch | 7d6aff54738a85d6bae2f220bd7c9d192971a349 | [
"MIT"
] | 4 | 2021-09-21T10:26:58.000Z | 2022-03-30T21:55:20.000Z | content/movies/the-little-shop-of-horrors.md | bradp/horror.watch | 7d6aff54738a85d6bae2f220bd7c9d192971a349 | [
"MIT"
] | 1 | 2021-11-10T12:18:16.000Z | 2021-11-10T12:18:16.000Z | +++
title = "The Little Shop of Horrors"
added = "2020-12-31"
description = "Seymour works in a skid row florist shop and is in love with his beautiful co-worker, Audrey. He creates a new plant that not only talks but cannot survive without human flesh and blood."
rating = "6"
popularity = "7.25"
released = "1960"
poster = "assets/poster/the-little-shop-of-horrors.jpg"
cover = "assets/cover/the-little-shop-of-horrors.jpg"
file = "https://archive.org/download/The_Little_Shop_of_Horrors.mp4/The_Little_Shop_of_Horrors.mp4"
genres = ["Horror", "Comedy"]
imdb_id = "tt0054033"
runtime = "72"
tagline = "The funniest picture this year!"
original_language = "en"
budget = "30000"
revenue = "0"
+++
| 36.684211 | 202 | 0.738881 | eng_Latn | 0.907348 |
24adc1010b0b65e72ae3def3cba5d193cb83d1e9 | 8,420 | md | Markdown | README.md | a-patel/csharp-style-guide | 8de20eb7ff685fa60930472364d932634afb92d2 | [
"MIT"
] | 2 | 2019-10-08T19:07:13.000Z | 2020-01-23T12:55:55.000Z | README.md | a-patel/csharp-style-guide | 8de20eb7ff685fa60930472364d932634afb92d2 | [
"MIT"
] | null | null | null | README.md | a-patel/csharp-style-guide | 8de20eb7ff685fa60930472364d932634afb92d2 | [
"MIT"
] | null | null | null | # C# Style Guide
C# Style Guide for Tutorials
---
The code is read much more often than it is written.
### The Zen of any programming language
* Beautiful is better than ugly.
* Explicit is better than implicit.
* Simple is better than complex.
* Complex is better than complicated.
* Flat is better than nested.
* Sparse is better than dense.
* Readability counts.
* Special cases aren't special enough to break the rules.
* Although practicality beats purity.
* Errors should never pass silently.
* Unless explicitly silenced.
* In the face of ambiguity, refuse the temptation to guess.
* There should be one-- and preferably only one --obvious way to do it.
* Although that way may not be obvious at first unless you're Dutch.
* Now is better than never.
* Although never is often better than *right* now.
* If the implementation is hard to explain, it's a bad idea.
* If the implementation is easy to explain, it may be a good idea.
* Namespaces are one honking great idea -- let's do more of those!
You also see "Readability Counts" in the above listed points, which should be your main concern while writing code: other programmers should understand and should be able to contribute to your code so that it can solve the task at hand.
## Style Guiding Principles
* Be consistent.
* Don't rewrite existing code to follow this guide.
* Don't violate a guideline without a good reason.
* A reason is good when you can convince a teammate, not just when you like it.
* Assume your reader knows C# and English.
* Prefer clarity to 'performance'.
* Prefer clarity to .NET dogma.
* Write comments that people want to read, with correct spelling and grammar.
## The Rundown
* Indent with tabs.
* Max line length is 100 columns.
* Use spaces and empty lines precisely.
* Braces generally go on their own lines.
* Never put a space before `[`.
* Always put a space before `{`.
* Always put a space before `(` except for method invocations or when following another `(`.
## Table of Contents
- [Nomenclature](#nomenclature)
+ [Namespaces](#namespaces)
+ [Classes & Interfaces](#classes--interfaces)
+ [Methods](#methods)
+ [Fields](#fields)
+ [Parameters](#parameters--parameters)
+ [Delegates](#delegates--delegates)
+ [Events](#events--events)
+ [Misc](#misc)
- [Declarations](#declarations)
+ [Access Level Modifiers](#access-level-modifiers)
+ [Fields & Variables](#fields--variables)
+ [Classes](#classes)
+ [Interfaces](#interfaces)
- [Spacing](#spacing)
+ [Indentation](#indentation)
+ [Line Length](#line-length)
+ [Vertical Spacing](#vertical-spacing)
- [Brace Style](#brace-style)
- [Switch Statements](#switch-statements)
- [Language](#language)
- [Copyright Statement](#copyright-statement)
- [Smiley Face](#smiley-face)
- [Credit](#credits)
## Nomenclature
On the whole, naming should follow C# standards.
### Namespaces
Namespaces are all **PascalCase**, multiple words concatenated together, without hypens ( - ) or underscores ( \_ ):
**BAD**:
```csharp
com.raywenderlich.fpsgame.hud.healthbar
```
**GOOD**:
```csharp
RayWenderlich.FpsGame.Hud.Healthbar
```
### Classes & Interfaces
Written in **PascalCase**. For example `RadialSlider`.
### Methods
Methods are written in **PascalCase**. For example `DoSomething()`.
### Fields
All non-static fields are written **camelCase**. Per Unity convention, this includes **public fields** as well.
For example:
```csharp
public class MyClass
{
public int publicField;
int packagePrivate;
private int myPrivate;
protected int myProtected;
}
```
**BAD:**
```csharp
private int _myPrivateVariable
```
**GOOD:**
```csharp
private int myPrivateVariable
```
Static fields are the exception and should be written in **PascalCase**:
```csharp
public static int TheAnswer = 42;
```
### Parameters
Parameters are written in **camelCase**.
**BAD:**
```csharp
void DoSomething(Vector3 Location)
```
**GOOD:**
```csharp
void DoSomething(Vector3 location)
```
Single character values are to be avoided except for temporary looping variables.
### Delegates
Delegates are written in **PascalCase**.
When declaring delegates, DO add the suffix **EventHandler** to names of delegates that are used in events.
**BAD:**
```csharp
public delegate void Click()
```
**GOOD:**
```csharp
public delegate void ClickEventHandler()
```
DO add the suffix **Callback** to names of delegates other than those used as event handlers.
**BAD:**
```csharp
public delegate void Render()
```
**GOOD:**
```csharp
public delegate void RenderCallback()
```
### Events
Prefix event methods with the prefix **On**.
**BAD:**
```csharp
public static event CloseCallback Close;
```
**GOOD:**
```csharp
public static event CloseCallback OnClose;
```
### Misc
In code, acronyms should be treated as words. For example:
**BAD:**
```csharp
XMLHTTPRequest
String URL
findPostByID
```
**GOOD:**
```csharp
XmlHttpRequest
String url
findPostById
```
## Declarations
### Access Level Modifiers
Access level modifiers should be explicitly defined for classes, methods and member variables.
### Fields & Variables
Prefer single declaration per line.
**BAD:**
```csharp
string username, twitterHandle;
```
**GOOD:**
```csharp
string username;
string twitterHandle;
```
### Classes
Exactly one class per source file, although inner classes are encouraged where scoping appropriate.
### Interfaces
All interfaces should be prefaced with the letter **I**.
**BAD:**
```csharp
RadialSlider
```
**GOOD:**
```csharp
IRadialSlider
```
## Spacing
Spacing is especially important in raywenderlich.com code, as code needs to be easily readable as part of the tutorial.
### Indentation
Indentation should be done using **spaces** — never tabs.
#### Blocks
Indentation for blocks uses **4 spaces** for optimal readability:
**BAD:**
```csharp
for (int i = 0; i < 10; i++)
{
Debug.Log("index=" + i);
}
```
**GOOD:**
```csharp
for (int i = 0; i < 10; i++)
{
Debug.Log("index=" + i);
}
```
#### Line Wraps
Indentation for line wraps should use **4 spaces** (not the default 8):
**BAD:**
```csharp
CoolUiWidget widget =
someIncrediblyLongExpression(that, reallyWouldNotFit, on, aSingle, line);
```
**GOOD:**
```csharp
CoolUiWidget widget =
someIncrediblyLongExpression(that, reallyWouldNotFit, on, aSingle, line);
```
### Line Length
Lines should be no longer than **100** characters long.
### Vertical Spacing
There should be exactly one blank line between methods to aid in visual clarity
and organization. Whitespace within methods should separate functionality, but
having too many sections in a method often means you should refactor into
several methods.
## Brace Style
All braces get their own line as it is a C# convention:
**BAD:**
```csharp
class MyClass {
void DoSomething() {
if (someTest) {
// ...
} else {
// ...
}
}
}
```
**GOOD:**
```csharp
class MyClass
{
void DoSomething()
{
if (someTest)
{
// ...
}
else
{
// ...
}
}
}
```
Conditional statements are always required to be enclosed with braces,
irrespective of the number of lines required.
**BAD:**
```csharp
if (someTest)
doSomething();
if (someTest) doSomethingElse();
```
**GOOD:**
```csharp
if (someTest)
{
DoSomething();
}
if (someTest)
{
DoSomethingElse();
}
```
## Switch Statements
Switch-statements come with `default` case by default (heh). If the `default` case is never reached, be sure to remove it.
**DEFAULT GETS USED:**
```csharp
switch (variable)
{
case 1:
break;
case 2:
break;
default:
break;
}
```
**DEFAULT DOESN'T GET USED:**
```csharp
switch (variable)
{
case 1:
break;
case 2:
break;
}
```
## Language
Use US English spelling.
**BAD:**
```csharp
string colour = "red";
```
**GOOD:**
```csharp
string color = "red";
```
Indentation
Maximum Line Length
Line Wraps
Blank Lines
Whitespaces in Expressions and Statements
Imports/usings/regions
Comments
Naming Conventions
links
https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/index
https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/inside-a-program/coding-conventions
https://www.dofactory.com/reference/csharp-coding-standards
| 18.264642 | 236 | 0.687886 | eng_Latn | 0.968227 |
24af51bbb7dbfede02674d2ba7b3a920090958d6 | 3,647 | md | Markdown | data-management-library/database-consolidation/introduction/intro-old.md | kamryn-v/learning-library | 5da55c082ccc41772ade8cd08af6c275737925b2 | [
"UPL-1.0"
] | 3 | 2020-04-03T17:57:44.000Z | 2020-05-31T06:50:06.000Z | data-management-library/database-consolidation/introduction/intro-old.md | kamryn-v/learning-library | 5da55c082ccc41772ade8cd08af6c275737925b2 | [
"UPL-1.0"
] | 1 | 2020-10-22T16:09:36.000Z | 2020-10-22T16:09:36.000Z | data-management-library/database-consolidation/introduction/intro-old.md | kamryn-v/learning-library | 5da55c082ccc41772ade8cd08af6c275737925b2 | [
"UPL-1.0"
] | 1 | 2020-06-24T16:38:53.000Z | 2020-06-24T16:38:53.000Z | # Workshop Introduction and Overview #
## Introduction to Consolidation of Oracle databases ##
Database consolidation involves placing multiple databases onto a single set of computing infrastructure, either on-premise or in
the Oracle Cloud. Database consolidation is similar to but different from server consolidation, which involves consolidating
multiple physical servers into a single physical server running Virtual Machines. The primary purpose of database consolidation
is to reduce the cost of database infrastructure by taking advantage of more powerful servers that have come onto the market that
include dozens of processor cores in a single server.
Databases consolidation may involve any of the following configurations:
- Multiple Databases on a Single Physical Server
- Multiple Databases on a Single Virtual Machine
- Multiple Databases on a Cluster of Physical Servers
- Multiple Databases on a Cluster of Virtual Machines
Database consolidation allows more databases to run on fewer servers, which reduces infrastructure, but also reduces operational
costs. Each physical server represents an Information Technology asset or “Configuration Item” (CI) that must be placed into a
data center rack, connected, secured, and maintained. Each Virtual Machine represents another Configuration Item (CI) that also
must be deployed, connected (virtually), secured, and maintained. Database Consolidation also applies in Cloud environments
such as the Oracle Database Cloud Service and Oracle Exadata Cloud Service.
Oracle databases can also be consolidated into a cluster of physical servers or virtual machines. Oracle Database clustering
capabilities include active/passive clustering, as well as active/active clustering using Oracle Real Application Clusters. Clustering
is used to increase availability of Oracle databases, enable rolling patching, and to provide for scalability across multiple physical
servers or virtual machines.
Oracle databases can also be further consolidated into what are known as Container Databases using the Oracle Multitenant
option that was first introduced in Oracle Database 12c. The Multitenant option allows multiple databases to be managed under
a single Container Database, with a single backup, single disaster recovery configuration, and single clustering configuration.
## Workshop Objectives
1. MV2ABD to consolidate databases on ADB
2. Goldengate to Consolidate databases on ADB / DBCS / EXADATA
3. Data Pump to Consolidate databases on ADB / DBCS / EXADATA
## Lab Breakdown
- Lab 1 : Consolidate your databases on ADB using MV2ADB
- Lab 2 : Consolidate your databases using Goldengate
- Lab 3 : Consolidate your databases using Data Pump
## Consolidation of Database
### MV2ADB
You want to move your data from on-premises to an autonomous database to maximum your database uptime, performance, and security, but you're concerned about how to safely and efficiently transfer the data.
The quickest method of data loading is to use Oracle Data Pump to upload the source files from on-premises to a cloud-based object store before loading the data into your autonomous database. One option is to use the Move to Autonomous Database (MV2ADB) tool to perform the entire data load process with a single click.
### Goldengate
Work in Progress..
### Data Pump
Work in Progress..
## Acknowledgements
- **Authors/Contributors** - NA Cloud Custom Apps and DB Engineering team
- **Last Updated By/Date** - October 2020
See an issue? Please open up a request [here](https://github.com/oracle/learning-library/issues). Please include the workshop name and lab in your request.
| 55.257576 | 319 | 0.811626 | eng_Latn | 0.990659 |
24af79e1a7a2f31a38ac38f93d9e9806d3210371 | 4,939 | md | Markdown | README.md | smaslan/TWM | bf731a8afd596d7f768cc8629aba980f4940f914 | [
"MIT"
] | null | null | null | README.md | smaslan/TWM | bf731a8afd596d7f768cc8629aba980f4940f914 | [
"MIT"
] | 3 | 2021-02-18T09:52:02.000Z | 2021-08-12T08:45:52.000Z | README.md | smaslan/TWM | bf731a8afd596d7f768cc8629aba980f4940f914 | [
"MIT"
] | 6 | 2017-11-20T12:52:22.000Z | 2021-08-03T15:29:06.000Z | 
# TWM - TracePQM Wattmeter
TWM is developed in scope of [EMPIR](https://msu.euramet.org/calls.html) project [TracePQM](http://tracepqm.cmi.cz/).
TWM is a transparent, metrology grade measurement system for traceable measurement of the Power and Power Quality (PQ) parameters. However, it is not restricted to power and PQ area only. It is designed to allow recording of the voltage and current waveforms using various digitizers and processing the measured waveforms using ANY algorithm. It is composed of two main components:
- User interface and instrument control in [LabVIEW](http://www.ni.com/labview/),
- [GNU Octave](https://www.gnu.org/software/octave/) or [Matlab](https://uk.mathworks.com/products/matlab.html) calculation scripts for data processing.
Both components are connected together into the single interactive application using [GOLPI](https://github.com/KaeroDot/GOLPI) interface. Note the current version does not support Matlab yet, however interface to the Matlab is already in development.
The TWM concept is modular, so it can be simply extended by various digitizer drivers whereas the rest of the application stays unchanged. In the current version the TWM supports:
- [niScope](http://sine.ni.com/nips/cds/view/p/lang/cs/nid/12638) drivers for control of NI's PXI-5922 digitizer for wideband measurements (can be unlocked for other cards as well...),
- Synchronized [HP/Agilent/Keysight 3458A](https://www.keysight.com/en/pd-1000001297%3Aepsg%3Apro-pn-3458A/digital-multimeter-8-digit?cc=US&lc=eng) sampling multimeters for precision measurements,
- [DirectSound](http://www.elektronika.kvalitne.cz/SW/dsdll/dsdll_eng.html) driver for ordinary soundcard for test purposes and low accuracy measurements,
- Simulated digitizer for debug purposes (synthesizer of the composite harmonics signal).
Modularity of the Power and PQ calculation algorithms used by the TWM is ensured by the [QWTB](https://qwtb.github.io/qwtb/) toolbox.
## Algorithms
Current version includes following algorithms:
- TWM-PSFE: Calculation of fundamental harmonic parameters by Phase Sensitive Frequency Estimator for non-coherent sampling (frequency, amplitude and phase).
- TWM-FPNLSF: Calculation of fundamental harmonic parameters by four parameter fitting for non-coherent sampling (frequency, amplitude, phase, offset).
- TWM-MFSF: Multi-harmonic fitting for non-coherent sampling (frequency, amplitudes, phases, offset, THD).
- TWM-MODTDPS: Calculation of amplitude modulation parameters for sine and rectangular modulation for non-coherent sampling.
- TWM-Flicker: Calculation of short-term flicker severity according IEC 61000-4-15 for non-coherent sampling.
- TWM-THDWFFT: Total Harmonic Distortion calculator and harmonics analyser for non-coherent sampling.
- TWM-PWRTDI: Four quadrant power meter by time-domain integration method for non-coherent sampling.
- TWM-PWRFFT: Four quadrant power meter by FFT method for coherent sampling.
- TWM-HCRMS: Half-cycle RMS calculator for PQ event detection according IEC 61000-3-40 for non-coherent sampling.
- TWM-InDiSwell: PQ event detection according IEC 61000-3-40 for non-coherent sampling.
- TWM-WRMS: RMS level calculation by time-domain integration method for non-coherent sampling.
- TWM-WFFT: Windowed FFT for single or multiharmonic estimation.
- TWM-InpZ: Estimator of digitizer input impedance (no uncertainty).
Details on the algorithms can be found in the [draft document A2.4.4 - Algorithms Description](https://github.com/smaslan/TWM/blob/master/doc/A244%20Algorithms%20description.pdf).
<img src="./imgz/gui_v2_small.jpg">
## Status
The project is still under development! In current version it can do following:
- Digitize waveforms using one of the supported digitizers in given configuration.
- Store the digitized waveforms in unified format independent of the digitizer.
- Display measured waveforms.
- Load the measured data and execute m-script on them using GNU Octave or Matlab:
- Direct call of the user m-code,
- or call of the algorithm from the QWTB toolbox.
- Display calculated results.
- Batch processing of recorded data.
## News
Important changes and news:
- 2017-11-20: First release.
- 2017-12-08: Matlab support.
- 2018-03-16: Improved GUI, few algorithms added.
- 2018-08-23: Improved GUI, 8 of 10 algorithms included (not validated yet!).
- 2019-01-24: Improved GUI, 10 of 10 algorithms included (not all validated yet!).
- 2019-04-04: Improved GUI, 12 algorithms included (not all validated yet!).
- 2019-04-15: Improved GUI, minor fixes.
## Download
Builds are available in separate Git: [smaslan/TWM-builds](https://github.com/smaslan/TWM-builds)
## License
The TWM is distributed under [MIT license](./LICENSE.txt). Note the algorithms in the QWTB toolbox may have different licenses.
| 63.320513 | 382 | 0.774448 | eng_Latn | 0.967889 |
24af863fe29bfbf56ec7157b5978aa3a2ff877f8 | 28 | md | Markdown | README.md | shinyhonor/StoneGameIV | fd131a7e875c6a26b9b7e22e0937674c4c3d686b | [
"MIT"
] | null | null | null | README.md | shinyhonor/StoneGameIV | fd131a7e875c6a26b9b7e22e0937674c4c3d686b | [
"MIT"
] | null | null | null | README.md | shinyhonor/StoneGameIV | fd131a7e875c6a26b9b7e22e0937674c4c3d686b | [
"MIT"
] | null | null | null | # StoneGameIV
Stone Game IV
| 9.333333 | 13 | 0.785714 | kor_Hang | 0.69535 |
24afd3ad11e5894e878d6a805762a68f789a540b | 2,005 | md | Markdown | docs/leetcode/leetcode-m59II.md | syfxlin/time-log | 66924e1cb5a42ec60c493244ae32378b8c5e431e | [
"MIT"
] | 4 | 2020-08-28T11:38:06.000Z | 2021-12-11T14:00:23.000Z | docs/leetcode/leetcode-m59II.md | syfxlin/time-log | 66924e1cb5a42ec60c493244ae32378b8c5e431e | [
"MIT"
] | null | null | null | docs/leetcode/leetcode-m59II.md | syfxlin/time-log | 66924e1cb5a42ec60c493244ae32378b8c5e431e | [
"MIT"
] | 1 | 2021-01-30T15:24:49.000Z | 2021-01-30T15:24:49.000Z | # [面试题 59]II 队列的最大值
> https://leetcode-cn.com/problems/dui-lie-de-zui-da-zhi-lcof/
请定义一个队列并实现函数 max_value 得到队列里的最大值，要求函数 max_value、push_back 和 pop_front 的均摊时间复杂度都是 O(1)。
若队列为空，pop_front 和 max_value 需要返回 -1
示例 1：
```
输入:
["MaxQueue","push_back","push_back","max_value","pop_front","max_value"]
[[],[1],[2],[],[],[]]
输出:[null,null,null,2,1,2]
```
示例 2：
```
输入:
["MaxQueue","pop_front","max_value"]
[[],[],[]]
输出:[null,-1,-1]
```
限制：
- 1 <= push_back,pop_front,max_value 的总操作数<= 10000
- 1 <= value <= 10^5
## 思考
本算法基于问题的一个重要性质：当一个元素进入队列的时候，它前面所有比它小的元素就不会再对答案产生影响。
举个例子，如果我们向队列中插入数字序列 1 1 1 1 2，那么在第一个数字 2 被插入后，数字 2 前面的所有数字 1 将不会对结果产生影响。因为按照队列的取出顺序，数字 2 只能在所有的数字 1 被取出之后才能被取出，因此如果数字 1 如果在队列中，那么数字 2 必然也在队列中，使得数字 1 对结果没有影响。
按照上面的思路，我们可以设计这样的方法：从队列尾部插入元素时，我们可以提前取出队列中所有比这个元素小的元素，使得队列中只保留对结果有影响的数字。这样的方法等价于要求维持队列单调递减，即要保证每个元素的前面都没有比它小的元素。
那么如何高效实现一个始终递减的队列呢？我们只需要在插入每一个元素 value 时，从队列尾部依次取出比当前元素 value 小的元素，直到遇到一个比当前元素大的元素 value' 即可。
上面的过程保证了只要在元素 value 被插入之前队列递减，那么在 value 被插入之后队列依然递减。
而队列的初始状态（空队列）符合单调递减的定义。
由数学归纳法可知队列将会始终保持单调递减。
上面的过程需要从队列尾部取出元素，因此需要使用双端队列来实现。另外我们也需要一个辅助队列来记录所有被插入的值，以确定 pop_front 函数的返回值。
保证了队列单调递减后，求最大值时只需要直接取双端队列中的第一项即可。
## 代码
```java
class MaxQueue {
Queue<Integer> queue;
Deque<Integer> deque;
public MaxQueue() {
queue = new LinkedList<>();
deque = new LinkedList<>();
}
public int max_value() {
return deque.isEmpty() ? -1 : deque.peekFirst();
}
public void push_back(int value) {
queue.add(value);
while (!deque.isEmpty() && value > deque.peekLast()) {
deque.pollLast();
}
deque.addLast(value);
}
public int pop_front() {
if (queue.isEmpty()) {
return -1;
}
int re_value = queue.poll();
if (re_value == deque.peekFirst()) {
deque.pollFirst();
}
return re_value;
}
}
/**
* Your MaxQueue object will be instantiated and called as such:
* MaxQueue obj = new MaxQueue();
* int param_1 = obj.max_value();
* obj.push_back(value);
* int param_3 = obj.pop_front();
*/
```
| 21.329787 | 157 | 0.689776 | yue_Hant | 0.437306 |
24b0107620408723744f58d790f45a82a8c53254 | 2,002 | md | Markdown | bluetooth_spp_with_windows/README.md | mundodisco8/bluetooth_applications | 5ee5734ec22b210f40b84ae9f1f98246d8ef8f4e | [
"Zlib"
] | 28 | 2020-05-27T08:36:36.000Z | 2022-03-13T15:35:30.000Z | bluetooth_spp_with_windows/README.md | futechiot/bluetooth_applications | f3529fff7c4c960c80e110ae2c5c52df71b01430 | [
"Zlib"
] | 7 | 2020-06-16T20:27:01.000Z | 2021-11-30T08:23:55.000Z | bluetooth_spp_with_windows/README.md | futechiot/bluetooth_applications | f3529fff7c4c960c80e110ae2c5c52df71b01430 | [
"Zlib"
] | 25 | 2021-01-06T15:38:54.000Z | 2022-03-09T11:45:14.000Z | # BLE SPP with Windows #
## Summary ##
This project uses Windows BLE API to communicate with the [SPP-over-BLE KBA](https://www.silabs.com/community/wireless/bluetooth/knowledge-base.entry.html/2017/04/13/spp-over-ble_c_examp-mnoe) example. A custom Windows Console App was created that acts like TeraTerm and PuTTY but uses BLE on the back end.
## Hardware Required ##
- One radio board which can run the SPP-over-BLE example
- One BRD4001A WSTK board
- A Windows PC
## Setup ##
Program the radio board with the SPP-over-BLE example code provided with the KBA. Connect the BLE device to the computer and open a COM port in the terminal application of your choice. Launch the provided executable and type in the name of the BLE device. The device should connect to the Windows machine, and they will be able to communicate. Typing in either console should send the data to the other.
## How It Works ##
This project was inspired by a community post which the user asked if there were examples of a BLE device communicating with the computer wirelessly. I thought substituting the VCOM USB communication to a computer terminal (PuTTY) with a Bluetooth wireless communication to a computer terminal would help debug if the device is not accessible. The application shows how printf is retargeted to use BLE and how to get keyboard inputs from the console on the device.
Since there is no official Windows Console Apps that have this functionality, a custom console app was created using Visual Studio. An executable file of the project allows any user to use this without having to download the Visual Studio IDE.
1. User types in name of BLE device
2. Console App finds and connects to the BLE device
3. Console App searches and saves the BLE characteristics related to SPP
4. Console App subscribes to SPP_data notifications and adds a callback to print the text whenever device notifies Windows
5. Whenever user types on the keyboard, the keystroke is saved into the SPP_data characteristic
| 71.5 | 464 | 0.796204 | eng_Latn | 0.999067 |
24b0955060e72719c27a0e860294b6e0433cbb9e | 347 | md | Markdown | README.md | konne/q2g-timerOnVariable | 71ad8cb5630b1210df02cb3c02cba5ca8df38c6a | [
"MIT"
] | 1 | 2018-12-11T16:40:04.000Z | 2018-12-11T16:40:04.000Z | README.md | konne/q2g-timerOnVariable | 71ad8cb5630b1210df02cb3c02cba5ca8df38c6a | [
"MIT"
] | null | null | null | README.md | konne/q2g-timerOnVariable | 71ad8cb5630b1210df02cb3c02cba5ca8df38c6a | [
"MIT"
] | null | null | null | # q2g-timerOnVariable
Qlik Extension that changes a variable with a timer
This extension shows on a simple example howto use the
enigmaJS inside a qlik extension.
# Install / Compile
1. Install Visual Studio 2015
2. Install TypeScript compiler
3. Build Project
4. import the q2g-timerOnVariable.zip from src\q2g-timerOnVariable\bin
| 26.692308 | 71 | 0.778098 | eng_Latn | 0.900079 |
24b0d5895a6c097934148ac6bb24ea0ef0cc2294 | 963 | md | Markdown | README.md | nishant-sethi/DeepLearning.ai | 7eaf4ac6aedee0b94fbd1737d08f65d856ddd40e | [
"Apache-2.0"
] | 8 | 2018-09-24T06:51:05.000Z | 2022-01-09T01:13:23.000Z | README.md | nishant-sethi/DeepLearning.ai | 7eaf4ac6aedee0b94fbd1737d08f65d856ddd40e | [
"Apache-2.0"
] | 1 | 2019-11-05T18:57:50.000Z | 2019-11-05T20:10:28.000Z | README.md | nishant-sethi/DeepLearning.ai | 7eaf4ac6aedee0b94fbd1737d08f65d856ddd40e | [
"Apache-2.0"
] | 15 | 2018-10-31T00:09:10.000Z | 2022-02-22T04:33:02.000Z | # DeepLearning.ai
This is my assignment on Andrew Ng's special course "Deep Learning Specialization" This course consists of five courses:
<b>Course Contents</b>
<b>Neural Networks and Deep Learning</b>
Week1 Introduction to deep learning
Week2 Neural Networks Basics
Week3 Shallow Neural networks
Week4 Deep Neural Networks
<b>Improving Deep Neural Networks</b>
Week1 Practical aspects of Deep Learning(Initialization-Regularization-Gradient Checking)
Week2 Optimization algorithms
Week3 Hyperparameter tuning, Batch Normalization and Programming Frameworks
<b>Convolutional Neural Network</b>
Week1 Foundations of Convolutional Neural Networks
Week2 Deep convolutional models: case studies
Week3 Object detection
Week4 Special applications: Face recognition & Neural style transfer
<b>Sequence Models</b>
Week1 Recurrent Neural Networks
Week2 Natural Language Processing & Word Embeddings
Week3 Sequence models & Attention mechanism
| 21.4 | 120 | 0.812046 | eng_Latn | 0.700022 |
24b1696e7d05e697f5045e53c3e4a97319743014 | 1,477 | md | Markdown | _posts/2020-07-10-HTML中表单校验（正则）的小总结（onkeyup、onafterpaste、ng-pattern）.md | Anarkh-Lee/Anarkh-Lee.github.io | 796e8ec5a4caf9154022b16aee6ad86f84485e57 | [
"MIT"
] | null | null | null | _posts/2020-07-10-HTML中表单校验（正则）的小总结（onkeyup、onafterpaste、ng-pattern）.md | Anarkh-Lee/Anarkh-Lee.github.io | 796e8ec5a4caf9154022b16aee6ad86f84485e57 | [
"MIT"
] | null | null | null | _posts/2020-07-10-HTML中表单校验（正则）的小总结（onkeyup、onafterpaste、ng-pattern）.md | Anarkh-Lee/Anarkh-Lee.github.io | 796e8ec5a4caf9154022b16aee6ad86f84485e57 | [
"MIT"
] | null | null | null | ---
layout: post
title: 'HTML中表单校验（正则）的小总结（onkeyup、onafterpaste、ng-pattern）'
date: 2020-07-10
author: Anarkh-Lee
cover: 'http://on2171g4d.bkt.clouddn.com/jekyll-banner.png'
tags: HTML
---
> 校验失败表单自动清空、校验信息及时显示在HTML页面上等。
##### 1、限制只能输入数字，非数字清空（粘贴非数字也清空）
```html
<div class="col-md-3" align="right">
<label style="color: red;">获奖年度</label>
</div>
<div class="col-md-8">
<input type="text" class="form-control" ng-model="tf0fadd.atf0f4" maxlength="4" onkeyup="this.value=this.value.replace(/[^\d]/g,'') " onafterpaste="this.value=this.value.replace(/[^\d]/g,'') ">
</div>
```
```
注:
onafterpaste事件是指限制文本框只能输入数字 onkeyup+onafterpaste。
“onkeyup”是指按键抬起触发，“onafterpaste”是指粘贴后打开。
整体的意思是用于限制只能输入数字。
/[^\d]/g:全局查找非数字 str是否符合非数字
```
##### 2、在html上使用正则校验年度提醒
```html
<form name="infoForm" class="form-horizontal formCustomSetting normalForm">
<div class="col-md-2">
<label><font color="red">申报年度</font></label>
</div>
<div class="col-md-3">
<input type="text" class="form-control" ng-model="tf50web.aae001" name="aae001" ng-pattern="/^(19\d{2}|20\d{2}|2100)$/" maxlength="4" />
<span style="color: #ce0000;" class="warning" ng- show="infoForm.aae001.$error.pattern">年度格式如2018</span>
</div>
</form>
```
效果：
```
注：
使用ng-pattern进行验证表单时（实际上使用ng进行表单验证时），需要给<form>、<input>等name属性赋值。
```
<iframe type="text/html" width="100%" height="385" src="http://www.youtube.com/embed/gfmjMWjn-Xg" frameborder="0"></iframe> | 25.912281 | 213 | 0.668923 | yue_Hant | 0.119857 |
24b2b93ea2cbb245a8b1bc05b3352f221ca25dd0 | 2,234 | md | Markdown | _posts/2016-01-03-COCKTAIL-DRESSES-Sherri-Hill-9813-Lace-Open-Back-Prom-Dress.md | lastgown/lastgown.github.io | f4a71e2a12910bc569ac7e77f819c2be1598d8e6 | [
"MIT"
] | null | null | null | _posts/2016-01-03-COCKTAIL-DRESSES-Sherri-Hill-9813-Lace-Open-Back-Prom-Dress.md | lastgown/lastgown.github.io | f4a71e2a12910bc569ac7e77f819c2be1598d8e6 | [
"MIT"
] | null | null | null | _posts/2016-01-03-COCKTAIL-DRESSES-Sherri-Hill-9813-Lace-Open-Back-Prom-Dress.md | lastgown/lastgown.github.io | f4a71e2a12910bc569ac7e77f819c2be1598d8e6 | [
"MIT"
] | null | null | null | ---
layout: post
date: '2016-01-03'
title: "COCKTAIL DRESSES Sherri Hill 9813 Lace Open Back Prom Dress"
category: COCKTAIL DRESSES
tags: [COCKTAIL DRESSES]
---
### COCKTAIL DRESSES Sherri Hill 9813 Lace Open Back Prom Dress
Just **$418.99**
###
Sherri Hill Lace prom dress style 9813 Available in sizes 00-16.
<a href="https://www.eudances.com/en/cocktail-dresses/1326-sherri-hill-9813-lace-open-back-prom-dress.html"><img src="//www.eudances.com/3966-thickbox_default/sherri-hill-9813-lace-open-back-prom-dress.jpg" alt="Sherri Hill 9813 Lace Open Back Prom Dress" style="width:100%;" /></a>
<!-- break --><a href="https://www.eudances.com/en/cocktail-dresses/1326-sherri-hill-9813-lace-open-back-prom-dress.html"><img src="//www.eudances.com/3967-thickbox_default/sherri-hill-9813-lace-open-back-prom-dress.jpg" alt="Sherri Hill 9813 Lace Open Back Prom Dress" style="width:100%;" /></a>
<a href="https://www.eudances.com/en/cocktail-dresses/1326-sherri-hill-9813-lace-open-back-prom-dress.html"><img src="//www.eudances.com/3968-thickbox_default/sherri-hill-9813-lace-open-back-prom-dress.jpg" alt="Sherri Hill 9813 Lace Open Back Prom Dress" style="width:100%;" /></a>
<a href="https://www.eudances.com/en/cocktail-dresses/1326-sherri-hill-9813-lace-open-back-prom-dress.html"><img src="//www.eudances.com/3969-thickbox_default/sherri-hill-9813-lace-open-back-prom-dress.jpg" alt="Sherri Hill 9813 Lace Open Back Prom Dress" style="width:100%;" /></a>
<a href="https://www.eudances.com/en/cocktail-dresses/1326-sherri-hill-9813-lace-open-back-prom-dress.html"><img src="//www.eudances.com/3970-thickbox_default/sherri-hill-9813-lace-open-back-prom-dress.jpg" alt="Sherri Hill 9813 Lace Open Back Prom Dress" style="width:100%;" /></a>
<a href="https://www.eudances.com/en/cocktail-dresses/1326-sherri-hill-9813-lace-open-back-prom-dress.html"><img src="//www.eudances.com/3965-thickbox_default/sherri-hill-9813-lace-open-back-prom-dress.jpg" alt="Sherri Hill 9813 Lace Open Back Prom Dress" style="width:100%;" /></a>
Buy it: [https://www.eudances.com/en/cocktail-dresses/1326-sherri-hill-9813-lace-open-back-prom-dress.html](https://www.eudances.com/en/cocktail-dresses/1326-sherri-hill-9813-lace-open-back-prom-dress.html)
| 106.380952 | 296 | 0.75291 | kor_Hang | 0.216897 |
24b3c3f18514d9e9c0800c457cf7d4d9c323d1a2 | 995 | md | Markdown | README.md | paulpessoa/HiringCodersVTEX | 1d7c36f41eaec2247bca7f8f1e6fcbf9ba9855f0 | [
"MIT"
] | 1 | 2021-07-17T03:01:40.000Z | 2021-07-17T03:01:40.000Z | README.md | paulpessoa/HiringCodersVTEX | 1d7c36f41eaec2247bca7f8f1e6fcbf9ba9855f0 | [
"MIT"
] | null | null | null | README.md | paulpessoa/HiringCodersVTEX | 1d7c36f41eaec2247bca7f8f1e6fcbf9ba9855f0 | [
"MIT"
] | null | null | null | # HiringCodersVTEX
O Hiring Coders é um programa de capacitação gratuito e sem pré-requisitos, feito para todos que querem uma carreira à prova do futuro.
- [ ] Treinamento 1 - Front-end (1ª à 3ª semana)
> Nesta fase os participantes receberá um treinamento de front-end com os conteúdos de: Introdução, Lógica de Programação, GIT, Javascript BásicoJavascript Intermediário, Typescript, React.
- [ ] Treinamento 2 - Back-end (4ª à 5ª semana)
> Não só de front vive um programador não é mesmo, por isso iremos te transformar em uma pessoa desenvolvedora fullstack nas três próximas semanas de treinamentos em back end. com os conteúdos de: Node.JS e GraphQl
- [ ] Treinamento 3 - ecommerce (6ª à 9ª semana)
> Além de formar profissionais com grandes habilidades full-stacks, iremos especializá-los na plataforma mais desejada do mercado de ecommerce VTEX com os conteúdos de: Devops + AWS, VTEX IO, Desenvolvendo com VTEX IO, Projetos de ecommerce.
Acesse: https://www.hiringcoders.com.br/
| 62.1875 | 241 | 0.779899 | por_Latn | 0.999741 |
24b45dafabce8a9f7a752de98724f0edf1131b4f | 11,575 | md | Markdown | notes/BGOONZ_BLOG_2.0.wiki/list-of-links.md.md | side-projects-42/blog-starter2.0 | 015f7d91f08a463f898fb59fbcd6655afb774696 | [
"MIT"
] | 17 | 2021-06-02T23:44:26.000Z | 2022-03-12T02:30:34.000Z | notes/BGOONZ_BLOG_2.0.wiki/list-of-links.md.md | side-projects-42/blog-starter2.0 | 015f7d91f08a463f898fb59fbcd6655afb774696 | [
"MIT"
] | 1,632 | 2021-05-12T03:46:54.000Z | 2022-03-31T05:29:11.000Z | notes/BGOONZ_BLOG_2.0.wiki/list-of-links.md.md | Web-Dev-Collaborative/BGOONZ_BLOG_2.0 | 385e121576326bc261763349a97fe9d08e278641 | [
"MIT"
] | 22 | 2021-06-06T11:31:00.000Z | 2022-03-30T11:11:33.000Z | ```
https://bgoonz-blog.netlify.app/
https://bgoonz-blog.netlify.app/blog
https://bgoonz-blog.netlify.app/docs
https://bgoonz-blog.netlify.app/privacy-policy
https://bgoonz-blog.netlify.app/readme
https://bgoonz-blog.netlify.app/showcase
https://bgoonz-blog.netlify.app/blog/300-react-questions
https://bgoonz-blog.netlify.app/blog/awesome-graphql
https://bgoonz-blog.netlify.app/blog/big-o-complexity
https://bgoonz-blog.netlify.app/blog/blog-archive
https://bgoonz-blog.netlify.app/blog/blogwcomments
https://bgoonz-blog.netlify.app/blog/data-structures
https://bgoonz-blog.netlify.app/blog/flow-control-in-python
https://bgoonz-blog.netlify.app/blog/functions-in-python
https://bgoonz-blog.netlify.app/blog/git-gateway
https://bgoonz-blog.netlify.app/blog/interview-questions-js
https://bgoonz-blog.netlify.app/blog/netlify-cms
https://bgoonz-blog.netlify.app/blog/platform-docs
https://bgoonz-blog.netlify.app/blog/python-for-js-dev
https://bgoonz-blog.netlify.app/blog/python-resources
https://bgoonz-blog.netlify.app/blog/web-dev-trends
https://bgoonz-blog.netlify.app/blog/web-scraping
https://bgoonz-blog.netlify.app/docs/about
https://bgoonz-blog.netlify.app/docs/articles
https://bgoonz-blog.netlify.app/docs/audio
https://bgoonz-blog.netlify.app/docs/career
https://bgoonz-blog.netlify.app/docs/community
https://bgoonz-blog.netlify.app/docs/content
https://bgoonz-blog.netlify.app/docs/data-structures
https://bgoonz-blog.netlify.app/docs/docs
https://bgoonz-blog.netlify.app/docs/faq
https://bgoonz-blog.netlify.app/docs/interact
https://bgoonz-blog.netlify.app/docs/interview
https://bgoonz-blog.netlify.app/docs/javascript
https://bgoonz-blog.netlify.app/docs/leetcode
https://bgoonz-blog.netlify.app/docs/privacy-policy
https://bgoonz-blog.netlify.app/docs/projects
https://bgoonz-blog.netlify.app/docs/python
https://bgoonz-blog.netlify.app/docs/quick-reference
https://bgoonz-blog.netlify.app/docs/react
https://bgoonz-blog.netlify.app/docs/reference
https://bgoonz-blog.netlify.app/docs/sitemap
https://bgoonz-blog.netlify.app/docs/tips
https://bgoonz-blog.netlify.app/docs/tools
https://bgoonz-blog.netlify.app/docs/tutorials
https://bgoonz-blog.netlify.app/docs/about/README
https://bgoonz-blog.netlify.app/docs/about/eng-portfolio
https://bgoonz-blog.netlify.app/docs/about/intrests
https://bgoonz-blog.netlify.app/docs/about/job-search
https://bgoonz-blog.netlify.app/docs/about/resume
https://bgoonz-blog.netlify.app/docs/articles/basic-web-dev
https://bgoonz-blog.netlify.app/docs/articles/buffers
https://bgoonz-blog.netlify.app/docs/articles/dev-dep
https://bgoonz-blog.netlify.app/docs/articles/event-loop
https://bgoonz-blog.netlify.app/docs/articles/fs-module
https://bgoonz-blog.netlify.app/docs/articles/how-the-web-works
https://bgoonz-blog.netlify.app/docs/articles/http
https://bgoonz-blog.netlify.app/docs/articles/install
https://bgoonz-blog.netlify.app/docs/articles/intro
https://bgoonz-blog.netlify.app/docs/articles/modules
https://bgoonz-blog.netlify.app/docs/articles/nextjs
https://bgoonz-blog.netlify.app/docs/articles/node-api-express
https://bgoonz-blog.netlify.app/docs/articles/node-cli-args
https://bgoonz-blog.netlify.app/docs/articles/node-common-modules
https://bgoonz-blog.netlify.app/docs/articles/node-env-variables
https://bgoonz-blog.netlify.app/docs/articles/node-js-language
https://bgoonz-blog.netlify.app/docs/articles/node-package-manager
https://bgoonz-blog.netlify.app/docs/articles/node-repl
https://bgoonz-blog.netlify.app/docs/articles/node-run-cli
https://bgoonz-blog.netlify.app/docs/articles/nodejs
https://bgoonz-blog.netlify.app/docs/articles/nodevsbrowser
https://bgoonz-blog.netlify.app/docs/articles/npm
https://bgoonz-blog.netlify.app/docs/articles/npx
https://bgoonz-blog.netlify.app/docs/articles/os-module
https://bgoonz-blog.netlify.app/docs/articles/reading-files
https://bgoonz-blog.netlify.app/docs/articles/semantic
https://bgoonz-blog.netlify.app/docs/articles/semantic-html
https://bgoonz-blog.netlify.app/docs/articles/the-uniform-resource-locator-(url)
https://bgoonz-blog.netlify.app/docs/articles/understanding-firebase
https://bgoonz-blog.netlify.app/docs/articles/v8
https://bgoonz-blog.netlify.app/docs/articles/web-standards-checklist
https://bgoonz-blog.netlify.app/docs/articles/webdev-tools
https://bgoonz-blog.netlify.app/docs/articles/writing-files
https://bgoonz-blog.netlify.app/docs/audio/audio
https://bgoonz-blog.netlify.app/docs/audio/audio-feature-extraction
https://bgoonz-blog.netlify.app/docs/audio/dfft
https://bgoonz-blog.netlify.app/docs/audio/discrete-fft
https://bgoonz-blog.netlify.app/docs/audio/dtw-python-explained
https://bgoonz-blog.netlify.app/docs/audio/dynamic-time-warping
https://bgoonz-blog.netlify.app/docs/audio/web-audio-api
https://bgoonz-blog.netlify.app/docs/career/dev-interview
https://bgoonz-blog.netlify.app/docs/career/interview-dos-n-donts
https://bgoonz-blog.netlify.app/docs/career/job-boards
https://bgoonz-blog.netlify.app/docs/community/an-open-letter-2-future-developers
https://bgoonz-blog.netlify.app/docs/community/video-chat
https://bgoonz-blog.netlify.app/docs/content/algo
https://bgoonz-blog.netlify.app/docs/content/archive
https://bgoonz-blog.netlify.app/docs/content/gatsby-Queries-Mutations
https://bgoonz-blog.netlify.app/docs/content/history-api
https://bgoonz-blog.netlify.app/docs/content/main-projects
https://bgoonz-blog.netlify.app/docs/content/trouble-shooting
https://bgoonz-blog.netlify.app/docs/docs/appendix
https://bgoonz-blog.netlify.app/docs/docs/art-of-command-line
https://bgoonz-blog.netlify.app/docs/docs/bash
https://bgoonz-blog.netlify.app/docs/docs/content
https://bgoonz-blog.netlify.app/docs/docs/css
https://bgoonz-blog.netlify.app/docs/docs/data-structures-docs
https://bgoonz-blog.netlify.app/docs/docs/es-6-features
https://bgoonz-blog.netlify.app/docs/docs/git-reference
https://bgoonz-blog.netlify.app/docs/docs/git-repos
https://bgoonz-blog.netlify.app/docs/docs/html-spec
https://bgoonz-blog.netlify.app/docs/docs/markdown
https://bgoonz-blog.netlify.app/docs/docs/no-whiteboarding
https://bgoonz-blog.netlify.app/docs/docs/node-docs-complete
https://bgoonz-blog.netlify.app/docs/docs/node-docs-full
https://bgoonz-blog.netlify.app/docs/docs/regex-in-js
https://bgoonz-blog.netlify.app/docs/docs/sitemap
https://bgoonz-blog.netlify.app/docs/faq/contact
https://bgoonz-blog.netlify.app/docs/faq/plug-ins
https://bgoonz-blog.netlify.app/docs/interact/callstack-visual
https://bgoonz-blog.netlify.app/docs/interact/clock
https://bgoonz-blog.netlify.app/docs/interact/jupyter-notebooks
https://bgoonz-blog.netlify.app/docs/interact/other-sites
https://bgoonz-blog.netlify.app/docs/interact/search
https://bgoonz-blog.netlify.app/docs/interact/video-chat
https://bgoonz-blog.netlify.app/docs/interview/front-end
https://bgoonz-blog.netlify.app/docs/interview/job-search-nav
https://bgoonz-blog.netlify.app/docs/interview/review-concepts
https://bgoonz-blog.netlify.app/docs/javascript/arrow-functions
https://bgoonz-blog.netlify.app/docs/javascript/asyncjs
https://bgoonz-blog.netlify.app/docs/javascript/await-keyword
https://bgoonz-blog.netlify.app/docs/javascript/bigo
https://bgoonz-blog.netlify.app/docs/javascript/clean-code
https://bgoonz-blog.netlify.app/docs/javascript/constructor-functions
https://bgoonz-blog.netlify.app/docs/javascript/promises
https://bgoonz-blog.netlify.app/docs/javascript/review
https://bgoonz-blog.netlify.app/docs/javascript/this-is-about-this
https://bgoonz-blog.netlify.app/docs/projects/embeded-websites
https://bgoonz-blog.netlify.app/docs/projects/list-of-projects
https://bgoonz-blog.netlify.app/docs/projects/mini-projects
https://bgoonz-blog.netlify.app/docs/projects/mini-projects2
https://bgoonz-blog.netlify.app/docs/projects/my-websites
https://bgoonz-blog.netlify.app/docs/python/at-length
https://bgoonz-blog.netlify.app/docs/python/cheat-sheet
https://bgoonz-blog.netlify.app/docs/python/comprehensive-guide
https://bgoonz-blog.netlify.app/docs/python/examples
https://bgoonz-blog.netlify.app/docs/python/flow-control
https://bgoonz-blog.netlify.app/docs/python/functions
https://bgoonz-blog.netlify.app/docs/python/google-sheets-api
https://bgoonz-blog.netlify.app/docs/python/intro-for-js-devs
https://bgoonz-blog.netlify.app/docs/python/python-ds
https://bgoonz-blog.netlify.app/docs/python/snippets
https://bgoonz-blog.netlify.app/docs/quick-reference/Emmet
https://bgoonz-blog.netlify.app/docs/quick-reference/all-emojis
https://bgoonz-blog.netlify.app/docs/quick-reference/create-react-app
https://bgoonz-blog.netlify.app/docs/quick-reference/git-bash
https://bgoonz-blog.netlify.app/docs/quick-reference/git-tricks
https://bgoonz-blog.netlify.app/docs/quick-reference/google-firebase
https://bgoonz-blog.netlify.app/docs/quick-reference/heroku-error-codes
https://bgoonz-blog.netlify.app/docs/quick-reference/installation
https://bgoonz-blog.netlify.app/docs/quick-reference/markdown-dropdowns
https://bgoonz-blog.netlify.app/docs/quick-reference/minifiction
https://bgoonz-blog.netlify.app/docs/quick-reference/new-repo-instructions
https://bgoonz-blog.netlify.app/docs/quick-reference/psql-setup
https://bgoonz-blog.netlify.app/docs/quick-reference/pull-request-rubric
https://bgoonz-blog.netlify.app/docs/quick-reference/quick-links
https://bgoonz-blog.netlify.app/docs/quick-reference/topRepos
https://bgoonz-blog.netlify.app/docs/quick-reference/understanding-path
https://bgoonz-blog.netlify.app/docs/quick-reference/vscode-themes
https://bgoonz-blog.netlify.app/docs/react/ajax-n-apis
https://bgoonz-blog.netlify.app/docs/react/cheatsheet
https://bgoonz-blog.netlify.app/docs/react/createReactApp
https://bgoonz-blog.netlify.app/docs/react/demo
https://bgoonz-blog.netlify.app/docs/react/dont-use-index-as-keys
https://bgoonz-blog.netlify.app/docs/react/jsx
https://bgoonz-blog.netlify.app/docs/react/react-docs
https://bgoonz-blog.netlify.app/docs/react/react-in-depth
https://bgoonz-blog.netlify.app/docs/react/react2
https://bgoonz-blog.netlify.app/docs/react/render-elements
https://bgoonz-blog.netlify.app/docs/reference/awesome-lists
https://bgoonz-blog.netlify.app/docs/reference/awesome-nodejs
https://bgoonz-blog.netlify.app/docs/reference/awesome-static
https://bgoonz-blog.netlify.app/docs/reference/bash-commands
https://bgoonz-blog.netlify.app/docs/reference/bookmarks
https://bgoonz-blog.netlify.app/docs/reference/embed-the-web
https://bgoonz-blog.netlify.app/docs/reference/gists
https://bgoonz-blog.netlify.app/docs/reference/github-search
https://bgoonz-blog.netlify.app/docs/reference/google-cloud
https://bgoonz-blog.netlify.app/docs/reference/how-2-reinstall-npm
https://bgoonz-blog.netlify.app/docs/reference/how-to-kill-a-process
https://bgoonz-blog.netlify.app/docs/reference/installing-node
https://bgoonz-blog.netlify.app/docs/reference/intro-to-nodejs
https://bgoonz-blog.netlify.app/docs/reference/notes-template
https://bgoonz-blog.netlify.app/docs/reference/psql
https://bgoonz-blog.netlify.app/docs/reference/resources
https://bgoonz-blog.netlify.app/docs/reference/vscode
https://bgoonz-blog.netlify.app/docs/reference/web-api's
https://bgoonz-blog.netlify.app/docs/tips/array-methods
https://bgoonz-blog.netlify.app/docs/tips/insert-into-array
https://bgoonz-blog.netlify.app/docs/tools/Archive
https://bgoonz-blog.netlify.app/docs/tools/data-structures
https://bgoonz-blog.netlify.app/docs/tools/dev-utilities
https://bgoonz-blog.netlify.app/docs/tools/embed-showcase
https://bgoonz-blog.netlify.app/docs/tools/markdown-html
https://bgoonz-blog.netlify.app/docs/tutorials/enviorment-setup
```
| 55.649038 | 81 | 0.808121 | yue_Hant | 0.576046 |
24b4944d9c1788b0966968d4eff3a128f1bccc2f | 748 | md | Markdown | njswpose/README.md | ddmm2020/njswpose | aad2ddc7dede973c5f359ff888f799d2431e590b | [
"MIT"
] | 3 | 2021-01-08T15:32:17.000Z | 2021-01-17T14:11:33.000Z | njswpose/README.md | ddmm2020/njswpose | aad2ddc7dede973c5f359ff888f799d2431e590b | [
"MIT"
] | null | null | null | njswpose/README.md | ddmm2020/njswpose | aad2ddc7dede973c5f359ff888f799d2431e590b | [
"MIT"
] | null | null | null | Introduction
-----
This package is used to estimate human body keypoints, developed by Waterway Research Insitutue of Nanjing
E-mail: [email protected]
our backbone netwoork is resnet50.
Installation
-----
```bash
pip install njswpose
or
# If you have changed your mirror source. You should try the following command.
pip install njswpose -i https://www.pypi.org/simple/
```
Example
-----
```bash
from PIL import Image
import PIL
from torchvision.transforms import transforms
from njswpose import pose_detection
image = Image.open('./test.jpg').convert('RGB')
loader = transforms.Compose([
transforms.ToTensor()])
image = loader(image)
pose_detection(image, detect_threshold=0.55, vis=True)
```
| 22.666667 | 108 | 0.713904 | eng_Latn | 0.906317 |
24b56d9caa38f700c6c76b1e56bc797cb3ab1a5e | 711 | md | Markdown | docs/standard-library/condition-variable-enums.md | trappergor/cpp-docs.ru-ru | 78663307b833606876da4cec59cd4512b67b641a | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-04T19:48:06.000Z | 2020-05-04T19:48:13.000Z | docs/standard-library/condition-variable-enums.md | trappergor/cpp-docs.ru-ru | 78663307b833606876da4cec59cd4512b67b641a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard-library/condition-variable-enums.md | trappergor/cpp-docs.ru-ru | 78663307b833606876da4cec59cd4512b67b641a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Перечисления <condition_variable>
ms.date: 11/04/2016
f1_keywords:
- condition_variable/std::cv_status
ms.assetid: f261ad79-e25b-4afa-9f8a-909ce697e0d8
ms.openlocfilehash: 593b79115e6f58edd8224d5f38dc6fbefb132fe4
ms.sourcegitcommit: 590e488e51389066a4da4aa06d32d4c362c23393
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 10/21/2019
ms.locfileid: "72689782"
---
# <a name="ltcondition_variablegt-enums"></a>Перечисления <condition_variable>
## <a name="cv_status"></a>cv_status
Предоставляет символьные имена для возвращаемых значений методов класса Template [CONDITION_VARIABLE](../standard-library/condition-variable-class.md).
Класс cv_status { no_timeout timeout };
| 33.857143 | 151 | 0.81294 | yue_Hant | 0.114806 |
24b5e85dbf96f3fc8b32118390787754f6256cb3 | 413 | md | Markdown | README.md | Rahulsawriya/udacity-image-classifier | ea576edfc88487edd4c5970659aa6225464dcab4 | [
"MIT"
] | null | null | null | README.md | Rahulsawriya/udacity-image-classifier | ea576edfc88487edd4c5970659aa6225464dcab4 | [
"MIT"
] | null | null | null | README.md | Rahulsawriya/udacity-image-classifier | ea576edfc88487edd4c5970659aa6225464dcab4 | [
"MIT"
] | null | null | null | # AI Programming with Python Project
Project code for Udacity's AI Programming with Python Nanodegree program. In this project, students first develop code for an image classifier built with PyTorch, then convert it into a command line application.
python train.py --save_dir checkpoint/ --gpu
python predict.py --image flowers/train/10/image_08090.jpg --checkpoint checkpoint --category_names cat_to_name.json
| 59 | 211 | 0.813559 | eng_Latn | 0.975659 |
24b635567e356947c588a6e2f832ae1b01ba3b74 | 20,089 | md | Markdown | aspnet/web-forms/overview/older-versions-getting-started/continuing-with-ef/what-s-new-in-the-entity-framework-4.md | d3suu/Docs.pl-pl | 298a5fea0179b8a52233aa60d7d0a5ac2e5df20c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnet/web-forms/overview/older-versions-getting-started/continuing-with-ef/what-s-new-in-the-entity-framework-4.md | d3suu/Docs.pl-pl | 298a5fea0179b8a52233aa60d7d0a5ac2e5df20c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnet/web-forms/overview/older-versions-getting-started/continuing-with-ef/what-s-new-in-the-entity-framework-4.md | d3suu/Docs.pl-pl | 298a5fea0179b8a52233aa60d7d0a5ac2e5df20c | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-25T21:46:03.000Z | 2020-05-25T21:46:03.000Z | ---
uid: web-forms/overview/older-versions-getting-started/continuing-with-ef/what-s-new-in-the-entity-framework-4
title: What's New in programu Entity Framework 4.0 | Dokumentacja firmy Microsoft
author: tdykstra
description: W tej serii samouczków opiera się na aplikacji sieci web firmy Contoso University, utworzony przez wprowadzenie do serii samouczków Entity Framework 4.0. CZY MOGĘ...
ms.author: riande
ms.date: 01/26/2011
ms.assetid: 393df4a8-b1db-44c4-9db7-2b533ca887d0
msc.legacyurl: /web-forms/overview/older-versions-getting-started/continuing-with-ef/what-s-new-in-the-entity-framework-4
msc.type: authoredcontent
ms.openlocfilehash: 402e7ace1abad899d32ed179d6b68de4e5a129f5
ms.sourcegitcommit: 45ac74e400f9f2b7dbded66297730f6f14a4eb25
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 08/16/2018
ms.locfileid: "41752904"
---
<a name="whats-new-in-the-entity-framework-40"></a>What's New in programu Entity Framework 4.0
====================
przez [Tom Dykstra](https://github.com/tdykstra)
> W tej serii samouczków jest oparta na Contoso University aplikacji sieci web, który jest tworzony przez [rozpoczęcie korzystania z programu Entity Framework](../getting-started-with-ef/the-entity-framework-and-aspnet-getting-started-part-1.md) serii samouczków. Jeśli nie została ukończona wcześniej samouczki, jako punkt początkowy na potrzeby tego samouczka możesz [pobrać aplikację](https://code.msdn.microsoft.com/ASPNET-Web-Forms-97f8ee9a) będzie utworzony. Możesz również [pobrać aplikację](https://code.msdn.microsoft.com/ASPNET-Web-Forms-6c7197aa) tworzone przez zakończenie serii samouczków. Jeśli masz pytania dotyczące samouczków, możesz zamieścić je do [forum ASP.NET Entity Framework](https://forums.asp.net/1227.aspx).
W poprzednim samouczku pokazano niektóre metody maksymalizowanie wydajności aplikacji sieci web, który używa programu Entity Framework. Ten samouczek zawiera przegląd niektórych Najważniejsze nowe funkcje w wersji 4 programu Entity Framework, a następnie łączy on zasobów, które oferują bardziej szczegółowy wprowadzenie do wszystkich nowych funkcji. Następujące funkcje wyróżnione w ramach tego samouczka:
- Klucz obcy skojarzenia.
- Wykonywanie poleceń SQL zdefiniowane przez użytkownika.
- Pierwszy model programowania.
- Obsługa POCO.
Ponadto krótko wprowadzi samouczka *najpierw kod rozwoju*, funkcja, która zostanie wprowadzona w kolejnej wersji programu Entity Framework.
Uruchom samouczek, uruchom program Visual Studio i otwarcie aplikacji sieci web firmy Contoso University pracowano w poprzednim samouczku.
## <a name="foreign-key-associations"></a>Skojarzenia klucza obcego
Entity Framework w wersji 3.5 dołączone właściwości nawigacji, ale nie zawierało właściwości klucza obcego w modelu danych. Na przykład `CourseID` i `StudentID` kolumn `StudentGrade` tabeli zostaną pominięte z `StudentGrade` jednostki.
[](what-s-new-in-the-entity-framework-4/_static/image1.png)
Przyczyna tego podejścia była, mówiąc ściślej, kluczy obcych są szczegółowo fizyczna implementacja i nie powinny znajdować się w modelu koncepcyjnego danych. Jednak w praktyce, jest często łatwiej jest pracować z jednostkami w kodzie, gdy masz bezpośredni dostęp do kluczy obcych.
Na przykład jak obcych kluczy w modelu danych można uprościć kod, należy wziąć pod uwagę sposób trzeba było kodowi *DepartmentsAdd.aspx* strony bez nich. W `Department` jednostki `Administrator` właściwość ma klucz obcy, który odpowiada `PersonID` w `Person` jednostki. Aby możliwe było nawiązanie skojarzenie między nowy dział i jego administratora, wszystkie trzeba było robić została ustawiona wartość `Administrator` właściwość `ItemInserting` program obsługi zdarzeń kontrolki z danymi:
[!code-csharp[Main](what-s-new-in-the-entity-framework-4/samples/sample1.cs)]
Bez klucze obce w modelu danych, możesz obsługiwać `Inserting` zdarzeń do kontroli źródła danych zamiast `ItemInserting` zdarzeń kontrolki z danymi, aby pobrać odwołanie do jednostki, sama przed jednostka zostanie dodana do zestawu jednostek. W przypadku tego odwołania jest nawiązywane skojarzenia przy użyciu kodu, tak jak w następujących przykładach:
[!code-csharp[Main](what-s-new-in-the-entity-framework-4/samples/sample2.cs)]
[!code-csharp[Main](what-s-new-in-the-entity-framework-4/samples/sample3.cs)]
Jak widać w zespole platformy Entity Framework [wpis w blogu na klucza obcego skojarzenia](https://blogs.msdn.com/b/efdesign/archive/2009/03/16/foreign-keys-in-the-entity-framework.aspx), są inne przypadki, w którym różnica w złożoność kodu jest dużo większy. Aby zaspokoić potrzeby tych, którzy wolą przy użyciu szczegółów implementacji w model koncepcyjny danych w celu uproszczenia kodu, platformy Entity Framework teraz z opcją, w tym klucze obce w modelu danych.
W terminologii programu Entity Framework, jeśli zawiera klucze obce w modelu danych używasz *skojarzenia klucza obcego*, i jeśli wykluczasz klucze obce używasz *niezależnych skojarzenia*.
## <a name="executing-user-defined-sql-commands"></a>Wykonywanie poleceń SQL zdefiniowane przez użytkownika
We wcześniejszych wersjach programu Entity Framework nie było żadnych łatwy sposób tworzenia własnych poleceń SQL na bieżąco i uruchom je. Entity Framework generowana dynamicznie poleceń SQL dla Ciebie albo było konieczne tworzenie procedur składowanych i zaimportuj go jako funkcję. W wersji 4 dodaje `ExecuteStoreQuery` i `ExecuteStoreCommand` metody `ObjectContext` klasę, która ułatwić przekazywać dowolne zapytanie bezpośrednio do bazy danych.
Załóżmy, że administratorzy Contoso University chcesz móc wykonywać zbiorcze zmiany w bazie danych bez konieczności przechodzenia przez proces tworzenia procedury składowanej i importowanie go do modelu danych. Jest ich pierwsze żądanie dla strony, która umożliwi zmianę liczby kredytów na wszystkie kursy w bazie danych. Na stronie sieci web chcą mieć możliwość wprowadzania numer na potrzeby Mnoży wartość każdego `Course` wiersza `Credits` kolumny.
Utwórz nową stronę, która używa *Site.Master* strony wzorcowej i nadaj mu nazwę *UpdateCredits.aspx*. Następnie dodaj następujący kod do `Content` formantu o nazwie `Content2`:
[!code-aspx[Main](what-s-new-in-the-entity-framework-4/samples/sample4.aspx)]
Tworzy ten kod znaczników `TextBox` kontrolki, w którym użytkownik może wprowadzić wartość mnożnika `Button` kontrolki kliknij, aby wykonać polecenie, a `Label` kontrola określającą liczbę uwzględnionych wierszy.
Otwórz *UpdateCredits.aspx.cs*i dodaj następującą `using` instrukcji i procedury obsługi dla przycisku `Click` zdarzeń:
[!code-csharp[Main](what-s-new-in-the-entity-framework-4/samples/sample5.cs)]
[!code-csharp[Main](what-s-new-in-the-entity-framework-4/samples/sample6.cs)]
Ten kod jest wykonywany SQL `Update` polecenia przy użyciu wartości w polu tekstowym i użyto etykiety, aby wyświetlić liczbę uwzględnionych wierszy. Przed uruchomieniem strony uruchamiania *Courses.aspx* strony w celu uzyskania obrazu "before" niektórych danych.
[](what-s-new-in-the-entity-framework-4/_static/image3.png)
Uruchom *UpdateCredits.aspx*wprowadź "10" jako mnożnik, a następnie kliknij przycisk **Execute**.
[](what-s-new-in-the-entity-framework-4/_static/image5.png)
Uruchom *Courses.aspx* strony ponownie, aby zobaczyć zmienione dane.
[](what-s-new-in-the-entity-framework-4/_static/image7.png)
(Jeśli chcesz ustawić liczbę środki na korzystanie z powrotem do ich oryginalnych wartości w *UpdateCredits.aspx.cs* zmienić `Credits * {0}` do `Credits / {0}` i uruchom ponownie na stronie wprowadzenie 10 co dzielnik.)
Aby uzyskać więcej informacji na temat wykonywania zapytań, które definiujesz w kodzie, zobacz [instrukcje: bezpośrednie wykonywanie poleceń względem źródła danych](https://msdn.microsoft.com/library/ee358769.aspx).
## <a name="model-first-development"></a>Pierwszy model programowania
Te przewodniki służy do wcześniejszego utworzenia bazy danych i następnie generowane model danych oparty na strukturze bazy danych. W programie Entity Framework 4 możesz zamiast tego uruchomić przy użyciu modelu danych i wygenerować bazę danych na podstawie struktury modelu danych. Jeśli tworzysz aplikację, dla którego jeszcze nie istnieje baza danych podejście modelu pozwala na tworzenie jednostek i relacji, które mają sens koncepcyjnie dla aplikacji, podczas nie martwiąc się o szczegóły implementacji fizycznych . (To pozostaje prawdziwy wyłącznie za pośrednictwem początkowych etapów rozwoju, jednak. Po pewnym czasie baza danych zostanie utworzony i będzie mieć danych produkcyjnych w nim i odtworzenia go z modelu nie będzie już praktyczne; w tym momencie będziesz mieć do podejście bazy danych.)
W tej części samouczka możesz utworzyć model danych proste i wygenerować bazę danych z niego.
W **Eksploratora rozwiązań**, kliknij prawym przyciskiem myszy *DAL* i wybierz polecenie **Dodaj nowy element**. W **Dodaj nowy element** dialogowego **zainstalowane szablony** wybierz **danych** , a następnie wybierz **ADO.NET Entity Data Model** szablonu . Nadaj nowemu plikowi *AlumniAssociationModel.edmx* i kliknij przycisk **Dodaj**.
[](what-s-new-in-the-entity-framework-4/_static/image9.png)
Spowoduje to uruchomienie Kreatora modelu danych jednostki. W **wybierz zawartość modelu** kroku, wybierz pozycję **pusty Model** a następnie kliknij przycisk **Zakończ**.
[](what-s-new-in-the-entity-framework-4/_static/image11.png)
**Projektancie Entity Data Model** zostanie otwarty przy użyciu powierzchni projektowej puste. Przeciągnij **jednostki** elementu z **przybornika** na powierzchnię projektu.
[](what-s-new-in-the-entity-framework-4/_static/image13.png)
Zmień nazwę jednostki z `Entity1` do `Alumnus`, zmień `Id` nazwę właściwości, aby `AlumnusId`i Dodaj nową właściwość skalarna, o nazwie `Name`. Aby dodać nowe właściwości naciśnięciu klawisza Enter po zmianie nazwy `Id` kolumn, lub kliknij prawym przyciskiem myszy jednostkę i wybierz pozycję **Dodaj właściwość skalarną**. Domyślnym typem dla nowej właściwości jest `String`, co jest dobrym rozwiązaniem w tej prezentacji prostego, ale oczywiście zmienisz elementów, takich jak typ danych w **właściwości** okna.
Utwórz inną jednostkę w taki sam sposób i nadaj mu `Donation`. Zmiana `Id` właściwości `DonationId` i Dodaj właściwość skalarną o nazwie `DateAndAmount`.
[](what-s-new-in-the-entity-framework-4/_static/image15.png)
Dodaj skojarzenie między tymi dwoma jednostkami, kliknij prawym przyciskiem myszy `Alumnus` jednostki, wybierz opcję **Dodaj**, a następnie wybierz pozycję **skojarzenie**.
[](what-s-new-in-the-entity-framework-4/_static/image17.png)
Domyślne wartości w **Dodawanie skojarzenia** to okno dialogowe, co ma (jeden do wielu, zawierają właściwości nawigacji, obejmują klucze obce), więc wystarczy kliknąć **OK**.
[](what-s-new-in-the-entity-framework-4/_static/image19.png)
Projektant dodaje linia skojarzenia i właściwości klucza obcego.
[](what-s-new-in-the-entity-framework-4/_static/image21.png)
Teraz możesz przystąpić do tworzenia bazy danych. Kliknij prawym przyciskiem myszy projekt powierzchni i wybierz **Generuj z bazy danych z modelu**.
[](what-s-new-in-the-entity-framework-4/_static/image23.png)
Spowoduje to uruchomienie Kreatora generowanie bazy danych. (Jeśli wyświetlane są ostrzeżenia, które wskazują, że jednostki nie są mapowane, możesz zignorować te, które w chwili obecnej.)
W **wybierz połączenie danych** kroku, kliknij przycisk **nowe połączenie**.
[](what-s-new-in-the-entity-framework-4/_static/image25.png)
W **właściwości połączenia** okna dialogowego Wybierz lokalne wystąpienie programu SQL Server Express, a nazwa bazy danych `AlumniAsssociation`.
[](what-s-new-in-the-entity-framework-4/_static/image27.png)
Kliknij przycisk **tak** kiedy pojawi się prośba Jeśli chcesz utworzyć bazę danych. Gdy **wybierz połączenie danych** kroku zostanie ponownie wyświetlony, kliknij przycisk **dalej**.
W **Podsumowanie i ustawienia** kroku, kliknij przycisk **Zakończ**.
[](what-s-new-in-the-entity-framework-4/_static/image29.png)
A *.sql* zostanie utworzony plik za pomocą poleceń (DDL) języka definicji danych, ale polecenia nie zostało jeszcze uruchomione.
[](what-s-new-in-the-entity-framework-4/_static/image31.png)
Użyj narzędzia takiego jak **SQL Server Management Studio** do uruchamiania skryptu i tworzenia tabel, ponieważ może zrobisz podczas tworzenia `School` bazy danych dla [pierwszym samouczku tej serii samouczka Wprowadzenie ](../getting-started-with-ef/the-entity-framework-and-aspnet-getting-started-part-1.md). (Jeśli nie można pobrać bazy danych.)
Teraz możesz używać `AlumniAssociation` modelu danych w sieci web pages taki sam sposób, jak korzystasz `School` modelu. Aby wypróbować tę możliwość, Dodaj dane do tabel i utworzyć stronę sieci web, który wyświetla dane.
Za pomocą **Eksploratora serwera**, Dodaj następujące wiersze do `Alumnus` i `Donation` tabel.
[](what-s-new-in-the-entity-framework-4/_static/image33.png)
Utwórz nową stronę sieci web o nazwie *Alumni.aspx* , który używa *Site.Master* strony wzorcowej. Dodaj następujący kod do `Content` formantu o nazwie `Content2`:
[!code-aspx[Main](what-s-new-in-the-entity-framework-4/samples/sample7.aspx)]
Ten kod znaczników tworzy zagnieżdżonych `GridView` kontrolki zewnętrznej jeden do wyświetlania nazw absolwentów i wewnętrznego katalog w celu wyświetlania darowizn dat i kwot.
Otwórz *Alumni.aspx.cs*. Dodaj `using` poufności danych dostęp do warstwy i obsługa zewnętrzny `GridView` kontrolki `RowDataBound` zdarzeń:
[!code-csharp[Main](what-s-new-in-the-entity-framework-4/samples/sample8.cs)]
Ten kod databinds wewnętrzny `GridView` sterować za pomocą `Donations` właściwość nawigacji bieżącego wiersza `Alumnus` jednostki.
Uruchom stronę.
[](what-s-new-in-the-entity-framework-4/_static/image35.png)
(Uwaga: na tej stronie znajduje się w projekcie do pobrania, ale aby umożliwić jej pracę, użytkownik musi utworzyć bazę danych w lokalnym wystąpieniu programu SQL Server Express; baza danych nie jest uwzględniona jako *.mdf* w pliku *aplikacji\_ Dane* folderu.)
Aby uzyskać więcej informacji o korzystaniu z funkcji modelu Entity Framework, zobacz [pierwszego modelu w programie Entity Framework 4](https://msdn.microsoft.com/data/ff830362.aspx).
## <a name="poco-support"></a>Obsługa obiektów POCO
Gdy używasz metodologię projektowania opartego na domenie, projektowania klas danych, które reprezentują dane i zachowania, która jest odpowiednia dla domeny biznesowej. Te klasy powinny być niezależne od wszelkich określonych technologii używany do przechowywania (utrwalanie) danych; innymi słowy powinny one być *trwałości zakresu*. Nieznajomości trwałości może również ułatwić klasy testu jednostkowego ponieważ projekt testów jednostkowych mogą używać niezależnie od technologii trwałości jest najwygodniejszym do testowania. Ograniczona obsługa nieznajomości trwałości jest oferowana w starszych wersjach programu Entity Framework, ponieważ musiały dziedziczyć z klas jednostek `EntityObject` klasy, a zatem się dużym stopniem Entity Framework funkcje.
Entity Framework 4 wprowadza możliwość używania klas jednostek, które nie dziedziczą `EntityObject` klasy, dlatego trwałości zakresu. W kontekście programu Entity Framework klasy takie są zwykle nazywane *obiektów CLR stary zwykły* (POCO lub POCOs). Można napisać klasy POCO ręcznie lub może automatycznie generować je na podstawie istniejącego modelu danych przy użyciu szablonów Toolkit przekształcania szablonu tekstu (T4) dostarczane przez program Entity Framework.
Aby uzyskać więcej informacji o używaniu POCOs platformy Entity Framework Zobacz następujące zasoby:
- [Praca z jednostkami POCO](https://msdn.microsoft.com/library/dd456853.aspx). To jest dokument MSDN, który zawiera omówienie POCOs, wraz z łączami do innych dokumentów, które zawierają bardziej szczegółowe informacje.
- [Wskazówki: Obiektów POCO szablonu programu Entity Framework](https://blogs.msdn.com/b/adonet/archive/2010/01/25/walkthrough-poco-template-for-the-entity-framework.aspx) to wpis w blogu od zespołu deweloperów platformy Entity Framework i zawiera łącza do innych wpisów w blogu o POCOs.
## <a name="code-first-development"></a>Najpierw kod tworzenia
Obsługa POCO w programie Entity Framework 4 nadal wymaga Tworzenie modelu danych, a następnie połączyć z klasami jednostki do modelu danych. Nowa wersja programu Entity Framework będzie zawierać funkcję o nazwie *najpierw kod rozwoju*. Ta funkcja umożliwia za pomocą programu Entity Framework własnych klas POCO bez konieczności używania Projektant modelu danych lub plik XML modelu danych. (W związku z tym, ta opcja również została wywołana *tylko kod*; *najpierw kod* i *tylko kod* odnoszą się do tej samej funkcji programu Entity Framework.)
Aby uzyskać więcej informacji o korzystaniu z podejścia najpierw kod do rozwoju, zobacz następujące zasoby:
- [Tworzenie aplikacji przy użyciu platformy Entity Framework 4 najpierw kod](https://weblogs.asp.net/scottgu/archive/2010/07/16/code-first-development-with-entity-framework-4.aspx). To jest wpis na blogu autorstwa Scotta Guthriego wprowadzenie do programowania najpierw kod.
- [Blog zespołu Entity Framework projektowania - publikuje oznakowane CodeOnly](https://blogs.msdn.com/b/efdesign/archive/tags/codeonly/)
- [Entity Framework rozwoju zespołu - przeczytać wpisy na blogu oznakowane Code First](https://blogs.msdn.com/b/efdesign/archive/tags/code+first/)
- [Samouczek platformy MVC Music Store — część 4: modele i dostęp do danych](../../../../mvc/overview/older-versions/mvc-music-store/mvc-music-store-part-4.md)
- [Wprowadzenie do MVC 3 — część 4: Entity Framework najpierw kod tworzenia](../../../../mvc/overview/older-versions/getting-started-with-aspnet-mvc3/cs/adding-a-model.md)
Ponadto nowe samouczek MVC najpierw kod, który tworzy aplikację, podobnie jak w aplikacji Contoso University jest rzutowany do opublikowania wiosną 2011 w [https://asp.net/entity-framework/tutorials](../../../../entity-framework.md)
## <a name="more-information"></a>Więcej informacji
Na tym kończy się przegląd, aby what's new in Entity Framework i ten proces jest kontynuowany z tej serii samouczka platformy Entity Framework. Aby uzyskać więcej informacji o nowych funkcjach w programie Entity Framework 4, które nie są omówione w tym miejscu zobacz następujące zasoby:
- [What's New in ADO.NET](https://msdn.microsoft.com/library/ex6y04yf.aspx) temacie w witrynie MSDN na temat nowych funkcji w wersji 4 programu Entity Framework.
- [Ogłoszenie wydania Entity Framework 4](https://blogs.msdn.com/b/efdesign/archive/2010/04/12/announcing-the-release-of-entity-framework-4.aspx) wpis w blogu zespołu programistycznego platformy Entity Framework nowe funkcje w wersji 4.
> [!div class="step-by-step"]
> [Poprzednie](maximizing-performance-with-the-entity-framework-in-an-asp-net-web-application.md)
| 93.873832 | 806 | 0.804072 | pol_Latn | 0.999282 |
24b672547d068bd2c0be3987044e695dcc30e489 | 2,364 | md | Markdown | README.md | tsuyoshicho/action-vimlint | 2c76678bc9c1cf90dc1f2556314e70a885b576b7 | [
"MIT"
] | null | null | null | README.md | tsuyoshicho/action-vimlint | 2c76678bc9c1cf90dc1f2556314e70a885b576b7 | [
"MIT"
] | 34 | 2019-11-14T07:58:31.000Z | 2022-03-07T02:00:15.000Z | README.md | tsuyoshicho/action-vimlint | 2c76678bc9c1cf90dc1f2556314e70a885b576b7 | [
"MIT"
] | null | null | null | # GitHub Action: Run vimlint with reviewdog
[](https://github.com/tsuyoshicho/action-vimlint/actions)
[](https://github.com/tsuyoshicho/action-vimlint/releases)
This action runs [vim-vimlint](https://github.com/syngan/vim-vimlint) with
[reviewdog](https://github.com/reviewdog/reviewdog) on pull requests to improve
code review experience.
based on [reviewdog/action-vint](https://github.com/reviewdog/action-vint)
[](https://github.com/tsuyoshicho/action-vimlint/pull/1)
[](https://github.com/tsuyoshicho/action-vimlint/pull/1)
## Inputs
### `github_token`
**Required**. Default is `${{ github.token }}`.
### `level`
Optional. Report level for reviewdog [info,warning,error].
It's same as `-level` flag of reviewdog.
### `reporter`
Reporter of reviewdog command [github-pr-check,github-check,github-pr-review].
Default is github-pr-review.
It's same as `-reporter` flag of reviewdog.
github-pr-review can use Markdown and add a link to rule page in reviewdog reports.
### `filter_mode`
Optional. Filtering mode for the reviewdog command [added,diff_context,file,nofilter].
Default is added.
### `fail_on_error`
Optional. Exit code for reviewdog when errors are found [true,false]
Default is `false`.
### `reviewdog_flags`
Optional. Additional reviewdog flags
### `target`
Check target files and/or directories.
If multi item list, use space separation.
Default is autoload.
### `vimlint_flags`
vimlint arguments (Default: `-e EVL102.l:_=1 -c func_abort=1`)
## Example usage
### [.github/workflows/reviewdog.yml](.github/workflows/reviewdog.yml)
```yml
name: reviewdog
on: [pull_request]
jobs:
vimlint:
name: runner / vimlint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: vimlint
uses: tsuyoshicho/action-vimlint@v1
with:
github_token: ${{ secrets.github_token }}
reporter: github-pr-review # Change reporter.
```
| 30.307692 | 182 | 0.739002 | eng_Latn | 0.226279 |
24b6fa722fc77458b6076cf5aa2ae49c532c72ba | 87 | md | Markdown | README.md | dumb-stuff/roblox-api-wrapper | cc86de7f9327bafa3092d981ed56b9bc6495dda6 | [
"MIT"
] | null | null | null | README.md | dumb-stuff/roblox-api-wrapper | cc86de7f9327bafa3092d981ed56b9bc6495dda6 | [
"MIT"
] | null | null | null | README.md | dumb-stuff/roblox-api-wrapper | cc86de7f9327bafa3092d981ed56b9bc6495dda6 | [
"MIT"
] | null | null | null | # roblox-api-wrapper
Roblox API Wrapper for python.
Not even done.
Maybe abandoned
| 17.4 | 32 | 0.758621 | eng_Latn | 0.845752 |
24b737c0cc8c5b10070faec87c801bb1b6c655b9 | 1,683 | md | Markdown | maskfile.md | rnons/tauri | 7e7b43cef31bc226d76874d24cfd000553e00f89 | [
"MIT"
] | 1 | 2020-04-25T02:26:23.000Z | 2020-04-25T02:26:23.000Z | maskfile.md | rnons/tauri | 7e7b43cef31bc226d76874d24cfd000553e00f89 | [
"MIT"
] | null | null | null | maskfile.md | rnons/tauri | 7e7b43cef31bc226d76874d24cfd000553e00f89 | [
"MIT"
] | null | null | null | # Shorthand Commands
## prepare
> Setup all stuffs needed for runing the examples
```sh
git clone --recursive [email protected]:tauri-apps/examples.git \
|| (cd examples && git pull origin master; cd ..) # always prepare up-to-date examples in case it's already available
export TAURI_DIST_DIR=$PWD/tauri/test/fixture/dist
export TAURI_DIR=$PWD/tauri/test/fixture/src-tauri
cargo build
cargo install --path cli/tauri-bundler --force
cargo install cargo-web # used by example rust/yew
cd cli/tauri.js
yarn && yarn build
```
## run
### run example (example)
> Run specific example in dev mode
```sh
source .scripts/init_env.sh
shopt -s globstar
cd examples/**/$example 2>/dev/null \
|| cd examples/**/$example/$example # workaround for rust/yew/todomvc/todomvc
case "$PWD" in
*/node/*)
yarn && yarn tauri:source dev
;;
*/rust/*)
cargo web deploy
[ $example = `basename $(dirname $PWD)` ] && cd ..
yarn add tauri@link:../../../cli/tauri.js
yarn && yarn tauri dev
;;
*)
echo unknown project $(dirname $example)/$example
;;
esac
```
## list
### list examples
> List all available examples
```sh
find examples/*/*/* -maxdepth 0 -type d -not -path '*.git*' \
-exec sh -c 'echo $(basename $(dirname {}))/$(basename {})' \;
```
## clean
> Remove installed dependencies and reset examples in case something gone wrong
```sh
cargo uninstall tauri-bundler
cargo clean
shopt -s globstar
rm -r **/node_modules
cd examples
git checkout -- . # discard all unstaged changes
git clean -dfX # remove all untracked files & directories
```
| 22.144737 | 126 | 0.698752 | eng_Latn | 0.871082 |
24b758fa733b84926b3ce2ffd65da5ad6cf49fbf | 221 | md | Markdown | docs/mobe1969/12-rounds-3-lockdown.md | bmiller/beqcatalogue | 86e79be46f1c710207b16cecc9c987627a46d618 | [
"MIT"
] | null | null | null | docs/mobe1969/12-rounds-3-lockdown.md | bmiller/beqcatalogue | 86e79be46f1c710207b16cecc9c987627a46d618 | [
"MIT"
] | null | null | null | docs/mobe1969/12-rounds-3-lockdown.md | bmiller/beqcatalogue | 86e79be46f1c710207b16cecc9c987627a46d618 | [
"MIT"
] | null | null | null | # 12 Rounds 3 Lockdown
* Author: mobe1969
* Production Year: 2015
## DTS-HD MA 5.1
| 22.1 | 133 | 0.723982 | yue_Hant | 0.15958 |
24b779d2492f14ff63edc9bd8bbd9f33cfa94b42 | 411 | md | Markdown | README.md | maxerium/scoop-minorgod | 4c4db8a9e366f11dde37511c25472da8b0961496 | [
"MIT"
] | 1 | 2021-12-02T04:35:35.000Z | 2021-12-02T04:35:35.000Z | README.md | maxerium/scoop-minorgod | 4c4db8a9e366f11dde37511c25472da8b0961496 | [
"MIT"
] | 4 | 2019-10-28T08:31:32.000Z | 2021-09-22T01:39:12.000Z | README.md | maxerium/scoop-minorgod | 4c4db8a9e366f11dde37511c25472da8b0961496 | [
"MIT"
] | 1 | 2020-10-08T20:30:11.000Z | 2020-10-08T20:30:11.000Z | # scoop-minorgod [](https://ci.appveyor.com/project/minorgod/scoop-minorgod)
The "minorgod" bucket for [Scoop](http://scoop.sh), for some random apps I wanted to manage through scoop.
To make it easy to install apps from this bucket, run
`scoop bucket add minorgod https://github.com/minorgod/scoop-minorgod.git`
| 58.714286 | 163 | 0.754258 | eng_Latn | 0.618664 |
24b98348e302f6afa62dec1d6cc0503e78673c2f | 4,201 | md | Markdown | content/post/2020-10-31-tested20/index.md | xdevroey/academic-kickstart | f01d22ac70f0a3dcbdb66603d1e1f8431aa2b27f | [
"MIT"
] | null | null | null | content/post/2020-10-31-tested20/index.md | xdevroey/academic-kickstart | f01d22ac70f0a3dcbdb66603d1e1f8431aa2b27f | [
"MIT"
] | null | null | null | content/post/2020-10-31-tested20/index.md | xdevroey/academic-kickstart | f01d22ac70f0a3dcbdb66603d1e1f8431aa2b27f | [
"MIT"
] | 1 | 2020-10-04T15:29:06.000Z | 2020-10-04T15:29:06.000Z | ---
# Documentation: https://sourcethemes.com/academic/docs/managing-content/
title: "TestEd 2020"
subtitle: "1st International Software Testing Education Workshop"
summary: ""
authors: [admin]
tags: ["Software Testing", "Teaching"]
categories: [Tips]
date: 2020-10-31T13:52:11+01:00
lastmod: 2020-10-31T13:52:11+01:00
featured: false
draft: false
# Featured image
# To use, add an image named `featured.jpg/png` to your page's folder.
# Focal points: Smart, Center, TopLeft, Top, TopRight, Left, Right, BottomLeft, Bottom, BottomRight.
image:
caption: "Source: https://twitter.com/JeffOffutt/status/1322569329561477121"
focal_point: ""
preview_only: false
# Projects (optional).
# Associate this post with one or more of your projects.
# Simply enter your project's folder or file name without extension.
# E.g. `projects = ["internal-project"]` references `content/project/deep-learning/index.md`.
# Otherwise, set `projects = []`.
projects: []
---
Last Wednesday (28/10/2020), I attended the first edition of the [Software Testing Education Workshop](https://testedworkshop.github.io), co-located with [ICST 2020](https://icst2020.info). The workshop was initially supposed to be held in Porto. Unfortunately, with the COVID-19 pandemic and the travel restrictions, ICST and all the workshops had to be held over Zoom. Nevertheless, the workshop was a great success! During four hours, we discussed how to enhance software testing education at various levels and in multiple contexts. In addition to the insights gained from the presentations and discussions, I collected a list of pointers to educational resources:
- [Code Defenders](https://code-defenders.org/), an online game to teach mutation testing. In Code Defenders, a team of attackers creates mutants while a team of defenders writes test cases to expose those mutants. Code Defenders is [open source](https://github.com/CodeDefenders/CodeDefenders) and can be deployed on a local server.
- The [Science of Software - Computing Education Research group webpage](https://sos-cer.github.io) lists projects and tools developed by the group to enhance computing education. In particular, the [Canary Framework](https://sos-cer.github.io/projects/auto-grading) relies on Jenkins to automate the grading of programming exercises.
- A [list of resources](http://www.cs.virginia.edu/~up3f/resources/index.php) for various software engineering teaching activities. Including an [activity to introduce testing in agile methods](https://uva.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=32a85eb0-d315-4e6a-af8b-abbe00706b3d), similar to another [educational game for teaching SCRUM in computing courses](https://doi.org/10.1016/j.jss.2013.05.030).
- A [list of open source testing tools for Java](https://java-source.net/open-source/testing-tools). The [website](https://java-source.net) also lists other open-source software in Java.
- A [curated list of open source projects](http://foss2serve.org/index.php/HFOSS_Projects) to use in assignments. Many software engineering courses rely on open source projects for various kinds of assignments. For instance, the [Software Architecture course](https://se.ewi.tudelft.nl/delftswa/) of TU Delft is organized around a list of blog posts writing assignments posts about the various architectural aspects of an open-source project.
- The [impress project](https://impress-project.eu/), seeking to improve students' engagement in software engineering courses through gamification. Additionally to [Code Defender](https://impress-project.eu/codedefenders/), the results of the project also include [FormalZ](https://impress-project.eu/formalz/), an educational game to teach formal methods, and a [quizz repository](https://impress-project.eu/quiz-repository/), a set of quizzes on software engineering that can be used in [Kahoot!](https://create.kahoot.it/auth/login?next=/search%3Fcreator%3Dimpressproject).
- Last but not least, a full [Algorithms and Data Structures course](https://github.com/arcuri82/algorithms) with slides and exercises for students. The course includes an introduction to unit testing with exercises for students to write unit tests.
| 91.326087 | 669 | 0.778862 | eng_Latn | 0.968643 |
24ba2eb389eec52171455fb56458576c815f5b05 | 1,804 | md | Markdown | README.md | slartibaartfast/go-redis-compose | 01fbcf6da3beaa52e7611fb562e52341b13f944b | [
"MIT"
] | 3 | 2020-09-20T23:06:31.000Z | 2022-02-17T20:06:03.000Z | README.md | slartibaartfast/go-redis-compose | 01fbcf6da3beaa52e7611fb562e52341b13f944b | [
"MIT"
] | null | null | null | README.md | slartibaartfast/go-redis-compose | 01fbcf6da3beaa52e7611fb562e52341b13f944b | [
"MIT"
] | 2 | 2021-02-21T02:42:09.000Z | 2021-07-06T17:16:31.000Z | # go-redis-compose
Docker compose for Redis and Golang
This is a practice Go project that receives xml from an external api and transforms it to JSON. Data is stored in Redis. Redis lives in one container, and the Go api lives in another.
The containers are based on Alpine Linux 3.6. The container for the api has a few extra packages added to it, namely:
- github.com/julienschmidt/httprouter
- github.com/garyburd/redigo/redis
These projects are also in the /vendor subdirectory, govendor style.
===========
## Running locally
Build and run using Swarm and Compose:
If you don't already have one, get a key for the venerable cat api from
[http://thecatapi.com/api-key-registration.html](http://thecatapi.com/api-key-registration.html)
Create a file, go-redis-compose/api-key.env, and save your cat api key in it. This gets used later as a Docker Secrets file. While it is a little silly to treat a public api key as a secret, it seems like a safe value to use when first integrating secrets into a project.
Open docker-compose.yml and edit the api Volumes so that your absolute path gets mapped.
>Volumes:
>
> \- </your/absolute/path/>/go-redis-compose: /code/go/src/go-redis-compose
Start a swarm engine:
`$ docker swarm init`
Deploy the stack with the name cats:
`$ docker stack deploy --compose-file=docker-compose.yml cats`
To see the status of service creation, run:
`$ docker service ls`
Once pulls are done and everything is built, check [http://0.0.0.0:8080/cat](http://0.0.0.0:8080/cat) to view a json string related to an image of a cat, retrieved from thecatapi.com
Check [http://0.0.0.0:8080/history](http://0.0.0.0:8080/history) to view the cumulative set of calls made to /cat during the session.
To bring the stack down:
`$ docker stack rm cats`
| 33.407407 | 273 | 0.743348 | eng_Latn | 0.980556 |
24ba2fefe01118d324b8a53ae9dc5ef0b4f5df9c | 306 | md | Markdown | python-app/README.md | maguowei/Dockerfiles | 0c3e18536a91e09fe80b957b25bb165fc2c81c30 | [
"MIT"
] | 8 | 2020-07-22T16:42:26.000Z | 2022-01-08T22:09:16.000Z | python-app/README.md | maguowei/Dockerfiles | 0c3e18536a91e09fe80b957b25bb165fc2c81c30 | [
"MIT"
] | 1 | 2020-03-13T04:11:18.000Z | 2020-06-09T13:45:12.000Z | python-app/README.md | maguowei/Dockerfiles | 0c3e18536a91e09fe80b957b25bb165fc2c81c30 | [
"MIT"
] | null | null | null | # Python App Base Image
## Usage
```Dockerfile
FROM maguowei/python-app:onbuild
LABEL maintainer="[email protected]"
LABEL name="maguowei/example"
ENV APP_NAME example
ENV APP_ENV dev
USER app
VOLUME /var/lib/${APP_NAME}/data
EXPOSE 8000
CMD ["python", "manage.py", "runserver", "0.0.0.0:8000"]
```
| 16.105263 | 56 | 0.728758 | kor_Hang | 0.351702 |
24ba84ffc5dde4e248938535aa82c17c2749a25b | 77 | md | Markdown | README.md | jclement/gbp4 | 3f50da23f646333ee78eb0dc4e4a68848051c162 | [
"MIT"
] | null | null | null | README.md | jclement/gbp4 | 3f50da23f646333ee78eb0dc4e4a68848051c162 | [
"MIT"
] | null | null | null | README.md | jclement/gbp4 | 3f50da23f646333ee78eb0dc4e4a68848051c162 | [
"MIT"
] | null | null | null | # GarageBerryPi 4
Software for GarageBerryPi - Garage Controller Software
| 12.833333 | 55 | 0.805195 | eng_Latn | 0.235621 |
24bb17502096c2e2605574e0c49deff0602b1595 | 2,756 | md | Markdown | README.md | guilhermesteves/brdoc | 943398953dd7c5677efd8b4dccada75e545561c1 | [
"Unlicense"
] | 1 | 2021-06-03T00:25:44.000Z | 2021-06-03T00:25:44.000Z | README.md | guilhermesteves/brdoc | 943398953dd7c5677efd8b4dccada75e545561c1 | [
"Unlicense"
] | null | null | null | README.md | guilhermesteves/brdoc | 943398953dd7c5677efd8b4dccada75e545561c1 | [
"Unlicense"
] | null | null | null | # BR Doc
[![Build Status][tag1img]][tag1link]
[![GoDoc][tag2img]][tag2link]
[![Go Report Card][tag3img]][tag3link]
[![codecov][tag4img]][tag4link]
CPF, CNPJ, CEP and license plate validator for Go!
Everything in this file, but the [License](#license) section, is in brazilian portuguese.
This package is also available in gopkg.in as [Nhanderu/brdoc.v2][1].
## Descrição
BR Doc é um pacote para validação, tanto do formato quanto dos dígitos, de documentos
brasileiros, como CPF, CNPJ, CEP, placa veicular e (futuramente) RG.
## Uso
Principais funções:
- `func IsCPF(doc string) bool`
- `func IsCNPJ(doc string) bool`
- `func IsCEP(doc string, ufs ...FederativeUnit) bool`
- `func IsPlate(doc string) bool`
- `func IsNationalPlate(doc string) bool`
- `func IsMercosulPlate(doc string) bool`
Exemplo de valores válidos e inválidos:
```go
// Inválidos por causa da inconsistência do dígito:
brdoc.IsCPF("248.438.034-99") //=> false
brdoc.IsCNPJ("26.637.142/0001-00") //=> false
// Inválidos por causa do formato:
brdoc.IsCPF("248 438 034 80") //=> false
brdoc.IsCNPJ("26637142-0001.58") //=> false
brdoc.IsCEP("01 001.001") //=> false
brdoc.IsPlate("A B C 0 0 0 0") //=> false
// Inválidos por causa da UF:
brdoc.IsCEP("01001-001", brdoc.RJ) //=> false
// Válidos:
brdoc.IsCPF("248.438.034-80") //=> true
brdoc.IsCPF("24843803480") //=> true
brdoc.IsCNPJ("26.637.142/0001-58") //=> true
brdoc.IsCNPJ("26637142000158") //=> true
brdoc.IsCEP("01001-001", brdoc.SP) //=> true
brdoc.IsCEP("01001001", brdoc.SP) //=> true
brdoc.IsPlate("AAA-0000") //=> true
brdoc.IsNationalPlate("ABC1234") //=> true
brdoc.IsMercosulPlate("ABC1D23") //=> true
```
## To-do list
- [x] validação de CPF
- [x] validação de CNPJ
- [x] validação de CEP
- [x] validação de placa veicular
- [ ] validação de RG
Validação de RG não foi implementado porque cada estado tem as suas regras
e eu não estou com vontade de terminar isso. :zzz:
## License
This project code is in the public domain. See the [LICENSE file][4].
[1]: https://gopkg.in/Nhanderu/brdoc.v2
[2]: https://github.com/asaskevich/govalidator
[3]: https://github.com/Nhanderu/brdoc-govalidator
[4]: https://github.com/Nhanderu/brdoc/blob/master/LICENSE
[tag1img]: https://travis-ci.org/Nhanderu/brdoc.svg?branch=master
[tag1link]: https://travis-ci.org/Nhanderu/brdoc
[tag2img]: https://godoc.org/github.com/Nhanderu/brdoc?status.png
[tag2link]: https://godoc.org/github.com/Nhanderu/brdoc
[tag3img]: https://goreportcard.com/badge/github.com/Nhanderu/brdoc
[tag3link]: https://goreportcard.com/report/github.com/Nhanderu/brdoc
[tag4img]: https://codecov.io/gh/Nhanderu/brdoc/branch/master/graph/badge.svg
[tag4link]: https://codecov.io/gh/Nhanderu/brdoc
| 32.046512 | 89 | 0.705007 | por_Latn | 0.424138 |
24bc298c5f014764b614dfd76184ef5f1a30e358 | 1,088 | md | Markdown | CHANGELOG.md | alexlili/components_lib_demo | 9d977ea8a0f2e14d1bb09c84e3a3fd607a57462e | [
"MIT"
] | null | null | null | CHANGELOG.md | alexlili/components_lib_demo | 9d977ea8a0f2e14d1bb09c84e3a3fd607a57462e | [
"MIT"
] | null | null | null | CHANGELOG.md | alexlili/components_lib_demo | 9d977ea8a0f2e14d1bb09c84e3a3fd607a57462e | [
"MIT"
] | null | null | null | # Changelog
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
### [1.0.15](https://github.com/alexlili/components_lib_demo/compare/v1.0.14...v1.0.15) (2022-01-17)
### [1.0.14](https://github.com/alexlili/components_lib_demo/compare/v1.0.13...v1.0.14) (2022-01-17)
### [1.0.13](https://github.com/alexlili/components_lib_demo/compare/v1.0.12...v1.0.13) (2022-01-17)
### 1.0.12 (2022-01-17)
### [1.0.11](///compare/v1.0.10...v1.0.11) (2022-01-14)
### [1.0.10](///compare/v1.0.9...v1.0.10) (2022-01-14)
### [1.0.9](///compare/v1.0.8...v1.0.9) (2022-01-14)
### [1.0.8](///compare/v1.0.7...v1.0.8) (2022-01-14)
### [1.0.7](///compare/v1.0.6...v1.0.7) (2022-01-14)
### [1.0.6](///compare/v1.0.5...v1.0.6) (2022-01-14)
### [1.0.5](///compare/v1.0.4...v1.0.5) (2022-01-14)
### [1.0.4](///compare/v1.0.3...v1.0.4) (2022-01-13)
### [1.0.3](///compare/v1.0.2...v1.0.3) (2022-01-12)
### [1.0.2](///compare/v1.0.1...v1.0.2) (2022-01-12)
### 1.0.1 (2022-01-12)
| 32 | 174 | 0.597426 | yue_Hant | 0.075797 |
24bc686456a24ad2f7ddfb5cb32854c3ef7315b8 | 477 | md | Markdown | HTM/ProgrGuide/Functions/AsModalBrowser/Left.md | LianaKh/as4x-docs | 08a6b99daf956442c3cf534596767568982462b2 | [
"MIT"
] | null | null | null | HTM/ProgrGuide/Functions/AsModalBrowser/Left.md | LianaKh/as4x-docs | 08a6b99daf956442c3cf534596767568982462b2 | [
"MIT"
] | 14 | 2019-05-30T10:47:31.000Z | 2022-03-29T14:11:37.000Z | HTM/ProgrGuide/Functions/AsModalBrowser/Left.md | LianaKh/as4x-docs | 08a6b99daf956442c3cf534596767568982462b2 | [
"MIT"
] | 13 | 2019-05-30T07:27:22.000Z | 2022-03-29T13:59:56.000Z | ---
layout: page
title: "AsModalBrowser/Left"
---
# Leftհատկություն
[См. также](StartUpAtCentre.md) Օրինակ [Применяется к](../AsModalBrowser.md)
Վերադարձնում կամ նշանակում է ցուցակի մոդալ ցուցադրիչի ձախ եզրի հեռավորությունը ծրագրի պատուհանի ձախ եզրից։
## Շարահյուսություն
``` vb
object.Left = [nLeftValue]
```
Բաղադրիչներն են՝
| Պարամետր | Նկարագրություն |
|--|--|
| object | Ցուցակի մոդալ ցուցադրիչի հղում։ |
| nLeftValue | Նոր հեռավորություն։ |
## Տվյալի տիպ
Single | 17.035714 | 106 | 0.727463 | hye_Armn | 0.983045 |
24be0e05353ff84077496522ad3c2fe026a4894f | 2,074 | md | Markdown | dynamic/README.md | aip9105/proj_study | e8bf923460dd530cd9150af0b85a0c84ada40c1a | [
"Apache-2.0"
] | null | null | null | dynamic/README.md | aip9105/proj_study | e8bf923460dd530cd9150af0b85a0c84ada40c1a | [
"Apache-2.0"
] | null | null | null | dynamic/README.md | aip9105/proj_study | e8bf923460dd530cd9150af0b85a0c84ada40c1a | [
"Apache-2.0"
] | null | null | null | # 动态定时任务
1.定时任务自动运行
2.动态定时任务使用方法
```
List<DynamicTask.Task> taskList = new ArrayList<>();
for (AddrDate addrDate : dateList) {
//针对缺考定时
DynamicTask.Task task = new DynamicTask.Task();
TaskService taskService = new TaskService();
taskService.setBeanName("autoMarkLackExamTaskImpl");
//开始考试时间 +30分钟 标记缺考 添加到定时任务
long timeStamp = addrDate.getExamDate().getTime()+addrDate.getBegTime().getTime()+8*3600*1000+30*60*1000;
String cron = CronUtils.getCronByDate(new Date(timeStamp));
task.setCron(cron);
task.setTaskId("lack_exam_"+addrDate.getDateId());
taskList.add(task);
String param = String.valueOf(addrDate.getDateId());
taskService.setParam(param);
task.setTaskService(taskService);
taskService.setTaskId(task.getTaskId());
taskService.setDynamicTask(dynamicTask);
//针对缺考定时
taskService.setBeanName("autoSubmitPaperTaskImpl");
timeStamp = addrDate.getExamDate().getTime()+addrDate.getEndTime().getTime()+8*3600*1000;
cron = CronUtils.getCronByDate(new Date(timeStamp));
task.setCron(cron);
task.setTaskId("submit_paper_"+addrDate.getDateId());
taskList.add(task);
taskService.setParam(param);
task.setTaskService(taskService);
taskService.setTaskId(task.getTaskId());
taskService.setDynamicTask(dynamicTask);
}
dynamicTask.addTasks(taskList);
```
```
//hellowworld定时打印
DynamicTask.Task task = new DynamicTask.Task();
TaskService taskService = new TaskService();
taskService.setBeanName("autoPrintHelloWorldImpl");
//当前时间1分钟后打印
long timeStamp = System.currentTimeMillis()+1*60*1000;
System.out.println(LocalDateTime.now());
String cron = CronUtils.getCronByDate(new Date(timeStamp));
task.setCron(cron);
task.setTaskId("print"+i);
taskList.add(task);
String param = String.valueOf(i);
taskService.setParam(param);
task.setTaskService(taskService);
taskService.setTaskId(task.getTaskId());
taskService.setDynamicTask(dynamicTask);
```
前端请求
```
POST localhost:8080/hello/openPrintHelloWorld
Content-Type: application/json
####
```
3.静态定时任务
```
SaticScheduleTask
``` | 29.211268 | 109 | 0.743009 | yue_Hant | 0.632879 |
24bf56ebdeabb4fec69abef47da8f6b6d81e3155 | 128 | md | Markdown | packages/form/README.md | domonda/domonda-js | b4d232893aea9bdd69c46e2c4898e05de552d4f6 | [
"0BSD"
] | 2 | 2020-11-16T07:24:32.000Z | 2020-11-20T12:25:20.000Z | packages/form/README.md | domonda/domonda-js | b4d232893aea9bdd69c46e2c4898e05de552d4f6 | [
"0BSD"
] | 33 | 2019-07-04T14:52:03.000Z | 2020-10-01T15:56:03.000Z | packages/form/README.md | domonda/domonda-js | b4d232893aea9bdd69c46e2c4898e05de552d4f6 | [
"0BSD"
] | 1 | 2019-11-02T17:05:43.000Z | 2019-11-02T17:05:43.000Z | # `domonda-form`
> TODO: description
## Usage
```
const domondaForm = require('domonda-form');
// TODO: DEMONSTRATE API
```
| 10.666667 | 44 | 0.648438 | kor_Hang | 0.39912 |
24bfcd8e52613be206eeee256fd3b00df789b048 | 544 | md | Markdown | Chapter05/README.md | dolgogae/GAN-projects | b323a6003be74fcee851edaa0b3cdeb3abea2ff6 | [
"MIT"
] | 190 | 2019-01-30T14:07:50.000Z | 2022-03-18T05:30:43.000Z | Chapter05/README.md | dolgogae/GAN-projects | b323a6003be74fcee851edaa0b3cdeb3abea2ff6 | [
"MIT"
] | 94 | 2019-03-16T21:31:12.000Z | 2022-03-11T23:39:36.000Z | Chapter05/README.md | dolgogae/GAN-projects | b323a6003be74fcee851edaa0b3cdeb3abea2ff6 | [
"MIT"
] | 126 | 2019-01-30T01:59:13.000Z | 2022-02-02T04:34:42.000Z | ## Using SRGANs to Generate Photo-Realistic Images
Keras implementation of "Photo-Realistic Single Image Super-Resolution Using a Generative Adversarial Network"
Python 3.6
Steps to set up the project:
1. Create a python3 virtual environment and activate it
2. Install dependencies using "pip install -r requirements.txt"
3. Create essential folders like 1. logs 2. results 3. data
4. Download 'img_align_celeba.zip' from "https://drive.google.com/drive/folders/0B7EVK8r0v71pTUZsaXdaSnZBZzg"
5. Train the model by executing "python3 run.py"
| 41.846154 | 110 | 0.801471 | eng_Latn | 0.784907 |
24c00d447b0ac53b9f5f2514eae42b0dd3cef43a | 97 | md | Markdown | games/README.md | LunaTechsDev/Luna-config | 390bea96b568697a31ca670fda5e6beaccb4c114 | [
"MIT"
] | 1 | 2021-09-06T23:06:10.000Z | 2021-09-06T23:06:10.000Z | games/README.md | LunaTechsDev/Luna-config | 390bea96b568697a31ca670fda5e6beaccb4c114 | [
"MIT"
] | 1 | 2020-09-14T02:33:04.000Z | 2020-09-14T02:33:04.000Z | games/README.md | LunaTechsDev/Luna-config | 390bea96b568697a31ca670fda5e6beaccb4c114 | [
"MIT"
] | 1 | 2020-09-30T01:52:26.000Z | 2020-09-30T01:52:26.000Z | # Game Folder
> This folder is for placing your RPGMaker MV/MZ projects in when creating plugins. | 48.5 | 83 | 0.793814 | eng_Latn | 0.999378 |
24c0b77d5979cd86ee1b887a3426f2c3b0aed650 | 8,470 | md | Markdown | _posts/2015-09-24-future-collect-result.md | jacoffee/allen.github.io | ec5683caa8f26088cd6b68b4554a79d0bd663010 | [
"MIT"
] | 1 | 2018-01-25T03:08:34.000Z | 2018-01-25T03:08:34.000Z | _posts/2015-09-24-future-collect-result.md | jacoffee/allen.github.io | ec5683caa8f26088cd6b68b4554a79d0bd663010 | [
"MIT"
] | null | null | null | _posts/2015-09-24-future-collect-result.md | jacoffee/allen.github.io | ec5683caa8f26088cd6b68b4554a79d0bd663010 | [
"MIT"
] | null | null | null | ---
layout: post
category: concurrency
date: 2015-09-24 09:51:22 UTC
title: 从Future产生到结果收集
tags: [异步计算，共享变量，链向根Promise，回调]
permalink: /concurrency/future/result-collect/
key: 488b299b8446fc87aa490a28629fcd61
description: "本文就Future的初始化以及结果收集的过程进行了研究"
keywords: [异步计算，共享变量，链向根Promise，回调]
---
Future在异步编程中使用非常广泛，Scala中的Actor就是建立在Future之上的，而Actor又在Akka和Spark中被广泛使用，重要性不言而喻。对于Future的语法和基本使用，网上已经有太多的资源了。本文想以源码为基础，就Future的结果收集进行剖析，不求多么深刻，但求能对结构收集的每一步有个大致的了解。
> A Future is a data structure used to retrieve the result of some concurrent operation. This result can be accessed synchronously (blocking) or asynchronously (non-blocking).
## Future的结果 - 非阻塞式 vs 阻塞式收集
```scala
val sumResult = Future((1L to 100000000L).sum)
```
非阻塞式的取值(onComplete | onSuccess | onFailure)
```scala
sumResult onComplete {
case Success(s) => println(" Future succeed " + sumResult)
case Failure(f) => println(" Future failed")
}
```
阻塞式的取值(Await.result)
```scala
Await.result(sumResult, Duration.Inf)
```
使用Future的初衷是为了不阻塞，所以尽量不要使用阻塞式取值，除非你不得不这么做。在项目开发中，一般通过**```For ... Yield```**将多个Future组合起来，最后调用Await.result获取最终的结果。
```scala
for {
A <- Future[A]
B <- Future[B]
C <- Future[C]
} yield {
op(A, B, C)
}
```
针对阻塞式的取值，以上面的代码为例就会阻塞主线程:
```scala
package scala
// STEP1
package concurrent {
object Await {
def result[T](awaitable: Awaitable[T], atMost: Duration): T =
blocking(awaitable.result(atMost)(AwaitPermission))
}
}
// STEP2
package object concurrent {
def blocking(body: => T) =
BlockContext.current.blockOn(body)(scala.concurrent.AwaitPermission)
}
// STEP3
package scala.concurrent
object BlockContext {
private val contextLocal = new ThreadLocal[BlockContext]()
def current = contextLocal.get {
case null => Thread.currentThread match {
case ctx: BlockContext => ctx
case _ => defaultBlockContext
}
case some => some
}
}
```
在最初阅读**current**方法时候会疑惑，为什么Thread.currentThread会匹配**BlockContext**类型，源码中的解释是: 有些线程池实现的时候会让Thread继承BlockContext。
对于非阻塞式的取值，我们可以通过Future的相关方法来判断它的当前状态。
```scala
sumResult.isCompleted
```
显然**onComplete**，**onSuccess**，**onFailure**这些回调也是根据当前Future的状态来执行相应的操作的。那么Future内部的状态有哪几种呢？这些状态之间又是如何切换的呢？
## 1.Future的状态以及改变
要研究Future的状态变化，最好的方式就是利用**onComplete**的调用栈并且打断点来摸清整个调用过程，下面通过代码调用来一步一步解释(由于之前没有接触过UML图，所以可能存在一些纰漏，以下涉及到UML图的地方仅供参考)。
### 1.1 Future的初始化 -- Future.apply
Future初始化的时候(实际上是DefaultPromise的初始化)，会调用**`AbstractPromise`**的updateState方法来设置初始状态。
```scala
class DefaultPromise[T] extends AbstractPromise { self =>
updateState(null, Nil) // 实际上更新的是AbstractPromise中的_ref属性
}
```
所以，**Future初始化之后状态变成了Nil(类型实际上是List[CallbackRunnable])**。
### 1.2 Future中的任务开始执行 -- PromiseCompletingRunnable
```scala
// executor ---> package scala.concurrent.impl.ExecutionContextImpl
def apply[T](body: => T)(implicit executor ExecutionContext):
scala.concurrent.Future[T] = {
/*
这里也体现了Promise的语义执行Runnable并且返回Future
每次启动一个异步计算的时候，PromiseCompletingRunnable都会被创建一次
body是懒加载的，所以在调用的时候才会被执行
*/
val runnable = new PromiseCompletingRunnable(body)
// 异步计算从这个地方开始然后调用PromiseCompletingRunnable的run方法
executor.prepare.execute(runnable)
// 返回Future，实际上是DefaultPromise实例，以便后续使用，比如说Compose
runnable.promise.future
}
}
```
而在**```PromiseCompletingRunnable```**执行的时候，会将**执行结果**封装在**```Try[T]```**中，所以onComplete的回调函数的参数也是**Try[T]**类型的。
```scala
class PromiseCompletingRunnable[T](body: => T) {
val promise = new Promise.DefaultPromise[T]()
override def run() = {
promise complete {
try {
Success(T)
} catch {
case NonFatal(e) => Failure(e)
}
}
}
}
```
#### 1.2.1 DefaultPromise.complete
```scala
// 如果该Promise已经完成则报错，否则就返回DefaultPromise的当前实例
def complete(result: Try[T]): this.type =
if (tryComplete(result)) this
else throw IllegalStateException("Promise already completed.")
```
#### 1.2.2 DefaultPromise.tryComplete
```scala
// tryComplete返回true则说明没有完成，返回false则说明完成
def tryComplete(result: Try[T]) = {
tryCompleteAndGetListeners(result) {
case null => false
case rs if rs.isEmpty => true
case rs => rs.foreach(r => r.executeWithValue(result)); true;
}
}
```
#### 1.2.3 DefaultPromise.tryCompleteAndGetListeners
```scala
@tailrec
private def tryCompleteAndGetListeners(v: Try[T]):
List[CallbackRunnable[T]] = {
getState match {
case raw: List[_] =>
val cur = raw.asInstanceOf[List[CallbackRunnable[T]]]
if (updateState(cur, v)) cur else tryCompleteAndGetListeners(v)
case _: DefaultPromise[_] =>
compressedRoot().tryCompleteAndGetListeners(v)
case _ => null
}
}
```
前面提到过，**DefaultPromise**的状态是由**AbstractPromise**的**_ref**属性维护的。状态有以下几种:
+ **List[CallbackRunnable[T]]**(最开始的状态是Nil)。
则接下来会将**DefaultPromise**的状态设置成**Try[T]**。在sumFuture的那种情况中，模式匹配会进到这种情况。然后**tryComplete**返回当前**DefaultPromise**实例并且它的状态已经变成了**Try[T]**
+ **DefaultPromise[_]**(一般是调用了map, flatMap生成了新的DefaultPromise)，这里涉及到链向根DefaultPromise的过程(会在后续的更新中补充)
+ 其它情况，则返回null
### 1.3 Future注册回调 -- Future.onComplete
Future的异步调用体现在当Future初始化之后，一个异步计算就已经开始；一般情况，我们会为Future注册相关的回调，要么是对正常的返回值进行处理，要么是对异常进行处理。同样以源码入手。
```scala
sumResult onComplete {
case Success(s) => println(" Future succeed " + sumResult)
case Failure(f) => println(" Future failed")
}
```
简化版的调用链如下:
#### 1.3.1 DefaultPromise.onComplete
```scala
def onComplete[U](func: Try[T] => U)
(implicit executor: ExecutionContext): Unit = {
...
val runnable = new CallbackRunnable(executor, func) // 1.1
dispatchOrAddCallback(runnable) // 1.2
}
```
#### 1.3.2 scala.concurrent.impl.CallbackRunnable
因为Java中Runnable的实现(run方法)默认是返回空的，所以此处基于Runnable再实现了一个，主要的目的是为了注入回调，让Future完成之后执行该回调。
```scala
class CallBackRunnable(
val executor: ExecutionContext, val onComplete: Try[T] => Any)
extends Runnable with OnCompleteRunnable {
var value: Try[T] = null
override def run() = {
// 与executeWithValue中require相结合，执行run的时候value必须不为null
require(value ne null)
try {
// case Success(s) => println(" Future succeed " + sumResult)
// case Failure(f) => println(" Future failed")
onComplete(value)
} catch {
case NoFatal(e) => ....
}
}
def executeWithValue(v: Try[T]) = {
// 确保回调函数没有被多次执行
require(value eq null)
value = v
try executor.execute(this)
catch {
case NonFatal(e) => ....
}
}
}
```
#### 1.3.3 DefaultPromise.dispatchOrAddCallback
这个方法的主要目的是获取Future的状态，从而决定是执行回调还是将回调转移给根Promise。注意这个过程中**`Future`**的执行会导致**`Promise`**的状态发生变化，也就是前面提到的**`PromiseCompletingRunnable中的run方法`**。 以sumFuture为例。
```scala
private def dispatchOrAddCallback(runnable: Runnable): Unit = {
getState match {
case r: Try[_] =>
runnable.executeWithValue(r.asInstanceOf[Try[T]])
case _: DefaultPromise[_] =>
compressRoot().dispatchOrAddCallback(runnable)
case listeners: List[_] =>
if (updateState(listeners, runnable :: listeners)) ()
else dispatchOrAddCallback(runnable)
}
}
```
前面提到过，**DefaultPromise**的状态有三种情况，在**执行回调函数的线程上**(Future运行和回调执行是不同的线程)通过取Future的状态来决定如何操作
+ **Try[T]**
表示已经执行完了，可以开始执行回调函数，这个比较好理解。**CallbackRunnable**的**executeWithValue**被调用，触发**run**方法，从而执行**onComplete**中注册的回调。
+ **DefaultPromise[_]**(一般是调用了map, flatMap生成了新的DefaultPromise)，
这里涉及到链向根DefaultPromise的过程(会在后续的更新中补充)
+ **List[CallbackRunnable]**，
Future的初始状态是**Nil(List[CallbackRunnable])**，<b style="color:red"> 如果执行回调函数的线程在执行的时候，Future的执行并没有结束就会将Future的状态更新为List[CallbackRunnable]， 实际上注册了一个监听器(在Future执行完成之后做什么)</b>。代码中如果状态更新成功，什么都没做，返回值是**`()`**。
由于Future执行线程和回调函数执行线程共享Future的状态，所以 在**`tryCompleteAndGetListeners`**中也能捕获到状态的变化然后进入不同的操作。
至此，一个最基本的Future初始化以及注册回调并收集结果的流程就走完了(对于，状态为DefaultPromise的情况会在后续的更新中完成)。
以下是本文的一些汇总:
+ Future的执行和结果搜集发生在不同的线程上，Promise以及DefaultPromise中的一些方法分别在<b style="color:red">两个线程被调用但是同时修改同一个Future的状态</b>，所以能根据Future不同的状态进行不同的响应。
+ Future的状态由父类**AbstractPromise**中的**_ref**属性维护
+ Future在初始化之后的状态为**List[CallbackRunnable]**，执行完成之后的状态为**Try[T]**，如果通过map，flatMap与其它的Future产生了联系，则状态为**DefaultPromise**。 | 27.322581 | 204 | 0.703896 | yue_Hant | 0.598973 |
24c2b852b05a7ffa3ba5fbb4887e991f1c2255cb | 26 | md | Markdown | README.md | dvhuy/-huydv-stenciljs-starter | 31ff1d03cb62243eb44f11a7082636a0e9095d96 | [
"MIT"
] | null | null | null | README.md | dvhuy/-huydv-stenciljs-starter | 31ff1d03cb62243eb44f11a7082636a0e9095d96 | [
"MIT"
] | null | null | null | README.md | dvhuy/-huydv-stenciljs-starter | 31ff1d03cb62243eb44f11a7082636a0e9095d96 | [
"MIT"
] | null | null | null | # -huydv-stenciljs-starter | 26 | 26 | 0.807692 | dan_Latn | 0.49626 |
24c3191a65eb97a2b1e6fe7fee2cce971d97a52c | 3,415 | md | Markdown | README.md | jraoatlogic/gitlab-exporter | 756c31a3bceb28b40961b77a39a5660b06820203 | [
"Apache-2.0"
] | null | null | null | README.md | jraoatlogic/gitlab-exporter | 756c31a3bceb28b40961b77a39a5660b06820203 | [
"Apache-2.0"
] | 2 | 2020-06-29T14:56:25.000Z | 2020-06-29T14:56:26.000Z | README.md | jraoatlogic/gitlab-exporter | 756c31a3bceb28b40961b77a39a5660b06820203 | [
"Apache-2.0"
] | null | null | null | # gitlab-exporter
Python tool for the command line to export various data sets from GitLab like project issues and group milestone dates. Scales nicely due to an API built on submodules.
*gitlab-exporter* is based on [argparse](https://docs.python.org/3.7/library/argparse.html#module-argparse) and uses [python-gitlab](https://python-gitlab.readthedocs.io/en/stable/) under the hood.
## Motivation
At TUHH we use GitLab CE a lot for project management. The Community Edition (CE) is missing some features that premium versions of GitLab have. As we want to stay independent with MIT licensed distribution of GitLab we have to implement the missing features ourselves.
It takes some time and patience to get all colleagues into working with GitLab. For many of them GitLab is not the tool that they open up first when they start working. Thus, some workarounds and helper functions can make their work more convenient and fun, as not all of them are coders.
*gitlab-exporter* is such a helper tool. Its purpose is to get data out off GitLab and locate it in your colleagues' personal digital environments like calendars, office programs and the like.
## Installation
### Requirements
You need at least on your system
- Python 3.6.x
- pandoc 2.x
### Installation from Source
Go to [the repository](https://collaborating.tuhh.de/hos/modernes-publizieren/offen/software/middleware/gitlab-exporter) and grab the source.
### Installation using Pip
*gitlab-exporter* is a Python tool that can easily be installed with pip.
pip install gitlab-exporter
After installation with pip you should be able to use the command `gitlab-exporter` in your shell.
## Getting to know the API
To learn about the API of *gitlab-exporter* type
gitlab-exporter -h
after installation. There are and will be several submodules for different purposes. Learn about the API of these submodules simply typing e.g.
gitlab-exporter gmd -h
to get help for the submodule that exports group milestone dates to an ICS file.
## Submodules and Examples
*gitlab-exporter* provides several submodules for different purposes.
### `gmd` - group milestone dates
Exports dates and descriptions of milestones on the group level to an ICS file. You then can import this file into your calendar of choice.
Example:
gitlab-exporter https://my-gitlab.com A2DF6HE6R7C88C9AE gmd 1234 milestones.ics
The command consists of the GitLab instance, a private token, the submodule name, the group id and the file name of the ICS file.
### `pi` - project issues
Exports issues belonging to a certain project to a CSV file.
gitlab-exporter https://my-gitlab.com A2DF6HE6R7C88C9AE pi 2345 issues.csv
The command consists of the GitLab instance, a private token, the submodule name, the project id and the CSV file name.
## Automate the boring stuff with Docker
If you have the CI/CD component running with GitLab you can easily have Docker build your exports from GitLab.
Further documentation is on the way...
## Tests
There are some, but they will be updated to [pytest](https://docs.pytest.org/en/latest/index.html) as soon as possible.
## License
Copyright 2019 Axel Dürkop; Hamburg University of Technology (TUHH)
This piece of software is licensed under the [**Apache License, Version 2.0**](https://collaborating.tuhh.de/hos/modernes-publizieren/offen/software/middleware/gitlab-exporter/blob/master/LICENSE) | 40.654762 | 288 | 0.779502 | eng_Latn | 0.994382 |
24c34a34a2541bcfcb246853574d207336dc0d01 | 32 | md | Markdown | power-platform/includes/pn-ms-dyn-365-for-sales.md | barlan/power-platform | a31b9fd040222db744e4e0a00b2dec2dfe415cc6 | [
"CC-BY-4.0",
"MIT"
] | 194 | 2018-04-02T15:18:06.000Z | 2022-03-24T19:55:48.000Z | power-platform/includes/pn-ms-dyn-365-for-sales.md | barlan/power-platform | a31b9fd040222db744e4e0a00b2dec2dfe415cc6 | [
"CC-BY-4.0",
"MIT"
] | 2,219 | 2018-04-12T06:42:32.000Z | 2022-03-31T21:52:26.000Z | power-platform/includes/pn-ms-dyn-365-for-sales.md | barlan/power-platform | a31b9fd040222db744e4e0a00b2dec2dfe415cc6 | [
"CC-BY-4.0",
"MIT"
] | 406 | 2018-03-30T19:22:39.000Z | 2022-03-28T19:14:42.000Z | Microsoft Dynamics 365 for Sales | 32 | 32 | 0.875 | eng_Latn | 0.708346 |
24c4241cec3449e5eafb74cf1552c4c455f700c7 | 1,296 | md | Markdown | SHINE-Extentions/README.md | kumardmebe/hana-shine | da06e135cb673d49a6196e77c570c7741cbed4b8 | [
"Apache-2.0"
] | 6 | 2020-01-06T00:39:40.000Z | 2022-01-14T15:36:56.000Z | SHINE-Extentions/README.md | kumardmebe/hana-shine | da06e135cb673d49a6196e77c570c7741cbed4b8 | [
"Apache-2.0"
] | 2 | 2020-05-12T18:57:14.000Z | 2022-01-11T06:38:05.000Z | SHINE-Extentions/README.md | kumardmebe/hana-shine | da06e135cb673d49a6196e77c570c7741cbed4b8 | [
"Apache-2.0"
] | 6 | 2020-01-06T00:39:45.000Z | 2020-11-13T16:10:40.000Z | ##SHINE Extensions
####Overview
Shine Extensions are Scenarios depicting other HANA features like Smart Data Access , Predictive Analysis etc , which requires additional installation. SHINE Extensions comes up Extension Delivery Unit which has to be Imported on top of Base SHINE DU after Following required Prerequisites.
#### Prerequisite to Run SHINE Extensions
1) You should have already imported SHINE Base DU. Follow Steps in [Shine Read Me](../README.md)
2) Add Shine Role to your User as mentioned in Step 1.
### SHINE Extensions Scenarios
1. **[SMART DATA ACCESS](./SmartDataAccess/README.md)**
Smart Data Access is a data virtualization feature in SAP HANA. This feature was introduced with SP6 in SAP HANA and allows customers to access data virtually from remote sources (heterogeneous sources) such as Hadoop, Oracle, Teradata, SQL Server and SAP databases and combines it with data that resides in an SAP HANA database.
1. **[Predictive Analysis Library](./PredictiveAnalysisLibrary/README.md)**
SAP HANA’s SQLScript, an extension of SQL that includes enhanced control-flow capabilities, lets developers
define complex application logic inside database procedures. However, it is difficult or even impossible to
describe predictive analysis logic with procedures | 54 | 329 | 0.793981 | eng_Latn | 0.963568 |
24c4490de35e54a84539ca64560d41ac6d98a472 | 6,841 | md | Markdown | chapters/automated-testing/integration-testing.md | jahbenjah/little-aspnetcore-book | 7efdde5d5748aac37d0fdd2edfb95c6836b0dd5f | [
"CC-BY-4.0"
] | 15 | 2019-03-19T15:42:41.000Z | 2022-03-31T18:06:07.000Z | chapters/7.automated-testing/integration-testing.md | wkrea/little-aspnetcore-book-ES | f9ed788ee76ea2bced79bc95a4f9e8ad181aec43 | [
"CC-BY-4.0"
] | 5 | 2019-03-06T03:57:44.000Z | 2019-03-15T18:49:04.000Z | chapters/7.automated-testing/integration-testing.md | wkrea/little-aspnetcore-book-ES | f9ed788ee76ea2bced79bc95a4f9e8ad181aec43 | [
"CC-BY-4.0"
] | 6 | 2019-03-20T14:37:03.000Z | 2020-11-30T05:22:49.000Z | ## Pruebas de integración
En comparación con las pruebas unitarias, las pruebas de integración tienen un alcance mucho mayor. Prueba toda la pila de aplicaciones. En lugar de aislar una clase o método, las pruebas de integración aseguran que todos los componentes de su aplicación estén funcionando juntos correctamente: enrutamiento, controladores, servicios, código de base de datos, etc.
Las pruebas de integración son más lentas y más complejas que las pruebas de unitarias, por lo que es común que un proyecto tenga muchas pruebas de unitarias pequeñas pero solo un puñado de pruebas de integración.
Para probar toda la pila (incluido el enrutamiento del controlador), las pruebas de integración normalmente hacen llamadas HTTP a su aplicación como lo haría un navegador web.
Para realizar una prueba de integración, puede iniciar su aplicación y realizar solicitudes manualmente a http://localhost:5000. Sin embargo, ASP.NET Core ofrece una mejor alternativa: la clase `TestServer`. Esta clase puede alojar su aplicación durante la duración de la prueba, y luego detenerla automáticamente cuando se completa la prueba.
### Crear un proyecto de prueba
Si actualmente se encuentra en el directorio de su proyecto, `cd` sube un nivel al directorio raíz `AspNetCoreTodo`. Use este comando para crear un nuevo proyecto de prueba:
```
dotnet new xunit -o AspNetCoreTodo.IntegrationTests
```
Su estructura de directorio ahora debería verse así:
```
AspNetCoreTodo/
AspNetCoreTodo/
AspNetCoreTodo.csproj
Controllers/
(etc...)
AspNetCoreTodo.UnitTests/
AspNetCoreTodo.UnitTests.csproj
AspNetCoreTodo.IntegrationTests/
AspNetCoreTodo.IntegrationTests.csproj
```
> Si lo prefiere, puede mantener sus pruebas unitarias y pruebas de integración en el mismo proyecto. Para proyectos grandes, es común dividirlos para que sea fácil ejecutarlos por separado.
Dado que el proyecto de prueba utilizará las clases definidas en su proyecto principal, deberá agregar una referencia al proyecto principal:
```
dotnet add reference ../AspNetCoreTodo/AspNetCoreTodo.csproj
```
También deberá agregar el paquete NuGet `Microsoft.AspNetCore.TestHost`:
```
dotnet add package Microsoft.AspNetCore.TestHost
```
Elimine el archivo `UnitTest1.cs` creado por `dotnet new`. Estás listo para escribir una prueba de integración.
### Escribir una prueba de integración.
Hay algunas cosas que deben configurarse en el servidor de prueba antes de cada prueba. En lugar de abarrotar la prueba con este código de configuración, puede mantener esta configuración en una clase separada. Crea una nueva clase llamada `TestFixture`:
**AspNetCoreTodo.IntegrationTests/TestFixture.cs**
```csharp
using System;
using System.Collections.Generic;
using System.IO;
using System.Net.Http;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.TestHost;
using Microsoft.Extensions.Configuration;
namespace AspNetCoreTodo.IntegrationTests
{
public class TestFixture : IDisposable
{
private readonly TestServer _server;
public HttpClient Client { get; }
public TestFixture()
{
var builder = new WebHostBuilder()
.UseStartup<AspNetCoreTodo.Startup>()
.ConfigureAppConfiguration((context, config) =>
{
config.SetBasePath(Path.Combine(
Directory.GetCurrentDirectory(),
"..\\..\\..\\..\\AspNetCoreTodo"));
config.AddJsonFile("appsettings.json");
});
_server = new TestServer(builder);
Client = _server.CreateClient();
Client.BaseAddress = new Uri("http://localhost:8888");
}
public void Dispose()
{
Client.Dispose();
_server.Dispose();
}
}
}
```
Esta clase se encarga de configurar un `TestServer`, y ayudará a mantener las pruebas limpias y ordenadas.
Ahora estás (realmente) listo para escribir una prueba de integración. Crea una nueva clase llamada `TodoRouteShould`:
**AspNetCoreTodo.IntegrationTests/TodoRouteShould.cs**
```csharp
using System.Net;
using System.Net.Http;
using System.Threading.Tasks;
using Xunit;
namespace AspNetCoreTodo.IntegrationTests
{
public class TodoRouteShould : IClassFixture<TestFixture>
{
private readonly HttpClient _client;
public TodoRouteShould(TestFixture fixture)
{
_client = fixture.Client;
}
[Fact]
public async Task ChallengeAnonymousUser()
{
// Arrange
var request = new HttpRequestMessage(
HttpMethod.Get, "/todo");
// Act: request the /todo route
var response = await _client.SendAsync(request);
// Assert: the user is sent to the login page
Assert.Equal(
HttpStatusCode.Redirect,
response.StatusCode);
Assert.Equal(
"http://localhost:8888/Account" +
"/Login?ReturnUrl=%2Ftodo",
response.Headers.Location.ToString());
}
}
}
```
Esta prueba realiza una solicitud anónima (sin iniciar sesión) a la ruta `/todo` y verifica que el navegador se redirige a la página de inicio de sesión.
Este escenario es un buen candidato para una prueba de integración, ya que involucra múltiples componentes de la aplicación: el sistema de enrutamiento, el controlador, el hecho de que el controlador está marcado con `[Authorize]`, y así sucesivamente. También es una buena prueba porque garantiza que nunca quitará accidentalmente el atributo `[Authorize]` y hará que la vista de tareas sea accesible para todos.
## Ejecutar la prueba
Ejecute la prueba en el terminal con `dotnet test`. Si todo funciona bien, verás un mensaje de éxito:
```
Starting test execution, please wait...
Discovering: AspNetCoreTodo.IntegrationTests
Discovered: AspNetCoreTodo.IntegrationTests
Starting: AspNetCoreTodo.IntegrationTests
Finished: AspNetCoreTodo.IntegrationTests
Total tests: 1. Passed: 1. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 2.0588 Seconds
```
## Resumiendo
Las pruebas son un tema amplio y hay mucho más que aprender. Este capítulo no toca el código de prueba de interfaz de usuario (UI) ni el código de prueba (JavaScript), que probablemente merecen libros completos por su cuenta. Sin embargo, debe tener las habilidades y el conocimiento básico que necesita para aprender más sobre las pruebas y practicar la escritura de pruebas para sus propias aplicaciones.
La documentación de ASP.NET Core (https://docs.asp.net) y Stack Overflow son excelentes recursos para aprender más y encontrar respuestas cuando te quedas atascado.
| 39.091429 | 413 | 0.718608 | spa_Latn | 0.981179 |
24c5c85d1053f830816ad4e7b2e1e9f12db3a88f | 3,483 | md | Markdown | README.md | larseggert/qvalve | d4c966e77c5eb3528c44b01b14545ced238b221f | [
"MIT"
] | 15 | 2018-09-12T14:05:59.000Z | 2020-11-08T11:07:56.000Z | README.md | larseggert/qvalve | d4c966e77c5eb3528c44b01b14545ced238b221f | [
"MIT"
] | 2 | 2018-10-09T07:52:54.000Z | 2019-01-06T20:48:44.000Z | README.md | larseggert/qvalve | d4c966e77c5eb3528c44b01b14545ced238b221f | [
"MIT"
] | 3 | 2018-10-08T14:52:25.000Z | 2019-08-09T13:34:03.000Z | # qvalve
`qvalve` can predictably impair QUIC flows, by dropping, reordering or
duplicating individual packets and sequences of packets. It is a non-transparent
UDP proxy that should be interposed between a QUIC client and a QUIC server.
The behavior of `qvalve` is configured with rules specified in a simple
language. Examples:
```
# drop the first three client initial pkts
> i1..3 drop
# drop the first server vneg pkt
< v1 drop
# duplicate the second server vneg pkt three times (= four copies sent)
< v2 dup 3
# reorder the first server handshake pkt (default: by one pkt)
< h1 reor
# nop does nothing
< h2 nop
```
More examples are in the `tests` directory and in https://github.com/NTAP/quant/tree/14/qvalve-tests.
See https://github.com/NTAP/quant/blob/14/bin/dtest.sh for an example for how to use this to automatically test a QUIC stack with docker containers (via the `docker-compose` config in https://github.com/NTAP/quant/blob/14/docker-compose.yml).
# Copyright
Copyright (c) 2018-2019, NetApp, Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Portions of this code are adapted from
https://gist.github.com/vxgmichel/b2cf8536363275e735c231caef35a5df by Vincent
Michel.
Copyright (c) 2017, Vincent Michel
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
| 41.464286 | 242 | 0.794143 | yue_Hant | 0.358064 |
24c5e2bf0833ad6b9bc57921ac0f702ab7b66fba | 33 | md | Markdown | README.md | AKnightWing/SDSS-Time-Series-Classification | 1cdc3cef07d17ea39be60c7ee73fd1b0d7b21981 | [
"MIT"
] | null | null | null | README.md | AKnightWing/SDSS-Time-Series-Classification | 1cdc3cef07d17ea39be60c7ee73fd1b0d7b21981 | [
"MIT"
] | null | null | null | README.md | AKnightWing/SDSS-Time-Series-Classification | 1cdc3cef07d17ea39be60c7ee73fd1b0d7b21981 | [
"MIT"
] | null | null | null | # SDSS-Time-Series-Classification | 33 | 33 | 0.848485 | kor_Hang | 0.816019 |
24c6299dbe8fec790141b40a0e4077ccaae3720d | 660 | md | Markdown | docs/devices/ikea/e1603_e1702_e1708.md | night199uk/homebridge-z2m | 9a0a2e234c63af56352a8bf14f695b12404e0a61 | [
"Apache-2.0"
] | 139 | 2020-06-28T00:14:19.000Z | 2022-03-30T05:11:11.000Z | docs/devices/ikea/e1603_e1702_e1708.md | night199uk/homebridge-z2m | 9a0a2e234c63af56352a8bf14f695b12404e0a61 | [
"Apache-2.0"
] | 380 | 2020-06-30T23:11:31.000Z | 2022-03-31T18:32:23.000Z | docs/devices/ikea/e1603_e1702_e1708.md | night199uk/homebridge-z2m | 9a0a2e234c63af56352a8bf14f695b12404e0a61 | [
"Apache-2.0"
] | 31 | 2020-07-12T06:29:50.000Z | 2022-03-13T02:30:53.000Z | ---
title: "IKEA E1603/E1702/E1708 Homebridge/HomeKit integration"
description: "Add HomeKit support to your IKEA E1603/E1702/E1708, using Homebridge, Zigbee2MQTT and homebridge-z2m."
---
<!---
This file has been GENERATED using src/docgen/docgen.ts
DO NOT EDIT THIS FILE MANUALLY!
-->
# IKEA E1603/E1702/E1708
> TRADFRI control outlet
# Services and characteristics
The following HomeKit Services and Characteristics are exposed by
the IKEA E1603/E1702/E1708
* [Switch](../../switch.md)
* On
# Related
* [Other devices from IKEA](../index.md#ikea)
* [Zigbee2MQTT documentation for this device](https://www.zigbee2mqtt.io/devices/E1603_E1702_E1708.html) | 28.695652 | 116 | 0.760606 | eng_Latn | 0.424023 |
24c7ec0fdb24ea19d11e63456c5a5e8353f44a52 | 3,608 | md | Markdown | README.md | myluco/NYTimesAndroidApp | 0277906ac86aed690e82143315f640903b5dd012 | [
"Apache-2.0"
] | 2 | 2016-05-26T07:37:49.000Z | 2016-09-14T09:29:19.000Z | README.md | myluco/NYTimesAndroidApp | 0277906ac86aed690e82143315f640903b5dd012 | [
"Apache-2.0"
] | 1 | 2016-02-16T05:33:16.000Z | 2016-02-16T06:02:23.000Z | README.md | myluco/NYTimesAndroidApp | 0277906ac86aed690e82143315f640903b5dd012 | [
"Apache-2.0"
] | null | null | null | # New York Times Article Search
# Pre-work - New York Times Article Search
Build a New York Times News Search article app which allows a user to find old articles.
Submitted by: Luiza Carneiro
Time spent: Not sure
## User Stories
The following user stories must be completed:
* [x] User can enter a search query that will display a grid of news articles using the thumbnail and headline from the New York Times Search API. (3 points)
* [x]User can click on "settings" which allows selection of advanced search options to filter results. (3 points)
* [x]User can configure advanced search filters such as: (points included above)
Begin Date (using a date picker)
News desk values (Arts, Fashion & Style, Sports)
Sort order (oldest or newest)
* [x] Subsequent searches will have any filters applied to the search results. (1 point)
* [x] User can tap on any article in results to view the contents in an embedded browser. (2 points)
* [x] User can scroll down "infinitely" to continue loading more news articles. The maximum number of articles is limited by the API search. (1 point)
The following advanced user stories are optional but recommended:
* [x] Advanced: Robust error handling, check if internet is available, handle error cases, network failures. (1 point)
* [] Advanced: Use the ActionBar SearchView or custom layout as the query box instead of an EditText. (1 point)
* [] Advanced: User can share a link to their friends or email it to themselves. (1 point)
* [] Advanced: Replace Filter Settings Activity with a lightweight modal overlay. (2 points)
* [] Advanced: Improve the user interface and experiment with image assets and/or styling and coloring (1 to 3 points depending on the difficulty of UI improvements)
* [] Bonus: Use the RecyclerView with the StaggeredGridLayoutManager to display improve the grid of image results (see Picasso guide too). (2 points)
* [] Bonus: For different news articles that only have text or have text with thumbnails, use Heterogenous Layouts with RecyclerView. (2 points)
* [] Bonus: Apply the popular ButterKnife annotation library to reduce view boilerplate. (1 point)
* [] Bonus: Use Parcelable instead of Serializable using the popular Parceler library. (1 point)
* [] Bonus: Leverage the popular GSON library to streamline the parsing of JSON data. (1 point)
* [] Bonus: Replace Picasso with Glide for more efficient image rendering. (1 point)
## Additional User Stories
* [x] If not thumbnail for the article is available, display the NYTimes Logo
* [x] If query term is blank, tell user that query term needs to contain something
## Video Walkthrough
Here's a walkthrough of implemented user stories:
<a href="http://i.imgur.com/BtAG7yQ.gifv" target="_blank">Video Walkthrough</a>
Showing exceptions: Network not available and search query is blank
<a href="http://i.imgur.com/7rgzu77.gifv" target="_blank">Video Walkthrough for Exceptions</a>
GIF created with [LiceCap](http://www.cockos.com/licecap/).
## Notes
*
.
## License
Copyright [2016] [Luiza Carneiro]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
| 48.106667 | 165 | 0.759424 | eng_Latn | 0.987862 |
24c9366f6307ea23187f6a953767cca5f2ae425c | 409 | md | Markdown | README.md | MarineGEO/marinegeo.github.io | f22b7153520b112b4ad2b623f593e2a1a6edf925 | [
"MIT"
] | null | null | null | README.md | MarineGEO/marinegeo.github.io | f22b7153520b112b4ad2b623f593e2a1a6edf925 | [
"MIT"
] | 5 | 2018-10-23T14:17:20.000Z | 2021-07-27T14:56:44.000Z | README.md | MarineGEO/marinegeo.github.io | f22b7153520b112b4ad2b623f593e2a1a6edf925 | [
"MIT"
] | 7 | 2018-08-01T21:15:46.000Z | 2021-07-22T03:14:01.000Z | # MarineGEO data website
[](https://travis-ci.com/MarineGEO/marinegeo.github.io)
[See repository wiki for help & instructions](https://github.com/MarineGEO/marinegeo.github.io/wiki)
## Beautiful Jekyll
Site built using the [Beautiful Jekyll](https://github.com/daattali/beautiful-jekyll#readme) theme by Dean Attali.
| 34.083333 | 141 | 0.775061 | yue_Hant | 0.645794 |
24c974fc3d963dd801bfb5ee7f64585e11430693 | 3,365 | md | Markdown | _pages/aot-group/achievements-awards.md | DesignHLO/aotgroup | 90a3b5627a123a1f4155e6bb0bd506442b489be3 | [
"MIT"
] | null | null | null | _pages/aot-group/achievements-awards.md | DesignHLO/aotgroup | 90a3b5627a123a1f4155e6bb0bd506442b489be3 | [
"MIT"
] | null | null | null | _pages/aot-group/achievements-awards.md | DesignHLO/aotgroup | 90a3b5627a123a1f4155e6bb0bd506442b489be3 | [
"MIT"
] | null | null | null | ---
title: "Achievements & Awards"
layout: archive
permalink: /achievements-awards/
sidebar:
nav: "docs"
---
The AOT Group has been recognised for excellence within the Australia and New Zealand Travel and Tourism industry, receiving the following awards and achievements over the years:
* 2014 AOT takes over the business of Territory Discoveries
* 2013 - Cinzia Burnes appointed to the Board of Tourism Victoria
* 2013 - AOT acquires ATS Pacific in Australia, New Zealand and Fiji together with Tourism Transport Fiji
* 2012 - AOT wins the Commonwealth Government contract and is appointed the official Accommodation Program Manager for all Agencies of the Government
* 2011 - AOT enters into joint-venture partnership and takes over the running of Air New Zealand Holidays
* 2011 - AOT New Zealand wins the Inbound Tour Operators Council of New Zealand 'Operator of the Year' award
* 2010 - Sunlover Holidays again wins the National Tourism Industry Award for best Domestic Wholesaler
* 2009 - Sunlover Holidays wins the National Tourism Industry Award for best Domestic Wholesaler
* 2009 - Winner Harvey World Travel Brochure of the Year (Sunlover Holidays)
* 2008 - AOT named number one supplier by Voyages Hotels and Resorts
* 2007 - AOT named number one supplier by Voyages Hotels and Resorts
* 2006 - Andrew Burnes, CEO, appointed Deputy Chairman of Tourism Australia
* 2006 - AOT named number one supplier by Voyages Hotels and Resorts
* 2006 - Winner National Travel Industry Awards for Excellence Tour Operator of the Year -Domestic (Sunlover Holidays)
* 2004 - Andrew Burnes, CEO, appointed to the Board of Tourism Australia
* 2004 - Winner Governor of Victoria Export Awards
* 2004 - Winner Harvey World Travel Brochure of the Year (Sunlover Holidays)
* 2004 - Winner Harvey World Travel Principal of the Year (Sunlover Holidays)
* 2004 - Winner Harvey World Travel Sales Executive of the Year (NSW and VIC)
* 2003 - Winner Australian Export Awards
* 2003 - Winner Governor of Victoria Export Awards
* 2003 - Winner Harvey World Travel Principal of the Year (Sunlover Holidays)
* 2002 - Winner Harvey World Travel Brochure of the Year (Sunlover Holidays)
* 2002 - Winner Harvey World Travel Principal of the Year (Sunlover Holidays)
* 2002 - Winner National Travel Industry Awards for Excellence Wholesaler of the Year
* 2001 - Winner Harvey World Travel Principal of the Year (Sunlover Holidays)
* 2000 - Business Review Weekly - AOT named as one of Australia's top 500 Private Companies
* 2000 - Business Review Weekly - AOT named as one of the Top 100 Fastest Growing Private Companies
* 1999 - Winner Governor of Victoria Export Awards
* 1999 - Winner Australian Export Awards
* 1999 - Business Review Weekly - AOT named as one of Australia's Top 500 Private Companies
* 1998 - Business Review Weekly - AOT named as Australia's * 19th fastest growing private company over the last 5 years (* 1993-* 1997), achieving a 637% increase in turnover growth since * 1993.
* 1997 - Business Review Weekly - AOT names as the 13th fastest growing private company over the last 5 years (* 1992-* 1996) achieving a 775% increase in turnover growth since * 1992.
* 1994 - Winner Queensland Tourism Awards - Best Inbound Tour Operator (The final year this category was offered)
* 1993 - Winner Queensland Tourism Awards - Best Inbound Tour Operator | 74.777778 | 198 | 0.783655 | eng_Latn | 0.95325 |
24ca2c385abed6e959b5bf60b9c674e42b0dc06f | 1,450 | md | Markdown | docs/migration-guides/0.5-0.6.md | blentz100/kyt | ffa4426300c1dd3ff58e3eb49d6b2ae585904c3e | [
"Apache-2.0"
] | 1,636 | 2016-09-13T14:47:11.000Z | 2019-03-04T15:55:01.000Z | docs/migration-guides/0.5-0.6.md | blentz100/kyt | ffa4426300c1dd3ff58e3eb49d6b2ae585904c3e | [
"Apache-2.0"
] | 269 | 2019-03-12T18:55:55.000Z | 2022-03-29T10:21:39.000Z | docs/migration-guides/0.5-0.6.md | blentz100/kyt | ffa4426300c1dd3ff58e3eb49d6b2ae585904c3e | [
"Apache-2.0"
] | 170 | 2016-09-14T02:25:12.000Z | 2019-03-01T21:03:38.000Z | # Migration Guide 0.5 - 0.6
## Refactor for the new vendor bundling
Version 0.6 adds a new `vendor.js` and `manifest.js` script to the exported client assets. It also changes the format of the asset manifest (`publicAssets.json`). Please refer to this section in the [conventions documentation](/docs/conventions.md#working-with-client-assets) for how the new assets should be referenced (and in what order!).
The following shows how we updated the starter kyts with the new rules:
- [include the new manifest and vendor scripts and update how the client assets are referenced](https://github.com/NYTimes/kyt/pull/487/files#diff-5c9af8ba0b7857800f72a55cdc5409aa)
- [output the scripts in the correct order](https://github.com/NYTimes/kyt/pull/487/files#diff-1a3dd5d68b85906698a452ac9279ecc5)
## PostCSS custom configuration
If you applied a custom PostCSS configuration in your kyt.config.js, then you should move your configuration into a postcss.config.js file at the root of your project. See more [here](/docs/Recipes.md#add-postcss-plugins).
## Naming your chunks
Webpack added a not-so-graceful implementation for naming your `import`ed chunks. You can now [add a comment to your `import` statement](https://github.com/NYTimes/kyt/blob/843341291ad99c925d2c8a1b07f323b9d40e954b/packages/kyt-starter-static/starter-src/src/routes/index.js#L12) to name the output file. This only helps in identifying your chunks during the build process.
| 76.315789 | 372 | 0.795172 | eng_Latn | 0.960294 |
24ca364468c02489fcb56812678657eca079df78 | 2,331 | md | Markdown | subscriptions/solutions/downloading-activating-or-using-software/downloading-activating-or-using-software/includes/unable-to-download-visual-studio-for-mac.md | MicrosoftDocs/visualstudio-docs.pl-pl | 64a8f785c904c0e158165f3e11d5b0c23a5e34c5 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-20T07:52:54.000Z | 2021-02-06T18:51:42.000Z | subscriptions/solutions/downloading-activating-or-using-software/downloading-activating-or-using-software/includes/unable-to-download-visual-studio-for-mac.md | MicrosoftDocs/visualstudio-docs.pl-pl | 64a8f785c904c0e158165f3e11d5b0c23a5e34c5 | [
"CC-BY-4.0",
"MIT"
] | 8 | 2018-08-02T15:03:13.000Z | 2020-09-27T20:22:01.000Z | subscriptions/solutions/downloading-activating-or-using-software/downloading-activating-or-using-software/includes/unable-to-download-visual-studio-for-mac.md | MicrosoftDocs/visualstudio-docs.pl-pl | 64a8f785c904c0e158165f3e11d5b0c23a5e34c5 | [
"CC-BY-4.0",
"MIT"
] | 16 | 2018-01-29T09:30:06.000Z | 2021-10-09T11:23:54.000Z | ---
title: Nie można pobrać ani aktywować Visual Studio dla komputerów Mac
description: Nie można pobrać ani aktywować Visual Studio dla komputerów Mac z subskrypcji programu Visual Studio
ms.topic: include
ms.assetid: afb945a3-b08e-4a9f-92d9-660f5657686b
author: caitybuschlen
ms.author: cabuschl
ms.date: 08/14/2020
user.type: subscriber
tags: download, activate
subscription.type: vl, cloud, retail, partner
sap.id: 53a7a6d4-7755-352a-5a65-715d78af84bf
ms.openlocfilehash: 679ad453f6b3693e6c3eae90cc8f6b69d8c7f3b1
ms.sourcegitcommit: 60e5a8a7ee91854356797d05f3b502572c4a4884
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 12/09/2020
ms.locfileid: "96916331"
---
## <a name="im-unable-to-download-or-activate-visual-studio-for-mac"></a>Nie mogę pobrać ani aktywować Visual Studio dla komputerów Mac
Jako subskrybent programu Visual Studio masz dostęp do środowiska IDE programu Visual Studio. Visual Studio dla komputerów Mac jest osobnym pobraniem, które można znaleźć na [stronie pliki do pobrania](https://my.visualstudio.com/Downloads) w portalu subskrypcje.
## <a name="find-and-download-visual-studio-for-mac"></a>Znajdź i Pobierz Visual Studio dla komputerów Mac
1. Zaloguj się do [portalu subskrypcji](https://my.visualstudio.com/benefits)i zobacz [Widok przefiltrowanych](https://my.visualstudio.com/Downloads?q=Visual%20Studio%20for%20mac&pgroup=) dostępnych Visual Studio dla komputerów Mac pobierania. Oferujemy tylko najnowsze wersje produktu.
2. Postępuj zgodnie z instrukcjami pobierania i instalowania.
1. Przy użyciu poczty e-mail, do której przypisano subskrypcję, będziesz mieć możliwość natychmiastowego zalogowania się do środowiska IDE po instalacji, ale nie jest wymagany żaden klucz produktu.
## <a name="no-download-available"></a>Brak dostępnych plików do pobrania
Dostępne do pobrania oprogramowanie są zależne od używanej subskrypcji. Jeśli nie widzisz szukanego pobrania, być może nie jest ono dostępne. Aby sprawdzić, jakie subskrypcje są dostępne dla Ciebie, zaloguj się na [stronie Subskrypcje](https://my.visualstudio.com/subscriptions) portalu. Możesz [pobrać obszerną listę](https://download.microsoft.com/download/1/5/4/15454442-CF17-47B9-A65D-DF84EF88511B/Visual_Studio_by_Subscription_Level.xlsx) dostępnych tytułów oprogramowania dla wszystkich typów subskrypcji. | 77.7 | 513 | 0.817675 | pol_Latn | 0.997013 |
24ca8522b08999d526472b944c7a4419d07b5b1e | 2,874 | md | Markdown | docs/misc/troubleshooting-exceptions-system-invalidcastexception.md | doodz/visualstudio-docs.fr-fr | 49c7932ec7a761e4cd7c259a5772e5415253a7a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/misc/troubleshooting-exceptions-system-invalidcastexception.md | doodz/visualstudio-docs.fr-fr | 49c7932ec7a761e4cd7c259a5772e5415253a7a5 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-10-19T08:00:06.000Z | 2018-10-19T08:00:06.000Z | docs/misc/troubleshooting-exceptions-system-invalidcastexception.md | doodz/visualstudio-docs.fr-fr | 49c7932ec7a761e4cd7c259a5772e5415253a7a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Dépannage des exceptions : System.InvalidCastException | Microsoft Docs"
ms.custom: ""
ms.date: "12/15/2016"
ms.prod: "visual-studio-dev14"
ms.reviewer: ""
ms.suite: ""
ms.technology:
- "devlang-csharp"
ms.tgt_pltfrm: ""
ms.topic: "article"
dev_langs:
- "JScript"
- "VB"
- "CSharp"
- "C++"
helpviewer_keywords:
- "InvalidCastException (classe)"
ms.assetid: a855dfe1-5c06-45a6-9c2f-c9e799ccf8f0
caps.latest.revision: 23
caps.handback.revision: 23
author: "mikeblome"
ms.author: "mblome"
manager: "douge"
---
# Dépannage des exceptions : System.InvalidCastException
Une exception <xref:System.InvalidCastException> est levée lorsqu'une défaillance se produit pendant une conversion de référence explicite. Des conversions de références sont des conversions d'un type référence à un autre. Si elles peuvent modifier le type de la référence, elles ne modifient jamais le type ou la valeur de la cible de la conversion L'exécution d'un cast des objets d'un type en un autre est souvent à l'origine de cette exception.
## Conseils associés
**Comparez les types sources aux types de destination pour vérifier la validité de la conversion.**
Pour plus d'informations sur les conversions prises en charge par le système, consultez <xref:System.Convert>.
## Notes
Pour réussir une conversion de référence explicite, la valeur source doit être Null \(`Nothing` en Visual Basic\) ou le type d'objet référencé par l'argument source doit être convertible au type de destination par une conversion de référence implicite.
Lorsqu'une application Visual Basic 6.0 avec un appel à un événement personnalisé dans un contrôle utilisateur est mise à niveau vers une version plus récente de Visual Basic et qu'elle s'exécute, cette exception peut se produire avec les informations supplémentaires : "Le cast spécifié n'est pas valide." Pour corriger cette erreur, recherchez la ligne de code suivante dans `Form1` :
`Call UserControl11_MyCustomEvent(UserControl11, New UserControl1.MyCustomEventEventArgs(5))`
Puis, remplacez\-la par :
`Call UserControl11_MyCustomEvent(UserControl11(0), New UserControl1.MyCustomEventEventArgs(5))`
## Voir aussi
<xref:System.InvalidCastException>
[Use the Exception Assistant](../Topic/How%20to:%20Use%20the%20Exception%20Assistant.md)
[How to: Convert an Object to Another Type in Visual Basic](../Topic/How%20to:%20Convert%20an%20Object%20to%20Another%20Type%20in%20Visual%20Basic.md)
[Conversion de chaînes en types de données .NET Framework](../Topic/Converting%20Strings%20to%20.NET%20Framework%20Data%20Types.md)
[Comment : implémenter des conversions définies par l'utilisateur entre des structs](../Topic/How%20to:%20Implement%20User-Defined%20Conversions%20Between%20Structs%20\(C%23%20Programming%20Guide\).md) | 58.653061 | 450 | 0.76096 | fra_Latn | 0.918562 |
24cbc93694951a45ebd3bb28d466c3ba2c9e2b39 | 52 | md | Markdown | README.md | farkasmark/loopback-crm | 75fd5cb3a4d630fa0ac3e7f0cdbd47d324057320 | [
"MIT"
] | 2 | 2019-01-10T18:38:07.000Z | 2019-01-14T06:21:36.000Z | README.md | farkasmark/loopback-crm | 75fd5cb3a4d630fa0ac3e7f0cdbd47d324057320 | [
"MIT"
] | null | null | null | README.md | farkasmark/loopback-crm | 75fd5cb3a4d630fa0ac3e7f0cdbd47d324057320 | [
"MIT"
] | null | null | null | # loopback-crm
A demonstration project for LoopBack
| 17.333333 | 36 | 0.826923 | eng_Latn | 0.917272 |
24cbcbb1dafdbe894106474c9be1272a08bf73bb | 51 | md | Markdown | README.md | MarEliSeg/ipic | 07b90d58219c3f9cbf4956bdc4147812cb536615 | [
"MIT"
] | null | null | null | README.md | MarEliSeg/ipic | 07b90d58219c3f9cbf4956bdc4147812cb536615 | [
"MIT"
] | null | null | null | README.md | MarEliSeg/ipic | 07b90d58219c3f9cbf4956bdc4147812cb536615 | [
"MIT"
] | null | null | null | # ipic
Inferring Persistent Interdomain Congestion
| 17 | 43 | 0.862745 | eng_Latn | 0.928679 |
24ccade7635ed3c07cbdf66fe290598ee04bdf3f | 1,699 | md | Markdown | _posts/2010-12-21-a-new-programming-language-is-created-every-week.md | darkmuck/darkmuck.github.io | 4143ead8102aca57614250b96e859944d889d8a8 | [
"MIT"
] | null | null | null | _posts/2010-12-21-a-new-programming-language-is-created-every-week.md | darkmuck/darkmuck.github.io | 4143ead8102aca57614250b96e859944d889d8a8 | [
"MIT"
] | null | null | null | _posts/2010-12-21-a-new-programming-language-is-created-every-week.md | darkmuck/darkmuck.github.io | 4143ead8102aca57614250b96e859944d889d8a8 | [
"MIT"
] | null | null | null | ---
ID: 1443
post_title: >
A New Programming Language is Created
Every Week
author: Shwuzzle
post_date: 2010-12-21 13:12:33
post_excerpt: ""
layout: post
published: true
aktt_notify_twitter:
- 'yes'
ratings_users:
- "0"
ratings_score:
- "0"
ratings_average:
- "0"
aktt_tweeted:
- "1"
---
"<em>A catalog maintained by Bill Kinnersley of the University of Kansas lists about 2,500 programming languages. Another survey, compiled by Diarmuid Piggott, puts the total even higher, at more than 8,500. And keep in mind that whereas human languages have had millennia to evolve and diversify, all the computer languages have sprung up in just 50 years. Even by the more-conservative standards of the Kinnersley count, that means we've been inventing one language a week, on average, ever since Fortran.</em>
<em>For ethnologists, linguistic diversity is a cultural resource to be nurtured and preserved, much like biodiversity. All human languages are valuable; the more the better. That attitude of detached reverence is harder to sustain when it comes to computer languages, which are products of design or engineering rather than evolution. The creators of a new programming language are not just adding variety for its own sake; they are trying to make something demonstrably better. But the very fact that the proliferation of languages goes on and on argues that we still haven't gotten it right. We still don't know the best notation—or even a good-enough notation—for expressing an algorithm or defining a data structure.</em>"
<a href="http://www.americanscientist.org/issues/id.3489,y.0,no.,content.true,page.1,css.print/issue.aspx">The Semicolon Wars (americanscientist.org)</a>
| 62.925926 | 727 | 0.782813 | eng_Latn | 0.995589 |
24cd2288abded6c96ac59deb58d15956dd6acc40 | 694 | md | Markdown | README.md | shravan-mohan/optimal-rectifier-switching-singlephase | baf4220dcc15c1a93d5bf6545e9e78db9acabbb2 | [
"MIT"
] | 2 | 2020-09-09T21:12:15.000Z | 2021-06-28T13:33:44.000Z | README.md | shravan-mohan/optimal-rectifier-switching-singlephase | baf4220dcc15c1a93d5bf6545e9e78db9acabbb2 | [
"MIT"
] | null | null | null | README.md | shravan-mohan/optimal-rectifier-switching-singlephase | baf4220dcc15c1a93d5bf6545e9e78db9acabbb2 | [
"MIT"
] | null | null | null | # Optimal Rectifier Switching (Single Phase)
This function computes the optimal switching of a single phase rectifier which minimizes a weighted sum of the THDs of the input current and the output voltage,
using linear programming.
# Use
optRectifierSwtiching(N=2048, outputVoltageSineHarmonicNums=[1,2,4,6],
outputVoltageSinevals=[0,0,0,0],
outputVoltagecosinharmonicnums=[1,2,4,6],
outputVoltagecosinevals=[0,0,0,0],
outputVoltageDCval=0.2, gamma=10,
solver='ECOS')
# Package Requirements
1. Numpy
2. Scipy
3. CVXPY
4. Matplotlib
| 38.555556 | 160 | 0.610951 | eng_Latn | 0.870339 |
24cd2fbffd82dd463440a87cab87cf2e3f288047 | 580 | md | Markdown | README.md | andyalexander/CV | b629de33d64c83d31117b2600f21beec12a6c1d0 | [
"MIT"
] | null | null | null | README.md | andyalexander/CV | b629de33d64c83d31117b2600f21beec12a6c1d0 | [
"MIT"
] | null | null | null | README.md | andyalexander/CV | b629de33d64c83d31117b2600f21beec12a6c1d0 | [
"MIT"
] | null | null | null | # About
Fork of the ShareLateX version of the [Friggeri CV](https://www.sharelatex.com/templates/cv-or-resume/fancy-cv) from Adrien Friggeri changed to render in A4 paper format. There is also a new option `nocolors` to disable use of colors in section headers.
You need
* TikZ,
* XeTex,
* fontspec
* biblatex and
* textpos
to build the CV.
## Options
* `print`: renders in black and white, and reverts the header to dark on light
* `nocolors`: no colors in section headers (but still use dark header)
 | 26.363636 | 253 | 0.734483 | eng_Latn | 0.967915 |
24ce5854594f2b057ef5db419a8445aa76b5c804 | 711 | md | Markdown | README.md | smedina2494/Creative-Coding-Final | cffb911081418ed81eee4038a3ada589b8db9f33 | [
"MIT"
] | null | null | null | README.md | smedina2494/Creative-Coding-Final | cffb911081418ed81eee4038a3ada589b8db9f33 | [
"MIT"
] | null | null | null | README.md | smedina2494/Creative-Coding-Final | cffb911081418ed81eee4038a3ada589b8db9f33 | [
"MIT"
] | null | null | null | # Demo
## How to run
### start a Serial Server
You might choose either with an GUI App or from cmd
#### GUI
run: https://github.com/vanevery/p5.serialcontrol/releases
#### Cmd Line
see https://github.com/vanevery/p5.serialport#p5serial-nodejs
### run web server
either via serve.js or Python
#### serve.js way (Prefered)
Make sure you have node.js installed to have it run, if you don't have it:
##### install `node.js`
```
$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
$ brew install node
```
##### install `serve.js`
```bash
$ npm install -g serve
```
##### run
``` bash
$ serve .
```
#### Python way
``` bash
$ python -m SimpleHTTPServer
```
| 18.230769 | 100 | 0.668073 | eng_Latn | 0.792858 |
24cf3bb29f2fe5c661398f56361ead58552b2103 | 29 | md | Markdown | README.md | Dreaded-Gnu/playground | b7a2998c8f1f367f1e9508010571edf3a725c472 | [
"MIT"
] | null | null | null | README.md | Dreaded-Gnu/playground | b7a2998c8f1f367f1e9508010571edf3a725c472 | [
"MIT"
] | null | null | null | README.md | Dreaded-Gnu/playground | b7a2998c8f1f367f1e9508010571edf3a725c472 | [
"MIT"
] | null | null | null | # playground
playground repo
| 9.666667 | 15 | 0.827586 | eng_Latn | 0.996498 |
24d1bd2779378c2421c5e72c7af6a9adcb2121dd | 308 | md | Markdown | README.md | kmui2/Multiple-Files-Renamer | 820e1b302ebb75d6aef7c9ede7c5181d9539fa9c | [
"MIT"
] | 2 | 2019-04-05T05:20:43.000Z | 2020-02-18T13:56:06.000Z | README.md | kmui2/Multiple-Files-Renamer | 820e1b302ebb75d6aef7c9ede7c5181d9539fa9c | [
"MIT"
] | 3 | 2020-01-27T18:40:17.000Z | 2022-02-26T10:16:07.000Z | README.md | kmui2/Multiple-Files-Renamer | 820e1b302ebb75d6aef7c9ede7c5181d9539fa9c | [
"MIT"
] | null | null | null | # Multiple Files Renamer
Renames multiple files at once by replacing a substring of each filename using regex or matching a substring.
## Usage
To use this extension, hold CTRL/CMD and click on multiple files on the Explorer. Then, right clicking on one of them will display an option to rename the files.
| 44 | 161 | 0.792208 | eng_Latn | 0.999188 |
24d1da6d2ae6ac029b2a77511eb46d6d30968adf | 250 | md | Markdown | psych_metric/datasets/volcano/README.md | prijatelj/bayesian_eval_ground_truth-free | c0e569c78d63beb79f5e1e727c322293c3584323 | [
"MIT"
] | 1 | 2021-12-26T05:55:46.000Z | 2021-12-26T05:55:46.000Z | psych_metric/datasets/volcano/README.md | prijatelj/bayesian_eval_ground_truth-free | c0e569c78d63beb79f5e1e727c322293c3584323 | [
"MIT"
] | null | null | null | psych_metric/datasets/volcano/README.md | prijatelj/bayesian_eval_ground_truth-free | c0e569c78d63beb79f5e1e727c322293c3584323 | [
"MIT"
] | null | null | null | # Data Simulating the Volcano paper data
`Inferring Ground Truth from Subjective Labeling of Venus Images`
`Knowledge Discovery in Large Image Databases: Dealing with Uncertaintites in Ground Truth`
# Usage
See `example.ipynb` for example usage
| 22.727273 | 91 | 0.8 | eng_Latn | 0.907653 |
24d2e65121c21e18e51d1be1d22e1c57fbb6a9a6 | 237 | md | Markdown | doc/send_help/bark.md | jj1345/tk-auto-study | 284633ef302eb8cedaa8271f469148ed0509696d | [
"MIT"
] | 3 | 2021-12-27T07:58:39.000Z | 2022-03-15T01:58:36.000Z | doc/send_help/bark.md | jj1345/tk-auto-study | 284633ef302eb8cedaa8271f469148ed0509696d | [
"MIT"
] | 1 | 2022-03-31T12:59:08.000Z | 2022-03-31T12:59:08.000Z | doc/send_help/bark.md | jj1345/tk-auto-study | 284633ef302eb8cedaa8271f469148ed0509696d | [
"MIT"
] | null | null | null | # Bark推送服务教程
### Bark 推送未经过测试，请酌情使用并及时报告异常
使用方法请自行参考官方文档，需要自己部署后端服务器，不想折腾建议直接用server_chan：[点击跳转Bark官方仓库](https://github.com/Finb/bark-server#readme)
### 重要事项
配置Bark推送时，send_key需要遵循以下格式：
`url#key`
即把你自己的后台服务器地址填入最前面，使用`#`分割地址和key
| 14.8125 | 105 | 0.78481 | yue_Hant | 0.313746 |
24d37bacf8ba6a31b8c703ebd99bfccf6e7bc2ca | 9,698 | md | Markdown | README.md | 4us-dev/4us-utils | 57bc4abf6a4479160bb6d2aef645bcab03daaf44 | [
"MIT"
] | 2 | 2020-07-22T16:15:58.000Z | 2020-07-22T16:25:09.000Z | README.md | 4us-dev/4us-utils | 57bc4abf6a4479160bb6d2aef645bcab03daaf44 | [
"MIT"
] | 5 | 2020-12-04T21:14:38.000Z | 2021-09-23T17:33:15.000Z | README.md | 4us-dev/utils | 57bc4abf6a4479160bb6d2aef645bcab03daaf44 | [
"MIT"
] | null | null | null | # 4us-dev utils
[](https://sonarcloud.io/dashboard?id=4us-dev_utils)
[](https://sonarcloud.io/dashboard?id=4us-dev_utils)
[](https://sonarcloud.io/dashboard?id=4us-dev_utils)
[](https://sonarcloud.io/dashboard?id=4us-dev_utils)
[](https://sonarcloud.io/dashboard?id=4us-dev_utils)
[](https://sonarcloud.io/dashboard?id=4us-dev_utils)
[](https://www.npmjs.com/package/@4us-dev/utils)
[](/issues)
[](https://www.npmjs.com/package/@4us-dev/utils)
[](/LICENSE)
Install with [npm](https://www.npmjs.com/)
```sh
npm i @4us-dev/utils
```
## Usage
- [StringUtils](#stringutils)
- [isBlank and isNotBlank](#isblank-and-isnotblank)
- [isEmpty and isNotEmpty](#isempty-and-isnotempty)
- [hideEmail](#hideemail)
- [removeNonNumeric](#removenonnumeric)
- [isInteger](#isinteger)
- [isDouble](#isdouble)
- [RandomUtils](#randomutils)
- [nextInt](#nextint)
- [nextString](#nextstring)
- [nextStringCustom](#nextstringcustom)
- [FormatUtils](#formatutils)
- [formatCPF](#formatCPF)
- [formatCNPJ](#formatCNPJ)
- [formatPhone](#formatphone)
- [formatCEP](#formatCEP)
- [onlyIntegers](#onlyintegers)
- [BrazilianUtils](#validatorutils)
- [isCPF](#isCPF)
- [isCNPJ](#isCNPJ)
- [generateCPF](#generateCPF)
- [generateCNPJ](#generateCNPJ)
## Introduction
`@4us-dev/utils` is a lib with utility methods to help developers during software development. It is developed with best practices in mind and to facilitate unit testing of your code. So, it does not have any static method, thus facilitating the practice of mocks during tests when necessary.
## StringUtils
### `isBlank` and `isNotBlank`
isBlank return true if value is null, undefined, empty or string with only white spaces.
Examples:
```js
new StringUtils().isBlank(null); // true
new StringUtils().isBlank(undefined); // true
new StringUtils().isBlank(''); // true
new StringUtils().isBlank(' '); // true
new StringUtils().isBlank('a'); // false
```
`new StringUtils().isNotBlank(value)` is equal to `!new StringUtils().isBlank(value)`
### `isEmpty` and `isNotEmpty`
isEmpty return true if value is null, undefined, or empty.
Examples:
```js
new StringUtils().isEmpty(null); // true
new StringUtils().isEmpty(undefined); // true
new StringUtils().isEmpty(''); // true
new StringUtils().isEmpty(' '); // false
new StringUtils().isEmpty('a'); // false
```
`new StringUtils().isNotEmpty(value)` is equal to `!new StringUtils().isEmpty(value)`
### `hideEmail`
Hides part of the email.
You could hide the start and/or the end of email.
Examples:
Default configuration
```js
new StringUtils().hideEmail(`[email protected]`); // `[email protected]`
```
How ofuscate the ends of the email too
```js
new StringUtils().hideEmail(`[email protected]`, {
hideStart: true, // default true
hideEnd: true, // default false
}); // `f...@gma...`
```
If the `email` informed does not contains `@` or is `null` or `undefined`
the return of the method will be `undefined`
```js
new StringUtils().hideEmail(`fulano.com`); // undefined
new StringUtils().hideEmail(``); // undefined
new StringUtils().hideEmail(``); // undefined
new StringUtils().hideEmail(null); // undefined
```
### `removeNonNumeric`
Removes all non-numeric caracteres from string.
Examples:
```js
new StringUtils().removeNonNumeric('a1b2c3'); // '123'
```
### `isInteger`
Returns true if the value contains only numeric values
Examples:
```js
new StringUtils().isInteger('123'); // true
new StringUtils().isInteger('12.3'); // false
new StringUtils().isInteger('12,3'); // false
new StringUtils().isInteger('a1b2c3'); // false
new StringUtils().isInteger(' 123 '); // false
```
### `isDouble`
Returns true if the value into string is a double
Examples:
```js
new StringUtils().isDouble('123'); // true
new StringUtils().isDouble('12.3'); // true
new StringUtils().isDouble('12,3'); // false
new StringUtils().isDouble('a1b2c3'); // false
new StringUtils().isDouble(' 123 '); // false
```
## RandomUtils
### `nextInt`
Generates a random integer between the `min` and `max` inclusive.
Examples:
```js
// the return a integer between 0 and 100 inclusive
const value = new RandomUtils().getRandomInteger();
// the return can be one of this values 0, 1, 2 or 3
const value = new RandomUtils().getRandomInteger({ min: 0, max: 3 });
```
### `nextString`
Generates a random string.
Examples:
```js
// returns a random string with length 16
const value = new RandomUtils().nextString();
// returns a random string with length 8
const value = new RandomUtils().nextString({ length: 8 });
// returns a random string with length 8 only with letters upper, letters lower and numbers
const value = new RandomUtils().nextString({
length: 8, // default 16
upper: true, // default true ex: ABCDEF...
lower: true, // default true ex: abcdef...
numbers: true, // default true ex: 012345...
specialSimple: false, // default true ex: !#$%&*_+=-^~?;:.,|
specialAmbiguous: false, // default true ex: "()\'`´{[]}/><
});
```
### `nextStringCustom`
Generates a random string with `length` informed and using `caracteresAllowed` variable as reference.
Examples:
```js
// returns a random string with length 10 using only `A`, `1` or `c` to generate the result
const value = new RandomUtils().nextStringCustom(10, 'A1c');
```
## FormatUtils
### `formatCPF`
Removes all non-numeric values and apply the CPF mask.
Examples:
```js
const value = new FormatUtils().formatCPF('66273306010'); // "662.733.060-10"
```
This should format the CPF partially like this
```js
const value = new FormatUtils().formatCPF('6627330'); // "662.733.0"
```
If the value contains non-numeric characters they will be removed in formatting
```js
const value = new FormatUtils().formatCPF('66A27B33C060D10'); // "662.733.060-10"
```
### `formatCNPJ`
Removes all non-numeric values and apply the CNPJ mask.
Examples:
```js
const value = new FormatUtils().formatCNPJ('94338204000180'); // "94.338.204/0001-80"
```
This should format the CNPJ partially like this
```js
const value = new FormatUtils().formatCNPJ('9433820'); // "94.338.20"
```
If the value contains non-numeric characters they will be removed in formatting
```js
const value = new FormatUtils().formatCNPJ('943A382B04000C180'); // "94.338.204/0001-80"
```
### `formatPhone`
Removes all non-numeric values and apply the phone mask (99)9999-9999 or (99)99999-9999.
Examples:
```js
const value = new FormatUtils().formatPhone('85999432345'); // "(85)99943-2345"
const value = new FormatUtils().formatPhone('8599943234'); // "(85)9994-3234"
```
This should format the phone partially like this
```js
const value = new FormatUtils().formatPhone('8599943'); // "(85)9994-3"
```
If the value contains non-numeric characters they will be removed in formatting
```js
const value = new FormatUtils().formatPhone('A8B5C9D9f9g4h3i23s4w5q'); // "(85)99943-2345"
```
### `formatCEP`
Removes all non-numeric values and apply the CEP mask 99999-999
Examples:
```js
const value = new FormatUtils().formatPhone('60601023'); // "60601-023"
```
This should format the cep partially like this
```js
const value = new FormatUtils().formatPhone('606010'); // "60601-0"
```
If the value contains non-numeric characters they will be removed in formatting
```js
const value = new FormatUtils().formatPhone('A60b601c02D3E'); // "60601-023"
```
### `formatOnlyIntegers`
Removes all non-numeric caracteres from string.
Examples:
```js
const value = new FormatUtils().formatOnlyIntegers('a1b2c3'); // '123'060-10"
```
## BrazilianUtils
### `isCPF`
Return true when CPF is valid
Examples:
```js
const brazilianUtils = new BrazilianUtils();
```
```js
if (brazilianUtils.isCPF('66273306010')) {
console.log('CPF is valid');
} else {
console.log('CPF is not valid');
}
```
or
```js
if (brazilianUtils.isCPF('662.733.060-10')) {
console.log('CPF is valid');
} else {
console.log('CPF is not valid');
}
```
### `isCNPJ`
Return true when CNPJ is valid
Examples:
```js
const brazilianUtils = new BrazilianUtils();
```
```js
if (brazilianUtils.isCNPJ('94338204000180')) {
console.log('CNPJ is valid');
} else {
console.log('CNPJ is not valid');
}
```
or
```js
if (brazilianUtils.isCNPJ('94.338.204/0001-80')) {
console.log('CNPJ is valid');
} else {
console.log('CNPJ is not valid');
}
```
### `generateCPF`
Return a valid CPF
Examples:
```js
const brazilianUtils = new BrazilianUtils();
```
```js
const cpf = brazilianUtils.generateCPF();
```
### `generateCNPJ`
Return a valid CNPJ
Examples:
```js
const brazilianUtils = new BrazilianUtils();
```
```js
const cpf = brazilianUtils.generateCNPJ();
```
| 24.676845 | 292 | 0.703856 | eng_Latn | 0.505405 |
24d40a476dcf8acb1eda3744ed7154e470b434b4 | 5,435 | md | Markdown | articles/aks/view-metrics.md | Microsoft/azure-docs.sv-se | a43cb26da920952026f5e9c8720f3356a84de75b | [
"CC-BY-4.0",
"MIT"
] | 7 | 2017-08-28T08:02:11.000Z | 2021-05-05T07:47:55.000Z | articles/aks/view-metrics.md | MicrosoftDocs/azure-docs.sv-se | a43cb26da920952026f5e9c8720f3356a84de75b | [
"CC-BY-4.0",
"MIT"
] | 476 | 2017-10-15T08:20:18.000Z | 2021-04-16T05:20:11.000Z | articles/aks/view-metrics.md | MicrosoftDocs/azure-docs.sv-se | a43cb26da920952026f5e9c8720f3356a84de75b | [
"CC-BY-4.0",
"MIT"
] | 39 | 2017-08-03T09:46:48.000Z | 2021-11-05T11:41:27.000Z | ---
title: Visa kluster mått för Azure Kubernetes service (AKS)
description: Visa kluster mått för Azure Kubernetes service (AKS).
services: container-service
ms.topic: article
ms.date: 03/30/2021
ms.openlocfilehash: 32d8745e0ea780b5f86588fabdc25b244cf2cd8e
ms.sourcegitcommit: f5448fe5b24c67e24aea769e1ab438a465dfe037
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 03/30/2021
ms.locfileid: "105969510"
---
# <a name="view-cluster-metrics-for-azure-kubernetes-service-aks"></a>Visa kluster mått för Azure Kubernetes service (AKS)
AKS tillhandahåller en uppsättning mått för kontroll planet, inklusive API-servern och kluster autoskalning och klusternoder. Med dessa mått kan du övervaka hälso tillståndet för klustret och felsöka problem. Du kan visa måtten för klustret med hjälp av Azure Portal.
> [!NOTE]
> Dessa AKS-kluster mått överlappar en delmängd av [måtten som tillhandahålls av Kubernetes][kubernetes-metrics].
## <a name="view-metrics-for-your-aks-cluster-using-the-azure-portal"></a>Visa mått för ditt AKS-kluster med hjälp av Azure Portal
Så här visar du måtten för ditt AKS-kluster:
1. Logga in på [Azure Portal][azure-portal] och navigera till ditt AKS-kluster.
1. Välj *mått* på vänster sida under *övervakning*.
1. Skapa ett diagram för de mått som du vill visa. Skapa till exempel ett diagram:
1. För *omfång* väljer du klustret.
1. I *mått namn området* väljer du *behållar tjänst (hanterade) standard mått*.
1. För *mått*, under *poddar* väljer du *antal poddar per fas*.
1. För *agg regering* väljer du *AVG*.
:::image type="content" source="media/metrics/metrics-chart.png" alt-text="{alt-text}":::
Exemplet ovan visar måtten för det genomsnittliga antalet poddar för *myAKSCluster*.
## <a name="available-metrics"></a>Tillgängliga mått
Följande kluster mått är tillgängliga:
| Name | Group | ID | Beskrivning |
| --- | --- | --- | ---- |
| Synlighetssekvensnummer-begäranden | API-Server (för hands version) |apiserver_current_inflight_requests | Maximalt antal aktiva synlighetssekvensnummer-begäranden på API-servern per typ av begäran. |
| Klusterhälsa | Kluster autoskalning (för hands version) | cluster_autoscaler_cluster_safe_to_autoscale | Anger om en kluster autoskalning ska vidta åtgärder i klustret. |
| Skala ned cooldown | Kluster autoskalning (för hands version) | cluster_autoscaler_scale_down_in_cooldown | Anger om nedskalning är i cooldown-inga noder kommer att tas bort under denna tidsram. |
| Onödiga noder | Kluster autoskalning (för hands version) | cluster_autoscaler_unneeded_nodes_count | Klustret auotscaler markerar noderna som kandidater för borttagning och tas slutligen bort. |
| Unschedulable poddar | Kluster autoskalning (för hands version) | cluster_autoscaler_unschedulable_pods_count | Antalet poddar som för närvarande är unschedulable i klustret. |
| Totalt antal tillgängliga processor kärnor i ett hanterat kluster | Noder | kube_node_status_allocatable_cpu_cores | Totalt antal tillgängliga processor kärnor i ett hanterat kluster. |
| Total mängd tillgängligt minne i ett hanterat kluster | Noder | kube_node_status_allocatable_memory_bytes | Total mängd tillgängligt minne i ett hanterat kluster. |
| Status för olika nod villkor | Noder | kube_node_status_condition | Status för olika nod villkor |
| Millicores för processor användning | Noder (för hands version) | node_cpu_usage_millicores | Aggregerad mätning av processor användning i millicores över klustret. |
| Procent andel CPU-användning | Noder (för hands version) | node_cpu_usage_percentage | Aggregerad genomsnittlig processor användning mätt i procent över klustret. |
| RSS-byte för minne | Noder (för hands version) | node_memory_rss_bytes | RSS-minne för behållare som används i byte. |
| RSS-procent för minne | Noder (för hands version) | node_memory_rss_percentage | RSS-minne för behållare som används i procent. |
| Byte för arbets minne | Noder (för hands version) | node_memory_working_set_bytes | Arbets minne för behållare som används i byte. |
| Procent andel ledigt minne | Noder (för hands version) | node_memory_working_set_percentage | Arbets minne för behållare som används i procent. |
| Använda byte på disk | Noder (för hands version) | node_disk_usage_bytes | Disk utrymme som används i byte av enhet. |
| Procent andel använt disk utrymme | Noder (för hands version) | node_disk_usage_percentage | Disk utrymme som används i procent av enheten. |
| Nätverk i byte | Noder (för hands version) | node_network_in_bytes | Mottagna byte i nätverket. |
| Utgående byte för nätverk | Noder (för hands version) | node_network_out_bytes | Överförda byte i nätverket. |
| Antal poddar i klart läge | Poddar | kube_pod_status_ready | Antalet poddar i *klar* läge. |
| Antal poddar per fas | Poddar | kube_pod_status_phase | Antal poddar per fas. |
> [!IMPORTANT]
> Mått i för hands versionen kan uppdateras eller ändras, inklusive namn och beskrivningar, i för hands versionen.
## <a name="next-steps"></a>Nästa steg
Förutom kluster måtten för AKS kan du också använda Azure Monitor med ditt AKS-kluster. Mer information om hur du använder Azure Monitor med AKS finns i [Azure Monitor for containers][aks-azure-monitory].
[aks-azure-monitory]: ../azure-monitor/containers/container-insights-overview.md
[azure-portal]: https://portal.azure.com/
[kubernetes-metrics]: https://kubernetes.io/docs/concepts/cluster-administration/system-metrics/ | 74.452055 | 267 | 0.783809 | swe_Latn | 0.993203 |
24d524cec3e800a442d5987b388b25ed56e1b5a0 | 774 | md | Markdown | _posts/Algorithm/Programmers/2020-12-18-Algorithm78.md | daekyojeong/daekyojeong.github.io | f6d8d6a555fb284d95b9ec46966c438c74aea9ee | [
"MIT"
] | 1 | 2021-04-22T16:29:13.000Z | 2021-04-22T16:29:13.000Z | _posts/Algorithm/Programmers/2020-12-18-Algorithm78.md | daekyojeong/daekyojeong.github.io | f6d8d6a555fb284d95b9ec46966c438c74aea9ee | [
"MIT"
] | null | null | null | _posts/Algorithm/Programmers/2020-12-18-Algorithm78.md | daekyojeong/daekyojeong.github.io | f6d8d6a555fb284d95b9ec46966c438c74aea9ee | [
"MIT"
] | 1 | 2021-01-06T13:58:00.000Z | 2021-01-06T13:58:00.000Z | ---
title: "[알고리즘] 프로그래머스 - 폰켓몬"
author: Daekyo Jeong
date: 2020-12-18 20:00:00 +0900
categories: [Algorithm, Programmers]
tags: [Algorithm, Programmers, Python, Cpp]
math: true
---
<br/>
# **문제**
[폰켓몬](https://programmers.co.kr/learn/courses/30/lessons/1845)
<br/>
# **접근**
문제가 복잡해보이지만, 중복없이 최대한 많은 수를 선택하는 문제이다.
<br/>
# **코드**
- 파이썬 코드
```py
def solution(nums):
n = len(nums) // 2
num = set(nums)
answer = min(n, len(num))
return answer
```
- C++ 코드
```cpp
#include <vector>
#include <set>
#include <algorithm>
using namespace std;
int solution(vector<int> nums)
{
set<int> s;
for(int i = 0; i<nums.size();i++){
s.insert(nums[i]);
}
int answer = min(nums.size()/2, s.size());
return answer;
}
```
<br/>
| 12.9 | 62 | 0.580103 | kor_Hang | 0.606518 |
24d5e55ab51c947deeae40d42d8cc9b70e0b41d9 | 28,465 | md | Markdown | windows-apps-src/gaming/racing-wheel-and-force-feedback.md | Aaron-Junker/windows-uwp.de-de | 7171d224a4a27d04e54ab083568710e32235af3d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-apps-src/gaming/racing-wheel-and-force-feedback.md | Aaron-Junker/windows-uwp.de-de | 7171d224a4a27d04e54ab083568710e32235af3d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-apps-src/gaming/racing-wheel-and-force-feedback.md | Aaron-Junker/windows-uwp.de-de | 7171d224a4a27d04e54ab083568710e32235af3d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Rennlenkräder und Kraftrückmeldung
description: Verwenden Sie die Windows.Gaming.Input-APIs für Rennlenkräder, um Funktionen zu erkennen und zu ermitteln sowie Kraftrückmeldungsbefehle zu lesen und an Rennlenkräder zu senden.
ms.assetid: 6287D87F-6F2E-4B67-9E82-3D6E51CBAFF9
ms.date: 05/09/2018
ms.topic: article
keywords: Windows 10, UWP, Games, Rennrad, Erzwingen von Feedback
ms.localizationpriority: medium
ms.openlocfilehash: 0d92fe45a008ee0c3864355faf8133ab8e1ebefb
ms.sourcegitcommit: 7b2febddb3e8a17c9ab158abcdd2a59ce126661c
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 08/31/2020
ms.locfileid: "89163064"
---
# <a name="racing-wheel-and-force-feedback"></a>Rennlenkräder und Kraftrückmeldung
Auf dieser Seite werden die Grundlagen der Programmierung für Xbox One-Rennräder mithilfe von [Windows. Gaming. Input. racingwheel][racingwheel] und zugehörigen APIs für die universelle Windows-Plattform (UWP) beschrieben.
Auf dieser Seite erhalten Sie Informationen zu folgenden Vorgängen:
* Erfassen einer Liste mit verbundenen Rennrädern und ihren Benutzern
* erkennen, dass ein Rennrad hinzugefügt oder entfernt wurde
* Lesen von Eingaben von einem oder mehreren Rennrädern
* Wie Sie Kraftrückmeldungsbefehle senden
* Verhalten von Rennrädern als UI-Navigationsgeräte
## <a name="racing-wheel-overview"></a>Übersicht über Rennlenkräder
Rennlenkräder sind Eingabegeräte, die Benutzern das Gefühl vermitteln, in einem echten Rennwagencockpit zu sitzen. Rennlenkräder sind das ideale Eingabegerät für Rennsportspiele im Arcade- und Simulationsstil, die Autos oder Trucks enthalten. Rennlenkräder werden in Windows 10- und Xbox One-UWP-Apps durch den Namespace [Windows.Gaming.Input](/uwp/api/windows.gaming.input) unterstützt.
Xbox One-Rennräder werden zu einer Vielzahl von Preispunkten angeboten, die im Allgemeinen mehr und bessere Eingabe-und Erzwingungs Funktionen haben, wenn Ihre Preispunkte steigen. Alle Rennwagen sind mit einem analogen steuerungrad, einer analogen Drosselung und einem Brems Steuerelement und einigen Schaltflächen ausgestattet. Einige Rennwagen sind zusätzlich mit analogen Kupplungs-und Hand Shake Steuerelementen, mustershifters und Funktionen zum Erzwingen von Feedback ausgestattet. Nicht alle Rennwagen sind mit denselben Features ausgestattet und können auch Unterstützung für bestimmte Features unterstützen, z. b. können die Steuerelemente — verschiedene Bereiche der Drehung unterstützen, und mustershifter unterstützen möglicherweise eine unterschiedliche Anzahl von Gängen.
### <a name="device-capabilities"></a>Gerätefunktionen
Verschiedene Xbox One-Rennräder bieten unterschiedliche Sätze Optionaler Gerätefunktionen und unterschiedliche Unterstützungsstufen für diese Funktionen. Diese Abweichung zwischen einer einzelnen Art von Eingabegerät ist für die Geräte, die von der [Windows. Gaming. Input](/uwp/api/windows.gaming.input) -API unterstützt werden, eindeutig. Darüber hinaus unterstützen die meisten Geräte, denen Sie begegnen werden, zumindest einige optionale Funktionen oder andere Abweichungen. Aus diesem Grund ist es wichtig, die Funktionen jedes verbundenen Renn Rades einzeln zu bestimmen und die vollständige Variation der Funktionen zu unterstützen, die für Ihr Spiel sinnvoll sind.
Weitere Informationen finden Sie unter [Ermitteln von Rennlenkradfunktionen](#determining-racing-wheel-capabilities).
### <a name="force-feedback"></a>Kraftrückmeldung
Einige Xbox One-Rennräder bieten echte Rückmeldungen, d — . h., Sie können tatsächliche Erzwingungen auf eine Steuerungs Achse anwenden, z. b. das Mausrad, — nicht nur einfache Vibrationen. Spiele verwenden diese Möglichkeit, um einen besseren Einblick zu schaffen (_simulierte Absturz Schäden_, "Fahrverhalten") und die Herausforderung, eine gute Leistung zu erzielen.
Weitere Informationen finden Sie unter [Übersicht über die Kraftrückmeldung](#force-feedback-overview).
### <a name="ui-navigation"></a>Benutzeroberflächennavigation
Um den Aufwand für die Unterstützung unterschiedlicher Eingabegeräte für die Benutzeroberflächennavigation zu verringern und die Konsistenz zwischen Spielen und Geräten zu fördern, dienen die meisten _physischen_ Eingabegeräte gleichzeitig als getrennte _logische_ Eingabegeräte, die als [Benutzeroberflächen-Navigationscontroller](ui-navigation-controller.md) bezeichnet werden. Der Benutzeroberflächen-Navigationscontroller stellt ein gemeinsames Vokabular für Benutzeroberflächen-Navigationsbefehle über verschiedene Eingabegeräte hinweg bereit.
Aufgrund des einzigartigen Schwerpunkts auf die analogen Steuerelemente und den Grad der Variation zwischen verschiedenen Rennrädern sind Sie in der Regel mit einer digitalen D-Pad-, **Ansichts** **-,** **Menü**-, **B**-, **X**-und **Y** -Schaltfläche ausgestattet, die denen eines [Gamepad](gamepad-and-vibration.md)ähnelt. Diese Schaltflächen sind nicht zur Unterstützung von Spiel Befehlen gedacht und können nicht ohne weiteres als Mausrad-Schaltflächen aufgerufen werden
Bei einem UI-Navigations Controller werden die erforderlichen Navigations Befehle auf den Schalt [Flächen](ui-navigation-controller.md#required-set) Linker, D-Pad, **Ansicht**, **Menü**, **a**und **B** angezeigt.
| Navigationsbefehl | Rennlenkradeingabe |
| ------------------:| ------------------ |
| Nach oben | Steuerkreuz nach oben |
| Nach unten | Steuerkreuz nach unten |
| Left | Steuerkreuz nach links |
| Right | Steuerkreuz nach rechts |
| Sicht | Ansicht-Taste |
| Menü | Menü-Taste |
| Akzeptieren | A-Taste |
| Abbrechen | B-Taste |
Darüber hinaus ordnen einige Rennlenkräder möglicherweise einige [optionale](ui-navigation-controller.md#optional-set) Navigationsbefehle anderen von ihnen unterstützten Eingaben zu. Die Befehlszuordnungen können sich jedoch von Gerät zu Gerät unterscheiden. Sie sollten die Unterstützung dieser Befehle ebenfalls in Betracht ziehen, dabei jedoch sicherstellen, dass diese Befehle für die Navigation in der Benutzeroberfläche Ihres Spiels nicht notwendig sind.
| Navigationsbefehl | Rennlenkradeingabe |
| ------------------:| --------------------- |
| BILD-AUF | _variiert_ |
| BILD-AB | _variiert_ |
| Seite nach links | _variiert_ |
| Seite nach rechts | _variiert_ |
| Bildlauf nach oben | _variiert_ |
| Bildlauf nach unten | _variiert_ |
| Bildlauf nach links | _variiert_ |
| Bildlauf nach rechts | _variiert_ |
| Kontext 1 | X-Schaltfläche (_häufig_) |
| Kontext 2 | Y-Taste (_in der Regel_) |
| Kontext 3 | _variiert_ |
| Kontext 4 | _variiert_ |
## <a name="detect-and-track-racing-wheels"></a>Erkennen und Nachverfolgen von Rennlenkrädern
Das erkennen und Nachverfolgen von Rennrädern funktioniert genauso wie bei Gamepads, außer bei der Klasse " [racingwheel](/uwp/api/windows.gaming.input.racingwheel) " anstelle der [Gamepad](/uwp/api/Windows.Gaming.Input.Gamepad) -Klasse. Weitere Informationen finden Sie unter [Gamepad und Vibration](gamepad-and-vibration.md) .
<!-- Racing wheels are managed by the system, therefore you don't have to create or initialize them. The system provides a list of connected racing wheels and events to notify you when a racing wheel is added or removed.
### The racing wheels list
The [RacingWheel](/uwp/api/windows.gaming.input.racingwheel) class provides a static property, [RacingWheels](/uwp/api/windows.gaming.input.racingwheel.racingwheels#Windows_Gaming_Input_RacingWheel_RacingWheels), which is a read-only list of racing wheels that are currently connected. Because you might only be interested in some of the connected racing wheels, it's recommended that you maintain your own collection instead of accessing them through the `RacingWheels` property.
The following example copies all connected racing wheels into a new collection.
```cpp
auto myRacingWheels = ref new Vector<RacingWheel^>();
for (auto racingwheel : RacingWheel::RacingWheels)
{
// This code assumes that you're interested in all racing wheels.
myRacingWheels->Append(racingwheel);
}
```
### Adding and removing racing wheels
When a racing wheel is added or removed the [RacingWheelAdded](/uwp/api/windows.gaming.input.racingwheel.racingwheeladded) and [RacingWheelRemoved](/uwp/api/windows.gaming.input.racingwheel.racingwheelremoved) events are raised. You can register handlers for these events to keep track of the racing wheels that are currently connected.
The following example starts tracking an racing wheels that's been added.
```cpp
RacingWheel::RacingWheelAdded += ref new EventHandler<RacingWheel^>(Platform::Object^, RacingWheel^ args)
{
// This code assumes that you're interested in all new racing wheels.
myRacingWheels->Append(args);
}
```
The following example stops tracking a racing wheel that's been removed.
```cpp
RacingWheel::RacingWheelRemoved += ref new EventHandler<RacingWheel^>(Platform::Object^, RacingWheel^ args)
{
unsigned int indexRemoved;
if(myRacingWheels->IndexOf(args, &indexRemoved))
{
myRacingWheels->RemoveAt(indexRemoved);
}
}
```
### Users and headsets
Each racing wheel can be associated with a user account to link their identity to their gameplay, and can have a headset attached to facilitate voice chat or in-game features. To learn more about working with users and headsets, see [Tracking users and their devices](input-practices-for-games.md#tracking-users-and-their-devices) and [Headset](headset.md). -->
## <a name="reading-the-racing-wheel"></a>Lesen der Rennlenkradwerte
Nachdem Sie die für Sie interessanten Rennräder identifiziert haben, sind Sie bereit, Eingaben von Ihnen zu erfassen. Anders als im Fall anderer Eingaben, die Sie möglicherweise kennen, teilen Rennlenkräder Zustandsänderungen jedoch nicht durch das Auslösen von Ereignissen mit. Stattdessen nehmen Sie regelmäßige Messungen Ihrer aktuellen Zustände vor, indem Sie Sie _Abfragen_ .
### <a name="polling-the-racing-wheel"></a>Abrufen von Rennlenkrädern
Durch den Abruf wird eine Momentaufnahme des Rennlenkrads zu einem genau festgelegten Zeitpunkt erfasst. Diese Vorgehensweise für die Eingabe Erfassung eignet sich gut für die meisten Spiele, da ihre Logik in der Regel in einer deterministischen Schleife ausgeführt wird, anstatt Sie als ereignisgesteuert zu betrachten. Es ist in der Regel einfacher, Spiel Befehle aus Eingaben zu interpretieren, die alle gleichzeitig gesammelt werden, als aus vielen einzelnen Eingaben, die im Laufe der Zeit gesammelt werden.
Sie rufen ein Rennrad durch Aufrufen von [getcurrentreading](/uwp/api/windows.gaming.input.racingwheel.getcurrentreading#Windows_Gaming_Input_RacingWheel_GetCurrentReading); ab. Diese Funktion gibt ein [racingwheelreading](/uwp/api/windows.gaming.input.racingwheelreading) zurück, das den Zustand des Renn Rades enthält.
Im folgenden Beispiel wird der aktuelle Zustand eines Rennlenkrads abgerufen.
```cpp
auto racingwheel = myRacingWheels[0];
RacingWheelReading reading = racingwheel->GetCurrentReading();
```
Zusätzlich zum Zustand des Rennlenkrads enthält jede Ablesung einen Zeitstempel, der den genauen Zeitpunkt angibt, an dem der Zustand abgerufen wurde. Der Zeitstempel ist nützlich, um einen Bezug zu den Zeitpunkten vorheriger Ablesungen oder zum Zeitpunkt der Spielsimulation herzustellen.
### <a name="determining-racing-wheel-capabilities"></a>Ermitteln der Rennlenkradfunktionalität
Viele Steuerelemente eines Rennlenkrads sind optional oder unterstützen verschiedene Varianten. Da dies auch für erforderliche Steuerelemente gilt, müssen Sie die Funktionalität jedes Rennlenkrads einzeln ermitteln, bevor Sie die Eingaben verarbeiten können, die mit den Ablesungen des Rennlenkrads erfasst wurden.
Optionale Steuerelemente sind Handbremse, Kupplung und Gangschaltung. Sie können ermitteln, ob ein verbundenes Rennlenkrad diese Steuerelemente unterstützt, indem Sie die Eigenschaften [HasHandbrake](/uwp/api/windows.gaming.input.racingwheel.hashandbrake#Windows_Gaming_Input_RacingWheel_HasHandbrake), [HasClutch](/uwp/api/windows.gaming.input.racingwheel.hasclutch#Windows_Gaming_Input_RacingWheel_HasClutch) bzw. [HasPatternShifter](/uwp/api/windows.gaming.input.racingwheel.haspatternshifter#Windows_Gaming_Input_RacingWheel_HasPatternShifter) des Rennlenkrads lesen. Das-Steuerelement wird unterstützt, wenn der Wert der-Eigenschaft **true**ist. Andernfalls wird Sie nicht unterstützt.
```cpp
if (racingwheel->HasHandbrake)
{
// the handbrake is supported
}
if (racingwheel->HasClutch)
{
// the clutch is supported
}
if (racingwheel->HasPatternShifter)
{
// the pattern shifter is supported
}
```
Die Steuerelemente, deren Funktionalität variieren kann, sind das Lenkrad und die Gangschaltung. Das Lenkrad kann hinsichtlich des Umfangs der physischen Drehung variieren, die durch das tatsächliche Lenkrad unterstützt wird. Die Gangschaltung kann hinsichtlich der Zahl der einzelnen Vorwärtsgänge variieren, die unterstützt werden. Sie können den größten, durch das tatsächliche Lenkrad unterstützten Drehwinkel ermitteln, indem Sie die Eigenschaft `MaxWheelAngle` des Rennlenkrads lesen. Dessen Wert entspricht dem maximal unterstützten physischen Winkel im Uhrzeigersinn, ausgedrückt in Grad (positive Gradangabe). Der gleiche Drehwinkel wird in der dem Uhrzeigersinn entgegengesetzten Richtung unterstützt (negative Gradangabe). Sie können das größte Forward-Zahnrad festlegen, das der mustershifter unterstützt, indem Sie die- `MaxPatternShifterGear` Eigenschaft des-baurades lesen. sein Wert ist die höchste unterstützte Vorwärtsbewegung, d. h — ., wenn der Wert 4 ist, unterstützt der mustershifter umgekehrte, neutrale, erste, zweite, dritte und vierte Gänge.
```cpp
auto maxWheelDegrees = racingwheel->MaxWheelAngle;
auto maxShifterGears = racingwheel->MaxPatternShifterGear;
```
Schließlich unterstützen einige Rennlenkräder die Kraftrückmeldung über das Lenkrad. Sie können ermitteln, ob ein verbundenes Rennlenkrad die Kraftrückmeldung unterstützt, indem Sie die Eigenschaft [WheelMotor](/uwp/api/windows.gaming.input.racingwheel.wheelmotor#Windows_Gaming_Input_RacingWheel_WheelMotor) des Rennlenkrads lesen. Das Erzwingen von Feedback wird unterstützt `WheelMotor` , wenn nicht **null**ist; andernfalls wird es nicht unterstützt.
```cpp
if (racingwheel->WheelMotor != nullptr)
{
// force feedback is supported
}
```
Weitere Informationen dazu, wie Sie die Kraftrückmeldungsfunktion der Rennlenkräder verwenden, die dies unterstützen, finden Sie unter [Übersicht über die Kraftrückmeldung](#force-feedback-overview).
### <a name="reading-the-buttons"></a>Lesen der Tastenwerte
Jedes der Mausrad — Schaltflächen, die vier Richtungen des D-Pads, die **vorherigen Zahnrad** -und **nächsten Zahnrad** Schaltflächen und 16 zusätzliche Schaltflächen, — bietet ein digitales Lesematerial, das angibt, ob es gedrückt oder freigegeben wird (nach oben). Aus Effizienzgründen werden die Ablesewerte der Tasten nicht als einzelne boolesche Werte angezeigt, sondern in einem einzelnen Bitfeld zusammengefasst, dargestellt durch die Enumeration [RacingWheelButtons](/uwp/api/windows.gaming.input.racingwheelbuttons).
> [!NOTE]
> Starträder sind mit zusätzlichen Schaltflächen für die Benutzeroberflächen Navigation ausgestattet, z. b. die **Ansicht** und die **Menü** Schaltflächen. Diese Tasten sind nicht in der Enumeration `RacingWheelButtons` enthalten und können nur gelesen werden, wenn auf das Rennlenkrad als Benutzeroberflächen-Navigationsgerät zugegriffen wird. Weitere Informationen finden Sie unter [Benutzeroberflächen-Navigationsgerät](ui-navigation-controller.md).
Die Tastenwerte werden aus der Eigenschaft `Buttons` der Struktur [RacingWheelReading](/uwp/api/windows.gaming.input.racingwheelreading) gelesen. Da diese Eigenschaft ein Bitfeld ist, wird eine bitweise Maskierung verwendet, um den Wert der Taste zu isolieren, an der Sie interessiert sind, Wenn das entsprechende Bit festgelegt ist, wird die Schaltfläche gedrückt (unten). Andernfalls wird Sie freigegeben (up).
Im folgenden Beispiel wird ermittelt, ob die Taste **Nächster Gang** gedrückt ist.
```cpp
if (RacingWheelButtons::NextGear == (reading.Buttons & RacingWheelButtons::NextGear))
{
// Next Gear is pressed
}
```
Im folgenden Beispiel wird ermittelt, ob die Taste „Nächster Gang“ freigegeben ist.
```cpp
if (RacingWheelButtons::None == (reading.Buttons & RacingWheelButtons::NextGear))
{
// Next Gear is released (not pressed)
}
```
Manchmal möchten Sie möglicherweise ermitteln, ob eine Schaltfläche von gedrückter zu freigegeben oder freigegeben ist, ob mehrere Schaltflächen gedrückt oder freigegeben sind oder ob ein Satz von Schaltflächen auf eine bestimmte Weise angeordnet — ist, nicht. Weitere Informationen zum Ermitteln dieser Bedingungen finden Sie unter [Erkennen von Tastenübergängen](input-practices-for-games.md#detecting-button-transitions) und [Erkennen von komplexen Tastenanordungen](input-practices-for-games.md#detecting-complex-button-arrangements).
### <a name="reading-the-wheel"></a>Lesen der Lenkradwerte
Das Lenkrad ist ein erforderliches Steuerelement, das einen analogen Ablesewert zwischen -1,0 und +1,0 bereitstellt. Der Wert -1,0 entspricht der äußersten linken Lenkradposition. Der Wert +1,0 entspricht der äußersten rechten Lenkradposition. Der Wert für das Lenkrad wird aus der Eigenschaft `Wheel` der Struktur [RacingWheelReading](/uwp/api/windows.gaming.input.racingwheelreading) gelesen.
```cpp
float wheel = reading.Wheel; // returns a value between -1.0 and +1.0.
```
Auch wenn die Lenkradwerte dem Grad der physischen Drehung des tatsächlichen Lenkrads entsprechen, abhängig vom durch das physische Rennlenkrad unterstützten Drehbereich, sollten Sie die Lenkradwerte nicht skalieren. Lenkräder, die einen größeren Drehbereich unterstützen, bieten lediglich eine größere Genauigkeit.
### <a name="reading-the-throttle-and-brake"></a>Lesen der Gas- und Bremsensteuerelementwerte
Die Drosselung und die Bremse sind erforderliche Steuerelemente, die jeweils analoge Messwerte zwischen 0,0 (vollständig freigegeben) und 1,0 (vollständig gedrückt) bereitstellen, die als Gleit Komma Werte dargestellt werden. Der Wert für das Gassteuerelement wird aus der Eigenschaft `Throttle` der Struktur [RacingWheelReading](/uwp/api/windows.gaming.input.racingwheelreading) gelesen. Der Wert für das Bremsensteuerelement wird aus der Eigenschaft `Brake` gelesen.
```cpp
float throttle = reading.Throttle; // returns a value between 0.0 and 1.0
float brake = reading.Brake; // returns a value between 0.0 and 1.0
```
### <a name="reading-the-handbrake-and-clutch"></a>Lesen der Handbremsen- und Kupplungswerte
Die Handbremsen- und Kupplungssteuerelemente sind optionale Steuerelemente, die jeweils analoge Ablesewerte zwischen 0,0 (vollständig freigegeben) und 1,0 (vollständig gedrückt) bereitstellen, dargestellt als Gleitkommawerte. Der Wert für das Handbremsensteuerelement wird aus der Eigenschaft `Handbrake` der Struktur [RacingWheelReading](/uwp/api/windows.gaming.input.racingwheelreading) gelesen. Der Wert für das Kupplungssteuerelement wird aus der Eigenschaft `Clutch` gelesen.
```cpp
float handbrake = 0.0;
float clutch = 0.0;
if(racingwheel->HasHandbrake)
{
handbrake = reading.Handbrake; // returns a value between 0.0 and 1.0
}
if(racingwheel->HasClutch)
{
clutch = reading.Clutch; // returns a value between 0.0 and 1.0
}
```
### <a name="reading-the-pattern-shifter"></a>Lesen der Gangschaltungswerte
Die Gangschaltung ist ein optionales Steuerelement, das einen digitalen Wert zwischen -1 und [MaxPatternShifterGear](/uwp/api/windows.gaming.input.racingwheel.maxpatternshiftergear) bereitstellt, dargestellt als ganze Zahl mit Vorzeichen. Der Wert-1 oder 0 entspricht den _umgekehrten_ bzw. _neutralen_ Gängen. zunehmend positive Werte entsprechen den größeren vorwärts Gängen bis zu **maxpatternshiftergear**(einschließlich). Der Wert des mustershifter wird aus der Eigenschaft " [patternshibertergear](/uwp/api/windows.gaming.input.racingwheelreading.patternshiftergear) " der " [racingwheelreading](/uwp/api/windows.gaming.input.racingwheelreading) "-Struktur gelesen.
```cpp
if (racingwheel->HasPatternShifter)
{
gear = reading.PatternShifterGear;
}
```
> [!NOTE]
> Der Muster-Shifter, sofern er unterstützt wird, ist neben den erforderlichen **vorherigen** Zahnrad-und **nächsten Zahnrad** Schaltflächen vorhanden, die sich auch auf den aktuellen Gang des Players des Players auswirken. Eine einfache Strategie zum vereinheitlichen dieser Eingaben, bei denen beide vorhanden sind, besteht darin, den mustershifter (und die-Kupplung) zu ignorieren, wenn ein Player eine automatische Übertragung für das Auto auswählt und die **Schalt** Flächen "zurück" und "weiter" ignoriert, wenn ein Spieler eine manuelle Übertragung für das Fahrzeug auswählt, **Wenn das** Rennrad mit einem Muster Shifter Wenn dies für Ihr Spiel nicht geeignet ist, können Sie eine andere Strategie für die Zusammenführung implementieren.
## <a name="run-the-inputinterfacing-sample"></a>Ausführen des InputInterfacing-Beispiels
Das [InputInterfacingUWP-Beispiel _(github)_](https://github.com/Microsoft/Xbox-ATG-Samples/tree/master/Samples/System/InputInterfacingUWP) zeigt, wie Rennlenkräder und verschiedene Arten von Eingabegeräten zusammen verwendet werden und wie sich diese Eingabegeräte bei Verwendung als Benutzeroberflächen-Navigationscontroller verhalten.
## <a name="force-feedback-overview"></a>Übersicht über die Kraftrückmeldung
Viele Rennwagen verfügen über eine Funktion zum Erzwingen von Feedback, um eine immersive und schwierigere Fahrleistung zu bieten. Rennlenkräder, die die Kraftrückmeldung unterstützen, besitzen in der Regel einen einzelnen Motor, der entlang einer einzelnen Achse (der Achse der Lenkraddrehung) Kraft auf das Lenkrad ausübt. Das Erzwingen von Feedback wird in Windows 10-und Xbox One-UWP-Apps durch den [Windows. Gaming. Input. ForceFeedback](/uwp/api/windows.gaming.input.forcefeedback) -Namespace unterstützt.
> [!NOTE]
> Die APIs für das Erzwingen von Feedback können mehrere Achsen von Force unterstützen, aber kein Xbox One-Rennrad unterstützt derzeit keine Feedback Achse außer der Radrotation.
## <a name="using-force-feedback"></a>Verwenden der Kraftrückmeldung
In den folgenden Abschnitten werden die Grundlagen der Programmierung von Kraftrückmeldungseffekten für Xbox One-Rennlenkräder beschrieben. Die Rückmeldung wird mithilfe von Effekten angewendet, die zuerst in das Rückmeldungsgerät geladen und anschließend gestartet, angehalten, fortgesetzt und gestoppt werden können, ähnlich wie Soundeffekte. Sie müssen jedoch zunächst die Rückmeldungsfunktionalität des Rennlenkrads ermitteln.
### <a name="determining-force-feedback-capabilities"></a>Ermitteln der Kraftrückmeldungsfunktionalität
Sie können ermitteln, ob ein verbundenes Rennlenkrad die Kraftrückmeldung unterstützt, indem Sie die Eigenschaft [WheelMotor](/uwp/api/windows.gaming.input.racingwheel.wheelmotor#Windows_Gaming_Input_RacingWheel_WheelMotor) des Rennlenkrads lesen. Das Erzwingen von Feedback wird nicht unterstützt, wenn `WheelMotor` **null**ist. andernfalls wird das Erzwingen von Feedback unterstützt, und Sie können mit der Ermittlung der spezifischen Feedback Funktionen des Motors fortfahren, wie z. b. der Achsen, die sich
```cpp
if (racingwheel->WheelMotor != nullptr)
{
auto axes = racingwheel->WheelMotor->SupportedAxes;
if(ForceFeedbackEffectAxes::X == (axes & ForceFeedbackEffectAxes::X))
{
// Force can be applied through the X axis
}
if(ForceFeedbackEffectAxes::Y == (axes & ForceFeedbackEffectAxes::Y))
{
// Force can be applied through the Y axis
}
if(ForceFeedbackEffectAxes::Z == (axes & ForceFeedbackEffectAxes::Z))
{
// Force can be applied through the Z axis
}
}
```
### <a name="loading-force-feedback-effects"></a>Laden der Kraftrückmeldungseffekte
Die Kraftrückmeldungseffekte werden in das Rückmeldungsgerät geladen, auf dem sie autonom nach den Regeln Ihres Spiels „gespielt“ werden. Eine Reihe grundlegender Effekte werden bereitgestellt. benutzerdefinierte Effekte können über eine Klasse erstellt werden, die die [iforcefeedbackeffect](/uwp/api/windows.gaming.input.forcefeedback.iforcefeedbackeffect) -Schnittstelle implementiert.
| Effektklasse | Effektbeschreibung |
| -------------------- | -------------------------------------------------------------------------------------- |
| ConditionForceEffect | Ein Effekt, der als Reaktion auf den aktuellen Sensor im Gerät unterschiedliche Kraft anwendet. |
| ConstantForceEffect | Ein Effekt, der eine konstante Kraft entlang eines Vektors anwendet. |
| PeriodicForceEffect | Ein Effekt, der entlang eines Vektors unterschiedliche Kraft anwendet, definiert durch eine Waveform. |
| RampForceEffect | Ein Effekt, der eine linear zunehmende/abnehmende Kraft entlang eines Vektors anwendet. |
```cpp
using FFLoadEffectResult = ForceFeedback::ForceFeedbackLoadEffectResult;
auto effect = ref new Windows.Gaming::Input::ForceFeedback::ConstantForceEffect();
auto time = TimeSpan(10000);
effect->SetParameters(Windows::Foundation::Numerics::float3(1.0f, 0.0f, 0.0f), time);
// Here, we assume 'racingwheel' is valid and supports force feedback
IAsyncOperation<FFLoadEffectResult>^ request
= racingwheel->WheelMotor->LoadEffectAsync(effect);
auto loadEffectTask = Concurrency::create_task(request);
loadEffectTask.then([this](FFLoadEffectResult result)
{
if (FFLoadEffectResult::Succeeded == result)
{
// effect successfully loaded
}
else
{
// effect failed to load
}
}).wait();
```
### <a name="using-force-feedback-effects"></a>Verwenden von Kraftrückmeldungseffekten
Nach dem Laden können alle Effekte synchron durch das Aufrufen von Funktionen in der Eigenschaft `WheelMotor` des Rennlenkrads oder einzeln durch das Aufrufen von Funktionen im Rückmeldungseffekt selbst gestartet, angehalten, fortgesetzt und gestoppt werden. In der Regel sollten Sie alle Effekte, die Sie verwenden möchten, vor Beginn des Spiels in das Rückmeldungsgerät laden und anschließend die jeweiligen `SetParameters`-Funktionen verwenden,, um die Effekte im Verlauf des Spiels zu aktualisieren.
```cpp
if (ForceFeedbackEffectState::Running == effect->State)
{
effect->Stop();
}
else
{
effect->Start();
}
```
Sie können das gesamte Kraftrückmeldungssystem auf einem bestimmten Rennlenkrad jederzeit asynchron aktivieren, deaktivieren oder zurücksetzen.
## <a name="see-also"></a>Weitere Informationen
* [Windows.Gaming.Input.UINavigationController](/uwp/api/windows.gaming.input.uinavigationcontroller)
* [Windows.Gaming.Input.IGameController](/uwp/api/windows.gaming.input.igamecontroller)
* [Eingabemethoden für Spiele](input-practices-for-games.md)
[Windows.Gaming.Input]: /uwp/api/Windows.Gaming.Input
[Windows.Gaming.Input.UINavigationController]: /uwp/api/Windows.Gaming.Input.UINavigationController
[Windows.Gaming.Input.IGameController]: /uwp/api/Windows.Gaming.Input.IGameController
[racingwheel]: /uwp/api/Windows.Gaming.Input.RacingWheel
[racingwheels]: /uwp/api/Windows.Gaming.Input.RacingWheel
[racingwheeladded]: /uwp/api/Windows.Gaming.Input.RacingWheel
[racingwheelremoved]: /uwp/api/Windows.Gaming.Input.RacingWheel
[haspatternshifter]: /uwp/api/Windows.Gaming.Input.RacingWheel
[hashandbrake]: /uwp/api/Windows.Gaming.Input.RacingWheel
[hasclutch]: /uwp/api/Windows.Gaming.Input.RacingWheel
[maxpatternshiftergear]: /uwp/api/Windows.Gaming.Input.RacingWheel
[maxwheelangle]: /uwp/api/Windows.Gaming.Input.RacingWheel
[getcurrentreading]: /uwp/api/Windows.Gaming.Input.RacingWheel
[wheelmotor]: /uwp/api/Windows.Gaming.Input.RacingWheel
[racingwheelreading]: /uwp/api/Windows.Gaming.Input.RacingWheelReading
[racingwheelbuttons]: /uwp/api/Windows.Gaming.Input.RacingWheelButtons | 72.430025 | 1,074 | 0.784507 | deu_Latn | 0.98673 |
24d756a9f640b457e74d9010335456fe34a447d8 | 2,267 | md | Markdown | lib/declarative-code/README.md | JakeRowsell89/functional-programming | d00c59bfcda03dcd50efec36139c3c55d1541120 | [
"Unlicense"
] | 2 | 2021-03-31T11:47:13.000Z | 2021-03-31T11:51:03.000Z | lib/declarative-code/README.md | JakeRowsell89/functional-programming | d00c59bfcda03dcd50efec36139c3c55d1541120 | [
"Unlicense"
] | null | null | null | lib/declarative-code/README.md | JakeRowsell89/functional-programming | d00c59bfcda03dcd50efec36139c3c55d1541120 | [
"Unlicense"
] | null | null | null | # Declarative Code
## What?
Declarative code tries to put the emphasis on what should happen, rather than how it should happen. A good example is iterating through a collection using a .forEach as opposed to a for-loop. In the first case, we are only waying we want to apply a function to each argument. In the second, we are defining how it should step through an array and can then apply a function to individual contents.
Luckily, most modern languages ship with a lot of methods that make taking a declarative approach easier.
### DSLs
JavaScript doesn't easily allow this (though it is possible) but some languages make it easy to create another "language" within it. In this case we are specifically thinking about Domain Specific Languages. Some uses of this may be:
- Allow solutions to be expressed at the level of abstraction of the context domain
- Can help domain experts instead of software engineers contribute to development
- Can be easy to learn as they tend to be small
- The DSL can be declarative
Take a look at Cucumber with one of the SDETS
## Why?
In the example provided we only get small benefits. No looping means less chance of a bug introduced by looping incorrectly. It also is clear immediately what something does, instead of needing to look inside the loop and try to figure that out.
Taking this concept a bit outside of the JavaScript context though, we could look at technologies like Terraform and Kubernetes.
We declaratively define what we want and the tools figure out HOW to achieve that. You need to configure it properly, but you aren't working out ordering of resource creation, dependencies, handling waiting for things to complete. That would be a nightmare, and that is the power that these tools offer. A less bad nightmare (haha, jk I love you both). You declare you need an S3 bucket, an IAM role and a bucket policy, terraform goes and creates it for you.
The aim is to abstract away the generalities in a different context than the specifics. Or to take Terraform as an example again, the generality being "how is resource X created" vs the specific of "I need a resource X that ties to resource Y in account Z". To compare it with OOP, it is a bit like separating the interface and the implementation.
| 83.962963 | 460 | 0.790031 | eng_Latn | 0.999911 |
24d795b5ae102de959dfb512287285b8f2076536 | 1,704 | md | Markdown | articles/＜摇光＞在两个极端之间徘徊/post.md | ibeidou/- | eaa99dc0f4daad16bf06ba1c5e0cb14579a8a3ef | [
"MIT"
] | 58 | 2018-05-06T17:41:51.000Z | 2022-03-10T18:12:00.000Z | articles/＜摇光＞在两个极端之间徘徊/post.md | megaxianzhengblog/ibeidou-articles | eaa99dc0f4daad16bf06ba1c5e0cb14579a8a3ef | [
"MIT"
] | null | null | null | articles/＜摇光＞在两个极端之间徘徊/post.md | megaxianzhengblog/ibeidou-articles | eaa99dc0f4daad16bf06ba1c5e0cb14579a8a3ef | [
"MIT"
] | 14 | 2018-05-08T00:58:30.000Z | 2021-06-02T22:00:42.000Z | # ＜摇光＞在两个极端之间徘徊
**为什么到现在都没有一个体制让人们一下就觉得这是政治发展的终极体制？我们认为美国的民主政治好，是因为我们不是权力分离制衡的体制；我们认为西欧的福利体制好，是因为我们的医疗产业化，教育产业化。去看美国和西欧，几乎天天都有抨击自己政治体制的人。所以我不相信有什么终极的体制出现。体制会随着人民的意愿变迁。**
# 在两个极端之间徘徊
## 文/ 尼莫
今天看了《浪潮》。总觉得应该写点什么，为那些逝去的日子。我感受过一群志同道合的人集体同心，一起去为了理想做一件事情带来的那种高效和愉悦，也正在感受一个人合理安排时间做自己想做的事情的惬意与自由。我很感谢有这样的体验，才对独裁主义（对应集体）和无政府主义（对应个人），进而对人性有了比较透彻的理解。
有一个故事说一个人死后，到了一个地方，发现有无穷无尽的山珍海味，都是他生前梦寐以求想得到的东西，于是很高兴，感谢上苍让自己来到了天堂。于是吃啊吃，感觉非常舒服。过了几天，觉得有点腻，再过了几个月，都想吐了。于是找到了把他带来的人，问，天堂里有事情可以做吗？回答说，你来的是地狱，在这里无事可做，除了吃。
所以最可怕的，是没有变化。好与坏都是相对的，都不能单独存在。政客在讲台上义愤填膺的演讲，抨击这个抨击那个，但这种演讲一般是速朽的。就像美国经济萧条时需要凯恩斯，经济繁荣时需要哈耶克；也像打天下时需要专政，坐天下时需要民主。
为什么到现在都没有一个体制让人们一下就觉得这是政治发展的终极体制？我们认为美国的民主政治好，是因为我们不是权力分离制衡的体制；我们认为西欧的福利体制好，是因为我们的医疗产业化，教育产业化。去看美国和西欧，几乎天天都有抨击自己政治体制的人。所以我不相信有什么终极的体制出现。体制会随着人民的意愿变迁。回到1949年，应该绝大多数人都相信gcd执政会给中国带来光明的未来；到现在几乎是180度的转变。我相信有了1966年，才有了1978年，也才有了1984年，也才有了现在。很多历史的偶然事件，其实都是群体选择的必然。而我们这个世界，就在一个一个群体选择中延续着。在好的社会里能动态的自洽，保持一直都处于大多数人感觉到的最舒适状态；在不好的社会里能促成变革，以一种剧烈的形式重回舒适状态。然而什么是好与不好的临界点，没有人知道。
[](d9317eea-57aa-41bf-ab93-92afba4cd74c.jpg)
就像《浪潮》里的那个老师的困惑一样。他领导了学生创立了浪潮，并殚精竭虑的设计了很多事情，包括到最后那一出精彩的先扬后抑的演讲。在他认为局势仍然在自己掌控之中并即将把不好的态势拉回到正常状态时，惨剧出现了。那个曾经给成员带来自豪感，荣誉感和归属感的组织，到最后带来了恐惧和灾难。
所以我钦佩那些思维敏锐的人。如电影中的那一对男女朋友，如马克思，如哈耶克，也如瞿秋白（《多余的话》）。在似乎只有一种声音时，他们察觉到了问题，并发出不一样的声音。这些声音促使我们身体里的某一部分苏醒，并在以后的岁月里日渐活跃，慢慢的由小众发展为大众，最终改变历史。所以我们每个人，都是矛盾的综合体，也只有“痛并快乐着”的幸福，才会真正成为记忆中磨灭不了的幸福。
从这个角度看，我们并不在真正追求某种“主义”，我们追求的只是自身的和谐。“主义”与“信仰”好像不是一个层次的东西。主义总伴随着要求他人与自己一同相信，而信仰却只是自己的追随。而信仰宗教和信仰主义也不是一回事。宗教信仰的对象是神，是此生无法抵达的彼岸的世界，因此其倾向是向内发力，让自己能够净化来达到神灵的认可；主义却通常被认为是现实世界可以达到的状态，因此更多的会向外发力，靠改变他人改变世界来达到主义的实现。
大多数人，都是在缺失时寻找，在拥有中漠视，在自由时渴望集体，在束缚中谋求独立。我们总在为自己寻找下一步需要解决的问题，从这里面挖掘并赋予自身生命的意义。
（采编：陈锴；责编：陈锴）
| 42.6 | 362 | 0.867958 | zho_Hans | 0.699894 |
24d9f2c768e5f80db2396bec0db069ff3de6d3c5 | 760 | md | Markdown | _project/laundry-room-door-laundry-room-door-ideas-adding-a-frosted-glass-door-to-a-laundry.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | _project/laundry-room-door-laundry-room-door-ideas-adding-a-frosted-glass-door-to-a-laundry.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | _project/laundry-room-door-laundry-room-door-ideas-adding-a-frosted-glass-door-to-a-laundry.md | rumnamanya/rumnamanya.github.io | 2deadeff04c8a48cf683b885b7fa6ab9acc1d9d9 | [
"MIT"
] | null | null | null | ---
layout: project_single
title: "Laundry room door. Laundry room door ideas. Adding a frosted glass door to a laundry room is always a smart idea; especially for those busy week days where piles of laundry is being done. The door keeps the noise contained and any mess out of sight. "
slug: "laundry-room-door-laundry-room-door-ideas-adding-a-frosted-glass-door-to-a-laundry"
parent: "laundry-room-tile-design-ideas"
---
Laundry room door. Laundry room door ideas. Adding a frosted glass door to a laundry room is always a smart idea; especially for those busy week days where piles of laundry is being done. The door keeps the noise contained and any mess out of sight. Glass and stencil Laundry room door #Laundryroomdoor #Laundryroom Soda Pop Design Inc. | 108.571429 | 336 | 0.788158 | eng_Latn | 0.997395 |
24db79919c000b7a2dc5aebde3451e174fe4065a | 854 | md | Markdown | _posts/2018-12-13-error-travisci-awss3-connect.md | knittinglove/gmlwjd9405.github.io | 656d51bea45de67ee4ed7dcff81ea8b2412ba040 | [
"MIT"
] | 68 | 2018-05-22T12:37:56.000Z | 2022-03-30T05:38:04.000Z | _posts/2018-12-13-error-travisci-awss3-connect.md | knittinglove/gmlwjd9405.github.io | 656d51bea45de67ee4ed7dcff81ea8b2412ba040 | [
"MIT"
] | 6 | 2019-02-12T09:37:27.000Z | 2019-08-29T01:48:35.000Z | _posts/2018-12-13-error-travisci-awss3-connect.md | knittinglove/gmlwjd9405.github.io | 656d51bea45de67ee4ed7dcff81ea8b2412ba040 | [
"MIT"
] | 77 | 2018-07-27T06:48:26.000Z | 2022-03-31T07:42:19.000Z | ---
layout: post
title: '[Error] Travis CI와 AWS s3 연동 시 오류'
subtitle: 'Oops, It looks like you tried to write to a bucket ...'
date: 2018-12-13
author: heejeong Kwon
cover: '/images/error/error-main.png'
tags: travis-ci aws error
comments: true
sitemap :
changefreq : daily
priority : 1.0
---
## 오류 내용
`Oops, It looks like you tried to write to a bucket that isn't yours or doesn't exist yet. Please create the bucket before trying to write to it.`
* 
## 해결 방법
1. AWS s3 버킷 퍼블릭 액세스 설정
* 
2. 새 퍼블릭 ACL 및 퍼블릭 객체 업로드 차단 - **체크 해제** 후 저장
* 
<!-- # 관련된 Post
* []() -->
# References
> - [https://github.com/jojoldu/blog-comments/issues/8](https://github.com/jojoldu/blog-comments/issues/8) | 25.878788 | 146 | 0.685012 | kor_Hang | 0.805965 |
24dbe25cf3aa4c073afc8144ac9a7df28fe4bd5b | 43 | md | Markdown | README.md | MichaelDiers/shared-workflows | e41142a3ba8ff0c75d9a5e67c4266e4e338a5489 | [
"MIT"
] | null | null | null | README.md | MichaelDiers/shared-workflows | e41142a3ba8ff0c75d9a5e67c4266e4e338a5489 | [
"MIT"
] | null | null | null | README.md | MichaelDiers/shared-workflows | e41142a3ba8ff0c75d9a5e67c4266e4e338a5489 | [
"MIT"
] | null | null | null | # shared-workflows
shared github workflows
| 14.333333 | 23 | 0.837209 | eng_Latn | 0.999038 |
24dcb5824caa26240cf51c34954959ac93984e3c | 639 | md | Markdown | README.md | morazow/ScaldingExamples | a9f0fd79b9a492004417ff3de42cb63f63c0bda8 | [
"Apache-2.0"
] | null | null | null | README.md | morazow/ScaldingExamples | a9f0fd79b9a492004417ff3de42cb63f63c0bda8 | [
"Apache-2.0"
] | null | null | null | README.md | morazow/ScaldingExamples | a9f0fd79b9a492004417ff3de42cb63f63c0bda8 | [
"Apache-2.0"
] | null | null | null | # Scalding Examples
This is repository of code examples shown in my [blog
posts](http://morazow.com/archive.html) about
[Scalding](https://github.com/twitter/scalding).
## Running Locally
```
> sbt run
```
## Running on Hadoop
First create 'fat jar' then run on Hadoop environment.
```
> sbt assembly
```
It will create fat jar with name **ScaldingExamples-1.0.jar** under
**target/scala-2.10/ScaldingExamples-1.0.jar**.
Run on Hadoop cluster giving proper input/output paths,
```
> hadoop/yarn jar ScaldingExamples-1.0.jar JobClassName \
--hdfs \
--input /hdfs/input/path/to/file \
--output /hdfs/output/path/
```
| 23.666667 | 67 | 0.699531 | eng_Latn | 0.764605 |
24de0e04b3d530472c4a47522eaa0e77e4fc2a8a | 1,042 | md | Markdown | translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md | Plotta/docs | dfc135a2bf91be244db6de86003348719a7e8cad | [
"CC-BY-4.0",
"MIT"
] | 11,698 | 2020-10-07T16:22:18.000Z | 2022-03-31T18:54:47.000Z | translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md | Husky57/docs | 1d590a4feb780b0acc9a41381e721b61146175db | [
"CC-BY-4.0",
"MIT"
] | 8,317 | 2020-10-07T16:26:58.000Z | 2022-03-31T23:24:25.000Z | translations/es-ES/data/reusables/github-actions/self-hosted-runner-labels-runs-on.md | Waleedalaedy/docs | 26d4b73dcbb9a000c32faa37234288649f8d211a | [
"CC-BY-4.0",
"MIT"
] | 48,204 | 2020-10-07T16:15:45.000Z | 2022-03-31T23:50:42.000Z | Para especificar un ejecutor auto-hospedado para tu trabajo, configura `runs-on` en tu archivo de flujo de trabajo con las etiquetas de dicho ejecutor.
Todos los ejecutores auto-hospedados tienen la etiqueta `self-hosted`. El utilizar únicamente esta etiqueta seleccionará cualquier ejecutor auto-hospedado. Para seleccionar los ejecutores que cumplen con ciertos criterios, tales como el sistema operativo o arquitectura, te recomendamos proporcionar un arreglo de etiquetas que comience con `self-hosted` (este se debe listar primero) y que luego incluya etiquetas adicionales conforme lo requieras. Cuando especifiques un arreglo de etiquetas, los jobs se pondrán en cola cuando se trate de ejecutores que tengan todas las etiquetas que especificas.
Aunque la etiqueta de `self-hosted` no se requiere, te recomendamos ampliamente especificarla cuando utilices ejecutores auto-hospedados para garantizar que tu trabajo no especifique algún ejecutor hospedado en {% data variables.product.prodname_dotcom %} futuro o actual por accidente.
| 173.666667 | 600 | 0.829175 | spa_Latn | 0.997435 |
24de9093b50bde6a04ca46875cf1f94ef3958fd2 | 410 | md | Markdown | README.md | quickbytesio/003-custom-keys-codable | e57f68bd869e8bda88f7f5100484e0a0313d8bdd | [
"MIT"
] | null | null | null | README.md | quickbytesio/003-custom-keys-codable | e57f68bd869e8bda88f7f5100484e0a0313d8bdd | [
"MIT"
] | null | null | null | README.md | quickbytesio/003-custom-keys-codable | e57f68bd869e8bda88f7f5100484e0a0313d8bdd | [
"MIT"
] | null | null | null | # Quickbytes
This project is a code sample that accompanies a tutorial that explains <a href='https://www.quickbytes.io/admin/tutorials/custom-keys-in-codable'>Custom Keys in Codable</a>.
## Tool Versions
Built with:
* macOS High Sierra
* Xcode 9.2
* iOS 11.2
* Swift 4.0
| 27.333333 | 174 | 0.763415 | eng_Latn | 0.556516 |
24dea978cba639df455f1a37f068b08adee32006 | 285 | md | Markdown | _collections/_biblio/van_damme_time-optimized_2020.md | AGrigis/baobab | 2d6f425e380346d69ba7fde0a449e8f7490fe5c7 | [
"CC-BY-3.0"
] | 2 | 2020-06-26T12:13:47.000Z | 2020-06-26T13:25:47.000Z | _collections/_biblio/van_damme_time-optimized_2020.md | AGrigis/baobab | 2d6f425e380346d69ba7fde0a449e8f7490fe5c7 | [
"CC-BY-3.0"
] | 3 | 2020-07-17T16:19:29.000Z | 2021-01-27T07:51:47.000Z | _collections/_biblio/van_damme_time-optimized_2020.md | AGrigis/baobab | 2d6f425e380346d69ba7fde0a449e8f7490fe5c7 | [
"CC-BY-3.0"
] | 4 | 2020-12-28T09:29:39.000Z | 2022-01-25T13:18:31.000Z | ---
cat: metric
subcat: metric
bestof: false
author: L. Van Damme et al.
title: Time-optimized universal non-selective pulses for 7T MRI with parallel transmission
year: 2020
type: inproceedings
booktitle: Proceedings of the International Society for Magnetic Resonance in Medicine
--- | 28.5 | 90 | 0.8 | eng_Latn | 0.734348 |
24debf2f2a0453a35efecfdf107696ddbdafde50 | 1,149 | md | Markdown | content/ja/problems/IOL/2008/1.md | fulfom/kotohazi | bf192b52f9bd82c1da07934869fe088543e6275a | [
"Apache-2.0"
] | 5 | 2020-08-07T09:52:21.000Z | 2022-03-16T04:12:52.000Z | content/ja/problems/IOL/2008/1.md | fulfom/kotohazi | bf192b52f9bd82c1da07934869fe088543e6275a | [
"Apache-2.0"
] | 18 | 2020-07-22T21:00:37.000Z | 2021-07-30T19:56:47.000Z | content/ja/problems/IOL/2008/1.md | fulfom/kotohazi | bf192b52f9bd82c1da07934869fe088543e6275a | [
"Apache-2.0"
] | null | null | null | ---
title: "IOL2008-1 ミクマク語"
weight: 33
type: docs
pagetype: prob
description: "翻訳・ヒント・解答・解説のまとめ"
problems:
- 33
---
{{% hasProbdata id=33 key="introduction" %}}
## 紹介
{{% problems/introduction id=33 %}}{{% /hasProbdata %}}
## 情報
{{% problems/probcard id=33 detailed=true %}}{{% hasProbdata id=33 key="probcorrection" %}}
### 問題訂正
{{% probdata id=33 key="probcorrection" %}}{{% /hasProbdata %}}{{% hasProbdata id=33 key="translation" %}}
### 翻訳・注釈
{{% problems/translation id=33 %}}{{% /hasProbdata %}}{{% hasProbdata id=33 key="hint" %}}
## ヒント
{{% problems/hint id=33 %}}{{% /hasProbdata %}}
## 解答
[解答]({{% probdata id=33 key="solution" default="link" %}}){{% hasProbdata id=33 key="solcorrection" %}}
### 解答訂正
{{% collapse title="解答訂正" %}}
{{% probdata id=33 key="solcorrection" %}}
{{% /collapse %}}{{% /hasProbdata %}}
## 解説
{{% hasProbdata id=33 key="sketch" %}}
{{% problems/sketch id=33 %}}
{{% /hasProbdata %}}{{% hasProbdata id=33 key="explanationlinks" %}}
### 詳しい解説
{{% problems/explanationLinks id=33 %}}{{% /hasProbdata %}}
## 関連記事
{{< problems/relatedarticle id=33 >}}
## 類題
{{< problems/relatedprob id=33 >}}
| 19.15 | 106 | 0.610096 | eng_Latn | 0.082188 |
24df08182b0897be4fd0fdba9ab7bbe85ca30b74 | 2,002 | md | Markdown | _posts/2017-06-07-Gulp构造工具使用.md | devin-huang/devin-huang.github.io | 3db7ad6a99f4ddb690fd7efe3adb060aea203ccc | [
"MIT"
] | 6 | 2018-02-08T07:02:31.000Z | 2021-01-18T10:53:08.000Z | _posts/2017-06-07-Gulp构造工具使用.md | devin-huang/devin-huang.github.io | 3db7ad6a99f4ddb690fd7efe3adb060aea203ccc | [
"MIT"
] | null | null | null | _posts/2017-06-07-Gulp构造工具使用.md | devin-huang/devin-huang.github.io | 3db7ad6a99f4ddb690fd7efe3adb060aea203ccc | [
"MIT"
] | 1 | 2019-07-03T04:30:31.000Z | 2019-07-03T04:30:31.000Z | ---
layout: post
title: Gulp构造工具使用
subtitle: 让程序猿更专注于开发
date: 2017-06-12
author: BY Devin
header-img: img/post-bg-ios9-web.jpg
catalog: true
tags:
- Gulp
- 构造工具
---
#### 前言
- gulp能为我们简单解决下列事项：
1.开发环境下，想要能够按模块组织代码，监听实时变化
2.CSS、JS预编译，postcss等方案，浏览器前缀自动补全等
3.条件输出不同的网页，比如app页面和mobile页面
4.线上环境下，我想要合并、压缩 html/css/javascritp/图片，减少网络请求，同时降低网络负担等
#### 使用流程
- 注意：
- 一、安装nodejs
1.安装：nodejs官网 **https://nodejs.org/en/** 绿色Download按钮，它会根据系统信息选择对应版本（.msi文件），然后傻瓜式安装；
2.开启命令提示符；
3.查看是否安装成功：命令提示符输入-> `node -v` 与 `npm -v`（npm是在安装nodejs同时安装的nodejs包管理器）；
- 二、全局安装Gulp
1.安装：命令提示符执行`npm install gulp -g`
2.查看是否安装成功：命令提示符输入->`gulp-v `
- 三、新建项目文件夹
1.创建一个名称为test项目，这里以F盘为例；
2.新建pageage.json：命令提示符执行`npm init`
name:项目名称 （填写）
varsion：项目版本（填写）
description：项目描述（填写）
- 四、本地安装Gulp
安装：项目根目录命令提示符执行`npm install gulp --save-dev `
查看是否安装成功：项目文件中生成** node_modules **文件
全局安装gulp是为了执行gulp任务，本地安装gulp则是为了调用gulp插件的功能
- 五、本地安装Gulp插件
注意：
1.首先安装-> `npm install [email protected]` 防止红字报错[email protected]则(其他文件不存在也需要安装)
2.路径转向指定项目根目录F/text
3.安装：命令提示符执行:
```
npm install gulp-concat gulp-rename gulp-jshint gulp-compass gulp-html-minify gulp-clean-css gulp-uglify gulp-imagemin gulp-tinypng-nokey gulp-clean gulp-rev gulp-rev-collector gulp-babel babel-core babel-preset-env --save-dev
```
查看是否安装成功：查看package.json；
- 六、新建gulpfile文件 并 执行 gulp
参考gulpfile.js文件CODE； [https://devin-huang.github.io/img/pubilc/gulpfile.js](/img/pubilc/gulpfile.js)
路径转向指定项目文件: cd D:\test
执行Gulp：命令提示符执行 all 、default 、 gulp ->分别为运行对应的任务
- 完成后的项目目录：
sass-cache/dist会使用Gulp后自动生成;
[gulpfile.js](/img/pubilc/gulpfile.js)
| 20.02 | 243 | 0.616384 | yue_Hant | 0.148966 |
24e1a591e25e11bbfffe85a445a42c82d601f56d | 12,701 | md | Markdown | articles/azure-functions/durable/durable-functions-monitor.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-08-10T02:23:39.000Z | 2019-08-10T02:23:40.000Z | articles/azure-functions/durable/durable-functions-monitor.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-functions/durable/durable-functions-monitor.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Dayanıklı işlevler - Azure izleyicileri
description: Bir Durum izleyicisini, Azure işlevleri için dayanıklı işlevler uzantısını kullanarak uygulamayı öğrenin.
services: functions
author: ggailey777
manager: jeconnoc
keywords: ''
ms.service: azure-functions
ms.devlang: multiple
ms.topic: conceptual
ms.date: 12/07/2018
ms.author: azfuncdf
ms.openlocfilehash: 9d5e06c3d72d87a87b41a52ed4df369ebc04dccd
ms.sourcegitcommit: d4dfbc34a1f03488e1b7bc5e711a11b72c717ada
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 06/13/2019
ms.locfileid: "66387090"
---
# <a name="monitor-scenario-in-durable-functions---weather-watcher-sample"></a>Dayanıklı işlevler - hava durumu İzleyicisi örnek senaryoda izleyin
İzleyici deseni esnek bir başvuruyor *yinelenen* bir iş akışında - Örneğin, belirli koşulların karşılanması kadar yoklama işlemi. Bu makalede kullanan bir örnek açıklanmaktadır [dayanıklı işlevler](durable-functions-overview.md) izleme uygulamak için.
[!INCLUDE [durable-functions-prerequisites](../../../includes/durable-functions-prerequisites.md)]
## <a name="scenario-overview"></a>Senaryoya genel bakış
Bu örnek, bir konumun geçerli hava koşulları izler ve bir kullanıcı tarafından SMS skies açık olduğunda uyarır. Normal bir Zamanlayıcı ile tetiklenen işlev hava durumunu denetleyin ve uyarıları göndermek için kullanabilirsiniz. Ancak, bu yaklaşım ile ilgili bir sorun olduğunu **ömür Yönetimi**. Yalnızca bir uyarı gönderilmesi gereken kendisini Temizle sonra devre dışı bırakmak izleyicinin hava durumu algılandı. İzleme desen, diğer avantajlarının yanı sıra kendi yürütme sona erdirilebilir:
* İzleyiciler, belirli aralıklarla çalıştırmak olmayan zamanlar: Zamanlayıcı tetikleyicisi *çalıştıran* saatte; bir izleyici *bekler* eylemler arasında bir saat. Bir izleyicinin eylemleri belirtilmediği sürece, uzun süre çalışan görevler için önemli olabilir çakışmaması.
* İzleyicilerle dinamik aralıkları: bekleme süresine bağlı olarak bazı koşullar değiştirebilirsiniz.
* Bazı koşullar karşılanması veya başka bir işlem tarafından sonlandırılacak izleyiciler sonlandırabilirsiniz.
* İzleyiciler, parametre alabilir. Tüm istenen konumu ve telefon numarası aynı hava durumu izleme işlemini nasıl uygulanabileceğini örnek gösterir.
* İzleyiciler ölçeklenebilir. Her bir izleyici bir düzenleme örneği olduğundan, birden çok monitör yeni işlevler oluşturun veya daha fazla kod tanımlamak zorunda kalmadan oluşturulabilir.
* İzleyiciler, daha büyük iş akışlarınızla kolayca tümleştirin. Bir izleyici daha karmaşık bir düzenleme işlevinin bir bölümü olabilir veya [alt düzenleme](durable-functions-sub-orchestrations.md).
## <a name="configuring-twilio-integration"></a>Twilio tümleştirmesi yapılandırma
[!INCLUDE [functions-twilio-integration](../../../includes/functions-twilio-integration.md)]
## <a name="configuring-weather-underground-integration"></a>Hava durumu Yeraltı tümleştirmesini yapılandırma
Bu örnek, bir konum için geçerli hava durumu koşullarını denetlemek için hava durumu Yeraltı API kullanmayı içerir.
İhtiyacınız olan ilk şey bir hava durumu Yeraltı hesabıdır. Ücretsiz, oluşturabilirsiniz [ https://www.wunderground.com/signup ](https://www.wunderground.com/signup). Hesabınızı edindikten sonra bir API anahtarı alma gerekecektir. Ziyaret ederek bunu [ https://www.wunderground.com/weather/api ](https://www.wunderground.com/weather/api/?MR=1), anahtar ayarlarını seçildikten sonra. Stratus Geliştirici planı ücretsizdir ve bu örneği çalıştırmak yeterli kullanılabilir.
Bir API anahtarı aldıktan sonra aşağıdaki ekleyin **uygulama ayarı** işlev uygulamanız için.
| Uygulama ayarı adı | Değer Açıklama |
| - | - |
| **WeatherUndergroundApiKey** | Hava durumu Yeraltı API anahtarınızı. |
## <a name="the-functions"></a>İşlevleri
Bu makalede örnek uygulama aşağıdaki işlevler açıklanmaktadır:
* `E3_Monitor`: Çağıran bir düzenleyici işlevi `E3_GetIsClear` düzenli aralıklarla. Çağrı `E3_SendGoodWeatherAlert` varsa `E3_GetIsClear` true değerini döndürür.
* `E3_GetIsClear`: Bir konum için geçerli hava koşulları denetler etkinlik işlevi.
* `E3_SendGoodWeatherAlert`: Twilio aracılığıyla SMS iletisi gönderen bir etkinlik işlev.
Aşağıdaki bölümlerde, betik C# ve JavaScript için kullanılan kod ve yapılandırma açıklanmaktadır. Visual Studio geliştirme için kod makalenin sonunda gösterilir.
## <a name="the-weather-monitoring-orchestration-visual-studio-code-and-azure-portal-sample-code"></a>Düzenleme (Visual Studio Code ve Azure portalı örnek kodu) izleme hava durumu
**E3_Monitor** işlevini kullanan standart *function.json* orchestrator işlevleri için.
[!code-json[Main](~/samples-durable-functions/samples/csx/E3_Monitor/function.json)]
İşlev uygulayan kod şu şekildedir:
### <a name="c"></a>C#
[!code-csharp[Main](~/samples-durable-functions/samples/csx/E3_Monitor/run.csx)]
### <a name="javascript-functions-2x-only"></a>JavaScript (yalnızca 2.x işlevleri)
[!code-javascript[Main](~/samples-durable-functions/samples/javascript/E3_Monitor/index.js)]
Bu orchestrator işlevi aşağıdaki eylemleri gerçekleştirir:
1. Alır **MonitorRequest** oluşan *konumu* izlemek için ve *telefon numarası* için hangi SMS bildirimi gönderir.
2. İzleyici zaman aşımı süresini belirler. Örnek, bir sabit kodlu değer konuyu uzatmamak amacıyla kullanır.
3. Çağrıları **E3_GetIsClear** istenen konuma Temizle skies olup olmadığını belirlemek için.
4. Hava durumu, boş olduğunda, çağıran **E3_SendGoodWeatherAlert** istenen telefon numarasına SMS bildirimi göndermek için.
5. Sonraki yoklama aralığı sırasında orchestration sürdürmek için kalıcı bir zamanlayıcı oluşturur. Örnek, bir sabit kodlu değer konuyu uzatmamak amacıyla kullanır.
6. Kadar çalışmaya devam eder [CurrentUtcDateTime](https://azure.github.io/azure-functions-durable-extension/api/Microsoft.Azure.WebJobs.DurableOrchestrationContext.html#Microsoft_Azure_WebJobs_DurableOrchestrationContext_CurrentUtcDateTime) (C#) veya `currentUtcDateTime` geçirir izleyicinin sona erme saati (JavaScript) veya SMS uyarı gönderilir.
Birden çok orchestrator örnekleri aynı anda birden çok göndererek çalışabilir **MonitorRequests**. İzlemek istediğiniz konumu ve telefon numarası için SMS uyarısı göndermek için belirtilebilir.
## <a name="strongly-typed-data-transfer-net-only"></a>Kesin türü belirtilmiş veri aktarımı (yalnızca .NET)
Orchestrator bu nedenle, verilerin birden çok parça gerektirir [POCO nesneleri paylaşılan](../functions-reference-csharp.md#reusing-csx-code) C# ve C# betiği kesin türü belirtilmiş veri aktarımı için kullanılır:
[!code-csharp[Main](~/samples-durable-functions/samples/csx/shared/MonitorRequest.csx)]
[!code-csharp[Main](~/samples-durable-functions/samples/csx/shared/Location.csx)]
JavaScript örnek normal JSON nesneleri parametreler olarak kullanır.
## <a name="helper-activity-functions"></a>Yardımcı etkinlik işlevleri
Diğer örneklerle yardımcı etkinlik işlevleri kullanan normal işlevlerde olduğu gibi `activityTrigger` bağlama tetikleyin. **E3_GetIsClear** işlevi hava durumu Yeraltı API'sini kullanarak geçerli hava koşulları alır ve sky açık olup olmadığını belirler. *Function.json* şu şekilde tanımlanır:
[!code-json[Main](~/samples-durable-functions/samples/csx/E3_GetIsClear/function.json)]
Ve burada uygulamasıdır. Veri aktarımı için kullanılan POCOs gibi API işlemek için mantığı çağırın ve JSON paylaşılan bir sınıf C# içinde soyutlanır yanıtı ayrıştıramadı. Bir parçası olarak bulabilirsiniz [Visual Studio örnek kodu](#run-the-sample).
### <a name="c"></a>C#
[!code-csharp[Main](~/samples-durable-functions/samples/csx/E3_GetIsClear/run.csx)]
### <a name="javascript-functions-2x-only"></a>JavaScript (yalnızca 2.x işlevleri)
[!code-javascript[Main](~/samples-durable-functions/samples/javascript/E3_GetIsClear/index.js)]
**E3_SendGoodWeatherAlert** işlevi, son kullanıcının bir ilerlemesi için uygun bir zaman olduğunu bildiren bir SMS mesajı göndermek için Twilio bağlama kullanır. Kendi *function.json* basittir:
[!code-json[Main](~/samples-durable-functions/samples/csx/E3_SendGoodWeatherAlert/function.json)]
Ve SMS mesajı gönderir kod aşağıdaki gibidir:
### <a name="c"></a>C#
[!code-csharp[Main](~/samples-durable-functions/samples/csx/E3_SendGoodWeatherAlert/run.csx)]
### <a name="javascript-functions-2x-only"></a>JavaScript (yalnızca 2.x işlevleri)
[!code-javascript[Main](~/samples-durable-functions/samples/javascript/E3_SendGoodWeatherAlert/index.js)]
## <a name="run-the-sample"></a>Örneği çalıştırma
Örnekte bulunan bir HTTP tetiklemeli işlevleri'ni kullanarak, aşağıdaki HTTP POST isteği göndererek düzenleme başlayabilirsiniz:
```
POST https://{host}/orchestrators/E3_Monitor
Content-Length: 77
Content-Type: application/json
{ "location": { "city": "Redmond", "state": "WA" }, "phone": "+1425XXXXXXX" }
```
```
HTTP/1.1 202 Accepted
Content-Type: application/json; charset=utf-8
Location: https://{host}/admin/extensions/DurableTaskExtension/instances/f6893f25acf64df2ab53a35c09d52635?taskHub=SampleHubVS&connection=Storage&code={SystemKey}
RetryAfter: 10
{"id": "f6893f25acf64df2ab53a35c09d52635", "statusQueryGetUri": "https://{host}/admin/extensions/DurableTaskExtension/instances/f6893f25acf64df2ab53a35c09d52635?taskHub=SampleHubVS&connection=Storage&code={systemKey}", "sendEventPostUri": "https://{host}/admin/extensions/DurableTaskExtension/instances/f6893f25acf64df2ab53a35c09d52635/raiseEvent/{eventName}?taskHub=SampleHubVS&connection=Storage&code={systemKey}", "terminatePostUri": "https://{host}/admin/extensions/DurableTaskExtension/instances/f6893f25acf64df2ab53a35c09d52635/terminate?reason={text}&taskHub=SampleHubVS&connection=Storage&code={systemKey}"}
```
**E3_Monitor** örneği başlatır ve istenilen konum için geçerli hava koşulları sorgular. Hava durumu boş olduğunda bir uyarı göndermek için bir etkinlik işlevi çağırır; Aksi takdirde, bir zamanlayıcı olarak ayarlar. Süreölçerdeki Süre dolduğunda düzenleme devam edecek.
Azure işlevleri portalda konumundaki işlev bakarak düzenleme ait etkinlik günlükleri görebilirsiniz.
```
2018-03-01T01:14:41.649 Function started (Id=2d5fcadf-275b-4226-a174-f9f943c90cd1)
2018-03-01T01:14:42.741 Started orchestration with ID = '1608200bb2ce4b7face5fc3b8e674f2e'.
2018-03-01T01:14:42.780 Function completed (Success, Id=2d5fcadf-275b-4226-a174-f9f943c90cd1, Duration=1111ms)
2018-03-01T01:14:52.765 Function started (Id=b1b7eb4a-96d3-4f11-a0ff-893e08dd4cfb)
2018-03-01T01:14:52.890 Received monitor request. Location: Redmond, WA. Phone: +1425XXXXXXX.
2018-03-01T01:14:52.895 Instantiating monitor for Redmond, WA. Expires: 3/1/2018 7:14:52 AM.
2018-03-01T01:14:52.909 Checking current weather conditions for Redmond, WA at 3/1/2018 1:14:52 AM.
2018-03-01T01:14:52.954 Function completed (Success, Id=b1b7eb4a-96d3-4f11-a0ff-893e08dd4cfb, Duration=189ms)
2018-03-01T01:14:53.226 Function started (Id=80a4cb26-c4be-46ba-85c8-ea0c6d07d859)
2018-03-01T01:14:53.808 Function completed (Success, Id=80a4cb26-c4be-46ba-85c8-ea0c6d07d859, Duration=582ms)
2018-03-01T01:14:53.967 Function started (Id=561d0c78-ee6e-46cb-b6db-39ef639c9a2c)
2018-03-01T01:14:53.996 Next check for Redmond, WA at 3/1/2018 1:44:53 AM.
2018-03-01T01:14:54.030 Function completed (Success, Id=561d0c78-ee6e-46cb-b6db-39ef639c9a2c, Duration=62ms)
```
Orchestration olacak [sonlandırmak](durable-functions-instance-management.md) , zaman aşımı ulaşıldığında veya açık olduğunda skies algılanır. Ayrıca `TerminateAsync` (.NET) veya `terminate` (JavaScript) içinde başka bir işlev veya çağırma **terminatePostUri** yukarıda değiştirerek 202 yanıtının başvurulan bir HTTP POST Web kancası `{text}` nedeni ile sonlandırma:
```
POST https://{host}/admin/extensions/DurableTaskExtension/instances/f6893f25acf64df2ab53a35c09d52635/terminate?reason=Because&taskHub=SampleHubVS&connection=Storage&code={systemKey}
```
## <a name="visual-studio-sample-code"></a>Visual Studio örnek kod
Tek bir C# dosyası olarak Visual Studio projesi içinde düzenleme şu şekildedir:
> [!NOTE]
> Yüklemek ihtiyacınız olacak `Microsoft.Azure.WebJobs.Extensions.Twilio` aşağıdaki örnek kodu çalıştırmak için Nuget paketi.
[!code-csharp[Main](~/samples-durable-functions/samples/precompiled/Monitor.cs)]
## <a name="next-steps"></a>Sonraki adımlar
Bu örnek, bir dış kaynağının durumunu izlemek için dayanıklı işlevler kullanmayı gösterilmiştir kullanarak [dayanıklı zamanlayıcılar](durable-functions-timers.md) ve koşul mantığı. Sonraki örnek, dış olayları kullanma işlemi gösterilmektedir ve [dayanıklı zamanlayıcılar](durable-functions-timers.md) insan etkileşimi işlemek için.
> [!div class="nextstepaction"]
> [İnsan etkileşimi örneği çalıştırma](durable-functions-phone-verification.md)
| 66.497382 | 615 | 0.808204 | tur_Latn | 0.997306 |
24e1e238fea8ee424d76e735af51e278c33793a8 | 923 | md | Markdown | javascript/code-challenges/hashMap/README.md | simon-panek/data-structures-and-algorithms | 08f1dc659c37a2535cf39e67f293e37407a3f8f1 | [
"MIT"
] | null | null | null | javascript/code-challenges/hashMap/README.md | simon-panek/data-structures-and-algorithms | 08f1dc659c37a2535cf39e67f293e37407a3f8f1 | [
"MIT"
] | 15 | 2020-12-08T00:26:53.000Z | 2021-01-16T05:02:41.000Z | javascript/code-challenges/hashMap/README.md | simon-panek/data-structures-and-algorithms | 08f1dc659c37a2535cf39e67f293e37407a3f8f1 | [
"MIT"
] | null | null | null | # Hashtables
A hash table or hash map stores key/value pairs as a node within a linked list that is stored in an array. The array index position for any key is provided by a repeatable hash calculation performed on the key.
## Author: Simon Panek
### Collaborators: Mariko, Ricardo, Stacy, Garret, Tamina, Ashley
## Challenge
Define a hash map class with the following methods: hash, set, get, & contains.
## Approach & Efficiency
- `hash()` --> Performs a calculation on a given key that turns it into a single repeatable integer and operates with an efficiency of O(1).
- `set()` --> Adds a key/value pair to the hash table and does so with an efficiency of O(n).
- `get()` --> Returns a value for a given key and does so with an efficiency of O(n).
- `contains()` --> Returns a boolean given a key. Returns true if the key currently exists in the hash map and false if not. This method has an efficiency of O(n).
| 48.578947 | 210 | 0.731311 | eng_Latn | 0.999189 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.