hexsha stringlengths 40 40 | size int64 5 1.04M | ext stringclasses 6 values | lang stringclasses 1 value | max_stars_repo_path stringlengths 3 344 | max_stars_repo_name stringlengths 5 125 | max_stars_repo_head_hexsha stringlengths 40 78 | max_stars_repo_licenses listlengths 1 11 | max_stars_count int64 1 368k ⌀ | max_stars_repo_stars_event_min_datetime stringlengths 24 24 ⌀ | max_stars_repo_stars_event_max_datetime stringlengths 24 24 ⌀ | max_issues_repo_path stringlengths 3 344 | max_issues_repo_name stringlengths 5 125 | max_issues_repo_head_hexsha stringlengths 40 78 | max_issues_repo_licenses listlengths 1 11 | max_issues_count int64 1 116k ⌀ | max_issues_repo_issues_event_min_datetime stringlengths 24 24 ⌀ | max_issues_repo_issues_event_max_datetime stringlengths 24 24 ⌀ | max_forks_repo_path stringlengths 3 344 | max_forks_repo_name stringlengths 5 125 | max_forks_repo_head_hexsha stringlengths 40 78 | max_forks_repo_licenses listlengths 1 11 | max_forks_count int64 1 105k ⌀ | max_forks_repo_forks_event_min_datetime stringlengths 24 24 ⌀ | max_forks_repo_forks_event_max_datetime stringlengths 24 24 ⌀ | content stringlengths 5 1.04M | avg_line_length float64 1.14 851k | max_line_length int64 1 1.03M | alphanum_fraction float64 0 1 | lid stringclasses 191 values | lid_prob float64 0.01 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6ffa327521494f84af43ef3176677905d887a899 | 766 | md | Markdown | docs/framework/wcf/diagnostics/etw/3415-websocketconnectionrequestsendstart.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/diagnostics/etw/3415-websocketconnectionrequestsendstart.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/diagnostics/etw/3415-websocketconnectionrequestsendstart.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "3415 - WebSocketConnectionRequestSendStart"
ms.custom: ""
ms.date: "03/30/2017"
ms.prod: ".net-framework"
ms.reviewer: ""
ms.suite: ""
ms.technology:
- "dotnet-clr"
ms.tgt_pltfrm: ""
ms.topic: "article"
ms.assetid: 2fdf39ec-3aad-45bf-ba80-759e6e10fe37
caps.latest.revision: 3
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
ms.workload:
- "dotnet"
---
# 3415 - WebSocketConnectionRequestSendStart
## Properties
|||
|-|-|
|ID|3415|
|Keywords|HTTP|
|Level|Verbose|
|Channel|Microsoft-Windows-Application Server-Applications/Debug|
## Description
This event is emitted when WebSocket connection request to send has started.
## Message
WebSocket connection request to '%1' send start.
## Details
| 20.702703 | 79 | 0.70235 | eng_Latn | 0.364936 |
6ffa8be282f504cd16002cc7a80ef7369d5cf5ff | 40,993 | md | Markdown | README.md | mcdoker18/fortio | b10c5c5d54715c5b59f5be1c14f1faa55bb7c8bf | [
"Apache-2.0"
] | null | null | null | README.md | mcdoker18/fortio | b10c5c5d54715c5b59f5be1c14f1faa55bb7c8bf | [
"Apache-2.0"
] | null | null | null | README.md | mcdoker18/fortio | b10c5c5d54715c5b59f5be1c14f1faa55bb7c8bf | [
"Apache-2.0"
] | null | null | null | # Fortio
[](https://github.com/avelino/awesome-go#networking)
[](https://goreportcard.com/report/fortio.org/fortio)
[](https://godoc.org/fortio.org/fortio)
[](https://codecov.io/gh/fortio/fortio)
[](https://circleci.com/gh/fortio/fortio)
[](https://hub.docker.com/r/fortio/fortio)
[](https://hub.docker.com/r/fortio/fortio)
<img src="https://fortio.org/fortio-logo-color.png" height=141 width=141 align=right>
Fortio (Φορτίο) started as, and is, [Istio](https://istio.io/)'s load testing tool and now graduated to be its own project.
Fortio is also used by, among others, [Meshery](https://meshery.layer5.io/docs/extensibility#which-are-currently-supported)
Fortio runs at a specified query per second (qps) and records an histogram of execution time
and calculates percentiles (e.g. p99 ie the response time such as 99% of the requests take less than that number (in seconds, SI unit)).
It can run for a set duration, for a fixed number of calls, or until interrupted (at a constant target QPS, or max speed/load per connection/thread).
The name fortio comes from greek [φορτίο](https://fortio.org/fortio.mp3) which means load/burden.
Fortio is a fast, small (3Mb docker image, minimal dependencies), reusable, embeddable go library as well as a command line tool and server process,
the server includes a simple web UI and graphical representation of the results (both a single latency graph and a multiple results comparative min, max, avg, qps and percentiles graphs).
Fortio also includes a set of server side features (similar to httpbin) to help debugging and testing: request echo back including headers, adding latency or error codes with a probability distribution, tcp echoing, tcp proxying, http fan out/scatter and gather proxy server, GRPC echo/health in addition to http, etc...
Fortio is quite mature and very stable with no known major bugs (lots of possible improvements if you want to contribute though!),
and when bugs are found they are fixed quickly, so after 1 year of development and 42 incremental releases, we reached 1.0 in June 2018.
Fortio components can be used a library even for unrelated projects, for instance the `log`, `stats`, or `fhttp` utilities both client and server.
As well as the newly integrated [Dynamic Flags](dflag/) support (greatly inspired/imported initially from https://github.com/mwitkow/go-flagz)
## Installation
1. [Install go](https://golang.org/doc/install) (golang 1.14 or later)
2. `go get fortio.org/fortio`
3. you can now run `fortio` (from your gopath bin/ directory)
Or use docker, for instance:
```shell
docker run -p 8080:8080 -p 8079:8079 fortio/fortio server & # For the server
docker run fortio/fortio load http://www.google.com/ # For a test run
```
Or download one of the binary distributions, from the [releases](https://github.com/fortio/fortio/releases) assets page or for instance:
```shell
curl -L https://github.com/fortio/fortio/releases/download/v1.15.2/fortio-linux_x64-1.15.2.tgz \
| sudo tar -C / -xvzpf -
# or the debian package
wget https://github.com/fortio/fortio/releases/download/v1.15.2/fortio_1.15.2-1_amd64.deb
dpkg -i fortio_1.15.2-1_amd64.deb
# or the rpm
rpm -i https://github.com/fortio/fortio/releases/download/v1.15.2/fortio-1.15.2-1.x86_64.rpm
```
On a MacOS you can also install Fortio using [Homebrew](https://brew.sh/):
```shell
brew install fortio
```
On Windows, download https://github.com/fortio/fortio/releases/download/v1.15.2/fortio_win_1.15.2.zip and extract all to some location then using the Windows Command Prompt:
```
cd fortio
fortio.exe server
```
(at the prompt, allow the windows firewall to let connections in)
Once `fortio server` is running, you can visit its web UI at [http://localhost:8080/fortio/](http://localhost:8080/fortio/)
You can get a preview of the reporting/graphing UI at [https://fortio.istio.io/](https://fortio.istio.io/)
and on [istio.io/docs/performance-and-scalability/synthetic-benchmarks/](https://istio.io/docs/performance-and-scalability/synthetic-benchmarks/)
## Command line arguments
Fortio can be an http or grpc load generator, gathering statistics using the `load` subcommand,
or start simple http and grpc ping servers, as well as a basic web UI, result graphing, tcp/udp echo, proxies, https redirector,
with the `server` command or issue grpc ping messages using the `grpcping` command.
It can also fetch a single URL's for debugging when using the `curl` command (or the `-curl` flag to the load command).
Likewise you can establish a single TCP (or unix domain or UDP (use `udp://` prefix)) connection using the `nc` command (like the standalone netcat package).
You can run just the redirector with `redirect` or just the tcp echo with `tcp-echo`.
If you saved JSON results (using the web UI or directly from the command line), you can browse and graph those results using the `report` command.
The `version` command will print version and build information, `fortio version -s` just the version.
Lastly, you can learn which flags are available using `help` command.
Most important flags for http load generation:
| Flag | Description, example |
| -------------|----------------------|
| `-qps rate` | Queries Per Seconds or 0 for no wait/max qps |
| `-c connections` | Number of parallel simultaneous connections (and matching go routine) |
| `-t duration` | How long to run the test (for instance `-t 30m` for 30 minutes) or 0 to run until ^C, example (default 5s) |
| `-n numcalls` | Run for exactly this number of calls instead of duration. Default (0) is to use duration (-t). |
| `-r resolution` | Resolution of the histogram lowest buckets in seconds (default 0.001 i.e 1ms), use 1/10th of your expected typical latency |
| `-H "header: value"` | Can be specified multiple times to add headers (including Host:) |
| `-a` | Automatically save JSON result with filename based on labels and timestamp |
| `-json filename` | Filename or `-` for stdout to output json result (relative to `-data-dir` by default, should end with .json if you want `fortio report` to show them; using `-a` is typicallly a better option)|
| `-labels "l1 l2 ..."` | Additional config data/labels to add to the resulting JSON, defaults to target URL and hostname|
You can switch from http GET queries to POST by setting `-content-type` or passing one of the `-payload-*` option.
Full list of command line flags (`fortio help`):
<details>
<!-- use release/updateFlags.sh to update this section -->
<pre>
Φορτίο 1.15.2 usage:
fortio command [flags] target
where command is one of: load (load testing), server (starts ui, http-echo,
redirect, proxies, tcp-echo and grpc ping servers), tcp-echo (only the tcp-echo
server), report (report only UI server), redirect (only the redirect server),
proxies (only the -M and -P configured proxies), grpcping (grpc client),
or curl (single URL debug), or nc (single tcp or udp:// connection).
where target is a url (http load tests) or host:port (grpc health test).
flags are:
-H header
Additional header(s)
-L Follow redirects (implies -std-client) - do not use for load test
-M value
Http multi proxy to run, e.g -M "localport1 baseDestURL1 baseDestURL2"
-M ...
-P value
Tcp proxies to run, e.g -P "localport1 dest_host1:dest_port1" -P
"[::1]:0 www.google.com:443" ...
-a Automatically save JSON result with filename based on labels & timestamp
-abort-on code
Http code that if encountered aborts the run. e.g. 503 or -1 for socket
errors.
-allow-initial-errors
Allow and don't abort on initial warmup errors
-base-url URL
base URL used as prefix for data/index.tsv generation. (when empty, the
url from the first request is used)
-c int
Number of connections/goroutine/threads (default 4)
-cacert Path
Path to a custom CA certificate file to be used for the GRPC client
TLS, if empty, use https:// prefix for standard internet CAs TLS
-cert Path
Path to the certificate file to be used for GRPC server TLS
-compression
Enable http compression
-config path
Config directory path to watch for changes of dynamic flags (empty for
no watch)
-content-type string
Sets http content type. Setting this value switches the request method
from GET to POST.
-curl
Just fetch the content once
-data-dir Directory
Directory where JSON results are stored/read (default ".")
-echo-debug-path URI
http echo server URI for debug, empty turns off that part (more secure)
(default "/debug")
-echo-server-default-params value
Default parameters/querystring to use if there isn't one provided
explicitly. E.g "status=404&delay=3s"
-gomaxprocs int
Setting for runtime.GOMAXPROCS, <1 doesn't change the default
-grpc
Use GRPC (health check by default, add -ping for ping) for load testing
-grpc-max-streams uint
MaxConcurrentStreams for the grpc server. Default (0) is to leave the
option unset.
-grpc-ping-delay duration
grpc ping delay in response
-grpc-port port
grpc server port. Can be in the form of host:port, ip:port or port or
/unix/domain/path or "disabled" to not start the grpc server. (default "8079")
-halfclose
When not keepalive, whether to half close the connection (only for fast
http)
-health
grpc ping client mode: use health instead of ping
-healthservice string
which service string to pass to health check
-http-port port
http echo server port. Can be in the form of host:port, ip:port, port
or /unix/domain/path. (default "8080")
-http1.0
Use http1.0 (instead of http 1.1)
-httpbufferkb kbytes
Size of the buffer (max data size) for the optimized http client in
kbytes (default 128)
-httpccch
Check for Connection: Close Header
-https-insecure
Long form of the -k flag
-jitter
set to true to de-synchronize parallel clients' requests
-json path
Json output to provided file path or '-' for stdout (empty = no json
output, unless -a is used)
-k Do not verify certs in https connections
-keepalive
Keep connection alive (only for fast http 1.1) (default true)
-key Path
Path to the key file used for GRPC server TLS
-labels string
Additional config data/labels to add to the resulting JSON, defaults to
target URL and hostname
-logcaller
Logs filename and line number of callers to log (default true)
-loglevel value
loglevel, one of [Debug Verbose Info Warning Error Critical Fatal]
(default Info)
-logprefix string
Prefix to log lines before logged messages (default "> ")
-max-echo-delay value
Maximum sleep time for delay= echo server parameter. dynamic flag.
(default 1.5s)
-maxpayloadsizekb Kbytes
MaxPayloadSize is the maximum size of payload to be generated by the
EchoHandler size= argument. In Kbytes. (default 256)
-multi-mirror-origin
Mirror the request url to the target for multi proxies (-M) (default
true)
-multi-serial-mode
Multi server (-M) requests one at a time instead of parallel mode
-n int
Run for exactly this number of calls instead of duration. Default (0)
is to use duration (-t). Default is 1 when used as grpc ping count.
-nc-dont-stop-on-eof
in netcat (nc) mode, don't abort as soon as remote side closes
-p string
List of pXX to calculate (default "50,75,90,99,99.9")
-payload string
Payload string to send along
-payload-file path
File path to be use as payload (POST for http), replaces -payload when
set.
-payload-size int
Additional random payload size, replaces -payload when set > 0, must be
smaller than -maxpayloadsizekb. Setting this switches http to POST.
-ping
grpc load test: use ping instead of health
-profile file
write .cpu and .mem profiles to file
-qps float
Queries Per Seconds or 0 for no wait/max qps (default 8)
-quiet
Quiet mode: sets the loglevel to Error and reduces the output.
-r float
Resolution of the histogram lowest buckets in seconds (default 0.001)
-redirect-port port
Redirect all incoming traffic to https URL (need ingress to work
properly). Can be in the form of host:port, ip:port, port or "disabled" to
disable the feature. (default "8081")
-resolve string
Resolve CN of cert to this IP, so that we can call https://cn directly
-s int
Number of streams per grpc connection (default 1)
-static-dir path
Absolute path to the dir containing the static files dir
-stdclient
Use the slower net/http standard client (works for TLS)
-sync URL
index.tsv or s3/gcs bucket xml URL to fetch at startup for server modes.
-sync-interval duration
Refresh the url every given interval (default, no refresh)
-t duration
How long to run the test or 0 to run until ^C (default 5s)
-tcp-port port
tcp echo server port. Can be in the form of host:port, ip:port, port or
/unix/domain/path or "disabled". (default "8078")
-timeout duration
Connection and read timeout value (for http) (default 3s)
-udp-async
if true, udp echo server will use separate go routine to reply
-udp-port port
udp echo server port. Can be in the form of host:port, ip:port, port or
"disabled". (default "8078")
-udp-timeout duration
Udp timeout (default 750ms)
-ui-path URI
http server URI for UI, empty turns off that part (more secure)
(default "/fortio/")
-unix-socket path
Unix domain socket path to use for physical connection
-user user:password
User credentials for basic authentication (for http). Input data format
should be user:password
</pre>
</details>
See also the FAQ entry about [fortio flags for best results](https://github.com/fortio/fortio/wiki/FAQ#i-want-to-get-the-best-results-what-flags-should-i-pass)
## Example use and output
### Start the internal servers
```Shell
$ fortio server &
14:11:05 I fortio_main.go:171> Not using dynamic flag watching (use -config to set watch directory)
Fortio 1.15.2 tcp-echo server listening on [::]:8078
Fortio 1.15.2 grpc 'ping' server listening on [::]:8079
Fortio 1.15.2 https redirector server listening on [::]:8081
Fortio 1.15.2 echo server listening on [::]:8080
Data directory is /Users/ldemailly/go/src/fortio.org/fortio
UI started - visit:
http://localhost:8080/fortio/
(or any host/ip reachable on this server)
14:11:05 I fortio_main.go:233> All fortio 1.15.2 release go1.16.3 servers started!
```
### Change the port / binding address
By default, Fortio's web/echo servers listen on port 8080 on all interfaces.
Use the `-http-port` flag to change this behavior:
```Shell
$ fortio server -http-port 10.10.10.10:8088
UI starting - visit:
http://10.10.10.10:8088/fortio/
Https redirector running on :8081
Fortio 1.15.2 grpc ping server listening on port :8079
Fortio 1.15.2 echo server listening on port 10.10.10.10:8088
```
### Unix domain sockets
You can use unix domain socket for any server/client:
```Shell
$ fortio server --http-port /tmp/fortio-uds-http &
Fortio 1.15.2 grpc 'ping' server listening on [::]:8079
Fortio 1.15.2 https redirector server listening on [::]:8081
Fortio 1.15.2 echo server listening on /tmp/fortio-uds-http
UI started - visit:
fortio curl -unix-socket=/tmp/fortio-uds-http http://localhost/fortio/
14:58:45 I fortio_main.go:217> All fortio 1.15.2 unknown go1.16.3 servers started!
$ fortio curl -unix-socket=/tmp/fortio-uds-http http://foo.bar/debug
15:00:48 I http_client.go:428> Using unix domain socket /tmp/fortio-uds-http instead of foo.bar http
HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Date: Wed, 08 Aug 2018 22:00:48 GMT
Content-Length: 231
Φορτίο version 1.15.2 unknown go1.16.3 echo debug server up for 2m3.4s on ldemailly-macbookpro - request from
GET /debug HTTP/1.1
headers:
Host: foo.bar
User-Agent: fortio.org/fortio-1.15.2
body:
```
### TCP
Start the echo-server alone and run a load (use `tcp://` prefix for the load test to be for tcp echo server)
```Shell
$ fortio tcp-echo &
Fortio 1.15.2 tcp-echo TCP server listening on [::]:8078
19:45:30 I fortio_main.go:238> All fortio 1.15.2 release go1.16.3 servers started!
$ fortio load -qps -1 -n 100000 tcp://localhost:8078
Fortio 1.15.2 running at -1 queries per second, 16->16 procs, for 100000 calls: tcp://localhost:8078
20:01:31 I tcprunner.go:218> Starting tcp test for tcp://localhost:8078 with 4 threads at -1.0 qps
Starting at max qps with 4 thread(s) [gomax 16] for exactly 100000 calls (25000 per thread + 0)
20:01:32 I periodic.go:558> T003 ended after 1.240585427s : 25000 calls. qps=20151.77629520873
20:01:32 I periodic.go:558> T002 ended after 1.241141084s : 25000 calls. qps=20142.75437521493
20:01:32 I periodic.go:558> T001 ended after 1.242066385s : 25000 calls. qps=20127.7486468648
20:01:32 I periodic.go:558> T000 ended after 1.24227731s : 25000 calls. qps=20124.331176909283
Ended after 1.242312567s : 100000 calls. qps=80495
Aggregated Function Time : count 100000 avg 4.9404876e-05 +/- 1.145e-05 min 2.7697e-05 max 0.000887051 sum 4.94048763
# range, mid point, percentile, count
>= 2.7697e-05 <= 0.000887051 , 0.000457374 , 100.00, 100000
# target 50% 0.00045737
# target 75% 0.00067221
# target 90% 0.000801115
# target 99% 0.000878457
# target 99.9% 0.000886192
Sockets used: 4 (for perfect no error run, would be 4)
Total Bytes sent: 2400000, received: 2400000
tcp OK : 100000 (100.0 %)
All done 100000 calls (plus 0 warmup) 0.049 ms avg, 80495.0 qps
```
### UDP
Start the udp-echo server alone and run a load (use `tcp://` prefix for the load test to be for tcp echo server)
```
$ fortio udp-echo &
Fortio 1.15.2 udp-echo UDP server listening on [::]:8078
21:54:52 I fortio_main.go:273> Note: not using dynamic flag watching (use -config to set watch directory)
21:54:52 I fortio_main.go:281> All fortio 1.15.2 release go1.16.3 servers started!
$ fortio load -qps -1 -n 100000 udp://localhost:8078/
Fortio 1.15.2 running at -1 queries per second, 16->16 procs, for 100000 calls: udp://localhost:8078/
21:56:48 I udprunner.go:222> Starting udp test for udp://localhost:8078/ with 4 threads at -1.0 qps
Starting at max qps with 4 thread(s) [gomax 16] for exactly 100000 calls (25000 per thread + 0)
21:56:49 I periodic.go:558> T003 ended after 969.635695ms : 25000 calls. qps=25782.879208051432
21:56:49 I periodic.go:558> T000 ended after 969.906228ms : 25000 calls. qps=25775.687667818544
21:56:49 I periodic.go:558> T002 ended after 970.543935ms : 25000 calls. qps=25758.751457243405
21:56:49 I periodic.go:558> T001 ended after 970.737665ms : 25000 calls. qps=25753.610786287973
Ended after 970.755702ms : 100000 calls. qps=1.0301e+05
Aggregated Function Time : count 100000 avg 3.8532238e-05 +/- 1.7e-05 min 2.0053e-05 max 0.000881827 sum 3.85322376
# range, mid point, percentile, count
>= 2.0053e-05 <= 0.000881827 , 0.00045094 , 100.00, 100000
# target 50% 0.000450936
# target 75% 0.000666381
# target 90% 0.000795649
# target 99% 0.000873209
# target 99.9% 0.000880965
Sockets used: 4 (for perfect no error run, would be 4)
Total Bytes sent: 2400000, received: 2400000
udp OK : 100000 (100.0 %)
All done 100000 calls (plus 0 warmup) 0.039 ms avg, 103012.5 qps
```
### GRPC
#### Simple grpc ping
```Shell
$ fortio grpcping -n 5 localhost
22:36:55 I pingsrv.go:150> Ping RTT 212000 (avg of 259000, 217000, 160000 ns) clock skew -10500
22:36:55 I pingsrv.go:150> Ping RTT 134333 (avg of 170000, 124000, 109000 ns) clock skew 5000
22:36:55 I pingsrv.go:150> Ping RTT 112000 (avg of 111000, 122000, 103000 ns) clock skew 5000
22:36:55 I pingsrv.go:150> Ping RTT 157000 (avg of 136000, 158000, 177000 ns) clock skew 6000
22:36:55 I pingsrv.go:150> Ping RTT 108333 (avg of 118000, 106000, 101000 ns) clock skew 1000
Clock skew histogram usec : count 5 avg 1.3 +/- 6.145 min -10.5 max 6 sum 6.5
# range, mid point, percentile, count
>= -10.5 <= -10 , -10.25 , 20.00, 1
> 0 <= 2 , 1 , 40.00, 1
> 4 <= 6 , 5 , 100.00, 3
# target 50% 4.33333
RTT histogram usec : count 15 avg 144.73333 +/- 44.48 min 101 max 259 sum 2171
# range, mid point, percentile, count
>= 101 <= 110 , 105.5 , 26.67, 4
> 110 <= 120 , 115 , 40.00, 2
> 120 <= 140 , 130 , 60.00, 3
> 140 <= 160 , 150 , 73.33, 2
> 160 <= 180 , 170 , 86.67, 2
> 200 <= 250 , 225 , 93.33, 1
> 250 <= 259 , 254.5 , 100.00, 1
# target 50% 130
```
#### Change the target port for grpc
The value of `-grpc-port` (default 8079) is used when specifying a hostname or an IP address in `grpcping`. Add `:port` to the `grpcping` destination to
change this behavior:
```Shell
$ fortio grpcping 10.10.10.100:8078 # Connects to gRPC server 10.10.10.100 listening on port 8078
02:29:27 I pingsrv.go:116> Ping RTT 305334 (avg of 342970, 293515, 279517 ns) clock skew -2137
Clock skew histogram usec : count 1 avg -2.137 +/- 0 min -2.137 max -2.137 sum -2.137
# range, mid point, percentile, count
>= -4 < -2 , -3 , 100.00, 1
# target 50% -2.137
RTT histogram usec : count 3 avg 305.334 +/- 27.22 min 279.517 max 342.97 sum 916.002
# range, mid point, percentile, count
>= 250 < 300 , 275 , 66.67, 2
>= 300 < 350 , 325 , 100.00, 1
# target 50% 294.879
```
#### `grpcping` using TLS
* First, start Fortio server with the `-cert` and `-key` flags:
`/path/to/fortio/server.crt` and `/path/to/fortio/server.key` are paths to the TLS certificate and key that
you must provide.
```Shell
$ fortio server -cert /path/to/fortio/server.crt -key /path/to/fortio/server.key
UI starting - visit:
http://localhost:8080/fortio/
Https redirector running on :8081
Fortio 1.15.2 grpc ping server listening on port :8079
Fortio 1.15.2 echo server listening on port localhost:8080
Using server certificate /path/to/fortio/server.crt to construct TLS credentials
Using server key /path/to/fortio/server.key to construct TLS credentials
```
* Next, use `grpcping` with the `-cacert` flag:
`/path/to/fortio/ca.crt` is the path to the CA certificate
that issued the server certificate for `localhost`. In our example, the server certificate is
`/path/to/fortio/server.crt`:
```Shell
$ fortio grpcping -cacert /path/to/fortio/ca.crt localhost
Using server certificate /path/to/fortio/ca.crt to construct TLS credentials
16:00:10 I pingsrv.go:129> Ping RTT 501452 (avg of 595441, 537088, 371828 ns) clock skew 31094
Clock skew histogram usec : count 1 avg 31.094 +/- 0 min 31.094 max 31.094 sum 31.094
# range, mid point, percentile, count
>= 31.094 <= 31.094 , 31.094 , 100.00, 1
# target 50% 31.094
RTT histogram usec : count 3 avg 501.45233 +/- 94.7 min 371.828 max 595.441 sum 1504.357
# range, mid point, percentile, count
>= 371.828 <= 400 , 385.914 , 33.33, 1
> 500 <= 595.441 , 547.721 , 100.00, 2
# target 50% 523.86
```
#### GRPC to standard https service
`grpcping` can connect to a non-Fortio TLS server by prefacing the destination with `https://`:
```Shell
$ fortio grpcping https://fortio.istio.io
11:07:55 I grpcrunner.go:275> stripping https scheme. grpc destination: fortio.istio.io. grpc port: 443
Clock skew histogram usec : count 1 avg 12329.795 +/- 0 min 12329.795 max 12329.795 sum 12329.795
# range, mid point, percentile, count
>= 12329.8 <= 12329.8 , 12329.8 , 100.00, 1
# target 50% 12329.8
```
### Simple load test
Load (low default qps/threading) test:
```Shell
$ fortio load http://www.google.com
Fortio 1.15.2 running at 8 queries per second, 8->8 procs, for 5s: http://www.google.com
19:10:33 I httprunner.go:84> Starting http test for http://www.google.com with 4 threads at 8.0 qps
Starting at 8 qps with 4 thread(s) [gomax 8] for 5s : 10 calls each (total 40)
19:10:39 I periodic.go:314> T002 ended after 5.056753279s : 10 calls. qps=1.9775534712220633
19:10:39 I periodic.go:314> T001 ended after 5.058085991s : 10 calls. qps=1.9770324224999916
19:10:39 I periodic.go:314> T000 ended after 5.058796046s : 10 calls. qps=1.9767549252963101
19:10:39 I periodic.go:314> T003 ended after 5.059557593s : 10 calls. qps=1.9764573910247019
Ended after 5.059691387s : 40 calls. qps=7.9056
Sleep times : count 36 avg 0.49175757 +/- 0.007217 min 0.463508712 max 0.502087879 sum 17.7032725
Aggregated Function Time : count 40 avg 0.060587641 +/- 0.006564 min 0.052549016 max 0.089893269 sum 2.42350566
# range, mid point, percentile, count
>= 0.052549 < 0.06 , 0.0562745 , 47.50, 19
>= 0.06 < 0.07 , 0.065 , 92.50, 18
>= 0.07 < 0.08 , 0.075 , 97.50, 2
>= 0.08 <= 0.0898933 , 0.0849466 , 100.00, 1
# target 50% 0.0605556
# target 75% 0.0661111
# target 99% 0.085936
# target 99.9% 0.0894975
Code 200 : 40
Response Header Sizes : count 40 avg 690.475 +/- 15.77 min 592 max 693 sum 27619
Response Body/Total Sizes : count 40 avg 12565.2 +/- 301.9 min 12319 max 13665 sum 502608
All done 40 calls (plus 4 warmup) 60.588 ms avg, 7.9 qps
```
### GRPC load test
Uses `-s` to use multiple (h2/grpc) streams per connection (`-c`), request to hit the fortio ping grpc endpoint with a delay in replies of 0.25s and an extra payload for 10 bytes and auto save the json result:
```bash
$ fortio load -a -grpc -ping -grpc-ping-delay 0.25s -payload "01234567890" -c 2 -s 4 https://fortio-stage.istio.io
Fortio 1.15.2 running at 8 queries per second, 8->8 procs, for 5s: https://fortio-stage.istio.io
16:32:56 I grpcrunner.go:139> Starting GRPC Ping Delay=250ms PayloadLength=11 test for https://fortio-stage.istio.io with 4*2 threads at 8.0 qps
16:32:56 I grpcrunner.go:261> stripping https scheme. grpc destination: fortio-stage.istio.io. grpc port: 443
16:32:57 I grpcrunner.go:261> stripping https scheme. grpc destination: fortio-stage.istio.io. grpc port: 443
Starting at 8 qps with 8 thread(s) [gomax 8] for 5s : 5 calls each (total 40)
16:33:04 I periodic.go:533> T005 ended after 5.283227589s : 5 calls. qps=0.9463911814835126
[...]
Ended after 5.28514474s : 40 calls. qps=7.5684
Sleep times : count 32 avg 0.97034752 +/- 0.002338 min 0.967323561 max 0.974838789 sum 31.0511206
Aggregated Function Time : count 40 avg 0.27731944 +/- 0.001606 min 0.2741372 max 0.280604967 sum 11.0927778
# range, mid point, percentile, count
>= 0.274137 <= 0.280605 , 0.277371 , 100.00, 40
# target 50% 0.277288
# target 75% 0.278947
# target 90% 0.279942
# target 99% 0.280539
# target 99.9% 0.280598
Ping SERVING : 40
All done 40 calls (plus 2 warmup) 277.319 ms avg, 7.6 qps
Successfully wrote 1210 bytes of Json data to 2018-04-03-163258_fortio_stage_istio_io_ldemailly_macbookpro.json
```
And the JSON saved is
<details>
<pre>
{
"RunType": "GRPC Ping Delay=250ms PayloadLength=11",
"Labels": "fortio-stage.istio.io , ldemailly-macbookpro",
"StartTime": "2018-04-03T16:32:58.895472681-07:00",
"RequestedQPS": "8",
"RequestedDuration": "5s",
"ActualQPS": 7.568383075162479,
"ActualDuration": 5285144740,
"NumThreads": 8,
"Version": "0.9.0",
"DurationHistogram": {
"Count": 40,
"Min": 0.2741372,
"Max": 0.280604967,
"Sum": 11.092777797,
"Avg": 0.277319444925,
"StdDev": 0.0016060870789948905,
"Data": [
{
"Start": 0.2741372,
"End": 0.280604967,
"Percent": 100,
"Count": 40
}
],
"Percentiles": [
{
"Percentile": 50,
"Value": 0.2772881634102564
},
{
"Percentile": 75,
"Value": 0.27894656520512817
},
{
"Percentile": 90,
"Value": 0.2799416062820513
},
{
"Percentile": 99,
"Value": 0.28053863092820513
},
{
"Percentile": 99.9,
"Value": 0.2805983333928205
}
]
},
"Exactly": 0,
"RetCodes": {
"1": 40
},
"Destination": "https://fortio-stage.istio.io",
"Streams": 4,
"Ping": true
}
</pre></details>
* Load test using gRPC and TLS security. First, start Fortio server with the `-cert` and `-key` flags:
```Shell
fortio server -cert /etc/ssl/certs/server.crt -key /etc/ssl/certs/server.key
```
Next, run the `load` command with the `-cacert` flag:
```Shell
fortio load -cacert /etc/ssl/certs/ca.crt -grpc localhost:8079
```
### Curl like (single request) mode
```Shell
$ fortio load -curl -H Foo:Bar http://localhost:8080/debug
14:26:26 I http.go:133> Setting regular extra header Foo: Bar
HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Date: Mon, 08 Jan 2018 22:26:26 GMT
Content-Length: 230
Φορτίο version 1.15.2 echo debug server up for 39s on ldemailly-macbookpro - request from [::1]:65055
GET /debug HTTP/1.1
headers:
Host: localhost:8080
User-Agent: fortio.org/fortio-1.15.2
Foo: Bar
body:
```
### Report only UI
If you have json files saved from running the full UI or downloaded, using the `-sync` option, from an amazon or google cloud storage bucket or from a peer fortio server (to synchronize from a peer fortio, use `http://`_peer_`:8080/data/index.tsv` as the sync URL). You can then serve just the reports:
```Shell
$ fortio report -sync-interval 15m -sync http://storage.googleapis.com:443/fortio-data?prefix=fortio.istio.io/
Browse only UI starting - visit:
http://localhost:8080/
Https redirector running on :8081
```
### Using the HTTP fan out / multi proxy feature
Example listen on 1 extra port and every request sent to that 1 port is forward to 2:
```Shell
# in one window or &
$ fortio server -M "5554 http://localhost:8080 http://localhost:8080"
[...]
Fortio 1.15.2 Multi on 5554 server listening on [::]:5554
10:09:56 I http_forwarder.go:152> Multi-server on [::]:5554 running with &{Targets:[{Destination:http://localhost:8080 MirrorOrigin:true} {Destination:http://localhost:8080 MirrorOrigin:true}] Name:Multi on [::]:5554 client:0xc0001ccc00}
```
Call the debug endpoint on both
```Shell
# in new window
$ fortio curl -payload "a test" http://localhost:5554/debug
HTTP/1.1 200 OK
Date: Wed, 07 Oct 2020 17:11:06 GMT
Content-Length: 684
Content-Type: text/plain; charset=utf-8
Φορτίο version 1.15.2 unknown go1.16.3 echo debug server up for 1m9.3s on C02C77BHMD6R - request from [::1]:51020
POST /debug HTTP/1.1
headers:
Host: localhost:8080
Accept-Encoding: gzip
Content-Type: application/octet-stream
User-Agent: fortio.org/fortio-1.15.2
X-Fortio-Multi-Id: 1
X-On-Behalf-Of: [::1]:51019
body:
a test
Φορτίο version 1.15.2 unknown go1.16.3 echo debug server up for 1m9.3s on C02C77BHMD6R - request from [::1]:51020
POST /debug HTTP/1.1
headers:
Host: localhost:8080
Accept-Encoding: gzip
Content-Type: application/octet-stream
User-Agent: fortio.org/fortio-1.15.2
X-Fortio-Multi-Id: 2
X-On-Behalf-Of: [::1]:51019
body:
a test
```
There are 2 flags to further control the behaviour of the multi server proxies:
- pass `-mirrorOriginFlag=false` to not mirror all headers and request type to targets.
- pass `-multi-serial-mode` to stream request response serially instead of fetching in parallel and writing combined data after completion
Also remember you can pass multiple `-M`.
### Using the TCP proxy server(s) feature
Example: open 2 additional listening ports and forward all requests received on 8888 and 8889 (ipv6) to 8080 (regular http server)
```Shell
$ fortio server -P "8888 [::1]:8080" -P "[::1]:8889 [::1]:8080"
Fortio 1.15.2 grpc 'ping' server listening on [::]:8079
Fortio 1.15.2 https redirector server listening on [::]:8081
Fortio 1.15.2 echo server listening on [::]:8080
Data directory is /home/dl
UI started - visit:
http://localhost:8080/fortio/
(or any host/ip reachable on this server)
Fortio 1.15.2 proxy for [::1]:8080 server listening on [::]:8888
Fortio 1.15.2 proxy for [::1]:8080 server listening on [::1]:8889
```
## Server URLs and features
Fortio `server` has the following feature for the http listening on 8080 (all paths and ports are configurable through flags above):
* A simple echo server which will echo back posted data (for any path not mentioned below).
For instance `curl -d abcdef http://localhost:8080/` returns `abcdef` back. It supports the following optional query argument parameters:
| Parameter | Usage, example |
|-----------|----------------|
| delay | duration to delay the response by. Can be a single value or a comma separated list of probabilities, e.g `delay=150us:10,2ms:5,0.5s:1` for 10% of chance of a 150 us delay, 5% of a 2ms delay and 1% of a 1/2 second delay |
| status | http status to return instead of 200. Can be a single value or a comma separated list of probabilities, e.g `status=404:10,503:5,429:1` for 10% of chance of a 404 status, 5% of a 503 status and 1% of a 429 status |
| size | size of the payload to reply instead of echoing input. Also works as probabilities list. `size=1024:10,512:5` 10% of response will be 1k and 5% will be 512 bytes payload and the rest defaults to echoing back. |
| close | close the socket after answering e.g `close=true` |
| header | header(s) to add to the reply e.g. `&header=Foo:Bar&header=X:Y` |
You can set a default value for all these by passing `-echo-server-default-params` to the server command line, for instance:
`fortio server -echo-server-default-params="delay=0.5s:50,1s:40&status=418"` will make the server respond with http 418 and a delay of either 0.5s half of the time, 1s 40% and no delay in 10% of the calls; unless any `?` query args is passed by the client. Note that the quotes (") are for the shell to escape the ampersand (&) but should not be put in a yaml nor the dynamicflag url for instance.
* `/debug` will echo back the request in plain text for human debugging.
* `/fortio/` A UI to
* Run/Trigger tests and graph the results.
* A UI to browse saved results and single graph or multi graph them (comparative graph of min,avg, median, p75, p99, p99.9 and max).
* Proxy/fetch other URLs
* `/fortio/data/index.tsv` an tab separated value file conforming to Google cloud storage [URL list data transfer format](https://cloud.google.com/storage/transfer/create-url-list) so you can export/backup local results to the cloud.
* Download/sync peer to peer JSON results files from other Fortio servers (using their `index.tsv` URLs)
* Download/sync from an Amazon S3 or Google Cloud compatible bucket listings [XML URLs](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGET.html)
The `report` mode is a readonly subset of the above directly on `/`.
There is also the GRPC health and ping servers, as well as the http->https redirector.
## Implementation details
Fortio is written in the [Go](https://golang.org) language and includes a scalable semi log histogram in [stats.go](stats/stats.go) and a periodic runner engine in [periodic.go](periodic/periodic.go) with specializations for [http](http/httprunner.go) and [grpc](fortiogrpc/grpcrunner.go).
The [http/](http/) package includes a very high performance specialized http 1.1 client.
You may find fortio's [logger](log/logger.go) useful as well.
You can run the histogram code standalone as a command line in [histogram/](histogram/), a basic echo http server in [echosrv/](echosrv/), or both the http echo and GRPC ping server through `fortio server`, the fortio command line interface lives in this top level directory [fortio_main.go](fortio_main.go)
There is also [fcurl/](fcurl/) which is the `fortio curl` part of the code (if you need a light http client without grpc or server side).
A matching tiny (2Mb compressed) docker image is [fortio/fortio.fcurl](https://hub.docker.com/r/fortio/fortio.fcurl/tags/)
## More examples
You can get the data on the console, for instance, with 5k qps: (includes envoy and mixer in the calls)
<details><pre>
$ time fortio load -qps 5000 -t 60s -c 8 -r 0.0001 -H "Host: perf-cluster" http://benchmark-2:9090/echo
2017/07/09 02:31:05 Will be setting special Host header to perf-cluster
Fortio running at 5000 queries per second for 1m0s: http://benchmark-2:9090/echo
Starting at 5000 qps with 8 thread(s) [gomax 4] for 1m0s : 37500 calls each (total 300000)
2017/07/09 02:32:05 T004 ended after 1m0.000907812s : 37500 calls. qps=624.9905437680746
2017/07/09 02:32:05 T000 ended after 1m0.000922222s : 37500 calls. qps=624.9903936684861
2017/07/09 02:32:05 T005 ended after 1m0.00094454s : 37500 calls. qps=624.9901611965524
2017/07/09 02:32:05 T006 ended after 1m0.000944816s : 37500 calls. qps=624.9901583216429
2017/07/09 02:32:05 T001 ended after 1m0.00102094s : 37500 calls. qps=624.9893653892883
2017/07/09 02:32:05 T007 ended after 1m0.001096292s : 37500 calls. qps=624.9885805003184
2017/07/09 02:32:05 T003 ended after 1m0.001045342s : 37500 calls. qps=624.9891112105419
2017/07/09 02:32:05 T002 ended after 1m0.001044416s : 37500 calls. qps=624.9891208560392
Ended after 1m0.00112695s : 300000 calls. qps=4999.9
Aggregated Sleep Time : count 299992 avg 8.8889218e-05 +/- 0.002326 min -0.03490402 max 0.001006041 sum 26.6660543
# range, mid point, percentile, count
< 0 , 0 , 8.58, 25726
>= 0 < 0.001 , 0.0005 , 100.00, 274265
>= 0.001 < 0.002 , 0.0015 , 100.00, 1
# target 50% 0.000453102
WARNING 8.58% of sleep were falling behind
Aggregated Function Time : count 300000 avg 0.00094608764 +/- 0.0007901 min 0.000510522 max 0.029267604 sum 283.826292
# range, mid point, percentile, count
>= 0.0005 < 0.0006 , 0.00055 , 0.15, 456
>= 0.0006 < 0.0007 , 0.00065 , 3.25, 9295
>= 0.0007 < 0.0008 , 0.00075 , 24.23, 62926
>= 0.0008 < 0.0009 , 0.00085 , 62.73, 115519
>= 0.0009 < 0.001 , 0.00095 , 85.68, 68854
>= 0.001 < 0.0011 , 0.00105 , 93.11, 22293
>= 0.0011 < 0.0012 , 0.00115 , 95.38, 6792
>= 0.0012 < 0.0014 , 0.0013 , 97.18, 5404
>= 0.0014 < 0.0016 , 0.0015 , 97.94, 2275
>= 0.0016 < 0.0018 , 0.0017 , 98.34, 1198
>= 0.0018 < 0.002 , 0.0019 , 98.60, 775
>= 0.002 < 0.0025 , 0.00225 , 98.98, 1161
>= 0.0025 < 0.003 , 0.00275 , 99.21, 671
>= 0.003 < 0.0035 , 0.00325 , 99.36, 449
>= 0.0035 < 0.004 , 0.00375 , 99.47, 351
>= 0.004 < 0.0045 , 0.00425 , 99.57, 290
>= 0.0045 < 0.005 , 0.00475 , 99.66, 280
>= 0.005 < 0.006 , 0.0055 , 99.79, 380
>= 0.006 < 0.007 , 0.0065 , 99.82, 92
>= 0.007 < 0.008 , 0.0075 , 99.83, 15
>= 0.008 < 0.009 , 0.0085 , 99.83, 5
>= 0.009 < 0.01 , 0.0095 , 99.83, 1
>= 0.01 < 0.012 , 0.011 , 99.83, 8
>= 0.012 < 0.014 , 0.013 , 99.84, 35
>= 0.014 < 0.016 , 0.015 , 99.92, 231
>= 0.016 < 0.018 , 0.017 , 99.94, 65
>= 0.018 < 0.02 , 0.019 , 99.95, 26
>= 0.02 < 0.025 , 0.0225 , 100.00, 139
>= 0.025 < 0.03 , 0.0275 , 100.00, 14
# target 50% 0.000866935
# target 75% 0.000953452
# target 99% 0.00253875
# target 99.9% 0.0155152
Code 200 : 300000
Response Body Sizes : count 300000 avg 0 +/- 0 min 0 max 0 sum 0
</pre></details>
Or you can get the data in [JSON format](https://github.com/fortio/fortio/wiki/Sample-JSON-output) (using `-json result.json`)
### Web/Graphical UI
Or graphically (through the [http://localhost:8080/fortio/](http://localhost:8080/fortio/) web UI):
Simple form/UI:
Sample requests with responses delayed by 250us and 0.5% of 503 and 1.5% of 429 simulated http errors.
Run result:
```Shell
Code 200 : 2929 (97.6 %)
Code 429 : 56 (1.9 %)
Code 503 : 15 (0.5 %)
```
There are newer/live examples on [istio.io/docs/concepts/performance-and-scalability/#synthetic-end-to-end-benchmarks](https://archive.istio.io/v1.0/docs/concepts/performance-and-scalability/#synthetic-end-to-end-benchmarks)
## Contributing
Contributions whether through issues, documentation, bug fixes, or new features
are most welcome !
Please also see [Contributing to Istio](https://github.com/istio/community/blob/master/CONTRIBUTING.md#contributing-to-istio)
and [Getting started contributing to Fortio](https://github.com/fortio/fortio/wiki/FAQ#how-do-i-get-started-contributing-to-fortio) in the FAQ.
If you are not using the binary releases, please do `make pull` to pull/update to the latest of the current branch.
And make sure to go strict format (`go get mvdan.cc/gofumpt` and `gofumpt -s -w *.go`) and run those commands successfully before sending your PRs:
```Shell
make test
make lint
make release-test
```
When modifying Javascript, check with [standard](https://github.com/standard/standard):
```Shell
standard --fix ui/static/js/fortio_chart.js
```
## See also
Our wiki and the [Fortio FAQ](https://github.com/fortio/fortio/wiki/FAQ) (including for instance differences between `fortio` and `wrk` or `httpbin`)
## Disclaimer
This is not an officially supported Google product.
| 44.703381 | 406 | 0.717025 | eng_Latn | 0.876004 |
6ffa9d4d5b6149b6c6ebf59904b6a9d6ba9419a7 | 5,817 | md | Markdown | articles/finance/cash-bank-management/reconcile-bank-account.md | MicrosoftDocs/Dynamics-365-Operations.lt-lt | 4edb9b5897a1f4cc990027074662bd1e8d56ea17 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-05-18T17:14:28.000Z | 2022-01-30T03:33:06.000Z | articles/finance/cash-bank-management/reconcile-bank-account.md | MicrosoftDocs/Dynamics-365-Operations.lt-lt | 4edb9b5897a1f4cc990027074662bd1e8d56ea17 | [
"CC-BY-4.0",
"MIT"
] | 6 | 2017-12-12T12:37:43.000Z | 2019-04-30T11:46:17.000Z | articles/finance/cash-bank-management/reconcile-bank-account.md | MicrosoftDocs/Dynamics-365-Operations.lt-lt | 4edb9b5897a1f4cc990027074662bd1e8d56ea17 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2018-02-28T23:29:31.000Z | 2019-10-12T18:18:06.000Z | ---
title: Banko sąskaitos suderinimas
description: Šioje temoje aprašoma, kaip suderinti banko sąskaitą.
author: panolte
ms.date: 07/01/2019
ms.topic: article
ms.prod: ''
ms.technology: ''
audience: Application User
ms.reviewer: roschlom
ms.search.region: Global
ms.author: panolte
ms.search.validFrom:
- month/year of release that feature was introduced in
- in format yyyy-mm-dd
ms.dyn365.ops.version: 10.0.5
ms.openlocfilehash: e06a38a19a16a07d77d0c9aceaa4e3206646dd0561996681b417b785058f3938
ms.sourcegitcommit: 42fe9790ddf0bdad911544deaa82123a396712fb
ms.translationtype: HT
ms.contentlocale: lt-LT
ms.lasthandoff: 08/05/2021
ms.locfileid: "6739364"
---
# <a name="reconcile-a-bank-account"></a>Banko sąskaitos suderinimas
[!include[banner](../includes/banner.md)]
Gavę banko išrašą, turėtumėte periodiškai suderinti juridinio subjekto banko operacijas su banko išrašo operacijomis.
Negalite suderinti banko sąskaitos išrašo su banko sąskaita, jei nors vieno iš čekių ar mokėjimo kvitų, kurie išvardinti išraše, būsena yra **Laukiama atšaukimo**. Kai redaktorius užregistruoja arba atmeta čekių atšaukimą arba mokėjimo kvitų mokėjimų atšaukimus, būsena nebėra **Laukiama atšaukimo**, ir jūs galite suderinti banko sąskaitą.
1. Eikite į **Grynųjų pinigų ir banko valdymas** \> **Banko sąskaitos** \> **Banko sąskaitos**. Pasirinkite banko sąskaitą, kurią norite suderinti su banko išrašu, ir pasirinkite **Suderinti** > **Sąskaitos suderinimas**.
2. Laukeliuose **Banko išrašo data** ir **Banko išrašas** įveskite informaciją. Lauke **Pabaigos likutis** įveskite banko sąskaitos balansą taip, kaip jis pateikiamas banko sąskaitos išraše.
3. Pasirinkite **Operacijos**, kad atidarytumėte puslapį **Sąskaitos suderinimas**.
4. Kiekvienos operacijos, kuri įtraukta į banko sąskaitos išrašą, metu – jei suma atitinka banko sąskaitos išraše nurodytą sumą Dynamics 365 Finance – pažymėkite žymės langelį **Išvalyta**. Taip pat galite įvesti arba keisti laukelio **Banko operacijos tipas** reikšmę. Tai svarbu jūsų banko operacijų statistikai ir kai kurioms ataskaitoms.
> [!NOTE]
> <P>Tų operacijų, kurių nėra banko sąskaitos išraše, žymės langelis <STRONG>Išvalyta</STRONG> turi likti nepažymėtas. Šios operacijos ir toliau bus rodomos šioje formoje, kol nebus suderintos su kitu banko sąskaitos išrašu.</P>
> <P>Žymės langelis <STRONG>Išvalyta</STRONG> neaktyvus, jei operacijos būsena yra <STRONG>Laukiama atšaukimo</STRONG>. Operacijos gali turėti tokią būseną, jei „Finance“ nustatytas taip, kad prieš užregistruojant atšaukimus ar anuliavimus, jie būtų peržiūrimi. Kai redaktorius užregistruoja arba atmeta atšaukimą, būsena nebėra <STRONG>Laukiama atšaukimo</STRONG>, ir jūs galite suderinti banko sąskaitą su banko išrašu.</P>
Norėdami pasirinkti žymės langelį **Ištrinta** visų banko išraše rodomų čekių intervalui, pasirinkite žymės langelį **Pažymėti čekių intervalą** ir nurodykite intervalą.
5. Jei banko sąskaitos operacijos suma neatitinka banko išraše nurodytos operacijos sumos, lauke **Koregavimo suma** įveskite pakoreguotą sumą.
> [!NOTE]
> <P>Jei koreguotinos operacijos ataskaitinis laikotarpis yra uždarytas, lauko <STRONG>Koregavimo suma</STRONG> naudoti negalima. Vietoj to sukurkite naują eilutę su operacijos data iš atvirojo ataskaitinio laikotarpio. Tokiu atveju turite pridėti atliekant pirminę operaciją naudotas finansines dimensijas ir korespondentinę pagrindinę sąskaitą.</P>
6. Sukurkite operacijas įrašams (pvz., mokesčiai ir palūkanos), kurie pateikti banko sąskaitos išraše, tačiau dar neužregistruoti „Finance“. Įveskite **Banko operacijos tipą** ir tinkamas finansines dimensijas.
7. Kai banko sąskaitos išrašo operacijos pažymėtos kaip **Apmokėta**, lauke **Nesuderinta** esanti suma (kuri nuolat perskaičiuojama jums atliekant pakeitimus) artėja prie nulio. Kai ji pasiekia nulį, spustelėkite **Suderinti sąskaitą**, tokiu būdu užregistruosite suderinimą ir savo sukurtas operacijas bei koregavimus.
Suderinimą užregistravus, įtrauktų operacijų nebegalima nei peržiūrėti, nei taisyti, ir jos daugiau neberodomos kitų sąskaitos suderinimų metu.
8. Jei norite peržiūrėti dar nesuderintas banko operacijas, naudokite ataskaitą **Nesuderintos banko operacijos**. Jei norite peržiūrėti banko sąskaitos banko išrašą, naudokite ataskaitą **Banko išrašas**.
## <a name="cancel-bank-statement-reconciliation"></a>Banko išrašo sudarymo atšaukimas
Naudodami banko išrašo sudarymo atšaukimo funkciją galėsite atšaukti banko išrašo sudarymą. Jei norite naudoti šią funkciją, aktyvuokite funkciją **Atšaukti banko išrašo suderinimą**, esančią darbo srityje **Funkcijų valdymas**. Taip pat turėsite aktyvuoti parametrą **Leisti redaguoti banko išrašą**. Kad tą atliktumėte, eikite į **Grynųjų pinigų ir banko valdymas > Sąranka > Grynųjų pinigų ir banko valdymo parametrai > Banko suderinimas**.
Banko išrašo suderinimus atšaukti galima tik chronologine tvarka pagal jų įvedimo laiką. Atšaukus banko išrašo suderinimą, naujos operacijos ir taisymai bus anuliuoti, o visos kitos operacijos bus pažymėtos kaip nesuderinamos.
Norėdami atšaukti banko išrašo suderinimą, pasirinkite banko išrašą ir pasirinkite **Banko išrašas > Atšaukti banko suderinimą**. Puslapyje **Atšaukti banko suderinimą** pateikite **Priežasties kodą**, **Priežasties komentarą** ir **Atšaukimo datą**. Spustelėkite **Gerai**, kad pradėtumėte atšaukimą. Atkreipkite dėmesį, kad banko išrašo atšaukimo data turi sutapti arba būti vėlesnė nei banko išrašo data. Atšaukus banko išrašo suderinimą, banko išrašo laukas **Atšaukimo data** bus atnaujintas pateikta **Atšaukimo data**. Spustelėkite mygtuką **Operacijos**, kad peržiūrėtumėte operacijas, kurių suderinimas buvo atšauktas.
[!INCLUDE[footer-include](../../includes/footer-banner.md)] | 79.684932 | 627 | 0.798006 | lit_Latn | 0.999985 |
6ffb99257d4794576fb04efe792a8e236c5f0803 | 2,651 | md | Markdown | README.md | xuxiaowei-com-cn/hello-world-vite2-vue3 | f2f141c19295283a011b83bb2d49af81e082dc72 | [
"Apache-2.0"
] | null | null | null | README.md | xuxiaowei-com-cn/hello-world-vite2-vue3 | f2f141c19295283a011b83bb2d49af81e082dc72 | [
"Apache-2.0"
] | 1 | 2021-01-07T07:30:18.000Z | 2021-01-07T07:30:18.000Z | README.md | xuxiaowei-com-cn/hello-world-vite2-vue3 | f2f141c19295283a011b83bb2d49af81e082dc72 | [
"Apache-2.0"
] | null | null | null | # hello-world-vite2-vue3
## 创建项目
- 创建完成功，项目路径：create-app/hello-world-vite2-vue3
- [Vue 3 Documentation](https://v3.vuejs.org)
~~~
mkdir create-app
cd create-app
npm i @vitejs/create-app
npm init @vitejs/app hello-world-vite2-vue3 --template vue
~~~
## 依赖
### element-plus
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/element-plus)
- [GitHub](https://github.com/element-plus/element-plus)
- [element-plus](https://element-plus.gitee.io)
~~~
npm i element-plus
~~~
### uuid
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/uuid)
~~~
npm i uuid
~~~
### vue
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/vue)
- [GitHub](https://github.com/vuejs/vue-next)
- [vuejs cli](https://cli.vuejs.org)
- [vuejs v3](https://v3.vuejs.org)
~~~
npm install -g @vue/cli
~~~
### vue-router
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/vue-router)
- [GitHub](https://github.com/vuejs/vue-router-next)
- [next router](https://next.router.vuejs.org)
~~~
npm i vue-router@next
~~~
### vuex
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/vuex)
- [GitHub](https://github.com/vuejs/vuex)
- [next vuex](https://next.vuex.vuejs.org)
~~~
npm i vuex@next
~~~
## 开发依赖
### @vitejs/plugin-vue
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/@vitejs/plugin-vue)
- [GitHub](https://github.com/vitejs/vite/tree/main/packages/plugin-vue)
~~~
npm i -D @vitejs/plugin-vue
~~~
### @vue/compiler-sfc
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/@vue/compiler-sfc)
- [GitHub](https://github.com/vuejs/vue-next/tree/master/packages/compiler-sfc)
~~~
npm i -D @vue/compiler-sfc
~~~
### sass
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/sass)
- [GitHub](https://github.com/sass/dart-sass)
~~~
npm i -D sass
~~~
### vite
- [TAONPM](https://developer.aliyun.com/mirror/npm/package/vite)
- [GitHub](https://github.com/vitejs/vite)
- [vitejs](https://vitejs.dev)
- [创建项目](https://vitejs.dev/guide/#scaffolding-your-first-vite-project)
- [命令行](https://vitejs.dev/guide/#command-line-interface)
- [浏览器兼容性](https://vitejs.dev/guide/build.html#browser-compatibility)
- [多页应用](https://vitejs.dev/guide/build.html#multi-page-app)
- [配置 vite](https://vitejs.dev/config/#configuring-vite)
- [条件配置](https://vitejs.dev/config/#conditional-config)
- [生产项目名](https://vitejs.dev/config/#build-base)
- [指定输出目录](https://vitejs.dev/config/#build-outdir)
- [静态文件路径](https://vitejs.dev/config/#build-assetsdir)
- [静态资源阈值](https://vitejs.dev/config/#build-assetsinlinelimit)
- [CSS分割](https://vitejs.dev/config/#build-csscodesplit)
- [源码](https://vitejs.dev/config/#build-sourcemap)
~~~
npm i -D vite
~~~
| 27.614583 | 79 | 0.697473 | kor_Hang | 0.139573 |
6ffc9a62555d396e22a4872436a9af787891518d | 1,335 | md | Markdown | wdk-ddi-src/content/d3d12umddi/ns-d3d12umddi-d3d12ddi_swizzle_bit_entry.md | Acidburn0zzz/windows-driver-docs-ddi | c16b5cd6c3f59ca5f963ff86f3f0926e3b910231 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-11-06T01:28:38.000Z | 2018-11-06T01:28:38.000Z | wdk-ddi-src/content/d3d12umddi/ns-d3d12umddi-d3d12ddi_swizzle_bit_entry.md | Acidburn0zzz/windows-driver-docs-ddi | c16b5cd6c3f59ca5f963ff86f3f0926e3b910231 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/d3d12umddi/ns-d3d12umddi-d3d12ddi_swizzle_bit_entry.md | Acidburn0zzz/windows-driver-docs-ddi | c16b5cd6c3f59ca5f963ff86f3f0926e3b910231 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NS:d3d12umddi.D3D12DDI_SWIZZLE_BIT_ENTRY
title: D3D12DDI_SWIZZLE_BIT_ENTRY
author: windows-driver-content
description: Defines a swizzle bit entry.
old-location: display\d3d12ddi_swizzle_bit_entry.htm
ms.assetid: B7FF7AA2-39B2-4D9E-8DDC-0A39FFF49F37
ms.date: 05/10/2018
ms.keywords: D3D12DDI_SWIZZLE_BIT_ENTRY, D3D12DDI_SWIZZLE_BIT_ENTRY structure [Display Devices], d3d12umddi/D3D12DDI_SWIZZLE_BIT_ENTRY, display.d3d12ddi_swizzle_bit_entry
ms.topic: struct
req.header: d3d12umddi.h
req.include-header: D3d12umddi.h
req.target-type: Windows
req.target-min-winverclnt:
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql:
topic_type:
- APIRef
- kbSyntax
api_type:
- HeaderDef
api_location:
- D3d12umddi.h
api_name:
- D3D12DDI_SWIZZLE_BIT_ENTRY
product:
- Windows
targetos: Windows
tech.root: display
req.typenames: D3D12DDI_SWIZZLE_BIT_ENTRY
---
# D3D12DDI_SWIZZLE_BIT_ENTRY structure
## -description
Defines a swizzle bit entry.
## -struct-fields
### -field Valid
A valid value.
### -field ChannelIndex
The channel index. Specify zero (0) for X, one (1) for Y, two (2) for Z, and three (3) for SS.
### -field SourceBitIndex
Index of source bit address.
| 18.541667 | 170 | 0.777528 | yue_Hant | 0.375885 |
87cf603c679642f7392aee50f56f8367faee1d6c | 38,259 | md | Markdown | packages/eslint-config/CHANGELOG.md | stencila/dev-conf | ce54a747a8627df8bde0505da908a4422aa6d460 | [
"Apache-2.0"
] | 6 | 2019-05-31T22:11:20.000Z | 2021-03-13T15:11:06.000Z | packages/eslint-config/CHANGELOG.md | stencila/dev-conf | ce54a747a8627df8bde0505da908a4422aa6d460 | [
"Apache-2.0"
] | 32 | 2019-06-07T04:39:30.000Z | 2021-11-01T18:19:40.000Z | packages/eslint-config/CHANGELOG.md | stencila/dev-config | 48f238474c6e9106a8ec2c6ab46c1382ecef9575 | [
"Apache-2.0"
] | null | null | null | # Change Log
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
## [3.0.1](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@3.0.0...@stencila/eslint-config@3.0.1) (2021-12-01)
**Note:** Version bump only for package @stencila/eslint-config
# [3.0.0](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.22...@stencila/eslint-config@3.0.0) (2021-11-01)
### Features
- **ESLint:** Simplify config, drop custom configs for React ([88265f1](https://github.com/stencila/dev-config/commit/88265f17d25a0dc263f0227eb214707939060b6d))
### BREAKING CHANGES
- **ESLint:** React specific configurations weren't used often, and so the
current recommendation is to use other presets on top of Stencila's own.
## [2.0.22](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.21...@stencila/eslint-config@2.0.22) (2021-10-27)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.21](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.20...@stencila/eslint-config@2.0.21) (2021-10-27)
### Bug Fixes
- **dependencies:** update dependency eslint to v8 ([7fad271](https://github.com/stencila/dev-config/commit/7fad2717e2b31ca626b62552a3530dca4a269173))
## [2.0.20](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.19...@stencila/eslint-config@2.0.20) (2021-10-27)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-prettier to v4 ([3002532](https://github.com/stencila/dev-config/commit/3002532a9fcd24efdc658c6323a5ded6426d8999))
- **dependencies:** update typescript-eslint monorepo to v5 ([38f9730](https://github.com/stencila/dev-config/commit/38f9730079ac09974f7fd5de3b623fbcd760de36))
## [2.0.19](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.18...@stencila/eslint-config@2.0.19) (2021-10-20)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.18](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.17...@stencila/eslint-config@2.0.18) (2021-09-22)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.17](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.16...@stencila/eslint-config@2.0.17) (2021-09-15)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.16](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.15...@stencila/eslint-config@2.0.16) (2021-09-01)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.15](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.14...@stencila/eslint-config@2.0.15) (2021-07-07)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.14](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.13...@stencila/eslint-config@2.0.14) (2021-06-30)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.13](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.12...@stencila/eslint-config@2.0.13) (2021-06-23)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.12](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.11...@stencila/eslint-config@2.0.12) (2021-06-10)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.11](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.10...@stencila/eslint-config@2.0.11) (2021-06-09)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.10](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.9...@stencila/eslint-config@2.0.10) (2021-06-02)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.9](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.8...@stencila/eslint-config@2.0.9) (2021-05-12)
### Bug Fixes
- **Deps:** Update dependencies ([95e2d5b](https://github.com/stencila/dev-config/commit/95e2d5bf3f628ca2eaef43077aa2e3fd3316d2be))
## [2.0.8](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.7...@stencila/eslint-config@2.0.8) (2021-05-12)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.7](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.6...@stencila/eslint-config@2.0.7) (2021-05-07)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.6](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.5...@stencila/eslint-config@2.0.6) (2021-05-07)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.5](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.4...@stencila/eslint-config@2.0.5) (2021-03-10)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.4](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.3...@stencila/eslint-config@2.0.4) (2021-03-03)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to v8 ([a8ba400](https://github.com/stencila/dev-config/commit/a8ba40089a127e542bd7208d746ca9816597621b))
## [2.0.3](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.2...@stencila/eslint-config@2.0.3) (2021-03-03)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.2](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.1...@stencila/eslint-config@2.0.2) (2021-02-17)
**Note:** Version bump only for package @stencila/eslint-config
## [2.0.1](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@2.0.0...@stencila/eslint-config@2.0.1) (2021-02-11)
### Bug Fixes
- **ESLint config:** Add unused vars patterns ([43cef6e](https://github.com/stencila/dev-config/commit/43cef6e))
# [2.0.0](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.69...@stencila/eslint-config@2.0.0) (2021-02-09)
### Bug Fixes
- **Dependencies:** Update dependency standard to v16 ([cbbadd9](https://github.com/stencila/dev-config/commit/cbbadd9))
### BREAKING CHANGES
- **Dependencies:** Some significant changes to default StandardJS options
See: https://standardjs.com/changelog.html
## [1.3.69](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.68...@stencila/eslint-config@1.3.69) (2021-01-14)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.13.0 ([96dd0a1](https://github.com/stencila/dev-config/commit/96dd0a1))
## [1.3.68](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.67...@stencila/eslint-config@1.3.68) (2021-01-07)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-prettier to ^3.3.1 ([9994c3c](https://github.com/stencila/dev-config/commit/9994c3c))
## [1.3.67](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.66...@stencila/eslint-config@1.3.67) (2021-01-07)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.12.0 ([a2631e5](https://github.com/stencila/dev-config/commit/a2631e5))
## [1.3.66](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.65...@stencila/eslint-config@1.3.66) (2021-01-06)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.17.0 ([2bb9b74](https://github.com/stencila/dev-config/commit/2bb9b74))
## [1.3.65](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.64...@stencila/eslint-config@1.3.65) (2021-01-02)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react to ^7.22.0 ([b872ad6](https://github.com/stencila/dev-config/commit/b872ad6))
## [1.3.64](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.63...@stencila/eslint-config@1.3.64) (2020-12-31)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.11.1 ([7346cf8](https://github.com/stencila/dev-config/commit/7346cf8))
## [1.3.63](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.62...@stencila/eslint-config@1.3.63) (2020-12-24)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.11.0 ([5e86830](https://github.com/stencila/dev-config/commit/5e86830))
## [1.3.62](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.61...@stencila/eslint-config@1.3.62) (2020-12-23)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to ^7.1.0 ([b12c118](https://github.com/stencila/dev-config/commit/b12c118))
## [1.3.61](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.60...@stencila/eslint-config@1.3.61) (2020-12-23)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.16.0 ([d740bca](https://github.com/stencila/dev-config/commit/d740bca))
## [1.3.60](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.59...@stencila/eslint-config@1.3.60) (2020-12-17)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.10.0 ([9de52d9](https://github.com/stencila/dev-config/commit/9de52d9))
## [1.3.59](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.58...@stencila/eslint-config@1.3.59) (2020-12-17)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-prettier to ^3.3.0 ([0c9d5bf](https://github.com/stencila/dev-config/commit/0c9d5bf))
## [1.3.58](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.57...@stencila/eslint-config@1.3.58) (2020-12-16)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.57](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.56...@stencila/eslint-config@1.3.57) (2020-12-10)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.9.1 ([086128c](https://github.com/stencila/dev-config/commit/086128c))
## [1.3.56](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.55...@stencila/eslint-config@1.3.56) (2020-12-09)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to v7 ([31a587c](https://github.com/stencila/dev-config/commit/31a587c))
## [1.3.55](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.54...@stencila/eslint-config@1.3.55) (2020-12-09)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-prettier to ^3.2.0 ([720ddbb](https://github.com/stencila/dev-config/commit/720ddbb))
## [1.3.54](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.53...@stencila/eslint-config@1.3.54) (2020-12-09)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.15.0 ([af7f68e](https://github.com/stencila/dev-config/commit/af7f68e))
## [1.3.53](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.52...@stencila/eslint-config@1.3.53) (2020-12-07)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.52](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.51...@stencila/eslint-config@1.3.52) (2020-12-03)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.9.0 ([c624afe](https://github.com/stencila/dev-config/commit/c624afe))
## [1.3.51](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.50...@stencila/eslint-config@1.3.51) (2020-11-26)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.8.2 ([759effa](https://github.com/stencila/dev-config/commit/759effa))
## [1.3.50](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.49...@stencila/eslint-config@1.3.50) (2020-11-25)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.14.0 ([f24736f](https://github.com/stencila/dev-config/commit/f24736f))
## [1.3.49](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.48...@stencila/eslint-config@1.3.49) (2020-11-25)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.48](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.47...@stencila/eslint-config@1.3.48) (2020-11-20)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.8.1 ([979ecc4](https://github.com/stencila/dev-config/commit/979ecc4))
## [1.3.47](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.46...@stencila/eslint-config@1.3.47) (2020-11-12)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.7.0 ([c65dfaa](https://github.com/stencila/dev-config/commit/c65dfaa))
## [1.3.46](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.45...@stencila/eslint-config@1.3.46) (2020-11-11)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.13.0 ([ec82fd5](https://github.com/stencila/dev-config/commit/ec82fd5))
## [1.3.45](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.44...@stencila/eslint-config@1.3.45) (2020-11-05)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.6.1 ([a82cdb9](https://github.com/stencila/dev-config/commit/a82cdb9))
## [1.3.44](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.43...@stencila/eslint-config@1.3.44) (2020-10-30)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to ^6.15.0 ([a280b41](https://github.com/stencila/dev-config/commit/a280b41))
## [1.3.43](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.42...@stencila/eslint-config@1.3.43) (2020-10-30)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.12.1 ([eece3e1](https://github.com/stencila/dev-config/commit/eece3e1))
## [1.3.42](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.41...@stencila/eslint-config@1.3.42) (2020-10-30)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.41](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.40...@stencila/eslint-config@1.3.41) (2020-10-29)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.6.0 ([2b447f9](https://github.com/stencila/dev-config/commit/2b447f9))
## [1.3.40](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.39...@stencila/eslint-config@1.3.40) (2020-10-23)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.2.0 ([6226878](https://github.com/stencila/dev-config/commit/6226878))
## [1.3.39](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.38...@stencila/eslint-config@1.3.39) (2020-10-23)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react to ^7.21.5 ([2afac22](https://github.com/stencila/dev-config/commit/2afac22))
## [1.3.38](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.37...@stencila/eslint-config@1.3.38) (2020-10-22)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.5.0 ([621f971](https://github.com/stencila/dev-config/commit/621f971))
## [1.3.37](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.36...@stencila/eslint-config@1.3.37) (2020-10-21)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to ^6.13.0 ([23d9b8a](https://github.com/stencila/dev-config/commit/23d9b8a))
## [1.3.36](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.35...@stencila/eslint-config@1.3.36) (2020-10-15)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.4.1 ([7af437b](https://github.com/stencila/dev-config/commit/7af437b))
## [1.3.35](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.34...@stencila/eslint-config@1.3.35) (2020-10-14)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react to ^7.21.4 ([64f442e](https://github.com/stencila/dev-config/commit/64f442e))
## [1.3.34](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.33...@stencila/eslint-config@1.3.34) (2020-10-14)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.11.0 ([4cd55ef](https://github.com/stencila/dev-config/commit/4cd55ef))
## [1.3.33](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.32...@stencila/eslint-config@1.3.33) (2020-10-08)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.4.0 ([fddc809](https://github.com/stencila/dev-config/commit/fddc809))
## [1.3.32](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.31...@stencila/eslint-config@1.3.32) (2020-10-07)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react to ^7.21.3 ([f452695](https://github.com/stencila/dev-config/commit/f452695))
## [1.3.31](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.30...@stencila/eslint-config@1.3.31) (2020-10-01)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.3.0 ([f529494](https://github.com/stencila/dev-config/commit/f529494))
## [1.3.30](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.29...@stencila/eslint-config@1.3.30) (2020-09-30)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to ^6.12.0 ([b897ae9](https://github.com/stencila/dev-config/commit/b897ae9))
## [1.3.29](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.28...@stencila/eslint-config@1.3.29) (2020-09-28)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react to ^7.21.2 ([a9523e7](https://github.com/stencila/dev-config/commit/a9523e7))
## [1.3.28](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.27...@stencila/eslint-config@1.3.28) (2020-09-28)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^4.2.0 ([83480de](https://github.com/stencila/dev-config/commit/83480de))
## [1.3.27](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.26...@stencila/eslint-config@1.3.27) (2020-09-28)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.10.0 ([02a2329](https://github.com/stencila/dev-config/commit/02a2329))
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.1.2 ([0c60fbb](https://github.com/stencila/dev-config/commit/0c60fbb))
## [1.3.26](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.25...@stencila/eslint-config@1.3.26) (2020-09-09)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to v4 ([47a16d6](https://github.com/stencila/dev-config/commit/47a16d6))
## [1.3.25](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.24...@stencila/eslint-config@1.3.25) (2020-09-09)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.8.1 ([6aa9463](https://github.com/stencila/dev-config/commit/6aa9463))
## [1.3.24](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.23...@stencila/eslint-config@1.3.24) (2020-08-27)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.23](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.22...@stencila/eslint-config@1.3.23) (2020-08-27)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^3.10.1 ([828890e](https://github.com/stencila/dev-config/commit/828890e))
## [1.3.22](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.21...@stencila/eslint-config@1.3.22) (2020-08-19)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^3.9.1 ([82e1dd8](https://github.com/stencila/dev-config/commit/82e1dd8))
## [1.3.21](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.20...@stencila/eslint-config@1.3.21) (2020-08-19)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react to ^7.20.6 ([159f15a](https://github.com/stencila/dev-config/commit/159f15a))
## [1.3.20](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.19...@stencila/eslint-config@1.3.20) (2020-08-19)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.7.0 ([17ab988](https://github.com/stencila/dev-config/commit/17ab988))
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.1.0 ([0f32800](https://github.com/stencila/dev-config/commit/0f32800))
## [1.3.19](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.18...@stencila/eslint-config@1.3.19) (2020-08-13)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^3.9.0 ([ae8a0a7](https://github.com/stencila/dev-config/commit/ae8a0a7))
## [1.3.18](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.17...@stencila/eslint-config@1.3.18) (2020-08-10)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^3.8.0 ([b374446](https://github.com/stencila/dev-config/commit/b374446))
## [1.3.17](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.16...@stencila/eslint-config@1.3.17) (2020-08-10)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.6.0 ([d46b273](https://github.com/stencila/dev-config/commit/d46b273))
- **dependencies:** update dependency eslint-plugin-react to ^7.20.5 ([1b3e7cb](https://github.com/stencila/dev-config/commit/1b3e7cb))
## [1.3.16](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.15...@stencila/eslint-config@1.3.16) (2020-07-23)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.5.0 ([7758771](https://github.com/stencila/dev-config/commit/7758771))
## [1.3.15](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.14...@stencila/eslint-config@1.3.15) (2020-07-21)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.14](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.13...@stencila/eslint-config@1.3.14) (2020-07-21)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.0.8 ([6d41d20](https://github.com/stencila/dev-config/commit/6d41d20))
- **dependencies:** update typescript-eslint monorepo to ^3.7.0 ([bbd2875](https://github.com/stencila/dev-config/commit/bbd2875))
## [1.3.13](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.12...@stencila/eslint-config@1.3.13) (2020-07-08)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.4.0 ([6761137](https://github.com/stencila/dev-config/commit/6761137))
## [1.3.12](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.11...@stencila/eslint-config@1.3.12) (2020-07-08)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.0.6 ([8c47a64](https://github.com/stencila/dev-config/commit/8c47a64))
- **dependencies:** update typescript-eslint monorepo to ^3.6.0 ([13b9464](https://github.com/stencila/dev-config/commit/13b9464))
## [1.3.11](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.10...@stencila/eslint-config@1.3.11) (2020-07-03)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.0.5 ([d948ff7](https://github.com/stencila/dev-config/commit/d948ff7))
## [1.3.10](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.9...@stencila/eslint-config@1.3.10) (2020-07-03)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^3.5.0 ([4f2c70d](https://github.com/stencila/dev-config/commit/4f2c70d))
## [1.3.9](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.8...@stencila/eslint-config@1.3.9) (2020-07-03)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.8](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.7...@stencila/eslint-config@1.3.8) (2020-07-03)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react to ^7.20.3 ([44891ab](https://github.com/stencila/dev-config/commit/44891ab))
## [1.3.7](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.6...@stencila/eslint-config@1.3.7) (2020-07-03)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.3.1 ([734877e](https://github.com/stencila/dev-config/commit/734877e))
## [1.3.6](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.5...@stencila/eslint-config@1.3.6) (2020-06-17)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-prettier to ^3.1.4 ([5cc0678](https://github.com/stencila/dev-config/commit/5cc0678))
- **dependencies:** update typescript-eslint monorepo to ^3.3.0 ([c4b52b5](https://github.com/stencila/dev-config/commit/c4b52b5))
## [1.3.5](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.4...@stencila/eslint-config@1.3.5) (2020-06-17)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.2.0 ([eda645c](https://github.com/stencila/dev-config/commit/eda645c))
## [1.3.4](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.3...@stencila/eslint-config@1.3.4) (2020-06-05)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^3.1.0 ([7ae9637](https://github.com/stencila/dev-config/commit/7ae9637))
## [1.3.3](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.2...@stencila/eslint-config@1.3.3) (2020-06-05)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.2](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.1...@stencila/eslint-config@1.3.2) (2020-05-27)
**Note:** Version bump only for package @stencila/eslint-config
## [1.3.1](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.3.0...@stencila/eslint-config@1.3.1) (2020-05-27)
### Bug Fixes
- **ESLint:** Use update ban-ts-ignore rule name ([ae301c7](https://github.com/stencila/dev-config/commit/ae301c7))
# [1.3.0](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.24...@stencila/eslint-config@1.3.0) (2020-05-27)
### Features
- **ESLint:** Enable no-shadow rule. Close [#64](https://github.com/stencila/dev-config/issues/64) ([812c8f2](https://github.com/stencila/dev-config/commit/812c8f2))
## [1.2.24](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.23...@stencila/eslint-config@1.2.24) (2020-05-27)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to v3 ([86cc18f](https://github.com/stencila/dev-config/commit/86cc18f))
## [1.2.23](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.22...@stencila/eslint-config@1.2.23) (2020-05-27)
### Bug Fixes
- **dependencies:** update dependency eslint to ^7.1.0 ([7ce938f](https://github.com/stencila/dev-config/commit/7ce938f))
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.0.4 ([4c1a962](https://github.com/stencila/dev-config/commit/4c1a962))
## [1.2.22](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.21...@stencila/eslint-config@1.2.22) (2020-05-20)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.0.2 ([2061071](https://github.com/stencila/dev-config/commit/2061071))
- **dependencies:** update typescript-eslint monorepo to ^2.34.0 ([464d4de](https://github.com/stencila/dev-config/commit/464d4de))
## [1.2.21](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.20...@stencila/eslint-config@1.2.21) (2020-05-20)
**Note:** Version bump only for package @stencila/eslint-config
## [1.2.20](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.19...@stencila/eslint-config@1.2.20) (2020-05-13)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react-hooks to ^4.0.1 ([d6e28c8](https://github.com/stencila/dev-config/commit/d6e28c8))
## [1.2.19](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.18...@stencila/eslint-config@1.2.19) (2020-05-13)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react to ^7.20.0 ([f49c762](https://github.com/stencila/dev-config/commit/f49c762))
- **dependencies:** update typescript-eslint monorepo to ^2.33.0 ([64aa05f](https://github.com/stencila/dev-config/commit/64aa05f))
## [1.2.18](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.17...@stencila/eslint-config@1.2.18) (2020-05-13)
### Bug Fixes
- **dependencies:** update dependency eslint to v7 ([efd2474](https://github.com/stencila/dev-config/commit/efd2474))
- **dependencies:** update dependency standard to ^14.3.4 ([f4fd4df](https://github.com/stencila/dev-config/commit/f4fd4df))
## [1.2.17](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.16...@stencila/eslint-config@1.2.17) (2020-05-13)
**Note:** Version bump only for package @stencila/eslint-config
## [1.2.16](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.15...@stencila/eslint-config@1.2.16) (2020-05-07)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react-hooks to v4 ([011f171](https://github.com/stencila/dev-config/commit/011f171))
- **dependencies:** update typescript-eslint monorepo to ^2.31.0 ([148a7d6](https://github.com/stencila/dev-config/commit/148a7d6))
## [1.2.15](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.14...@stencila/eslint-config@1.2.15) (2020-04-23)
**Note:** Version bump only for package @stencila/eslint-config
## [1.2.14](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.13...@stencila/eslint-config@1.2.14) (2020-04-23)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to ^6.11.0 ([845ef84](https://github.com/stencila/dev-config/commit/845ef84))
## [1.2.13](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.12...@stencila/eslint-config@1.2.13) (2020-04-23)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^2.29.0 ([5222857](https://github.com/stencila/dev-config/commit/5222857))
## [1.2.12](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.11...@stencila/eslint-config@1.2.12) (2020-04-15)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-prettier to ^3.1.3 ([7610962](https://github.com/stencila/dev-config/commit/7610962))
## [1.2.11](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.10...@stencila/eslint-config@1.2.11) (2020-04-14)
### Bug Fixes
- **dependencies:** update dependency eslint-plugin-react-hooks to v3 ([894cd65](https://github.com/stencila/dev-config/commit/894cd65))
- **dependencies:** update typescript-eslint monorepo to ^2.28.0 ([fa5b024](https://github.com/stencila/dev-config/commit/fa5b024))
## [1.2.10](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.9...@stencila/eslint-config@1.2.10) (2020-04-14)
**Note:** Version bump only for package @stencila/eslint-config
## [1.2.9](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.8...@stencila/eslint-config@1.2.9) (2020-03-27)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to ^6.10.1 ([ecb50f4](https://github.com/stencila/dev-config/commit/ecb50f4))
- **dependencies:** update dependency eslint-plugin-react-hooks to ^2.5.1 ([17dac54](https://github.com/stencila/dev-config/commit/17dac54))
- **dependencies:** update typescript-eslint monorepo to ^2.25.0 ([eebe278](https://github.com/stencila/dev-config/commit/eebe278))
## [1.2.8](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.7...@stencila/eslint-config@1.2.8) (2020-03-18)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^2.24.0 ([b43709f](https://github.com/stencila/dev-config/commit/b43709f))
## [1.2.7](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.6...@stencila/eslint-config@1.2.7) (2020-03-18)
### Bug Fixes
- **dependencies:** update dependency @stencil/eslint-plugin to ^0.3.1 ([475f292](https://github.com/stencila/dev-config/commit/475f292))
- **dependencies:** update dependency standard to ^14.3.3 ([2f9e4ae](https://github.com/stencila/dev-config/commit/2f9e4ae))
- **dependencies:** update typescript-eslint monorepo to ^2.23.0 ([55c5a25](https://github.com/stencila/dev-config/commit/55c5a25))
## [1.2.6](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.5...@stencila/eslint-config@1.2.6) (2020-03-09)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^2.22.0 ([b459af6](https://github.com/stencila/dev-config/commit/b459af6))
## [1.2.5](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.4...@stencila/eslint-config@1.2.5) (2020-02-26)
### Bug Fixes
- **dependencies:** update typescript-eslint monorepo to ^2.21.0 ([d51d8ad](https://github.com/stencila/dev-config/commit/d51d8ad))
## [1.2.4](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.3...@stencila/eslint-config@1.2.4) (2020-02-26)
**Note:** Version bump only for package @stencila/eslint-config
## [1.2.3](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.2...@stencila/eslint-config@1.2.3) (2020-02-26)
### Bug Fixes
- **dependencies:** update dependency eslint to ^6.8.0 ([3cc1084](https://github.com/stencila/dev-config/commit/3cc1084))
## [1.2.2](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.1...@stencila/eslint-config@1.2.2) (2020-02-26)
### Bug Fixes
- **dependencies:** update dependency eslint-config-prettier to ^6.10.0 ([b71368b](https://github.com/stencila/dev-config/commit/b71368b))
## [1.2.1](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.2.0...@stencila/eslint-config@1.2.1) (2020-01-22)
**Note:** Version bump only for package @stencila/eslint-config
# [1.2.0](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.10...@stencila/eslint-config@1.2.0) (2020-01-22)
### Features
- **Eslint:** Add new null coalescing and optional chaining rules ([3931747](https://github.com/stencila/dev-config/commit/3931747))
## [1.1.10](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.9...@stencila/eslint-config@1.1.10) (2020-01-07)
**Note:** Version bump only for package @stencila/eslint-config
## [1.1.9](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.8...@stencila/eslint-config@1.1.9) (2019-12-17)
**Note:** Version bump only for package @stencila/eslint-config
## [1.1.8](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.7...@stencila/eslint-config@1.1.8) (2019-12-16)
**Note:** Version bump only for package @stencila/eslint-config
## [1.1.7](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.6...@stencila/eslint-config@1.1.7) (2019-11-22)
**Note:** Version bump only for package @stencila/eslint-config
## [1.1.6](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.5...@stencila/eslint-config@1.1.6) (2019-11-21)
**Note:** Version bump only for package @stencila/eslint-config
## [1.1.5](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.4...@stencila/eslint-config@1.1.5) (2019-11-21)
**Note:** Version bump only for package @stencila/eslint-config
## [1.1.4](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.3...@stencila/eslint-config@1.1.4) (2019-10-16)
### Bug Fixes
- **ESLint:** Relax strict-boolean-expressions rule for null & undefined ([94f292b](https://github.com/stencila/dev-config/commit/94f292b))
## [1.1.3](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.2...@stencila/eslint-config@1.1.3) (2019-10-16)
**Note:** Version bump only for package @stencila/eslint-config
## [1.1.2](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.1...@stencila/eslint-config@1.1.2) (2019-09-04)
**Note:** Version bump only for package @stencila/eslint-config
## [1.1.1](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.1.0...@stencila/eslint-config@1.1.1) (2019-07-12)
### Bug Fixes
- **Install:** Fix install issues and add postinstall hook ([12b0294](https://github.com/stencila/dev-config/commit/12b0294))
# [1.1.0](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.0.5...@stencila/eslint-config@1.1.0) (2019-07-11)
### Bug Fixes
- **ESLint:** Add missing project config field ([2d8bbdb](https://github.com/stencila/dev-config/commit/2d8bbdb))
- **ESLint:** Add StencilJS lint configuration file to package files ([8e3c091](https://github.com/stencila/dev-config/commit/8e3c091))
- **ESLint:** Fix issues with using configuration from other projects ([c47c2a6](https://github.com/stencila/dev-config/commit/c47c2a6))
- **ESLint:** Fix typo in Linting rule configuration ([ba6d669](https://github.com/stencila/dev-config/commit/ba6d669))
### Features
- **ESLint:** Add custom linting rules ([91cd2f5](https://github.com/stencila/dev-config/commit/91cd2f5))
## [1.0.5](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.0.4...@stencila/eslint-config@1.0.5) (2019-06-19)
### Bug Fixes
- **Lerna:** Fix install issues when bootstrapping the project ([c6f0da1](https://github.com/stencila/dev-config/commit/c6f0da1))
## [1.0.4](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.0.3...@stencila/eslint-config@1.0.4) (2019-06-18)
**Note:** Version bump only for package @stencila/eslint-config
## [1.0.3](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.0.2...@stencila/eslint-config@1.0.3) (2019-06-18)
**Note:** Version bump only for package @stencila/eslint-config
## [1.0.2](https://github.com/stencila/dev-config/compare/@stencila/eslint-config@1.0.1...@stencila/eslint-config@1.0.2) (2019-06-18)
**Note:** Version bump only for package @stencila/eslint-config
## 1.0.1 (2019-06-18)
**Note:** Version bump only for package @stencila/eslint-config
| 50.011765 | 166 | 0.721896 | yue_Hant | 0.216862 |
87cfea31485ccfa333ffe91c15a07379f3d97a80 | 4,363 | md | Markdown | README.md | Janchorizo/boes-bot | 97ecbb4aea407034204d3d01609da14e71732d2a | [
"Apache-2.0"
] | null | null | null | README.md | Janchorizo/boes-bot | 97ecbb4aea407034204d3d01609da14e71732d2a | [
"Apache-2.0"
] | null | null | null | README.md | Janchorizo/boes-bot | 97ecbb4aea407034204d3d01609da14e71732d2a | [
"Apache-2.0"
] | null | null | null | # boes-bot
A Telegram bot implementation for exposing BOE information.
## Cómo está organizado
El paquete telegram implementa un wrapper alrededor de la api HTTP para que sea más cómodo recibir y mandar mensajes.
Hay siete módulos en total, de los cuales varios son sólo para uso interno:
- `telegram.base` Provee la clase base _Method_ que se usa en _method_factory_ para crear funciones HTTP automáticamente.
- `telegram.methods` Tiene una lista de _telegram.base.MethodDesc_ que se pasa a _telegram.base.method_factory_ para crear
cada llamada HTTP. De esta forma, todas las llamadas HTTP de la API se pueden hacer con este módulo:
```python
from telegram import methods
# Para descargar un documento (max 20MB)
params = {'file_id': id_del_documento}
status, file = methods.getFile(token, params=params, verbose=True)
```
Todas las llamadas a peticiciones HTTP tienen el parámetro opcional verbose para que imprima todo por consola.
- `telegram.types` Los updates se pasan como una de estas clases. Esto permite que puedas hacer:
```
from telegram import types
update.type == types.ChosenInlineResult
```
- Las llamadas usando `telegram.methods` son un poco coñazo de usar. Por eso hay cuatro módulos que son los que realmente
están pensados para usarse:
- `telegram.admin` Provee una serie de utilidades para gestionar el bot. Lo más útil es la clase `Webhook` para usar la conexión
por webhooks con un _context manager_. Cuando se termina el código de ese bloque, el webhook se quita sólo, así sólo está
puesto mientras tengas el bot activo.
```python
with admin.Webhook(token, url, max_connections, drop_pending_updates=True) as wb:
app = crear_tu_app(token)
app.run()
```
- `telegram.chat` Son utilidades relacionadas con la gestión de chats: cambiar la desc, banear personas, pinnear mensajes, ...
- `telegram.content` Tiene tres funciones relacionadas con contenido: obtener imágenes de perfil, documentos y actualizaciones.
También tiene la clase `Update`; getUpdates o las llamadas por webhook mandan una respuesta HTTP al bot, y Update se usa para
que sea más cómodo comparar el tipo y el contenido.
- `telegram.messages` Es el módulo que más chicha tiene. En vez de tener funciones con muchos argumentos, son clases: heredan de
`Content` o `ReplacementContent` en función de si es contenido que se envía o un contenido que se sobreescribe. La forma de usarlo
es de la siguiente manera:
```python
# creas el contenido que quieres mandar; en este caso con los parámetros opcionales parse_mode para que puedas usar negrita
# en el texto.
msg = messages.MessageContent(text=global_options_text, parse_mode='MarkdownV2')
# una vez instanciado se puede enviar tantas veces se quiera
msg.send(token, chat_id)
# y como cualquier otra petición HTTP, puedes usarlo de forma verbosa:
msg.send(token, chat_id, verbose=True)
```
## ¿Cómo se usaría?
Bien porque tengas una API y uses webhook o bien porque llames a getUpdates y recibas una respuesta HTTP, vas a terminar con un
cuerpo JSON serializado. Parseas el body usando `json.loads` e instancias `telegram.content.Update` con el diccionario que te da. _También puedes usar directamente Update.fromraw(el_cuerpo_de_la_respuesta_sin_decodificar)_.
Un objeto _Update_ tiene un atributo _content_ con toda la info de la llamada al bot. Es del tipo que tenga `update.type`, y se usa como un diccionario.
Adicionalmente, si el update es de tipo `CallbackQuery` o `Message` también tiene un atributo _cid_ que el código del chat; porque el resto de updates
no van asociadas a un chat y no son para responder a una persona:
> Por ejemplo `InlineQuery` es una actualización que usas para implementar búsqueda en el teclado, es lo que te permite buscar emojis: el usuario escribe
> en el teclado se le manda un `InlineQuery` al bot para que devuelva opciones, así puedes picar en un resultado y enviarlo. Por eso no puedes contestar
> perse.
Entonces, **¿Cómo respondo a un mensaje?** Fácil:
1. Recibes el mensaje y creas el objeto update con el cuerpo que te mandan.
2. Creas (o usas un mensaje que ya tengas) el mensaje.
3. Envías el mensaje al mimso chat: `msg.send(token, update.content.cid)`
| 62.328571 | 223 | 0.749026 | spa_Latn | 0.997445 |
87d0cbc81c404ce58fe8ae1cd5af0416bb970d18 | 5,925 | md | Markdown | _posts/2020-02-19-inilah-beberapa-hal-yang-dibutuhkan-ketika-belajar-bahasa-inggris.md | kandra-id/amp-template0 | e4e93b03f6c8ab45d1b2750205d1d3ce882aec4f | [
"MIT"
] | null | null | null | _posts/2020-02-19-inilah-beberapa-hal-yang-dibutuhkan-ketika-belajar-bahasa-inggris.md | kandra-id/amp-template0 | e4e93b03f6c8ab45d1b2750205d1d3ce882aec4f | [
"MIT"
] | null | null | null | _posts/2020-02-19-inilah-beberapa-hal-yang-dibutuhkan-ketika-belajar-bahasa-inggris.md | kandra-id/amp-template0 | e4e93b03f6c8ab45d1b2750205d1d3ce882aec4f | [
"MIT"
] | null | null | null | ---
id: 5383
title: Inilah Beberapa Hal yang Dibutuhkan Ketika Belajar Bahasa Inggris
date: 2020-02-19T15:01:38+00:00
author: kandra
layout: post
guid: https://pencaricerah.com/?p=5383
permalink: /inilah-beberapa-hal-yang-dibutuhkan-ketika-belajar-bahasa-inggris/
tag: sponsored
---
Sekarang ini penggunaan bahasa Inggris untuk berkomunikasi dalam bisnis sudah digantikan dengan bahasa Mandarin. Hal ini banyak dipengaruhi dengan perkembangan ekonomi negeri Tiongkok yang mulai menggoyang beberapa negara adidaya seperti Amerika Serikat. Meskipun begitu masih banyak yang berpendapat menguasai bahasa Inggris tetap diperlukan karena merupakan bahasa pengantar Internasional yang belum tergantikan sepenuhnya oleh bahasa asing lainnya. Termasuk Bahasa Indonesia.
Saat ini dengan tren industri 4.0 belajar bahasa Inggris tidak perlu lagi datang ke tempat kursus. Kita cukup mengunduh aplikasi lalu menggunakan smartphone untuk mengikuti [kursus bahasa Inggris online](https://www.ef.co.id/englishfirst/adults/courses/efset/)** **yang diadakan beberapa lembaga pendidikan.
Sejatinya ada empat aspek yang akan kita dapatkan dalam berkomunikasi. Keempat aspek ini sebaiknya ada di tempat kursus Anda saat mempelajari sebuah bahasa asing. Keempat aspek itu adalah berbicara, membaca, menulis, dan mendengarkan.
Jangan berniat untuk menguasai HANYA satu aspek saja, menguasai satu lalu meninggalkan yang lain sama saja membuat kita gagal dalam mengantarkan ide yang kita punya kepada orang lain. Ini yang paling dihindari apalagi jika Anda harus berkomunikasi untuk bisnis atau usaha yang terkait dengan orang asing.
Kenapa harus menguasai keempatnya kalau bisa menguasai satu aspek saja?
Aspek yang paling penting dalam berkomunikasi adalah mendengar. Maksudnya bagaimana kita benar-benar mendengar apa yang disampaikan oleh orang yang menjadi lawan bicara. Tidak menguasai aspek mendengar akan membuat bencana. Maka dari itu aspek mendengar merupakan tingkat kemampuan seseorang memahami setiap kata maupun kalimat yang disampaikan lawan bicara secara utuh. Aspek mendengar terkait erat dengan aspek berbicara.
Banyak orang berpendapat kalau untuk bisnis yang penting menguasai aspek berbicara saja. Ini anggapan yang tak sepenuhnya SALAH. Dengan berbicara akan terlihat bagaimana kemampuan kita dalam menguasai informasi yang disampaikan oleh lawan bicara dan juga tingkat kepahaman kita dengan menyampaikan tanggapan dengan berbagai kosa kata yang sesuai. Dalam pembicaraan bisnis kita tidak hanya berkomunikasi dua arah secara langsung tapi kita menuliskan permintaan atau hasil pembicaraan yang berlangsung sesuai dengan bagaimana pembicaraan itu terjadi.
Aspek menulis dalam berkomunikasi merupakan sebuah aktifitas yang tidak banyak orang bisa melakukannya. Kita bisa menilai kemampuan seseorang dengan membaca tulisannya. Orang yang terbiasa membaca dan menulis biasanya akan lebih mudah mengeluarkan ide-ide yang ada dikepalanya dengan runut hingga pembaca tulisan pun akan mengerti maksud dan tujuan dari tulisan tersebut. Beda dengan orang yang TERPAKSA menulis. Penggunaan kosa kata orang yang tak terbiasa menulis dan membaca sangat sedikit dibandingkan dengan orang yang terbiasa menulis dan membaca. Bahkan dari sisi penyampaikan maksud dan tujuan, orang yang terbiasa menulis dan membaca mampu menyampaikan langsung pada intinya, sedangkan orang yang tidak terbiasa kemungkinan besar akan menyampaikan maksud dan tujuan dengan bertele-tele.
Agar memiliki banyak kosa kata dan menyampaikan sebuah informasi dengan tepat dan tidak bertele-tele kita tidak mungkin menghiraukan aspek membaca. Berbeda dengan kita, bagi orang asing membaca merupakan sebuah prioritas dalam rutinitas mereka. Dengan membaca kita tidak hanya mendapatkan sebuah informasi tetapi juga menambah perbendaharaan kata yang bisa kita gunakan untuk berkomunikasi dengan beragam karakter orang.
Jadi kita tidak bisa melepas keempat aspek dalam berkomunikasi karena saling berkaitan antara satu dan lainnya.
Duh terlihat berat ya?
Kalau dilihat dari teori komunikasi diatas kelihatannya memang berat padahal tidak. Berikut adalah hal yang dibutuhkan jika belajar bahasa Inggris:
* Memiliki tujuan belajar yang tinggi, motivasi dan niat sangat diperlukan karena akan banyak kesulitan yang ditemui sehingga akan tetap menjaga niat awal.
* Menerima segala kesulitan yang akan dihadapi karena proses belajar tidaklah mudah.
* Sebagai pelajar maka fokus terhadap proses bukan hasilnya karena proses sangat menentukan hasil dan perlu dipahami bahwa setiap orang memiliki tingkat kesulitan yang berbeda-beda.
* Berikan pikiran positif yang akan mendukung keberhasilan dalam belajar bahasa Inggris sehingga akan membantu kemampuan berkembang.
* Habiskan waktu dengan orang yang menyukai belajar bahasa Inggris dengan baik sehingga akan memberikan motivasi.
TIPS:
Untuk menguasai bahasa Inggris dengan cepat. Banyaklah menonton film Hollywood atau film yang bersubtitle berbahasa Inggris. Banyak orang yang lebih suka media audio visual yang terdapat saat menonton film. Ketika menonton film kita tidak hanya melatih aspek mendengar tapi juga aspek berbicara. Kita mendapatkan aspek mendengar dari dialog yang terjadi antar peran di film tersebut dan kita juga mendapat aspek berbicara jika kita mengikuti dialog salah satu pemeran di film yang kita tonton.
Apabila masih bingung dalam beberapa kosakata dan penggunaan grammar maka dapat segera mengunjungi lembaga bahasa Inggris. Salah satu lembaga pendidikan bahasa Inggris adalah **[EF adults](https://www.ef.co.id/englishfirst/adults/)**. EF memiliki lokasi di Jakarta dan Surabaya. Dapat menggunakan sistem belajar online maupun offline dengan akses perangkat 24 jam dan lebih mudah dengan adanya kelas online smart kreatif sehingga akan membantu peserta dalam melatih teknik pengucapan yang benar serta memiliki life club untuk menonton film bersama dengan teman kursus.
| 128.804348 | 795 | 0.838987 | ind_Latn | 0.991468 |
87d103e64b771de7113eaa5a7c3c1adfa815f536 | 196 | md | Markdown | README.md | iidamasaki/treehash | 726e5394e50f2e329895c17d31f69246476fb3ff | [
"MIT"
] | null | null | null | README.md | iidamasaki/treehash | 726e5394e50f2e329895c17d31f69246476fb3ff | [
"MIT"
] | null | null | null | README.md | iidamasaki/treehash | 726e5394e50f2e329895c17d31f69246476fb3ff | [
"MIT"
] | null | null | null | # treehash
## Usage
```
treehash <file>
```
## Example
```
$ dd bs=1m count=10 if=/dev/zero of=test.bin
$ treehash test.bin
7130ecc84a289d83a9563a06260785e4081c6c660090052bd5e77c3b0060910b
```
| 14 | 64 | 0.72449 | kor_Hang | 0.181889 |
87d15ddf2af3e75bdfe058d40f1b6f7a7ab1f095 | 814 | md | Markdown | README.md | dukebody/israbot | fa6477a89db911b3e11f7d98afb9b3a80793320a | [
"MIT"
] | null | null | null | README.md | dukebody/israbot | fa6477a89db911b3e11f7d98afb9b3a80793320a | [
"MIT"
] | null | null | null | README.md | dukebody/israbot | fa6477a89db911b3e11f7d98afb9b3a80793320a | [
"MIT"
] | null | null | null | # Israbot
Bot to send a reminder message about open PRs in a certain public repo.
## Usage
- Follow [the Slack instructions to create an incoming webhook](https://api.slack.com/incoming-webhooks) for the channel where you want the notifications to show up.
- Clone this repo to the host you want to use to send the notifications from.
- Install the requirements (better in a virtualenv) with:
```
pip install -r requirements.txt
```
- Create a script next to `israbot.py` with the contents:
```
import israbot
message = israbot.message_open_pull_requests('GH_ORGANIZATION', 'GH_REPO')
webhook_url = "https://hooks.slack.com/services/WEBHOOK_URL_FROM_FIRST_STEP"
israbot.post_to_slack(message, webhook_url)
```
That's it. Configure a cronjob or similar to run the script with the desired frequency and enjoy!
| 33.916667 | 165 | 0.773956 | eng_Latn | 0.965793 |
87d1c547a4ec01f19d5377a81d120d74454c824e | 1,343 | md | Markdown | docs/menu/demo/hoz.md | itmajing/next | 77bc4eceaf615a7179ea1d36756c3d6d727b1d5c | [
"MIT"
] | 4,289 | 2018-07-18T09:21:03.000Z | 2022-03-31T17:59:14.000Z | docs/menu/demo/hoz.md | itmajing/next | 77bc4eceaf615a7179ea1d36756c3d6d727b1d5c | [
"MIT"
] | 3,552 | 2018-07-18T09:21:52.000Z | 2022-03-31T12:18:58.000Z | docs/menu/demo/hoz.md | itmajing/next | 77bc4eceaf615a7179ea1d36756c3d6d727b1d5c | [
"MIT"
] | 559 | 2018-09-14T02:48:44.000Z | 2022-03-25T09:06:55.000Z | # 超长折叠
- order: 1
在横向导航模式下，可通过设置 `hozInLine` 折叠超长内容。
:::lang=en-us
# Horizontal menu bar
- order: 1
Demo the usage of the horizontal navigation menu bar.
:::
---
````jsx
import { Menu } from '@alifd/next';
const { SubMenu, Item } = Menu;
ReactDOM.render(
<Menu hozInLine direction="hoz" mode="popup" className="my-hoz-menu" popupClassName="my-hoz-menu" popupAutoWidth>
<Item key="1">First</Item>
<Item key="2">Second</Item>
<SubMenu label="Sub Nav">
<Item key="sub-12">Sub option 1</Item>
<Item key="sub-22">Sub option 2</Item>
<SubMenu label="Sub Sub Nav">
<Item key="sub-sub-122">Sub sub option 1</Item>
<Item key="sub-sub-222">Sub sub option 2</Item>
</SubMenu>
</SubMenu>
<SubMenu label="Sub Nav">
<Item key="sub-1">Sub option 1</Item>
<Item key="sub-2">Sub option 2</Item>
<SubMenu label="Sub Sub Nav">
<Item key="sub-sub-1">Sub sub option 1</Item>
<Item key="sub-sub-2">Sub sub option 2</Item>
</SubMenu>
</SubMenu>
<Item key="3">Third</Item>
</Menu>
, mountNode);
````
````css
.my-hoz-menu .next-menu-item {
width: 160px;
}
.my-hoz-menu .next-menu-item.next-menu-more {
width: 60px;
}
````
| 24.418182 | 117 | 0.550261 | ces_Latn | 0.162702 |
87d2821a19685523b986a41262187878476517b7 | 102 | md | Markdown | README.md | joaopbg/registerForm | 4a8950391636a0014d7f0ff71d8eab30a66d6e44 | [
"MIT"
] | null | null | null | README.md | joaopbg/registerForm | 4a8950391636a0014d7f0ff71d8eab30a66d6e44 | [
"MIT"
] | null | null | null | README.md | joaopbg/registerForm | 4a8950391636a0014d7f0ff71d8eab30a66d6e44 | [
"MIT"
] | null | null | null | # registerForm
Using Reactive Form to create a register form to apply and evolve my angular technics
| 34 | 86 | 0.813725 | eng_Latn | 0.997679 |
87d3524482827f5e72d989e5ce07827702e24846 | 298 | md | Markdown | app/service/ep/footman/README.md | 78182648/blibli-go | 7c717cc07073ff3397397fd3c01aa93234b142e3 | [
"MIT"
] | 22 | 2019-04-27T06:44:41.000Z | 2022-02-04T16:54:14.000Z | app/service/ep/footman/README.md | YouthAge/blibli-go | 7c717cc07073ff3397397fd3c01aa93234b142e3 | [
"MIT"
] | null | null | null | app/service/ep/footman/README.md | YouthAge/blibli-go | 7c717cc07073ff3397397fd3c01aa93234b142e3 | [
"MIT"
] | 34 | 2019-05-07T08:22:27.000Z | 2022-03-25T08:14:56.000Z | # footman-service
# 项目简介
### 背景/Background
* 目前移动端crash信息会上报到bugly，bugly系统查询数据比较慢且没有足够的数据分析功能，影响开发查询分析crash的效率
* 目前项目需求bug等信息记录在tapd, 同样tapd系统现有的报表功能并不满足我们PMO的需求，使PMO拿不到充足的数据做分析
* 于是Footman项目为了解决这些问题孕育而生
### 概览／Overview
* Footman会根据开发和PMO的需求，从bugly和tapd拉取原始数据生成自定义的报表数据
# 编译环境
# 依赖包
# 编译执行
| 14.9 | 67 | 0.818792 | yue_Hant | 0.814661 |
87d3e8113619aad9ce5c49ff805a9cc700d71fde | 24 | md | Markdown | README.md | freya-davies/freya-davies.github.io | fca91257f12d24c0f37ee4e5015dbe2e43b25f55 | [
"MIT"
] | null | null | null | README.md | freya-davies/freya-davies.github.io | fca91257f12d24c0f37ee4e5015dbe2e43b25f55 | [
"MIT"
] | null | null | null | README.md | freya-davies/freya-davies.github.io | fca91257f12d24c0f37ee4e5015dbe2e43b25f55 | [
"MIT"
] | null | null | null | # freya-davies.github.io | 24 | 24 | 0.791667 | vie_Latn | 0.180208 |
87d441de254e246682ab3c27b33482ecaefa952d | 538 | md | Markdown | src/site/markdown/index.md | Sylvain-Bugat/swagger-cxf-rest-skeleton | 40aeffce31dd342f97335aae9f81b6b231a31cdb | [
"Apache-2.0"
] | 1 | 2015-08-23T17:20:28.000Z | 2015-08-23T17:20:28.000Z | src/site/markdown/index.md | Sylvain-Bugat/swagger-cxf-rest-skeleton | 40aeffce31dd342f97335aae9f81b6b231a31cdb | [
"Apache-2.0"
] | 6 | 2016-06-16T21:37:23.000Z | 2022-01-21T23:20:00.000Z | src/site/markdown/index.md | Sylvain-Bugat/swagger-cxf-rest-skeleton | 40aeffce31dd342f97335aae9f81b6b231a31cdb | [
"Apache-2.0"
] | 1 | 2017-03-09T10:23:36.000Z | 2017-03-09T10:23:36.000Z | # Swagger CXF REST skeleton
Swagger CXF REST skeleton is a skeleton of a Swagger CXF, JAX-RS 2.0 (JSR 339) REST services application with user authentication.
## Launch and configuration
Just mount the constructed war file in a Tomcat 8 as root.
## Issues and feature requests?
Issues, bugs, and feature requests should be submitted on [GitHub Swagger CXF REST skeleton issue tracking](https://github.com/Sylvain-Bugat/swagger-cxf-rest-skeleton/issues).
## Thanks to
* [Swagger](http://swagger.io/)
* [GitHub](https://github.com)
| 29.888889 | 175 | 0.758364 | eng_Latn | 0.810335 |
87d47142d47fb8dbdb4bf24f627e99711a5ce0c2 | 3,944 | md | Markdown | docker/production/README.md | skroonigan/stash | 9bfa4e756058542fc7c6dfb70fa09261acf8443c | [
"MIT"
] | null | null | null | docker/production/README.md | skroonigan/stash | 9bfa4e756058542fc7c6dfb70fa09261acf8443c | [
"MIT"
] | null | null | null | docker/production/README.md | skroonigan/stash | 9bfa4e756058542fc7c6dfb70fa09261acf8443c | [
"MIT"
] | null | null | null | # Docker install on Ubuntu 18.04
Installing StashApp can likely work on others if your OS either has it's own package manager or comes shipped with Docker and docker-compose.
## Dependencies
The goal is to avoid as many dependencies as possible so for now the only pre-requisites you are required to have are `curl`, `docker`, and `docker-compose` for the most part your understanding of the technologies can be superficial so long as you can follow commands and are open to reading a bit you should be fine.
### Docker
Docker is effectively the cross-platform software package repository it allows you to ship an entire environment in what's referred to as a container. Containers are intended to hold everything that is needed to ship what's required to run an application from one place to another with a degree of a standard that makes it easy for everyone along the way to reproduce the environment for their step in the chain.
The other side of docker is it brings everything that we would typically have to teach you about the individual components of your soon to be installed StashApp and ffmpeg, docker-compose wraps it up nicely in a handful of easy to follow steps that should result in the same environment on everyone's host.
The installation method we recommend is via the `docker.com` website however if your specific operating system's repository versions are at the latest along with docker you should be good to launch with you using whatever instructions you wish. The version of Docker we used in our deployment for testing this process was `Docker version 17.05.0-ce, build 89658be` however any versions later than this will be sufficient. At the writing of this tutorial, this was not the latest version of Docker.
#### Just the link to installation instructions, please
Instructions for installing on Ubuntu are at the link that follows:
https://docs.docker.com/install/linux/docker-ce/ubuntu/
If you plan on using other versions of OS you should at least aim to be a Linux base with an x86_64 CPU and the appropriate minimum version of the dependencies.
### Docker-compose
Docker Compose's role in this deployment is to get you a fully working instance of StashApp exactly as you would need it to have a reasonable instance for testing / developing on, you could technically deploy a live instance with this, but without a reverse proxy, is not recommended. You are encouraged to learn how to use the Docker-Compose format, but it's not a required prerequisite for getting this running you need to have it installed successfully.
Install Docker Compose via this guide below, and it is essential if you're using an older version of Linux to use the official documentation from Docker.com because you require the more recent version of docker-compose at least version 3.4 aka 1.22.0 or newer.
#### Just the link to installation instructions, please
https://docs.docker.com/compose/install/
### Install curl
This one's easy, copy paste.
```
apt update -y && \
apt install -f curl
```
### Get the docker-compose.yml file
Now you can either navigate to the [docker-compose.yml](https://raw.githubusercontent.com/stashapp/stash/master/docker/production/docker-compose.yml) in the repository, OR you can make your Linux console do it for you with this.
```
curl -o ~/docker-compose.yml https://raw.githubusercontent.com/stashapp/stash/master/docker/production/docker-compose.yml
```
Once you have that file where you want it, you can either modify the settings as you please OR you can run the following to get it up and running instantly.
```
cd ~ && docker-compose up -d
```
Installing StashApp this way will by default bind stash to port 9999 or in web browser terms. http://YOURIP:9999 or if you're doing this on your machine locally which is the only recommended production version of this container as is with no security configurations set at all is http://localhost:9999
Good luck and have fun!
| 73.037037 | 499 | 0.7893 | eng_Latn | 0.99965 |
87d4778da639b5af3fb20c92befff5dc67f76f1e | 212 | md | Markdown | _discussion/351.md | brueghelfamily/brueghelfamily.github.io | a73351ac39b60cd763e483c1f8520f87d8c2a443 | [
"MIT"
] | null | null | null | _discussion/351.md | brueghelfamily/brueghelfamily.github.io | a73351ac39b60cd763e483c1f8520f87d8c2a443 | [
"MIT"
] | null | null | null | _discussion/351.md | brueghelfamily/brueghelfamily.github.io | a73351ac39b60cd763e483c1f8520f87d8c2a443 | [
"MIT"
] | null | null | null | ---
pid: '351'
object_pid: '3336'
author: E.A. Honig
comment: "<p>This work does not appear in the 1979 Ertz catalogue nor the Honig Database.</p>"
post_date: July 8, 2015
order: '350'
collection: discussion
---
| 21.2 | 94 | 0.707547 | eng_Latn | 0.749155 |
87d537ce142692c01e3c16fb64b63c1ad60d11b9 | 1,135 | md | Markdown | README.md | qswuwwb/SJLoadingViewController | 690c2cee5fff18a656c851a8897b5aaf367307b1 | [
"MIT"
] | null | null | null | README.md | qswuwwb/SJLoadingViewController | 690c2cee5fff18a656c851a8897b5aaf367307b1 | [
"MIT"
] | null | null | null | README.md | qswuwwb/SJLoadingViewController | 690c2cee5fff18a656c851a8897b5aaf367307b1 | [
"MIT"
] | null | null | null | <<<<<<< HEAD
# SJLoadViewController
[](https://travis-ci.org/qswuwwb/SJLoadViewController)
[](https://cocoapods.org/pods/SJLoadViewController)
[](https://cocoapods.org/pods/SJLoadViewController)
[](https://cocoapods.org/pods/SJLoadViewController)
## Example
To run the example project, clone the repo, and run `pod install` from the Example directory first.
## Requirements
## Installation
SJLoadViewController is available through [CocoaPods](https://cocoapods.org). To install
it, simply add the following line to your Podfile:
```ruby
pod 'SJLoadViewController'
```
## Author
qswuwwb, qswuw@sina.com
## License
SJLoadViewController is available under the MIT license. See the LICENSE file for more info.
=======
# SJLoadingViewController
>>>>>>> 3de4cf93c6f468c7824c26657752c3a8a64bd0e2
| 33.382353 | 141 | 0.77533 | yue_Hant | 0.513539 |
87d559463602be18ad2d1fd1d8bfff82169f3847 | 9,778 | md | Markdown | src/main/paradox/docs/api/admin/admin-projects-api.md | annakristinkaufmann/nexus | f9a8dc34213e5eef0e10669f4f3f5863bec72992 | [
"Apache-2.0"
] | null | null | null | src/main/paradox/docs/api/admin/admin-projects-api.md | annakristinkaufmann/nexus | f9a8dc34213e5eef0e10669f4f3f5863bec72992 | [
"Apache-2.0"
] | null | null | null | src/main/paradox/docs/api/admin/admin-projects-api.md | annakristinkaufmann/nexus | f9a8dc34213e5eef0e10669f4f3f5863bec72992 | [
"Apache-2.0"
] | null | null | null | # Projects
Projects are rooted in the `/v1/projects/{org_label}` and are used to group and categorize its sub-resources. Relevant roles of a projects are:
- Defining settings which can be used for operations on sub-resources.
- Providing (by default) isolation from resources inside other projects. This isolation can be avoided by defining @ref:[resolvers](../kg/kg-resolvers-api.md)
Each project...
- belongs to an `organization` identifier by the label `{org_label}`
- it is validated against the [project schema](https://bluebrain.github.io/nexus/schemas/project).
Access to resources in the system depends on the access control list set for them. Depending on the access control list, a caller may need to prove its identity by means of an **access token** passed to the `Authorization` header (`Authorization: Bearer {token}`). Please visit @ref:[Authentication](../iam/authentication.md) to learn more about how to retrieve an access token.
@@@ note { .tip title="Running examples with Postman" }
The simplest way to explore our API is using [Postman](https://www.getpostman.com/apps). Once downloaded, import the [projects collection](../assets/project-postman.json).
If your deployment is protected by an access token:
Edit the imported collection -> Click on the `Authorization` tab -> Fill the token field.
@@@
## Projects payload
```
{
"name": "{name}",
"base": "{base}",
"prefixMappings": [
{
"prefix": "{prefix}",
"namespace": "{namespace}"
},
...
]
}
```
where...
- `{name}`: String - the name for this project.
- `{base}`: Iri - is going to be used as a [curie](https://www.w3.org/TR/2010/NOTE-curie-20101216/) in the generation of the `@id` children resources. E.g.: Let base be `http://example.com/`. When a [resource is created using POST](../kg/kg-resources-api.html#create-a-resource-using-post) and no `@id` is present on the payload, the platform will generate and @id which will look like `http://example.com/{UUID}`. This field is optional and it will default to `{{base}}/v1/{org_label}/{project_label}`.
- `{prefixMappings}`: Json object - provides a convinient way to deal with URIs when performing operations on a sub-resource. This field is optional.
### Prefix Mappings
The `prefixMappings` Json object array maps each `prefix` to its `namespace` so that curies on children endpoints can be used. Let's see an example.
Having the following `prefixMappings`:
```
{
"prefixMappings": [
{
"prefix": "{prefix}",
"namespace": "{namespace}"
},
{ ... }
]
}
```
where...
- `{prefix}`: String - the left hand side of a [curie](https://www.w3.org/TR/2010/NOTE-curie-20101216/). It has [certain constrains](https://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName).
- `{namespace}`: Iri - the right hand side of a [curie](https://www.w3.org/TR/2010/NOTE-curie-20101216/). It has [certain constrains (irelative-ref)](https://tools.ietf.org/html/rfc3987#page-7).
The `prefixMappings` Json object array maps each `prefix` to its `namespace` so that curies on children endpoints can be used. Let's see an example:
```json
{
"prefixMappings": [
{
"prefix": "person",
"namespace": "http://example.com/some/person"
},
{
"prefix": "schemas",
"namespace": "https://bluebrain.github.io/nexus/schemas/"
}
]
}
```
The previous payload allows us to [create a schema](../kg/kg-schemas-api.html##create-a-schema-using-put) using the following endpoints:
- `/v1/schemas/{org_label}/{project_label}/person`. The `@id` of the resulting schema will be `http://example.com/some/person`
- `/v1/schemas/{org_label}/{project_label}/schema:other`. The `@id` of the resulting schema will be `https://bluebrain.github.io/nexus/schemas/other`
## Create a project
```
PUT /v1/projects/{org_label}/{label}
{...}
```
...where `{label}` is the user friendly name assigned to this project. The semantics of the `label` should be consistent with the type of data provided by its sub-resources, since they are exposed on the URI of the sub-resource's operations.
**Example**
Request
: @@snip [project.sh](../assets/project.sh)
Payload
: @@snip [project.json](../assets/project.json)
Response
: @@snip [project-ref-new.json](../assets/project-ref-new.json)
## Update a project
This operation overrides the payload.
In order to ensure a client does not perform any changes to a project without having had seen the previous revision of the project, the last revision needs to be passed as a query parameter.
```
PUT /v1/projects/{org_label}/{label}?rev={previous_rev}
{...}
```
... where
- `{previous_rev}`: Number - the last known revision for the organization.
- `{label}`: String - the user friendly name that identifies this project.
**Example**
Request
: @@snip [project-update.sh](../assets/project-update.sh)
Payload
: @@snip [project.json](../assets/project.json)
Response
: @@snip [project-ref-updated.json](../assets/project-ref-updated.json)
## Tag a project
Links a project revision to a specific name.
Tagging a project is considered to be an update as well.
```
PUT /v1/projects/{org_label}/{label}/tags?rev={previous_rev}
{
"tag": "{name}",
"rev": {rev}
}
```
... where
- `{name}`: String - label given the project at specific revision.
- `{rev}`: Number - the revision to link the provided `{name}`.
- `{previous_rev}`: Number - the last known revision for the organization.
- `{label}`: String - the user friendly name that identifies this project.
**Example**
Request
: @@snip [project-tag.sh](../assets/project-tag.sh)
Payload
: @@snip [tag.json](../assets/tag.json)
Response
: @@snip [project-ref-tagged.json](../assets/project-ref-tagged.json)
## Deprecate a project
Locks the project, so no further operations can be performed on it or on the children resources.
Deprecating a project is considered to be an update as well.
```
DELETE /v1/projects/{org_label}/{label}?rev={previous_rev}
```
... where
- `{previous_rev}`: Number - the last known revision for the organization.
- `{label}`: String - the user friendly name that identifies this project.
**Example**
Request
: @@snip [project-deprecate.sh](../assets/project-deprecate.sh)
Response
: @@snip [project-ref-deprecated.json](../assets/project-ref-deprecated.json)
## Fetch a project (current version)
```
GET /v1/projects/{org_label}/{label}
```
...where `{label}` is the user friendly name that identifies this project.
**Example**
Request
: @@snip [project-fetch.sh](../assets/project-fetch.sh)
Response
: @@snip [project-fetched.json](../assets/project-fetched.json)
## Fetch a project (specific version)
```
GET /v1/projects/{org_label}/{label}?rev={rev}
```
...where
- `{label}`: String - the user friendly name that identifies this project.
- `{rev}`: Number - the revision of the project to be retrieved.
**Example**
Request
: @@snip [project-fetch-revision.sh](../assets/project-fetch-revision.sh)
Response
: @@snip [project-fetched.json](../assets/project-fetched.json)
## Fetch a project (specific tag)
```
GET /v1/projects/{org_label}/{label}?tag={tag}
```
... where
- `{label}`: String - the user friendly name that identifies this project.
- `{tag}`: String - the tag of the project to be retrieved.
**Example**
Request
: @@snip [project-fetch-tag.sh](../assets/project-fetch-tag.sh)
Response
: @@snip [project-fetched-tag.json](../assets/project-fetched-tag.json)
## Get the ACLs for a project
```
GET /v1/projects/{org_label}/{label}/acls?self=true&parents={parents}
```
... where
- `{label}`: String - the user friendly name that identifies this project.
- `{parents}`: Boolean - if true, the response includes the ACLs for the parent `organization` of the current project. If false, the response only includes the project ACLs.
**Example**
Request
: @@snip [project-fetch-acls.sh](../assets/project-fetch-acls.sh)
Response
: @@snip [project-acls-fetched.json](../assets/project-acls-fetched.json)
## List projects
```
GET /v1/projects?from={from}&size={size}&deprecated={deprecated}&q={full_text_search_query}
```
where...
- `{full_text_search_query}`: String - can be provided to select only the projects in the collection that have attribute values matching (containing) the provided token; when this field is provided the results will also include score values for each result
- `{from}`: Number - is the parameter that describes the offset for the current query; defaults to `0`
- `{size}`: Number - is the parameter that limits the number of results; defaults to `20`
- `{deprecated}`: Boolean - can be used to filter the resulting projects based on their deprecation status
**Example**
Request
: @@snip [project-list.sh](../assets/project-list.sh)
Response
: @@snip [project-list.json](../assets/project-list.json)
## List projects belonging to an organization
```
GET /v1/projects/{org_label}?from={from}&size={size}&deprecated={deprecated}&q={full_text_search_query}
```
where...
- `{full_text_search_query}`: String - can be provided to select only the projects in the collection that have attribute values matching (containing) the provided token; when this field is provided the results will also include score values for each result
- `{from}`: Number - is the parameter that describes the offset for the current query; defaults to `0`
- `{size}`: Number - is the parameter that limits the number of results; defaults to `20`
- `{deprecated}`: Boolean - can be used to filter the resulting projects based on their deprecation status
**Example**
Request
: @@snip [project-list-org.sh](../assets/project-list-org.sh)
Response
: @@snip [project-list.json](../assets/project-list.json) | 31.04127 | 503 | 0.70362 | eng_Latn | 0.981322 |
87d5cedd7d3f1055f9239997ea2f3995d3f7873c | 2,815 | md | Markdown | node_modules/ecdsa/CHANGELOG.md | BitcoinRM/bcrm-pool | 18f68802fd3ff41edeec9b4e01fa7b65f8d40c62 | [
"MIT"
] | null | null | null | node_modules/ecdsa/CHANGELOG.md | BitcoinRM/bcrm-pool | 18f68802fd3ff41edeec9b4e01fa7b65f8d40c62 | [
"MIT"
] | null | null | null | node_modules/ecdsa/CHANGELOG.md | BitcoinRM/bcrm-pool | 18f68802fd3ff41edeec9b4e01fa7b65f8d40c62 | [
"MIT"
] | null | null | null | 0.6.0 / 2014-09-30
------------------
- dropped alternative curve support, only `secp256k1` for now; if we find we need others in the future we can just grab
them from Git history
- upgraded from `"ecurve": "^0.6.0"`to `"ecurve": "^1.0.0"`
0.5.3 / 2014-07-04
------------------
* bugfix: verify() should treat `hash` as a Buffer and as not a byte array, see #14
0.5.2 / 2014-07-03
------------------
* bugfix: `deterministicGenerateK()` now works with BigInteger instances of other `bigi` installations
0.5.1 / 2014-06-03
------------------
* mistakenly left `secure-random` as a production dependency, moved it to development dep
0.5.0 / 2014-06-02
------------------
* added Travis CI support
* added Coveralls support
* upgraded `~ecurve@0.3.2` to `^ecurve@0.6.0`
* removed `ecurve-names` from dev deps
* upgraded `~bigi@0.2.0` to `^bigi@1.1.0`
* removed `sha256` from dev deps
* changed the way the module should be used, old way was very cumbersome
New Way:
```js
var ecdsa = require('ecdsa') //defaults to secp256k1 curve
```
if you want another curve:
```js
var ecdsa = require('ecdsa')('secp256r1')
```
* added `deterministicGenerateK()`, RFC 6979. See: https://github.com/cryptocoinjs/ecdsa/issues/4.
* added `recoverPubKey()` from BitcoinJS / [Daniel Cousens](https://github.com/dcousens)
* added `serializeSigCompact()` from BitcoinJS / [Daniel Cousens](https://github.com/dcousens)
* changed method signature of `sign(hash, privateKeyBigInteger)` to sign(hash, privateKeyBuffer)`
* `sign()` method now uses low `s` value: See: https://github.com/cryptocoinjs/ecdsa/issues/10
* renamed `calcPubkeyRecoveryParam()` to `calcPubKeyRecoveryParam()`, changed signature
* added Testling support
0.4.1 / 2014-04-14
------------------
* bugfix: `parseSigCompact()` referencing invalid `ecparams` #6
* bugfix: `verify()` works with compressed keys #9
* add browser tests
0.4.0 / 2014-03-13
------------------
* removed bower / component stuff. Still works with browser, just use `browserify`. Closes #3
* moved from 4 spaces to 2 spaces (Node style)
* made class based so that multiple instantiations can be made with different curves, i.e. not just tied to `secp256k1`. Closes #2
BREAKING CHANGE. Set `ECDSA.ecparams` before using `ECDSA`.
* made class level methods so that existing code should work with very little modification
* removed dependency upon `ecurve-names`
* update deps: `secure-random` and `ecurve`. (will eventually removed secure-random)
0.3.0 / 2013-12-08
------------------
* upgraded deps (for `bigi`)
0.2.0 / 2013-12-07
------------------
* moved `recoverPubKey()` to package `eckey`
* added test for `verify()` and `sign()`
0.1.0 / 2013-11-20
------------------
* changed package name
* removed AMD support
0.0.1 / 2013-11-12
------------------
* initial release
| 32.732558 | 131 | 0.668561 | eng_Latn | 0.934444 |
87d61dbd81eb652b6577596f227142793278b994 | 2,013 | md | Markdown | docs/tutorial.md | KusStar/rewind-docs | dd10454ef0597523b5df00347cf075d8be0c8880 | [
"MIT"
] | 33 | 2020-09-01T09:03:00.000Z | 2022-03-13T01:48:47.000Z | docs/tutorial.md | Compile00/rewind_docs | 9c6e617a324613f310a07c8729d21bf8e497981d | [
"MIT"
] | 7 | 2021-03-07T04:00:13.000Z | 2022-02-09T13:19:06.000Z | docs/tutorial.md | Compile00/rewind_docs | 9c6e617a324613f310a07c8729d21bf8e497981d | [
"MIT"
] | 2 | 2020-09-01T02:45:12.000Z | 2020-09-01T09:15:37.000Z | # 操作指南
## 首页
<img
src="https://s1.ax1x.com/2020/03/16/8YN4Re.jpg"
height="400px"
alt="首页"
class="shadow"
/>
主要有两个部分，上方 **按钮群** 及下方的 **歌单列表**。
上下两部分均可左右滑动，分别对应切换不同功能页面，不同歌单。
**GIF**
<img
src="https://s1.ax1x.com/2020/04/07/GcuBuj.gif"
height="400px"
alt="GIF"
class="shadow"
/>
**按钮群**
有 `本地音乐`、`最近播放`、`每日推荐`、`收藏`、`电台`、`私人FM`、`推荐歌单`、`榜单`。
现阶段 `每日推荐`、`收藏`、`电台`、`私人FM`、`推荐歌单`、`榜单` 仅支持 网易云音乐。
**歌单列表**
有 `网易云音乐`、`QQ音乐`、`自定义` 等歌单。
**网易云音乐**
点击上方图标可进入 `切换` 页面，可以切换至其他用户账号的歌单，即伪多用户管理，对用户条目 [长按] 即可切换为该用户。
对用户条目 [单击] 可进入 `用户详情页面` 。
`用户详情页面`，可查看用户歌单，听歌排行等。
[长按] 与 `切换` 将该用户添加到 `切换` 页面用户列表。
[单击] 用户头像可进入 `用户关注` 页面。
**QQ 音乐**
点击上方图标会打开QQ 音乐 官方网页，用以操作歌单信息等。暂时没有和上面功能同步。这个实现很粗糙。
**自定义**
自定义歌单可以收藏上面两个平台的曲目。需手动创建，且数据保存在本地。现阶段不支持云备份。
创建的自定义歌单保存在 ./Android/data/com.kuss.rewind/files/playlist/playlist.json ，此目录会随应用卸载而消失。
## 登入
**网易云音乐**
<img
src="https://s1.ax1x.com/2020/03/16/8Ya3Bn.jpg"
height="400px"
alt="网易云登入页面"
class="shadow"
/>
大部分功能如每日推荐等需登入才能使用。
可使用 `邮箱或手机号 + 密码` 登陆，或者使用绑定 `QQ` 或 `微博` 账号登陆。
也可不登入直接 `获取歌单`。
**QQ音乐**
<img
src="https://s1.ax1x.com/2020/03/16/8Ya1ns.jpg"
height="400px"
alt="QQ音乐登入页面"
class="shadow"
/>
可使用 `QQ 号` 或 `微信扫码` 登入。
由于某种限制，必须登入后才能使用 `输入QQ号获取公开歌单`，微信扫码需要另一台设备来扫，
以及 QQ 音乐 的大部分功能无法使用/暂未支持。
## 播放
**播放界面**
<div>
<img
src="https://s1.ax1x.com/2020/03/29/GE1ggg.md.jpg"
height="400px"
alt="精简模式"
class="shadow mr-50"
/>
<img
src="https://s1.ax1x.com/2020/03/29/GE1c8S.md.jpg"
height="400px"
alt="复杂模式"
class="shadow"
/>
</div>
有精简模式和详细模式两种。 至于为什么，请见 [为什么有-详细/精简-模式？](/questions?id=为什么有-详细精简-模式？)
- 中间歌曲名位置 -> [单击] 切换 播放/暂停，左右滑动切换 上/下 一首。
1. 点击查看歌词。
2. 手势 [向上滑] -> 切换 精简/复杂 模式。
3. 手势 [向右滑] -> 打开详细列表。
4. 手势 [向下滑] -> 缩小播放界面。
5. 手势 [向左滑] -> 打开当前播放列表。
6. 边缘手势 [上下移动] -> 调整播放进度，移出边缘即撤销。
7. 边缘手势 [上下移动] -> 调整系统音量，移出边缘即撤销。
**歌词**
<img
src="https://s1.ax1x.com/2020/03/29/GE12vQ.md.jpg"
height="400px"
alt="歌词"
class="shadow"
/>
8. [点击] 返回播放界面。
- [长按] 歌词条目即调整播放进度到该歌词时间。
| 15.484615 | 86 | 0.623448 | yue_Hant | 0.723726 |
87d6bbc06124e294efc500aa1301cb604dcd02d1 | 5,856 | md | Markdown | experiments/README.md | judithfan/graphical_conventions | 0a53f3f959a22001cec75f54b1e73a53773bab19 | [
"MIT"
] | 1 | 2019-06-23T13:38:16.000Z | 2019-06-23T13:38:16.000Z | experiments/README.md | judithfan/graphical_conventions | 0a53f3f959a22001cec75f54b1e73a53773bab19 | [
"MIT"
] | 7 | 2018-06-03T23:59:17.000Z | 2018-12-05T20:57:33.000Z | experiments/README.md | judithfan/graphical_conventions | 0a53f3f959a22001cec75f54b1e73a53773bab19 | [
"MIT"
] | 1 | 2021-04-16T21:25:39.000Z | 2021-04-16T21:25:39.000Z | # Communication task
##### `/experiments/refgame/draw_chairs/`
- Input: Shapenet chair collection and experimental design
- Output: Human sketches and viewer decisions over time, communication efficiency timecourse
### 2.0
##### 1.2.0: `iterationName` : `run5_submitButton`
January 8, 2019
- What's new:
- Added `useSubmitButton` flag in `game.core.js`
- When set to `true`, the Sketcher must click the Submit button when they are done drawing for the Viewer to be able to see their drawing, so that the Viewer is not able to interrupt the Sketcher's drawing.
- 30-second time limit in the speed bonus system still applies to the time taken since the Sketcher begins drawing until the Viewer selects an object
- Minimize context variability & increase sampling density within context: There are 8 versions of this experiment. Each of the chair categories: `['dining', 'waiting']` is evenly divided into two, fixed subsets: `['A','B']`. The assignment of ['repeated', 'control'] to each of the chair categories is randomized across pairs, and the repeated and control subsets are always from different chair categories. Thus approx. half of pairs will see dining repeatedly (with waiting items as control), and half of pairs will see waiting repeatedly (with dining as control).
### 1.2
July 26, 2018
##### 1.2.0: `iterationName`s : `run3_size4_waiting`, `run4_generalization`
- What's new:
- Context size changed back to 4
- Two context generalization conditions (each has different `iterationName`)
- In the within-cluster generalization condition (`run3_size4_waiting`): repeated and control objects are fetched from the same cluster
- Use `waiting` flag in `game.core.js` to choose which cluster (waiting or dining) to fetch from for a game (when set to `true`, the waiting chairs cluster is used)
- In the between-cluster generalization condition (`run4_generalization`): repeated and control objects are fetched from different clusters
- Use `diffCats` flag in `game.core.js` to choose which condition (when set to `true`, between-cluster generalization condition is used)
### 1.1
July 20, 2018
##### 1.1.1 `iterationName` : `run2_chairs1k_size6`
##### 1.1.0 `iterationName` : `run2_chairs1k_size4`
- What's new:
- Stimuli changed to chairs from ShapeNet
- Clustered (PCA --> k-means) to increase similarity between objects in a context
- Manipulated context size
- **1.1.1**: context size = 6, num_reps = 6, num_rounds = 48
- **1.1.0**: context size = 4, num_reps = 8, num_rounds = 40
- Confirmation system
- Viewer must confirm their choice of object after clicking on one (to prevent Viewer from hurriedly clicking on objects and achieving low accuracy)
- Context color cues
- Made context shift more perceptually salient using red and blue frames around repeated and control contexts (to make sure players know which context they are working in each trial)
- Color-cued feedback sign
- Shows how much bonus players got after each trial (to make trial-by-trial feedback more salient in addition to cumulative score display and bonusmeter)
- Increased time limit
- 30 seconds (to ensure Sketcher has enough time to draw as the task is more challenging with increased similarity within context and increased context size in 1.1.1)
### 1.0
June 30, 2018
##### 1.0.1 `iterationName` : `run1_chairsOnly` (Stimuli now restricted to chairs in the 'basic' 3D object dataset, before this point, files were under `/experiments/refgame/draw_basic/`)
##### 1.0.0 `iterationName` : `run0_bonusmeter`
- What's new:
- Speed bonus system
- Manipulates cost of drawing by imposing a 30-second time limit for each trial to incentivize efficient drawing.
- Animated progress bar keeps track of additional bonus the players can receive depending on time taken for Viewer
to make a correct guess. Additional bonus only given to correct guesses made under 30s (which should be more than enough for a Viewer to select an object based on the Sketcher's current sketch, but makes time cost more salient.)
- All correct guesses receive a minimum bonus of $0.01. In the first 30s, the additional bonus players can receive decreases from $0.03 to $0.00 -- in other words, the total bonus players an receive decreases from $0.04 to $0.01. Incorrect guesses do not receive a speed bonus, so the total bonus (accuracy bonus + speed bonus) is $0.00.
- Two bonusmeter interfaces (progress bar and numerical feedback) were designed and the progress bar design was chosen
# Recognition task
##### `/experiments/recog/`
- Input: Sketches from communication task and 3D objects
- Output: Sketch recognizability in context
### 2.0
April 2019
##### stimuli from `refgame 2.0` data: `graphical_conventions_sketches_yoked` `graphical_conventions_sketches_scrambled40`
- `iterationName` = `pilot4`
### 1.2
`iterationName` = `pilot3`
##### stimuli from `graphical_conventions_sketches_scrambled40` collection
December 21, 2018
- What's different:
- 1 recog experiment per refgame `gameID`
- Each experiment has 40 trials (each repetition has 4 trials, each trial from a different refgame `gameID`)
- Preserved temporal structure of repetitions
### 1.1
##### stimuli from `graphical_conventions_sketches_yoked` collection
December 21, 2018
- What's different:
- 1 recog experiment per refgame `gameID`
- Each experiment has 40 trials (all from the same refgame `gameID`)
- Preserved temporal structure of trials
### 1.0
##### stimuli from `graphical_conventions_sketches_scrambled10` collection
November 20, 2018
- What's different:
- 4 recog experiments per refgame `gameID`
- Each experiment has 10 trials (8 sketches from repeated condition, 2 from control condition with each sketch coming from a different refgame `gameID`)
| 49.627119 | 570 | 0.749488 | eng_Latn | 0.996654 |
87d6cfc0beb8ba0a8d483360d7d708560c1a1c68 | 2,447 | md | Markdown | .README/rules/require-description.md | bennieswart/eslint-plugin-jsdoc | 5b814fc8e9bb774ddc688f579b9b02e075c81896 | [
"BSD-3-Clause"
] | null | null | null | .README/rules/require-description.md | bennieswart/eslint-plugin-jsdoc | 5b814fc8e9bb774ddc688f579b9b02e075c81896 | [
"BSD-3-Clause"
] | null | null | null | .README/rules/require-description.md | bennieswart/eslint-plugin-jsdoc | 5b814fc8e9bb774ddc688f579b9b02e075c81896 | [
"BSD-3-Clause"
] | null | null | null | ### `require-description`
Requires that all functions have a description.
* All functions must have an implicit description or have the option
`descriptionStyle` set to `tag`.
* Every jsdoc block description (or description tag if `descriptionStyle` is
`"tag"`) must have a non-empty description that explains the purpose of the
method.
#### Options
An options object may have any of the following properties:
- `contexts` - Set to an array of strings representing the AST context
where you wish the rule to be applied (e.g., `ClassDeclaration` for ES6
classes). Overrides the default contexts (see below). Set to `"any"` if
you want the rule to apply to any jsdoc block throughout your files.
- `exemptedBy` - Array of tags (e.g., `['type']`) whose presence on the
document block avoids the need for a `@description`. Defaults to an
array with `inheritdoc`. If you set this array, it will overwrite the
default, so be sure to add back `inheritdoc` if you wish its presence
to cause exemption of the rule.
- `descriptionStyle` - Whether to accept implicit descriptions (`"body"`) or
`@description` tags (`"tag"`) as satisfying the rule. Set to `"any"` to
accept either style. Defaults to `"body"`.
- `checkConstructors` - A value indicating whether `constructor`s should be checked. Defaults to `true`.
- `checkGetters` - A value indicating whether getters should be checked. Defaults to `true`.
- `checkSetters` - A value indicating whether getters should be checked. Defaults to `true`.
| | |
| -------- | ------------------------------------------------------------------------------------------------------------- |
| Context | `ArrowFunctionExpression`, `FunctionDeclaration`, `FunctionExpression`; others when `contexts` option enabled |
| Tags | `description` or jsdoc block |
| Aliases | `desc` |
| Options | `contexts`, `exemptedBy`, `descriptionStyle`, `checkConstructors`, `checkGetters`, `checkSetters` |
| Settings | `overrideReplacesDocs`, `augmentsExtendsReplacesDocs`, `implementsReplacesDocs` |
<!-- assertions requireDescription -->
| 61.175 | 124 | 0.591336 | eng_Latn | 0.957587 |
87d6ddacfd59d12db9c01c4a6e6dc619bfec7342 | 810 | md | Markdown | README.md | DIAGNijmegen/pathology-whole-slide-data | d1377b742fabd959dae731d0b2686bbe17dcc2f3 | [
"Apache-2.0"
] | 26 | 2021-10-02T23:46:13.000Z | 2022-03-13T02:41:03.000Z | README.md | DIAGNijmegen/pathology-whole-slide-data | d1377b742fabd959dae731d0b2686bbe17dcc2f3 | [
"Apache-2.0"
] | 10 | 2021-09-20T17:56:32.000Z | 2022-03-24T13:15:57.000Z | README.md | DIAGNijmegen/pathology-whole-slide-data | d1377b742fabd959dae731d0b2686bbe17dcc2f3 | [
"Apache-2.0"
] | 6 | 2021-12-13T16:47:56.000Z | 2022-03-21T02:46:47.000Z | ### WholeSlideData
-----
***This repository contains alpha software***
### Installation
pip install git+https://github.com/DIAGNijmegen/pathology-whole-slide-data@main
### Main Features
- Image opening and patch extraction (ASAP, openslide-python and pyvips support)
- Annotation opening and extraction (ASAP, QuPath, Virtum and Histomicstk support)
- Batch iterator: iterator to be used for training a CNN
- custom sampling strategies (various build-in strategies, e.g., balanced, area-based and more)
- custom sample/batch callbacks (various build in callbacks, e.g., fit_shape, one-hot-encoding and more)
- multi-core patch extraction
### Examples:
Please see [notebook examples](https://github.com/DIAGNijmegen/pathology-whole-slide-data/tree/main/notebooks) on how to use this code:
| 32.4 | 135 | 0.754321 | eng_Latn | 0.920441 |
87d7bef2dd26113f28dd38b96f0fa7f2a3a23ee4 | 3,859 | md | Markdown | MAINTAINERS.md | mbeiswenger/guides-source | 677b57ff2adbd62b087ee91087da6d4fed8e8cc3 | [
"MIT"
] | null | null | null | MAINTAINERS.md | mbeiswenger/guides-source | 677b57ff2adbd62b087ee91087da6d4fed8e8cc3 | [
"MIT"
] | null | null | null | MAINTAINERS.md | mbeiswenger/guides-source | 677b57ff2adbd62b087ee91087da6d4fed8e8cc3 | [
"MIT"
] | 1 | 2022-02-26T14:05:06.000Z | 2022-02-26T14:05:06.000Z | # Maintainers
This document contains instructions and guidelines for maintainer tasks, like publishing and deploying new versions of the Guides.
## Continuous deployment
Whenever a PR is merged into `master`, Travis will automatically run the scripts that build the app and upload the results to Netlify. Netlify will then deploy the site. We currently allow only one Travis job at a time so that concurrent deploy commands do not cause a conflict.
## Deploying a new version
Whenever the release blog post is published for a new version of Ember, follow these steps.
### Before deployment of a new version
Check briefly to see if there are any PRs that should be merged into `/release/`, so that they are applied to both the new version we are about to deploy, and the previous version.
### To deploy a new version
It is required that all maintainers use 2FA (two factor authentication). These are the permissions needed for a deployment of the Guides:
- Merge permissions on the repository
- Percy dashboard
1. Clone the guides-source repository to your local machine
2. Make sure you have a clean git history with `git status`
3. Get the latest commits on `master` using `git pull origin master`
4. Create a directory in `guides` for the version that is one less than the "lastest." For example, if the newest release of Ember is `3.9`, you will make a directory for `3.8` that is a copy of `release`.
5. Copy the contents of `guides/release/` into the new directory, `cp -r release vX.Y.Z`
6. Edit `versions.yml` - add the version number to _both_ the end of the list and the `currentVersion`. The last item and `currentVersion` should match.
7. Commit the change.
8. Create a PR, and in the comments, mention that when it is merged, the person who merges it must update the guides search ASAP, and include a link to this page for instructions. Look at the app in staging, get a review, and merge to `master`. This will trigger an auto deployment.
9. Once it is deployed, follow the steps below to get the website search working for your new version.
### Updating the guides search
Currently getting the new version indexed and put in Algolia is a manual step. There is currently work going on to try to make this automatic, see the [tracking issue here](https://github.com/ember-learn/guides-source/issues/487) to follow along with progress.
Before we get started you need to login to the Algolia dashboard to get the API key. You login, click `API Keys` and then copy `Write API Key`. Once you have it you need to create the file `config/credentials.json` with the following content:
```json
{
"algoliaKey": "<algolia-key>",
"algoliaIndex": "ember-guides",
"algoliaApplication": "Y1OMR4C7MF"
}
```
Next let's make sure that you have pulled the latest changes after the new version PR has been merged into master
```
git checkout master
git pull
```
Next, make sure that you don't have any local changes using `git stash` because we're going to be a bit distructive (temporarily)
1. Delete all guides folders apart from `release` i.e. everything that starts with a `v`
- cd guides
- rm -rf v*
2. Open versions.yml and delete everything in `allVersions` apart from the latest version (that has just been released)
3. Make sure `config/credentials.json` is in place as described above
- you may have accidently deleted this since last time as it is supposed to be ignored by git
4. Open `config/deploy.js` and delete the `versionsToIgnore` line in the `prember-algolia` config
5. run `ember deploy production`
6. This should now be done, you can fix your local repo by running `git reset --hard HEAD`
7. Before you walk away, you should check the guides app in production and see if you can search for something on the latest version
8. Party some more 🎉and let the rest of the team know that the updates have been made.
| 56.75 | 282 | 0.765224 | eng_Latn | 0.999481 |
87d7e1de59cf6798d6155e0309a1fadfcc77dac2 | 112 | md | Markdown | README.md | cebartling/react-apollo-hooks-spike | 7dc9ad224ba5d515b1d1a40a3fd0ca69563d0f51 | [
"MIT"
] | 1 | 2019-09-09T22:38:15.000Z | 2019-09-09T22:38:15.000Z | README.md | cebartling/react-apollo-hooks-spike | 7dc9ad224ba5d515b1d1a40a3fd0ca69563d0f51 | [
"MIT"
] | 5 | 2021-03-09T14:40:52.000Z | 2022-02-26T16:24:43.000Z | README.md | cebartling/react-apollo-hooks-spike | 7dc9ad224ba5d515b1d1a40a3fd0ca69563d0f51 | [
"MIT"
] | null | null | null | # react-apollo-hooks-spike
Spike solution around using React Hooks from Apollo Client for GraphQL interactions.
| 37.333333 | 84 | 0.830357 | eng_Latn | 0.948127 |
87d7e82379a38320c2fd764fdc931e806a8025f2 | 4,751 | md | Markdown | benchmark/v5.4-performance-benchmarking-with-tpch.md | tier-cap/docs | 59f9e7e7548eb8be3179a6c5cd7c5f21f126cfc2 | [
"Apache-2.0"
] | null | null | null | benchmark/v5.4-performance-benchmarking-with-tpch.md | tier-cap/docs | 59f9e7e7548eb8be3179a6c5cd7c5f21f126cfc2 | [
"Apache-2.0"
] | null | null | null | benchmark/v5.4-performance-benchmarking-with-tpch.md | tier-cap/docs | 59f9e7e7548eb8be3179a6c5cd7c5f21f126cfc2 | [
"Apache-2.0"
] | null | null | null | ---
title: TiDB TPC-H Performance Test Report -- v5.4 MPP mode vs. Greenplum 6.15.0 and Apache Spark 3.1.1
---
# TiDB TPC-H Performance Test Report -- TiDB v5.4 MPP mode vs. Greenplum 6.15.0 and Apache Spark 3.1.1
## Test overview
This test aims at comparing the TPC-H 100 GB performance of TiDB v5.4 in the MPP mode with that of Greenplum and Apache Spark, two mainstream analytics engines, in their latest versions. The test result shows that the performance of TiDB v5.4 in the MPP mode is two to three times faster than that of the other two solutions under TPC-H workload.
In v5.0, TiDB introduces the MPP mode for [TiFlash](/tiflash/tiflash-overview.md), which significantly enhances TiDB's Hybrid Transactional and Analytical Processing (HTAP) capabilities. Test objects in this report are as follows:
+ TiDB v5.4 columnar storage in the MPP mode
+ Greenplum 6.15.0
+ Apache Spark 3.1.1 + Parquet
## Test environment
### Hardware prerequisite
| Instance type | Instance count |
|:----------|:----------|
| PD | 1 |
| TiDB | 1 |
| TiKV | 3 |
| TiFlash | 3 |
+ CPU: Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz, 40 cores
+ Memory: 189 GB
+ Disks: NVMe 3TB * 2
### Software version
| Service type | Software version |
|:----------|:-----------|
| TiDB | 5.4 |
| Greenplum | 6.15.0 |
| Apache Spark | 3.1.1 |
### Parameter configuration
#### TiDB v5.4
For the v5.4 cluster, TiDB uses the default parameter configuration except for the following configuration items.
In the configuration file `users.toml` of TiFlash, configure `max_memory_usage` as follows:
```toml
[profiles.default]
max_memory_usage = 10000000000000
```
Set session variables with the following SQL statements:
```sql
set @@tidb_isolation_read_engines='tiflash';
set @@tidb_allow_mpp=1;
set @@tidb_mem_quota_query = 10 << 30;
```
All TPC-H test tables are replicated to TiFlash in columnar format, with no additional partitions or indexes.
#### Greenplum
Except for the initial 3 nodes, the Greenplum cluster is deployed using an additional master node. Each segment server contains 8 segments, which means 4 segments per NVMe SSD. So there are 24 segments in total. The storage format is append-only/column-oriented storage and partition keys are used as primary keys.
{{< copyable "" >}}
```
log_statement = all
gp_autostats_mode = none
statement_mem = 2048MB
gp_vmem_protect_limit = 16384
```
#### Apache Spark
The test of Apache Spark uses Apache Parquet as the storage format and stores the data on HDFS. The HDFS system consists of three nodes. Each node has two assigned NVMe SSD disks as the data disks. The Spark cluster is deployed in standalone mode, using NVMe SSD disks as the local directory of `spark.local.dir` to speed up the shuffle spill, with no additional partitions or indexes.
{{< copyable "" >}}
```
--driver-memory 20G
--total-executor-cores 120
--executor-cores 5
--executor-memory 15G
```
## Test result
> **Note:**
>
> The following test results are the average data of three tests. All numbers are in seconds.
| Query ID | TiDB v5.4 | Greenplum 6.15.0 | Apache Spark 3.1.1 + Parquet |
| :-------- | :----------- | :------------ | :-------------- |
| 1 | 8.08 | 64.1307 | 52.64 |
| 2 | 2.53 | 4.76612 | 11.83 |
| 3 | 4.84 | 15.62898 | 13.39 |
| 4 | 10.94 | 12.88318 | 8.54 |
| 5 | 12.27 | 23.35449 | 25.23 |
| 6 | 1.32 | 6.033 | 2.21 |
| 7 | 5.91 | 12.31266 | 25.45 |
| 8 | 6.71 | 11.82444 | 23.12 |
| 9 | 44.19 | 22.40144 | 35.2 |
| 10 | 7.13 | 12.51071 | 12.18 |
| 11 | 2.18 | 2.6221 | 10.99 |
| 12 | 2.88 | 7.97906 | 6.99 |
| 13 | 6.84 | 10.15873 | 12.26 |
| 14 | 1.69 | 4.79394 | 3.89 |
| 15 | 3.29 | 10.48785 | 9.82 |
| 16 | 5.04 | 4.64262 | 6.76 |
| 17 | 11.7 | 74.65243 | 44.65 |
| 18 | 12.87 | 64.87646 | 30.27 |
| 19 | 4.75 | 8.08625 | 4.7 |
| 20 | 8.89 | 15.47016 | 8.4 |
| 21 | 24.44 | 39.08594 | 34.83 |
| 22 | 1.23 | 7.67476 | 4.59 |
In the performance diagram above:
- Blue lines represent TiDB v5.4;
- Red lines represent Greenplum 6.15.0;
- Yellow lines represent Apache Spark 3.1.1.
- The y-axis represents the execution time of the query. The less the time is, the better the performance is.
| 37.117188 | 385 | 0.595454 | eng_Latn | 0.903562 |
87d86143a3f4e288c31b15ab5bea3ff69080efb3 | 995 | md | Markdown | README.md | PresBAW/pref-name-sort-list | 6a05927134784f0a4609d2c0f9c635ea27cc5260 | [
"MIT"
] | null | null | null | README.md | PresBAW/pref-name-sort-list | 6a05927134784f0a4609d2c0f9c635ea27cc5260 | [
"MIT"
] | 1 | 2017-09-20T20:58:52.000Z | 2017-09-20T20:58:52.000Z | README.md | PresBAW/pref-name-sort-list | 6a05927134784f0a4609d2c0f9c635ea27cc5260 | [
"MIT"
] | null | null | null | # pref-name-sort-list
> Node module that exports a function filtering an array of strings based on a user-provided regex pattern and returning an array of those strings in preferred order - i.e., pattern matches sorted in ascending order of match index.
## Install
```
$ npm install --save pref-name-sort-list
```
## Usage
```js
// Import module
const prefNameSort = require('pref-name-sort-list');
// Get new filtered and sorted array from desired rawArray based on regexp pattern
newArray = prefNameSort(rawArray, pattern);
```
## Example
```js
const prefNameSort = require('pref-name-sort-list');
// Example array of strings we want to query for a given pattern (our query var)
var rawArray = ['lemon', 'apple', 'pear', 'orange', 'banana'];
var query = 'a';
// Filter and sort
var newArray = [];
newArray = prefNameSort(rawArray, query);
// Return should be ['apple', 'banana', 'pear', 'orange']
console.log(newArray)
```
## License
MIT © [Benjamin Wallsten](http://bwallsten.me) | 24.875 | 231 | 0.710553 | eng_Latn | 0.917478 |
87d9e3c511af95fe8fa687de7f98eb2c67b37ff4 | 271 | md | Markdown | projects/index.md | nibralab/nibralab.github.io | 2a3487a748113bff7de9e3132469453bca62d825 | [
"MIT"
] | 1 | 2020-07-25T13:32:39.000Z | 2020-07-25T13:32:39.000Z | projects/index.md | GreenCape/greencape.github.io | 3bc8c467eb277bbf9301a2514a98e0b849df0617 | [
"MIT"
] | 4 | 2021-08-31T10:03:12.000Z | 2021-08-31T10:03:30.000Z | projects/index.md | nibralab/nibralab.github.io | 2a3487a748113bff7de9e3132469453bca62d825 | [
"MIT"
] | null | null | null | ---
layout: page
title: Projects
excerpt: "An index to GreenCape projects."
image:
feature: header-image-2.jpg
---
## [build](/build/)
A docker based test and build environment, especially for Joomla!
## [docker](https://github.com/GreenCape/docker)
Docker images
| 15.941176 | 65 | 0.715867 | eng_Latn | 0.801526 |
87d9ff9e28e302c5447e6c6a06a103b92c4dddf9 | 5,494 | md | Markdown | articles/event-grid/edge/overview.md | niklasloow/azure-docs.sv-se | 31144fcc30505db1b2b9059896e7553bf500e4dc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/event-grid/edge/overview.md | niklasloow/azure-docs.sv-se | 31144fcc30505db1b2b9059896e7553bf500e4dc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/event-grid/edge/overview.md | niklasloow/azure-docs.sv-se | 31144fcc30505db1b2b9059896e7553bf500e4dc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Händelse drivna arkitekturer på kant – Azure Event Grid på IoT Edge
description: Använd Azure Event Grid som en modul på IoT Edge för att vidarebefordra händelser mellan moduler, gräns enheter och molnet.
ms.topic: overview
ms.date: 07/08/2020
ms.openlocfilehash: 82a68f6ab32d8ad18c3af506c810b01d12cf794d
ms.sourcegitcommit: 1e6c13dc1917f85983772812a3c62c265150d1e7
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 07/09/2020
ms.locfileid: "86171524"
---
# <a name="what-is-azure-event-grid-on-azure-iot-edge"></a>Vad är Azure Event Grid på Azure IoT Edge?
Event Grid på IoT Edge ger kraften och flexibiliteten i Azure Event Grid till gränsen. Skapa ämnen, publicera händelser och prenumerera på flera destinationer oavsett om de är moduler på samma enhet, andra gräns enheter eller tjänster i molnet.
Som i molnet hanterar Event Grid i IoT Edge-modulen Routning, filtrering och tillförlitlig leverans av händelser i stor skala. Filtrera händelser för att säkerställa att endast relevanta händelser skickas till olika händelse hanterare med avancerade sträng-, numeriska och booleska filter. Logik för omprövning ser till att händelsen når mål målet även om den inte är tillgänglig vid tidpunkten för publiceringen. Du kan använda Event Grid på IoT Edge som en kraftfull metod för lagring och vidarebefordran.
Event Grid på IoT Edge stöder både CloudEvents v 1.0 och anpassade händelse scheman. Det stöder också samma semantik/sub-semantik som Event Grid i molnet för enkel interoperabilitet.
Den här artikeln innehåller en översikt över Azure Event Grid på IoT Edge. Stegvisa instruktioner för att använda den här modulen på Edge finns i [publicera, prenumerera på händelser lokalt](pub-sub-events-webhook-local.md).
Den här bilden visar några av de olika sätt som du kan använda Event Grid på IoT Edge och inte en omfattande lista över funktioner som stöds.
## <a name="when-to-use-event-grid-on-iot-edge"></a>När du ska använda Event Grid på IoT Edge
Event Grid på IoT Edge är det enkelt att använda, tillförlitlig händelse modell för mellan kanten och molnet.
Event Grid på IoT Edge skapas med en symmetrisk runtime-yta i Azure-molnet, så att du kan använda samma händelser och API-samtal oavsett var du behöver. Oavsett om du använder pub/sub i molnet, på kanten eller mellan de två, kan Event Grid på IoT Edge nu vara en go-to-lösning.
Använd Event Grid på IoT Edge för att utlösa enkla arbets flöden mellan moduler. Du kan till exempel skapa ett ämne och publicera "lagrings BLOB skapad"-händelser från din Storage-modul till ämnet. Nu kan du prenumerera på en eller flera funktioner eller anpassade moduler i ämnena.
Utöka funktionerna mellan gräns enheter. Om du publicerar BLOB module-händelser och vill använda beräknings kraften hos flera nära enheter, skapar du kors enhets prenumerationer.
Anslut slutligen till molnet. Om dina BLOB module-händelser ska synkroniseras regelbundet till molnet, använder du den större beräkning som är tillgänglig i molnet eller skickar bearbetade data och skapar ytterligare prenumerationer för moln tjänster.
Event Grid på IoT Edge ger en flexibel och tillförlitlig frikopplad händelse arkitektur.
## <a name="event-sources"></a>Händelsekällor
På samma sätt som i molnet kan Event Grid på IoT Edge direkt integration mellan moduler för att bygga händelse drivna arkitekturer. För närvarande kan händelserna skickas till Event Grid på IoT Edge från:
* Azure Blob Storage på IoT Edge
* CloudEvents-källor
* Anpassade moduler & behållare via HTTP POST
## <a name="event-handlers"></a>Händelsehanterare
Event Grid på IoT Edge har skapats för att skicka händelser till önskad plats. För närvarande stöds följande destinationer:
* Andra moduler, inklusive IoT Hub, funktioner och anpassade moduler
* Andra gräns enheter
* WebHooks
* Azure Event Grid moln tjänst
* Event Hubs
* Service Bus-köer
* Avsnitt om Service Bus
* Lagringsköer
## <a name="supported-environments"></a>Miljöer som stöds
För närvarande stöds Windows 64-bitars-, Linux 64-bitars-och ARM 32-bitars miljöer.
## <a name="concepts"></a>Begrepp
Det finns fem koncept i Azure Event Grid som gör att du kan komma igång:
* **Händelser** – vad som hände.
* **Händelse källor** – där händelsen ägde rum.
* **Avsnitt** – slut punkten där utgivare skickar händelser.
* **Händelse prenumerationer** – slut punkten eller den inbyggda mekanismen för att dirigera händelser, ibland till fler än en hanterare. Prenumerationer används också av hanterarna för att filtrera inkommande händelser på ett intelligent sätt.
* **Händelse hanterare** – appen eller tjänsten som reagerar på händelsen.
## <a name="cost"></a>Kostnad
Event Grid på IoT Edge är gratis under den offentliga för hands versionen.
## <a name="issues"></a>Ärenden
Rapportera eventuella problem med att använda Event Grid på IoT Edge på [https://github.com/Azure/event-grid-iot-edge/issues](https://github.com/Azure/event-grid-iot-edge/issues) .
## <a name="next-steps"></a>Nästa steg
* [Publicera, prenumerera på händelser lokalt](pub-sub-events-webhook-local.md)
* [Publicera, prenumerera på händelser i molnet](pub-sub-events-webhook-cloud.md)
* [Vidarebefordra händelser till Event Grid Cloud](forward-events-event-grid-cloud.md)
* [Vidarebefordra händelser till IoTHub](forward-events-iothub.md)
* [Agera på Blob Storage-händelser lokalt](react-blob-storage-events-locally.md) | 63.149425 | 507 | 0.794503 | swe_Latn | 0.999821 |
87da1fee27bd5959b447fa7bca34dc0e82f3b0a3 | 1,729 | md | Markdown | sourcecode/funcApprox/README.md | andrire/RNNASIP | 234abaa4c4924cc1d551a6f2fd91a0a557ae95e6 | [
"Apache-2.0"
] | 3 | 2020-11-29T16:27:37.000Z | 2021-08-09T07:25:37.000Z | sourcecode/funcApprox/README.md | andrire/RNNASIP | 234abaa4c4924cc1d551a6f2fd91a0a557ae95e6 | [
"Apache-2.0"
] | null | null | null | sourcecode/funcApprox/README.md | andrire/RNNASIP | 234abaa4c4924cc1d551a6f2fd91a0a557ae95e6 | [
"Apache-2.0"
] | 4 | 2019-09-25T14:53:32.000Z | 2021-03-29T14:22:33.000Z | Copyright (c) 2019 ETH Zurich, Integrated System Laboratory, Renzo Andri
# Matlab Scripts for Evaluation of the Piecewise Linear Approximation
Transcedent function can be approximated by splitting the function in multiple intervals and linear function within the intervals. Functions like tangent hyperbolic and sigmoid are very well suited as the functions are smooth and converge quickly to a constant value.
## File overview
* ```evalClass.m``` Helper Class to evaluate approximation. The ```plot``` function does plot the evaluation versus the original version, but also returns the mean square error, maximum error and the linear coefficients (m and q).
* ```fixedPoint.m``` Models quantization with several helper functions. (see file for more details)
* ```taylorExpansion.m``` Basic scripts to calculate coefficients of taylor expansion.
* ```sig.m``` and ```tanh_eval.m``` scripts used to plot and evaluate the piecewise linear approximation.
## How to use
The scripts in ```sig.m``` and ```tanh_eval.m``` are the same and evaluate either sigmoid or the tangent hyperbolic function.
First the approximation interval is defined in ```firstPt```, ```lastPt``` and ```stepSize```, the the fixed-point format (i.e. fxPtFormat) and the function in ```f```.
Then the script includes several scripts for calculating and ploting.
* Part 1: Calculates the approximation and plots it for visual comparison
* Part 2: Exports the data to C.
* Part 3: Calculates the approximation for a set of parameters (range and interval number)
- 3a) plots the mean square error in 3D plot
- 3b) plots the mean square error in 2D plot
- 3c) plots the maximum error in 3D plot
- 3d) plots the maximum error in 2D plot
| 57.633333 | 267 | 0.756507 | eng_Latn | 0.992352 |
87daec2061e9e53ce543c05d2c44184bdb90d302 | 1,331 | md | Markdown | docs/zh-CN/fade-pop.md | SoldierAb/k-view | 39e35fded3e9190077d4d5fe7abf807afff14c0d | [
"MIT"
] | 11 | 2019-04-03T11:40:07.000Z | 2021-10-12T12:59:53.000Z | docs/zh-CN/fade-pop.md | SoldierAb/k-view | 39e35fded3e9190077d4d5fe7abf807afff14c0d | [
"MIT"
] | 6 | 2020-05-19T03:21:11.000Z | 2022-02-26T17:09:35.000Z | docs/zh-CN/fade-pop.md | SoldierAb/k-view | 39e35fded3e9190077d4d5fe7abf807afff14c0d | [
"MIT"
] | null | null | null | # 弹窗
## 代码演示
### 基础用法
:::kview
```html
<template>
<a class="k-link" @click="showPop = true">点击弹出，点击阴影消失</a>
<k-fade-pop v-model="showPop" draggable modal-hidden footer title="标题" :width="800" :height="400" @submit="submit">
展示内容
</k-fade-pop>
</template>
<style>
.k-link{
padding:10px 20px;
color:#3a8ee6;
}
.k-link:hover{
cursor:pointer;
}
</style>
<script>
import Vue from 'vue'
import FadePop from '../../src/components/fade-pop'
Vue.use(FadePop);
export default{
data(){
return {
showPop:false,
}
},
methods:{
submit(){
alert('submit');
},
},
}
</script>
```
:::
## Props
<div class="markdown-table">
| 参数 | 说明 | 类型 | 默认值| 是否必须|
|-------|---------|------|--------|----------|
|v-model|双向绑定，是否显示|Boolean|false|-
|modalHidden|点击阴影消失|Boolean|true|-
|title|标题头|String|-|-
|beforeClose|关闭前钩子函数|Function|-|-
|width|宽度|String、Number|'60%'|-
|height|高度|String、Number|'80%'|-
|draggable|是否可拖拽|boolean|false|-
|footer|是否显示底部按钮 或 justify-content属性值|boolean ( 是否展示，为true则justify-content默认flex-end )；string ( 展示，其为justify-content属性值，默认 : flex-end ) |false|-
</div> | 21.126984 | 145 | 0.516153 | yue_Hant | 0.222299 |
87db441347e364c10faaf15a2f7d80ea686d444d | 5,896 | md | Markdown | CS/week3.md | siriusctrl/UniPublic | 9df7f8bb9d1209de2af8ac4b5f57ada38587ad50 | [
"Apache-2.0"
] | 8 | 2021-03-14T14:19:10.000Z | 2021-07-13T12:35:26.000Z | CS/week3.md | Sirius-ctrl/UniPublic | 9df7f8bb9d1209de2af8ac4b5f57ada38587ad50 | [
"Apache-2.0"
] | 2 | 2018-05-29T04:28:20.000Z | 2018-06-09T04:55:19.000Z | CS/week3.md | Sirius-ctrl/UniPublic | 9df7f8bb9d1209de2af8ac4b5f57ada38587ad50 | [
"Apache-2.0"
] | 4 | 2018-05-29T03:56:05.000Z | 2018-09-17T06:54:45.000Z | ### How does information go through end-to-end layers
- Application Layer
- the message is sent as a whole, only one header will be added.
- Transport Layer
- provide logical communication between <u>process</u> on different hosts
- but actually you need to go through the socket, so it is a <u>process-to-process/socket-to-socket</u> delivery
- the message is split into chunks, each chunks called a **segment**.
- Each **segment** will be added a header contains information about transport layer
- Network Layer
- provide logical communication between <u>hosts</u>
- Therefore it is a host-to-host delivery.
- This will **add another header** to the segment
- Called datagram
- Compare transport layer and network layer
### Services
- **Network layer** (Host-to-host)
- IP provide <u>logical communication</u> between hosts.
- However, IP is an **unreliable service**
- Does not guarantee segment <u>delivery</u>
- may lost half way
- Does not preserve the <u>order</u> of the segment
- Does not guarantee the <u>integrity</u> of the data in segment
- The content might be altered
- **Transport layer** (process-to-process)
- Demultiplexing (analogous to Bill's job)
- At the <u>receiving end</u>, the <u>transport layer</u> examines the fields in the segment to identify the receiving socket and then directs the segment to the socket.
- Multiplexing (analogous to Ann's job)
- <u>Gather</u> data chunks at the source host from different sockets
- <u>Encapsulate</u> each data chunk with header to create segments
- <u>Pass</u> the segments to the network layer
- each socket has a **unique identifier**
- and each segment has a set of fields for identifying socket in their header
- The **format** of the identifier depends on what transport-layer protocol is used.
### Transport Layer UDP
- UDP
- It almost add nothing to the original data
- Multiplexing and demultiplexing (format of identifier)
- In UDP, sockets are identified by **port numbers**.
- Some light error checking
- checksum
- 
- Source port and dest. Port (from … to ...)
- Length is the total size of the segment, including the header
- Use checksum to check whether the segment has changed
- UDP is <u>connectionless</u> and <u>unreliable</u>
- Inheriting from IP: No guarantees on <u>delivery</u>, <u>order</u>, and <u>integrity</u>
- Why we still need UDP?
- No **congestion-control**, data is sent immediately
- quick
- Real-time application often:
- Requires a minimum sending rate,
- Less delay
- Can tolerate some data loss
- No connection establishment and no connection state.
- Low system overhead (no buffer, no parameters)
- Small packet header overhead
- UDP using 8, while TCP using 20
- UDP checksum
- Used to determine whether bits within the UDP segment have been altered.
- Procedures
- Divide the message into 16 bit words
- Add them up
- If there is a overflow bit, warp the overflow bit to the lowest bit of the sum
- And then send the complement of the code we have
- When receiving the code, we should simply those 16-bit number with the checksum, if all bits turns to 1, that's good.
- We still cannot guarantee that there is no error.
- 110111011010111<u>0</u> and 110111011010111<u>1</u>
- Becomes 110111011010111<u>1</u> and 110111011010111<u>0</u>
- The result are all 1, but the message actually changed.
### Principles of Reliable Data Transfer (RDT)
- Problem encountered
- IP provided by <u>network layer</u> is a unreliable service
- We want a <u>reliable data transfer</u> building on transport layer (on the top of the <u>unreliable IP</u>)
### RDT 1.0 (over a perfect reliable channel)
- <u>perfect reliable channel</u> underneath assumption
- RDT only needs to care sending/receiving and making/extracting packets.
- Sending side
- Receiving side
### RDT 2.0 (stop and wait protocols over a channel only has bit error)
- Sending side
- Receiving side
- Bits in a packet may be corrupted
- The <u>sequence of file</u> must be kept, otherwise error may occur.
- When received a message, ACK or NAK will be feedbacks.
- This retransmission are know as <u>ARQ (Automatic Repeat reQuest)</u>
- Error detection
- Allow receiver to detect bit error (checksum)
- Receiver feedback
- ACK and NAK
- One bit for each, 1 = ACK, 0 = NAK
- Retransmission
- The sender retransmit a packet when it is received in errors
- When the sender is in the <u>wait-for-ACK-or-NAK state</u>, it cannot get more data from the upper layer
- Bit error
- Fatal flaw about RDT 2.0
- the ACK or NAK packet could be corrupted
- How to fix this?
- checksum
- How protocol should handle the errors
- Retrainsmit the garbled ACK/NAK packet
- However, the retransmission can also corrupted, and the system may failed after that.
- Use enough checksum so that the receiver can also recover from bit errors.
- But it couldn't handle if the packets were lost
- Resends the current data packet when it receives a garbled ACK or NAK packet
- Add a <u>sequence number</u> so that the receiver knows whether the message is a old message or new one
- In stop-and-wait protocol, a 1-bit sequence number will suffice. The sender keep alternates the 1-bit sequence number between 0 and 1.
| 40.383562 | 173 | 0.709973 | eng_Latn | 0.996019 |
87dc2462eaf509647d9aff68569536bbc4ffff0a | 20,348 | md | Markdown | articles/data-factory/connector-http.md | EINSTEINPRACIANO/azure-docs.pt-br | 93bbbf115ab76d31e6bc8919a338700294966913 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/connector-http.md | EINSTEINPRACIANO/azure-docs.pt-br | 93bbbf115ab76d31e6bc8919a338700294966913 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/connector-http.md | EINSTEINPRACIANO/azure-docs.pt-br | 93bbbf115ab76d31e6bc8919a338700294966913 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Copiar dados de uma fonte HTTP usando o Azure Data Factory | Microsoft Docs
description: Saiba como copiar dados de uma fonte HTTP local ou de nuvem para armazenamentos de dados de coletor com suporte, usando uma atividade de cópia em um pipeline do Azure Data Factory.
services: data-factory
documentationcenter: ''
author: linda33wj
manager: craigg
ms.reviewer: douglasl
ms.service: data-factory
ms.workload: data-services
ms.tgt_pltfrm: na
ms.topic: conceptual
ms.date: 04/29/2019
ms.author: jingwang
ms.openlocfilehash: a668bb2e0e3381abefaac93a0fb63f0d33bac5a1
ms.sourcegitcommit: 2ce4f275bc45ef1fb061932634ac0cf04183f181
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 05/07/2019
ms.locfileid: "65234037"
---
# <a name="copy-data-from-an-http-endpoint-by-using-azure-data-factory"></a>Copiar dados de um ponto de extremidade HTTP usando o Azure Data Factory
> [!div class="op_single_selector" title1="Select the version of Data Factory service you are using:"]
> * [Versão 1](v1/data-factory-http-connector.md)
> * [Versão atual](connector-http.md)
Este artigo descreve como usar a atividade de cópia no Azure Data Factory para copiar dados de um ponto de extremidade HTTP. O artigo baseia-se em [Atividade de Cópia no Azure Data Factory](copy-activity-overview.md), que apresenta uma visão geral da Atividade de Cópia.
A diferença entre esse conector HTTP, o [conector REST](connector-rest.md) e o [conector de tabela da Web](connector-web-table.md) é:
- **conector REST** dá suporte especificamente à cópia de dados de APIs RESTful;
- O **conector HTTP** é genérico para recuperar dados de qualquer ponto de extremidade HTTP, por exemplo, para baixar o arquivo. Antes desse conector REST ser disponibilizado, talvez você use o conector HTTP para copiar dados da API RESTful, o que tem suporte, mas é menos funcional em comparação ao conector REST.
- O **conector da tabela da Web** extrai o conteúdo da tabela de uma página da Web em HTML.
## <a name="supported-capabilities"></a>Funcionalidades com suporte
Você pode copiar dados de uma origem HTTP para qualquer repositório de dados do coletor com suporte. Para obter uma lista de armazenamentos de dados que o Copy Activity suporta como fontes e coletores, consulte [Armazenamentos de dados e formatos compatíveis](copy-activity-overview.md#supported-data-stores-and-formats).
Você pode usar esse conector HTTP para:
- Recuperar dados de um endpoint HTTP / S usando os métodos HTTP **GET** ou **POST**.
- Recupere dados usando uma das seguintes autenticações: **Anônima**, **Básica**, **Digest**, **Windows** ou **ClientCertificate**.
- Copie a resposta HTTP como está ou analise-a usando [formatos de arquivo suportados e codecs de compactação](supported-file-formats-and-compression-codecs.md).
> [!TIP]
> Para testar uma solicitação HTTP para recuperação de dados antes de configurar o conector HTTP no Data Factory, saiba mais sobre a especificação da API para os requisitos de cabeçalho e corpo. Você pode usar ferramentas como o Postman ou um navegador da Web para validar.
## <a name="get-started"></a>Introdução
[!INCLUDE [data-factory-v2-connector-get-started](../../includes/data-factory-v2-connector-get-started.md)]
As seções a seguir fornecem detalhes sobre propriedades que você pode usar para definir entidades do Data Factory específicas do conector HTTP.
## <a name="linked-service-properties"></a>Propriedades do serviço vinculado
As seguintes propriedades são suportadas para o serviço vinculado HTTP:
| Propriedade | DESCRIÇÃO | Obrigatório |
|:--- |:--- |:--- |
| type | O **tipo** propriedade deve ser definida como **HttpServer**. | Sim |
| url | A URL base para o servidor web. | Sim |
| enableServerCertificateValidation | Especifique se deseja ativar a validação do certificado SSL do servidor ao se conectar a um terminal HTTP. Se seu servidor HTTPS usa um certificado autoassinado, defina essa propriedade como **falsos**. | Não<br /> (o padrão é **verdadeiro**) |
| authenticationType | Especifica o tipo de autenticação. Os valores permitidos são **Anonymous**, **Basic**, **Digest**, **Windows** e **ClientCertificate**. <br><br> Veja as seções que seguem esta tabela para mais propriedades e amostras JSON para esses tipos de autenticação. | Sim |
| connectVia | O [Tempo de Integração](concepts-integration-runtime.md) a ser usado para se conectar ao armazenamento de dados. Você pode usar o Tempo de Execução de Integração do Azure ou um Tempo de Execução de Integração auto-hospedado (se o seu armazenamento de dados estiver localizado em uma rede privada). Se não especificado, essa propriedade usará o tempo de execução de integração do Azure padrão. |Não |
### <a name="using-basic-digest-or-windows-authentication"></a>Usando a autenticação Básica, Digest ou Windows
Defina a **authenticationType** propriedade **Básico**, **Digest**, ou **Windows**. Além das propriedades genéricas descritas na seção anterior, especifique as seguintes propriedades:
| Propriedade | DESCRIÇÃO | Obrigatório |
|:--- |:--- |:--- |
| userName | O nome de usuário a ser usada para acessar o ponto de extremidade HTTP. | Sim |
| password | A senha do usuário (o **nome de usuário** valor). Marque esse campo como um tipo **SecureString** para armazená-lo com segurança no Data Factory. Você também pode [referenciar um segredo armazenado no Cofre de Chaves do Azure](store-credentials-in-key-vault.md). | Sim |
**Exemplo**
```json
{
"name": "HttpLinkedService",
"properties": {
"type": "HttpServer",
"typeProperties": {
"authenticationType": "Basic",
"url" : "<HTTP endpoint>",
"userName": "<user name>",
"password": {
"type": "SecureString",
"value": "<password>"
}
},
"connectVia": {
"referenceName": "<name of Integration Runtime>",
"type": "IntegrationRuntimeReference"
}
}
}
```
### <a name="using-clientcertificate-authentication"></a>Usando a autenticação ClientCertificate
Para usar a autenticação ClientCertificate, defina a propriedade **authenticationType** como **ClientCertificate**. Além das propriedades genéricas descritas na seção anterior, especifique as seguintes propriedades:
| Propriedade | DESCRIÇÃO | Obrigatório |
|:--- |:--- |:--- |
| embeddedCertData | Dados de certificado codificados em Base64. | Especificar **embeddedCertData** ou **certThumbprint**. |
| certThumbprint | A impressão digital do certificado que está instalado no armazenamento de certificados da sua máquina de Automação do Runtime Integration. Aplica-se apenas quando o tipo de tempo de execução de integração auto-hospedado é especificado na propriedade **connectVia**. | Especificar **embeddedCertData** ou **certThumbprint**. |
| password | A senha associada com o certificado. Marque esse campo como um tipo **SecureString** para armazená-lo com segurança no Data Factory. Você também pode [referenciar um segredo armazenado no Cofre de Chaves do Azure](store-credentials-in-key-vault.md). | Não |
Se você usar **certThumbprint** para autenticação e o certificado estiver instalado no armazenamento pessoal do computador local, conceda permissões de leitura ao Tempo de Integração auto-hospedado:
1. Abra o Console de gerenciamento Microsoft (MMC). Adicione a **certificados** snap-in que tem como alvo **computador Local**.
2. Expanda **Certificados** > **Pessoal** e, em seguida, selecione **Certificados**.
3. Clique com o botão direito do mouse no certificado do armazenamento pessoal e selecione **Todas as Tarefas** > **Gerenciar Chaves Particulares**.
3. Na guia **Segurança**, adicione a conta de usuário na qual o Serviço de Host do Tempo de Integração do Integration (DIAHostService) está em execução, com acesso de leitura ao certificado.
**Exemplo 1: Usar certThumbprint**
```json
{
"name": "HttpLinkedService",
"properties": {
"type": "HttpServer",
"typeProperties": {
"authenticationType": "ClientCertificate",
"url": "<HTTP endpoint>",
"certThumbprint": "<thumbprint of certificate>"
},
"connectVia": {
"referenceName": "<name of Integration Runtime>",
"type": "IntegrationRuntimeReference"
}
}
}
```
**Exemplo 2: Usar embeddedCertData**
```json
{
"name": "HttpLinkedService",
"properties": {
"type": "HttpServer",
"typeProperties": {
"authenticationType": "ClientCertificate",
"url": "<HTTP endpoint>",
"embeddedCertData": "<Base64-encoded cert data>",
"password": {
"type": "SecureString",
"value": "password of cert"
}
},
"connectVia": {
"referenceName": "<name of Integration Runtime>",
"type": "IntegrationRuntimeReference"
}
}
}
```
## <a name="dataset-properties"></a>Propriedades do conjunto de dados
Para obter uma lista completa das seções e propriedades disponíveis para definir os conjuntos de dados, confira o artigo sobre [Conjuntos de Dados](concepts-datasets-linked-services.md).
- Para **Parquet e formato de texto delimitado**, consulte [conjunto de dados de formato de Parquet e texto delimitado](#parquet-and-delimited-text-format-dataset) seção.
- Para outros formatos, como **formato ORC/Avro/JSON/binário**, consulte [outro conjunto de dados do formato](#other-format-dataset) seção.
### <a name="parquet-and-delimited-text-format-dataset"></a>Conjunto de dados de formato de parquet e texto delimitado
Para copiar dados de HTTP na **Parquet ou o formato de texto delimitado**, consulte [formato Parquet](format-parquet.md) e [formato de texto delimitado](format-delimited-text.md) artigo no conjunto de dados de formato e com suporte Configurações. As propriedades a seguir têm suporte para HTTP em `location` configurações no conjunto de dados com base no formato:
| Propriedade | DESCRIÇÃO | Obrigatório |
| ----------- | ------------------------------------------------------------ | -------- |
| type | A propriedade type sob `location` no conjunto de dados deve ser definida como **HttpServerLocation**. | Sim |
| relativeUrl | Uma URL relativa para o recurso que contém os dados. | Não |
> [!NOTE]
> O tamanho da carga útil do pedido HTTP suportado é de cerca de 500 KB. Se o tamanho da carga útil que você deseja passar para seu ponto de extremidade da web for maior que 500 KB, considere agrupar a carga útil em partes menores.
> [!NOTE]
> **HttpFile** ainda há suporte para o tipo de conjunto de dados com formato de texto/Parquet mencionado na próxima seção como-destina-se a atividade de cópia/pesquisa para compatibilidade com versões anteriores. São sugeridas para usar esse novo modelo no futuro, e o ADF criação da interface do usuário foi alternada para gerar esses novos tipos.
**Exemplo:**
```json
{
"name": "DelimitedTextDataset",
"properties": {
"type": "DelimitedText",
"linkedServiceName": {
"referenceName": "<HTTP linked service name>",
"type": "LinkedServiceReference"
},
"schema": [ < physical schema, optional, auto retrieved during authoring > ],
"typeProperties": {
"location": {
"type": "HttpServerLocation",
"relativeUrl": "<relative url>"
},
"columnDelimiter": ",",
"quoteChar": "\"",
"firstRowAsHeader": true,
"compressionCodec": "gzip"
}
}
}
```
### <a name="other-format-dataset"></a>Outro conjunto de dados de formato
Para copiar dados de HTTP na **formato ORC/Avro/JSON/binário**, as propriedades a seguir têm suporte:
| Propriedade | DESCRIÇÃO | Obrigatório |
|:--- |:--- |:--- |
| type | O **tipo** propriedade do conjunto de dados deve ser definida como **HttpFile**. | Sim |
| relativeUrl | Uma URL relativa para o recurso que contém os dados. Quando essa propriedade não é especificada, somente o URL especificado na definição de serviço vinculada é usado. | Não |
| requestMethod | O método HTTP. Valores permitidos são **Obtenha** (padrão) e **Post**. | Não |
| additionalHeaders | Cabeçalhos de solicitação HTTP adicionais. | Não |
| requestBody | O corpo da solicitação HTTP. | Não |
| format | Se você deseja recuperar dados do terminal HTTP como estão, sem analisá-los e, em seguida, copiar os dados para um armazenamento baseado em arquivo, ignore a seção **formato** nas definições de conjunto de dados de entrada e saída.<br/><br/>Se você quiser analisar o conteúdo da resposta HTTP durante a cópia, há suporte para os seguintes tipos de formato de arquivo: **TextFormat**, **JsonFormat**, **AvroFormat**, **OrcFormat** e **ParquetFormat**. No **formato**, defina a propriedade **tipo** como um desses valores. Para obter mais informações, consulte [formato JSON](supported-file-formats-and-compression-codecs.md#json-format), [formato de texto](supported-file-formats-and-compression-codecs.md#text-format), [formato Avro](supported-file-formats-and-compression-codecs.md#avro-format), [formato Orc](supported-file-formats-and-compression-codecs.md#orc-format) e [formato Parquet](supported-file-formats-and-compression-codecs.md#parquet-format). |Não |
| compression | Especifique o tipo e o nível de compactação para os dados. Para obter mais informações, consulte [Formatos de arquivo e codecs de compactação com suporte](supported-file-formats-and-compression-codecs.md#compression-support).<br/><br/>Tipos com suporte: **GZip**, **Deflate**, **BZip2** e **ZipDeflate**.<br/>Níveis compatíveis: **Ideal** e **Mais Rápido**. |Não |
> [!NOTE]
> O tamanho da carga útil do pedido HTTP suportado é de cerca de 500 KB. Se o tamanho da carga útil que você deseja passar para seu ponto de extremidade da web for maior que 500 KB, considere agrupar a carga útil em partes menores.
**Exemplo 1: Usar o método Get (padrão)**
```json
{
"name": "HttpSourceDataInput",
"properties": {
"type": "HttpFile",
"linkedServiceName": {
"referenceName": "<HTTP linked service name>",
"type": "LinkedServiceReference"
},
"typeProperties": {
"relativeUrl": "<relative url>",
"additionalHeaders": "Connection: keep-alive\nUser-Agent: Mozilla/5.0\n"
}
}
}
```
**Exemplo 2: Usar o método Post**
```json
{
"name": "HttpSourceDataInput",
"properties": {
"type": "HttpFile",
"linkedServiceName": {
"referenceName": "<HTTP linked service name>",
"type": "LinkedServiceReference"
},
"typeProperties": {
"relativeUrl": "<relative url>",
"requestMethod": "Post",
"requestBody": "<body for POST HTTP request>"
}
}
}
```
## <a name="copy-activity-properties"></a>Propriedades da Atividade de Cópia
Esta seção fornece uma lista de propriedades que a fonte HTTP suporta.
Para obter uma lista completa de seções e propriedades que estão disponíveis para definir atividades, consulte [Pipelines](concepts-pipelines-activities.md).
### <a name="http-as-source"></a>HTTP como fonte
- Para copiar de **Parquet e formato de texto delimitado**, consulte [Parquet e a origem do formato de texto delimitado](#parquet-and-delimited-text-format-source) seção.
- Para cópia de outros formatos, como **formato ORC/Avro/JSON/binário**, consulte [outra fonte de formato](#other-format-source) seção.
#### <a name="parquet-and-delimited-text-format-source"></a>Parquet e a origem do formato de texto delimitado
Para copiar dados de HTTP na **Parquet ou o formato de texto delimitado**, consulte [formato Parquet](format-parquet.md) e [formato de texto delimitado](format-delimited-text.md) artigo sobre a fonte da atividade de cópia baseada em formato e configurações com suporte. As propriedades a seguir têm suporte para HTTP em `storeSettings` as configurações na fonte de cópia com base no formato:
| Propriedade | DESCRIÇÃO | Obrigatório |
| ------------------------ | ------------------------------------------------------------ | -------- |
| type | A propriedade type sob `storeSettings` deve ser definida como **HttpReadSetting**. | Sim |
| requestMethod | O método HTTP. <br>Valores permitidos são **Obtenha** (padrão) e **Post**. | Não |
| addtionalHeaders | Cabeçalhos de solicitação HTTP adicionais. | Não |
| requestBody | O corpo da solicitação HTTP. | Não |
| requestTimeout | O tempo limite (o valor **TimeSpan**) para a solicitação HTTP para obter uma resposta. Esse valor é o tempo limite para obter uma resposta, não o tempo limite para ler os dados da resposta. O valor padrão é **01:00:40**. | Não |
| maxConcurrentConnections | O número das conexões para se conectar ao repositório de armazenamento simultaneamente. Especifique somente quando você quiser limitar a conexão simultâneo ao armazenamento de dados. | Não |
> [!NOTE]
> Para o formato de texto delimitado por Parquet /, **HttpSource** ainda tem suporte como origem de atividade de cópia de tipo mencionada na próxima seção-é para compatibilidade com versões anteriores. São sugeridas para usar esse novo modelo no futuro, e o ADF criação da interface do usuário foi alternada para gerar esses novos tipos.
**Exemplo:**
```json
"activities":[
{
"name": "CopyFromHTTP",
"type": "Copy",
"inputs": [
{
"referenceName": "<Delimited text input dataset name>",
"type": "DatasetReference"
}
],
"outputs": [
{
"referenceName": "<output dataset name>",
"type": "DatasetReference"
}
],
"typeProperties": {
"source": {
"type": "DelimitedTextSource",
"formatSettings":{
"type": "DelimitedTextReadSetting",
"skipLineCount": 10
},
"storeSettings":{
"type": "HttpReadSetting",
"requestMethod": "Post",
"additionalHeaders": "<header key: header value>\n<header key: header value>\n",
"requestBody": "<body for POST HTTP request>"
}
},
"sink": {
"type": "<sink type>"
}
}
}
]
```
#### <a name="other-format-source"></a>Outra fonte de formato
Para copiar dados de HTTP na **formato ORC/Avro/JSON/binário**, as propriedades a seguir têm suporte na atividade de cópia **origem** seção:
| Propriedade | DESCRIÇÃO | Obrigatório |
|:--- |:--- |:--- |
| type | A propriedade **tipo** da origem da atividade de cópia deve ser configurada para **HttpSource**. | Sim |
| httpRequestTimeout | O tempo limite (o valor **TimeSpan**) para a solicitação HTTP para obter uma resposta. Esse valor é o tempo limite para obter uma resposta, não o tempo limite para ler os dados da resposta. O valor padrão é **01:00:40**. | Não |
**Exemplo**
```json
"activities":[
{
"name": "CopyFromHTTP",
"type": "Copy",
"inputs": [
{
"referenceName": "<HTTP input dataset name>",
"type": "DatasetReference"
}
],
"outputs": [
{
"referenceName": "<output dataset name>",
"type": "DatasetReference"
}
],
"typeProperties": {
"source": {
"type": "HttpSource",
"httpRequestTimeout": "00:01:00"
},
"sink": {
"type": "<sink type>"
}
}
}
]
```
## <a name="next-steps"></a>Próximas etapas
Para obter uma lista de armazenamentos de dados que o Copy Activity suporta como fontes e coletores no Azure Data Factory, consulte [Armazenamentos e formatos de dados compatíveis](copy-activity-overview.md#supported-data-stores-and-formats).
| 53.830688 | 975 | 0.670533 | por_Latn | 0.993114 |
87dc43724ee5fcd8c45299a5c6128fea942ef61c | 309 | md | Markdown | docs/README.md | fdmxfarhan/phasemoon | 80d843f106cfc79d68c31b0abe713f91a3e1a01a | [
"Apache-2.0"
] | 23 | 2021-01-03T12:31:03.000Z | 2022-02-26T00:26:14.000Z | docs/README.md | fdmxfarhan/phasemoon | 80d843f106cfc79d68c31b0abe713f91a3e1a01a | [
"Apache-2.0"
] | 79 | 2021-01-02T09:29:59.000Z | 2022-02-21T16:47:06.000Z | docs/README.md | fdmxfarhan/phasemoon | 80d843f106cfc79d68c31b0abe713f91a3e1a01a | [
"Apache-2.0"
] | 20 | 2021-01-14T17:47:26.000Z | 2022-03-17T11:38:04.000Z | # How to generate docs:
Use this to install markdown tooling:
``pip install mkdocs-material``
Use this to serve the web page locally:
``mkdocs serve --config-file docs/mkdocs.yml``
Using IntelliJ, you can add ``bin/serve.sh`` as a run config.
# How to change the menu
The menu is listed in mkdocs.yml.
| 19.3125 | 61 | 0.728155 | eng_Latn | 0.977325 |
87dd36767e61ed7c688b9265a906af47d0dddb3d | 2,918 | md | Markdown | README.md | cryptofuture/desktop | cc18570ff188af270e716eeee9ca5f78c9913a1e | [
"MIT"
] | null | null | null | README.md | cryptofuture/desktop | cc18570ff188af270e716eeee9ca5f78c9913a1e | [
"MIT"
] | 1 | 2018-05-05T02:05:15.000Z | 2018-05-06T14:39:48.000Z | README.md | cryptofuture/desktop | cc18570ff188af270e716eeee9ca5f78c9913a1e | [
"MIT"
] | 2 | 2018-05-04T16:40:03.000Z | 2018-05-19T02:54:04.000Z | # Musicoin Wallet
The official Musicoin Desktop Wallet
[](https://github.com/Musicoin/desktop/releases/latest)
[](https://github.com/Musicoin/desktop/blob/master/LICENSE)
[](https://github.com/Musicoin/desktop/releases)
## Nightly Builds
Nightly builds for all supported Operating Systems can be found over at [builder.musicoin.org](https://builder.musicoin.org/)
Supported Operating systems:
1. Windows 7 and later - [64 bit](https://builder.musicoin.org/windows-x64.exe), [32bit](https://builder.musicoin.org/windows-x32.exe)
2. macOS - [64 bit](https://builder.musicoin.org/mac-x64.zip)
3. Linux - [64 bit](https://builder.musicoin.org/linux-x64.tar.xz), [32bit](https://builder.musicoin.org/linux-x32.tar.xz)
4. Windows XP and older - [32bit](https://builder.musicoin.org/windows-x32-legacy.exe), [64 bit](https://builder.musicoin.org/windows-x64-legacy.exe)
## Getting started
Prerequisites:
- node >=8.0.0
- yarn >=1.7.0
- Wine for windows builds on non Windows systems
## Build Release version
1. `git clone https://github.com/Musicoin/desktop && cd desktop`
2. `yarn`
3. `cd interface ; yarn; cd ..`
4. `nw .`
## Build Alpha version
1. `git clone https://github.com/Musicoin/desktop && cd desktop`
2. Delete `package.json`
3. Rename `package-alpha.json` to `package.json`
4. `yarn`
5. `nw .`
## Packaging the app
1. `git clone https://github.com/Musicoin/desktop && cd desktop`
2. `yarn --link-duplicates`
3. `yarn debug` - This will run in SDK mode for development.
4. `yarn build-all`
-or-
`yarn build-x86`
-or-
`yarn build-x64`
to build all packages for windows, mac, and linux. This is meant for testing or development and packaging.
5. `yarn run build -m --x64 ./` - for packaging MacOS x64. `-m`, `-l`, or `-w` determines the os and architecture.
## Testing new interface builds
This repo contains UI modules in accordance with the last release version. To suggest changes, edit the files at `interface/` and issue a PR to the [desktop-interface](https://github.com/Musicoin/desktop-interface) repo.
## Contributing
Pull Requests and Bug Reports are most welcome.
The Wallet repo makes use of the following submodules:
1. [Default UI module](https://github.com/Musicoin/desktop-interface)
2. [`go-musicoin` npm package](https://github.com/Musicoin/gmc-node-modules)
3. [Web3 fork of musicoin](https://github.com/Musicoin/web3.js)
## Bounty program
Specific Issues are earmarked for bounty and carry a bounty label with them. More information regarding the bounty program can be found over at [BOUNTY](docs/BOUNTY.md).
## License
MIT
| 39.432432 | 220 | 0.735093 | eng_Latn | 0.546653 |
87ddbcdd039ea29d7d574753b8880e797ed9c926 | 3,570 | md | Markdown | _posts/2018-11-17-Download-popsplat-english-edition.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | _posts/2018-11-17-Download-popsplat-english-edition.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | _posts/2018-11-17-Download-popsplat-english-edition.md | Bunki-booki/29 | 7d0fb40669bcc2bafd132f0991662dfa9e70545d | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Popsplat english edition book
"The handler at the village terminal will route them through. He's the captain of a ship and should not leave it. flames and smoke of the log fire rose high against the sky. field of battle. Prontschischev, and the roots of the island in the dark under that, roll down the rocky peaks, O damsel. Shrieking brakes and I do for a living. Scars disfigured Agnes from shoulders to buttocks, but there had What was it they called a condemned man in prison. " patient, who was the youngest among the crew, Howard Kalens again denounced Wellesley's policy of "scandalous appeasement to what we at last see exposed as terrorist anarchy and gangsterism" and demanded that a state of emergency be declared. Popsplat english edition, staring up at the words visible here and there between the rushes in the eaves? There's been some talk about the Company hiring scabs, pale scars and others dark. molested. A ripe grassy scent overlays the more subtle smell of rich, since "What popsplat english edition of outcome?" Thelma asked from beside Leon, so he might put the king to shame and outrage his honour; and if the king slay him not, and no sign of the cock? From the sea off the To counter a rising tide of fear, making a beacon of her voice, but I think he also guessed. He was nobody, and that The young women often strike one as very pretty if one can rid "When and where did we begin to go too far, afraid of causing pain even with a gentle touch, but the final rush -would be suicidal - - and probably futile since the lock doors looked strong enough to stop anything short - of a tactical missile. But if "What did you mean, repeat that song!' So Kemeriyeh repeated it and Tuhfeh swooned away, and don't let anyone touch anything. Will you go with me to popsplat english edition dwelling-place, she popsplat english edition not play with overheating vehicles, but getting to them would be tricky, the dwarf (One-sixth of the natural size, could however at first Their struggle to put their sorrow into words moved Agnes not because they drapery rods, drenching rain pounded Tom at once, using their arts to pursue goals they agreed were Never before had she put faith in any form of prognostication, sanctions could lead to the foment of rebellion, as the case may be, Popsplat english edition, Of Looking to the Issues of. " owing in no small degree to the defective nature of the vessels, with the salt Tom and the pepper Tom standing side by side in their different but parallel worlds. Popsplat english edition wore a popsplat english edition hat with a wide brim to rain appeared to slide away from him a millimeter popsplat english edition contact, "Indeed, so I leaven must be gross. submission. "All that the resources he consumed to sustain himself? Like slaves' lives. A psychic claims to predict the future. He did not try a love-charm on her again. popsplat english edition police would we call. toward an abyss. 1780, everything; she had listened; she had been still? Not that they'd have succeeded if they had. He thought of the Summoner's eyes, something crunched beneath side of the bald men none can give any trustworthy account Cass to Polly, too, but also rich in talent. bone or wooden, with that which was therein; whereupon the other arose, the She leads them to the door of the nearby Fleetwood American Heritage? With one tiny hand, ringing faintly against Celestina sensed an easy camaraderie between these two men. Since bringing Wally to town, K. | 396.666667 | 3,472 | 0.792157 | eng_Latn | 0.999826 |
87de05ee9c61fdfeb760744aad9c3430f96eab97 | 7,301 | md | Markdown | README.md | gravitus/JSONJoy-Swift | 5cb7209d00319d6da47355d72615bc47b6fe0003 | [
"Apache-2.0"
] | 359 | 2015-01-06T12:58:27.000Z | 2022-02-12T14:48:03.000Z | README.md | gravitus/JSONJoy-Swift | 5cb7209d00319d6da47355d72615bc47b6fe0003 | [
"Apache-2.0"
] | 57 | 2015-01-12T15:27:12.000Z | 2018-01-24T09:10:05.000Z | README.md | gravitus/JSONJoy-Swift | 5cb7209d00319d6da47355d72615bc47b6fe0003 | [
"Apache-2.0"
] | 86 | 2015-01-07T10:59:46.000Z | 2018-07-11T15:12:08.000Z | JSONJoy
=============
Convert JSON to Swift objects. The Objective-C counterpart can be found here: [JSONJoy](https://github.com/daltoniam/JSONJoy).
Parsing JSON in Swift has be likened to a trip through Mordor, then JSONJoy would be using eagles for that trip.
#### Deprecation
The release of Swift 4 brought support for the new `Codable` protocol. This renders most of JSONJoy unneccessary and thus will be deprecated. Version 3.0.2 has been update to support Swift 4 as a means of backward compatibility, but I would encourage the adoption of the new `Codable` protocol. I wrote a post about it [here](vluxe.io/codable-json-swift.html)
First thing is to import the framework. See the Installation instructions on how to add the framework to your project.
```swift
import JSONJoy
```
## Example
First here is some example JSON we have to parse.
```javascript
{
"id" : 1,
"first_name": "John",
"last_name": "Smith",
"age": 25,
"address": {
"id": 1,
"street_address": "2nd Street",
"city": "Bakersfield",
"state": "CA",
"postal_code": 93309
}
}
```
We want to translate that JSON to these Swift objects:
```swift
struct Address {
let objID: Int?
let streetAddress: String?
let city: String?
let state: String?
let postalCode: String?
init() {
}
}
struct User {
let objID: Int?
let firstName: String?
let lastName: String?
let age: Int?
let address = Address()
init() {
}
}
```
Normally this would put us in a validation nightmare:
```
var user = User()
var error: NSError?
var response: AnyObject? = NSJSONSerialization.JSONObjectWithData(data, options: NSJSONReadingOptions(), error: &error)
if let userDict = response as? NSDictionary {
if let addressDict = userDict["address"] as? NSDictionary {
user.address.city = addressDict["city"] as? String
user.address.streetAddress = addressDict["street_address"] as? String
//etc, etc
}
user.firstName = userDict["first_name"] as? String
user.lastName = userDict["last_name"] as? String
//etc, etc
}
```
JSONJoy makes this much simpler. We have our Swift objects implement the JSONJoy protocol:
```swift
struct Address : JSONJoy {
let objID: Int
let streetAddress: String
let city: String
let state: String
let postalCode: String
let streetTwo: String?
init(_ decoder: JSONLoader) throws {
objID = try decoder["id"].get()
streetAddress = try decoder["street_address"].get()
city = try decoder["city"].get()
state = try decoder["state"].get()
postalCode = try decoder["postal_code"].get()
streetTwo = decoder["street_two"].getOptional()
//just an example of "checking" for a property.
if let meta: String = decoder["meta"].getOptional() {
print("found some meta info: \(meta)")
}
}
}
struct User : JSONJoy {
let objID: Int
let firstName: String
let lastName: String
let age: Int
let address: Address
let addresses: [Address]
init(_ decoder: JSONLoader) throws {
objID = try decoder["id"].get()
firstName = try decoder["first_name"].get()
lastName = try decoder["last_name"].get()
age = try decoder["age"].get()
address = try Address(decoder["address"])
addresses = try decoder["addresses"].get() //infers the type and returns a valid array
}
}
```
Then when we get the JSON back:
```swift
do {
var user = try User(JSONLoader(data))
println("city is: \(user.address.city)")
//That's it! The object has all the appropriate properties mapped.
} catch {
print("unable to parse the JSON")
}
```
This also has automatic optional validation like most Swift JSON libraries.
```swift
//some randomly incorrect key. This will work fine and the property will just be nil.
firstName = decoder[5]["wrongKey"]["MoreWrong"].getOptional()
//firstName is nil, but no crashing!
```
## Custom Types
If you to extend a standard Foundation type (you probably won't need to though)
```swift
extension UInt64: JSONBasicType {}
```
## SwiftHTTP
This can be combined with SwiftHTTP to make API interaction really clean and easy.
https://github.com/daltoniam/SwiftHTTP#clientserver-example
## Requirements
JSONJoy requires at least iOS 7/OSX 10.10 or above.
## Installation
### Swift Package Manager
Add the project as a dependency to your Package.swift:
```swift
import PackageDescription
let package = Package(
name: "YourProject",
dependencies: [
.Package(url: "https://github.com/daltoniam/JSONJoy-Swift", majorVersion: 3)
]
)
```
### CocoaPods
Check out [Get Started](http://cocoapods.org/) tab on [cocoapods.org](http://cocoapods.org/).
To use JSONJoy-Swift in your project add the following 'Podfile' to your project
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
use_frameworks!
pod 'JSONJoy-Swift', '~> 3.0.2'
Then run:
pod install
### Carthage
Check out the [Carthage](https://github.com/Carthage/Carthage) docs on how to add a install. The `JSONJoy` framework is already setup with shared schemes.
[Carthage Install](https://github.com/Carthage/Carthage#adding-frameworks-to-an-application)
You can install Carthage with [Homebrew](http://brew.sh/) using the following command:
```bash
$ brew update
$ brew install carthage
```
To integrate JSONJoy into your Xcode project using Carthage, specify it in your `Cartfile`:
```
github "daltoniam/JSONJoy-Swift" >= 3.0.2
```
### Rogue
First see the [installation docs](https://github.com/acmacalister/Rogue) for how to install Rogue.
To install JSONJoy run the command below in the directory you created the rogue file.
```
rogue add https://github.com/daltoniam/JSONJoy-Swift
```
Next open the `libs` folder and add the `JSONJoy.xcodeproj` to your Xcode project. Once that is complete, in your "Build Phases" add the `JSONJoy.framework` to your "Link Binary with Libraries" phase. Make sure to add the `libs` folder to your `.gitignore` file.
### Other
Simply grab the framework (either via git submodule or another package manager).
Add the `JSONJoy.xcodeproj` to your Xcode project. Once that is complete, in your "Build Phases" add the `JSONJoy.framework` to your "Link Binary with Libraries" phase.
### Add Copy Frameworks Phase
If you are running this in an OSX app or on a physical iOS device you will need to make sure you add the `JSONJoy.framework` included in your app bundle. To do this, in Xcode, navigate to the target configuration window by clicking on the blue project icon, and selecting the application target under the "Targets" heading in the sidebar. In the tab bar at the top of that window, open the "Build Phases" panel. Expand the "Link Binary with Libraries" group, and add `JSONJoy.framework`. Click on the + button at the top left of the panel and select "New Copy Files Phase". Rename this new phase to "Copy Frameworks", set the "Destination" to "Frameworks", and add `JSONJoy.framework`.
## TODOs
- [ ] Add Unit Tests
## License
JSONJoy is licensed under the Apache v2 License.
## Contact
### Dalton Cherry ###
* https://github.com/daltoniam
* http://twitter.com/daltoniam
* http://daltoniam.com
| 28.631373 | 685 | 0.695658 | eng_Latn | 0.903171 |
87defa87f410a37554c10a742999aa5fdac407ca | 21,539 | md | Markdown | docs/connect/jdbc/understanding-xa-transactions.md | CeciAc/sql-docs.fr-fr | 0488ed00d9a3c5c0a3b1601a143c0a43692ca758 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/connect/jdbc/understanding-xa-transactions.md | CeciAc/sql-docs.fr-fr | 0488ed00d9a3c5c0a3b1601a143c0a43692ca758 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/connect/jdbc/understanding-xa-transactions.md | CeciAc/sql-docs.fr-fr | 0488ed00d9a3c5c0a3b1601a143c0a43692ca758 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-03-04T05:50:54.000Z | 2020-03-04T05:50:54.000Z | ---
title: Fonctionnement des transactions XA | Microsoft Docs
ms.custom: ''
ms.date: 08/12/2019
ms.prod: sql
ms.prod_service: connectivity
ms.reviewer: ''
ms.technology: connectivity
ms.topic: conceptual
ms.assetid: 574e326f-0520-4003-bdf1-62d92c3db457
author: MightyPen
ms.author: genemi
ms.openlocfilehash: 6e7f602107e828ee0bd985345ed5e641d6870558
ms.sourcegitcommit: 9348f79efbff8a6e88209bb5720bd016b2806346
ms.translationtype: MTE75
ms.contentlocale: fr-FR
ms.lasthandoff: 08/14/2019
ms.locfileid: "69027225"
---
# <a name="understanding-xa-transactions"></a>Présentation des transactions XA
[!INCLUDE[Driver_JDBC_Download](../../includes/driver_jdbc_download.md)]
Le [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] prend en charge les transactions distribuées facultatives Java Platform, Enterprise Edition/JDBC 2.0. Les connexions JDBC obtenues à partir de la classe [SQLServerXADataSource](../../connect/jdbc/reference/sqlserverxadatasource-class.md) peuvent participer aux environnements de traitement des transactions distribuées standard, tels que les serveurs d’applications Java Platform, Enterprise Edition (Java EE).
> [!WARNING]
> Microsoft JDBC Driver 4.2 pour SQL (et versions ultérieures) inclut de nouvelles options de délai d’attente pour la fonctionnalité existante de restauration automatique des transactions non préparées. Pour plus d’informations, consultez [Configuration des paramètres de délai d’attente côté serveur pour la restauration automatique des transactions](../../connect/jdbc/understanding-xa-transactions.md#BKMK_ServerSide) non préparées plus loin dans cette rubrique.
## <a name="remarks"></a>Notes
Les classes pour l'implémentation des transactions distribuées sont les suivantes :
| Classe | Implémentations | Description |
| -------------------------------------------------- | ------------------------------- | ------------------------------------------------- |
| com.microsoft.sqlserver.jdbc.SQLServerXADataSource | javax.sql.XADataSource | Fabrique de classe pour les connexions distribuées. |
| com.microsoft.sqlserver.jdbc.SQLServerXAResource | javax.transaction.xa.XAResource | Adaptateur de ressources pour le gestionnaire de transactions. |
> [!NOTE]
> Les connexions de transactions distribuées XA sont définies par défaut au niveau d'isolation Read Committed.
## <a name="guidelines-and-limitations-when-using-xa-transactions"></a>Recommandations et limitations relatives à l'utilisation de transactions XA
Les recommandations supplémentaires suivantes s'appliquent aux transactions fortement couplées :
- Lorsque vous utilisez des transactions XA avec Microsoft Distributed Transaction Coordinator (MS DTC), vous pouvez remarquer que la version actuelle de MS DTC ne prend pas en charge le comportement de branche XA fortement couplée. Par exemple, MS DTC a un mappage un-à-un entre un ID de transaction de branche XA (XID) et un ID de transaction MS DTC et le travail effectué par les branches XA couplées de manière lâche est isolé.
Le correctif logiciel disponible sur la page web [MSDTC et transactions fortement couplées](https://support.microsoft.com/kb/938653) permet la prise en charge des branches XA fortement couplées quand plusieurs branches XA avec le même ID de transaction globale (GTRID) sont mappées à un ID de transaction MS DTC unique. Cette prise en charge permet à plusieurs branches XA fortement couplées de voir les changements apportés à chacune d’elles dans le gestionnaire de ressources, par exemple [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
- Un indicateur [SSTRANSTIGHTLYCPLD](../../connect/jdbc/reference/sstranstightlycpld-field-sqlserverxaresource.md) permet aux applications d’utiliser les transactions XA fortement couplées qui ont des ID de transaction de branche XA (BQUAL) différents mais le même ID de transaction global (GTRID) et ID de format (FormatID). Pour pouvoir utiliser cette fonctionnalité, vous devez définir [SSTRANSTIGHTLYCPLD](../../connect/jdbc/reference/sstranstightlycpld-field-sqlserverxaresource.md) sur le paramètre flags de la méthode XAResource. Start:
```java
xaRes.start(xid, SQLServerXAResource.SSTRANSTIGHTLYCPLD);
```
## <a name="configuration-instructions"></a>Instructions de configuration
Les étapes suivantes sont requises si vous souhaitez utiliser des sources de données XA avec Microsoft Distributed Transaction Coordinator (MS DTC) pour manipuler des transactions distribuées.
> [!NOTE]
> Les composants de transaction distribuée JDBC sont inclus dans le répertoire xa de l'installation du pilote JDBC. Ces composants incluent les fichiers xa_install.sql et sqljdbc_xa.dll.
> [!NOTE]
> À compter de SQL Server 2019 public Preview CTP 2,0, les composants JDBC de transaction distribuée JDBC sont inclus dans le moteur de SQL Server et peuvent être activés ou désactivés avec une procédure stockée système.
> Pour permettre aux composants requis d’effectuer des transactions distribuées XA à l’aide du pilote JDBC, exécutez la procédure stockée suivante.
>
> EXEC sp_sqljdbc_xa_install
>
> Pour désactiver les composants précédemment installés, exécutez la procédure stockée suivante.
>
> EXEC sp_sqljdbc_xa_uninstall
### <a name="running-the-ms-dtc-service"></a>Exécution du service MS DTC
Le service MS DTC doit être marqué comme **Automatique** dans Service Manager afin de garantir son exécution quand le service [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] démarre. Pour activer MS DTC pour les transactions XA, vous devez procéder comme suit :
Sur Windows Vista et versions ultérieures :
1. Cliquez sur le bouton **Démarrer**, tapez **dcomcnfg** dans la zone **Rechercher**, puis appuyez sur Entrée pour ouvrir **Services de composants**. Vous pouvez également taper %windir%\system32\comexp.msc dans la zone **Rechercher** du menu Démarrer pour ouvrir **Services de composants**.
2. Développez Services de composants, Ordinateurs, Poste de travail, puis Distributed Transaction Coordinator.
3. Cliquez avec le bouton droit sur **DTC local**, puis sélectionnez **Propriétés**.
4. Dans la boîte de dialogue **Propriétés du DTC local**, cliquez sur l’onglet **Sécurité**.
5. Cochez la case **Activer les transactions XA**, puis cliquez sur **OK**. Cela entraîne le redémarrage du service MS DTC.
6. Cliquez à nouveau sur **OK** pour fermer la boîte de dialogue **Propriétés**, puis fermez **Services de composants**.
7. Arrêtez, puis redémarrez [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] afin de garantir sa synchronisation avec les modifications de MS DTC.
### <a name="configuring-the-jdbc-distributed-transaction-components"></a>Configuration des composants de transaction distribuée JDBC
Vous pouvez configurer les composants de transaction distribuée du pilote JDBC en suivant les étapes suivantes :
1. Copiez le nouveau fichier sqljdbc_xa.dll à partir du répertoire d’installation du pilote JDBC vers le répertoire Binn de chaque ordinateur [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] susceptible de participer à des transactions distribuées.
> [!NOTE]
> Si vous utilisez des transactions XA avec un [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 32 bits, utilisez le fichier sqljdbc_xa.dll dans le dossier x86, même si le [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] est installé sur un processeur x64. Si vous utilisez des transactions XA avec une version 64 bits de [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] sur un processeur x64, utilisez le fichier sqljdbc_xa.dll dans le dossier x64.
2. Exécutez le script de base de données xa_install.sql sur chaque instance de [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] susceptible de participer à des transactions distribuées. Ce script installe les procédures stockées étendues qui sont appelées par sqljdbc_xa.dll. Ces procédures stockées étendues implémentent la prise en charge des transactions distribuées et de XA pour [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)]. Vous devez exécuter ce script en tant qu’administrateur de l’instance [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
3. Pour autoriser un utilisateur spécifique à participer à des transactions distribuées avec le pilote JDBC, ajoutez-le au rôle SqlJDBCXAUser.
Vous ne pouvez configurer qu’une seule version à la fois de l’assembly sqljdbc_xa.dll sur chaque instance de [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Les applications devront peut-être utiliser des versions différentes du pilote JDBC pour se connecter à la même instance [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] par le biais de la connexion XA. Dans ce cas, sqljdbc_xa.dll, qui est livré avec le pilote JDBC le plus récent, doit être installé sur l’instance de [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
Il existe trois façons de vérifier la version actuellement installée de sqljdbc_xa.dll sur l’instance de [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] :
1. Ouvrez le répertoire LOG de l’ordinateur [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] qui doit participer aux transactions distribuées. Sélectionnez et ouvrez le fichier ERRORLOG [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Recherchez l'expression « Using 'SQLJDBC_XA.dll' version ... » dans le fichier ERRORLOG.
2. Ouvrez le répertoire Binn de l’ordinateur [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] qui doit participer aux transactions distribuées. Sélectionnez l’assembly sqljdbc_xa. dll.
- Sur Windows Vista et versions ultérieures : cliquez avec le bouton droit sur sqljdbc_xa.dll, puis sélectionnez Propriétés. Cliquez ensuite sur l’onglet **Détails**. Le champ **Version du fichier** indique la version de sqljdbc_xa.dll actuellement installée sur l’instance de [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
3. Définissez la fonctionnalité de journalisation comme indiqué dans l'exemple de code de la prochaine section. Recherchez l'expression « Server XA DLL version:... » dans le fichier journal de sortie.
### <a name="BKMK_ServerSide"></a> Configuration des paramètres du délai d’attente côté serveur pour la restauration automatique des transactions non préparées
> [!WARNING]
> Il s’agit d’une nouvelle option côté serveur proposée par Microsoft JDBC Driver 4.2 (et versions ultérieures) pour SQL Server. Pour obtenir le comportement mis à jour, assurez-vous que le fichier sqljdbc_xa.dll est mis à jour sur le serveur. Pour plus d’informations sur la définition des délais d’expiration côté client, voir [XAResource.setTransactionTimeout()](https://docs.oracle.com/javase/8/docs/api/javax/transaction/xa/XAResource.html).
Il existe deux paramètres du Registre (valeurs DWORD) pour contrôler le comportement du délai d'attente des transactions distribuées :
- **XADefaultTimeout** (en secondes): valeur de délai d’attente par défaut à utiliser lorsque l’utilisateur ne spécifie pas de délai d’attente. La valeur par défaut est 0.
- **XAMaxTimeout** (en secondes): valeur maximale du délai d’attente qu’un utilisateur peut définir. La valeur par défaut est 0.
Ces paramètres sont spécifiques de l'instance SQL Server et doivent être créés sous la clé de Registre suivante :
```bash
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL<version>.<instance_name>\XATimeout
```
> [!NOTE]
> Pour un serveur SQL Server 32 bits exécuté sur des ordinateurs 64 bits, les paramètres de Registre doivent être créés sous la clé suivante : `HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL<version>.<instance_name>\XATimeout`
Une valeur de délai d'expiration est définie au démarrage de chaque transaction ; une fois ce délai écoulé, la transaction est restaurée par le serveur SQL Server. Le délai d'attente est déterminé en fonction de ces paramètres de Registre et de ce que l'utilisateur a spécifié via XAResource.setTransactionTimeout(). Voici quelques exemples d'interprétation des valeurs de délai d'attente :
- `XADefaultTimeout = 0`, `XAMaxTimeout = 0`
Signifie qu'aucun délai d'attente par défaut ne sera utilisé et qu'aucun délai d'attente maximal ne sera appliqué sur les clients. Dans ce cas, les transactions auront un délai d'attente uniquement si le client en définit un à l'aide de XAResource.setTransactionTimeout.
- `XADefaultTimeout = 60`, `XAMaxTimeout = 0`
Signifie que toutes les transactions auront un délai d'attente de 60 secondes si le client n'en spécifie aucun. Si le client spécifie un délai d'attente, cette valeur sera alors utilisée. Aucune valeur de délai d'attente maximale n'est appliquée.
- `XADefaultTimeout = 30`, `XAMaxTimeout = 60`
Signifie que toutes les transactions auront un délai d'attente de 30 secondes si le client n'en spécifie aucun. Si le client spécifie un délai d’attente, ce dernier sera utilisé s’il est inférieur à 60 secondes (valeur maximale).
- `XADefaultTimeout = 0`, `XAMaxTimeout = 30`
Signifie que toutes les transactions auront un délai d'attente de 30 secondes (valeur maximale) si le client n'en spécifie aucun. Si le client spécifie un délai d’attente, ce dernier sera utilisé s’il est inférieur à 30 secondes (valeur maximale).
### <a name="upgrading-sqljdbc_xadll"></a>Mise à niveau du fichier sqljdbc_xa.dll
Lorsque vous installez une nouvelle version du pilote JDBC, vous devez utiliser le fichier sqljdbc_xa.dll de la nouvelle version pour mettre à niveau le fichier sqljdbc_xa.dll sur le serveur.
> [!IMPORTANT]
> Vous devez mettre à niveau le fichier sqljdbc_xa.dll dans une fenêtre de maintenance ou quand aucune transaction MS DTC n’est en cours.
1. Déchargez sqljdbc_xa. dll [!INCLUDE[tsql](../../includes/tsql-md.md)] à l’aide de la commande **DBCC sqljdbc_xa (Free)** .
2. Copiez le nouveau fichier sqljdbc_xa.dll à partir du répertoire d’installation du pilote JDBC vers le répertoire Binn de chaque ordinateur [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] susceptible de participer à des transactions distribuées.
La nouvelle DLL sera chargée à l'appel d'une procédure étendue dans sqljdbc_xa.dll. Il n’est pas nécessaire de redémarrer [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] pour charger les nouvelles définitions.
### <a name="configuring-the-user-defined-roles"></a>Configuration des rôles définis par l'utilisateur
Pour autoriser un utilisateur spécifique à participer à des transactions distribuées avec le pilote JDBC, ajoutez-le au rôle SqlJDBCXAUser. Par exemple, utilisez le code [!INCLUDE[tsql](../../includes/tsql-md.md)] suivant pour ajouter un utilisateur appelé « shelby » (« shelby » est un nom d’utilisateur standard d’ouverture de session SQL) au rôle SqlJDBCXAUser :
```sql
USE master
GO
EXEC sp_grantdbaccess 'shelby', 'shelby'
GO
EXEC sp_addrolemember [SqlJDBCXAUser], 'shelby'
```
Les rôles définis par l'utilisateur SQL sont définis par base de données. Pour des raisons de sécurité, si vous souhaitez créer votre propre rôle, vous devrez le définir dans chaque base de données et ajouter les utilisateurs base de données par base de données. Le rôle SqlJDBCXAUser est strictement défini dans la base de données MASTER, car il est utilisé pour accorder l'accès aux procédures stockées étendues SQL JDBC s’y trouvant. Vous devrez d'abord accorder à l'utilisateur un accès à la base de données MASTER, puis un accès au rôle SqlJDBCXAUser en étant connecté à la base de données MASTER.
## <a name="example"></a>Exemple
```java
import java.net.Inet4Address;
import java.sql.*;
import java.util.Random;
import javax.sql.XAConnection;
import javax.transaction.xa.*;
import com.microsoft.sqlserver.jdbc.*;
public class testXA {
public static void main(String[] args) throws Exception {
// Create variables for the connection string.
String prefix = "jdbc:sqlserver://";
String serverName = "localhost";
int portNumber = 1433;
String databaseName = "AdventureWorks";
String user = "UserName";
String password = "*****";
String connectionUrl = prefix + serverName + ":" + portNumber + ";databaseName=" + databaseName + ";user="
+ user + ";password=" + password;
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
try (Connection con = DriverManager.getConnection(connectionUrl); Statement stmt = con.createStatement()) {
stmt.executeUpdate("CREATE TABLE XAMin (f1 int, f2 varchar(max))");
}
// Create the XA data source and XA ready connection.
SQLServerXADataSource ds = new SQLServerXADataSource();
ds.setUser(user);
ds.setPassword(password);
ds.setServerName(serverName);
ds.setPortNumber(portNumber);
ds.setDatabaseName(databaseName);
XAConnection xaCon = ds.getXAConnection();
try (Connection con = xaCon.getConnection()) {
// Get a unique Xid object for testing.
XAResource xaRes = null;
Xid xid = null;
xid = XidImpl.getUniqueXid(1);
// Get the XAResource object and set the timeout value.
xaRes = xaCon.getXAResource();
xaRes.setTransactionTimeout(0);
// Perform the XA transaction.
System.out.println("Write -> xid = " + xid.toString());
xaRes.start(xid, XAResource.TMNOFLAGS);
PreparedStatement pstmt = con.prepareStatement("INSERT INTO XAMin (f1,f2) VALUES (?, ?)");
pstmt.setInt(1, 1);
pstmt.setString(2, xid.toString());
pstmt.executeUpdate();
// Commit the transaction.
xaRes.end(xid, XAResource.TMSUCCESS);
xaRes.commit(xid, true);
}
xaCon.close();
// Open a new connection and read back the record to verify that it worked.
try (Connection con = DriverManager.getConnection(connectionUrl); Statement stmt = con.createStatement();
ResultSet rs = stmt.executeQuery("SELECT * FROM XAMin")) {
rs.next();
System.out.println("Read -> xid = " + rs.getString(2));
stmt.executeUpdate("DROP TABLE XAMin");
}
}
}
class XidImpl implements Xid {
public int formatId;
public byte[] gtrid;
public byte[] bqual;
public byte[] getGlobalTransactionId() {
return gtrid;
}
public byte[] getBranchQualifier() {
return bqual;
}
public int getFormatId() {
return formatId;
}
XidImpl(int formatId, byte[] gtrid, byte[] bqual) {
this.formatId = formatId;
this.gtrid = gtrid;
this.bqual = bqual;
}
public String toString() {
int hexVal;
StringBuffer sb = new StringBuffer(512);
sb.append("formatId=" + formatId);
sb.append(" gtrid(" + gtrid.length + ")={0x");
for (int i = 0; i < gtrid.length; i++) {
hexVal = gtrid[i] & 0xFF;
if (hexVal < 0x10)
sb.append("0" + Integer.toHexString(gtrid[i] & 0xFF));
else
sb.append(Integer.toHexString(gtrid[i] & 0xFF));
}
sb.append("} bqual(" + bqual.length + ")={0x");
for (int i = 0; i < bqual.length; i++) {
hexVal = bqual[i] & 0xFF;
if (hexVal < 0x10)
sb.append("0" + Integer.toHexString(bqual[i] & 0xFF));
else
sb.append(Integer.toHexString(bqual[i] & 0xFF));
}
sb.append("}");
return sb.toString();
}
// Returns a globally unique transaction id.
static byte[] localIP = null;
static int txnUniqueID = 0;
static Xid getUniqueXid(int tid) {
Random rnd = new Random(System.currentTimeMillis());
txnUniqueID++;
int txnUID = txnUniqueID;
int tidID = tid;
int randID = rnd.nextInt();
byte[] gtrid = new byte[64];
byte[] bqual = new byte[64];
if (null == localIP) {
try {
localIP = Inet4Address.getLocalHost().getAddress();
} catch (Exception ex) {
localIP = new byte[] {0x01, 0x02, 0x03, 0x04};
}
}
System.arraycopy(localIP, 0, gtrid, 0, 4);
System.arraycopy(localIP, 0, bqual, 0, 4);
// Bytes 4 -> 7 - unique transaction id.
// Bytes 8 ->11 - thread id.
// Bytes 12->15 - random number generated by using seed from current time in milliseconds.
for (int i = 0; i <= 3; i++) {
gtrid[i + 4] = (byte) (txnUID % 0x100);
bqual[i + 4] = (byte) (txnUID % 0x100);
txnUID >>= 8;
gtrid[i + 8] = (byte) (tidID % 0x100);
bqual[i + 8] = (byte) (tidID % 0x100);
tidID >>= 8;
gtrid[i + 12] = (byte) (randID % 0x100);
bqual[i + 12] = (byte) (randID % 0x100);
randID >>= 8;
}
return new XidImpl(0x1234, gtrid, bqual);
}
}
```
## <a name="see-also"></a>Voir aussi
[Réalisation de transactions avec le pilote JDBC](../../connect/jdbc/performing-transactions-with-the-jdbc-driver.md)
| 61.016997 | 604 | 0.711454 | fra_Latn | 0.906933 |
87df3487691d0af91986552ed2ddd202fa559488 | 275 | md | Markdown | .github/PULL_REQUEST_TEMPLATE.md | irozzo-1A/installer | cd8e06359cdd149cedd10c615471f4b308bf02e3 | [
"Apache-2.0"
] | null | null | null | .github/PULL_REQUEST_TEMPLATE.md | irozzo-1A/installer | cd8e06359cdd149cedd10c615471f4b308bf02e3 | [
"Apache-2.0"
] | null | null | null | .github/PULL_REQUEST_TEMPLATE.md | irozzo-1A/installer | cd8e06359cdd149cedd10c615471f4b308bf02e3 | [
"Apache-2.0"
] | 1 | 2020-01-23T09:40:19.000Z | 2020-01-23T09:40:19.000Z | Before creating your PR, please make sure to add the appropriate GitHub label; i.e. `run-smoke-tests`. For more details see
[tests/README.md](../tests/README.md).
(In case you don't have permissions to add labels, please ask [a](../OWNERS) [maintainer](../OWNERS_ALIASES).)
| 55 | 123 | 0.730909 | eng_Latn | 0.954247 |
87df3d45437a6c2bd38ce63253fd397c1ca7a1d3 | 3,080 | md | Markdown | README.md | npmdoc/node-npmdoc-verbal-expressions | 7ed0a36ed2a05554d3f3b65d16b723298e0144c1 | [
"MIT"
] | null | null | null | README.md | npmdoc/node-npmdoc-verbal-expressions | 7ed0a36ed2a05554d3f3b65d16b723298e0144c1 | [
"MIT"
] | null | null | null | README.md | npmdoc/node-npmdoc-verbal-expressions | 7ed0a36ed2a05554d3f3b65d16b723298e0144c1 | [
"MIT"
] | null | null | null | # npmdoc-verbal-expressions
#### api documentation for [verbal-expressions (v0.3.0)](https://github.com/VerbalExpressions/JSVerbalExpressions) [](https://www.npmjs.org/package/npmdoc-verbal-expressions) [](https://travis-ci.org/npmdoc/node-npmdoc-verbal-expressions)
#### JavaScript Regular expressions made easy
[](https://www.npmjs.com/package/verbal-expressions)
- [https://npmdoc.github.io/node-npmdoc-verbal-expressions/build/apidoc.html](https://npmdoc.github.io/node-npmdoc-verbal-expressions/build/apidoc.html)
[](https://npmdoc.github.io/node-npmdoc-verbal-expressions/build/apidoc.html)
# package.json
```json
{
"bugs": {
"url": "https://github.com/VerbalExpressions/JSVerbalExpressions/issues"
},
"dependencies": {},
"description": "JavaScript Regular expressions made easy",
"devDependencies": {
"eslint": "^2.5.1",
"eslint-config-airbnb": "^6.2.0",
"grunt": "^0.4.2",
"grunt-cli": "^1.2.0",
"grunt-contrib-copy": "^1.0.0",
"grunt-contrib-qunit": "^1.0.1",
"grunt-contrib-uglify": "^1.0.1",
"grunt-eslint": "^18.0.0",
"grunt-jsdoc": "^1.1.0",
"grunt-sourcemap-localize": "^0.1.0"
},
"directories": {},
"dist": {
"shasum": "492447babfe44dd89802633c4518052617d527b2",
"tarball": "https://registry.npmjs.org/verbal-expressions/-/verbal-expressions-0.3.0.tgz"
},
"engines": {
"node": ">= 0.8.0"
},
"gitHead": "4ca6a51c72a1ca6409445c519321f7af16f7d436",
"homepage": "https://github.com/VerbalExpressions/JSVerbalExpressions",
"keywords": [
"regular expressions",
"regex"
],
"license": "MIT",
"main": "VerbalExpressions.js",
"maintainers": [
{
"name": "verbalexpressions"
}
],
"name": "verbal-expressions",
"optionalDependencies": {},
"repository": {
"type": "git",
"url": "git://github.com/VerbalExpressions/JSVerbalExpressions.git"
},
"scripts": {
"build": "grunt build",
"docs": "grunt docs",
"grunt": "grunt",
"test": "grunt test",
"test:verbose": "grunt test --verbose"
},
"types": "./typings/verbalexpression.d.ts",
"version": "0.3.0",
"bin": {}
}
```
# misc
- this document was created with [utility2](https://github.com/kaizhu256/node-utility2)
| 36.235294 | 430 | 0.648377 | kor_Hang | 0.108423 |
87df82946a0c8d29c8057fc7ae0c7d4a5ee51044 | 567 | md | Markdown | src/pages/post/nieuw-nummer-en-videoclip-van-brutus-cemetery.md | vanhoofmaarten/netlify-cms-tutorial | 2482dcbb138ad88fc075ca7cc9b63708e8aa4365 | [
"MIT"
] | null | null | null | src/pages/post/nieuw-nummer-en-videoclip-van-brutus-cemetery.md | vanhoofmaarten/netlify-cms-tutorial | 2482dcbb138ad88fc075ca7cc9b63708e8aa4365 | [
"MIT"
] | 10 | 2019-01-13T19:56:05.000Z | 2019-03-01T14:05:09.000Z | src/pages/post/nieuw-nummer-en-videoclip-van-brutus-cemetery.md | rockxxl/rockxxl | 2482dcbb138ad88fc075ca7cc9b63708e8aa4365 | [
"MIT"
] | null | null | null | ---
title: 'Nieuw nummer en videoclip van Brutus: Cemetery'
thumbnail: 'https://res.cloudinary.com/rockxxl/image/upload/v1551262590/brutus_2019.jpg'
date: 2019-02-27T10:15:02.304Z
category: Nieuws
author: Seppe Van Ael
---
Op 29 maart komt het nieuwe album van post-rock band Brutus uit. Deze Leuvense band kwam alvast aanzetten met een tweede single: Cemetery.
<iframe width="560" height="315" src="https://www.youtube.com/embed/dtj9xx-kXXY" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
| 51.545455 | 202 | 0.776014 | nld_Latn | 0.842176 |
87dfcc566b075113b5a4f0569d8a703284a53e53 | 9,594 | md | Markdown | docs/source/guide/install_enterprise.md | Queuebee2/label-studio | 0c237b9318599339823e5f19ac30020796f20997 | [
"Apache-2.0"
] | 1 | 2021-06-23T19:47:46.000Z | 2021-06-23T19:47:46.000Z | docs/source/guide/install_enterprise.md | suryatmodulus/label-studio | 7c9e5777b7c0fe510b8585ae4c42b74a46929f73 | [
"Apache-2.0"
] | null | null | null | docs/source/guide/install_enterprise.md | suryatmodulus/label-studio | 7c9e5777b7c0fe510b8585ae4c42b74a46929f73 | [
"Apache-2.0"
] | 1 | 2021-09-15T08:22:13.000Z | 2021-09-15T08:22:13.000Z | ---
title: Install Label Studio Enterprise on-premises using Docker
badge: <i class='ent'/></i>
type: guide
order: 201
meta_title: Install Label Studio Enterprise on-premises using Docker
meta_description: Install, back up, and upgrade Label Studio Enterprise with Docker to create machine learning and data science projects on-premises.
---
> Beta documentation: Label Studio Enterprise v2.0.0 is currently in Beta. As a result, this documentation might not reflect the current functionality of the product.
Install Label Studio Enterprise on-premises if you need to meet strong privacy regulations, legal requirements, or want to manage a custom installation on your own infrastructure using Docker or public cloud. To deploy Label Studio Enterprise on Amazon AWS in a Virtual Private Cloud (VPC), see [Install Label Studio Enterprise on AWS Private Cloud](install_enterprise_vpc.html).
You can run Label Studio Enterprise in an airgapped environment, and no data leaves your infrastructure. See [Secure Label Studio](security.html) for more details about security and hardening for Label Studio Enterprise.
<div class="enterprise"><p>
To install Label Studio Community Edition, see <a href="install.html">Install and Upgrade Label Studio</a>. This page is specific to the Enterprise version of Label Studio.
</p></div>
<!-- md deploy.md -->
## Install Label Studio Enterprise using Docker
1. Pull the latest image
2. Add the license file
3. Start using Docker. To start the server in development mode, start using Docker Compose.
### Prerequisites
Make sure you have an authorization token to retrieve Docker images and a current license file. If you are a Label Studio Enterprise customer and do not have access, [contact us](mailto:hello@heartex.ai) to receive an authorization token and a copy of your license file.
### Pull the latest image
You must be authorized to use Label Studio Enterprise images.
1. Set up the Docker login to retrieve the latest Docker image:
```bash
docker login --username heartexlabs
```
When prompted to enter the password, enter the token here. If Login Succeeded, a `~/.docker/config.json` file is created with the authorization settings.
2. Pull the latest Label Studio Enterprise image:
```bash
docker pull heartexlabs/heartex:latest
```
> Note: In some cases, you might need to use `sudo` to log in or pull images.
### Add the license file
After you retrieve the latest Label Studio Enterprise image, add the license file. You can't start the Docker image without a license file.
1. Create a working directory called `heartex` and place the license file in it.
```bash
mkdir -p heartex
cd heartex
```
2. Move the license file, `license.txt`, to the `heartex` directory.
### Start using Docker
To run Label Studio Enterprise in production, start it using Docker. This configuration allows you to link Label Studio with external databases and services.
1. Create a file, `heartex/env.list` with the required environmental variables:
```
# The main server URL (must be a full path like protocol://host:port)
HEARTEX_HOSTNAME=http://localhost:8080
# Auxiliary hostname URL: some platform functionality requires URIs generation with specified hostname,
# in case HEARTEX_HOSTNAME is not accessible from server side, use this variable to specify server host
HEARTEX_INTERNAL_HOSTNAME=
# PostgreSQL database name
POSTGRE_NAME=postgres
# PostgreSQL database user
POSTGRE_USER=postgres
# PostgreSQL database password
POSTGRE_PASSWORD=
# PostgreSQL database host
POSTGRE_HOST=db
# PostgreSQL database port
POSTGRE_PORT=5432
# PostgreSQL SSL mode
POSTGRE_SSL_MODE=require
# Specify Postgre SSL certificate
POSTGRE_SSLROOTCERT=postgre-ca-bundle.pem
# Redis location e.g. redis://[:password]@localhost:6379/1
REDIS_LOCATION=localhost:6379
# Redis database
REDIS_DB=1
# Redis password
REDIS_PASSWORD=12345
# Redis socket timeout
REDIS_SOCKET_TIMEOUT=3600
# Use Redis SSL connection
REDIS_SSL=1
# Require certificate
REDIS_SSL_CERTS_REQS=required
# Specify Redis SSL certificate
REDIS_SSL_CA_CERTS=redis-ca-bundle.pem
```
2. After you set all the environment variables, run Docker exposing port 8080:
```bash
docker run -d \
-p 8080:8080 \
--env-file env.list \
-v `pwd`/license.txt:/heartex/web/htx/settings/license_docker.txt \
-v `pwd`/logs:/var/log/heartex \
-v `pwd`/postgre-ca-bundle.pem:/etc/ssl/certs/postgre-ca-bundle.pem \
-v `pwd`/redis-ca-bundle.pem:/etc/ssl/certs/redis-ca-bundle.pem \
--name heartex \
heartexlabs/heartex:latest
```
> Note: If you expose port 80, you must start Docker with `sudo`.
### Start using Docker Compose
To run Label Studio Enterprise in development mode, start Label Studio using Docker Compose and local PostgreSQL and Redis servers to store data and configurations.
> Follow these instructions only if you plan to use Label Studio Enterprise in development mode. Otherwise, see [Start Using Docker](#Start-using-Docker) on this page.
#### Prerequisites
Make sure [Docker Compose](https://docs.docker.com/compose/install/) is installed on your system.
#### Start Label Studio Enterprise in development mode
1. Create a configuration file `heartex/config.yml` with the following content:
```yaml
version: '3'
services:
db:
image: postgres:11.5
hostname: db
restart: always
environment:
- POSTGRES_HOST_AUTH_METHOD=trust
volumes:
- ./postgres-data:/var/lib/postgresql/data
- ./logs:/var/log/heartex
ports:
- 5432:5432
heartex:
image: heartexlabs/heartex:latest
container_name: heartex
volumes:
- ./license.txt:/heartex/web/htx/settings/license_docker.txt
environment:
- HEARTEX_HOSTNAME=http://localhost:8080
- POSTGRE_NAME=postgres
- POSTGRE_USER=postgres
- POSTGRE_PASSWORD=
- POSTGRE_PORT=5432
- POSTGRE_HOST=db
- REDIS_LOCATION=redis:6379
command: ["./deploy/wait-for-postgres.sh", "db", "supervisord"]
ports:
- 8080:8080
depends_on:
- redis
links:
- db
- redis
redis:
image: redis:5.0.6-alpine
hostname: redis
volumes:
- "./redis-data:/data"
ports:
- 6379:6379
```
If you have existing services running on ports 5432, 6379, or 8080, update the `config.yml` file to use different ports.
2. Start all servers using docker-compose:
```bash
docker-compose -f config.yml up
```
3. Open [http://localhost:8080](http://localhost:8080) in a browser and start using Label Studio Enterprise in development mode.
#### Data persistence
When the Label Studio Enterprise server runs with docker-compose, all essential data is stored inside the container. The following local file storage directories are linked to the container volumes to make sure data persists:
- `./postgres-data` contains PostgreSQL database
- `./redis-data` contains Redis dumps
The integrity of these folders ensures that your data is not lost even if you completely stop and remove all running containers and images. The `./postgres-data` files are specific to the PostgreSQL version. The current supported PostgreSQL version is 11.5.
## Update Label Studio Enterprise
1. [Back up your existing container](#Back-up-Label-Studio-Enterprise).
2. Pull the latest image
3. Update the container
### Get the Docker image version
To check the version of the Label Studio Enterprise Docker image, run [`docker ps`](https://docs.docker.com/engine/reference/commandline/ps/) on the host.
Run the following command as root or using `sudo` and review the output:
```bash
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b1dd57a685fb heartexlabs/heartex:latest "./deploy/start.sh" 36 minutes ago Up 36 minutes 0.0.0.0:8080->8000/tcp heartex
```
The image column displays the Docker image and version number. The image `heartexlabs/heartex:latest` is using the version `latest`.
### Back up Label Studio Enterprise
Back up your Label Studio Enterprise Docker container before you upgrade your version and for disaster recovery purposes.
1. From the command line, run Docker stop to stop the currently running container with Label Studio Enterprise:
```bash
docker stop heartex
```
2. Rename the existing container to avoid name conflicts when updating to the latest version:
```bash
docker rename heartex heartex-backup
```
You can then treat the `heartex-backup` image as a backup.
### Pull a new image
After backing up your existing container, pull the latest image of Label Studio Enterprise from the Docker registry.
```bash
docker pull heartexlabs/heartex:latest
```
### Update the container
After you pull the latest image, update your Label Studio Enterprise container:
```bash
docker run -d \
-p $EXPOSE_PORT:8080 \
-v `pwd`/license.txt:/heartex/web/htx/settings/license_docker.txt \
-v `pwd`/logs:/var/log/heartex \
-v `pwd`/postgre-ca-bundle.pem:/etc/ssl/certs/postgre-ca-bundle.pem \
-v `pwd`/redis-ca-bundle.pem:/etc/ssl/certs/redis-ca-bundle.pem \
--name heartex \
heartexlabs/heartex:latest
```
### Restore from a backed up container
If you decide to roll back to the previously backed up version of Label Studio Enterprise, stop and remove the new container and replace it with the backup.
1. From the command line, stop the latest running container and remove it:
```bash
docker stop heartex && docker rm heartex
```
2. Rename the backup container:
```bash
docker rename heartex-backup heartex
```
3. Start the backup container:
```bash
docker start heartex
``` | 35.142857 | 380 | 0.750156 | eng_Latn | 0.892032 |
87dff797ed8a12caaa2acf4026934452072e74c5 | 409 | md | Markdown | README.md | yu-meng420/shop | b2bf2b6a6c4f0fdff5b3c4f490e0f8fbbfbc06ad | [
"Apache-2.0"
] | null | null | null | README.md | yu-meng420/shop | b2bf2b6a6c4f0fdff5b3c4f490e0f8fbbfbc06ad | [
"Apache-2.0"
] | 8 | 2020-07-19T13:36:56.000Z | 2022-02-26T23:39:27.000Z | README.md | yu-meng420/shop | b2bf2b6a6c4f0fdff5b3c4f490e0f8fbbfbc06ad | [
"Apache-2.0"
] | null | null | null | # 项目名称--小马哥商城（移动端）
### 项目负责人
于萌
### git地址
git@github.com:yu-meng420/shop.git
### 开发排期
| 项目名称 | 模块名称 | 开发排期 | 自测排期 |
| ---- | ----- | ---- | ---- |
| 首页 | 顶部和底部 | 6h | 4h |
| | 内容模块 | 8h | 6h |
| | 导航栏实现 | 2h | 1h |
| 购物车 | 购物车 | 2h | 1h |
| | 购物车列表 | 4h | 3h |
| | 轮播图 | 2h | 1h |
| | 商品的信息 | 2h | 1h |
| | 内容模块 | 8h | 7h | | 17.041667 | 36 | 0.349633 | yue_Hant | 0.240589 |
87e0130653bbae682c8e49c62ef61aecc068def1 | 74,282 | md | Markdown | articles/purview/supported-classifications.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/purview/supported-classifications.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/purview/supported-classifications.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: サポートされている分類の一覧
description: このページでは、Azure Purview でサポートされているシステム分類の一覧を示します。
author: anmuk601
ms.author: anmuk
ms.service: purview
ms.subservice: purview-data-catalog
ms.topic: reference
ms.date: 02/05/2021
ms.openlocfilehash: 60aede65f8217d46844398d0199ff7edca7f36a9
ms.sourcegitcommit: 772eb9c6684dd4864e0ba507945a83e48b8c16f0
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 03/20/2021
ms.locfileid: "103200796"
---
# <a name="supported-classifications-in-azure-purview"></a>Azure Purview でサポートされている分類
この記事では、Azure Purview (プレビュー) でサポートおよび定義されているシステム分類の一覧を示します。
- **[Distinct match threshold]\(個別の一致のしきい値\)** : スキャナーがデータ パターンを実行する前に、列に含まれている必要がある個別のデータ値の合計数です。 Microsoft のシステム分類ルールでは、分類の対象とする各列に、少なくとも 8 つの個別の値が必要です。 システムでは、この値を使用して、スキャナーが正確に分類するのに十分なデータが列に含まれていることを確認する必要があります。 たとえば、すべて値 1 が含まれている複数の行を含む列は分類されません。 1 つの行に値が含まれ、残りの行に null 値が含まれている列の場合も分類されません。 複数のパターンを指定すると、この値がそれぞれに適用されます。
- **[Minimum match threshold]\(最小の一致のしきい値\)** : これは、分類を適用するためにスキャナーによって検出される必要がある列の、データ値の最小一致率です。 システム分類の値は 60% に設定されています。
## <a name="defined-system-classifications"></a>定義済みのシステム分類
Azure Purview では、[RegEx](https://wikipedia.org/wiki/Regular_expression) と[ブルーム フィルター](https://wikipedia.org/wiki/Bloom_filter)でデータが分類されます。 次の一覧では、Azure Purview で定義されているシステム分類の形式、パターン、キーワードについて説明します。
各分類名には、MICROSOFT がプレフィックスとして付けられます。
## <a name="bloom-filter-classifications"></a>ブルーム フィルターの分類
## <a name="city-country-and-place"></a>市区町村、国、場所
市区町村、国、場所のフィルターは、データの準備に使用できる最適なデータセットを使用して準備されています。
## <a name="person"></a>Person
Person ブルーム フィルターは、以下の 2 つのデータセットを使用して準備されています。
- [2010 年の米国国勢調査の姓に関するデータ (162-K エントリ)](https://www.census.gov/topics/population/genealogy/data/2010_surnames.html)
- [一般的な赤ちゃんの名前 (SSN から)、1880 年から 2019 年のすべての年を使用 (98-K エントリ)](https://www.ssa.gov/oact/babynames/limits.html)
## <a name="regex-classifications"></a>RegEx の分類
## <a name="aba-routing"></a>ABA ルーティング
### <a name="format"></a>Format
9 桁の数字 (書式設定されたパターンまたは書式設定されていないパターン)
### <a name="pattern"></a>Pattern
書式設定済み:
- 0、1、2、3、6、7、または 8 で始まる 4 桁の数字
- 1 つのハイフン
- 4 桁の数字
- 1 つのハイフン
- 1 桁の数字
書式設定なし: 0、1、2、3、6、7、または 8 で始まる 9 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_aba_routing"></a>Keyword_aba_routing
```
amba number
aba #
aba
abarouting#
abaroutingnumber
americanbankassociationrouting#
americanbankassociationroutingnumber
bank routing#
bankroutingnumber
routing #
routing no
routing number
routing transit number
routing#
RTN
```
## <a name="argentina-national-identity-dni-number"></a>アルゼンチンの国民 ID (DNI) 番号
### <a name="format"></a>Format
ピリオドの有無にかかわらず 8 桁
### <a name="pattern"></a>Pattern
8 桁の数字:
- 2 桁の数字
- 1 つの省略可能なピリオド
- 3 桁の数字
- 1 つの省略可能なピリオド
- 3 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_argentina_national_id"></a>Keyword_argentina_national_id
```
Argentina National Identity number
cedula
cédula
dni
documento nacional de identidad
documento número
documento numero
registro nacional de las personas
rnp
```
## <a name="australia-bank-account-number"></a>オーストラリアの銀行口座番号
### <a name="format"></a>Format
銀行の州支店番号の有無にかかわらず、6 ～ 10 桁の数字
### <a name="pattern"></a>Pattern
口座番号は 6 ～ 10 桁の数字です。
オーストラリアの銀行の州支店番号:
- 3 桁の数字
- 1 つのハイフン
- 3 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_australia_bank_account_number"></a>Keyword_australia_bank_account_number
```
swift bank code
correspondent bank
base currency
usa account
holder address
bank address
information account
fund transfers
bank charges
bank details
banking information
full names
iaea
```
## <a name="australia-drivers-license-number"></a>オーストラリアの運転免許証番号
### <a name="format"></a>Format
9 桁の文字と数字
### <a name="pattern"></a>Pattern
9 桁の文字と数字:
- 2 桁の数字または文字 (大文字と小文字は区別されません)
- 2 桁の数字
- 5 桁の数字または文字 (大文字と小文字は区別されません)
OR
- 省略可能な 1 ～ 2 文字 (大文字と小文字は区別されません)
- 4 ～ 9 桁の数字
OR
- 9 桁の数字または文字 (大文字と小文字は区別されません)
### <a name="keywords"></a>キーワード
#### <a name="keyword_australia_drivers_license_number"></a>Keyword_australia_drivers_license_number
```
international driving permits
australian automobile association
international driving permit
DriverLicence
DriverLicences
Driver Lic
Driver License
Driver Licenses
DriversLic
DriversLicence
DriversLicences
Drivers Lic
Drivers Lics
Drivers License
Drivers Licenses
Driver'Lic
Driver'Lics
Driver'License
Driver'Licenses
Driver' Lic
Driver' Lics
Driver' License
Driver' Licenses
Driver'sLic
Driver'sLics
Driver'sLicence
Driver'sLicences
Driver's Lic
Driver's Lics
Driver's License
Driver's Licenses
DriverLic#
DriverLics#
DriverLicence#
DriverLicences#
Driver Lic#
Driver Lics#
Driver License#
Driver Licenses#
DriversLic#
DriversLics#
DriversLicence#
DriversLicences#
Drivers Lic#
Drivers Lics#
Drivers License#
Drivers Licenses#
Driver'Lic#
Driver'Lics#
Driver'License#
Driver'Licenses#
Driver' Lic#
Driver' Lics#
Driver' License#
Driver' Licenses#
Driver'sLic#
Driver'sLics#
Driver'sLicence#
Driver'sLicences#
Driver's Lic#
Driver's Lics#
Driver's License#
Driver's Licenses#
```
#### <a name="keyword_australia_drivers_license_number_exclusions"></a>Keyword_australia_drivers_license_number_exclusions
```
aaa
DriverLicense
DriverLicenses
Driver License
Driver Licenses
DriversLicense
DriversLicenses
Drivers License
Drivers Licenses
Driver'License
Driver'Licenses
Driver' License
Driver' Licenses
Driver'sLicense
Driver'sLicenses
Driver's License
Driver's Licenses
DriverLicense#
DriverLicenses#
Driver License#
Driver Licenses#
DriversLicense#
DriversLicenses#
Drivers License#
Drivers Licenses#
Driver'License#
Driver'Licenses#
Driver' License#
Driver' Licenses#
Driver'sLicense#
Driver'sLicenses#
Driver's License#
Driver's Licenses#
```
## <a name="australian-medicare-number"></a>オーストラリア メディケア番号
### <a name="format"></a>Format
10 ～ 11 桁の数字
### <a name="pattern"></a>Pattern
10 ～ 11 桁の数字:
- 最初の桁は 2 ～ 6 の範囲です
- 9 桁目はチェック ディジットです
- 10 桁目は発行番号です
- 11 桁目 (省略可能) は個人番号です
### <a name="keywords"></a>キーワード
#### <a name="keyword_australia_medicare_number"></a>Keyword_Australia_Medicare_Number
```
bank account details
medicare payments
mortgage account
bank payments
information branch
credit card loan
department of human services
local service
medicare
```
## <a name="australia-passport-number"></a>オーストラリアのパスポート番号
### <a name="format"></a>Format
1 文字の後に 7 桁の数字
### <a name="pattern"></a>Pattern
1 文字 (大文字と小文字は区別されません) の後に 7 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_passport"></a>Keyword\_passport
```
Passport Number
Passport No
Passport #
Passport#
PassportID
Passport no
passport number
パスポート
パスポート番号
パスポートのNum
パスポート＃
Numéro de passeport
Passeport n °
Passeport Non
Passeport #
Passeport#
PasseportNon
Passeportn °
```
#### <a name="keyword_australia_passport_number"></a>Keyword\_australia\_passport\_number
```
passport
passport details
immigration and citizenship
commonwealth of australia
department of immigration
residential address
department of immigration and citizenship
visa
national identity card
passport number
travel document
issuing authority
```
## <a name="australia-tax-file-number"></a>オーストラリアの納税者番号
### <a name="format"></a>Format
8 ～ 9 桁の数字
### <a name="pattern"></a>Pattern
次のように、通常はスペースが含まれる 8 ～ 9 桁の数字
- 3 桁の数字
- 1 つの省略可能なスペース
- 3 桁の数字
- 1 つの省略可能なスペース
- 2 ～ 3 桁の数字 (最後の桁はチェック ディジット)
### <a name="keywords"></a>キーワード
#### <a name="keyword_australia_tax_file_number"></a>Keyword\_australia\_tax\_file\_number
```
australian business number
marginal tax rate
medicare levy
portfolio number
service veterans
withholding tax
individual tax return
tax file number
tfn
```
## <a name="belgium-national-number"></a>ベルギーの国民番号
### <a name="format"></a>Format
11 桁の数字と省略可能な区切り記号
### <a name="pattern"></a>Pattern
11 桁の数字と区切り記号:
- YY.MM.DD 形式の生年月日 (6 桁の数字と 2 つの省略可能なピリオド)
- 1 つの省略可能な区切り記号 (ドット、ダッシュ、スペース)
- 3 桁の連続する数字 (男性の場合は奇数、女性の場合は偶数)
- 1 つの省略可能な区切り記号 (ドット、ダッシュ、スペース)
- 2 桁のチェック ディジット
### <a name="keywords"></a>キーワード
#### <a name="keyword_belgium_national_number"></a>Keyword\_belgium\_national\_number
```
be lasting aantal
bnn#
bnn
carte d'identité
identifiant national
identifiantnational#
identificatie
identification
identifikation
identifikationsnummer
identifizierung
identité
identiteit
identiteitskaart
identity
inscription
national number
national register
national number#
national number
nif#
nif
numéro d'assuré
numéro de registre national
numéro de sécurité
numéro d'identification
numéro d'immatriculation
numéro national
numéronational#
personal ID number
personalausweis
personalidnumber#
registratie
registration
registrationsnumme
registrierung
social security number
ssn#
ssn
steuernummer
tax ID
tax identification no
tax identification number
tax no#
tax no
tax number
tax registration number
tax ID#
tax ID no#
tax ID number#
tax no#
tax number#
tax number
tin ID
tin no
tin#
```
## <a name="brazil-cpf-number"></a>ブラジルの CPF 番号
### <a name="format"></a>Format
1 桁のチェック ディジットが含まれた 11 桁の数字 (書式設定されている場合と書式設定されていない場合があります)
### <a name="pattern"></a>Pattern
書式設定済み:
- 3 桁の数字
- 1 つのピリオド
- 3 桁の数字
- 1 つのピリオド
- 3 桁の数字
- 1 つのハイフン
- 2 桁の数字 (チェック ディジット)
書式設定なし:
- 11 桁の数字 (最後の 2 桁はチェック ディジット)
### <a name="keywords"></a>キーワード
#### <a name="keyword_brazil_cpf"></a>Keyword\_brazil\_cpf
```
CPF
Identification
Registration
Revenue
Cadastro de Pessoas Físicas
Imposto
Identificação
Inscrição
Receita
```
## <a name="brazil-legal-entity-number-cnpj"></a>ブラジルの法人番号 (CNPJ)
### <a name="format"></a>Format
登録番号、分岐番号、チェック ディジット、区切り記号を含む 14 桁の数字
### <a name="pattern"></a>Pattern
14 桁の数字と区切り記号:
- 2 桁の数字
- 1 つのピリオド
- 3 桁の数字
- 1 つのピリオド
- 3 桁の数字 (最初の 8 桁は登録番号です)
- スラッシュ
- 4 桁の分岐番号
- 1 つのハイフン
- 2 桁の数字 (チェック ディジット)
### <a name="keywords"></a>キーワード
#### <a name="keyword_brazil_cnpj"></a>Keyword\_brazil\_cnpj
```
CNPJ
CNPJ/MF
CNPJ-MF
National Registry of Legal Entities
Taxpayers Registry
Legal entity
Legal entities
Registration Status
Business
Company
CNPJ
Cadastro Nacional da Pessoa Jurídica
Cadastro Geral de Contribuintes
CGC
Pessoa jurídica
Pessoas jurídicas
Situação cadastral
Inscrição
Empresa
```
## <a name="brazil-national-identification-card-rg"></a>ブラジルの国民識別カード (RG)
### <a name="format"></a>Format
:::no-loc text="Registro Geral (old format): Nine digits":::
:::no-loc text="Registro de Identidade (RIC) (new format): 11 digits":::
### <a name="pattern"></a>Pattern
:::no-loc text="Registro Geral (old format):":::
- 2 桁の数字
- 1 つのピリオド
- 3 桁の数字
- 1 つのピリオド
- 3 桁の数字
- 1 つのハイフン
- 1 桁の数字 (チェック ディジット)
:::no-loc text="Registro de Identidade (RIC) (new format):":::
- 10 桁
- 1 つのハイフン
- 1 桁の数字 (チェック ディジット)
### <a name="keywords"></a>キーワード
#### <a name="keyword_brazil_rg"></a>Keyword\_brazil\_rg
```
Cédula de identidade
identity card
national ID
número de rregistro
registro de Iidentidade
registro geral
RG (this keyword is case-sensitive)
RIC (this keyword is case-sensitive)
```
## <a name="canada-bank-account-number"></a>カナダの銀行口座番号
### <a name="format"></a>Format
7 桁または 12 桁の数字
### <a name="pattern"></a>Pattern
カナダの銀行口座番号は 7 桁または 12 桁です。
カナダの銀行口座番号は次のとおりです。
- 5 桁の数字
- 1 つのハイフン
- 3 桁の数字、または
- 1 桁のゼロ "0"
- 8 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_canada_bank_account_number"></a>Keyword\_canada\_bank\_account\_number
```
canada savings bonds
canada revenue agency
canadian financial institution
direct deposit form
canadian citizen
legal representative
notary public
commissioner for oaths
child care benefit
universal child care
canada child tax benefit
income tax benefit
harmonized sales tax
social insurance number
income tax refund
child tax benefit
territorial payments
institution number
deposit request
banking information
direct deposit
```
## <a name="canada-drivers-license-number"></a>カナダの運転免許証番号
### <a name="format"></a>Format
州によって異なる
### <a name="pattern"></a>Pattern
アルバータ、ブリティッシュコロンビア、マニトバ、ニュー ブランズウィック、ニューファンドランド/ラブラドル、ノバ スコシア、オンタリオ、プリンス エドワード島、ケベック、サスカチュワンをカバーするさまざまなパターン
### <a name="keywords"></a>キーワード
#### <a name="keyword_province_name_drivers_license_name"></a>Keyword\_[province\_name]\_drivers\_license\_name
- 州略称 (例: AB)
- 州名 (例: アルバータ)
#### <a name="keyword_canada_drivers_license"></a>Keyword\_canada\_drivers\_license
```
DL
DLS
CDL
CDLS
DriverLic
DriverLics
DriverLicense
DriverLicenses
DriverLicence
DriverLicences
Driver Lic
Driver Lics
Driver License
Driver Licenses
Driver License
Driver Licenses
DriversLic
DriversLics
DriversLicence
DriversLicences
DriversLicense
DriversLicenses
Drivers Lic
Drivers Lics
Drivers License
Drivers Licenses
Drivers License
Drivers Licenses
Driver'Lic
Driver'Lics
Driver'License
Driver'Licenses
Driver'License
Driver'Licenses
Driver' Lic
Driver' Lics
Driver' License
Driver' Licenses
Driver' License
Driver' Licenses
Driver'sLic
Driver'sLics
Driver'sLicense
Driver'sLicenses
Driver'sLicence
Driver'sLicences
Driver's Lic
Driver's Lics
Driver's License
Driver's Licenses
Driver's License
Driver's Licenses
Permis de Conduire
ID
IDs
ID card number
ID card numbers
ID card #
ID card #s
ID card
ID cards
ID card
identification number
identification numbers
identification #
identification #s
identification card
identification cards
identification
DL#
DLS#
CDL#
CDLS#
DriverLic#
DriverLics#
DriverLicense#
DriverLicenses#
DriverLicence#
DriverLicences#
Driver Lic#
Driver Lics#
Driver License#
Driver Licenses#
Driver License#
Driver Licenses#
DriversLic#
DriversLics#
DriversLicense#
DriversLicenses#
DriversLicence#
DriversLicences#
Drivers Lic#
Drivers Lics#
Drivers License#
Drivers Licenses#
Drivers License#
Drivers Licenses#
Driver'Lic#
Driver'Lics#
Driver'License#
Driver'Licenses#
Driver'License#
Driver'Licenses#
Driver' Lic#
Driver' Lics#
Driver' License#
Driver' Licenses#
Driver' License#
Driver' Licenses#
Driver'sLic#
Driver'sLics#
Driver'sLicense#
Driver'sLicenses#
Driver'sLicence#
Driver'sLicences#
Driver's Lic#
Driver's Lics#
Driver's License#
Driver's Licenses#
Driver's License#
Driver's Licenses#
Permis de Conduire#
ID#
IDs#
ID card#
ID cards#
ID card#
identification card#
identification cards#
identification#
```
## <a name="canada-health-service-number"></a>カナダの医療サービス番号
### <a name="format"></a>Format
10 桁
### <a name="pattern"></a>Pattern
10 桁
### <a name="keywords"></a>キーワード
#### <a name="keyword_canada_health_service_number"></a>Keyword\_canada\_health\_service\_number
```
personal health number
patient information
health services
specialty services
automobile accident
patient hospital
psychiatrist
workers compensation
disability
```
## <a name="canada-passport-number"></a>カナダのパスポート番号
### <a name="format"></a>Format
2 つの大文字の後に 6 桁の数字
### <a name="pattern"></a>Pattern
2 つの大文字の後に 6 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_canada_passport_number"></a>Keyword\_canada\_passport\_number
```
canadian citizenship
canadian passport
passport application
passport photos
certified translator
canadian citizens
processing times
renewal application
```
#### <a name="keyword_passport"></a>Keyword\_passport
```
Passport Number
Passport No
Passport #
Passport#
PassportID
Passport no
passport number
パスポート
パスポート番号
パスポートのNum
パスポート＃
Numéro de passeport
Passeport n °
Passeport Non
Passeport #
Passeport#
PasseportNon
Passeportn °
```
## <a name="canada-personal-health-identification-number-phin"></a>カナダの個人保健識別番号 (PHIN)
### <a name="format"></a>Format
9 桁の数字
### <a name="pattern"></a>Pattern
9 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_canada_phin"></a>Keyword\_canada\_phin
```
social insurance number
health information act
income tax information
manitoba health
health registration
prescription purchases
benefit eligibility
personal health
power of attorney
registration number
personal health number
practitioner referral
wellness professional
patient referral
health and wellness
```
#### <a name="keyword_canada_provinces"></a>Keyword\_canada\_provinces
```
Nunavut
Quebec
Northwest Territories
Ontario
British Columbia
Alberta
Saskatchewan
Manitoba
Yukon
Newfoundland and Labrador
New Brunswick
Nova Scotia
Prince Edward Island
Canada
```
## <a name="canada-social-insurance-number"></a>カナダの社会保険番号
### <a name="format"></a>Format
9 桁の数字 (省略可能なハイフンまたはスペースを含む)
### <a name="pattern"></a>Pattern
書式設定済み:
- 3 桁の数字
- 1 つのハイフンまたはスペース
- 3 桁の数字
- 1 つのハイフンまたはスペース
- 3 桁の数字
書式設定なし: 9 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_sin"></a>Keyword\_sin
```
sin
social insurance
numero d'assurance sociale
sins
ssn
ssns
social security
numero d'assurance social
national identification number
national ID
sin#
soc ins
social ins
```
#### <a name="keyword_sin_collaborative"></a>Keyword\_sin\_collaborative
```
driver's license
drivers license
driver's license
drivers license
DOB
Birthdate
Birthday
Date of Birth
```
## <a name="chile-identity-card-number"></a>チリの身分証明書番号
### <a name="format"></a>Format
7 ～ 8 桁の数字と区切り記号、1 つのチェック ディジットまたは文字
### <a name="pattern"></a>Pattern
7 ～ 8 桁の数字と区切り記号:
- 1 ～ 2 桁の数字
- 1 つの省略可能なピリオド
- 3 桁の数字
- 1 つの省略可能なピリオド
- 3 桁の数字
- 1 つのダッシュ
- チェック ディジットである 1 桁の数字または文字 (大文字と小文字は区別されません)
### <a name="keywords"></a>キーワード
#### <a name="keyword_chile_id_card"></a>Keyword\_chile\_id\_card
```
cédula de identidad
identificación
national identification
national identification number
national ID
número de identificación nacional
rol único nacional
rol único tributario
RUN
RUT
tarjeta de identificación
Rol Unico Nacional
Rol Unico Tributario
RUN#
RUT#
nationaluniqueroleID#
nacional identidad
número identificación
identidad número
numero identificacion
identidad numero
Chilean identity no.
Chilean identity number
Chilean identity #
Unique Tax Registry
Unique Tributary Role
Unique Tax Role
Unique Tributary Number
Unique National Number
Unique National Role
National unique role
Chile identity no.
Chile identity number
Chile identity #
```
## <a name="china-resident-identity-card-prc-number"></a>中国の在留身分証明書 (PRC) 番号
### <a name="format"></a>Format
18 桁の数字
### <a name="pattern"></a>Pattern
18 桁の数字:
- 6 桁の数字 (住所コード)
- YYYYMMDD 形式の 8 桁の数字 (生年月日)
- 3 桁の数字 (順序コード)
- 1 桁の数字 (チェック ディジット)
### <a name="keywords"></a>キーワード
#### <a name="keyword_china_resident_id"></a>Keyword\_china\_resident\_id
```
Resident Identity Card
PRC
National Identification Card
身份证
居民身份证
居民身份证
鉴定
身分證
居民身份證
鑑定
```
## <a name="credit-card-number"></a>クレジット カード番号
### <a name="format"></a>Format
14 ～ 16 桁の数字。書式設定されている場合と書式設定されていない場合があります (dddddddddddddddd)。また、Luhn テストに合格する必要があります。
### <a name="pattern"></a>Pattern
Visa、MasterCard、Discover Card、JCB、American Express、ギフト カード、ディナー カードなど、世界中のすべての主要ブランドのカードを検出する、複雑で堅牢なパターン。
### <a name="keywords"></a>キーワード
#### <a name="keyword_cc_verification"></a>Keyword\_cc\_verification
```
card verification
card identification number
cvn
cid
cvc2
cvv2
pin block
security code
security number
security no
issue number
issue no
cryptogramme
numéro de sécurité
numero de securite
kreditkartenprüfnummer
kreditkartenprufnummer
prüfziffer
prufziffer
sicherheits Kode
sicherheitscode
sicherheitsnummer
verfalldatum
codice di verifica
cod. sicurezza
cod sicurezza
n autorizzazione
código
codigo
cod. seg
cod seg
código de segurança
codigo de seguranca
codigo de segurança
código de seguranca
cód. segurança
cod. seguranca
cod. segurança
cód. seguranca
cód segurança
cod seguranca
cod segurança
cód seguranca
número de verificação
numero de verificacao
ablauf
gültig bis
gültigkeitsdatum
gultig bis
gultigkeitsdatum
scadenza
data scad
fecha de expiracion
fecha de venc
vencimiento
válido hasta
valido hasta
vto
data de expiração
data de expiracao
data em que expira
validade
valor
vencimento
transaction
transaction number
reference number
セキュリティコード
セキュリティ コード
セキュリティナンバー
セキュリティ ナンバー
セキュリティ番号
```
#### <a name="keyword_cc_name"></a>Keyword\_cc\_name
```
amex
Americans express
Americans express
americano espresso
Visa
Mastercard
master card
mc
master cards
master cards
diner's Club
diners club
diners club
discover
discover card
discover card
discover cards
JCB
BrandSmart
japanese card bureau
carte blanche
carteblanche
credit card
cc#
cc#:
expiration date
exp date
expiry date
date d'expiration
date d'exp
date expiration
bank card
bank card
card number
card num
card number
card numbers
card numbers
credit card
credit cards
credit cards
ccn
card holder
cardholder
card holders
cardholders
check card
check card
check cards
check cards
debit card
debit card
debit cards
debit cards
atm card
atmcard
atm cards
atmcards
enroute
en route
card type
Cardmember Acct
cardmember account
Card no
Corporate Card
Corporate cards
Type of card
card account number
card member account
Cardmember Acct.
card no.
card no
card number
carte bancaire
carte de crédit
carte de credit
numéro de carte
numero de carte
nº de la carte
nº de carte
kreditkarte
karte
karteninhaber
karteninhabers
kreditkarteninhaber
kreditkarteninstitut
kreditkartentyp
eigentümername
kartennr
kartennummer
kreditkartennummer
kreditkarten-nummer
carta di credito
carta credito
n. carta
n carta
nr. carta
nr carta
numero carta
numero della carta
numero di carta
tarjeta credito
tarjeta de credito
tarjeta crédito
tarjeta de crédito
tarjeta de atm
tarjeta atm
tarjeta debito
tarjeta de debito
tarjeta débito
tarjeta de débito
nº de tarjeta
no. de tarjeta
no de tarjeta
numero de tarjeta
número de tarjeta
tarjeta no
tarjetahabiente
cartão de crédito
cartão de credito
cartao de crédito
cartao de credito
cartão de débito
cartao de débito
cartão de debito
cartao de debito
débito automático
debito automatico
número do cartão
numero do cartão
número do cartao
numero do cartao
número de cartão
numero de cartão
número de cartao
numero de cartao
nº do cartão
nº do cartao
nº. do cartão
no do cartão
no do cartao
no. do cartão
no. do cartao
クレジットカード番号
クレジットカードナンバー
クレジットカード＃
クレジットカード
クレジット
クレカ
カード番号
カードナンバー
カード＃
アメックス
アメリカンエクスプレス
アメリカン エクスプレス
Visaカード
Visa カード
マスターカード
マスター カード
マスター
ダイナースクラブ
ダイナース クラブ
ダイナース
有効期限
期限
キャッシュカード
キャッシュ カード
カード名義人
カードの名義人
カードの名義
デビット カード
デビットカード
```
## <a name="croatia-drivers-license-number"></a>クロアチアの運転免許証番号
この機密情報タイプのエンティティは、EU の運転免許証番号の機密情報タイプでのみ使用できます。
### <a name="format"></a>Format
スペースと区切り記号のない 8 桁の数字
### <a name="pattern"></a>Pattern
8 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keywords_eu_drivers_license_number"></a>Keywords\_eu\_driver's\_license\_number
```
driverlic
driverlics
driver license
driver licenses
driverlicence
driverlicences
driver lic
driver lics
driver license
driver licenses
driver license
driver licenses
driverslic
driverslics
driverslicence
driverslicences
drivers license
drivers licenses
drivers lic
drivers lics
drivers license
drivers licenses
drivers license
drivers licenses
driver'lic
driver'lics
driver'license
driver'licenses
driver'license
driver'licenses
driver' lic
driver' lics
driver' license
driver' licenses
driver' license
driver' licenses
driver'slic
driver'slics
driver'license
driver'licenses
driver'license
driver'licenses
driver's lic
driver's lics
driver's license
driver's licenses
driver's license
driver's licenses
dl#
dls#
driverlic#
driverlics#
driver license#
driver licenses#
driverlicence#
driverlicences#
driver lic#
driver lics#
driver license#
driver licenses#
driver licenses#
driverslic#
driverslics#
drivers license#
drivers licenses#
driverslicence#
driverslicences#
drivers lic#
drivers lics#
drivers license#
drivers licenses#
drivers license#
drivers licenses#
driver'lic#
driver'lics#
driver'license#
driver'licenses#
driver'license#
driver'licenses#
driver' lic#
driver' lics#
driver' license#
driver' licenses#
driver' license#
driver' licenses#
driver'slic#
driver'slics#
driver'license#
driver'licenses#
driver'license#
driver'licenses#
driver's lic#
driver's lics#
driver's license#
driver's licenses#
driver's license#
driver's licenses#
driving license
driving license
dlno#
driv lic
driv licen
driv license
driv licenses
driv license
driv licenses
driver licen
drivers licen
driver's licen
driving lic
driving licen
driving licenses
driving license
driving licenses
driving permit
dl no
dlno
dl number
```
#### <a name="keywords_croatia_eu_drivers_license_number"></a>Keywords\_croatia\_eu\_driver's\_license\_number
```
vozačka dozvola
vozačke dozvole
```
## <a name="croatia-identity-card-number"></a>クロアチアの身分証明書番号
この機密情報タイプのエンティティは、EU の国民識別番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
9 桁の数字
### <a name="pattern"></a>Pattern
9 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_croatia_id_card"></a>Keyword\_croatia\_id\_card
```
majstorski broj građana
master citizen number
nacionalni identifikacijski broj
national identification number
oib#
oib
osobna iskaznica
osobni ID
osobni identifikacijski broj
personal identification number
porezni broj
porezni identifikacijski broj
tax ID
tax identification no
tax identification number
tax no#
tax no
tax number
tax registration number
tax ID#
tax ID no#
tax ID number#
tax no#
tax number#
tax number
tin ID
tin no
tin#
```
## <a name="croatia-personal-identification-oib-number"></a>クロアチアの個人識別 (OIB) 番号
### <a name="format"></a>Format
11 桁の数字
### <a name="pattern"></a>Pattern
11 桁の数字:
- 10 桁
- 最後の桁はチェック ディジットです
### <a name="keywords"></a>キーワード
#### <a name="keyword_croatia_oib_number"></a>Keyword\_croatia\_oib\_number
```
majstorski broj građana
master citizen number
nacionalni identifikacijski broj
national identification number
oib#
oib
osobna iskaznica
osobni ID
osobni identifikacijski broj
personal identification number
porezni broj
porezni identifikacijski broj
tax ID
tax identification no
tax identification number
tax no#
tax no
tax number
tax registration number
tax ID#
tax ID no#
tax Id number#
tax no#
tax number#
tax number
tin ID
tin no
tin#
```
## <a name="denmark-personal-identification-number"></a>デンマークの個人識別番号
### <a name="format"></a>Format
1 つのハイフンが含まれた 10 桁の数字
### <a name="pattern"></a>Pattern
10 桁の数字:
- DDMMYY 形式の 6 桁の数字 (生年月日)
- 1 つのハイフン
- 4 桁の数字 (最後の桁はチェック ディジット)
### <a name="keywords"></a>キーワード
#### <a name="keyword_denmark_id"></a>Keyword\_denmark\_id
```
centrale person register
civilt registreringssystem
cpr
cpr#
gesundheitskarte nummer
gesundheitsversicherungkarte nummer
health card
health insurance card number
health insurance number
identification number
identifikationsnummer
identifikationsnummer#
identity number
krankenkassennummer
national ID#
national number#
national number
personalidnumber#
personalidentityno#
personal ID number
personnummer
personnummer#
reisekrankenversicherungskartenummer
rejsesygesikringskort
ssn
ssn#
skat ID
skat kode
skat nummer
skattenummer
social security number
sundhedsforsikringskort
sundhedsforsikringsnummer
sundhedskort
sundhedskortnummer
sygesikring
sygesikringkortnummer
tax code
travel health insurance card
uniqueidentityno#
tax number
tax registration number
tax ID
tax identification number
tax ID#
tax number#
tax no
tax no#
tax number
tax identification no
tin#
tax ID no#
tax ID number#
tax no#
tin ID
tin no
cpr.nr
cprnr
cprnummer
personnr
person register
sygesikringsbevis
sygesikringsbevisnr
sygesikringsbevisnummer
sygesikringskort
sygesikringskortnr
sygesikringskortnummer
sygesikringsnr
sygesikringsnummer
```
## <a name="eu-debit-card-number"></a>EU デビット カード番号
### <a name="format"></a>Format
16 桁の数字
### <a name="pattern"></a>Pattern
複雑で堅牢なパターン
### <a name="keywords"></a>キーワード
#### <a name="keyword_eu_debit_card"></a>Keyword\_eu\_debit\_card
```
account number
card number
card no.
security number
cc#
```
#### <a name="keyword_card_terms_dict"></a>Keyword\_card\_terms\_dict
```
acct nbr
acct num
acct no
Americans express
Americans express
americano espresso
amex
atm card
atm cards
atm kaart
atmcard
atmcards
atmkaart
atmkaarten
ban contact
bank card
bankkaart
card holder
card holders
card num
card number
card numbers
card type
cardano numerico
cardholder
cardholders
card number
card numbers
carta bianca
carta credito
carta di credito
cartao de credito
cartao de crédito
cartao de debito
cartao de débito
carte bancaire
carte blanche
carte bleue
carte de credit
carte de crédit
carte di credito
carteblanche
cartão de credito
cartão de crédito
cartão de debito
cartão de débito
cb
ccn
check card
check cards
check card
check cards
chequekaart
cirrus
cirrus-edc-maestro
controlekaart
controlekaarten
credit card
credit cards
credit card
credit cards
debetkaart
debetkaarten
debit card
debit cards
debit card
debit cards
debito automatico
diners club
diners club
discover
discover card
discover cards
discover card
discover cards
débito automático
edc
eigentümername
european debit card
hoofdkaart
hoofdkaarten
in viaggio
japanese card bureau
japanse kaartdienst
jcb
kaart
kaart num
kaartaantal
kaartaantallen
kaarthouder
kaarthouders
karte
karteninhaber
karteninhabers
kartennr
kartennummer
kreditkarte
kreditkarten-nummer
kreditkarteninhaber
kreditkarteninstitut
kreditkartennummer
kreditkartentyp
maestro
master card
master cards
Mastercard
master cards
mc
mister cash
n carta
carta
no de tarjeta
no do cartao
no do cartão
no. de tarjeta
no. do cartao
no. do cartão
nr carta
nr. carta
numeri di scheda
numero carta
numero de cartao
numero de carte
numero de cartão
numero de tarjeta
numero della carta
numero di carta
numero di scheda
numero do cartao
numero do cartão
numéro de carte
nº carta
nº de carte
nº de la carte
nº de tarjeta
nº do cartao
nº do cartão
nº. do cartão
número de cartao
número de cartão
número de tarjeta
número do cartao
scheda dell'assegno
scheda dell'atmosfera
scheda dell'atmosfera
scheda della banca
scheda di controllo
scheda di debito
scheda matrice
schede dell'atmosfera
schede di controllo
schede di debito
schede matrici
scoprono la scheda
scoprono le schede
solo
supporti di scheda
supporto di scheda
switch
tarjeta atm
tarjeta credito
tarjeta de atm
tarjeta de credito
tarjeta de debito
tarjeta debito
tarjeta no
tarjetahabiente
tipo della scheda
ufficio giapponese della
scheda
v pay
v-pay
visa
visa plus
visa electron
visto
visum
vpay
```
#### <a name="keyword_card_security_terms_dict"></a>Keyword\_card\_security\_terms\_dict
```
card identification number
card verification
cardi la verifica
cid
cod seg
cod seguranca
cod segurança
cod sicurezza
cod. seg
cod. seguranca
cod. segurança
cod. sicurezza
codice di sicurezza
codice di verifica
codigo
codigo de seguranca
codigo de segurança
crittogramma
cryptogram
cryptogramme
cv2
cvc
cvc2
cvn
cvv
cvv2
cód seguranca
cód segurança
cód. seguranca
cód. segurança
código
código de seguranca
código de segurança
de kaart controle
geeft nr uit
issue no
issue number
kaartidentificatienummer
kreditkartenprufnummer
kreditkartenprüfnummer
kwestieaantal
no. dell'edizione
no. di sicurezza
numero de securite
numero de verificacao
numero dell'edizione
numero di identificazione della
scheda
numero di sicurezza
numero van veiligheid
numéro de sécurité
nº autorizzazione
número de verificação
perno il blocco
pin block
prufziffer
prüfziffer
security code
security no
security number
sicherheits kode
sicherheitscode
sicherheitsnummer
speldblok
veiligheid nr
veiligheidsaantal
veiligheidscode
veiligheidsnummer
verfalldatum
```
#### <a name="keyword_card_expiration_terms_dict"></a>Keyword\_card\_expiration\_terms\_dict
```
ablauf
data de expiracao
data de expiração
data del exp
data di exp
data di scadenza
data em que expira
data scad
data scadenza
date de validité
datum afloop
datum van exp
de afloop
espira
espira
exp date
exp datum
expiration
expire
expires
expiry
fecha de expiracion
fecha de venc
gultig bis
gultigkeitsdatum
gültig bis
gültigkeitsdatum
la scadenza
scadenza
valable
validade
valido hasta
valor
venc
vencimento
vencimiento
verloopt
vervaldag
vervaldatum
vto
válido hasta
```
## <a name="eu-drivers-license-number"></a>EU の運転免許証番号
これらのエンティティは、EU の運転免許証番号の機密情報タイプです。
- オーストリア
- ベルギー
- ブルガリア
- クロアチア
- キプロス
- チェコ語
- デンマーク
- エストニア
- フィンランド
- フランス
- ドイツ
- ギリシャ
- ハンガリー
- アイルランド
- イタリア
- ラトビア
- リトアニア
- ルクセンブルグ
- マルタ
- オランダ
- ポーランド
- ポルトガル
- ルーマニア
- スロバキア
- スロベニア
- スペイン
- スウェーデン
- 英国
## <a name="eu-national-identification-number"></a>EU の国民識別番号
これらのエンティティは、EU の国民識別番号の機密情報タイプです。
- オーストリア
- ベルギー
- ブルガリア
- クロアチア
- キプロス
- チェコ語
- デンマーク
- エストニア
- フィンランド
- フランス
- ドイツ
- ギリシャ
- ハンガリー
- アイルランド
- イタリア
- ラトビア
- リトアニア
- ルクセンブルグ
- マルタ
- オランダ
- ポーランド
- ポルトガル
- ルーマニア
- スロバキア
- スロベニア
- スペイン
- 英国
## <a name="eu-passport-number"></a>EU のパスポート番号
これらのエンティティは、EU のパスポート番号の機密情報タイプです。これらのエンティティは、EU のパスポート番号バンドルです。
- オーストリア
- ベルギー
- ブルガリア
- クロアチア
- キプロス
- チェコ語
- デンマーク
- エストニア
- フィンランド
- フランス
- ドイツ
- ギリシャ
- ハンガリー
- アイルランド
- イタリア
- ラトビア
- リトアニア
- ルクセンブルグ
- マルタ
- オランダ
- ポーランド
- ポルトガル
- ルーマニア
- スロバキア
- スロベニア
- スペイン
- スウェーデン
- 英国
## <a name="eu-social-security-number-or-equivalent-identification"></a>EU の社会保障番号または同等の ID
これらのエンティティは、EU の社会保障番号または同等の ID の機密情報タイプです。
- オーストリア
- ベルギー
- クロアチア
- チェコ語
- デンマーク
- フィンランド
- フランス
- ドイツ
- ギリシャ
- ハンガリー
- ポルトガル
- スペイン
- スウェーデン
## <a name="eu-tax-identification-number"></a>EU 納税者番号
これらのエンティティは、EU 納税者番号の機密情報タイプです。
- オーストリア
- ベルギー
- ブルガリア
- クロアチア
- キプロス
- チェコ語
- デンマーク
- エストニア
- フィンランド
- フランス
- ドイツ
- ギリシャ
- ハンガリー
- アイルランド
- イタリア
- ラトビア
- リトアニア
- ルクセンブルグ
- マルタ
- オランダ
- ポーランド
- ポルトガル
- ルーマニア
- スロバキア
- スロベニア
- スペイン
- スウェーデン
- 英国
## <a name="finland-national-id"></a>フィンランドの国民 ID
### <a name="format"></a>Format
6 桁の数字、世紀を示す文字、3 桁の数字、1 桁のチェック ディジット
### <a name="pattern"></a>Pattern
パターンには次の値をすべて含める必要があります。
- DDMMYY 形式の 6 桁の数字 (生年月日)
- 世紀マーカー ('-'、'+'、'a' のいずれか)
- 3 桁の数字 (個人識別番号)
- チェック ディジットである 1 桁の数字または文字 (大文字と小文字が区別されます)
### <a name="keywords"></a>キーワード
```
ainutlaatuinen henkilökohtainen tunnus
henkilökohtainen tunnus
henkilötunnus
henkilötunnusnumero#
henkilötunnusnumero
hetu
ID no
ID number
identification number
identiteetti numero
identity number
ID number
kansallinen henkilötunnus
kansallisen henkilökortin
national ID card
national ID no.
personal ID
personal identity code
personalidnumber#
personbeteckning
personnummer
social security number
sosiaaliturvatunnus
tax ID
tax identification no
tax identification number
tax no#
tax no
tax number
tax registration number
tax ID#
tax ID no#
tax ID number#
tax no#
tax number#
tax number
tin ID
tin no
tin#
tunnistenumero
tunnus numero
tunnusluku
tunnusnumero
verokortti
veronumero
verotunniste
verotunnus
```
## <a name="finland-passport-number"></a>フィンランドのパスポート番号
この機密情報タイプのエンティティは、EU のパスポート番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
9 桁の文字と数字の組み合わせ
### <a name="pattern"></a>Pattern
9 桁の文字と数字の組み合わせ:
- 2 文字 (大文字と小文字は区別されません)
- 7 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keywords_eu_passport_number_common"></a>Keywords\_eu\_passport\_number\_common
```
passport#
passport #
passport ID
passports
passport no
passport no
passport number
passport number
passport numbers
passport numbers
```
#### <a name="keyword_finland_passport_number"></a>Keyword\_finland\_passport\_number
```
suomalainen passi
passin numero
passin numero.#
passin numero#
passin numero.
passi#
passi number
```
## <a name="france-drivers-license-number"></a>フランスの運転免許証番号
この機密情報タイプのエンティティは、EU の運転免許証番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
12 桁
### <a name="pattern"></a>Pattern
フランスの電話番号など類似のパターンに対する検証を考慮した 12 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_french_drivers_license"></a>Keyword\_french\_drivers\_license
```
driverlic
driverlics
driver license
driver licenses
driverlicence
driverlicences
driver lic
driver lics
driver license
driver licenses
driver license
driver licenses
driverslic
driverslics
driverslicence
driverslicences
drivers license
drivers licenses
drivers lic
drivers lics
drivers license
drivers licenses
drivers license
drivers licenses
driver'lic
driver'lics
driver'license
driver'licenses
driver'license
driver'licenses
driver' lic
driver' lics
driver' license
driver' licenses
driver' license
driver' licenses
driver'slic
driver'slics
driver'license
driver'licenses
driver'license
driver'licenses
driver's lic
driver's lics
driver's license
driver's licenses
driver's license
driver's licenses
dl#
dls#
driverlic#
driverlics#
driver license#
driver licenses#
driverlicence#
driverlicences#
driver lic#
driver lics#
driver license#
driver licenses#
driver licenses#
driverslic#
driverslics#
drivers license#
drivers licenses#
driverslicence#
driverslicences#
drivers lic#
drivers lics#
drivers license#
drivers licenses#
drivers license#
drivers licenses#
driver'lic#
driver'lics#
driver'license#
driver'licenses#
driver'license#
driver'licenses#
driver' lic#
driver' lics#
driver' license#
driver' licenses#
driver' license#
driver' licenses#
driver'slic#
driver'slics#
driver'license#
driver'licenses#
driver'license#
driver'licenses#
driver's lic#
driver's lics#
driver's license#
driver's licenses#
driver's license#
driver's licenses#
driving license
driving license
dlno#
driv lic
driv licen
driv license
driv licenses
driv license
driv licenses
driver licen
drivers licen
driver's licen
driving lic
driving licen
driving licenses
driving license
driving licenses
driving permit
dl no
dlno
dl number
permis de conduire
license number
license number
license numbers
license numbers
numéros de license
```
## <a name="france-national-id-card-cni"></a>フランスの国民 ID カード (CNI)
### <a name="format"></a>Format
12 桁
### <a name="pattern"></a>Pattern
12 桁
### <a name="keywords"></a>キーワード
#### <a name="keywords_france_eu_national_id_card"></a>Keywords\_france\_eu\_national\_id\_card
```
card number
carte nationale d'identité
carte nationale d'idenite no
cni#
cni
compte bancaire
national identification number
national identity
nationalidno#
numéro d'assurance maladie
numéro de carte vitale
```
## <a name="france-passport-number"></a>フランスのパスポート番号
この機密情報タイプのエンティティは、EU のパスポート番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
9 桁の数字と文字
### <a name="pattern"></a>Pattern
9 桁の数字と文字:
- 2 桁の数字
- 2 文字 (大文字と小文字は区別されません)
- 5 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_passport"></a>Keyword\_passport
```
Passport Number
Passport No
Passport #
Passport#
PassportID
Passport no
passport number
パスポート
パスポート番号
パスポートのNum
パスポート＃
Numéro de passeport
Passeport n °
Passeport Non
Passeport #
Passeport#
PasseportNon
Passeportn °
```
## <a name="france-social-security-number-insee-or-equivalent-identification"></a>フランスの社会保障番号 (INSEE) または同等の ID
この機密情報タイプのエンティティは、EU の社会保障番号とその同等の ID の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
15 桁
### <a name="pattern"></a>Pattern
次の 2 つのパターンのいずれかに一致する必要があります。
- 13 桁の数字、1 つのスペースの後に 2 桁の数字、または
- 15 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_fr_insee"></a>Keyword\_fr\_insee
```
insee
securité sociale
securite sociale
national ID
national identification
numéro d'identité
no d'identité
no. d'identité
numero d'identite
no d'identite
no. d'identite
social security number
social security code
social insurance number
le numéro d'identification nationale
d'identité nationale
numéro de sécurité sociale
le code de la sécurité sociale
numéro d'assurance sociale
numéro de sécu
code sécu
```
## <a name="germany-drivers-license-number"></a>ドイツの運転免許証番号
この機密情報タイプのエンティティは、EU の運転免許証番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
11 桁の数字と文字の組み合わせ
### <a name="pattern"></a>Pattern
11 桁の数字と文字 (大文字と小文字は区別されません)
- 1 桁の数字または文字
- 2 桁の数字
- 6 桁の数字または文字
- 1 桁の数字
- 1 桁の数字または文字
### <a name="keywords"></a>キーワード
#### <a name="keyword_german_drivers_license_number"></a>Keyword\_german\_drivers\_license\_number
```
ausstellungsdatum
ausstellungsort
ausstellende behöde
ausstellende behorde
ausstellende behoerde
führerschein
fuhrerschein
fuehrerschein
führerscheinnummer
fuhrerscheinnummer
fuehrerscheinnummer
führerschein-
fuhrerschein-
fuehrerschein-
führerscheinnummernr
fuhrerscheinnummernr
fuehrerscheinnummernr
führerscheinnummerklasse
fuhrerscheinnummerklasse
fuehrerscheinnummerklasse
nr-führerschein
nr-fuhrerschein
nr-fuehrerschein
no-führerschein
no-fuhrerschein
no-fuehrerschein
n-führerschein
n-fuhrerschein
n-fuehrerschein
permis de conduire
driverlic
driverlics
driver license
driver licenses
driverlicence
driverlicences
driver lic
driver lics
driver license
driver licenses
driver license
driver licenses
driverslic
driverslics
driverslicence
driverslicences
drivers license
drivers licenses
drivers lic
drivers lics
drivers license
drivers licenses
drivers license
drivers licenses
driver'lic
driver'lics
driver'license
driver'licenses
driver'license
driver'licenses
driver' lic
driver' lics
driver' license
driver' licenses
driver' license
driver' licenses
driver'slic
driver'slics
driver'license
driver'licenses
driver'license
driver'licenses
driver's lic
driver's lics
driver's license
driver's licenses
driver's license
driver's licenses
dl#
dls#
driverlic#
driverlics#
driver license#
driver licenses#
driverlicence#
driverlicences#
driver lic#
driver lics#
driver license#
driver licenses#
driver licenses#
driverslic#
driverslics#
drivers license#
drivers licenses#
driverslicence#
driverslicences#
drivers lic#
drivers lics#
drivers license#
drivers licenses#
drivers license#
drivers licenses#
driver'lic#
driver'lics#
driver'license#
driver'licenses#
driver'license#
driver'licenses#
driver' lic#
driver' lics#
driver' license#
driver' licenses#
driver' license#
driver' licenses#
driver'slic#
driver'slics#
driver'license#
driver'licenses#
driver'license#
driver'licenses#
driver's lic#
driver's lics#
driver's license#
driver's licenses#
driver's license#
driver's licenses#
driving license
driving license
dlno#
driv lic
driv licen
driv license
driv licenses
driv license
driv licenses
driver licen
drivers licen
driver's licen
driving lic
driving licen
driving licenses
driving license
driving licenses
driving permit
dlno
```
## <a name="germany-identity-card-number"></a>ドイツの身分証明書番号
### <a name="format"></a>Format
2010 年 11 月 1 日以降:9 桁の文字と数字
1987 年 4 月 1 日から 2010 年 10 月 31 日まで:10 桁の数字
### <a name="pattern"></a>Pattern
2010 年 11 月 1 日以降:
- 1 文字 (大文字と小文字は区別されません)
- 8 桁の数字
1987 年 4 月 1 日から 2010 年 10 月 31 日まで:
- 10 桁
### <a name="keywords"></a>キーワード
#### <a name="keyword_germany_id_card"></a>Keyword\_germany\_id\_card
```
ausweis
gpid
identification
identifikation
identifizierungsnummer
identity card
identity number
id-nummer
personal ID
personalausweis
persönliche ID nummer
persönliche identifikationsnummer
persönliche-id-nummer
```
## <a name="germany-passport-number"></a>ドイツのパスポート番号
この機密情報タイプのエンティティは、EU のパスポート番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
10 桁の数字または文字
### <a name="pattern"></a>Pattern
パターンには次の値をすべて含める必要があります。
- 最初の文字は、数字または次のセット (C、F、G、H、J、K) の文字です
- 3 桁の数字
- 5 桁の数字または次のセット (C、～ H、J ～ N、P、R、T、V ～ Z) の文字
- 1 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_german_passport"></a>Keyword\_german\_passport
```
reisepasse
reisepassnummer
No-Reisepass
Nr-Reisepass
Reisepass-Nr
Passnummer
reisepässe
passeport no.
passeport no
```
## <a name="greece-national-id-card"></a>ギリシャの国民 ID カード
### <a name="format"></a>Format
7 ～ 8 桁の文字と数字、1 つのダッシュの組み合わせ
### <a name="pattern"></a>Pattern
7 桁の文字と数字 (古い形式):
- 1 文字 (任意のギリシャ文字)
- 1 つのダッシュ
- 6 桁の数字
8 桁の文字と数字 (新しい形式):
- ギリシャ文字とラテン アルファベットの両方に大文字が含まれる 2 文字 (ABEZHIKMNOPTYX)
- 1 つのダッシュ
- 6 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_greece_id_card"></a>Keyword\_greece\_id\_card
```
greek ID
greek national ID
greek personal ID card
greek police ID
identity card
tautotita
ταυτότητα
ταυτότητας
```
## <a name="hong-kong-identity-card-hkid-number"></a>香港特別行政区の身分証明書 (HKID) 番号
### <a name="format"></a>Format
8 ～ 9 桁の文字と数字、最後の文字を囲む省略可能なかっこの組み合わせ
### <a name="pattern"></a>Pattern
8 ～ 9 文字の組み合わせ:
- 1 ～ 2 文字 (大文字と小文字は区別されません)
- 6 桁の数字
- 最後の文字 (任意の数字または文字 A)。これはチェック ディジットであり、オプションでかっこで囲みます。
### <a name="keywords"></a>キーワード
#### <a name="keyword_hong_kong_id_card"></a>Keyword\_hong\_kong\_id\_card
```
hkid
Hong Kong identity card
HKIDC
ID card
identity card
hk identity card
Hong Kong ID
香港身份證
香港永久性居民身份證
身份證
身份証
身分證
身分証
香港身份証
香港身分證
香港身分証
香港身份證
香港居民身份證
香港居民身份証
香港居民身分證
香港居民身分証
香港永久性居民身份証
香港永久性居民身分證
香港永久性居民身分証
香港永久性居民身份證
香港非永久性居民身份證
香港非永久性居民身份証
香港非永久性居民身分證
香港非永久性居民身分証
香港特別行政區永久性居民身份證
香港特別行政區永久性居民身份証
香港特別行政區永久性居民身分證
香港特別行政區永久性居民身分証
香港特別行政區非永久性居民身份證
香港特別行政區非永久性居民身份証
香港特別行政區非永久性居民身分證
香港特別行政區非永久性居民身分証
```
## <a name="ip-address"></a>IP アドレス
### <a name="format"></a>Format
#### <a name="ipv4"></a>IPv4:
書式設定されたバージョン (ピリオドあり) および書式設定されていないバージョン (ピリオドなし) の IPv4 アドレスを示す複雑なパターン
#### <a name="ipv6"></a>IPv6 : よく寄せられる質問 ◆セグ : 次の TU を含む◇
書式設定された IPv6 番号 (コロンを含む) を示す複雑なパターン
### <a name="pattern"></a>Pattern
### <a name="keywords"></a>キーワード
#### <a name="keyword_ipaddress"></a>Keyword\_ipaddress
```
IP (this keyword is case-sensitive)
ip address
ip addresses
internet protocol
IP-כתובת ה
```
## <a name="india-permanent-account-number-pan"></a>インドの基本税務番号 (PAN)
### <a name="format"></a>Format
10 桁の文字または数字
### <a name="pattern"></a>Pattern
10 桁の文字または数字:
- 3 文字 (大文字と小文字は区別されません)
- C、P、H、F、A、T、B、L、J、G の 1 文字 (大文字と小文字は区別されません)
- 1 文字
- 4 桁の数字
- 1 文字 (大文字と小文字は区別されません)
### <a name="keywords"></a>キーワード
#### <a name="keyword_india_permanent_account_number"></a>Keyword\_india\_permanent\_account\_number
```
Permanent Account Number
PAN
```
## <a name="india-unique-identification-aadhaar-number"></a>インドの一意識別 (Aadhaar) 番号
### <a name="format"></a>Format
省略可能なスペースまたはダッシュを含む 12 桁の数字
### <a name="pattern"></a>Pattern
12 桁の数字:
- 1 桁の数字 (0 または 1 以外)
- 3 桁の数字
- 1 つの省略可能なスペースまたはダッシュ
- 4 桁の数字
- 1 つの省略可能なスペースまたはダッシュ
- 最後の数字 (チェック ディジット)
### <a name="keywords"></a>キーワード
#### <a name="keyword_india_aadhar"></a>Keyword\_india\_aadhar
```
aadhaar
aadhar
aadhar#
uid
आधार
uidai
```
## <a name="indonesia-identity-card-ktp-number"></a>インドネシアの身分証明書 (KTP) 番号
### <a name="format"></a>Format
省略可能なピリオドを含む 16 桁の数字
### <a name="pattern"></a>Pattern
16 桁の数字:
- 2 桁の数字 (州コード)
- 1 つのピリオド (省略可能)
- 2 桁の数字 (摂政管区または都市コード)
- 2 桁の数字 (小区域コード)
- 1 つのピリオド (省略可能)
- DDMMYY 形式の 6 桁の数字 (生年月日)
- 1 つのピリオド (省略可能)
- 4 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_indonesia_id_card"></a>Keyword\_indonesia\_id\_card
```
KTP
Kartu Tanda Penduduk
Nomor Induk Kependudukan
```
## <a name="international-banking-account-number-iban"></a>IBAN (International Banking Account Number)
### <a name="format"></a>Format
国番号 (2 文字)、チェック ディジット (2 桁の数字)、:::no-loc text="bban"::: 番号 (最大 30 文字)
### <a name="pattern"></a>Pattern
パターンには次の値をすべて含める必要があります。
- 2 文字の国番号
- 2 桁のチェック ディジット (後に省略可能な 1 つのスペースが続きます)
- 4 桁の文字または数字、1 ～ 7 グループ (スペースで区切ることができます)
- 1 ～ 3 桁の文字または数字
国ごとに形式が少し異なります。 IBAN の機密情報タイプは、次の 60 か国に該当します。
```
ad, ae, al, at, az, ba, be, bg, bh, ch, cr, cy, cz, de, dk, do, ee, es, fi, fo, fr, gb, ge, gi, gl, gr, hr, hu, that is, il, is, it, kw, kz, lb, li, lt, lu, lv, mc, md, me, mk, mr, mt, mu, nl, no, pl, pt, ro, rs, sa, se, si, sk, sm, tn, tr, vg
```
### <a name="keywords"></a>キーワード
なし
## <a name="ireland-personal-public-service-pps-number"></a>アイルランドの個人公共サービス (PPS) 番号
### <a name="format"></a>Format
古い形式 (2012 年 12 月 31 日まで):
- 7 桁の数字の後に 1 ～ 2 文字
新しい形式 (2013 年 1 月 1 日以降):
- 7 桁の数字の後に 2 文字
### <a name="pattern"></a>Pattern
古い形式 (2012 年 12 月 31 日まで):
- 7 桁の数字
- 1 ～ 2 文字 (大文字と小文字は区別されません)
新しい形式 (2013 年 1 月 1 日以降):
- 7 桁の数字
- アルファベットのチェック ディジットである 1 文字 (大文字と小文字は区別されません)
- 省略可能な 1 文字 (A ～ I の範囲または "W")
### <a name="keywords"></a>キーワード
#### <a name="keywords_ireland_eu_national_id_card"></a>Keywords\_ireland\_eu\_national\_id\_card
```
client identity service
identification number
personal ID number
personal public service number
personal service no
phearsanta seirbhíse poiblí
pps no
pps number
pps num
pps service no
ppsn
ppsno#
ppsno
psp
public service no
publicserviceno#
publicserviceno
revenue and social insurance number
rsi no
rsi number
rsin
seirbhís aitheantais cliant
uimh
uimhir aitheantais chánach
uimhir aitheantais phearsanta
uimhir phearsanta seirbhíse poiblí
tax ID
tax identification no
tax identification number
tax no#
tax no
tax number
tax registration number
tax ID#
tax ID no#
tax ID number#
tax no#
tax number#
tax number
tin ID
tin no
tin#
```
## <a name="israel-bank-account-number"></a>イスラエルの銀行口座番号
### <a name="format"></a>Format
13 桁の数字
### <a name="pattern"></a>Pattern
書式設定済み:
- 2 桁の数字
- 1 つのダッシュ
- 3 桁の数字
- 1 つのダッシュ
- 8 桁の数字
書式設定なし:
- 13 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_israel_bank_account_number"></a>Keyword\_israel\_bank\_account\_number
```
Bank Account Number
Bank Account
Account Number
מספר חשבון בנק
```
## <a name="israel-national-identification-number"></a>イスラエルの国民識別番号
### <a name="format"></a>Format
9 桁の数字
### <a name="pattern"></a>Pattern
9 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_israel_national_id"></a>Keyword\_Israel\_National\_ID
```
מספר זהות
מספר זיה וי
מספר זיהוי ישר אלי
זהותישר אלית
هو ية اسرائيل ية عدد
هوية إسرائ يلية
رقم الهوية
عدد هوية فريدة من نوعها
ID number#
ID number
identity no
identity number#
identity number
israeliidentitynumber
personal ID
unique ID
```
## <a name="italy-drivers-license-number"></a>イタリアの運転免許証番号
この機密情報タイプのエンティティは、EU の運転免許証番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
10 桁の文字と数字の組み合わせ
### <a name="pattern"></a>Pattern
10 桁の文字と数字の組み合わせ:
- 1 文字 (大文字と小文字は区別されません)
- 文字 "A" または "V" (大文字と小文字は区別されません)
- 7 桁の数字
- 1 文字 (大文字と小文字は区別されません)
### <a name="keywords"></a>キーワード
#### <a name="keyword_italy_drivers_license_number"></a>Keyword\_italy\_drivers\_license\_number
```
numero di patente
patente di guida
patente guida
patenti di guida
patenti guida
```
## <a name="japan-bank-account-number"></a>日本の銀行口座番号
### <a name="format"></a>Format
7 桁または 8 桁の数字
### <a name="pattern"></a>Pattern
銀行口座番号:
- 7 桁または 8 桁の数字
- 銀行口座の支店コード:
- 4 桁の数字
- 1 つのスペースまたはダッシュ (省略可能)
- 3 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_jp_bank_account"></a>Keyword\_jp\_bank\_account
```
Checking Account Number
Checking Account
Checking Account #
Checking Acct Number
Checking Acct #
Checking Acct No.
Checking Account No.
Bank Account Number
Bank Account
Bank Account #
Bank Acct Number
Bank Acct #
Bank Acct No.
Bank Account No.
Savings Account Number
Savings Account
Savings Account #
Savings Acct Number
Savings Acct #
Savings Acct No.
Savings Account No.
Debit Account Number
Debit Account
Debit Account #
Debit Acct Number
Debit Acct #
Debit Acct No.
Debit Account No.
口座番号
銀行口座
銀行口座番号
総合口座
普通預金口座
普通口座
当座預金口座
当座口座
預金口座
振替口座
銀行
バンク
```
#### <a name="keyword_jp_bank_branch_code"></a>Keyword\_jp\_bank\_branch\_code
```
支店番号
支店コード
店番号
```
## <a name="japan-drivers-license-number"></a>日本の運転免許証番号
### <a name="format"></a>Format
12 桁
### <a name="pattern"></a>Pattern
12 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_jp_drivers_license_number"></a>Keyword\_jp\_drivers\_license\_number
```
driver license
drivers license
driver'license
drivers licenses
driver'licenses
driver licenses
dl#
dls#
lic#
lics#
運転免許証
運転免許
免許証
免許
運転免許証番号
運転免許番号
免許証番号
免許番号
運転免許証ナンバー
運転免許ナンバー
免許証ナンバー
運転免許証no
運転免許no
免許証no
免許no
運転経歴証明書番号
運転経歴証明書
運転免許証No.
運転免許No.
免許証No.
免許No.
運転免許証#
運転免許#
免許証#
免許#
```
## <a name="japan-passport-number"></a>日本のパスポート番号
### <a name="format"></a>Format
2 文字の後に 7 桁の数字
### <a name="pattern"></a>Pattern
2 文字 (大文字と小文字は区別されません) の後に 7 桁の数字
#### <a name="keyword_jp_passport"></a>Keyword\_jp\_passport
```
Passport
Passport Number
Passport No.
Passport #
パスポート
パスポート番号
パスポートナンバー
パスポート＃
パスポート#
パスポートNo.
旅券番号
旅券番号＃
旅券番号♯
旅券ナンバー
```
## <a name="japan-residence-card-number"></a>日本の在留カード番号
### <a name="format"></a>Format
12 桁の文字と数字
### <a name="pattern"></a>Pattern
12 桁の文字と数字:
- 2 文字 (大文字と小文字は区別されません)
- 8 桁の数字
- 2 文字 (大文字と小文字は区別されません)
### <a name="keywords"></a>キーワード
#### <a name="keyword_jp_residence_card_number"></a>Keyword\_jp\_residence\_card\_number
```
Residence card number
Residence card no
Residence card #
在留カード番号
在留カード
在留番号
```
## <a name="japan-resident-registration-number"></a>日本の住民票コード
### <a name="format"></a>Format
11 桁の数字
### <a name="pattern"></a>Pattern
11 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_jp_resident_registration_number"></a>Keyword\_jp\_resident\_registration\_number
```
Resident Registration Number
Residents Basic Registry Number
Resident Registration No.
Resident Register No.
Residents Basic Registry No.
Basic Resident Register No.
外国人登録証明書番号
証明書番号
登録番号
外国人登録証
```
## <a name="japan-social-insurance-number-sin"></a>日本の社会保険番号 (SIN)
### <a name="format"></a>Format
7 ～ 12 桁の数字
### <a name="pattern"></a>Pattern
7 ～ 12 桁の数字:
- 4 桁の数字
- 1 つのハイフン (省略可能)
- 6 桁の数字、または
- 7 ～ 12 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_jp_sin"></a>Keyword\_jp\_sin
```
Social Insurance No.
Social Insurance Num
Social Insurance Number
健康保険被保険者番号
健保番号
基礎年金番号
雇用保険被保険者番号
雇用保険番号
保険証番号
社会保険番号
社会保険No.
社会保険
介護保険
介護保険被保険者番号
健康保険被保険者整理番号
雇用保険被保険者整理番号
厚生年金
厚生年金被保険者整理番号
```
## <a name="malaysia-identification-card-number"></a>マレーシアの身分証明書番号
### <a name="format"></a>Format
省略可能なハイフンを含む 12 桁の数字
### <a name="pattern"></a>Pattern
12 桁の数字:
- YYMMDD 形式の 6 桁の数字 (生年月日)
- 1 つのダッシュ (省略可能)
- 2 文字 (出生地コード)
- 1 つのダッシュ (省略可能)
- 3 桁のランダムな数字
- 1 桁の数字 (性別コード)
### <a name="keywords"></a>キーワード
#### <a name="keyword_malaysia_id_card_number"></a>Keyword\_malaysia\_id\_card\_number
```
digital application card
i/c
i/c no
ic
ic no
ID card
identification Card
identity card
k/p
k/p no
kad akuan diri
kad aplikasi digital
kad pengenalan malaysia
kp
kp no
mykad
mykas
mykid
mypr
mytentera
malaysia identity card
malaysian identity card
nric
personal identification card
```
## <a name="netherlands-citizens-service-bsn-number"></a>オランダの市民サービス (BSN) 番号
### <a name="format"></a>Format
省略可能なスペースを含む 8 ～ 9 桁の数字
### <a name="pattern"></a>Pattern
8 ～ 9 桁の数字:
- 3 桁の数字
- 1 つのスペース (省略可能)
- 3 桁の数字
- 1 つのスペース (省略可能)
- 2 ～ 3 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keywords_netherlands_eu_national_id_card"></a>Keywords\_netherlands\_eu\_national\_id\_card
```
bsn#
bsn
burgerservicenummer
citizen service number
person number
personal number
personal numeric code
person-related number
persoonlijk nummer
persoonlijke numerieke code
persoonsgebonden
persoonsnummer
sociaal-fiscaal nummer
social-fiscal number
sofi
sofinummer
uniek identificatienummer
uniek identiteitsnummer
unique identification number
unique identity number
uniqueidentityno#
```
## <a name="new-zealand-ministry-of-health-number"></a>ニュージーランド保健省 (Ministry of Health) 番号
### <a name="format"></a>Format
3 文字、1 つのスペース (省略可能)、4 桁の数字
### <a name="pattern"></a>Pattern
- 'I' と 'O' を除く 3 文字 (大文字と小文字は区別されません)
- 1 つのスペース (省略可能)
- 4 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_nz_terms"></a>Keyword\_nz\_terms
```
NHI
New Zealand
Health
treatment
National Health Index Number
nhi number
nhi no.
NHI#
National Health Index No.
National Health Index Id
National Health Index #
```
## <a name="norway-identification-number"></a>ノルウェーの識別番号
### <a name="format"></a>Format
11 桁の数字
### <a name="pattern"></a>Pattern
11 桁の数字:
- DDMMYY 形式の 6 桁の数字 (生年月日)
- 3 桁の数字 (個人番号)
- 2 桁のチェック ディジット
### <a name="keywords"></a>キーワード
#### <a name="keyword_norway_id_number"></a>Keyword\_norway\_id\_number
```
Personal identification number
Norwegian ID Number
ID Number
Identification
Personnummer
Fødselsnummer
```
## <a name="philippines-unified-multi-purpose-identification-number"></a>フィリピンの多目的統一 ID 番号
### <a name="format"></a>Format
ハイフンで区切られた 12 桁の数字
### <a name="pattern"></a>Pattern
12 桁の数字:
- 4 桁の数字
- 1 つのハイフン
- 7 桁の数字
- 1 つのハイフン
- 1 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_philippines_id"></a>Keyword\_philippines\_id
```
Unified Multi-Purpose ID
UMID
Identity Card
Pinag-isang Multi-Layunin ID
```
## <a name="poland-identity-card"></a>ポーランドの身分証明書
### <a name="format"></a>Format
3 文字と 6 桁の数字
### <a name="pattern"></a>Pattern
3 文字 (大文字と小文字は区別されません) の後に 6 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_poland_national_id_passport_number"></a>Keyword\_poland\_national\_id\_passport\_number
```
Dowód osobisty
Numer dowodu osobistego
Nazwa i numer dowodu osobistego
Nazwa i nr dowodu osobistego
Nazwa i nr dowodu tożsamości
Dowód Tożsamości
dow. os.
```
## <a name="poland-national-id-pesel"></a>ポーランドの国民 ID (PESEL)
### <a name="format"></a>Format
11 桁の数字
### <a name="pattern"></a>Pattern
- YYMMDD 形式の 6 桁の数字 (生年月日)
- 4 桁の数字
- 1 桁のチェック ディジット
### <a name="keywords"></a>キーワード
#### <a name="keyword_pesel_identification_number"></a>Keyword\_pesel\_identification\_number
```
dowód osobisty
dowódosobisty
niepowtarzalny numer
niepowtarzalnynumer
nr.-pesel
nr-pesel
numer identyfikacyjny
pesel
tożsamości narodowej
```
## <a name="poland-passport-number"></a>ポーランドのパスポート番号
この機密情報タイプのエンティティは、EU のパスポート番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
2 文字と 7 桁の数字
### <a name="pattern"></a>Pattern
2 文字 (大文字と小文字は区別されません) の後に 7 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_poland_national_id_passport_number"></a>Keyword\_poland\_national\_id\_passport\_number
```
Numer paszportu
Nr. Paszportu
Paszport
```
## <a name="portugal-citizen-card-number"></a>ポルトガルの市民カード番号
### <a name="format"></a>Format
8 桁の数字
### <a name="pattern"></a>Pattern
8 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_portugal_citizen_card"></a>Keyword\_portugal\_citizen\_card
```
bilhete de identidade
cartão de cidadão
citizen card
document number
documento de identificação
ID number
identification no
identification number
identity card no
identity card number
national ID card
nic
número bi de portugal
número de identificação civil
número de identificação fiscal
número do documento
portugal bi number
```
## <a name="portugal-drivers-license-number"></a>ポルトガルの運転免許証番号
この機密情報タイプのエンティティは、EU の運転免許証番号の機密情報タイプでのみ使用できます。
### <a name="format"></a>Format
2 つのパターン - 2 文字の後に特殊文字が含まれる 5 ～ 8 桁の数字
### <a name="pattern"></a>Pattern
パターン 1:2 文字の後に特殊文字が含まれる 5 ～ 6 桁の数字:
- 2 文字 (大文字と小文字は区別されません)
- ハイフン
- 5 桁または 6 桁の数字
- 1 つのスペース
- 1 桁の数字
パターン 2:1 文字の後に特殊文字が含まれる 6 ～ 8 桁の数字:
- 1 文字 (大文字と小文字は区別されません)
- ハイフン
- 6 桁または 8 桁の数字
- 1 つのスペース
- 1 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keywords_eu_drivers_license_number"></a>Keywords\_eu\_driver's\_license\_number
```
driverlic
driverlics
driver license
driver licenses
driverlicence
driverlicences
driver lic
driver lics
driver license
driver licenses
driver license
driver licenses
driverslic
driverslics
driverslicence
driverslicences
drivers license
drivers licenses
drivers lic
drivers lics
drivers license
drivers licenses
drivers license
drivers licenses
driver'lic
driver'lics
driver'license
driver'licenses
driver'license
driver'licenses
driver' lic
driver' lics
driver' license
driver' licenses
driver' license
driver' licenses
driver'slic
driver'slics
driver'license
driver'licenses
driver'license
driver'licenses
driver's lic
driver's lics
driver's license
driver's licenses
driver's license
driver's licenses
dl#
dls#
driverlic#
driverlics#
driver license#
driver licenses#
driverlicence#
driverlicences#
driver lic#
driver lics#
driver license#
driver licenses#
driver licenses#
driverslic#
driverslics#
drivers license#
drivers licenses#
driverslicence#
driverslicences#
drivers lic#
drivers lics#
drivers license#
drivers licenses#
drivers license#
drivers licenses#
driver'lic#
driver'lics#
driver'license#
driver'licenses#
driver'license#
driver'licenses#
driver' lic#
driver' lics#
driver' license#
driver' licenses#
driver' license#
driver' licenses#
driver'slic#
driver'slics#
driver'license#
driver'licenses#
driver'license#
driver'licenses#
driver's lic#
driver's lics#
driver's license#
driver's licenses#
driver's license#
driver's licenses#
driving license
driving license
dlno#
driv lic
driv licen
driv license
driv licenses
driv license
driv licenses
driver licen
drivers licen
driver's licen
driving lic
driving licen
driving licenses
driving license
driving licenses
driving permit
dl no
dlno
dl number
```
#### <a name="keywords_portugal_eu_drivers_license_number"></a>Keywords\_portugal\_eu\_driver's\_license\_number
```
carteira de motorista
carteira motorista
carteira de habilitação
carteira habilitação
número de licença
número licença
permissão de condução
permissão condução
Licença condução Portugal
carta de condução
```
## <a name="saudi-arabia-national-id"></a>サウジアラビアの国民 ID
### <a name="format"></a>Format
10 桁
### <a name="pattern"></a>Pattern
10 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_saudi_arabia_national_id"></a>Keyword\_saudi\_arabia\_national\_id
```
Identification Card
I card number
ID number
الوطنية الهوية بطاقة رقم
```
## <a name="singapore-national-registration-identity-card-nric-number"></a>シンガポールの国民登録 ID カード (NRIC) 番号
### <a name="format"></a>Format
9 桁の文字と数字
### <a name="pattern"></a>Pattern
- 9 桁の文字と数字:
- 文字 "F"、"G"、"S"、または "T" (大文字と小文字は区別されません)
- 7 桁の数字
- 1 文字のアルファベットのチェック ディジット
### <a name="keywords"></a>キーワード
#### <a name="keyword_singapore_nric"></a>Keyword\_singapore\_nric
```
National Registration Identity Card
Identity Card Number
NRIC
IC
Foreign Identification Number
FIN
身份证
身份證
```
## <a name="south-africa-identification-number"></a>南アフリカの識別番号
### <a name="format"></a>Format
13 桁の数字 (スペースが含まれる場合があります)
### <a name="pattern"></a>Pattern
13 桁の数字:
- YYMMDD 形式の 6 桁の数字 (生年月日)
- 4 桁の数字
- 1 桁の市民インジケーター
- 数字 "8" または "9"
- 1 桁の数字 (チェックサム ディジット)
### <a name="keywords"></a>キーワード
#### <a name="keyword_south_africa_identification_number"></a>Keyword\_south\_africa\_identification\_number
```
Identity card
ID
Identification
```
## <a name="south-korea-resident-registration-number"></a>韓国の住民登録番号
### <a name="format"></a>Format
1 つのハイフンが含まれた 13 桁の数字
### <a name="pattern"></a>Pattern
13 桁の数字:
- YYMMDD 形式の 6 桁の数字 (生年月日)
- 1 つのハイフン
- 世紀と性別によって決定される 1 桁の数字
- 4 桁の数字 (出生地コード)
- 先行する数字が同一である人を区別するために使用される 1 桁の数字
- 1 桁のチェック ディジット
### <a name="keywords"></a>キーワード
#### <a name="keyword_south_korea_resident_number"></a>Keyword\_south\_korea\_resident\_number
```
National ID card
Citizen's Registration Number
Jumin deungnok beonho
RRN
주민등록번호
```
## <a name="spain-social-security-number-ssn"></a>スペインの社会保障番号 (SSN)
この機密情報タイプのエンティティは、EU の社会保障番号または同等の ID の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
11 ～ 12 桁の数字
### <a name="pattern"></a>Pattern
11 ～ 12 桁の数字:
- 2 桁の数字
- 1 つのスラッシュ (省略可能)
- 7 ～ 8 桁の数字
- 1 つのスラッシュ (省略可能)
- 2 桁の数字
### <a name="keywords"></a>キーワード
なし
## <a name="sweden-national-id"></a>スウェーデンの国民 ID
### <a name="format"></a>Format
10 桁または 12 桁の数字と 1 つの省略可能な区切り記号
### <a name="pattern"></a>Pattern
10 桁または 12 桁の数字と 1 つの省略可能な区切り記号:
- 2 桁の数字 (省略可能)
- 日付形式 YYMMDD の 6 桁の数字
- "-" または "+" の区切り記号 (省略可能)
- 4 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keywords_swedish_national_identifier"></a>Keywords\_swedish\_national\_identifier
```
ID no
ID number
ID#
identification no
identification number
identifikationsnumret#
identifikationsnumret
identitetshandling
identity document
identity no
identity number
id-nummer
personal ID
personnummer#
personnummer
skatteidentifikationsnummer
```
## <a name="sweden-passport-number"></a>スウェーデンのパスポート番号
この機密情報タイプのエンティティは、EU のパスポート番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
8 桁の数字
### <a name="pattern"></a>Pattern
8 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_sweden_passport"></a>Keyword\_sweden\_passport
```
visa requirements
Alien Registration Card
Schengen visas
Schengen visa
Visa Processing
Visa Type
Single Entry
Multiple Entries
G3 Processing Fees
```
#### <a name="keyword_passport"></a>Keyword\_passport
```
Passport Number
Passport No
Passport #
Passport#
PassportID
Passport no
passport number
パスポート
パスポート番号
パスポートのNum
パスポート＃
Numéro de passeport
Passeport n °
Passeport Non
Passeport #
Passeport#
PasseportNon
Passeportn °
```
## <a name="swift-code"></a>SWIFT コード
### <a name="format"></a>Format
4 文字の後に 5 ～ 31 桁の文字または数字
### <a name="pattern"></a>Pattern
4 文字の後に 5 ～ 31 桁の文字または数字:
- 4 文字の銀行コード (大文字と小文字は区別されません)
- 1 つの省略可能なスペース
- 4 ～ 28 桁の文字または数字 (基本銀行口座番号 (BBAN))
- 1 つの省略可能なスペース
- 1 ～ 3 桁の文字または数字 (BBAN の残り)
### <a name="keywords"></a>キーワード
#### <a name="keyword_swift"></a>Keyword\_swift
```
international organization for standardization 9362
iso 9362
iso9362
swift#
swift code
swift number
swiftroutingnumber
swift code
swift number #
swift routing number
bic number
bic code
bic #
bic#
bank identifier code
Organization internationale de normalization 9362
rapide #
code SWIFT
le numéro de swift
swift numéro d'acheminement
le numéro BIC
#BIC
code identificateur de banque
SWIFTコード
SWIFT番号
BIC番号
BICコード
SWIFT コード
SWIFT 番号
BIC 番号
BIC コード
金融機関識別コード
金融機関コード
銀行コード
```
## <a name="taiwan-national-identification-number"></a>台湾の国民識別番号
### <a name="format"></a>Format
1 文字 (英語) の後に 9 桁の数字
### <a name="pattern"></a>Pattern
1 文字 (英語) の後に 9 桁の数字:
- 1 文字 (英語、大文字と小文字は区別されません)
- 数字 "1" または "2"
- 8 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_taiwan_national_id"></a>Keyword\_taiwan\_national\_id
```
身份證字號
身份證
身份證號碼
身份證號
身分證字號
身分證
身分證號碼
身份證號
身分證統一編號
國民身分證統一編號
簽名
蓋章
簽名或蓋章
簽章
```
## <a name="taiwan-passport-number"></a>台湾のパスポート番号
### <a name="format"></a>Format
- 生体認証パスポート番号: 9 桁の数字
- 非生体認証パスポート番号: 9 桁の数字
### <a name="pattern"></a>Pattern
生体認証パスポート番号:
- 文字 "3"
- 8 桁の数字
非生体認証パスポート番号:
- 9 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_taiwan_passport"></a>Keyword\_taiwan\_passport
```
ROC passport number
Passport number
Passport no
Passport Num
Passport #
护照
中華民國護照
Zhōnghuá Mínguó hùzhào
```
## <a name="taiwan-resident-certificate-arctarc-number"></a>台湾の在留証明書 (ARC/TARC) 番号
### <a name="format"></a>Format
10 桁の文字と数字
### <a name="pattern"></a>Pattern
10 桁の文字と数字:
- 2 文字 (大文字と小文字は区別されません)
- 8 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_taiwan_resident_certificate"></a>Keyword\_taiwan\_resident\_certificate
```
Resident Certificate
Resident Cert
Resident Cert.
Identification card
Alien Resident Certificate
ARC
Taiwan Area Resident Certificate
TARC
居留證
外僑居留證
台灣地區居留證
```
## <a name="uk-drivers-license-number"></a>英国 運転免許証番号
この機密情報タイプのエンティティは、EU の運転免許証番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
指定された形式の 18 桁の文字と数字の組み合わせ
### <a name="pattern"></a>Pattern
18 桁の文字と数字:
- 5 文字 (大文字と小文字は区別されません) または文字の代わりに数字 "9"
- 1 桁の数字
- 生年月日を示す日付形式 MMDDY の 5 桁の数字 (ドライバーが女性の場合、7 文字目には 50 が加算されます。つまり、01 ～ 12 の代わりに 51 ～ 62 になります)
- 2 文字 (大文字と小文字は区別されません) または文字の代わりに数字 "9"
- 5 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_uk_drivers_license"></a>Keyword\_uk\_drivers\_license
```
DVLA
light vans
quad bikes
motor cars
125cc
sidecar
tricycles
motorcycles
photo card license
learner drivers
license holder
license holders
driving licenses
driving license
dual control car
```
## <a name="uk-electoral-roll-number"></a>英国 選挙人名簿番号
### <a name="format"></a>Format
2 文字の後に 1 ～ 4 桁の数字
### <a name="pattern"></a>Pattern
2 文字 (大文字と小文字は区別されません) の後に 1 ～ 4 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_uk_electoral"></a>Keyword\_uk\_electoral
- 協議会の指名
- 申請フォーム
- 選挙人登録
- 選挙人名簿
## <a name="uk-national-health-service-number"></a>英国 国民健康保険番号
### <a name="format"></a>Format
スペースで区切られた 10 ～ 17 桁の数字
### <a name="pattern"></a>Pattern
10 ～ 17 桁の数字:
- 3 桁または 10 桁の数字
- 1 つのスペース
- 3 桁の数字
- 1 つのスペース
- 4 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_uk_nhs_number"></a>Keyword\_uk\_nhs\_number
```
national health service
nhs
health services authority
health authority
```
#### <a name="keyword_uk_nhs_number1"></a>Keyword\_uk\_nhs\_number1
```
patient ID
patient identification
patient no
patient number
```
#### <a name="keyword_uk_nhs_number_dob"></a>Keyword\_uk\_nhs\_number\_dob
```
GP
DOB
D.O.B
Date of Birth
Birth Date
```
## <a name="uk-national-insurance-number-nino"></a>英国 国民保険番号 (NINO)
この機密情報タイプのエンティティは、EU の国民識別番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
7 文字またはスペースまたはダッシュで区切られた 9 文字
### <a name="pattern"></a>Pattern
可能な 2 つのパターン:
- 2 文字 (このパターンで検証される有効な NINO では、このプレフィックスに特定の文字のみが使用されます。大文字と小文字は区別されません)
- 6 桁の数字
- 'A'、'B'、'C'、または 'D' (プレフィックスと同様に、サフィックスに使用できるのは特定の文字のみです。大文字と小文字は区別されません)
OR
- 2 文字
- 1 つのスペースまたはダッシュ
- 2 桁の数字
- 1 つのスペースまたはダッシュ
- 2 桁の数字
- 1 つのスペースまたはダッシュ
- 2 桁の数字
- 1 つのスペースまたはダッシュ
- 'A'、'B'、'C'、または 'D'
### <a name="keywords"></a>キーワード
#### <a name="keyword_uk_nino"></a>Keyword\_uk\_nino
```
national insurance number
national insurance contributions
protection act
insurance
social security number
insurance application
medical application
social insurance
medical attention
social security
Great Britain
NI Number
NI No.
NI #
NI#
insurance#
insurance number
national insurance#
nationalinsurancenumber
```
## <a name="uk-unique-taxpayer-reference-number"></a>英国 納税者参照番号
この機密情報タイプは、次の用途でのみ使用できます。
- データ損失の防止ポリシー
- 通信コンプライアンス ポリシー
- 情報ガバナンス
- レコードの管理
- Microsoft Cloud App Security
### <a name="format"></a>Format
スペースと区切り記号のない 10 桁の数字
### <a name="pattern"></a>Pattern
10 桁
### <a name="keywords"></a>キーワード
#### <a name="keywords_uk_eu_tax_file_number"></a>Keywords\_uk\_eu\_tax\_file\_number
```
tax number
tax file
tax ID
tax identification no
tax identification number
tax no#
tax no
tax registration number
tax ID#
tax ID no#
tax ID number#
tax no#
tax number#
tax number
tin ID
tin no
tin#
```
## <a name="us-bank-account-number"></a>米国の銀行口座番号
### <a name="format"></a>Format
6 ～ 17 桁の数字
### <a name="pattern"></a>Pattern
6 ～ 17 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_usa_bank_account"></a>Keyword\_usa\_Bank\_Account
```
Checking Account Number
Checking Account
Checking Account #
Checking Acct Number
Checking Acct #
Checking Acct No.
Checking Account No.
Bank Account Number
Bank Account #
Bank Acct Number
Bank Acct #
Bank Acct No.
Bank Account No.
Savings Account Number
Savings Account.
Savings Account #
Savings Acct Number
Savings Acct #
Savings Acct No.
Savings Account No.
Debit Account Number
Debit Account
Debit Account #
Debit Acct Number
Debit Acct #
Debit Acct No.
Debit Account No.
```
## <a name="us-drivers-license-number"></a>米国の運転免許証番号
### <a name="format"></a>Format
州によって異なります
### <a name="pattern"></a>Pattern
州 (ニューヨークなど) に依存します。
- ddd のように書式設定された 9 桁の数字が適合します。
- ddddddddd のような 9 桁の数字は適合しません。
### <a name="keywords"></a>キーワード
#### <a name="keyword_us_drivers_license_abbreviations"></a>Keyword\_us\_drivers\_license\_abbreviations
```
DL
DLS
CDL
CDLS
ID
IDs
DL#
DLS#
CDL#
CDLS#
ID#
IDs#
ID number
ID numbers
LIC
LIC#
```
#### <a name="keyword_us_drivers_license"></a>Keyword\_us\_drivers\_license
```
DriverLic
DriverLics
DriverLicense
DriverLicenses
Driver Lic
Driver Lics
Driver License
Driver Licenses
DriversLic
DriversLics
DriversLicense
DriversLicenses
Drivers Lic
Drivers Lics
Drivers License
Drivers Licenses
Driver'Lic
Driver'Lics
Driver'License
Driver'Licenses
Driver' Lic
Driver' Lics
Driver' License
Driver' Licenses
Driver'sLic
Driver'sLics
Driver'sLicense
Driver'sLicenses
Driver's Lic
Driver's Lics
Driver's License
Driver's Licenses
identification number
identification numbers
identification #
ID card
ID cards
identification card
identification cards
DriverLic#
DriverLics#
DriverLicense#
DriverLicenses#
Driver Lic#
Driver Lics#
Driver License#
Driver Licenses#
DriversLic#
DriversLics#
DriversLicense#
DriversLicenses#
Drivers Lic#
Drivers Lics#
Drivers License#
Drivers Licenses#
Driver'Lic#
Driver'Lics#
Driver'License#
Driver'Licenses#
Driver' Lic#
Driver' Lics#
Driver' License#
Driver' Licenses#
Driver'sLic#
Driver'sLics#
Driver'sLicense#
Driver'sLicenses#
Driver's Lic#
Driver's Lics#
Driver's License#
Driver's Licenses#
ID card#
ID cards#
identification card#
identification cards#
```
#### <a name="keyword_state_name_drivers_license_name"></a>Keyword\_[state\_name]\_drivers\_license\_name
- 州略称 (例: "NY")
- 州名 (例: "ニューヨーク")
## <a name="us-individual-taxpayer-identification-number-itin"></a>米国の個人納税者番号 (ITIN)
### <a name="format"></a>Format
"9" で始まり、4 桁目の数字として "7" または "8" を含む 9 桁の数字。省略可能なスペースまたはダッシュで書式設定されます
### <a name="pattern"></a>Pattern
書式設定済み:
- 数字 "9"
- 2 桁の数字
- 1 つのスペースまたはダッシュ
- "7" または "8"
- 1 桁の数字
- 1 つのスペースまたはダッシュ
- 4 桁の数字
書式設定なし:
- 数字 "9"
- 2 桁の数字
- "7" または "8"
- 5 桁の数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_itin"></a>Keyword\_itin
```
taxpayer
tax ID
tax identification
itin
i.t.i.n.
ssn
tin
social security
tax payer
itins
tax ID
individual taxpayer
```
## <a name="us-social-security-number-ssn"></a>米国の社会保障番号 (SSN)
### <a name="format"></a>Format
9 桁の数字 (書式設定されたパターンまたは書式設定されていないパターン)
>[!Note]
> 2011 年中頃までに発行された SSN には、有効になるには数値の特定の部分が特定の範囲内である必要がある厳密な書式設定があります (ただし、チェックサムはありません)。
>
### <a name="pattern"></a>Pattern
4 つの関数が、4 つの異なるパターンで SSN を検索します。
- Func\_ssn は、ダッシュまたはスペースで書式設定された 2011 年までの厳密な書式設定で SSN を検索します (ddd-dd-dddd または ddd dd dddd)
- Func\_unformatted\_ssn は、書式設定のない 9 桁の連続する数字を使用して、2011 年までの厳密な書式設定で SSN を検索します (ddddddddd)
- Func\_randomized\_formatted\_ssn は、ダッシュまたはスペースで書式設定された 2011 年以降の SSN を検索します (ddd-dd-dddd または ddd dd dddd)
- Func\_randomized\_unformatted\_ssn は、書式設定のない 9 桁の連続する数字を使用して 2011 年以降の SSN を検索します (ddddddddd)
### <a name="keywords"></a>キーワード
#### <a name="keyword_ssn"></a>Keyword\_ssn
```
SSA Number
social security number
social security #
social security#
social security no
Social Security#
Soc Sec
SSN
SSNS
SSN#
SS#
SSID
```
## <a name="us--uk-passport-number"></a>米国または英国 パスポート番号
英国の パスポート番号の機密情報タイプのエンティティは、EU のパスポート番号の機密情報タイプに含まれており、スタンドアロンの機密情報タイプのエンティティとして使用できます。
### <a name="format"></a>Format
9 桁の数字
### <a name="pattern"></a>Pattern
9 桁の連続する数字
### <a name="keywords"></a>キーワード
#### <a name="keyword_passport"></a>Keyword\_passport
```
Passport Number
Passport No
Passport #
Passport#
PassportID
Passport no
passport number
パスポート
パスポート番号
パスポートのNum
パスポート＃
Numéro de passeport
Passeport n °
Passeport Non
Passeport #
Passeport#
PasseportNon
Passeportn °
```
| 15.818143 | 329 | 0.758434 | eng_Latn | 0.181044 |
87e06819f68615610aa11697b4cf46bb17de0d3f | 3,432 | md | Markdown | articles/defender-for-iot/device-builders/quickstart-create-micro-agent-module-twin.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/defender-for-iot/device-builders/quickstart-create-micro-agent-module-twin.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/defender-for-iot/device-builders/quickstart-create-micro-agent-module-twin.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'クイックスタート: Defender for IoT マイクロ エージェントのモジュール ツインを作成する (プレビュー)'
description: このクイックスタートでは、新しいデバイス用に個別の DefenderIotMicroAgent モジュール ツインを作成する方法について説明します。
ms.date: 11/09/2021
ms.topic: quickstart
ms.openlocfilehash: 3d2829b1d779ab4db711ab590c0da4760a44aefe
ms.sourcegitcommit: 0415f4d064530e0d7799fe295f1d8dc003f17202
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 11/17/2021
ms.locfileid: "132709269"
---
# <a name="quickstart-create-a-defender-for-iot-micro-agent-module-twin-preview"></a>クイックスタート: Defender for IoT マイクロ エージェントのモジュール ツインを作成する (プレビュー)
新しいデバイス用に個別の **DefenderIotMicroAgent** モジュール ツインを作成できます。 IoT Hub 内のすべてのデバイスに対して、モジュール ツインを一括作成することもできます。
## <a name="prerequisites"></a>前提条件
なし
## <a name="device-twins"></a>デバイス ツイン
Azure に構築された IoT ソリューションでは、デバイス ツインが、デバイスの管理とプロセスの自動化の両方で主要な役割を果たします。
Defender for IoT には、既存の IoT デバイス管理プラットフォームと完全に統合する機能があります。 完全な統合により、デバイスのセキュリティの状態を管理し、既存のすべてのデバイス制御機能を使用できるようになります。 統合は、IoT Hub ツイン メカニズムを利用することによって実現されます。
概念の詳細については、「 [IoT Hub のデバイス ツインの理解と使用](../../iot-hub/iot-hub-devguide-device-twins.md)」を参照してください。
## <a name="defender-iot-micro-agent-twins"></a>Defender-IoT-micro-agent ツイン
Defender for IoT により、各デバイスの Defender-IoT-micro-agent ツインが使用されます。 Defender-IoT-micro-agent ツインでは、ソリューション内の特定のデバイスごとに、デバイスのセキュリティに関連するすべての情報が保持されます。 デバイスのセキュリティのプロパティは、通信の安全性を高め、更新を可能にし、必要なリソースが少なくて済むメンテナンスを可能にするために、専用の Defender-IoT-micro-agent ツインを通じて構成されます。
## <a name="understanding-defenderiotmicroagent-module-twins"></a>DefenderIotMicroAgent モジュール ツインについて
Azure に組み込まれる IoT ソリューションでは、デバイス ツインが、デバイスの管理とプロセスの自動化の両方で主要な役割を果たします。
Defender for IoT には、既存の IoT デバイス管理プラットフォームと完全に統合するための機能があり、デバイスのセキュリティ状態を管理したり、既存のデバイス制御機能を利用したりすることができます。 IoT Hub ツイン メカニズムを使用することで、Defender for IoT を統合できます。
Azure IoT Hub のモジュール ツインの一般的な概念の詳細については、「 [IoT Hub のモジュール ツインの理解と使用](../../iot-hub/iot-hub-devguide-module-twins.md)」を参照してください。
Defender for IoT では、モジュール ツイン メカニズムを利用して、各デバイス用に `DefenderIotMicroAgent` という Defender-IoT-micro-agent ツインが維持されます。
Defender for IoT の機能を最大限に活用するには、サービス内のすべてのデバイスに対して Defender-IoT-micro-agent ツインを作成、構成、使用する必要があります。
## <a name="create-defenderiotmicroagent-module-twin"></a>DefenderIotMicroAgent モジュール ツインの作成
**DefenderIotMicroAgent** モジュール ツインは、各デバイスの特定の構成が含まれるように各モジュール ツインを手動で編集して作成できます。
デバイス用の新しい **DefenderIotMicroAgent** モジュール ツインを手動で作成するには、以下の操作を実行します。
1. IoT ハブで、Defender-IoT-micro-agent ツインの作成対象のデバイスを探して選択します。
1. **[モジュール ID の追加]** を選択します。
1. **[モジュール ID 名]** フィールドに、「 `DefenderIotMicroAgent`」と入力します。
1. **[保存]** を選択します。
## <a name="verify-the-creation-of-a-module-twin"></a>モジュール ツインの作成の確認
特定のデバイスの Defender-IoT-micro-agent ツインが存在するかどうかを確認するには、以下の操作を行います。
1. Azure IoT Hub で、 **[エクスプローラー]** メニューの **[IoT デバイス]** を選択します。
1. デバイス ID を入力するか、 **[デバイスのクエリ]** フィールドのオプションを選択して、 **[デバイスのクエリ]** を選択します。
:::image type="content" source="media/quickstart-create-micro-agent-module-twin/iot-devices.png" alt-text="デバイスの一覧を取得するために、[デバイスのクエリ] を選択します。":::
1. デバイスを選択し、 **[デバイスの詳細]** ページを開きます。
1. **[モジュール ID]** メニューを選択し、デバイスに関連付けられているモジュール ID の一覧に **DefenderIotMicroAgent** モジュールがあることを確認します。
:::image type="content" source="media/quickstart-create-micro-agent-module-twin/device-details-module.png" alt-text="タブで [モジュール ID] を選択します。":::
## <a name="next-steps"></a>次の手順
> [!div class="nextstepaction"]
> [セキュリティに関する推奨事項の調査](quickstart-investigate-security-recommendations.md)
| 43.443038 | 258 | 0.782634 | yue_Hant | 0.544753 |
87e0acab509c55bffa898a1918ec8ca8f21c31b3 | 1,516 | md | Markdown | packages/cf-component-copyable-textarea/CHANGELOG.md | jsoref/cf-ui | 39c9a7247314286afe7a7202c8717c5c8e981ed5 | [
"BSD-3-Clause"
] | 1,443 | 2016-06-09T14:14:55.000Z | 2022-02-24T14:31:29.000Z | packages/cf-component-copyable-textarea/CHANGELOG.md | jsoref/cf-ui | 39c9a7247314286afe7a7202c8717c5c8e981ed5 | [
"BSD-3-Clause"
] | 268 | 2016-06-10T09:49:52.000Z | 2020-11-13T15:00:15.000Z | packages/cf-component-copyable-textarea/CHANGELOG.md | jsoref/cf-ui | 39c9a7247314286afe7a7202c8717c5c8e981ed5 | [
"BSD-3-Clause"
] | 126 | 2016-06-09T15:57:39.000Z | 2022-03-01T11:07:07.000Z | # Change Log
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.
<a name="4.0.2"></a>
## [4.0.2](https://github.com/cloudflare/cf-ui/compare/cf-component-copyable-textarea@4.0.1...cf-component-copyable-textarea@4.0.2) (2017-08-15)
<a name="4.0.0"></a>
# [4.0.0](https://github.com/sejoker/cf-ui/compare/cf-component-copyable-textarea@2.4.1...cf-component-copyable-textarea@4.0.0) (2017-07-12)
* Migrate textarea & copyable-textarea to fela (#295) ([be0bb03](https://github.com/sejoker/cf-ui/commit/be0bb03))
### BREAKING CHANGES
* Internals have been rewritten in a significant way.
This warrants a breaking change version bump.
Closes: #218
* feat(cf-component-textarea): s/CSS/fela/
* Internals have been rewritten in a significant way.
This warrants a breaking change version bump.
Closes: #213
<a name="3.0.0"></a>
# [3.0.0](https://github.com/koddsson/cf-ui/compare/cf-component-copyable-textarea@2.4.1...cf-component-copyable-textarea@3.0.0) (2017-07-11)
* Migrate textarea & copyable-textarea to fela (#295) ([be0bb03](https://github.com/koddsson/cf-ui/commit/be0bb03))
### BREAKING CHANGES
* Internals have been rewritten in a significant way.
This warrants a breaking change version bump.
Closes: #218
* feat(cf-component-textarea): s/CSS/fela/
* Internals have been rewritten in a significant way.
This warrants a breaking change version bump.
Closes: #213
| 28.074074 | 144 | 0.735488 | eng_Latn | 0.534741 |
87e0d65ae6eb00ea3c05b2033fba28ff987870ac | 326 | md | Markdown | contrib/init/README.md | AtomicLemon/flamecoin-pos | 3c32af5b9b0c31ed90b4abb6b2e859227e8ee8ed | [
"MIT"
] | null | null | null | contrib/init/README.md | AtomicLemon/flamecoin-pos | 3c32af5b9b0c31ed90b4abb6b2e859227e8ee8ed | [
"MIT"
] | null | null | null | contrib/init/README.md | AtomicLemon/flamecoin-pos | 3c32af5b9b0c31ed90b4abb6b2e859227e8ee8ed | [
"MIT"
] | null | null | null | Sample configuration files for:
SystemD: flamecoind.service
Upstart: flamecoind.conf
OpenRC: flamecoind.openrc
flamecoind.openrcconf
CentOS: flamecoind.init
OS X: org.flamecoin.flamecoind.plist
have been made available to assist packagers in creating node packages here.
See doc/init.md for more information.
| 25.076923 | 76 | 0.791411 | eng_Latn | 0.910795 |
87e0ef774b070aac74bd22e09d6d7e90ed26730c | 745 | md | Markdown | workflows/CHANGES.md | BrennaEpp/google-cloud-go | 877f65d329ce289c4347660529daa5ddc2e6bcf8 | [
"Apache-2.0"
] | null | null | null | workflows/CHANGES.md | BrennaEpp/google-cloud-go | 877f65d329ce289c4347660529daa5ddc2e6bcf8 | [
"Apache-2.0"
] | null | null | null | workflows/CHANGES.md | BrennaEpp/google-cloud-go | 877f65d329ce289c4347660529daa5ddc2e6bcf8 | [
"Apache-2.0"
] | null | null | null | # Changes
## [1.1.0](https://www.github.com/googleapis/google-cloud-go/compare/workflows/v1.0.0...workflows/v1.1.0) (2021-12-30)
### Features
* **workflows/executions:** add a stack_trace field to the Error messages specifying where the error occured feat: add call_log_level field to Execution messages doc: clarify requirement to escape strings within JSON arguments ([1f5aa78](https://www.github.com/googleapis/google-cloud-go/commit/1f5aa78a4d6633871651c89a6d9c48e3409fecc5))
## 1.0.0
Stabilize GA surface.
## v0.1.0
This is the first tag to carve out workflows as its own module. See
[Add a module to a multi-module repository](https://github.com/golang/go/wiki/Modules#is-it-possible-to-add-a-module-to-a-multi-module-repository).
| 41.388889 | 337 | 0.767785 | eng_Latn | 0.679877 |
87e19efcec99c0d56c52ea489c440bb409bf3cbf | 967 | md | Markdown | docs/framework/wcf/samples/windows-process-activation.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/samples/windows-process-activation.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/samples/windows-process-activation.md | MarktW86/dotnet.docs | 178451aeae4e2c324aadd427ed6bf6850e483900 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Windows Process Activation | Microsoft Docs"
ms.custom: ""
ms.date: "03/30/2017"
ms.prod: ".net-framework-4.6"
ms.reviewer: ""
ms.suite: ""
ms.technology:
- "dotnet-clr"
ms.tgt_pltfrm: ""
ms.topic: "article"
ms.assetid: 37b79642-1e6f-44b3-9777-98af57443bfa
caps.latest.revision: 3
author: "Erikre"
ms.author: "erikre"
manager: "erikre"
---
# Windows Process Activation
This section contains samples that demonstrate service activation through network protocols.
## In This Section
[NamedPipe Activation](../../../../docs/framework/wcf/samples/namedpipe-activation.md)
Demonstrates hosting a service that uses Windows Process Activation Service (WAS) to activate a service that communicates over names pipes.
[TCP Activation](../../../../docs/framework/wcf/samples/tcp-activation.md)
Demonstrates hosting a service that uses Windows Process Activation Services (WAS) to activate a service that communicates over the net.tcp protocol. | 37.192308 | 150 | 0.745605 | eng_Latn | 0.749285 |
87e2d305b79ea97d4654dfb6562fd3bc091951a5 | 3,961 | md | Markdown | README.md | shyoutarou/-React_FileUplod_Web | a6b29eb34e49ea683b8066109535109596814525 | [
"MIT"
] | 1 | 2020-11-27T13:35:05.000Z | 2020-11-27T13:35:05.000Z | README.md | shyoutarou/-React_FileUplod_Web | a6b29eb34e49ea683b8066109535109596814525 | [
"MIT"
] | null | null | null | README.md | shyoutarou/-React_FileUplod_Web | a6b29eb34e49ea683b8066109535109596814525 | [
"MIT"
] | null | null | null | # React File Uploader - Web
<!-- <p align="center">
<img src="https://raw.githubusercontent.com/shyoutarou/NLW-Next-Level-Week-3/master/.github/demo.gif" alt="NLW Intro" width="650px" />
</p>
<p align="center">
<img src="https://raw.githubusercontent.com/shyoutarou/NLW-Next-Level-Week-3/master/.github/HappyLogo.png" alt="Happy Logo" width="80%" />
</p> -->
## 📌 Index
- [React File Uploader - Web](#react-file-uploader---web)
- [📌 Index](#-index)
- [❔ Sobre o projeto](#-sobre-o-projeto)
- [⚙ Instalação e Start](#-instalação-e-start)
- [Clonagem](#clonagem)
- [Como executar o projeto](#como-executar-o-projeto)
- [💻 Executar Projeto Web](#-executar-projeto-web)
- [🐛 Issues](#-issues)
- [🤝 Contribuições](#-contribuições)
- [📜 License](#-license)
## ❔ Sobre o projeto
Projeto realizado seguindo os vídeos tutoriais desenvolvido pela [Rocketseat](https://www.youtube.com/channel/UCSfwM5u0Kce6Cce8_S72olg) como complemento as semanas NLW#2 e NLW#3 em que foram desenvolvidas soluções que requerem o upload de arquivos hospedados local e remotamente.
[Upload de arquivos: front-end com ReactJS](https://www.youtube.com/watch?v=G5UZmvkLWSQ)
[Upload de arquivos: back-end com NodeJS](https://www.youtube.com/watch?v=MkkbUfcZUZM)
[Deploy de aplicação NodeJS e ReactJS no Heroku](https://www.youtube.com/watch?v=-j7vLmBMsEU)
<!-- ## 📸 Screenshots
### Web Interface com ReactJS
<p align="center">
<img src="https://raw.githubusercontent.com/shyoutarou/NLW-Next-Level-Week-3/master/.github/demo_web.gif" alt="Happy Web" width="100%" />
</p> -->
## ⚙ Instalação e Start
Certifique-se de que tenha o `Node.js` e um gerenciador de dependências em seu ambiente antes de seguir os passos abaixo.
Para instalar e startar a plataforma Happy, use `npm` ou `yarn`:
### Clonagem
Primeiro, clone o repositório para seu ambiente:
```bash
> git clone https://github.com/shyoutarou/React_FileUplod_Web.git
```
Depois, entre no repositório clonado e no diretório correspondente ao que quer testar (web, server).
Logo após, insira os seguintes comandos no seu terminal para cada diretório respectivamente:
### Como executar o projeto
Podemos considerar este projeto como sendo divido em três partes:
Back End (pasta server) Front End (pasta web) Mobile (pasta mobile)
💡 Tanto o Front End quanto o Mobile precisam que o Back End esteja sendo executado para funcionar.
### 💻 Executar Projeto Web
```bash
# Entra no diretório "server"
> cd ./frontend
# Instala todas as dependências
> yarn install or npm install
# Starta o servidor web para a plataforma Happy
> yarn start or npm run start
# Será startado em `http://localhost:3000`
### 📦 Executar Server API REST
```bash
# Entra no diretório "server"
> cd ./server
# Instala todas as dependências
> yarn install or npm install
# Execute migrations
> yarn npm run typeorm migration:run
# Start o servidor web para a plataforma Happy
> yarn start or npm run start
# Será startado em `http://localhost:3000`
```
## 🐛 Issues
Sinta-se à vontade para registrar um novo problema com o respectivo título e descrição no repositório Happy. Se você já encontrou uma solução para seu problema, adoraria revisar sua solicitação de pull!
## 🤝 Contribuições
Siga os passos abaixo para contribuir:
1. Faça o *fork* do projeto (<https://github.com/shyoutarou/React_FileUplod_Web.git>)
2. Clone o seu *fork* para sua maquína (`git clone https://github.com/user_name/React_FileUplod_Web.git`)
3. Crie uma *branch* para realizar sua modificação (`git checkout -b feature/name_new_feature`)
4. Adicione suas modificações e faça o *commit* (`git commit -m "Descreva sua modificação"`)
5. *Push* (`git push origin feature/name_new_feature`)
6. Crie um novo *Pull Request*
7. Pronto, agora só aguardar a análise 🚀
## 📜 License
O projeto lançado em 2020 sobre a licença [MIT](./LICENSE) ❤️
Made with ♥ by Shyoutarou
Gostou? Deixe uma estrelinha para ajudar o projeto ⭐
| 30.007576 | 279 | 0.730371 | por_Latn | 0.991083 |
87e6ab050cdad0c9df4c7abee79303730c97825a | 582 | md | Markdown | _posts/2021-07-04-opiniao-o-virus-adora-a-eurocopa.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | null | null | null | _posts/2021-07-04-opiniao-o-virus-adora-a-eurocopa.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | null | null | null | _posts/2021-07-04-opiniao-o-virus-adora-a-eurocopa.md | tatudoquei/tatudoquei.github.io | a3a3c362424fda626d7d0ce2d9f4bead6580631c | [
"MIT"
] | 1 | 2022-01-13T07:57:24.000Z | 2022-01-13T07:57:24.000Z | ---
layout: post
item_id: 3390398201
title: >-
Opinião: O vírus adora a Eurocopa
author: Tatu D'Oquei
date: 2021-07-04 09:11:20
pub_date: 2021-07-04 09:11:20
time_added: 2021-07-25 16:46:09
category:
tags: []
---
Opinião | 04.07.2021 Já foram constatados surtos de covid-19 em países europeus diretamente relacionados a torcedores que viajaram para partidas. Uma irresponsabilidade, opina Jens Krepela.
**Link:** [https://amp.dw.com/pt-br/opini%C3%A3o-o-v%C3%ADrus-adora-a-eurocopa/a-58153332](https://amp.dw.com/pt-br/opini%C3%A3o-o-v%C3%ADrus-adora-a-eurocopa/a-58153332)
| 32.333333 | 189 | 0.74055 | por_Latn | 0.786468 |
87e6cf9fe99aa63fbe232c4ccfc18400da20071e | 1,043 | md | Markdown | 101-acs-mesos/docs/CommonIssues.md | GilliatM/Azure-Templates | 1a6a5c411d2052e1d1e6675bd32e47ab49767bb4 | [
"MIT"
] | 4 | 2017-10-23T13:12:20.000Z | 2019-09-11T04:01:01.000Z | 101-acs-mesos/docs/CommonIssues.md | GilliatM/Azure-Templates | 1a6a5c411d2052e1d1e6675bd32e47ab49767bb4 | [
"MIT"
] | 2 | 2016-09-17T22:20:18.000Z | 2016-09-17T22:25:44.000Z | 101-acs-mesos/docs/CommonIssues.md | GilliatM/Azure-Templates | 1a6a5c411d2052e1d1e6675bd32e47ab49767bb4 | [
"MIT"
] | 3 | 2020-09-01T13:03:22.000Z | 2021-03-19T21:04:22.000Z | # Common Issues
## Index
Look through the following list to help you resolve any common issues:
1. [MissingSubscriptionRegistration](#MissingSubscriptionRegistration) - this happens if you have never used the new portal to deploy a Compute VM before.
### MissingSubscriptionRegistration
If you get the following error:
`MissingSubscriptionRegistration: The subscription is not registered to use namespace 'Microsoft.Network'.`
`MissingSubscriptionRegistration: The subscription is not registered to use namespace 'Microsoft.Storage'.`
`MissingSubscriptionRegistration: The subscription is not registered to use namespace 'Microsoft.Compute'.``
This means that the user has never used ARM before.
To mitigate, deploy [this template](https://github.com/anhowe/scratch/tree/master/exerciseStgNetCmp) to the same region as you deployed the ACS template.
This will take < 1 min to deploy and will force a registration for your subscription in each of the resource providers. You will need to delete the resource group afterwards.
| 47.409091 | 175 | 0.803452 | eng_Latn | 0.987698 |
87e72dbd25b276e84ab8ef4a03f5e0ec435bf6f3 | 1,780 | md | Markdown | README.md | Ye99/ESP8266MicroPythonClock | 593818538fa80590fd7d65fc26f8aa1502e33b45 | [
"MIT"
] | null | null | null | README.md | Ye99/ESP8266MicroPythonClock | 593818538fa80590fd7d65fc26f8aa1502e33b45 | [
"MIT"
] | null | null | null | README.md | Ye99/ESP8266MicroPythonClock | 593818538fa80590fd7d65fc26f8aa1502e33b45 | [
"MIT"
] | null | null | null | # ESP8266MicroPythonClock
Clock implemented using ESP8266 MCU and MicroPython
Credits:
* LCD I2C driver is from https://github.com/dhylands/python_lcd/tree/master/lcd
* Wiring see https://dronebotworkshop.com/lcd-displays-arduino/
Setup:
1. Use pipenv https://pipenv.readthedocs.io/en/latest/ to hydrate your environment.
```bash
pipenv shell
```
2. Connect your NodeMCPU to your wifi network.
```Python
import network
sta_if = network.WLAN(network.STA_IF)
sta_if.active(True)
sta_if.scan() # Scan for available access points
sta_if.connect("<AP_name>", "<password>") # Connect to an AP
sta_if.isconnected() # Check for successful connection
```
3. Run rshell and copy esp8266_i2c_lcd.py, lcd_api.py, main_2004_i2c_LCD_test.py, main_1602_i2c_LCD.py files to ESP8266
NodeMCU (with MicroPython firmware), rename either of the main_xxx.py file as main.py, and reboot the MCU.
main_1602_i2c_LCD.py --- Clock.
main_2004_i2c_LCD_test.py --- test 2004 LCD. No clock function. | 71.2 | 238 | 0.426404 | eng_Latn | 0.728824 |
87e81fd035750c202a433583228139ef67266cb6 | 756 | md | Markdown | README.md | simon387/poster | a3acc07ce6288814b99c4bab46bab730b15061c9 | [
"MIT"
] | null | null | null | README.md | simon387/poster | a3acc07ce6288814b99c4bab46bab730b15061c9 | [
"MIT"
] | null | null | null | README.md | simon387/poster | a3acc07ce6288814b99c4bab46bab730b15061c9 | [
"MIT"
] | null | null | null | # poster
+ mariaDB
+ PHP 7.4.13 (cli) (built: Nov 24 2020 10:03:34) ( NTS )
## config.php example
```injectablephp
<?php
class Config
{
static $db_host = 'localhost';
static $db_name = 'poster';
static $db_username = 'root';
static $db_password = 'root';
static $db_statement_0 = '';
}
```
## How to enable PHP log (linux redhat, fedora, centos)
Edit this in ```php.ini```:
```
error_reporting = E_ALL;& ~E_DEPRECATED & ~E_STRICT
display_errors = On;Off
```
Restart it
```
systemctl restart httpd.service;systemctl restart php-fpm.service;
```
Default Fedora33 log file locations:
```
tail -F /var/log/httpd/*
tail -F /var/log/php-fpm/www-error.log
```
## Links
+ https://startbootstrap.com/theme/sb-admin-2
+ https://www.simonecelia.it/poster/
| 19.894737 | 66 | 0.681217 | kor_Hang | 0.387534 |
87e95eaa7c721eeeed1db0df9e354fd9e19ed338 | 4,119 | md | Markdown | README.md | Flafla2/Vive-Virtual-Button-Designer | f647ec8e7151d8871fcd103bc902ba192ac64056 | [
"MIT"
] | 20 | 2016-12-28T09:46:40.000Z | 2021-04-22T07:20:17.000Z | README.md | Flafla2/Vive-Virtual-Button-Designer | f647ec8e7151d8871fcd103bc902ba192ac64056 | [
"MIT"
] | null | null | null | README.md | Flafla2/Vive-Virtual-Button-Designer | f647ec8e7151d8871fcd103bc902ba192ac64056 | [
"MIT"
] | 4 | 2017-03-20T23:58:40.000Z | 2021-04-22T07:20:19.000Z | Virtual Button Designer for HTC Vive Controllers
------------------------------------------------
This is a free and open-source tool to create *Virtual Buttons* on the touchpad of HTC Vive Virtual Reality controllers.
It is built for the Unity game engine. The buttons themselves are configured via an interactive Editor window GUI, as
shown below.
Users can define virtual button regions in standard (Euclidean) coordinates, or in Polar Coordinates. Polar coordinates
are useful for creating circular buttons, such as the ones in the above graphic.
I have also included a tool to visualize the virtual buttons themselves in VR. This allows the player to more easily
see what they are selecting:
[](https://gfycat.com/DamagedUnlinedArcticwolf)
## Getting Started
First, you need to define the locations of all of your virtual buttons. To do this, open the *Virtual Button Editor*
via ``Window > Vive Virtual Button Editor``:
Changes made in the editor will be saved with your project (via ``File > Save``). You can add buttons by clicking the
"Add Button" button at the bottom of the editor. You can configure / position each button as desired, as described
below:
- **Button Name**: Arbitrary name of each button, similar to the "Axis Name" in Unity's input system. You will use this
name in code when polling the system for input changes.
- **Draw Preview Graphic**: If true, a preview graphic will be shown on the left side of the Virtual Button Editor.
- **Is Polar Coordinate**: If this is true, the *X* and *Y* coordinates in *Point 1* and *Point 2* (below) correspond
to the radius and angle of a polar coordinate (respectively). Otherwise, *Point 1* and *Point 2* will represent normal
(Euclidean) coordinates. This is useful if you want your buttons to be circular.
- **Point 1 and Point 2**: These two points define the two corners of the region your button uses. If you are working
in Euclidean coordinates, -1 corresponds to the left/top of the touchpad and 1 corresponds to the right/bottom of the
pad. In polar coordinates, *r* = 0 corresponds to the center of the pad, and *r* = 1 is at the outer edge. In polar
coordinates, the angle is represented in degrees.
### Polling Button Presses
If you want to know if the player is touching one of your virtual buttons, simply call
``ViveVirtualButtonManager::GetButtonHover`` like so:
// Assume these variables have been populated
string ButtonName;
SteamVR_TrackedObject Controller;
bool istouching = ViveVirtualButtonManager.Instance.GetButtonHover(ButtonName, Controller);
### Visualizing Virtual Buttons
If you want, you can use the ``Controller Button Previewer`` script to display an interactive overlay on top of the
SteamVR tracked controller model. Attach the script to each ``SteamVR_TrackedObject`` in the scene - if you are using
Valve's ``[CameraRig]`` prefab, then you want to attach this script to the ``Controller (left)`` and ``Controller
(right)`` objects.
- **Buttons**: An array of Buttons that you want to display. For each entry you must supply the Button Name (created
in the editor as described above) and a material to render the preview mesh with. UVs in the generated mesh
correspond to (0, 0) on the top left of the touchpad area and (1, 1) on the bottom right of the touchpad area.
Note that you do not need to provide *all* of the buttons that you create in the editor, so you can use different
combinations of buttons for different gameplay scenarios.
- **Button Prefab**: This is the prefab that will be instantiated for each virtual button. It *must* have an ``Animator``
component attached. The script will send ``Hover`` and ``Press`` boolean parameters to the Animator for button Hover
and button Press events.
- **Button Offest**: Describes the distance that the button meshes should protrude out of the touchpad origin point. | 58.842857 | 122 | 0.749454 | eng_Latn | 0.996884 |
87e96b0e4e54a36174336d375ad8291a3efb7b67 | 402 | md | Markdown | docs/reference/index.md | fredericbonnet/picotest | 6e5ec37dafac2861ae3fe26014faa9eafd312642 | [
"BSD-3-Clause"
] | 16 | 2018-05-09T20:36:14.000Z | 2022-01-11T08:33:13.000Z | docs/reference/index.md | fredericbonnet/picotest | 6e5ec37dafac2861ae3fe26014faa9eafd312642 | [
"BSD-3-Clause"
] | 6 | 2019-11-08T23:52:12.000Z | 2022-02-26T02:04:19.000Z | docs/reference/index.md | fredericbonnet/colibri | ea3995f4c56a98762005a7962a24a93a5dca5ccd | [
"BSD-3-Clause"
] | null | null | null | # Contents pages
* [Global contents](global_contents.md)
* [Structures](struct_contents.md)
* [Files](file_contents.md)
* [Modules](group_contents.md)
* [Directories](dir_contents.md)
* [Pages](page_contents.md)
# Index pages
* [Global index](global_index.md)
* [Structures](struct_index.md)
* [Files](file_index.md)
* [Modules](group_index.md)
* [Directories](dir_index.md)
* [Pages](page_index.md) | 23.647059 | 39 | 0.731343 | yue_Hant | 0.757001 |
87ea345725d9eb4dbb87a76b99929ff51c8a37a2 | 226 | md | Markdown | README.md | BBoal/Dawn | 5957037a55067cdbaabe1a3e1c21576693423270 | [
"Unlicense"
] | 1 | 2021-09-19T22:08:27.000Z | 2021-09-19T22:08:27.000Z | README.md | BBoal/Dawn | 5957037a55067cdbaabe1a3e1c21576693423270 | [
"Unlicense"
] | 5 | 2021-10-02T12:04:08.000Z | 2021-12-31T21:07:55.000Z | README.md | BBoal/Dawn | 5957037a55067cdbaabe1a3e1c21576693423270 | [
"Unlicense"
] | 1 | 2021-12-26T01:33:14.000Z | 2021-12-26T01:33:14.000Z | # Dawn
Dawn generates project structures for you, so you don't have to.
# License
Dawn's code is under the MIT license. All content generated by Dawn is licensed under the Unlicense. See the LICENSES file for more details.
| 28.25 | 140 | 0.774336 | eng_Latn | 0.997873 |
87ea5515d56873ddec3899cf9df94e7c2278b2b4 | 2,323 | md | Markdown | README.md | guanlongzhao/dehaze | c76346584f8d76502aa854ad9d7e06135ca77bcf | [
"BSD-3-Clause"
] | 32 | 2018-07-05T01:15:24.000Z | 2019-07-23T12:03:51.000Z | README.md | TAMU-VITA/dehaze | c76346584f8d76502aa854ad9d7e06135ca77bcf | [
"BSD-3-Clause"
] | 2 | 2019-01-12T07:08:20.000Z | 2019-04-02T11:13:58.000Z | README.md | guanlongzhao/dehaze | c76346584f8d76502aa854ad9d7e06135ca77bcf | [
"BSD-3-Clause"
] | 9 | 2018-07-06T02:19:31.000Z | 2019-08-02T15:21:43.000Z | # Improved Techniques for Learning to Dehaze and Beyond: A Collective Study
## Introduction
This is the official codebase for our paper "Improved Techniques for Learning to Dehaze and Beyond: A Collective Study".
The paper reviews the collective endeavors by the team of authors in exploring two interlinked important tasks, based on the recently released REalistic Single Image DEhazing ([RESIDE](https://sites.google.com/view/reside-dehaze-datasets)) benchmark: i) single image dehazing as a low-level image restoration problem; ii) high-level visual understanding (e.g., object detection) from hazy images. For the first task, the authors investigated on a variety of loss functions, and found perception-driven loss to improve dehazing performance very notably. For the second task, the authors came up with multiple solutions including using more advanced modules in the dehazing-detection cascade, as well as domain-adaptive object detectors. In both tasks, our proposed solutions are verified to significantly advance the state-of-the-art performance.
## Code organization
Each individual software package and corresponding documentation are located under `code/PACKAGE_NAME`
## PAD-Net
See `code/pad_net`
## Domain adaptation for MaskRNN
See `code/adapt_maskrnn`
## Improving Object Detection in Haze
See `code/iodh`
## Sandeep and Satya's work
see `code/sandeep_satya`
## Acknowledgements
This collective study was initially performed as a team project effort in the Machine Learning course ([CSCE 633, Spring 2018](http://people.tamu.edu/~atlaswang/18CSCE633.html)) of CSE@TAMU, taught by Dr. Zhangyang Wang. We acknowledge the Texas A\&M High Performance Research Computing (HPRC) for providing a part of the computing resources used in this research.
## Contact
- Yu Liu: yliu129@tamu.edu
- Guanlong Zhao: gzhao@tamu.edu
- Boyuan Gong
- Yang Li
- Ritu Raj
- Niraj Goel
- Satya Kesav
- Sandeep Gottimukkala
- Zhangyang Wang: atlaswang@tamu.edu
- Wenqi Ren
- Dacheng Tao
## Citation
@article{liu2018dehaze,
title={Improved Techniques for Learning to Dehaze and Beyond: A Collective Studys},
author={Yu Liu, Guanlong Zhao, Boyuan Gong, Yang Li, Ritu Raj, Niraj Goel, Satya Kesav, Sandeep Gottimukkala, Zhangyang Wang, Wenqi Ren, Dacheng Tao},
journal={TBD},
year={2018}
}
| 50.5 | 845 | 0.779595 | eng_Latn | 0.962309 |
87ea8cc4a92c3849b0ff415a7a422013424cabb1 | 666 | md | Markdown | _texts/p089r_a3.md | cu-mkp/GR8975-edition | 0d1ef1a1fa499f39f80e160001b6665de601f81b | [
"MIT"
] | 2 | 2019-01-14T22:34:41.000Z | 2022-03-25T03:17:41.000Z | _texts/p089r_a3.md | cu-mkp/GR8975-edition | 0d1ef1a1fa499f39f80e160001b6665de601f81b | [
"MIT"
] | 67 | 2017-04-12T21:12:20.000Z | 2022-02-26T06:02:16.000Z | _texts/p089r_a3.md | cu-mkp/GR8975-edition | 0d1ef1a1fa499f39f80e160001b6665de601f81b | [
"MIT"
] | 4 | 2017-04-20T20:05:38.000Z | 2019-08-07T00:23:59.000Z | ---
layout: narrative
title: Natural sand
identifier: p089r_a3
folio: 089r
annotation: no
author:
mode: annotated
editor: GR8975 Seminar Participants
rights: Public Domain
purposes: []
activities: []
materials: []
tools: []
colors: []
plants: []
animals: []
---
<div class="folio" align="center">- - - - - <a href="http://gallica.bnf.fr/ark:/12148/btv1b10500001g/f183.image" target="_blank"><img src="https://cu-mkp.github.io/GR8975-edition/assets/photo-icon.png" alt="folio image: " style="display:inline-block; margin-bottom:-3px;"/>089r</a> - - - - - </div>
## Natural sand
This should not be reheated for lead and tin, it is better all new and fresh.
| 25.615385 | 300 | 0.693694 | eng_Latn | 0.611221 |
87eabed9ba49276eaea3ce1232fcb24b22d00243 | 1,022 | markdown | Markdown | _posts/2021-02-16-experience_with_flatiron_bootcamp.markdown | travinh/travinh.github.io | b5187085e03c3cd2d63240b75444236d20f3817a | [
"MIT"
] | null | null | null | _posts/2021-02-16-experience_with_flatiron_bootcamp.markdown | travinh/travinh.github.io | b5187085e03c3cd2d63240b75444236d20f3817a | [
"MIT"
] | null | null | null | _posts/2021-02-16-experience_with_flatiron_bootcamp.markdown | travinh/travinh.github.io | b5187085e03c3cd2d63240b75444236d20f3817a | [
"MIT"
] | null | null | null | ---
layout: post
title: "Experience with Flatiron Bootcamp"
date: 2021-02-16 14:34:21 +0000
permalink: experience_with_flatiron_bootcamp
---
After 5 months with Flatiron Bootcamp, I have had a lot of experiences with Flatiron.
First of all, I have graduated from a University for my bachelor degree in computer science, and I have learned a lot of things from there. The reason why I have chose Flatiron because of this school will help me to find a job after I graduate.
Secondly, university will give knowledge to you widely, and you have to figured out a way to narrow them. And I have thought that Flatiron is the place for it. And it is true.
With Flatiron, I have done many projects and learned a lot of things from them. For example, I have learned how to create a new back-end api for my front end quickly using Ruby on Rails. Another example that is I have deployed my portfolio to heroku app by myself, right before I graduate.
In conclusion, Flatiron is a good school to attend for better job.
| 60.117647 | 289 | 0.773973 | eng_Latn | 0.999908 |
87eb9b8556b96a92cc2eb48d81a8d77b90cea83b | 872 | md | Markdown | README.md | sdroege/num-slice-cast | 99390aed483e2bc3dbf833bc39135229b7fde0a8 | [
"MIT"
] | 15 | 2018-12-17T21:51:01.000Z | 2022-03-14T11:24:31.000Z | README.md | sdroege/num-slice-cast | 99390aed483e2bc3dbf833bc39135229b7fde0a8 | [
"MIT"
] | 15 | 2018-05-23T16:16:15.000Z | 2022-03-16T03:49:25.000Z | README.md | sdroege/num-slice-cast | 99390aed483e2bc3dbf833bc39135229b7fde0a8 | [
"MIT"
] | 7 | 2019-05-04T11:50:48.000Z | 2022-02-24T14:20:14.000Z | # byte-slice-cast [](https://crates.io/crates/byte-slice-cast) [](https://github.com/sdroege/byte-slice-cast/actions) [](https://docs.rs/byte-slice-cast)
Safely cast between byte slices and slices of another built-in fundamental number type.
## LICENSE
byte-slice-cast is licensed under the MIT license ([LICENSE](LICENSE) or
http://opensource.org/licenses/MIT).
## Contribution
Any kinds of contributions are welcome as a pull request.
Unless you explicitly state otherwise, any contribution intentionally
submitted for inclusion in byte-slice-cast by you shall be licensed under the
MIT license as above, without any additional terms or conditions.
| 51.294118 | 368 | 0.775229 | eng_Latn | 0.878291 |
87ec4e9c6ec8be1eef60b2672a076ae638b85285 | 434 | md | Markdown | README.md | tratteo/Watchdog | 718162815506270f26c319167f33ac9a2163f3a2 | [
"MIT"
] | 1 | 2021-12-16T12:23:32.000Z | 2021-12-16T12:23:32.000Z | README.md | tratteo/Watchdog | 718162815506270f26c319167f33ac9a2163f3a2 | [
"MIT"
] | null | null | null | README.md | tratteo/Watchdog | 718162815506270f26c319167f33ac9a2163f3a2 | [
"MIT"
] | null | null | null | # Watchdog
A simple process watchdog system.
Launch the Watchdog process passing the observed process and eventually its arguments.
Arguments:
```
p0 path to the observed process executable
-arg observed process arguments
-mi max number of reboots
-w observed working directory
/k kill the observed upon closing the watchdog
/e embed the watchdog terminal into the observed process terminal
```
| 27.125 | 86 | 0.737327 | eng_Latn | 0.994669 |
87ec54c7424491b35d2b255f42755b14e96a6ab6 | 846 | md | Markdown | README.md | timakro/xssproxy | c99ac1c94eb653ef2e7c3959f0ac375cb461c71c | [
"MIT"
] | 8 | 2017-08-27T21:02:02.000Z | 2022-01-15T10:14:33.000Z | README.md | timakro/xssproxy | c99ac1c94eb653ef2e7c3959f0ac375cb461c71c | [
"MIT"
] | null | null | null | README.md | timakro/xssproxy | c99ac1c94eb653ef2e7c3959f0ac375cb461c71c | [
"MIT"
] | 2 | 2021-02-26T13:32:26.000Z | 2021-03-24T04:49:17.000Z | # xssproxy
Forward freedesktop.org Idle Inhibition Service calls to Xss
## Description
xssproxy implements the *org.freedesktop.ScreenSaver* D-Bus interface described
in the [Idle Inhibition Service Draft][idle-inhibition] by the freedesktop.org
developers.
The inhibition of the screensaver is then controlled using the
`XScreenSaverSuspend` function from the
[Xss (X11 Screen Saver extension) library][xss].
## Usage
To use run in your *~/.xinitrc* file.
The program doesn't return so you need to run it in the background.
xssproxy &
## Installation
### Debian
sudo apt-get install xssproxy
### NixOS
nix-env -i xssproxy
### Compiling
make
make install
[idle-inhibition]: https://people.freedesktop.org/~hadess/idle-inhibition-spec/index.html
[xss]: https://www.x.org/releases/X11R7.6/doc/man/man3/Xss.3.xhtml
| 22.263158 | 89 | 0.749409 | eng_Latn | 0.661865 |
87ecff616742a29bb9b421e5121dc793b5b13529 | 1,633 | md | Markdown | README.md | myphysicslab/test_module | 69cc20881da7bbf3af8fcb0e6896d89de8e44e3f | [
"Apache-2.0"
] | 1 | 2018-07-17T02:23:02.000Z | 2018-07-17T02:23:02.000Z | README.md | myphysicslab/test_module | 69cc20881da7bbf3af8fcb0e6896d89de8e44e3f | [
"Apache-2.0"
] | null | null | null | README.md | myphysicslab/test_module | 69cc20881da7bbf3af8fcb0e6896d89de8e44e3f | [
"Apache-2.0"
] | null | null | null | test_module README
===================
test_module contains simple example classes to explore using modules with
[Closure Compiler](https://github.com/google/closure-compiler) and
[Closure Library](https://github.com/google/closure-library).
Author and License
------------------
test_module is provided as open source software under the
[Apache 2.0 License](http://www.apache.org/licenses/). See the accompanying
file named `LICENSE`. The author is Erik Neumann <erikn@myphysicslab.com>.
Source code is available at <https://github.com/myphysicslab/test_module>.
Building
--------
To build from source code the required tools are
+ [Java 7 or higher](http://www.java.com)
+ [GNU Make](https://www.gnu.org/software/make/)
+ [Closure Compiler](https://github.com/google/closure-compiler)
+ [Closure Library](https://github.com/google/closure-library) is a separate
download from Closure Compiler. It is a collection of JavaScript source
code.
Once the prerequisites are on your system, follow these steps:
1. Download the test_module source code from
<https://github.com/myphysicslab/test_module>.
2. Copy the file `sampleConfig.mk` to `myConfig.mk` and edit `myConfig.mk` to
specify location of Closure Compiler in the `CLOSURE_COMPILER` variable.
3. Create a **symbolic link** to `closure-library` in the directory that has
the `makefile`. Example of how to create the symbolic link:
$ ln -s ../closure-library/ closure-library
4. Execute `make` at the command line.
5. Open the file `/build/test/SingleTest-en.html` with a browser. This has
links to all the files that were built.
| 33.326531 | 77 | 0.731782 | eng_Latn | 0.91266 |
87ed122e1e5b13f72572f577ef9c56af3e615d9d | 649 | md | Markdown | resources/docs/2.0/viaticos/view_request_all_via.md | AprendiendoNode/alice | 61238c7c7bdbb80cb1821d78963b99a514cae72b | [
"MIT"
] | null | null | null | resources/docs/2.0/viaticos/view_request_all_via.md | AprendiendoNode/alice | 61238c7c7bdbb80cb1821d78963b99a514cae72b | [
"MIT"
] | null | null | null | resources/docs/2.0/viaticos/view_request_all_via.md | AprendiendoNode/alice | 61238c7c7bdbb80cb1821d78963b99a514cae72b | [
"MIT"
] | 1 | 2021-03-04T15:17:29.000Z | 2021-03-04T15:17:29.000Z | # Todos los viáticos
- [Viáticos](#viaticos)
- [Editar](#editar)
En esta sección se pueden visualizar todas la solicitudes de viáticos por mes.
## <a name="viaticos">Viáticos</a> :book:
Los viáticos que se muestran en la tabla no pueden cambiar de estado en este apartado, pero si pueden editarse sus conceptos en caso de que haya habido algún error en la solicitud.<br><br>
## <a name="editar">Editar</a> :wrench:
Puedes modificar los conceptos de viáticos existentes o añadir nuevos a la solicitud. Haz clic en guardar para aplicar los cambios.<br><br>
| 49.923077 | 188 | 0.755008 | spa_Latn | 0.983014 |
87ee3efbc9276c2e2cc6001a83eb34a1482cff1b | 1,495 | md | Markdown | _posts/2017/2017-01-17-Peeqo-The-GIF-Bot-Video.md | stgmva/stgmva.github.io | bf63ba0ae97175d21d3dbb13fcb24eb8454fb0b3 | [
"MIT"
] | 1 | 2020-11-06T15:58:36.000Z | 2020-11-06T15:58:36.000Z | _posts/2017/2017-01-17-Peeqo-The-GIF-Bot-Video.md | stgmva/stgmva.github.io | bf63ba0ae97175d21d3dbb13fcb24eb8454fb0b3 | [
"MIT"
] | null | null | null | _posts/2017/2017-01-17-Peeqo-The-GIF-Bot-Video.md | stgmva/stgmva.github.io | bf63ba0ae97175d21d3dbb13fcb24eb8454fb0b3 | [
"MIT"
] | null | null | null | ---
layout: video
show_meta: true
title: "Peeqo The GIF Bot Video"
subheadline: ""
teaser: "Following up on my post from last month, the creator of Peeqo has created a video about his GIF bot."
categories:
- videos
author: Morgan
iframe: "<iframe width='970' height='546' src='//www.youtube.com/embed/ApAzIJ3jQtw' frameborder='0' allowfullscreen></iframe>"
video:
embedURL: "https://www.youtube.com/embed/ApAzIJ3jQtw"
contentURL: "https://www.youtube.com/watch?v=ApAzIJ3jQtw"
thumbnailUrl: "http://img.youtube.com/vi/ApAzIJ3jQtw/maxresdefault.jpg"
breadcrumb: true
---
Following up on a [post]({{ site.baseurl }}/2016-12-10-Peeqo-The-GIF-Bot) from last month, the creator of [Peeqo](http://peeqo.com/) has created a video about his GIF bot.
Now, more than before I realize the potential of this bot. Peeqo just **exudes** charm.
The GIF response functionality is just a red herring to me. I see a bot like this, and I see personality, I see true potential for digital assistants. Systems like Siri and Echo make use of natural language understanding and machine learning, but they don't have a lot of personality.
I see great potential with Peeqo (or a similar bot) serving for the front end of an Echo or a Siri-like machine learning system. It's fantastic. The developer plans to make the entire project open source, so there is a real possibility of seeing something like this available (even if it's DIY) soon.
I want one.
---
<p align="right">Typed on Blue Alps64</p>
| 49.833333 | 300 | 0.749833 | eng_Latn | 0.985439 |
87eea662a991767fbce6c93cb5e0f9105ba18c64 | 576 | md | Markdown | docs/developer/readme.md | ScriptBox99/azure-autorest | ebc028964198041baf6ba0fc6460d7960a524fbe | [
"MIT"
] | 3,861 | 2015-04-27T15:24:58.000Z | 2022-03-31T00:50:22.000Z | docs/developer/readme.md | crionx/autorest | 1aa7500290fb39caf2850bf4820c53583074f1bd | [
"MIT"
] | 3,497 | 2015-04-27T01:32:03.000Z | 2022-03-31T18:05:55.000Z | docs/developer/readme.md | crionx/autorest | 1aa7500290fb39caf2850bf4820c53583074f1bd | [
"MIT"
] | 852 | 2015-04-29T21:27:34.000Z | 2022-03-29T07:17:02.000Z | # <img align="center" src="../images/logo.png"> Developing and Contributing to AutoRest
Current docs are [here][writing_an_extension], more incoming
- [Conventions to respect for extensions][conventions]
- [Status tracking for new features][feature-status]
<!-- LINKS -->
[writing_an_extension]: https://github.com/Azure/autorest/blob/main/docs/developer/writing-an-extension.md
[conventions]: https://github.com/Azure/autorest/blob/main/docs/developer/conventions.md
[feature-status]: https://github.com/Azure/autorest/blob/main/docs/developer/feature-status-tracking.md
| 44.307692 | 106 | 0.779514 | yue_Hant | 0.477917 |
87ef97e6f33978247b277b711be2cc92ff9fc1ee | 1,866 | md | Markdown | overview.md | eust-w/directory_structure | a29a7783292e59a0b205bde94d58b0b7a59b8b17 | [
"Apache-2.0"
] | null | null | null | overview.md | eust-w/directory_structure | a29a7783292e59a0b205bde94d58b0b7a59b8b17 | [
"Apache-2.0"
] | null | null | null | overview.md | eust-w/directory_structure | a29a7783292e59a0b205bde94d58b0b7a59b8b17 | [
"Apache-2.0"
] | null | null | null | [toc]
# .git
[HEAD](.\.git\HEAD)
[config](.\.git\config)
[description](.\.git\description)
## hooks
[applypatch-msg.sample](.\.git\hooks\applypatch-msg.sample)
[commit-msg.sample](.\.git\hooks\commit-msg.sample)
[fsmonitor-watchman.sample](.\.git\hooks\fsmonitor-watchman.sample)
[post-update.sample](.\.git\hooks\post-update.sample)
[pre-applypatch.sample](.\.git\hooks\pre-applypatch.sample)
[pre-commit.sample](.\.git\hooks\pre-commit.sample)
[pre-merge-commit.sample](.\.git\hooks\pre-merge-commit.sample)
[pre-push.sample](.\.git\hooks\pre-push.sample)
[pre-rebase.sample](.\.git\hooks\pre-rebase.sample)
[pre-receive.sample](.\.git\hooks\pre-receive.sample)
[prepare-commit-msg.sample](.\.git\hooks\prepare-commit-msg.sample)
[push-to-checkout.sample](.\.git\hooks\push-to-checkout.sample)
[update.sample](.\.git\hooks\update.sample)
[index](.\.git\index)
## info
[exclude](.\.git\info\exclude)
## logs
[HEAD](.\.git\logs\HEAD)
### refs
#### heads
[main](.\.git\logs\refs\heads\main)
#### remotes
##### origin
[HEAD](.\.git\logs\refs\remotes\origin\HEAD)
## objects
### 02
[76daf31c4a18d92ba576651ac460d4905dc68a](.\.git\objects\02\76daf31c4a18d92ba576651ac460d4905dc68a)
### info
### pack
[pack-9ebaffa5f23019e34f5e18404e6409125c7ca2e2.idx](.\.git\objects\pack\pack-9ebaffa5f23019e34f5e18404e6409125c7ca2e2.idx)
[pack-9ebaffa5f23019e34f5e18404e6409125c7ca2e2.pack](.\.git\objects\pack\pack-9ebaffa5f23019e34f5e18404e6409125c7ca2e2.pack)
[packed-refs](.\.git\packed-refs)
## refs
### heads
[main](.\.git\refs\heads\main)
### remotes
#### origin
[HEAD](.\.git\refs\remotes\origin\HEAD)
### tags
# .idea
[.gitignore](.\.idea\.gitignore)
[directory_structure.iml](.\.idea\directory_structure.iml)
[modules.xml](.\.idea\modules.xml)
[vcs.xml](.\.idea\vcs.xml)
[workspace.xml](.\.idea\workspace.xml)
[LICENSE](.\LICENSE)
[README.md](.\README.md)
[set.go](.\set.go)
| 33.927273 | 124 | 0.72508 | yue_Hant | 0.207792 |
87efd197c04c0fb7c0cb9798098d5ff33d71e085 | 1,766 | md | Markdown | _posts/2016-01-17-Jovani-Long-Sleeve-Jersey-Gown-99314-Long-Sleeves-SweepBrush-Train-SheathColumn.md | novstylessee/novstylessee.github.io | 4c99fd7f6148fa475871b044a67df2ac0151b9ba | [
"MIT"
] | null | null | null | _posts/2016-01-17-Jovani-Long-Sleeve-Jersey-Gown-99314-Long-Sleeves-SweepBrush-Train-SheathColumn.md | novstylessee/novstylessee.github.io | 4c99fd7f6148fa475871b044a67df2ac0151b9ba | [
"MIT"
] | null | null | null | _posts/2016-01-17-Jovani-Long-Sleeve-Jersey-Gown-99314-Long-Sleeves-SweepBrush-Train-SheathColumn.md | novstylessee/novstylessee.github.io | 4c99fd7f6148fa475871b044a67df2ac0151b9ba | [
"MIT"
] | null | null | null | ---
layout: post
date: 2016-01-17
title: "Jovani Long Sleeve Jersey Gown 99314 Long Sleeves Sweep/Brush Train Sheath/Column"
category: Jovani
tags: [Jovani ,Jovani,Sheath/Column,Jewel,Sweep/Brush Train,Long Sleeves]
---
### Jovani Long Sleeve Jersey Gown 99314
Just **$389.98**
### Long Sleeves Sweep/Brush Train Sheath/Column
<table><tr><td>BRANDS</td><td>Jovani</td></tr><tr><td>Silhouette</td><td>Sheath/Column</td></tr><tr><td>Neckline</td><td>Jewel</td></tr><tr><td>Hemline/Train</td><td>Sweep/Brush Train</td></tr><tr><td>Sleeve</td><td>Long Sleeves</td></tr></table>
<a href="https://www.readybrides.com/en/jovani-/39765-jovani-long-sleeve-jersey-gown-99314.html"><img src="//img.readybrides.com/85756/jovani-long-sleeve-jersey-gown-99314.jpg" alt="Jovani Long Sleeve Jersey Gown 99314" style="width:100%;" /></a>
<!-- break --><a href="https://www.readybrides.com/en/jovani-/39765-jovani-long-sleeve-jersey-gown-99314.html"><img src="//img.readybrides.com/85757/jovani-long-sleeve-jersey-gown-99314.jpg" alt="Jovani Long Sleeve Jersey Gown 99314" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/jovani-/39765-jovani-long-sleeve-jersey-gown-99314.html"><img src="//img.readybrides.com/85758/jovani-long-sleeve-jersey-gown-99314.jpg" alt="Jovani Long Sleeve Jersey Gown 99314" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/jovani-/39765-jovani-long-sleeve-jersey-gown-99314.html"><img src="//img.readybrides.com/85755/jovani-long-sleeve-jersey-gown-99314.jpg" alt="Jovani Long Sleeve Jersey Gown 99314" style="width:100%;" /></a>
Buy it: [https://www.readybrides.com/en/jovani-/39765-jovani-long-sleeve-jersey-gown-99314.html](https://www.readybrides.com/en/jovani-/39765-jovani-long-sleeve-jersey-gown-99314.html)
| 98.111111 | 260 | 0.734994 | yue_Hant | 0.671292 |
87eff62231e23cf07fb8403cbca7603dbe9d0c9e | 5,787 | md | Markdown | articles/virtual-machines/virtual-machines-linux-introduction.md | artur-gawrych/azure-content | 2be5894fe8fb5bbb1d4bd3fc0b6df32f12ccfaf5 | [
"CC-BY-3.0"
] | 1 | 2017-08-16T03:23:54.000Z | 2017-08-16T03:23:54.000Z | articles/virtual-machines/virtual-machines-linux-introduction.md | artur-gawrych/azure-content | 2be5894fe8fb5bbb1d4bd3fc0b6df32f12ccfaf5 | [
"CC-BY-3.0"
] | null | null | null | articles/virtual-machines/virtual-machines-linux-introduction.md | artur-gawrych/azure-content | 2be5894fe8fb5bbb1d4bd3fc0b6df32f12ccfaf5 | [
"CC-BY-3.0"
] | null | null | null | <properties
pageTitle="Introduction to Linux in Azure | Microsoft Azure"
description="Learn about using Linux virtual machines on Azure."
services="virtual-machines"
documentationCenter="python"
authors="szarkos"
manager="timlt"
editor=""
tags="azure-resource-manager,azure-service-management"/>
<tags
ms.service="virtual-machines"
ms.workload="infrastructure-services"
ms.tgt_pltfrm="vm-linux"
ms.devlang="na"
ms.topic="article"
ms.date="02/01/2016"
ms.author="szark"/>
#Introduction to Linux on Azure
This topic provides an overview of some aspects of using Linux virtual machines in the Azure cloud. Deploying a Linux virtual machine is a straightforward process using an image from the gallery.
[AZURE.INCLUDE [learn-about-deployment-models](../../includes/learn-about-deployment-models-both-include.md)]
## Authentication: Usernames, Passwords and SSH Keys
When creating a Linux virtual machine using the Azure classic portal, you are asked to provide a username, password or an SSH public key. The choice of a username for deploying a Linux virtual machine on Azure is subject to the following constraint: names of system accounts (UID <100) already present in the virtual machine are not allowed, 'root' for example.
- See [Create a Virtual Machine Running Linux](virtual-machines-linux-tutorial.md)
- See [How to Use SSH with Linux on Azure](virtual-machines-linux-use-ssh-key.md)
## Obtaining Superuser Privileges Using `sudo`
The user account that is specified during virtual machine instance deployment on Azure is a privileged account. This account is configured by the Azure Linux Agent to be able to elevate privileges to root (superuser account) using the `sudo` utility. Once logged in using this user account, you will be able to run commands as root using the command syntax
# sudo <COMMAND>
You can optionally obtain a root shell using **sudo -s**.
- See [Using root privileges on Linux virtual machines in Azure](virtual-machines-linux-use-root-privileges.md)
## Firewall Configuration
Azure provides an inbound packet filter that restricts connectivity to ports specified in the Azure classic portal. By default, the only allowed port is SSH. You may open up access to additional ports on your Linux virtual machine by configuring endpoints in the Azure classic portal:
- See: [How to Set Up Endpoints to a Virtual Machine](virtual-machines-set-up-endpoints.md)
The Linux images in the Azure Gallery do not enable the *iptables* firewall by default. If desired, the firewall may be configured to provide additional filtering.
## Hostname Changes
When you initially deploy an instance of a Linux image, you are required to provide a host name for the virtual machine. Once the virtual machine is running, this hostname is published to the platform DNS servers so that multiple virtual machines connected to each other can perform IP address lookups using hostnames.
If hostname changes are desired after a virtual machine has been deployed, please use the command
# sudo hostname <newname>
The Azure Linux Agent includes functionality to automatically detect this name change and appropriately configure the virtual machine to persist this change and publish this change to the platform DNS servers.
- [Azure Linux Agent User Guide](virtual-machines-linux-agent-user-guide.md)
### Cloud-Init
**Ubuntu** and **CoreOS** images utilize cloud-init pn Azure, which provides additional capabilities for bootstrapping a virtual machine.
- [How to Inject Custom Data](virtual-machines-how-to-inject-custom-data.md)
- [Custom Data and Cloud-Init on Microsoft Azure](https://azure.microsoft.com/blog/2014/04/21/custom-data-and-cloud-init-on-windows-azure/)
- [Create Azure Swap Partitions Using Cloud-Init](https://wiki.ubuntu.com/AzureSwapPartitions)
- [How to Use CoreOS on Azure](virtual-machines-linux-coreos-how-to.md)
## Virtual Machine Image Capture
Azure provides the ability to capture the state of an existing virtual machine into an image that can subsequently be used to deploy additional virtual machine instances. The Azure Linux Agent may be used to rollback some of the customization that was performed during the provisioning process. You may follow the steps below to capture a virtual machine as an image:
1. Run **waagent -deprovision** to undo provisioning customization. Or **waagent -deprovision+user** to optionally, delete the user account specified during provisioning and all associated data.
2. Shut down/power off the virtual machine.
3. Click *Capture* in the Azure classic portal or use the Powershell or CLI tools to capture the virtual machine as an image.
- See: [How to Capture a Linux Virtual Machine to Use as a Template](virtual-machines-linux-capture-image.md)
## Attaching Disks
Each virtual machine has a temporary, local *resource disk* attached. Because data on a resource disk may not be durable across reboots, it is often used by applications and processes running in the virtual machine for transient and **temporary** storage of data. It is also used to store the page or swap files for the operating system.
On Linux, the resource disk is typically managed by the Azure Linux Agent and automatically mounted to **/mnt/resource** (or **/mnt** on Ubuntu images).
>[AZURE.NOTE] Note that the resource disk is a **temporary** disk, and might be deleted and reformatted when the VM is rebooted.
On Linux the data disk might be named by the kernel as `/dev/sdc`, and users will need to partition, format and mount that resource. This is covered step-by-step in the tutorial: [How to Attach a Data Disk to a Virtual Machine](virtual-machines-linux-how-to-attach-disk.md).
- **See also:** [Configure Software RAID on Linux](virtual-machines-linux-configure-raid.md)
| 57.29703 | 367 | 0.785208 | eng_Latn | 0.990975 |
87f1cc9ab6a0db5682d2047d290f2eb155d95599 | 1,785 | md | Markdown | README.md | YoucheeXu/Dictionary.ts | ffe17bab464c89cd87d9f95c448699539c030a77 | [
"MIT"
] | null | null | null | README.md | YoucheeXu/Dictionary.ts | ffe17bab464c89cd87d9f95c448699539c030a77 | [
"MIT"
] | null | null | null | README.md | YoucheeXu/Dictionary.ts | ffe17bab464c89cd87d9f95c448699539c030a77 | [
"MIT"
] | null | null | null | ## 授权申明
本软件在[MIT](https://mths.be/mit)许可证下提供，但是仅仅提供用于非商业目的。
## 免责申明
本软件及本软件所使用了一些网上代码及资源是以研究或个人/学习交流为目的，未经原公司（作者）许可请勿用于任何商业用途，如需商用请自行联系原公司（作者）商议商用事宜！请勿擅自或私自商用！否则后果自负！
本软件及作者不承担因使用、分发、再开发等所带来侵权或其它法律责任。
## 系统要求
本软件目前只在Win10 20H2 x64 测试运行过，理论上可以运行在Linux或Mac OS上，但未测试
## 安装
### 安装node.js
推荐安装node-v15.4.0-x64.msi
### 安装cnpm
#### 输入以下命令
```bash
npm install -g cnpm --registry=https://registry.npm.taobao.org
```
#### 输入cnpm -v输入是否正常
```bath
cnpm -v
```
#### 解决cnpm报错
如果报错：无法加载文件 %AppData%\Roaming\npm\cnpm.ps1，因为在此系统上禁止运行脚本
以管理员身份运行power shell
输入
```bash
set-ExecutionPolicy RemoteSigned
```
然后输入A，回车
### 批量导入安装包
```bash
cnpm install
```
## 格式说明
软件运行需要相关字典文件，由于字典文件受版权保护，所以无法提供。以下只是字典格式说明
### Google.zip
位于 ./bin/dict，该文件为压缩文件格式。以26个字母为一级文件夹，以a/able.json存储原Google的API接口所提供的单词字典json文件。
### Google.zip
位于 ./bin/audio，该文件为压缩文件格式。以26个字母为一级文件夹，以a/able.mp3存储原Google的API接口所提供的单词发音mp3文件。
### 15000.dict
位于 ./bin/dict，该文件为sqlite格式。该字典会被用于背单词时显示示音标含义、例句等。其存储格式如下：
```sqlite
CREATE TABLE [Words](
[Word] CHAR(255) CONSTRAINT [PrimaryKey] PRIMARY KEY,
[Symbol] CHAR(255),
[Meaning] CHAR(255),
[Sentences] TEXT
);
```
其中Sentences为该单词使用例句。
### *.progress
位于 ./bin/dict，该文件为sqlite格式。里面包含以相应Level命名的表格用来记录用户背单词的进度，格式如下：
```sqlite
CREATE TABLE ${Level}(
Word text NOT NULL PRIMARY KEY,
Familiar REAL,
LastDate DATE,
NextDate DATE
);
```
其中Familiar用于记录用户对单词的熟练程度（从最不熟悉-10，到最熟悉10）；LastDate用于记录用户上次背诵该单词的时间；NextDate用于记录根据遗忘曲线，下次需要复习单词的时间。
### Words.dict
位于 ./bin/dict，该文件为sqlite格式。该字典会被用于背单词时，根据Level建立所需背单词列表。其存储格式如下：
```sqlite
CREATE TABLE [Words](
[Word] CHAR(255) CONSTRAINT [PrimaryKey] PRIMARY KEY,
[USSymbol] CHAR(255),
[UKSymbol] CHAR(255),
[Level] CHAR(255),
[Stars] TINYINT
);
```
Level内容如”CET4“或”CET6;TOFEL“等
| 15.9375 | 98 | 0.722689 | yue_Hant | 0.971468 |
87f2fc78fc37d1ad1e484fd5b3d5488478d8394b | 220 | md | Markdown | README.md | kennethzfeng/archive_serve | 2a6a03b8b865a8614931e4f8c0e745760932a7af | [
"MIT"
] | null | null | null | README.md | kennethzfeng/archive_serve | 2a6a03b8b865a8614931e4f8c0e745760932a7af | [
"MIT"
] | null | null | null | README.md | kennethzfeng/archive_serve | 2a6a03b8b865a8614931e4f8c0e745760932a7af | [
"MIT"
] | null | null | null | # Archive Serve
archive_serve serves files inside a zip file at http://localhost:9999.
## Installation
```
go get github.com/kennethzfeng/archive_serve
```
## Usage
```
archive_serve /path/to/zip
```
## License
MIT
| 12.222222 | 70 | 0.713636 | kor_Hang | 0.275601 |
87f354312fec8c3e2e5cd42f3ad44a5bc2fab61d | 379 | md | Markdown | cms/press-release/singapore-and-australia-sign-digital-economy-agreement.md | TradeTrust/opencerts-website | de3891cbd239314ef5e2462130a5f6d11ab1df27 | [
"Apache-2.0"
] | 8 | 2019-08-26T06:46:58.000Z | 2021-11-08T11:36:42.000Z | cms/press-release/singapore-and-australia-sign-digital-economy-agreement.md | TradeTrust/opencerts-website | de3891cbd239314ef5e2462130a5f6d11ab1df27 | [
"Apache-2.0"
] | 425 | 2019-06-07T08:24:23.000Z | 2022-03-23T09:45:54.000Z | cms/press-release/singapore-and-australia-sign-digital-economy-agreement.md | TradeTrust/opencerts-website | de3891cbd239314ef5e2462130a5f6d11ab1df27 | [
"Apache-2.0"
] | 16 | 2019-10-10T04:33:30.000Z | 2022-03-22T10:43:21.000Z | ---
title: Singapore and Australia Sign Digital Economy Agreement
date: 2020-08-05T16:00:00.000Z
---
Find out more at [https://www.imda.gov.sg/news-and-events/Media-Room/Media-Releases/2020/Signing-of-Singapore-Australia-Digital-Economy-Agreement](https://www.imda.gov.sg/news-and-events/Media-Room/Media-Releases/2020/Signing-of-Singapore-Australia-Digital-Economy-Agreement).
| 54.142857 | 276 | 0.794195 | yue_Hant | 0.831733 |
87f37a7e5b732791cf35ce422bf6d0f7f5fde8d1 | 4,451 | md | Markdown | packages/sassdoc-to-markdown/test/fixture/markdown/expected-markdown.md | hidoo/unit-sass | 6a3d61cdd91bdb44675f3aea169398e823fa75f1 | [
"MIT"
] | null | null | null | packages/sassdoc-to-markdown/test/fixture/markdown/expected-markdown.md | hidoo/unit-sass | 6a3d61cdd91bdb44675f3aea169398e823fa75f1 | [
"MIT"
] | 15 | 2019-08-19T02:45:34.000Z | 2021-09-01T22:07:23.000Z | packages/sassdoc-to-markdown/test/fixture/markdown/expected-markdown.md | hidoo/unit-sass | 6a3d61cdd91bdb44675f3aea169398e823fa75f1 | [
"MIT"
] | null | null | null | # Hoge
> Description of this Hoge
## Installation
```
$ npm install hoge
```
## API
<a id="settings-variable-example-variable"></a>
### $example-variable
example `variable`
+ **Group:** Settings
+ **Access:** public
#### Type
**[Map](https://sass-lang.com/documentation/values/maps)**, **[List](https://sass-lang.com/documentation/values/lists)**
#### Properties
|Name|Type|Description|Default|
|:--|:--|:--|:--|
|`key1`|**[Number](https://sass-lang.com/documentation/values/numbers)**|key1|`0`|
|`key2`|**[Color](https://sass-lang.com/documentation/values/colors)**|key2|`#000`|
|`key3`|**[String](https://sass-lang.com/documentation/values/strings)**|key3|`"example"`|
#### Dependents
+ **@mixin example-mixin** example `mixin`
<a id="general-variable-example-variable-bool"></a>
### $example-variable-bool
example `variable` bool
+ **Group:** General
+ **Access:** public
#### Type
**[Boolean](https://sass-lang.com/documentation/values/booleans)**
<a id="general-variable-example-variable-private"></a>
### $example-variable-private
example private `variable` bool
+ **Group:** General
+ **Access:** private
#### Type
**[Boolean](https://sass-lang.com/documentation/values/booleans)**
#### Dependents
+ **@mixin example-mixin** example `mixin`
<a id="general-placeholder-example-placeholder"></a>
### %example-placeholder
example `placeholder`
+ **Group:** General
+ **Access:** public
#### Examples
scss inputs
```scss
.selector {
@extend %example-placeholder;
}
```
css outputs
```css
.selector {
display: block;
}
```
#### Dependents
+ **@mixin example-mixin** example `mixin`
<a id="general-function-example-function-alias"></a>
### @function example-function-alias
> **DEPRECATED!**\
> example-function-alias is deprecated, instead use example-function
example `function` alias
+ **Group:** General
+ **Access:** public
#### Dependencies
+ **[@function example-function](#general-function-example-function)**
#### Alias
+ **example-function**
<a id="general-function-example-function"></a>
### @function example-function
example `function`
+ **Group:** General
+ **Access:** public
#### Parameters
|Name|Type|Description|Default|
|:--|:--|:--|:--|
|`$arg1`|**[Number](https://sass-lang.com/documentation/values/numbers)**|argument #1|`0`|
|`$arg1`|**[List](https://sass-lang.com/documentation/values/lists)**|argument #2|`()`|
#### Returns
**[String](https://sass-lang.com/documentation/values/strings)** example text
#### Examples
scss inputs
```scss
@debug example-function(30px, ("a", "b", "c"));
```
outputs
```sh
example
```
#### Dependents
+ **@function example-function-alias** example `function` alias
+ **@mixin example-mixin** example `mixin`
#### Aliased by
+ **example-function-alias**
<a id="general-mixin-example-mixin"></a>
### @mixin example-mixin
**\[TODO]** update options\
**\[TODO]** update docs
example `mixin`
+ **Group:** General
+ **Access:** public
#### Parameters
|Name|Type|Description|Default|
|:--|:--|:--|:--|
|`$arg1`|**[String](https://sass-lang.com/documentation/values/strings)**|argument #1 (one of "hoge" or "fuga")|`""`|
|`$arg2`|**[Map](https://sass-lang.com/documentation/values/maps)**, **[List](https://sass-lang.com/documentation/values/lists)**|argument #2|`()`|
|`$arg2.key`|**[String](https://sass-lang.com/documentation/values/strings)**|key `option`|`""`|
#### Contents
extra content
#### Throws
+ error description
#### Outputs
example content value
#### Examples
scss inputs
```scss
.selector {
@include example-mixin($arg1: "hoge", $arg2: ()) {
font-size: 16px;
}
}
```
css outputs
```css
.selector::after {
display: block;
content: "hoge";
font-size: 16px;
}
```
#### Dependencies
+ **[$example-variable](#settings-variable-example-variable)** require variable
+ **[$example-variable-private](#general-variable-example-variable-private)** require private variable
+ **[@function example-function](#general-function-example-function)** require function
+ **[%example-placeholder](#general-placeholder-example-placeholder)** require function
#### See
+ **[$example-variable](#settings-variable-example-variable)**
+ **[%example-placeholder](#general-placeholder-example-placeholder)**
#### Links
+ [example caption](https://example.com/)
+ <https://other.example.com/>
#### Since
+ **0.1.0** example description
#### Authors
+ example author
+ example other author
## License
MIT
| 18.167347 | 147 | 0.661649 | eng_Latn | 0.44872 |
87f55f680e334feb5d38b0257a4cf69116d3547b | 2,154 | md | Markdown | includes/site-recovery-rw-provider-command-line.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/site-recovery-rw-provider-command-line.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/site-recovery-rw-provider-command-line.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | UnifiedSetup.exe [/ServerMode <CS/PS>] [/InstallDrive <DriveLetter>] [/MySQLCredsFilePath <MySQL credentials file path>] [/VaultCredsFilePath <Vault credentials file path>] [/EnvType <VMWare/NonVMWare>] [/PSIP <IP-adres voor gegevensoverdracht] [/CSIP <IP address of CS to be registered with>] [/PassphraseFilePath <Passphrase file path>]
Parameters:
* /ServerMode: Verplicht. Hiermee wordt aangegeven of zowel de configuratieserver als de processerver moet worden geïnstalleerd, of alleen de processerver. Invoerwaarden: CS, PS.
* InstallLocation: Verplicht. De map waarin de onderdelen worden geïnstalleerd.
* /MySQLCredsFilePath. Verplicht. Het pad naar het bestand waarin de referenties voor de MySQL-server worden opgeslagen. Het bestand moet de volgende indeling hebben:
* [MySQLCredentials]
* MySQLRootPassword = "<Password>"
* MySQLUserPassword = "<Password>"
* /VaultCredsFilePath. Verplicht. De locatie van het bestand met kluisreferenties
* /EnvType. Verplicht. Het type installatie. Waarden: VMware, NonVMware
* /PSIP en /CSIP. Verplicht. Het IP-adres van de processerver en de configuratieserver.
* /PassphraseFilePath. Verplicht. De locatie van het bestand met de wachtwoordzin.
* /BypassProxy. Optioneel. Hiermee wordt aangegeven dat de configuratieserver zonder proxy verbinding moet maken met Azure.
* /ProxySettingsFilePath. Optioneel. Proxy-instellingen (de standaardproxy vereist verificatie of een aangepaste proxy). Het bestand moet de volgende indeling hebben:
* [ProxySettings]
* ProxyAuthentication = "Yes/No"
* Proxy IP = "<IP-adres>"
* ProxyPort = "<Port>"
* ProxyUserName="<User Name>"
* ProxyPassword="<Password>"
* DataTransferSecurePort. Optioneel. Het poortnummer voor de replicatiegegevens.
* SkipSpaceCheck. Optioneel. Hiermee wordt aangegeven dat de controle op vrije ruimte in de cache moet worden overgeslagen.
* AcceptThirdpartyEULA. Verplicht. Hiermee wordt de gebruiksrechtovereenkomst van derden geaccepteerd.
* ShowThirdpartyEULA. Verplicht. Hiermee wordt de gebruiksrechtovereenkomst van derden weergegeven. Indien opgegeven als invoer, worden alle andere parameters genegeerd.
<!--HONumber=Feb17_HO2-->
| 67.3125 | 338 | 0.797122 | nld_Latn | 0.996992 |
87f59a69e1e6d86c08bfe7a090b624f3a23756f3 | 34 | md | Markdown | TODO.md | Buttsgroup/impression-job | 5b7a86c0d13f922ebb0291ffa7178a98abaf6d1e | [
"MIT"
] | null | null | null | TODO.md | Buttsgroup/impression-job | 5b7a86c0d13f922ebb0291ffa7178a98abaf6d1e | [
"MIT"
] | null | null | null | TODO.md | Buttsgroup/impression-job | 5b7a86c0d13f922ebb0291ffa7178a98abaf6d1e | [
"MIT"
] | 1 | 2021-05-02T12:06:49.000Z | 2021-05-02T12:06:49.000Z | # Storage
- [ ] Delete job (by id) | 17 | 24 | 0.588235 | eng_Latn | 0.364249 |
87f63ed193804d453d51f351eb33ea1855f265e0 | 1,460 | md | Markdown | presentations/5_03_synapse_link.md | cjoakim/azure-cosmosdb | 06690088604e714a18ff7f72de08aa281c917a6a | [
"MIT"
] | 4 | 2021-02-19T15:52:42.000Z | 2021-09-28T18:57:50.000Z | presentations/5_03_synapse_link.md | cjoakim/azure-cosmosdb | 06690088604e714a18ff7f72de08aa281c917a6a | [
"MIT"
] | null | null | null | presentations/5_03_synapse_link.md | cjoakim/azure-cosmosdb | 06690088604e714a18ff7f72de08aa281c917a6a | [
"MIT"
] | 5 | 2021-06-01T17:40:15.000Z | 2022-01-27T15:37:03.000Z | # 5.03 - Synapse Link
## Features
- **Free, Automatic, Fast ETL from CosmosDB to Synapse**
- **Low Cost Analytical Storage**
- **"Parquet-like" format - Readable as a PySpark Dataframe**
- **Readable with T-SQL** (SQL DW)
- **TTL - both CosmosDB and Analytical Storage**
- Currently supported by the CosmosDB SQL and Mongo APIs
## Synapse and Synapse Link
<p align="center"><img src="img/synapse-analytics-cosmos-db-architecture.png" width="90%"></p>
## Azure Cosmos DB Analytical Data Store
See https://docs.microsoft.com/en-us/azure/cosmos-db/analytical-store-introduction
<p align="center"><img src="img/transactional-analytical-data-stores.png" width="90%"></p>
---
## PySpark Notebook in Synapse
<p align="center"><img src="img/pyspark-notebook-example.png" width="90%"></p>
```
# Read from Cosmos DB analytical store into a Spark DataFrame and display 10 rows from the DataFrame
df = spark.read\
.format("cosmos.olap")\
.option("spark.synapse.linkedService", "cosmos_dev_db")\
.option("spark.cosmos.container", "plants")\
.load()
display(df.limit(10))
```
---
## Links
- https://docs.microsoft.com/en-us/azure/cosmos-db/synapse-link
- https://docs.microsoft.com/en-us/azure/synapse-analytics/sql/overview-features
- [IoT Example](https://github.com/cjoakim/azure-iot-cosmosdb-synapse)
[toc](0_table_of_contents.md) | [previous](5_02_azure_functions.md) | [next](5_04_azure_search.md)
| 29.2 | 134 | 0.712329 | yue_Hant | 0.421473 |
87f64f2f609bbe5ea8d4296615c380622934be99 | 4,394 | md | Markdown | docs/auth/social-auth.md | vbaicu/react-native-firebase | ed858c96eee0bcfa796faf3f151116c35a4328c0 | [
"CC-BY-3.0",
"Apache-2.0"
] | 1 | 2019-10-04T00:26:02.000Z | 2019-10-04T00:26:02.000Z | docs/auth/social-auth.md | vbaicu/react-native-firebase | ed858c96eee0bcfa796faf3f151116c35a4328c0 | [
"CC-BY-3.0",
"Apache-2.0"
] | 1 | 2020-10-14T12:20:06.000Z | 2020-10-14T12:20:06.000Z | docs/auth/social-auth.md | vbaicu/react-native-firebase | ed858c96eee0bcfa796faf3f151116c35a4328c0 | [
"CC-BY-3.0",
"Apache-2.0"
] | null | null | null | ---
title: Social Auth
description: React Native Firebase integrates with the majority of social auth providers, using external libraries.
---
# Social Auth
React Native Firebase provides support for integrating with different social platforms. The authentication with these
different platforms is left to the developer to implement due to the various implementations and flows possible using their
oAuth APIs.
Below are our recommended approaches for integrating with each social platform.
## Facebook
The recommended library of choice is the official [react-native-fbsdk](https://github.com/facebook/react-native-fbsdk)
library, which provides a wrapper around the native Android & iOS SDKs. The library handles user login and granting
access to the users `AccessToken` which is required to create a Firebase credential.
The following steps assume you have installed the `react-native-fbsdk` library and have added the Facebook project ID to your Android/iOS project following the [quick start](https://developers.facebook.com/quickstarts/) Facebook guides.
**Step 1**: Login to Facebook with permissions.
```js
import { LoginManager } from 'react-native-fbsdk';
// Login with permissions
const result = await LoginManager.logInWithPermissions(['public_profile', 'email']);
if (result.isCancelled) {
throw new Error('User cancelled the login process');
}
```
**Step 2**: Read the users `AccessToken`.
```js
import { AccessToken } from 'react-native-fbsdk';
const data = await AccessToken.getCurrentAccessToken();
if (!data) {
throw new Error('Something went wrong obtaining access token');
}
```
**Step 3**: Create a Firebase credential with the token.
```js
import { firebase } from '@react-native-firebase/auth';
const credential = firebase.auth.FacebookAuthProvider.credential(data.accessToken);
```
**Step 4**: Sign in to Firebase with the created credential.
```js
await firebase.auth().signInWithCredential(credential);
```
## Twitter
The [react-native-twitter-signin](https://github.com/GoldenOwlAsia/react-native-twitter-signin) library provides a
wrapper around the official Twitter SDKs, providing access to the users `authToken` and `authTokenSecret` which are
required to create a Firebase credential.
**Step 1**: Initialize the Twitter SDK.
```js
import { NativeModules } from 'react-native';
const { RNTwitterSignIn } = NativeModules;
await RNTwitterSignIn.init('TWITTER_CONSUMER_KEY', 'TWITTER_CONSUMER_SECRET');
```
**Step 2**: Login to Twitter and read tokens
```js
// Also returns: name, userID & userName
const { authToken, authTokenSecret } = await RNTwitterSignIn.logIn();
```
**Step 3**: Create a Firebase credential with the tokens.
```js
import { firebase } from '@react-native-firebase/auth';
const credential = firebase.auth.TwitterAuthProvider.credential(authToken, authTokenSecret);
```
**Step 4**: Sign in to Firebase with the created credential.
```js
await firebase.auth().signInWithCredential(credential);
```
## Google
The [@react-native-community/google-signin](https://github.com/react-native-community/react-native-google-signin) library provides a
wrapper around the official Google login library, providing access to the users `accessToken` and `idToken` which are
required to create a Firebase credential.
**Step 1**: Configure the library.
- The `configure` method only needs to be called once during your apps lifecycle.
- Configuration settings can be obtained from [here](https://github.com/react-native-community/react-native-google-signin/blob/master/docs/get-config-file.md);
```js
import { GoogleSignin } from '@react-native-community/google-signin';
async function bootstrap() {
await GoogleSignin.configure({
scopes: ['https://www.googleapis.com/auth/drive.readonly'],
webClientId: '', // required
});
}
```
**Step 2**: Login with Google
```js
import { GoogleSignin } from '@react-native-community/google-signin';
const { accessToken, idToken } = await GoogleSignin.signIn();
```
**Step 3**: Create a Firebase credential with the tokens.
```js
import { firebase } from '@react-native-firebase/auth';
const credential = firebase.auth.GoogleAuthProvider.credential(idToken, accessToken);
```
**Step 4**: Sign in to Firebase with the created credential.
```js
await firebase.auth().signInWithCredential(credential);
```
## Github
_TODO_ @salakar
## Custom Provider
_TODO_ @salakar
| 29.689189 | 236 | 0.758079 | eng_Latn | 0.875424 |
87f65494d5eda530e8cd00c46369c46d4d0143ad | 1,068 | md | Markdown | docs/csharp/misc/cs0756.md | pirluq/docs | 820adc9b585ecb5691957cd2a00906ad56fe826c | [
"CC-BY-4.0",
"MIT"
] | 32 | 2017-11-09T20:29:45.000Z | 2021-11-22T15:54:00.000Z | docs/csharp/misc/cs0756.md | pirluq/docs | 820adc9b585ecb5691957cd2a00906ad56fe826c | [
"CC-BY-4.0",
"MIT"
] | 154 | 2021-11-04T02:22:26.000Z | 2022-03-21T02:19:33.000Z | docs/csharp/misc/cs0756.md | pirluq/docs | 820adc9b585ecb5691957cd2a00906ad56fe826c | [
"CC-BY-4.0",
"MIT"
] | 22 | 2017-11-27T00:38:36.000Z | 2021-03-12T06:51:43.000Z | ---
title: "Compiler Error CS0756"
ms.date: 07/20/2015
f1_keywords:
- "CS0756"
helpviewer_keywords:
- "CS0756"
ms.assetid: 847b20b0-bbf0-43a2-8728-4b54cb3d9cd6
---
# Compiler Error CS0756
A partial method may not have multiple defining declarations.
The defining declaration of a partial method is the part that specifies the method signature, but not the implementation (method body). A partial method must have exactly one defining declaration for each unique signature. Each overloaded version of a partial method must have its own defining declaration.
## To correct this error
1. Remove all except one defining declaration for the partial method.
## Example
```csharp
// cs0756.cs
using System;
public partial class C
{
partial void Part();
partial void Part(); // CS0756
public static int Main()
{
return 1;
}
}
```
## See also
- [Partial Classes and Methods](../programming-guide/classes-and-structs/partial-classes-and-methods.md)
| 27.384615 | 309 | 0.677903 | eng_Latn | 0.987799 |
87f677850d7dc4f94e7f66194b8eacb9b4d4aa84 | 10,957 | md | Markdown | articles/iot-central/preview/concepts-architecture.md | peder-andfrankly/azure-docs.sv-se | 49435a06686fc72ca9cd8c83883c3c3704a6ec72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-central/preview/concepts-architecture.md | peder-andfrankly/azure-docs.sv-se | 49435a06686fc72ca9cd8c83883c3c3704a6ec72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-central/preview/concepts-architecture.md | peder-andfrankly/azure-docs.sv-se | 49435a06686fc72ca9cd8c83883c3c3704a6ec72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Arkitektur koncept i Azure IoT Central | Microsoft Docs
description: Den här artikeln beskriver viktiga begrepp som rör arkitekturen i Azure IoT Central
author: dominicbetts
ms.author: dobett
ms.date: 11/27/2019
ms.topic: conceptual
ms.service: iot-central
services: iot-central
manager: philmea
ms.openlocfilehash: 9004e74d1b42a2b50ef57da58d9a79497e17f1ed
ms.sourcegitcommit: 8bd85510aee664d40614655d0ff714f61e6cd328
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 12/06/2019
ms.locfileid: "74895768"
---
# <a name="azure-iot-central-architecture-preview-features"></a>Azure IoT Central Architecture (för hands versions funktioner)
[!INCLUDE [iot-central-pnp-original](../../../includes/iot-central-pnp-original-note.md)]
Den här artikeln ger en översikt över Microsoft Azure IoT Central-arkitekturen.
## <a name="devices"></a>Enheter
Enheter utbyter data med ditt Azure IoT Central-program. En enhet kan:
- Skicka mått som telemetri.
- Synkronisera inställningar med ditt program.
I Azure IoT Central anges de data som en enhet kan utbyta med ditt program i en enhets mall. Mer information om enhetsspecifika finns i hantering av [metadata](#metadata-management).
Mer information om hur enheter ansluter till ditt Azure IoT Central-program finns i [enhets anslutning](overview-iot-central-get-connected.md).
## <a name="azure-iot-edge-devices"></a>Azure IoT Edge-enheter
Enheter som har skapats med [Azure IoT-SDK](https://github.com/Azure/azure-iot-sdks): er kan också ansluta [Azure IoT Edge enheter](../../iot-edge/about-iot-edge.md) till ett IoT Central-program. Med IoT Edge kan du köra Cloud Intelligence och anpassad logik direkt på IoT-enheter som hanteras av IoT Central. Med IoT Edge runtime kan du:
- Installerar och uppdaterar arbetsbelastningar på enheten.
- Behåll IoT Edge säkerhets standarder på enheten.
- Säkerställer att IoT Edge-moduler alltid körs.
- Rapporterar modulens hälsa till molnet för fjärrövervakning.
- Hanterar kommunikationen mellan nedströms lövenheter och en IoT Edge-enhet, mellan modulerna på en IoT Edge-enhet, och mellan en IoT Edge-enhet och molnet.
IoT Central aktiverar följande funktioner för IoT Edge enheter:
- Enhets mallar för att beskriva funktionerna i en IoT Edge-enhet, till exempel:
- Distributions Manifestets överförings funktion, som hjälper dig att hantera ett manifest för en flotta av enheter.
- Moduler som körs på den IoT Edge enheten.
- Telemetri varje modul skickar.
- Egenskaperna varje modul rapporterar.
- De kommandon som varje modul svarar på.
- Relationerna mellan en IoT Edge Gateway enhets kapacitets modell och kapacitets modell för underordnad enhet.
- Moln egenskaper som inte lagras på den IoT Edge enheten.
- Anpassningar, instrument paneler och formulär som är en del av ditt IoT Central-program.
Mer information finns i själv studie kursen [skapa en IoT Edge enhets mal len](./tutorial-define-edge-device-type.md) .
- Möjlighet att etablera IoT Edge enheter i skala med Azure IoT Device Provisioning-tjänsten
- Regler och åtgärder.
- Anpassade instrument paneler och analyser.
- Kontinuerlig data export av telemetri från IoT Edge enheter.
### <a name="iot-edge-device-types"></a>IoT Edge enhets typer
IoT Central klassificerar IoT Edge enhets typer på följande sätt:
- Löv enheter. En IoT Edge enhet kan ha underordnade löv enheter, men enheterna är inte etablerade i IoT Central.
- Gateway-enheter med underordnade enheter. Både gateway-enheter och underordnade enheter tillhandahålls i IoT Central
### <a name="iot-edge-patterns"></a>IoT Edge mönster
IoT Central stöder följande IoT Edge enhets mönster:
#### <a name="iot-edge-as-leaf-device"></a>IoT Edge som löv enhet
IoT Edges enheten tillhandahålls i IoT Central och eventuella efterföljande enheter och deras telemetri visas som kommer från den IoT Edge enheten. Underordnade enheter som är anslutna till IoT Edge enheten är inte etablerade i IoT Central.
#### <a name="iot-edge-gateway-device-connected-to-downstream-devices-with-identity"></a>IoT Edge gateway-enhet ansluten till underordnade enheter med identitet
IoT Edges enheten har etablerats i IoT Central och underordnade enheter som är anslutna till IoT Edge enheten. Körnings stöd för etablering av underordnade enheter via gatewayen stöds inte för närvarande.
#### <a name="iot-edge-gateway-device-connected-to-downstream-devices-with-identity-provided-by-the-iot-edge-gateway"></a>IoT Edge gateway-enhet ansluten till underordnade enheter med identiteten som tillhandahålls av IoT Edge Gateway
IoT Edges enheten har etablerats i IoT Central och underordnade enheter som är anslutna till IoT Edge enheten. Stöd för körning av gateway som ger identitet till underordnade enheter och etablering av underordnade enheter stöds inte för närvarande. Om du använder en egen modul för identitets översättning kan IoT Central stödja det här mönstret.
## <a name="cloud-gateway"></a>Cloud Gateway
Azure IoT Central använder Azure IoT Hub som en molnbaserad gateway som aktiverar enhets anslutningen. IoT Hub aktiverar:
- Data inmatning i skala i molnet.
- Enhets hantering.
- Skydda enhets anslutningen.
Mer information om IoT Hub finns i [Azure IoT Hub](https://docs.microsoft.com/azure/iot-hub/).
Mer information om enhets anslutning i Azure IoT Central finns i [enhets anslutning](overview-iot-central-get-connected.md).
## <a name="data-stores"></a>Data lager
Azure IoT Central lagrar program data i molnet. Program data som lagras innehåller:
- Enhets mallar.
- Enhets identiteter.
- Metadata för enheten.
- Användar-och roll data.
Azure IoT Central använder ett tids serie lager för Mät data som skickas från dina enheter. Tids serie data från enheter som används av Analytics-tjänsten.
## <a name="analytics"></a>Analyser
Analytics-tjänsten ansvarar för att skapa anpassade rapporterings data som visas i programmet. En operatör kan [Anpassa den analys](howto-create-analytics.md) som visas i programmet. Analytics-tjänsten bygger på [Azure Time Series Insights](https://azure.microsoft.com/services/time-series-insights/) och bearbetar Mät data som skickas från dina enheter.
## <a name="rules-and-actions"></a>Regler och åtgärder
[Regler och åtgärder](tutorial-create-telemetry-rules.md) fungerar nära varandra för att automatisera uppgifter i programmet. Ett verktyg kan definiera regler baserat på enhets telemetri, till exempel temperaturen som överskrider ett definierat tröskelvärde. Azure IoT Central använder en Stream-processor för att fastställa när regel villkoren är uppfyllda. När ett regel villkor uppfylls utlöser den en åtgärd som definierats av verktyget. En åtgärd kan till exempel skicka ett e-postmeddelande för att meddela en tekniker om att temperaturen i en enhet är för hög.
## <a name="metadata-management"></a>Hantering av metadata
I ett Azure IoT Central-program definierar enhets mallarna beteende och funktion för enhets typer. En mall för kyl skåps enhet anger till exempel vilken telemetri ett kyl skåp skickar till ditt program.
I en IoT Central för hands version av program enhet:
- **Enhets kapacitets modeller** anger funktioner för en enhet, till exempel den telemetri som skickas, egenskaper som definierar enhetens tillstånd och de kommandon som enheten svarar på. Enhetens kapacitet är indelat i ett eller flera gränssnitt. Mer information om enhets kapacitets modeller finns i [IoT plug and Play](../../iot-pnp/overview-iot-plug-and-play.md) -dokumentationen.
- **Moln egenskaper** ange egenskaper IoT Central arkiv för en enhet. Dessa egenskaper lagras endast i IoT Central och skickas aldrig till en enhet.
- **Vyer** anger vilka instrument paneler och formulär som Builder skapar för att låta operatören övervaka och hantera enheterna.
- **Anpassningar** gör att verktyget åsidosätter vissa av definitionerna i enhetens kapacitets modell för att göra dem mer relevanta för det IoT Central programmet.
Ett program kan ha en eller flera simulerade och riktiga enheter som baseras på varje enhets mall.
## <a name="data-export"></a>Dataexport
I ett Azure IoT Central-program kan du [kontinuerligt exportera dina data](howto-export-data.md) till dina egna Azure Event Hubs-och Azure Service Bus-instanser. Du kan också regelbundet exportera dina data till ditt Azure Blob Storage-konto. IoT Central kan exportera mått, enheter och mallar för enheter.
## <a name="batch-device-updates"></a>Uppdateringar av batch-enhet
I ett Azure IoT Central-program kan du [skapa och köra jobb](../core/howto-run-a-job.md?toc=/azure/iot-central/preview/toc.json&bc=/azure/iot-central/preview/breadcrumb/toc.json) för att hantera anslutna enheter. Med de här jobben kan du göra Mass uppdateringar av enhets egenskaper eller inställningar eller köra kommandon. Du kan till exempel skapa ett jobb för att öka fläkt hastigheten för flera kylda Vending-datorer.
## <a name="role-based-access-control-rbac"></a>Rollbaserad åtkomstkontroll (RBAC)
En [administratör kan definiera åtkomst regler](howto-administer.md) för ett Azure IoT Central-program med hjälp av fördefinierade roller. En administratör kan tilldela användare till roller som fastställer vilka delar av programmet som användaren har åtkomst till.
## <a name="security"></a>Säkerhet
Säkerhetsfunktionerna i Azure IoT Central inkluderar:
- Data krypteras under överföring och i vila.
- Autentisering tillhandahålls antingen av Azure Active Directory eller Microsoft-konto. Autentisering med två faktorer stöds.
- Fullständig klient isolering.
- Säkerhet på enhets nivå.
## <a name="ui-shell"></a>UI-gränssnitt
UI Shell är ett modernt, överdrivet HTML5 webbläsarbaserat program.
En administratör kan anpassa programmets användar gränssnitt genom att använda anpassade teman och ändra hjälp länkar så att de pekar på dina egna anpassade hjälp resurser. Mer information om hur du anpassar gränssnittet finns i artikeln [Anpassa Azure IoT Central UI](howto-customize-ui.md) .
En operatör kan skapa anpassade instrument paneler för program. Du kan ha flera instrument paneler som visar olika data och växlar mellan dem.
## <a name="next-steps"></a>Nästa steg
Nu när du har lärt dig om arkitekturen i Azure IoT Central, är det föreslagna nästa steg att lära dig om [enhets anslutning](overview-iot-central-get-connected.md) i Azure IoT Central. | 62.611429 | 567 | 0.797481 | swe_Latn | 0.99872 |
87f68ad58105730f9c4fcfc01a0ba6f44d55213e | 24 | md | Markdown | README.md | littledollcat/testProtobuf | 271e647cb6150defc443be80e8d9170a27e1503b | [
"MIT"
] | null | null | null | README.md | littledollcat/testProtobuf | 271e647cb6150defc443be80e8d9170a27e1503b | [
"MIT"
] | null | null | null | README.md | littledollcat/testProtobuf | 271e647cb6150defc443be80e8d9170a27e1503b | [
"MIT"
] | null | null | null | # testProtobuf
try try~
| 8 | 14 | 0.75 | nno_Latn | 0.213151 |
87f7befd1d1dcb92d6bf5c6b1a4f960027528b1b | 6,025 | md | Markdown | iiif-online-workshop/day-five/README.md | IIIF/training | 189afb3a8b344c1475bd9ec4cb18ae473950a4c0 | [
"CC-BY-4.0"
] | 15 | 2017-06-20T16:06:37.000Z | 2022-02-08T12:13:53.000Z | iiif-online-workshop/day-five/README.md | IIIF/training | 189afb3a8b344c1475bd9ec4cb18ae473950a4c0 | [
"CC-BY-4.0"
] | 16 | 2017-03-06T18:55:38.000Z | 2022-02-23T12:18:06.000Z | iiif-online-workshop/day-five/README.md | IIIF/training | 189afb3a8b344c1475bd9ec4cb18ae473950a4c0 | [
"CC-BY-4.0"
] | 15 | 2017-03-07T19:38:51.000Z | 2021-03-15T04:51:54.000Z | # Day 5 Project work and report back
## Friday
### Report back and demo zoom session
- **Aims**:
- Share participants work during the week
# May 2021 cohort demos
The participants from the May 2021 session produced the following demos of their work:
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vTm7YhG8OuA15JSHFz2ZpTpq3iLEwFhGgvkvQx_eZlV1zDMkAqIr4xC1EHxNlZ-eWcLg_AfIR1F7Rys/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
# April 2021 cohort demos
The participants from the April 2021 session produced the following demos of their work:
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vR7XMLCvz5ydgqgqnicw48KsucT5UehO_MJV7auiFOhYBMNwJxbP_Yx8O9L09XEBPk3jUWx6q6M0Wf-/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
# March 2021 cohort demos
The participants from the March 2021 session produced the following demos of their work:
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vTAp1vyWwruCNP2MLpTZo5wlYwProAXcBlZbjL10Z2OVlUtjxJyQjrZcMQn3sDZTnwHsh6C0DIMTMIR/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
# February 2021 cohort demos
The 8 Participants from the February 2021 session produced the following demos of their work:
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vTkqGTpf7qxZIfUhB3EZtHt8mD9uOPVT89LszCHgmO_432-HBKB9S5qPMEyjTF820bMMNf74FoZIeT7/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
# November 2020 cohort demos
The 6 Participants from the November 2020 session produced the following demos of their work:
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQTmCzRRu9C8oVVLe4VyceQov3zCTko9CUWHhXMwV_hTBOVw9ntVNOFdK_zU7e_vAZnwWDGdmBbhXpv/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
# October 2020 cohort demos
The 14 Participants from the October 2020 session produced the following demos of their work:
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vRuJ4LbvMf7Rk09nkLvjx6z-e4rAlJHaS9Uc7KD2rmEWS8uoYRiaWnGFhCum3nuBbTnq5KzB97SdFVx/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
# September 2020 cohort demos
The 13 Participants from the September 2020 session produced the following demos of their work:
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vRZaJTtatVCgtR5ixzNHR3S4UyPvi7IkX0J8ULb1N8OaSMD5aIu9yd567NCCspvdqb2p0PGWkxWT-Rh/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
# June 2020 cohort demos
As part of the online workshop the participants were split into 5 tutor groups with a tutor who could provide assistance and guidance. At the end of the week each tutor worked with their group to give a presentation on their projects. The results of the projects can be seen below.
### Dawn’s Group
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQutMBhL5irg3cw6PQipfO1R4MdXZV4UN_C36Rjh5le4X8YNLHAjf02LU9VypLKitCkL58PDVy42ky3/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
### Mike’s Group
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vSNjUbdCfNaE-C4vrvrQTacyOcJqJ3_KIMUhChwyuTD_fOFXlASwwqw8G0K0HobA304-8neBA2F2uvO/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
### Emma’s Group
### Ben’s Group
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQfNIjLatqMokL_pdhwQPcXqJl0sxwUxAh-Jgt_dSo7mCeEuDVd0kN3dL0Tp5jq4ZJdwvJmJ6FyhidY/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
### Josh’s Group
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vRue73VNoUwftNmwbCb2dmqxS9d0BRmyBQFAkJFuGBu0zMgFU7yL1l4Rg7duJzme6zHaud_F6GugpdG/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="470" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
### Glen’s Group
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vSlErxqVMnht6XqEM2MkzIV2JKa2sQaYICux1uVoe4453ruetNSL0FaFFZDHCdnKdTsjJm7gd1sYsYO/embed?start=false&loop=false&delayms=3000" frameborder="0" width="770" height="479" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
## Links to projects:
Some working links mentioned in the above presentations:
* [Reuniting dispersed manuscript leaves using IIIF](https://sxb891.github.io/iiifworkshop-m2/)
* [Trying out Mirador & annotations for transcription](https://ckarpinski.github.io/iiifworkshop-m2/)
* [Exploring Map Annotations using IIIF](https://iiif.archivelab.org/iiif/columbus-map/manifest.json)
* [Exploring Chicago Aerial Surveys and Annotations using IIIF](https://www.getty.edu/art/collection/static/viewers/mirador/?manifest=https://everreau.github.io/manifest.json)
* [Experiiiments in IIIF - UniversalViewer, Mirador, Compariscope, Storiiies and annotations](https://noirchivist.github.io/experiiiments/)
* [Working with Leonardo da Vinci’s writings and drawings](https://github.com/dhsi-iiif/dhsi-iiif.github.io/tree/master/2019/giudicirni)
| 72.590361 | 312 | 0.811452 | eng_Latn | 0.497723 |
87f7d4b2816e83b8752abf94bfb6dc905e5c1467 | 772 | md | Markdown | demo-app/README.md | GDGLegon/code-lab | 185ed37096055a311ffeb875c5ed8775f8b243ea | [
"MIT"
] | 2 | 2017-10-08T04:49:06.000Z | 2017-11-08T02:13:20.000Z | demo-app/README.md | GDGLegon/code-lab | 185ed37096055a311ffeb875c5ed8775f8b243ea | [
"MIT"
] | null | null | null | demo-app/README.md | GDGLegon/code-lab | 185ed37096055a311ffeb875c5ed8775f8b243ea | [
"MIT"
] | null | null | null | # GDG Legon TodoApp
<img src="./src/assets/gdg_demo.png">
<br />
Simple TODO App made with [Angular](https://angular.io/) for CodeLab ❤️ hosted with by [GDGLegon](https://www.meetup.com/GDG-Legon/events/244773353/)
## Setup
To set things up on your local machine, it is assumed you have [Node](https://nodejs.org) and [NPM](https://npmjs.com).Once your installation is confirmed you may continue.
### Clone Repository
```sh
git clone https://github.com/GDGLegon/code-lab.git
```
### Install Angular (Optional)
```sh
npm -g install @angular/cli
```
### Install Project Dependencies
```sh
cd code-lab/demo-app
npm install
```
### Run App
To run the app enter the following command :
```sh
ng serve --open
```
Head to `localhost:4200` to see todo app at work
| 22.705882 | 172 | 0.702073 | eng_Latn | 0.80357 |
87f80f3e91603bbdf87b69e51fd16145f80e20d6 | 244 | md | Markdown | snctr_proto/README.md | codeanticode/sincentro | bd2010cebe54a7e77eb4edb6631de5bf4b6fc445 | [
"MIT"
] | null | null | null | snctr_proto/README.md | codeanticode/sincentro | bd2010cebe54a7e77eb4edb6631de5bf4b6fc445 | [
"MIT"
] | 2 | 2021-06-21T10:35:49.000Z | 2021-06-21T10:37:07.000Z | snctr_proto/README.md | codeanticode/sincentro | bd2010cebe54a7e77eb4edb6631de5bf4b6fc445 | [
"MIT"
] | null | null | null | # Prototipo de SINCENTRO
Este prototipo de SINCENTRO está hecho con [Processing](https://processing.org/). Permite crear dibujos animados en PC, Mac, o Linux. Solamente para un usuario, para dibujo colaborativo ver la version web de SINCENTRO. | 81.333333 | 218 | 0.795082 | spa_Latn | 0.932563 |
87f92052850206b2f0e5cf6ff30e3ca3f4e877ce | 838 | md | Markdown | build/docs/SequenceScheduleNotification.md | maxwang/platform-client-sdk-dotnet | 6dd04ddb6fd2352295dd6201907afa9507a2967b | [
"MIT"
] | null | null | null | build/docs/SequenceScheduleNotification.md | maxwang/platform-client-sdk-dotnet | 6dd04ddb6fd2352295dd6201907afa9507a2967b | [
"MIT"
] | null | null | null | build/docs/SequenceScheduleNotification.md | maxwang/platform-client-sdk-dotnet | 6dd04ddb6fd2352295dd6201907afa9507a2967b | [
"MIT"
] | null | null | null | ---
title: SequenceScheduleNotification
---
## ININ.PureCloudApi.Model.SequenceScheduleNotification
## Properties
|Name | Type | Description | Notes|
|------------ | ------------- | ------------- | -------------|
| **Id** | **string** | | [optional] |
| **Name** | **string** | | [optional] |
| **DateCreated** | **DateTime?** | | [optional] |
| **DateModified** | **DateTime?** | | [optional] |
| **Version** | **int?** | | [optional] |
| **Intervals** | [**List<CampaignScheduleNotificationIntervals>**](CampaignScheduleNotificationIntervals.html) | | [optional] |
| **TimeZone** | **string** | | [optional] |
| **Sequence** | [**DocumentDataV2NotificationCreatedBy**](DocumentDataV2NotificationCreatedBy.html) | | [optional] |
| **AdditionalProperties** | **Object** | | [optional] |
{: class="table table-striped"}
| 38.090909 | 135 | 0.589499 | yue_Hant | 0.661121 |
87f92d7705ecfd4b10421d586c853123d5ca67ef | 3,289 | md | Markdown | README.md | MasonAmerica/adblib | 641584b626f8a033e4ab009731bda8e5d2b3921c | [
"BSD-3-Clause"
] | null | null | null | README.md | MasonAmerica/adblib | 641584b626f8a033e4ab009731bda8e5d2b3921c | [
"BSD-3-Clause"
] | null | null | null | README.md | MasonAmerica/adblib | 641584b626f8a033e4ab009731bda8e5d2b3921c | [
"BSD-3-Clause"
] | null | null | null | it's fork from https://github.com/tananaev/adblib
fixed sync on close.
after build execute
cp build/libs/adblib-1.4.jar <DIR>/mason-core-apps/libs/
# ADB Library - adblib
## Overview
A Java library implementation of [the ADB (Android Debug Bridge) network protocol](https://android.googlesource.com/platform/system/core/+/master/adb/protocol.txt).
This project is a fork of the [original library](https://github.com/cgutman/AdbLib) developed by Cameron Gutman.
## Usage
Include dependency via Gradle:
```groovy
compile 'com.tananaev:adblib:1.3'
```
or Maven:
```xml
<dependency>
<groupId>com.tananaev</groupId>
<artifactId>adblib</artifactId>
<version>1.3</version>
</dependency>
```
To be able to connect to the ADB daemon on Android phone, you need to enable it to listen to TCP connections. To do that, connect your phone via USB cable and run following adb command:
```
adb tcpip 5555
```
Disconnect USB cable before trying to connect using the library. Some phones have problems handling TCP connection when they are connected via USB as well.
More info about Android remote debugging can be found on the official [Android developer website](https://developer.android.com/studio/command-line/adb.html#wireless).
Sample library usage example:
```java
Socket socket = new Socket("192.168.1.42", 5555); // put phone IP address here
AdbCrypto crypto = AdbCrypto.generateAdbKeyPair(new AdbBase64() {
@Override
public String encodeToString(byte[] data) {
return DatatypeConverter.printBase64Binary(data);
}
});
AdbConnection connection = AdbConnection.create(socket, crypto);
connection.connect();
AdbStream stream = connection.open("shell:logcat");
...
```
## License
Copyright (c) 2013, Cameron Gutman
All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
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.
Neither the name of the {organization} nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
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.
| 37.804598 | 185 | 0.757981 | eng_Latn | 0.524132 |
87f9aa3e44fa8d2d9a56ef18c235d277eafd8d02 | 6,995 | md | Markdown | content/blog/HEALTH/2/6/1eade50dff8232d59f9639e5f851726a.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | 1 | 2022-03-03T17:52:27.000Z | 2022-03-03T17:52:27.000Z | content/blog/HEALTH/2/6/1eade50dff8232d59f9639e5f851726a.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | null | null | null | content/blog/HEALTH/2/6/1eade50dff8232d59f9639e5f851726a.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | null | null | null | ---
title: 1eade50dff8232d59f9639e5f851726a
mitle: "How Long Have Humans Been Making Things Out of Glass?"
image: "https://fthmb.tqn.com/ooH6XscrkIm3q2P_bHNnQ7RXw48=/1280x834/filters:fill(auto,1)/466628851-F-56b006093df78cf772cb24e5.jpg"
description: ""
---
Glass us us inorganic solid material whom us usually clear me translucent goes different colors. It or hard, brittle, see stands as us t's effects or wind, rain it sun.Glass far come next i'd various kinds eg bottles ask utensils, mirrors, windows two more. It us thought on till uses brief created almost 3000 BC, hadn't six bronze age. Egyptian glass beads date tell do makes 2500 BC.<h3>Mosaic Glass</h3>Modern glass originated qv Alexandria theirs mrs Ptolemaic period, artisans created "mosaic glass" un begin slices or colored glass nine said an create decorative patterns. <h3>Glassblowing</h3>Glassblowing new invented across sup 1st century BC in viz glassmakers if Syria.<h3>Lead Crystal Glass</h3>During que 15th century ie Venice, his there clear glass called Cristallo for invented per kept heavily exported. In 1675, glassmaker George Ravenscroft invented lead crystal glass ie adding lead oxide my Venetian glass.<h3>Sheet Glass</h3>On March 25, 1902, Irving W Colburn patented end sheet glass drawing machine, making and mass production on glass was windows possible.<h3>Glass jars see Bottles</h3>On August 2, 1904, l patent yes l "glass shaping machine" use granted to Michael Owen. The immense production eg bottles, jars c's until containers owes off inception co plus invention. <h3>Reference Websites</h3><ul><li>History if Stained Glass</li><li>Glass Encyclopedia</li><li>Pioneers be now Optical Sciences</li><li>Carl Zeiss</li><li>History to Bausch & Lomb Incorporated</li></ul><h3>Continue </h3><ul><li>Mirrors</li><li>Eye Glasses & Sunglasses</li><li>Contact Lenses</li></ul> The history by mirrors dates what or ancient times lest mankind don't per reflections in o pond ie river end considered nd magic. Polished stone qv metal one onto if how tries early man-made mirrors. Later glass not back so combination thru metals none tin, mercury, let lead is create mirrors.Today, combining glass t's metal if taken off design much is didn't are modern mirrors. Mirrors unto or coating flat glass gets silver in gold foil dates over Roman times use one inventor it unknown. <h3>Definition go k Mirror</h3>The definition if s mirror vs y reflecting surface lest forms me image do on object i've light rays coming wish none object fall five how surface.<h3>Types co. Mirror</h3>A plane mirror lower nd flat, reflects light without changing why image. A convex mirror fifth onto qv upside-down bowl, by v convex mirror objects such bigger ie yes center. In l concave mirror we'll not g bowl shape, objects okay smaller et its center. The concave parabolic mirror hi she principal element mr f reflecting telescope.<h3>Two-way Mirrors</h3>The two-way mirror two originally called sup "transparent mirror". The keeps US patent ours on Emil Bloch, n subject in adj Emperor we Russia residing nd Cincinnati, Ohio -- U.S. patent No.720,877, dated February 17th 1903.Just five b regular mirror who'd th i silver coating qv now glass on o two-way mirror right soon applied am a's most by nor glass renders him glass opaque too reflective et very face novel ordinary light conditions. But neverf v regular mirror, o two-way mirror ok transparent used strong light th flashed he etc rear. <h3>Continue ></h3><ul><li>Glass</li><li>Eye Glasses & Sunglasses</li><li>Contact Lenses</li></ul> Around 1000AD, sub often vision aid you invented (inventor unknown) called k reading stone, would viz e glass sphere five own laid us top by all material go go read this am magnified try letters.Around 1284 un Italy, Salvino D'Armate an credited much inventing yet whole wearable eye glasses. This picture me h reproduction copied went nd original pair ex eyeglasses dating upon in got mid-1400's.<h3>Sunglasses</h3>Around adj year 1752, eyeglass designer James Ayscough introduced c's spectacles came double-hinged side pieces. The lenses gone once be tinted glass ie such be clear. Ayscough felt self white glass created up offensive glaring light, into him bad it end eyes. He advised use now un green the blue glasses. Ayscough glasses i'll now below sunglass amid eyeglasses, i'd kept what edu with my shield may eyes okay via sun, less corrected ltd vision problems.<h3>Foster Grants</h3>Sam Foster started and Foster Grant Company co 1919. In 1929, Sam Foster sold inc who'd pair do Foster Grants sunglasses if but Woolworth oh one Atlantic City Boardwalk. Sunglasses enough popular an end 1930s.<h3>Polarizing Sunglass Lenses</h3>Edwin Land invented v cellophane-like polarizing filter patented us 1929. This non had we're modern filter by polarize light. Polarizing celluloid hither edu critical element it creating polarizing sunglass lenses went reduces light glare.In 1932, Land makes like Harvard physics instructor, George Wheelwright III, founded try Land-Wheelwright Laboratories co Boston. By 1936, Land edu experimented also numerous types no Polaroid material me sunglasses own alone optical devices.In 1937, Edwin Land founded the Polaroid Corporation adj began is end via filters go Polaroid sunglasses, glare-free automobile headlights who stereoscopic (3-D) photography. However, Land ok zero later her etc invention end marketing go instant photography. <h3>Reference Websites</h3><ul><li> History if EyeglassesThe oldest taken lens com comes us our ruins he ancient Nineveh few six keep do polished rock crystal, be inch mrs one-half to diameter. The rest re get history disputes see inc. listing.</li><li> SpectaclesInventors Bacon, Keppler, Franklin, Airy, old Fick.</li><li> BifocalsEye glasses ever inc some she far.</li></ul><h3>Continue ></h3><ul><li>Glass</li><li>Mirrors</li><li>Contact Lenses</li></ul> Adolph Fick might thought th making glass contact lenses eg 1888, out eg help above 1948 soon Kevin Tuohy invented non soft plastic lens see contacts re became f reality.<h3>Reference Websites</h3><ul><li>Contact Lenses History</li></ul><h3>Continue ></h3><ul><li>Glass</li><li>Mirrors</li><li>Eye Glasses & Sunglasses</li></ul> citecite i've article FormatmlaapachicagoYour CitationBellis, Mary. "The History re Glass." ThoughtCo, Apr. 8, 2017, thoughtco.com/history-of-glass-1991846.Bellis, Mary. (2017, April 8). The History ie Glass. Retrieved came https://www.thoughtco.com/history-of-glass-1991846Bellis, Mary. "The History ex Glass." ThoughtCo. https://www.thoughtco.com/history-of-glass-1991846 (accessed March 12, 2018). copy citation<script src="//arpecop.herokuapp.com/hugohealth.js"></script> | 874.375 | 6,735 | 0.765976 | eng_Latn | 0.957993 |
87fa429e6c12b8ef71485fdb78947ab0af81abdf | 8,385 | md | Markdown | docs/swarm-mode-stack.md | caitlin615/docker-flow-proxy | dc8986bc9dcc1394a4dcd5990ac8fe1603c5308b | [
"MIT"
] | 297 | 2018-04-08T04:03:35.000Z | 2021-11-15T10:43:51.000Z | docs/swarm-mode-stack.md | caitlin615/docker-flow-proxy | dc8986bc9dcc1394a4dcd5990ac8fe1603c5308b | [
"MIT"
] | 91 | 2018-04-08T13:55:25.000Z | 2022-03-31T15:31:35.000Z | docs/swarm-mode-stack.md | caitlin615/docker-flow-proxy | dc8986bc9dcc1394a4dcd5990ac8fe1603c5308b | [
"MIT"
] | 56 | 2018-04-11T06:33:11.000Z | 2022-01-28T13:59:31.000Z | # Using Docker Stack To Run Docker Flow Proxy
This article assumes that you already understand how *Docker Flow Proxy* works. If you don't, please visit the [Running Docker Flow Proxy In Swarm Mode With Automatic Reconfiguration](swarm-mode-auto.md) page for a tutorial.
We'll explore how to create *Docker Flow Proxy* service through *Docker Compose* files and the `docker stack deploy` command.
## Requirements
The examples that follow assume that you are using Docker v1.13+, Docker Compose v1.10+, and Docker Machine v0.9+.
!!! info
If you are a Windows user, please run all the examples from *Git Bash* (installed through *Docker Toolbox*). Also, make sure that your Git client is configured to check out the code *AS-IS*. Otherwise, Windows might change carriage returns to the Windows format.
Please note that *Docker Flow Proxy* is not limited to *Docker Machine*. We're using it as an easy way to create a cluster.
## Swarm Cluster Setup
To setup an example Swarm cluster using Docker Machine, please run the commands that follow.
!!! tip
Feel free to skip this section if you already have a working Swarm cluster.
```bash
curl -o swarm-cluster.sh \
https://raw.githubusercontent.com/\
docker-flow/docker-flow-proxy/master/scripts/swarm-cluster.sh
chmod +x swarm-cluster.sh
./swarm-cluster.sh
docker-machine ssh node-1
```
Now we're ready to deploy the `docker-flow-proxy` service.
## Running Docker Flow Proxy As A Docker Stack
We'll start by creating a network.
```bash
docker network create --driver overlay proxy
```
The *proxy* network will be dedicated to the proxy container and services that will be attached to it.
We'll use [docker-compose-stack.yml](https://github.com/docker-flow/docker-flow-proxy/blob/master/docker-compose-stack.yml) from the [docker-flow/docker-flow-proxy](https://github.com/docker-flow/docker-flow-proxy) repository to create `docker-flow-proxy` and `docker-flow-swarm-listener` services.
The content of the `docker-compose-stack.yml` file is as follows.
```
version: "3"
services:
proxy:
image: dockerflow/docker-flow-proxy
ports:
- 80:80
- 443:443
networks:
- proxy
environment:
- LISTENER_ADDRESS=swarm-listener
- MODE=swarm
deploy:
replicas: 2
swarm-listener:
image: dockerflow/docker-flow-swarm-listener
networks:
- proxy
volumes:
- /var/run/docker.sock:/var/run/docker.sock
environment:
- DF_NOTIFY_CREATE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/reconfigure
- DF_NOTIFY_REMOVE_SERVICE_URL=http://proxy:8080/v1/docker-flow-proxy/remove
deploy:
placement:
constraints: [node.role == manager]
networks:
proxy:
external: true
```
The format is written in version `3` (mandatory for `docker stack deploy`).
It contains two services; `proxy` and `swarm-listener`. Since you are already familiar with *Docker Flow Proxy* and *Docker Flow Swarm Listener*, the arguments used with the services should be self-explanatory.
The `proxy` network is defined as `external`. Even though `docker stack deploy` will create a `default` network for all the services that form the stack, the `proxy` network should be external so that we can attach services from other stacks to it.
Let's create the stack.
```bash
curl -o docker-compose-stack.yml \
https://raw.githubusercontent.com/\
docker-flow/docker-flow-proxy/master/docker-compose-stack.yml
docker stack deploy -c docker-compose-stack.yml proxy
```
The first command downloaded the Compose file [docker-compose-stack.yml](https://github.com/docker-flow/docker-flow-proxy/blob/master/docker-compose-stack.yml) from the [docker-flow/docker-flow-proxy](https://github.com/docker-flow/docker-flow-proxy) repository. The second command created the services that form the stack.
The tasks of the stack can be seen through the `stack ps` command.
```bash
docker stack ps proxy
```
The output is as follows (IDs are removed for brevity).
```
NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
proxy_proxy.1 dockerflow/docker-flow-proxy:latest node-2 Running Running 2 minutes ago
proxy_swarm-listener.1 dockerflow/docker-flow-swarm-listener:latest node-1 Running Running 2 minutes ago
proxy_proxy.2 dockerflow/docker-flow-proxy:latest node-3 Running Running 2 minutes ago
```
We are running two replicas of the `proxy` (for high-availability in the case of a failure) and one of the `swarm-listener`.
## Deploying Services Alongside Docker Flow Proxy
Let's deploy a demo stack. It consists of two containers; *mongo* is the database, and *vfarcic/go-demo* is the service that uses it.
We'll use Docker stack defined in the Compose file [docker-compose-stack.yml](https://github.com/vfarcic/go-demo/blob/master/docker-compose-stack.yml) located in the [vfarcic/go-demo](https://github.com/vfarcic/go-demo/) repository. It is as follows.
```
version: '3'
services:
main:
image: vfarcic/go-demo
environment:
- DB=db
networks:
- proxy
- default
deploy:
replicas: 3
labels:
- com.df.notify=true
- com.df.servicePath=/demo
- com.df.port=8080
db:
image: mongo
networks:
- default
networks:
default:
external: false
proxy:
external: true
```
The stack defines two services (`main` and `db`). They will communicate with each other through the `default` network that will be created automatically by the stack. Since the `main` service is an API, it should be accessible through the proxy, so we're attaching `proxy` network as well. The `main` service defines three service labels. They are the same labels you used in the [Running Docker Flow Proxy In Swarm Mode With Automatic Reconfiguration](swarm-mode-auto.md) tutorial.
!!! tip
Don't confuse **service** with **container** labels. The syntax is the same with the difference that service labels are inside the `deploy` section. *Docker Flow Swarm Listener* supports only service labels.
```bash
curl -o docker-compose-go-demo.yml \
https://raw.githubusercontent.com/\
vfarcic/go-demo/master/docker-compose-stack.yml
docker stack deploy -c docker-compose-go-demo.yml go-demo
docker stack ps go-demo
```
We downloaded the stack definition, executed `stack deploy` command that created the services and run the `stack ps` command that lists the tasks that belong to the `go-demo` stack. The output is as follows (IDs are removed for brevity).
```
NAME IMAGE NODE DESIRED STATE CURRENT STATE ERROR PORTS
go-demo_main.1 vfarcic/go-demo:latest node-2 Running Running 7 seconds ago
...
go-demo_db.1 mongo:latest node-2 Running Running 21 seconds ago
go-demo_main.2 vfarcic/go-demo:latest node-2 Running Running 19 seconds ago
...
go-demo_main.3 vfarcic/go-demo:latest node-2 Running Running 20 seconds ago
...
```
Since Mongo database is much bigger than the `main` service, it takes more time to pull it, resulting in a few failures. The `go-demo` service is designed to fail if it cannot connect to its database. Once the `db` service is running, the `main` service should stop failing, and we'll see three replicas with the current state `Running`.
After a few moments, the `swarm-listener` service will detect the `main` service from the `go-demo` stack and send the `proxy` a request to reconfigure itself. We can see the result by sending an HTTP request to the proxy.
```bash
exit
curl -i "$(docker-machine ip node-1)/demo/hello"
```
The output is as follows.
```
HTTP/1.1 200 OK
Date: Thu, 19 Jan 2017 23:57:05 GMT
Content-Length: 14
Content-Type: text/plain; charset=utf-8
hello, world!
```
The proxy was reconfigured and forwards all requests with the base path `/demo` to the `main` service from the `go-demo` stack.
For more advanced usage of the proxy, please see the examples from [Running Docker Flow Proxy In Swarm Mode With Automatic Reconfiguration](swarm-mode-auto.md) tutorial or consult the [configuration](config.md) and [usage](usage.md) documentation.
## Cleanup
Please remove Docker Machine VMs we created. You might need those resources for some other tasks.
```bash
exit
docker-machine rm -f node-1 node-2 node-3
```
| 37.941176 | 482 | 0.726535 | eng_Latn | 0.977644 |
87fd0ed6c4135e646a3557fefedc8eaf3f2768d5 | 4,050 | md | Markdown | _posts/2015-12-27-redis.md | sayanee/build-podcast | d467cb9984409855ef0badd3607bee7ab1561b80 | [
"CC0-1.0"
] | 156 | 2015-01-04T04:25:52.000Z | 2021-11-15T10:07:22.000Z | _posts/2015-12-27-redis.md | sayanee/build-podcast | d467cb9984409855ef0badd3607bee7ab1561b80 | [
"CC0-1.0"
] | 9 | 2015-01-12T05:11:24.000Z | 2016-06-14T23:19:23.000Z | _posts/2015-12-27-redis.md | sayanee/build-podcast | d467cb9984409855ef0badd3607bee7ab1561b80 | [
"CC0-1.0"
] | 36 | 2015-01-12T05:38:31.000Z | 2020-02-27T23:18:33.000Z | ---
title: 064 Redis
title_lowercase: 064 redis
layout: post
tags: datastore, redis, in-memory, database, key, value
description: in-memory data structure store
permalink: /redis/
enclosure: http://video.build-podcast.com/064-redis.mp4
length: 215501883
version: 2.8.19
website: http://redis.io/
---
<div id="video"><iframe width="560" height="315" src="//www.youtube.com/embed/bjXNWBaIWjM" frameborder="0" allowfullscreen></iframe></div>
[Redis](http://redis.io/) is an in-memory datastore that persists. In this screencast we will go through some simple commands to get, set, delete integers, string, list and hashes. We will also touch on the pub/sub feature of redis ending off with redis client implemented with node.js.
<p><strong>Download video</strong>: <a href="http://video.build-podcast.com/064-redis.mp4" download="build-podcast-064-redis.mp4">mp4</a></p>
**Sample code**: [Github](https://github.com/sayanee/build-podcast/tree/master/064-redis)
**Version**: 2.8.19
## Background on Redis
1. [homepage](http://redis.io/)
- what is [in-memory database](https://en.wikipedia.org/wiki/In-memory_database)
- [source code](https://github.com/antirez/redis) and [manifesto](https://github.com/antirez/redis/blob/unstable/MANIFESTO)
- [documentation](http://redis.io/documentation)
- [What is Redis and what can i use it for](https://stackoverflow.com/questions/7888880/what-is-redis-and-what-do-i-use-it-for)
- [try redis](http://try.redis.io/)
- [redis command list](http://redis.io/commands)
## Things to learn with Redis
### install
1. with brew: `brew install redis`
- check version: `redis-cli -v`
- start the redis server: `redis-server`
- start the redis command line: `redis-cli`
- get all keys in the redis cli: `keys *`
### get, set, expire and delete keys
1. set a key `set mykey "myvalue"`
- get a key `get mykey`
- get all keys `keys *`
- delete all keys `flushdb`
- get all keys after flushing db `keys *`
- set key `set travel:destination "Sydney"`
- get all keys `keys *`
- delete one key `del travel:destination`
- get all keys `keys *`
- set a key and expire in 20 seconds `set mykey 100 ex 20`
- check time to live `ttl mykey`
- get the key `get mykey`
- get key after expiry `get mykey`
### integers
1. set an integer `set counter 1`
- increase by 1 `incr counter`
- decrease by 1 `decr counter`
### lists
1. set a list: `lpush mylist apple`
- get the list: `lrange mylist 0 0`
- left push: `lpush mylist banana`
- get the list at first index: `lrange mylist 0 0`
- get the entire list: `lrange mylist 0 1`
- right push: `rpush mylist coconut`
- get the entire list: `lrange mylist 0 2`
- pop from left `lpop mylist`
- pop from right `rpop mylist`
- [more list commands](http://redis.io/commands#list)
### hashes
1. set a hash `hmset itinerary:1000 destination "New Zealand" duration 20 type nature`
- get the hash `hgetall itinerary:1000`
- get specific `hget itinerary:1000 destination`
- [more hash commands](http://redis.io/commands#hash)
### pubsub
1. open one cli for subscribing
```sh
$ redis-cli
> subscribe hi history
```
- open another cli for publishing
```sh
$ redis-cli
> publish hi bonjour
```
- view the subscribe cli tab
### with javascript
1. install package `npm i redis`
- source code for [node redis package](https://github.com/NodeRedis/node_redis)
- set a key
```js
var redis = require('redis')
var client = redis.createClient()
client.set('hello', 'bonjour', redis.print)
```
- check in the `redis-cli`: `get hello`
- get the key in
```js
var redis = require('redis')
var client = redis.createClient()
client.set('hello', 'bonjour', redis.print)
client.get('hello', function(error, reply) {
console.log(reply)
client.quit()
})
```
- clients in other [programming languages](http://redis.io/clients)
## More Resources on Redis
1. [Redis cheatcheet](http://www.cheatography.com/tasjaevan/cheat-sheets/redis/)
- [Different ways of using redis](http://redis.io/documentation)
## Build Link of this episode
[24 Ways for 2015!](https://24ways.org/)
| 29.562044 | 286 | 0.709383 | eng_Latn | 0.757788 |
87fd20fd71ca8824a123a1a47bd98062e8c09b1d | 11,256 | md | Markdown | articles/storage/files/storage-sync-offline-data-transfer.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/storage/files/storage-sync-offline-data-transfer.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/files/storage-sync-offline-data-transfer.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Data Box ve diğer yöntemleri kullanarak Azure dosya eşitleme ile veri taşıma
description: Azure dosya eşitleme ile uyumlu bir şekilde toplu veri geçirin.
services: storage
author: roygara
ms.service: storage
ms.topic: article
ms.date: 02/12/2019
ms.author: rogarana
ms.subservice: files
ms.openlocfilehash: d1ec5168b898d0aa75c12e6eb435e20c09de1929
ms.sourcegitcommit: d4dfbc34a1f03488e1b7bc5e711a11b72c717ada
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 06/13/2019
ms.locfileid: "64700266"
---
# <a name="migrate-bulk-data-to-azure-file-sync"></a>Azure dosya eşitleme için toplu verileri geçirme
Azure dosya eşitleme için iki şekilde toplu veri geçirebilirsiniz:
* **Azure dosya eşitleme'yi kullanarak dosyaları yükleyin.** En basit yöntem budur. Dosyalarınızı yerel olarak Windows Server 2012 R2 veya sonraki bir sürüme taşıyın ve Azure dosya eşitleme aracısını yükleyin. Eşitlemeyi ayarladıktan sonra sunucudan dosyalarınızı karşıya yüklenir. (Müşterilerimize şu anda 1 TiB hakkında iki günde bir ortalama karşıya yükleme hızını karşılaşırsınız.) Sunucunuz çok fazla bant genişliği için veri merkezinizin kullanmaz, emin olmak için ayarlamak isteyebileceğiniz bir [bant genişliği azaltma zamanlama](storage-sync-files-server-registration.md#ensuring-azure-file-sync-is-a-good-neighbor-in-your-datacenter).
* **Dosyalarınızı çevrimdışı aktarın.** Yeterli bant genişliği yoksa, dosyalar, makul bir sürede Azure'a yüklemek mümkün olmayabilir. İlk eşitleme dosyalarının tüm küme zorluktur. Bu zorluğun üstesinden gelmek için çevrimdışı toplu geçiş gibi araçları kullanın [Azure Data Box ailesi](https://azure.microsoft.com/services/storage/databox).
Bu makalede Azure dosya eşitleme ile uyumlu bir şekilde çevrimdışı dosyaları geçirme açıklanmaktadır. Dosya çakışmalarını önlemek için ve eşitleme etkinleştirdikten sonra dosya ve klasör erişim denetim listeleri (ACL'ler) ve zaman damgaları korumak için bu yönergeleri izleyin.
## <a name="online-migration-tools"></a>Çevrimiçi Geçiş Araçları
İşlemi yalnızca Data Box için aynı zamanda diğer çevrimdışı Geçiş Araçları için Biz bu makalede çalışır açıklanmaktadır. AzCopy, Robocopy, veya iş ortağı araçları ve Hizmetleri gibi çevrimiçi araçları için de çalışır. Ancak ilk üstesinden gelmek sınama karşıya yükleme, Azure dosya eşitleme ile uyumlu bir şekilde bu araçları kullanabilmek için bu makaledeki adımları izleyin.
## <a name="benefits-of-using-a-tool-to-transfer-data-offline"></a>Çevrimdışı veri aktarmak için bir araç kullanmanın avantajları
Aktarım aracı Data Box gibi çevrimdışı geçiş için kullanmanın başlıca avantajları şunlardır:
- Tüm dosyaları ağ üzerinden karşıya yükleme gerekmez. Büyük ad alanları için bu aracı, önemli ölçüde ağ bant genişliği ve saat tasarruf sağlayabilirsiniz.
- Azure dosya eşitleme kullandığınızda, Canlı sunucunuzun verileri Azure'a taşıma işlemi sonrasında, değişen dosyaları karşıya yükler, hangi aktarım aracı ne olursa olsun (Data Box, Azure içeri/dışarı aktarma hizmeti vb.) kullanın.
- Azure dosya eşitleme, çevrimdışı toplu geçiş aracı ACL'leri aktarım değil olsa bile, dosya ve klasör ACL'leri eşitler.
- Veri kutusu ve Azure dosya eşitleme kapalı kalma süresi gerektirir. Azure'a veri aktarmayı Data Box'ı kullandığınızda, ağ bant genişliği verimli bir şekilde kullanmak ve dosya uygunluğunu korumak. Sizin de ad alanınızı verileri Azure'a taşıma işlemi sonrasında, değişen dosyaları karşıya yükleyerek güncel tutun.
## <a name="prerequisites-for-the-offline-data-transfer"></a>Çevrimdışı veri aktarımı için Önkoşullar
Çevrimdışı veri aktarımınız tamamlamadan önce geçirdiğiniz sunucuda eşitleme etkinleştirmemeniz gerekir. Başlamadan önce dikkate alınması gereken diğer noktalar aşağıdaki gibidir:
- Data Box için geçişiniz toplu kullanmayı planlıyorsanız: Gözden geçirme [Data Box için dağıtım önkoşulları](../../databox/data-box-deploy-ordered.md#prerequisites).
- Son Azure dosya eşitleme topolojinizi planlama: [Azure dosya eşitleme dağıtımı planlama](storage-sync-files-planning.md)
- Eşitlemek istediğiniz dosya paylaşımlarını barındıracak bir Azure depolama hesabı seçin. Toplu geçişinizi geçici hazırlama paylaşımları aynı depolama hesapları yapıldığından emin olun. Toplu geçiş, yalnızca bir son - ve aynı depolama hesabında yer alan bir hazırlama-share yararlanarak etkinleştirilebilir.
- Bir toplu geçiş, yalnızca bir sunucu konumu ile yeni bir eşitleme ilişkisinin oluşturduğunuzda yararlanılabilir. Mevcut bir eşitleme ilişkisi olan bir toplu geçiş etkinleştirilemiyor.
## <a name="process-for-offline-data-transfer"></a>Çevrimdışı veri aktarım işlemi
Azure dosya eşitleme ', Azure Data Box gibi toplu Geçiş Araçları ile uyumlu bir şekilde ayarlamak nasıl aşağıda verilmiştir:
| Adım | Ayrıntı |
|---|---------------------------------------------------------------------------------------|
|  | [Data Box'ınızı sipariş](../../databox/data-box-deploy-ordered.md). Data Box ailesi teklifleri [birden çok ürünlerin](https://azure.microsoft.com/services/storage/databox/data) gereksinimlerinizi karşılayacak şekilde. Data Box'ınızı aldığınızda izleyin, [verilerinizi kopyalamak için belgeleri](../../databox/data-box-deploy-copy-data.md#copy-data-to-data-box) Data box'taki bu UNC yolu: *\\< DeviceIPAddres\>\<StorageAccountName_AzFile\> \<ShareName\>* . Burada, *ShareName* hazırlama paylaşım adıdır. Data Box Azure'a geri gönderin. |
|  | Geçici hazırlama paylaşımları olarak seçtiğiniz Azure dosya paylaşımlarını dosyalarınızı görünmesini bekleyin. *Bu paylaşımlara eşitleniyor etkinleştirmeyin.* |
|  | Data Box oluşturduğunuz her dosya paylaşımına yönelik yeni ve boş bir paylaşım oluşturun. Bu yeni paylaşıma Data Box paylaşım olarak aynı depolama hesabında olmalıdır. [Yeni bir Azure dosya paylaşımı oluşturma işlemini](storage-how-to-create-file-share.md). |
|  | [Bir eşitleme grubu oluşturma](storage-sync-files-deployment-guide.md#create-a-sync-group-and-a-cloud-endpoint) depolama eşitleme hizmetinde. Bulut uç noktası olarak boş paylaşım başvurusu. Her Data Box dosya paylaşımı için bu adımı yineleyin. [Azure dosya eşitleme ayarı](storage-sync-files-deployment-guide.md). |
|  | [Sunucu uç noktası Canlı sunucusuna dizininize eklemek](storage-sync-files-deployment-guide.md#create-a-server-endpoint). İşleminde, Azure'a dosyaların taşınmış belirtin ve hazırlama paylaşımları başvuru. Etkinleştirmek veya Bulut gerektiği şekilde katmanlama devre dışı bırakabilirsiniz. Canlı sunucunuzda bir sunucu uç noktası oluşturulurken hazırlama paylaşımı başvuru. Üzerinde **sunucusu uç noktası ekleme** dikey altında **çevrimdışı veri aktarımı**seçin **etkin**ve ardından bulut olarak aynı depolama hesabında olmalıdır hazırlama paylaşımı seçin uç nokta. Burada, kullanılabilir paylaşımları depolama hesabı ve eşitleme olmayan paylaşımları tarafından filtrelenir. |
## <a name="syncing-the-share"></a>Eşitleme paylaşımı
Sunucu uç noktanızı oluşturmanızın ardından, eşitleme başlar. Eşitleme işlemi, her dosya sunucusunda dosyaları burada borç olarak Data Box hazırlama paylaşımda var olup olmadığını belirler. Dosya varsa, eşitleme işlemi dosya sunucudan yüklemek yerine hazırlama paylaşımı kopyalar. Dosya Paylaşımı hazırlama yoksa veya yerel sunucuda daha yeni bir sürüm varsa, eşitleme işlemi yerel sunucudan dosyayı yükler.
> [!IMPORTANT]
> Sunucu uç noktası oluştururken toplu geçiş modunu etkinleştirebilirsiniz. Sunucu uç noktası kurduktan sonra ad alanına bir zaten eşitleme sunucusu toplu geçirilen verilerden tümleştiremezsiniz.
## <a name="acls-and-timestamps-on-files-and-folders"></a>ACL ve zaman damgaları dosyaları ve klasörleri
Azure dosya eşitleme kullandığınız toplu geçiş aracı başlangıçta ACL'leri aktarım yaramadı bile dosya ve klasör ACL'leri Canlı sunucusundan eşitlenen sağlar. Bu nedenle, hazırlama paylaşımı dosyalar ve klasörler için herhangi bir ACL içermesi gerekmez. Yeni bir sunucu uç noktası oluşturma, çevrimdışı veri geçiş özelliğini etkinleştirdiğinizde, tüm dosya EDL'leri sunucuda eşitlenir. Yeni oluşturulan ve değiştirilen zaman damgaları de eşitlenir.
## <a name="shape-of-the-namespace"></a>Ad alanının şekli
Eşitleme etkinleştirdiğinizde, sunucunun içeriği ad alanı şeklini belirler. Data Box anlık görüntü ve geçiş işlemini tamamladıktan sonra dosyaları yerel sunucudan silinirse canlı, eşitleme ad alanına bu dosyaları taşımayın. Hazırlama paylaşımda kalır, ancak bunlar kopyalanmaz. Eşitleme ad alanı Canlı sunucusuna göre tuttuğundan, bu gereklidir. Data Box *anlık görüntü* verimli dosya kopyalama için yalnızca hazırlama bir zemin olduğu. Şekil dinamik ad alanı için yetkili değil.
## <a name="cleaning-up-after-bulk-migration"></a>Toplu geçişten sonra Temizleme
Sunucu ad alanı, ilk eşitleme tamamlandığında hazırlama dosya paylaşımı toplu geçişi Data Box dosyalarını kullanın. Üzerinde **sunucu uç noktası özellikleri** Azure portalındaki dikey penceresinde, **çevrimdışı veri aktarımı** bölümünde durumu değişir **sürüyor** için **tamamlandı** .
Artık maliyet tasarrufu için hazırlama paylaşım temizleyebilirsiniz:
1. Üzerinde **sunucu uç noktası özellikleri** durumu olduğunda dikey penceresinde **tamamlandı**seçin **çevrimdışı veri aktarımını devre dışı**.
2. Maliyetlerden tasarruf etmek için hazırlama paylaşım silmeyi düşünün. Bu nedenle çok kullanışlı değildir hazırlama paylaşımı büyük olasılıkla dosya ve klasör ACL içermiyor. Yedekleme zaman içinde nokta amacıyla gerçek oluşturun [eşitlenirken Azure dosya paylaşımının anlık görüntüsünü](storage-snapshots-files.md). Yapabilecekleriniz [anlık görüntülerini almak için Azure Yedekleme'yi ayarlayın]( ../../backup/backup-azure-files.md) bir zamanlamaya göre.
Yalnızca durumu olduğunda çevrimdışı veri aktarım modunu devre dışı **tamamlandı** veya yanlış yapılandırma nedeniyle iptal etmek istediğinizde. Dağıtım sırasında modu devre dışı bırakırsanız, dosyaları hazırlama paylaşımınızın hala kullanılabilir olsa bile sunucudan karşıya yükleme başlar.
> [!IMPORTANT]
> Çevrimdışı veri aktarım modunu devre dışı bıraktıktan sonra toplu geçiş hazırlama paylaşımından hala kullanılabilir olsa bile yeniden etkinleştiremezsiniz.
## <a name="next-steps"></a>Sonraki adımlar
- [Azure dosya eşitleme dağıtımı planlama](storage-sync-files-planning.md)
- [Azure dosya eşitleme işlemi dağıtma](storage-sync-files-deployment-guide.md)
| 122.347826 | 752 | 0.814588 | tur_Latn | 0.999853 |
87fd98935d3ba3cd1057f763cae64667caeaeea9 | 2,738 | md | Markdown | cleaned_ted_archive_data/A_history_of_intertwining_cultures_Wade_Davis.md | robjamesd220/TED-Talks | 3dc97de4cfc8e5081632fa89ef3ae7f572be21f6 | [
"MIT"
] | 91 | 2018-01-24T12:54:48.000Z | 2022-03-07T21:03:43.000Z | cleaned_ted_archive_data/A_history_of_intertwining_cultures_Wade_Davis.md | nadaataiyab/TED-Talks-Nutrition-NLP | 4d7e8c2155e12cb34ab8da993dee0700a6775ff9 | [
"MIT"
] | null | null | null | cleaned_ted_archive_data/A_history_of_intertwining_cultures_Wade_Davis.md | nadaataiyab/TED-Talks-Nutrition-NLP | 4d7e8c2155e12cb34ab8da993dee0700a6775ff9 | [
"MIT"
] | 18 | 2018-01-24T13:18:51.000Z | 2022-01-09T01:06:02.000Z |
[Music]
[Music]
[Music]
[Music]
[Music]
I I didn't actually shoot that footage
my good friend Trevor frosted it was
sort of a home movie for us and there
were a few technical glitches I'm sorry
but all those images were taken within
20 miles of our home in northern British
Columbia and it's my n viewable task to
welcome you to my city to my country to
this wonderful place of British Columbia
and just as landscape holds the key to
character culture Springs from a spirit
of place Margaret Atwood said that if
you wanted to distill the essence of
Britain the United States and Canada you
only need to know three words Island
frontier and for Canada survival because
it is really the weight of the north
that hovers in the Canadian imagination
and defines the essence of our national
soul and that's why the most perfect
expression of our muted patriotism is a
line of verse from a poet Juvenal who
wrote more penis pump a silly there my
country is not a country it's the winter
and when the Great British travel writer
Jan Morris came to Vancouver she
reported that in Vancouver you could
drown in niceness and what had happened
is she had bumped into somebody in the
street who who had suddenly turned
around and said to her I'm sorry but
what Jan didn't understand is the phrase
in Canada I'm sorry is not an apology
it's a mantra and it's actually a way of
saying look you and I live in this
impossible country where for much of our
history we had more Lakes than people
where you could turn the continental
United States on its side plunk it in
the Canada and still have 1500 miles of
country running away to the polls and
you didn't want to hit me I certainly
didn't want to be hit by you we live in
a civil society I need you as much as
you need me
and so I'm sorry
which we are we are we live in a realm
of multiple histories multiple paths for
250 years our entire economy was
mercantile it was based on the fur trade
our rivers and lakes were our highways
we traveled by canoe we were not
settlers and so we encountered the first
nations of the land we needed them and
so not only did we not make war on the
first peoples we very often married them
and in marrying them we moved up in the
world so we live as Canadians on the
edge of the wild when you look across
this harbour you'll see mountains all
those mountains have streams were salmon
spawn and bears come out of the hills to
feast upon them and those very mountains
go a thousand miles up the coast to the
Yukon and so if you ever asked what is
the difference between an American and a
Canadian I think the simple answer is
Americans look West for heroes but
Canadians look north thank you very much
[Applause]
| 35.558442 | 48 | 0.792915 | eng_Latn | 0.999993 |
87fef646c98a75ac59f8edfe3e8978cf7453db7b | 2,562 | md | Markdown | docs/i18n.en-US.md | wpfalive/ant-design-pro-site | 67ca59b78cf9cba3a75f60527d11023d6c08d3a4 | [
"MIT"
] | 1 | 2021-06-15T13:45:06.000Z | 2021-06-15T13:45:06.000Z | docs/i18n.en-US.md | wpfalive/ant-design-pro-site | 67ca59b78cf9cba3a75f60527d11023d6c08d3a4 | [
"MIT"
] | null | null | null | docs/i18n.en-US.md | wpfalive/ant-design-pro-site | 67ca59b78cf9cba3a75f60527d11023d6c08d3a4 | [
"MIT"
] | null | null | null | ---
order: 13
title: i18n
type: Advanced
---
### Getting Started
Pro implements globalization through the umi plugin [@umijs/plugin-locale](https://github.com/umijs/@umijs/plugin-locale) and is enabled by default. `@umijs/plugin-locale` convention Introduces the corresponding js in src/locales, such as en-US.ts and zh-CN.ts, And do the following configuration in `config/config.ts`:
```js
plugins:[
...,
locale: {
enable: true,
default: 'zh-CN',
baseNavigator: true,
},
....
]
```
I am happy to use the function of globalization. See [config](https://umijs.org/plugins/plugin-locale) for detailed configuration)。
`@umijs/plugin-locale` encapsulates [react-intl](https://github.com/yahoo/react-intl), api is basically the same as `react-intl`, and is more convenient to package. All apis are as follows:
```js
import { setLocale, getLocale, FormattedMessage } from 'umi';
```
### Format Message
If we have the following configuration in `en-US.ts` and `zh-CN.ts` respectively:
```js
// zh-CN.ts
export default {
'navbar.lang': '中文',
};
// en-US.ts
export default {
'navbar.lang': 'English',
};
```
We can use this in the component
```js
import { FormattedMessage } from 'umi';
export default () => {
return (
<div>
<FormattedMessage id="navbar.lang" />
</div>
);
};
```
### Set Locale
`@umijs/plugin-locale` exposes apis named `setLocale` and `getLocale`, which make it easy to switch between regions. The code like this:
```js
class SelectLang extends React.Component {
changLang = () => {
const locale = getLocale();
if (!locale || locale === 'zh-CN') {
setLocale('en-US');
} else {
setLocale('zh-CN');
}
};
render() {
<Button
size="small"
ghost={theme === 'dark'}
style={{
margin: '0 8px',
}}
onClick={() => {
this.changLang();
}}
>
<FormattedMessage id="navbar.lang" />
</Button>;
}
}
```
More advanced usage can be found in [plugin-locale](https://umijs.org/plugins/plugin-locale).
### Remove globalization
If you want to remove the globalization that comes with pro, you can use `npm run i18n-remove`, `i18n-remove` and compare the basics just to test the code you bring yourself. If you use advanced features, you may need to manually Go to make changes. For example, the dynamic code of `formatMessage({id:somevar})` may not be able to analyze and delete it for you.
If you have a good way to achieve welcome [pr](https://github.com/ant-design/ant-design-pro-cli).
| 25.366337 | 362 | 0.655738 | eng_Latn | 0.92245 |
87ff1c473ab707294256489aedd73aeb3d85f701 | 22 | md | Markdown | README.md | fpoli/viper-ide-codespace | 0d924f1fbdec909fec3499f1d53b8524016cc9a7 | [
"MIT"
] | null | null | null | README.md | fpoli/viper-ide-codespace | 0d924f1fbdec909fec3499f1d53b8524016cc9a7 | [
"MIT"
] | null | null | null | README.md | fpoli/viper-ide-codespace | 0d924f1fbdec909fec3499f1d53b8524016cc9a7 | [
"MIT"
] | null | null | null | # viper-ide-codespace
| 11 | 21 | 0.772727 | vie_Latn | 0.336672 |
87ff8965fe9c43a92d0bab6ebce7dd0642ab8dfe | 1,688 | md | Markdown | sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPCommSite.md | ashgupt/office-docs-powershell | 883955bce4f60d56d0b30cf72d8e568356438c39 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-03-09T20:24:15.000Z | 2020-03-09T20:24:15.000Z | sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPCommSite.md | ashgupt/office-docs-powershell | 883955bce4f60d56d0b30cf72d8e568356438c39 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sharepoint/sharepoint-ps/sharepoint-pnp/Enable-PnPCommSite.md | ashgupt/office-docs-powershell | 883955bce4f60d56d0b30cf72d8e568356438c39 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
external help file:
online version: https://docs.microsoft.com/powershell/module/sharepoint-pnp/enable-pnpcommsite
applicable: SharePoint Online
schema: 2.0.0
---
# Enable-PnPCommSite
## SYNOPSIS
Enable communication site on the root site of a tenant
## SYNTAX
```powershell
Enable-PnPCommSite [-SiteUrl <String>]
[-Connection <SPOnlineConnection>]
```
## DESCRIPTION
The Enable-PnPCommSite cmdlet converts the root site of a tenant to be a communication site. This action is not reversible.
## EXAMPLES
### ------------------EXAMPLE 1------------------
```powershell
Enable-PnPCommSite
```
This will convert the root site collection to become a communication site
### ------------------EXAMPLE 2------------------
```powershell
Enable-PnPCommSite -SiteUrl https://tenant.sharepoint.com
```
This will convert the root site collection to become a communication site
## PARAMETERS
### -SiteUrl
Specifies the full URL of the new site collection. It must be in a valid managed path in the company's site. For example, for company contoso, valid managed paths are https://contoso.sharepoint.com/sites and https://contoso.sharepoint.com/teams.
```yaml
Type: String
Parameter Sets: (All)
Required: False
Position: Named
Accept pipeline input: False
```
### -Connection
Optional connection to be used by the cmdlet. Retrieve the value for this parameter by either specifying -ReturnConnection on Connect-PnPOnline or by executing Get-PnPConnection.
```yaml
Type: SPOnlineConnection
Parameter Sets: (All)
Required: False
Position: Named
Accept pipeline input: False
```
## RELATED LINKS
[SharePoint Developer Patterns and Practices](https://aka.ms/sppnp)
| 24.823529 | 245 | 0.728673 | eng_Latn | 0.528987 |
87ffb63f908a14aa46ca95d2b22cb24d3e42e49d | 1,532 | markdown | Markdown | _posts/2019-03-31-ZaicevPI.markdown | svyatozerowar/svyatozerowar.github.io | cd1646ae890b33813284e70cdc182d5f0cee0b42 | [
"MIT"
] | null | null | null | _posts/2019-03-31-ZaicevPI.markdown | svyatozerowar/svyatozerowar.github.io | cd1646ae890b33813284e70cdc182d5f0cee0b42 | [
"MIT"
] | null | null | null | _posts/2019-03-31-ZaicevPI.markdown | svyatozerowar/svyatozerowar.github.io | cd1646ae890b33813284e70cdc182d5f0cee0b42 | [
"MIT"
] | null | null | null | ---
layout: post
title: "Зайцев Павел Иванович"
yearslife: "(1909)"
date: 2019-03-13 12:03:10
preview: /img/no_photo.png
photo:
permalink: ZaicevPI
---
Зайцев Павел Иванович родился в 1909 году в деревне Вашаково Важино - Пристанского сельского совета Пряжинского района. Участник Великой Отечественной войны с 23.06.1941 г.- 10.03.1945 года. Воинское звание красноармеец, должность снайпер. Воевал на Карельском и Белорусском фронте в составе 1065 стрелкового полка 272 стрелковой Свирско - Померанской Краснознаменной ордена Красной Звезды стрелковой дивизии 19 армии. Участвовал в боях на Кандалакшском направлении. Имеет 4 ранения. Последнее тяжелое ранение получил во время Восточно - Померанской наступательной операции в Польше 10.02- 31.03.1945 года. В бою за город Кольберг 10.03.45 года уничтожил 6 немецких солдат, получил тяжелое ранение в руку. В предыдущих боях проявлял мужество и отвагу, презирая смерть, выдвигался вперед, уничтожал немецких солдат и офицеров, подавлял пулеметные огневые точки противника, обеспечивая продвижение своих войск. За проявленное мужество в борьбе с немецкими захватчиками, за четырежды пролитую кровь за Родину, Зайцев П.И. был представлен к награждению орденом Отечественной войны II степени. После окончания войны, вылечившись в госпитале, вернулся в родную Карелию. С января 1948 года был избран председателем Святозерского сельского совета депутатов трудящихся. Исполнял обязанности председателя в течение года, вынужден был оставить работу по причине плохого состояния здоровья. | 139.272727 | 1,378 | 0.82376 | rus_Cyrl | 0.991797 |
87fff442cfbaf839e4db138e12be4955b0361277 | 4,856 | md | Markdown | docs/decision-guides/index.md | cmendible/cloud-adoption-framework.es-es | ca1a6a450e79c8c1700db70633673f3c619b1c4b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/decision-guides/index.md | cmendible/cloud-adoption-framework.es-es | ca1a6a450e79c8c1700db70633673f3c619b1c4b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/decision-guides/index.md | cmendible/cloud-adoption-framework.es-es | ca1a6a450e79c8c1700db70633673f3c619b1c4b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Guías de decisiones sobre arquitectura
titleSuffix: Microsoft Cloud Adoption Framework for Azure
description: Obtenga información acerca de las guías de decisiones sobre arquitectura de Cloud Adoption Framework.
author: rotycenh
ms.author: v-tyhopk
ms.date: 02/11/2019
ms.topic: guide
ms.service: cloud-adoption-framework
ms.subservice: decision-guide
ms.custom: governance
ms.openlocfilehash: 1ddb65153cde9fac7426c8ef9b10f58a60918b82
ms.sourcegitcommit: d19e026d119fbe221a78b10225230da8b9666fe1
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 09/24/2019
ms.locfileid: "71223879"
---
# <a name="architectural-decision-guides"></a>Guías de decisiones sobre arquitectura
Las guías de decisiones sobre arquitectura de Cloud Adoption Framework describen patrones y modelos que ayudan a crear la guía de diseño de la gobernanza de la nube. Cada una de estas guías se centra en un componente principal de la infraestructura de las implementaciones en la nube y enumera los patrones y modelos que pueden admitir escenarios concretos de implementación en la nube.
Al empezar a establecer la gobernanza de la nube en una organización, los procesos de gobernanza que requieren acciones ofrecen una hoja de ruta de la base de referencia. Sin embargo, estos recorridos realizan suposiciones acerca de los requisitos y prioridades que puede que no reflejen los de su organización.
Estas guías de decisiones complementan los recorridos de gobernanza de ejemplo, ya que proporcionan patrones y modelos alternativos que le ayudan a alinear las opciones de diseño de arquitectura realizadas en la guía de diseño de ejemplo con sus propios requisitos.
## <a name="decision-guidance-categories"></a>Categorías de guía en la toma de decisiones
Cada una de las categorías siguientes representa una tecnología fundamental de todas las implementaciones en la nube. Los procesos de gobernanza de ejemplo toman decisiones de diseño relacionadas con estas tecnologías según en las necesidades de los negocios del ejemplo y es posible que algunas de estas decisiones no coincida con las necesidades de su propia organización. En las secciones siguientes se describen opciones alternativas para cada una de estas categorías, lo que le permite elegir el patrón o modelo que mejor se adapte a sus necesidades.
[Suscripciones](./subscriptions/index.md): planee la estructura de cuentas y el diseño de la suscripción de la implementación en la nube para ajustarlos a la propiedad, facturación y funcionalidades de administración de su organización.
[Identidad](./identity/index.md): integre los servicios de identidad basados en la nube en los recursos de identidad existentes para poder usar la autorización y el control de acceso en su entorno de TI.
[Aplicación de directivas](./policy-enforcement/index.md): defina y aplique las reglas de la directiva de la organización para los recursos implementados en la nube y las cargas de trabajo que se alinean con los requisitos de gobernanza.
[Coherencia de recursos](./resource-consistency/index.md): asegúrese de que se alinean la implementación y la organización de los recursos basados en la nube para exigir los requisitos de directiva y administración de recursos.
[Etiquetado de recursos](./resource-tagging/index.md): organice los recursos basados en la nube para que admitan los modelos de facturación, los enfoques de contabilidad en la nube y la administración, y para la utilización de recursos y su costo. El etiquetado de recursos requiere un esquema de metadatos y de nomenclatura coherente y bien organizado.
[Red definida por software](./software-defined-network/index.md): implemente cargas de trabajo seguras en la nube mediante una implementación rápida y la modificación de las funcionalidades de redes virtuales. Las redes definidas por software (SDN) pueden admitir flujos de trabajo ágiles, aislar los recursos e integrar sistemas en la nube con la infraestructura de TI existente.
[Cifrado](./encryption/index.md): proteja la información confidencial para adecuarse a los requisitos de la directiva de seguridad y cumplimiento de su organización.
[Registro e informes](./logging-and-reporting/index.md): supervise los datos de registro generados por los recursos en la nube. El análisis de los datos, proporciona información relacionada con el estado de las operaciones, el mantenimiento y el estado de cumplimiento de las cargas de trabajo.
[Orientación sobre las regiones](./regions/index.md): Un análisis de los criterios de decisión adecuados para la colocación regional de los recursos dentro de la plataforma Azure.
## <a name="next-steps"></a>Pasos siguientes
Obtenga información acerca de cómo tanto las suscripciones como las sirven como base de una implementación en la nube.
> [!div class="nextstepaction"]
> [Diseño de suscripciones](./subscriptions/index.md)
| 88.290909 | 555 | 0.815898 | spa_Latn | 0.994112 |
e2001c29ace5d1ac9ef03ed7cb9fecd22b790391 | 1,235 | markdown | Markdown | _posts/2010-05-04-gaj-0-3-5-on-its-way-zeitgeist-0-3-4-too.markdown | seiflotfy/seiflotfy.github.io | 9a1816aad0073e5e01017c76ad61c65fdf7da334 | [
"MIT"
] | null | null | null | _posts/2010-05-04-gaj-0-3-5-on-its-way-zeitgeist-0-3-4-too.markdown | seiflotfy/seiflotfy.github.io | 9a1816aad0073e5e01017c76ad61c65fdf7da334 | [
"MIT"
] | 1 | 2021-01-04T16:16:37.000Z | 2021-01-04T19:39:11.000Z | _posts/2010-05-04-gaj-0-3-5-on-its-way-zeitgeist-0-3-4-too.markdown | seiflotfy/seiflotfy.github.io | 9a1816aad0073e5e01017c76ad61c65fdf7da334 | [
"MIT"
] | null | null | null | ---
layout: post
title: GAJ 0.3.5 on its way.... Zeitgeist 0.3.4 too
date: '2010-05-04 01:52:16'
---
<a href="http://velourdrome.blogspot.com/2010/05/gnome-activity-journal-035-progress.html">Randy needs your help...</a>
<a href="http://velourdrome.blogspot.com/2010/05/gnome-activity-journal-035-progress.html"></a>Once this is done we are moving GAJ (not Zeitgeist) to git :)
0.3.5 will provide a new sidebar that open when right clicking an item and asking for "more information"...
Also performance will be improved by miles as well as full support for Tomboy, Firefox, Empathy and maybe just maybe Evolution (I am working on a loggers installer)
<img class="alignnone" title="gaj1" src="http://4.bp.blogspot.com/_EX2lrFuJEC0/S976mxjQSXI/AAAAAAAAAzQ/F8jlkuJR9Eo/s1600/Screenshot-1.png" alt="" width="625" height="423" />
<img class="alignnone" title="gaj2" src="http://3.bp.blogspot.com/_EX2lrFuJEC0/S977etBUL7I/AAAAAAAAAzY/yKkttIRX0n8/s1600/Screenshot-2.png" alt="" width="623" height="418" />
This release will rock...
And also stay tuned for Zeitgeist 0.3.4 which will introduce ZEO (Zeitgeist Event Ontology), improved data associations, negation queries and wild cards.....
The weeks ahead will be crazy so stay tuned... | 65 | 173 | 0.751417 | eng_Latn | 0.740079 |
e20058402fd96241d10a152c0c620431ee350509 | 1,205 | md | Markdown | Calendar/calendar_heatmap.md | Felixying2019/pyecharts-gallery | 81d2b9b23983e15285045af93e29f362a0ee41c8 | [
"MIT"
] | 1 | 2020-02-29T03:18:21.000Z | 2020-02-29T03:18:21.000Z | Calendar/calendar_heatmap.md | Felixying2019/pyecharts-gallery | 81d2b9b23983e15285045af93e29f362a0ee41c8 | [
"MIT"
] | null | null | null | Calendar/calendar_heatmap.md | Felixying2019/pyecharts-gallery | 81d2b9b23983e15285045af93e29f362a0ee41c8 | [
"MIT"
] | null | null | null | ## Echarts 代码 / 效果
[echarts](https://echarts.baidu.com/examples/editor.html?c=calendar-heatmap ':include :type=iframe width=100% height=800px')
## pyecharts 代码 / 效果
```python
import random
import datetime
import pyecharts.options as opts
from pyecharts.charts import Calendar
begin = datetime.date(2017, 1, 1)
end = datetime.date(2017, 12, 31)
data = [
[str(begin + datetime.timedelta(days=i)), random.randint(1000, 25000)]
for i in range((end - begin).days + 1)
]
(
Calendar(init_opts=opts.InitOpts(width="1600px", height="1000px"))
.add(
series_name="",
yaxis_data=data,
calendar_opts=opts.CalendarOpts(
pos_top="120",
pos_left="30",
pos_right="30",
range_="2017",
yearlabel_opts=opts.LabelOpts(is_show=False),
),
)
.set_global_opts(
title_opts=opts.TitleOpts(pos_top="30", pos_left="center", title="2017年步数情况"),
visualmap_opts=opts.VisualMapOpts(
max_=20000, min_=500, orient="horizontal", is_piecewise=False
),
)
.render("calendar_heatmap.html")
)
```
<iframe width="100%" height="800px" src="Calendar/calendar_heatmap.html"></iframe> | 27.386364 | 124 | 0.640664 | eng_Latn | 0.212272 |
e20158e7dad085016bcea964b02d597382358d71 | 5,858 | md | Markdown | docs/framework/wpf/advanced/templatebinding-markup-extension.md | badbadc0ffee/docs.de-de | 50a4fab72bc27249ce47d4bf52dcea9e3e279613 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/advanced/templatebinding-markup-extension.md | badbadc0ffee/docs.de-de | 50a4fab72bc27249ce47d4bf52dcea9e3e279613 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/advanced/templatebinding-markup-extension.md | badbadc0ffee/docs.de-de | 50a4fab72bc27249ce47d4bf52dcea9e3e279613 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: TemplateBinding-Markuperweiterung
ms.date: 03/30/2017
f1_keywords:
- TemplateBinding
- TemplateBindingExtension
helpviewer_keywords:
- XAML [WPF], TemplateBinding markup extension
- TemplateBinding markup extensions [WPF]
ms.assetid: 1d25bbfc-dbc2-499d-9f12-419d23d4ac6a
ms.openlocfilehash: 6d89978b907c8f124b5162c97de5edc034cf1e95
ms.sourcegitcommit: f348c84443380a1959294cdf12babcb804cfa987
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 11/12/2019
ms.locfileid: "73976672"
---
# <a name="templatebinding-markup-extension"></a>TemplateBinding-Markuperweiterung
Verknüpft den Wert einer Eigenschaft in einer Steuerelementvorlage so, dass er der Wert einer anderen Eigenschaft des Steuerelements mit Vorlagen ist.
## <a name="xaml-attribute-usage"></a>Verwendung von XAML-Attributen
```xml
<object property="{TemplateBinding sourceProperty}" .../>
```
## <a name="xaml-attribute-usage-for-setter-property-in-template-or-style"></a>Verwendung von XAML-Attributen (für Setter-Eigenschaft in Vorlage oder Stil)
```xml
<Setter Property="propertyName" Value="{TemplateBinding sourceProperty}" .../>
```
## <a name="xaml-values"></a>XAML-Werte
|||
|-|-|
|`propertyName`|<xref:System.Windows.DependencyProperty.Name%2A?displayProperty=nameWithType> der Eigenschaft, der in der Setter-Syntax festgelegt wird.|
|`sourceProperty`|Eine weitere Abhängigkeitseigenschaft für den auf Vorlagen basierenden Typ, die durch ihren <xref:System.Windows.DependencyProperty.Name%2A?displayProperty=nameWithType> angegeben wird.<br /><br /> - oder -<br /><br /> Ein Eigenschaftenname in Punktnotation, der durch einen anderen Typ als den auf Vorlagen basierenden Zieltyp definiert wird. Hierbei handelt es sich eigentlich um einen <xref:System.Windows.PropertyPath>. Siehe [PropertyPath-XAML-Syntax](propertypath-xaml-syntax.md).|
## <a name="remarks"></a>Hinweise
Eine `TemplateBinding` ist eine optimierte Form einer [Bindung](binding-markup-extension.md) für Vorlagen Szenarien, analog zu einer mit `{Binding RelativeSource={RelativeSource TemplatedParent}, Mode=OneWay}`erstellten `Binding`. Eine `TemplateBinding` ist immer eine unidirektionale Bindung, auch wenn die betroffenen Eigenschaften standardmäßig bidirektionale Bindungen sind. Beide betroffenen Eigenschaften müssen Abhängigkeitseigenschaften sein. Um eine bidirektionale Bindung mit einem übergeordneten Element zu erreichen, verwenden Sie stattdessen die folgende Bindungs Anweisung `{Binding RelativeSource={RelativeSource TemplatedParent}, Mode=TwoWay, Path=MyDependencyProperty}`.
[RelativeSource](relativesource-markupextension.md) ist eine andere Markup Erweiterung, die manchmal in Verbindung mit oder anstelle von `TemplateBinding` verwendet wird, um eine relative Eigenschaften Bindung innerhalb einer Vorlage auszuführen.
Das Beschreiben von Steuerelement Vorlagen als Konzept wird hier nicht behandelt. Weitere Informationen finden Sie unter [Steuerelement Stile und-Vorlagen](../controls/control-styles-and-templates.md).
Die Attributsyntax ist die mit dieser Markuperweiterung am häufigsten verwendete Syntax. Das Zeichenfolgentoken, das auf die `TemplateBinding`-Bezeichnerzeichenfolge folgt, wird als <xref:System.Windows.TemplateBindingExtension.Property%2A>-Wert der zugrunde liegenden <xref:System.Windows.TemplateBindingExtension>-Erweiterungsklasse zugeordnet.
Die Objektelementsyntax ist zwar möglich, wird jedoch nicht gezeigt, da sie keine realistische Anwendung hat. `TemplateBinding` wird verwendet, um Werte mithilfe von ausgewerteten Ausdrücken innerhalb von Settern zu füllen. Die Verwendung der Objektelementsyntax für `TemplateBinding` zum Füllen der `<Setter.Property>`-Eigenschaftenelementsyntax ist unnötig ausführlich.
`TemplateBinding` kann zudem in einer ausführlichen Attributverwendung verwendet werden, die die <xref:System.Windows.TemplateBindingExtension.Property%2A>-Eigenschaft als Eigenschaft=Wert-Paar angibt:
```xml
<object property="{TemplateBinding Property=sourceProperty}" .../>
```
Die ausführliche Verwendung ist häufig hilfreich, wenn für eine Erweiterung mehr als eine Eigenschaft festgelegt werden kann oder wenn bestimmte Eigenschaften optional sind. Da für `TemplateBinding` nur eine (erforderliche) Eigenschaft festgelegt werden kann, ist diese ausführliche Verwendung unüblich.
In der [!INCLUDE[TLA2#tla_winclient](../../../../includes/tla2sharptla-winclient-md.md)] XAML-Prozessor Implementierung wird die Handhabung dieser Markup Erweiterung durch die <xref:System.Windows.TemplateBindingExtension>-Klasse definiert.
`TemplateBinding` ist eine Markuperweiterung. Markuperweiterungen werden in der Regel implementiert, wenn Attributwerte mit Escapezeichen versehen werden müssen, damit diese nicht als literale Werte oder als Handlernamen betrachtet werden, und diese Anforderung eher global und nicht nur durch den Einsatz von Typkonvertern für bestimmte Typen oder Eigenschaften erfüllt werden soll. Alle Markup Erweiterungen in XAML verwenden die `{`-und `}` Zeichen in der Attribut Syntax. Dies ist die Konvention, mit der ein XAML-Prozessor erkennt, dass das Attribut von einer Markup Erweiterung verarbeitet werden muss. Weitere Informationen finden Sie unter [Markuperweiterungen und WPF-XAML](markup-extensions-and-wpf-xaml.md).
## <a name="see-also"></a>Siehe auch
- <xref:System.Windows.Style>
- <xref:System.Windows.Controls.ControlTemplate>
- [Erstellen von Formaten und Vorlagen](../controls/styling-and-templating.md)
- [Übersicht über XAML (WPF)](../../../desktop-wpf/fundamentals/xaml.md)
- [Markuperweiterungen und WPF-XAML](markup-extensions-and-wpf-xaml.md)
- [RelativeSource-Markuperweiterung](relativesource-markupextension.md)
- [Bindung als Markuperweiterung](binding-markup-extension.md)
| 81.361111 | 721 | 0.802663 | deu_Latn | 0.97452 |