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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
612563b1de39d19a775e43c6ddff87df03682902 | 783 | md | Markdown | Documentation/commands/overview.md | dolittle-obsolete/common | c317156e3a101278c42a996c3539765ff421def8 | [
"MIT"
] | null | null | null | Documentation/commands/overview.md | dolittle-obsolete/common | c317156e3a101278c42a996c3539765ff421def8 | [
"MIT"
] | 62 | 2019-01-05T09:35:08.000Z | 2020-01-19T21:08:31.000Z | Documentation/commands/overview.md | dolittle-obsolete/common | c317156e3a101278c42a996c3539765ff421def8 | [
"MIT"
] | 2 | 2019-02-13T09:45:50.000Z | 2019-10-14T20:16:46.000Z | ---
title: Overview
description: Learn about the commands system
keywords: Tools, tooling platform, commands
author: einari, woksin
weight: 10
aliases:
- /tools/common/commands
---
The commands system is related to everything around the execution of a command. It is essentially the core of the [Tooling Platform](../), providing the system to provide actual functionality to the tools built upon the Tooling Platform.
It makes it possible to create commands, provide new commands to the Tooling Platform and to execute them.
There are three important building blocks; [Commands](./command), [CommandGroups](./command_group) and [Namespaces](./namespace), with the Command being at the core of this. These pieces are glued together in the [Command Manager](./command_manager).
| 52.2 | 250 | 0.780332 | eng_Latn | 0.998889 |
612575d9c22f11acdc617bf143df51b356dda964 | 4,072 | md | Markdown | curriculum/challenges/espanol/02-javascript-algorithms-and-data-structures/basic-javascript/counting-cards.md | chaitany-raghav/freeCodeCamp | a962d6afd46e7743a9d69f66b55e037391909708 | [
"BSD-3-Clause"
] | 7 | 2021-08-03T09:38:07.000Z | 2021-11-08T10:44:21.000Z | curriculum/challenges/espanol/02-javascript-algorithms-and-data-structures/basic-javascript/counting-cards.md | chaitany-raghav/freeCodeCamp | a962d6afd46e7743a9d69f66b55e037391909708 | [
"BSD-3-Clause"
] | 450 | 2020-08-27T06:27:53.000Z | 2021-08-13T03:55:18.000Z | curriculum/challenges/espanol/02-javascript-algorithms-and-data-structures/basic-javascript/counting-cards.md | Dman247/freeCodeCamp | eafb8ae34b51a8fb33518c510f643bcc2d6ac946 | [
"BSD-3-Clause"
] | 7 | 2021-05-19T15:11:47.000Z | 2022-03-13T04:34:52.000Z | ---
id: 565bbe00e9cc8ac0725390f4
title: Conteo de cartas
challengeType: 1
videoUrl: 'https://scrimba.com/c/c6KE7ty'
forumTopicId: 16809
dashedName: counting-cards
---
# --description--
En el juego de casino Blackjack el jugador puede sacarle ventaja a la casa llevando un registro del numero relativo de cartas altas y bajas que quedan en la baraja. Esto es llamado [conteo de cartas](https://es.wikipedia.org/wiki/Conteo_de_cartas).
Tener más cartas altas en la baraja es una ventaja para el jugador. Se le asigna una valor a cada carta de acuerdo a la siguiente tabla. Cuando el conteo es positivo, el jugador debería apostar alto. Cuando el conteo da 0 o negativo, el jugador debería apostar bajo.
<table class='table table-striped'><thead><tr><th>Cambios del conteo</th><th>Cartas</th></tr></thead><tbody><tr><td>+1</td><td>2, 3, 4, 5, 6</td></tr><tr><td>0</td><td>7, 8, 9</td></tr><tr><td>-1</td><td>10, 'J', 'Q', 'K', 'A'</td></tr></tbody></table>
Escribirás una función para contar cartas. Recibirá un parámetro `card` (carta) que puede ser un número o una cadena y aumentar o reducir la variable global `count` (conteo) de acuerdo al valor de la carta (observa la tabla). La función devolverá una cadena con el conteo actual y la cadena `Bet` (Apuesta) si el conteo es positivo, o `Hold` (Espera) si el conteo es cero o negativo. El conteo actual y la decisión del jugador (`Bet` o `Hold`) deben estar separados por un solo espacio.
**Resultados de ejemplo:** `-3 Hold` o `5 Bet`
**Sugerencia**
NO reinicies `count` a 0 cuando el valor sea 7, 8 o 9. NO devuelvas un arreglo.
NO incluyas comillas (individuales o dobles) en el resultado.
# --hints--
La secuencia de cartas 2, 3, 4, 5, 6 debe devolver `5 Bet`
```js
assert(
(function () {
count = 0;
cc(2);
cc(3);
cc(4);
cc(5);
var out = cc(6);
if (out === '5 Bet') {
return true;
}
return false;
})()
);
```
La secuencia de cartas 7, 8, 9 debe devolver la cadena `0 Hold`
```js
assert(
(function () {
count = 0;
cc(7);
cc(8);
var out = cc(9);
if (out === '0 Hold') {
return true;
}
return false;
})()
);
```
La secuencia de cartas 10, J, Q, K, A debe devolver la cadena `-5 Hold`
```js
assert(
(function () {
count = 0;
cc(10);
cc('J');
cc('Q');
cc('K');
var out = cc('A');
if (out === '-5 Hold') {
return true;
}
return false;
})()
);
```
La secuencia de cartas 3, 7, Q, 8, A debe devolver la cadena `-1 Hold`
```js
assert(
(function () {
count = 0;
cc(3);
cc(7);
cc('Q');
cc(8);
var out = cc('A');
if (out === '-1 Hold') {
return true;
}
return false;
})()
);
```
La secuencia de cartas 2, J, 9, 2, 7 debe devolver la cadena `1 Bet`
```js
assert(
(function () {
count = 0;
cc(2);
cc('J');
cc(9);
cc(2);
var out = cc(7);
if (out === '1 Bet') {
return true;
}
return false;
})()
);
```
La secuencia de cartas 2, 2, 10 debe devolver la cadena `1 Bet`
```js
assert(
(function () {
count = 0;
cc(2);
cc(2);
var out = cc(10);
if (out === '1 Bet') {
return true;
}
return false;
})()
);
```
La secuencia de cartas 3, 2, A, 10, K debe devolver la cadena `-1 Hold`
```js
assert(
(function () {
count = 0;
cc(3);
cc(2);
cc('A');
cc(10);
var out = cc('K');
if (out === '-1 Hold') {
return true;
}
return false;
})()
);
```
# --seed--
## --seed-contents--
```js
var count = 0;
function cc(card) {
// Only change code below this line
return "Change Me";
// Only change code above this line
}
cc(2); cc(3); cc(7); cc('K'); cc('A');
```
# --solutions--
```js
var count = 0;
function cc(card) {
switch(card) {
case 2:
case 3:
case 4:
case 5:
case 6:
count++;
break;
case 10:
case 'J':
case 'Q':
case 'K':
case 'A':
count--;
}
if(count > 0) {
return count + " Bet";
} else {
return count + " Hold";
}
}
```
| 20.158416 | 486 | 0.571955 | spa_Latn | 0.651208 |
612582911aeb6f6749cbcc424dafa1dfc76026be | 1,448 | md | Markdown | README.md | jaydp17/serverless-plugin-ncc | 0fcf3f03e5f4c61eac77cb812ff455aa4d763987 | [
"MIT"
] | 23 | 2018-11-29T07:38:34.000Z | 2021-02-17T12:44:49.000Z | README.md | jaydp17/serverless-plugin-ncc | 0fcf3f03e5f4c61eac77cb812ff455aa4d763987 | [
"MIT"
] | 13 | 2019-03-02T09:27:50.000Z | 2022-01-22T03:23:18.000Z | README.md | jaydp17/serverless-plugin-ncc | 0fcf3f03e5f4c61eac77cb812ff455aa4d763987 | [
"MIT"
] | 9 | 2019-02-28T13:31:14.000Z | 2021-08-12T02:52:47.000Z | # serverless-plugin-ncc
A serverless plugin to use [@zeit/ncc](https://www.npmjs.com/package/@zeit/ncc) for compiling code before packaging.
## Usage
```sh
npm install -D serverless-plugin-ncc @zeit/ncc
```
`@zeit/ncc` is a peer dependency, so we'll have to install it separately.
Add the pluging to `serverless.yml`
```yml
plugins:
- serverless-plugin-ncc
```
## How to use with TypeScript files?
```yml
# serverless.yml
functions:
typescriptFn:
# the plugin checks for src/index.ts as well as src/index.js
# whichever exists is picked up
handler: src/index.handler
```
## Pass options
Custom options can be passed to ncc like this:
```yml
# serverless.yml
custom:
ncc:
minify: true
```
Note that all options are currently passed directly to ncc. To view all possible options
check the [ncc docs](https://github.com/zeit/ncc#programmatically-from-nodejs)
## Pass custom options per-function
Passing custom options to a function is as simple as introducing a custom block under the function with your ncc config
```yml
# serverless.yml
functions:
hello:
handler: src/hello/index.hello
custom:
ncc:
minify: false
```
## Disable ncc per function
You can pass `enabled: false` as custom config per function to disable ncc on that function
```yml
# serverless.yml
functions:
hello:
handler: src/hello/index.hello
custom:
ncc:
enabled: false
```
## License
MIT
| 18.564103 | 119 | 0.705801 | eng_Latn | 0.902049 |
6125c8f9412f090bd8c3a7eebd5914fa98c655d3 | 16,781 | md | Markdown | src/posts/2020-11-10-ebpf-future-of-networking/index.md | k8isdead/cilium.io | a2bc6f6f6e8f5e0ef10d36e7f70e861c394288f1 | [
"CC-BY-4.0"
] | 3 | 2022-03-08T17:50:19.000Z | 2022-03-29T15:56:13.000Z | src/posts/2020-11-10-ebpf-future-of-networking/index.md | k8isdead/cilium.io | a2bc6f6f6e8f5e0ef10d36e7f70e861c394288f1 | [
"CC-BY-4.0"
] | 31 | 2022-03-07T12:41:39.000Z | 2022-03-28T16:41:50.000Z | src/posts/2020-11-10-ebpf-future-of-networking/index.md | k8isdead/cilium.io | a2bc6f6f6e8f5e0ef10d36e7f70e861c394288f1 | [
"CC-BY-4.0"
] | 3 | 2022-03-08T19:48:35.000Z | 2022-03-29T11:34:04.000Z | ---
path: '/blog/2020/11/10/ebpf-future-of-networking/'
date: '2020-11-10T09:00:00.000Z'
isPopular: true
title: 'eBPF - The Future of Networking & Security'
categories:
- Technology
tags:
- Kubernetes
- Cilium
- eBPF
- BPF
- GKE
- Google
ogImage: ogimage.png
ogSummary: "Today is an exciting day for the Cilium community: Isovalent, the company behind Cilium, is announcing its $29M Series A financing round backed by Andreessen Horowitz, Google, and Cisco. This is a perfect occasion to take a deeper look
into where eBPF-based networking is coming from and to understand what the
excitement is all about."
---
import authors from 'utils/author-data';
Today is an exciting day for the Cilium community:
[Isovalent](https://www.isovalent.com), the company behind Cilium, is
announcing its [$29M Series A financing round](https://techcrunch.com/2020/11/10/with-29m-in-funding-isovalent-launches-its-cloud-native-networking-and-security-platform-based-on-ebpf-and-cilium/) backed by [Andreessen
Horowitz](https://a16z.com/2020/11/10/investing-in-isovalent/), Google, and Cisco. This is a perfect occasion to take a deeper look
into where eBPF-based networking is coming from and to understand what the
excitement is all about.
Two weeks ago, we hosted the first ever [eBPF Summit
2020](https://ebpf.io/summit-2020/). Besides exciting keynotes, several users
of Cilium spoke about their use cases including
[Adobe](https://www.youtube.com/watch?v=7UQ2CU6UEGY&t=5s), [Capital
One](https://www.youtube.com/watch?v=hwOpCKBaJ-w&t=28s&ab_channel=eBPFSummit),
[Datadog](https://www.youtube.com/watch?v=6mTVuZUHLBg&t=5s),
[GitLab](https://youtu.be/kwQ0ooO3UM8?t=5),
[Google](https://www.youtube.com/watch?v=oLS25ztnlMk), and [Wildlife
Studios](https://youtu.be/_1t3bXzptP0?t=10). Earlier last month, [Alibaba
Cloud](/blog/2020/10/09/cilium-in-alibaba-cloud) covered how they are using
Cilium for eBPF-based high-performance cloud-native networking. This was just a
couple of weeks after Google had
[announced](https://cloud.google.com/blog/products/containers-kubernetes/bringing-ebpf-and-cilium-to-google-kubernetes-engine)
the availability of a Cilium-based networking dataplane for GKE and Anthos.
The last few months have already been incredibly exciting for the entire team.
It's not every day that one of the co-founders of Kubernetes praises the
technology and work your team has created.
Today's launch out of stealth is another great moment for the team and an
achievement of all team members who have worked incredibly hard for this day.
We are looking forward to talk more publicly about what we do as a company
while we continue to innovate around our open-source projects.
This moment is a great opportunity to provide a deeper dive into the motivation
to use eBPF for networking. What are all these users seeing in Cilium? What is
so special about eBPF?
# The Roots of Programmability: Software Defined Networking
To really understand the shift, let's briefly look back at the history of
networking. In the 90s, networking was almost entirely physical. Cables,
perimeters, dial-up modems and a lot of Layer 2. Around the same time, in 1999,
iptables was created for Linux and just shortly after, PF was released for BSD.
Both projects focused on software-based firewalling. Early signs of a much
larger movement later on: software-defined networking. This was the time I
personally got involved in Linux networking.
In the years 2003-2008, VLANs were first described, the first release of the Xen
hypervisor happened, EMC acquired VMware, and KVM was merged into the Linux
kernel. This was the start of the virtualization era but from a networking
perspective, not much had changed. Networking of virtual machines was
delegated to the underlying physical network by bridging VMs directly to the
network. Almost no networking logic existed in software. During this early
virtualization era, most of the Linux kernel networking focus was on the TCP/IP
stack and optimizing the kernel as a system to run applications.
It was the year 2009 when things got exciting from a software networking
perspective. The first version of [Open vSwitch](https://www.openvswitch.org/)
was released which brought us software-defined networking (SDN). It brought
massive network programmability to the Linux kernel.
This programmability aspect can still be found in eBPF-based networking today
and is one of the corner stones. eBPF-based networking has its roots in SDN and
evolves it by removing the device-centric model from the equation.
# The Rise of Containers and Kubernetes
The year 2013 brought Docker. Docker primarily inherited the networking from
the virtualization layers and containers were treated like miniature VMs from a
networking perspective. The fundamental shift that Docker brought focused on
application packaging with container images and not on the infrastructure side.
Therefore, almost all of the early networking solutions for containers were
inherited from OpenStack days.
In 2014, the first commit to Kubernetes happened. Kubernetes was obviously not
the first project to attempt translating high-level user intent into
infrastructure automation, but Kubernetes made a deliberate decision to make a
lot fewer assumptions in networking and security. For example, there is no
concept of a network or subnet in Kubernetes. This led to an impressive cycle
of innovations.
But the quick evolution of Kubernetes also has a dark side: The desire to get
to a complete enough state as quickly as possible made it rely on iptables. A
packet filter in the Linux kernel I personally worked on while still using a
dial-up modem. Clearly not perfectly suited for the task, but widely available
and good enough to get started.
# The eBPF Revolution Begins
The same year that Kubernetes started, eBPF was first merged into the Linux
kernel as a successor to the long-standing packet filter BPF. Hence the
name extended BPF or short: eBPF. One year later, the eBPF backend was merged into the LLVM compiler
suite, allowing for LLVM to emit eBPF bytecode. In parallel, integration
into the kernel's traffic control layer made Linux networking programmable with eBPF.
2016, XDP was merged into the Linux kernel enabling a high-performance datapath
by allowing eBPF programs to run directly in the driver of a network device.
This is what later unlocked the development of eBPF-based high-performance load
balancers driving some of the largest data centers today.
Ever since, eBPF is in an incredibly steep trajectory to evolve further and
becomes more and more powerful every year. The general-purpose nature of eBPF
allowed for a diverse community to form around it, spanning networking,
tracing, security, profiling, and observability.
# Cilium & eBPF - An ideal match for the Cloud-Native World
To recap history, with hardware networking, the functionality and scale were
mostly defined by the hardware. With software-defined networking a lot of it
moved from hardware to software by taking functionality previously provided
with hardware, rewrite it in software, and then put the word virtual in front.
All of this made sense as long as machines are involved.
Containers and the cloud-native era are not about machines. We care about
applications, APIs, and services. Some machines will still exist for a long
time but you don't want to build your architecture around them.
> However, in modern systems we rarely think about connecting machines, or
> virtual machines, or even containers really. Instead we’re concerned with
> connecting microservices. So rather than machines and wires, we think in
> terms of cloud services, APIs and the higher level protocols and the
> systems used to connect them. The past was IP addresses, ports, vNICs and
> VLANS. Now it is service identity, gRPC, Kafka, distributed data stores,
> remote APIs, etc.
>
> -- Martin Casado, Creator of SDN, Partner, a16z
What makes eBPF and thus Cilium such a great fit to address the new cloud
native challenges?
## Programmability
The programmability of eBPF makes it possible to adjust to the quickly evolving
cloud-native requirements and tackle the increase in scale with ease. Here is
an example on how the programmability of eBPF lead Google to adopt Cilium as
its new networking dataplane for GKE:
> As more and more enterprises adopt Kubernetes, the gamut of use cases is
> widening with new requirements around multi-cloud, security, visibility and
> scalability. In addition, new technologies such as service mesh and
> serverless demand more customization from the underlying Kubernetes layer.
> These new requirements all have something in common: they need a more
> programmable dataplane that can perform Kubernetes-aware packet manipulations
> without sacrificing performance.
>
> Enter Extended Berkeley Packet Filter (eBPF), a new Linux networking
> paradigm that exposes programmable hooks to the network stack inside the
> Linux kernel.
>
> -- Gobind Johar, Product Manager, Google Kubernetes Engine
Even more important, eBPF is not networking specific or tied to a particular
domain. The generic nature of eBPF not only attracts a much bigger community to
innovate, it also avoids making premature assumptions about what building
blocks are required to solve future problems. This is a massive advantage over
any networking specific programmability solution such as iptables, Open
vSwitch, or nftables.
## Embedded in the Linux kernel
Some of you may correctly state that programmability already existed in the
form of user-space networking. The unique new aspect of eBPF's programmability
is being embedded in the Linux kernel. Applications use system calls to
interact via the network and the Linux kernel is responsible to handle these
system calls. In order for a user-space networking framework to remain
transparent to the application, it still has to traverse the socket layer of
the Linux kernel. eBPF avoids this by remaining in the kernel altogether.
The reason why this was not more important before is because with virtual
machines, the hypervisor created a natural boundary between the network
device of the metal machine and the sockets of the operator system inside the
VM. With containers, this all happens in the same kernel.
## Safety and Efficiency
Why not just load a Linux kernel module then? It obviously provides arbitrary
programmability at a very high efficiency. We could dive into the cost of
maintaining kernel modules across kernel versions, but the major downside is
more trivial: Safety while remaining efficient.
> Buggy kernel code will crash your machine. The kernel is not protected from
> a buggy kernel module. I think people assumed that this is just how things
> are; that's the price to do kernel programming. eBPF changed this dogma. It
> brought safety to kernel programming.
>
> -- Alexei Starovoitov, eBPF Co-Maintainer, Facebook
By requiring eBPF programs to pass through a verification process, eBPF
programs are significantly more secure than loading a kernel module.
The efficiency is guaranteed by a Just in Time (JIT) compiler that ensures
native execution speed of eBPF bytecode.
All of this makes eBPF incredibly powerful, but it is also a low-level
technology intended to be used primarily by Linux kernel developers. This is
where Cilium comes into play.
# Cilium - eBPF-based Networking, Observability, and Security
Cilium is an open source project that has been designed on top of eBPF to
address the networking, security, and visibility requirements of container
workloads. It provides a high-level abstraction on top of eBPF. Cilium is to
eBPF what Kubernetes and container runtimes are to Linux kernel namespaces,
cgroups, and seccomp. The right abstraction layer on top.
Let's dive into particular use cases that Cilium is solving:
## Networking
- **Network connectivity:** In its most basic form, Cilium is a CNI to provide
network connectivity to Kubernetes workloads. The eBPF-based datapath
features both IPv4 and IPv6 with the ability to support direct-routing,
encapsulation/overlay topologies, as well as integration with cloud provider
specific networking layers.
- **Service Load-Balancing:** Cilium can act as 100% kube-proxy replacement to
provide all service load-balancing in a Kubernetes cluster. The
implementation is highly scalable and supports direct server return (DSR)
with session affinity. If possible, Cilium will perform the load balancing on
the system call level and translate the address directly in the `connect()`
system call instead of relying on network address translation throughout the
entire duration of a network connection.
- **Edge Load-Balancing:** The XDP-based edge load-balancing capability can
steer traffic into Kubernetes clusters or run entirely independent of
Kubernetes. It supports consistent hashing with Maglev and provides an
implementation for Kubernetes service types NodePort, LoadBalancer and
services with externalIPs.
- **Multi-cluster connectivity + security:** With the multi-cluster ability, Kubernetes clusters can be
connected without the introduction of additional gateways or proxies. The
notion of global services allows to route service traffic across clusters.
- **Integration of VM/metal:** Virtual and metal machines can be seamlessly
connected with Kubernetes workloads without proxies or gateways by
representing such external workloads in the Kubernetes cluster as if the
workload would run as a pod.
## Security
- **Network Policy:** Full support for Kubernetes Network Policy based on a
modern identity-based implementation built entirely in eBPF. Extensive
visibility functionality eases problem troubleshooting and compliance
monitoring.
- **FQDN/DNS-based:** Transparent integration with DNS-based service discovery
allows for network policies based on DNS names instead of IP address
blocks to cope with the highly dynamic nature of modern services backed by
constantly changing set of IP addresses. The built-in DNS authorization
further improves the security model.
- **API Awareness:** Transparent injection of Envoy and other proxies on an
on-demand basis enables policy enforcement on API level, e.g. HTTP, Kafka,
gRPC, Cassandra, ...
- **Policy-driven SSL termination & injection:** SSL termination and injection
of SSL certificates is policy driven, allowing to terminate SSL connections on
behalf of an application or to transparently inject use of a certificate or
token for service traffic without requiring to share the secret with the
workload directly.
- **Simulation & Audit:** With policy simulation and policy audit, the effect
of network policy changes can be inspected before dropping live traffic.
## Observability
- **Flow logging:** Flow logs at L3-L7 provide deep visibility of forwarding
and policy decisions on the network level. A cluster-wide flow query API
enables the quick inspection of networking behavior and network drops during
incidents.
- **Programmable Metrics:** Configurable and programmable metrics allow users
to understand network, application, and security behavior and monitor the
correctness consistently.
- **Service Map:** A graphical service topology map simplifies understanding of
deployed application topologies and dependencies.
- **Troubleshooting:** The troubleshooting tooling has been built into Cilium
from the beginning. An internal tracing system makes it possible to track every
forwarding decision and can be enabled on the fly. Metrics capture packet
drops with detailed reasoning.
For more details, check out the [Functionality
Overview](https://docs.cilium.io/en/stable/intro/#functionality-overview) in
the Cilium documentation.
# Conclusion
Our team has had its fair share of exciting moments. The public launch of
Isovalent as a company is yet another major milestone.
Technically it's only a "Hello world" for something that our customers have
already been using for a while, but for our team, today is emotional. This year
has been challenging in many ways and not everything has always been within our
control. Being able to achieve and build something as a team that everbody can
be truly proud of will always be the most rewarding aspect of team and company
building to me.
I'm looking forward to work with many of you, as users, contributors, or
customers.
# Further Reading
- [Learn more about Cilium](https://cilium.io/)
- [Learn more about eBPF](https://ebpf.io/)
- [Learn more about Isovalent](https://www.isovalent.com/)
<BlogAuthor {...authors.thomasGraf} />
| 48.64058 | 247 | 0.796317 | eng_Latn | 0.998499 |
6125debb55ca8267d546ee4d97cfefa2ecf8b2d2 | 43 | md | Markdown | bitcoinin/static/README.md | pablodz/bitcoinin | c2a42c6dc2bfbc8031d2b6966fdcb11ea485e3b0 | [
"MIT"
] | 1 | 2021-01-02T21:02:21.000Z | 2021-01-02T21:02:21.000Z | bitcoinin/static/README.md | pablodz/bitcoinin | c2a42c6dc2bfbc8031d2b6966fdcb11ea485e3b0 | [
"MIT"
] | 2 | 2021-04-18T00:42:05.000Z | 2021-04-29T20:27:52.000Z | bitcoinin/static/README.md | pablodz/bitcoinin | c2a42c6dc2bfbc8031d2b6966fdcb11ea485e3b0 | [
"MIT"
] | null | null | null | 1.- front page
2.- dashboard
3.- personal | 8.6 | 14 | 0.674419 | eng_Latn | 0.824529 |
61260c3daad28f8a483d03824b4dee446423dbec | 1,183 | md | Markdown | content/10.hymns-and-tunes-1876/02.001-100/08.071-080/10.OH!-that-the-Lord-would-guide-my-ways/docs.md | GospelSounders/adventhymnals | d2108ab49d735b373c59901e5296c8819a1ad3f2 | [
"Apache-2.0"
] | null | null | null | content/10.hymns-and-tunes-1876/02.001-100/08.071-080/10.OH!-that-the-Lord-would-guide-my-ways/docs.md | GospelSounders/adventhymnals | d2108ab49d735b373c59901e5296c8819a1ad3f2 | [
"Apache-2.0"
] | 1 | 2021-05-10T23:24:05.000Z | 2021-05-10T23:24:05.000Z | content/10.hymns-and-tunes-1876/02.001-100/08.071-080/10.OH!-that-the-Lord-would-guide-my-ways/docs.md | GospelSounders/adventhymnals | d2108ab49d735b373c59901e5296c8819a1ad3f2 | [
"Apache-2.0"
] | null | null | null | ---
title: |
080 OH! that the Lord would guide my ways - Hymns and Tunes 1876
metadata:
description: |
Hymns and Tunes 1876 080. OH! that the Lord would guide my ways. To keep his statutes still; Oh! that my God would grant me grace To know and do his will.
keywords: |
Hymns and Tunes 1876, adventhymnals, advent hymnals, OH! that the Lord would guide my ways, To keep his statutes still;,
author: Brian Onang'o
---
#### Advent Hymnals
## 080. OH! that the Lord would guide my ways
#### Hymns and Tunes 1876
```txt
^Meter:^ ^CM^
1. OH! that the Lord would guide my ways
To keep his statutes still;
Oh! that my God would grant me grace
To know and do his will.
2. O send thy Spirit down to write
Thy law upon my heart;
Nor let my tongue indulge deceit,
Nor act the liar’s part.
3. From vanity turn off my eyes;
Let no corrupt design.
Nor covetous desires, arise
Within this soul of mine.
4. Order my footsteps by thy word,
And make my heart sincere;
Let sin have no dominion, Lord,
But keep my conscience clear.
5. Make me to walk in thy commands—
’Tis a delightful road;
Nor let my head, nor heart, nor hands,
Offend against my God.
``` | 25.717391 | 163 | 0.707523 | eng_Latn | 0.997142 |
61268cd95748bbe0491eeae1615a2adc57382fe2 | 576 | md | Markdown | README.md | implydata/druid.d.ts | 17ac922469906eead992b6c4fe36e1230e5ddc21 | [
"Apache-2.0"
] | 8 | 2016-10-28T21:34:03.000Z | 2020-11-12T08:08:08.000Z | README.md | implydata/druid.d.ts | 17ac922469906eead992b6c4fe36e1230e5ddc21 | [
"Apache-2.0"
] | 1 | 2020-04-14T02:41:49.000Z | 2020-04-14T02:41:49.000Z | README.md | implydata/druid.d.ts | 17ac922469906eead992b6c4fe36e1230e5ddc21 | [
"Apache-2.0"
] | 4 | 2016-12-19T23:07:08.000Z | 2021-08-17T07:23:46.000Z | # TypeScript definitions for the Druid API
For people who like all their types in order.
This ambient type definition was written as part of [Plywood](https://github.com/implydata/plywood) but was extracted as it can be of use in any TypeScript based project that deals with Druid queries.
## Usage
1. Copy the file `druid/druid.d.ts` into your project.
2. Refer to it using: `/// <reference path="path/to/file/druid.d.ts" />`
3. Use the types defined within the `Druid` module.
## Note
These definitions use union and string types and thus requires TypeScript >= 1.8
| 32 | 200 | 0.748264 | eng_Latn | 0.994199 |
612739104ef7de4389a79b840f91df16e75c8d6f | 2,989 | markdown | Markdown | _posts/2019-03-31-using-multiple-accounts-in-git.markdown | mioscode/mioscode.github.io | ade7802e91f490288e18b8f667a85b58a056c683 | [
"BSD-3-Clause",
"MIT"
] | 1 | 2019-04-18T01:29:08.000Z | 2019-04-18T01:29:08.000Z | _posts/2019-03-31-using-multiple-accounts-in-git.markdown | mioscode/mioscode.github.io | ade7802e91f490288e18b8f667a85b58a056c683 | [
"BSD-3-Clause",
"MIT"
] | 1 | 2019-11-14T09:11:50.000Z | 2019-11-15T04:39:44.000Z | _posts/2019-03-31-using-multiple-accounts-in-git.markdown | mioscode/mioscode.github.io | ade7802e91f490288e18b8f667a85b58a056c683 | [
"BSD-3-Clause",
"MIT"
] | null | null | null | ---
title: "한 대의 컴퓨터에서 여러 개의 github 계정 사용하기"
categories:
- Github
tags:
- Github
comments: true
---
# 1. 새로운 SSH 키 생성
SSH 키들은 기본적으로 사용자의 ~/.ssh 디렉토리에 저장됨
먼저 기존의 키들을 확인
```
$ cd ~/.ssh
$ ls
id_rsa.pub id_rsa
```
.pub 이 붙은 파일과 그렇지 않은 파일을 볼 수 있는데, .pub 이 붙은 것이 공개키이고 다른 것은 개인키
새로운 SSH 키를 만들기
기존에 생성된 SSH 키가 없거나, .ssh 디렉토리가 없어도 다음 명령으로 만들 수 있다.
```
$ ssh-keygen -t rsa -C "username@gmail.com" // 새 계정의 이메일 주소
```
새로운 키를 저장할 경로를 묻는데 이 때, 기존의 키를 덮어쓰지 않도록 조심
id_second 라는 이름으로 SSH 키를 생성
```
$ Enter file in which to save the key (/Users/YOURNAME/.ssh/id_rsa):/Users/YOURNAME/.ssh/id_rsa_second
```
암호를 두 번 입력하라고 하는데 엔터를 쳐서 넘어가면 새로운 키가 생성된 것을 확인 가능
```
$ ls
id_rsa.pub id_rsa_second.pub id_rsa id_rsa_second
```
id_rsa_second.pub 의 내용을 복사해서 다음 단계에서 사용
```
$ cat id_rsa_second.pub
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBvlgEqRqaVp/zOoxtAnKdMr6/y9SaP0Y3MGG4648N+MLD6yy+JjOYE3HnLNDWsOhsOXkjr7phVHYBqVd6QtpHZrgw5PXOEo1V00Es+HGcHU0sONLWK/OWtV7598eULXnQfNjPlND/09BW+D5IXI8plNRcjfaD4dRxtSOtolZ5jxxxT4gpR5v17Axm3ut4ukS+6f6GHNYZ4QcZJtlaps+eN0Ol/juEYy47r3l5CPIc9sxyQGE4o5Mm4LhLk769yVQGgGcR21Aj0DuEVN0HyeEZcAbqFqze9ZY5kdtYcI2L4B23X781nlX6zfpeVL9iU9pxkw/UGLUx2bcSGHOfrvhX username@gmail.com
```
# 2. SSH 키 설정
[github](https://github.com/) 사이트에서 두 번쨰 계정 생성하고 로그인
오른쪽 위 아이콘 클릭
Settings -> SSH Keys -> Nes SSH key 클릭
Title : 구별 가능한 간단한 이름
Key : 복사해둔 키
Add SSH key 버튼 눌러서 완료
터미널에서 생성한 키를 SSH에 추가
```
$ ssh-add ~/.ssh/id_second
```
# 3. Config 파일 만들기
로컬 저장소에서 github으로 푸시할 때 어떤 키 참조할 것인지 결정하도록 config 만들기
```
$ cd .ssh
$ vim config
```
config 파일에 다음 내용 입력
```
# Default account
Host github.com
HostName github.com
User git
IdentityFile ~/.ssh/id_rsa
# Second account
Host github.com-second
HostName github.com
User git
IdentityFile ~/.ssh/id_rsa_second
```
# 4. 새 계정으로 Push
지금까지의 작업이 잘 되었는지 확인
먼저 github 사이트에서 새 repository 를 만든다. 그리고 로컬에서 원하는 위치에 새 폴더를 만들고 다음 명령을 입력
```
$ git init
$ git commit -am "first commit"
$ git remote add origin git@github.com-second:YOURNAME/REPOSITORY.git
$ git push origin master
```
여기서 YOURNAME 에는 github 계정의 이름, REPOSITORY 에는 새로 만든 repository의 이름을 입력
유의해야 할 점은, config 파일에서 Host github.com-second 라고 입력했으므로 원격저장소 설정시 git@github.com 대신 git@github.com-second 를 입력해야 한다는 점
이것은 clone 시에도 마찬가지
만약 기존의 계정으로 작업하려면 원래하던 방법으로 git@github.com으로 하면 된다.
추가적으로, 새 계정으로 작업하는 폴더에서 다음 명령으로 commit 시 사용될 이름과 이메일 주소를 변경할 수 있다.
```
$ git config user.name "YOURNAME"
$ git config user.email "YOUREMAIL"
```
# NOTE : 만약 잘 사용하다가 갑자기 git access denied 라는 메세지가 뜨면 아래 명령을 입력한 뒤 다시 시도
```
$ ssh-add ~/.ssh/id_rsa_second
```
# Reference
- [https://aweekj.github.io/using-multiple-accounts-in-git/](https://aweekj.github.io/using-multiple-accounts-in-git/)
- [How to Work with GitHub and Multiple Accounts](https://code.tutsplus.com/tutorials/quick-tip-how-to-work-with-github-and-multiple-accounts--net-22574)
- [Git 서버 - SSH 공개키 만들기](https://git-scm.com/book/ko/v1/Git-%EC%84%9C%EB%B2%84-SSH-%EA%B3%B5%EA%B0%9C%ED%82%A4-%EB%A7%8C%EB%93%A4%EA%B8%B0)
| 26.927928 | 399 | 0.726999 | kor_Hang | 0.999979 |
61283339b60b1c48d85a6f8aed431b514a36ae62 | 1,116 | md | Markdown | api/Word.ShapeRange.ZOrder.md | kibitzerCZ/VBA-Docs | 046664c5f09c17707e8ee92fd1505ddd0f6c9a91 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-03-09T13:24:12.000Z | 2020-03-09T16:19:11.000Z | api/Word.ShapeRange.ZOrder.md | kibitzerCZ/VBA-Docs | 046664c5f09c17707e8ee92fd1505ddd0f6c9a91 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Word.ShapeRange.ZOrder.md | kibitzerCZ/VBA-Docs | 046664c5f09c17707e8ee92fd1505ddd0f6c9a91 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-11-28T06:51:45.000Z | 2019-11-28T06:51:45.000Z | ---
title: ShapeRange.ZOrder method (Word)
keywords: vbawd10.chm162856988
f1_keywords:
- vbawd10.chm162856988
ms.prod: word
api_name:
- Word.ShapeRange.ZOrder
ms.assetid: 7f9a1a08-ac21-8866-9bf7-6a850200e2fd
ms.date: 06/08/2017
localization_priority: Normal
---
# ShapeRange.ZOrder method (Word)
Moves the specified shape range in front of or behind other shapes in the collection (that is, changes the shape range's position in the z-order).
## Syntax
_expression_.**ZOrder** (_ZOrderCmd_)
_expression_ An expression that returns a **[ShapeRange](Word.shaperange.md)** object.
## Parameters
|Name|Required/Optional|Data type|Description|
|:-----|:-----|:-----|:-----|
| _ZOrderCmd_|Required| **MsoZOrderCmd**|Specifies where to move the specified shape range relative to the other shapes.|
## Return value
Nothing
## Remarks
Use the **[ZOrderPosition](Word.ShapeRange.ZOrderPosition.md)** property to determine a shape range's current position in the z-order.
## See also
[ShapeRange Collection Object](Word.shaperange.md)
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 22.32 | 146 | 0.747312 | eng_Latn | 0.777002 |
612846584207ce642320f579ee0226bbf63b87c3 | 162 | md | Markdown | README.md | Samaritan89/interview-source-code | 516873895d656a6d5f5cceacf1bca5c0dfaa0936 | [
"MIT"
] | 1 | 2020-01-13T06:12:38.000Z | 2020-01-13T06:12:38.000Z | README.md | Samaritan89/interview-source-code | 516873895d656a6d5f5cceacf1bca5c0dfaa0936 | [
"MIT"
] | null | null | null | README.md | Samaritan89/interview-source-code | 516873895d656a6d5f5cceacf1bca5c0dfaa0936 | [
"MIT"
] | null | null | null | # interview-source-code
通过面试题目巩固前端知识，题目都是前端一些基础知识的灵活使用，不搞犄角旮旯的特性做噱头
面试题目 [https://www.yuque.com/sunluyong/interview](https://www.yuque.com/sunluyong/interview)
| 27 | 91 | 0.814815 | yue_Hant | 0.441048 |
6128de85d3873c7e8ed2b54cd240cacde507dbec | 979 | md | Markdown | README.md | matquant14/CD-Dark-Theme | 38b7105fe504eeb6f4ae5360d2ac0d12150fd3f4 | [
"MIT"
] | null | null | null | README.md | matquant14/CD-Dark-Theme | 38b7105fe504eeb6f4ae5360d2ac0d12150fd3f4 | [
"MIT"
] | 31 | 2021-05-04T20:54:26.000Z | 2022-03-31T10:12:07.000Z | README.md | matquant14/CD-Dark-Theme | 38b7105fe504eeb6f4ae5360d2ac0d12150fd3f4 | [
"MIT"
] | null | null | null | # CD-Dark-Theme
[](https://plugins.jetbrains.com/plugin/PLUGIN_ID)
[](https://plugins.jetbrains.com/plugin/PLUGIN_ID)
<!-- Plugin description -->
Dark theme inspired by Hiberbee Dark theme.
<!-- Plugin description end -->
<!-- Plugin ID -->
com.github.matquant14.cddarktheme
<!-- Plugin ID end -->
## Installation
- Using IDE built-in plugin system:
<kbd>Settings/Preferences</kbd> > <kbd>Plugins</kbd> > <kbd>Marketplace</kbd> > <kbd>Search for "CD-Dark-Theme"</kbd> >
<kbd>Install Plugin</kbd>
- Manually:
Download the [latest release](https://github.com/matquant14/CD-Dark-Theme/releases/latest) and install it manually using
<kbd>Settings/Preferences</kbd> > <kbd>Plugins</kbd> > <kbd>⚙️</kbd> > <kbd>Install plugin from disk...</kbd>
| 32.633333 | 122 | 0.709908 | yue_Hant | 0.575484 |
61298c354266abb33811065a1e7b0abb3f74c889 | 7,385 | md | Markdown | README.md | MeetzhDing/tencentcloud-monitor-grafana-app | 99f3b73f2368af60616084b71e9e64e74c61bb6e | [
"Apache-2.0"
] | null | null | null | README.md | MeetzhDing/tencentcloud-monitor-grafana-app | 99f3b73f2368af60616084b71e9e64e74c61bb6e | [
"Apache-2.0"
] | null | null | null | README.md | MeetzhDing/tencentcloud-monitor-grafana-app | 99f3b73f2368af60616084b71e9e64e74c61bb6e | [
"Apache-2.0"
] | null | null | null | [](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app)
[](https://grafana.com/grafana/plugins/tencentcloud-monitor-app)
[](https://grafana.com/grafana/plugins/tencentcloud-monitor-app)
[](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/blob/master/LICENSE)
[](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/blob/master/CHANGELOG.md)
[](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/pulls)
# 腾讯云监控插件 @ Grafana
简体中文 | [English](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/blob/master/README.en-US.md)
> 注意：该插件从 2.0.0 版本起的最低运行要求为 Grafana 7.3 或更高的版本上。请优先安装 Grafana 环境，详情参考 [Grafana 安装文档](https://grafana.com/grafana/download) 。
# 简介
[腾讯云监控](https://cloud.tencent.com/product/cm) 为用户提供云服务器、云数据库等多个云产品的负载和性能监控指标，用户可以使用云监控控制台、云监控 API 等方式获取相关监控数据。
[腾讯云日志服务](https://cloud.tencent.com/product/cls) 是腾讯云提供的一站式日志服务平台，提供了从日志采集、日志存储到日志检索，图表分析、监控告警、日志投递等多项服务，协助用户通过日志来解决业务运维、服务监控、日志审计等场景问题。
腾讯云监控与日志插件 Tencent Cloud Monitor App，是一款适配开源软件 Grafana 的应用插件，通过调用 [腾讯云监控 API 3.0](https://cloud.tencent.com/document/product/248/30342) 和 [腾讯云日志服务 API 3.0](https://cloud.tencent.com/document/product/614/56479) 的方式获取监控与日志数据，并对数据进行自定义 Dashboard 展示。
该插件监控能力支持的云产品请参见[监控Grafana文档简介](https://cloud.tencent.com/document/product/248/54505) ，该插件支持日志服务的[检索分析能力](https://cloud.tencent.com/document/product/614/47044) 能力。
该插件提供了云服务器、云数据库 MySQL、负载均衡 和 云产品日志数据 等具有代表性的 [Dashboard 预设模板](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/tree/master/src/dashboards)
# 入门指南
使用 Grafana CLI 安装：
```bash
$ grafana-cli plugins install tencentcloud-monitor-app
```
更多安装方式与入门指南请参见[云监控文档](https://cloud.tencent.com/document/product/248/54506) 和 [日志服务文档](https://cloud.tencent.com/document/product/614/52102) 。
# 模板变量
模板变量 [Variables](https://grafana.com/docs/reference/templating/) 是 Grafana 提供的一种 Dashboard 优化特性，用于创建高度可复用和交互式 Dashboard。模板变量的一般思想是允许 Grafana 从数据源获得不同的度量，并提供一种无需修改仪表板就可以动态更改它的方法。腾讯云监控应用目前提供了地域、云服务器实例、云数据库 MySQL 实例 等变量。
详细文档与示例请参见 [文档](https://cloud.tencent.com/document/product/248/54510) 。
# FAQs
常见问题请参见 [FAQ](https://cloud.tencent.com/document/product/248/55171) 。
# 联系我们
若在使用过程中遇到任何问题，您可以在此[创建 issue](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/issues/new/choose) ，或者扫码添加 云监控插件@Grafana 使用交流QQ群，我们将竭诚为您服务！
| QQ 群 (861359693) |
| ----------- |
|  |
# 贡献者 ✨
感谢这些可爱的人对此项目的热爱 ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
[](#contributors)
<table>
<tr>
<td align="center"><a href="https://github.com/heriky"><img src="https://avatars.githubusercontent.com/u/12195736?v=4?s=70" width="70px;" alt=""/><br /><sub><b>heriky</b></sub></a><br /><a href="#" title="Code">💻</a></td>
<td align="center"><a href="https://github.com/jamesxwang"><img src="https://avatars.githubusercontent.com/u/36892657?v=4?s=70" width="70px;" alt=""/><br /><sub><b>jamesxwang</b></sub></a><br /><a href="https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/commits?author=jamesxwang" title="Code">💻</a> <a href="#" title="Documentation ">📖</a></td>
<td align="center"><a href="https://github.com/leonlysu"><img src="https://avatars.githubusercontent.com/u/73583724?v=4?s=70" width="70px;" alt=""/><br /><sub><b>leonlysu</b></sub></a><br /><a href="https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/commits?author=leonlysu" title="Code">💻</a></td>
<td align="center"><a href="https://github.com/bonnielliu-cloud"><img src="https://avatars.githubusercontent.com/u/85279550?v=4?s=70" width="70px;" alt=""/><br /><sub><b>bonnielliu-cloud</b></sub></a><br /><a href="#" title="Code">💻</a></td>
<td align="center"><a href="https://github.com/smallpath"><img src="https://avatars.githubusercontent.com/u/10809900?v=4?s=70" width="70px;" alt=""/><br /><sub><b>smallpath</b></sub></a><br /><a href="#" title="Code">💻</a></td>
<td align="center"><a href="https://github.com/susiezhao"><img src="https://avatars.githubusercontent.com/u/13827192?v=4?s=70" width="70px;" alt=""/><br /><sub><b>susiezhao</b></sub></a><br /><a href="#" title="Code">💻</a></td>
<td align="center"><a href="https://github.com/taoran34"><img src="https://avatars.githubusercontent.com/u/9361046?v=4?s=70" width="70px;" alt=""/><br /><sub><b>taoran34</b></sub></a><br /><a href="#" title="Code">💻</a></td>
<td align="center"><a href="https://github.com/Cloudlie"><img src="https://avatars.githubusercontent.com/u/7425309?v=4?s=70" width="70px;" alt=""/><br /><sub><b>Cloudlie</b></sub></a><br /><a href="https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/commits?author=Cloudlie" title="Code">💻</a><a href="https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/issues/created_by/Cloudlie">🐛</a></td>
</tr>
<td align="center"><a href="https://github.com/woson-wang"><img src="https://avatars.githubusercontent.com/u/34298517?v=4?s=70" width="70px;" alt=""/><br /><sub><b>woson-wang</b></sub></a><br /><a href="https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/issues/created_by/woson-wang">🐛</a></td>
<td align="center"><a href="https://github.com/TomatoAres"><img src="https://avatars.githubusercontent.com/u/34213033?v=4?s=70" width="70px;" alt=""/><br /><sub><b>TomatoAres</b></sub></a><br /><a href="https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/pulls?q=author%3ATomatoAres">🐛</a></td>
</tr>
</table>
该项目遵循 [all-contributors](https://github.com/all-contributors/all-contributors) 规范。 欢迎任何形式的贡献！
# 贡献指南
欢迎大家参与到 腾讯云监控插件 @ Grafana 的开发工作，贡献一份力量！
您可以选择如下的贡献方式：
- [贡献 Dashboard 模板](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/tree/master/src/dashboards)
- [贡献代码，提交 Pull Request](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/pulls)
- [反馈 bug，提交 Issue](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/issues/new/choose)
我们会将您加入 [我们的贡献者名单](#contributors)；
贡献方式请参考 [贡献指南](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/blob/master/CONTRIBUTING.md) 文档。
# 许可证
腾讯云监控应用插件在 [Apache License 2.0](https://github.com/TencentCloud/tencentcloud-monitor-grafana-app/blob/master/LICENSE) 许可证下提供。
| 74.59596 | 422 | 0.73717 | yue_Hant | 0.39661 |
6129f731fa70dce317c40030049b9d742d98e6dd | 66 | md | Markdown | README.md | HimanshuMercury/bench_practice | 81b24189de07ebe45adb2078ceec112f62c32cf1 | [
"MIT"
] | 2 | 2019-11-05T14:49:41.000Z | 2020-10-09T12:00:51.000Z | README.md | HimanshuMercury/bench_practice | 81b24189de07ebe45adb2078ceec112f62c32cf1 | [
"MIT"
] | null | null | null | README.md | HimanshuMercury/bench_practice | 81b24189de07ebe45adb2078ceec112f62c32cf1 | [
"MIT"
] | null | null | null | # bench_practice
this Repo contains python programs and txt files
| 22 | 48 | 0.833333 | eng_Latn | 0.995567 |
612ac1e2acbe53462319bb16f40b542beddc2c22 | 4,234 | md | Markdown | README.md | nidorx/roblox-ecs | c6be4a85b13caf1f73facc816a08f20737e4e545 | [
"MIT"
] | 21 | 2020-10-28T06:04:19.000Z | 2021-08-05T09:17:33.000Z | README.md | nidorx/roblox-ecs | c6be4a85b13caf1f73facc816a08f20737e4e545 | [
"MIT"
] | 3 | 2021-02-17T04:49:39.000Z | 2021-07-30T06:24:59.000Z | README.md | nidorx/roblox-ecs | c6be4a85b13caf1f73facc816a08f20737e4e545 | [
"MIT"
] | 9 | 2020-11-04T10:03:32.000Z | 2021-07-13T10:50:10.000Z | <p align="center">
<a href="https://nidorx.github.io/ecs-lua">
<img
src="docs/assets/logo.svg"
alt="https://nidorx.github.io/ecs-lua"
/>
</a>
</p>
<p align="center">
<a href="https://app.travis-ci.com/nidorx/ecs-lua">
<img src="https://app.travis-ci.com/nidorx/ecs-lua.svg?branch=master" alt="Build Status" />
</a>
</p>
<p align="center">
<strong><a href="https://nidorx.github.io/ecs-lua#/">Read the Documentation</a></strong>
</p>
# What is it?
<strong>ECS Lua</strong> is a fast and easy to use ECS (Entity Component System) engine for game development.
<div align="center">
</div>
The basic idea of this pattern is to stop defining entities using a
[hierarchy](https://en.wikipedia.org/wiki/Inheritance_(object-oriented_programming)) of classes and start doing use of
[composition](https://en.wikipedia.org/wiki/Object_composition) in a Data Oriented Programming paradigm.
([More information on Wikipedia](https://en.wikipedia.org/wiki/Entity_component_system)).
Programming with an ECS can result in code that is more efficient and easier to extend over time.
# How does it work?
<div align="center">
</div>
# Talk is cheap. Show me the code!
```lua
local World, System, Query, Component = ECS.World, ECS.System, ECS.Query, ECS.Component
local Health = Component(100)
local Position = Component({ x = 0, y = 0})
local isInAcid = Query.Filter(function()
return true -- it's wet season
end)
local InAcidSystem = System("process", Query.All( Health, Position, isInAcid() ))
function InAcidSystem:Update()
for i, entity in self:Result():Iterator() do
local health = entity[Health]
health.value = health.value - 0.01
end
end
local world = World({ InAcidSystem })
world:Entity(Position({ x = 5.0 }), Health())
```
# Features
**ECS Lua** has no external dependencies and is compatible and tested with [Lua 5.1], [Lua 5.2], [Lua 5.3], [Lua 5.4],
[LuaJit] and [Roblox Luau](https://luau-lang.org/)
- **Game engine agnostic**: It can be used in any engine that has the Lua scripting language.
- **Ergonomic**: Focused on providing a simple yet efficient API
- **FSM**: Finite State Machines in an easy and intuitive way
- **JobSystem**: To running systems in parallel (through [coroutines])
- **Reactive**: Systems can be informed when an entity changes
- **Predictable**:
- The systems will work in the order they were registered or based on the priority set when registering them.
- Reactive events do not generate a random callback when issued, they are executed at a predefined step.
# Goal
To be a lightweight, simple, ergonomic and high-performance ECS library that can be easily extended. The **ECS Lua**
does not strictly follow _"pure ECS design"_.
# Usage
Read our [Full Documentation][docs] to learn how to use **ECS Lua**.
# Get involved
All kinds of contributions are welcome!
🐛 **Found a bug?**
Let me know by [creating an issue][new-issue].
❓ **Have a question?**
[Roblox DevForum][discussions] is a good place to start.
⚙️ **Interested in fixing a [bug][bugs] or adding a [feature][features]?**
Check out the [contributing guidelines](CONTRIBUTING.md).
📖 **Can we improve [our documentation][docs]?**
Pull requests even for small changes can be helpful. Each page in the docs can be edited by clicking the
"Edit on GitHub" link at the bottom right.
[docs]: https://nidorx.github.io/ecs-lua
[bugs]: https://github.com/nidorx/ecs-lua/issues?q=is%3Aissue+is%3Aopen+label%3Abug
[features]: https://github.com/nidorx/ecs-lua/issues?q=is%3Aissue+is%3Aopen+label%3Afeature
[new-issue]: https://github.com/nidorx/ecs-lua/issues/new/choose
[discussions]: https://devforum.roblox.com/t/841175
[Lua 5.1]:https://app.travis-ci.com/github/nidorx/ecs-lua
[Lua 5.2]:https://app.travis-ci.com/github/nidorx/ecs-lua
[Lua 5.3]:https://app.travis-ci.com/github/nidorx/ecs-lua
[Lua 5.4]:https://app.travis-ci.com/github/nidorx/ecs-lua
[LuaJit]:https://app.travis-ci.com/github/nidorx/ecs-lua
[coroutines]:http://www.lua.org/pil/9.1.html
# License
This code is distributed under the terms and conditions of the [MIT license](LICENSE).
| 32.821705 | 119 | 0.711856 | eng_Latn | 0.770201 |
612b1d27f1e56a7355ff5270f12eebd1167bf20f | 13,261 | md | Markdown | _tutorials/04-FirstJobs.md | attesillanpaa/linux-2 | 152a1204641146587765c85d1da96740c301bf90 | [
"MIT"
] | null | null | null | _tutorials/04-FirstJobs.md | attesillanpaa/linux-2 | 152a1204641146587765c85d1da96740c301bf90 | [
"MIT"
] | null | null | null | _tutorials/04-FirstJobs.md | attesillanpaa/linux-2 | 152a1204641146587765c85d1da96740c301bf90 | [
"MIT"
] | 1 | 2020-10-07T19:28:57.000Z | 2020-10-07T19:28:57.000Z | ---
title: Running your first job on Puhti
---
## Logging in
To prepare and run your jobs, you first need to log in to Puhti. You
can use either command line application or a special terminal
program. Command line applications come standard on most operating
systems. Terminal programs may need to installed separately, but they
typically offer more options on things like font size, copy-paste etc.
On Linux or macOS open a terminal. In Windows 10 open Powershell. Give command:
```text
ssh <csc_username>@puhti.csc.fi
```
You can find more detailed instructions in our User Guide: [Connecting
to CSC supercomputers](../../computing/connecting.md).
## What is Puhti?
Puhti, like most modern HPC (High Performance Computing) systems, is
cluster computer. It means that is has a small number of login nodes
and a large number of compute nodes.
When you log in, you end up in one of the two login nodes. Login nodes
are meant for things like moving data and setting up and managing you
batch jobs. You should not run actual jobs on the login nodes. There
are only two login nodes that are shared by everybody, so running big
jobs on them can make the system slow and unresponsive for all.
Jobs should be run in the compute nodes. This is done using the *batch
job system* also called a *scheduler* or a *workload manager*. The
system in use in Puhti is called Slurm.
To run your job through the batch job system you use command **srun**
or write a batch jobs script and use command **sbatch**. We will
discuss this in more detail later.
To check what kind of compute nodes are available in Puhti, see the
User Guide: [Technical details about
Puhti](../../computing/systems-puhti.md).
## Software environment
Puhti has a selection of commonly used bioscience software
available. You can check the listing in
[Applications](../../apps/index.md).
The application listing may not be quite up to date, so it is a good
idea to use **module spider** command to see if a software or software
is available, *e.g*:
```text
module spider bowtie2
```
To avoid conflicts between different applications and versions, most
software on Puhti is installed as *modules*. To use an application you
will need to load the module, *e.g*:
```text
module load bowtie2
```
You can also specify a specific version, *e.g*:
```text
module load bowtie2/2.3.5.1
```
If you do not specify a version, the default version (typically latest
stable release) is loaded.
We also provide a module that loads most commonly used bioscience applications at once:
```text
module load biokit
```
The easiest way to see the content of the biokit module is to load it and check the listing.
To see which modules to load, see the instruction page for each software
For more information on the module system, please see the user guide:
[The module system](../../computing/modules.md).
## Planning your job
To run a job through a batch job system, you will need to reserve
resources, *i.e.* cores, memory and time, suitable for the job. To
decide on the needed resources, you will have to answer some
questions:
### How many cores can my application use?
First a short note on terminology: When speaking about home computers
people usually use terms "processor" and "core". For example most
modern home computers have one processor with two or more cores. When
speaking about HPC machines the corresponding terms are "socket" and
"CPU". For example Puhti compute nodes have two sockets with 20 CPUs
each. This tutorial uses terms "processors/cores", as thay are
probably more familiar for people without HPC background.
Applications can be divided into categories according to the amount of cores they can use:
- **Serial applications**
- Can only use one core
- Many bioscience applications belong to this category
- If the application manual makes no mention of number of cores or threads to use, the application is probably serial
- Reserving more cores will not make these applications any faster as they can only use one
- **Shared memory/threaded/OpenMP applications**
- Can use more than one core, but all cores mut be in the same node (so in Puhti max 40 cores)
- Most bioscience applications that can use more than one core are in this category
- Also remember to tell the application to use the number of cores to use
- Check the application documentation for correct command line options
- Usually best to batch the number of cores to the number of threads, but check application documentation
- **MPI parallel applications**
- Can use more than one core, cores need not be in the same node
- Only very few bioscience applications in this category
- **Hybrid parallel applications**
- A job where each MPI task is an OpenMP task
- Quite rare in bioscience applications
To find out what category your application belongs to, read the documentation.
It should also be noted that more cores does not automatically mean
faster run time. Reserving too many cores can actually make teh
software run slower. The optimal number of cores depends on the
application, data and the analysis performed. You should check the
application documentation to see if the developers give any
guidelines. It is also a good idea to run some tests with different
core numbers to see how well the application scales.
### How much memory does my application need?
Estimating the required memory can be quite difficult. In many cases
it is affected by the data and the application options chosen. Also
number of threads used can often the memory requirements.
You should read the application documentation to see if the developers
give any estimate. Often it is also helpful to check the user forums,
if the software has one.
Often, especially when running an application fro the first time, you
just have to make a guess. If you get an error message about memory
running out, increase memory reservation and try again. If the job
finishes, you can check the actual memory usage and use that to make
the reservations in the future.
More information can be found in this FAQ entry: [How to estimate how
much memory my batch job
needs?](../faq/how-much-memory-my-job-needs.md)
### How much time should I reserve?
Knowing the run tme in advance can also be difficult if you are not
familiar with an application.
You should make sure to reserve enough, as the job will be stopped
when the time reservation runs out, whether it is finished or not.
On the other hand reserving to much time is not that big of a
problem. The job will finish when the last task of the job
finishes. Your job will also consume billing units according to the
actual elapsed time, not according to reservation.
It is OK to reserve teh maximum time allowed in the partition you are
using when running an application first time. After the job finishes,
you can check the elapsed time, and make a more informed reservation
next time.
## Running your job
### Interactive jobs
Interactive jobs are good for things like testing, running small tasks
and for software that has graphical user interface.
As mentioned, you should not run jobs in the login node. Instead you
can use **sinteractive** command to open an interactive shell:
```text
sinteractive -i
```
For more detailed instruction, see the User Guide: [Interactive usage](../../computing/running/interactive-usage.md)
Longer jobs that take more resources are best run as batch jobs.
### Batch jobs
Running a batch job typically has three steps:
1. Make sure you have all the necessary input files
1. For instructions on how to move data from your own computer to Puhti, see section Data/Moving data in the User Guide
2. Write a batch job script
1. Use a text editor like nano, vim or emacs to write the script
2. If you write the script on your own computer, and move it to
Puhti, some care should be taken. Make sure it is saved as text,
not as a Word doc or something like that. Also be aware that Windows
treats line endings differently that Linux, and this can cause problems.
3. Submit the job
Here is an example batch job script. It is saved as "myjob.sh"
```text
#!/bin/bash
#SBATCH --job-name=bowtie2
#SBATCH --account=project_123456
#SBATCH --ntasks=1
#SBATCH --nodes=1
#SBATCH --cpus-per-task=16
#SBATCH --mem=16g
#SBATCH --time=04:00:00
#SBATCH --partition=small
module load biokit
bowtie2 -p $SLURM_CPUS_PER_TASK -x genome -1 reads_1.fq -2 reads_2.fq > output.sam
```
All the lines staring with **#SBATCH** are passed on to the batch job
system. We use them to request the necessary resources.
Job name (--job-name) is mainly used to identify your job *e.g.* when
listing jobs with **squeue**.
It is necessary to to inform the system which project should be
billed. This is done with --account. You can check the projects that
you belong to in [MyCSC](https://my.csc.fi/myProjects).
Bowtie2 is a shared memory application. As discussed earlier that
means it can use more than one core, but all cores must be in the same
node. We specify that we want to run one task (--ntask=1) in one node
(--nodes=1) using 16 cores (--cpus-per-task):
```text
#SBATCH --ntasks=1
#SBATCH --nodes=1
#SBATCH --cpus-per-task=16
```
Because it is a shared memory application we can use --mem to specify
the total memory requested for the task. For a MPI job we would have
to request memory per core with --mem-per-cpu.
```text
#SBATCH --mem=16G
```
The time reservation is given as hours:minutes:seconds: hh:mm:ss. in
this case we reserve four hours:
```text
#SBATCH --time=04:00:00
```
We also need to specify which queue we want the job to run in. this
specified with teh --partition option. For most bioscience jobs
"small" is the correct choice.
```text
#SBATCH --partition=small
```
You can check the available partitions in the User Guide: [Available
batch job partitions](../../computing/running/batch-job-partitions.md)
By default various outputs and error messages that would be printed to
the screen if the application was run interactively, are saved in a
file called *slurm-<jobid>.out*. Sometimes it is clearer to separate
the outputs and errors. This can be done adding options --output and
--error. The %j will be replaced by jobid in the file name.
```text
#SBATCH --output=output_%j.txt
#SBATCH --error=errors_%j.txt
```
There are also other available options. For a more detailed
explanation, please see the User Guide: [Creating a batch job script
for Puhti](../../computing/running/creating-job-scripts-puhti.md)
When you have written the batch job script, you cab submit the job to the queue:
```text
sbatch myjob.sh
```
It is possible to launch a job directly with command **srun** by
giving the options given as #SBATCH lines directly as command line
options, but writing a batch job script is generally preferable for
clarity and ease of re-use if you *e.g.* want submit a similar job wit
different data or modified parameters.
### Array jobs
```<To be added>```
## Managing jobs
Check your current jobs, both running and queueing:
```text
squeue -u <username>
```
Cancel a submitted batch job with:
```text
scancel <jobid>
```
## Monitoring resource usage
```<To be added>```
## Troubleshooting
### Getting familiar with a new program
Here are some useful steps when familiarizing yourself with a new program.
- Read the manual
- It may be helpful to first try run the program interactively to find the correct command line options
- Good chance to use top to get rough estimate on memory use etc
- If developers provide some test or example data, run it first
- Make sure the results are as expected
- You can use test partition to check your batch job script
- Limits : 15 min, 2 nodes
- Job turnaround usually very fast
- Can be useful to spot typos, missing files etc before submitting a job that will spend long in the queue
- Before very large runs, it’s a good idea do a smaller trial run
- Check that results are as expected
- Check resource usage after test run and adjust accordingly
- Try different core numbers and see how the software scales
### Troubleshooting checklist
Start with these if you job fails:
1. Did the job run out of time?
2. Did the job run out of memory?
3. Did the job actually use resources you specified?
- Problems in batch job script can cause parameters to be ignored and default values getting used instead
4. Did it fail immediately or did it run for some time?
- Jobs failing immediately are often due to something simple like
typos in command line, missing inputs, bad parameters etc
5. Check the error file captured by the batch job script
6. Check any other error files and logs the program may have produced
7. Error messaged can sometimes be long, cryptic and a bit intimidating,
but try skimming through them and see if you can spot something
”human readable” instead of ”nerd readable”
- Often you can spot the actual problem easily if you go through the
whole message. Something like ”required input file so-and-so missing”
or ”parameter X out of range” etc.
If you can't figure it out, please don't hesitate to contact us at
servicedesk@csc.fi. Remember to include relevant information like what
| 37.041899 | 123 | 0.760652 | eng_Latn | 0.999278 |
612b8f87310a532f1eb79ece7bcb50b954622406 | 1,757 | md | Markdown | content/games/Moon_Nation_Game/index.zh-cn.md | itey/metabd | 263376ea70afea08cbc752c7117928826d2ec61a | [
"MIT"
] | null | null | null | content/games/Moon_Nation_Game/index.zh-cn.md | itey/metabd | 263376ea70afea08cbc752c7117928826d2ec61a | [
"MIT"
] | 6 | 2022-03-14T18:35:35.000Z | 2022-03-28T18:43:54.000Z | content/games/Moon_Nation_Game/index.zh-cn.md | itey/metabd | 263376ea70afea08cbc752c7117928826d2ec61a | [
"MIT"
] | null | null | null | ---
title: "Moon Nation Game"
description: "Largest Space-Based RPG on BSC. Invest-Play-Earn"
lead: "Largest Space-Based RPG on BSC. Invest-Play-Earn"
date: 2022-02-28T12:51:55.898+0800
lastmod: 2022-02-28T12:51:55.898+0800
draft: false
featuredImage: ["100_moon-nation-game.jpg"]
score: "175"
status: "Development"
blockchain: ["Binance"]
nft_support: "Yes"
free_to_play: "Crypto"
play_to_earn: ["NFT","Crypto"]
website: "https://www.moonnation.org/?utm_source=PlayToEarn.net&utm_medium=organic&utm_campaign=gamepage"
twitter: "https://twitter.com/MoonNation0"
discord: "https://discord.com/invite/hfKU8pqSMt"
telegram: "https://t.me/moonnation"
github:
youtube: "https://www.youtube.com/channel/UCkkBiGhY8lJmv2AoudTSpxQ"
twitch:
facebook: "https://web.facebook.com/groups/258204765724858"
instagram: "https://www.instagram.com/moonnationgame/"
reddit: "https://www.reddit.com/r/TheMoonNation/"
medium:
steam:
gitbook:
googleplay:
appstore:
categories: ["games"]
games: ["RPG","Space","Strategy"]
toc: false
pinned: false
weight:
---
Moon Nation Game is the first of its kind: A next generation, crypto-fueled, blockchain-supported role-playing space game with Moon Nation Game ($MNG) as its native platform token.<br> <br> Users can achieve higher ranks and learn new skills by doing tasks and spending currency. Reaching a new rank can provide rewards, prizes and special powers. <br> <br> Some communities may host competitions, or even engage in war. If so, the winner will receive certain resources from the losing side. In addition to individual rewards, some community-wide rewards will be available as well.<br> <br> Moon Nation will have its own unique resources, weapons and NFTS, all available in game.<br> <br> PLAY-INVEST-EARN | 45.051282 | 705 | 0.762664 | eng_Latn | 0.701536 |
612ba7d3b014ba7b73bff27b1927abc163a7b104 | 518 | md | Markdown | README.md | LMesaric/RG-FER-2021 | a4989be90ee185c7749a92cc7301490a6f0ca52a | [
"MIT"
] | 3 | 2021-01-22T23:30:31.000Z | 2021-01-24T20:31:45.000Z | README.md | LMesaric/RG-FER-2021 | a4989be90ee185c7749a92cc7301490a6f0ca52a | [
"MIT"
] | null | null | null | README.md | LMesaric/RG-FER-2021 | a4989be90ee185c7749a92cc7301490a6f0ca52a | [
"MIT"
] | null | null | null | # RG-FER-2021
Laboratory exercises for course Computer Graphics at Faculty of Electrical Engineering and Computing, University of Zagreb.
<br>
# Lab1 - B-spline
Model of an F-16 aircraft travels along a B-spline determined by a set of control points.
<br>
<br>
# Lab2 - Particle system
<br>
# Lab3 - Numerical integration visualization [[link](https://github.com/LMesaric/ODE-Explorer)]
[](https://github.com/LMesaric/ODE-Explorer)
| 19.923077 | 123 | 0.735521 | eng_Latn | 0.584102 |
612bb7869067e2e4e6f698a0883997636fcee97d | 6,788 | md | Markdown | translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md | RahmaNiftaliyev/docs | 4e1ee81587e95617e25aa51c9d761289b193bd37 | [
"CC-BY-4.0",
"MIT"
] | 5 | 2021-12-23T00:28:02.000Z | 2022-01-20T17:53:05.000Z | translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md | RahmaNiftaliyev/docs | 4e1ee81587e95617e25aa51c9d761289b193bd37 | [
"CC-BY-4.0",
"MIT"
] | 63 | 2022-02-01T12:55:45.000Z | 2022-03-30T14:21:14.000Z | translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md | RahmaNiftaliyev/docs | 4e1ee81587e95617e25aa51c9d761289b193bd37 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: About remote repositories
redirect_from:
- /articles/working-when-github-goes-down
- /articles/sharing-repositories-without-github
- /articles/about-remote-repositories
- /articles/which-url-should-i-use
- /articles/which-remote-url-should-i-use
- /github/using-git/which-remote-url-should-i-use
- /github/using-git/about-remote-repositories
- /github/getting-started-with-github/about-remote-repositories
- /github/getting-started-with-github/getting-started-with-git/about-remote-repositories
intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update.'
versions:
fpt: '*'
ghes: '*'
ghae: '*'
ghec: '*'
---
## About remote repositories
A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
You can only push to two types of URL addresses:
* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git`
* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git`
Git associates a remote URL with a name, and your default remote is usually called `origin`.
## Creating remote repositories
You can use the `git remote add` command to match a remote URL with a name.
For example, you'd type the following in the command line:
```shell
git remote add origin <em> <REMOTE_URL> </em>
```
This associates the name `origin` with the `REMOTE_URL`.
You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories).
## Choosing a URL for your remote repository
There are several ways to clone repositories available on {% data variables.product.product_location %}.
When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
## Cloning with HTTPS URLs
The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy.
When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user-settings.password-authentication-deprecation %}
{% data reusables.command_line.provide-an-access-token %}
{% tip %}
**Tips**:
- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
{% endtip %}
{% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
## Cloning with SSH URLs
SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
{% tip %}
**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)."
{% endtip %}
## Cloning with {% data variables.product.prodname_cli %}
You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
{% ifversion not ghae %}
## Cloning with Subversion
You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
{% endif %}
| 71.452632 | 724 | 0.765616 | eng_Latn | 0.973206 |
612c050783f533bbbda1a98e32bed6007b5b72f0 | 1,851 | md | Markdown | docs/c-language/null-statement-c.md | Erikarts/cpp-docs.es-es | 9fef104c507e48ec178a316218e1e581753a277c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/c-language/null-statement-c.md | Erikarts/cpp-docs.es-es | 9fef104c507e48ec178a316218e1e581753a277c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/c-language/null-statement-c.md | Erikarts/cpp-docs.es-es | 9fef104c507e48ec178a316218e1e581753a277c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: NULL (Instrucción) (C)
ms.date: 11/04/2016
helpviewer_keywords:
- semicolon, C null statement
- expressions [C++], null
- null statement
- null values, expressions
ms.assetid: 72576ce6-26d0-4379-be65-fee522088790
ms.openlocfilehash: 4fdfa2283e40856ccaffd55daacb697b1344134b
ms.sourcegitcommit: f4be868c0d1d78e550fba105d4d3c993743a1f4b
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 02/12/2019
ms.locfileid: "56148457"
---
# <a name="null-statement-c"></a>NULL (Instrucción) (C)
Una "instrucción null" es una instrucción que solo contiene un punto y coma; puede aparecer en cualquier lugar donde se espere una instrucción. No ocurre nada cuando se ejecuta una instrucción null. La manera correcta de escribir una instrucción null es:
## <a name="syntax"></a>Sintaxis
> **;**
## <a name="remarks"></a>Comentarios
Las instrucciones como **do**, **for**, **if** y `while` requieren que aparezca una instrucción ejecutable como cuerpo de la instrucción. La instrucción null cumple el requisito sintáctico en los casos en que no se necesita un cuerpo de instrucción sustancial.
Como con cualquier otra instrucción de C, puede incluir una etiqueta delante de una instrucción null. Para etiquetar un elemento que no es una instrucción, como la llave de cierre de una instrucción compuesta, puede etiquetar una instrucción null e insertarla inmediatamente delante del elemento para obtener el mismo efecto.
En este ejemplo se ilustra la instrucción null:
```C
for ( i = 0; i < 10; line[i++] = 0 )
;
```
En este ejemplo, la expresión de bucle de la instrucción **for** `line[i++] = 0` inicializa los 10 primeros elementos de `line` en 0. El cuerpo de la instrucción es una instrucción null, ya que no se requieren más instrucciones.
## <a name="see-also"></a>Vea también
[Instrucciones](../c-language/statements-c.md)
| 43.046512 | 325 | 0.76067 | spa_Latn | 0.967342 |
612c05393f85f057041ba72fb6f492984e2075dd | 1,471 | md | Markdown | content/APIReference/BecknGatewayAppSide.md | harshavardhanc/developer-docs | 03d642740397364c103ba45e99d174c61cb80433 | [
"MIT"
] | null | null | null | content/APIReference/BecknGatewayAppSide.md | harshavardhanc/developer-docs | 03d642740397364c103ba45e99d174c61cb80433 | [
"MIT"
] | null | null | null | content/APIReference/BecknGatewayAppSide.md | harshavardhanc/developer-docs | 03d642740397364c103ba45e99d174c61cb80433 | [
"MIT"
] | null | null | null | ---
title: "Beckn Gateway App Side API"
metaTitle: "Developer Documentation"
metaDescription: "Beckn Mobility is a set of open specifications and protocols to create a Digital Infrastructure for public good. It enables any application to connect to Mobility Service Providers (like Cab, Bus and Metro Services, EV Charging Stations, Parking Services, Tolls etc) through a network of Gateways."
---
## Introduction
This API is for connecting **Beckn Apps** to **Beckn Gateways**. The BG will implement the following endpoints -
- [Journey/search](/APIReference/BecknGatewayDemandSide/searchJourneys)
- [Journey/init](/APIReference/BecknGatewayDemandSide/initJourney)
- [Journey/confirm](/APIReference/BecknGatewayDemandSide/confirmJourney)
- [Journey/State/update](/APIReference/BecknGatewayDemandSide/updateJourneyState)
- [Journey/Trip/add](/APIReference/BecknGatewayDemandSide/addTrip)
- [Journey/Trip/remove](/APIReference/BecknGatewayDemandSide/removeTrip)
- [Trip/track](/APIReference/BecknGatewayDemandSide/trackTrip)
- [Trip/FareProducts/get](/APIReference/BecknGatewayDemandSide/getFareProducts)
- [Trip/Stop/add](/APIReference/BecknGatewayDemandSide/addStop)
- [Trip/Stop/remove](/APIReference/BecknGatewayDemandSide/removeStop)
- [Trip/State/update](/APIReference/BecknGatewayDemandSide/updateTripState)
- [Trip/Travelers/add](/APIReference/BecknGatewayDemandSide/addTravelers)
- [Travelers/Cred/cb_get](/APIReference/BecknGatewayDemandSide/getTravelersCred)
| 63.956522 | 316 | 0.818491 | yue_Hant | 0.729962 |
612c7c4f734464fa3fa54237fbae314607ccc8cb | 17,126 | md | Markdown | documentation/running_bolt_commands.md | carabasdaniel/bolt | 4485f0b8fd109f31deba20c1a64a8641e837a975 | [
"Apache-2.0"
] | null | null | null | documentation/running_bolt_commands.md | carabasdaniel/bolt | 4485f0b8fd109f31deba20c1a64a8641e837a975 | [
"Apache-2.0"
] | null | null | null | documentation/running_bolt_commands.md | carabasdaniel/bolt | 4485f0b8fd109f31deba20c1a64a8641e837a975 | [
"Apache-2.0"
] | null | null | null | # Run commands on remote targets
You can use Bolt commands to connect to remote targets and perform actions on
them. These actions range in complexity from invoking a simple command to
running a series of commands and tasks as part of an orchestration workflow.
For a full list of available Bolt commands, see the [Bolt command
reference](bolt_command_reference.md).
## Run a command
Bolt can run arbitrary commands on remote targets. To run a command, provide a
command and a list of targets to run the command on.
_\*nix shell command_
```shell
bolt command run 'pwd' --targets servers
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'Get-Location' -Targets servers
```
> 🔩 **Tip:** If a command contains spaces or special shell characters, wrap
> the command in single quotation marks.
### Run a quoted command
If you need to run a command that uses quotation marks, you must properly escape
the quotations. The way you escape the quotations depends on whether you're
using Bash or PowerShell.
In a Bash shell, use backslashes `\` or double the the quotation marks:
_\*nix shell command_
```shell
bolt command run "Get-WMIObject Win32_Service -Filter ""Name like '%mon'""" -t localhost
```
In a PowerShell shell, use a combination of backslashes `\` and doubling of
quotation marks. The example below uses two double quotation marks to quote the
value being passed to `Filter`, however the example also uses a backslash so
that Bolt's underlying Ruby argument parser accepts the command.
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command "Get-WMIObject Win32_Service -Filter \""Name like '%mon'\""" -Targets localhost
```
### Read a command from a file
Reading a command from a file is useful when you need to run a script on a target
that does not permit file uploads. To read a command from a file, pass an `@` symbol,
followed by the relative path to the file.
_\*nix shell command_
```shell
bolt command run @configure.sh --targets servers
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command '@configure.ps1' -Targets servers
```
> **Note:** In PowerShell, always wrap the file name in single quotes.
### Read a command from stdin
To read a command from standard input (stdin), pipe the results from another
command to Bolt and pass a single dash (`-`) as the command.
_\*nix shell command_
```shell
cat command.sh | bolt command run - --targets servers
```
Reading from stdin is not supported by the PowerShell module.
## Specify targets
The most common way to specify targets on the command line is with the
`targets` option. This option accepts a comma-separated list of targets.
_\*nix shell command_
```shell
bolt command run 'pwd' --targets bolt1.example.org,bolt2.example.org
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'pwd' -Targets bolt1.example.org,bolt2.example.org
```
### Specify targets from an inventory file
If you have an inventory file, you can list targets and groups of targets by
name instead of using the target's Universal Resource Identifier (URI).
_\*nix shell command_
```shell
bolt command run 'pwd' --targets servers,databases
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'pwd' -Targets servers,databases
```
### Specify targets using glob matching
Bolt supports glob matches for targets. This is helpful when you have several
targets that you want to run a comand on that have similar names. For example,
to run a command on all targets that start with the word `bolt`:
_\*nix shell command_
```shell
bolt command run 'pwd' --targets 'bolt*'
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'pwd' -Targets 'bolt*'
```
### Read targets from a file
To read a file of targets, pass an `@` symbol, followed by the relative path to
the file, to the `targets` option.
_\*nix shell command_
```shell
bolt command run 'pwd' --targets '@targets.txt'
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'pwd' -Targets '@targets.txt'
```
> **Note:** In PowerShell, always wrap the file name in single quotes.
### Read targets from stdin
To read a list of targets from stdin, pipe the results from another command to
Bolt and pass a single dash (`-`) to the `targets` option.
_\*nix shell command_
```shell
cat targets.txt | bolt command run 'pwd' --targets -
```
Reading from stdin is not supported by the PowerShell module.
### Specify targets from the previous command
After every execution, Bolt writes information about the result of that run to a
`.rerun.json` file inside the Bolt project directory. You can use the
`.rerun.json` file together with the `rerun` option to specify targets for
future commands. The `rerun` option accepts one of three values:
- `success`: The list of targets the command succeeded on.
- `failure`: The list of targets the command failed on.
- `all`: All of the targets the command ran on.
For example, if you need to run a command that is dependent on the success of
the previous command, you can target the successful targets with the `success`
value.
_\*nix shell command_
```shell
bolt task run restart_server --targets servers --rerun success
```
_PowerShell cmdlet_
```powershell
Invoke-BoltTask -Name restart_server -Targets servers -Rerun success
```
#### Disable `.rerun.json`
If you want to preserve the results of a specific Bolt run and run multiple
`rerun` commands against it, you can disable the `.rerun.json` file.
_\*nix shell command_
Use the `--no-save-rerun` option to disable saving the rerun file:
```shell
bolt task run restart_server --targets server --rerun success --no-save-rerun
```
_PowerShell cmdlet_
Use the `-SaveRerun` argument with a value of `$false` to disable saving the
rerun file:
```powershell
Invoke-BoltTask -Name restart_server -Targets servers -Rerun success -SaveRerun:$false
```
## Specify connection credentials
To establish connections with remote targets, Bolt needs to provide credentials
to the target. You can provide credentials at the command line or in an
inventory file, and the credentials you provide might vary based on the
operating system the target is running.
Whether a target is running a Unix-like operating system or Windows, the
simplest way to specify credentials is to pass the `user` and `password`
to the Bolt command:
_\*nix shell command_
```shell
bolt command run 'pwd' --targets servers --user bolt --password puppet
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'pwd' -Targets servers -User bolt -Password puppet
```
If you'd prefer to have Bolt securely prompt for a password, so that it does not
appear in a process listing or on the console, use the `password-prompt` option
instead:
_\*nix shell command_
```shell
bolt command run 'pwd' --targets servers --user bolt --password-prompt
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'pwd' -Targets servers -User bolt -PasswordPrompt
```
## Specify a transport
Bolt uses a specific transport to establish a connection with a target. By
default, Bolt connects to targets using the `ssh` transport. You can use one of
the methods below to set a different transport from the command line, or you can
configure transports in your inventory file.
You can specify the transport used to connect to a specific target by setting
it as the protocol in the target's URI:
_\*nix shell command_
```shell
bolt command run 'Get-Location' --targets winrm://windows.example.org
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'Get-Location' -Targets winrm://windows.example.org
```
You can also use the `transport` command-line option:
_\*nix shell command_
```shell
bolt command run 'Get-Location' --targets windows.example.org --transport winrm
```
_PowerShell cmdlet_
```powershell
Invoke-BoltCommand -Command 'Get-Location' -Targets windows.example.org -Transport winrm
```
📖 **Related information**
- [Bolt transports reference](bolt_transports_reference.md)
## Run a script
When you run a script on a remote target, Bolt copies the script from your
workstation to a temporary directory on the target, runs the script, and then
deletes the script from the target.
You can run scripts in any language, as long as the appropriate interpreter is
installed on the remote system. This includes scripting languages such as Bash,
PowerShell, Python, and Ruby.
To run a script, provide the path to the script on the workstation and a list of
targets to run the script on.
_\*nix shell command_
```shell
bolt script run ./scripts/configure.sh --targets servers
```
_PowerShell cmdlet_
```powershell
Invoke-BoltScript -Script ./scripts/configure.ps1 -Targets servers
```
### Pass arguments to a script
Argument values are passed literally and are not interpolated by the shell on
the remote host.
_\*nix shell command_
To pass arguments to a script, specify them after the command:
```shell
bolt script run ./scripts/configure.sh --targets servers arg1 arg2
```
_PowerShell cmdlet_
To pass arguments to a script, use the `-Arguments` parameter:
```powershell
Invoke-BoltScript -Script ./scripts/configure.sh -Targets servers -Arguments arg1 arg2
```
> 🔩 **Tip:** If an argument contains spaces or special characters, wrap them
> in single quotes.
### Requirements for running a script
Depending on a target's operating system, there are additional requirements for
running scripts:
- On Unix-like targets, your scripts must include a shebang line specifying the
interpreter. For example, a Bash script should provide the path to the Bash
interpreter:
```bash
#!/bin/bash
echo hello
```
- For Windows targets, you might need to enable file extensions. By default,
Windows targets support the extensions `.ps1`, `.rb`, and `.pp`. To add
additional file extensions, add them to the `winrm` configuration section of
your inventory file:
```yaml
# inventory.yaml
config:
winrm:
extensions:
- .py
- .pl
```
## Run a task
Tasks are single actions that you can execute on a target. They are similar
to scripts, but have metadata, accept structured input, and return structured
output. You can write tasks that are specific to your project or download
modules from the Puppet Forge that include tasks.
To run a task, provide the name of the task and a list of targets to run the
task on.
_\*nix shell command_
```shell
bolt task run facts --targets servers
```
_PowerShell cmdlet_
```powershell
Invoke-BoltTask -Name facts -Targets servers
```
### Pass parameters to a task
If a task accepts parameters, you can pass them to Bolt as part of the command.
_\*nix shell command_
To pass parameters to a task, add parameter declarations of the form
`parameter=value` to the command:
```shell
bolt task run package action=status name=apache2 --targets servers
```
_PowerShell cmdlet_
To pass parameters to a task, add an object with parameter declarations to
the command:
```powershell
Invoke-BoltTask -Name package -Targets servers -Params @{action='status';name='apache2'}
```
📖 **Related information**
- [Running tasks](bolt_running_tasks.md)
- [Writing tasks](writing_tasks.md)
- [Installing modules](bolt_installing_modules.md)
## Run a plan
Plans are sets of tasks and commands that can be combined with other logic. They
allow you to do complex operations, such as running multiple tasks with one
command, computing values for the input for a task, or running certain tasks
based on the results of another task. Similar to tasks, you can write plans that
are specific to your project or download modules from the Puppet Forge that
include plans.
To run a plan, provide the name of the plan.
_\*nix shell command_
```shell
bolt plan run myplan
```
_PowerShell cmdlet_
```powershell
Invoke-BoltPlan -Name myplan
```
### Pass parameters to a plan
If a plan accepts parameters, you can pass them to Bolt as part of the command.
_\*nix shell command_
To pass parameters to a plan, add parameter declarations of the form
`parameter=value` to the command:
```shell
bolt plan run reboot targets=servers
```
_PowerShell cmdlet_
To pass parameters to a task, add an object with parameter declarations to
the command:
```powershell
Invoke-BoltTask -Name reboot -Params @{targets='servers'}
```
### Pass targets to a plan parameter
If a plan accepts a `targets` parameter with the type `TargetSpec`, you can
use the `targets` command-line option to provide a value to the parameter.
_\*nix shell command_
```shell
bolt task run reboot --targets servers
```
_PowerShell cmdlet_
```powershell
Invoke-BoltPlan -Name reboot -Targets servers
```
📖 **Related information**
- [Running plans](bolt_running_plans.md)
- [Writing YAML plans](writing_yaml_plans.md)
- [Writing plans in the Puppet language](writing_plans.md)
- [Installing modules](bolt_installing_modules.md)
## Upload a file or directory
Bolt can copy files and directories from your workstation to remote targets. To
upload a file or directory, provide the `source` path on your workstation, the
`destination` path on the remote target that it should be copied to, and a
list of targets.
Both the `source` and `destination` accept absolute and relative paths. If you
provide a relative path as the `destination`, Bolt will copy the file relative
to the current working directory on the target. Typically, the current working
directory for the target is the log-in user's home directory.
_\*nix shell command_
```shell
bolt file upload /path/to/source /path/to/destination --targets servers
```
_PowerShell cmdlet_
```powershell
Send-BoltFile -Source /path/to/source -Destination /path/to/destination -Targets servers
```
## Download a file or directory
Bolt can copy files and directories from remote targets to a destination
directory on your workstation. To download a file or directory, provide the
`source` path on the remote target, the path to the `destination` directory on
the workstation, and a list of targets.
Both the `source` and `destination` accept absolute and relative paths. If you
provide a relative path as the `source`, Bolt will copy the file relative to the
current working directory on the target. Typically, the current working
directory for the target is the log-in user's home directory.
_\*nix shell command_
```shell
bolt file download /path/to/source /path/to/destination --targets servers
```
_PowerShell cmdlet_
```powershell
Receive-BoltFile -Source /path/to/source -Destination /path/to/destination -Targets servers
```
The `destination` on the workstation is a path to a directory that the downloaded
file or directory is copied to. If the `destination` directory does not exist,
Bolt will create it for you.
Bolt saves each file or directory it downloads to a subdirectory of the
`destination` directory that matches the URL-encoded name of the target it was
downloaded from. The target directory names are URL-encoded to ensure that they
are valid directory names.
For example, the following command downloads the SSH daemon configuration file from
two targets, `linux` and `ssh://example.com`, saving it to the destination
directory `sshd_config`:
_\*nix shell command_
```shell
bolt file download /etc/ssh/sshd_config sshd_config --targets linux,ssh://example.com
```
_PowerShell cmdlet_
```powershell
Receive-BoltFile -Source /etc/ssh/sshd_config -Destination sshd_config -Targets linux,ssh://example.com
```
After running this command from the root of your project directory, your project
directory structure would look similar to this:
```shell
.
├── bolt-project.yaml
├── inventory.yaml
└── sshd_config/
├── linux/
│ └── sshd_config
└── ssh%3A%2F%2Fexample.com/
└── sshd_config
```
> 🔩 **Tip:** To avoid creating directories with special characters, give your
> targets a simple, human-readable name.
## Apply Puppet code
### Apply Puppet code from a file
You can directly apply Puppet code from a file containing Puppet code (known as
a manifest) to your targets. To apply Puppet manifest code to a target, provide
the path to the manifest file and a list of targets.
The Puppet Agent package needs to be installed on the target for the manifest
code to be run. When you apply Puppet manifest code, Bolt ensures that the
Puppet Agent package is installed on the target.
_\*nix shell command_
```shell
bolt apply manifests/servers.pp --targets servers
```
_PowerShell cmdlet_
```powershell
Invoke-BoltApply -Manifest manifests/servers.pp -Targets servers
```
### Apply Puppet code from the command line
You can also apply Puppet code directly to your targets, without the need
for writing it to a file first. To apply Puppet code directly to a target,
use the `execute` command-line option.
_\*nix shell command_
```shell
bolt apply --execute "file { '/etc/puppetlabs': ensure => present }" --targets servers
```
_PowerShell cmdlet_
```powershell
Invoke-BoltApply -Execute "file { '/etc/puppetlabs': ensure => present}" -Targets servers
```
📖 **Related information**
- [Applying Puppet code](applying_manifest_blocks.md)
| 27.184127 | 107 | 0.758321 | eng_Latn | 0.991726 |
612ca7d5a7cbad8e69232355d474380534ab8131 | 2,494 | md | Markdown | README.md | thearchitector/practical-pig | fc91c6c178ee14642c845fb6a0bb22610aabb416 | [
"MIT"
] | 4 | 2020-05-24T16:41:28.000Z | 2020-09-09T02:52:13.000Z | README.md | thearchitector/practical-pig | fc91c6c178ee14642c845fb6a0bb22610aabb416 | [
"MIT"
] | null | null | null | README.md | thearchitector/practical-pig | fc91c6c178ee14642c845fb6a0bb22610aabb416 | [
"MIT"
] | null | null | null | # practical-pig
[](https://rubygems.org/gems/practical-pig)
[](https://travis-ci.org/github/thearchitector/practical-pig)
[](https://rubygems.org/gems/practical-pig)
[](./LICENSE)
Practical Pig is an opinionated Ruby on Rails template that makes use of webpacker-pnpm, RuboCop, and Prettier to provide a simple yet robust foundation for any web application.
## Features
- Opinionated so you don't have to deal with the nitty-gritty
- Provides production-ready application templates
- Agnostic of underlying Rails version
## Installation and Usage
Assuming you have `pnpm` installed, simply download the gem to your system and then create a new repository as you would using `rails`.
```sh
$ gem install practical-pig
$ pig new APP_PATH
```
To view the help dialog, you may run `pig help new`, which will yield the following output:
```plaintext
Usage:
pig new APP_PATH
Options:
-q, [--quiet], [--no-quiet] # Suppress status output
[--with-hmr], [--no-with-hmr] # Install Webpack HMR development server
Description:
`pig new` will generate a new Ruby on Rails application and modify it to adhere
to Practical Pig's application design guidelines.
The APP_PATH you provide will be used as the path of the application during
creation, with its name being the basename (last part of the path). In every
case, the new application will be generated relative to the current working
directory (where you execute this command).
By design, your application name must start and end with an alphanumeric
character.
This command makes use of `rails new` under the hood but does not accept any
generator options.
```
## License
MIT License
Copyright (c) 2020 Elias Gabriel
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the conditions outlined in [LICENSE](./LICENSE).
| 39.587302 | 177 | 0.762229 | eng_Latn | 0.983476 |
612e3abcb97dd75836c606d0df7dbfc0471a6ee5 | 3,627 | md | Markdown | README.md | conrad10781/php-git-server | 6df084e3ef88b22b3d06a38bbdb4060fb83856f2 | [
"MIT"
] | null | null | null | README.md | conrad10781/php-git-server | 6df084e3ef88b22b3d06a38bbdb4060fb83856f2 | [
"MIT"
] | null | null | null | README.md | conrad10781/php-git-server | 6df084e3ef88b22b3d06a38bbdb4060fb83856f2 | [
"MIT"
] | null | null | null | # php-git-server
DAV based PHP based Git server. No dependencies on git command.
## Install
Install latest version using [composer](https://getcomposer.org/).
```
$ composer require rcs_us/php-git-server
```
## Usage
The server extends sabre.io's DAV server(http://sabre.io/dav/) and nikic's FastRoute (https://github.com/nikic/FastRoute).
A basic implementation would look like the following:
```php
if (PHP_SAPI == "cli-server") {
// To help the built-in PHP dev server, check if the request was actually for
// something which should probably be served as a static file
$file = __DIR__ . $_SERVER['REQUEST_URI'];
if (is_file($file)) {
return false;
}
}
// Define source path ( built in PHP server doesn't like relative paths )
defined('SOURCE_PATH')
|| define('SOURCE_PATH', (getenv('SOURCE_PATH') ? getenv('SOURCE_PATH') : dirname(__DIR__)));
defined('REPOSITORY_PATH')
|| define('REPOSITORY_PATH', (getenv('REPOSITORY_PATH') ? getenv('REPOSITORY_PATH') : "/tmp/git-repositories"));
$loader = require SOURCE_PATH . "/vendor/autoload.php";
$rcsGitServer = new \RCS\Git\Server();
$serverAuthBackend = new \Sabre\DAV\Auth\Backend\BasicCallBack(function($user, $pass){
$args = [$user, $pass];
error_log("args: " . print_r($args, true) );
return true;
});
$serverAuthPlugin = new \Sabre\DAV\Auth\Plugin($serverAuthBackend);
// OPTIONALLY, you can add authentication this way
// $rcsGitServer->addServerPlugin($serverAuthPlugin);
$dispatcher = \FastRoute\simpleDispatcher(function(\FastRoute\RouteCollector $r) {
// This can also be a single addRoute(['PROPFIND','MKCOL',....])
$r->addRoute('PROPFIND', '/{repository}.git/[{path:.+}]', 'webdav');
$r->addRoute('MKCOL', '/{repository}.git/[{path:.+}]', 'webdav');
$r->addRoute('LOCK', '/{repository}.git/[{path:.+}]', 'webdav');
$r->addRoute('PUT', '/{repository}.git/[{path:.+}]', 'webdav');
$r->addRoute('UNLOCK', '/{repository}.git/[{path:.+}]', 'webdav');
$r->addRoute('GET', '/{repository}.git/[{path:.+}]', 'webdav');
$r->addRoute('MOVE', '/{repository}.git/[{path:.+}]', 'webdav');
});
// Fetch method and URI from somewhere
$httpMethod = $_SERVER['REQUEST_METHOD'];
$uri = $_SERVER['REQUEST_URI'];
// Strip query string (?foo=bar) and decode URI
if (false !== $pos = strpos($uri, '?')) {
$uri = substr($uri, 0, $pos);
}
$uri = rawurldecode($uri);
$routeInfo = $dispatcher->dispatch($httpMethod, $uri);
switch ($routeInfo[0]) {
case \FastRoute\Dispatcher::NOT_FOUND:
error_log("\FastRoute\Dispatcher::NOT_FOUND");
// ... 404 Not Found
break;
case \FastRoute\Dispatcher::METHOD_NOT_ALLOWED:
error_log("\FastRoute\Dispatcher::METHOD_NOT_ALLOWED");
$allowedMethods = $routeInfo[1];
// ... 405 Method Not Allowed
break;
case \FastRoute\Dispatcher::FOUND:
error_log("\FastRoute\Dispatcher::FOUND");
$handler = $routeInfo[1];
$vars = $routeInfo[2];
// ... call $handler with $vars
// list($class, $method) = explode(":", $handler, 2);
// call_user_func_array(array(new $class, $method), $vars);
call_user_func(array($rcsGitServer, $handler), $vars);
break;
}
// So you can see the requests as they come in on the PHP built in server
if (PHP_SAPI == "cli-server") {
error_log($_SERVER["REQUEST_METHOD"] . "::" . $_SERVER["REQUEST_URI"]."\n");
}
```
This can be tested with PHP's built in server using ( you can substitute 8888 for whatever port you want ):
```php
php -S localhost:8888 -t public index.php
```
| 32.383929 | 122 | 0.641577 | yue_Hant | 0.317132 |
612f0752d45ce535e0643ea538f2c2f6bca56eec | 2,148 | md | Markdown | README.md | kityan/morfana | 4ef70798fa25d6aa15cd13b41016792e78f6ab2b | [
"MIT"
] | 5 | 2016-04-27T23:58:28.000Z | 2022-01-26T05:33:02.000Z | README.md | kityan/morfana | 4ef70798fa25d6aa15cd13b41016792e78f6ab2b | [
"MIT"
] | 1 | 2015-11-15T22:00:38.000Z | 2015-11-15T22:00:38.000Z | README.md | kityan/morfana | 4ef70798fa25d6aa15cd13b41016792e78f6ab2b | [
"MIT"
] | 4 | 2018-02-25T20:41:13.000Z | 2021-05-05T04:07:50.000Z | Morfana
=======
JavaScript display engine for morphemic analysis in russian language
[Official website](http://morfana.ru/)
Demo HTML document
-----
``` html
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<script type="text/javascript" src="http://cdnjs.cloudflare.com/ajax/libs/jquery/1.7/jquery.min.js"></script>
<script type="text/javascript" src="http://cdnjs.cloudflare.com/ajax/libs/rangy/1.2.3/rangy-core.js"></script>
<script type="text/javascript" src="http://cdn.morfana.kityan.ru/latest/morfana.min.js"></script>
</head>
<body>
<span data-morfana-markup="ko:1-5;ok:6-6;ko:7-10;su:11-11;ok:12-13;osL:1-5;osR:7-11">десятиэтажный</span>
</body>
</html>
```
For more demos visit [official website](http://morfana.ru/)
##Changelog
`2.3.0b` / `29.09.2014`
- Added 'callback' to Morfana.draw(). Called when queue goes empty.
`2.2.0b` / `10.09.2014`
- Code refactoring: adding paddings for '(zero)-ending' and positioning them
- Changed default of configp['zeroEndingWidthFactor'], now is 0.7
- Added 'paddingFactor' to config, default is 0.2
`2.1.1b` / `07.09.2014`
- Added 'zeroEndingWidthFactor' to config
- SVG for morpheme "ending" and "zero-ending" now contains not PATH but RECT
`2.0.1b` / `06.09.2014`
- Heavily code refactoring
- Added 'stroke', 'strokeWidth' and 'disablePointerEvents' to config
- Added colorization mode for debugging
- Each SVG now have data-morfana-command attribute with markup code used for SVG
`1.1.2a` / `25.07.2014`
- Code refactoring
- Changed draw() behaviour. If elements selected with selector don't have attribute 'data-morfana-markup' Morfana trying to select their children with this attribute
- Fixed #3. Now: 'pointer-events: none' for all SVG elements used as morpheme signs.
- Added morphemes: "zero-ending" inside word, "postfix", "interrupted stem" in 3 parts
- Decreased size of vertical lines in sign of morpheme "basis"
- Added to API: Morfana.clear()
- Added to API: Morfana.getLettersBounds()
`1.0.3a` / `04.11.2013`
- Code refactoring
- Minor bug fixes
`1.0.2a` / `04.11.2013`
- Code refactoring
- Minor bug fixes
`1.0.1a` / `04.11.2013`
- Library release
| 30.253521 | 165 | 0.71648 | eng_Latn | 0.634421 |
612f1b3a548f7ba044d45adc2c5404e957792dd2 | 31,277 | md | Markdown | README-ZH.md | innomon/extended_image | fdb7ccf4a692a6e90342d293b61d5ec8858a8526 | [
"MIT"
] | null | null | null | README-ZH.md | innomon/extended_image | fdb7ccf4a692a6e90342d293b61d5ec8858a8526 | [
"MIT"
] | null | null | null | README-ZH.md | innomon/extended_image | fdb7ccf4a692a6e90342d293b61d5ec8858a8526 | [
"MIT"
] | null | null | null | # extended_image
[](https://pub.dartlang.org/packages/extended_image) [](https://github.com/fluttercandies/extended_image/stargazers) [](https://github.com/fluttercandies/extended_image/network) [](https://github.com/fluttercandies/extended_image/blob/master/LICENSE) [](https://github.com/fluttercandies/extended_image/issues) <a target="_blank" href="https://jq.qq.com/?_wv=1027&k=5bcc0gy"><img border="0" src="https://pub.idqqimg.com/wpa/images/group.png" alt="flutter-candies" title="flutter-candies"></a>
文档语言: [English](README.md) | [中文简体](README-ZH.md)
强大的官方Image扩展组件, 支持加载以及失败显示，缓存网络图片，缩放拖拽图片，图片浏览(微信掘金效果)，滑动退出页面(微信掘金效果)，编辑图片(裁剪旋转翻转)，保存，绘制自定义效果等功能
- [Flutter 什么功能都有的 Image](https://juejin.im/post/5c867112f265da2dd427a340)
- [Flutter 可以缩放拖拽的图片](https://juejin.im/post/5ca758916fb9a05e1c4d01bb)
- [Flutter 仿掘金微信图片滑动退出页面效果](https://juejin.im/post/5cf62ab0e51d45776031afb2)
- [Flutter 图片裁剪旋转翻转编辑器](https://juejin.im/post/5d77dfbb6fb9a06b160f55fc)
## 目录
- [extended_image](#extendedimage)
- [目录](#%e7%9b%ae%e5%bd%95)
- [缓存网络图片](#%e7%bc%93%e5%ad%98%e7%bd%91%e7%bb%9c%e5%9b%be%e7%89%87)
- [简单使用](#%e7%ae%80%e5%8d%95%e4%bd%bf%e7%94%a8)
- [使用 Extendednetworkimageprovider](#%e4%bd%bf%e7%94%a8-extendednetworkimageprovider)
- [加载状态](#%e5%8a%a0%e8%bd%bd%e7%8a%b6%e6%80%81)
- [例子](#%e4%be%8b%e5%ad%90)
- [缩放拖拽](#%e7%bc%a9%e6%94%be%e6%8b%96%e6%8b%bd)
- [双击图片动画](#%e5%8f%8c%e5%87%bb%e5%9b%be%e7%89%87%e5%8a%a8%e7%94%bb)
- [图片编辑](#%e5%9b%be%e7%89%87%e7%bc%96%e8%be%91)
- [裁剪框的宽高比](#%e8%a3%81%e5%89%aa%e6%a1%86%e7%9a%84%e5%ae%bd%e9%ab%98%e6%af%94)
- [旋转,翻转,重置](#%e6%97%8b%e8%bd%ac%e7%bf%bb%e8%bd%ac%e9%87%8d%e7%bd%ae)
- [裁剪数据](#%e8%a3%81%e5%89%aa%e6%95%b0%e6%8d%ae)
- [使用dart库(稳定)](#%e4%bd%bf%e7%94%a8dart%e5%ba%93%e7%a8%b3%e5%ae%9a)
- [使用原生库(快速)](#%e4%bd%bf%e7%94%a8%e5%8e%9f%e7%94%9f%e5%ba%93%e5%bf%ab%e9%80%9f)
- [图片浏览](#%e5%9b%be%e7%89%87%e6%b5%8f%e8%a7%88)
- [滑动退出页面](#%e6%bb%91%e5%8a%a8%e9%80%80%e5%87%ba%e9%a1%b5%e9%9d%a2)
- [首先开启滑动退出页面效果](#%e9%a6%96%e5%85%88%e5%bc%80%e5%90%af%e6%bb%91%e5%8a%a8%e9%80%80%e5%87%ba%e9%a1%b5%e9%9d%a2%e6%95%88%e6%9e%9c)
- [把你的页面用ExtendedImageSlidePage包一下](#%e6%8a%8a%e4%bd%a0%e7%9a%84%e9%a1%b5%e9%9d%a2%e7%94%a8extendedimageslidepage%e5%8c%85%e4%b8%80%e4%b8%8b)
- [确保你的页面是透明背景的](#%e7%a1%ae%e4%bf%9d%e4%bd%a0%e7%9a%84%e9%a1%b5%e9%9d%a2%e6%98%af%e9%80%8f%e6%98%8e%e8%83%8c%e6%99%af%e7%9a%84)
- [Push一个透明的页面](#push%e4%b8%80%e4%b8%aa%e9%80%8f%e6%98%8e%e7%9a%84%e9%a1%b5%e9%9d%a2)
- [Border BorderRadius Shape](#border-borderradius-shape)
- [清除缓存和保存](#%e6%b8%85%e9%99%a4%e7%bc%93%e5%ad%98%e5%92%8c%e4%bf%9d%e5%ad%98)
- [清除缓存](#%e6%b8%85%e9%99%a4%e7%bc%93%e5%ad%98)
- [保存网络图片](#%e4%bf%9d%e5%ad%98%e7%bd%91%e7%bb%9c%e5%9b%be%e7%89%87)
- [显示裁剪图片](#%e6%98%be%e7%a4%ba%e8%a3%81%e5%89%aa%e5%9b%be%e7%89%87)
- [绘制](#%e7%bb%98%e5%88%b6)
- [其他 APIs](#%e5%85%b6%e4%bb%96-apis)
## 缓存网络图片
### 简单使用
你可以直接使用 ExtendedImage.network，这跟官方是一样。
```dart
ExtendedImage.network(
url,
width: ScreenUtil.instance.setWidth(400),
height: ScreenUtil.instance.setWidth(400),
fit: BoxFit.fill,
cache: true,
border: Border.all(color: Colors.red, width: 1.0),
shape: boxShape,
borderRadius: BorderRadius.all(Radius.circular(30.0)),
//cancelToken: cancellationToken,
)
```
### 使用 Extendednetworkimageprovider
你也可以通过[ExtendedNetworkImageProvider](https://github.com/fluttercandies/extended_image_library/blob/master/lib/src/extended_network_image_provider.dart)，设置更多的网络请求的参数
```dart
ExtendedNetworkImageProvider(
this.url, {
this.scale = 1.0,
this.headers,
this.cache: false,
this.retries = 3,
this.timeLimit,
this.timeRetry = const Duration(milliseconds: 100),
CancellationToken cancelToken,
}) : assert(url != null),
assert(scale != null),
cancelToken = cancelToken ?? CancellationToken();
```
| 参数 | 描述 | 默认 |
| ----------- | --------------------- | ------------------- |
| url | 网络请求地址 | required |
| scale | ImageInfo 中的 scale | 1.0 |
| headers | HttpClient 的 headers | - |
| cache | 是否缓存到本地 | false |
| retries | 请求尝试次数 | 3 |
| timeLimit | 请求超时 | - |
| timeRetry | 请求重试间隔 | milliseconds: 100 |
| cancelToken | 用于取消请求的 Token | CancellationToken() |
## 加载状态
Extended Image一共有3种状态，分别是正在加载，完成，失败(loading,completed,failed)，你可以通过实现loadStateChanged回调来定义显示的效果
loadStateChanged 不仅仅只在网络图片中可以使用, 如果你的图片很大，需要长时间加载，
你可以把enableLoadState设置为了true，这样也会有状态回调了，（默认只有网络图片,enableLoadState为true）
注意:
* 如果你不想重写某个状态，那么请返回null
* 如果你想重写完成图片的 size 或者 soucreRect, 你可以通过使用 ExtendedRawImage 来完成
* 如果你想增加一些新效果 (比如动画), 你可以重写并且使用ExtendedImageState.completedWidget
* ExtendedImageState.completedWidget 包含手势或者裁剪, 这样你不会丢失它们
```dart
/// custom load state widget if you want
final LoadStateChanged loadStateChanged;
enum LoadState {
//loading
loading,
//completed
completed,
//failed
failed
}
///whether has loading or failed state
///default is false
///but network image is true
///better to set it's true when your image is big and take some time to ready
final bool enableLoadState;
```
ExtendedImageState 状态回调
| 参数/方法 | 描述 | 默认 |
| ---------------------------- | -------------------------------------------------------------------------------------------------- | ---- |
| extendedImageInfo | 图片的信息，包括底层image和image的大小 | - |
| extendedImageLoadState | 状态(loading,completed,failed) | - |
| returnLoadStateChangedWidget | 如果这个为true的话，状态回调返回的widget将不会对(width/height/gesture/border/shape）等效果进行包装 | - |
| imageProvider | 图片的Provider | - |
| invertColors | 是否反转颜色 | - |
| imageStreamKey | 图片流的唯一键 | - |
| reLoadImage() | 如果图片加载失败，你可以通过调用这个方法来重新加载图片 | - |
| completedWidget | 返回图片完成的Widget，它包含手势以及裁剪 | - |
```dart
abstract class ExtendedImageState {
void reLoadImage();
ImageInfo get extendedImageInfo;
LoadState get extendedImageLoadState;
///return widget which from LoadStateChanged fucntion immediately
bool returnLoadStateChangedWidget;
ImageProvider get imageProvider;
bool get invertColors;
Object get imageStreamKey;
Widget get completedWidget;
}
```
### 例子
```dart
ExtendedImage.network(
url,
width: ScreenUtil.instance.setWidth(600),
height: ScreenUtil.instance.setWidth(400),
fit: BoxFit.fill,
cache: true,
loadStateChanged: (ExtendedImageState state) {
switch (state.extendedImageLoadState) {
case LoadState.loading:
_controller.reset();
return Image.asset(
"assets/loading.gif",
fit: BoxFit.fill,
);
break;
///if you don't want override completed widget
///please return null or state.completedWidget
//return null;
//return state.completedWidget;
case LoadState.completed:
_controller.forward();
return FadeTransition(
opacity: _controller,
child: ExtendedRawImage(
image: state.extendedImageInfo?.image,
width: ScreenUtil.instance.setWidth(600),
height: ScreenUtil.instance.setWidth(400),
),
);
break;
case LoadState.failed:
_controller.reset();
return GestureDetector(
child: Stack(
fit: StackFit.expand,
children: <Widget>[
Image.asset(
"assets/failed.jpg",
fit: BoxFit.fill,
),
Positioned(
bottom: 0.0,
left: 0.0,
right: 0.0,
child: Text(
"load image failed, click to reload",
textAlign: TextAlign.center,
),
)
],
),
onTap: () {
state.reLoadImage();
},
);
break;
}
},
)
```
## 缩放拖拽
ExtendedImage
| 参数 | 描述 | 默认 |
| ------------------------ | --------------------------------------------------------------------- | ---- |
| mode | 图片模式，默认/手势/编辑 (none,gestrue,editor) | none |
| initGestureConfigHandler | 手势配置的回调(图片加载完成时).你可以根据图片的信息比如宽高，来初始化 | - |
| onDoubleTap | 支持手势的时候，双击回调 | - |
GestureConfig
| 参数 | 描述 | 默认值 |
| ----------------- | ---------------------------------------------------------------------------------------------------- | -------------- |
| minScale | 缩放最小值 | 0.8 |
| animationMinScale | 缩放动画最小值，当缩放结束时回到minScale值 | minScale * 0.8 |
| maxScale | 缩放最大值 | 5.0 |
| animationMaxScale | 缩放动画最大值，当缩放结束时回到maxScale值 | maxScale * 1.2 |
| speed | 缩放拖拽速度，与用户操作成正比 | 1.0 |
| inertialSpeed | 拖拽惯性速度，与惯性速度成正比 | 100 |
| cacheGesture | 是否缓存手势状态，可用于ExtendedImageGesturePageView中保留状态，使用clearGestureDetailsCache方法清除 | false |
| inPageView | 是否使用ExtendedImageGesturePageView展示图片 | false |
```dart
ExtendedImage.network(
imageTestUrl,
fit: BoxFit.contain,
//enableLoadState: false,
mode: ExtendedImageMode.Gesture,
initGestureConfigHandler: (state) {
return GestureConfig(
minScale: 0.9,
animationMinScale: 0.7,
maxScale: 3.0,
animationMaxScale: 3.5,
speed: 1.0,
inertialSpeed: 100.0,
initialScale: 1.0,
inPageView: false);
},
)
```
### 双击图片动画
支持双击动画，具体双击图片什么样子的效果，可以自定义
```dart
onDoubleTap: (ExtendedImageGestureState state) {
///you can use define pointerDownPosition as you can,
///default value is double tap pointer down postion.
var pointerDownPosition = state.pointerDownPosition;
double begin = state.gestureDetails.totalScale;
double end;
//remove old
_animation?.removeListener(animationListener);
//stop pre
_animationController.stop();
//reset to use
_animationController.reset();
if (begin == doubleTapScales[0]) {
end = doubleTapScales[1];
} else {
end = doubleTapScales[0];
}
animationListener = () {
//print(_animation.value);
state.handleDoubleTap(
scale: _animation.value,
doubleTapPosition: pointerDownPosition);
};
_animation = _animationController
.drive(Tween<double>(begin: begin, end: end));
_animation.addListener(animationListener);
_animationController.forward();
},
```
## 图片编辑
``` dart
ExtendedImage.network(
imageTestUrl,
fit: BoxFit.contain,
mode: ExtendedImageMode.editor,
extendedImageEditorKey: editorKey,
initEditorConfigHandler: (state) {
return EditorConfig(
maxScale: 8.0,
cropRectPadding: EdgeInsets.all(20.0),
hitTestSize: 20.0,
cropAspectRatio: _aspectRatio.aspectRatio);
},
);
```
ExtendedImage
| 参数 | 描述 | 默认 |
| ------------------------ | ----------------------------------------------------------------------- | ---- |
| mode | 图片模式，默认/手势/编辑 (none,gestrue,editor) | none |
| initGestureConfigHandler | 编辑器配置的回调(图片加载完成时).你可以根据图片的信息比如宽高，来初始化 | - |
| extendedImageEditorKey | key of ExtendedImageEditorState 用于裁剪旋转翻转 | - |
EditorConfig
| 参数 | 描述 | 默认 |
| ---------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| maxScale | 最大的缩放倍数 | 5.0 |
| cropRectPadding | 裁剪框跟图片layout区域之间的距离。最好是保持一定距离，不然裁剪框边界很难进行拖拽 | EdgeInsets.all(20.0) |
| cornerSize | 裁剪框四角图形的大小 | Size(30.0, 5.0) |
| cornerColor | 裁剪框四角图形的颜色 | primaryColor |
| lineColor | 裁剪框线的颜色 | scaffoldBackgroundColor.withOpacity(0.7) |
| lineHeight | 裁剪框线的高度 | 0.6 |
| eidtorMaskColorHandler | 蒙层的颜色回调，你可以根据是否手指按下来设置不同的蒙层颜色 | scaffoldBackgroundColor.withOpacity(pointerdown ? 0.4 : 0.8) |
| hitTestSize | 裁剪框四角以及边线能够拖拽的区域的大小 | 20.0 |
| animationDuration | 当裁剪框拖拽变化结束之后，自动适应到中间的动画的时长 | Duration(milliseconds: 200) |
| tickerDuration | 当裁剪框拖拽变化结束之后，多少时间才触发自动适应到中间的动画 | Duration(milliseconds: 400) |
| cropAspectRatio | 裁剪框的宽高比 | null(无宽高比) |
| initCropRectType | 剪切框的初始化类型(根据图片初始化区域或者图片的layout区域) | imageRect |
### 裁剪框的宽高比
这是一个double类型，你可以自定义裁剪框的宽高比。
如果为null，那就没有宽高比限制。
如果小于等于0，宽高比等于图片的宽高比。
下面是一些定义好了的宽高比
``` dart
class CropAspectRatios {
/// no aspect ratio for crop
static const double custom = null;
/// the same as aspect ratio of image
/// [cropAspectRatio] is not more than 0.0, it's original
static const double original = 0.0;
/// ratio of width and height is 1 : 1
static const double ratio1_1 = 1.0;
/// ratio of width and height is 3 : 4
static const double ratio3_4 = 3.0 / 4.0;
/// ratio of width and height is 4 : 3
static const double ratio4_3 = 4.0 / 3.0;
/// ratio of width and height is 9 : 16
static const double ratio9_16 = 9.0 / 16.0;
/// ratio of width and height is 16 : 9
static const double ratio16_9 = 16.0 / 9.0;
}
```
### 旋转,翻转,重置
- 定义key，以方便操作ExtendedImageEditorState
`final GlobalKey<ExtendedImageEditorState> editorKey =GlobalKey<ExtendedImageEditorState>();`
- 顺时针旋转90°
`editorKey.currentState.rotate(right: true);`
- 逆时针旋转90°
`editorKey.currentState.rotate(right: false);`
- 翻转(镜像)
`editorKey.currentState.flip();`
- 重置
`editorKey.currentState.reset();`
### 裁剪数据
#### 使用dart库(稳定)
- 添加 [Image](https://github.com/brendan-duncan/image) 库到 pubspec.yaml, 它是用来裁剪/旋转/翻转图片数据的
``` yaml
dependencies:
image: any
```
- 从ExtendedImageEditorState中获取裁剪区域以及图片数据
``` dart
///crop rect base on raw image
final Rect cropRect = state.getCropRect();
var data = state.rawImageData;
```
- 将flutter的图片数据转换为image库的数据
``` dart
/// it costs much time and blocks ui.
//Image src = decodeImage(data);
/// it will not block ui with using isolate.
//Image src = await compute(decodeImage, data);
//Image src = await isolateDecodeImage(data);
final lb = await loadBalancer;
Image src = await lb.run<Image, List<int>>(decodeImage, data);
```
- 翻转，旋转，裁剪数据
``` dart
//相机拍照的图片带有旋转，处理之前需要去掉
src = bakeOrientation(src);
if (editAction.needCrop)
src = copyCrop(src, cropRect.left.toInt(), cropRect.top.toInt(),
cropRect.width.toInt(), cropRect.height.toInt());
if (editAction.needFlip) {
Flip mode;
if (editAction.flipY && editAction.flipX) {
mode = Flip.both;
} else if (editAction.flipY) {
mode = Flip.horizontal;
} else if (editAction.flipX) {
mode = Flip.vertical;
}
src = flip(src, mode);
}
if (editAction.hasRotateAngle) src = copyRotate(src, editAction.rotateAngle);
```
- 将数据转为为图片的元数据
获取到的将是图片的元数据，你可以使用它来保存或者其他的一些用途
``` dart
/// you can encode your image
///
/// it costs much time and blocks ui.
//var fileData = encodeJpg(src);
/// it will not block ui with using isolate.
//var fileData = await compute(encodeJpg, src);
//var fileData = await isolateEncodeImage(src);
var fileData = await lb.run<List<int>, Image>(encodeJpg, src);
```
#### 使用原生库(快速)
- 添加 [ImageEditor](https://github.com/fluttercandies/flutter_image_editor) 库到 pubspec.yaml, 它是用来裁剪/旋转/翻转图片数据的。
``` yaml
dependencies:
image_editor: any
```
- 从ExtendedImageEditorState中获取裁剪区域以及图片数据
``` dart
///crop rect base on raw image
final Rect cropRect = state.getCropRect();
final img = state.rawImageData;
```
- 准备裁剪选项
``` dart
final rotateAngle = action.rotateAngle.toInt();
final flipHorizontal = action.flipY;
final flipVertical = action.flipX;
ImageEditorOption option = ImageEditorOption();
if (action.needCrop) option.addOption(ClipOption.fromRect(cropRect));
if (action.needFlip)
option.addOption(
FlipOption(horizontal: flipHorizontal, vertical: flipVertical));
if (action.hasRotateAngle) option.addOption(RotateOption(rotateAngle));
```
- 使用editImage方法进行裁剪
获取到的将是图片的元数据，你可以使用它来保存或者其他的一些用途
``` dart
final result = await ImageEditor.editImage(
image: img,
imageEditorOption: option,
);
```
[more detail](https://github.com/fluttercandies/extended_image/blob/master/example/lib/common/crop_editor_helper.dart)
## 图片浏览
支持跟微信/掘金一样的图片查看效果
ExtendedImageGesturePageView跟官方PageView一样的使用，不同的是，它避免了跟缩放拖拽手势冲突
支持缓存手势的状态，就是说你缩放了图片，然后下一个，再回到之前的图片，图片的缩放状态可以保存，
如果你缓存了手势，记住在合适的时候使用clearGestureDetailsCache()清除掉，比如页面销毁的时候
ExtendedImageGesturePageView
| parameter | description | default |
| ----------- | -------------------------------------------------------------------- | ------- |
| canMovePage | 是否滑动页面.有些场景如果Scale大于1.0，并不想滑动页面，可以返回false | true |
GestureConfig
| 参数 | 描述 | 默认 |
| ------------ | ---------------------------------------------------------------------------------------------------- | ----- |
| cacheGesture | 是否缓存手势状态，可用于ExtendedImageGesturePageView中保留状态，使用clearGestureDetailsCache方法清除 | false |
| inPageView | 是否使用ExtendedImageGesturePageView展示图片 | false |
```dart
ExtendedImageGesturePageView.builder(
itemBuilder: (BuildContext context, int index) {
var item = widget.pics[index].picUrl;
Widget image = ExtendedImage.network(
item,
fit: BoxFit.contain,
mode: ExtendedImageMode.Gesture,
gestureConfig: GestureConfig(
inPageView: true, initialScale: 1.0,
//you can cache gesture state even though page view page change.
//remember call clearGestureDetailsCache() method at the right time.(for example,this page dispose)
cacheGesture: false
),
);
image = Container(
child: image,
padding: EdgeInsets.all(5.0),
);
if (index == currentIndex) {
return Hero(
tag: item + index.toString(),
child: image,
);
} else {
return image;
}
},
itemCount: widget.pics.length,
onPageChanged: (int index) {
currentIndex = index;
rebuild.add(index);
},
controller: PageController(
initialPage: currentIndex,
),
scrollDirection: Axis.horizontal,
),
```
## 滑动退出页面
支持微信掘金滑动退出页面的效果
### 首先开启滑动退出页面效果
ExtendedImage
| parameter | description | default |
| ------------------------- | ----------------------------------------------------------------------------------- | ------- |
| enableSlideOutPage | 是否开启滑动退出页面效果 | false |
| heroBuilderForSlidingPage | 滑动退出页面的transform必须作用在Hero上面，这样在退出页面的时候，Hero动画才不会奇怪 | null |
### 把你的页面用ExtendedImageSlidePage包一下
注意：onSlidingPage回调，你可以使用它来设置滑动页面的时候,页面上其他元素的状态。但是注意别直接使用setState来刷新，因为这样会导致ExtendedImage的状态重置掉，你应该只通知需要刷新的Widgets进行刷新
```dart
return ExtendedImageSlidePage(
child: result,
slideAxis: SlideAxis.both,
slideType: SlideType.onlyImage,
onSlidingPage: (state) {
///you can change other widgets' state on page as you want
///base on offset/isSliding etc
//var offset= state.offset;
var showSwiper = !state.isSliding;
if (showSwiper != _showSwiper) {
// do not setState directly here, the image state will change,
// you should only notify the widgets which are needed to change
// setState(() {
// _showSwiper = showSwiper;
// });
_showSwiper = showSwiper;
rebuildSwiper.add(_showSwiper);
}
},
);
```
ExtendedImageGesturePage的参数
| parameter | description | default |
| -------------------------- | --------------------------------------------------------------------- | --------------------------------- |
| child | 需要包裹的页面 | - |
| slidePageBackgroundHandler | 在滑动页面的时候根据Offset自定义整个页面的背景色 | defaultSlidePageBackgroundHandler |
| slideScaleHandler | 在滑动页面的时候根据Offset自定义整个页面的缩放值 | defaultSlideScaleHandler |
| slideEndHandler | 滑动页面结束的时候计算是否需要pop页面 | defaultSlideEndHandler |
| slideAxis | 滑动页面的方向（both,horizontal,vertical）,掘金是vertical，微信是Both | both |
| resetPageDuration | 滑动结束，如果不pop页面，整个页面回弹动画的时间 | milliseconds: 500 |
| slideType | 滑动整个页面还是只是图片(wholePage/onlyImage) | SlideType.onlyImage |
| onSlidingPage | 滑动页面的回调，你可以在这里改变页面上其他元素的状态 | - |
下面是默认实现，你也可以根据你的喜好，来定义属于自己方式
```dart
Color defaultSlidePageBackgroundHandler(
{Offset offset, Size pageSize, Color color, SlideAxis pageGestureAxis}) {
double opacity = 0.0;
if (pageGestureAxis == SlideAxis.both) {
opacity = offset.distance /
(Offset(pageSize.width, pageSize.height).distance / 2.0);
} else if (pageGestureAxis == SlideAxis.horizontal) {
opacity = offset.dx.abs() / (pageSize.width / 2.0);
} else if (pageGestureAxis == SlideAxis.vertical) {
opacity = offset.dy.abs() / (pageSize.height / 2.0);
}
return color.withOpacity(min(1.0, max(1.0 - opacity, 0.0)));
}
bool defaultSlideEndHandler(
{Offset offset, Size pageSize, SlideAxis pageGestureAxis}) {
if (pageGestureAxis == SlideAxis.both) {
return offset.distance >
Offset(pageSize.width, pageSize.height).distance / 3.5;
} else if (pageGestureAxis == SlideAxis.horizontal) {
return offset.dx.abs() > pageSize.width / 3.5;
} else if (pageGestureAxis == SlideAxis.vertical) {
return offset.dy.abs() > pageSize.height / 3.5;
}
return true;
}
double defaultSlideScaleHandler(
{Offset offset, Size pageSize, SlideAxis pageGestureAxis}) {
double scale = 0.0;
if (pageGestureAxis == SlideAxis.both) {
scale = offset.distance / Offset(pageSize.width, pageSize.height).distance;
} else if (pageGestureAxis == SlideAxis.horizontal) {
scale = offset.dx.abs() / (pageSize.width / 2.0);
} else if (pageGestureAxis == SlideAxis.vertical) {
scale = offset.dy.abs() / (pageSize.height / 2.0);
}
return max(1.0 - scale, 0.8);
}
```
### 确保你的页面是透明背景的
如果你设置 slideType =SlideType.onlyImage, 请确保的你页面是透明的，毕竟没法操控你页面上的颜色
### Push一个透明的页面
这里我把官方的MaterialPageRoute 和CupertinoPageRoute拷贝出来了，
改为TransparentMaterialPageRoute/TransparentCupertinoPageRoute，因为它们的opaque不能设置为false
```dart
Navigator.push(
context,
Platform.isAndroid
? TransparentMaterialPageRoute(builder: (_) => page)
: TransparentCupertinoPageRoute(builder: (_) => page),
);
```
[滑动退出页面相关代码演示 1](https://github.com/fluttercandies/extended_image/blob/master/example/lib/common/crop_image.dart)
[滑动退出页面相关代码演示 2](https://github.com/fluttercandies/extended_image/blob/master/example/lib/common/pic_swiper.dart)
## Border BorderRadius Shape
ExtendedImage
| 参数 | 描述 | 默认 |
| ------------ | -------------------------------------------------- | ---- |
| border | 跟官方的含义一样，你可以通过它设置边框 | - |
| borderRadius | 跟官方的含义一样，你可以通过它设置圆角 |
| shape | 跟官方的含义一样，你可以通过它设置裁剪（矩形和圆） | - |
```dart
ExtendedImage.network(
url,
width: ScreenUtil.instance.setWidth(400),
height: ScreenUtil.instance.setWidth(400),
fit: BoxFit.fill,
cache: true,
border: Border.all(color: Colors.red, width: 1.0),
shape: boxShape,
borderRadius: BorderRadius.all(Radius.circular(30.0)),
),
```
## 清除缓存和保存
### 清除缓存
清除本地缓存，可以调用clearDiskCachedImages方法
```dart
// Clear the disk cache directory then return if it succeed.
/// <param name="duration">timespan to compute whether file has expired or not</param>
Future<bool> clearDiskCachedImages({Duration duration})
```
根据某一个url清除缓存， 可以调用clearDiskCachedImage方法.
```dart
/// clear the disk cache image then return if it succeed.
/// <param name="url">clear specific one</param>
Future<bool> clearDiskCachedImage(String url) async {
```
根据url获取缓存图片文件
```dart
Future<File> getCachedImageFile(String url) async {
```
清除内存缓存，可以调用clearMemoryImageCache方法
```dart
///clear all of image in memory
clearMemoryImageCache();
/// get ImageCache
getMemoryImageCache() ;
```
### 保存网络图片
这是一个例子，使用到[image_picker_saver](https://github.com/cnhefang/image_picker_saver)
插件，ExtendedImage做的只是提供网络图片的数据源
```dart
///save netwrok image to photo
Future<bool> saveNetworkImageToPhoto(String url, {bool useCache: true}) async {
var data = await getNetworkImageData(url, useCache: useCache);
var filePath = await ImagePickerSaver.saveFile(fileData: data);
return filePath != null && filePath != "";
}
```
## 显示裁剪图片
你可以通过
[ExtendedRawImage](https://github.com/fluttercandies/extended_image/blob/master/lib/src/image/extended_raw_image.dart)(可以在状态回调的时候使用),soucreRect 是你想要显示图片的哪一部分，这个在各个app里面应该是比较常见的操作
```dart
ExtendedRawImage(
image: image,
width: num400,
height: num300,
fit: BoxFit.fill,
soucreRect: Rect.fromLTWH(
(image.width - width) / 2.0, 0.0, width, image.height.toDouble()),
)
```
[crop image demo](https://github.com/fluttercandies/extended_image/blob/master/example/lib/crop_image_demo.dart)
## 绘制
提供了 BeforePaintImage and AfterPaintImage 两个回调, 这样你就能绘制你想要的东西或者进图片进行Clip。
ExtendedImage
| parameter | description | default |
| ---------------- | -------------- | ------- |
| beforePaintImage | 在绘制图片之前 | - |
| afterPaintImage | 在绘制图片之后 | - |
```dart
ExtendedImage.network(
url,
width: ScreenUtil.instance.setWidth(400),
height: ScreenUtil.instance.setWidth(400),
fit: BoxFit.fill,
cache: true,
beforePaintImage: (Canvas canvas, Rect rect, ui.Image image) {
if (paintType == PaintType.ClipHeart) {
if (!rect.isEmpty) {
canvas.save();
canvas.clipPath(clipheart(rect, canvas));
}
}
return false;
},
afterPaintImage: (Canvas canvas, Rect rect, ui.Image image) {
if (paintType == PaintType.ClipHeart) {
if (!rect.isEmpty) canvas.restore();
} else if (paintType == PaintType.PaintHeart) {
canvas.drawPath(
clipheart(rect, canvas),
Paint()
..colorFilter =
ColorFilter.mode(Color(0x55ea5504), BlendMode.srcIn)
..isAntiAlias = false
..filterQuality = FilterQuality.low);
}
},
);
```
在例子中可以看到把图片Clip成了一个桃心，你也可以根据你的要求，做出不同的Clip
[绘制例子](https://github.com/fluttercandies/extended_image/blob/master/example/lib/paint_image_demo.dart)
[下拉刷新头当中，也使用了这个技巧](https://github.com/fluttercandies/extended_image/tree/master/example/lib/common/push_to_refresh_header.dart)
## 其他 APIs
ExtendedImage
| 参数 | 描述 | 默认 |
| ------------------------ | ---------------------------------- | ---- |
| enableMemoryCache | 是否缓存到内存 | true |
| clearMemoryCacheIfFailed | 如果图片加载失败，是否清掉内存缓存 | true |
| 36.116628 | 891 | 0.5646 | yue_Hant | 0.44094 |
612f2fef937da606a549f98b29beb0ba28e7ad3d | 1,991 | md | Markdown | README.md | mthiele/mvvmFX | d8c9caa341cd253e83c5d156e3c2c6d2b149ab9b | [
"Apache-2.0"
] | null | null | null | README.md | mthiele/mvvmFX | d8c9caa341cd253e83c5d156e3c2c6d2b149ab9b | [
"Apache-2.0"
] | null | null | null | README.md | mthiele/mvvmFX | d8c9caa341cd253e83c5d156e3c2c6d2b149ab9b | [
"Apache-2.0"
] | null | null | null | 
__mvvm(fx)__ is an application framework which provides you necessary components to implement the [MVVM](../../wiki/MVVM "MVVM") pattern with JavaFX.
__MVVM__ is the enhanced version of the [Presentation Model](http://martinfowler.com/eaaDev/PresentationModel.html "Presentation Model") pattern and was created by Microsoft engineers for [WPF](http://msdn.microsoft.com/en-us/library/ms754130.aspx "WPF") . JavaFX and WPF does have similarities like Databinding and descriptive UI declaration (FXML/XAML). Because of this fact we adopt best practices of the development with the Microsoft technology.
[](https://travis-ci.org/sialcasa/mvvmFX)
###[Howto](../../wiki "Howto")###
### Maven dependency###
#### Stable Release
```
<dependency>
<groupId>de.saxsys</groupId>
<artifactId>mvvmfx</artifactId>
<version>1.3.1</version>
</dependency>
```
#### Development Snapshot
```
<dependency>
<groupId>de.saxsys</groupId>
<artifactId>mvvmfx</artifactId>
<version>1.4.0-SNAPSHOT</version>
</dependency>
```
### Get Help
If you need help you can use the forums on [Google Groups](https://groups.google.com/forum/#!forum/mvvmfx-dev) for asking questions and interacting with the mvvmFX developers. Additionally you can create issues, report bugs and add feature requests on the issue tracker at [github](https://github.com/sialcasa/mvvmFX/issues).
### Links
- [Project Page](http://sialcasa.github.io/mvvmFX/)
- [javadoc mvvmfx core](http://sialcasa.github.io/mvvmFX/javadoc/1.3.1/mvvmfx/)
- [javadoc mvvmfx-cdi](http://sialcasa.github.io/mvvmFX/javadoc/1.3.1/mvvmfx-cdi/)
- [javadoc mvvmfx-guice](http://sialcasa.github.io/mvvmFX/javadoc/1.3.1/mvvmfx-guice/)
- [javadoc mvvmfx-utils](http://sialcasa.github.io/mvvmFX/javadoc/1.3.1/mvvmfx-utils/)
- [javadoc mvvmfx-testing-utils](http://sialcasa.github.io/mvvmFX/javadoc/1.3.1/mvvmfx-testing-utils/)
| 44.244444 | 450 | 0.745354 | eng_Latn | 0.50492 |
612f393f4321ed5c5a83104af15ef4654e9843de | 7,761 | md | Markdown | T1-kokubum/A2_Clojure.md | micaelomota/caracterizacao | 2cd6455d2f46fd1780744e82f4e622a87220ec7a | [
"MIT"
] | 1 | 2021-08-22T19:48:27.000Z | 2021-08-22T19:48:27.000Z | T1-kokubum/A2_Clojure.md | micaelomota/caracterizacao | 2cd6455d2f46fd1780744e82f4e622a87220ec7a | [
"MIT"
] | 14 | 2021-08-21T18:45:57.000Z | 2021-12-06T18:14:28.000Z | T1-kokubum/A2_Clojure.md | micaelomota/caracterizacao | 2cd6455d2f46fd1780744e82f4e622a87220ec7a | [
"MIT"
] | 35 | 2021-08-18T21:58:29.000Z | 2021-12-03T20:58:33.000Z | # Trabalho 1 - Atividade A1
### Linguagem de Programação: Clojure
#
## Modelo de compilação:
A linguagem Clojure é definida como uma linguagem compilada pelo fato de rodar sob a JVM (máquina virtual Java) compilando seu código "on the fly" para o byte code e permitindo que você rode o código em qualquer ambiente sem necessidade de recompilação.
## Nomes, variáveis e vinculação:
### Nomes
#
O Clojure não tem um padrão de nomenclatura obrigatório, mas assim como a maioria das linguages, ele possui algumas diretrizes que são adotadas pela comunidade.
- Funções puras: Definidas através de substantivos, com todas as letras minúsculas e separadas pelo "-".
- Funções com efeitos colaterais: Definidas com verbos que descrevem a ação seguindo a mesma ideia das funções puras de letras minúsculas e separadas pelo "-".
- Funções que retornam funções: Devem ter o sufixo -fn
- Aliases de namespaces: Podem economizar em repetições (products/price em vez de products/product-price) e evitar conflitos locais em bindings
- Variáveis: Seguem sempre o mesmo padrão de letras minúsculas seguidas de "-".
### Variáveis
#
- Variável global: Variáveis criadas através da keyword "def".
Ex:
```
(def variavel "exemplo") variavel ;; => "exemplo"
```
- Variavel de namespace: Variáveis que são definidas após a definição do "namespace".
Ex:
```
(ns 'exemplo)
(def variavel "exemplo") variavel ;; => "exemplo"
;; De forma gráfica, o escopo seria assim:
+----------------------+
|ns exemplo |
+----------------------+
|variavel = "exemplo" |
| |
| |
+----------------------+
```
- Varável local: São variáveis que estão visíveis apenas dentro do escopo em que foram definidas, geralmente uma função.
Ex:
```
(ns 'exemplo)
(def variavel 1)
(let [nova-variavel 2]
(println (+ variavel nova-variavel)))
variavel ;; => 1
nova-variavel ;; => Erro
;; De forma gráfica, o escopo seria assim:
+-------------------------------------+
| ns exemplo |
+-------------------------------------+
| variavel = 1 |
| |
| +---------------------------------+
| | let |
| +---------------------------------+
| | nova-variavel = 2 |
| | |
| | |
| | (println |
| | (+ variavel nova-variavel)) |
| | |
+---|---------------------------------+
```
### Vinculação
#
- Dinâmica: O Clojure tem o processo de vinculação dinâmica, ou seja, em tempo de execução, proporciado simplismente pelo uso da keyword "bindind".
Ex:
```
user> (defn foo [] (println x))
user> (binding [x 1] (foo))
1
nil
```
- Estática: O clojure tem a vinculação de valores que ocorre em tempo de compilação proporcionada pelo simples uso do "let" na atribuição.
```
user> (defn foo [] (println x))
user> (let [x 1] (foo))
0
nil
```
## Escopo, Tempo De Vida e Ambientes de Referência
### Escopo e tempo de vida:
#
- Escopo Global
Uma variável declarada através da keyword "def" é responsável pela definiçào de símbolos globais.
Tempo de vida - Para essa situação a variável tem o tempo de vida igual ao tempo de execução do programa.
Ex:
```
(def denominator 0)
```
- Escopo Local
Uma variável declarada através da "let-expression", basicamente uma macro cujo primeiro parâmetro é um vetor (que em Clojure declaramos com [ e ] - encare como o Array de outras linguagens, exceto que não precisamos de vírgulas entre os elementos, logo um vetor com os valores 1 4 5 seria escrito [1 4 5]) que precisa ter elementos par – o elemento par é o nome da variável/símbolo, e o elemento ímpar é seu valor.
Tempo de vida - Para essa situação, como foi mencionado acima, a variável tem o tempo de vida de duração da execução dessa função, de forma que no momento que a função for finalizada, ela deixa de existir.
Ex:
```
(let [variable-1 "Hello"
variable-2 "World!"]
(str variable-1 ", " variable-2))
```
### Ambientes de Referência: Estático e Dinâmico
#
- Estático: Escopo que é definido antes da execução do programa, com base na estrutura léxica do mesmo, ou seja, baseado sempre onde cada uma de suas instruções foram declaradas.
Ex:
```
(def x 0)
;=> #'user/x
;; Escopo estático
(defn f [] x)
;=> #'user/f
(f)
;=> 0
(defn g [] (let [x 1] (f)))
;=> #'user/g
(g)
;=> 0
```
- Dinâmico: Escopo que é definido com base na pilha de execução.
Ex:
```
;; Leve como base que o código acima também tenha sido definido aqui.
;; Escopo dinâmico
(defn h [] (binding [x 1] (f)))
;=> #'user/h
(h)
;=> 1
```
## Estruturas de Controle:
#
Na linguagem clojure, podemos perceber a existência de diversas estruturas de controle que tem o mesmo propósito das estruturas das linguagens tradicionais, porém com uma sintaxe diferente.
### **1. Condicional:**
#
- **if/else**
Clojure possui o operador if e o if-not. O interessante é que a palavra "else" não é utilizada; if realiza uma verificação lógica (true ou false) e caso seja true realiza a operação do primeiro input, caso não a do segundo. if-not tem o mesmo comportamento só que ao contrário.
```
(ns learn-structures.core
(:gen-class))
(defn learn-if
"exemplo simples if/else"
[x]
(if (= x 1)
(println "É um")
(println "Não é um")))
(defn learn-if-not
"exemplo simples if-not/else"
[x]
(if-not (= x 1)
(println "Não é um")
(println "É um")))
```
- **when**
É parecido com if, mas apenas produz um resultado para caso a condição seja atendida
```
(defn learn-when
"exemplo simples when"
[x]
(when (< x 10) (throw (AssertionError. "Entrada errada"))))
```
- **Cond, Condp e Case**
As três funções se assemelham com o construct switch de outras linguagens, então recebe uma variável e, com base em seu valor, faz comparações para produzir um resultado. A diferença entres as três está nas comparações; cond avalia diferentes operações que passamos diretamente e retorna a primeira que for satisfeita (podemos passar :else para avaliar o caso em que nenhuma condição tenha sido satisfeita). condp é semelhante à cond, mas recebe também a operação (função) a ser utilizada em todos os casos. Por fim, case faz uma comparação simples de igualdade. Nas duas últimas, não precisamos de uma keyword para definir um valor padrão.
```
(defn learn-cond
"exemplo simples cond"
[x]
(cond
(< x 1) "menor que 1"
(> x 1) "maior que 1"
:else "1"))
(defn learn-condp
"exemplo simples condp"
[x]
(condp = x
3 "é 3"
2 "é 2"
1 "é 1"
"Valor inesperado"))
(defn learn-case
"exemplo simples case"
[x]
(case x
3 "é 3"
2 "é 2"
1 "é 1"
"Valor inesperado"))
```
### **2. Repetição:**
#
Clojure possui uma macro for, porém não é muito utilizada e não é igual a outras linguagens (afinal Clojure é imutável). É mais comum utilizar loop em conjunto de recur.
- **for**
```
(defn learn-for
(for [x [0 1 2 3 4 5]
:let [y (* x 3)]
:when (even? y)]
y))
```
A função recebe um vetor com valores e/ou binding forms e produz um resultado. No exemplo abaixo, um vetor x é declarado, e com ajuda de :let, for irá iterar x e atribuir um valor a y. Após isso, when filtrará os pares e a função retorna y diretamente (que é uma lazy sequence).
- **loop**
```
(defn learn-loop
"learn-loo simples loop"
(loop [n x]
(when (> n 0)
(prinln n)
(recur (dec n)))))
```
loop é usada em conjunto com recur para que haja efeito. Veja que ele atribui x a n e que quando n for maior que zero, imprime seu valor, subtrai um com dec e volta para when. Quando for zero, quebra o loop e retorna.
| 26.488055 | 640 | 0.640381 | por_Latn | 0.999711 |
612f6f25cd4da7bc5f5f942d295a2c10e5a8f775 | 5,043 | md | Markdown | cse474/home_work002/readme.md | cosmicray001/academic | 6aa142baeba4bb1ad73b8669e37305ca0b5102a7 | [
"MIT"
] | 2 | 2020-09-02T12:07:47.000Z | 2020-11-17T11:17:16.000Z | cse474/home_work002/readme.md | cosmicray001/academic | 6aa142baeba4bb1ad73b8669e37305ca0b5102a7 | [
"MIT"
] | null | null | null | cse474/home_work002/readme.md | cosmicray001/academic | 6aa142baeba4bb1ad73b8669e37305ca0b5102a7 | [
"MIT"
] | 4 | 2020-08-11T14:23:34.000Z | 2020-11-17T10:52:31.000Z |
```python
#P2.7.1
def fnc(s, pos):
a = ord(pos[0]) - ord('A') + 1
b = ord(pos[1]) - ord('0')
a = 15 - a
b = 15 - b
if(len(s) <= a):
return "YES"
elif(len(s) <= b):
return "YES"
else:
return "NO"
s = input()
pos = input()
print(fnc(s, pos))
```
samiul
D3
YES
```python
#P2.7.2
def fnc(n):
mul = 1
for i in range(n):
mul = mul * (i + 1)
temp = mul
sm = 0
while(temp > 0):
sm = sm + int(temp % 10)
temp = temp / 10
if(mul % sm != 0):
#print(mul, sm)
return True
else:
return False
i = 1
while(fnc(i) == False):
i = i + 1
print(i)
```
23
```python
#P2.7.3
import math as m
def dot_fnc(a, b):
sum = 0
for i in range(3):
sum = sum + (a[i] * b[i])
return sum
def cross_fnc(a, b):
sum = 0
sum = sum + ((b[2] * a[1]) - (b[1] * a[2])) ** 2
sum = sum + (-((b[2] * a[0]) - (b[0] * a[2]))) ** 2
sum = sum + ((a[0] * b[1]) - (a[1] * b[0])) ** 2
return m.sqrt(sum)
a, b = [100, 200, -6], [4, -6, 5]
print("Dot product: ", dot_fnc(a, b))
a, b = [3, 1, -2], [1, -3, 4]
print("Cross product: ", cross_fnc(a, b))
```
Dot product: -830
Cross product: 17.320508075688775
```python
#P2.7.4
import math
def pyramid_AV(n, s, h):
pi = math.acos(-1.0)
a = .5 * s * (1 / math.tan(math.radians(pi / n)))
A = .5 * n * s * a
l = math.sqrt(h ** 2 + a ** 2)
V = (1 / 3) * A * h
S = A + .5 * n * s * l
return V, S
a, b = pyramid_AV(18, 20, 3)
print("Value of V: ", a, "\nValue of S: ", b)
```
Value of V: 590903.3152964646
Value of S: 1181806.877333751
```python
#P2.7.5
import math
def range(ang, v):
v = v ** 2
a = math.sin(math.radians(2 * ang))
return (v * a) / 9.81
def hight(ang, v):
v = v ** 2
a = math.sin(math.radians(ang)) ** 2
return (v * a) / (2 * 9.81)
print("Range: ", range(30, 10))
print("Height: ", hight(30, 10))
```
Range: 8.827985767425469
Height: 1.2742099898063197
```python
#P2.7.6
import math
def fnc(n):
if(n == 1 or n == 2):
return n
else:
return n * fnc(n - 2)
def sinm_cosn(m, n):
pii = math.acos(-1.0)
a = fnc(m - 1)
b = fnc(n - 1)
c = fnc(m + n)
ve = (a * b) / c
if(m % 2 == 0 and n % 2 == 0):
return ve * (pii / 2)
else:
return ve
print(sinm_cosn(2, 4))
```
0.09817477042468103
```python
#E2.7.7
def palindrome(s, i, j):
if(i > j):
return "palindrome"
elif(s[i] == s[j]):
return palindrome(s, i + 1, j - 1)
else:
return "not palindrome"
s = "MADAM"
print(palindrome(s, 0, len(s) - 1))
```
palindrome
```python
#P2.7.8
def fnc(a, b):
if(b == 0):
return 1
elif(b % 2 == 0):
re = fnc(a, b / 2)
return re * re
else:
return a * fnc(a, b - 1)
def fnc1(n):
co = 0
while(n > 0):
co = co + 1
n = n // 10
return co
n = int(input("Enter the value for n: "))
x = int(input("Enter the value for x: "))
a, b = x, x
ans = 0
for i in range(n - 1):
ans = fnc(a, b)
b = ans
print("Number of digits in ", n, x, ": ", fnc1(ans))
```
Enter the value for n: 3
Enter the value for x: 5
Number of digits in 3 5 : 2185
```python
#P3.1.1__1
import math, pylab, numpy
n = 1000
mn, mx = -20, 20
x = pylab.linspace(mn, mx, n)
temp = pylab.cos(x) ** 2
y = numpy.log(1 / temp)
pylab.plot(x, y)
pylab.show()
```
```python
#P3.1.1__2
import math, pylab, numpy
n = 1000
mn, mx = -20, 20
x = pylab.linspace(mn, mx, n)
temp = pylab.sin(x) ** 2
y = numpy.log(1 / temp)
pylab.plot(x, y)
pylab.show()
```
```python
#P3.1.3
import numpy as np, math as m
import pylab as plt
import scipy.stats
n = 1000
mn, mx, meam, std = 0.0, 16.0, 8.0, 2.0
x = np.linspace(mn, mx, n)
y = scipy.stats.norm.pdf(x,mean,std)
plt.plot(x, y)
plt.show()
```
```python
import math, pylab
n = 1000
mn, mx = -20., 20.
x = pylab.linspace(mn, mx, n)
y = pylab.sin(x) / x
pylab.plot(x, y)
pylab.show()
```
```python
import math, pylab
n = 1000
mn, mx = -2.0 * math.pi, 2.0 * math.pi
x = pylab.linspace(mn, mx, n)
y = pylab.sin(x) ** 2
pylab.plot(x, y)
pylab.show()
```
```python
import math, pylab
xmin, xmax = -2.0 * math.pi, 2 * math.pi
n = 1000
x = [0.] * n
y = [0.] * n
dx = (xmax - xmin) / (n - 1)
for i in range(n):
xpt = xmin + i * dx
x[i] = xpt
y[i] = math.sin(xpt) ** 2
pylab.plot(x, y)
pylab.show()
```
```python
import pylab
import numpy as np
ax, ay = [], []
for i in range(100):
ax.append(np.random.random())
ay.append(np.random.random())
pylab.scatter(ax, ay)
pylab.show()
```
```python
import pylab
ax = [0., 0.5, 1.0, 1.5, 2.0, 2.5, 3.0]
ay = [0.0, 0.25, 1.0, 2.25, 4.0, 6.25, 9.0]
pylab.plot(ax, ay)
pylab.show()
```
| 15.516923 | 55 | 0.505651 | eng_Latn | 0.221877 |
612fd643f6e58954eeea73b15b56a0fc922a675f | 172 | md | Markdown | README.md | LiviaAAndrade/estudo-node | 7be0cb8e826943c2ff29057ccdeb672f47bbffe8 | [
"MIT"
] | 1 | 2021-05-30T14:37:40.000Z | 2021-05-30T14:37:40.000Z | README.md | LiviaAAndrade/estudo-node | 7be0cb8e826943c2ff29057ccdeb672f47bbffe8 | [
"MIT"
] | null | null | null | README.md | LiviaAAndrade/estudo-node | 7be0cb8e826943c2ff29057ccdeb672f47bbffe8 | [
"MIT"
] | 2 | 2021-10-03T23:49:22.000Z | 2021-10-04T19:53:21.000Z | # <p align="center"> 🐱👤 Estudos de NodeJs </p>
<br />
# ✍
// ola ta certo isso?
Um repositório criado com o intuito de
registrar meus projetos para estudos com NodeJs.
| 19.111111 | 48 | 0.680233 | por_Latn | 0.999661 |
613094ed5030bbfaafa74918a8970200215a032f | 2,250 | md | Markdown | README.md | flowground/googleapis-com-appsactivity-connector | 71c5599c9bef73405f73d66ae2f88d9c07a8ca84 | [
"Apache-2.0"
] | 1 | 2019-07-06T13:28:19.000Z | 2019-07-06T13:28:19.000Z | README.md | flowground/googleapis-com-appsactivity-connector | 71c5599c9bef73405f73d66ae2f88d9c07a8ca84 | [
"Apache-2.0"
] | null | null | null | README.md | flowground/googleapis-com-appsactivity-connector | 71c5599c9bef73405f73d66ae2f88d9c07a8ca84 | [
"Apache-2.0"
] | null | null | null | #  Drive Activity **flow**ground Connector
## Description
A generated **flow**ground connector for the Drive Activity API (version v1).
Generated from: https://api.apis.guru/v2/specs/googleapis.com/appsactivity/v1/swagger.json<br/>
Generated at: 2019-06-11T18:14:34+03:00
## API Description
Provides a historical view of activity.
## Authorization
Supported authorization schemes:
- OAuth2
For OAuth 2.0 you need to specify OAuth Client credentials as environment variables in the connector repository:
* `OAUTH_CLIENT_ID` - your OAuth client id
* `OAUTH_CLIENT_SECRET` - your OAuth client secret
## Actions
### Returns a list of activities visible to the current logged in user. Visible activities are determined by the visiblity settings of the object that was acted on, e.g. Drive files a user can see. An activity is a record of past events. Multiple events may be merged if they are similar. A request is scoped to activities from a given Google service using the source parameter.
*Tags:* `activities`
#### Input Parameters
* `drive.ancestorId` - _optional_ - Identifies the Drive folder containing the items for which to return activities.
* `drive.fileId` - _optional_ - Identifies the Drive item to return activities for.
* `groupingStrategy` - _optional_ - Indicates the strategy to use when grouping singleEvents items in the associated combinedEvent object.
Possible values: driveUi, none.
* `pageSize` - _optional_ - The maximum number of events to return on a page. The response includes a continuation token if there are more events.
* `pageToken` - _optional_ - A token to retrieve a specific page of results.
* `source` - _optional_ - The Google service from which to return activities. Possible values of source are:
- drive.google.com
* `userId` - _optional_ - Indicates the user to return activity for. Use the special value me to indicate the currently authenticated user.
## License
**flow**ground :- Telekom iPaaS / googleapis-com-appsactivity-connector<br/>
Copyright © 2019, [Deutsche Telekom AG](https://www.telekom.de)<br/>
contact: flowground@telekom.de
All files of this connector are licensed under the Apache 2.0 License. For details
see the file LICENSE on the toplevel directory.
| 46.875 | 378 | 0.772889 | eng_Latn | 0.976242 |
6130d35bf45ec77f11cd1158268c51f35abbc71d | 2,169 | md | Markdown | CVE-2022-22908/Readme.md | NF-Security-Team/CVEs | cbacc298e409a214d046a643f80ed1b4e8914785 | [
"MIT"
] | null | null | null | CVE-2022-22908/Readme.md | NF-Security-Team/CVEs | cbacc298e409a214d046a643f80ed1b4e8914785 | [
"MIT"
] | null | null | null | CVE-2022-22908/Readme.md | NF-Security-Team/CVEs | cbacc298e409a214d046a643f80ed1b4e8914785 | [
"MIT"
] | null | null | null | # Coordinated Disclosure Timeline
04/01/2022: Report submission to Vendor via Ticket <br>
05/01/2022: Vendor acknowledged CVE and has been notified of my intention to publish the advisory <br>
05/01/2022: CVE submission sent to MITRE.org <br>
17/02/2022: CVE reservation "CVE-2022-22908" <br>
26/02/2022: CVE advisory publishment via this repository <br>
# Executive Summary
An issue found in "SangforCSClient.exe", a core component of Sangfor VDI Client v5.4.2.1006 allows attackers to access user credentials via unspecified vectors.
# Technical Summary
To exploit the vulnerability an attacker must get a Full Dump of the "SangforCSClient.exe" process after the user inserted at least one time his credentials and clicked "Log In" button.
After a Log In try any string previously inserted in "Username:" and "Password:" textboxes will be written in plaintext inside the Full Dump near known and standard strings or hex array.
IMPORTANT: this local vulnerability can expose useful information to an attacker willing to escalate his privileges. After a successful attack lateral movement can be done via multiple ways.
# Product
Sangfor VDI Client
# Tested Version
v5.4.2.1006
# Details
<b> Issue: Sensitive data written in plaintext into process working memory </b>
After dumping the process Memory you can look for the victim password near the following HEX sequence
<br>
Password location is near "based authentication" string, or seen in HEX:
```
62 61 73 65 64 20 61 75 74 68 65 6E 74 69 63 61 74 69 6F 6E
```
<br>
the username is usually inside the first part of the memory dump, just like you can see in the following screenshot
<br>
# Impact
Auth data disclosure.
# CVE
CVE-2022-22908
# Credit
This issue was discovered and reported by Nicolas Fasolo (@Err0r0x41414141) team Owner of NF_Security (www.threatfeedservice.it).
# Contact
You can contact the NF_Security team at info@threatfeedservice.it, please include a reference to CVE-2022-22908 in any communication regarding this topic.
| 38.732143 | 190 | 0.78331 | eng_Latn | 0.994535 |
6132715de18f78205bab428014200c305c5c2802 | 378 | md | Markdown | src/com/interview/problems/election/winner/README.md | gosaliajigar/ProblemSolving | 078a769fe61eaf54c4b90c22b96f7af84b0fee1e | [
"MIT"
] | null | null | null | src/com/interview/problems/election/winner/README.md | gosaliajigar/ProblemSolving | 078a769fe61eaf54c4b90c22b96f7af84b0fee1e | [
"MIT"
] | null | null | null | src/com/interview/problems/election/winner/README.md | gosaliajigar/ProblemSolving | 078a769fe61eaf54c4b90c22b96f7af84b0fee1e | [
"MIT"
] | null | null | null | Problem Statement: Build a election winner finder which follows the criteria ...
1) It will receive data set of votes along with candidate and timestamp information.
2) At any given time, it should give us the information about the winner considering no. of votes.
3) In an event of tie, it should give the candidates that are involved in tie.
Solution : Run the Problem from | 54 | 98 | 0.783069 | eng_Latn | 0.999669 |
61329f96bd2bac557e226cd9f035e2c8afd00983 | 20,809 | md | Markdown | articles/active-directory/active-directory-aadconnect-version-history.md | OpenLocalizationTestOrg/azure-docs-pr16_de-DE | bf18172a4f9060051b3861ff8930d9f0303f7f10 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/active-directory-aadconnect-version-history.md | OpenLocalizationTestOrg/azure-docs-pr16_de-DE | bf18172a4f9060051b3861ff8930d9f0303f7f10 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/active-directory-aadconnect-version-history.md | OpenLocalizationTestOrg/azure-docs-pr16_de-DE | bf18172a4f9060051b3861ff8930d9f0303f7f10 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Azure AD verbinden: Versionsverlauf Release | Microsoft Azure"
description="In diesem Thema werden alle Versionen von Azure AD verbinden und Azure-Active Directory-Synchronisierung"
services="active-directory"
documentationCenter=""
authors="AndKjell"
manager="femila"
editor=""/>
<tags
ms.service="active-directory"
ms.devlang="na"
ms.topic="article"
ms.tgt_pltfrm="na"
ms.workload="identity"
ms.date="08/23/2016"
ms.author="billmath"/>
# <a name="azure-ad-connect-version-release-history"></a>Azure AD verbinden: Release-Versionsverlauf
Das Team Azure Active Directory aktualisiert regelmäßig Azure AD-Verbinden mit neuen Features und Funktionen. Nicht alle Ergänzungen gelten für alle Zielgruppen.
In diesem Artikel dient, mit deren Hilfe Sie die Versionen verfolgen, die freigegeben wurden, und Sie wissen, ob Sie auf die neueste Version oder nicht aktualisieren müssen.
Dies ist eine Liste der verwandten Themen:
Thema |
--------- | --------- |
Schritte zum Aktualisieren von Azure AD-verbinden | Andere Methoden zum [Upgrade von einer früheren Version auf die neueste](active-directory-aadconnect-upgrade-previous-version.md) Azure AD verbinden Release.
Erforderliche Berechtigungen | Welche Berechtigungen zum Anwenden von Updates erforderlich sind finden Sie unter [Konten und Berechtigungen](./connect/active-directory-aadconnect-accounts-permissions.md#upgrade)
Herunterladen| [Download Azure AD verbinden](http://go.microsoft.com/fwlink/?LinkId=615771)
## <a name="112810"></a>1.1.281.0
Zur Verfügung: 2016 August
**Feste Probleme:**
- Intervall synchronisieren Änderungen nicht durchgeführt erst nach Abschluss der nächsten Synchronisierung Zyklus.
- Azure AD verbinden-Assistent akzeptiert keine Azure AD-Konto, dessen Benutzername mit einem Unterstrich beginnt (\_).
- Azure AD verbinden-Assistenten nicht authentifiziert Azure AD-Konto bereitgestellt werden, wenn das Kontokennwort zu viele Sonderzeichen enthält. Fehlermeldung "kann nicht Anmeldeinformationen überprüfen. Ein unerwarteter Fehler aufgetreten." wird zurückgegeben.
- Deinstallieren von Bereitstellungsserver deaktiviert die Synchronisierung von Kennwörtern in Azure AD-Mandanten und bewirkt, dass die Synchronisierung von Kennwörtern mit active Server fehlschlägt.
- Synchronisierung von Kennwörtern fehlschlägt in ungewöhnliche Fälle, wenn keine Kennworthash gespeichert, auf die Benutzer vorhanden ist.
- Wenn für das staging Modus Azure AD verbinden Server aktiviert ist, ist Kennwort abgeschlossenen writebackvorgängen nicht vorübergehend deaktiviert.
- Azure AD verbinden-Assistent wird die Synchronisierung der tatsächlichen Kennwort und Kennwort abgeschlossenen writebackvorgängen Konfiguration bei Server befindet sich im staging-Modus nicht angezeigt. Es wird immer diese als deaktiviert angezeigt.
- Konfiguration Änderungen Synchronisierung von Kennwörtern und Kennwort abgeschlossenen writebackvorgängen werden beim Server befindet sich im staging-Modus nicht vom Assistenten Azure AD verbinden beibehalten.
**Verbesserte:**
- Dieses Cmdlet der aktualisierten Start-ADSyncSyncCycle um anzugeben, ob es erfolgreich einen neuer synchronisieren Zyklus oder nicht gestartet werden kann.
- Dieses Cmdlet der hinzugefügten beenden-ADSyncSyncCycle zum Beenden der Synchronisierung Kreis und ein Vorgang derzeit ausgeführt werden.
- Dieses Cmdlet der aktualisierten beenden-ADSyncScheduler zum Beenden der Synchronisierung Kreis und ein Vorgang derzeit ausgeführt werden.
- Beim [Verzeichnis Erweiterungen](active-directory-aadconnectsync-feature-directory-extensions.md) Azure AD verbinden-Assistenten konfigurieren, kann Active Directory-Attribut vom Typ "Teletex-Zeichenfolge" jetzt ausgewählt sein.
## <a name="111890"></a>1.1.189.0
Veröffentlicht: 2016 Juni
**Feste beseitigt und produktverbesserungen:**
- Verbinden von Azure AD kann nun auf einen kompatiblen FIPS-Server installiert werden.
- Synchronisierung von Kennwörtern finden Sie unter [Kennwort synchronisieren und FIPS](active-directory-aadconnectsync-implement-password-synchronization.md#password-synchronization-and-fips)
- Ein Problem behoben, wo konnte ein NetBIOS-Name nicht auf den vollqualifizierten Domänennamen in der Active Directory-Connector aufgelöst werden.
## <a name="111800"></a>1.1.180.0
Veröffentlicht: 2016 Mai
**Neue Features:**
- Gibt eine Warnung aus, und hilft Ihnen der Überprüfung von Domänen, wenn Sie es nicht durchgearbeitet haben, vor dem Ausführen von Azure AD verbinden.
- Unterstützung für [Microsoft Cloud-Deutschland](active-directory-aadconnect-instances.md#microsoft-cloud-germany)hinzugefügt.
- Unterstützung für die neuesten [Microsoft Azure Government-Cloud](active-directory-aadconnect-instances.md#microsoft-azure-government-cloud) -Infrastruktur mit neuen URL-Anforderungen hinzugefügt.
**Feste beseitigt und produktverbesserungen:**
- Hinzugefügt Filtern zum Synchronisieren Regel-Editor zu synchronisieren Regeln suchen zu erleichtern.
- Verbesserte Leistung, wenn ein Leerzeichen Verbinder zu löschen.
- Feste Einheiten einer Probleme beim dasselbe Objekt sowohl gelöscht und in der gleichen ausführen (sogenannte löschen/hinzufügen) hinzugefügt wurde.
- Deaktivierte Regeln synchronisieren können nicht mehr reaktivieren im Lieferumfang von Objekten und Attributen auf Upgrade oder Verzeichnis Schema aktualisieren.
## <a name="111300"></a>1.1.130.0
Veröffentlicht: 2016 April
**Neue Features:**
- Unterstützung für mehrwertige Attribute auf [Verzeichnis Extensions](active-directory-aadconnectsync-feature-directory-extensions.md)hinzugefügt.
- Hinzugefügte Unterstützung für weitere Konfiguration Variationen für die [Automatische Aktualisierung](active-directory-aadconnect-feature-automatic-upgrade.md) berechtigt für das Upgrade vor berücksichtigt werden.
- Einige Cmdlets für [benutzerdefinierte Scheduler](active-directory-aadconnectsync-feature-scheduler.md#custom-scheduler)wird hinzugefügt.
## <a name="111190"></a>1.1.119.0
Veröffentlicht: 2016 März
**Feste Probleme:**
- Vorgenommen wird, dass seit Kennwort synchronisieren Express-Installation unter Windows Server 2008 (R2 Pre-ab) verwendet werden kann nicht auf diesem Betriebssystem unterstützt.
- Upgrade von DirSync mit einer benutzerdefinierten Filterkonfiguration nicht erwartungsgemäß.
- Beim Upgrade auf eine neuere Version, und es werden keine Änderungen an der Konfiguration, eine vollständige importieren/Synchronisierung nicht geplant werden soll.
## <a name="111100"></a>1.1.110.0
Zur Verfügung: 2016 Februar
**Feste Probleme:**
- Upgrades einer früheren Version funktioniert nicht, wenn die Installation nicht im Standardordner **C:\Programme Dateien** ist.
- Wenn Sie installieren und Aufheben der Markierung **Starten der Synchronisierung Prozess...** am Ende des Assistenten wird die Installationsassistenten erneut ausführen den Scheduler nicht aktivieren.
- Der Scheduler funktioniert nicht erwartungsgemäß auf Servern, wo das Datum/Uhrzeit-Format nicht US-En ist. Es blockiert auch `Get-ADSyncScheduler` korrekten Zeitpunkt zurück.
- Wenn Sie als die Anmeldung Option und das Upgrade eine frühere Version von Azure AD-Verbinden mit ADFS installiert haben, können nicht Sie den Installationsassistenten erneut ausführen.
## <a name="111050"></a>1.1.105.0
Zur Verfügung: 2016 Februar
**Neue Features:**
- Die Funktion für [Automatische Aktualisierung](active-directory-aadconnect-feature-automatic-upgrade.md) für Express-Einstellungen-Kunden.
- Unterstützung für die Verwendung von MFA und PIM im Assistenten zum Installieren globaler Administrator.
- Sie müssen Ihre Proxy auch den Datenverkehr in https://secure.aadcdn.microsoftonline-p.com dürfen, wenn Sie MFA verwenden dürfen.
- Sie müssen https://secure.aadcdn.microsoftonline-p.com für MFA ordnungsgemäß funktioniert Ihrer Liste der vertrauenswürdigen Websites hinzufügen.
- Ändern des Benutzers Anmeldung Methode nach Erstinstallation zulässig.
- Im Assistenten zum Installieren [Domäne und Organisationseinheit Filtern](./connect/active-directory-aadconnect-get-started-custom.md#domain-and-ou-filtering) zulassen. Dies ermöglicht außerdem das Herstellen einer Verbindung mit Gesamtstrukturen, wenn nicht alle Domänen verfügbar sind.
- [Planer](active-directory-aadconnectsync-feature-scheduler.md) ist in der Synchronisierungs-Engine integriert.
**Features für die Kundendaten von Seitenansicht in GA:**
- [Gerät abgeschlossenen writebackvorgängen](active-directory-aadconnect-feature-device-writeback.md).
- [Directory-Erweiterungen](active-directory-aadconnectsync-feature-directory-extensions.md).
**Neue Features von Preview:**
- Das neue Standardformat synchronisieren Zyklus das Intervall 30 Minuten ist. 3 Stunden für alle früheren Versionen werden verwendet. Fügt Support, um das Verhalten der [Scheduler](active-directory-aadconnectsync-feature-scheduler.md) zu ändern.
**Feste Probleme:**
- Die Seite überprüfen DNS-Domänen haben immer die Domänen erkannt.
- Anweisungen für die Domäne Administrator-Anmeldeberechtigungen beim ADFS konfigurieren.
- Der lokalen AD-Konten werden vom Assistenten nicht erkannt, wenn befindet sich in einer Domäne mit einer anderen DNS-Struktur als die Domäne aus.
## <a name="1091310"></a>1.0.9131.0
Zur Verfügung: 2015 Dezember
**Feste Probleme:**
- Kennwort synchronisieren funktioniert möglicherweise nicht, wenn Sie die Kennwörter in AD DS, jedoch funktioniert ändern, wenn Sie ein Kennwort festlegen.
- Wenn Sie einen Proxyserver verfügen, Azure AD-Authentifizierung möglicherweise ein Fehler auftreten, während der Installation oder heben Sie die Markierung auf der Konfigurationsseite, Upgrade.
- SQL Server schlägt fehl, wenn Sie nicht SA in SQL sind aus einer früheren Version von Azure AD-Verbinden mit einem vollständigen aktualisieren.
- Aktualisieren von einer früheren Version von Azure AD-Verbinden mit einem Remote wird SQL Server die Fehlermeldung "Kein ADSync SQL-Datenbank Zugriff auf" angezeigt.
## <a name="1091250"></a>1.0.9125.0
Zur Verfügung: 2015 November
**Neue Features:**
- Die ADFS zum Azure AD-vertrauen können neu zu konfigurieren.
- Aktualisieren von Active Directory-Schema können und erneut synchronisieren Regeln generieren.
- Deaktivieren Sie eine Regel synchronisieren können.
- Definieren von "AuthoritativeNull" als neue Literal in einer Regel synchronisieren.
**Neue Features von Preview:**
- [Azure AD verbinden Gesundheit für synchronisieren](active-directory-aadconnect-health-sync.md).
- Unterstützung für die Synchronisierung von Kennwörtern [Azure Active Directory-Domänendiensten](active-directory-passwords-getting-started.md#enable-users-to-reset-or-change-their-ad-passwords) .
**Neue unterstützte Szenario:**
- Mehrere lokalen Exchange-Organisationen unterstützt. Weitere Informationen finden Sie unter [hybridbereitstellungen mit mehreren Active Directory-Gesamtstrukturen](https://technet.microsoft.com/library/jj873754.aspx) .
**Feste Probleme:**
- Kennwort Synchronisierungsprobleme:
- Objekt von außerhalb des Bereichs auf in Bereich verschoben wird nicht das Datenbankkennwort synchronisiert haben. Diese schichtigen Organisationseinheit sowohl Attribut zu filtern.
- Markieren eine neue Organisationseinheit synchron aufnehmen möchten ist eine vollständige Kennwort Synchronisierung nicht erforderlich.
- Wenn ein deaktivierter Benutzer aktiviert ist, ist das Kennwort nicht synchron.
- Die Kennwort "Wiederholen" Warteschlange unbegrenzte und die vorherige Grenze von 5.000 Objekte zu entfernenden wurde entfernt.
- [Verbesserte Problembehandlung](active-directory-aadconnectsync-implement-password-synchronization.md#troubleshoot-password-synchronization).
- Es können keine Verbindung mit Active Directory mit Windows Server 2016 Gesamtstruktur funktionsübergreifendes Ebene.
- Kann nicht zum Ändern der Gruppe für die Gruppe filtern nach Erstinstallation verwendet.
- Ein neues Benutzerprofil wird nicht mehr auf dem Server Azure AD verbinden für jeden Benutzer daran, wie Sie ein Kennwort ändern Kennwort abgeschlossenen writebackvorgängen aktiviert erstellt werden.
- Long Integer Werte synchron Regeln Bereiche kann nicht verwendet werden.
- Das Kontrollkästchen "Gerät abgeschlossenen writebackvorgängen" bleibt deaktiviert, wenn es nicht erreichbar Domänencontroller sind.
## <a name="1086670"></a>1.0.8667.0
Zur Verfügung: 2015 August
**Neue Features:**
- Der Assistent zum Installieren von Azure AD verbinden ist nun für alle Sprachen für Windows Server lokalisiert.
- Hinzugefügte Unterstützung für Konto entsperren bei Verwendung von Azure AD-Kennwort Management.
**Feste Probleme:**
- Assistent zum Installieren von Azure AD verbinden stürzt ab, wenn ein anderer Benutzer weiterhin Installation statt der Person, die zuerst die Installation gestartet.
- Wenn eine frühere Deinstallation Azure AD verbinden fehlschlägt Azure AD verbinden synchronisieren ordnungsgemäß deinstallieren können, ist es nicht möglich, neu zu installieren.
- Nicht installieren Azure AD Verbinden mit Express installieren, wenn der Benutzer nicht in der Domäne aus, der die Struktur ist oder eine nicht englischen Version von Active Directory verwendet wird.
- Wenn Sie der vollqualifizierten Domänennamen des Benutzerkontos Active Directory aufgelöst werden kann, wird eine irreführende Fehlermeldung "Fehler beim commit des Schemas" angezeigt.
- Wenn das Konto in den Active Directory-Connector verwendet außerhalb des Assistenten geändert wird, tritt der Assistent auf nachfolgende ausgeführt wird.
- Verbinden von Azure AD kann manchmal auf einem Domain Controller installieren.
- Kann nicht aktivieren und deaktivieren "Staging Modus" aus, wenn die Erweiterungsattribute hinzugefügt wurden.
- Kennwort abgeschlossenen writebackvorgängen, schlägt aufgrund eines falschen Kennworts auf Active Directory-Connector einige Konfiguration.
- DirSync kann nicht aktualisiert werden, wenn dn in Attribut Filtern verwendet wird.
- Übermäßige CPU-Auslastung, wenn das Zurücksetzen von Kennwörtern verwenden.
**Entfernte Preview-Features:**
- Der Preview-Features, die [Benutzer abgeschlossenen writebackvorgängen](active-directory-aadconnect-feature-preview.md#user-writeback) vorübergehend entfernt wurde, basierend auf Feedback von Kunden Vorschau. Es wird später erneut hinzugefügt werden, wenn wir die bereitgestellte Feedback berücksichtigt haben.
## <a name="1086410"></a>1.0.8641.0
Veröffentlicht: 2015 Juni
**Erste Version von Azure AD verbinden.**
Geänderte Name aus Azure AD synchronisieren, Azure AD verbinden.
**Neue Features:**
- [Express-Einstellungen](./connect/active-directory-aadconnect-get-started-express.md) -installation
- [Konfigurieren von ADFS](./connect/active-directory-aadconnect-get-started-custom.md#configuring-federation-with-ad-fs) können
- [Aktualisieren von DirSync](./connect/active-directory-aadconnect-dirsync-upgrade-get-started.md) können
- [Unbeabsichtigte Löschen sperren](active-directory-aadconnectsync-feature-prevent-accidental-deletes.md)
- [Das staging von Modus](active-directory-aadconnectsync-operations.md#staging-mode) eingeführt
**Neue Features von Preview:**
- [Benutzer abgeschlossenen writebackvorgängen](active-directory-aadconnect-feature-preview.md#user-writeback)
- [Gruppe abgeschlossenen writebackvorgängen](active-directory-aadconnect-feature-preview.md#group-writeback)
- [Gerät abgeschlossenen writebackvorgängen](active-directory-aadconnect-feature-device-writeback.md)
- [Directory-Erweiterungen](active-directory-aadconnect-feature-preview.md#directory-extensions)
## <a name="104940501"></a>1.0.494.0501
Veröffentlicht: 2015 Mai
**Neue Anforderung:**
- Azure AD-Synchronisierung erforderlich ist jetzt der .net Framework-Version 4.5.1 installiert sein.
**Feste Probleme:**
- Kennwort abgeschlossenen writebackvorgängen von Azure AD-wird mit einer Servicebus-Konnektivitätsfehlern fehl.
## <a name="104910413"></a>1.0.491.0413
Veröffentlicht: 2015 April
**Feste beseitigt und produktverbesserungen:**
- Active Directory-Connector verarbeitet keine Löschvorgänge ordnungsgemäß, wenn der Papierkorb aktiviert ist, und es mehrere Domänen in der Gesamtstruktur gibt.
- Die Leistung von Importvorgänge wurde für Azure Active Directory Connector verbessert.
- Wenn verfügt über eine Gruppe hat die Mitgliedschaft überschritten (standardmäßig der Grenzwert ist festgelegt auf 50k Objekte), die Gruppe in Azure Active Directory gelöscht wurde. Das neue Verhalten ist, dass die Gruppe bleibt, ein Fehler ausgelöst wird und keine neuen Änderungen für die Mitgliedschaft exportiert werden.
- Wenn ein eingerichtetes löschen mit den gleichen DN bereits in dem Bereich Verbinder vorhanden ist, kann ein neues Objekt bereitgestellt werden.
- Einige Objekte werden für während einer Synchronisierungs Delta synchronisiert werden zwar keine bereitgestellt werden, klicken Sie auf das Objekt Änderung markiert.
- Erzwingen eine Synchronisierung Kennwort wird auch die Liste der bevorzugte DC entfernt.
- Probleme mit einigen Objekten Staaten verfügt CSExportAnalyzer
**Neue Features:**
- Eine Verknüpfung kann jetzt mit "ANY" Objekttyp im Metaverse verbinden.
## <a name="104850222"></a>1.0.485.0222
Zur Verfügung: 2015 Februar
**Verbesserte:**
- Verbesserte importieren optimale Leistung.
**Feste Probleme:**
- Kennwort synchronisieren berücksichtigt das CloudFiltered Attribut untersuchten Attribut Filtern nach. Gefilterte Objekte werden im Bereich für die Synchronisierung von Kennwörtern nicht mehr.
- In wenigen Situationen, in dem der Suchtopologie sehr viele Domänencontroller hatten, funktioniert nicht Kennwort synchronisieren.
- "Angehalten-Server" beim Importieren aus der Azure AD-Verbinder nach Device Management wurde in Azure AD/Intune aktiviert.
- Teilnehmen an einer Fremdschlüssel Sicherheit Hauptbenutzer (FSPs) aus mehreren Domänen in der gleichen Struktur führt zu einem Fehler mehrdeutige Join.
## <a name="104751202"></a>1.0.475.1202
Zur Verfügung: 2014 Dezember
**Neue Features:**
- Führen Sie die Synchronisierung von Kennwörtern basierendes Attribut Filtern wird jetzt unterstützt. Weitere Informationen hierzu finden Sie unter [Synchronisierung von Kennwörtern mit Filtern](active-directory-aadconnectsync-configure-filtering.md).
- Das Attribut MsDS-ExternalDirectoryObjectID wird wieder in AD geschrieben werden. Dies fügt Unterstützung für Office 365-Anwendungen mit OAuth2 auf beide, Online zugreifen und lokaler Postfächer in einer Exchange-Hybridbereitstellung.
**Feste Upgrade Probleme:**
- Eine neuere Version von der Anmelde-Assistenten wird auf dem Server verfügbar.
- Ein Pfad für die benutzerdefinierte Installation wurde verwendet, um die Azure AD synchronisieren zu installieren.
- Ein ungültiges benutzerdefinierte Verknüpfung Kriterium blockiert das Upgrade.
**Weitere Updates:**
- Feste Vorlagen für Office Pro Plus an.
- Installationsprobleme mit festen aufgrund von Benutzernamen, die mit einem Bindestrich beginnen.
- Dadurch die Einstellung SourceAnchor verlieren, wenn Sie den Assistenten ein zweites Mal ausführen.
- Feste ETW für die Synchronisierung von Kennwörtern
## <a name="104701023"></a>1.0.470.1023
Zur Verfügung: 2014 Oktober
**Neue Features:**
- Synchronisierung von Kennwörtern aus mehreren lokalen AD in Azure Active Directory.
- Installation lokalisierten Benutzeroberfläche für alle Sprachen für Windows Server.
**Aktualisieren von AADSync 1.0 GA**
Wenn Sie bereits Azure AD synchronisieren installiert haben, gibt es einen weiterer Schritt, die, den Sie haben, wird für den Fall, dass Sie eine Out-of-Box-Synchronisierung geändert haben. Nachdem Sie auf die 1.0.470.1023 aktualisiert haben lassen Sie, Sie die Synchronisierung, die Regeln, die Sie geändert haben doppelt vorhanden sind. Für jede geänderte synchronisieren Regel folgendermaßen vor:
- Suchen Sie die Regel synchronisieren Sie geändert haben, und notieren Sie sich die Änderungen vor.
- Löschen Sie die Regel synchronisieren.
- Suchen Sie die neue synchronisieren Regel erstellte Azure AD synchronisieren, und erneut anzuwenden Sie die Änderungen.
**Berechtigungen für die AD-Konto**
Active Directory-Konto muss die Kennworthashes aus dem Active Directory lesen können zusätzliche Berechtigungen erteilt werden. Die Berechtigungen zum erteilen sind "Repliziert Directory Änderungen" und "Repliziert Directory Änderungen alle" benannte. Beide Berechtigungen sind erforderlich, um die Kennworthashes lesen können
## <a name="104190911"></a>1.0.419.0911
Zur Verfügung: 2014 September
**Erste Version von Azure AD synchronisieren.**
## <a name="next-steps"></a>Nächste Schritte
Erfahren Sie mehr über die [Integration von Ihrem lokalen Identitäten mit Azure Active Directory](active-directory-aadconnect.md).
| 65.851266 | 399 | 0.816954 | deu_Latn | 0.995845 |
613316e73430cdd80a3590d0953cbe38225322a9 | 147 | md | Markdown | content/topics/2013-07-18.en.md | zEttOn86/simizlab-homepage | 2a44bef03a2a4763fedcd93bba282c79810e9ad5 | [
"Apache-2.0"
] | null | null | null | content/topics/2013-07-18.en.md | zEttOn86/simizlab-homepage | 2a44bef03a2a4763fedcd93bba282c79810e9ad5 | [
"Apache-2.0"
] | null | null | null | content/topics/2013-07-18.en.md | zEttOn86/simizlab-homepage | 2a44bef03a2a4763fedcd93bba282c79810e9ad5 | [
"Apache-2.0"
] | 1 | 2019-08-28T19:07:47.000Z | 2019-08-28T19:07:47.000Z | ---
date: 2013-07-18
description: ""
auther: ""
tags: ["2013"]
draft: false
---
18,19 July
MIA lab. organized 17th Computational Anatomy Seminar.
| 13.363636 | 54 | 0.687075 | eng_Latn | 0.46458 |
61335f0a6f0a74e6b3e9aceebc4fe4211b86e0e9 | 1,690 | md | Markdown | README.md | jnylund/latlongchooser | ba56d24199f96d42b3b2914b75075297ae31d7ba | [
"MIT"
] | null | null | null | README.md | jnylund/latlongchooser | ba56d24199f96d42b3b2914b75075297ae31d7ba | [
"MIT"
] | null | null | null | README.md | jnylund/latlongchooser | ba56d24199f96d42b3b2914b75075297ae31d7ba | [
"MIT"
] | null | null | null | [](https://www.webcomponents.org/element/solutionstreet/latlongchooser)
# \<lat-long-chooser\>
A Polymer (lit-element) to choose latitude and longitude.
## Running locally
```
$ npm install
$ polymer serve
```
[then open "http://127.0.0.1:8081/components/@solutionstreet/latlongchooser/" in your browser](http://127.0.0.1:8081/components/@solutionstreet/latlongchooser/)
This component has 2 properties to style the buttons
There are slots for all the title text
This button sends an custom event called lag-long-chosen, see example below for details
## Example
```html
<lat-long-chooser buttonBackgroundColor="red" buttonForegroundColor="yellow">
<script>
<span slot="degrees-mins-secs-title">Deg/Min/Sec<span>
<span slot="latitude-title">Lat:</span>
<span slot="longitude-title">Long:</span>
<span slot="dec-degrees-title">Degrees in Decimal Form:</span>
<span slot="map-title">My Map Locator:</span>
var latLongDialog = document.getElementById('latLongDialog');
latLongDialog.addEventListener('lag-long-chosen', function(e){
console.log("got event from dialog")
var latDegrees = e.target.latDecimalDegrees;
var longDegrees = e.target.longDecimalDegrees;
var latLocalElement = document.getElementById("latDecimalId")
latLocalElement.innerHTML = latDegrees
var longLocalElement = document.getElementById("longDecimalId")
longLocalElement.innerHTML = longDegrees
});
</script>
</lat-long-chooser>
```
| 37.555556 | 171 | 0.692308 | eng_Latn | 0.476816 |
6134575874e280ee8fb15c9788a58fd264ef01a4 | 2,909 | md | Markdown | docs/packages/react.md | kirillku/reatom | dae0c0e007d9678fbcd699aca424529460b42aba | [
"MIT"
] | null | null | null | docs/packages/react.md | kirillku/reatom | dae0c0e007d9678fbcd699aca424529460b42aba | [
"MIT"
] | null | null | null | docs/packages/react.md | kirillku/reatom | dae0c0e007d9678fbcd699aca424529460b42aba | [
"MIT"
] | null | null | null | # @reatom/react
React bindings package for [Reatom](https://github.com/artalar/reatom) store.
[](https://www.npmjs.com/package/@reatom/react)
[](https://bundlephobia.com/result?p=@reatom/react)
## Install
```
npm i @reatom/react
```
or
```sh
yarn add @reatom/react
```
> NOTE. **@reatom/react** depends on and works with [@reatom/core](https://reatom.js.org/#/reatom-core).
## Hooks Api
### useAtom
Connects the atom to the store provided in context and returns the state of the atom from the store (or default atom state).
#### Retrieve atom state from the store
```ts
const atomValue = useAtom(atom)
```
#### Retrieve atom state and apply dynamic selector
```ts
const atomValue = useAtom(atom, atomState => atomState[props.id], [props.id])
```
> NOTE. You need to pass a third argument to `useAtom` that is the array of values that the atom depends on. To make sure the state selector is reapplied and derived value is recalculated when dependencies change.
#### Mount without subscription (for subscribing atoms to actions)
```ts
const atomValue = useAtom(atom, () => null, [])
```
### useAction
Binds action and dispatch to the store provided in the context.
#### Basic (useAction)
```ts
const handleDoSome = useAction(doSome)
```
#### Prepare payload for dispatch
```ts
const handleDoSome = useAction(value => doSome({
id: props.id,
value
}), [props.id])
```
#### Conditional dispatch
Dispatch is not called if action creator doesn't return an action.
```ts
const handleDoSome = useAction(payload => {
if (condition) return doSome(payload)
}, [])
```
## Usage
### Step 1. Create store
```jsx
// App
import React from 'react';
import { createStore } from '@reatom/core'
import { context } from '@reatom/react'
import { Form } from './components/Form'
import './App.css';
export const App = () => {
// create stateful context for atoms execution
const store = createStore();
return (
<div className='App'>
<context.Provider value={store}>
<Form />
</context.Provider>
</div>
);
}
```
### Step 2. Use in components
```jsx
// components/Form
import { declareAction, declareAtom } from '@reatom/core'
import { useAction, useAtom } from '@reatom/react'
const changeName = declareAction()
const nameAtom = declareAtom('', on => [
on(changeName, (state, payload) => payload)
])
export const Form = () => {
const name = useAtom(nameAtom)
const handleChangeName = useAction(e => changeName(e.target.value))
return (
<form>
<label htmlFor="name">Enter your name</label>
<input id="name" value={name} onChange={handleChangeName}/>
</form>
)
}
```
---
[Open source code on GitHub](https://github.com/artalar/reatom/tree/master/packages/react)
| 22.206107 | 213 | 0.682021 | eng_Latn | 0.664331 |
6135cf3703fb73249de8c2addc35ef7002be14b3 | 825 | md | Markdown | README.md | jacobmarshall-etc/docker-cleanup-volumes | 4dce6102f848056075d159b838bc95b4bcf72b4c | [
"MIT"
] | null | null | null | README.md | jacobmarshall-etc/docker-cleanup-volumes | 4dce6102f848056075d159b838bc95b4bcf72b4c | [
"MIT"
] | null | null | null | README.md | jacobmarshall-etc/docker-cleanup-volumes | 4dce6102f848056075d159b838bc95b4bcf72b4c | [
"MIT"
] | null | null | null | docker-cleanup-volumes.sh
======================
Shellscript to delete orphaned docker volumes in /var/lib/docker/volumes and /var/lib/docker/vfs/dir
usage: sudo ./docker-cleanup-volumes.sh [--dry-run]
--dry-run : Use the --dry-run option to have the script print the volumes that would have been deleted without actually deleting them.
### Running from Docker
run the "latest" forward compatible Docker client version, currently 1.5.0 (available are 1.4.1, 1.5.0 and 1.6.2)
```
docker run -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker:/var/lib/docker --rm martin/docker-cleanup-volumes --dry-run
```
or run a specific Docker client version, e.g. 1.4.1
```
docker run -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker:/var/lib/docker --rm martin/docker-cleanup-volumes:1.4.1 --dry-run
```
| 43.421053 | 141 | 0.715152 | eng_Latn | 0.798561 |
613697223366ec837ae30d5ab20c95841f9e8e0d | 1,535 | md | Markdown | src/posts/matt-haugheys-podcast-diet.md | polarbirke/chrisennsdotcom | 7a9df5abefa429ef2b1a4bbac592f0d4830b03cd | [
"MIT"
] | null | null | null | src/posts/matt-haugheys-podcast-diet.md | polarbirke/chrisennsdotcom | 7a9df5abefa429ef2b1a4bbac592f0d4830b03cd | [
"MIT"
] | null | null | null | src/posts/matt-haugheys-podcast-diet.md | polarbirke/chrisennsdotcom | 7a9df5abefa429ef2b1a4bbac592f0d4830b03cd | [
"MIT"
] | null | null | null | ---
title: "Matt Haughey''s Podcast Diet"
date: 2018-08-10
draft: false
---
Matt's [got a list of podcasts](https://a.wholelottanothing.org/2018/08/10/my-podcast-diet-august-2018/) you may not have heard of to add to your listening schedule. He's broken them down by priority from "drop everything to listen to these" to "shows I occasionally pick up an episode when I hear it’s a good one".
> Podcast discovery is still a mostly-broken problem...There isn’t really a good app to share podcasts quite yet (Breaker seems to be getting there), so posts like this will suffice.
I personally think this is something that shouldn't be fixed by algorithms. I think podcast player apps need to make it super easy to auto-share episodes of a show you like to social media - as easy as it is on my favourite app [Pocket Casts](https://www.shiftyjelly.com/pocketcasts/), I should be able to just hit a heart and have that be shared automagically (whether from the app or via a bit of [If This Then That](https://ifttt.com) API wizardry):
### Sharing from Pocket Casts
[YouTube tutorial](https://youtu.be/kYgQ-7JRjjM)
I'd much rather hear about a great episode of a podcast from a friend and then be able to listen to that episode and decide whether I want to subscribe or not. I'm wary of any one podcast app/service that's going to try and take over the whole experience - despite that idea being what millions of investment money is likely flowing into these days. Keep your algorithms as far away from my podcasts as possible. Please.
| 80.789474 | 452 | 0.76873 | eng_Latn | 0.9995 |
6137d6b3575e44b67ba1054cad6ceb237896d125 | 1,787 | md | Markdown | articles/api/management/guides/applications/rotate-client-secret.md | thepsi/auth0_docs | ad47b5eb1556496ec6c386d9c1be57069d32a657 | [
"MIT"
] | null | null | null | articles/api/management/guides/applications/rotate-client-secret.md | thepsi/auth0_docs | ad47b5eb1556496ec6c386d9c1be57069d32a657 | [
"MIT"
] | 1 | 2019-05-28T15:47:03.000Z | 2019-05-28T15:47:03.000Z | articles/api/management/guides/applications/rotate-client-secret.md | dafortune/docs | 44371369525043ce76dd0e5a26a992cc8c3fb947 | [
"MIT"
] | null | null | null | ---
title: Rotate Client Secret
description: Learn how to change your application's client secret using the Auth0 Management API.
topics:
- applications
- client-secrets
- mgmt-api
contentType:
- how-to
useCase:
- build-an-app
---
# Rotate Client Secret
This guide will show you how to change your application's client secret using Auth0's Management API. This task can also be performed [using the Dashboard](/dashboard/guides/applications/rotate-client-secret).
::: warning
New secrets may be delayed while rotating. To minimize downtime, we suggest you store the new client secret in your application's code as a fallback to the previous secret. This way, if the connection doesn't work with the old secret, your app will use the new secret.
Secrets can be stored in a list (or similar structure) until they're no longer needed. Once you're sure that an old secret is obsolete, you can remove its value from your app's code.
:::
1. Make a `POST` call to the [Rotate a Client Secret endpoint](/api/management/v2#!/Clients/post_rotate_secret). Be sure to replace `YOUR_CLIENT_ID` and `MGMT_API_ACCESS_TOKEN` placeholder values with your client ID and Management API Access Token, respectively.
```har
{
"method": "POST",
"url": "https://${account.namespace}/api/v2/clients/YOUR_CLIENT_ID/rotate-secret",
"headers": [
{ "name": "Authorization", "value": "Bearer MGMT_API_ACCESS_TOKEN" }
]
}
```
| Value | Description |
| - | - |
| `YOUR_CLIENT_ID` | Τhe ID of the application to be updated. |
| `MGMT_API_ACCESS_TOKEN` | [Access Tokens for the Management API](/api/management/v2/tokens) with the scope `update:client_keys`. |
2. Update authorized applications
When you rotate a client secret, you must update any authorized applications with the new value.
| 41.55814 | 268 | 0.75042 | eng_Latn | 0.96098 |
6138001c5c36a4b599e19c08afc3fcc6527ab97a | 859 | md | Markdown | dbPrinciple/DCL.md | Tanglong9344/db | 52b86d0c3d083ec29f98fe3df7faf256c87ca9d6 | [
"MIT"
] | 7 | 2018-05-20T14:35:15.000Z | 2019-09-04T06:29:51.000Z | dbPrinciple/DCL.md | Tanglong9344/SQL | 74cc454408556f87aa2e5eeb005ba110e0baa8d0 | [
"MIT"
] | null | null | null | dbPrinciple/DCL.md | Tanglong9344/SQL | 74cc454408556f87aa2e5eeb005ba110e0baa8d0 | [
"MIT"
] | 1 | 2019-05-31T05:22:38.000Z | 2019-05-31T05:22:38.000Z | # DCL(Data Control Language)
### 关键字：grant revoke
+ DBA为用户注册|GRANT
1. 基本格式：
```
GRANT<权限列表>on<库.表>TO<用户名@'ip'>[IDENTIFIED BY<口令>][with grant option];
```
2. 说明：
```
<权限列表>：ALL,insert,select,update,delete,drop,create,alter
[with grant option]：用户可以将该权限授予其他用户
```
3. 示例：
```
# 授予用户root对于所有表的全部权限，ip是'192.168.1.1'，口令是"password"
grant all on *.* to root@'192.168.1.1' identified by "password";
flush privileges; //授权之后，不要忘记更新权限表
# 查看当前用户的所有权限
show grants;
```
---
---
```
# 查看指定用户root@'192.168.1.1'的权限
show grants for root@'192.168.1.1';
```
---
---
+ DBA撤销对用户的注册|REVOKE
1. 基本格式：
```
REVOKE<权限列表>on<库.表>FROM<用户名@'ip'>;
```
2. 示例
```
# 撤销用户的所有权限
revoke all on *.* from root@'192.168.1.1';
flush privileges;//刷新权限表
``` | 20.95122 | 71 | 0.601863 | yue_Hant | 0.81782 |
6139ecdc62733852149954d3092432e3c56a415f | 475 | md | Markdown | content/post/my-first-blog-post.md | givingthought/givingthought.github.io | b40c9ee15ebd94cdae534346ff3291054c2f6961 | [
"MIT"
] | null | null | null | content/post/my-first-blog-post.md | givingthought/givingthought.github.io | b40c9ee15ebd94cdae534346ff3291054c2f6961 | [
"MIT"
] | null | null | null | content/post/my-first-blog-post.md | givingthought/givingthought.github.io | b40c9ee15ebd94cdae534346ff3291054c2f6961 | [
"MIT"
] | null | null | null | ---
title: "My First Blog Post"
date: 2017-11-01T23:24:45-05:00
draft: false
---
# Hey everyone!
This is my first blog post. I hope you enjoy some random text so I can test formatting!.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent tellus lacus, auctor vehicula molestie quis, tempor quis velit. Quisque in quam ac leo efficitur vulputate. Phasellus ullamcorper aliquam sodales. Maecenas sit amet condimentum ipsum. Proin sit amet ligula elit. Mauris.
| 39.583333 | 285 | 0.774737 | eng_Latn | 0.544627 |
613b1ba5398089b7469404f1184faaa6bf7903bb | 1,920 | md | Markdown | doc/SIMULATION_EXERCISE.md | sweetkimchi/cellularautomata | f2a86e10729abeeb1a871160b0b83b3d285767b7 | [
"MIT"
] | null | null | null | doc/SIMULATION_EXERCISE.md | sweetkimchi/cellularautomata | f2a86e10729abeeb1a871160b0b83b3d285767b7 | [
"MIT"
] | null | null | null | doc/SIMULATION_EXERCISE.md | sweetkimchi/cellularautomata | f2a86e10729abeeb1a871160b0b83b3d285767b7 | [
"MIT"
] | null | null | null | # Simulation Lab Discussion
## Cell Society
## Names and NetIDs
Ji Yun Hyo - jh160, Shaw Phillips - sp422, Harrison Huang - hlh38
### High Level Design Ideas
### CRC Card Classes
This class's purpose or value is to manage something:
```java
public class Something {
// sums the numbers in the given data
public int getTotal (Collection<Integer> data)
// creates an order from the given data
public Order makeOrder (String structuredData)
}
```
This class's purpose or value is to organize the data from Something:
```java
public class Order {
// updates the information based on new data
public void update (int data)
}
```
### Use Cases
* Apply the rules to a middle cell: set the next state of a cell to dead by counting its number of
neighbors using the Game of Life rules for a cell in the middle (i.e., with all its neighbors)
```java
Something thing = new Something();
Value v = thing.getValue();
v.update(13);
```
* Apply the rules to an edge cell: set the next state of a cell to live by counting its number of
neighbors using the Game of Life rules for a cell on the edge (i.e., with some of its neighbors
missing)
```java
Something thing = new Something();
Value v = thing.getValue();
v.update(13);
```
* Move to the next generation: update all cells in a simulation from their current state to their
next state and display the result graphically
```java
Something thing = new Something();
Value v = thing.getValue();
v.update(13);
```
* Set a simulation parameter: set the value of a parameter, probCatch, for a simulation, Fire, based
on the value given in an XML file
```java
Something thing = new Something();
Value v = thing.getValue();
v.update(13);
```
* Switch simulations: use the GUI to change the current simulation from Game of Life to Wa-Tor
```java
Something thing = new Something();
Value v = thing.getValue();
v.update(13);
```
| 23.414634 | 100 | 0.709375 | eng_Latn | 0.985184 |
613b2aa5679e9425ec2afe14c7b58c716fe30cba | 3,670 | md | Markdown | content/blog/english/202105/20210526-english-speaking.md | offetuoso/hugo | f606f4ca0935e305dc2810afd17b7b9d6129e8db | [
"MIT"
] | 1 | 2021-05-04T13:22:07.000Z | 2021-05-04T13:22:07.000Z | content/blog/english/202105/20210526-english-speaking.md | offetuoso/hugo | f606f4ca0935e305dc2810afd17b7b9d6129e8db | [
"MIT"
] | null | null | null | content/blog/english/202105/20210526-english-speaking.md | offetuoso/hugo | f606f4ca0935e305dc2810afd17b7b9d6129e8db | [
"MIT"
] | null | null | null | ---
title: "잉그올 영어 회화 21.05.26"
image: "bg-post.jpg"
font_color: "white"
font_size: 30px
opacity: "0.4"
date: 2021-05-26
slug: "20210526-english-speak"
description: "영어 회화 문법정리"
draft: true
categories: ["English"]
subcategories: ["Speaking"]
tags: ["english","speak","talk","EngAll","잉그올"]
math: false
toc: true
---
## nervous about ~ (- 에 대해 긴장.)
> I am nervous about tomorrow’s coding test. (내일 코딩 테스트가 떨려요.)
## conduct ( 실시하다, 행위 )
> Who is conducting the test? (누가 테스트를 실시합니까?)
## recruitment ( 모집 )
> the recruitment of developer (개발자 모집)
## official (formal) ( 공식 )
> official recruitment (공식 모집)
## informal ( 비공식 )
> informalrecruitment recruitment (비공식 채용 모집)
## conducted by ~ (- 에 의해 실시/주관 )
> The test is conducted by 'A회사'. (테스트는 'A 회사'에서 진행합니다.)
## A says sth (A는 sth[주제 요약]이라고 말합니다. ) 주제 요약 (정보)
> The video says exercising regularly is helpful for our health. (비디오는 규칙적인 운동이 우리의 건강에 도움이된다고 말합니다.)
## A tells us [to] sth (A는 sth[교훈/핵심 메시지]를 알려줍니다. ) 교훈/핵심 메시지
> The video tells us to start exercising regularly. (비디오는 우리에게 규칙적으로 운동을 시작하라고 알려줍니다.)
> The video tells us the benefits of a regular exercising habit. (비디오는 규칙적인 운동 습관의 이점을 알려줍니다.)
## A talks about sth ([주제 키워드]에 대한 이야기 ) 주제 키워드
> The video talks about the benefits of a regular exercising habit. (동영상은 규칙적인 운동 습관의 이점에 대해 설명합니다.)
## Grammar Error:
```
Tomorrow, I have a schedule for the coding test. Nervous. (So, I’m very nervous about it.) → I am nervous about tomorrow’s coding test.
'A회사' conducts the tests. → The test is conducted by 'A회사'.
The video says starting exercising regularly.
→ The video says exercising regularly is helpful for our health. → 주제 요약 (정보)
→ The video tells us to start exercising regularly. → 교훈/핵심 메시지
→ The video tells us the benefits of a regular exercising habit.
→ The video talks about the benefits of a regular exercising habit. → 주제 키워드
```
## New expressions learned today:
```conduct 실시하다 (Who is conducting the test?)
recruitment 채용, 모집
official (formal) vs. informal
say vs. tell
talk → talk to someone / have a conversation/talk with someone.
We need to have some conversation.
Go talk to him.
The way he talked seemed a bit weird.
He said he would come. / Did you tell him the time correctly?
I don’t remember what I said. / I think I told him the wrong date.
He said “I will go there for sure.” → He said (that) he would come for sure.
Did you tell him the news? / Did you talk to him about that?
I told you to clean up the mess. / I told you about the party, right?
She told me to come to the party. / She told me about the party.
He didn’t tell me he couldn’t make it.
tell someone to (Verb) → ~하라고 이야기하다 (명령/지시)
I told you to do clean up / I told you to bathe
I told you to clean the bathroom.
tell someone about (sth; Noun) / tell someone (절) → ~에 대해 이야기하다 (정보 전달)
He told me about coding test is tough.
→ He told me (that) the coding test is tough.
→ He told me about the difficulty of the coding test.
→ He told me about [how difficult the coding test is].
easy vs difficult
I can get to the 양재천 how.
How can I go to the 양재천 → How can I get to the 양재천?
→ Do you know [how I can get to the 양재천]? / Could you tell me how I can get to the 양재천?
Could you tell me how get to difficulty? → How difficult is the coding test?
The coding test is difficult. → Is the coding test difficult?
The coding test is (how) difficult. / The coding test is very difficult. / The coding test is not that difficult.
How beautiful is(was) the waterfall?
He told me how difficult is the coding test.
Can you make it?
```
본 게시물은 개인 복습용이라 수업내용과 별개 입니다.
예시로 만든 문장은 문법적 오류가 있을 수 있습니다.
잘못된 점이 있다면 댓글로 남겨주시면 수정하겠습니다.
## end | 35.288462 | 135 | 0.707357 | eng_Latn | 0.771542 |
613ba98123e22019ddc0d0ca0d13f2c67ba98f16 | 6,840 | md | Markdown | packages/@romejs/js-compiler/transforms/lint/noEmptyCharacterClass.test.md | asmockler/rome | a66dca36f18bdfe02f9391db2c070aa526b4e2d2 | [
"MIT"
] | null | null | null | packages/@romejs/js-compiler/transforms/lint/noEmptyCharacterClass.test.md | asmockler/rome | a66dca36f18bdfe02f9391db2c070aa526b4e2d2 | [
"MIT"
] | null | null | null | packages/@romejs/js-compiler/transforms/lint/noEmptyCharacterClass.test.md | asmockler/rome | a66dca36f18bdfe02f9391db2c070aa526b4e2d2 | [
"MIT"
] | null | null | null | # `noEmptyCharacterClass.test.ts`
**DO NOT MODIFY**. This file has been autogenerated. Run `rome test packages/@romejs/js-compiler/transforms/lint/noEmptyCharacterClass.test.ts --update-snapshots` to update.
## `format disabled in project config should not regenerate the file`
```
✔ No known problems!
```
## `format enabled in project config should result in regenerated file`
```javascript
Object {
diagnostics: Array []
src: 'foobar(\'yes\');\n'
suppressions: Array []
}
```
## `no empty character class in regular expression`
### `0`
```
✔ No known problems!
```
### `1`
```
✔ No known problems!
```
### `10`
```
✔ No known problems!
```
### `11`
```
✔ No known problems!
```
### `12`
```
unknown:1:15 lint/noEmptyCharacterClass FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Empty character classes in regular expressions are not allowed
let foo = /^abc[]/;foo;
^
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Found 1 problem
```
### `13`
```
unknown:1:14 lint/noEmptyCharacterClass FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Empty character classes in regular expressions are not allowed
let foo = /foo[]bar/;foo;
^^
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Found 1 problem
```
### `14`
```
unknown:1:32 lint/noEmptyCharacterClass FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Empty character classes in regular expressions are not allowed
let foo = "";if (foo.match(/^abc[]/)) { foo; }
^
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Found 1 problem
```
### `15`
```
unknown:1:11 lint/noEmptyCharacterClass FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Empty character classes in regular expressions are not allowed
let foo = /[]]/;foo;
^^
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Found 1 problem
```
### `16`
```
unknown:1:13 lint/noEmptyCharacterClass FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Empty character classes in regular expressions are not allowed
let foo = /\[[]/;foo;
^
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Found 1 problem
```
### `17`
```
unknown:1:20 lint/noEmptyCharacterClass FIXABLE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Empty character classes in regular expressions are not allowed
let foo = /\[\[\]a-z[]/;foo;
^
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✖ Found 1 problem
```
### `2`
```
✔ No known problems!
```
### `3`
```
✔ No known problems!
```
### `4`
```
✔ No known problems!
```
### `5`
```
✔ No known problems!
```
### `6`
```
✔ No known problems!
```
### `7`
```
✔ No known problems!
```
### `8`
```
✔ No known problems!
```
### `9`
```
✔ No known problems!
```
| 32.727273 | 400 | 0.194737 | yue_Hant | 0.999795 |
613bb185c88b7e0328e17e82cc2a13a13072b6e9 | 6,182 | md | Markdown | enhavo/tradukenda/README.md | Donesra/kurso-zagreba-metodo | 7325745c87b1cbe6162a835886265be1ec3a5e25 | [
"CC-BY-4.0"
] | 124 | 2016-03-22T16:53:28.000Z | 2022-03-10T15:10:10.000Z | enhavo/tradukenda/README.md | Donesra/kurso-zagreba-metodo | 7325745c87b1cbe6162a835886265be1ec3a5e25 | [
"CC-BY-4.0"
] | 55 | 2016-02-01T19:47:49.000Z | 2022-02-23T00:00:15.000Z | enhavo/tradukenda/README.md | Donesra/kurso-zagreba-metodo | 7325745c87b1cbe6162a835886265be1ec3a5e25 | [
"CC-BY-4.0"
] | 55 | 2016-02-16T19:18:49.000Z | 2021-07-04T22:33:33.000Z | # Kiel traduki al nova lingvo
Saluton! Unue dankegon, ke vi volas traduki tiun ĉi kurson! Kiel fari tion:
## Kreu konton ĉe Github
1. Bonvole iru al https://github.com/join kaj kreu (senpagan) personan konton.
2. Sendu vian uzantnomon al georg@jaehnig.org kaj skribu ankaŭ:
- al kiu lingvo vi volas traduki
- kiun jam ekzistantan, similan lingvon vi volas havi kiel ĝermo. (Normale, oni elektas la anglan. Sed se vi ekzemple volas traduki al la indonezia, indus elekti la similan malajan.)
3. Atendu mian respondon. :)
## Akceptu la inviton al la teamo
Kiam mi legis vian mesaĝon, mi invitas vin al la Esperanta teamo ĉe Github. Mi skribas al vi, kiam mi faris tion. Por akcepti la inviton
1. iru al https://github.com/Esperanto kaj klaku al "View invitation".
2. En la sekva paĝo, klaku al "Join Esperanto".
## Kontrolu ĉu traduko al via lingvo jam ekzistas
La [Zagreba metodo](https://eo.wikipedia.org/wiki/Zagreba_metodo) estas jam tradukita al multe da lingvoj, tial plej bonus se vi ne mem tradukas al via lingvo sed trovas tradukaĵon al tiu lingvo.
La tradukaĵoj ĝis nun nur eldonitas en libra formo. Kelkaj skanaĵoj troviĝas:
- en la dosierujo [materialo](materialo)
- en aliaj retpaĝoj:
- [angla](http://esperantofre.com/zagreb/zagreba.htm)
- [bulgara](https://drive.google.com/open?id=0B73-tppgbUreWE9Pakk3X3YtajA)
- [finna](https://drive.google.com/open?id=0B73-tppgbUreUmhjOXhfRjROTms)
- [hispana](http://esperantofre.com/zagreb/zagrebh.htm)
- [itala](https://drive.google.com/open?id=0B73-tppgbUreZ3dxUVB5QWFTMGs)
- [korea](https://drive.google.com/open?id=0B73-tppgbUreRGVKUXJqSzUwaVU), [alia versio](https://drive.google.com/open?id=0B73-tppgbUreQ3hOOG50WGFPQTQ)
- [kroata](https://drive.google.com/open?id=0B73-tppgbUrecVZxc21TQ2syUzQ)
- [makedona (nekompleta)](https://drive.google.com/open?id=0B73-tppgbUreZVRhTUVQWjMtYlU)
- [pola](https://drive.google.com/open?id=0B73-tppgbUreU2tGMEFWR0pCblU)
- [rumana](https://drive.google.com/open?id=0B73-tppgbUreN19waV84ZnFwd0E)
- [slovaka](https://drive.google.com/open?id=0B73-tppgbUreTGdWT19JQ09jamM)
- [vjetnama](https://drive.google.com/open?id=0B73-tppgbUreYjBObFBhcHZROTg)
(Se vi havas pli da skanaĵojn, bonvole aldonu ilin aŭ [informu min](mailto:georg@jaehnig.org)!)
## Tradukado
Nun ek al la tradukado!
### Ĝenerale: kiel redakti
1. Bonvole iru al la dosierujo kiun mi kreis por la nova lingvo. (Mi sendis la ligilon en mia retpoŝto al vi.)
2. Eniru la dosierujon kaj malfermu dosieron kiun vi volas traduki (simple klaku al ĝi).
3. Redaktu la dosierojn: Klaku al la redaktu-butono:
### Ekzercoj
Plej bonas komenci kun la ekzercoj:
#### Ekzerco 1
1. Iru al `/ekzercoj/traduku` kaj malfermu `01.yml`. Nun vi vidas la fontdosieron de la [unua ekzerco](http://learn.esperanto.com/en/01/ekzerco1/)
2. Traduku nun la Esperantajn vortojn al la nova lingvo:
- Forigu la anglajn vortojn
- en ilia loko, entajpu la vortojn de la nova lingvo
Se via nova lingvo havas nur 1 tradukaĵon, skribu unu linion, ekzemple:
- enskribi: to register
Se via nova lingvo havas pli ol 1 tradukaĵon, skribu pli da linioj, ekzemple:
- enskribi:
- to register
- to inscribe
Finfine, klaku al "Commit changes" sube por konservi viajn ŝanĝojn.
Same, traduku la aliajn dosierojn en `/ekzercoj/traduku`. Bonas se vi ĉiam skribas multajn eblajn tradukaĵojn per vorto. Tiel ĉiuj eblaj respondoj de la estontaj lernantoj ĝustos.
#### Vortaro
Same, traduku ĉiujn dosierojn en `/vortaro`.
#### Ekzerco 3
En `/ekzercoj/traduku-kaj-respondu`, ni tradukas la [trian ekzercon](http://learn.esperanto.com/en/01/ekzerco3/). Por ĉiu traduko, vi vidas 2 linojn:
demando:
rektatraduko:
En la linio `demando:`, skribu bonsonan frazon en via lingvo, ekzemple:
demando: Does friendship make you more happy than love does?
En la linio `rektatraduko:`, skribu laŭvortan tradukon en via lingvo. Ĝi ne devas esti bonsona aŭ eĉ gramatike ĝusta. Ĝi nur celas informi la lernanton kiujn Esperantajn vortojn li aŭ ŝi uzu. Ekzemple:
rektatraduko:
- Ĉu: Whether
- amikeco: friendship
- pli: more
- feliĉigas: makes happy
- vin: you
- ol: than
- la: the
- amo: love
- '?'
Tre bonas uzi la samajn vortojn kiel en viaj tradukoj en `/vortaro`. Sed rimarku ke tie oni bezonas __nur unu__ tradukaĵon per vorto.
Se via lingvo tute ne havas laŭvortan tradukon de kelkaj Esperantaj vortoj, skribu ian klarigon. Ekzemple, se la angla ne havus la vorton "the", oni povus skribi
- la: (definite article)
Denove: La celo estas ke la lernanto sciu kion li aŭ ŝi skribu.
#### Se iu traduko ne aperas
Foje vi devas uzi citilojn, ekzemple jen:
vorto: "on"
Ĉar `on` estas angla vorto, la dosierformato ne komprenas ĝin kiel ĉeno (string), sed kiel buleo (boolean) kaj pensas ke signifas `TRUE`. Tial vi devas uzi citilojn: `"on"`.
Alia ekzemplo:
vorto: "apostrophe's translation"
Se vi uzas apostrofon en la tradukaĵo, uzu citilojn ĉirkaŭe.
### Gramatiko
La gramatikaj klarigoj estas en la dosierujo `/gramatiko`. Ili skribitas en [Markdown](https://en.wikipedia.org/wiki/Markdown).
Ĉi tie vi estas tute libera pri la enhavo: Vi povas aldoni ekzemplojn kaj klarigojn kiom vi volas. Eble la parolantojn de via nova lingvo bezonas aliajn klarigojn ol tiujn kiuj jam ekzistas en la ĝerma lingvo. Adaptu ilin laŭ via gusto.
- Por ĉiu leciono, kreu dosieron laŭ la leciona indekso. Ekzemple:
- `01.md` - Klarigo pri leciono 1
- `02.md` - Klarigo pri leciono 2
- ktp.
- Skribu ĉion Esperanton uzante `*`, ekzemple
- `*bona lingvo*`
- Disigu Esperanto kaj la tradukon per `–` (dash), ne per `-`. Ekzemple:
- `*bona lingvo* – good language`
- Skribu vortojn aŭ literojn pri kiuj vi nun klarigas uzante `__`. Ekzemple:
- `The morpheme *-ej* denotes a place, for example *lern__ej__o* – school`
- se vi dubas, rigardu la [germanan version](de/)
Ne timu se Github kelkfoje malĝuste transigas partojn de Markdown (ekz. kombinadojn kiel `*lern__ej__o*`), montrante la Markdown-dosierojn en sia retejo. Tio nur estas problemo de Github, nia kreanta skripto tamen bone tradukos ilin.
| 41.77027 | 236 | 0.740052 | epo_Latn | 0.999971 |
613bb7eb4aee8d9710423b791f491249ddbda46d | 813 | md | Markdown | mkv.md | ppo/gist | ab036a8018644e1a72603ab3a34760f649690195 | [
"MIT"
] | 1 | 2020-05-01T18:19:25.000Z | 2020-05-01T18:19:25.000Z | mkv.md | ppo/gist | ab036a8018644e1a72603ab3a34760f649690195 | [
"MIT"
] | null | null | null | mkv.md | ppo/gist | ab036a8018644e1a72603ab3a34760f649690195 | [
"MIT"
] | null | null | null | # mkv
> 👋Errors, improvements or other cool stuff? Let me know! 😀
[MKVToolNix](https://mkvtoolnix.download/) – Matroska tools for Linux/Unix and Windows
### View info about a file
```bash
mkvinfo <filename.mkv>
```
### Modify default audio & subtitle tracks
_The track identifier is not the track number but (a|s) and its index starting from 1._
```bash
mkvpropedit <filename.mkv> \
--edit track:a1 --set flag-default=0 \ # Disable first audio track (a1).
--edit track:a2 --set flag-default=1 \ # Enable second audio track (a2).
--edit track:s1 --set flag-default=0 # Disable first subtitles (s1).
```
### Extract subtitles
_Use `mkvinfo` to retrieve `track_number` (use the value specified for mkvextract)._
```bash
mkvextract tracks <filename.mkv> <track_number>:<subtitles.srt>
```
| 23.911765 | 87 | 0.701107 | eng_Latn | 0.908904 |
613d4ca8863a472e779366c6d323873c0385866f | 6,218 | md | Markdown | README.md | narwhal-chat/narwhal | ea8a468e7fbd21308e7ad302909c1d2d29bb0269 | [
"MIT"
] | 3 | 2018-04-06T01:09:00.000Z | 2018-04-25T23:55:34.000Z | README.md | narwhal-chat/narwhal | ea8a468e7fbd21308e7ad302909c1d2d29bb0269 | [
"MIT"
] | null | null | null | README.md | narwhal-chat/narwhal | ea8a468e7fbd21308e7ad302909c1d2d29bb0269 | [
"MIT"
] | 3 | 2018-02-20T12:57:18.000Z | 2018-06-11T05:59:49.000Z | # narwhal
narwhal is an open-source project aimed at providing a responsive, real-time chat app with a strong focus on open communities. Imagine Slack but with an easy way to discover new communities built right into the app!
## Table of Contents
1. [Team](#team)
1. [Current Feature Set](#current-feature-set)
1. [Demo](#demo)
1. [Under the Hood](#under-the-hood)
1. [Development](#development)
1. [Getting Started](#getting-started)
1. [Contributing](#contributing)
## Team
- [Sam Lee](https://github.com/sleex89)
- [Rory Well](https://github.com/roryewell)
- [Jonathan Weinstein](https://github.com/JonathanWeinstein)
## Current Feature Set
- Log in and register a new account
- Edit user profile
- Find new communities on the Discover page
- Create and join pods (communities)
- Create and join topics (channels)
- Real-time group chat for each topic
- Upload custom pod and user avatars
- Message searching
## Demo
#### Login
#### Discover
#### Chat
## Under the Hood
narwhal is a Node.js application built with Express and React. We take pride in our modern tech stack. Here's a brief list of other technologies we've implemented in our app:
- Redux
- Redux-Saga
- Socket.IO
- CSS Grid / Flexbox
- Postgres
- Postgres Full Text Search
## Development
### Getting Started
#### Main narwhal Repo
Clone the main narwhal repo and cd to the new directory.
```sh
npm install
cd client
npm install
```
To start the Node.js server, open up another terminal and run the following command from the root folder of the directory:
```sh
nodemon
```
Start the React development server by first going to the root folder of the directory and then running the following commands:
```sh
cd client
npm start
```
#### Databases
narhwal uses Postgres as the main back-end database. All databases must be created before using the application. Below is a list of scripts to create the databases and their tables.
##### narwhal_users
```sql
-- Table: users
CREATE TABLE users (
id serial NOT NULL,
username varchar(20) NOT NULL,
password varchar(100) NOT NULL,
email_address varchar(320) NOT NULL,
avatar varchar(500) NOT NULL,
create_date timestamp NOT NULL DEFAULT now(),
CONSTRAINT user_ak_email_address UNIQUE (email_address) NOT DEFERRABLE INITIALLY IMMEDIATE,
CONSTRAINT user_ak_username UNIQUE (username) NOT DEFERRABLE INITIALLY IMMEDIATE,
CONSTRAINT users_pk PRIMARY KEY (id)
);
```
##### narwhal_pods
```sql
-- Table: pod_user
CREATE TABLE pod_user (
id serial NOT NULL,
pod_id int NOT NULL,
user_id int NOT NULL,
is_admin boolean NOT NULL,
join_date timestamp NOT NULL DEFAULT now(),
CONSTRAINT pod_user_ak_pod_id_user_id UNIQUE (pod_id, user_id) NOT DEFERRABLE INITIALLY IMMEDIATE,
CONSTRAINT pod_user_pk PRIMARY KEY (id)
);
-- Table: pod_category
CREATE TABLE pod_category (
id serial NOT NULL,
name varchar(50) NOT NULL,
default_category_avatar varchar(500) NOT NULL,
CONSTRAINT pod_category_ak_name UNIQUE (name) NOT DEFERRABLE INITIALLY IMMEDIATE,
CONSTRAINT pod_category_pk PRIMARY KEY (id)
);
-- Table: pod
CREATE TABLE pod (
id serial NOT NULL,
reference_name varchar(25) NOT NULL,
display_name varchar(25) NOT NULL,
description varchar(100) NOT NULL,
avatar varchar(500) NOT NULL,
pod_category_id int NOT NULL,
author_id int NOT NULL,
create_date timestamp NOT NULL DEFAULT now(),
is_deleted boolean NOT NULL DEFAULT false,
delete_date timestamp NULL,
CONSTRAINT pod_ak_reference_name UNIQUE (reference_name) NOT DEFERRABLE INITIALLY IMMEDIATE,
CONSTRAINT pod_pk PRIMARY KEY (id)
);
-- Table: topic
CREATE TABLE topic (
id serial NOT NULL,
name varchar(20) NOT NULL,
pod_id int NOT NULL,
author_id int NOT NULL,
create_date timestamp NOT NULL DEFAULT now(),
is_deleted boolean NOT NULL DEFAULT false,
delete_date timestamp NULL,
CONSTRAINT topic_pk PRIMARY KEY (id)
);
-- Foreign keys
-- Reference: pod_category_id (table: pod)
ALTER TABLE pod ADD CONSTRAINT pod_category_id
FOREIGN KEY (pod_category_id)
REFERENCES pod_category (id)
NOT DEFERRABLE
INITIALLY IMMEDIATE
;
-- Reference: pod_user_pod (table: pod_user)
ALTER TABLE pod_user ADD CONSTRAINT pod_user_pod
FOREIGN KEY (pod_id)
REFERENCES pod (id)
NOT DEFERRABLE
INITIALLY IMMEDIATE
;
-- Reference: topic_pod_id (table: topic)
ALTER TABLE topic ADD CONSTRAINT topic_pod_id
FOREIGN KEY (pod_id)
REFERENCES pod (id)
NOT DEFERRABLE
INITIALLY IMMEDIATE
;
```
##### narwhal_messages
```sql
-- Table: topic_message
CREATE TABLE topic_message (
id serial NOT NULL,
message_text varchar(500) NOT NULL,
message_text_tokens tsvector NOT NULL,
topic_id int NOT NULL,
author_id int NOT NULL,
create_date timestamp NOT NULL DEFAULT now(),
is_deleted boolean NOT NULL DEFAULT false,
delete_date timestamp NULL,
last_update_date timestamp NOT NULL DEFAULT now(),
CONSTRAINT topic_message_pk PRIMARY KEY (id)
);
```
#### Microservices
Clone each of the microservice repos.
- [User microservice](https://github.com/narwhal-chat/narwhal-user-microservice)
- [Pod microservice](https://github.com/narwhal-chat/narwhal-pod-microservice)
- [Message microservice](https://github.com/narwhal-chat/narwhal-message-microservice)
- [Message search microservice](https://github.com/narwhal-chat/narwhal-message-search-microservice)
Install the dependencies for each of the cloned microservice directories.
```sh
npm install
```
To start a microservice, navigate to the root folder of the directory and run the following command:
```sh
nodemon
```
## Contributing
Want to help make narwhal an amazing product? Review the [Development](#development) guide and start submitting pull requests ^_^
| 28.263636 | 215 | 0.738019 | kor_Hang | 0.33777 |
613d4f451ef6a49e0f467481970b41cee2c567f0 | 93 | md | Markdown | README.md | ibahri/blockchain_demo | 845b7490930de11a5c7ede3d120c9d8e187ef0be | [
"Apache-2.0"
] | null | null | null | README.md | ibahri/blockchain_demo | 845b7490930de11a5c7ede3d120c9d8e187ef0be | [
"Apache-2.0"
] | null | null | null | README.md | ibahri/blockchain_demo | 845b7490930de11a5c7ede3d120c9d8e187ef0be | [
"Apache-2.0"
] | null | null | null | Hello , This a app is for leaning purpose in order to understand blockchain and its mechanism | 93 | 93 | 0.817204 | eng_Latn | 0.999977 |
613e396a8dba2f7bdfd379b6e4eb9a10b67299dd | 808 | md | Markdown | README.md | janis-rullis/dev | 371555d6b4cef0e57167aca0b4e38b026e93bf06 | [
"MIT"
] | 5 | 2018-07-06T14:23:25.000Z | 2019-10-05T15:54:35.000Z | README.md | Janis-Rullis-IT/dev | 14c4f85ab8ac2aa4874a4c2b7ace07f058e51e33 | [
"MIT"
] | 5 | 2020-04-14T09:06:13.000Z | 2021-09-01T08:35:20.000Z | README.md | Janis-Rullis-IT/dev | 14c4f85ab8ac2aa4874a4c2b7ace07f058e51e33 | [
"MIT"
] | null | null | null | # DEV - Notes related with development
* How to organize a project ([Management-Organization](Management-Organization))
* design a code ([Infrastructure/Software](Infrastructure/Software), [Coding](Coding))
* and deliver it using the hardware ([Infrastructure/Hardware](Infrastructure/Hardware)).
## See also
* https://github.com/Janis-Rullis-IT/pc-server
* https://github.com/Janis-Rullis-IT/shell-scripts
* https://github.com/Janis-Rullis-IT/sql
## Good reads
- https://www.tomasvotruba.com/
- https://tsh.io/blog/
- https://www.thinktocode.com/
- https://hackernoon.com/
- https://dzone.com/
- https://dev.to/
- https://www.journaldev.com/31902/gangs-of-four-gof-design-patterns
- https://designpatternsphp.readthedocs.io/en/latest/README.html
- https://refactoring.guru/design-patterns/catalog
| 33.666667 | 89 | 0.74505 | yue_Hant | 0.648152 |
613f7bcf99a1eac20af6aafcea38ed3e45ec06ae | 594 | md | Markdown | README.md | alpersonalwebsite/basic-vue-sibling | 5b3a258f5e8b25cd6b82a41002becee551bae8fd | [
"MIT"
] | null | null | null | README.md | alpersonalwebsite/basic-vue-sibling | 5b3a258f5e8b25cd6b82a41002becee551bae8fd | [
"MIT"
] | 46 | 2019-11-23T01:51:05.000Z | 2022-03-21T02:14:08.000Z | README.md | alpersonalwebsite/basic-vue-sibling | 5b3a258f5e8b25cd6b82a41002becee551bae8fd | [
"MIT"
] | null | null | null | # Vue.js: EventBus and communication between sibling components
[](https://greenkeeper.io/)
[](https://opensource.org/licenses/MIT)
## Project setup
```
npm install
```
### Compiles and hot-reloads for development
```
npm serve
```
### Compiles and minifies for production
```
npm build
```
### Lints and fixes files
```
npm lint
```
### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).
| 21.214286 | 118 | 0.723906 | eng_Latn | 0.434102 |
bcf1fb21e47cff674bba9f9a22046a302ef3b440 | 7,763 | md | Markdown | curriculum/challenges/spanish/02-javascript-algorithms-and-data-structures/basic-data-structures/create-complex-multi-dimensional-arrays.spanish.md | tmonks/freeCodeCamp | 7453131461f5073d9160bbc1402bcb0e052579c0 | [
"BSD-3-Clause"
] | 25 | 2020-02-16T00:26:35.000Z | 2022-03-30T19:46:05.000Z | curriculum/challenges/spanish/02-javascript-algorithms-and-data-structures/basic-data-structures/create-complex-multi-dimensional-arrays.spanish.md | SweeneyNew/freeCodeCamp | e24b995d3d6a2829701de7ac2225d72f3a954b40 | [
"BSD-3-Clause"
] | 2,056 | 2019-08-25T19:29:20.000Z | 2022-02-13T22:13:01.000Z | curriculum/challenges/spanish/02-javascript-algorithms-and-data-structures/basic-data-structures/create-complex-multi-dimensional-arrays.spanish.md | SweeneyNew/freeCodeCamp | e24b995d3d6a2829701de7ac2225d72f3a954b40 | [
"BSD-3-Clause"
] | 27 | 2017-02-12T11:48:34.000Z | 2022-03-30T17:44:39.000Z | ---
id: 587d7b7b367417b2b2512b16
title: Create complex multi-dimensional arrays
challengeType: 1
videoUrl: ''
localeTitle: Crear complejos arreglos multidimensionales.
---
## Description
<section id="description"> ¡Increíble! ¡Acabas de aprender un montón de arreglos! Este ha sido un resumen de nivel bastante alto, y hay mucho más que aprender sobre el trabajo con matrices, muchas de las cuales veremos en secciones posteriores. Pero antes de pasar a mirar <dfn>Objetos</dfn> , echemos un vistazo más y veamos cómo los arreglos pueden volverse un poco más complejos de lo que hemos visto en desafíos anteriores. Una de las características más poderosas cuando se piensa en los arreglos como estructuras de datos, es que los arreglos pueden contener, o incluso estar completamente compuestos de otros arreglos. Hemos visto matrices que contienen matrices en desafíos anteriores, pero bastante simples. Sin embargo, las matrices pueden contener una profundidad infinita de matrices que pueden contener otras matrices, cada una con sus propios niveles arbitrarios de profundidad, y así sucesivamente. De esta manera, una matriz puede convertirse muy rápidamente en una estructura de datos muy compleja, conocida como una matriz <dfn>multidimensional</dfn> o anidada. Considere el siguiente ejemplo: <blockquote> Deje nestedArray = [// top, o primer nivel: la matriz más externa <br> ['deep'], // una matriz dentro de una matriz, 2 niveles de profundidad <br> El <br> ['deep'], ['deep'] // 2 arreglos anidados 3 niveles de profundidad <br> ] <br> El <br> El <br> ['deepest'], ['deepest'] // 2 arrays anidados 4 niveles de profundidad <br> ] <br> El <br> El <br> ['deepest-est?'] // una matriz anidada 5 niveles de profundidad <br> ] <br> ] <br> ] <br> ]; </blockquote> Si bien este ejemplo puede parecer complicado, este nivel de complejidad no es inaudito, o incluso inusual, cuando se trata de grandes cantidades de datos. Sin embargo, aún podemos acceder fácilmente a los niveles más profundos de una matriz de este complejo con notación de corchetes: <blockquote> console.log (nestedArray [2] [1] [0] [0] [0]); <br> // logs: deepest-est? </blockquote> Y ahora que sabemos dónde se encuentra ese dato, podemos restablecerlo si necesitamos: <blockquote> nestedArray [2] [1] [0] [0] [0] = 'deep still still'; <br><br> console.log (nestedArray [2] [1] [0] [0] [0]); <br> // ahora registra: aún más profundo </blockquote></section>
## Instructions
<section id="instructions"> Hemos definido una variable, <code>myNestedArray</code> , igual a una matriz. Modifique <code>myNestedArray</code> , utilizando cualquier combinación de <dfn>cadenas</dfn> , <dfn>números</dfn> y <dfn>valores booleanos</dfn> para los elementos de datos, de modo que tenga exactamente cinco niveles de profundidad (recuerde, la matriz más externa es el nivel 1). En algún lugar en el tercer nivel, incluye la cadena <code>'deep'</code> , en el cuarto nivel, incluyen la cadena <code>'deeper'</code> , y en el quinto nivel, incluyen la cadena <code>'deepest'</code> . </section>
## Tests
<section id='tests'>
```yml
tests:
- text: '<code>myNestedArray</code> debe contener solo números, booleanos y cadenas como elementos de datos'
testString: 'assert.strictEqual((function(arr) { let flattened = (function flatten(arr) { const flat = [].concat(...arr); return flat.some (Array.isArray) ? flatten(flat) : flat; })(arr); for (let i = 0; i < flattened.length; i++) { if ( typeof flattened[i] !== "number" && typeof flattened[i] !== "string" && typeof flattened[i] !== "boolean") { return false } } return true })(myNestedArray), true, "<code>myNestedArray</code> should contain only numbers, booleans, and strings as data elements");'
- text: <code>myNestedArray</code> debe tener exactamente 5 niveles de profundidad
testString: 'assert.strictEqual((function(arr) {let depth = 0;function arrayDepth(array, i, d) { if (Array.isArray(array[i])) { arrayDepth(array[i], 0, d + 1);} else { depth = (d > depth) ? d : depth;}if (i < array.length) { arrayDepth(array, i + 1, d);} }arrayDepth(arr, 0, 0);return depth;})(myNestedArray), 4, "<code>myNestedArray</code> should have exactly 5 levels of depth");'
- text: <code>myNestedArray</code> debe contener exactamente una aparición de la cadena <code>"deep"</code> en una matriz anidada con 3 niveles de profundidad
testString: 'assert((function howDeep(array, target, depth = 0) {return array.reduce((combined, current) => {if (Array.isArray(current)) { return combined.concat(howDeep(current, target, depth + 1));} else if (current === target) { return combined.concat(depth);} else { return combined;}}, []);})(myNestedArray, "deep").length === 1 && (function howDeep(array, target, depth = 0) {return array.reduce((combined, current) => {if (Array.isArray(current)) { return combined.concat(howDeep(current, target, depth + 1));} else if (current === target) { return combined.concat(depth);} else { return combined;}}, []);})(myNestedArray, "deep")[0] === 2, "<code>myNestedArray</code> should contain exactly one occurrence of the string <code>"deep"</code> on an array nested 3 levels deep");'
- text: <code>myNestedArray</code> debe contener exactamente una aparición de la cadena <code>"deeper"</code> deep <code>"deeper"</code> en una matriz anidada con 4 niveles de profundidad
testString: 'assert((function howDeep(array, target, depth = 0) {return array.reduce((combined, current) => {if (Array.isArray(current)) { return combined.concat(howDeep(current, target, depth + 1));} else if (current === target) { return combined.concat(depth);} else { return combined;}}, []);})(myNestedArray, "deeper").length === 1 && (function howDeep(array, target, depth = 0) {return array.reduce((combined, current) => {if (Array.isArray(current)) { return combined.concat(howDeep(current, target, depth + 1));} else if (current === target) { return combined.concat(depth);} else { return combined;}}, []);})(myNestedArray, "deeper")[0] === 3, "<code>myNestedArray</code> should contain exactly one occurrence of the string <code>"deeper"</code> on an array nested 4 levels deep");'
- text: <code>myNestedArray</code> debe contener exactamente una aparición de la cadena <code>"deepest"</code> en una matriz anidada con 5 niveles de profundidad
testString: 'assert((function howDeep(array, target, depth = 0) {return array.reduce((combined, current) => {if (Array.isArray(current)) { return combined.concat(howDeep(current, target, depth + 1));} else if (current === target) { return combined.concat(depth);} else { return combined;}}, []);})(myNestedArray, "deepest").length === 1 && (function howDeep(array, target, depth = 0) {return array.reduce((combined, current) => {if (Array.isArray(current)) { return combined.concat(howDeep(current, target, depth + 1));} else if (current === target) { return combined.concat(depth);} else { return combined;}}, []);})(myNestedArray, "deepest")[0] === 4, "<code>myNestedArray</code> should contain exactly one occurrence of the string <code>"deepest"</code> on an array nested 5 levels deep");'
```
</section>
## Challenge Seed
<section id='challengeSeed'>
<div id='js-seed'>
```js
let myNestedArray = [
// change code below this line
['unshift', false, 1, 2, 3, 'complex', 'nested'],
['loop', 'shift', 6, 7, 1000, 'method'],
['concat', false, true, 'spread', 'array'],
['mutate', 1327.98, 'splice', 'slice', 'push'],
['iterate', 1.3849, 7, '8.4876', 'arbitrary', 'depth']
// change code above this line
];
```
</div>
</section>
## Solution
<section id='solution'>
```js
// solution required
```
</section>
| 117.621212 | 2,298 | 0.711194 | spa_Latn | 0.670892 |
bcf22ac2331e2dfc6b394c5cf9f7fc1173082f84 | 2,194 | md | Markdown | glosalist/559_raw.md | fiasinstitute/glosa | 541c7b892226d21043f06f86322f7ec52ee294d1 | [
"MIT"
] | 3 | 2020-10-27T22:49:36.000Z | 2022-02-20T17:15:55.000Z | glosalist/559_raw.md | fiasinstitute/glosa | 541c7b892226d21043f06f86322f7ec52ee294d1 | [
"MIT"
] | null | null | null | glosalist/559_raw.md | fiasinstitute/glosa | 541c7b892226d21043f06f86322f7ec52ee294d1 | [
"MIT"
] | null | null | null | ---
authorName: Konstantin Aleksandrov
canDelete: false
contentTrasformed: false
from: Konstantin Aleksandrov <kaleksandrov@...>
headers.inReplyToHeader: PDQyREMwN0ZELjUwOTAxMDVAaG90cG9wLmNvbT4=
headers.messageIdInHeader: PDQyREM5OEFDLjMwMDA1MDZATUFHUk9VUC5SVT4=
headers.referencesHeader: PEUxRHJSMmotMDAwNnNwLTAwLm4xOTU0LW1haWwtcnVAZjIxLm1haWwucnU+IDw0MkQyMjlFOS42MDkwNDA3QE1BR1JPVVAuUlU+IDwyMDA1MDcxMTEyMjAxNi5HQTMwOTQzQHZpY2VydmV6YT4gPDQyREMwN0ZELjUwOTAxMDVAaG90cG9wLmNvbT4=
layout: email
msgId: 559
msgSnippet: "Ja la problemo estas ke oni ne tre klare povas kompreni. Mi jam skribis\
\ pri tio. Mi \u0109esis lerni Glosan \u011Duste pro tio ke malaperis multaj anglismoj\
\ kiujn"
nextInTime: 560
nextInTopic: 560
numMessagesInTopic: 27
postDate: '1121753260'
prevInTime: 558
prevInTopic: 558
profile: .nan
replyTo: LIST
senderId: xTTKPy7jTZ7djaJ9RHOMTOiHirjtdcwAineN2VTFA5LNi5xnI8anlpF-KHs-BKF5gC5mrkJhpP5uOMJKeGr6f3tm72g-xsTkYyncp_4IAdT_L5wkU_wJ
spamInfo.isSpam: false
spamInfo.reason: '12'
systemMessage: false
title: 'Re: [glosalist] Sound "U" in Glosa'
topicId: 533
userId: 222928034
---
Ja la problemo estas ke oni ne tre klare povas kompreni. Mi jam skribis pri tio.
Mi ĉesis lerni Glosan ĝuste pro tio ke malaperis multaj anglismoj kiujn estis
malfacile traduki. Vere, tre strange aspektas por mi la frazo "La manko de
klaraj gramatikaj reguloj ne estas tro grava problemo". Manko de parolantoj
ŝajne ne estas bona kialo por manko de gramatikaj reguloj :-)
// bv. ne plue provoku paroli en esperanto ĉi tie :-) mi neniam povus rifuzi
tian provokon.
Manuel Pavón Valderrama wrote:
> Mi ne emas kredi ke "forko" estos bona ideo por glosa. Glosa estas sufiche bona
> lingvo nuntempe, kaj la manko de klaraj gramatikaj reguloj ne estas tro grava
> problemo. Se oni povas kompreni, tio sufichas.
>
> Iel ajn nun gramatikreguligi glosan ne taugus, char estas malmultaj parolantoj.
> La gramatikaj regulaj devas aperi kiam la parolantoj multighas kaj la uzo mem de
> la lingvo endigas ghin.
--
When the spiritual intelligence which stands alone and freed from objects,
reflects itself in the mind stuff, then comes awareness of the Self. 183
| 38.491228 | 214 | 0.810392 | epo_Latn | 0.995293 |
bcf250dc34d627a698179d5fdb956b2b1e40ce70 | 1,215 | md | Markdown | README.md | econtarino/appNavbar | 57169a9397c78c4b9c5f3f2c72a6b88f5efd64bd | [
"MIT"
] | null | null | null | README.md | econtarino/appNavbar | 57169a9397c78c4b9c5f3f2c72a6b88f5efd64bd | [
"MIT"
] | null | null | null | README.md | econtarino/appNavbar | 57169a9397c78c4b9c5f3f2c72a6b88f5efd64bd | [
"MIT"
] | null | null | null | # Ezequiel Contarino
## _Ecommerce navbar_
[](https://travis-ci.org/joemccann/dillinger)
Proyecto Ecommerce para mostrar un navbar por material ui,
React & Material UI .
## Consigna
Crea un componente contenedor ItemListContainer.js con una prop greeting, y muestra el mensaje dentro del contenedor con el styling integrado.
Crea un componente ItemListContainer. Impórtalo dentro de App.js, y abajo de NavBar.js
## Tecnología
Herramientas utilizadas
- [ReactJS] - web framework!
- [MaterialUI] - for presentation
- [node.js] - npm commands
## Instalación
Ecommerce navbar requires [Node.js](https://nodejs.org/) v10+ to run.
## License
MIT
[//]: # (These are reference links used in the body of this note and get stripped out when the markdown processor does its job. There is no need to format nicely because it shouldn't be seen. Thanks SO - http://stackoverflow.com/questions/4823468/store-comments-in-markdown-syntax)
[MaterialUI]: <https://material-ui.com/es/>
[node.js]: <http://nodejs.org>
[ReactJS]: <http://reactjs.org>
| 28.928571 | 281 | 0.747325 | kor_Hang | 0.227539 |
bcf41397f69076471440664b19bea0a9c8198102 | 635 | md | Markdown | _talks/2019_DFCM_ResearchProgramEvaluation.md | meaneych/ChrisMeaneyBiostatsPortfolio | 01f111426c2a0c6f6159b2384d5c51355ddd7f8c | [
"MIT"
] | null | null | null | _talks/2019_DFCM_ResearchProgramEvaluation.md | meaneych/ChrisMeaneyBiostatsPortfolio | 01f111426c2a0c6f6159b2384d5c51355ddd7f8c | [
"MIT"
] | null | null | null | _talks/2019_DFCM_ResearchProgramEvaluation.md | meaneych/ChrisMeaneyBiostatsPortfolio | 01f111426c2a0c6f6159b2384d5c51355ddd7f8c | [
"MIT"
] | null | null | null | ---
title: "Using Computational Methods to Mine Indicators of Academic Program Performance"
collection: talks
type: "Talk"
permalink: /talks/2019_DFCM_ResearchProgramEvaluation
venue: "University of Toronto, DFCM"
date: 12-March-2019
location: "Toronto, Canada"
---
This talk illustrates how to mine research program performance indicators using modern computational methods (e.g. Scopus API, PubMed API, web scraping Google Scholar). We are currently extending these methods as part of a larger departmental environmental scan (check back soon for updates).
[Downloaded talk here](../files/2019_DFCM_ResearchProgramEvaluation.pdf)
| 42.333333 | 292 | 0.806299 | eng_Latn | 0.838378 |
bcf4b3eeb435e861196bec1af105c7eb590c6c7d | 244 | md | Markdown | NewTabPage/README.md | mingyaulee/Blazor.BrowserExtension.Samples | 86e17cbd4613969b7064d3a59699e8e98f9b7716 | [
"MIT"
] | 3 | 2021-10-20T03:42:39.000Z | 2022-03-09T20:00:51.000Z | NewTabPage/README.md | mingyaulee/Blazor.BrowserExtension.Samples | 86e17cbd4613969b7064d3a59699e8e98f9b7716 | [
"MIT"
] | null | null | null | NewTabPage/README.md | mingyaulee/Blazor.BrowserExtension.Samples | 86e17cbd4613969b7064d3a59699e8e98f9b7716 | [
"MIT"
] | null | null | null | # New tab page sample
This sample project overrides the default new tab page and uses the bookmarks API.
You can load the output directly in the browser by following the steps [here](../README.md#test-the-sample-projects). | 34.857143 | 117 | 0.762295 | eng_Latn | 0.994512 |
bcf4d4a420852bd0ca231b5c05eb33d031b645df | 1,032 | md | Markdown | README.md | our-wave/escape-button-wordpress | f97e1c6a7dcdfa64f700f1faf22c3c1515b9df7d | [
"MIT"
] | null | null | null | README.md | our-wave/escape-button-wordpress | f97e1c6a7dcdfa64f700f1faf22c3c1515b9df7d | [
"MIT"
] | null | null | null | README.md | our-wave/escape-button-wordpress | f97e1c6a7dcdfa64f700f1faf22c3c1515b9df7d | [
"MIT"
] | null | null | null | # Escape Button WordPress
🔒 Open source widget to help users quickly and discretely leave your website. Developed by the Our Wave engineering team.
## SVN
This project is managed via WordPress SVN.
Check out these resources for more information:
Using Subversion with the WordPress Plugin Directory:
https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/
FAQ about the WordPress Plugin Directory:
https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/
WordPress Plugin Directory readme.txt standard:
https://wordpress.org/plugins/developers/#readme
A readme.txt validator:
https://wordpress.org/plugins/developers/readme-validator/
Plugin Assets (header images, etc):
https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/
WordPress Plugin Directory Guidelines:
https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/
Block Specific Plugin Guidelines:
https://developer.wordpress.org/plugins/wordpress-org/block-specific-plugin-guidelines/ | 36.857143 | 121 | 0.817829 | kor_Hang | 0.42413 |
bcf51fb23f872d362e3f649b731934756bc205e2 | 80 | md | Markdown | README.md | isTravis/tech-archive-search | 2e8b75bf95de94c7d556ea921f8488bf0e6004fa | [
"MIT"
] | null | null | null | README.md | isTravis/tech-archive-search | 2e8b75bf95de94c7d556ea921f8488bf0e6004fa | [
"MIT"
] | null | null | null | README.md | isTravis/tech-archive-search | 2e8b75bf95de94c7d556ea921f8488bf0e6004fa | [
"MIT"
] | null | null | null | # Tech Archive Search
A sample starter site for the tech archive search tool.
| 16 | 55 | 0.775 | eng_Latn | 0.414268 |
bcf5ccd883c285315e1cab0abad860623cf46d9f | 217 | md | Markdown | README.md | miguel-freitas/vale-do-paraiba-site--Bootstrap | b2299252443e960cba981b271ff71e72e148ca9c | [
"MIT"
] | null | null | null | README.md | miguel-freitas/vale-do-paraiba-site--Bootstrap | b2299252443e960cba981b271ff71e72e148ca9c | [
"MIT"
] | null | null | null | README.md | miguel-freitas/vale-do-paraiba-site--Bootstrap | b2299252443e960cba981b271ff71e72e148ca9c | [
"MIT"
] | null | null | null | # vale-do-paraiba-site--Bootstrap
Projeto de site criado para colocar em prática conhecimentos de HTML5 e CSS3 com Bootstrap
Link para visualização: https://miguel-freitas.github.io/vale-do-paraiba-site--Bootstrap/.
| 43.4 | 90 | 0.801843 | por_Latn | 0.997843 |
bcf5da96ce38e114a9d726872f279f7751721a6f | 3,381 | md | Markdown | content/blog/the-path-to-service-mesh/index.md | SataQiu/website-1 | 3c53323602b742f372637e4213d6aa73995e7fb1 | [
"Apache-2.0"
] | null | null | null | content/blog/the-path-to-service-mesh/index.md | SataQiu/website-1 | 3c53323602b742f372637e4213d6aa73995e7fb1 | [
"Apache-2.0"
] | null | null | null | content/blog/the-path-to-service-mesh/index.md | SataQiu/website-1 | 3c53323602b742f372637e4213d6aa73995e7fb1 | [
"Apache-2.0"
] | null | null | null | ---
title: "服务网格之路"
date: 2018-06-04T15:55:08+08:00
draft: false
banner: "/img/blog/banners/00704eQkgy1frz7j5n8mfj30rs0kuhdt.jpg"
author: "Aspen Mesh"
translator: "卢宇亮"
translatorlink: "https://github.com/LJosef"
reviewer: ["宋净超"]
reviewerlink: ["https://jimmysong.io"]
authorlink: "https://aspenmesh.io"
originallink: "https://blog.aspenmesh.io/blog/2018/03/the-path-to-service-mesh/"
summary: "通过 Aspen Mesh 之旅，我们带来三个主题的系列博文来讨论我们为什么选择了 Istio。"
tags: ["service mesh"]
categories: ["translation"]
keywords: ["service mesh","服务网格"]
---
当我们谈论服务网格的时候，有几个问题经常被提及。这些问题的范围覆盖从简单的了解服务网格的历史，到产品和架构相关的比较深入的技术问题。
为了回答这些问题，通过 Aspen Mesh 之旅，我们带来三个主题的系列博文来讨论我们为什么选择了 Istio 。
作为开始，我将重点讨论我最经常被问到的问题之一：
*为什么你选择服务网格，是什么原因促使你这样做？*
#### **LineRate ：高性能负载均衡软件**
这个旅程起源于来自 Boulder 的初创公司 LineRate ，该公司在2013年被 F5 Networks 公司收购。 LineRate 除了是我曾经有幸参与的最聪明、最有才华的工程团队，还是一款轻量级高性能 L7 软件代理。当我说高性能时，我正在谈论的是如何将5年前在数据中心已经存在的服务器，变成一个高性能20+ Gbps 200,000+ HTTP 请求每秒的全功能负载。
虽然性能本身是引入注目的并为我们的客户打开了大门，但是我们的出发点在于客户期望付费的是容量，而不是硬件。这种见解是 LineRate 的核心价值主张。这个简单的概念将使我们的客户能够改变他们在应用之前使用和部署负载均衡的方式。
为了满足这个需求，我们交付了一种产品和商业模式，使我们的客户能够基于 COTS （可在市场上买到的）硬件按需多次复制他们的软件，从而不管部署多少实例都可以获得峰值性能。如果客户需要更多的容量，他们只需要简单的升级其订购层并部署更多的产品副本，直到达到他们许可证允许的带宽，请求速率或者交易速率。
这很有吸引力，我们也取得了一些成就，但是很快我们有了新的想法......
#### 效率优于性能
对于我们而言，应用架构正在发生变化，而客户的价值曲线随之变化的趋势也变得明显。我们在与资深团队沟通的过程中注意到，他们讨论的是诸如效率，敏捷，速度，印迹和横向扩展这类的概念。同时我们也开始听到这些领域的创新者开始采用Docker的新技术，以及它将如何改变应用和服务交付的方式。
我们与这些团队交流的越多，思考我们如何开发自己的内部应用程序，我们就越意识到转变正在发生。团队从根本上改变他们交付应用的方式，结果是我们的客户开始更少的关注原始性能而是更多地关心分布式代理。这些转变还有更多地收益，包含减少应用的故障域，增加部署的灵活性和赋予应用将负载和网络作为配置管理的能力。
与此同时容器和容器编排引擎也开始登上舞台，因此我们开始致力于通过一个新的控制面板以容器的方式交付 LineRate 的产品，并深入的思考人们未来会如何使用这些新技术来交付应用。
这些发生在2015的早期讨论促使我们思考未来应用交付将会如何......
#### 与时俱进的想法
随着我们对于未来应用交付方式的思考，我们开始关注云原声分布式应用领域中有关策略和网络服务的概念。尽管我们仍然有很多不同的优先级项目，改变应用蓝图，云原生应用和基于DevOps交付模式的想法始终在我们思想的最前端。
在这个领域将会有一个新的市场。
我们设计了许多项目，但由于种种原因未能成功。我们亲切的称这些项目为 v1.0 ，v1.5 和 v2.0 。每个项目都有一种解决分布式应用架构（微服务）挑战的独特技术。
我们尽最大可能去思考。下一个应用交付控制架构（ ADC ):一个完全与 API 驱动的控制面板和一个分离的数据面板。数据面板可能来自云你能够设想到的任意一种形式：靠近微服务的专用硬件，商用软件，或者云原生组件（就像服务网格）。这种无限可扩展的架构可以实现优雅的平衡，能够完美的工作于任意规模的任意组织的任意一种工作。很有野心吧？我们陷入了为客户提供所有东西的陷阱。
接下来，我们在“1.5”中完善了我们的方法，我们决定开发一种策略语言...... 关键是要定义开源的策略接口并将它无缝地连接到完成工作的数据路径。在一个真正开放的平台中，其中一些数据路径也是开源的。但是仍然有很多发展中的事情没有一步到位；事后看来，其中一些事情已经到来了...... 市场还没有到来，加上我们在开源方面也没有专业知识，于是我们在描述我们在做什么以及为什么时遇到了麻烦。
但是想法仍然在我们的脑海中燃烧，而我们也没有放弃......
在 2.0 版本，我们设计了一个帮助希望开始容器之旅的 F5 的用户的计划。技术是新的，而市场也刚刚开始走向成熟，我们决定用户将会通过三步开启他们的微服务之旅。
1. *试验* - 在笔记本、服务器或者云主机上通过容器测试应用。
2. *生产规划* - 识别能够帮忙开发人员在生产环境部署容器化应用的技术。
3. *规模经营* - 重点关注容器应用的可观察性，可操作性和安全性，以减少平均停机发现时间 MTTD 和平均故障恢复时间 MTTR。
对于实验性用户我们做不了什么，但是对于生产规划，我们将创造一个开源的连接器，用来连接容器编排环境和 BIG-IP 。我们称之为 BIG-IP Container Connector，我们能够解决现有 F5 客户的问题，并和这些用户讨论下一步工作。BIG-IP ContainerConnector 的团队持续弥合在 ADC 和 快速改变的容器编排环境中的差距。
我们也开始开发一个新的轻量级容器化代理，称之为容器服务代理 （ Application Service Proxy ），或者 ASP 。 与 Linkerd 和 Envoy 类似的是，它被设计来促使微服务间的高效、灵活、可控的通信。与 Linkerd 和 Envoly 不同的是，它并没有开源社区。我们在考虑一种开源策略，同时它对于 ASP 意味着什么。
与此同时，F5 也在发生变化......
#### Aspen Mesh - F5 的创新
在我们开展 ASP 市场计划的同时，F5 通过孵化计划改变了投资新技术和新兴市场的方式。这两个事件与容器的爆炸性增长相结合，导致我们决定承诺在现有的开源服务网格之上构建产品。我们选择 Istio 是因为它具有吸引力的声明式策略语言，可扩展的控制平面架构以及其他我们将在更深入讨论时会涉及的内容。
计划已定，是时候将我们的想法推向我们力所能及的位置。Aspen Mesh 是这次推广的结果，也是一段历程的结局，同时也开启了一个新的篇章。
本系列文章的第二和第三章节将会重点讨论为什么我们决定将 Istio 作为我们服务网格的核心，和我们将会在未来的几个月内推出什么样的商业化的服务网格。
| 41.231707 | 192 | 0.835552 | yue_Hant | 0.414276 |
bcf6c7b3cf137307e7cc215568e98ea9f5f956c2 | 3,641 | md | Markdown | docs/testing/ci.md | Zondax/web-docs-tee | a5ef29da351aab4184968e27670bbb2973ae6cd6 | [
"Apache-2.0"
] | null | null | null | docs/testing/ci.md | Zondax/web-docs-tee | a5ef29da351aab4184968e27670bbb2973ae6cd6 | [
"Apache-2.0"
] | null | null | null | docs/testing/ci.md | Zondax/web-docs-tee | a5ef29da351aab4184968e27670bbb2973ae6cd6 | [
"Apache-2.0"
] | null | null | null | ---
title: CI Tests
sidebar_position: 5
---
Nowadays software development is more complicated than ever and it's important that software is tested and verified so that we can be sure it works as intended.
There are many ways to test software, and we decided to test every commit we make to guarantee that our changes do not cause tests to fail, and eventually catching breaking changes early in the development pipeline.
Unfortunately this project has some complex requirements that require certain environment to be setup before running or even compiling the application is possible.
As such we have prepared a set of tests (and framework) to be run by Github Actions on every commit. These tests are run and the reports collected by a [script].
## Setup
Due to the nature of the environment, the quickest way to create the test suite to be run in CI was to provide it as an alternative build mode for the (host) application.
Using such method, it's possible to execute the application normally and have it run the entire test suite, as written in the [`execute_tests`](https://github.com/Zondax/tee-substrate-service/blob/master/REE/lib/src/ci.rs#L13) function.
This is done by creating a connection to the service exposed by the application and then running all the tests.
:::note
To avoid usage of the "CI" build in production a "fake task" mechanism is adopted.
This implies "selecting" a never-ending task in the application scheduler in the case of a normal build, but in the "CI" build this task is instead the set of tests.
This leads to the application terminating once the tests have all executed, while otherwise just execute the server task.
:::
The Github Action manifest makes the runner build the application in "CI mode" to enable the tests before running them via the script.
## Sample test
In the following snippet you can see our custom test utility used to run our test suite.
```rust
Test::new(
"generateNew 00",
"generate new sr25519 keypair and return a public key; no seed",
|| {
client
.sr25519_generate_new()
.map_err(|e| format!("failed to issue request: {:?}", e))?;
Ok::<_, String>(())
},
)
.exec();
```
This is a simple utility to reduce boilerplate related to scheduling in the application scheduler or [printing test reports](#reports).
## Reports
Due to the nature of how we run these tests, we are not able to run these tests directly.
This in turn translates on printing test reports to the console and then later interpreting them to collect the results.
A [script] has been devised to serve the purpose of doing setup tasks, running the application and finally collecting reports and presenting a summary
## Script Overview
The [script] will first start the qemu virtual machine (via `make run`), then setup a netcat listeners on the ports exposed by the machine for both the logging interfaces, capturing their output.
After the tests have run it detects (via grep) the section of the logging output that contains the raw test reports created by the suite.
The region of the reports is delimited by `TESTS STARTING` and `TESTS FINISHED` output strings.
After that, the region is searched once again for successes and failures (marked by `SUCCESS` and `FAILURE` strings) and these results are counted.
If there's at least 1 failure the whole suite is considered failed and the script exits with an error, so that the Github Action can determine it was a failure.
[script]: https://github.com/Zondax/tee-base/blob/b034c42bfa4e3a00e7d3ee173ddac6a01b1a0803/scripts/run_ci_tests.sh
| 49.876712 | 236 | 0.758857 | eng_Latn | 0.9996 |
bcf6c84cf1b63b1f951bc502355fabcc3fdd2221 | 6,601 | md | Markdown | docs/src/pages/de/core-concepts/layouts.md | Leon0824/astro | 3e4cfea4e29ab958d69e4502c1f634a007393a7b | [
"MIT"
] | null | null | null | docs/src/pages/de/core-concepts/layouts.md | Leon0824/astro | 3e4cfea4e29ab958d69e4502c1f634a007393a7b | [
"MIT"
] | null | null | null | docs/src/pages/de/core-concepts/layouts.md | Leon0824/astro | 3e4cfea4e29ab958d69e4502c1f634a007393a7b | [
"MIT"
] | null | null | null | ---
layout: ~/layouts/MainLayout.astro
title: Layouts
description: Eine Einführung in Layouts - eine Art Astro-Komponente, die für gemeinsame Layouts auf verschiedenen Seiten verwendet wird.
---
**Layouts** sind eine besondere Art der [Komponente](/core-concepts/astro-components) - sie können dir helfen gemeinsame Seiten-Layouts über dein Projekt verteilt zu nutzen.
Layouts verhalten sich so, wie andere mehrfach verwendbare Astro-Komponenten auch. Es gibt keine neue Syntax oder API zu erlernen. Allerdings sind mehrfach verwendbare Layouts ein so weit verbreitetes Modell im Bereich der Web-Entwicklung, dass wir diese Anleitung verfasst haben, um dich bei der Verwendung zu unterstützen.
## Anwendung
Astro-Layouts unterstützen Props, Slots und alle anderen Merkmale von Astro-Komponenten. Layouts sind letztendlich einfach normale Komponenten!
Anders als andere Komponenten enthalten Layouts allerdings oft auch die einfassenden Seitenelemente `<html>`, `<head>` und `<body>` (die so genannte **Page Shell**).
Es ist ein allgemein übliches Verfahren alle Layout-Komponenten unter einem einzigen `src/layouts`-Verzeichnis anzulegen.
## Beispiel
```astro
---
// src/layouts/BasisLayout.astro
const {title} = Astro.props;
---
<html>
<head>
<title>Beispiel-Layout: {title}</title>
</head>
<body>
<!-- Fügt jeder Seite eine Navigationsleiste hinzu. -->
<nav>
<a href="#">Home</a>
<a href="#">Posts</a>
<a href="#">Kontakt</a>
</nav>
<!-- slot: Deine Seiteninhalte werden hier eingefügt. -->
<slot />
</body>
</html>
```
📚 Über das `<slot />`-Element lässt sich in Astro definieren, wo untergeordnete Elemente (die an das Layout übergeben werden) erscheinen sollen. Erfahre mehr darüber wie `<slot />` funktioniert in unserer [Anleitung zu Astro-Komponenten](/core-concepts/astro-components).
Sobald du dein erstes Layout erstellt hast, kannst du es so verwenden, wie du jede andere Komponente in einer Seite verwenden würdest. Denke daran, dass dein Layout den gesamten Seitenaufbau enthält: `<html>`, `<head>`, und `<body>`. Du musst nur den Seiteninhalt hinzufügen.
```astro
---
// src/pages/index.astro
import BasisLayout from '../layouts/BasisLayout.astro'
---
<BasisLayout title="Homepage">
<h1>Hallo Welt!</h1>
<p>Dies ist mein Seiteninhalt, er wird innerhalb eines Layouts ausgegeben.</p>
</BasisLayout>
```
## Verschachtelte Layouts
Du kannst Layouts ineinander verschachteln, wenn du vom Basis-Layout abweichende Layout-Elemente auf einzelnen Seiten einsetzen willst, ohne dabei jedes Mal das gesamte Layout zu wiederholen. Es ist ein übliches Verfahren in Astro ein generisches `BasisLayout` zu verwenden und auf diesem weitere spezifische Layouts (`PostLayout`, `ProduktLayout` etc.) aufzusetzen, die das `BasisLayout` als Grundlage verwenden.
```astro
---
// src/layouts/PostLayout.astro
import BasisLayout from '../layouts/BasisLayout.astro'
const {title, author} = Astro.props;
---
<!-- Dieses Layout verwendet das Basis-Layout (siehe obiges Beispiel): -->
<BasisLayout title={title}>
<!-- Fügt neue Post-spezifische Inhalte zu jeder Seite hinzu. -->
<div>Post-Autor/Autorin: {author}</div>
<!-- slot: Deine Seiteninhalte werden hier eingefügt. -->
<slot />
</BasisLayout>
```
## Layouts zusammenstellen
Manchmal benötigst du detailliertere Kontrolle über deine Seiten. Zum Beispiel willst du vielleicht SEO- oder Social-Media-`meta`-Tags auf bestimmten Seiten hinzufügen, auf anderen aber nicht. Das kannst du mit Props in deinem Layout erreichen (`<BasisLayout addMeta={true} ...`) - ab einem bestimmten Punkt ist es möglicherweise jedoch leichter deine Layouts nicht zu verschachteln.
Anstatt deine gesamte `<html>`-Seite als ein einziges großes Layout zu definieren, kannst du die `head`- und `body`-Inhalte als kleinere, getrennte Komponenten definieren. Hierdurch kannst du verschiedene Layouts auf jeder Seite zusammenstellen.
```astro
---
// src/layouts/BasisHead.astro
const {title, description} = Astro.props;
---
<meta charset="UTF-8">
<title>{title}</title>
<meta name="description" content={description}>
<link rel="preconnect" href="https://fonts.gstatic.com">
<link href="https://fonts.googleapis.com/css2?family=Spectral:ital,wght@0,400;0,700;1,400;1,700&display=swap" rel="stylesheet">
```
Beachte dass dieses Layout deine **page shell** nicht mit einschließt und nur einige generische Elemente auflistet, die in deinem `<head>`-Block erscheinen sollen. Du hast mehr Kontrolle über die Struktur der einzelnen Seite und kannst mehrere Layout-Komponenten kombinieren.
```astro
---
// src/pages/index.astro
import BasisHead from '../layouts/BasisHead.astro';
import OpenGraphMeta from '../layouts/OpenGraphMeta.astro';
---
<html>
<head>
<!-- Nun hast du volle Kontrole über `head` - pro Seite. -->
<BasisHead title="Title der Seite" description="Beschreibung der Seite" />
<OpenGraphMeta />
<!-- Du kannst je nach Bedarf sogar eigene einmalig benötigte Elemente hinzufügen. -->
<link rel="alternate" type="application/rss+xml" href="/feed/posts.xml">
</head>
<body>
<!-- ... -->
</body>
</html>
```
Der Nachteil bei diesem Ansatz ist, dass du die `<html>`-, `<head>`- und `<body>`-Elemente dabei auf jeder Seite definieren musst. Diese werden benötigt, um die Seite vollständig zusammenzustellen, da die Layout-Komponenten nicht mehr die gesamte **Page Shell** beinhalten.
## Markdown-Layouts
Für Markdown-Dateien ist ein Layout unerlässlich. Markdown-Dateien können ein bestimmtes Layout im Frontmatter aufrufen. Jede Markdown-Datei wird als HTML gerendert und anschließend an der Stelle in den `<slot />` eingespeist, wo dieser im Layout definiert ist.
```markdown
---
title: Blog-Post
layout: ../layouts/PostLayout.astro
---
Dieser Blog-Post wird innerhalb des `<PostLayout />`-Layout **gerendert**.
```
Markdown-Seiten übergeben immer eine oder mehrere `content`-Eigenschaften an ihr Layout. Dies ist sehr hilfreich, um Informationen über die Seite, einen Titel, Metadaten, eine Index-Tabelle, Kopfzeilen und anderes für die Seite zur Verfügung zu haben.
```astro
---
// src/layouts/PostLayout.astro
const { content } = Astro.props;
---
<html>
<head>
<title>{content.title}</title>
</head>
<body>
<h1>{content.title}</h1>
<h2>{content.description}</h2>
<img src={content.image} alt="">
<article>
<!-- slot: Markdown-Inhalte erscheinen hier! -->
<slot />
</article>
</body>
</html>
```
📚 Lerne mehr über die Verwendung von Markdown in Astro in unserer [Markdown-Anleitung](/guides/markdown-content).
| 42.314103 | 413 | 0.737767 | deu_Latn | 0.985418 |
bcf741d7b132403dbe3544118f1740aeb168bf41 | 4,792 | md | Markdown | countries/do.md | florenthemmi/ips-by-country | 2f63ec2108ceaae97221de52654753c545733d84 | [
"MIT"
] | 1 | 2021-05-24T06:16:49.000Z | 2021-05-24T06:16:49.000Z | countries/do.md | florenthemmi/ips-by-country | 2f63ec2108ceaae97221de52654753c545733d84 | [
"MIT"
] | null | null | null | countries/do.md | florenthemmi/ips-by-country | 2f63ec2108ceaae97221de52654753c545733d84 | [
"MIT"
] | null | null | null | # Dominican Republic
CIDR | Range start | Range end | Total IPs | Assign date | Owner
------------------ | --------------- | --------------- | ---------- | ----------- | -----
64.32.64.0/18 | 64.32.64.0 | 64.32.127.255 | 16384 | 2001-02-06 |
66.98.0.0/18 | 66.98.0.0 | 66.98.63.255 | 16384 | 2001-04-06 |
66.98.64.0/19 | 66.98.64.0 | 66.98.95.255 | 8192 | 2001-04-06 |
148.0.0.0/16 | 148.0.0.0 | 148.0.255.255 | 65536 | 2014-04-14 |
148.101.0.0/16 | 148.101.0.0 | 148.101.255.255 | 65536 | 2014-04-14 |
148.103.0.0/16 | 148.103.0.0 | 148.103.255.255 | 65536 | 2014-05-27 |
148.255.0.0/16 | 148.255.0.0 | 148.255.255.255 | 65536 | 2014-04-14 |
152.0.0.0/16 | 152.0.0.0 | 152.0.255.255 | 65536 | 2014-04-14 |
152.166.0.0/15 | 152.166.0.0 | 152.167.255.255 | 131072 | 2014-05-28 |
179.43.192.0/18 | 179.43.192.0 | 179.43.255.255 | 16384 | 2013-09-30 |
179.49.80.0/20 | 179.49.80.0 | 179.49.95.255 | 4096 | 2013-05-20 |
179.51.64.0/20 | 179.51.64.0 | 179.51.79.255 | 4096 | 2014-01-20 |
179.52.0.0/15 | 179.52.0.0 | 179.53.255.255 | 131072 | 2013-03-07 |
181.36.0.0/15 | 181.36.0.0 | 181.37.255.255 | 131072 | 2011-02-18 |
186.1.64.0/18 | 186.1.64.0 | 186.1.127.255 | 16384 | 2011-06-08 |
186.6.0.0/16 | 186.6.0.0 | 186.6.255.255 | 65536 | 2010-06-17 |
186.7.0.0/16 | 186.7.0.0 | 186.7.255.255 | 65536 | 2011-07-12 |
186.33.64.0/18 | 186.33.64.0 | 186.33.127.255 | 16384 | 2012-03-29 |
186.120.0.0/17 | 186.120.0.0 | 186.120.127.255 | 32768 | 2009-07-15 |
186.120.128.0/17 | 186.120.128.0 | 186.120.255.255 | 32768 | 2010-03-18 |
186.149.0.0/16 | 186.149.0.0 | 186.149.255.255 | 65536 | 2011-06-24 |
186.150.0.0/16 | 186.150.0.0 | 186.150.255.255 | 65536 | 2013-06-03 |
190.0.64.0/19 | 190.0.64.0 | 190.0.95.255 | 8192 | 2006-07-20 |
190.6.128.0/20 | 190.6.128.0 | 190.6.143.255 | 4096 | 2006-05-11 |
190.6.144.0/20 | 190.6.144.0 | 190.6.159.255 | 4096 | 2007-04-16 |
190.8.32.0/20 | 190.8.32.0 | 190.8.47.255 | 4096 | 2007-05-14 |
190.52.224.0/20 | 190.52.224.0 | 190.52.239.255 | 4096 | 2008-03-13 |
190.52.240.0/20 | 190.52.240.0 | 190.52.255.255 | 4096 | 2008-12-09 |
190.80.128.0/18 | 190.80.128.0 | 190.80.191.255 | 16384 | 2006-10-19 |
190.80.192.0/18 | 190.80.192.0 | 190.80.255.255 | 16384 | 2007-04-12 |
190.94.0.0/19 | 190.94.0.0 | 190.94.31.255 | 8192 | 2007-04-16 |
190.94.32.0/19 | 190.94.32.0 | 190.94.63.255 | 8192 | 2008-07-02 |
190.94.64.0/18 | 190.94.64.0 | 190.94.127.255 | 16384 | 2008-07-02 |
190.110.0.0/19 | 190.110.0.0 | 190.110.31.255 | 8192 | 2008-09-10 |
190.110.32.0/19 | 190.110.32.0 | 190.110.63.255 | 8192 | 2009-08-21 |
190.113.64.0/20 | 190.113.64.0 | 190.113.79.255 | 4096 | 2014-04-30 |
190.122.96.0/20 | 190.122.96.0 | 190.122.111.255 | 4096 | 2009-05-14 |
190.122.112.0/20 | 190.122.112.0 | 190.122.127.255 | 4096 | 2011-02-25 |
190.124.64.0/19 | 190.124.64.0 | 190.124.95.255 | 8192 | 2010-02-11 |
190.166.0.0/17 | 190.166.0.0 | 190.166.127.255 | 32768 | 2007-07-16 |
190.166.128.0/17 | 190.166.128.0 | 190.166.255.255 | 32768 | 2008-02-28 |
190.167.0.0/16 | 190.167.0.0 | 190.167.255.255 | 65536 | 2008-12-04 |
190.211.176.0/20 | 190.211.176.0 | 190.211.191.255 | 4096 | 2013-06-20 |
200.42.192.0/19 | 200.42.192.0 | 200.42.223.255 | 8192 | 2002-05-29 |
200.42.224.0/20 | 200.42.224.0 | 200.42.239.255 | 4096 | 2004-06-04 |
200.42.240.0/20 | 200.42.240.0 | 200.42.255.255 | 4096 | 2005-06-08 |
200.88.0.0/19 | 200.88.0.0 | 200.88.31.255 | 8192 | 2002-08-21 |
200.88.32.0/19 | 200.88.32.0 | 200.88.63.255 | 8192 | 2003-02-17 |
200.88.64.0/18 | 200.88.64.0 | 200.88.127.255 | 16384 | 2003-05-30 |
200.88.128.0/19 | 200.88.128.0 | 200.88.159.255 | 8192 | 2004-03-24 |
200.88.160.0/19 | 200.88.160.0 | 200.88.191.255 | 8192 | 2005-08-05 |
200.88.192.0/18 | 200.88.192.0 | 200.88.255.255 | 16384 | 2004-10-29 |
201.229.128.0/18 | 201.229.128.0 | 201.229.191.255 | 16384 | 2005-12-05 |
201.229.192.0/18 | 201.229.192.0 | 201.229.255.255 | 16384 | 2006-06-07 |
| 81.220339 | 89 | 0.483723 | yue_Hant | 0.061395 |
bcf755c4274aa4fb26fb63cb38f84a4fb9ce87ab | 80 | md | Markdown | README.md | kavish-p/devops-notes-commands | 46ea5626ca13282df2906759d65f93fc5cb61c30 | [
"MIT"
] | null | null | null | README.md | kavish-p/devops-notes-commands | 46ea5626ca13282df2906759d65f93fc5cb61c30 | [
"MIT"
] | null | null | null | README.md | kavish-p/devops-notes-commands | 46ea5626ca13282df2906759d65f93fc5cb61c30 | [
"MIT"
] | null | null | null | # devops-notes-commands
Notes and useful commands for some popular DevOps tools
| 26.666667 | 55 | 0.825 | eng_Latn | 0.998151 |
bcf79881d59e458b542f662f6a504885b4532c9a | 2,228 | md | Markdown | AlchemyInsights/onedrive-missing-files-or-folders.md | pebaum/OfficeDocs-AlchemyInsights-pr.es-ES | 1ef7350ca1a1c8038bc57b9e47bdd510bb7c83d5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/onedrive-missing-files-or-folders.md | pebaum/OfficeDocs-AlchemyInsights-pr.es-ES | 1ef7350ca1a1c8038bc57b9e47bdd510bb7c83d5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/onedrive-missing-files-or-folders.md | pebaum/OfficeDocs-AlchemyInsights-pr.es-ES | 1ef7350ca1a1c8038bc57b9e47bdd510bb7c83d5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'OneDrive: faltan archivos o carpetas'
ms.author: pebaum
author: pebaum
ms.audience: ITPro
ms.topic: article
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.assetid: 1afe2f6d-bf4f-4fe7-87c6-25fd86bd89a5
ms.openlocfilehash: a8c5dd6e75c35be185cea1bf3ffb733b5f5b61d2
ms.sourcegitcommit: 631cbb5f03e5371f0995e976536d24e9d13746c3
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 04/22/2020
ms.locfileid: "43761469"
---
# <a name="onedrive-missing-files-or-folders"></a>OneDrive: faltan archivos o carpetas
**Compruebe la papelera de reciclaje del sitio**.
- [Restaurar elementos de un sitio de SharePoint en la Papelera de reciclaje](https://support.office.com/article/restore-deleted-items-from-the-site-collection-recycle-bin-5fa924ee-16d7-487b-9a0a-021b9062d14b)
- [Restaurar archivos o carpetas eliminados en OneDrive](https://support.office.com/article/Restore-deleted-files-or-folders-in-OneDrive-949ada80-0026-4db3-a953-c99083e6a84f)
**Usar la característica de restauración de archivos de OneDrive**.
Si muchos de los archivos de OneDrive se eliminan, se sobrescriben, están dañados o están infectados por malware, puede restaurar todo el OneDrive a una hora anterior mediante la característica de [restauración de archivos de OneDrive](https://support.office.com/article/Restore-your-OneDrive-fa231298-759d-41cf-bcd0-25ac53eb8a15) .
**Use el registro de auditoría o el panel actividad de archivo para comprobar el historial del archivo**.
Consulte los [informes de auditoría](https://docs.microsoft.com/office365/securitycompliance/search-the-audit-log-in-security-and-compliance) desplazándose [aquí](https://sip.protection.office.com/).
Use el [Panel actividad de archivo](https://support.office.com/article/File-activity-in-a-document-library-6105ecda-1dd0-4f6f-9542-102bf5c0ffe0) para comprobar el historial del archivo.
**Compruebe el cliente de sincronización de OneDrive en el equipo local**.
Si está sincronizando los archivos de su equipo con el cliente de sincronización de OneDrive, Compruebe la carpeta de sincronización local para asegurarse de que se haya cargado correctamente. Asegúrese de que también comprueba la papelera de reciclaje en el equipo local.
| 53.047619 | 332 | 0.810144 | spa_Latn | 0.813814 |
bcf7afeeb61fc7193033281c109053cace89686a | 2,010 | md | Markdown | en/docs/security-advisories/2020/WSO2-2020-0713.md | 1uffyD9/docs-security | 3fc01119ab08268bf8e136157050f97036340458 | [
"Apache-2.0"
] | null | null | null | en/docs/security-advisories/2020/WSO2-2020-0713.md | 1uffyD9/docs-security | 3fc01119ab08268bf8e136157050f97036340458 | [
"Apache-2.0"
] | null | null | null | en/docs/security-advisories/2020/WSO2-2020-0713.md | 1uffyD9/docs-security | 3fc01119ab08268bf8e136157050f97036340458 | [
"Apache-2.0"
] | null | null | null | ---
title: Security Advisory WSO2-2020-0713
category: security-advisories
published: 5th June 2020
version: 1.0.0
severity: Medium
cvss: "6.1 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)"
---
# Security Advisory WSO2-2020-0713
<p class="doc-info">Published: 5th June 2020</p>
<p class="doc-info">Version: 1.0.0</p>
<p class="doc-info">Severity: Medium</p>
<p class="doc-info">CVSS Score: 6.1 (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N)</p>
---
### AFFECTED PRODUCTS
* WSO2 IS as Key Manager : 5.10.0 or earlier
* WSO2 Identity Server : 5.10.0 or earlier
### OVERVIEW
Client-side open redirect arise when an application incorporates user-controllable data into the target of a redirection in an unsafe way in the management console.
### DESCRIPTION
Client-side open redirect arise when an application incorporates user-controllable data into the target of a redirection in an unsafe way. This payload is allowing to redirect the user to external domain.
### IMPACT
An attacker can construct a URL within the application that causes a redirection to an arbitrary external domain. This behavior can be leveraged to facilitate phishing attacks against users of the application.
### SOLUTION
If you are using an affected product version, it is highly recommended to migrate to the latest released version to receive security fixes.
Otherwise you may apply the relevant fixes to the product based on the public fix(s):
* [https://github.com/wso2/carbon-identity-framework/pull/2848](https://github.com/wso2/carbon-identity-framework/pull/2848)
!!! info todo
**If you are a WSO2 customer with Support Subscription, please use [WSO2 Update Manager](https://wso2.com/updates/wum)(WUM) updates in order to apply the fix to the affected versions.**
### CREDITS
WSO2 thanks, [Vijayakumar Muniraj](https://www.linkedin.com/in/vijaykumarmuniraj) ([Cyber Security Research Labs](https://cybersecurityworks.com/)) for responsibly reporting the identified issue and working with us as we addressed it.
| 41.875 | 234 | 0.757711 | eng_Latn | 0.960095 |
bcf7e63978990f56ba86b32a919ee1c520896cb1 | 2,490 | md | Markdown | ce/customerengagement/on-premises/deploy/dynamics-365-for-tablets-and-ifd.md | erical77/dynamics-365-customer-engagement | 9de2c7096b7c9eed1a7192f3e3c84791926dca23 | [
"CC-BY-4.0",
"MIT"
] | 194 | 2018-04-02T15:18:06.000Z | 2022-03-24T19:55:48.000Z | ce/customerengagement/on-premises/deploy/dynamics-365-for-tablets-and-ifd.md | erical77/dynamics-365-customer-engagement | 9de2c7096b7c9eed1a7192f3e3c84791926dca23 | [
"CC-BY-4.0",
"MIT"
] | 2,219 | 2018-04-12T06:42:32.000Z | 2022-03-31T21:52:26.000Z | ce/customerengagement/on-premises/deploy/dynamics-365-for-tablets-and-ifd.md | erical77/dynamics-365-customer-engagement | 9de2c7096b7c9eed1a7192f3e3c84791926dca23 | [
"CC-BY-4.0",
"MIT"
] | 406 | 2018-03-30T19:22:39.000Z | 2022-03-28T19:14:42.000Z | ---
title: "Dynamics 365 for tablets and IFD | Microsoft Docs"
description: Learn about using Dynamics 365 for tablets over the internet with Dynamics 365 Customer Engagement (on-premises)
ms.custom: ""
ms.date: "10/01/2018"
ms.prod: d365ce-op
ms.reviewer: ""
ms.suite: ""
ms.tgt_pltfrm: ""
ms.topic: "article"
applies_to:
- "Dynamics 365 (on-premises)"
ms.assetid: 5ae8ee8a-7161-429d-90f6-1300263a2679
caps.latest.revision: 11
ms.author: matp
author: Mattp123
manager: kvivek
---
# Dynamics 365 for tablets and IFD
[!INCLUDE[pn_microsoftcrm](../includes/pn-microsoftcrm.md)] on-premises deployments require Internet Facing Deployment (IFD) for users to access their data on their tablets. If you have your [!INCLUDE[pn_microsoftcrm](../includes/pn-microsoftcrm.md)] website available over the internet but it is not using the [!INCLUDE[pn_microsoftcrm](../includes/pn-microsoftcrm.md)] IFD configuration, **it is not supported**. To verify that your on-premises deployment is configured for IFD, open [!INCLUDE[pn_Deployment_Manager_long](../includes/pn-deployment-manager-long.md)] on your [!INCLUDE[pn_microsoftcrm](../includes/pn-microsoftcrm.md)] Server. The Authentication Summary section should show that both Claims-Based Authentication and Internet-Facing Deployment are enabled.
> [!IMPORTANT]
> For [!INCLUDE[pn_moca_full](../includes/pn-moca-full.md)] to successfully connect to a new deployment of [!INCLUDE[pn_microsoftcrm](../includes/pn-microsoftcrm.md)], you must run a Repair of [!INCLUDE[pn_microsoftcrm](../includes/pn-microsoftcrm.md)] on the server running [!INCLUDE[pn_iis](../includes/pn-iis.md)] where the [!INCLUDE[pn_Web_Application_Server](../includes/pn-web-application-server.md)] role is installed *after* the [!INCLUDE[pn_Internet_Facing_Deployment_Configuration_Wizard](../includes/pn-internet-facing-deployment-configuration-wizard.md)] is successfully completed. [!INCLUDE[proc_more_information](../includes/proc-more-information.md)][Uninstall, change, or repair Microsoft Dynamics 365 Server](uninstall-change-repair-dynamics-365-server.md).
## See Also
[Setup overview for mobile apps](/dynamics365/customer-engagement/mobile-app/set-up-dynamics-365-for-phones-and-dynamics-365-for-tablets)
[Configure IFD for Microsoft Dynamics 365](configure-ifd-for-dynamics-365.md)
[!INCLUDE[footer-include](../../../includes/footer-banner.md)] | 73.235294 | 777 | 0.771486 | eng_Latn | 0.788351 |
bcf822f8b47ee08f176041e1773ce4751cea1b33 | 2,984 | md | Markdown | README.md | brndnmtthws/cracking-the-coding-interview-rust | e4d89066ccbe0d31c616c1265fe2f6ab620e5a58 | [
"Unlicense"
] | 307 | 2019-02-12T11:16:05.000Z | 2022-03-27T16:21:58.000Z | README.md | brndnmtthws/cracking-the-coding-interview-rust | e4d89066ccbe0d31c616c1265fe2f6ab620e5a58 | [
"Unlicense"
] | 2 | 2019-06-28T11:16:31.000Z | 2019-07-25T14:05:25.000Z | README.md | brndnmtthws/cracking-the-coding-interview-rust | e4d89066ccbe0d31c616c1265fe2f6ab620e5a58 | [
"Unlicense"
] | 38 | 2019-03-13T03:07:01.000Z | 2022-03-25T06:31:49.000Z | [](https://travis-ci.org/brndnmtthws/cracking-the-coding-interview-rust) [](https://dependabot.com) [](https://coveralls.io/github/brndnmtthws/cracking-the-coding-interview-rust?branch=master)
# Cracking the Coding Interview with Rust
This repository contains code for my YouTube programming interview practice & learning series about [Rust](https://www.rust-lang.org/). The problems are based on the book "Cracking the Coding Interview" by Gayle Laakmann McDowell. You can find the [existing solutions here](https://github.com/careercup/CtCI-6th-Edition).
To follow along, you can:
- [📹 Subscribe to my YouTube channel](https://www.youtube.com/c/BrendenMatthews/live), or
- [🎮 Follow me on Twitch](https://www.twitch.tv/letsmakestuff)
You can find the existing videos on YouTube below:
- [📽 Chapter 1, problems 1-4](https://youtu.be/MoTEALq5UjI)
- [📽 Chapter 1, problems 5-9](https://youtu.be/dTp7d7xqqAo)
- [📽 Chapter 2, problem 1 (part 1)](https://youtu.be/zLuGFOLDA4Q)
- [📽 Chapter 2, problem 1 (part 2)](https://youtu.be/uAV5H1SiPVE)
- [📽 Chapter 2, problems 1-3](https://youtu.be/SdsgfnwPNT4)
- [📽 Chapter 2, problems 4-6](https://youtu.be/V5ngI_V_kI8?t=749)
- [📽 Chapter 2, problems 7-8, Chapter 3, problems 1-2](https://youtu.be/sC9HMy5Tilw)
- [📽 Chapter 3, problems 3-6](https://youtu.be/JRWVesPoIbQ)
- [📽 Chapter 4, problems 1-3](https://youtu.be/EUJAy5_At6o)
- [📽 Chapter 4, problems 4-9](https://youtu.be/Q-Z_B9sZHYc)
- [📽 Chapter 4, problems 10-12, Chapter 5, problems 1-8](https://youtu.be/Evd-z6aGIAA)
- [📽 Chapter 6, problems 1-10](https://youtu.be/1bowu80HSHg)
- [📽 Chapter 7, problems 1-3](https://youtu.be/uOTIWwVtgfI)
- [📽 Chapter 7, problems 4-6](https://youtu.be/lqrUScbFLgQ)
- [📽 Chapter 7, problems 7-9, Part 1](https://youtu.be/mIU-GhHpATg)
- [📽 Chapter 7, problems 7-9, Part 2](https://youtu.be/1FioBErAYew)
- [📽 Chapter 7, problems 10-11](https://youtu.be/P_KrbWKabeA)
- [📽 Chapter 7, problem 12, Chapter 8, problems 1-4](https://youtu.be/W209V_dqakM)
- [📽 Chapter 8, problems 5-11](https://youtu.be/L6GqbfKwldg)
- [📽 Chapter 8, problems 12-14 (part 1)](https://youtu.be/5axLcIOVnbE)
- [📽 Chapter 8, problems 12-14 (part 2)](https://youtu.be/jV5BFjVGftI)
- [📽 Chapter 8, problems 12-14 (part 3)](https://youtu.be/A8pNIwpZdoU)
## Prerequisites
To run the code, you'll need an up-to-date version of Rust. The recommended way of
installing Rust is [using a tool called rustup](https://rustup.rs/):
```ShellSession
$ curl https://sh.rustup.rs -sSf | sh
...
```
Once you have Rust installed, you can build and run the tests.
### Running the Code
```ShellSession
$ cargo build
$ cargo test
...
```
| 53.285714 | 545 | 0.722855 | yue_Hant | 0.45166 |
bcf826afaec4a0ece2084b4a3337ddf7901990b1 | 416 | md | Markdown | gateway_testcases/doc/SUMMARY.md | sandmars/web | f301bce6ecd018709efd6d76167d47cdbdaab21e | [
"CC0-1.0"
] | null | null | null | gateway_testcases/doc/SUMMARY.md | sandmars/web | f301bce6ecd018709efd6d76167d47cdbdaab21e | [
"CC0-1.0"
] | null | null | null | gateway_testcases/doc/SUMMARY.md | sandmars/web | f301bce6ecd018709efd6d76167d47cdbdaab21e | [
"CC0-1.0"
] | null | null | null | # 测试方案
* [通用测试方案]()
- [WEB测试](README_WEB.md)
- [呼叫测试](README_CALLTEST.md)
- [多SIP测试](multi_sip_test.md)
- [Failover测试](failover_test.md)
- [号码变换测试](manipulation_test.md)
- [多号码变换测试](multi_manipulation_test.md)
- [多路由测试](multi_route_test.md)
- [路由顺序测试](route_order_test.md)
* [DGW-100X测试方案]()
- [AutoProvision测试](test_autoprovision.md)
* [VS-GW-G测试方案]()
- [短信](README_SMS.md)
| 26 | 46 | 0.644231 | yue_Hant | 0.679069 |
bcf84f931eff34d9b92f5d6a3f64d514d0d2fbc2 | 4,856 | md | Markdown | source/_posts/blackpool_illuminations_are_lit_behind_closed_doors_and_will_stay_on_an_extra_two_months.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | null | null | null | source/_posts/blackpool_illuminations_are_lit_behind_closed_doors_and_will_stay_on_an_extra_two_months.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | null | null | null | source/_posts/blackpool_illuminations_are_lit_behind_closed_doors_and_will_stay_on_an_extra_two_months.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | 2 | 2021-09-18T12:06:26.000Z | 2021-11-14T15:17:34.000Z | ---
extends: _layouts.post
section: content
image: https://i.dailymail.co.uk/1s/2020/09/05/01/32796290-0-image-a-28_1599264387548.jpg
title: Blackpool Illuminations are lit behind closed doors and will stay on an extra two months
description: Six NHS workers and a young fundraiser switched on the Blackpool Illuminations last night, which were being held away from the public for the first time in more than 70 years.
date: 2020-09-05-03-54-30
categories: [latest, latest]
featured: true
---
Blackpool Illuminations were lit last night and will be staying on two months longer than usual until January in order to get tourism moving after lockdown.
Six NHS workers and a young fundraiser switched on the Illuminations, which were being held away from the public for the first time in more than 70 years.
Due to the Covid-19 pandemic the resort's annual celebration took place on Friday night behind closed doors, but were filmed in the Tower Ballroom.
The display usually runs for 66 days until early November but this year it has been extended by two months to boost the resort's tourism season due to the pandemic and will not be switched off until January 3.
Blackpool Illuminations were lit last night and will be staying on until January 2021, two months longer than usual in order to get tourism moving after lockdown
Six NHS workers and a young fundraiser switched on the Illuminations, which were being held away from the public for the first time in more than 70 years
The 'Corona Heroes' joined the event hosted by Diversity's Jordan Banjo and Perri Kiely, Blackpool-born singer-songwriter Rae Morris and the Illuminations' creative curator Laurence Llewelyn-Bowen
Due to the Covid-19 pandemic the resort's annual celebration took place on Friday night behind closed doors, but will be filmed in the Tower Ballroom
The 'Corona Heroes' joined the event hosted by Diversity's Jordan Banjo and Perri Kiely, Blackpool-born singer-songwriter Rae Morris and the Illuminations' creative curator Laurence Llewelyn-Bowen.
This year's theme of Bring On The Light featured a display of hearts and rainbows along the Promenade's Golden Mile, along with images of a further 48 Corona Heroes from hundreds of nominations across the UK.
Those chosen to pull the switch included nurse Leona Harris, from Rossendale, Lancashire, nicknamed 'the Angel from the North'.
The display, which uses more than one million bulbs, stretches along the Promenade from Starr Gate at the south end of the town to Bispham in the north
A section of the lights along the Promenade's Golden Mile features a festoon of hearts and rainbows as a special thank you to the NHS
The lights will remain on display until January, two months longer than normal, to help boost the tourism trade which has been hit by the Covid-19 pandemic
She helped raise £75,000 to buy iPads for patients in hospitals, care homes and hospices all over Britain to keep families connected.
Joining her was six-year-old Will Ritchie, from Wirral, Merseyside, who raised £14,000 for hospitals in the area after he walked a marathon in a month.
The youngster, who was born with severe visual impairment and suffers with epilepsy, struggled to reach 100 metres at the start of lockdown but later stepped up to 1,500 metres a day.
Hospital chaplain David Anderson and therapy dog Jasper were also chosen for the support and comfort they provided to patients as well as boosting morale for staff at hospitals in east Lancashire.
Each year a celebrity is invited to switch on the lights and there are usually performances in the Radio 2 arena with a pre-switch on concert
This year's theme of Bring On The Light featured a display of hearts and rainbows along the Promenade's Golden Mile, along with images of a further 48 Corona Heroes from hundreds of nominations across the UK
Completing the line-up were Dr Jason Cupitt, who led the Covid-19 response at Blackpool Victoria Hospital's intensive care unit; Donna Doyle, restaurant manager at Liverpool's Alder Hey Hospital; and nurses Kirsty Jones and Rachelle Sutton, who moved out of their family homes while working at Blackpool's Trinity Hospice and Manchester's Nightingale Hospital.
Gillian Campbell, cabinet member for tourism and culture for Blackpool Council, said: 'Those that have been invited to perform the actual switch-on will be there to represent the hundreds of thousands of people who have done so much to protect and support the British people.
'This is an extraordinary year with our traditional celebration on the Tower Festival Headland becoming a virtual event, but we are delighted that the switch-on moment will be a tribute to the truly remarkable people who have led our nation's response to coronavirus.'
The Illuminations will stay lit for an extra two months until January 3 to boost tourist trade.
| 82.305085 | 360 | 0.805601 | eng_Latn | 0.999763 |
bcf8d60eb672260535629f24a664e710a447b4a3 | 613 | md | Markdown | README.md | dafo90/tic-tac-toe | c1c3520b9bb51ca0adf45e4b1b7afde1858505fe | [
"MIT"
] | null | null | null | README.md | dafo90/tic-tac-toe | c1c3520b9bb51ca0adf45e4b1b7afde1858505fe | [
"MIT"
] | null | null | null | README.md | dafo90/tic-tac-toe | c1c3520b9bb51ca0adf45e4b1b7afde1858505fe | [
"MIT"
] | null | null | null | # Tic-Tac-Toe
[Tic-Tac-Toe](https://dafo90.github.io/tic-tac-toe) game built with React, Material-UI, Redux and Saga.
1. Clone the project
```
git clone https://github.com/dafo90/tic-tac-toe.git
cd tic-tac-toe
```
2. Install all necessary dependencies
```
npm install
```
3. Run the application
```
npm start
```
#
- Images: [Tic Tac Toe with JavaScript](https://github.com/alialaa/js-tic-tac-toe)
- Base structure and player vs. player logic: [Build a Tic Tac Toe Game With React/Redux, Babel, Webpack and Material-UI](https://github.com/vanister/medium.com)
| 21.892857 | 163 | 0.662316 | kor_Hang | 0.494466 |
bcfa14de988c5c29985a27fbfe6a7d85e17c016b | 3,608 | md | Markdown | Language/Reference/User-Interface-Help/object-library-for-visual-basic-for-applications-not-found.md | CeptiveYT/VBA-Docs | 1d9c58a40ee6f2d85f96de0a825de201f950fc2a | [
"CC-BY-4.0",
"MIT"
] | 283 | 2018-07-06T07:44:11.000Z | 2022-03-31T14:09:36.000Z | Language/Reference/User-Interface-Help/object-library-for-visual-basic-for-applications-not-found.md | CeptiveYT/VBA-Docs | 1d9c58a40ee6f2d85f96de0a825de201f950fc2a | [
"CC-BY-4.0",
"MIT"
] | 1,457 | 2018-05-11T17:48:58.000Z | 2022-03-25T22:03:38.000Z | Language/Reference/User-Interface-Help/object-library-for-visual-basic-for-applications-not-found.md | CeptiveYT/VBA-Docs | 1d9c58a40ee6f2d85f96de0a825de201f950fc2a | [
"CC-BY-4.0",
"MIT"
] | 469 | 2018-06-14T12:50:12.000Z | 2022-03-27T08:17:02.000Z | ---
title: Object library for Visual Basic for Applications not found
ms.prod: office
ms.assetid: 1776826f-0842-4a7c-8e05-6dd4d777eca3
ms.date: 06/08/2017
ms.localizationpriority: medium
---
# Object library for Visual Basic for Applications not found
The Visual Basic for Applications [object library](../../Glossary/vbe-glossary.md#object-library) is no longer a standalone file; it is integrated into the [dynamic-link library (DLL)](../../Glossary/vbe-glossary.md#dynamic-link-library-dll).
Under unusual circumstances a previous version of the object library (vaxxx.olb or vaxxxx.olb) corresponding to the language of the [project](../../Glossary/vbe-glossary.md#project) might be needed, but not found. This error has the following causes and solutions:
- The object library is missing completely, isn't in the expected directory, or is an incorrect version. Search your disk to make sure the object library is in the correct directory, as specified in the [host-application](../../Glossary/vbe-glossary.md#host-application) documentation.
If the missing library is a language version that is installed by the host application, it may be easiest to simply rerun the setup program. If a project requires a different language object library than the one that accompanies your host application (for example, if someone sends you a project written on a machine set up for a different language), make sure the correct language version of the Visual Basic object library is included with the project and it is installed in the expected location.
Applications may support different language versions of their object libraries. To find out which language version is required, display the **References** dialog box, and see which language is indicated at the bottom of the dialog box.
Object libraries exist in different versions for each platform. Therefore, when projects are moved across platforms, for example, from Macintosh to Microsoft Windows, the correct language version of the referenced library for that platform must be available in the location specified in your host application documentation. Note that some language codes are two characters while others are three characters.
The Visual Basic object library file name is constructed as follows:
- Windows: Application Code + Language Code + [Version].OLB. For example: The French Visual Basic for Applications object library for version 2 was vafr2.olb.
- Macintosh: Application Name Language Code [Version] OLB. For example: The French Visual Basic for Applications object library for version 2 was VA FR 2 OLB.
If you can't find a missing project or object library on your system, contact the [referencing project's](../../Glossary/vbe-glossary.md#referencing-project) author. If the missing library is a Microsoft application object library, you can obtain it as follows:
- If you have access to Microsoft electronic technical support services, refer to the technical support section of this Help file. Under electronic services, you will find instructions on how to use the appropriate service option.
- If you don't have access to Microsoft electronic technical support services, Microsoft object libraries are available upon request as an application note from Microsoft. Information on how to contact your local Microsoft product support organization is also available in the technical support section of this Help file.
For additional information, select the item in question and press F1 (in Windows) or HELP (on the Macintosh).
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 90.2 | 499 | 0.797118 | eng_Latn | 0.998611 |
bcfa1c2dc18d223f06c3bf954936384b4fe70fc8 | 2,279 | markdown | Markdown | content/schedule/week-12/index.markdown | sta199-fa20-002/website | 53ac445f602dbcaf6b922d377c729c001a4e0bd5 | [
"CC0-1.0"
] | null | null | null | content/schedule/week-12/index.markdown | sta199-fa20-002/website | 53ac445f602dbcaf6b922d377c729c001a4e0bd5 | [
"CC0-1.0"
] | null | null | null | content/schedule/week-12/index.markdown | sta199-fa20-002/website | 53ac445f602dbcaf6b922d377c729c001a4e0bd5 | [
"CC0-1.0"
] | 5 | 2021-05-15T12:24:13.000Z | 2021-12-22T18:10:30.000Z | ---
title: "Week 12: Spatial data"
weight: 12
---
<style>
table {
font-size: 18px;
}
</style>
## Lectures
| | Slides | Videos | Application Exercise (AE) |
|-----------|--------------------------|--------|--------|
| Monday | [Spatial data + visualization](https://sta199-fa20-002.netlify.app/slides/23-spatial.html) | [Spatial data + visualization](https://warpwire.duke.edu/w/lb0EAA/)| [AE 23: Spatial data](https://sta199-fa20-002.netlify.app/appex/appex23-spatial.html) |
| Wednesday | No lecture: Statistics experience | | |
<!-- ## Readings -->
<!-- | | | -->
<!-- |------------|---| -->
<!-- |[Introduction to Modern Statistics: 4.1 Regression with multiple predictors](https://openintro-ims.netlify.app/multi-logistic-models.html#regression-multiple-predictors)| **Required** | -->
## Assignments
| | |
|------------------------|---|
| [Peer review](https://sta199-fa20-002.netlify.app/labs/peer-review.html)| **due Thu, Nov 5 at 11:59p** |
|[HW 03](https://sta199-fa20-002.netlify.app/hw/hw-03.html) | **due Sun, Nov 8 at 11:59p**|
|[Statistics experience #2](https://sta199-fa20-002.netlify.app/hw/stat-experience.html) | **due Sun, Nov 8 at 11:59p**|
|[Lab 08](https://sta199-fa20-002.netlify.app/labs/lab-08-logistic.html) | **due Wed, Nov 11 at 11:59p**|
## Announcements
### Tea with a TA!
Hang out with the TAs from STA 199! This is a casual conversation and a fun opportunity to meet the members of the STA 199 teaching time. The only rule is these can't turn into office hours!
Tea with a TA counts as a statistics experience.
**Upcoming Tea with a TA events**
- [**Caroline Levenson**](https://www.linkedin.com/in/carolinelevenson/), Mon, Nov 2, 1p - 2p
- [Click here](https://forms.gle/FucAXE6bLeJVyqRY9) to sign up
*Caroline Levenson is a junior studying Statistics and Computer Science. She did not know she wanted to study statistics until taking this class. Since then, she has completed an independent study with Professor Tackett where she created an R Shiny app for data visualization. The project was with the Duke Law School where she continues to work as a research assistant. In addition, she has worked in industry primarily as a software engineer.*
| 43.826923 | 447 | 0.658183 | eng_Latn | 0.837838 |
bcfa672d09959a3f9038fb938e0507b56ae39d36 | 11,211 | md | Markdown | articles/azure-monitor/app/asp-net.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/app/asp-net.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/app/asp-net.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Application Insights ile ASP.NET Web uygulaması analizi ayarlama | Microsoft Docs
description: Şirket içinde veya Azure'da barındırılan ASP.NET web siteniz için performans, kullanılabilirlik ve kullanıcı davranışı analizi araçlarını yapılandırın.
ms.topic: conceptual
ms.date: 05/08/2019
ms.openlocfilehash: 0843d6c04bf6fc9bab07207072990fb3fb8f1844
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/28/2020
ms.locfileid: "77665927"
---
# <a name="set-up-application-insights-for-your-aspnet-website"></a>ASP.NET web siteniz için Application Insights'ı ayarlama
Bu yordam ASP.NET web uygulamanızı [Azure Application Insights](../../azure-monitor/app/app-insights-overview.md) hizmetine telemetri gönderecek şekilde yapılandırır. Kendi IIS sunucunuzda şirket içi olarak veya Bulut’ta barındırılan ASP.NET uygulamaları için çalışır. Uygulamanızın performansını ve nasıl kullanıldığını anlamanıza yardımcı olan grafikler ve güçlü bir sorgu dilinin yanı sıra hata ya da performans sorunları hakkında otomatik uyarılar alırsınız. Çoğu geliştirici, özellikleri bu haliyle mükemmel bulsa da, gerekirse telemetriyi genişletip özelleştirebilirsiniz.
Visual Studio'da kurulum yalnızca birkaç tıklama ile yapılır. Telemetri hacmini sınırlayarak ücret doğmamasını sağlayabilirsiniz. Bu işlev, deneme ve hata ayıklama veya çok fazla kullanıcı ile bir site izlemek için izin verir. Devam edip üretim merkezinizi izlemeye karar verdiğinizde, sınırı daha sonra kolayca artırabilirsiniz.
## <a name="prerequisites"></a>Ön koşullar
Application Insights’ı ASP.NET web sitenize eklemek için şunu yapmanız gerekir:
- [Windows için Visual Studio 2019'u](https://www.visualstudio.com/downloads/) aşağıdaki iş yükleriyle yükleyin:
- ASP.NET ve web geliştirme (İsteğe bağlı bileşenlerin denetimini kaldırın)
- Azure geliştirme
Azure aboneliğiniz yoksa, başlamadan önce [ücretsiz](https://azure.microsoft.com/free/) bir hesap oluşturun.
## <a name="step-1-add-the-application-insights-sdk"></a><a name="ide"></a> 1. Adım: Application Insights SDK’yı ekleme
> [!IMPORTANT]
> Bu örnekteki ekran görüntüleri Visual Studio 2017 sürüm 15.9.9 ve sonraki sürüm dayanmaktadır. Uygulama Öngörüleri ekleme deneyimi Visual Studio sürümlerinin yanı sıra ASP.NET şablon türüne göre değişir. Eski sürümlerde "Uygulama Öngörülerini Yapılandır" gibi alternatif metinler olabilir.
Solution Explorer'da web uygulama adınızı sağ tıklatın ve Uygulama Öngörüleri **Telemetrisi Ekle'yi** > **Application Insights Telemetry** seçin
(Application Insights SDK sürümünüze bağlı olarak, son SDK sürümüne güncelleştirme yapmanız istenebilir. İstenirse **SDK’yı güncelleştir**’i seçin.)
Application Insights Yapılandırması ekranı:
**Başlat'ı**seçin.
Verilerin depolandığı kaynak grubunu veya konumu ayarlamak isterseniz **Ayarları yapılandır**'a tıklayın. Kaynak grupları, verilere erişimi denetlemek için kullanılır. Örneğin aynı sistemin parçalarını oluşturan birden uygulamanız varsa bunların Application Insights verilerini aynı kaynak grubuna ekleyebilirsiniz.
**Kaydol**’u seçin.
**Proje** > **Yönet NuGet Paketleri** > **Paket kaynağını seçin: nuget.org** > Application Insights SDK'nın en son kararlı sürümüne sahip olduğunuzu doğrulayın.
Telemetri hem hata ayıklama sırasında hem de uygulamanızı yayımladıktan sonra [Azure portalına](https://portal.azure.com) gönderilir.
> [!NOTE]
> Hata ayıklama sırasında portala telemetri göndermek istemiyorsanız, uygulamanıza Application Insights SDK’sını ekleyin, ancak portalda bir kaynak yapılandırmayın. Hata ayıklama sırasında telemetri verilerini Visual Studio'da görebilirsiniz. Daha sonra bu yapılandırma sayfasına dönebilir veya uygulamanızı dağıtana kadar bekleyip [telemetriyi çalışma zamanında açabilirsiniz](../../azure-monitor/app/monitor-performance-live-website-now.md).
## <a name="step-2-run-your-app"></a><a name="run"></a> 2. Adım: Uygulamanızı çalıştırma
F5 tuşuna basarak uygulamanızı çalıştırın. Farklı sayfalar açarak telemetri verileri oluşturun.
Visual Studio'da günlüğe kaydedilmiş etkinliklerin sayısını görürsünüz.
## <a name="step-3-see-your-telemetry"></a>Adım 3: Telemetrinize bakma
Visual Studio’da veya Application Insights web portalında telemetrinizi görebilirsiniz. Uygulamanızın hatalarını ayıklamanıza yardımcı olması için Visual Studio'da telemetri arayın. Sisteminiz canlıyken web portalında performans ve kullanımı izleyin.
### <a name="see-your-telemetry-in-visual-studio"></a>Visual Studio'da telemetrinize bakma
Visual Studio’da Application Insights verilerini görüntülemek için şunları yapın. **Çözüm Gezgini** > **Bağlantılı Hizmetler** > Sağ tıkla Application **Insights'ı**seçin ve ardından **Canlı Telemetri'yi Arayın'ı**tıklatın.
Visual Studio Application Insights Arama penceresinde, uygulamanızın sunucu tarafında oluşturulan telemetri için uygulamanızdan alınan veriler görünümü açılır. Filtrelerle denemeler yapın ve daha fazla ayrıntı için herhangi bir etkinliğe tıklayın.
> [!Tip]
> Herhangi bir veri gösterilmiyorsa zaman aralığının doğru olduğundan emin olup Ara simgesine tıklayın.
[Visual Studio’daki Application Insights araçları hakkında daha fazla bilgi edinin](../../azure-monitor/app/visual-studio.md).
<a name="monitor"></a>
### <a name="see-telemetry-in-web-portal"></a>Web portalında telemetriye bakma
Yalnızca SDK’yı yüklemeyi seçmediyseniz telemetriyi Application Insights web portalında da görüntüleyebilirsiniz. Portalda, Visual Studio’ya kıyasla daha çok grafik, analiz aracı ve bileşenler arası görünüm bulunur. Portal ayrıca uyarılar sağlar.
Application Insights kaynağınızı açın. [Azure portalında](https://portal.azure.com/) oturum açarak aradığınız öğeyi orada bulabilir veya **Çözüm Gezgini** > **Bağlı Hizmetler**’i seçip > **Application Insights** > **Application Insights Portal’ı aç**’a sağ tıklayarak sayfaya yönlendirilebilirsiniz.
Portal, uygulamanızdan alınan telemetri görünümünde açılır.
Daha fazla ayrıntı görmek için portalda istediğiniz kutucuğa veya grafiğe tıklayın.
## <a name="step-4-publish-your-app"></a>4. Adım: Uygulamanızı yayımlama
Uygulamanızı IIS sunucunuza veya Azure’a yayımlayın. Her şeyin sorunsuz çalıştığından emin olmak için [Canlı Ölçümler Akışı](../../azure-monitor/app/metrics-explorer.md#live-metrics-stream)’nı izleyin.
Telemetriniz, ölçümleri izleyebileceğiniz, telemetrinizi arayabildiğiniz Application Insights portalında biriker. Ayrıca, kullanımı ve performansı çözümlemek veya belirli olayları bulmak için güçlü [Kusto sorgu dilini](/azure/kusto/query/) de kullanabilirsiniz.
Telemetrinizi tanılama araması ve [eğilimler](../../azure-monitor/app/visual-studio-trends.md) gibi araçlarla [Visual Studio](../../azure-monitor/app/visual-studio.md)’da analiz etmeye de devam edebilirsiniz.
> [!NOTE]
> Uygulamanız [azaltma sınırlarına](../../azure-monitor/app/pricing.md#limits-summary) yaklaşmak için yeterli telemetri gönderiyorsa, otomatik [örnekleme](../../azure-monitor/app/sampling.md) etkinleştirilir. Örnekleme, tanılama amaçlı bağlantı verilerini korurken uygulamanızdan gönderilen telemetri miktarını azaltır.
>
>
## <a name="youre-all-set"></a><a name="land"></a>Hepiniz hazırsınız.
Tebrikler! Application Insights paketini uygulamanıza yüklediniz ve Azure üzerinde Application Insights hizmetine telemetri gönderecek şekilde yapılandırdınız.
Uygulamanızın telemetrisini alan Azure kaynağı bir *izleme anahtarı* ile tanımlanır. Bu anahtarı ApplicationInsights.config dosyasında bulabilirsiniz.
## <a name="upgrade-to-future-sdk-versions"></a>Gelecek SDK sürümlerine yükseltme
[SDK’nın yeni bir sürümüne](https://github.com/Microsoft/ApplicationInsights-dotnet-server/releases) yükseltme yapmak için, **NuGet paket yöneticisini** açıp yüklü paketleri filtreleyin. **Microsoft.ApplicationInsights.Web'i**seçin ve **Yükseltme'yi**seçin.
ApplicationInsights.config’de herhangi bir özelleştirme gerçekleştirdiyseniz yükseltmeden önce dosyanın bir kopyasını kaydedin. Daha sonra, yaptığınız değişiklikleri yeni sürümle birleştirin.
## <a name="video"></a>Video
* [Uygulama Öngörülerini sıfırdan bir .NET uygulamasıyla yapılandırma](https://www.youtube.com/watch?v=blnGAVgMAfA)hakkında harici adım adım video .
## <a name="next-steps"></a>Sonraki adımlar
İlginizi çekiyorsa inceleyebileceğiniz alternatif konu başlıkları da mevcuttur:
* [Çalışma zamanında bir web uygulamasını izleme](../../azure-monitor/app/monitor-performance-live-website-now.md)
* [Azure Cloud Services](../../azure-monitor/app/cloudservices.md)
### <a name="more-telemetry"></a>Daha fazla telemetri
* **[Tarayıcı ve sayfa yükleme verileri](../../azure-monitor/app/javascript.md)** - Web sayfalarınıza bir kod parçacığı ekleyin.
* **[Daha ayrıntılı bağımlılık ve özel durum izlemesi alın](../../azure-monitor/app/monitor-performance-live-website-now.md)** - Sunucunuza Durum İzleyicisi yükleyin.
* Kullanıcı eylemlerini saymak, zamanlamak veya ölçmek için **[özel olaylar kodlayın](../../azure-monitor/app/api-custom-events-metrics.md)**.
* **[Günlük verilerini alma](../../azure-monitor/app/asp-net-trace-logs.md)** - Günlük verilerini telemetrinizle ilişkilendirin.
### <a name="analysis"></a>Analiz
* **[Visual Studio’da Application Insights ile çalışma](../../azure-monitor/app/visual-studio.md)**<br/>Telemetri, tanılama araması ve kodun detayına gitme ile hata ayıklama hakkında bilgi içerir.
* **[Analytics](../../azure-monitor/log-query/get-started-portal.md)** - Güçlü sorgu dili.
### <a name="alerts"></a>Uyarılar
* [Kullanılabilirlik testleri](../../azure-monitor/app/monitor-web-app-availability.md): Sitenizin web’de görünür olduğundan emin olmaya yönelik testler oluşturun.
* [Akıllı tanılama](../../azure-monitor/app/proactive-diagnostics.md): Bu testler otomatik olarak çalıştığından, bunları ayarlamak için herhangi bir şey yapmanız gerekmez. Uygulamanızda olağan dışı oranda başarısız istek olup olmadığını bildirirler.
* [Metrik uyarılar](../../azure-monitor/app/alerts.md): Bir metrik bir eşiği geçerse sizi uyarmak için uyarılar ayarlayın. Bunları, uygulamanıza kodladığınız özel ölçümlerde ayarlayabilirsiniz.
### <a name="automation"></a>Automation
* [Application Insights kaynağı oluşturmayı otomatikleştirme](../../azure-monitor/app/powershell.md)
| 74.245033 | 578 | 0.801534 | tur_Latn | 0.998682 |
bcfa85fa4bc46b38eef48f11e5cddc9ffcd71617 | 66 | md | Markdown | README.md | marisa-inacio/calc-imc-c | b20829b84bcd42c12fc7911d232a7c754f329d82 | [
"MIT"
] | null | null | null | README.md | marisa-inacio/calc-imc-c | b20829b84bcd42c12fc7911d232a7c754f329d82 | [
"MIT"
] | null | null | null | README.md | marisa-inacio/calc-imc-c | b20829b84bcd42c12fc7911d232a7c754f329d82 | [
"MIT"
] | null | null | null | Calculadora de IMC em React e Bootstrap com componentes de Classe
| 33 | 65 | 0.833333 | por_Latn | 0.986035 |
bcfaf73c70201f0bdccfdcea7af6c0f14d704fcb | 3,013 | md | Markdown | rabbitMQ/readme.md | huynhp24/Project-Theia | cfc0eba342c27050905e0ec34267b37356bfa725 | [
"MIT"
] | null | null | null | rabbitMQ/readme.md | huynhp24/Project-Theia | cfc0eba342c27050905e0ec34267b37356bfa725 | [
"MIT"
] | 3 | 2021-04-23T18:00:00.000Z | 2021-05-03T21:41:26.000Z | rabbitMQ/readme.md | huynhp24/Project-Theia | cfc0eba342c27050905e0ec34267b37356bfa725 | [
"MIT"
] | null | null | null | # Installation
```
#!/bin/sh
## If sudo is not available on the system,
## uncomment the line below to install it
# apt-get install -y sudo
sudo apt-get update -y
## Install prerequisites
sudo apt-get install curl gnupg -y
## Install RabbitMQ signing key
curl -fsSL https://github.com/rabbitmq/signing-keys/releases/download/2.0/rabbitmq-release-signing-key.asc | sudo apt-key add -
## Install apt HTTPS transport
sudo apt-get install apt-transport-https
## Add Bintray repositories that provision latest RabbitMQ and Erlang 23.x releases
sudo tee /etc/apt/sources.list.d/bintray.rabbitmq.list <<EOF
## Installs the latest Erlang 23.x release.
## Change component to "erlang-22.x" to install the latest 22.x version.
## "bionic" as distribution name should work for any later Ubuntu or Debian release.
## See the release to distribution mapping table in RabbitMQ doc guides to learn more.
deb https://dl.bintray.com/rabbitmq-erlang/debian bionic erlang
## Installs latest RabbitMQ release
deb https://dl.bintray.com/rabbitmq/debian bionic main
EOF
## Update package indices
sudo apt-get update -y
## Install rabbitmq-server and its dependencies
sudo apt-get install rabbitmq-server -y --fix-missing
```
# Some Commands
### Looking at the queues
`sudo rabbitmqctl list_queues`
### Starting
`sudo service rabbitmq-server start`
### Stopping
`sudo service rabbitmq-server stop`
# Usage
## Overall
rabbitmq is used through python commands, as depicted in the python files rabbit-setup.py and rabbit-uploads-printer.py
### rabbit-setup.py
In this file, a connection is made using pika to the rabbitMQ server. Then, that channel is declared. With commands like `queue_declare`, queues are initialized within the rabbitMQ server and are ready to be used.
With a simple `basic_publish` command, data can be loaded into the queue, as you can see in the file.
### rabbit-uploads-printer.py
This file makes a connection the same as the setup.
However, with a `basic_consume` command, hooked up to a proper callback function, the script can start processing the data within the queue.
In this case, the script waits for an item in the queue, and runs the callback method to print it whenver it happens.
# Ports
```
beam.smp 458 rabbitmq 81u IPv4 22265 0t0 TCP *:25672 (LISTEN)
beam.smp 458 rabbitmq 94u IPv6 22761 0t0 TCP *:5672 (LISTEN)
epmd 841 rabbitmq 3u IPv4 22198 0t0 TCP *:4369 (LISTEN)
epmd 841 rabbitmq 4u IPv6 22199 0t0 TCP *:4369 (LISTEN)
```
These are the ports being used for rabbitmq. However, the command line and the python connection both make the connection automatically. The beam.smp are the rabbitmq service ports, while the epmd are just supplementary ones to manage nodes.
# Documentation
Please refer to the official documentation for connecting to rabbitMQ at the command line (rabbitmqctl) or more library functions to use in python.
https://www.rabbitmq.com/documentation.html
| 38.139241 | 241 | 0.747428 | eng_Latn | 0.961987 |
bcfc657487c2d4a5a2b8fc647be5216aeee96e84 | 5,446 | md | Markdown | _posts/2015-06-03-python-string-format.md | kuanghy/kuanghy.github.io | 5585b94d5ec568804208facfa46bde592958eec7 | [
"MIT"
] | 14 | 2017-06-21T06:06:47.000Z | 2021-10-11T10:07:08.000Z | _posts/2015-06-03-python-string-format.md | kuanghy/kuanghy.github.io | 5585b94d5ec568804208facfa46bde592958eec7 | [
"MIT"
] | 1 | 2018-09-12T09:42:39.000Z | 2018-09-18T11:44:17.000Z | _posts/2015-06-03-python-string-format.md | kuanghy/kuanghy.github.io | 5585b94d5ec568804208facfa46bde592958eec7 | [
"MIT"
] | 14 | 2016-09-20T19:28:29.000Z | 2020-07-11T13:04:10.000Z | ---
layout: post
title: Python 的字符串格式化操作
category: Python
keywords: Python string str format_string 字符串 格式化
tags: python
---
Python 的字符串格式化操作需要用到格式化操作符：`%`。Python 风格的字符串格式化非常类似于 C 语言里面的 `printf()` 函数的字符串格式化，甚至所用的符号都一样，都用百分号(%)，并且支持所有 printf() 式的格式化操作。语法如下:
> format_string % string_to_convert
format_string 为包含 `%` 的格式标记字符串，表1 中列出了可用的各种符号；string_to_convert 为要格式化的字符串，包含要转化、显示的变量，如果是两个以上，则需要用元组或字典。
<div style="text-align:center;"><b>表1 字符串格式化符号表</b></div>
| 格式化字符 | 转换方式 |
|:-----------|:----------------------------------------------------------------------|
| %c | 转换成字符(ASCII 码值,或者长度为一的字符串) |
| %r | 优先用 repr() 函数进行字符串转换 |
| %s | 优先用 str() 函数进行字符串转换 |
| %d / %i | 转成有符号十进制数 |
| %u | 转成无符号十进制数 |
| %o | 转成无符号八进制数 |
| %x / %X | (Unsigned)转成无符号十六进制数(x/X 代表转换后的十六进制字符的大 小写) |
| %e / %E | 转成科学计数法(e/E 控制输出 e/E) |
| %f / %F | 转成浮点数(小数部分自然截断) |
| %g / %G | %e 和 %f / %E 和 %F 的简写 |
| %% | 输出% |
Python 支持两种格式的输入参数。第一种是元组，这基本上是一种的 C 语言中 printf() 风格的转换参数集；另一种形式是字典形式，字典其实是一个 哈希键-值 对的集合，这种形式里面，key 是作为格式字符串出现，相对应的 value 值作为参数在进行转化时提供给格式字符串。
格式字符串既可以跟 print 语句一起用来向终端用户输出数据，又可以用来合并字符串形成新字符串，而且还可以直接显示到 GUI(Graphical User Interface) 界面上去。
可以对格式化进行更加细腻的控制，其格式如下：
```
%[(name)][flags][width].[precision]typecode
```
其中：
- `(name)` 在输入为字典时使用，为字典里对应的 key
- `flags` 可以有 +, -, ' ' 或 0。+表示添加正负符号，-表示左对齐，' '表示用空格填充，0表示使用 0 填充
- `width` 表示显示宽度
- `precision` 表示小数点后精度
- `typecode` 对应表1中的值
表2 总结了一些常用的格式字符和方法：
<div style="text-align:center;"><b>表2 格式化操作符辅助指令</b></div>
| 符号 | 作用 |
|:----------|:---------------------------------------------------------------------------------|
| * | 定义宽度或者小数点精度 |
| - | 用做左对齐 |
| `<space>` | 在正数前面显示空格 |
| # | 在八进制数前面显示零('0'),在十六进制前面显示'0x'或者'0X'(取决于用的是'x'还是'X') |
| 0 | 显示的数字前面填充‘0’而不是默认的空格 |
| % | '%%'输出一个单一的'%' |
| (var) | 映射变量(字典参数) |
| m.n | m 是显示的最小总宽度,n 是小数点后的位数(如果可用的话) |
字符串输出示例：
```python
# -*- coding: utf-8 -*-
intnum = 108
floatnum = 1234.567890
num = 123
print("十六进制输出：")
print("%x" % intnum)
print("%X" % intnum)
print("%#X" % intnum)
print("%#x" % intnum)
print("\n浮点数和科学记数法形式输出:")
print("%f" % floatnum) # 默认保留 6 为小数位
print("%.2f" % floatnum)
print("%E" % floatnum)
print("%e" % floatnum)
print("%g" % floatnum)
print("%G" % floatnum)
print("%e" % (1111111111111111111111111L))
print("\n整数和字符串输出:")
print("%+d" % 4)
print("%+d" % -4)
print("we are at %d%%" % 100)
print("Your host is: %s" % "earth")
print("Host: %s\tPort:%d" % ("mars", 80))
print("dec: %d/oct: %#o/hex: %#X" % (num, num, num))
print("MM/DD/YY = %02d/%02d/%d" % (2, 15, 67))
print("There are %(howmany)d %(lang)s Quotation Symbols" % {'lang': 'Python', 'howmany': 3})
```
输出结果：
```
十六进制输出：
6c
6C
0X6C
0x6c
浮点数和科学记数法形式输出:
1234.567890
1234.57
1.234568E+03
1.234568e+03
1234.57
1234.57
1.111111e+24
整数和字符串输出:
+4
-4
we are at 100%
Your host is: earth
Host: mars Port:80
dec: 123/oct: 0173/hex: 0X7B
MM/DD/YY = 02/15/67
There are 3 Python Quotation Symbols
```
在使用格式化操作符对字符串进行格式化时，有时候可能并不能满足我们的需求。在 Python2.4 之后，增加了 **新式的字符串模板 Template**。新式的字符串模板的优势是不用去记住所有的转换类型相关的细节，而是像现在 Shell 风格的脚本语言里面那样使用美元符号($)。
由于新式的字符串 Template 对象的引进使得 string 模块又重新活了过来，Template 对象有两个方法，substitute() 和 safe_substitute()。前者更为严谨，在 key 缺少的情况下它会报一个 KeyError 的异常出来，而后者在缺少 key 时，直接原封不动的把字符串显示出来.。
示例：
```python
>>> from string import Template
>>> s = Template('There are ${howmany} ${lang} Quotation Symbols')
>>> print s.substitute(lang='Python', howmany=3)
There are 3 Python Quotation Symbols
>>> print s.substitute(lang='Python')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python2.7/string.py", line 176, in substitute
return self.pattern.sub(convert, self.template)
File "/usr/lib/python2.7/string.py", line 166, in convert
val = mapping[named]
KeyError: 'howmany'
>>> print s.safe_substitute(lang='Python')
There are ${howmany} Python Quotation Symbols
```
**注：** 以上内容摘自《Python核心编程》一书，仅供学习参考。
在 Python 2.6 版本及以后，又新加入了一种字符串格式化方法，即给字符串对象增加了 **format** 方法，用于对字符串进行格式化，其使用方式与 Template 有些类似，只是不用再指定 $ 来标记替换位置。示例：
```python
>>> "The sum of 1 + 2 is {}".format(1+2)
'The sum of 1 + 2 is 3'
>>> "My name is {name}".format(name='Huoty')
'My name is Huoty'
```
而后，在 Python 3.6 上又加入了一种新的字符串格式化方法，这种方法算是对 str.format 方法的增强，即在格式化时可以自动从当前名字空间中查找变量并完成格式化，在定义字符串时只需再其前加上 `f` 标记。示例：
```python
>>> sum = 1 + 2
>>> f"The sum of 1 + 2 is {sum}"
'The sum of 1 + 2 is 3'
>>> name = "Huoty"
>>> f"My name is {name}"
'My name is Huoty'
```
| 32.035294 | 163 | 0.517077 | yue_Hant | 0.610528 |
bcfc670ca60064cbd900539238f6ebc315e23a1f | 1,055 | md | Markdown | src/0040. Combination Sum II.md | xindoo/leetcode | 70ca54ce05d0135283d96d9a1765bca40a8ed76b | [
"Xnet",
"X11"
] | 7 | 2017-11-15T15:18:45.000Z | 2021-11-05T16:45:23.000Z | src/0040. Combination Sum II.md | xindoo/leetcode | 70ca54ce05d0135283d96d9a1765bca40a8ed76b | [
"Xnet",
"X11"
] | null | null | null | src/0040. Combination Sum II.md | xindoo/leetcode | 70ca54ce05d0135283d96d9a1765bca40a8ed76b | [
"Xnet",
"X11"
] | null | null | null | ```java
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
class Solution {
public List<List<Integer>> combinationSum2(int[] candidates, int target) {
List<List<Integer>> ans = new ArrayList();
Arrays.sort(candidates);
dfs(ans, candidates, target, 0, new ArrayList<>());
return ans;
}
private void dfs(List<List<Integer>> ans, int[] candidates, int target, int idx, List<Integer> cur) {
if (target == 0) {
ans.add(new ArrayList<>(cur));
return;
}
if (idx >= candidates.length) {
return;
}
for (int i = idx; i < candidates.length; i++) {
if (target < candidates[i]) {
return;
}
cur.add(candidates[i]);
dfs(ans, candidates, target - candidates[i], i + 1, cur);
cur.remove(cur.size() - 1);
while (i + 1 < candidates.length && candidates[i] == candidates[i + 1]){
i++;
}
}
}
}
``` | 30.142857 | 105 | 0.5109 | eng_Latn | 0.241971 |
bcfc95f12a0159a6bd325571e41f295fd4d870d5 | 1,665 | md | Markdown | README.md | mavisyupyup1/readme-generator | 5faa8df8295fb0c4affeb0d37ece570ad9a31eed | [
"BSD-Source-Code"
] | 1 | 2021-11-26T20:01:29.000Z | 2021-11-26T20:01:29.000Z | README.md | mavisyupyup1/readme-generator | 5faa8df8295fb0c4affeb0d37ece570ad9a31eed | [
"BSD-Source-Code"
] | null | null | null | README.md | mavisyupyup1/readme-generator | 5faa8df8295fb0c4affeb0d37ece570ad9a31eed | [
"BSD-Source-Code"
] | null | null | null |
# README Generator
## Description
This is a command-line application that dynamically generates a professional README.md file from a user's input using the the [Inquirer package](https://www.npmjs.com/package/inquirer).
## Table of Contents
* [Installation](#installation)
* [Usage](#usage)
* [Testing](#testing)
* [Credits](#credits)
* [License](#license)
* [Questions](#questions)
## Built with
* JavaScript
* Node.js
* npm
## Installation
To install the package, go to project [github](https://github.com/mavisyupyup1/readme-generator) page. Click on the green "code" button to either clone or download the repo. Node.js is required to run the application. Use 'npm install' to install the required npm packages
## Usage
To use this application, go the terminal and navigate to the directory of this project, run `node index.js` in the command line and answer the questions prompted. Once all the question is answer, you will see a README file generated in './dist/README.md'
## Demo
https://watch.screencastify.com/v/FnzFokX0B3CP6nsRY3iQ
## Testing
n/a
## Credits
* [Inquirer package](https://www.npmjs.com/package/inquirer)
* [starter code](https://github.com/coding-boot-camp/potential-enigma)
## License
This application is licensed under mit. See link below for more details about the license(s).
* https://choosealicense.com/licenses/mit
## Questions?
* Check out my profile on Github: <a class="ml-2 my-1 px-2 py-1 bg-secondary text-dark" href="https://github.com/mavisyupyup1">mavisyupyup1</a>
* More questions, send me an email: gliu42@gmail.com
| 36.195652 | 273 | 0.746547 | eng_Latn | 0.848608 |
bcfd241c4c0f641b384e524c9d281148a230872b | 3,883 | md | Markdown | articles/redis-cache/cache-nodejs-get-started.md | OpenLocalizationTestOrg/azure-docs-pr15_fi-FI | fd5644538d5deb8abf20f8d401bd1741ff804a81 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/redis-cache/cache-nodejs-get-started.md | OpenLocalizationTestOrg/azure-docs-pr15_fi-FI | fd5644538d5deb8abf20f8d401bd1741ff804a81 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/redis-cache/cache-nodejs-get-started.md | OpenLocalizationTestOrg/azure-docs-pr15_fi-FI | fd5644538d5deb8abf20f8d401bd1741ff804a81 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Voit käyttää Azure Redis välimuistin Node.js | Microsoft Azure"
description="Azure Redis välimuistin Node.js ja node_redis käytön aloittaminen."
services="redis-cache"
documentationCenter=""
authors="steved0x"
manager="douge"
editor="v-lincan"/>
<tags
ms.service="cache"
ms.devlang="nodejs"
ms.topic="hero-article"
ms.tgt_pltfrm="cache-redis"
ms.workload="tbd"
ms.date="10/25/2016"
ms.author="sdanie"/>
# <a name="how-to-use-azure-redis-cache-with-nodejs"></a>Voit käyttää Azure Redis välimuistin Node.js
> [AZURE.SELECTOR]
- [.NET](cache-dotnet-how-to-use-azure-redis-cache.md)
- [ASP.NET](cache-web-app-howto.md)
- [Node.js](cache-nodejs-get-started.md)
- [Java](cache-java-get-started.md)
- [Python](cache-python-get-started.md)
Azure Redis välimuistin kautta pääset käsiksi suojattua ja erillinen Redis.txt välimuistiin, Microsoft hallitsee. Välimuistin on käytettävissä mistä tahansa sovelluksesta Microsoft Azure kuluessa.
Tässä ohjeaiheessa kerrotaan, miten Aloita Azure Redis välimuistin Node.js avulla. Toinen esimerkki Azure Redis välimuistin käyttäminen Node.js kohdassa [Muodosta Node.js Chat sovellus, jolla Socket.IO Azure-sivustossa](../app-service-web/web-sites-nodejs-chat-app-socketio.md).
## <a name="prerequisites"></a>Edellytykset
Asenna [node_redis](https://github.com/mranney/node_redis):
npm install redis
Tässä opetusohjelmassa käytetään [node_redis](https://github.com/mranney/node_redis). Esimerkkejä Node.js muiden asiakkaiden ohjeissa yksittäisten [Node.js Redis asiakkaiden](http://redis.io/clients#nodejs)on lueteltu Node.js asiakkaille.
## <a name="create-a-redis-cache-on-azure"></a>Luo Redis.txt välimuistin Azure
[AZURE.INCLUDE [redis-cache-create](../../includes/redis-cache-create.md)]
## <a name="retrieve-the-host-name-and-access-keys"></a>Noutaa host nimet ja avaimet
[AZURE.INCLUDE [redis-cache-create](../../includes/redis-cache-access-keys.md)]
## <a name="connect-to-the-cache-securely-using-ssl"></a>Yhteyden muodostaminen välimuistin suojatusti SSL-yhteys
[Node_redis](https://github.com/mranney/node_redis) uusimmat versiot tukevat Azure Redis välimuistin muodostaminen SSL-yhteys. Seuraavassa esimerkissä esitetään Azure Redis välimuistin muodostaminen käyttämällä 6380 SSL-päätepistettä. Korvaa `<name>` välimuistin nimellä ja `<key>` joko ensisijaisen tai toissijaisen avain kuin kuvattu [noutaa host nimet ja näppäimet](#retrieve-the-host-name-and-access-keys) edellisessä osassa.
var redis = require("redis");
// Add your cache name and access key.
var client = redis.createClient(6380,'<name>.redis.cache.windows.net', {auth_pass: '<key>', tls: {servername: '<name>.redis.cache.windows.net'}});
## <a name="add-something-to-the-cache-and-retrieve-it"></a>Lisää jotain välimuistin ja hakea sitä
Seuraavassa esimerkissä esitetään, kuinka Azure Redis välimuisti-esiintymään, tallentaa ja palauttaa kohteen välimuistista. Katso Lisää esimerkkejä Redis.txt käyttäminen [node_redis](https://github.com/mranney/node_redis) asiakkaan [http://redis.js.org/](http://redis.js.org/).
var redis = require("redis");
// Add your cache name and access key.
var client = redis.createClient(6380,'<name>.redis.cache.windows.net', {auth_pass: '<key>', tls: {servername: '<name>.redis.cache.windows.net'}});
client.set("key1", "value", function(err, reply) {
console.log(reply);
});
client.get("key1", function(err, reply) {
console.log(reply);
});
Tulos:
OK
value
## <a name="next-steps"></a>Seuraavat vaiheet
- [Käyttöön välimuistin diagnostiikka](cache-how-to-monitor.md#enable-cache-diagnostics) , niin voit [näytön](cache-how-to-monitor.md) välimuistin kunto.
- Lue virallinen [Redis ohjeissa](http://redis.io/documentation).
| 43.629213 | 429 | 0.732681 | fin_Latn | 0.878426 |
bcff0ca1e54920f1e4dd3ee7185b11d73b0dbf08 | 2,815 | md | Markdown | _death_bus/1181.md | Meniny/Fiction_DeathBus | 7cd5b097a050607530d2f98793664e7b5f2cc5ab | [
"MIT"
] | null | null | null | _death_bus/1181.md | Meniny/Fiction_DeathBus | 7cd5b097a050607530d2f98793664e7b5f2cc5ab | [
"MIT"
] | null | null | null | _death_bus/1181.md | Meniny/Fiction_DeathBus | 7cd5b097a050607530d2f98793664e7b5f2cc5ab | [
"MIT"
] | null | null | null | ---
layout: fiction
title: "复仇心切"
fiction: "death_bus"
index: 1181
next:
index: 1182
url: "1182"
previous:
index: 1180
url: "1180"
---
我已经被愤怒和仇恨冲昏了头脑，头也没回的飞回了玫瑰城，我没有使用隐身之术，毅然决然的站在城主府的大门外。我想要光明正大的杀了他们，为阿狗报仇雪恨。
之前我还想继续隐藏自己的身份，但计划赶不上变化，他们杀了阿狗，我绝对不会放过他们，能够让他们死，就不能让他们多活一秒。
屹立在大门外的我，很快被人给包围了，有修罗人，也有城内普通的护卫，一重紧接着一重，黑压压的一片都是人头。他们的气势冲天，这一次势必想要我的命。
在姓杜的母子没来之前，他们忍不住动了手，但让他们没有想到的是，我手掌一挥，一长道红光突然出现，瞬间便杀死几重人，他们都是人头落地，鲜红色的血液喷涌不停。无比浓重的血腥味，弥漫在夜空之中，我心里清楚，这将是一个杀戮之夜。
他们见我出手如此之狠，又如此之准，没有人再敢上前一步，甚至开始后退，不敢再轻易对我动手，免得像那些人一样，人头落地。
躺在地上的尸体，即便没有一千，也有八百。如果是普通之人还好说，关键是其中还包括不少的修罗人，他们可都是高手啊。高手在我面前，如今却是如此的不堪。我坚信，今晚只要我坚持下去，定可以将他们杀个片甲不留。
“刘明布，你真是好大的胆子，居然晚上还敢来这里。”杜逍飞出来了，他对着我大喊道。
我望着他怒道：“我是来找你们报仇的，你们的死期到了。”
杜逍飞冷笑一声道：“哼，死期到的人应该是你，而不是我们，几次都让你跑掉了，这次你休想。”
至于我的实力，杜逍飞领教过，他之所以这样说，一定是有了什么准备，但不管他有什么样的准备，今晚谁都挡不了我要杀他。所以，这下不等他们先动手，我便先动手了，而且攻击的目标是杜逍飞。谁要是敢阻拦我，谁就只有死路一条。
可让我没有想到的是，就在我靠近他的过程中，一个中年人从天而降，拦住了我的去路。此人看起来极为的阴邪，全身上下透着黑色之气，同时也能看出来，此人相当的强大，不是杜逍飞等人所能比的。
“你就是那个曾经名噪一时的明帝？”此人问我道。
“既然知道了，那就不要废话了。如果你不想死的话，就马上给我离开这里，否则你会死在这里。”我非常认真的道。
“哈哈，我活了那么多年，还从没有人跟我用这样的口气和方式说话，也从没输过谁，这次来我不光要阻止你做一切，我还要取了你的狗命。”说完，他便对我展开了进攻。
他进攻之时，身影浮动，忽隐忽现，时有时无，而且气势极为的强大，实力绝非一般。他的动作极快，出招极狠，若不是我反应极快，非得被他所伤。
他进攻，我防守，一来是想要摸一摸他的路子，二来是想试探一下他到底有多强。其他人没有加入打斗，让我们形成了单打独斗的局面，这应该就是他想要的。
他应该知道我强，但他绝对没有想到，我会那么的强，不是他一个人所能打败的。以他的实力来看，就算有十个他，也不是我的对手。
防守了良久，我开始进攻了，极为的疯狂。我打的他节节败退，最后他一招不慎，被我打中了他的胸口，将他打成重伤。他已经知道自己不是我的对手，所以他慌忙摆手道：“停一停！”
听到他说，我住了手，他接着道：“青出于蓝胜于蓝，后生可畏啊。今生能够遇到你这样的高手，我也是无憾了，我和你无怨无仇，没必要斗个你死我活的，所以我要告辞了，咱们后会有期。”
说完他便想离开这，但被我迅速给拦住了，我怒视着他道：“现在这里是我说了算，不是你想走就能走的。”
他意识到情况不妙，皱起眉头，有些颤抖的问道：“那你是什么意思？”
我非常果断的道：“我的意思早已经很明确，挡我者，死！所以，你得死！”
说着，我猛然间开出一掌，打向他的胸膛，而他反应够快，赶忙用手挡住了。但因为他受伤的缘故，这一掌看起来他挡住了，实际上掌力没有挡住，无比强劲的力道作用在他的身上，直接将他打飞了。
然而在他飞着的过程中，我又隔空一掌，接着便听到一声爆响，他的身体发生了爆炸，可以说是粉身碎骨。血肉骨头，犹如空中的大雨一般，洒落在人头之上。
可以说，杀死他，我不费吹灰之力。当然，我能够想到，杜逍飞刚才之所以那样说，以为他能够将我打败，但结果让他失望了。我清楚的看到，杜逍飞的脸色变了，明显是他怕了，怕我杀了他。反正不管他怕，还是不怕，他都要死，而且就在这不久的将来。
“你们都给我上，杀了他，谁要是能够杀了他，本少爷重重有赏。”杜逍飞对着众人大声喊道。
一声令下，让很多人对我群起而攻之，但是面对他们的进攻，我不急不缓。而是非常镇定的道：“万家灯火！”
这是神灯中的厉害一招，此招一出，大火将如流星一般，从天而降，扑向他们。这火看起来并不怎么可怕，但实际上非常可怕，一旦谁碰到了火，必然会被烧成灰烬，而且是在短时间内。
事实正如我所说，铺天盖地的大火，落到了太多人身上，明明看起来是火苗，可一旦落到他们的身上，便立马变成了焚身大火。一时之间，他们便手忙脚乱起来，想要扑灭自己身上的大火，但让他们没有想到的是，这火根本无法扑灭，而且越扑越大，最终大火笼罩住了他们的身体。
须臾的功夫，一缕缕的青烟飘向高空，他们在痛苦的嘶喊中死去，连具尸体都没有，直接化为了灰烬。
在城主府的大门口，前后左右以及空中，足有上万人。没错，我又是不费什么力气的解决了他们，他们该死，全部该死，他们死有余辜。
这时候的我，脑子里只有一个念想，那就是报仇，杀了这里所有该杀的人，特别是姓杜的母子。然而当我从大火中回过神来的时候，我忽然发现杜家母子不见了，他们应该是逃跑了，除了逃，现在他们已经无路可走，不然就是死路一条。
“阿布！”我转过身，想要追他们母子的时候，我听到了一个熟悉的声音，回头一看，是苏桢。她出来了，瞪大双眼望着我，一副欲言又止的样子。
“苏桢，你在这等着我，等我杀了他们就回来找你。”我道。
苏桢犹豫片刻，默默的点点头道：“你小心一点儿。”
接下来，我头也不回的追了过去，我用罗盘诀探知了他们的方向，所以他们逃不出我的手掌心。只要能够杀死他们，那我的仇恨就会消去很多，也算是对得起那些死去的人了。
当然，他们的仇并没有全报，因为仇人之中，还有帝王那边的人，以及修罗门的人，还有我那个既固执又倔强的儿子。关于儿子这边的仇，我只能昧着的良心愧对他们了，因为我实在没有办法去杀自己的儿子，相信每一个当爹的人，都不能做出这样的事。
杜家母子逃跑的速度很快，但还是快不过我，没用多长的时间，终究还是被我给拦住了去路。 | 32.356322 | 125 | 0.81421 | zho_Hans | 0.436304 |
4c0077d025861bab3235d18dbc0e42b947275ca6 | 1,456 | md | Markdown | fr_FR/plugins/devicecommunication/ikealight/index.md | henribi/documentations | cd87fb349b097d832453f37e44b9a1d4b8b7ad75 | [
"MIT"
] | 3 | 2020-05-17T19:20:29.000Z | 2021-11-25T03:51:15.000Z | fr_FR/plugins/devicecommunication/ikealight/index.md | henribi/documentations | cd87fb349b097d832453f37e44b9a1d4b8b7ad75 | [
"MIT"
] | 15 | 2020-05-26T13:57:05.000Z | 2022-01-03T17:04:09.000Z | fr_FR/plugins/devicecommunication/ikealight/index.md | henribi/documentations | cd87fb349b097d832453f37e44b9a1d4b8b7ad75 | [
"MIT"
] | 40 | 2020-03-11T16:47:52.000Z | 2022-03-01T17:37:24.000Z | # Plugin IkeaLight
Le plugin IkeaLight permet d’établir un lien avec la passerelle Ikea Tradfri. Vous pourrez contrôler vos lumières et avoir un retour d’état en temps réel.
# Configuration
## Configuration du plugin
Après téléchargement du plugin il vous faut l’activer et renseigner l’IP de votre passerelle ainsi que la clé disponible sur l’étiquette de la passerelle (le "Security code").
## Compatibilité
Vous pouvez trouver [ici](https://compatibility.jeedom.com/index.php?v=d&p=home&plugin=ikealight) la liste des modules compatible avec le plugin
## Détection des ampoules
Pour scanner les équipements Ikea, il suffit de démarrer le démon une fois les dépendances correctement installées.
Les ampoules remontées par la passerelle et qui sont reconnus par Jeedom seront automatiquement intégrées.
Si une ampoule ne remonte pas merci de mettre le plugin en ``Debug``, de relancer la découverte et de nous fournir la log afin que l’on puisse ajouter les ampoules manquantes. (Pensez à bien préciser le modèle de votre ampoule ainsi que ses caractéristiques dans le ticket : est elle dimmable, est elle variable en blanc, est elle variable en couleur). Le plugin vous remontera également les prises les stores
**Une fois decouverte chaque ampoule aura :**
- Les actions correspondantes
- Les infos correspondantes
>**SYMFONISK**
>
>Les enceintes connectées Symfonisk ne sont pas gerées par ce plugin mais par le plugin Sonos.
| 48.533333 | 409 | 0.788462 | fra_Latn | 0.994896 |
4c00db7d2ae861f6e67880071c1563f9eb04d727 | 641 | md | Markdown | source/_posts/other/node-gyp安装.md | lingchenzheng/lingchenzheng.github.io | 48354e286a37e68fc3283cc928c6c17e595c89f8 | [
"MIT"
] | 1 | 2020-08-16T11:48:15.000Z | 2020-08-16T11:48:15.000Z | source/_posts/other/node-gyp安装.md | lingchenzheng/lingchenzheng.github.io | 48354e286a37e68fc3283cc928c6c17e595c89f8 | [
"MIT"
] | null | null | null | source/_posts/other/node-gyp安装.md | lingchenzheng/lingchenzheng.github.io | 48354e286a37e68fc3283cc928c6c17e595c89f8 | [
"MIT"
] | null | null | null | ---
title: node-gyp安装
category: 其他
tag: 工具
---
##### 介绍
node-gyp，是由于node程序中需要调用一些其他语言编写的 工具 甚至是dll，需要先编译一下，否则就会有跨平台的问题，例如在windows上运行的软件copy到mac上就不能用了，但是如果源码支持，编译一下，在mac上还是可以用的。node-gyp在较新的Node版本中都是自带的（平台相关），用来编译原生C++模块。
##### node-gyp的依赖
以windows为例
通过命令行一键安装
```shell
npm install --global --production windows-build-tools
```
`windows-build-tools`会安装如下包
- python2.7(不支持3.x)
- visual C++ Build Tools(vistual studio2015及以上)
- .net framework 4.5.1
注意：需要以管理的方式运行上面的命令。
##### 安装node-gyp
```shell
npm i -g node-gyp
```
注意：安装`node-gyp`之前，确认`node`是32位的，如果你的电脑安装的是64位的，可以通过nvm来安装管理node版本。
##### 验证是否安装完成
```shell
node-gyp list
```
| 15.634146 | 163 | 0.723869 | yue_Hant | 0.483647 |
4c01b47632bf8b66629c58dc56abe91726e21875 | 63 | md | Markdown | pygameMenuPro/README.md | achiyazigi/pygameMenuPro | d9bfaa42e6dd3035de06bdf04dd476ffec4fd3c2 | [
"MIT"
] | null | null | null | pygameMenuPro/README.md | achiyazigi/pygameMenuPro | d9bfaa42e6dd3035de06bdf04dd476ffec4fd3c2 | [
"MIT"
] | null | null | null | pygameMenuPro/README.md | achiyazigi/pygameMenuPro | d9bfaa42e6dd3035de06bdf04dd476ffec4fd3c2 | [
"MIT"
] | null | null | null | # pygame-menu-pro
create a pygame menu fast without compromise
| 21 | 44 | 0.809524 | eng_Latn | 0.955203 |
4c01c1ee857ee69df17d2140f4af5d6b8b4ac839 | 4,336 | markdown | Markdown | README.markdown | nicolasembleton/NEVersionCompare | 9c9e9b97cd00b0a4fc56f966e721262593f0460e | [
"BSD-2-Clause-FreeBSD"
] | 2 | 2015-05-26T10:08:11.000Z | 2016-01-27T19:06:30.000Z | README.markdown | nicolasembleton/NEVersionCompare | 9c9e9b97cd00b0a4fc56f966e721262593f0460e | [
"BSD-2-Clause-FreeBSD"
] | null | null | null | README.markdown | nicolasembleton/NEVersionCompare | 9c9e9b97cd00b0a4fc56f966e721262593f0460e | [
"BSD-2-Clause-FreeBSD"
] | null | null | null | NEVersionCompare
================
A tiny Obj-c library for easy version comparisons.
Current version: *1.0.0*
Setup
-----
1. Drag&drop the NEVersionCompare folder to your XCode project
2. Import the .h file using: *#import "NEVersionCompare.h"*
You're done!
Typical Usage
-------------
This is how you create a typical NEVersionCompare object:
NEVersionCompare *myVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1.0.3.550"];
Advanced Use Case on iOS project
--------------------------------
### Popup an Alert View to your iOS app user when you release a new version and redirect them to the AppStore
// Use Case: Test version at application opening time
// File: AppDelegate.m
// Requirement: Your class has to register to UIAlertViewDelegate by using <UIAlertViewDelegate>
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
/* Test cases //
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1"];
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1.0"];
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1.3"];
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1.399"];
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1.0.33"];
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1.0.2.5339"];
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1.0.3"];
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"I made a mistake!!! :)"];
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:[[[NSBundle mainBundle] infoDictionary] objectForKey:@"CFBundleVersion"]];
*/
// This line gets the current Application version number ( useful to compare against new versions )
NEVersionCompare *appVersion = [[NEVersionCompare alloc] initWithFullTextVersion:[[[NSBundle mainBundle] infoDictionary] objectForKey:@"CFBundleVersion"]];
// Typically get the latest available version from a .txt file somewhere on your server,
// Remember to take care if Internet is available or not!
NSString *onlineVersionString = [[NSString alloc] initWithContentsOfURL:[NSURL URLWithString:@"http://www.myserver.com/apps/myapp/version.txt"] encoding:NSUTF8StringEncoding error:nil];
NEVersionCompare *updatedVersion = [[NEVersionCompare alloc] initWithFullTextVersion:onlineVersionString];
// Or simply enter by hand ( not recommended though )
// NEVersionCompare *updatedVersion = [[NEVersionCompare alloc] initWithFullTextVersion:@"1.0.3.550"];
NSLog(@"Compare gave the result: %i ", [appVersion compareWith:updatedVersion withBuild:NO]);
if([appVersion compareWith:updatedVersion] == NEVersionSmallerThan) {
UIAlertView *alertView = [[UIAlertView alloc] initWithTitle:@"Your Version is outdated"
message:@"A newer, greater version is available on the appStore, please click \"Open AppStore\" to go to the update process. Enjoy!"
delegate:self
cancelButtonTitle:@"Close"
otherButtonTitles:@"Open AppStore", nil];
[alertView show];
}
// Then you can easily implement UIAlertView delegate to open the AppStore with your application
#pragma mark -
#pragma mark UIAlertViewDelegate implementation
- (void)alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex {
NSLog(@"A button was clicked: %i", buttonIndex);
if(buttonIndex == 1) {
// Opens the appStore
NSURL *appStore = [[NSURL alloc] initWithString:@"itms-apps://itunes.com/apps/{APPLICATION-NAME}"];
[[UIApplication sharedApplication] openURL:appStore];
}
}
Supported Patterns
------------------
Pretty much all patterns are supported, except that you have to use periods (".") as a separator
Like:
* XXX
* XXX.XXX
* XXX.XXX.XX
* XXX.XXX.XXX.XXX
* XXX.Whateverwillnotbetakenintoaccountanyway
| 46.623656 | 190 | 0.695111 | kor_Hang | 0.343719 |
4c01ebd96dee0884db8b6441646b8b2945b18a43 | 122 | md | Markdown | CONTRIBUTING.md | forrestang/MemoryGame | 2c44f0e3a4e5fa37fd03600d652287c26a5efcb6 | [
"MIT"
] | null | null | null | CONTRIBUTING.md | forrestang/MemoryGame | 2c44f0e3a4e5fa37fd03600d652287c26a5efcb6 | [
"MIT"
] | null | null | null | CONTRIBUTING.md | forrestang/MemoryGame | 2c44f0e3a4e5fa37fd03600d652287c26a5efcb6 | [
"MIT"
] | null | null | null | # How to contribute
I can barely use github at this point, it will be a while before I have contribution instructions :(
| 30.5 | 100 | 0.770492 | eng_Latn | 0.999988 |
4c028a465c3b111ded9c508582ffa69a5f36162e | 5,679 | md | Markdown | docs/user_guides/tfm_integration_guide.md | jlwatson/trusted-firmware-m | 073ee8a497deb5866d70237f390d0c14b6d3521e | [
"BSD-3-Clause"
] | null | null | null | docs/user_guides/tfm_integration_guide.md | jlwatson/trusted-firmware-m | 073ee8a497deb5866d70237f390d0c14b6d3521e | [
"BSD-3-Clause"
] | null | null | null | docs/user_guides/tfm_integration_guide.md | jlwatson/trusted-firmware-m | 073ee8a497deb5866d70237f390d0c14b6d3521e | [
"BSD-3-Clause"
] | null | null | null | # TF-M integration guide
The purpose of this document is to provide a guide on how to integrate TF-M with
other hardware platforms and operating systems.
## How to build TF-M
Follow the [Build instructions](tfm_build_instruction.md).
## How to export files for building non-secure applications
Explained in the [Build instructions](tfm_build_instruction.md).
## How to add a new platform
The hardware platforms currently supported are:
* Soft Macro Model (SMM) Cortex-M33 SSE-200 subsystem for MPS2+ (AN521)
* Cortex-M23 IoT Kit subsystem for MPS2+ (AN519)
* Musca-A test chip board (Cortex-M33 SSE-200 subsystem)
* Musca-B1 test chip board (Cortex-M33 SSE-200 subsystem)
The files related to the supported platforms are contained under the `platform`
subfolder. The platform specific files are under `platform/ext/target`, which is
organized by boards (e.g. `platform/ext/target/mps2`), while the folder
`platform/ext/common` is used to store source and header files which are
platform generic.
More information about subsystems supported by the MPS2+ board can be found in:
[MPS2+ homepage](https://developer.arm.com/products/system-design/development-boards/fpga-prototyping-boards/mps2)
More information about the Musca-A test chip board can be found in:
[Musca-A homepage](https://developer.arm.com/products/system-design/development-boards/iot-test-chips-and-boards/musca-a-test-chip-board)
More information about the Musca-B1 test chip board can be found in:
[Musca-B1 homepage](https://www.arm.com/products/development-tools/development-boards/musca-b1-iot)
#### generic drivers and startup/scatter files
The addition of a new platform means the creation of a new subfolder inside
`target/<board_name>` to provide an implementation of the drivers currently used
by TF-M, in particular MPC, PPC, and USART drivers. In addition to the drivers,
startup and scatter files need to be provided for the supported toolchains.
There are also board specific drivers which are used by the board platform to
interact with the external world, for example during tests, that have to be
provided, e.g. to blink LEDs or count time in the MPS2 board.
`Note: Currently SST and BL2 bootloader use different flash interface`
#### target configuration files
Inside the base root folder of the selected target, each implementation has to
provide its own copy of `target_cfg.c/.h`. This file has target specific
configuration functions and settings that are called by the TF-M during the
platform configuration step during TF-M boot. Examples of the configurations
performed during this phase are the MPC configuration, the SAU configuration,
or eventually PPC configuration if supported by the hardware platform.
Similarly, the `uart_stdout.c` is used to provide functions needed to redirect
the stdout on UART (this is currently used by TF-M to log messages).
#### platform retarget files
An important part that each new platform has to provide is the set of retarget
files which are contained inside the `retarget` folder. These files define the
peripheral base addresses for the platform, both for the secure and non-secure
aliases (when available), and bind those addresses to the base addresses used by
the devices available in the hardware platform.
## How to integrate another OS
To work with TF-M, the OS needs to support the Armv8-M architecture and,
in particular, it needs to be able to run in the non-secure world. More
information about OS migration to the Armv8-M architecture can be found in the
[OS requirements](os_migration_guide_armv8m.md). Depending upon the system
configuration this may require configuring drivers to use appropriate address
ranges.
#### interface with TF-M
The files needed for the interface with TF-M are exported at the
`<build_dir>/install/export/tfm` path. The NS side is only allowed to call TF-M
secure functions (veneers) from the NS Thread mode. For this reason, the API is
a collection of functions in the `<build_dir>/install/export/tfm/inc`
directory. For example, the interface for the Secure STorage (SST) service
is described in the file `psa_sst_api.h` as a collection of
functions that call service veneer functions. This API is a wrapper for the
secure veneers, and returns the return value from the service to the caller.
The secure storage service uses a numerical ID, to identify the clients that use
the service. For details see
[ns client identification documentation](tfm_ns_client_identification.md).
#### interface with non-secure world regression tests
A non-secure application that wants to run the non-secure regression tests
needs to call the `tfm_non_secure_client_run_tests()`. This function is
exported into the header file `test_framework_integ_test.h` inside the
`<build_dir>/install` folder structure in the test specific files, i.e.
`<build_dir>/install/export/tfm/test/inc`. The non-secure regression tests are
precompiled and delivered as a static library which is available in
`<build_dir>/install/export/tfm/test/lib`, so that the non-secure application
needs to link against the library to be able to invoke the
`tfm_non_secure_client_run_tests()` function. The SST non-secure side regression
tests rely on some OS functionality e.g. threads, mutexes etc. These functions
comply with CMSIS RTOS2 standard and have been exported as thin wrappers defined
in `os_wrapper.h` contained in `<build_dir>/install/export/tfm/test/inc`. OS
needs to provide the implementation of these wrappers to be able to run the
tests.
#### NS client Identification
See [ns client identification documentation](tfm_ns_client_identification.md).
--------------
*Copyright (c) 2017-2019, Arm Limited. All rights reserved.*
| 56.227723 | 137 | 0.796091 | eng_Latn | 0.997627 |
4c029ab15d6ba579db0910c7ddf29491fc28e1f0 | 1,303 | markdown | Markdown | _posts/publications/2014-06-21-KROC14.markdown | ggory15/ggory15.github.io | dc2dbaca9e856913f8c3c8951fc3cc64f2d8352f | [
"MIT"
] | null | null | null | _posts/publications/2014-06-21-KROC14.markdown | ggory15/ggory15.github.io | dc2dbaca9e856913f8c3c8951fc3cc64f2d8352f | [
"MIT"
] | null | null | null | _posts/publications/2014-06-21-KROC14.markdown | ggory15/ggory15.github.io | dc2dbaca9e856913f8c3c8951fc3cc64f2d8352f | [
"MIT"
] | 2 | 2019-01-07T08:21:04.000Z | 2021-03-10T11:39:36.000Z | ---
published: true
layout: post
title: Estimation of Hand Posture and Grasping Force Using Surface EMG
author: J. Lee, M. Kim, Sanghyun Kim, and J. Park
name: The 9th Korea Robotics Society Annual Conference (KROC)
state: accepted
year: 2014
type: Domestic_conference
date: 2014-06-21 7:00:00 -0400
permalink: /kroc141
categories: publications
tags: Robot_Hand, EMG
excerpt: This article is accepted in the 9th Korea Robotics Society Annual Conference (KROC).
image: /assets/img/post-images/slider-images/NO.jpg
imageAlt: HQP logo
image-slider: /assets/img/post-images/slider-images/NO.jpg
pdf: http://dyros.snu.ac.kr/wp-content/plugins/uploadingdownloading-non-latin-filename/download.php?id=2295
sourcecode:
---
### Abstract
인간의 손을 이용한 로봇 핸드의 원격조작을 원활히 수행하기 위해서, 인간의 의도를 파악하여 로봇 핸드에 전송하는
알고리즘의 구축은 필수적이다. 이 때 인간의 의도는 손의 파지 자세 및 파지력 추정을 통하여 파악 할 수 있다. 본 논
문에서는 여러 개의 표면 근전도 센서를 사용하여 각각의 파지자세에서 발현되는 근육 활성도를 통한 전완근의 근육 시
너지를 추출한다. 각 자세에서 추출한 근육 시너지를 기반으로 전처리되지 않은 임의의 파지자세를 추정하고 해당 파지
자세에서 파지력을 추정하는 방법을 제안한다. 실험을 통하여 다양한 파지자세에서의 근육 시너지를 추출하였고 이를 통
해 파지자세 추정, 파지력 추정 성능을 검증하였다.
### PDF
[**PDF file**](http://dyros.snu.ac.kr/wp-content/plugins/uploadingdownloading-non-latin-filename/download.php?id=2295)
### See More
Please visit [**Robot Hand project**]({{ site.url}}/robothand-project).
| 32.575 | 118 | 0.751343 | kor_Hang | 0.999945 |
4c02cfac640e8cad7561853c2b0b0c83895b8a93 | 70 | md | Markdown | exercises/practice/macros/.docs/instructions.append.md | sm1215/rust | bb90986674ea9f3541af76e53a8a58d19bca36f2 | [
"MIT"
] | 787 | 2017-06-29T23:38:15.000Z | 2022-03-31T06:05:56.000Z | exercises/practice/macros/.docs/instructions.append.md | sm1215/rust | bb90986674ea9f3541af76e53a8a58d19bca36f2 | [
"MIT"
] | 795 | 2017-06-18T17:08:32.000Z | 2022-03-18T11:52:44.000Z | exercises/practice/macros/.docs/instructions.append.md | sm1215/rust | bb90986674ea9f3541af76e53a8a58d19bca36f2 | [
"MIT"
] | 391 | 2017-06-25T09:44:54.000Z | 2022-03-30T15:01:51.000Z | # Compatibility
Note that this exercise requires Rust 1.36 or later.
| 17.5 | 52 | 0.785714 | eng_Latn | 0.997812 |
4c0485696a5e5dcbff790ef64cd4e8007b426b7c | 4,788 | md | Markdown | README.md | TurtleBot-Mfg/ros-system-daemon-hydro | 4166da41d728f602ebd8ef4a613b5decdcbdb37f | [
"BSD-3-Clause"
] | null | null | null | README.md | TurtleBot-Mfg/ros-system-daemon-hydro | 4166da41d728f602ebd8ef4a613b5decdcbdb37f | [
"BSD-3-Clause"
] | 1 | 2015-11-09T08:14:07.000Z | 2015-11-11T23:47:35.000Z | README.md | TurtleBot-Mfg/ros-system-daemon-hydro | 4166da41d728f602ebd8ef4a613b5decdcbdb37f | [
"BSD-3-Clause"
] | 1 | 2019-06-27T03:22:06.000Z | 2019-06-27T03:22:06.000Z | # ROS system daemon for Hydro
This package provides functionality for automatically starting/stopping ROS
## ROS System User
Username: ros
Home Directory: /var/lib/ros
Group: ros
Shell: /bin/sh
*ros* should be a member of group *dialout* to access serial ports.
```chown -R ros:ros /var/lib/ros```
```chmod 2775 /var/lib/ros```
ROS Log Dir: /var/log/ros
ROS PID: /var/run/ros/roscore.pid
## Startup and shutdown
Startup and shutdown is controlled by an upstart script that can be auto-configured via D-Bus communication with Network Manager. It also supports manual overrides by setting ```ROS_IP``` and ```ROS_INTERFACE``` in ```/etc/ros/setup.bash``` or ```/etc/ros/envvars```. ROS is started when upstart receives a *net-device-up* signal and it is stopped when a network interface stops.
Future work will resolve the issue where ROS starts connected to *eth0* and the machine is also equipped with a WiFi interface. In this case the state of the WiFi device should not produce a stop/start event effecting ROS.
For this we plan to separate the upstart scripts into two packages
* *ros-system-upstart-lan-hydro*
* *ros-system-upstart-wan-hydro*
These packages will provide *ros-system-upstart-hydro* for dependency management.
### ros-system-daemon-hydro.ros.upstart
* Config file ```/etc/init/ros.conf```
* ```start on net-device-up IFACE!=lo```
* ```stop on platform-device-changed```
* Check/update ownership & permissions of ```/var/run/ros```
* Autoconf network ```ROS_IP=`ros-network ip````
* Start via 'setuidgid ros rosctl start'
* Stop via 'setuidgid ros rosctl stop'
## System-wide Logging
Log Dir: /var/log/ros
chown -R ros:ros /var/log/ros
chmod 2775 /var/log/ros
### ros-system-daemon-hydro.ros.logrotate
* Config file ```/etc/logrotate.d/ros```
* Rotate logs daily *.log -> *.log.1 -> *.log.2 -> etc
* Compress the previous days logs daily *.log.2 -> *.log.2.gz
* Keep up to one weeks logs for an active rosmaster
* Archive inactive log subdirectories daily
* Remove archived logs older than one week
* Rotation currently done by copying and truncating the active log
Note: 01 Jan 2013 Sending SIGHUP to the ROS does not cause it to write to a new log.
<https://github.com/ros/ros_comm/issues/45>
## Files
### /usr/sbin/rosctl
Modelled after ```apachectl```, this script allows ros to be started
locally by users or system-wide by user *ros*.
The script will attempt to source configuration files as follows
* ```/etc/ros/setup.bash```
* ```/opt/ros/$ROS_DISTRO/setup.bash```
* ```/opt/ros/hydro/setup.bash```
If ```rosctl``` is run as user *ros* it will attempt to launch ```/etc/ros/robot.launch``` or the launch file specified in ```ROS_LAUNCH``` if it exists.
The PID file will be written to ```ROS_PID``` if it is set or ```/var/run/ros/roscore.pid``` or if it run as a local user it will be written to ```~/.ros/roscore-11311.pid``` or similar.
If ```gnome-session``` is running, the script will attempt to send desktop notifications via ```notify-send``` to the user that is logged in when ROS starts or stops.
Sub-commands
* start - Start ROS (roscore + default launch file)
* stop - Stop ROS (rosnode kill nodes then killall roslaunch)
* restart - Start followed by Stop
* status - Display the PID and user running ROS
In the near future running this as script as root will check/repair directory permissions and re-run itself setuidgid ros. Also, when run as root it should issue a warning and run ```initctl stop ros``` to prevent upstart from respawning. It may also be worth issuing a warning when run as *ros* and ```initctl status ros``` shows that upstart will respawn the process.
### /usr/sbin/ros-network
This tool autodetects network settings by querying NetworkManager via D-Bus. Autoconf can be overridden by setting ```ROS_IP``` and ```ROS_INTERFACE```.
Sub-commands
* interface - Outputs the primary interface name (wlan0, eth0, etc)
* ip - Outputs the ipv4 address of the primary network connection
* ssid - If WiFi connection, provide ssid of access point
In the event of autoconf failure, the script returns ```lo``` for the interface name and ```127.0.0.1``` for the ip address.
Eventually we would like this tool to be able to provide an automatic configuration of the ```ROS_MASTER_URI``` when a user logs in.
### /etc/ros/envvars
The idea behind using this instead of modifying setup.ash is that if the file only contains environmental variables it can be parsed and edited by hardware vendor install scripts.
## Special Thanks
The program ```rosctl``` was inspired by ```apachectl```
Package was influenced by the alternate approach used by
Thomas Moulard <thomas.moulard@gmail.com> on ros_comm_upstart
| 48.857143 | 379 | 0.724728 | eng_Latn | 0.989654 |
4c04f15fa0842dbb56731ae7edf6b7ee92578c0f | 231 | md | Markdown | README.md | samschmalz/class_notes | 97b9e191d9924eace70cb7a5082066aa4feff2aa | [
"Unlicense"
] | null | null | null | README.md | samschmalz/class_notes | 97b9e191d9924eace70cb7a5082066aa4feff2aa | [
"Unlicense"
] | null | null | null | README.md | samschmalz/class_notes | 97b9e191d9924eace70cb7a5082066aa4feff2aa | [
"Unlicense"
] | null | null | null | This is just a repository for my university class notes.
Notes are taken with the CherryTree note-taking tool, and stored in an unencrypted XML-formatted file. This repository simply allows me to sync my notes between computers.
| 57.75 | 172 | 0.809524 | eng_Latn | 0.999882 |
4c0591cd3b4cbc3072c0a17d0543e333635f0041 | 2,667 | md | Markdown | translations/es-ES/content/github/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md | JoyChannel/docs | 2d85af3d136df027c5e9230cac609b3712abafb3 | [
"CC-BY-4.0",
"MIT"
] | 17 | 2021-01-05T16:29:05.000Z | 2022-02-26T09:08:44.000Z | translations/es-ES/content/github/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md | moonlightnigh/docs | 37b2dc7444c4f38bd089298a097a755dd0df46ab | [
"CC-BY-4.0",
"MIT"
] | 116 | 2021-10-13T00:58:04.000Z | 2022-03-19T23:23:44.000Z | translations/es-ES/content/github/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md | moonlightnigh/docs | 37b2dc7444c4f38bd089298a097a755dd0df46ab | [
"CC-BY-4.0",
"MIT"
] | 3 | 2021-08-31T03:18:06.000Z | 2021-10-30T17:49:09.000Z | ---
title: Acerca de los modelos de desarrollo colaborativo
intro: El modo en que usas las solicitudes de extracción depende del tipo de modelo de desarrollo que uses en tu proyecto. Puedes utilizar el modelo de bifurcación y extracción o el modelo de repositorio compartido.
redirect_from:
- /github/collaborating-with-issues-and-pull-requests/getting-started/about-collaborative-development-models
- /articles/types-of-collaborative-development-models/
- /articles/about-collaborative-development-models
- /github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models
versions:
free-pro-team: '*'
enterprise-server: '*'
github-ae: '*'
topics:
- Pull requests
---
### Modelo de bifurcación y extracción
En el modelo de bifurcación y extracción, cualquiera puede bifurcar un repositorio existente y subir los cambios a su bifurcación personal. No necesitas permiso del repositorio fuente para subir información a una bifurcación que sea propiedad del usuario. El mantenedor del proyecto puede extraer los cambios hacia el repositorio de origen. Cuando abres una solicitud de extracción que proponga cambios desde la bifurcación que es propiedad de tu usuario para ramificar en el repositorio fuente (ascendente), puedes permitir que cualquiera con acceso de escritura en éste haga cambios en dicha solicitud. Este modelo es muy usado con los proyectos de código abierto, ya que reduce la cantidad de fricción para los colaboradores nuevos y le permite a las persona trabajar de forma independiente sin una coordinación inicial.
{% tip %}
**Sugerencia:** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %}
{% endtip %}
### Modelo de repositorio compartido
En el modelo de repositorio compartido, se le otorga a los colaboradores acceso de escritura a un único repositorio compartido y las ramas de tema son creadas cuando es necesario hacer cambios. Las solicitudes de extracción son útiles en este modelo ya que inician la revisión de código y el debate general acerca de un conjunto de cambios antes de que los mismos sean fusionados en la rama de desarrollo principal. Este modelo es más frecuente con las organizaciones y los equipos pequeños que colaboran en proyectos privados.
### Leer más
- "[Acerca de las solicitudes de extracción](/articles/about-pull-requests)"
- "[Crear una solicitud de extracción desde una bifurcación](/articles/creating-a-pull-request-from-a-fork)"
- "[Permitir cambios en una rama de solicitud de extracción creada desde una bifurcación](/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)"
| 74.083333 | 824 | 0.79865 | spa_Latn | 0.993085 |
4c05a30df11ea049b67f1e35fc2d299803424bec | 5,223 | md | Markdown | docs/build/reference/fa-fa-listing-file.md | asklar/cpp-docs | c5e30ee9c63ab4d88b4853acfb6f084cdddb171f | [
"CC-BY-4.0",
"MIT"
] | 14 | 2018-01-28T18:10:55.000Z | 2021-11-16T13:21:18.000Z | docs/build/reference/fa-fa-listing-file.md | asklar/cpp-docs | c5e30ee9c63ab4d88b4853acfb6f084cdddb171f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/build/reference/fa-fa-listing-file.md | asklar/cpp-docs | c5e30ee9c63ab4d88b4853acfb6f084cdddb171f | [
"CC-BY-4.0",
"MIT"
] | 2 | 2018-11-01T12:33:08.000Z | 2021-11-16T13:21:19.000Z | ---
title: "/FA, /Fa (Listing File) | Microsoft Docs"
ms.custom: ""
ms.date: "11/04/2016"
ms.reviewer: ""
ms.suite: ""
ms.technology: ["cpp-tools"]
ms.tgt_pltfrm: ""
ms.topic: "article"
f1_keywords: ["VC.Project.VCCLWCECompilerTool.AssemblerListingLocation", "VC.Project.VCCLCompilerTool.ConfigureASMListing", "VC.Project.VCCLWCECompilerTool.AssemblerOutput", "VC.Project.VCCLCompilerTool.AssemblerListingLocation", "/fa", "VC.Project.VCCLCompilerTool.AssemblerOutput", "VC.Project.VCCLCompilerTool.UseUnicodeForAssemblerListing"]
dev_langs: ["C++"]
helpviewer_keywords: ["FA compiler option [C++]", "/FA compiler option [C++]", "-FA compiler option [C++]", "listing file type", "assembly-only listing"]
ms.assetid: c7507d0e-c69d-44f9-b8e2-d2c398697402
caps.latest.revision: 12
author: "corob-msft"
ms.author: "corob"
manager: "ghogen"
---
# /FA, /Fa (Listing File)
Creates a listing file containing assembler code.
## Syntax
> **/FA**[**c**\][**s**\][**u**]
> **/Fa**_pathname_
## Remarks
The `/FA` compiler option generates an assembler listing file for each translation unit in the compilation, which generally corresponds to a C or C++ source file. By default, only assembler is included in the listing file, which is encoded as ANSI. The optional `c`, `s`, and `u` arguments to `/FA` control whether machine code or source code are output together with the assembler listing, and whether the listing is encoded as UTF-8.
By default, each listing file gets the same base name as the source file, and has a .asm extension. When machine code is included by using the `c` option, the listing file has a .cod extension. You can change the name and extension of the listing file and the directory where it is created by using the `/Fa` option.
### /FA arguments
none
Only assembler language is included in the listing.
`c`
Optional. Includes machine code in the listing.
`s`
Optional. Includes source code in the listing.
`u`
Optional. Encodes the listing file in UTF-8 format, and includes a byte order marker. By default, the file is encoded as ANSI. Use `u` to create a listing file that displays correctly on any system, or if you are using Unicode source code files as input to the compiler.
If both `s` and `u` are specified, and if a source code file uses a Unicode encoding other than UTF-8, then the code lines in the .asm file may not display correctly.
### /Fa argument
none
One *source*.asm file is created for each source code file in the compilation.
*filename*
A listing file named *filename*.asm is placed in the current directory. This is only valid when compiling a single source code file.
*filename.extension*
A listing file named *filename.extension* is placed in the current directory. This is only valid when compiling a single source code file.
*directory*\
One *source_file*.asm file is created and placed in the specified *directory* for each source code file in the compilation. Note the required trailing backslash. Only paths on the current disk are allowed.
*directory*\\*filename*
A listing file named *filename*.asm is placed in the specified *directory*. This is only valid when compiling a single source code file.
*directory*\\*filename.extension*
A listing file named *filename.extension* is placed in the specified *directory*. This is only valid when compiling a single source code file.
### To set this compiler option in the Visual Studio development environment
1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../../ide/working-with-project-properties.md).
2. Open the **C/C++** folder and select the **Output Files** property page.
3. Modify the **Assembler Output** property to set the `/FAc` and `/FAs` options for assembler, machine, and source code. Modify the **Use Unicode For Assembler Listing** property to set the `/FAu` option for ANSI or UTF-8 output. Modify the **ASM List Location** to set the `/Fa` option for listing file name and location.
Note that setting both **Assembler Output** and **Use Unicode For Assembler Listing** properties can cause [Command-Line Warning D9025](../../error-messages/tool-errors/command-line-warning-d9025.md). To combine these options in the IDE, use the **Additional Options** field in the **Command Line** property page instead.
### To set this compiler option programmatically
- See <xref:Microsoft.VisualStudio.VCProjectEngine.VCCLCompilerTool.AssemblerListingLocation%2A> or <xref:Microsoft.VisualStudio.VCProjectEngine.VCCLCompilerTool.AssemblerOutput%2A>. To specify `/FAu`, see <xref:Microsoft.VisualStudio.VCProjectEngine.VCCLCompilerTool.AdditionalOptions%2A>.
## Example
The following command line produces a combined source and machine-code listing called HELLO.cod:
```
CL /FAcs HELLO.CPP
```
## See Also
[Output-File (/F) Options](../../build/reference/output-file-f-options.md)
[Compiler Options](../../build/reference/compiler-options.md)
[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
[Specifying the Pathname](../../build/reference/specifying-the-pathname.md) | 57.395604 | 437 | 0.739422 | eng_Latn | 0.981848 |
4c0702585108df639014c33d52376d4b28babb5e | 1,117 | md | Markdown | articles/azure-arc/data/view-data-controller-in-azure-portal.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-arc/data/view-data-controller-in-azure-portal.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-arc/data/view-data-controller-in-azure-portal.md | fuatrihtim/azure-docs.tr-tr | 6569c5eb54bdab7488b44498dc4dad397d32f1be | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Arc Data Controller kaynağını Azure portal görüntüle
description: Azure Arc Data Controller kaynağını Azure portal görüntüle
services: azure-arc
ms.service: azure-arc
ms.subservice: azure-arc-data
author: twright-msft
ms.author: twright
ms.reviewer: mikeray
ms.date: 09/22/2020
ms.topic: how-to
ms.openlocfilehash: 385546fe8b9f8bde4dcdc21fd3eea62f4e2bbdb4
ms.sourcegitcommit: 772eb9c6684dd4864e0ba507945a83e48b8c16f0
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/19/2021
ms.locfileid: "90941546"
---
# <a name="view-azure-arc-data-controller-resource-in-azure-portal"></a>Azure Arc Data Controller kaynağını Azure portal görüntüle
İlk [ölçümleri tamamladıktan veya günlükleri Azure 'a](upload-metrics-and-logs-to-azure-monitor.md) veya [karşıya yüklenmiş kullanıma](view-billing-data-in-azure.md)yükledikten sonra, Azure Portal Azure 'da oluşturulan Azure Arc veri denetleyicisi kaynağını görebilirsiniz.
Özel URL 'YI kullanarak Azure portal açın: [https://portal.azure.com](https://portal.azure.com) .
Arama çubuğunda veri denetleyicinizi ada göre arayın ve üzerine tıklayın. | 44.68 | 273 | 0.812892 | tur_Latn | 0.956958 |
4c07813b4a710d1c293ff32a694b422f034cad22 | 1,012 | md | Markdown | docs/vcd_gateway_sub-allocate-ip.md | ltimothy7/vcd-cli | b30e6fa1b96c2d2f0153ea39e08034962f50c669 | [
"Apache-2.0",
"MIT"
] | 96 | 2017-07-26T05:02:07.000Z | 2022-03-01T20:32:05.000Z | docs/vcd_gateway_sub-allocate-ip.md | ltimothy7/vcd-cli | b30e6fa1b96c2d2f0153ea39e08034962f50c669 | [
"Apache-2.0",
"MIT"
] | 243 | 2017-07-22T23:08:28.000Z | 2022-03-28T17:28:06.000Z | docs/vcd_gateway_sub-allocate-ip.md | ltimothy7/vcd-cli | b30e6fa1b96c2d2f0153ea39e08034962f50c669 | [
"Apache-2.0",
"MIT"
] | 87 | 2017-07-26T22:03:25.000Z | 2021-12-06T22:38:54.000Z | ```
Usage: vcd gateway sub-allocate-ip [OPTIONS] COMMAND [ARGS]...
Configures sub-allocate ip pools of gateway in vCloud Director.
Examples
vcd gateway sub-allocate-ip add gateway1
--external-network extNw1
--ip-range 10.10.10.20-10.10.10.30
Adds sub allocate ip pools to the edge gateway.
vcd gateway sub-allocate-ip update gateway1
-e extNw1
--old-ip-range 10.10.10.20-10.10.10.30
--new-ip-range 10.10.10.40-10.10.10.50
Updates sub allocate ip pools of the edge gateway.
vcd gateway sub-allocate-ip remove gateway1
-e extNetwork -i 10.10.10.40-10.10.10.50
Removes the provided IP range
Options:
-h, --help Show this message and exit.
Commands:
add Adds sub allocate ip pools to the edge gateway
remove Removes the given IP ranges from existing IP ranges
update Edits sub allocate IP pools to the edge gateway
```
| 31.625 | 65 | 0.619565 | eng_Latn | 0.840609 |
4c07f9963ad0e3ae78eaa6b1925db40969adb91a | 1,829 | markdown | Markdown | slides/automation-qa/simple-cov.markdown | RubyWorkout/rubyworkout.github.com | ec12c5fa1376ffdfc54033594aa36f37d22d2698 | [
"CC-BY-4.0"
] | 37 | 2016-06-07T08:52:01.000Z | 2021-09-29T13:28:28.000Z | slides/automation-qa/simple-cov.markdown | RubyWorkout/rubyworkout.github.com | ec12c5fa1376ffdfc54033594aa36f37d22d2698 | [
"CC-BY-4.0"
] | 14 | 2016-12-04T21:38:47.000Z | 2021-09-27T20:23:51.000Z | slides/automation-qa/simple-cov.markdown | RubyWorkout/rubyworkout.github.com | ec12c5fa1376ffdfc54033594aa36f37d22d2698 | [
"CC-BY-4.0"
] | 55 | 2016-10-06T20:02:04.000Z | 2022-02-02T18:23:47.000Z | ---
layout: slide
title: SimpleCov
---
# SimpleCov
### SimpleCov is a code coverage analysis tool for Ruby.
---
# Installation
--
## Install gem - `simplecov`
Gemfile <!-- .element: class="filename" -->
```ruby
group :test do
gem 'simplecov', require: false
end
```
Then, run `bundle install` to download and install new gem
```bash
$ bundle install
```
--
Load and launch [SimpleCov](https://github.com/colszowka/simplecov) at the **very top** of your `spec/rails_helper.rb`
spec/rails_helper.rb <!-- .element: class="filename" -->
```ruby
require 'simplecov'
SimpleCov.start
```
--
## Configuring SimpleCov
If you're making a Rails application, SimpleCov comes with built-in configurations. To use it, the first two lines of your `rails_helper` should be like this:
spec/rails_helper.rb <!-- .element: class="filename" -->
```ruby
require 'simplecov'
SimpleCov.start 'rails'
```
For example you can add any custom configs like groups and filters:
spec/rails_helper.rb <!-- .element: class="filename" -->
```ruby
SimpleCov.start 'rails' do
add_filter '/spec/' # simple string filter will remove all files that match "/spec/" in their path
minimum_coverage 95 # define the minimum coverage percentage expected
minimum_coverage_by_file 90 # define the minimum coverage by file percentage expected
end
```
[Configuration](https://rubydoc.info/gems/simplecov/SimpleCov/Configuration) API documentation to find out what you can customize.
---
# How to use SimpleCov?
--
Just run your tests with RSpec command:
```bash
$ rspec # SimpleCov will generate 'coverage/index.html' file
```
After running your tests, open `coverage/index.html` in the browser of your choice:
For Mac:
```terminal
open coverage/index.html
```
For Ubuntu:
```bash
$ xdg-open coverage/index.html
```
| 18.474747 | 158 | 0.710771 | eng_Latn | 0.869614 |
4c08c186f1086639a2b5ff2b42f84bc08273e697 | 104 | md | Markdown | README.md | liwenchi123000/Todo | 085b0ba72fbe8412c2d9f4e2ae2b2c6c12ab9091 | [
"Apache-2.0"
] | 2 | 2018-04-19T07:13:54.000Z | 2018-07-23T03:22:15.000Z | README.md | liwenchi123000/Todo | 085b0ba72fbe8412c2d9f4e2ae2b2c6c12ab9091 | [
"Apache-2.0"
] | null | null | null | README.md | liwenchi123000/Todo | 085b0ba72fbe8412c2d9f4e2ae2b2c6c12ab9091 | [
"Apache-2.0"
] | null | null | null | # Todo
vue进阶练习 webpack+Single File Components
QQ截图比较模糊
| 17.333333 | 38 | 0.711538 | yue_Hant | 0.14746 |
4c08da3231afb717485aca1b6b002dd7e4e74d0e | 1,348 | md | Markdown | README.md | tmorin/docker-image-keepalived | 6c88bf38536f0af7dd971c1f2c6eb643dfc23884 | [
"MIT"
] | 2 | 2020-02-10T00:26:48.000Z | 2021-11-01T07:10:51.000Z | README.md | tmorin/docker-image-keepalived | 6c88bf38536f0af7dd971c1f2c6eb643dfc23884 | [
"MIT"
] | null | null | null | README.md | tmorin/docker-image-keepalived | 6c88bf38536f0af7dd971c1f2c6eb643dfc23884 | [
"MIT"
] | 1 | 2020-06-03T10:21:06.000Z | 2020-06-03T10:21:06.000Z | # docker-image-keepalived
[](https://hub.docker.com/r/thibaultmorin/keepalived)
Provide a Docker image running [keepalived](https://keepalived.org/) which is highly inspired by the project [osixia/docker-keepalived](https://github.com/osixia/docker-keepalived).
## Configuration
- `KEEPALIVED_INTERFACE`: Keepalived network interface. Default value `eth0`
- `KEEPALIVED_PASSWORD`: Keepalived password. Default value `d0cker`
- `KEEPALIVED_PRIORITY`: Keepalived node priority. Default value `150`
- `KEEPALIVED_ROUTER_ID`: Keepalived virtual router ID. Default value `51`
- `KEEPALIVED_UNICAST_PEERS`: Keepalived unicast peers. Default value `192.168.1.10,192.168.1.11`
- `KEEPALIVED_VIRTUAL_IPS`: Keepalived virtual IPs. Default value `192.168.1.231,192.168.1.232`
- `KEEPALIVED_NOTIFY`: Script to execute when node state change. Default value `/notify.sh`
## Usage
```bash
docker run -d --name keepalived --restart=always \
--cap-add=NET_ADMIN --net=host \
-e KEEPALIVED_VIRTUAL_IPS="192.168.0.99" \
-e KEEPALIVED_UNICAST_PEERS="192.168.0.100,192.168.0.101,192.168.0.102" \
thibaultmorin/keepalived
```
| 49.925926 | 183 | 0.761128 | yue_Hant | 0.511723 |
4c093a80b4f90007a910fac75795d515b5f9298f | 965 | md | Markdown | aspnet/web-forms/videos/net-4/routing/aspnet-4-quick-hit-imperative-webforms-routing.md | v-hearya/AspNetDocs | 4e11984fa5c9be7f48358fac15cbbfd070f04db5 | [
"CC-BY-4.0",
"MIT"
] | 159 | 2020-02-20T05:22:34.000Z | 2022-03-29T12:07:40.000Z | aspnet/web-forms/videos/net-4/routing/aspnet-4-quick-hit-imperative-webforms-routing.md | v-hearya/AspNetDocs | 4e11984fa5c9be7f48358fac15cbbfd070f04db5 | [
"CC-BY-4.0",
"MIT"
] | 130 | 2020-02-20T15:57:30.000Z | 2022-03-25T03:49:08.000Z | aspnet/web-forms/videos/net-4/routing/aspnet-4-quick-hit-imperative-webforms-routing.md | v-hearya/AspNetDocs | 4e11984fa5c9be7f48358fac15cbbfd070f04db5 | [
"CC-BY-4.0",
"MIT"
] | 672 | 2020-02-20T07:49:28.000Z | 2022-03-31T13:37:20.000Z | ---
uid: web-forms/videos/net-4/routing/aspnet-4-quick-hit-imperative-webforms-routing
title: ASP.NET 4 Quick Hit - Imperative WebForms Routing
author: JoeStagner
description: "In this video you will learn how to use an expression builder to do WebForms routing imperatively."
ms.author: riande
ms.date: 11/05/2009
ms.assetid: c78fd810-4309-4d58-afd9-81e9ffa77429
msc.legacyurl: /web-forms/videos/net-4/routing/aspnet-4-quick-hit-imperative-webforms-routing
msc.type: video
---
# ASP.NET 4 "Quick Hit" - Imperative WebForms Routing
by [Joe Stagner](https://github.com/JoeStagner)
In this video you will learn how to use an expression builder to do WebForms routing imperatively.
[▶ Watch video (12 minutes)](https://channel9.msdn.com/Blogs/ASP-NET-Site-Videos/aspnet-4-quick-hit-imperative-webforms-routing)
> [!div class="step-by-step"]
> [Previous](aspnet-4-quick-hit-permanent-redirect.md)
> [Next](aspnet-4-quick-hit-declarative-webforms-routing.md)
| 41.956522 | 134 | 0.774093 | eng_Latn | 0.39678 |
4c0aed361ec238b9be8ddc665bbe919576b6da65 | 2,529 | md | Markdown | _posts/2019-09-26-bewertungen-flaggschiffs-4-pixel-von-google-gab-es-im-netz-vor-der-ank-ndigung.md | anatolii331/DE | e1962ed571f087b6c29a57ca7ee3bbee9a6bbbde | [
"MIT"
] | null | null | null | _posts/2019-09-26-bewertungen-flaggschiffs-4-pixel-von-google-gab-es-im-netz-vor-der-ank-ndigung.md | anatolii331/DE | e1962ed571f087b6c29a57ca7ee3bbee9a6bbbde | [
"MIT"
] | null | null | null | _posts/2019-09-26-bewertungen-flaggschiffs-4-pixel-von-google-gab-es-im-netz-vor-der-ank-ndigung.md | anatolii331/DE | e1962ed571f087b6c29a57ca7ee3bbee9a6bbbde | [
"MIT"
] | null | null | null | ---
id: 4886
title: Bewertungen Flaggschiffs 4 Pixel von Google gab es im Netz vor der Ankündigung
date: 2019-09-26T06:02:07+00:00
author: user
layout: post
guid: http://de.bestwow.net/bewertungen-flaggschiffs-4-pixel-von-google-gab-es-im-netz-vor-der-ank-ndigung/
permalink: /bewertungen-flaggschiffs-4-pixel-von-google-gab-es-im-netz-vor-der-ank-ndigung/
tdc_dirty_content:
- "1"
- "1"
tdc_icon_fonts:
- 'a:0:{}'
- 'a:0:{}'
tdc_google_fonts:
- 'a:2:{i:0;s:3:"662";i:4;s:3:"394";}'
- 'a:2:{i:0;s:3:"662";i:4;s:3:"394";}'
ap_mark:
- Это пост был добавлен через AftParser
- Это пост был добавлен через AftParser
ap_link:
- https://lifehacker.ru/google-pixel-4-video-reviews/
- https://lifehacker.ru/google-pixel-4-video-reviews/
post_views_count:
- "10"
- "10"
categories:
- Instagram
---
Vor der Veröffentlichung der neuen Pixel 4 Pixel und 4 XL bleibt etwa einen Monat, und Google anscheinend auch nicht versucht, die Leckagen zu widerstehen. Haben wir vorher gesehen haben, vor allem Renderings und minderwertige Fotos, ist jetzt auf YouTube erschienen drei Video-review, in denen Smartphones erschien in seiner ganzen Pracht (und 1080p).</p>
Zuvor hatte Google selbst bekannt das Design der Rückseite, und die neuen Rollen haben gezeigt, wie es Aussehen wird das Smartphone von allen Seiten. Und es ist nicht verwunderlich, dass Top-End-Smartphone läuft auf dem kürzlich angekündigten Android 10. In dem Video zeigten auch die aktualisierte Kamera-App.</p>
Einzigartig für «Pixel» – Einstellungen hier nicht viel — Ambient EQ (dynamische Anpassung der Display-Helligkeit und Temperatur), eigene themes Pixel und eine neue Funktion namens Screen attention. Wenn Sie die neueste, Bildschirm leuchtet auf und zeigt Uhrzeit und Benachrichtigungen, wenn das Telefon erkennt den Benutzer in der Nähe — eine Art Variation AlwaysOn-Displays. Im Menü Einstellungen können Sie auch wählen Sie die Bildwiederholrate von 90 Hz.</p>
In dem Video Kanal mit Rabbit TV sind alle drei Farbvarianten Pixel 4: weiß, schwarz und Koralle. Schwarzes Modell ist glänzend, während die hellen matt und nicht so stark festklammern Fingerabdrücke.
Die Präsentation der Google-Pixel 4 Pixel und 4 XL muss im Oktober. Das genaue Datum der Ankündigung noch nicht bekannt gegeben.
<div>
<h2 class="read-also__title">
<span>Lesen Sie auch</span> <span>🧐 </span>
</h2>
<ul class="read-also__list">
<li>
Google Pixel 4: суперплавный Bildschirm, mehr RAM und andere Details
</li>
</ul>
</div> | 50.58 | 469 | 0.753658 | deu_Latn | 0.984166 |
4c0b56b1abd129e9faaaf969621fbdcedb081a36 | 6,621 | md | Markdown | articles/active-directory/governance/perform-access-review.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-08-10T02:23:39.000Z | 2019-08-10T02:23:40.000Z | articles/active-directory/governance/perform-access-review.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/governance/perform-access-review.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Gruplar veya erişim gözden geçirmeleri - Azure Active Directory uygulamaları için erişimi gözden geçir | Microsoft Docs
description: Grup üyelerinin erişim veya uygulama erişimi Azure Active Directory erişim gözden geçirmeleri, gözden geçirmeyi öğrenin.
services: active-directory
author: rolyon
manager: mtillman
editor: markwahl-msft
ms.service: active-directory
ms.workload: identity
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: conceptual
ms.subservice: compliance
ms.date: 05/21/2019
ms.author: rolyon
ms.reviewer: mwahl
ms.collection: M365-identity-device-management
ms.openlocfilehash: b6f73d3bf5e502a758dd46561059c15a2970d9b6
ms.sourcegitcommit: f811238c0d732deb1f0892fe7a20a26c993bc4fc
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 06/29/2019
ms.locfileid: "67471820"
---
# <a name="review-access-to-groups-or-applications-in-azure-ad-access-reviews"></a>Gruplara erişimi gözden geçirmek veya Azure AD uygulama erişim gözden geçirmeleri
Azure Active Directory (Azure AD) nasıl kuruluşlar, Azure AD'de gruplara ve uygulamalara erişimi yönetme ve diğer Microsoft Çevrimiçi Hizmetler Azure AD erişim adlı bir özellik ile inceler kolaylaştırır.
Bu makalede nasıl üyeleri bir grup veya uygulamaya erişimi olan kullanıcılar için erişim gözden geçirmesi belirlenen bir Gözden Geçiren gerçekleştirdiğini açıklar.
## <a name="prerequisites"></a>Önkoşullar
- Azure AD Premium P2
Daha fazla bilgi için [hangi kullanıcıların lisansına sahip olması gerekir?](access-reviews-overview.md#which-users-must-have-licenses).
## <a name="open-the-access-review"></a>Erişim gözden geçirmesi açın
Erişim gözden geçirmesi gerçekleştirmek için ilk adım, erişim gözden geçirmesi açın sağlamaktır.
1. Erişim gözden geçirme ister Microsoft'tan bir e-posta için bakın. Bir grup erişimini gözden geçirmek için bir örnek e-posta aşağıda verilmiştir.
1. Tıklayın **Başlat gözden geçirme** erişim gözden geçirmesi açmaya yönelik bağlantı.
E-posta yoksa, aşağıdaki adımları izleyerek, beklemedeki erişim gözden geçirmeleri bulabilirsiniz.
1. MyApps portalında oturum açın [ https://myapps.microsoft.com ](https://myapps.microsoft.com).
1. Sayfanın sağ üst köşesinde yer alan ve adınızla varsayılan kuruluşunuzun gösterildiği kullanıcı simgesine tıklayın. Listede birden fazla kuruluş varsa erişim gözden geçirmesi isteğinde bulunan kuruluşu seçin.
1. Tıklayın **erişim gözden geçirmeleriyle** beklemedeki erişim gözden geçirmeleri listesini görmek için kutucuğu.
Kutucuk yoksa ilgili kuruluş için bekleyen erişim gözden geçirmesi yoktur ve herhangi bir işlem yapmanız gerekmez.
1. Tıklayın **başlamak gözden geçirme** gerçekleştirmek istediğiniz erişim gözden geçirmesi için bağlantı.
## <a name="perform-the-access-review"></a>Erişim değerlendirmesi gerçekleştirme
Erişim gözden geçirmesi açtıktan sonra gözden geçirilmesi gereken kullanıcılar adlarını görürsünüz.
İstek, kendi erişim gözden geçirmek için ise sayfa farklı görünecektir. Daha fazla bilgi için [erişimi gözden geçir kendiniz grupları ve uygulamaları için](review-your-access.md).
Onaylama veya reddetme erişim iki yolu vardır:
- Onaylayın veya bir veya daha fazla kullanıcı erişimi reddetmek veya
- Kolay ve hızlı bir yolu olan sistem önerileri kabul edebilir.
### <a name="approve-or-deny-access-for-one-or-more-users"></a>Onaylamak veya reddetmek için bir veya daha fazla kullanıcı erişimi
1. Onaylayın veya reddedin sürekli erişimleri karar vermek için kullanıcıların listesini gözden geçirin.
1. Onaylayın veya tek bir kullanıcı erişimi reddetmek için satırın gerçekleştirilecek eylemi belirtmek için bir pencere açmak için tıklayın. Onaylayın veya reddedin birden çok kullanıcı için erişim için kullanıcıların yanında onay işareti ekleyin ve ardından **gözden geçirme X kullanıcı** gerçekleştirilecek eylemi belirtmek için bir pencere açmak için düğmeyi.
1. Tıklayın **onaylama** veya **Reddet**. Emin değilseniz, tıklayabilirsiniz **bilmiyorum**. Bunun yapılması, kullanıcının kendi erişimini koruma neden olur, ancak seçimi denetim günlüklerinde yansıtılır.
1. Gerekirse, bir neden girin **neden** kutusu.
Erişim gözden geçirmesi Yöneticisi sürekli erişim veya grup üyeliği onaylama için bir neden sağlamanızı gerektirebilir.
1. Gerçekleştirilecek eylemi belirledikten sonra tıklayın **Kaydet**.
Yanıtınız değiştirmek istiyorsanız, bir satırı seçin ve yanıt güncelleştirin. Örneğin, önceden reddedilen bir kullanıcı tarafından onaylanması veya önceden onaylanmış bir kullanıcıyı engelle. Erişim gözden geçirmesi sona erinceye kadar herhangi bir zamanda yanıtınızı değiştirebilirsiniz.
Birden çok Gözden Geçiren varsa, son gönderilen yanıt kaydedilir. Burada yöneticinin iki Gözden Geçiren – Alice ve Bob atar örneği göz önünde bulundurun. Alice, erişim gözden geçirmesi ilk açılır ve erişim onaylar. Gözden geçirme sona ermeden önce Bob erişim gözden geçirmesi açılır ve erişimi engeller. Son reddetme yanıttır ne kaydedilir.
> [!NOTE]
> Bir kullanıcının erişimi reddedilirse, hemen kaldırılmaz. Bunlar, gözden geçirme sona erdiğinde veya yöneticinin gözden durduğunda kaldırılır.
### <a name="approve-or-deny-access-based-on-recommendations"></a>Onaylayın veya reddedin önerilerine göre erişim
Erişim gözden geçirmeleri daha kolay ve hızlı sizin yerinize yapmasını isteyin de kabul edebileceği önerileri tek bir tıklamayla sunuyoruz. Öneriler, kullanıcının oturum açma etkinliklere göre oluşturulur.
1. Sayfanın alt kısmındaki mavi çubuğunda **önerileri kabul et**.
Önerilen eylemleri özetini görürsünüz.
1. Tıklayın **Tamam** önerileri kabul etmek için.
## <a name="next-steps"></a>Sonraki adımlar
- [Grupları ve uygulamaları, erişim değerlendirmesi tamamlama](complete-access-review.md)
| 57.077586 | 362 | 0.81317 | tur_Latn | 0.999967 |