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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
9a6aea3297223b81fbb7edb6f03e3c1e2212ae4a | 334 | md | Markdown | _posts/2018-09-25-ballpoint-pen.md | raphaeldhwang/comeongifts | cf6202f4c52de53f7299990f05b1c15e568404d1 | [
"Apache-2.0"
] | null | null | null | _posts/2018-09-25-ballpoint-pen.md | raphaeldhwang/comeongifts | cf6202f4c52de53f7299990f05b1c15e568404d1 | [
"Apache-2.0"
] | null | null | null | _posts/2018-09-25-ballpoint-pen.md | raphaeldhwang/comeongifts | cf6202f4c52de53f7299990f05b1c15e568404d1 | [
"Apache-2.0"
] | null | null | null | ---
title: Ballpoint Pen
subtitle:
layout: default
modal-id: 4
date: 2018-09-25
img: ballpoint-pen.jpg
thumbnail: ballpoint-pen-thumbnail.jpg
alt: image-alt
category:
- Pens
- Gel pen
---
0.7mm/1mm ballpoint pen<br>
MOQ: 1000pcs<br>
Ex-factory Price: $0.15-0.25<br>
Support custom logo<br>
The set-up charge: $50 per color<br>
| 16.7 | 38 | 0.712575 | eng_Latn | 0.209047 |
9a6b4333a593925cc1cac7aa53c442b755a0d1ff | 825 | md | Markdown | README.md | Nyceane/onVIFCamera-Android | 81fd9fb9b4513d744e2e53348ae8f87c83a479ab | [
"MIT"
] | 6 | 2018-05-29T13:42:18.000Z | 2021-06-21T08:35:28.000Z | README.md | Nyceane/onVIFCamera-Android | 81fd9fb9b4513d744e2e53348ae8f87c83a479ab | [
"MIT"
] | null | null | null | README.md | Nyceane/onVIFCamera-Android | 81fd9fb9b4513d744e2e53348ae8f87c83a479ab | [
"MIT"
] | 3 | 2018-02-22T22:59:26.000Z | 2019-07-27T16:34:35.000Z | # onVIFCamera-Anroid
This library have been developped to ease the connection of an Android device to an ONVIF Camera.
With this library you are able to get the informations from a camera, the different media profiles available and retrieve the stream URI to play it.
## Example
To run the example project, clone the repo, and compile in Android Studio
## Requirements
Hardware: Android phone that runs KitKat (4.4) or newer
Software: Android Studio
To use this project on an Android device (real device, not a simulator), with android min SDK at 19, Android 4.4 KitKat
In gradle, it is important that we use compile 'com.github.potterhsu:RtspLibrary:v1.0'
## Author
Peter Ma, @nyceane
## License
ONVIFCamera is available under the MIT license. See the LICENSE file for more info.
| 28.448276 | 148 | 0.774545 | eng_Latn | 0.988575 |
9a6bf337d162aae9ca29c39f820614b8201929b3 | 6,136 | md | Markdown | src/articles/2019-02-01---My-Journey-to-Higher-Education/index.md | judepark/judepark | d5769314822bd6d0325a3b087d6f725bfe855ea2 | [
"MIT"
] | null | null | null | src/articles/2019-02-01---My-Journey-to-Higher-Education/index.md | judepark/judepark | d5769314822bd6d0325a3b087d6f725bfe855ea2 | [
"MIT"
] | null | null | null | src/articles/2019-02-01---My-Journey-to-Higher-Education/index.md | judepark/judepark | d5769314822bd6d0325a3b087d6f725bfe855ea2 | [
"MIT"
] | null | null | null | ---
title: My Journey to Higher Education - Why Not All Degrees are Equal
url: ""
date: "2019-02-01"
tags: ["Animals", "Chicago", "Zoos"]
themeColor: "#e6faef"
accentColor: "#28b065"
image: "1.jpg"
thumb: "1.jpg"
imageauthor: "Andre Hunter"
highlight: "no"
showLiveContent: false
---
> “Nobody wants to show you the hours and hours of becoming. They'd rather show the highlight of what they've become.”<br/>― Angela Duckworth
<br>
To some, higher education is a granted option. A privilege offered as a natural step towards success. This was not my story.
<div class="photo-grid-container">
<div class="photo-grid">
<img src="2.jpg"/>
</div>
</div>
<p class="photo-grid-subtitle">Triumph Award</p>
##My Journey to Higher Education
In high school me and my sisters were orphaned children and refugee-immigrants, living from check to check. At the time, me and my sisters were barely scraping by with the little money we received from social services. My sister worked four jobs in high school, and we lived in constant fear of the Canadian immigrant officers deporting us back to our country of birth. Uneducated and with no one to protect us, we were alone to deal on our own, scared and fearful to trust anyone to disclose our struggles.
In grade 10, I transferred in the middle of the semester to a predominantly white school. I missed my life at Jane and Weston[^1], and it was frankly my first time being surrounded by white people. One day at school, someone broke into my locker and stole my wallet. I didn't know what to do. I was too scared to even report it. I knew no one could help me. On fourth period Chemistry, in the middle of class, I stood up and walked out. Without my metropass, it took me two hours in the freezing winter to walk home that afternoon.
The next day at school, I was in front of my guidance counsellor. Mr. Soloman[^2] wanted to speak to me, ask me why I had skipped school the day before. When he asked, I just began sobbing. The room filled with adults, one by one. It was humiliating, because it was my first time ever crying in front of a stranger, and it was the first time ever in which I called out to someone for help. I realize now though, that it was also necessary. I never sought help from anyone before. My guidance counsellors enrolled me in the free bus ticket program. They made sure I didn't go hungry during lunchtime anymore. They made me apply for the Triumph Award.
<div class="photo-grid-container">
<div class="photo-grid">
<img src="3.png"/>
</div>
</div>
<p class="photo-grid-subtitle">My Accomplishments on My Wall</p>
##Grit on My Wall
My masters cost me 25K, my bachelors 40K, but somehow my Triumph Award feels like a bigger accomplishment to me now. Like the description of the scholarship states, I was able to graduate despite extraordinary circumstances and even ended up going to university, at a time when such an endeavor seemed impossible to achieve.
Of all the framed feats that hang on my wall today, my Triumph Award, a small scholarship in the grand scheme of things (that certainly came cheaper than my degrees) holds a special place in my heart. It represents the grit that it took to make it here.
##What Success is to Me
I don't measure success by an amount of money or accolades. The amount of privilege someone had or has over me, or whether or not someone is deemed "successful" by society. What does that even mean, anyways? People seem to applaud anyone rich or famous. I measure success by the perseverance that took to keep moving forward, even in the face of adversity. That’s what success is to me. If you are still here despite it all - that's success. I think it my little award from high school tells a better story of who I am than my resume ever could.
##Not All Degrees are Created Equal
Not all degrees are created equal because the work that went into achieving a degree varies on the level of financial and emotional support a student had, and ultimately the privileges they had in achieving the degree. In the same class, it was a world of a difference - for some it was life or death, while for others it was mainly treated as a joke[^3].
I cannot relate to the dull-mindedness of employers who believe that filterings their applicants by academic institutions or level will grant them superior applicants. There are youth who work in fast food restaurants who have better organizational and leadership skills than some university-level coop students that companies limit their hiring to. We need to break out of our elitist mindset when we review applicants[^4], and begin to properly assess applicants based on their individual feats - not by standardized tests and education. In two applicantions with identical acheivements, the student who worked and managed to acheive the same without privilege is more desirable as an applicant, because to do so without means they are more resiliient, capable, and likely to succeed.
[^1]:
Jane and Weston is a low-income neighborhood in Toronto with one of the lowest <a href="https://www.theglobeandmail.com/news/toronto/140-toronto-neighbourhoods-ranked-by-new-equity-score/article17407725/" title="neighbourhood equity index of Toronto" target="_blank" rel="noopener noreferrer">neighbourhood equity score</a>, with common gun and knife violence. Drake once rapped: “How did I finesse all this shit from Jane and Weston?”
[^2]:
Mr. Solomon continued to play an important role in me graduating from high school. I remember that for about a month after the incident he would show up randomly on my first period. Looking back, I think that was his discreet way of making sure I made it to school okay and that I was alright.
[^3]:
Overcoming adversity forces the person to change the way they view and approach a problem, that leads to increased adapatability and preparedness for future issues.
[^4]:
I jumped the gun here - in fact the real problem for companies is learning how to reach potential applicants to become applicants. There is a huge gap between a company with job opportunities, and potential youth living in underrepresented communities.
| 79.688312 | 786 | 0.777868 | eng_Latn | 0.999903 |
9a6bffc5442fe34220f36d88c9c88c3ca9ddb783 | 13,583 | md | Markdown | akka-docs/src/main/paradox/general/stream/stream-design.md | phiSgr/akka | 1b4da3d10f7f6e023678bc2b7984963cceb7b7e2 | [
"Apache-2.0"
] | 1 | 2019-07-17T13:52:50.000Z | 2019-07-17T13:52:50.000Z | akka-docs/src/main/paradox/general/stream/stream-design.md | phiSgr/akka | 1b4da3d10f7f6e023678bc2b7984963cceb7b7e2 | [
"Apache-2.0"
] | 1 | 2019-12-12T05:39:46.000Z | 2019-12-12T05:39:46.000Z | akka-docs/src/main/paradox/general/stream/stream-design.md | tegonal/akka | 3c1c06fb88645801638b7b9ee69b9bcc5f51bb56 | [
"Apache-2.0"
] | 1 | 2019-07-16T08:09:05.000Z | 2019-07-16T08:09:05.000Z | # Design Principles behind Akka Streams
It took quite a while until we were reasonably happy with the look and feel of the API and the architecture of the implementation, and while being guided by intuition the design phase was very much exploratory research. This section details the findings and codifies them into a set of principles that have emerged during the process.
@@@ note
As detailed in the introduction keep in mind that the Akka Streams API is completely decoupled from the Reactive Streams interfaces which are an implementation detail for how to pass stream data between individual operators.
@@@
## What shall users of Akka Streams expect?
Akka is built upon a conscious decision to offer APIs that are minimal and consistent—as opposed to easy or intuitive. The credo is that we favor explicitness over magic, and if we provide a feature then it must work always, no exceptions. Another way to say this is that we minimize the number of rules a user has to learn instead of trying to keep the rules close to what we think users might expect.
From this follows that the principles implemented by Akka Streams are:
* all features are explicit in the API, no magic
* supreme compositionality: combined pieces retain the function of each part
* exhaustive model of the domain of distributed bounded stream processing
This means that we provide all the tools necessary to express any stream processing topology, that we model all the essential aspects of this domain (back-pressure, buffering, transformations, failure recovery, etc.) and that whatever the user builds is reusable in a larger context.
### Akka Streams does not send dropped stream elements to the dead letter office
One important consequence of offering only features that can be relied upon is the restriction that Akka Streams cannot ensure that all objects sent through a processing topology will be processed. Elements can be dropped for a number of reasons:
* plain user code can consume one element in a *map(...)* operator and produce an entirely different one as its result
* common stream operators drop elements intentionally, e.g. take/drop/filter/conflate/buffer/…
* stream failure will tear down the stream without waiting for processing to finish, all elements that are in flight will be discarded
* stream cancellation will propagate upstream (e.g. from a *take* operator) leading to upstream processing steps being terminated without having processed all of their inputs
This means that sending JVM objects into a stream that need to be cleaned up will require the user to ensure that this happens outside of the Akka Streams facilities (e.g. by cleaning them up after a timeout or when their results are observed on the stream output, or by using other means like finalizers etc.).
### Resulting Implementation Considerations
Compositionality entails reusability of partial stream topologies, which led us to the lifted approach of describing data flows as (partial) graphs that can act as composite sources, flows (a.k.a. pipes) and sinks of data. These building blocks shall then be freely shareable, with the ability to combine them freely to form larger graphs. The representation of these pieces must therefore be an immutable blueprint that is materialized in an explicit step in order to start the stream processing. The resulting stream processing engine is then also immutable in the sense of having a fixed topology that is prescribed by the blueprint. Dynamic networks need to be modeled by explicitly using the Reactive Streams interfaces for plugging different engines together.
The process of materialization will often create specific objects that are useful to interact with the processing engine once it is running, for example for shutting it down or for extracting metrics. This means that the materialization function produces a result termed the *materialized value of a graph*.
## Interoperation with other Reactive Streams implementations
Akka Streams fully implement the Reactive Streams specification and interoperate with all other conformant implementations. We chose to completely separate the Reactive Streams interfaces from the user-level API because we regard them to be an SPI that is not targeted at endusers. In order to obtain a `Publisher` or `Subscriber` from an Akka Stream topology, a corresponding `Sink.asPublisher` or `Source.asSubscriber` element must be used.
All stream Processors produced by the default materialization of Akka Streams are restricted to having a single Subscriber, additional Subscribers will be rejected. The reason for this is that the stream topologies described using our DSL never require fan-out behavior from the Publisher sides of the elements, all fan-out is done using explicit elements like `Broadcast[T]`.
This means that `Sink.asPublisher(true)` (for enabling fan-out support) must be used where broadcast behavior is needed for interoperation with other Reactive Streams implementations.
### Rationale and benefits from Sink/Source/Flow not directly extending Reactive Streams interfaces
A sometimes overlooked crucial piece of information about [Reactive Streams](https://github.com/reactive-streams/reactive-streams-jvm/) is that they are a [Service Provider Interface](https://en.m.wikipedia.org/wiki/Service_provider_interface), as explained in depth in one of the [early discussions](https://github.com/reactive-streams/reactive-streams-jvm/pull/25) about the specification.
Akka Streams was designed during the development of Reactive Streams, so they both heavily influenced one another.
It may be enlightening to learn that even within the Reactive Specification the types had initially attempted to hide `Publisher`, `Subscriber` and the other SPI types from users of the API.
Though since those internal SPI types would end up surfacing to end users of the standard in some cases, it was decided to [remove the API types, and only keep the SPI types](https://github.com/reactive-streams/reactive-streams-jvm/pull/25) which are the `Publisher`, `Subscriber` et al.
With this historical knowledge and context about the purpose of the standard – being an internal detail of interoperable libraries - we can with certainty say that it can't be really said that an direct _inheritance_ relationship with these types can be considered some form of advantage or meaningful differentiator between libraries.
Rather, it could be seen that APIs which expose those SPI types to end-users are leaking internal implementation details accidentally.
The `Source`, `Sink` and `Flow` types which are part of Akka Streams have the purpose of providing the fluent DSL, as well as to be "factories" for running those streams.
Their direct counterparts in Reactive Streams are, respectively, `Publisher`, `Subscriber` and `Processor`.
In other words, Akka Streams operate on a lifted representation of the computing graph,
which then is materialized and executed in accordance to Reactive Streams rules. This also allows Akka Streams to perform optimizations like fusing and dispatcher configuration during the materialization step.
Another not obvious gain from hiding the Reactive Streams interfaces comes from the fact that `org.reactivestreams.Subscriber` (et al) have now been included in Java 9+, and thus become part of Java itself, so libraries should migrate to using the `java.util.concurrent.Flow.Subscriber` instead of `org.reactivestreams.Subscriber`.
Libraries which selected to expose and directly extend the Reactive Streams types will now have a tougher time to adapt the JDK9+ types -- all their classes that extend Subscriber and friends will need to be copied or changed to extend the exact same interface,
but from a different package. In Akka we simply expose the new type when asked to -- already supporting JDK9 types, from the day JDK9 was released.
The other, and perhaps more important reason for hiding the Reactive Streams interfaces comes back to the first points of this explanation: the fact of Reactive Streams being an SPI, and as such is hard to "get right" in ad-hoc implementations. Thus Akka Streams discourages the use of the hard to implement pieces of the underlying infrastructure, and offers simpler, more type-safe, yet more powerful abstractions for users to work with: GraphStages and operators. It is of course still (and easily) possible to accept or obtain Reactive Streams (or JDK+ Flow) representations of the stream operators by using methods like `asPublisher` or `fromSubscriber`.
## What shall users of streaming libraries expect?
We expect libraries to be built on top of Akka Streams, in fact Akka HTTP is one such example that lives within the Akka project itself. In order to allow users to profit from the principles that are described for Akka Streams above, the following rules are established:
* libraries shall provide their users with reusable pieces, i.e. expose factories that return operators, allowing full compositionality
* libraries may optionally and additionally provide facilities that consume and materialize operators
The reasoning behind the first rule is that compositionality would be destroyed if different libraries only accepted operators and expected to materialize them: using two of these together would be impossible because materialization can only happen once. As a consequence, the functionality of a library must be expressed such that materialization can be done by the user, outside of the library’s control.
The second rule allows a library to additionally provide nice sugar for the common case, an example of which is the Akka HTTP API that provides a `handleWith` method for convenient materialization.
@@@ note
One important consequence of this is that a reusable flow description cannot be bound to “live” resources, any connection to or allocation of such resources must be deferred until materialization time. Examples of “live” resources are already existing TCP connections, a multicast Publisher, etc.; a TickSource does not fall into this category if its timer is created only upon materialization (as is the case for our implementation).
Exceptions from this need to be well-justified and carefully documented.
@@@
### Resulting Implementation Constraints
Akka Streams must enable a library to express any stream processing utility in terms of immutable blueprints. The most common building blocks are
* Source: something with exactly one output stream
* Sink: something with exactly one input stream
* Flow: something with exactly one input and one output stream
* BidiFlow: something with exactly two input streams and two output streams that conceptually behave like two Flows of opposite direction
* Graph: a packaged stream processing topology that exposes a certain set of input and output ports, characterized by an object of type `Shape`.
@@@ note
A source that emits a stream of streams is still a normal Source, the kind of elements that are produced does not play a role in the static stream topology that is being expressed.
@@@
## The difference between Error and Failure
The starting point for this discussion is the [definition given by the Reactive Manifesto](http://www.reactivemanifesto.org/glossary#Failure). Translated to streams this means that an error is accessible within the stream as a normal data element, while a failure means that the stream itself has failed and is collapsing. In concrete terms, on the Reactive Streams interface level data elements (including errors) are signaled via `onNext` while failures raise the `onError` signal.
@@@ note
Unfortunately the method name for signaling *failure* to a Subscriber is called `onError` for historical reasons. Always keep in mind that the Reactive Streams interfaces (Publisher/Subscription/Subscriber) are modeling the low-level infrastructure for passing streams between execution units, and errors on this level are precisely the failures that we are talking about on the higher level that is modeled by Akka Streams.
@@@
There is only limited support for treating `onError` in Akka Streams compared to the operators that are available for the transformation of data elements, which is intentional in the spirit of the previous paragraph. Since `onError` signals that the stream is collapsing, its ordering semantics are not the same as for stream completion: transformation operators of any kind will collapse with the stream, possibly still holding elements in implicit or explicit buffers. This means that data elements emitted before a failure can still be lost if the `onError` overtakes them.
The ability for failures to propagate faster than data elements is essential for tearing down streams that are back-pressured—especially since back-pressure can be the failure mode (e.g. by tripping upstream buffers which then abort because they cannot do anything else; or if a dead-lock occurred).
### The semantics of stream recovery
A recovery element (i.e. any transformation that absorbs an `onError` signal and turns that into possibly more data elements followed normal stream completion) acts as a bulkhead that confines a stream collapse to a given region of the stream topology. Within the collapsed region buffered elements may be lost, but the outside is not affected by the failure.
This works in the same fashion as a `try`–`catch` expression: it marks a region in which exceptions are caught, but the exact amount of code that was skipped within this region in case of a failure might not be known precisely—the placement of statements matters.
| 109.540323 | 765 | 0.809615 | eng_Latn | 0.999782 |
9a6d73bb1d7bda4d2c62b6b38dc63774305426ac | 376 | md | Markdown | content/posts/2013/11/2013-11-02-starting-new-blog/index.md | justinyoo/gridsome-starter-bleda | 662d48c1d6a32e95b8f0ff4a02541e7ed2a36f41 | [
"MIT"
] | null | null | null | content/posts/2013/11/2013-11-02-starting-new-blog/index.md | justinyoo/gridsome-starter-bleda | 662d48c1d6a32e95b8f0ff4a02541e7ed2a36f41 | [
"MIT"
] | null | null | null | content/posts/2013/11/2013-11-02-starting-new-blog/index.md | justinyoo/gridsome-starter-bleda | 662d48c1d6a32e95b8f0ff4a02541e7ed2a36f41 | [
"MIT"
] | 2 | 2020-02-08T11:05:32.000Z | 2020-08-11T16:16:56.000Z | ---
title: "새 술은 새 부대에"
date: "2013-11-02"
slug: starting-new-blog
description: ""
author: Justin-Yoo
tags:
- life-in-australia
fullscreen: false
cover: ""
---
블로그가 폭파된 후 방치당한지 수백만년 만에 다시 세팅. 마침 무료 호스팅도 생겼겠다, 하나 다시 열었음. 이것도 언제까지 다시 운영할런지는 모르겠다마는 그래도 또 힘 닿는 데까지! 기존의 블로그들을 백업해서 이리로 다 옮겨오려고 했다마는, 그런데 신경을 쓰느니 기존 것들은 걍 링크로 냅두고, 여기서 새로 시작하는 것이 낫겠다는 판단도 했음.
**야튼, 다시 한 번 으쌰으쌰.**
| 23.5 | 192 | 0.683511 | kor_Hang | 1.00001 |
9a6dd9f9d0281f32bbb8bae09ea7ff9118a135dc | 693 | md | Markdown | README.md | zuber1077/Group_Chat | 60286ab5da69b470095461288612f6a608292d6b | [
"MIT"
] | 10 | 2018-04-24T09:54:42.000Z | 2022-02-22T02:40:03.000Z | README.md | zuber1077/Group_Chat | 60286ab5da69b470095461288612f6a608292d6b | [
"MIT"
] | 1 | 2018-06-20T15:28:33.000Z | 2018-06-23T04:06:20.000Z | README.md | zuber1077/Group_Chat | 60286ab5da69b470095461288612f6a608292d6b | [
"MIT"
] | 11 | 2018-05-12T04:39:35.000Z | 2022-02-21T19:32:11.000Z | GPchat - Private & Group chat using nodeJS
==========================================
[](https://zuham.herokuapp.com)
[](https://github.com/zuber1077/Group_Chat/stargazers)
## Usage
`npm install` --> `node server.js`
## License
>You can check out the full license [here](https://github.com/zuber1077/Group_chat/LICENSE)
This project is licensed under the terms of the **MIT** license.
| 33 | 131 | 0.69697 | kor_Hang | 0.218265 |
9a6e07492904bc771dcb2352ddd8a09dc16ff6f0 | 3,349 | md | Markdown | docs/slim.md | peter279k/database-2 | 68aea0478e86cb3b70494619b0febaf94968359c | [
"MIT"
] | 14 | 2017-10-24T16:11:52.000Z | 2019-11-14T12:41:40.000Z | docs/slim.md | peter279k/database-2 | 68aea0478e86cb3b70494619b0febaf94968359c | [
"MIT"
] | 8 | 2019-07-09T07:53:42.000Z | 2019-07-18T14:42:44.000Z | docs/slim.md | peter279k/database-2 | 68aea0478e86cb3b70494619b0febaf94968359c | [
"MIT"
] | 4 | 2021-11-30T08:12:40.000Z | 2021-12-31T18:17:35.000Z | ---
layout: default
title: Slim 4 integration
nav_order: 8
---
# Slim 4 integration
## Requirements
* PHP 7.4+
* MySQL 5.7+
* Composer
* [A Slim 4 application](https://odan.github.io/2019/11/05/slim4-tutorial.html)
* A DI container (PSR-11), e.g. PHP-DI
## Installation
To add the query builder to your application, run:
```
composer require selective/database
```
## Configuration
Add the database settings to Slim’s settings array, e.g `config/settings.php`:
```php
// Database settings
$settings['db'] = [
'driver' => 'mysql',
'host' => 'localhost',
'database' => 'test',
'username' => 'root',
'password' => '',
'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
'prefix' => '',
'options' => [
// Turn off persistent connections
PDO::ATTR_PERSISTENT => false,
// Enable exceptions
PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION,
// Emulate prepared statements
PDO::ATTR_EMULATE_PREPARES => true,
// Set default fetch mode to array
PDO::ATTR_DEFAULT_FETCH_MODE => PDO::FETCH_ASSOC,
// Set character set
PDO::MYSQL_ATTR_INIT_COMMAND => 'SET NAMES utf8mb4 COLLATE utf8mb4_unicode_ci'
],
];
```
Add the following container definitions into your `config/container.php` file:
```php
<?php
use Psr\Container\ContainerInterface;
use Selective\Config\Configuration;
use Selective\Database\Connection;
use Slim\App;
//...
return [
// ...
// Database connection
Connection::class => function (ContainerInterface $container) {
return new Connection($container->get(PDO::class));
},
PDO::class => function (ContainerInterface $container) {
$settings = $container->get(Configuration::class)->getArray('db');
$driver = $settings['driver'];
$host = $settings['host'];
$dbname = $settings['database'];
$username = $settings['username'];
$password = $settings['password'];
$charset = $settings['charset'];
$flags = $settings['flags'];
$dsn = "$driver:host=$host;dbname=$dbname;charset=$charset";
return new PDO($dsn, $username, $password, $flags);
},
];
```
### Usage
You can inject the `Connection` instance into your repository like this:
```php
<?php
namespace App\Domain\User\Repository;
use DomainException;
use Selective\Database\Connection;
/**
* Repository.
*/
final class UserCreatorRepository
{
/**
* @var Connection The database connection
*/
private Connection $connection;
/**
* The constructor.
*
* @param Connection $connection The database connection
*/
public function __construct(Connection $connection)
{
$this->connection = $connection;
}
/**
* Get user by id.
*
* @param int $userId The user id
*
* @return array The user row
*/
public function getUserById(int $userId): array
{
$query = $this->connection->select()->from('users');
$query->columns(['id', 'username', 'email']);
$query->where('id', '=', $userId);
$row = $query->execute()->fetch() ?: [];
if(!$row) {
throw new DomainException(sprintf('User not found: %s', $userId));
}
return $row;
}
}
```
**Next page:** [Select](selects.md)
| 21.888889 | 86 | 0.60854 | eng_Latn | 0.294263 |
9a6e0f0a51b67fc96e82c5c8d08aeb36e82d97a6 | 6,669 | md | Markdown | README.md | Natali-Skv/VVT-i | 6dccd8d29abebf565325a0b52e0c3808580b5ae4 | [
"BSD-3-Clause"
] | null | null | null | README.md | Natali-Skv/VVT-i | 6dccd8d29abebf565325a0b52e0c3808580b5ae4 | [
"BSD-3-Clause"
] | null | null | null | README.md | Natali-Skv/VVT-i | 6dccd8d29abebf565325a0b52e0c3808580b5ae4 | [
"BSD-3-Clause"
] | null | null | null | <div align="left">
## 🔑 VVT-i
<h4>Linux-user-friendly console utility that provides terminal access to remote file storage with different user modes</h4>
<br>
## Code analysis ⚙️📈📈
[](https://app.travis-ci.com/frontend-park-mail-ru/2021_2_MonKeys)
[](https://github.com/danmar/cppcheck)
<br>
<br>
<br>
## 📝 Content table
- [About project](#about)
- [Usecase gifs](#gifs)
- [Launching the application](#getting_started)
- [Usage in real life](#usage)
- [Libraries & technologies](#lib_technologies)
- [Languages](#languages)
- [Developers](#developers)
- [Mentors & tutors](#mentors_tutors)
- [Sources for project presentation](#presentation_src)
<br>
## 🧐 About project<a name = "about"></a>
Большинство студентов нашего ВУЗа встречались с такой проблемой: пришел на лабы по программированию, например, даже выполнил её на университетском компьютере, но забыл флешку... тогда приходится выходить в интернет и авторизовываться в соцсети/почте/облачном хранилище, чтобы закинуть свою лабу -- довольно долго, так еще и можно не помнить пароль или забыть выйти из своего аккаунта.
**Наша дружная команда объединила усилия для решения этой проблемы!**
Решением этой проблемы является создание продукта, который будет максимально простым в использовании и предусматривать работу с неавторизованными пользователями.
Наш проект удовлетворяет этим требованиям. Он имеет Linux-friendly синтаксис команд, что также упрощает взаимодействие с продуктом. Помимо этого, для удобства пользования используется отправка уведомлений на почту, указанную пользователем. Это помогает ему не хранить код извне, а получить его в удобной пользователю момент через почту.
<br>
## 🔆 Sources for project presentation <a name = "presentation_src"></a>
Ссылка на презентацию: [Презентация](https://docs.google.com/presentation/d/1GjSVECv2N7I9ksSQ0BhA4O3BCKgyCcM_lY23q1cRnEg/edit#slide=id.p)
<br>
## :red_circle: the "master" branch contains the server side code, and the "client" branch contains the client side code
<br>
## Usecases gifs<a name = "gifs"></a>
- сценарий работы неавторизованного пользователя (код для олучения файла отправляется пользователю на почту)
- сценарий регистрации, логина и логаута пользователя
- сценарий работы авторизованного пользователя (загрузка и скачивание файла)
- сценарий работы авторизованного пользователя (создание директорий)
- сценарий работы авторизованного пользователя (переход по директориям)
<br>
## 🏁 Launching the application <a name = "getting_started"></a>
Пошаговая инструкция, как запустить приложение у себя
Введите команду для клонирования репозитория приложения:
```
git clone git@github.com:yutfut/VVT-i.git
```
Через терминал зайдите в директорию сервера и выполните следующие команды:
```
sudo ./server.sh build
sudo ./server.sh create --config
```
Теперь сервер готов к работе, остается только заполнить конфигурационный файл,
указав в нем количество процессов-воркеров, пути для логов, порт и адрес сервера,
а также заполнить блочную директиву database, и простую fs_root с путем до корня файловой системы.
Запуск сервера:
```
sudo ./server.sh start
```
Запуск клиента:
```
./vvti_client
```
Для получения информации о командах, предварительно запустив клиента, введите в терминале:
```
help
```
<br>
## 🌟 Usage in real life <a name="usage"></a>
Используя наш сервис, можно не заботиться о наличии с собой переносного носителя или данных своего аккаунта, к тому же сервис исключает утечку личных данных в случае если пользователь выходит, забывая выйти из своего аккаунта.
Пользователь может с любого компьютера, на котором есть 5-7Мб свободного места, отправить и получить свои файлы максимально быстро и безопасно без лишних действий. Для работы с клиентским приложением достаточно установить пару легковесных библиотек и более ни о чем не заботиться, сервис все сделает сам.
<br>
<br>
## ⛏️ Libraries & technologies<a name = "lib_technologies"></a>
[PostgreSQL](https://www.postgresql.org/) - Database
[Fmt](https://github.com/fmtlib/fmt) - Formatting library
[LibPQXX](http://pqxx.org/development/libpqxx/) - The C++ connector for PostgreSQL
[Boost](https://www.boost.org/) - Multiprocessing Logging & gzip file compression
[Epoll](https://ru.wikipedia.org/wiki/Epoll) - Asynchronous Multiplex Technology
[JWT++](https://github.com/arun11299/cpp-jwt) - JWT Authorization Technology
[Mailio](https://github.com/karastojko/mailio) - Send Emails Module
[LIBMAGIC](https://man7.org/linux/man-pages/man3/libmagic.3.html) - Getting file type for compression
[OpenSSL](https://www.openssl.org/)
<br>
<br>
## Languages <a name = "languages"></a>
<br>
<br>
## ✍️ Developers <a name = "developers"></a>
[@skvortsova_na](https://github.com/Natali-Skv) - Скворцова Наталья [Filesystem development & Server development]
[@And_Dayk](https://github.com/Andrey123815) - Дьяконов Андрей [Database development]
[@kirill555101](https://github.com/kirill555101) - Каташинский Кирилл [Server development]
[@yut_fut](https://github.com/yutfut) - Голубев Сергей [Team Lead, Client development]
<br>
<br>
## 🙇 Mentors & tutors <a name = "mentors_tutors"></a>
Наш ментор:
[@znjuko](https://github.com/znjuko) - Никита Черных
Преподаватели:
[@Ciberst](https://github.com/ciberst) - Александр Жиров
И вся команда Технопарк VK!
<br>
<br>
| 35.473404 | 384 | 0.740741 | rus_Cyrl | 0.453937 |
9a6ed6dc47de28af2306d86f7c384f921e882a14 | 2,590 | md | Markdown | docs/mfc/reference/type-library-access.md | FlorianHaupt/cpp-docs.de-de | 0ccd351cf627f1a41b14514c746f729b778d87e3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/reference/type-library-access.md | FlorianHaupt/cpp-docs.de-de | 0ccd351cf627f1a41b14514c746f729b778d87e3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/reference/type-library-access.md | FlorianHaupt/cpp-docs.de-de | 0ccd351cf627f1a41b14514c746f729b778d87e3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Zugreifen auf die Typbibliothek
ms.date: 11/04/2016
f1_keywords:
- vc.mfc.macros
helpviewer_keywords:
- type libraries [MFC], accessing
ms.assetid: a03fa7f0-86c2-4119-bf81-202916fb74b3
ms.openlocfilehash: 4dc5a445f4a7736182350c16720686ca7e0bc27c
ms.sourcegitcommit: 6052185696adca270bc9bdbec45a626dd89cdcdd
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 10/31/2018
ms.locfileid: "50468379"
---
# <a name="type-library-access"></a>Zugreifen auf die Typbibliothek
Typbibliotheken verfügbar Schnittstellen, die der OLE-Steuerelements für andere OLE-fähigen Anwendungen. Jeder OLE-Steuerelements benötigen eine Typbibliothek aus, wenn eine oder mehrere Schnittstellen sind verfügbar gemacht werden.
Die folgenden Makros zulassen ein OLE-Steuerelements, um Zugriff auf eine eigene Typbibliothek bereitzustellen:
### <a name="type-library-access"></a>Zugreifen auf die Typbibliothek
|||
|-|-|
|[DECLARE_OLETYPELIB](#declare_oletypelib)|Deklariert eine `GetTypeLib` Memberfunktion eines OLE-Steuerelements (muss in der Klassendeklaration verwendet werden).|
|[IMPLEMENT_OLETYPELIB](#implement_oletypelib)|Implementiert eine `GetTypeLib` Memberfunktion eines OLE-Steuerelements (muss in der klassenimplementierung verwendet werden).|
## <a name="declare_oletypelib"></a> DECLARE_OLETYPELIB
Deklariert die `GetTypeLib` Memberfunktion der Steuerelementklasse.
```
DECLARE_OLETYPELIB(class_name)
```
### <a name="parameters"></a>Parameter
*CLASS_NAME*<br/>
Der Name des der Control-Klasse, die im Zusammenhang mit der Typbibliothek.
### <a name="remarks"></a>Hinweise
Verwenden Sie dieses Makro in der Headerdatei des Steuerelement-Klasse.
### <a name="requirements"></a>Anforderungen
**Header:** afxdisp.h
## <a name="implement_oletypelib"></a> IMPLEMENT_OLETYPELIB
Das Steuerelement implementiert die `GetTypeLib` Member-Funktion.
```
IMPLEMENT_OLETYPELIB(class_name, tlid, wVerMajor, wVerMinor)
```
### <a name="parameters"></a>Parameter
*CLASS_NAME*<br/>
Der Name des der Control-Klasse, die im Zusammenhang mit der Typbibliothek.
*tlid*<br/>
Die ID der Typbibliothek.
*wVerMajor*<br/>
Die Typ-Bibliothek Hauptversionsnummer.
*wVerMinor*<br/>
Die Typ-Bibliothek Nebenversionsnummer.
### <a name="remarks"></a>Hinweise
Dieses Makro muss in der Implementierungsdatei für jede Steuerelementklasse angezeigt werden, die die DECLARE_OLETYPELIB-Makro verwendet.
### <a name="requirements"></a>Anforderungen
**Header:** afxdisp.h
## <a name="see-also"></a>Siehe auch
[Makros und globale Variablen](../../mfc/reference/mfc-macros-and-globals.md)
| 31.204819 | 232 | 0.781853 | deu_Latn | 0.8923 |
9a6f4cadaefa17668dfa228c9f9d471d961dc571 | 4,842 | md | Markdown | doc/technical.md | willie68/GoBlobStore | 9bc215e51a6d45cfbb05ebd90437efb1dc88fb08 | [
"Apache-2.0"
] | null | null | null | doc/technical.md | willie68/GoBlobStore | 9bc215e51a6d45cfbb05ebd90437efb1dc88fb08 | [
"Apache-2.0"
] | 16 | 2021-10-08T11:38:22.000Z | 2022-03-31T14:07:46.000Z | doc/technical.md | willie68/GoBlobStore | 9bc215e51a6d45cfbb05ebd90437efb1dc88fb08 | [
"Apache-2.0"
] | null | null | null | The blobstorage consist of some storage implementations and a business manager.
## dao/simplefile
This is the implementation of a simple file storage.
Every tenant has it's own folder.
Retention files are stored in a separate folder called `retention`.
The binary file is stored into a double hierarchical folder structure, as the first 2 digits of the id are the first folder, third and forth digits represent the second subfolder. File name is the id and the postfix `.bin`
Because of some compatibility with older java services, reading can be done in a simple folder structure. So the base folder is the tenant.
The description is placed beside the binary and has the extension `.json`.
### Parameters
`rootpath`: path to the file system to store the data
## dao/s3
The implementation of the s3 storage provider.
tenants are placed into a separate file called `storelist.json`. Every file is automatically encrypted.
every tenant got his own base folder.
Retention files are stored in a separate folder called `retention`.
The binary file is stored into a double hierarchical folder structure, as the first 2 digits of the id are the first folder, third and forth digits represent the second sub folder. File name is the id and the postfix `.bin`
The description is placed as user properties the the file.
### Parameters
`endpoint`: URL to the s3 endpoint
`insecure`: bool true for not checking the SSL certificate (mainly for self signed certificates)
`bucket`: the bucket to use
`accessKey`: the access key of the s3 storage
`secretKey`: the secret key of the s3 storage
`password`: a salt to the password encryption part for storing encryption
## dao/fastcache
The implementation of cache storage provider. This implementation usage a LRU cache mechanism. The description files are stored in memory for all cached blobs. The files are stored on a separate file system (fast bound SSD Storage or similar). If the file size <mffrs the file is stored into the memory, too. In the option you can define, how many files are stored into the cache and file system. And you can define the max ram usage for the in memory stored files. Both will be checked automatically.
### Parameters
`rootpath`: path to the filesystem to store the cached data
`maxcount`: how many files are stored into the cache
`maxramusage`: for files <mffrs max RAM usage.
`maxfilesizeforram`: file size to put into the in memory cache (mffrs)
## dao/business
Here is the implementation of the business part of the storage. The mainstorage class handles the usages of backup and cached storage as the base storage class.
## dao/retentionmanager
Because of some circle dependencies the retention manager class must be in the main dao folder. At the moment only the single node retention manager is implemented, which will take control over all retention related parts. It can consist with other single retention manager nodes, but they will not share any workload. Every retention manager will have a full list of all retentions of the complete system. So on a multi node setup, there can be some errors present because f missing retention files (because another retention manager was faster on deletion)
# FastCache
The FastCache is an LRU implementation with 2-level data storage. All files in the cache are stored on a separate volume. This should be a very fast local medium. (e.g. local SSD) Files up to a certain file size (100kb) are also stored in the RAM.
First you set the maximum number of files in the cache with an option. These are all stored on the assigned volume.
In addition, a memory size is specified that specifies how much memory the files stored in the memory can use. Thus, small files can be served directly from the memory, which brings additional performance.
Why LRU? There is a corresponding note here: https://dropbox.tech/infrastructure/caching-in-theory-and-practice
A bloom filter is also used to determine whether a file is in the cache. Thus, the CacheMiss case can be decided quickly in most cases (the setting is 0.1%).
# Search/Index
The first implemented index engine is mongodb.
For parsing the query string i use https://github.com/mna/pigeon and a PEG grammar based on https://github.com/elireisman/go_es_query_parser
This is one of the moving targets. You will find the peg file in build/pigeon/parser.peg
There is much more implemented in the parser file, but not everything is working. So i only documented the working parts in the readme. In addition, various automated tests are still missing. Here, above all, the evaluation of the results. The parser will be generated into pkg/model/query
Be ware the parser itself is not thread safe, so a serialization is done in the API. | 50.968421 | 560 | 0.770962 | eng_Latn | 0.999634 |
9a70348dd9362c17e218c0d7433c71c898ca7bf2 | 2,888 | md | Markdown | ReadMe.md | dita-community/org.dita-community.pdf-page-break | 8d57819fccaba071362279c30133970a53ec00e7 | [
"Apache-2.0"
] | 1 | 2017-12-31T04:14:12.000Z | 2017-12-31T04:14:12.000Z | ReadMe.md | dita-community/org.dita-community.pdf-page-break | 8d57819fccaba071362279c30133970a53ec00e7 | [
"Apache-2.0"
] | 1 | 2018-11-23T13:59:36.000Z | 2018-11-23T14:30:15.000Z | ReadMe.md | dita-community/org.dita-community.pdf-page-break | 8d57819fccaba071362279c30133970a53ec00e7 | [
"Apache-2.0"
] | null | null | null | # PDF Page Break Plugin for DITA-OT
This plugin for [DITA Open Toolkit][1] is based on a [blog post][2] by Radu Coravu of Syncro Soft, the makers of [oXygen XML Editor][3].
The instructions from the original post are included here for convenience:
---
## DITA PDF publishing - Force page breaks between two block elements
[blog.oxygenxml.com](http://blog.oxygenxml.com/2015/04/dita-pdf-publishing-force-page-breaks.html) * by Radu Coravu * April 29, 2015
Let's say that at some point in your DITA content you have two block level elements, like for example two paragraphs:
```xml
<p>First para</p>
<p>Second para</p>
```
and you want to force in the PDF output a page break between them.
Here's how a DITA Open Toolkit plugin which would achieve this could be implemented:
1. You define your custom processing instruction which marks the place where a page break should be inserted in the PDF, for example:
```xml
<p>First para</p>
<?pagebreak?>
<p>Second para</p>
```
2. In the **DITA Open Toolkit** distribution in the plugins directory you create a new plugin folder named for example `pdf-page-break`.
3. In this new folder create a new `plugin.xml` file with the content:
```xml
<plugin id="com.yourpackage.pagebreak">
<feature extension="package.support.name" value="Force Page Break Plugin"/>
<feature extension="package.support.email" value="support@youremail.com"/>
<feature extension="package.version" value="1.0.0"/>
<feature extension="dita.xsl.xslfo" value="pageBreak.xsl" type="file"/>
</plugin>
```
The most important feature in the plugin is that it will add a new XSLT stylesheet to the XSL processing which produces the PDF content.
4. Create in the same folder an **XSLT** stylesheet named `pageBreak.xsl` with the content:
```xml
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
version="1.0">
<xsl:template match="processing-instruction('pagebreak')">
<fo:block break-after="page"/>
</xsl:template>
</xsl:stylesheet>
```
5. Install your plugin in the **DITA Open Toolkit** by running the DITA-OT Ant integrator task.
If you are running the publishing from **Oxygen XML Editor** you can use the predefined transformation scenario: [http://www.oxygenxml.com/doc/ug-oxygen/#topics/dita-ot-install-plugin.html](http://www.oxygenxml.com/doc/ug-oxygen/#topics/dita-ot-install-plugin.html).
If you run DITA-OT from the command line please follow these guidelines:
[http://www.dita-ot.org/2.0/dev_ref/plugins-installing.html](http://www.dita-ot.org/2.0/dev_ref/plugins-installing.html).
---
[1]: http://www.dita-ot.org/
[2]: http://blog.oxygenxml.com/2015/04/dita-pdf-publishing-force-page-breaks.html
[3]: http://www.oxygenxml.com/
| 40.111111 | 271 | 0.704294 | eng_Latn | 0.704602 |
9a7047202221a0ef47f28034316f619f29b3c180 | 2,471 | md | Markdown | doc/Chapter 2/Exercise 2.14.md | CosVVeLL/sicp | 5e51b5cdf2161a8295ff97c31e61c9617e087da6 | [
"MIT"
] | 1 | 2021-02-10T17:59:35.000Z | 2021-02-10T17:59:35.000Z | doc/Chapter 2/Exercise 2.14.md | CosVVeLL/sicp | 5e51b5cdf2161a8295ff97c31e61c9617e087da6 | [
"MIT"
] | null | null | null | doc/Chapter 2/Exercise 2.14.md | CosVVeLL/sicp | 5e51b5cdf2161a8295ff97c31e61c9617e087da6 | [
"MIT"
] | 1 | 2022-01-13T18:11:45.000Z | 2022-01-13T18:11:45.000Z | ## [Chapter 2](../index.md#2-Building-Abstractions-with-Data)
### Exercise 2.14
Demonstrate that Lem is right. Investigate the behavior of the system on a variety of arithmetic expressions. Make some intervals _A_ and _B_, and use them in computing the expressions _A_/_A_ and _A_/_B_. You will get the most insight by using intervals whose width is a small percentage of the center value. Examine the results of the computation in center-percent form (see [exercise 2.12](./Exercise%202.12.md)).
### Solution
Проведем небольшой эксперимент с процедурами `parl1` и `parl2`:
```scheme
(define (par1 r1 r2)
(div-interval (mul-interval r1 r2)
(add-interval r1 r2)))
(define (par2 r1 r2)
(let ((one (make-interval 1 1)))
(div-interval one
(add-interval (div-interval one r1)
(div-interval one r2)))))
(define i1 (make-center-percent 1000 1))
(define i2 (make-center-percent 2000 5))
(par1 i1 i1)
; => (485.1980198019802 . 515.2020202020202)
(par2 i1 i1)
; => (495 . 505)
(par1 i1 i2)
; => (604.823151125402 . 733.910034602076)
(par2 i1 i2)
; => (650.8650519031141 . 681.9935691318328)
```
Можем заметить, что в процедуре `parl2` инервалы получаются с меньшей погрешностью. В задании нам предложили создать пару интервалов и произвести два деления — _A/A_ и _A/B_, а также обратить внимание на центр интервалов и погрешность в процентах. Сделаем это с уже созданными интервалами `i1` (990 . 1010) и `i2` (1900 . 2100).
```scheme
d1-1 ; => (0.9801980198019802 . 1.02020202020202)
d1-2 ; => (0.4714285714285714 . 0.531578947368421)
(center d1-1) ; => 1.000200020002
(center d1-2) ; => 0.5015037593984962
(percent d1-1) ; => 1.9998000199979968
(percent d1-2) ; => 5.997001499250374
(percent i1) ; => 1
(percent i2) ; => 5
(center i1) ; => 1000
(center i2) ; => 2000
```
Из полученных результатов увидел закономероность, что погрешность в процентах итогового интервала примерно равна сумме погрешностей в процентах интервала-делимого и интервала-делителя.
```
1.9998000199979968 ~ 1 + 1
5.997001499250374 ~ 1 + 5
```
Вот ещё пара проверок с этими же интервалами:
```scheme
(define d2-2 (div-interval i2 i2))
(define d2-1 (div-interval i2 i1))
d2-2 ; => (0.9047619047619048 . 1.1052631578947367)
d2-1 ; => (1.8811881188118813 . 2.121212121212121)
(percent d2-2) ; => 9.975062344139646
(percent d2-1) ; => 5.997001499250369
```
```
9.975062344139646 ~ 5 + 5
5.997001499250369 ~ 5 + 1
```
| 32.090909 | 416 | 0.69567 | eng_Latn | 0.097447 |
9a707e913a05aa46b6753c6bb2d77358b15ba7b5 | 5,721 | md | Markdown | _posts/2018-10-31-Download-pearson-algebra-2-common-core-workbook-answers.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2018-10-31-Download-pearson-algebra-2-common-core-workbook-answers.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2018-10-31-Download-pearson-algebra-2-common-core-workbook-answers.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Pearson algebra 2 common core workbook answers book
Story of the Barber's Fifth Brother xxxii Indeed, I could relate unto thee, i, loud sob reached our ears, not without difficulty. resemble. "The question is: would you be willing to give it?" said the grey man. He tasted the liquor, through the pages of books. " (Dragons are generally referred to both in Hardic and Kargish as astray, beyond these shores, with a gray plastic knob on the top, "You may go out now, was connected to the western part of Terranova via an isthmus that narrowed to a neck below the equator; Artemis lay farther to the east, 'Pay what is due from thee, but in her serene face and her bird-bright pearson algebra 2 common core workbook answers eyes. " "The baby's small but healthy. Selene held on. "But it was only a miniature collie. No fence protects the If to my favours thou aspire and covet me, 172; looks of astonishment and numerous frowns. " manned with 20 men. " Sitting in the co-pilot's chair with her back to the lounge, airy clean. It's only been fifteen days. Excuse me, more than once admirable determination. farther from them they saw her then, and the behind her, just went bing-bong, El Melik ez Zahir Rukneddin Bibers el Bunducdar and pearson algebra 2 common core workbook answers Sixteen, heavier boned, and then thought to ask him if he might want a bath, as though a great weight were unfortunate a result for the greater part pearson algebra 2 common core workbook answers the crew? He might spend this retainer on beer, Small wars unlikely to escalate into worldwide clashes should be viewed not as and toward the end I believed that they were there with me. Darlene's voice trailed off into an incoherent babbling, the word of a teenage Negro girl would have greater weight than Junior's clean record. The questions and answers, defended by a thousand spells against the present pearson algebra 2 common core workbook answers, they were obliged to hew it down, and what everybody knows is true turns out to be what some people used to think. RUN. 1554 and was on the way plundered by the Dutch (_Purchas_, it will be Selene's decision. Not a thing. For a every childhood, with an underlying spice of turpentine, there could be no concessions, he'd seen no reason to change his mind, backward-hooked fangs exposed to their full wicked arc. She was busty: hammered soup pots as breasts, and for awhile he didn't know why. "He's still here?" He could have killed Vanadium while the cop slept; however, rather than by check or credit card. the balls!" you. " Pearson algebra 2 common core workbook answers stood, his expression suddenly serious. But the curer from the south said he wasn't dead, as in modern operations. He unlocked the steel door and stepped into a small, now I was not so its fate. Foxes, doesn't amount to pearson algebra 2 common core workbook answers much, c, excessive for a woman. The same kind of destructive parasitism by its own masses, opening his throat and one or both of his carotid arteries, Leilani said. 156 all his chips on a tactic of complete candor, or reindeer Suddenly Leilani was scared, watching the sunset, screen the telltale energy signature that only Curtis emits. They appeared to be taking this north-east voyages of the English and the Dutch, The Ninth. want of fuel, the flickering candlelight contributed not to a romantic "So what about the nuts?" Jay asked. I feel surrounded by a confused mass of lofty shattered mountain tops, I remember. "Didn't he tell us he was a ship carpenter. He had fallen down in a fit in San's doorway? A little special tools for cutting it up. She was profusely apologetic, and this one is always ready to be amused, Lucy?" Lang asked pearson algebra 2 common core workbook answers, they are pearson algebra 2 common core workbook answers on getting away from flying bullets, had been set up regarding the state of the ice As Curtis realizes that somehow he has further offended her, yes," Irioth said, as though to retrieve something, Pegu of the ruby. Brandy would give her that excuse and spare her the pain of caring. bloody intent, he hadn't been able to find anything to smile about, toward the inverted ceiling and also backward. Irian second, for this is my slave-girl, I sent our boat on shore to fetch Nanook looked mildly surprised, only I had time, the right whale (_Balaena mysticetus_ L. She was silent. They sound more like boars than piggies. She had been thinking about scraping his child out of her womb without even telling him. My blood runs silver. "Disappointing, acceptant as always, and it was remarkable that Merchant of Cairo and the Favourite of the Khalif El Maraoun El Hakim bi Amrillah. of crisp new hundred-dollar bills from an inside jacket pocket. Some keep tributaries almost met, with lots of coverlets and satiny drapes. 173; other has wintered in the old world, for the space of three and thirtie yeeres. But this boat too did not come back? 157 [ to match entry in index and confirmed on Internet ] bright the hawk's flight Story of King Bekhtzeman. It is safe. [52] file:D|Documents20and20Settingsharry. He All Animals Are Vegetables, he couldn't claim perfection, till he could pay me, which is unsurpassed by the many She moved her head. bathing-shed open to the street, almost the lips of a girl! "It's pi to ten places. The other car had always returning that portion of the funds which might not be required, Merrick drew a long breath, but it might be they'd pay a bit of ivory for what they want. At first I misread it as "orgasm? "I love you, and said, the Obi and the "Sybir" are to "On TV, sun in the heart! | 635.666667 | 5,601 | 0.784828 | eng_Latn | 0.999912 |
9a71c13b2187800cdc1f5a5770843a66ba799f53 | 61 | md | Markdown | Education/TSH_video/Timur_Video_Node.js/part_10/NodeServer-master/impress-simple/applications/example/static/README.md | legioner9/Node_Way_source_2 | 04d1980bfe4e7c42ada4ccd7f54a14e9ceca7c42 | [
"MIT"
] | null | null | null | Education/TSH_video/Timur_Video_Node.js/part_10/NodeServer-master/impress-simple/applications/example/static/README.md | legioner9/Node_Way_source_2 | 04d1980bfe4e7c42ada4ccd7f54a14e9ceca7c42 | [
"MIT"
] | 1 | 2021-02-24T21:17:25.000Z | 2021-05-03T07:38:41.000Z | Education/TSH_video/Timur_Video_Node.js/part_10/NodeServer-master/impress-simple/applications/example/static/README.md | legioner9/Node_Way_source_2 | 04d1980bfe4e7c42ada4ccd7f54a14e9ceca7c42 | [
"MIT"
] | null | null | null | Folder for static files: client-side js, images, styles, etc. | 61 | 61 | 0.770492 | eng_Latn | 0.790722 |
9a72022f7cd08d77b3a0b95519535befddf22fc4 | 989 | md | Markdown | _posts/2016-02-20-Mac-Duggal-Cassandra-Stone-Style-40403A.md | promsome/promsome.github.io | 69236f5c8f4d9591eec55dafa47ce21914b51851 | [
"MIT"
] | null | null | null | _posts/2016-02-20-Mac-Duggal-Cassandra-Stone-Style-40403A.md | promsome/promsome.github.io | 69236f5c8f4d9591eec55dafa47ce21914b51851 | [
"MIT"
] | null | null | null | _posts/2016-02-20-Mac-Duggal-Cassandra-Stone-Style-40403A.md | promsome/promsome.github.io | 69236f5c8f4d9591eec55dafa47ce21914b51851 | [
"MIT"
] | null | null | null | ---
layout: post
date: 2016-02-20
title: "Mac Duggal Cassandra Stone Style 40403A"
category: Mac Duggal
tags: [Mac Duggal]
---
### Mac Duggal Cassandra Stone Style 40403A
Just **$529.99**
###
<table><tr><td>BRANDS</td><td>Mac Duggal</td></tr></table>
<a href="https://www.readybrides.com/en/mac-duggal/80274-mac-duggal-cassandra-stone-style-40403a.html"><img src="//img.readybrides.com/199777/mac-duggal-cassandra-stone-style-40403a.jpg" alt="Mac Duggal Cassandra Stone Style 40403A" style="width:100%;" /></a>
<!-- break --><a href="https://www.readybrides.com/en/mac-duggal/80274-mac-duggal-cassandra-stone-style-40403a.html"><img src="//img.readybrides.com/199776/mac-duggal-cassandra-stone-style-40403a.jpg" alt="Mac Duggal Cassandra Stone Style 40403A" style="width:100%;" /></a>
Buy it: [https://www.readybrides.com/en/mac-duggal/80274-mac-duggal-cassandra-stone-style-40403a.html](https://www.readybrides.com/en/mac-duggal/80274-mac-duggal-cassandra-stone-style-40403a.html)
| 61.8125 | 273 | 0.737108 | kor_Hang | 0.134554 |
9a7231f47fd0b61f6dac0f32bd66d068614ec038 | 2,174 | md | Markdown | docs/framework/unmanaged-api/hosting/ihostsemaphore-interface.md | BraisOliveira/docs.es-es | cc6cffb862a08615c53b07afbbdf52e2a5ee0990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/hosting/ihostsemaphore-interface.md | BraisOliveira/docs.es-es | cc6cffb862a08615c53b07afbbdf52e2a5ee0990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/hosting/ihostsemaphore-interface.md | BraisOliveira/docs.es-es | cc6cffb862a08615c53b07afbbdf52e2a5ee0990 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: IHostSemaphore (Interfaz)
ms.date: 03/30/2017
api_name:
- IHostSemaphore
api_location:
- mscoree.dll
api_type:
- COM
f1_keywords:
- IHostSemaphore
helpviewer_keywords:
- IHostSemaphore interface [.NET Framework hosting]
ms.assetid: c0765321-656c-441e-bab5-58176292be1e
topic_type:
- apiref
ms.openlocfilehash: 2cf490bcd167b7a498ae21f479f616694ccb5521
ms.sourcegitcommit: 559fcfbe4871636494870a8b716bf7325df34ac5
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 10/30/2019
ms.locfileid: "73139483"
---
# <a name="ihostsemaphore-interface"></a>IHostSemaphore (Interfaz)
Representa la implementación del host de un semáforo para el subprocesamiento.
## <a name="methods"></a>Métodos
|Método|Descripción|
|------------|-----------------|
|[ReleaseSemaphore (método)](../../../../docs/framework/unmanaged-api/hosting/ihostsemaphore-releasesemaphore-method.md)|Aumenta el recuento de la instancia de `IHostSemaphore` actual en la cantidad especificada.|
|[Wait (método)](../../../../docs/framework/unmanaged-api/hosting/ihostsemaphore-wait-method.md)|Hace que la instancia de `IHostSemaphore` actual espere hasta que sea propiedad o transcurra la cantidad de tiempo especificada.|
## <a name="requirements"></a>Requisitos
**Plataformas:** Vea [Requisitos de sistema](../../../../docs/framework/get-started/system-requirements.md).
**Encabezado:** MSCorEE. h
**Biblioteca:** Se incluye como recurso en MSCorEE. dll
**Versiones de .NET Framework:** [!INCLUDE[net_current_v20plus](../../../../includes/net-current-v20plus-md.md)]
## <a name="see-also"></a>Vea también
- [ICLRSyncManager (interfaz)](../../../../docs/framework/unmanaged-api/hosting/iclrsyncmanager-interface.md)
- [IHostAutoEvent (interfaz)](../../../../docs/framework/unmanaged-api/hosting/ihostautoevent-interface.md)
- [IHostManualEvent (interfaz)](../../../../docs/framework/unmanaged-api/hosting/ihostmanualevent-interface.md)
- [IHostSyncManager (interfaz)](../../../../docs/framework/unmanaged-api/hosting/ihostsyncmanager-interface.md)
- [Interfaces de hospedaje](../../../../docs/framework/unmanaged-api/hosting/hosting-interfaces.md)
| 43.48 | 228 | 0.732291 | spa_Latn | 0.246005 |
9a723e96460c28c63feddb8103e84dc9c32cca24 | 2,829 | md | Markdown | occupancy-quickstart/README.md | baanders/digital-twins-samples-csharp | b491654265025ea2e229bfe7989c45952fd67bf4 | [
"MIT"
] | 39 | 2018-10-21T22:34:14.000Z | 2021-12-20T07:43:48.000Z | occupancy-quickstart/README.md | baanders/digital-twins-samples-csharp | b491654265025ea2e229bfe7989c45952fd67bf4 | [
"MIT"
] | 9 | 2018-10-16T17:33:13.000Z | 2020-07-09T16:21:14.000Z | occupancy-quickstart/README.md | Azure-Samples/digital-twins-samples-csharp | 3d26df0473d2585dc2d263dc68639465c6bfc6cb | [
"MIT"
] | 50 | 2018-10-19T13:49:16.000Z | 2021-08-23T17:55:35.000Z | # Occupancy Sample
[](https://opensource.org/licenses/MIT) [](../CONTRIBUTING.md)
Sample code to provision and read resources in a Digital Twins topology via management APIs. It also creates an example function that runs within the Digital Twins instance that computes motion from a sensor in a room in order to determine the occupancy.
## Build and Run the Sample
Below are some details on how to get up and running. For a more detailed walkthrough or more details on how to get the values described below, please see this [quickstart doc](https://docs.microsoft.com/azure/digital-twins/quickstart-view-occupancy-dotnet).
### Update appSettings.json
[appSettings.json](./src/appSettings.json) is used to specify info on which Digital Twins instance to connect to. The three fields you will need to fill in are:
- `ClientId`: The **application ID** of a native Azure Active Directory app that has permissions to call the Azure Digital Twins service.
- `Tenant`: The **directory ID** of a your Azure Active Directory.
- `BaseUrl`: The management api url to your Digital Twins instance (see `appSetting.json` for what this should look like).
- `AadRedirectUri`: A valid **Redirect URI** configured for your Azure Active Directory app. We recommend using the default **Redirect URI** `http://www.localhost:8080`. However, you may also choose another port or domain as required.
### Use a shell
1. Run the app:
```shell
cd src
dotnet restore
dotnet run
```
This will show usage. For a walkthrough of what you can do see [quickstart doc](https://docs.microsoft.com/azure/digital-twins/quickstart-view-occupancy-dotnet).
1. Run tests:
```shell
dotnet test ../tests
```
### Use Visual Studio Code
1. Open the 'occupancy-quickstart' folder in Visual Studio Code.
1. Run the app by using the `F5` key. You can change the command-line parameters in `launch.json`.
1. To build and run tests use the 'Run Task' command in Visual Studio Code and choose `test`.
## Notes
### Authentication
To learn more about configuration, security, and API authentication:
1. See the [role-based access control doc](https://docs.microsoft.com/azure/digital-twins/security-role-based-access-control).
1. See the [Management API doc](https://docs.microsoft.com/azure/digital-twins/security-authenticating-apis).
## Problems
If you run into problems or have questions checkout our [FAQ](./docs/faq.md). If that doesn't help search open and closed [issues](https://github.com/Azure-Samples/digital-twins-samples-csharp/issues) and open a new one if you can't find an answer.
## Licensing and Use
Azure Digital Twins Samples are [MIT Licensed](./LICENSE.md).
| 47.949153 | 258 | 0.751149 | eng_Latn | 0.958977 |
9a731351dd7ad96e3f493854f9e7d97be81236c8 | 8,895 | md | Markdown | articles/site-recovery/avs-tutorial-reprotect.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/site-recovery/avs-tutorial-reprotect.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/site-recovery/avs-tutorial-reprotect.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure-beli virtuális gépek újravédése Azure-beli VMware-megoldáshoz Azure Site Recovery
description: Ismerje meg, hogyan védhető fel újra az Azure VMware-megoldás virtuális gépei az Azure-ba történő feladatátvétel után Azure Site Recovery.
author: Harsha-CS
manager: rochakm
ms.service: site-recovery
ms.topic: tutorial
ms.date: 09/30/2020
ms.author: harshacs
ms.custom: MVC
ms.openlocfilehash: 80ff2f3f3d5fdcf61770889dcdaaf075941b90ff
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: hu-HU
ms.lasthandoff: 10/09/2020
ms.locfileid: "91814572"
---
# <a name="reprotect-from-azure-to-azure-vmware-solution-private-cloud"></a>Ismételt védelem az Azure-ból az Azure VMware-megoldás saját felhőbe
Az Azure VMware-megoldás virtuális gépei Azure-ba történő [feladatátvétele](avs-tutorial-failover.md) után az Azure VMware-megoldás saját felhőbe való visszaállításának első lépéseként újra kell védetté tenni a feladatátvétel során létrehozott Azure-beli virtuális gépeket. Ez a cikk azt ismerteti, hogyan teheti ezt meg.
## <a name="before-you-begin"></a>Előkészületek
1. A [cikk](vmware-azure-prepare-failback.md) lépéseit követve készítse elő a helyreállítást és a feladat-visszavételt, beleértve az Azure-beli folyamat-kiszolgáló beállítását, valamint egy Azure VMware-megoldás saját Felhőbeli fő célkiszolgáló konfigurálását, és konfigurálja a helyek közötti VPN-t vagy a ExpressRoute a feladat-visszavételhez.
2. Győződjön meg arról, hogy az Azure VMware-megoldás saját Felhőbeli konfigurációs kiszolgálója fut, és csatlakozik az Azure-hoz. A feladat-visszavétel során a virtuális gépnek léteznie kell a konfigurációs kiszolgáló adatbázisában. Ellenkező esetben a feladat-visszavétel sikertelen.
3. Törölje az Azure VMware Solution Private Cloud Master célkiszolgálón található összes pillanatképet. Az ismételt védelem nem fog működni, ha vannak Pillanatképek. A virtuális gépen lévő Pillanatképek automatikusan egyesülnek egy újravédelemi feladatokban.
4. Ha a több virtuális gépre kiterjedő konzisztencia érdekében a replikálási csoportba begyűjtött virtuális gépeket újra védelemmel látja el, győződjön meg arról, hogy mindegyikük azonos operációs rendszerrel rendelkezik (Windows vagy Linux), és győződjön meg arról, hogy a telepített fő célkiszolgáló azonos típusú operációs rendszerrel rendelkezik. A replikációs csoportban lévő összes virtuális gépnek ugyanazt a fő célkiszolgáló-kiszolgálót kell használnia.
5. Nyissa meg a feladat-visszavételhez [szükséges portokat](vmware-azure-prepare-failback.md#ports-for-reprotectionfailback) .
6. A feladat-visszavétel előtt ellenőrizze, hogy a vCenter Server csatlakoztatva van-e. Ellenkező esetben a lemezek leválasztása és a virtuális géphez való csatolása meghiúsul.
7. Ha a vCenter-kiszolgáló felügyeli azokat a virtuális gépeket, amelyeken a feladat-visszavételt végzi, győződjön meg arról, hogy rendelkezik a szükséges engedélyekkel. Ha csak olvasási jogosultsággal rendelkező felhasználói vCenter-felderítést végez, és a virtuális gépek védelme, a védelem sikeres és a feladatátvétel működik. Az ismételt védelem során azonban a feladatátvétel meghiúsul, mert az adattárolók nem észlelhetők, és nem szerepelnek az ismételt védelem során. A probléma megoldásához frissítse a vCenter hitelesítő adatait egy [megfelelő fiókkal/engedélyekkel](avs-tutorial-prepare-avs.md#prepare-an-account-for-automatic-discovery), majd próbálja megismételni a feladatot.
8. Ha a virtuális gépek létrehozásához sablont használt, győződjön meg arról, hogy minden virtuális gépnek saját UUID-je van a lemezekhez. Ha az Azure VMware-megoldás virtuálisgép-UUID-je a fő célkiszolgáló UUID-ának összeütközését eredményezi, mert mindkettő ugyanabból a sablonból lett létrehozva, az ismételt védelem sikertelen lesz. Üzembe helyezés egy másik sablonból.
9. Ha egy másik vCenter Server nem tud visszatérni, győződjön meg arról, hogy az új vCenter Server és a fő célkiszolgáló fel van derítve. Általában, ha nem az adattárolók nem érhetők el, vagy nem láthatók az ismételt **védelemben**.
10. Ellenőrizze, hogy a következő helyzetekben nem lehet visszaadni a feladatokat:
- Ha az ESXi 5,5 Free Edition vagy a vSphere 6 hypervisor Free Edition verziót használja. Frissítsen egy másik verzióra.
- Ha Windows Server 2008 R2 SP1 fizikai kiszolgálóval rendelkezik.
- A VMware virtuális gépek nem tudnak visszavenni a Hyper-V-t.
- Az áttelepített virtuális gépek.
- Egy másik erőforráscsoporthoz áthelyezett virtuális gép.
- Egy olyan replika Azure-beli virtuális gép, amelyet töröltek.
- Olyan replika Azure-beli virtuális gép, amely nem védett.
10. [Tekintse át az Ön által használható feladat-visszavételi típusokat – az](concepts-types-of-failback.md) eredeti helyre történő helyreállítást és a másodlagos hely helyreállítását.
## <a name="enable-reprotection"></a>Ismételt védelem engedélyezése
Engedélyezze a replikációt. Az adott virtuális gépek vagy helyreállítási terv ismételt védetté teheti:
- Ha újravédi a helyreállítási tervet, meg kell adnia minden védett gép értékét.
- Ha a virtuális gépek a több virtuális gépre kiterjedő konzisztencia replikációs csoportjához tartoznak, akkor csak helyreállítási terv használatával lehet őket újra védelemmel ellátni. A replikációs csoportba tartozó virtuális gépeknek ugyanazt a fő célkiszolgáló kiszolgálót kell használniuk
>[!NOTE]
>Az Azure-ból a hajdani forrásba az ismételt védelem során eljuttatott adatok mennyisége 0 bájt és az összes védett gép lemezének mérete között lehet, és nem számítható ki.
### <a name="before-you-start"></a>Előkészületek
- Miután egy virtuális gép a feladatátvétel után elindul az Azure-ban, eltarthat egy ideig, amíg az ügynök vissza nem regisztrálja a konfigurációs kiszolgálót (akár 15 percet is igénybe vehet). Ebben az időszakban nem fogja tudni újból védelemmel ellátni, és hibaüzenet jelzi, hogy az ügynök nincs telepítve. Ha ez történik, várjon néhány percet, majd végezze el az ismételt védelem megtörténtét.
- Ha az Azure-beli virtuális gépet egy meglévő Azure VMware Megoldásbeli virtuális gépre szeretné visszaadni, csatlakoztassa a virtuális gép adattárolóit olvasási/írási hozzáféréssel a fő célkiszolgáló ESXi-gazdagépén.
- Ha vissza szeretne térni egy másik helyre, például ha az Azure VMware-megoldás virtuális gépe nem létezik, válassza ki a fő célkiszolgáló számára konfigurált adatmegőrzési meghajtót és adattárat. Ha visszaadja az Azure VMware-megoldás saját felhőjét, a feladat-visszavételi védelmi tervben szereplő virtuális gépek ugyanazt az adattárt használják, mint a fő célkiszolgáló. Ezután létrejön egy új virtuális gép a vCenter-ben.
A következőképpen engedélyezheti az ismételt védelmet:
1. Válassza **a**tár > **replikált elemek**lehetőséget. Kattintson a jobb gombbal a feladatátvétel alatt álló virtuális gépre, majd válassza az **ismételt védelem**lehetőséget. Vagy a parancsgombok közül válassza ki a gépet, majd válassza az **ismételt védelem**lehetőséget.
2. Ellenőrizze, hogy be van-e jelölve az **Azure és a** helyszíni védelem iránya.
3. A **fő célkiszolgáló** és a **folyamat-kiszolgáló**területen válassza ki a helyszíni fő célkiszolgáló és a Process Server kiszolgálót.
4. Az **adattár**mezőben válassza ki azt az adattárolót, amelynek a lemezeit helyre szeretné állítani az Azure VMware-megoldásban. Ezt a beállítást akkor használja a rendszer, ha az Azure VMware-megoldás virtuális gépe törölve van, és új lemezeket kell létrehoznia. Ezt a beállítást a rendszer figyelmen kívül hagyja, ha a lemezek már léteznek. Továbbra is meg kell adnia egy értéket.
5. Válassza ki az adatmegőrzési meghajtót.
6. A feladat-visszavételi szabályzat automatikusan ki van jelölve.
7. A védelem megkezdéséhez kattintson **az OK gombra** .
8. A feladatok megkezdik az Azure-beli virtuális gép replikálását az Azure VMware megoldás saját felhőbe. A **Feladatok** lapon követheti nyomon a folyamat állapotát.
- Ha az ismételt védelem sikeres, a virtuális gép védett állapotba kerül.
- Az Azure VMware megoldás virtuális gépe ki van kapcsolva az ismételt védelem során. Ez elősegíti az adatok konzisztenciáját a replikáció során.
- Az ismételt védelem befejeződése után ne kapcsolja be az Azure VMware megoldás virtuális gépet.
## <a name="next-steps"></a>További lépések
- Ha bármilyen problémába ütközik, tekintse át a [hibaelhárítási cikket](vmware-azure-troubleshoot-failback-reprotect.md).
- Az Azure-beli virtuális gépek védelme után elvégezheti a feladat- [visszavétel futtatását](avs-tutorial-failback.md). A feladat-visszavétel leállítja az Azure-beli virtuális gépet, és elindítja az Azure VMware megoldás virtuális gépet. Némi állásidőt vár az alkalmazáshoz, és ennek megfelelően kiválaszthatja a feladat-visszavételi időt.
| 105.892857 | 689 | 0.81765 | hun_Latn | 1.00001 |
9a73e4ed0e947563a4ce45f607ebc662535c4e3a | 350 | md | Markdown | CHANGELOG.md | janipiippow/dart_my_complex | a82bb326e719f11b88bc6a4a4a7a276b28f9d213 | [
"BSD-3-Clause"
] | null | null | null | CHANGELOG.md | janipiippow/dart_my_complex | a82bb326e719f11b88bc6a4a4a7a276b28f9d213 | [
"BSD-3-Clause"
] | null | null | null | CHANGELOG.md | janipiippow/dart_my_complex | a82bb326e719f11b88bc6a4a4a7a276b28f9d213 | [
"BSD-3-Clause"
] | 1 | 2022-03-15T18:19:00.000Z | 2022-03-15T18:19:00.000Z | # Changelog
## 0.0.1
- Initial version, fast Complex number library!
## 0.0.2
- Changed equals functions to catch identity faster
## 0.0.3
- Made some fields final
- Corrected wrong path in README.md
## 0.0.4
- Learned how to add documentation so that it appears on the pub
- renamed "equal" to "similar"
## 0.1.0
- compatibility with dart2 | 15.217391 | 64 | 0.702857 | eng_Latn | 0.993766 |
9a742a838d5d8a60a2ef3efadb7d121ad39cf7a6 | 918 | md | Markdown | docs/edge-stack/1.4/TODO.md | balazs92117/ambassador-docs | 58168f6acec3be5264df6c4eddb30f17884ccc03 | [
"Apache-2.0"
] | 21 | 2019-05-16T14:58:57.000Z | 2022-02-18T12:11:11.000Z | docs/edge-stack/1.4/TODO.md | balazs92117/ambassador-docs | 58168f6acec3be5264df6c4eddb30f17884ccc03 | [
"Apache-2.0"
] | 157 | 2019-04-10T12:30:50.000Z | 2022-03-26T16:16:32.000Z | docs/edge-stack/1.4/TODO.md | balazs92117/ambassador-docs | 58168f6acec3be5264df6c4eddb30f17884ccc03 | [
"Apache-2.0"
] | 88 | 2019-04-10T12:06:26.000Z | 2022-03-24T17:58:37.000Z | The following pages are deleted and need redirects:
Permanent redirects
* /user-guide/cd-declarative-gitops/ --> /concepts/gitops-continuous-delivery
* /user-guide/gitops-ambassador/ --> /concepts/gitops-continuous-delivery
* /docs/dev-guide/test-in-prod/ --> /concepts/progressive-delivery
* /about/microservices-api-gateways/ --> /concepts/microservices-api-gateways
* Everything else in /about/ --> /docs/about/
Temporary redirects:
* /reference/services/access-control --> /using/filters/
* /concepts/auth-overview --> /using/filters/oauth2
* /reference/authentication --> /using/filters/oauth2
* /user-guide/tracing-tutorial/ --> /howto/
* /reference/configuration/ --> /topics/using/
* /reference/config-format/ --> /topics/using/
* /reference/core/annotations/ --> ??
* /reference/filter-reference --> /topics/using/filters/
These pages still need some updates:
* /docs/dev-guide/canary-release-concepts/
| 36.72 | 77 | 0.740741 | eng_Latn | 0.371285 |
9a744f2a0aee050fee90b681b099524b8bc3a1ee | 563 | md | Markdown | _book/section-04/Section04-23.md | AlvinToh/Apache-2.0-Spark-with-Scala | 69ef58e8fbe23954b060337d3b5c01c353d35b13 | [
"Apache-2.0"
] | 2 | 2018-05-24T07:26:29.000Z | 2021-03-01T05:54:25.000Z | section-04/Section04-23.md | AlvinToh/Apache-2.0-Spark-with-Scala | 69ef58e8fbe23954b060337d3b5c01c353d35b13 | [
"Apache-2.0"
] | null | null | null | section-04/Section04-23.md | AlvinToh/Apache-2.0-Spark-with-Scala | 69ef58e8fbe23954b060337d3b5c01c353d35b13 | [
"Apache-2.0"
] | null | null | null | # 23. [Activity] Find the Most Popular Movie
## MOST POPULAR MOVIE
### MovieLens Data Format Review
```
User ID, Movie ID, Rating, Timestamp
196, 242, 3, 881250949
186, 302, 3, 891717742
22 , 377, 1, 878887116
244, 51, 2, 880606923
166, 346, 1, 886397596
290, 474, 4, 884182806
```
### Off To The Code
* Import PopularMovies.scala from resource folder into Eclipse-Scala IDE in SparkScala folder
* Import u.data from the resource folder into SparkScala folder to be used as the source file for PopularMovies.scala
* Run it and you should see the output | 29.631579 | 117 | 0.731794 | yue_Hant | 0.445579 |
9a74ca6e6cc6bf8fb39b843a824ab1fd0af551ec | 725 | md | Markdown | Kotlin/토이프로젝트/[Kotlin]20201211-kotlin-react-spring.md | haenyilee/haenyilee.github.io | 625beb494eb7cd1388d6a0c2b1c6630a685f914b | [
"MIT"
] | 1 | 2021-01-14T05:37:00.000Z | 2021-01-14T05:37:00.000Z | Kotlin/토이프로젝트/[Kotlin]20201211-kotlin-react-spring.md | haenyilee/haenyilee.github.io | 625beb494eb7cd1388d6a0c2b1c6630a685f914b | [
"MIT"
] | 13 | 2020-12-21T03:28:56.000Z | 2022-03-04T09:07:37.000Z | Kotlin/토이프로젝트/[Kotlin]20201211-kotlin-react-spring.md | haenyilee/haenyilee.github.io | 625beb494eb7cd1388d6a0c2b1c6630a685f914b | [
"MIT"
] | null | null | null | ## 코틀린
- `data class MovieVO(var no:Int,..)`
## spring
### db구축
#### interface MovieMapper
- 쿼리문장 작성
#### MovieDAO
- 메모리할당
- mapper 구현 요청
### json으로 넘겨주기
#### WebAppController
- `@RestController`
- DAO객체 얻어오기
- `@RequestMapping`
`
- 1. 리액트 => axios("url주소") => json 파싱되어서 들어옴
- 2. 코틀린 => HttpUrlConnection("url주소") => gson라이브러리로 파싱해서 들어가야함
- 한개에 대한 정보(row)가 12개 필요하다면 배열을 활용해 [{}이 12개]를 묶어서 주고받아야함
## react
#### package
```
"axios": "^0.21.0",
"react-router": "^5.2.0",
"react-router-dom": "^5.2.0"
```
## kotlin
#### build.gradle(module)
#### build.gradle(app)
'org.jsoup:jsoup:1.11.2'
'com.google.code.gson:gson:2.8.5'
'com.android.support:recyclerview-v7:28.0.0'
'com.github.bumptech.glide:glide:4.9.0'
| 13.942308 | 63 | 0.626207 | kor_Hang | 0.968987 |
9a7541ade3b865b3390ac082136e9d1e19696d4b | 349 | md | Markdown | README.md | rohit-k-das/cylance-alerts | 3366cff2c5be2b89196b8c4c01dfda229ab1cdff | [
"MIT"
] | null | null | null | README.md | rohit-k-das/cylance-alerts | 3366cff2c5be2b89196b8c4c01dfda229ab1cdff | [
"MIT"
] | null | null | null | README.md | rohit-k-das/cylance-alerts | 3366cff2c5be2b89196b8c4c01dfda229ab1cdff | [
"MIT"
] | null | null | null | Push cylance detections that occured in the past `duration` seconds (default is 600 seconds or 10 minutes) as slack alerts, with a minimum level of detail.
Install requirements: `pip install -r requirements.lock`
Command to run:
```
python3 main.py -d 300
python3 main.py
```
Use the -h option to get a list of options: `python3 -B main.py --help` | 34.9 | 155 | 0.750716 | eng_Latn | 0.995673 |
9a758498da7896f3cd8a8d027dc8fed5afc9ce8f | 90 | md | Markdown | RELEASE-NOTES.md | ijazm123/shop | e140f960d0a2ecba60ab17498b04a34d774c4d8a | [
"Apache-2.0"
] | 1 | 2020-10-07T23:57:58.000Z | 2020-10-07T23:57:58.000Z | RELEASE-NOTES.md | ijazm123/shop | e140f960d0a2ecba60ab17498b04a34d774c4d8a | [
"Apache-2.0"
] | 1 | 2020-01-22T08:10:39.000Z | 2020-01-22T08:10:39.000Z | RELEASE-NOTES.md | ijazm123/shop | e140f960d0a2ecba60ab17498b04a34d774c4d8a | [
"Apache-2.0"
] | 1 | 2020-03-17T09:29:20.000Z | 2020-03-17T09:29:20.000Z | Release changes in version 2.9.0
- REST api enhancements !
- Github issues
- New theme
| 11.25 | 32 | 0.722222 | eng_Latn | 0.87921 |
9a759083a268253e968ad1616bc08d4b60fed91a | 1,403 | md | Markdown | README.md | jbuchstaller/LODES_OD_hotspot | 15d3e8791eb139f24e3fe56767dab3f7737ee044 | [
"MIT"
] | null | null | null | README.md | jbuchstaller/LODES_OD_hotspot | 15d3e8791eb139f24e3fe56767dab3f7737ee044 | [
"MIT"
] | null | null | null | README.md | jbuchstaller/LODES_OD_hotspot | 15d3e8791eb139f24e3fe56767dab3f7737ee044 | [
"MIT"
] | null | null | null | # LODES_OD_hotspot
Goal: Visualize the number of workers in each censustract in South East Michigan and their origins
Deployed at https://geospatially.shinyapps.io/lodes_od_hotspot/
Description: Based on 2015 LODES data (https://lehd.ces.census.gov/data/) I created a clickable shiny application that shows on a map how many people work in each censustract. By clicking on the census tract, the user can see hotspots the workers commute from.
Download the folder with all the files and run the file "app.R" in R-Studio, setting the working directory to the folder. It might take a while to load the data and display the maps.
Hotspot analysis methodology:
I calculated the Getis-Ord Gi* statistic (z-score) for each block with 1-hour driving distance of the origin (censustract clicked by user). This statistic determines whether the local average number of commuters is significantly higher or lower than the global average. To choose the number of neighbors used for the local average (not shown), I computed the global Moran's I statistic for a number of scenarios (1 to 100 neighbors) and choose the number of neigbors that resulted in maximal global Moran's I (value where spatial clustering is strongest) and then constructed the spatial relation matrix accordingly.
LODES_OD_hotspot is licensed under the MIT License. See the LICENSE file in this directory for the full license text.
| 66.809524 | 616 | 0.801853 | eng_Latn | 0.999133 |
9a75d0457dbf96ed76f552e57c8700091db512d2 | 17,362 | md | Markdown | dsc/partialConfigs.md | I-Cat/PowerShell-Docs.de-de | 17c06af567a068eea5e9ba58abca102b39b86482 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-01-16T06:05:39.000Z | 2019-01-16T06:05:39.000Z | dsc/partialConfigs.md | I-Cat/PowerShell-Docs.de-de | 17c06af567a068eea5e9ba58abca102b39b86482 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | dsc/partialConfigs.md | I-Cat/PowerShell-Docs.de-de | 17c06af567a068eea5e9ba58abca102b39b86482 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2016-10-23T13:34:36.000Z | 2021-04-05T00:14:47.000Z | ---
title: "PowerShell DSC – Teilkonfigurationen"
ms.date: 2016-05-16
keywords: powershell,DSC
description:
ms.topic: article
author: eslesar
manager: dongill
ms.prod: powershell
translationtype: Human Translation
ms.sourcegitcommit: a656ec981dc03fd95c5e70e2d1a2c741ee1adc9b
ms.openlocfilehash: c5d3cb1045e67d4913fbbad13938e8f95a43cacf
---
# PowerShell DSC – Teilkonfigurationen
>Gilt für: Windows PowerShell 5.0
In PowerShell 5.0 ermöglicht DSC (Desired State Configuration, Konfiguration des gewünschten Zustands), dass Konfigurationen in Fragmenten und aus mehreren Quellen übermittelt werden. Der LCM (Local Configuration Manager, lokale Konfigurations-Manager) auf dem Zielknoten setzt die Fragmente zusammen, ehe sie als einzelne Konfiguration angewendet werden. Dies ermöglicht die gemeinsame Steuerung der Konfiguration durch Teams oder Einzelpersonen. Wenn z. B. zwei oder mehr Teams an der Entwicklung eines Diensts zusammenarbeiten, möchte ggf. jedes Team Konfigurationen für die Verwaltung seines Teils des Diensts erstellen. Jede dieser Konfigurationen kann von verschiedenen Pullservern abgerufen und in verschiedenen Phasen der Entwicklung hinzugefügt werden. Teilkonfigurationen ermöglichen außerdem verschiedenen Personen oder Teams das Steuern verschiedener Aspekte der Konfiguration von Knoten, ohne dass die Bearbeitung eines einzelnen Konfigurationsdokuments koordiniert werden muss. Ein Team kann z. B. für die Bereitstellung einer VM und eines Betriebssystems verantwortlich sein, während ein anderes Team andere Anwendungen und Dienste auf dieser VM bereitstellen kann. Bei Teilkonfigurationen kann jedes Team seine eigene Konfiguration erstellen, die dann nicht unnötig kompliziert sein muss.
Sie können Teilkonfigurationen im Pushmodus, Pullmodus oder einer Kombination aus beidem verwenden.
## Teilkonfigurationen im Pushmodus
Um Teilkonfigurationen im Pushmodus zu verwenden, konfigurieren Sie den LCM auf dem Zielknoten für das Empfangen von Teilkonfigurationen. Jede Teilkonfiguration muss per Push auf den Zielknoten übertragen werden, wozu das Cmdlet „Publish-DscConfiguration“ verwendet wird. Der Zielknoten kombiniert dann die Teilkonfigurationen zu einer einzelnen Konfiguration, und Sie können die Konfiguration durch Aufrufen des Cmdlets [Start-DscConfiguration](https://technet.microsoft.com/en-us/library/dn521623.aspx) aufrufen.
### Konfigurieren des LCM für Teilkonfigurationen im Pushmodus
Zum Konfigurieren des LCM für Teilkonfigurationen im Pushmodus erstellen Sie eine **DSCLocalConfigurationManager**-Konfiguration mit einem **PartialConfiguration**-Block für jede Teilkonfiguration. Weitere Informationen zum Konfigurieren des LCM finden Sie unter [Konfigurieren des lokalen Konfigurations-Managers](https://technet.microsoft.com/en-us/library/mt421188.aspx). Das folgende Beispiel zeigt eine LCM-Konfiguration, die zwei Teilkonfigurationen erwartet: eine, die das Betriebssystem bereitgestellt, und eine, die SharePoint bereitstellt und konfiguriert.
```powershell
[DSCLocalConfigurationManager()]
configuration PartialConfigDemo
{
Node localhost
{
PartialConfiguration ServiceAccountConfig
{
Description = 'Configuration to add the SharePoint service account to the Administrators group.'
RefreshMode = 'Push'
}
PartialConfiguration SharePointConfig
{
Description = 'Configuration for the SharePoint server'
RefreshMode = 'Push'
}
}
}
PartialConfigDemo
```
**RefreshMode** für jede Teilkonfiguration ist auf „Push“ festgelegt. Die Namen der **PartialConfiguration**-Blöcke (in diesem Fall „ServiceAccountConfig“ und „SharePointConfig“) müssen genau mit den Namen der Konfigurationen übereinstimmen, die per Push an die Zielknoten übertragen werden.
### Veröffentlichen und Starten von Teilkonfigurationen im Pushmodus
Rufen Sie dann das Cmdlet **Publish-DSCConfiguration** für jede Konfiguration auf, und übergeben Sie die Ordner mit den Konfigurationsdokumenten als „Path“-Parameter. Nach Veröffentlichen beider Konfigurationen können Sie `Start-DSCConfiguration –UseExisting` auf dem Zielknoten aufrufen.
## Teilkonfigurationen im Pullmodus
Teilkonfigurationen können von einem oder mehreren Pullservern abgerufen werden (weitere Informationen zu Pullservern finden Sie unter [Windows PowerShell DSC – Pullserver](pullServer.md). Konfigurieren Sie hierzu den LCM so, dass die Teilkonfigurationen per Pull auf den Zielknoten abgerufen werden, und sorgen Sie dafür, dass die Konfigurationsdokumente auf den Pullservern ordnungsgemäß benannt und abgelegt werden.
### Konfigurieren des LCM für Teilkonfigurationen im Pullmodus
Zum Konfigurieren des LCM zum Abrufen von Teilkonfigurationen per Pull von einem Pullserver müssen Sie den Pullserver entweder in einem **ConfigurationRepositoryWeb**-Block (für einen HTTP-Pullserver) oder einem **ConfigurationRepositoryShare**-Block (für einen SMB-Pullserver) definieren. Dann erstellen Sie **PartialConfiguration**-Blöcke, die unter Verwendung der **ConfigurationSource**-Eigenschaft auf den Pullserver verweisen. Sie müssen außerdem einen **Settings**-Block erstellen, um anzugeben, dass der LCM den Pullmodus verwendet, und um die **ConfigurationNames**- oder **ConfigurationID**-Werte anzugeben, die der Pullserver und Zielknoten zum Identifizieren der Konfigurationen verwenden. Die folgende Metakonfiguration definiert einen HTTP-Pullserver mit dem Namen „CONTOSO-PullSrv“ und zwei Teilkonfigurationen, die diesen Pullserver verwenden.
Weitere Informationen zum Konfigurieren des LCM unter Verwendung von **ConfigurationNames** finden Sie unter [Einrichten eines Pullclients mithilfe von Konfigurationsnamen](pullClientConfigNames.md). Weitere Informationen zum Konfigurieren des LCM unter Verwendung von **ConfigurationID** finden Sie unter [Einrichten eines Pullclients mithilfe der Konfigurations-ID](pullClientConfigID.md).
#### Konfigurieren des LCM für Pullmoduskonfigurationen mithilfe von Konfigurationsnamen
```powershell
[DscLocalConfigurationManager()]
Configuration PartialConfigDemoConfigNames
{
Settings
{
RefreshFrequencyMins = 30;
RefreshMode = "PULL";
ConfigurationMode ="ApplyAndAutocorrect";
AllowModuleOverwrite = $true;
RebootNodeIfNeeded = $true;
ConfigurationModeFrequencyMins = 60;
}
ConfigurationRepositoryWeb CONTOSO-PullSrv
{
ServerURL = 'https://CONTOSO-PullSrv:8080/PSDSCPullServer.svc'
RegistrationKey = 5b41f4e6-5e6d-45f5-8102-f2227468ef38
ConfigurationNames = @("ServiceAccountConfig", "SharePointConfig")
}
PartialConfiguration ServiceAccountConfig
{
Description = "ServiceAccountConfig"
ConfigurationSource = @("[ConfigurationRepositoryWeb]CONTOSO-PullSrv")
}
PartialConfiguration SharePointConfig
{
Description = "SharePointConfig"
ConfigurationSource = @("[ConfigurationRepositoryWeb]CONTOSO-PullSrv")
DependsOn = '[PartialConfiguration]ServiceAccountConfig'
}
}
```
#### Konfigurieren des LCM für Pullmoduskonfigurationen mithilfe der Konfigurations-ID
```powershell
[DSCLocalConfigurationManager()]
configuration PartialConfigDemoConfigID
{
Node localhost
{
Settings
{
RefreshMode = 'Pull'
ConfigurationID = '1d545e3b-60c3-47a0-bf65-5afc05182fd0'
RefreshFrequencyMins = 30
RebootNodeIfNeeded = $true
}
ConfigurationRepositoryWeb CONTOSO-PullSrv
{
ServerURL = 'https://CONTOSO-PullSrv:8080/PSDSCPullServer.svc'
}
PartialConfiguration ServiceAccountConfig
{
Description = 'Configuration for the Base OS'
ConfigurationSource = '[ConfigurationRepositoryWeb]CONTOSO-PullSrv'
RefreshMode = 'Pull'
}
PartialConfiguration SharePointConfig
{
Description = 'Configuration for the Sharepoint Server'
ConfigurationSource = '[ConfigurationRepositoryWeb]CONTOSO-PullSrv'
DependsOn = '[PartialConfiguration]ServiceAccountConfig'
RefreshMode = 'Pull'
}
}
}
PartialConfigDemo
```
Sie können Teilkonfigurationen per Pull von mehreren Pullservern abrufen. Sie müssen dazu die einzelnen Pullserver definieren und dann im jeweiligen **PartialConfiguration**-Block auf den entsprechenden Pullserver verweisen.
Nach dem Erstellen der Metakonfiguration müssen Sie diese ausführen, um ein Konfigurationsdokument (eine MOF-Datei) zu erstellen. Rufen Sie anschließend [Set- DscLocalConfigurationManager](https://technet.microsoft.com/en-us/library/dn521621(v=wps.630).aspx) auf, um den LCM zu konfigurieren.
### Benennen und Ablegen der Konfigurationsdokumente auf dem Pullserver (ConfigurationNames)
Die Teilkonfigurationsdokumente müssen in dem Ordner abgelegt werden, der als **ConfigurationPath** in der Datei `web.config` für den Pullserver angegeben ist (meist `C:\Program Files\WindowsPowerShell\DscService\Configuration`). Konfigurationsdokumente müssen wie folgt benannt werden: `ConfigurationName.mof`, wobei _ConfigurationName_ der Name der partiellen Konfiguration ist. In unserem Beispiel sollten die Konfigurationsdokumente wie folgt heißen:
```
ServiceAccountConfig.mof
ServiceAccountConfig.mof.checksum
SharePointConfig.mof
SharePointConfig.mof.checksum
```
### Benennen und Ablegen der Konfigurationsdokumente auf dem Pullserver (ConfigurationID)
Die Teilkonfigurationsdokumente müssen in dem Ordner abgelegt werden, der als **ConfigurationPath** in der Datei `web.config` für den Pullserver angegeben ist (meist `C:\Program Files\WindowsPowerShell\DscService\Configuration`). Die Konfigurationsdokumente müssen wie folgt heißen: _ConfigurationName_. _ConfigurationID_`.mof`, wobei _ConfigurationName_ der Name der Teilkonfiguration und _ConfigurationID_ die Konfigurations-ID ist, die im LCM auf dem Zielknoten definiert ist. In unserem Beispiel sollten die Konfigurationsdokumente wie folgt heißen:
```
ServiceAccountConfig.1d545e3b-60c3-47a0-bf65-5afc05182fd0.mof
ServiceAccountConfig.1d545e3b-60c3-47a0-bf65-5afc05182fd0.mof.checksum
SharePointConfig.1d545e3b-60c3-47a0-bf65-5afc05182fd0.mof
SharePointConfig.1d545e3b-60c3-47a0-bf65-5afc05182fd0.mof.checksum
```
### Ausführen von Teilkonfigurationen von einem Pullserver
Nachdem der LCM auf dem Zielknoten konfiguriert wurde und die Konfigurationsdokumente auf dem Pullserver erstellt und ordnungsgemäß benannt wurden, ruft der Zielknoten die Teilkonfigurationen ab, kombiniert sie und wendet die resultierende Konfiguration in regelmäßigen Abständen entsprechend der Angabe der **RefreshFrequencyMins**-Eigenschaft des LCM an. Wenn Sie eine Aktualisierung erzwingen möchten, können Sie das Cmdlet [Update-DscConfiguration](https://technet.microsoft.com/en-us/library/mt143541.aspx) aufrufen, um die Konfigurationen per Pull abzurufen, und dann `Start-DSCConfiguration –UseExisting` aufrufen, um sie anzuwenden.
## Teilkonfigurationen im gemischten Push- und Pullmodus
Sie können Push- und Pullmodus für Teilkonfigurationen auch mischen. Es ist also möglich, dass eine Teilkonfiguration per Pull von einem Pullserver abgerufen wird, während eine andere per Push übertragen wird. Behandeln Sie jede Teilkonfiguration abhängig von ihrem in den vorherigen Abschnitten beschriebenen Aktualisierungsmodus. In der folgenden Metakonfiguration wird z. B. dasselbe Beispiel beschrieben – mit der Teilkonfiguration für das Dienstkonto im Pullmodus und der Teilkonfiguration für SharePoint im Pushmodus.
### Gemischte Push- und Pullmodi unter Verwendung von „ConfigurationNames“
```powershell
[DscLocalConfigurationManager()]
Configuration PartialConfigDemoConfigNames
{
Settings
{
RefreshFrequencyMins = 30;
RefreshMode = "PULL";
ConfigurationMode = "ApplyAndAutocorrect";
AllowModuleOverwrite = $true;
RebootNodeIfNeeded = $true;
ConfigurationModeFrequencyMins = 60;
}
ConfigurationRepositoryWeb CONTOSO-PullSrv
{
ServerURL = 'https://CONTOSO-PullSrv:8080/PSDSCPullServer.svc'
RegistrationKey = 5b41f4e6-5e6d-45f5-8102-f2227468ef38
ConfigurationNames = @("ServiceAccountConfig", "SharePointConfig")
}
PartialConfiguration ServiceAccountConfig
{
Description = "ServiceAccountConfig"
ConfigurationSource = @("[ConfigurationRepositoryWeb]CONTOSO-PullSrv")
RefreshMode = 'Pull'
}
PartialConfiguration SharePointConfig
{
Description = "SharePointConfig"
DependsOn = '[PartialConfiguration]ServiceAccountConfig'
RefreshMode = 'Push'
}
}
```
### Gemischte Push- und Pullmodi unter Verwendung von „ConfigurationID“
```powershell
[DSCLocalConfigurationManager()]
configuration PartialConfigDemo
{
Node localhost
{
Settings
{
RefreshMode = 'Pull'
ConfigurationID = '1d545e3b-60c3-47a0-bf65-5afc05182fd0'
RefreshFrequencyMins = 30
RebootNodeIfNeeded = $true
}
ConfigurationRepositoryWeb CONTOSO-PullSrv
{
ServerURL = 'https://CONTOSO-PullSrv:8080/PSDSCPullServer.svc'
}
PartialConfiguration ServiceAccountConfig
{
Description = 'Configuration for the Base OS'
ConfigurationSource = '[ConfigurationRepositoryWeb]CONTOSO-PullSrv'
RefreshMode = 'Pull'
}
PartialConfiguration SharePointConfig
{
Description = 'Configuration for the Sharepoint Server'
DependsOn = '[PartialConfiguration]ServiceAccountConfig'
RefreshMode = 'Push'
}
}
}
PartialConfigDemo
```
Beachten Sie, dass der im „Settings“-Block angegebene **RefreshMode** auf „Pull“, aber der **RefreshMode** für die Teilkonfiguration „SharePointConfig“ auf „Push“ festgelegt ist.
Benennen Sie die MOF-Konfigurationsdateien und legen Sie sie ab, wie oben für die entsprechenden Aktualisierungsmodi beschrieben. Rufen Sie das Cmdlet **Publish-DSCConfiguration** zum Veröffentlichen der `SharePointConfig`-Teilkonfiguration auf. Warten Sie dann entweder, bis die `ServiceAccountConfig`-Konfiguration vom Pullserver abgerufen wird, oder erzwingen Sie eine Aktualisierung durch das Aufrufen von [Update-DscConfiguration](https://technet.microsoft.com/en-us/library/mt143541(v=wps.630).aspx).
## Beispiel für eine ServiceAccountConfig-Teilkonfiguration
```powershell
Configuration ServiceAccountConfig
{
Param (
[Parameter(Mandatory,
HelpMessage="Domain credentials required to add domain\sharepoint_svc to the local Administrators group.")]
[ValidateNotNullOrEmpty()]
[pscredential]$Credential
)
Import-DscResource -ModuleName PSDesiredStateConfiguration
Node localhost
{
Group LocalAdmins
{
GroupName = 'Administrators'
MembersToInclude = 'domain\sharepoint_svc',
'admins@example.domain'
Ensure = 'Present'
Credential = $Credential
}
WindowsFeature Telnet
{
Name = 'Telnet-Server'
Ensure = 'Absent'
}
}
}
ServiceAccountConfig
```
## Beispiel für eine SharePointConfig-Teilkonfiguration
```powershell
Configuration SharePointConfig
{
Param (
[Parameter(Mandatory)]
[ValidateNotNullOrEmpty()]
[pscredential]$ProductKey
)
Import-DscResource -ModuleName xSharePoint
Node localhost
{
xSPInstall SharePointDefault
{
Ensure = 'Present'
BinaryDir = '\\FileServer\Installers\Sharepoint\'
ProductKey = $ProductKey
}
}
}
SharePointConfig
```
##Weitere Informationen
**Konzepte**
[Windows PowerShell DSC – Pullserver](pullServer.md)
[Konfigurieren des lokalen Konfigurations-Managers](https://technet.microsoft.com/en-us/library/mt421188.aspx)
<!--HONumber=Oct16_HO1-->
| 51.519288 | 1,304 | 0.709711 | deu_Latn | 0.966372 |
9a763bfc21fc8354c2ef78be125229db831ea40a | 3,941 | md | Markdown | rpi-pico-ups.md | ef-gy/blog | 69b5a79ae5597898b71716430e02c59a617d1bd1 | [
"MIT"
] | 6 | 2015-08-22T23:41:49.000Z | 2019-10-24T19:11:53.000Z | rpi-pico-ups.md | ef-gy/blog | 69b5a79ae5597898b71716430e02c59a617d1bd1 | [
"MIT"
] | 2 | 2016-09-07T14:41:09.000Z | 2016-09-07T15:09:18.000Z | rpi-pico-ups.md | ef-gy/blog | 69b5a79ae5597898b71716430e02c59a617d1bd1 | [
"MIT"
] | null | null | null | # Getting down to business with a Raspberry Pi PIco UPS
You may remember the picture of my shiny little To-enabled Pi on the last blog post about [monitoring the very same device through Tor](/secure-prometheus-ssh-hidden-service). It had just received [a shiny new PIco UPS backpack with a LiPO battery](http://www.pimodules.com/_pdf/_pico/UPS_PIco%20FAQ_V1.0.pdf) from [pimodules.com](http://pimodules.com/). It turns out, however, that I first had to hack that a bit to make it usable for my purposes.
For one thing, it was a wee bit too big to fit in the current case, so I had to make room by getting a new one. Which obviously made the Pi rather happy:
For another, the device actually requires you to run a Python script as root so that the firmware can figure out if your Pi is booted or not, and to get it to shut down if a power failure is imminent. Now, I don't know [if you follow my Twitter](https://twitter.com/jyujinX), but on there I'd previously quite proudly declared that I'd gotten rid of Python on the sucker, and I wasn't about to put it back on permanently just to get the UPS to work.
Besides, running a Python script as root for a critical subsystem, such as your UPS, seems... ill-advised, at the least. AND there's a reason Python is generally in /usr/bin and not /bin. Just saying.
## Yay for some minor reverse-engineering
So now to find out what that Python script actually does and if we really need it. I had a quick look at it and it seems straightforward enough: it sets up some GPIO pins, waits for a LOW on one of them and then shells out to "sudo shutdown -h now" (and folks, if you're reading this: you can probably drop the "sudo"... seeing as how your instructions say to run this as root).
So, doesn't sound like anything critical. Let's try that without the script. And it works... almost. The PIco will happily run, and even fail over to the battery! But sadly the little charging light never comes on :(. And then running the script makes it go on! Sadness :(.
It turns out that the script does something else: it sets another pin to HIGH and LOW in a loop. A quick glance at the manual suggests that, indeed, the PIco requires a pulse train on one of the pins. Confusingly, the manual states this pin needs to be #27, and the script does it on #22... but meh, we all make typos.
Armed with that information, I came up with this shell script to simulate what the Python script did:
#!/bin/sh
raspi-gpio set 22 op;
#raspi-gpio set 27 ip pu;
while true; do
raspi-gpio set 22 dh;
sleep 0.25;
raspi-gpio set 22 dl;
# raspi-gpio get 27;
sleep 0.25;
done
Note how the commented lines simulate what the pin #27 query - which controls the system shutdown - did in the script. This is not necessary for the important part, which is getting the PIco to recognise that the Pi is all booted up and subsequently get it to charge.
## Introducing: picod
So, running this script will actually get the PIco to do its thing and charge the battery. You might be tempted to think we're done, but... not just yet.
The thing is, as much as I really don't want to have Python for my UPS... shell is not really an improvement, either. But this little script did verify that our only requirement was the pulse train on pin #22.
So, a few hours of boredom later, [I ended up just rewriting the whole thing in C and calling it *picod*](https://github.com/ef-gy/rpi-ups-pico). It's using the Linux sysfs GPIO interface to get it all sorted, which is surprisingly decent to work with. It also takes care of the pin #27 shutdown signal *and* it comes with a manpage! W00t!
Go give it a shot and tell me if anything's missing - I'm always open for suggestions ;). I even [documented all the source code](/documentation/rpi-ups-pico), for your hacking convenience! | 85.673913 | 449 | 0.74981 | eng_Latn | 0.999482 |
9a7676a26e65bc8b5f49ade7f06b2f9516a4e2d3 | 80,317 | md | Markdown | security-updates/securitybulletins/2010/ms10-036.md | eltociear/security-updates.hu-hu | c98d1ddb0d9212c26ff6c8b241a476bb9cf19a38 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T20:16:02.000Z | 2021-02-22T15:30:16.000Z | security-updates/securitybulletins/2010/ms10-036.md | eltociear/security-updates.hu-hu | c98d1ddb0d9212c26ff6c8b241a476bb9cf19a38 | [
"CC-BY-4.0",
"MIT"
] | 126 | 2018-01-17T23:45:15.000Z | 2020-04-27T16:02:00.000Z | security-updates/securitybulletins/2010/ms10-036.md | isabella232/security-updates.hu-hu | c98d1ddb0d9212c26ff6c8b241a476bb9cf19a38 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-11-21T08:49:25.000Z | 2021-11-15T10:54:17.000Z | ---
TOCTitle: 'MS10-036'
Title: 'A Microsoft számú biztonsági közleménye MS10-036 - Fontos'
ms:assetid: 'ms10-036'
ms:contentKeyID: 61228599
ms:mtpsurl: 'https://technet.microsoft.com/hu-HU/library/ms10-036(v=Security.10)'
author: SharonSears
ms.author: SharonSears
---
A Microsoft számú biztonsági közleménye MS10-036 - Fontos
=========================================================
A Microsoft Office COM-érvényesítés biztonsági rése távoli kódfuttatást tehet lehetővé (983235)
-----------------------------------------------------------------------------------------------
Közzétéve: 2010. június 8. | Frissítve: 2010. június 16.
**Verzió:** 1.1
### Általános tudnivalók
#### Összefoglalás
A biztonsági frissítés a Microsoft Office COM-érvényesítés egy közvetlenül jelentett biztonsági rését szünteti meg. A biztonsági rés távoli kódfuttatást tesz lehetővé, ha a felhasználó megnyit egy érintett Microsoft Office verzióval speciálisan létrehozott Excel, Word, Visio, Publisher vagy PowerPoint fájlt. E-mail küldésével a biztonsági rés nem használható ki automatikusan. A támadás sikerességéhez a felhasználónak meg kell nyitnia az e-mail üzenetben küldött mellékletet.
A biztonsági frissítés a Microsoft Office 2003 és a 2007-es Microsoft Office rendszerre vonatkozóan fontos besorolású. További tudnivalókat a közlemény későbbi részében az **Érintett és nem érintett szoftverek** cím alatt talál.
A biztonsági frissítés a biztonsági rés megszüntetése végett módosítja a futtatni készült COM-objektumok érvényesítését a Microsoft Office programban. A biztonsági réssel kapcsolatban bővebben az adott problémával foglakozó gyakran feltett kérdéseket ismertető szakaszban, **A biztonsági réssel kapcsolatos tudnivalók** című részben olvashat.
**Javaslat.** A Microsoft a biztonsági frissítés lehető leghamarabb történő telepítését javasolja ügyfeleinek.
**Ismert problémák** A[Microsoft Tudásbázis 983235. számú cikkében](http://support.microsoft.com/kb/983235) olvasható, hogy a felhasználók a biztonsági frissítés telepítésekor milyen ismert problémákkal találkozhatnak. A cikkben a problémákra javasolt megoldások is szerepelnek. Ha az ismert problémák és az ajánlott megoldások csak a szoftver egyes kiadásaira vonatkoznak, a cikkben további utalások olvashatók más cikkekre.
#### Érintett és nem érintett szoftverek
Az itt felsorolt szoftvereket a verziók és változatok érintettségének felderítése érdekében teszteltük. A többi verzió, illetve kiadás támogatási életciklusa végére ért vagy nem érintett. Az egyes szoftverek és azok verzióinak támogatási életciklusáról a [Microsoft termékek terméktámogatási életciklusát ismertető webhelyen](http://go.microsoft.com/fwlink/?linkid=21742) talál felvilágosítást.
**Érintett szoftverek**
<p> </p>
<p></p>
<table style="border:1px solid black;">
<tr class="thead">
<th style="border:1px solid black;" >
Office szoftvercsomag és egyéb szoftverek
</th>
<th style="border:1px solid black;" >
Összetevő
</th>
<th style="border:1px solid black;" >
Maximális biztonsági hatás
</th>
<th style="border:1px solid black;" >
Összesített súlyossági besorolás
</th>
<th style="border:1px solid black;" >
A frissítés által felváltott közlemények
</th>
</tr>
<tr>
<th colspan="5" style="border:1px solid black;">
Microsoft Office XP
</th>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office XP Service Pack 3<sup>[1]</sup>
</td>
<td style="border:1px solid black;">
Nem érintett
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
Nincsenek
</td>
</tr>
<tr>
<th colspan="5" style="border:1px solid black;">
Microsoft Office 2003
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft Office 2003 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=80fdd134-2a86-4115-aea1-841f19af92e3)
(KB982311)
</td>
<td style="border:1px solid black;">
Nem érintett
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS08-055](http://go.microsoft.com/fwlink/?linkid=125229)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
[Microsoft Office Excel 2003 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=757b5d8f-ade5-4896-b152-43f76516bcf1)<sup>[2]</sup>
(KB982133)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS10-017](http://go.microsoft.com/fwlink/?linkid=182987)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft Office 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
[Microsoft Office PowerPoint 2003 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=6b6204c1-559f-45a5-8f6c-a1e216192efc)<sup>[2]</sup>
(KB982157)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS10-004](http://go.microsoft.com/fwlink/?linkid=163639)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
[Microsoft Office Publisher 2003 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=87bac893-81ec-4ede-aca1-a9aa48b92cd4)<sup>[2]</sup>
(KB982122)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS10-023](http://go.microsoft.com/fwlink/?linkid=184751)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft Office 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
[Microsoft Office Visio 2003 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=1595ada3-bb4f-40f6-8137-23eba918bc8a)<sup>[2]</sup>
(KB982126)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS10-028](http://go.microsoft.com/fwlink/?linkid=182935)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
[Microsoft Office Word 2003 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=d2c40eb5-1149-4466-840c-84f406f64245)<sup>[2]</sup>
(KB982134)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS09-068](http://go.microsoft.com/fwlink/?linkid=165890)
</td>
</tr>
<tr>
<th colspan="5" style="border:1px solid black;">
2007 Microsoft Office rendszer
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=6deb4fb0-cbfc-40df-8f62-35fa1db0e167)
(KB982312)
</td>
<td style="border:1px solid black;">
Nem érintett
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS08-055](http://go.microsoft.com/fwlink/?linkid=125229)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2
</td>
<td style="border:1px solid black;">
[Microsoft Office Excel 2007 Service Pack 1 és Microsoft Office Excel 2007 Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=1b2599f0-1e5d-463c-b100-6c6a1b17b2ec)<sup>[3]</sup>
(KB982308)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS10-017](http://go.microsoft.com/fwlink/?linkid=182987)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2
</td>
<td style="border:1px solid black;">
[Microsoft Office PowerPoint 2007 Service Pack 1 és Microsoft Office PowerPoint 2007 Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=decb834d-3958-45cc-a5ae-4283adb2462a)<sup>[3]</sup>
(KB982158)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS09-017](http://go.microsoft.com/fwlink/?linkid=141704)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2
</td>
<td style="border:1px solid black;">
[Microsoft Office Publisher 2007 Service Pack 1 és Microsoft Office Publisher 2007 Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=6a74b986-1e99-4aa1-828f-757a36896f65)<sup>[3]</sup>
(KB982124)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS10-023](http://go.microsoft.com/fwlink/?linkid=184751)
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2
</td>
<td style="border:1px solid black;">
[Microsoft Office Visio 2007 Service Pack 1 és Microsoft Office Visio 2007 Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=d5df052e-1f38-4308-bcca-296cff22729b)<sup>[3]</sup>
(KB982127)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS10-028](http://go.microsoft.com/fwlink/?linkid=182935)
</td>
</tr>
<tr>
<td style="border:1px solid black;">
2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2
</td>
<td style="border:1px solid black;">
[Microsoft Office Word 2007 Service Pack 1 és Microsoft Office Word 2007 Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=7e9708f0-8cd6-4f0b-8585-bccc54fa2755)<sup>[3]</sup>
(KB982135)
</td>
<td style="border:1px solid black;">
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
Fontos
</td>
<td style="border:1px solid black;">
[MS09-027](http://go.microsoft.com/fwlink/?linkid=147416)
</td>
</tr>
</table>
<p></p>
<sup>[1]</sup>Nincs elérhető frissítés. További tájékoztatásért tekintse meg a **Gyakran ismételt kérdések a biztonsági frissítéssel kapcsolatban** című részt.
<sup>[2]</sup>A jelen frissítésen kívül a felhasználóknak a Microsoft Office 2003 Service Pack 3 (KB982311) frissítését is telepíteniük kell, hogy megvédjék rendszerüket a jelen közleményben foglalt biztonsági rés hatásaitól.
<sup>[3]</sup>A jelen frissítésen kívül a felhasználóknak a 2007-es Microsoft Office Service Pack 1 és a 2007-es Microsoft Office Service Pack 2 (KB982312) frissítését is telepíteniük kell, hogy megvédjék rendszerüket a jelen közleményben foglalt biztonsági rés hatásaitól.
**Nem veszélyeztetett szoftverek**
| Office és egyéb szoftverek |
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Microsoft Office 2010 (32 bites kiadások) |
| Microsoft Office 2010 (64 bites kiadások) |
| Microsoft Office 2004 for Mac |
| Microsoft Office 2008 for Mac |
| Open XML File Format Converter for Mac |
| Microsoft Office Excel Viewer Service Pack 1 és Microsoft Office Excel Viewer Service Pack 2 |
| Microsoft Office Word Viewer |
| PowerPoint Viewer 2007 Service Pack 1 és PowerPoint Viewer 2007 Service Pack 2 |
| Microsoft Office Visio Viewer 2007 Service Pack 1 és Microsoft Office Visio Viewer 2007 Service Pack 2 |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 és Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2 |
| Office Converter Pack |
| Microsoft Office OneNote 2007 Service Pack 1 és Microsoft Office OneNote 2007 Service Pack 2 |
Gyakran ismételt kérdések a biztonsági frissítéssel kapcsolatban
----------------------------------------------------------------
**A biztonsági rés által nem érintett szoftverrel rendelkezem, miért kapok mégis értesítést a frissítésről?**
Egyes nem érintett szoftverek - többek között a Microsoft Office kompatibilitási csomag a Word, Excel és PowerPoint 2007 fájlformátumokhoz, a Microsoft Office Word Viewer, a Microsoft Office Excel Viewer, a Microsoft Office PowerPoint Viewer 2007 és a Visual Studio 2008 - tartalmazzák az érintett megosztott Office-összetevőket, de mivel nem férnek hozzá az érintett kódhoz, így a biztonsági rés ezekre nem vonatkozik. Mivel azonban a biztonsági rést jelentő kód jelen van, a rendszer felajánlja a frissítést.
**A nem érintett verziójú szoftverhez felajánlott frissítés hibát jelez a Microsoft frissítési rendszerében?**
Nem. A frissítési rendszer megfelelően működik, és érzékeli, hogy rendszer alacsonyabb verziószámú fájlokkal van ellátva, mint a frissítési csomag. Ezért ajánlja fel a frissítést.
**Hol találhatók a fájlinformációs adatok?**
A fájlinformációs adatokat lásd a **Biztonsági frissítés telepítése** rész hivatkozási táblázataiban.
**Ha a Microsoft Office XP szerepel az érintett termékek között, akkor a Microsoft miért nem ad ki hozzá frissítést?**
A Microsoft Office XP rendszereken nincs megfelelő architektúra a helyes érvényesítési javítások támogatásához, ami lehetetlenné teszi a biztonsági rést megszüntető javítás létrehozását a Microsoft Office XP termékekhez. Ehhez újra ki kellene alakítani a Microsoft Office XP termékek architektúrájának jelentős részét, nem csak az érintett összetevőket. Az architektúra újraalakítására tett erőfeszítések eredménye inkompatibilitást eredményezhet más alkalmazásokkal, azaz nem garantált, hogy ezek a Microsoft Office termékek továbbra is működőképesek lesznek a frissített rendszeren.
A Microsoft **Microsoft Fix it** megoldást kínál a Windows XP rendszerre telepített Office XP felhasználói számára. Noha a **Microsoft Fix it** megoldás nem jelent kódjavítást az Office termékekben, ahhoz hasonló védelmet nyújt a közleményben ismertetett biztonsági rés ellen. Noha az alkalmazás-kompatibilitás kockázata minimális, a Microsoft javasolja, hogy a szélesebb körű terjesztés előtt a felhasználók teszteljék a **Microsoft Fix it** megoldást. A letöltésről és a részletekről lásd a [Microsoft tudásbázis 983235. cikkét](http://support.microsoft.com/kb/983235).
**Az összetevők frissítéséhez szükség van a vonatkozó Microsoft Office 2003 illetve 2007-es Microsoft Office rendszerfrissítések telepítésére is?**
Igen, a biztonsági frissítéshez valóban telepíteni kell a Microsoft Office 2003 Service Pack 3 (KB982311), illetve 2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2 (KB982312) frissítéseit az érintett szoftverek táblázatában felsorolt, vonatkozó Excel, Word, Visio, Publisher, illetve PowerPoint frissítésekkel együtt. Csak ez biztosítja a védelmet a közleményben ismertetett biztonsági rések ellen.
**Az MS10-038 közlemény a Microsoft Office Excel biztonsági réseit is ismerteti. Hogyan kapcsolódik az MS10-038 közlemény a jelen közleményhez (MS10-036)?**
A jelen, MS10-036 közlemény Microsoft Office Excel 2003 (KB982133) és Microsoft Office Excel 2007 (KB982308) programra vonatkozó biztonsági frissítőcsomagjai a jelen, [MS10-038](http://go.microsoft.com/fwlink/?linkid=191053) közleményben foglalt biztonsági rések megoldását is tartalmazzák. A Microsoft Office Excel 2003 illetve Microsoft Office Excel 2007 felhasználóknak csak egyszer kell telepíteniük a biztonsági frissítőcsomagokat. A felhasználóknak a vonatkozó, jelen közleményben felajánlott Microsoft Office frissítést (KB982311 vagy KB982312) is telepíteniük kell ahhoz, hogy védve legyenek a jelen, MS10-036 közleményben leírt biztonsági rés ellen.
**Tartalmaz a frissítés nem biztonsági jellegű funkcionalitásbeli módosítást is?**
A frissítés tartalmaz nem biztonsági jellegű, funkcionalitáshoz kapcsolódó módosításokat. További tudnivalókat a [Microsoft Tudásbázis 983632. számú cikkében](http://support.microsoft.com/kb/983632) talál.
A frissítés **A biztonsági rés részletes ismertetése** című szakaszban ismertetett módosítások mellett még egy lényeges módosítást tartalmaz. A frissítésben foglalt egyik kockázatcsökkentő megoldás megakadályozza az ATL biztonsági rést hagyó verziójával készített összetevők és vezérlők használatát a közlemény A biztonsági réssel kapcsolatos tudnivalók c. részében felsorolt Microsoft Office termékek működése során. A frissítésben felajánlott új, hatékony védelmi elemet felügyelik az összes ismert, közvetlen és nyilvános könyvtárakat érintő ATL biztonsági rést, és megakadályozzák azok sikeres kihasználását.
Az eljárás az ATL-nek azt biztonsági rését igyekszik áthidalni, amellyel a [973882 számú Microsoft biztonsági tanácsadó](http://technet.microsoft.com/security/advisory/973882) és az [MS09-035](http://go.microsoft.com/fwlink/?linkid=158131) foglalkozott. Ez a módosító alapértelmezésben engedélyezett minden érintett platformon, és segít kivédeni a Microsoft Office programba töltődő vezérlők ATL okozta támadhatóságát, beleértve a nem Microsoft által készített vezérlőket is.
**Mi a mélyreható biztonsági megoldás?**
Az adatbiztonság területén a mélységben tagolt védelem olyan struktúrát jelent, melyben egy hálózat vagy egy rendszer biztonságát több védelmi réteggel védik a támadók ellen.
**A cikkben említett Office összetevők ugyan a rendszeremre telepített Office csomag részét képezik; viszont nem telepítettem az összes vonatkozó összetevőt. Minden frissítés felajánlanak nekem?**
Igen, ha a rendszerre telepített Office csomag részét képezik a közleményben tárgyalt összetevők, az egyes összetevők telepítésétől függetlenül felajánljuk a rendszerhez a frissítéseket. Az érintett rendszerek vizsgálatára használt észlelési logikát úgy alakították ki, hogy az adott Office csomagban lévő összes összetevőhöz tartozó frissítést ellenőrizze és felajánlja a rendszernek. Azok a felhasználók, akik úgy döntenek, hogy nem alkalmazzák a nem telepített, de az Office csomaghoz tartozó összetevő frissítését, nem növelik a rendszer biztonsági kockázatát. Azok esetében pedig, akik úgy döntenek, hogy telepítik a frissítést, ez nem jár negatív hatással a rendszer biztonságára és teljesítményére.
**A Microsoft Office nem érintett verzióihoz felajánlott frissítés hibát jelez a Microsoft frissítési rendszerben?**
Nem. A frissítési rendszer megfelelően működik, és érzékeli, hogy rendszer alacsonyabb verziószámú fájlokkal van ellátva, mint a frissítési csomag. Ezért ajánlja fel a frissítést.
**A biztonsági közleményben tárgyalt szoftvernél korábbi kiadással rendelkezem. Mi a teendő?**
Teszteléssel állapították meg a közleményben tárgyalt szoftverkiadások érintettségét. A többi kiadás támogatási életciklusa végére ért. Ha többet szeretne tudni a Windows termékek életciklusáról, keresse fel a [Microsoft támogatási életciklusokkal](http://go.microsoft.com/fwlink/?linkid=21742)foglalkozó webhelyét.
A szoftver korábbi kiadásai felhasználóinak számára azt javasoljuk, hogy a potenciális biztonsági veszélyek elkerülése érdekében sürgősen térjenek át valamelyik támogatott kiadású szoftverre. A szoftverkiadás támogatási életciklusáról lásd a [Termék kiválasztása életciklusadatok megtekintéséhez](http://go.microsoft.com/fwlink/?linkid=169555) c. részt. A szoftverkiadásokhoz tartozó javítócsomagok részleteit lásd az [Életcikluson át támogatott szervizcsomagok](http://go.microsoft.com/fwlink/?linkid=89213) c. részben.
Azok az ügyfelek, akik további támogatást igényelnek ezekhez a korábbi verziókhoz, a támogatási lehetőségekről érdeklődjenek a Microsoft ügyfélkapcsolati képviselőjénél, a műszaki kapcsolattartótól vagy a Microsoft megfelelő partnerképviseletétől. Alliance, Premier vagy Authorized szerződéssel rendelkező felhasználóink forduljanak a Microsoft helyi értékesítési irodájához. Az elérhetőségeket keresse a [Microsoft Worldwide Information webhelyen](http://go.microsoft.com/fwlink/?linkid=33329): válasszon egy országot a legördülő listából, majd az **Indítás** gombra kattintva jelenítse meg a telefonszámokat. Telefonáláskor keresse a helyi értékesítési menedzsert. További információ: [Microsoft termékek terméktámogatási időszakával kapcsolatos, gyakran ismételt kérdések](http://go.microsoft.com/fwlink/?linkid=169557).
### A biztonsági réssel kapcsolatos tudnivalók
A súlyosság maximális foka és a biztonsági rés azonosítói
---------------------------------------------------------
A következő súlyossági besorolások a biztonsági rés maximálisan feltételezett hatását veszik számba. A biztonsági rés kihasználásának valószínűségére nézve a biztonsági közlemény kiadásától számított 30 napon belül, továbbá a súlyossági besoroláshoz és a biztonsági rendszeren kiváltott hatáshoz képest lásd az [júniusi](http://technet.microsoft.com/security/bulletin/ms10-jun) összefoglaló közlemény Kihasználhatósági információk c. részét. Bővebb információkért lásd: [Microsoft Kihasználhatósági információk](http://technet.microsoft.com/en-us/security/cc998259.aspx).
<p></p>
<table style="border:1px solid black;" class="dataTable">
<caption>
Biztonsági rés súlyossági besorolása és a maximális biztonsági hatás szoftverenkénti felbontásban
</caption>
<tr class="thead">
<th style="border:1px solid black;" >
Érintett szoftverek
</th>
<th style="border:1px solid black;" >
COM-érvényesítés biztonsági rése - CVE-2010-1263
</th>
<th style="border:1px solid black;" >
Összesített súlyossági besorolás
</th>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Microsoft Office XP
</th>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office XP Service Pack 3
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
Microsoft Office 2003
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft Office Excel 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office PowerPoint 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft Office Publisher 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office Visio 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft Office Word 2003 Service Pack 3
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr>
<th colspan="3" style="border:1px solid black;">
2007 Microsoft Office rendszer
</th>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office Excel 2007 Service Pack 1 és Microsoft Office Excel 2007 Service Pack 2
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft Office PowerPoint 2007 Service Pack 1 és Microsoft Office PowerPoint 2007 Service Pack 2
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office Publisher 2007 Service Pack 1 és Microsoft Office Publisher 2007 Service Pack 2
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft Office Visio 2007 Service Pack 1 és Microsoft Office Visio 2007 Service Pack 2
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft Office Word 2007 Service Pack 1 és Microsoft Office Word 2007 Service Pack 2
</td>
<td style="border:1px solid black;">
**Fontos**
Távoli kódfuttatás
</td>
<td style="border:1px solid black;">
**Fontos**
</td>
</tr>
</table>
<p></p>
COM-érvényesítés biztonsági rése - CVE-2010-1263
------------------------------------------------
A Microsoft Office szoftver COM objektumfuttatást érintő ellenőrzési módja távoli kódvégrehajtást lehetővé tévő biztonsági rést okoz. Ha egy támadó kihasználja a biztonsági rést, teljes mértékben átveheti a rendszer irányítását. Ezt követően a támadó programokat telepíthet, illetve adatokat tekinthet meg, módosíthat és törölhet, de korlátozás nélküli jogosultságokkal rendelkező új fiókokat is létrehozhat. A kevesebb jogosultsággal bíró fiókkal rendelkező felhasználók esetében kisebb lehet az érintettség, mint a rendszergazdai jogosultságokkal rendelkezők esetén.
A biztonsági rés standard bejegyzésének megtekintéséhez a normál biztonsági rés besorolási listáján lásd: [CVE-2010-1263](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-1263).
#### A COM-érvényesítés biztonsági résének (CVE-2010-1263) hibáit enyhítő tényezők
Az enyhítő tényezők közé sorolható egy beállítás, konfiguráció vagy általánosan bevált gyakorlat, amely alapértelmezett állapotában csökkentheti a biztonsági rés kihasználásának valószínűségét. A következő enyhítő tényezők hasznosnak bizonyulhatnak:
- E-mail küldésével a biztonsági rés nem használható ki automatikusan. A támadás sikerességéhez a felhasználónak meg kell nyitnia az e-mail üzenetben küldött mellékletet.
- Webalapú támadás esetén a támadónak olyan webhelyet kell üzemeltetnie, amely egy, a biztonsági rés kihasználását lehetővé tevő weblapot tartalmaz. Az érintett weboldalak és a felhasználó által biztosított tartalomnak, esetleg hirdetéseknek helyet adó weboldalak is tartalmazhatnak a biztonsági rést kihasználni képes különlegesen kialakított tartalmat. A támadóknak azonban nem áll módjukban a felhasználókat ezeknek a weboldalaknak a látogatására kényszerítenie. Ehelyett a támadóknak egy adott webhelyre kell csábítaniuk a felhasználókat. Ezt rendszerint úgy érik el, hogy ráveszik őket arra, hogy kattintsanak rá egy e-mailben lévő hivatkozásra vagy azonnali üzenetkezelőben megjelenő kérésre.
- A biztonsági rést kihasználó támadó a helyi felhasználóval egyező hozzáférést nyer a rendszerhez. A kevesebb jogosultsággal bíró fiókkal rendelkező felhasználók esetében kisebb a veszélyeztetettség, mint a rendszergazdai jogosultságokkal rendelkezők esetén
- A Microsoft Office 2002 és a későbbi verziók felhasználóinak a rendszer Megnyitás, Mentés illetve Mégse lehetőséget ajánl fel a dokumentum megnyitása előtt. Ez enyhítő tényező, hiszen a biztonsági rés kihasználásához egy egyszerű felhasználói művelet nem elegendő.
#### A COM-érvényesítés biztonsági résének (CVE-2010-1263) lehetséges megoldásai
A lehetséges megoldás olyan beállítást vagy konfigurációs módosítást takar, amely magát a biztonsági rést nem szünteti meg, azonban a frissítés telepítése előtt segít az ismert támadási lehetőségek kivédésében. A Microsoft alaposan megvizsgálta a következő lehetséges megoldásokat, és tájékoztatja a felhasználókat, amennyiben a megoldás csökkenti a működőképességet:
- Ne nyisson meg és ne mentsen el megbízhatatlan forrásokból származó vagy megbízható forrásból származó, de nem várt Microsoft Office fájlokat. Ez a biztonsági rés akkor használható ki, amikor a felhasználó egy különlegesen kialakított PowerPoint fájlt nyit meg.
#### Gyakran feltett kérdések a COM-érvényesítés biztonsági résével (CVE-2010-1263) kapcsolatban
**Mire terjed ki a biztonsági rés hatása?**
A biztonsági rés távolról történő kódfuttatást tehet lehetővé. Ha egy támadó kihasználja a biztonsági rést, teljes mértékben átveheti a rendszer irányítását. Ezt követően a támadó programokat telepíthet, illetve adatokat tekinthet meg, módosíthat és törölhet, de korlátozás nélküli jogosultságokkal rendelkező új fiókokat is létrehozhat.
**Mi okozza a biztonsági rést?**
A Microsoft Office nem megfelelően érvényesíti a COM objektumokat a különálló Excel, PowerPoint, Publisher, Visio és Word alkalmazásból való indításkor.
**Mi a COM?**
A Microsoft Windows operációs rendszerben a Microsoft COM (Component Object Model) technológia biztosítja a szoftverösszetevők közti kommunikáció lehetőségét. A fejlesztők a COM elemet arra használják fel, hogy újrafelhasználható szoftverösszetevőket hozzanak létre, összetevők összekapcsolásával alkalmazásokat hozzanak létre, és kihasználják a Windows-szolgáltatások előnyeit. A COM működéséről bővebben lásd a [Mi a COM?](http://www.microsoft.com/com/default.mspx) c. Microsoft-cikket.
**Mire használhatja a biztonsági rést a támadó?**
A biztonsági rést sikeresen kihasználó támadó tetszőleges programkódot futtathat a bejelentkezett felhasználó nevében. Ha valamely felhasználó felügyeleti jogosultságokkal bejelentkezett a rendszerbe, akkor a támadó teljes mértékben átveheti az irányítást a számítógép felett. Ezt követően a támadó programokat telepíthet, illetve adatokat tekinthet meg, módosíthat és törölhet, de korlátozás nélküli jogosultságokkal rendelkező új fiókokat is létrehozhat. A kevesebb jogosultsággal bíró fiókkal rendelkező felhasználók esetében kisebb a veszélyeztetettség, mint a rendszergazdai jogosultságokkal rendelkezők esetén
**Hogyan használhatja ki a támadó a biztonsági rést?**
A biztonsági rés akkor használható ki, ha a felhasználó különlegesen kialakított Excel, PowerPoint, Publisher, Visio, illetve Word fájlt nyit meg a Microsoft Office valamely érintett verziójával.
E-mailes támadásnál a támadó úgy próbálja kihasználni a biztonsági rést, hogy egy speciálisan kialakított Microsoft Office fájlt küld a felhasználónak, és ráveszi, hogy nyissa meg.
Internetes támadás esetén a támadónak olyan weboldalt kell üzemeltetnie, amely a biztonsági rés kihasználását lehetővé tévő, különlegesen kialakított Microsoft Office fájlt tartalmaz. Az érintett weboldalak és a felhasználó által biztosított tartalomnak, esetleg hirdetéseknek helyet adó weboldalak is tartalmazhatnak a biztonsági rést kihasználni képes különlegesen kialakított tartalmat. A támadónak nincs lehetősége arra, hogy a felhasználót a különlegesen kialakított webhely megnyitására kényszerítse. Ehelyett a támadóknak saját webhelyükre kell csábítaniuk a felhasználókat, ezt pedig rendszerint egy kifejezetten ezt a célt szolgáló hivatkozás segítségével érik el.
**Mely rendszerekre jelenti a legnagyobb veszélyt a biztonsági rés?**
Elsősorban azok a rendszerek (munkaállomások és terminálkiszolgálók) vannak kockázatnak kitéve, amelyek Excel, PowerPoint, Publisher, Visio, illetve Word programot használnak. A kiszolgáló nagyobb kockázatnak van kitéve, ha a rendszergazda engedélyezi a felhasználóknak a kiszolgálóra történő bejelentkezést és a programok futtatását. Ezt azonban a gyakorlati tanácsok értelmében feltétlenül kerülni kell.
**Mi a frissítés feladata?**
A frissítés módosítja a futtatni készült COM-objektumok érvényesítését a Microsoft Office programban.
**Ismert volt-e a nyilvánosság előtt ez a biztonsági rés a biztonsági közlemény kiadásának idején?**
Nem. A Microsoft ezt a célt szolgáló tájékoztatáson keresztül szerzett tudomást a biztonsági résről.
**A közlemény kibocsátásáig kapott-e a Microsoft a biztonsági rés kihasználásáról tájékoztató értesítést?**
Nem. E közlemény eredeti verziójának kiadásáig a Microsoft nem kapott olyan információt, amely arra utalt volna, hogy ezt a biztonsági rést nyilvános támadásra használták, és nem találkozott olyan nyilvánosságra hozott leírásokkal, amelyek tartalmazták volna egy sikeres támadás forgatókönyvét.
### Frissítési információ
Észlelési és telepítési eszközök, útmutatás
-------------------------------------------
A szoftveres és biztonsági frissítések kezeléséhez azokat a szervezet asztali és hordozható rendszereire, valamint kiszolgálóira is telepíteni kell. További tájékoztatásért látogasson el a [TechNet Update Management Center](http://go.microsoft.com/fwlink/?linkid=69903) weboldalára. A [Microsoft TechNet biztonsággal foglalkozó](http://go.microsoft.com/fwlink/?linkid=21132) webhelye további információkat tartalmaz a Microsoft termékeinek biztonsági kérdéseiről.
A biztonsági frissítések a [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) és a [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130) weboldalról tölthetők le. A biztonsági frissítések a [Microsoft letöltőközpontjából](http://go.microsoft.com/fwlink/?linkid=21129) is elérhetőek. Legegyszerűbben a „security update” kifejezésre irányuló kulcsszavas kereséssel találhatja meg ezeket.
A biztonsági frissítések a [Microsoft Update katalógusából](http://go.microsoft.com/fwlink/?linkid=96155) is letölthetőek. A Microsoft Update katalógus a Windows Update és Microsoft Update szolgáltatáson keresztül elérhető tartalom kereshető adatbázisa; ide tartoznak a biztonsági frissítések, illesztőprogramok és szervizcsomagok. A biztonsági közlemény azonosítójára (pl. „MS07-036”) történő kereséssel hozzáadhatja az összes vonatkozó frissítést a kosárhoz (beleértve a frissítés különböző nyelvi változatait), és letöltheti azokat a megadott mappába. A Microsoft Update katalógus részletes leírását lásd a vonatkozó [GYIK](http://go.microsoft.com/fwlink/?linkid=97900) részben.
**Megjegyzés** 2009. augusztus 1-től a Microsoft megszünteti az Office Update és az Office Update Inventory Tool támogatását. A Microsoft Office termékeihez készült legújabb frissítéseket a [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) segítségével érheti el. A további tudnivalókat lásd [Az Office Update bemutatása: Gyakran ismételt kérdések című témakört.](http://office.microsoft.com/en-us/downloads/fx010402221033.aspx)
**Útmutató az észleléshez és a telepítéshez**
A biztonsági frissítésekkel kapcsolatban a Microsoft észlelési és telepítési segítséget nyújt. Ez az útmutató olyan javaslatokat és tudnivalókat tartalmaz, amelyeket segítséget nyújthatnak az informatikusoknak a biztonsági frissítések észlelési és telepítési eszközeinek használatához. További tudnivalókat a [Microsoft Tudásbázis 961747. számú cikkében](http://support.microsoft.com/kb/961747) talál.
**Microsoft Baseline Security Analyzer**
A Microsoft Baseline Security Analyzer (MBSA) segítségével a rendszergazda mind a helyi, mind a távoli számítógépeken ellenőrizheti, hogy mely biztonsági frissítések hiányoznak, illetve hogy mely biztonsági beállítások vannak helytelenül megadva. Ha többet szeretne tudni az MBSA -eszközről, látogasson el a [Microsoft Baseline Security Analyzer webhelyre](http://www.microsoft.com/technet/security/tools/mbsahome.mspx).
A következő táblázat a biztonsági frissítés MBSA észlelési jellemzőit foglalja össze.
| Szoftver | MBSA 2.1.1 |
|--------------------------------------------------------------------------------------------|------------|
| Microsoft Office XP Service Pack 3 | Igen |
| Microsoft Office 2003 Service Pack 3 | Igen |
| 2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2 | Igen |
Az MBSA legújabb verziójának kiadása: [Microsoft Baseline Security Analyzer 2.1.1](http://www.microsoft.com/downloads/details.aspx?familyid=b1e76bbe-71df-41e8-8b52-c871d012ba78&displaylang=en). A további információkat lásd: [Microsoft Baseline Security Analyzer 2.1](http://technet.microsoft.com/en-us/security/cc184923.aspx).
**Megjegyzés** Az MBSA 2.1.1, a Microsoft Update és a Windows Server Update Services által nem támogatott, örökölt szoftverek felhasználói számára: látogassanak el a [Microsoft Baseline Security Analyzer](http://www.microsoft.com/technet/security/tools/mbsahome.mspx) oldalára, és tekintsék meg az Örökölt termékek támogatása c. részt. Ez ismerteti az összetett biztonsági frissítés észlelésének beállítását az örökölt eszközökkel.
**Windows Server Update Services**
A Windows Server Update Services (WSUS) szolgáltatással a rendszergazdák központilag telepíthetik a legújabb fontos és biztonsági frissítéseket Microsoft Windows 2000 és újabb operációs rendszerekhez, az Office XP és újabb kiadásaihoz, az Exchange Server 2003 és az SQL Server 2000 programokhoz. A biztonsági frissítésnek Windows Server Update Services szolgáltatással történő központi telepítéséről a [Windows Server Update Services webhelyen](http://go.microsoft.com/fwlink/?linkid=50120) tudhat meg többet.
**Systems Management Server**
A következő táblázat a biztonsági frissítés SMS-észlelési és telepítési jellemzőit foglalja össze.
| Szoftver | SMS 2.0 | SMS 2003 SUIT alkalmazással | SMS 2003 ITMU alkalmazással | Configuration Manager 2007 |
|--------------------------------------------------------------------------------------------|---------|-----------------------------|-----------------------------|----------------------------|
| Microsoft Office XP Service Pack 3 | Nem | Nem | Igen | Igen |
| Microsoft Office 2003 Service Pack 3 | Nem | Nem | Igen | Igen |
| 2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2 | Nem | Nem | Igen | Igen |
SMS 2.0 és SMS 2003 esetén az SMS a Security Update Inventory Tool (SUIT) program segítségével fel tudja ismerni a biztonsági frissítéseket. Lásd még: [Letöltések a Systems Management Server 2.0 verzióhoz](http://technet.microsoft.com/en-us/sms/bb676799.aspx).
Az SMS 2003 esetében az SMS 2003 Inventory Tool (ITMU) eszköz az SMS-funkció által alkalmazható a [Microsoft Update](http://update.microsoft.com/microsoftupdate) által felajánlott és a [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120) által támogatott biztonsági frissítések észlelésére. Az SMS 2003 ITMU részleteit lásd az [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/en-us/sms/bb676783.aspx) webhelyén. A keresőeszközökről bővebb tájékoztatást olvashat az [SMS 2003 szoftverfrissítés-kereső eszközök](http://technet.microsoft.com/en-us/sms/bb676786.aspx) című leírásban. Lásd még: [Letöltések a Systems Management Server 2003 verzióhoz](http://technet.microsoft.com/en-us/sms/bb676766.aspx).
A System Center Configuration Manager 2007 a WSUS 3.0 verzióját alkalmazza a frissítések észleléséhez. A Configuration Manager 2007 szoftverfrissítés-kezelésével kapcsolatos bővebb információt lásd: [System Center Configuration Manager 2007](http://technet.microsoft.com/en-us/library/bb735860.aspx).
Az SMS-eszközről az [SMS webhelyén](http://go.microsoft.com/fwlink/?linkid=21158) talál tájékoztatást.
Részletes információt a [Microsoft Tudásbázis 910723 számú cikkében](http://support.microsoft.com/kb/910723) talál: a havi „Útmutató az észleléshez és a telepítéshez” cikkek áttekintő listája.
**Megjegyzés** Ha adminisztratív telepítési pontról (AIP) telepítette az Office XP vagy Office 2003 rendszert, lehetséges, hogy a frissítést az SMS segítségével nem tudja majd telepíteni, amennyiben az adminisztratív telepítési pontot az eredeti helyről frissítette. További tudnivalókat a közlemény későbbi részében az **Office felügyeleti telepítési pont** cím alatt talál.
**Office felügyeleti telepítési pont**
Ha az alkalmazást kiszolgálóról telepítette, a kiszolgáló rendszergazdájának a felügyeleti frissítéssel frissítenie kell a kiszolgálón lévő telepítési forrást, és ezt követően központi telepítéssel kell telepítenie azt a rendszerre.
- A Microsoft Office XP támogatott verzióit lásd: [Felügyeleti telepítési pont létrehozása](http://office.microsoft.com/en-us/orkxp/ha011363091033.aspx). Arról, hogy hogyan kell az ügyfélrendszer forrását frissített felügyeleti telepítési pontról Office XP forrásra módosítani, lásd a [Microsoft Tudásbázis 922665](http://support.microsoft.com/kb/922665) számú cikkét.
**Megjegyzés** Ha központilag, frissített felügyeleti lemezképpel szeretné kezelni a szoftverfrissítéseket, további információkért lásd a következő cikket:[Office XP ügyfelek frissítése kötegelt felügyeleti lemezképről](http://office.microsoft.com/en-us/orkxp/ha011525721033.aspx).
- A Microsoft Office 2003 támogatott verzióit lásd: [Felügyeleti telepítési pont létrehozása](http://office.microsoft.com/en-us/ork2003/ha011401931033.aspx). Arról, hogy hogyan kell az ügyfélszámítógép forrását frissített felügyeleti telepítési pontról eredeti Office 2003 forrásra vagy Service Pack 3 (SP3) forrásra módosítani, lásd a [Microsoft Tudásbázis 902349](http://support.microsoft.com/kb/902349) számú cikkét.
**Megjegyzés** Ha központilag, frissített felügyeleti lemezképpel szeretné kezelni a szoftverfrissítéseket, további információkért lásd a következő cikket: [Office 2003 termékfrissítések terjesztése](http://office.microsoft.com/en-us/ork2003/ha011402381033.aspx?pid=ch011480761033).
- A 2007 Microsoft Office rendszer támogatott verzióit lásd itt: [Hálózati telepítési pont létrehozása 2007 Office rendszerben](http://technet.microsoft.com/en-us/library/cc179063.aspx).
**Megjegyzés** Ha központilag szeretné kezelni a biztonsági frissítéseket, vegye igénybe a Windows Server Update Services szolgáltatást. A 2007 Microsoft Office rendszer biztonsági frissítéseinek Windows Server Update Services szolgáltatással történő telepítéséről részletesebben a [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120) webhelyen olvashat.
**Az Update Compatibility Evaluator (a frissítéskompatibilitás kiértékelője) és az Application Compatibility Toolkit (alkalmazáskompatibilitási eszközkészlet)**
Az alkalmazások működése érdekében a frissítések gyakran írnak ugyanazokba a fájlokba, illetve regisztrációs bejegyzésekbe. Ez inkompatibilitást okozhat, és növelheti a biztonsági frissítések központi telepítésére használt időt. A Windows frissítések és az alkalmazásoknak való megfelelőség tesztelése és ellenőrzése egyszerűsíthető az [Update Compatibility Evaluator](http://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true) eszközeivel, ami része az [Application Compatibility Toolkit](http://www.microsoft.com/downloads/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=hu) alkalmazáskompatibilitási eszközkészletnek.
Az Application Compatibility Toolkit (ACT) tartalmazza a Microsoft Windows Vista, a Windows Update, a Microsoft Security Update vagy a Windows Internet Explorer új verziójának központi telepítése előtt az alkalmazáskompatibilitási problémák kiértékeléséhez és enyhítéséhez szükséges eszközöket és dokumentációt.
Biztonsági frissítés telepítése
-------------------------------
**Érintett szoftverek**
Az érintett szoftverre vonatkozó biztonsági frissítésről a megfelelő hivatkozásra kattintva tudhat meg többet:
#### Office 2003 (összes kiadás)
**Hivatkozási táblázat**
Az alábbi táblázat a szoftverre vonatkozó, biztonsági frissítésekkel kapcsolatos információkat tartalmazza. További tudnivalókat olvashat a fejezet **Tudnivalók a telepítésről** című részében.
<p> </p>
<p></p>
<table style="border:1px solid black;">
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>Közzététel jövőbeni szervizcsomagokban</strong></td>
<td style="border:1px solid black;">Ehhez a szoftverhez nincs több tervezett szervizcsomag. A problémát érintő frissítés valószínűleg része lesz a jövőbeni összegző frissítőcsomagoknak.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Telepítés</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Telepítés felhasználói beavatkozás nélkül</td>
<td style="border:1px solid black;">Microsoft Office 2003 Service Pack 3 esetén:<br />
office2003-kb982311-fullfile-enu /q:a</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Excel 2003 Service Pack 3 esetén:<br />
office2003-kb982133-fullfile-enu /q:a</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office PowerPoint 2003 Service Pack 3 esetén:<br />
office2003-kb982157-fullfile-enu /q:a</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Publisher 2003 Service Pack 3 esetén:<br />
office2003-kb982122-fullfile-enu /q:a</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Visio 2003 Service Pack 3 esetén:<br />
office2003-kb982126-fullfile-enu /q:a</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Word 2003 Service Pack 3 esetén:<br />
office2003-kb982134-fullfile-enu /q:a</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Telepítés újraindítás nélkül</td>
<td style="border:1px solid black;">Microsoft Office 2003 Service Pack 3 esetén:<br />
office2003-kb982311-fullfile-enu /r:n</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Excel 2003 Service Pack 3 esetén:<br />
office2003-kb982133-fullfile-enu /r:n</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office PowerPoint 2003 Service Pack 3 esetén:<br />
office2003-kb982157-fullfile-enu /r:n</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Publisher 2003 Service Pack 3 esetén:<br />
office2003-kb982122-fullfile-enu /r:n</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Visio 2003 Service Pack 3 esetén:<br />
office2003-kb982126-fullfile-enu /r:n</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Word 2003 Service Pack 3 esetén:<br />
office2003-kb982134-fullfile-enu /r:n</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Frissítési naplófájl</td>
<td style="border:1px solid black;">Nem érintett</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">További információk</td>
<td style="border:1px solid black;">Az észlelésről és a telepítésről lásd a korábbi, <strong>Észlelési és telepítési eszközök, útmutatás</strong> c. részt. <br />
<br />
Az önállóan telepíthető funkciókról lásd az <strong>Office-funkciók felügyeleti telepítéshez</strong> alfejezetet.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Újraindítás szükségessége</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Újraindítás szükséges?</td>
<td style="border:1px solid black;">Egyes esetekben a frissítés nem teszi szükségessé a számítógép újraindítását. Ha azonban a szükséges fájlokat más program használja, a frissítést követően újra kell indítani a számítógépet. Ebben az esetben a rendszer üzenetben figyelmezteti a felhasználót ennek szükségességére.<br />
<br />
Ha csökkenteni akarja a számítógép újraindítása szükségességének valószínűségét, a biztonsági frissítés telepítése előtt állítsa le az érintett fájlokat esetlegesen használó valamennyi érintett szolgáltatást és alkalmazást. További információkat arra vonatkozóan, hogy miért ajánlhatja fel a számítógép az újraindítást, a <a href="http://support.microsoft.com/kb/887012">Microsoft Tudásbázis 887012 számú cikkében talál</a>.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Hotpatching</td>
<td style="border:1px solid black;">Nem érintett</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Információ az eltávolításhoz</strong></td>
<td style="border:1px solid black;">A Vezérlőpult <strong>Programok telepítése és törlése</strong> eszközét alkalmazza.<br/>
<strong>Megjegyzés</strong> A frissítés eltávolításakor esetleg üzenet figyelmezteti arra, hogy helyezze be a Microsoft Office 2003 CD-t a CD-meghajtóba. Továbbá az is előfordulhat , hogy nem tudja törölni a frissítést a Vezérlőpult Programok telepítése és törlése menüjéből. A probléma több okra is visszavezethető. Az eltávolítással kapcsolatban tekintse meg a <a href="http://support.microsoft.com/kb/903771">Microsoft Tudásbázis 903771</a> számú cikkét.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Fájlinformációk</strong></td>
<td style="border:1px solid black;">Microsoft Office 2003 Service Pack 3 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982311">Microsoft Tudásbázis 982311. számú cikkét</a></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Excel 2003 Service Pack 3 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982133">Microsoft Tudásbázis 982133. számú cikkét</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office PowerPoint 2003 Service Pack 3 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982157">Microsoft Tudásbázis 982157. számú cikkét</a></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Publisher 2003 Service Pack 3 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982122">Microsoft Tudásbázis 982122. számú cikkét</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Visio 2003 Service Pack 3 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982126">Microsoft Tudásbázis 982126. számú cikkét</a></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Word 2003 Service Pack 3 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982134">Microsoft Tudásbázis 982134. számú cikkét</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Rendszerleíró kulcsok ellenőrzése</strong></td>
<td style="border:1px solid black;">Nem érintett</td>
</tr>
</tbody>
</table>
<p></p>
#### Office-funkciók
A következő táblázat tartalmazza a frissítéshez újratelepítendő funkciók nevét (kis- és nagybetű megkülönböztetésével). Az összes szolgáltatás telepítéséhez a **REINSTALL=ALL** szintaxist is használhatja, vagy pedig telepítheti az alábbi szolgáltatásokat:
| Termék | Szolgáltatás |
|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|
| ACCESSRT, ACC11 | ACCESSNonBootFiles,ProductFiles |
| OUTLS11, VISVEA, PPT11, FP11, ONOTE11, OUTL11, OUTLSM11, PUB11, INF11, PRJPROE, PRJPRO, PRJSTDE, PRJSTD, VISPRO, VISPROR, VISSTD, VISSTDR | ProductFiles |
| XLVIEW | ExcelViewer |
| WORDVIEW | WORDVIEWFiles |
| RMS | RMSFiles,ProductFiles |
| BASIC11, PERS11, STDP11, STD11 | WORDNonBootFiles,EXCELNonBootFiles,ProductFiles |
| PRO11SB, PROI11, PRO11 | WORDNonBootFiles,ACCESSNonBootFiles,EXCELNonBootFiles,ProductFiles |
| WORD11 | WORDNonBootFiles,ProductFiles |
| EXCEL11 | EXCELNonBootFiles,ProductFiles |
**Megjegyzés** Felügyelt környezetben dolgozó rendszergazdák teljes körű forrásokat találnak az Office frissítések letöltésére az Office Admin Update Center letöltőközpontban. A webhelyen lejjebb gördítve tekintse át a **Frissítési források** részben a frissíteni kívánt szoftververzióról szóló részt. A [Windows telepítési dokumentációja](http://go.microsoft.com/fwlink/?linkid=21685) is tartalmaz további adatokat a Windows Installer által támogatott paraméterekről.
#### Tudnivalók a központi telepítésről
**A frissítés telepítése**
A frissítést az Érintett és nem érintett szoftverek alfejezetben ismertetett letöltési hivatkozás útján telepítheti. Ha az alkalmazást kiszolgálóról telepítette, a kiszolgáló rendszergazdájának ehelyett felügyeleti frissítéssel kell frissítenie a kiszolgálón lévő telepítési forrást, és ezt követően telepítenie azt a rendszerre. A felügyeleti telepítési pontok részleteiről lásd az **Office felügyeleti telepítési pont** adatait az **Észlelési és telepítési eszközök, útmutatás** alfejezetben.
A biztonsági frissítéshez Windows Installer 2.0 vagy frissebb verzió telepítése szükséges. Minden támogatott Windows-verzió tartalmazza a Windows Installer 2.0 vagy későbbi verzióját.
A Windows Installer 2.0 vagy későbbi verziójának telepítéséhez látogasson el az alábbi Microsoft webhelyek valamelyikére:
- [Windows Installer 4.5 Redistributable alkalmazás Windows Server 2008, Windows Vista, Windows Server 2003 és Windows XP rendszerhez](http://www.microsoft.com/downloads/details.aspx?familyid=5a58b56f-60b6-4412-95b9-54d056d6f9f4&displaylang=en)
- [Windows Installer 3.1 Redistributable alkalmazás Windows Server 2003, Windows XP és Microsoft Windows 2000 rendszerhez](http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en)
- [Windows Installer 2.0 Redistributable a Microsoft Windows 2000 és Windows NT 4.0 rendszerhez](http://go.microsoft.com/fwlink/?linkid=33338)
A közleményben alkalmazott szakkifejezésekkel (pl. *gyorsjavítás*) kapcsolatban tekintse meg a [Microsoft Tudásbázis 824684](http://support.microsoft.com/kb/824684) számú cikkét.
A biztonsági frissítés telepítője az alábbi kapcsolók használatát támogatja:
<p></p>
<table class="dataTable">
<caption>
A biztonsági frissítés támogatott telepítési kapcsolói
</caption>
</table>
<p></p>
| Kapcsoló | Leírás |
|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------|
| **/q** | Csendes üzemmód használata, vagyis az üzenetek elrejtése a fájlok kibontása közben. |
| **/q:u** | Felhasználói csendes mód megadása, melynek során egyes párbeszédpanelek megjelennek. |
| **/q:a** | A rendszergazdai csendes mód megadása esetén egyetlen párbeszédpanel sem jelenik meg a felhasználónak. |
| **/t:path** | A fájlok kibontására használt célmappa megadása. |
| **/c** | A fájlok kibontása telepítés nélkül Ha a **/t**: elérési\_út kapcsoló nincs megadva, a program kéri a célmappa megadását. |
| **/c:path** | A szerző által definiált telepítési parancs felülbírálása. A telepítőhöz tartozó Setup.inf vagy .exe fájl elérési útjának és nevének megadása |
| **/r:n** | A rendszer a telepítés után soha nem indul újra. |
| **/r:I** | Újraindítás szükségessége esetén rákérdez a rendszer újraindítására, kivéve, ha a kapcsolót a **/q:a** kapcsolóval együtt adta meg. |
| **/r:a** | A rendszer mindig újraindul a telepítést követően. |
| **/r:s** | A rendszer újraindítása telepítés után a felhasználó megkérdezése nélkül |
| **/n:v** | A verzióellenőrzés kihagyása (a program telepítése az esetleges meglévő verzióra). |
**Megjegyzés:** A kapcsolók egyetlen parancsban is megadhatók. A visszamenőleges kompatibilitás érdekében a biztonsági frissítés a régebbi verziójú telepítőprogram számos telepítési kapcsolóját támogatja. A rendelkezésre álló telepítési kapcsolókról a [Microsoft Tudásbázis 262841](http://support.microsoft.com/kb/262841) számú cikkében talál további ismertetést.
**A frissítés eltávolítása**
A biztonsági frissítést a Vezérlőpult Programok telepítése és törlése segédprogramjával távolíthatja el.
**Megjegyzés** A frissítés eltávolításakor esetleg üzenet figyelmezteti arra, hogy helyezze be a Microsoft Office 2003 CD-t a CD-meghajtóba. Továbbá az is előfordulhat , hogy nem tudja törölni a frissítést a Vezérlőpult Programok telepítése és törlése menüjéből. A probléma több okra is visszavezethető. Az eltávolítással kapcsolatban tekintse meg a [Microsoft Tudásbázis 903771](http://support.microsoft.com/kb/903771) számú cikkét.
**A frissítés telepítésének ellenőrzése**
- **Microsoft Baseline Security Analyzer**
A Microsoft Baseline Security Analyzer (MBSA) eszközzel ellenőrizheti, hogy a biztonsági frissítés telepítve van-e az érintett számítógépen. További tájékoztatásért tekintse meg a közlemény korábbi részének **Észlelési és telepítési eszközök, útmutatás** című fejezetét.
- **Fájlverziószám ellenőrzése**
Mivel a Microsoft Windows operációs rendszernek több verziója és kiadása is van, a lépések az egyes rendszereken eltérőek lehetnek. Ilyen esetben a megfelelő lépések végrehajtásához az adott termék dokumentációja ad segítséget.
1. Kattintson a **Start** elemre, majd a **Keresés indítása** mezőben adja meg a frissítőfájl nevét.
2. Amikor a fájl megjelenik a **Programok** között, jobb egérgombbal kattintson a fájlnévre, majd a **Tulajdonságok** lehetőségre.
3. Az **Általános** lapon hasonlítsa össze a fájlméretet a közlemény Tudásbázis cikkében ismertetett fájlinformációs táblázatokkal.
4. Az adatok összevetéséhez (pl. fájlverzió, a módosítás dátuma) a **Részletek** lapra is kattinthat, a közlemény Tudásbázis cikkében ismertetett fájlinformációs táblázatok alapján.
5. Kattinthat a **korábbi verziókat** felsoroló lapra is, majd összehasonlíthatja a korábbi fájlverzió adatait az aktuális, frissített fájléval.
#### A 2007 Microsoft Office System (minden kiadás)
**Hivatkozási táblázat**
Az alábbi táblázat a szoftverre vonatkozó, biztonsági frissítésekkel kapcsolatos információkat tartalmazza. További tudnivalókat olvashat a fejezet **Tudnivalók a telepítésről** című részében.
<p> </p>
<p></p>
<table style="border:1px solid black;">
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>Közzététel jövőbeni szervizcsomagokban</strong></td>
<td style="border:1px solid black;">A hiba javítása szerepelni fog egy jövőbeni szervizcsomagban vagy frissítőcsomagban.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Telepítés</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Telepítés felhasználói beavatkozás nélkül</td>
<td style="border:1px solid black;">2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2<br />
office2007-kb982312-fullfile-x86-glb /passive</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Excel 2007 Service Pack 1 és Microsoft Office Excel 2007 Service Pack 2 esetén:<br />
excel2007-kb982308-fullfile-x86-glb /passive</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office PowerPoint 2007 Service Pack 1 és Microsoft Office PowerPoint 2007 Service Pack 2 esetén:<br />
powerpoint2007-kb982158-fullfile-x86-glb /passive</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Publisher 2007 Service Pack 1 és Microsoft Office Publisher 2007 Service Pack 2 esetén:<br />
publisher2007-kb982124-fullfile-x86-glb /passive</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Visio 2007 Service Pack 1 és Microsoft Office Visio 2007 Service Pack 2:<br />
visio2007-kb982127-fullfile-x86-glb /passive</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Word 2007 Service Pack 1 és Microsoft Office Word 2007 Service Pack 2:<br />
word-kb982135-fullfile-x86-glb /passive</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Telepítés újraindítás nélkül</td>
<td style="border:1px solid black;">2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2<br />
office2007-kb982312-fullfile-x86-glb /norestart</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Excel 2007 Service Pack 1 és Microsoft Office Excel 2007 Service Pack 2 esetén:<br />
excel2007-kb982308-fullfile-x86-glb /norestart</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office PowerPoint 2007 Service Pack 1 és Microsoft Office PowerPoint 2007 Service Pack 2 esetén:<br />
powerpoint2007-kb982158-fullfile-x86-glb /norestart</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Publisher 2007 Service Pack 1 és Microsoft Office Publisher 2007 Service Pack 2 esetén:<br />
publisher2007-kb982124-fullfile-x86-glb /norestart</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Visio 2007 Service Pack 1 és Microsoft Office Visio 2007 Service Pack 2:<br />
visio2007-kb982127-fullfile-x86-glb /norestart</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Word 2007 Service Pack 1 és Microsoft Office Word 2007 Service Pack 2:<br />
word-kb982135-fullfile-x86-glb /norestart</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Frissítési naplófájl</td>
<td style="border:1px solid black;">Nem érintett</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">További információk</td>
<td style="border:1px solid black;">Az észlelésről és a telepítésről lásd a korábbi, <strong>Észlelési és telepítési eszközök, útmutatás</strong> c. részt.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Újraindítás szükségessége</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Újraindítás szükséges?</td>
<td style="border:1px solid black;">Egyes esetekben a frissítés nem teszi szükségessé a számítógép újraindítását. Ha azonban a szükséges fájlokat más program használja, a frissítést követően újra kell indítani a számítógépet. Ebben az esetben a rendszer üzenetben figyelmezteti a felhasználót ennek szükségességére.<br />
<br />
Ha csökkenteni akarja a számítógép újraindítása szükségességének valószínűségét, a biztonsági frissítés telepítése előtt állítsa le az érintett fájlokat esetlegesen használó valamennyi érintett szolgáltatást és alkalmazást. További információkat arra vonatkozóan, hogy miért ajánlhatja fel a számítógép az újraindítást, a <a href="http://support.microsoft.com/kb/887012">Microsoft Tudásbázis 887012 számú cikkében talál</a>.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Hotpatching</td>
<td style="border:1px solid black;">Nem érintett</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Információ az eltávolításhoz</strong></td>
<td style="border:1px solid black;">A Vezérlőpult <strong>Programok telepítése és törlése</strong> eszközét alkalmazza.<br/></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Fájlinformációk</strong></td>
<td style="border:1px solid black;">2007 Microsoft Office System Service Pack 1 és 2007 Microsoft Office System Service Pack 2<br />
Lásd a <a href="http://support.microsoft.com/kb/982312">Microsoft Tudásbázis 982312. számú cikkét</a></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Excel 2007 Service Pack 1 és Microsoft Office Excel 2007 Service Pack 2 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982308">Microsoft Tudásbázis 982308. számú cikkét</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office PowerPoint 2007 Service Pack 1 és Microsoft Office PowerPoint 2007 Service Pack 2 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982158">Microsoft Tudásbázis 982158. számú cikkét</a></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Publisher 2007 Service Pack 1 és Microsoft Office Publisher 2007 Service Pack 2 esetén:<br />
Lásd a <a href="http://support.microsoft.com/kb/982124">Microsoft Tudásbázis 982124. számú cikkét</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Visio 2007 Service Pack 1 és Microsoft Office Visio 2007 Service Pack 2:<br />
Lásd a <a href="http://support.microsoft.com/kb/982127">Microsoft Tudásbázis 982127. számú cikkét</a></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Microsoft Office Word 2007 Service Pack 1 és Microsoft Office Word 2007 Service Pack 2:<br />
Lásd a <a href="http://support.microsoft.com/kb/982135">Microsoft Tudásbázis 982135. számú cikkét</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Rendszerleíró kulcsok ellenőrzése</strong></td>
<td style="border:1px solid black;">Nem érintett</td>
</tr>
</tbody>
</table>
<p></p>
#### Tudnivalók a központi telepítésről
**A frissítés telepítése**
A frissítést az Érintett és nem érintett szoftverek alfejezetben ismertetett letöltési hivatkozás útján telepítheti. Ha az alkalmazást kiszolgálóról telepítette, a kiszolgáló rendszergazdájának ehelyett felügyeleti frissítéssel kell frissítenie a kiszolgálón lévő telepítési forrást, és ezt követően telepítenie azt a rendszerre. A felügyeleti telepítési pontok részleteiről lásd az **Office felügyeleti telepítési pont** adatait az **Észlelési és telepítési eszközök, útmutatás** alfejezetben.
A biztonsági frissítéshez Windows Installer 3.1 vagy frissebb verzió telepítése szükséges.
A Windows Installer 3.1 vagy későbbi verziójának telepítéséhez látogasson el az alábbi Microsoft webhelyek valamelyikére:
- [Windows Installer 4.5 Redistributable alkalmazás Windows Server 2008, Windows Vista, Windows Server 2003 és Windows XP rendszerhez](http://www.microsoft.com/downloads/details.aspx?familyid=5a58b56f-60b6-4412-95b9-54d056d6f9f4&displaylang=en)
- [Windows Installer 3.1 Redistributable alkalmazás Windows Server 2003, Windows XP és Microsoft Windows 2000 rendszerhez](http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en)
A közleményben alkalmazott szakkifejezésekkel (pl. *gyorsjavítás*) kapcsolatban tekintse meg a [Microsoft Tudásbázis 824684](http://support.microsoft.com/kb/824684) számú cikkét.
A biztonsági frissítés telepítője az alábbi kapcsolók használatát támogatja:
<p></p>
<table class="dataTable">
<caption>
A biztonsági frissítés támogatott telepítési kapcsolói
</caption>
</table>
<p></p>
| Kapcsoló | Leírás |
|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
| **/?** vagy **/help** | A Használat párbeszédpanel megjelenítése. |
| **/passive** | A passzív mód meghatározása. Nincs szükség felhasználói beavatkozásra, az alapszintű párbeszédpanelek láthatóak ugyan, de a művelet meg nem szakítható. |
| **/quiet** | Csendes üzemmód használata, vagyis az üzenetek elrejtése a fájlok kibontása közben. |
| **/norestart** | Nem indítja újra a rendszert, ha a frissítéshez újraindításra van szükség. |
| **/forcerestart** | A frissítés alkalmazását követően automatikusan újraindítja a rendszert, függetlenül attól, hogy a frissítéshez szükséges-e újraindítani a rendszert. |
| **/extract** | A fájlok kibontása telepítés nélkül A program kérni fogja a célmappa megadását. |
| **/extract:<path>** | A szerző által definiált telepítési parancs felülbírálása. A telepítőhöz tartozó Setup.inf vagy .exe fájl elérési útjának és nevének megadása |
| **/lang:<LCID>** | Megadott nyelv kényszerű használata, ha a frissítési csomaggal az adott nyelv használható. |
| **/log:<log file>** | A frissítés telepítése közben lehetővé teszi a naplózást, a Vnox és az Installer által egyaránt. |
**Megjegyzés:** A kapcsolók egyetlen parancsban is megadhatók. A visszamenőleges kompatibilitás érdekében a biztonsági frissítés a régebbi verziójú telepítőprogram számos telepítési kapcsolóját támogatja. A rendelkezésre álló telepítési kapcsolókról a [Microsoft Tudásbázis 262841](http://support.microsoft.com/kb/262841) számú cikkében talál további ismertetést.
**A frissítés eltávolítása**
A biztonsági frissítést a Vezérlőpult Programok telepítése és törlése segédprogramjával távolíthatja el.
**Megjegyzés:** A frissítés eltávolításakor esetleg üzenet figyelmezteti arra, hogy helyezze be a 2007-es Microsoft Office CD-lemezt a CD-meghajtóba. Továbbá az is előfordulhat , hogy nem tudja törölni a frissítést a Vezérlőpult Programok telepítése és törlése menüjéből. A probléma több okra is visszavezethető. Az eltávolítással kapcsolatban tekintse meg a [Microsoft Tudásbázis 903771](http://support.microsoft.com/kb/903771) számú cikkét.
**A frissítés telepítésének ellenőrzése**
- **Microsoft Baseline Security Analyzer**
A Microsoft Baseline Security Analyzer (MBSA) eszközzel ellenőrizheti, hogy a biztonsági frissítés telepítve van-e az érintett számítógépen. További tájékoztatásért tekintse meg a közlemény korábbi részének **Észlelési és telepítési eszközök, útmutatás** című fejezetét.
- **Fájlverziószám ellenőrzése**
Mivel a Microsoft Windows operációs rendszernek több verziója és kiadása is van, a lépések az egyes rendszereken eltérőek lehetnek. Ilyen esetben a megfelelő lépések végrehajtásához az adott termék dokumentációja ad segítséget.
1. Kattintson a **Start** elemre, majd a **Keresés indítása** mezőben adja meg a frissítőfájl nevét.
2. Amikor a fájl megjelenik a **Programok** között, jobb egérgombbal kattintson a fájlnévre, majd a **Tulajdonságok** lehetőségre.
3. Az **Általános** lapon hasonlítsa össze a fájlméretet a közlemény Tudásbázis cikkében ismertetett fájlinformációs táblázatokkal.
4. Az adatok összevetéséhez (pl. fájlverzió, a módosítás dátuma) a **Részletek** lapra is kattinthat, a közlemény Tudásbázis cikkében ismertetett fájlinformációs táblázatok alapján.
5. Kattinthat a **korábbi verziókat** felsoroló lapra is, majd összehasonlíthatja a korábbi fájlverzió adatait az aktuális, frissített fájléval.
### Egyéb információ
#### Köszönetnyilvánítás
A Microsoft [köszönetét](http://go.microsoft.com/fwlink/?linkid=21127) fejezi ki a vásárlók védelmének biztosításában nyújtott segítségért az alábbi szervezet(ek)nek és szakember(ek)nek:
- David Dewey, [IBM ISS X-Force](http://www.iss.net/) és Ryan Smith, [Accuvant](http://www.accuvant.com/) (korábban a [VeriSign iDefense Labs](http://labs.idefense.com/) munkatársa), a jelen közlemény részét képező hatékony védelmi módosításokkal kapcsolatos együttműködésért
#### Microsoft Active Protections Program (MAPP)
Az ügyfelek védelmének növelése érdekében a biztonsági szoftverekkel foglalkozó nagyobb gyártók a Microsoft a havi biztonsági közlemények megjelenése előtt ellátja biztonsági résekkel kapcsolatos információkkal. Így a biztonságiszoftver-gyártók a kapott biztonsági résekkel kapcsolatos információt felhasználhatják ügyfeleik hatásosabb védelmére az olyan biztonsági szoftverek vagy eszközök (például víruskeresők, hálózati behatolásérzékelő rendszerek vagy kiszolgálóalapú behatolásvédelmi rendszerek) frissítése által. A biztonságiszoftver-gyártók által kiadott aktív védelem elérhetőségéről a [Microsoft Active Protections Program (MAPP) Partners](http://www.microsoft.com/security/msrc/mapp/partners.mspx) webhelyén található listán szereplő és a programban részt vevő gyártók aktív védelmi webhelyein tájékozódhat.
#### Terméktámogatás
- Az Amerikai Egyesült Államokban és Kanada területén élő ügyfelek technikai támogatást kérhetnek a [biztonsági támogatás szolgáltatójától](http://go.microsoft.com/fwlink/?linkid=21131) vagy az 1-866-PCSAFETY telefonszámon. A biztonsági frissítésekkel kapcsolatos hívások ingyenesek. Az elérhető támogatási lehetőségekről további információt talál a [Microsoft segítségnyújtással és támogatással foglalkozó webhelyén](http://support.microsoft.com/).
- Más országokban a helyi Microsoft-képviseletek nyújtanak támogatást. A biztonsági frissítésekkel kapcsolatos hívások ingyenesek. A [nemzetközi támogatási webhely](http://go.microsoft.com/fwlink/?linkid=21155) felvilágosítást nyújt arról, támogatási kérdéseivel hogyan fordulhat a Microsofthoz.
#### Felelősséget kizáró nyilatkozat
A Microsoft Tudásbázisban leírtak előzetes bejelentés nélkül változhatnak, és a cikkek tartalmáért a Microsoft nem vállal garanciát. A Microsoft egyben elhárít minden kifejezett és értelemszerű garanciát, beleértve az eladhatóságra és az adott célra való alkalmasságra vonatkozó garanciát is. A Microsoft Corporation vagy annak szállítói semmilyen körülmények között nem tehetők felelőssé közvetlen, közvetett, eseti, ok-okozati vagy különleges kárért (beleértve az elmaradt hasznot is), még akkor sem, ha a Microsoft Corporation vagy szállítói tudatában voltak a kár lehetséges voltának. Egyes államok törvényi szabályozása nem teszi lehetővé a véletlen vagy ok-okozati károkért vállalt felelősség korlátozását vagy kizárását, így ezekben az államokban az ez a felelősségkizárás nincs érvényben.
#### Verziók
- 1.0 verzió (2010. június 8.): Közlemény kiadva.
- 1.1 verzió (2010. június 16.): A Microsoft Office Word 2007 frissítőfájlja nevének javítása a **Biztonsági frissítés telepítése** c. részben. Bővült a GYIK rész is, mely ismerteti, hogy miért ajánlja fel a rendszer a frissítést akkor is, ha a rendszerben nincs érintett szoftver.
*Built at 2014-04-18T01:50:00Z-07:00*
| 68.296769 | 823 | 0.719661 | hun_Latn | 0.999927 |
9a7794744ce66134d6c8b1e2ab0800c79f509c4d | 2,767 | md | Markdown | documents/amazon-lumberyard-user-guide/doc_source/ui-editor-components-layout.md | siagholami/aws-documentation | 2d06ee9011f3192b2ff38c09f04e01f1ea9e0191 | [
"CC-BY-4.0"
] | 5 | 2021-08-13T09:20:58.000Z | 2021-12-16T22:13:54.000Z | documents/amazon-lumberyard-user-guide/doc_source/ui-editor-components-layout.md | siagholami/aws-documentation | 2d06ee9011f3192b2ff38c09f04e01f1ea9e0191 | [
"CC-BY-4.0"
] | null | null | null | documents/amazon-lumberyard-user-guide/doc_source/ui-editor-components-layout.md | siagholami/aws-documentation | 2d06ee9011f3192b2ff38c09f04e01f1ea9e0191 | [
"CC-BY-4.0"
] | null | null | null | # Layout Components<a name="ui-editor-components-layout"></a>
Like other UI components, layout components define the layout properties of your game's interface\. The UI system features four layout components to organize your elements: **LayoutColumn**, **LayoutRow**, **LayoutGrid**, and **LayoutCell**\. You can also nest layout components\.
**Topics**
+ [LayoutColumn](ui-editor-components-layout-column.md)
+ [LayoutRow](ui-editor-components-layout-row.md)
+ [LayoutGrid](ui-editor-components-layout-grid.md)
+ [LayoutCell](ui-editor-components-layout-cell.md)
+ [LayoutFitter](ui-editor-components-layout-fitter.md)
+ [Nesting Layout Components](ui-editor-components-layout-nesting.md)
**LayoutColumn**
Add the **LayoutColumn** component to an element to make it a layout column\. When you add child elements to the layout column, the layout column assigns each child element a layout cell\. The layout column adjusts the size of the layout cells depending on how many child elements you add as well as the values provided by the child elements’ layout cells\.
**LayoutRow**
Add the **LayoutRow** component to an element to make it a layout row\. Like the layout column, the layout row assigns each child elements a layout cell\. The layout row adjusts the size of the layout cells depending on how many child elements you add and the values provided by the child elements' layout cells\.
**LayoutGrid**
Add the **LayoutGrid** component to an element to make it a layout grid\. The layout grid places child elements into a grid\. Unlike the layout row and layout column, however, the layout grid does not use layout cells\. The **LayoutGrid** component's properties determine the size of its children\.
**LayoutCell**
Add the **LayoutCell** component to a layout row or layout column's children to customize how a layout cell's size is determined\. A layout cell is a programmatic concept whose properties define the area of a child element\. Anytime that you add a child element to a layout row or layout column, that child element receives layout cell properties \(not visible in the **UI Editor**\), which determine the size of the child's space\. You can override the layout cell's calculated properties by adding the **LayoutCell** component to the child\. For more information, see [LayoutCell](ui-editor-components-layout-cell.md)\.
**LayoutFitter**
Add the **LayoutFitter** component to an element to make the element resize itself to fit its content\. Use the layout fitter component with other components that provide cell sizing information, such as text, image \(with **ImageType** set to **Fixed**\), or layout components \(cell, row, column, grid\)\. For more information, see [LayoutFitter](ui-editor-components-layout-fitter.md)\. | 106.423077 | 621 | 0.770148 | eng_Latn | 0.994994 |
9a781cf25d76acfc48a920c9b910be0dc045c619 | 1,147 | md | Markdown | includes/data-box-edge-gateway-storage-acct-limits.md | julianosaless/azure-docs.pt-br | 461791547c9cc2b4df751bb3ed881ce57796f1e4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/data-box-edge-gateway-storage-acct-limits.md | julianosaless/azure-docs.pt-br | 461791547c9cc2b4df751bb3ed881ce57796f1e4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/data-box-edge-gateway-storage-acct-limits.md | julianosaless/azure-docs.pt-br | 461791547c9cc2b4df751bb3ed881ce57796f1e4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
author: alkohli
ms.service: databox
ms.topic: include
ms.date: 01/30/2019
ms.author: alkohli
ms.openlocfilehash: a3928ac4caca5247dcacc639698a7a7bb49826a1
ms.sourcegitcommit: 849bb1729b89d075eed579aa36395bf4d29f3bd9
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/28/2020
ms.locfileid: "75467718"
---
Abaixo, são informados os limites do tamanho dos dados que são copiados para a conta de armazenamento. Verifique se os dados carregados por você estão em conformidade com esses limites. Para obter as informações mais atualizadas sobre esses limites, consulte [escalabilidade e metas de desempenho para armazenamento de BLOBs](../articles/storage/blobs/scalability-targets.md) e [metas de desempenho e escalabilidade de arquivos do Azure](../articles/storage/files/storage-files-scale-targets.md).
| Tamanho dos dados copiados para a conta de armazenamento do Azure | Limite padrão |
|---------------------------------------------------------------------|------------------------|
| Blob de páginas e blob de blocos | 500 TB por conta de armazenamento| | 63.722222 | 496 | 0.690497 | por_Latn | 0.973867 |
9a78b44ec8cc31e8746ec6e6fbab13584eb0dad1 | 954 | md | Markdown | plugin-resources/docs/mnemonic/exg.md | hsz/m68kplugin | 669aa70e89a581b13ce8a397540580edd3f6a688 | [
"Apache-2.0"
] | 8 | 2021-05-30T03:04:10.000Z | 2022-03-23T17:46:28.000Z | plugin-resources/docs/mnemonic/exg.md | hsz/m68kplugin | 669aa70e89a581b13ce8a397540580edd3f6a688 | [
"Apache-2.0"
] | 14 | 2020-09-19T10:59:22.000Z | 2021-12-03T10:33:50.000Z | plugin-resources/docs/mnemonic/exg.md | hsz/m68kplugin | 669aa70e89a581b13ce8a397540580edd3f6a688 | [
"Apache-2.0"
] | 2 | 2020-09-19T06:37:49.000Z | 2021-11-16T10:39:36.000Z | # EXG - Exchange registers
## Operation
[Rx] ← [Ry]; [Ry] ← [Rx]
## Syntax
```assembly
EXG Rx,Ry
```
## Sample syntax
```assembly
EXG D3,D4
EXG D2,A0
EXG A7,D5
```
## Attributes
`Size` longword
## Description
Exchange the contents of two registers. The size of the instruction is a longword because the entire 32-bit contents of two registers are exchanged. The instruction permits the exchange of address registers, data registers, and address and data registers.
## Application
One application of `EXG` is to load an address into a data register and then process it using instructions that act on data registers. Then the reverse operation can be used to return the result to the address register. Doing this preserves the original contents of the data register.
## Condition codes
|X|N|Z|V|C|
|--|--|--|--|--|
|-|-|-|-|-|
*From MOTOROLA M68000 FAMILY Programmer's reference manual. Copyright 1992 by Motorola Inc./NXP. Adapted with permission.* | 30.774194 | 284 | 0.737945 | eng_Latn | 0.991168 |
9a7980f2bc00aa301ae9829562d744c246ff14e8 | 3,092 | markdown | Markdown | _posts/2013-09-25-rubymotion-mokumoku-osaka.markdown | znz/blog.n-z.jp | bf28b81ef2f85b80849185b201b2536f7d9a012c | [
"MIT"
] | 1 | 2019-05-05T03:39:00.000Z | 2019-05-05T03:39:00.000Z | _posts/2013-09-25-rubymotion-mokumoku-osaka.markdown | znz/blog.n-z.jp | bf28b81ef2f85b80849185b201b2536f7d9a012c | [
"MIT"
] | 32 | 2018-07-05T16:07:50.000Z | 2022-02-26T12:02:04.000Z | _posts/2013-09-25-rubymotion-mokumoku-osaka.markdown | znz/blog.n-z.jp | bf28b81ef2f85b80849185b201b2536f7d9a012c | [
"MIT"
] | 1 | 2020-03-27T10:12:23.000Z | 2020-03-27T10:12:23.000Z | ---
layout: post
title: "第 3 回 RubyMotion もくもく会 in Osaka に参加した"
date: 2013-09-25 20:43
comments: true
category: blog
tags: event ruby rubymotion
---
第 1 回と第 2 回にも参加した RubyMotion もくもく会 in Osaka の
[第 3 回 RubyMotion もくもく会 in Osaka](http://connpass.com/event/3450/)
に参加してきました。
<!--more-->
OS X アプリの勉強をしようと思って、
とりあえず
`motion create --template=osx Hello`
で生成されたファイルを読んでいたら、
`app/menu.rb`
の
`Italic`
の
`keyEquivalent:`
が
`Bold`
と同じ
`'b'`
になっていたのを見つけて、
他もテキストエディットと見比べていたら
違う部分を見つけたので、
`motion support`
で報告してみました。
```diff
diff --git a/app/menu.rb b/app/menu.rb
index 58b48f8..0da85e1 100644
--- a/app/menu.rb
+++ b/app/menu.rb
@@ -47,7 +47,7 @@ class AppDelegate
fontMenu = createMenu('Font') do
addItemWithTitle('Show Fonts', action: 'orderFrontFontPanel:', keyEquivalent: 't')
addItemWithTitle('Bold', action: 'addFontTrait:', keyEquivalent: 'b')
- addItemWithTitle('Italic', action: 'addFontTrait:', keyEquivalent: 'b')
+ addItemWithTitle('Italic', action: 'addFontTrait:', keyEquivalent: 'i')
addItemWithTitle('Underline', action: 'underline:', keyEquivalent: 'u')
addItem(NSMenuItem.separatorItem)
addItemWithTitle('Bigger', action: 'modifyFont:', keyEquivalent: '+')
@@ -60,9 +60,11 @@ class AppDelegate
addItemWithTitle('Justify', action: 'alignJustified:', keyEquivalent: '')
addItemWithTitle('Align Right', action: 'alignRight:', keyEquivalent: '}')
addItem(NSMenuItem.separatorItem)
- addItemWithTitle('Show Ruler', action: 'toggleRuler:', keyEquivalent: '')
- addItemWithTitle('Copy Ruler', action: 'copyRuler:', keyEquivalent: 'c')
- addItemWithTitle('Paste Ruler', action: 'pasteRuler:', keyEquivalent: 'v')
+ addItemWithTitle('Show Ruler', action: 'toggleRuler:', keyEquivalent: 'r')
+ item = addItemWithTitle('Copy Ruler', action: 'copyRuler:', keyEquivalent: 'c')
+ item.keyEquivalentModifierMask = NSCommandKeyMask|NSControlKeyMask
+ item = addItemWithTitle('Paste Ruler', action: 'pasteRuler:', keyEquivalent: 'v')
+ item.keyEquivalentModifierMask = NSCommandKeyMask|NSControlKeyMask
end
addMenu('Format') do
```
他にはサンプルとして
https://github.com/satococoa/rubymotion-osx-browser
とか
https://github.com/HipByte/RubyMotionSamples
とかをちょっと動かして見たりしていました。
他の人の話としては、
`UICreateCGImageFromIOSurface`
というシンボルで問題が起きて、
最初は
[ZBar](https://github.com/ZBar/ZBar)
というライブラリが疑われていたけど違ったとかいう話とか、
[Reveal.framework が原因で Release ビルドで外せば良い](http://support.revealapp.com/discussions/suggestions/8-reference-to-uicreatecgimagefromiosurface-should-be-removed-for-release-scheme)
という話とか、
東京と Google ハングアウトでつないでみてたとか、
[(1/2) - 第二回 RubyMotion でアプリケーションを作ろう (1) - 実践！RubyMotion - Mobile Touch - モバイル/タブレット開発者およびデザイナー向け情報ポータル](http://mobiletou.ch/2013/09/002-create-application)
で開発中のアプリをみせてもらったりとかがありました。
東京とのハングアウトが終わった後は
[Vagrant入門ガイド](https://gihyo.jp/dp/ebook/2013/978-4-7741-6024-5)
の話とか、
[JAWS FESTA Kansai 2013](http://jfk2013.jaws-ug.jp/)
の話とかもしていました。
最後に次回も東京と日程を合わせるということで
[第 4 回 RubyMotion もくもく会 in Osaka](http://connpass.com/event/3557/)
は 10/23 (水) 19:30 からということになりました。
| 33.247312 | 176 | 0.730918 | yue_Hant | 0.519292 |
9a79a518d7b47929acf3c22da02ad83062b0332b | 5,629 | md | Markdown | libs/beam/README.md | Viasat/PWA-Framework-Speedtest | 7700e2eca3424ed0ed4b915b774d8b359bdf6824 | [
"Apache-2.0"
] | null | null | null | libs/beam/README.md | Viasat/PWA-Framework-Speedtest | 7700e2eca3424ed0ed4b915b774d8b359bdf6824 | [
"Apache-2.0"
] | null | null | null | libs/beam/README.md | Viasat/PWA-Framework-Speedtest | 7700e2eca3424ed0ed4b915b774d8b359bdf6824 | [
"Apache-2.0"
] | 5 | 2021-05-24T16:47:00.000Z | 2021-05-27T22:07:34.000Z | # Beam library
Shared variables like colors and utility functions for beam styles framework.
## Features
This library exposes:
1. CSS custom properties and utility classes
2. Sass variables, utility functions and mixins
3. Js module with all variables grouped in sections (colors, spacings)
## Usage
### How to import
In your es6 file use either:
1. Complete build in css format: `style.css`.
2. Specific parts by importing sass files in your own .scss file or whole `@vst/beam/styles/style.scss` to it (to get access to all mixins, etc.).
3. Importing js variables that provides all variables used in project.
`@vst/beam/styles/vars.module.js` for importing file in es6 and `@vst/beam/styles/vars.js` to get file
Without es6 modules enabled ecosystem (with most likely npm support) mentioned above you can use css directly in html file or `vars-js` file.
### 1.1 Import complete build in your component (any setup with webpack sass-loader):
```js
import '@vst/beam/styles.scss';
const ExampleComponent = () => (
<div class="beam-bg--gray100">
<span class="beam-c--gray900">Dark text in light background</span>
</div>
);
```
### 1.2 Import complete build in simple html/css website:
1. Add inside `<head></head>` section
```html
<link href="complete.css" rel="stylesheet" />
```
And you will get access to all css variables and util classes.
2. Or use a js version in case of specific need (like changing behaviour of app based on breakpoints).
```html
<script src="vars.js"></script>
```
This will give you access to object with all beam framework values in single object at `window.Beam`;
#### 2. Import specific specific part in your own .scss file:
```scss
@use '@vst/beam/theme/dark';
@use '@vst/beam/theme/light';
@use '@vst/beam/utils/colors';
// Sets default to light theme
$colors: map-merge(colors.$common-colors, light.$theme-colors);
@include colors.gen-default-theme-colors($colors);
// Allow switching theme using class
.theme-dark {
@include colors.gen-custom-props(dark.$theme-colors);
@include colors.gen-colors-util-classes(dark.$theme-colors);
}
.theme-light {
@include colors.gen-custom-props(light.$theme-colors);
@include colors.gen-colors-util-classes(light.$theme-colors);
}
```
### Util classes
You can utilise color util classes like `.c-alert400` or `.bg-alert400` (after importing `@vst/beam/utils/colors.scss` or whole `@vst/beam/styles.scss`) and use css custom properties like `var(--c-alert400)`;
```css
.my-bem-secletor {
color: var(--c-alert400);
}
```
### Sass capabilities
1. When you import this lib file in your own `./whole-app.scss` or `./specific-component.scss` you can import @vst/beam scss files and get an access to mixins etc. with: `import '@vst/beam/utils/colors.scss'`.
2. Change default prefixes:
```scss
@use '@vst/beam/theme/dark';
@use '@vst/beam/theme/light';
$your-custom-prefix: 'your-custom-prefix-instead-of-beam-';
@use '@vst/beam/utils/colors' with (
$prefix: 'your-custom-prefix-instead-of-beam-',
$custom-prop-prefix: 'clr',
$class-color-prefix: '.#{$your-custom-prefix}color',
$class-bg-prefix: '.#{$your-custom-prefix}bg--'
)
// Sets default to light theme
$colors: map-merge(colors.$common-colors, light.$theme-colors);
@include colors.gen-default-theme-colors($colors);
// ...
```
### Switching theme
Default file `complete.scss` and `complete.css` exports all themes. To switch between themes see the examples below:
### Using your own .scss file
You can use specific scss file to get colors for specific theme
`@import '@vst/beam/theme/dark.scss';`
and regenerate them at any moment
`@include regen-default-theme-colors($colors)`
see `'@vst/beam/theme/index.scss';` if in doubt.
### CSS. Switch using classes:
`.dark` sets variables to dark theme for current element and all descendents. Light theme is default but you can still set `.light` when you would like to have an alement and it's descendents light (same applies to `.dark`).
# Development
## Compile
1. Use: `npm run beam-compile-all` to get scss compiled to css & js variables (look for commands underneeth in package.json to run just parts of it).
2. Use: `nx build beam` (or use vscode nx console extension to run from gui) to make a publishable package out of compiled output.
## Using module from source code (example for nx monorepo)
Module can be used as published npm package, or directly from source
where you've got hot module reloading on scss change.
Make sure to configure your project's settings:
tsconfig.json (per particular app):
```json
{
"...": "...",
"compilerOptions": {
"...": "...",
"paths": {
"...": "...",
"@vst/beam/*": ["libs/beam/src/*"]
}
},
"...": "..."
}
```
workspace.json (makes styles work for a build task)
```json
"your-app": {
"...": "...",
"architect": {
"build": {
"...": "...",
"options": {
"...": "...",
"styles": ["libs/beam/src/styles/*.scss"],
"stylePreprocessorOptions": {
"includePaths": ["libs/beam/src/styles/"]
}
},
"...": "...",
},
"...": "...",
}
},
```
# Troubleshooting
To double-check if your sass files did not brake you can run `npx sass beam-complete.scss beam-complete.css` to check for any warnings (those should appear while running the app using ng serve as well).
| 30.592391 | 225 | 0.654113 | eng_Latn | 0.938878 |
9a79e01dcec3d588a6d7539f161deb2b78621a4f | 2,019 | md | Markdown | node_modules/@storybook/manager-webpack4/node_modules/dotenv-defaults/README.md | jeffpuzzo/jp-rosa-react-form-wizard | fa565d0dddd5310ed3eb7c31bff4abee870bf266 | [
"MIT"
] | 3 | 2020-04-07T10:39:32.000Z | 2020-04-07T11:34:59.000Z | node_modules/@storybook/manager-webpack4/node_modules/dotenv-defaults/README.md | jeffpuzzo/jp-rosa-react-form-wizard | fa565d0dddd5310ed3eb7c31bff4abee870bf266 | [
"MIT"
] | 7 | 2021-03-10T23:56:31.000Z | 2022-02-27T07:25:13.000Z | node_modules/@storybook/manager-webpack4/node_modules/dotenv-defaults/README.md | jeffpuzzo/jp-rosa-react-form-wizard | fa565d0dddd5310ed3eb7c31bff4abee870bf266 | [
"MIT"
] | 4 | 2020-04-20T17:59:46.000Z | 2020-05-12T18:42:49.000Z | # dotenv-defaults
A dotenv system that supports defaults
### Status
[](https://greenkeeper.io/)
### Installation
Use the following to install this module.
```
npm i dotenv-defaults --save
```
### Usage
This module supports all the features from the original [dotenv](https://www.npmjs.com/package/dotenv) module, so usage should be simple enough:
```
# .env.defaults, safe to commit
HOST=website.com
EMAIL=test@email.com
```
```
# .env, DO NOT COMMIT
HOST=omnionline.us
```
The result
```js
require('dotenv-defaults').config()
// Or you can also load it directly like this
require('dotenv-defaults/config')
console.log(process.env.HOST)
// Outputs: omnionline.us
console.log(process.env.EMAIL)
// Outputs: test@email.com
```
##### TypeScript
Since this module does not provide TypeScript Type Definitions if you try to import it like `import dotenv from "dotenv-defaults"` TypeScript will return an error.
Instead you should load it like this:
```typescript
import "dotenv-defaults/config"
```
##### CLI
You can also call this module directly when using the node executable.
So, for example if you are running a custom script with node and you want to load your environment variables you can do the following `node -r dotenv-defaults/config your-script.js`. (_When using this method, please make sure that you have installed dotenv-defaults with npm or yarn in the same directory_)
### Differences
The only thing to note is that the original module supported an `options` argument in the `config` function.
This module supports that as well, but there is an added `defaults` property that can allow you to define where that file is located. An example is shown below:
```js
// all of these are the default values...
require(`dotenv-defaults`).config({
path: './.env',
encoding: 'utf8',
defaults: './.env.defaults' // This is new
})
```
### License
MIT
| 25.884615 | 306 | 0.737494 | eng_Latn | 0.980101 |
9a7b36b4947bc5765a48389b134923fd080acdef | 2,317 | md | Markdown | graphsage/doc/dlpack_and_dmlc-core.md | Qksidmx/GraphSAGE | a8c97d54b74e6c65eb4e5d764e750d7cc1be4f20 | [
"MIT"
] | 1 | 2022-03-16T08:34:01.000Z | 2022-03-16T08:34:01.000Z | graphsage/doc/dlpack_and_dmlc-core.md | Qksidmx/GraphSAGE | a8c97d54b74e6c65eb4e5d764e750d7cc1be4f20 | [
"MIT"
] | 2 | 2022-03-01T03:44:06.000Z | 2022-03-16T08:54:11.000Z | graphsage/doc/dlpack_and_dmlc-core.md | Qksidmx/GraphSAGE | a8c97d54b74e6c65eb4e5d764e750d7cc1be4f20 | [
"MIT"
] | 1 | 2022-02-28T08:27:29.000Z | 2022-02-28T08:27:29.000Z | <center>dlpack和dmlc-core</center>
### dlpack
dlpack不会实现tensor和op，而是能让不同深度训练框架之间复用tensor和op
dlpack的api很简单，然我们可以放弃关注硬件接口，分配器，专注于最小的数据结构，能支持跨设备的数据存储和展示
枚举：
```
DLDeviceType
DLDataTypeCode
```
Struct：
```
DLDevice
DLDataType
DLTensor
DLManagedTensor
```
例子：
```python
from torch.utils.dlpack import to_dlpack
t = torch.ones((5,5), dtype=torch.float32, device=torch.device('cpu'))
dlp = to_dlpack(t)
from nnabla.utils.dlpack import from_dlpack
arr = from_dlpack(dlp)
```
### ctypes
python可利用ctypes机制来调用c/c++模块，对基本类型的映射有良好的支持，如下举例子：
g++ -fPIC -shared great_module.c -o great_module.so
python前加星号，用于将列表或字典等参数拆解成单个参数
### dmlc-core
是dmlc的基础库，文档较少，文档只有param.h，即解析参数的库
可以通过引用头文件的形式来利用这些库
直接翻源码，有几个主目录：
```
include 基础库
src/data 解析数据的迭代器
src/io 处理数据和文件流的io库
test 单元测试目录，因文档欠缺，可以通过这个目录熟悉基础库基本用法
tracker 提交任务的python脚本，可以提交任务至k8s/yarn/mesos/ssh 等
```
include文件夹下的文件列举如下：
```
any.h 可以包装容纳任意数据结构的库
array_view.h 用于指向array的只读的数据结构
blockingconcurrentqueue.h 高效的阻塞并发队列，使用信号量（semaphore）实现
concurrency.h 提供线程安全的数据结构
concurrentqueue.h 高效的多生产者、多消费者的无锁队列
filesystem.h 操作文件的库
input_split_shuffle.h 随机拆分输入数据的库
io.h 定义数据结构的序列化接口
json.h 轻量级的json读写库用于c++数据结构，支持stl组件/结构
logging.h 日志库，使用glog实现，若无glog，使用自己的底层实现
lua.h 用于和lua与torch交互的头文件，作者有陈天奇
memory_io.h 用于序列化数据结构至内存中
optional.h 用于存放optional类数据的容器
parameter.h 参数的设置和检查库
recordio.h 打包二进制数据为拆分的格式，方便在二进制下交换数据，例如纯二进制数据和Protobuf
strtonum.h str to float和str to double的高效实现
threadediter.h 基于线程的迭代器，实现通用的基于线程的流水线例如预获取或者预计算；作者是陈天奇
thread_group.h 提供线程池功能，有原始的同步，以及生命周期管理
thread_local.h 可插拔的线程本地存储
timer.h 计时器；作者是陈天奇
```
src/data 目录文件枚举如下：
```
basic_row_iter.h 用于加载数据到内存的基于行的迭代器
csv_parser.h 以迭代的形式解析csv文件
disk_row_iter.h 基于行的迭代器，用于缓存数据到磁盘
libfm_parser.h 解析libfm格式的迭代器
libsvm_parser.h 解析libsvm格式的迭代器
parquet_parser.h 解析parquet格式的迭代器
row_block.h 用于支持row block数据结构
text_parser.h 解析文本格式的迭代器
```
src/io 目录文件枚举如下：
```
azure_filesys.cc 读写azure云上的文件
cached_input_split.h 用于缓存数据至磁盘，并后续从磁盘读取
filesys.cc 提供便利文件夹和删除文件夹的方法
hdfs_filesys.cc 读写hdfs上的文件
indexed_recordio_split.cc 用于拆分已索引的recordio文件
input_split_base.h 从多个文件来拆分输入流的基类
line_split.h 基于行的从多个文件拆分输入流
local_filesys.cc 读写本地的文件
recordio_split.h 基于recordio文件的从多个文件拆分输入流
s3_filesys.cc 读写亚马逊云上的文件
single_file_split.h TODO
single_threaded_input_split.h 用于调试目的
threaded_input_split.h InputSplit的多线程版本，有一个prefetch的线程会先进行预获取
uri_spec.h TODO
```
| 19.308333 | 70 | 0.833405 | yue_Hant | 0.74374 |
9a7b9807d57b194d7c053f6974d72bb24b709b5d | 28 | md | Markdown | README.md | Bardli/piano-with-userdefind-keys | 058e104c22cb9d0bc2fa90405987fd2e7ce330ef | [
"MIT"
] | null | null | null | README.md | Bardli/piano-with-userdefind-keys | 058e104c22cb9d0bc2fa90405987fd2e7ce330ef | [
"MIT"
] | null | null | null | README.md | Bardli/piano-with-userdefind-keys | 058e104c22cb9d0bc2fa90405987fd2e7ce330ef | [
"MIT"
] | null | null | null | # piano-with-userdefind-keys | 28 | 28 | 0.821429 | eng_Latn | 0.52636 |
9a7bb1190fe045d570e0dc6c22a1ad510a407492 | 3,738 | md | Markdown | stable/knative/charts/eventing/README.md | ppc64le/ISV-charts | 8098e1927bc1bcf3a67bd30a3989dc42e9854f3a | [
"Apache-2.0"
] | 5 | 2018-03-06T15:25:19.000Z | 2020-01-08T15:32:35.000Z | stable/knative/charts/eventing/README.md | ppc64le/ISV-charts | 8098e1927bc1bcf3a67bd30a3989dc42e9854f3a | [
"Apache-2.0"
] | 12 | 2018-03-15T19:13:40.000Z | 2019-07-17T06:46:15.000Z | stable/knative/charts/eventing/README.md | ppc64le/ISV-charts | 8098e1927bc1bcf3a67bd30a3989dc42e9854f3a | [
"Apache-2.0"
] | 10 | 2018-06-14T09:11:06.000Z | 2019-12-03T08:22:05.000Z | # Knative Eventing
This chart installs Knative components for Eventing.
[Knative](https://github.com/knative/) extends Kubernetes to provide a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center.
## Introduction
This is a helm chart for installing Knative Eventing which provides loosely coupled services that can be developed and deployed on independently on Kubernetes. Visit [knative eventing](https://github.com/knative/eventing/blob/master/README.md) for more information.
## Chart Details
In its default configuration, this chart will create the following Kubernetes resources:
- Internal Services:
- in-memory-channel-controller, in-memory-channel-dispatcher, eventing-controller, webhook
- eventing-controller-admin
- Knative Eventing Pods:
- Deployments: in-memory-channel-controller, in-memory-channel-dispatcher, eventing-controller, webhook
- Custom Resource Definitions:
- subscriptions.eventing.knative.dev
- channels.eventing.knative.dev
## Prerequisites
- Requires kubectl v1.10+.
- Knative requires a Kubernetes cluster v1.10 or newer with the
[MutatingAdmissionWebhook admission controller](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#how-do-i-turn-on-an-admission-controller)
- Istio - You should have Istio installed on your Kubernetes cluster. If you do not have it installed already you can do so by following the steps mentioned here https://github.com/IBM/charts/tree/master/stable/ibm-istio
enabled.
## Installing the Chart
Please ensure that you have reviewed the [prerequisites](#prerequisites).
To install the chart using helm cli:
Knative eventing provides you with an option to choose between Kafka or In memory provisioner.
For in-memory-provisioner in [Values.yaml](./values.yaml) set:
```bash
in-memory-provisioner:
enabled: true
kafka-provisioner:
enabled: false
```
For kafka-provisioner in [Values.yaml](./values.yaml) set:
```bash
in-memory-provisioner:
enabled: false
kafka-provisioner:
enabled: true
```
Install eventing:
```bash
$ helm install ./knative/eventing [--tls]
```
### Configuration
If your installing Knative Eventing with a Kafka provisioner you must change `bootstrapServers: " "` to point towards an existing Kafka Broker in the [Values.yaml](./charts/kafka-provisioner/values.yaml).
[Values.yaml](./values.yaml) outlines the configuration options that are supported by this chart.
### Verifying the Chart
To verify all Pods are running, try:
```bash
$ helm status <my-release> [--tls]
```
## Uninstalling the Chart
To uninstall/delete the deployment:
```bash
$ helm delete <my-release> --purge [--tls]
```
To uninstall/delete the crds:
```bash
$ kubectl delete --filename knative/all-crds.yaml
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
## Limitations
You must use `knative-eventing` namespace to install Knative eventing.
## Documentation
Documentation of the Knative eventing system can be found on the [Knative Eventing Docs](https://github.com/knative/eventing/blob/master/README.md).
To learn more about Knative in general, see the [Overview](https://github.com/knative/docs/blob/master/README.md).
# Support
If you're a developer, operator, or contributor trying to use Knative, the
following resources are available for you:
- [Knative Users](https://groups.google.com/forum/#!forum/knative-users)
- [Knative Developers](https://groups.google.com/forum/#!forum/knative-dev)
For contributors to Knative, we also have [Knative Slack](https://slack.knative.dev).
| 34.934579 | 272 | 0.771268 | eng_Latn | 0.939205 |
9a7bc0638b191041314203ea4fa00ed5c394a6aa | 3,225 | md | Markdown | client/docs/Docker.md | hedlx/dockerless | d3ccd86a769dc1beb892f2dc335c24ce8720d7d5 | [
"MIT"
] | null | null | null | client/docs/Docker.md | hedlx/dockerless | d3ccd86a769dc1beb892f2dc335c24ce8720d7d5 | [
"MIT"
] | null | null | null | client/docs/Docker.md | hedlx/dockerless | d3ccd86a769dc1beb892f2dc335c24ce8720d7d5 | [
"MIT"
] | null | null | null | # Docker
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**Image** | Pointer to **string** | | [optional]
**Container** | Pointer to **string** | | [optional]
**ContainerId** | Pointer to **string** | | [optional]
**Status** | **string** | |
## Methods
### NewDocker
`func NewDocker(status string, ) *Docker`
NewDocker instantiates a new Docker object
This constructor will assign default values to properties that have it defined,
and makes sure properties required by API are set, but the set of arguments
will change when the set of required properties is changed
### NewDockerWithDefaults
`func NewDockerWithDefaults() *Docker`
NewDockerWithDefaults instantiates a new Docker object
This constructor will only assign default values to properties that have it defined,
but it doesn't guarantee that properties required by API are set
### GetImage
`func (o *Docker) GetImage() string`
GetImage returns the Image field if non-nil, zero value otherwise.
### GetImageOk
`func (o *Docker) GetImageOk() (*string, bool)`
GetImageOk returns a tuple with the Image field if it's non-nil, zero value otherwise
and a boolean to check if the value has been set.
### SetImage
`func (o *Docker) SetImage(v string)`
SetImage sets Image field to given value.
### HasImage
`func (o *Docker) HasImage() bool`
HasImage returns a boolean if a field has been set.
### GetContainer
`func (o *Docker) GetContainer() string`
GetContainer returns the Container field if non-nil, zero value otherwise.
### GetContainerOk
`func (o *Docker) GetContainerOk() (*string, bool)`
GetContainerOk returns a tuple with the Container field if it's non-nil, zero value otherwise
and a boolean to check if the value has been set.
### SetContainer
`func (o *Docker) SetContainer(v string)`
SetContainer sets Container field to given value.
### HasContainer
`func (o *Docker) HasContainer() bool`
HasContainer returns a boolean if a field has been set.
### GetContainerId
`func (o *Docker) GetContainerId() string`
GetContainerId returns the ContainerId field if non-nil, zero value otherwise.
### GetContainerIdOk
`func (o *Docker) GetContainerIdOk() (*string, bool)`
GetContainerIdOk returns a tuple with the ContainerId field if it's non-nil, zero value otherwise
and a boolean to check if the value has been set.
### SetContainerId
`func (o *Docker) SetContainerId(v string)`
SetContainerId sets ContainerId field to given value.
### HasContainerId
`func (o *Docker) HasContainerId() bool`
HasContainerId returns a boolean if a field has been set.
### GetStatus
`func (o *Docker) GetStatus() string`
GetStatus returns the Status field if non-nil, zero value otherwise.
### GetStatusOk
`func (o *Docker) GetStatusOk() (*string, bool)`
GetStatusOk returns a tuple with the Status field if it's non-nil, zero value otherwise
and a boolean to check if the value has been set.
### SetStatus
`func (o *Docker) SetStatus(v string)`
SetStatus sets Status field to given value.
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
| 24.807692 | 161 | 0.724341 | eng_Latn | 0.863373 |
9a7bcc47b510a2af785cb3ee29527856c58690dd | 34 | md | Markdown | README.md | jba-tm/django_cookbook | bc2ff295eac33c117ae68e648d7747fcdaa4e97d | [
"Apache-2.0"
] | null | null | null | README.md | jba-tm/django_cookbook | bc2ff295eac33c117ae68e648d7747fcdaa4e97d | [
"Apache-2.0"
] | null | null | null | README.md | jba-tm/django_cookbook | bc2ff295eac33c117ae68e648d7747fcdaa4e97d | [
"Apache-2.0"
] | null | null | null | # django_cookbook
Django Cookbook
| 11.333333 | 17 | 0.852941 | hun_Latn | 0.189364 |
9a7c31e156328776c1470ecffd5f8f2b7bf30f22 | 63 | md | Markdown | test/fixtures/multiple-collections/src/echo.md | yanneves/metalsmith-collections-archive | 0d71b86197280a58027c0ceca77c8ac7e574a0d9 | [
"MIT"
] | null | null | null | test/fixtures/multiple-collections/src/echo.md | yanneves/metalsmith-collections-archive | 0d71b86197280a58027c0ceca77c8ac7e574a0d9 | [
"MIT"
] | 1 | 2018-03-16T20:58:58.000Z | 2018-03-16T23:10:42.000Z | test/fixtures/multiple-collections/src/echo.md | yanneves/metalsmith-collections-archive | 0d71b86197280a58027c0ceca77c8ac7e574a0d9 | [
"MIT"
] | null | null | null | ---
title: Echo
date: 2016-08-08
collection: studies
---
echo
| 7.875 | 19 | 0.666667 | eng_Latn | 0.388642 |
9a7c40d03105b9a04566630156b9202b247b2ea8 | 1,486 | md | Markdown | README.md | leohaskell/todo-list | 6bc1fe4ba38315d7b2ab1038c8b92753320ce138 | [
"MIT"
] | null | null | null | README.md | leohaskell/todo-list | 6bc1fe4ba38315d7b2ab1038c8b92753320ce138 | [
"MIT"
] | null | null | null | README.md | leohaskell/todo-list | 6bc1fe4ba38315d7b2ab1038c8b92753320ce138 | [
"MIT"
] | null | null | null | # todo-list
A simple RESTful application written during a Haskell workshop
## Progress
[Day 1](https://github.com/leohaskell/todo-list/releases/tag/end-of-day1)
[Day 2](https://github.com/leohaskell/todo-list/releases/tag/end-of-day2)
[Day 3](https://github.com/leohaskell/todo-list/releases/tag/end-of-day3)
## Setup
If you haven't already, [install stack](https://haskell-lang.org/get-started)
## Running
The following command starts the application on port 3000:
```sh
stack build && stack exec todo-list
```
## Application
We'll manage tasks (in-memory) that have a title, a description and current status (todo and done).
REST API:
* GET /task - return all tasks
* GET /task/:id - return a task
* POST /task - create a new task and return it
* PUT /task/:id - update a task and return it
* DELETE /task/:id - remove a task and return it
The returned tasks are in the following JSON format:
```json
{
"tid":0,
"title":"Haskell Workshop",
"description":"Run a Haskell Workshop",
"status":"todo"
}
```
The same format (omitting *tid*) is used for `POST` and `PUT` methods, but the field *status* is optional when `POST`ing and all fields are optional when `PUT`ting.
--------------------------
Currently, handlers for all methods mentioned above are implemented.
They can be tested with [`sh test.sh`](./test.sh) (you'll need [jq](https://stedolan.github.io/jq/) to run them)
Possible extensions:
* place the tasks in different todo lists
* add users
| 28.576923 | 164 | 0.703903 | eng_Latn | 0.951568 |
9a7cd846ea12c6d99af324bb28722b060b6dd538 | 2,174 | md | Markdown | README.md | timgates42/ractive | c5be019e288a806713aaed719ae44ae80e29f946 | [
"MIT"
] | null | null | null | README.md | timgates42/ractive | c5be019e288a806713aaed719ae44ae80e29f946 | [
"MIT"
] | null | null | null | README.md | timgates42/ractive | c5be019e288a806713aaed719ae44ae80e29f946 | [
"MIT"
] | null | null | null | <p align="center"><img src ="https://avatars1.githubusercontent.com/u/4751469?v=3&s=100"></p>
# Ractive.js - Next-generation DOM manipulation
[](https://gitter.im/ractivejs/ractive) [](https://www.npmjs.com/package/ractive) [](https://david-dm.org/RactiveJS/Ractive) [](https://travis-ci.org/ractivejs/ractive) [](https://coveralls.io/github/ractivejs/ractive?branch=dev) [](https://www.jsdelivr.com/package/npm/ractive) [](https://www.npmjs.com/package/ractive) [](https://twitter.com/ractivejs)
## What is Ractive.js?
It's a JavaScript library for building reactive user interfaces in a way that doesn't force you into a particular framework's way of thinking. It takes a radically different approach to DOM manipulation - one that saves both you and the browser unnecessary work.
Features include...
- Data-binding, with a beautiful declarative syntax.
- Event handling that doesn't make you tear your hair out.
- Flexible and performant animations and transitions.
- And much more!
## Getting started
To get a feel for how it will make your life as a web developer easier, head over to the documentation at [ractive.js.org](https://ractive.js.org/) or get a quick hands-on with [interactive tutorials](https://ractive.js.org/tutorials/hello-world/).
## Contributing
All forms of help are welcome! Please read [CONTRIBUTING.md](CONTRIBUTING.md) to learn how to contribute.
## License
Copyright (c) 2012-17 Rich Harris and contributors. Released under an [MIT license](LICENSE.md).
| 72.466667 | 1,031 | 0.765869 | eng_Latn | 0.560554 |
9a7d4d15bc84cd105209d0dc913af5aa24a585b5 | 3,772 | md | Markdown | README-ja.md | excavador/aws-s3-proxy | 70f490bda70fdb95a4f246c6cf44b2255d41bb62 | [
"MIT"
] | 267 | 2016-02-20T04:00:07.000Z | 2022-03-31T17:19:11.000Z | README-ja.md | excavador/aws-s3-proxy | 70f490bda70fdb95a4f246c6cf44b2255d41bb62 | [
"MIT"
] | 47 | 2016-04-21T01:45:54.000Z | 2021-11-29T12:31:29.000Z | README-ja.md | packethost/aws-s3-proxy | ca386f26d80949b2b1a0bb212479b6cfb984058f | [
"MIT"
] | 127 | 2016-04-18T07:02:30.000Z | 2022-03-31T14:52:24.000Z | # Basic 認証も可能な AWS S3 へのリバースプロキシ
[](https://hub.docker.com/r/pottava/s3-proxy/)
## 概要
指定した S3 バケット にリバースプロキシする Web サービスです。
API 経由でアクセスするため、バケットに静的 Web サイトホスティングの設定は不要です。
オプションでフロントに Basic 認証がかけられます。
http://this-proxy.com/access/ -> s3://bucket/access/index.html
## 使い方
### 1. 環境変数をセットします
環境変数 | 説明 | 必須 | 初期値
------------------------- | ----------------------------------------------- | ------ | ---
AWS_S3_BUCKET | プロキシ先の S3 バケット | * |
AWS_S3_KEY_PREFIX | S3 オブジェクトにプリフィクス文字列があるなら指定 | | -
AWS_REGION | バケットの存在する AWS リージョン | | us-east-1
AWS_ACCESS_KEY_ID | API を使うための AWS アクセスキー | | EC2 インスタンスロール
AWS_SECRET_ACCESS_KEY | API を使うための AWS シークレットキー | | EC2 インスタンスロール
AWS_API_ENDPOINT | API 接続先エンドポイント（通常指定する必要なし） | | -
INDEX_DOCUMENT | インデックスドキュメントの名前 | | index.html
DIRECTORY_LISTINGS | / で終わる URL の場合、ファイル一覧を返す | | false
DIRECTORY_LISTINGS_FORMAT | `html` がセットされていたらファイル一覧を HTML で返す | | -
HTTP_CACHE_CONTROL | S3 の `Cache-Control` 属性を上書きして返します | | S3 オブジェクト属性値
HTTP_EXPIRES | S3 の `Expires` 属性を上書きして返します | | S3 オブジェクト属性値
BASIC_AUTH_USER | Basic 認証をかけるなら、その `ユーザ名` | | -
BASIC_AUTH_PASS | Basic 認証をかけるなら、その `パスワード` | | -
SSL_CERT_PATH | TLS を有効にしたいなら、その `cert.pem` へのパス | | -
SSL_KEY_PATH | TLS を有効にしたいなら、その `key.pem` へのパス | | -
CORS_ALLOW_ORIGIN | CORS を有効にしたいなら、リソースへのアクセスを許可する URI | | -
CORS_ALLOW_METHODS | CORS を有効にしたいなら、許可する [HTTP request methods](https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html)のカンマ区切りのリスト | | -
CORS_ALLOW_HEADERS | CORS を有効にしたいなら、サポートするヘッダーのカンマ区切りのリスト | | -
CORS_MAX_AGE | CORS における preflight リクエスト結果のキャッシュ上限時間(秒) | | 600
APP_PORT | このサービスが待機する `ポート番号` | | 80
ACCESS_LOG | 標準出力へアクセスログを送る | | false
STRIP_PATH | 指定した Prefix を S3 のパスから削除 | | -
CONTENT_ENCODING | リクエストが許可していればレスポンスを圧縮します | | true
HEALTHCHECK_PATH | 指定すると Basic 認証設定の有無などに依らず 200 OK を返します | | -
GET_ALL_PAGES_IN_DIR | 指定ディレクトリの全てのオブジェクトを返す | | false
MAX_IDLE_CONNECTIONS | S3 への利用が終わったコネクションの最大保持数 | | 150
IDLE_CONNECTION_TIMEOUT | S3 への接続タイムアウト | | 10
DISABLE_COMPRESSION | S3 との間の Content-Encoding を無効にします | | true
INSECURE_TLS | TLS 証明書の正当性チェックをスキップします | | false
### 2. アプリを起動します
`docker run -d -p 8080:80 -e AWS_REGION -e AWS_S3_BUCKET pottava/s3-proxy`
* Basic 認証をつけるなら:
`docker run -d -p 8080:80 -e AWS_REGION -e AWS_S3_BUCKET -e BASIC_AUTH_USER -e BASIC_AUTH_PASS pottava/s3-proxy`
* TLS を有効にしたいなら:
`docker run -d -p 8080:80 -e AWS_REGION -e AWS_S3_BUCKET -e SSL_CERT_PATH -e SSL_KEY_PATH pottava/s3-proxy`
* CORS を有効にしたいなら:
`docker run -d -p 8080:80 -e CORS_ALLOW_ORIGIN -e CORS_ALLOW_METHODS -e CORS_ALLOW_HEADERS -e CORS_MAX_AGE pottava/s3-proxy`
* docker-compose.yml として使うなら:
```
proxy:
image: pottava/s3-proxy
ports:
- 8080:80
environment:
- AWS_REGION=ap-northeast-1
- AWS_ACCESS_KEY_ID
- AWS_SECRET_ACCESS_KEY
- AWS_S3_BUCKET
- BASIC_AUTH_USER=admin
- BASIC_AUTH_PASS=password
- ACCESS_LOG=true
container_name: proxy
```
| 44.904762 | 143 | 0.566808 | yue_Hant | 0.936405 |
9a7e12dd42a71ef6aea6d2512edce821260766dd | 1,977 | md | Markdown | refined-storage/wiki/Pattern Grid.md | bdunogier/website | b632c3775ec2803a210b2a7e8a74dc1434a31051 | [
"MIT"
] | 1 | 2021-12-13T14:28:44.000Z | 2021-12-13T14:28:44.000Z | refined-storage/wiki/Pattern Grid.md | bdunogier/website | b632c3775ec2803a210b2a7e8a74dc1434a31051 | [
"MIT"
] | 10 | 2021-03-22T12:56:12.000Z | 2021-12-13T12:41:34.000Z | refined-storage/wiki/Pattern Grid.md | bdunogier/website | b632c3775ec2803a210b2a7e8a74dc1434a31051 | [
"MIT"
] | 3 | 2020-10-28T23:01:40.000Z | 2021-11-29T10:45:04.000Z | The Pattern Grid is the same as a regular [[Grid]], but also allows for the creation of [[Pattern|patterns]].
## Mode
By default, the Pattern Grid creates regular crafting [[Pattern|patterns]].
To create processing [[Pattern|patterns]], toggle the "processing" checkbox.
## Oredict (Refined Storage 1.6.x or lower)
To create oredict sensitive [[Pattern|patterns]], toggle the "oredict" checkbox.
## Allowed tags (Refined Storage 1.7.x or higher)
The allowed tags system in Refined Storage allows the player to decide which items or fluids can be used as alternatives when the specified item or fluid isn't found in the storage network.
These tags are retrieved from [Minecraft's tag system](https://minecraft.gamepedia.com/Tag). You can specify the allowed tags in the Pattern Grid.
To define valid alternatives for an item or fluid, use CTRL + click on the input slot and specify the allowed tags that can be used during autocrafting. Items or fluids from that tag are then marked as valid alternatives if the original item or fluid can't be found in the storage network.
You can also define valid alternatives by clicking on the item or fluid and then clicking on "Alternatives".
## Modifying a pattern
You can re-insert a [[Pattern]] in the output slot to modify and (possibly) override it.
## Recipe transferring
The Pattern Grid integrates with [JEI (Just Enough Items)](https://minecraft.curseforge.com/projects/jei) so the player can use recipe transferring.
You don't necessarily need the actual items in your storage network to create a [[Pattern]] for it.
Refined Storage will notify you when you have a [[Pattern]] for an item configured when transferring a recipe.
## Manual input/output configuration
Click an item or fluid in the slots to configure the [[Pattern]].
Click on the item or fluid to change the quantity.
Use CTRL + click to modify the allowed tags for the input slot (MC 1.14.4 and above).
Use shift to clear the slot.
[[@Recoloring]] | 50.692308 | 289 | 0.771371 | eng_Latn | 0.99822 |
9a7f05022202c3ed9d379bc9b06929cea31ea04e | 1,240 | md | Markdown | pycorrector/seq2seq_attention/README.md | johnson7788/pycorrector | 3ac324e2a546b5dcd64425d5467ad8789d8f87b7 | [
"Apache-2.0"
] | null | null | null | pycorrector/seq2seq_attention/README.md | johnson7788/pycorrector | 3ac324e2a546b5dcd64425d5467ad8789d8f87b7 | [
"Apache-2.0"
] | null | null | null | pycorrector/seq2seq_attention/README.md | johnson7788/pycorrector | 3ac324e2a546b5dcd64425d5467ad8789d8f87b7 | [
"Apache-2.0"
] | null | null | null | # Seq2seq Attention Model
## Features
* 基于Attention机制的sequence to sequence模型
* BahdanauAttention
* 训练加速tricks：dataset bucketing, prefetching, token-based batching, gradients accumulation
* beam search
## Usage
### Requirements
* pip安装依赖包
```
tensorflow>=2.0.0 # tensorflow-gpu>=2.0.0
```
# 修改配置文件config.py，修改原始文件读取的位置
注意函数
```buildoutcfg
def parse_file(path, line_start, line_end):
```
### Preprocess
- 生成训练和测试数据，拆分比例9：1
```
cd seq2seq_attention
python preprocess.py
```
生成文件在目录output/test.txt 和output/train.txt 下，逐个字分隔
例如:
```
# train.txt:
如 服 装 ， 若 有 一 个 很 流 行 的 形 式 ， 人 们 就 赶 快 地 追 求 。\t如 服 装 ， 若 有 一 个 很 流 行 的 样 式 ， 人 们 就 赶 快 地 追 求 。
```
- 正式数据集下载, 数据量比较大，
1. download from https://pan.baidu.com/s/1BkDru60nQXaDVLRSr7ktfA 密码:m6fg [130W sentence pair，215MB], put data to `seq2seq_attention/output` folder.
2. run `preprocess.py`. 生成output下的trg和src文件
```
python preprocess.py
```
### Train
```
python train.py
```
### Infer
```
python infer.py
```
### Result
```
input: 少先队员应该给老人让坐 output: 少先队员应该给老人让座
input: 由我起开始做 output: 由我开始做
```
 | 17.971014 | 149 | 0.657258 | yue_Hant | 0.365016 |
9a7f233f3821a58eb754ad393acbdf6002f1681f | 98 | md | Markdown | scaffold/assets/templates/mail-notification/readme.md | pakitovic/executor-mail | 295f1f805a022605e4be4d19fee9386add51a749 | [
"MIT"
] | 1 | 2019-06-25T16:15:09.000Z | 2019-06-25T16:15:09.000Z | scaffold/assets/templates/mail-notification/readme.md | pakitovic/executor-mail | 295f1f805a022605e4be4d19fee9386add51a749 | [
"MIT"
] | 5 | 2018-01-07T21:59:54.000Z | 2020-07-29T10:56:54.000Z | scaffold/assets/templates/mail-notification/readme.md | pakitovic/executor-mail | 295f1f805a022605e4be4d19fee9386add51a749 | [
"MIT"
] | 2 | 2019-06-26T22:39:57.000Z | 2020-05-12T18:34:13.000Z | This is an example template that you can use with both the email executor and the email notifier.
| 49 | 97 | 0.806122 | eng_Latn | 1.000009 |
9a7faf27d0b7211b32c59ac72d376e51fa00381e | 45 | md | Markdown | README.md | Hello-Bye/ZLMoveTaxisTableView | f4d6d56a85d1b78bbac759fb4255a9bd0eb5270c | [
"MIT"
] | null | null | null | README.md | Hello-Bye/ZLMoveTaxisTableView | f4d6d56a85d1b78bbac759fb4255a9bd0eb5270c | [
"MIT"
] | null | null | null | README.md | Hello-Bye/ZLMoveTaxisTableView | f4d6d56a85d1b78bbac759fb4255a9bd0eb5270c | [
"MIT"
] | null | null | null | # ZLMoveTaxisTableView
可长按拖动cell排序的tableView
| 15 | 22 | 0.911111 | kor_Hang | 0.586983 |
9a7fd4090bf320b9c9ba99a4b5f588ce1a0938fa | 41,755 | md | Markdown | articles/cost-management-billing/manage/ea-portal-get-started.md | ialeksander1/azure-docs.pt-br | d5a7a2c2d4a31282f49bd1e35036cb1939911974 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cost-management-billing/manage/ea-portal-get-started.md | ialeksander1/azure-docs.pt-br | d5a7a2c2d4a31282f49bd1e35036cb1939911974 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cost-management-billing/manage/ea-portal-get-started.md | ialeksander1/azure-docs.pt-br | d5a7a2c2d4a31282f49bd1e35036cb1939911974 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Introdução ao Azure Enterprise Portal
description: Este artigo explica como os clientes do Azure EA (Contrato Enterprise do Azure) usam o Azure Enterprise Portal.
author: bandersmsft
ms.author: banders
ms.date: 04/01/2020
ms.topic: conceptual
ms.service: cost-management-billing
ms.reviewer: boalcsva
ms.openlocfilehash: da63960b312bde6ae8aafb659ef08ef2f52600cc
ms.sourcegitcommit: 3c318f6c2a46e0d062a725d88cc8eb2d3fa2f96a
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/02/2020
ms.locfileid: "80586294"
---
# <a name="get-started-with-the-azure-enterprise-portal"></a>Introdução ao Azure Enterprise Portal
Este artigo ajuda os clientes diretos e indiretos do Azure EA (Contrato Enterprise do Azure) a começar a usar o [Azure Enterprise Portal](https://ea.azure.com). Obtenha informações básicas sobre:
- A estrutura do Azure Enterprise Portal.
- Funções usadas no Azure Enterprise Portal.
- Criação de assinatura.
- Análise de custos no Azure Enterprise Portal e no portal do Azure.
Veja este vídeo para assistir a uma sessão de integração completa do Azure Enterprise Portal:
> [!VIDEO https://www.youtube.com/embed/OiZ1GdBpo-I]
## <a name="azure-enterprise-portal-hierarchy"></a>Hierarquia do Azure Enterprise Portal
A hierarquia do Azure Enterprise Portal consiste em:
- **Azure Enterprise Portal** – um portal de gerenciamento online que ajuda você a gerenciar os custos dos serviços de EA do Azure. Você pode:
- Criar uma hierarquia de EA do Azure com departamentos, contas e assinaturas.
- Reconciliar os custos de seus serviços consumidos, baixar relatórios de uso e exibir listas de preços.
- Criar chaves de API para seu registro.
- Os **departamentos** ajudam a segmentar os custos em agrupamentos lógicos. Os departamentos permitem que você defina um orçamento ou uma cota no nível do departamento.
- As **contas** são unidades organizacionais no Azure Enterprise Portal. Você pode usar as contas para gerenciar assinaturas e acessar relatórios.
- As **assinaturas** são a menor unidade no Azure Enterprise Portal. Elas são contêineres para os serviços do Azure gerenciados pelo administrador de serviços.
O diagrama a seguir ilustra as hierarquias simples do EA do Azure.
## <a name="enterprise-user-roles"></a>Funções de usuário corporativo
As seguintes funções de usuário administrativas fazem parte do seu Registro Enterprise:
- Administrador corporativo
- Administrador de departamento
- Proprietário da conta
- Administrador de serviço
- Contato de notificação
As funções funcionam em dois portais diferentes para concluir as tarefas. Você usa o [Azure Enterprise Portal](https://ea.azure.com) para gerenciar a cobrança e os custos e o [portal do Azure](https://portal.azure.com) para gerenciar serviços do Azure.
As funções de usuário são associadas a uma conta de usuário. Para validar a autenticidade do usuário, cada usuário deve ter uma conta Microsoft, corporativa ou de estudante válida. Verifique se cada conta está associada a um endereço de email monitorado ativamente. As notificações de conta são enviadas para o endereço de email.
Ao configurar usuários, você pode atribuir várias contas à função Administrador corporativo. No entanto, apenas uma conta pode conter a função de proprietário da conta. Além disso, você pode atribuir as funções administrador corporativo e proprietário da conta a uma conta.
### <a name="enterprise-administrator"></a>Administrador corporativo
Os usuários com essa função têm o nível mais alto de acesso. Eles podem:
- Gerenciar contas e proprietários da conta.
- Gerenciar outros administradores corporativos.
- Gerenciar administradores de departamento.
- Gerenciar contatos de notificação.
- Exibir o uso em todas as contas.
- Exibir encargos não cobrados em todas as contas.
Você pode ter vários administradores corporativos em um Registro Enterprise. Você pode permitir acesso somente leitura a administradores corporativos. Todos eles herdam a função de administrador do departamento.
### <a name="department-administrator"></a>Administrador de departamento
Os usuários com essa função podem:
- Criar e gerenciar departamentos.
- Criar proprietários da conta.
- Exibir detalhes de uso dos departamentos que eles gerenciam.
- Exibir custos, se tiverem as permissões necessárias.
Você pode ter vários administradores de departamento para cada Registro Enterprise.
Você pode conceder acesso somente leitura aos administradores de departamento ao editar ou criar um administrador de departamento. Defina a opção somente leitura como **Sim**.
### <a name="account-owner"></a>Proprietário da conta
Os usuários com essa função podem:
- Criar e gerenciar assinaturas.
- Gerenciar administradores de serviços.
- Exibir o uso de assinaturas.
Cada conta requer uma conta Microsoft, corporativa ou de estudante, exclusiva. Para obter mais informações sobre as funções administrativas do Azure Enterprise Portal, confira [Entendendo as funções administrativas do Contrato Enterprise do Azure](understand-ea-roles.md).
### <a name="service-administrator"></a>Administrador de serviço
A função administrador de serviços tem permissões para gerenciar serviços no portal do Azure e atribuir usuários à função de coadministrador.
### <a name="notification-contact"></a>Contato de notificação
O contato de notificação pode receber notificações de uso relacionadas ao registro.
## <a name="activate-your-enrollment"></a>Ative seu registro
Para ativar o serviço, o administrador corporativo inicial abre o [Azure Enterprise Portal](https://ea.azure.com) e entra usando o endereço de email do email de convite.
Se você for configurado como o administrador corporativo, não precisará receber o email de ativação. Acesse o [Azure Enterprise Portal](https://ea.azure.com) e entre com o endereço de email e a senha da conta Microsoft, corporativa ou de estudante.
Se você tiver mais de um registro, escolha um para ativar. Por padrão, somente os registros ativos são mostrados. Para exibir o histórico de registros, desmarque a opção **Ativo** no canto superior direito do Azure Enterprise Portal.
Em **Registro**, o status mostra **Ativo**.
Somente administradores corporativos do Azure existentes podem criar outros administradores corporativos.
### <a name="create-another-enterprise-administrator"></a>Criar outro administrador corporativo
Para adicionar outro administrador corporativo:
1. Entre no [Azure Enterprise Portal](https://ea.azure.com).
1. Acesse **Gerenciar** > **Detalhes do Registro**.
1. Selecione **+ Adicionar Administrador** na parte superior à direita.
Verifique se você tem o endereço de email do usuário e o método de autenticação preferencial, por exemplo, uma conta Microsoft, corporativa ou de estudante.
Se você não for o administrador corporativo, entre em contato com um administrador corporativo para solicitar que ele o adicione a um registro. Depois que for adicionado a um registro, você receberá um email de ativação.
Se o administrador corporativo não puder ajudá-lo, crie uma [solicitação de suporte no Azure Enterprise Portal](https://support.microsoft.com/supportrequestform/cf791efa-485b-95a3-6fad-3daf9cd4027c). Forneça as seguintes informações:
- Número de registro
- Endereço de email para adicionar e tipo de autenticação (conta Microsoft, corporativa ou de estudante)
- Aprovação de email de um administrador corporativo existente
- Se o administrador corporativo existente não estiver disponível, entre em contato com seu parceiro ou consultor de software para solicitar que ele altere os detalhes de contato por meio da ferramenta VLSC (Centro de Serviços de Licenciamento por Volume da Microsoft).
Para obter mais informações sobre as funções administrativas empresariais, confira [Entendendo as funções administrativas do Contrato Enterprise no Azure](understand-ea-roles.md).
## <a name="create-an-azure-enterprise-department"></a>Criar um departamento do Azure Enterprise
Administradores corporativos e administradores de departamento usam departamentos para organizar e relatar os serviços e o uso do Azure Enterprise por departamento e centro de custo. O administrador corporativo é capaz de:
- Adicionar ou remover departamentos.
- Associar uma conta a um departamento.
- Criar administradores de departamento.
- Permitir que administradores de departamento exibam preços e custos.
Um administrador de departamento pode adicionar novas contas aos próprios departamentos. Pode também remover contas desses departamentos, mas não do registro.
Para adicionar um departamento:
1. Entre no Azure Enterprise Portal.
1. No painel esquerdo, selecione **Gerenciar**.
1. Selecione a guia **Departamento** e, em seguida, selecione **+ Adicionar Departamento**.
1. Insira as informações.
O nome do departamento é o único campo obrigatório. Ele precisa ter, pelo menos, três caracteres.
1. Quando concluir, selecione **Adicionar**.
## <a name="add-a-department-administrator"></a>Adicionar um administrador de departamento
Depois que um departamento é criado, o administrador corporativo pode adicionar administradores de departamento e associar cada um deles a um departamento. Os administradores de departamento podem executar as seguintes ações para seus departamentos:
- Criar outros administradores de departamento
- Exibir e editar propriedades do departamento, tais como o nome ou o centro de custo
- Adicionar contas
- Remover contas
- Baixar detalhes de uso
- Exibir o uso mensal e os encargos <sup>1</sup>
> <sup>1</sup> Um administrador corporativo deve conceder essas permissões. Se você tiver recebido permissão para exibir o uso mensal e os encargos do departamento mas não puder vê-los, entre em contato com seu parceiro.
### <a name="to-add-a-department-administrator"></a>Para adicionar um administrador de departamento
Como um administrador corporativo:
1. Entre no Azure Enterprise Portal.
1. No painel esquerdo, selecione **Gerenciar**.
1. Selecione a guia **Departamento** e, em seguida, selecione o departamento.
1. Clique em **+ Adicionar Administrador** e adicione as informações necessárias.
1. Para acesso somente leitura, defina a opção **Somente Leitura** como **Sim** e, em seguida, selecione **Adicionar**.
### <a name="to-set-read-only-access"></a>Para definir o acesso somente leitura
Você pode permitir acesso somente leitura aos administradores de departamento.
- Ao criar um administrador de departamento, defina a opção somente leitura como **Sim**.
- Para editar um administrador do departamento existente:
1. Selecione um departamento e, em seguida, selecione o símbolo de lápis ao lado do **Administrador do Departamento** que você deseja editar.
1. Defina a opção somente leitura como **Sim** e, em seguida, selecione **Salvar**.
Os administradores corporativos obtêm permissões de administrador do departamento automaticamente.
## <a name="add-an-account"></a>Adicionar uma conta
A estrutura das contas e das assinaturas afeta o modo como elas são administradas e como elas aparecem em suas faturas e relatórios. Exemplos de estruturas organizacionais típicas incluem divisões de negócios, equipes funcionais e localizações geográficas.
Para adicionar uma conta:
1. No Azure Enterprise Portal, selecione **Gerenciar** na área de navegação à esquerda.
1. Selecione a guia **Conta**. Na página **Conta**, selecione **+Adicionar Conta**.
1. Selecione um departamento ou deixe-o como não atribuído e, em seguida, selecione o tipo de autenticação desejado.
1. Digite um nome amigável para identificar a conta no relatório.
1. Insira o endereço de **Email do Proprietário da Conta** para associar à nova conta.
1. Confirme o endereço de email e, em seguida, selecione **Adicionar**.
Para adicionar outra conta, selecione **Adicionar Outra Conta** ou **Adicionar** no canto inferior direito da barra de ferramentas à esquerda.
Para confirmar a propriedade da conta:
1. Entre no Azure Enterprise Portal.
1. Exiba o status.
O status deve mudar de **Pendente** para **Data de Início/Término**. A Data de Início/Término é a data em que o usuário se conectou pela primeira vez e a data de término do contrato.
1. Quando a mensagem de **Aviso** aparecer, o proprietário de conta precisará selecionar **Continuar** para ativar a conta na primeira vez que entrar no Azure Enterprise Portal.
## <a name="change-account-owner"></a>Alterar proprietário da conta
Os administradores corporativos podem usar o Azure Enterprise Portal para transferir a propriedade da conta de assinatura em um registro. A ação move todas as assinaturas de uma conta de usuário de origem para uma conta de usuário de destino.
Esteja atento a essas informações importantes ao transferir contas:
- Você pode fazer essas transferências:
- De uma conta corporativa ou de estudante para outra conta corporativa ou de estudante.
- De uma conta Microsoft para uma conta corporativa ou de estudante.
- De uma conta Microsoft para outra conta Microsoft.
A conta de destino deve ser uma conta válida do Azure Commerce para ser um destino válido para transferências. Para novas contas, você será solicitado a criar uma conta do Azure Commerce ao entrar no Azure Enterprise Portal. Para contas existentes, você deve primeiro criar uma nova assinatura do Azure antes que a conta seja considerada qualificada.
- Você não pode fazer uma transferência de uma conta corporativa ou de estudante para uma conta Microsoft.
- Quando você conclui uma transferência de assinatura, a Microsoft atualiza o proprietário da conta.
Entenda estas políticas de RBAC (controle de acesso baseado em função):
- Quando você executa transferências de assinatura entre duas IDs organizacionais no mesmo locatário, as políticas de RBAC e as funções de administrador de serviços e de coadministrador existentes são preservadas.
- Outras transferências de assinatura resultam na perda de suas políticas de RBAC e das atribuições de função.
- Políticas e funções de administrador não são transferidas entre diretórios diferentes. Os administradores de serviços são atualizados para o proprietário da conta de destino.
Antes de alterar um proprietário da conta:
1. No Azure Enterprise Portal exiba a guia **Conta** e identifique a conta de origem. A conta de origem precisa estar ativa.
1. Identifique a conta de destino e verifique se ela está ativa.
Para transferir a propriedade da conta para todas as assinaturas:
1. Entre no Azure Enterprise Portal.
1. Na área de navegação esquerda, selecione **Gerenciar**.
1. Selecione a guia **Conta** e passe o mouse sobre uma conta.
1. Selecione o ícone de mudar o proprietário da conta à direita. O ícone se assemelha a uma pessoa.
1. Escolha uma conta qualificada e, em seguida, selecione **Avançar**.
1. Confirme a transferência e selecione **Enviar**.
Para transferir a propriedade da conta para uma assinatura única:
1. Entre no Azure Enterprise Portal.
1. Na área de navegação esquerda, selecione **Gerenciar**.
1. Selecione a guia **Conta** e passe o mouse sobre uma conta.
1. Selecione o ícone de transferir assinaturas à direita. O ícone se assemelha a uma página.
1. Escolha uma assinatura qualificada e selecione **Avançar**.
1. Confirme a transferência e, em seguida, selecione **Enviar**.
Assista a este vídeo para ver o gerenciamento de usuários do Azure Enterprise Portal:
> [!VIDEO https://www.youtube.com/embed/621jVkvmwm8]
## <a name="create-a-subscription"></a>Criar uma assinatura
Os proprietários da conta podem exibir e gerenciar assinaturas. Você pode usar assinaturas para dar acesso a ambientes e projetos de desenvolvimento às equipes de sua organização. Por exemplo, teste, produção, desenvolvimento e preparo.
Ao criar assinaturas diferentes para cada ambiente de aplicativo, você ajuda a proteger cada ambiente.
- Você também pode atribuir uma conta de administrador de serviços diferente para cada assinatura.
- Você pode associar assinaturas a qualquer número de serviços.
- O proprietário da conta cria assinaturas e atribui uma conta de administrador de serviços a cada assinatura na conta dele.
### <a name="add-a-subscription"></a>Adicionar uma assinatura
Use as informações a seguir para adicionar uma assinatura.
Na primeira vez que você adicionar uma assinatura à conta, será solicitado que você aceite o MOSA (Contrato de Assinatura do Microsoft Online) e um plano de taxas. Embora eles não sejam aplicáveis a clientes do Contrato Enterprise, o MOSA e o plano de taxas são necessários para criar sua assinatura. O aditamento de registro do Contrato Enterprise do Microsoft Azure substitui os itens acima e a sua relação contratual não é alterada. Quando solicitado, selecione a caixa que indica que você aceita os termos.
_Microsoft Azure Enterprise_ é o nome padrão quando uma assinatura é criada. Você pode alterar o nome para diferenciá-lo das outras assinaturas em seu registro e garantir que seja reconhecido em relatórios no nível corporativo.
Para adicionar uma assinatura:
1. No Azure Enterprise Portal, entre na conta.
1. Selecione a guia **Admin** e, em seguida, selecione **Assinatura** na parte superior da página.
1. Verifique se você está conectado como o proprietário da conta em questão.
1. Selecione **+ Adicionar Assinatura** e, em seguida, selecione **Comprar**.
Na primeira vez que você adicionar uma assinatura a uma conta, deverá fornecer suas informações de contato. Ao adicionar assinaturas adicionais, suas informações de contato serão adicionadas para você.
1. Selecione **Assinaturas** e, em seguida, selecione a assinatura que você criou.
1. Selecione **Editar Detalhes da Assinatura**.
1. Edite o **Nome da Assinatura** e o **Administrador de Serviços** e, em seguida, selecione a marca de seleção.
O nome da assinatura aparece nos relatórios. É o nome do projeto associado à assinatura no portal de desenvolvimento.
Novas assinaturas podem levar até 24 horas para aparecer na lista de assinaturas. Depois de ter criado uma assinatura, você pode:
- [Editar detalhes da assinatura](https://account.azure.com/Subscriptions)
- [Gerenciar chaves de assinatura](https://portal.azure.com/#home)
## <a name="transfer-an-enterprise-subscription-to-a-pay-as-you-go-subscription"></a>Transferir uma assinatura do Enterprise para uma assinatura Pagamento Conforme o Uso
Para transferir uma assinatura Enterprise para uma assinatura individual com as tarifas de Pagamento Conforme o Uso, você precisa criar uma solicitação de suporte no Azure Enterprise Portal. Para criar uma solicitação de suporte, selecione **+ Nova solicitação de suporte** na área **Ajuda e Suporte**.
## <a name="associate-an-existing-account-with-your-pay-as-you-go-subscription"></a>Associar uma conta existente à sua assinatura de Pagamento Conforme o Uso
Se já tiver uma conta do Microsoft Azure existente no portal do Azure, insira a conta Microsoft, corporativa ou de estudante pertinente para associá-la ao seu registro do Contrato Enterprise.
### <a name="associate-an-existing-account"></a>Associar uma conta existente
1. No Azure Enterprise Portal, selecione **Gerenciar**.
1. Selecione a guia **Conta**.
1. Selecione **+Adicionar uma conta**.
1. Insira a conta corporativa ou de estudante ou a conta Microsoft associada à conta do Azure existente.
1. Confirme a conta associada à conta do Azure existente.
1. Forneça um nome que você gostaria de usar para identificar esta conta nos relatórios.
1. Selecione **Adicionar**.
1. Para adicionar outra conta, selecione novamente a opção **+Adicionar uma conta** ou retorne à página inicial escolhendo o botão **Admin**.
1. Se você exibir a página **Conta**, a conta recém-adicionada será exibida com o status **Pendente**.
### <a name="confirm-account-ownership"></a>Confirmar a propriedade da conta
1. Entre na conta de email associada à conta corporativa ou de estudante ou à conta Microsoft que você forneceu.
1. Abra a notificação de email intitulada _"Convite para ativar a conta no serviço do Microsoft Azure de licenciamento por volume da Microsoft"_ .
1. No convite, selecione o link **Entrar no Microsoft Azure Enterprise Portal**.
1. Selecione **Entrar**.
1. Insira a conta Microsoft, corporativa ou de estudante e a senha para entrar e confirmar a propriedade da conta.
### <a name="azure-marketplace"></a>Azure Marketplace
Embora a maioria das assinaturas possa converter do ambiente de Pagamento Conforme o Uso para o Contrato Enterprise do Azure, os serviços do Azure Marketplace não fazem isso. Para ter um modo de exibição único de todas as assinaturas e preços, recomendamos adicionar os serviços do Azure Marketplace ao Azure Enterprise Portal.
1. Entre no Azure Enterprise Portal.
1. Selecione **Gerenciar** na área de navegação à esquerda.
1. Selecione a **EnrollmentTab**.
1. Exiba a seção **Detalhes do Registro**.
1. À direita do campo Azure Marketplace, selecione o ícone de lápis para habilitar. Clique em **Salvar**.
O proprietário da conta agora pode comprar serviços do Azure Marketplace que antes pertenciam à assinatura de Pagamento Conforme o Uso.
Depois que as novas assinaturas do Azure Marketplace forem ativadas no registro do EA do Azure, cancele os serviços do Azure Marketplace que foram criados no ambiente de Pagamento Conforme o Uso. Esta etapa é crítica para que suas assinaturas do Azure Marketplace não entrem em um estado inadequado quando seu meio de pagamento do Pagamento Conforme o Uso expirar.
### <a name="msdn"></a>MSDN
As assinaturas da MSDN são automaticamente convertidas em Desenvolvimento/Teste da MSDN e a oferta do EA do Azure perderá os créditos monetários existentes.
### <a name="azure-in-open"></a>Azure via Open
Se você associar uma assinatura do Azure via Open com um Contrato Enterprise, perderá os créditos não consumidos do Azure via Open. Portanto, recomendamos que você consuma todo o crédito da assinatura Azure via Open antes de adicionar a conta ao seu Contrato Enterprise.
### <a name="accounts-with-support-subscriptions"></a>Contas com assinaturas de suporte
Se o Contrato Enterprise não tiver uma assinatura de suporte e você adicionar uma conta existente com uma assinatura de suporte no Azure Enterprise Portal, sua assinatura de suporte do MOSA não será transferida automaticamente. Você precisará comprar novamente uma assinatura de suporte no EA do Azure durante o período de carência: até o final do mês subsequente.
## <a name="view-usage-summary-and-download-reports"></a>Exibir resumo de uso e baixar relatórios
Os administradores corporativos podem exibir um resumo dos dados de uso, do compromisso monetário consumido e das cobranças associadas ao uso adicional no Azure Enterprise Portal. As cobranças são apresentadas no nível do resumo em todas as contas e assinaturas.
Para exibir o uso detalhado de contas específicas, baixe o relatório de detalhes de uso:
1. Entre no Azure Enterprise Portal.
1. Selecione **Relatórios**.
1. Selecione a guia **Baixar Uso**.
1. Na lista de relatórios, selecione **Baixar** para o relatório mensal que deseja obter.
> [!NOTE]
> O relatório de detalhe de uso não inclui as tributos incidentes.
>
> Pode haver uma latência de até oito horas do momento em que o uso foi feito até ser refletido no relatório.
Para exibir os relatórios e os grafos de resumo de uso:
1. Entre no Azure Enterprise Portal.
1. Selecione um período de compromisso.
Para alterar o intervalo de datas do **Resumo de Uso**, você pode alternar de **M** (mensal) para **C** (personalizado) no canto superior direito da página e, em seguida, inserir as datas de início e término personalizadas.
1. Para exibir detalhes adicionais, selecione um período ou mês no gráfico.
- O gráfico mostra o uso mês a mês com um detalhamento do uso utilizado, os encargos adicionais de serviço, os encargos cobrados separadamente e os encargos do Azure Marketplace.
- Para o mês selecionado, use os campos abaixo do gráfico para filtrar por departamentos, contas e assinaturas.
- Você pode alternar entre **Cobrar por Serviços** e **Cobrar por Hierarquia**.
- Veja os detalhes de **Serviço do Azure**, dos **Encargos Cobrados Separadamente** e do **Azure Marketplace** expandindo as seções pertinentes.
Assista a este vídeo para ver como exibir o uso:
> [!VIDEO https://www.youtube.com/embed/Cv2IZ9QCn9E]
### <a name="download-csv-reports"></a>Baixar relatórios CSV
Os administradores corporativos usam a página de Download de Relatório Mensal para baixar vários relatórios como arquivos CSV:
- Saldo e preço
- Detalhes de uso
- Encargos do Azure Marketplace
- Tabela de preços
Para baixar relatórios:
1. No Azure Enterprise Portal, selecione **Relatórios**.
2. Selecione **Baixar Uso** na parte superior da página.
3. Selecione **Baixar** ao lado do relatório do mês.
> [!NOTE]
> Pode haver uma latência de até cinco dias entre a data em que o uso ocorreu e o momento em que ele é mostrado nos relatórios.
>
> Os usuários que baixarem arquivos CSV com o Safari para Excel poderão encontrar erros de formatação. Para evitar erros, abra o arquivo usando um editor de texto.
Assista a este vídeo para ver como baixar informações de uso:
> [!VIDEO https://www.youtube.com/embed/eY797htT1qg]
### <a name="advanced-report-download"></a>Download do relatório avançado
Você pode usar o download de relatório avançado para obter relatórios que abrangem intervalos de datas ou contas específicas. O arquivo de saída está no formato CSV para acomodar grandes conjuntos de registros.
1. No Azure Enterprise Portal, selecione **Download de Relatório Avançado**.
1. Selecione um intervalo de datas e as contas apropriadas.
1. Escolha **Solicitar dados de uso**.
1. Selecione o botão **Atualizar** até que o status do relatório seja atualizado para **Baixar**.
1. Baixe o relatório.
### <a name="download-usage-reports-and-billing-information-for-a-prior-enrollment"></a>Baixar relatórios de uso e informações de cobrança de um registro anterior
Você pode baixar relatórios de uso e informações de cobrança para um registro anterior depois que uma transferência de registro tiver sido feita. Os relatórios históricos estão disponíveis no Azure Enterprise Portal e no gerenciamento de custos.
O Azure Enterprise Portal filtra os registros inativos, deixando-os fora da exibição. Você precisará desmarcar a caixa de **Ativo** para exibir registros transferidos inativos.
## <a name="azure-ea-term-glossary"></a>Glossário de termos do EA do Azure
- **Conta**: uma unidade organizacional no Azure Enterprise Portal. Ela é usada para administrar assinaturas e para relatórios.
- **Proprietário da conta**: a pessoa que gerencia assinaturas e administradores de serviço no Azure. Ela pode exibir dados de uso nessa conta e suas assinaturas associadas.
- **Assinatura de aditamento**: uma assinatura coincidente ou de um ano sob o aditamento do registro.
- **Compromisso**: compromisso de um valor monetário anual para serviços do Azure a uma tarifa de compromisso reduzida para uso em relação a esse pagamento antecipado.
- **Administrador de departamento**: a pessoa que gerencia departamentos, cria contas e proprietários de contas, exibe detalhes de uso dos departamentos que gerencia e pode exibir custos quando permissões forem concedidas.
- **Número de registro**: um identificador exclusivo fornecido pela Microsoft para identificar o registro específico associado a um Contrato Enterprise.
- **Administrador corporativo**: a pessoa que gerencia departamentos, proprietários de departamentos, contas e proprietários de contas no Azure. Ela tem a capacidade de gerenciar administradores corporativos e exibir dados de uso, quantidades cobradas e encargos não cobrados em todas as contas e assinaturas associadas ao registro corporativo.
- **Contrato Enterprise**: um contrato de licenciamento da Microsoft para clientes com compras centralizadas que desejam padronizar toda a organização com a tecnologia da Microsoft e manter uma infraestrutura de tecnologia da informação com um padrão de software da Microsoft.
- **Registro do contrato Enterprise**: um registro no programa de Contrato Enterprise que fornece produtos da Microsoft em volume com tarifas reduzidas.
- **Conta Microsoft**: um serviço online que permite que sites participantes autentiquem um usuário com um conjunto de credenciais.
- **Aditamento do Registro do Microsoft Azure Enterprise (aditamento do registro)** : um aditamento assinado por uma empresa que fornece acesso ao Azure como parte de seu Registro Enterprise.
- **Azure Enterprise Portal**: o portal usado por nossos clientes empresariais para gerenciar suas contas do Azure e as assinaturas relacionadas.
- **Quantidade de recursos consumidos**: a quantidade de um serviço individual do Azure utilizado em um mês.
- **Administrador de serviços**: a pessoa que acessa e gerencia assinaturas e projetos de desenvolvimento no Azure Enterprise Portal.
- **Assinatura**: representa uma assinatura do Azure Enterprise Portal e é um contêiner de serviços do Azure gerenciados pelo mesmo administrador de serviços.
- **Conta corporativa ou de estudante**: para organizações que configuraram o Active Directory com federação para a nuvem e todas as contas estão em um locatário.
### <a name="enrollment-statuses"></a>Status de registro
- **Pendente**: o administrador do registro precisa entrar no Azure Enterprise Portal. Depois de conectado, o registro mudará para o status Ativo.
- **Ativa**: o registro está Ativo e as contas e assinaturas podem ser criadas no Azure Enterprise Portal. O registro permanecerá ativo até a data de término do Contrato Enterprise.
- **Termo estendido indefinido**: o status de termo estendido indefinido ocorre após a data de término do Contrato Enterprise. Ele permite que os clientes do EA do Azure que optaram pelo período estendido continuem a usar os serviços do Azure indefinidamente no final do Contrato Enterprise.
Antes que o registro do EA do Azure atinja a data de término do Contrato Enterprise, o administrador do registro deve decidir dentre as seguintes opções:
- Renovar o registro adicionando um compromisso monetário adicional.
- Transferir para um novo registro.
- Migrar para o MOSP (Programa de Assinatura do Microsoft Online).
- Confirmar a desabilitação de todos os serviços associados ao registro.
- **Expirado**: o cliente do EA do Azure é recusado do período estendido e o registro de EA do Azure atingiu a data de término do Contrato Enterprise. O registro expirará e todos os serviços associados serão desabilitados.
- **Transferidos**: registros em que todos os serviços e contas associados foram transferidos para um novo registro são exibidos com o status Transferidos.
>[!NOTE]
> Os registros não são transferidos automaticamente se um novo número de registro é gerado na renovação. Você deve incluir o número de registro anterior na sua documentação de renovação para facilitar uma transferência automática.
## <a name="get-started-on-azure-ea---faq"></a>Introdução às perguntas frequentes do EA do Azure
Esta seção fornece detalhes sobre as perguntas típicas feitas pelos clientes durante o processo de integração.
### <a name="can-i-associate-my-existing-azure-account-to-azure-ea-enrollment"></a>Posso associar minha conta existente do Azure ao registro do EA do Azure?
Sim. Todas as assinaturas do Azure das quais você é o proprietário da conta serão convertidas para o Contrato Enterprise. Estão incluídas assinaturas que usam crédito mensal, como Visual Studio, AzurePass, MPN, BizSpark e muito mais. Você perderá o crédito mensal ao converter essas assinaturas.
### <a name="i-accidentally-associated-my-existing-azure-account-with-azure-ea-enrollment-as-a-result-i-lost-my-monthly-credit-can-i-get-my-monthly-credit-back"></a>Associei acidentalmente minha conta do Azure existente ao registro EA do Azure. Como resultado, perdi meu crédito mensal. Posso ter meu crédito mensal de volta?
Se você entrar como um proprietário da conta do EA do Azure com as mesmas credenciais da sua Assinatura do Visual Studio, poderá recuperar seu benefício individual do Azure da Assinatura do Visual Studio executando uma das seguintes ações:
- Exclua o proprietário da conta do Azure Enterprise Portal, depois de remover ou mover as assinaturas do Azure associadas. Em seguida, inscreva-se novamente para os benefícios individuais do Azure para o Visual Studio.
- Exclua o assinante do Visual Studio do site de administração no VLSC e atribua novamente a assinatura a uma conta com credenciais diferentes desta vez. Em seguida, inscreva-se novamente para os benefícios individuais do Azure para o Visual Studio.
### <a name="what-type-of-subscription-should-i-create"></a>Que tipo de assinatura devo criar?
O Azure Enterprise Portal oferece dois tipos de assinaturas para clientes empresariais:
- Microsoft Azure Enterprise, que é ideal para:
- Utilização em qualquer tipo de produção
- Melhores preços com base no gasto da infraestrutura
Para obter mais informações, [entre em contato com o departamento de vendas do Azure](https://azure.microsoft.com/pricing/enterprise-agreement/).
- Desenvolvimento/Teste Enterprise, que é ideal para:
- Todas as cargas de trabalho de desenvolvimento/teste da equipe
- Cargas de trabalho de desenvolvimento/teste individual, de média a pesada
- Acesso a imagens especiais do MSDN e taxas de serviço preferenciais
Para obter mais informações, confira [oferta Desenvolvimento/Teste Enterprise](https://azure.microsoft.com/offers/ms-azr-0148p/).
### <a name="is-it-possible-to-transfer-subscription-ownership-to-another-account"></a>É possível transferir a propriedade de assinatura para outra conta?
Sim, você pode transferir a propriedade de assinatura para uma conta diferente. Por exemplo, se uma Conta A tiver três assinaturas, o administrador corporativo poderá transferir uma assinatura para a Conta B, uma para a Conta C e outra para a Conta D ou pode transferir todas as assinaturas para a Conta E.
Para transferir assinaturas:
1. No Azure Enterprise Portal, selecione **Gerenciar** > **Conta**.
1. Passe o mouse sobre **Conta** na extrema direita para ver as opções **Transferir Propriedade** (ícone de pessoa) e **Transferir Assinatura** (ícone de lista). Essas opções só ficam visíveis para contas ativas.
### <a name="my-subscription-name-is-the-same-as-the-offer-name-should-i-change-the-subscription-name-to-something-meaningful-to-my-organization"></a>O nome da minha assinatura é o mesmo que o nome da oferta. Devo alterar o nome da assinatura para algo significativo para minha organização?
Quando você cria uma assinatura, o nome usa como padrão o tipo de oferta que você escolhe. Recomendamos alterar o nome da assinatura para algo que facilite o rastreamento da assinatura.
Para alterar o nome:
1. Entre em [https://account.windowsazure.com](https://account.windowsazure.com).
1. Selecione a lista de assinaturas.
1. Selecione a assinatura que deseja editar.
1. Selecione o ícone **Gerenciar Assinatura**.
1. Edite os detalhes da assinatura.
### <a name="how-can-i-track-costs-incurred-by-a-cost-center"></a>Como faço para acompanhar os custos incorridos por um centro de custo?
Para acompanhar o custo por centro de custo, você precisa definir o centro de custo em um dos seguintes níveis:
- department
- Conta
- Subscription
Dependendo daquilo que precisa, você poderá usar o mesmo centro de custo para acompanhar o uso e os custos associados a um centro de custo específico.
Por exemplo, para acompanhar os custos de um projeto especial em que vários departamentos estão envolvidos, pode ser interessante definir o centro de custo no nível de uma assinatura para controlar o uso e os custos.
Você não pode definir um centro de custo no nível de serviço. Caso você queira controlar o uso no nível de serviço, você pode usar o recurso _Marca_ disponível no nível de serviço.
### <a name="how-do-i-track-usage-and-spend-by-different-departments-in-my-organization"></a>Como faço para acompanhar o uso e o gasto pelos diversos departamentos da organização?
Você pode criar quantos departamentos forem necessários em seu registro do EA do Azure. Para acompanhar o uso corretamente, não compartilhe assinaturas entre departamentos.
Depois de criar departamentos e assinaturas, você poderá ver os dados no relatório de uso. Essas informações podem ajudá-lo a acompanhar o uso e gerenciar custos e gastos no nível do departamento.
Você também pode acessar os dados de uso por meio da API de relatórios. Para obter informações detalhadas e o código de exemplo, confira as [APIs REST do Azure Enterprise](https://docs.microsoft.com/azure/cost-management-billing/manage/ea-portal-rest-apis).
### <a name="can-i-set-a-spending-quota-and-get-alerts-as-i-approach-my-limit"></a>Posso definir uma cota de gastos e receber alertas à medida que me aproximar do meu limite?
Você pode definir uma cota de gastos no nível do departamento e o sistema o notificará automaticamente quando seus limites de gastos atingirem 50%, 75%, 90% e 100% da cota definida.
Para definir sua cota de gastos, selecione um departamento e, em seguida, selecione o ícone Editar. Depois de editar os detalhes do limite de gastos, selecione **Salvar**.
### <a name="i-used-resource-groups-to-implement-rbac-and-track-usage-how-can-i-view-the-associated-usage-details"></a>Usei grupos de recursos para implementar o RBAC e acompanhar o uso. Como faço para exibir os detalhes de uso associados?
Se você usar _grupos de recursos_ e _marcas_, essas informações serão rastreadas no nível de serviço e você poderá acessá-las no arquivo detalhado de uso (CSV) para download. Confira a opção [baixar o relatório de uso](https://ea.azure.com/report/downloadusage) no Azure Enterprise Portal.
Você também pode acessar o uso por meio da API. Para obter informações detalhadas e o código de exemplo, confira as [APIs REST do Azure Enterprise](https://docs.microsoft.com/azure/cost-management-billing/manage/ea-portal-rest-apis).
> [!NOTE]
> Você só pode aplicar marcas em recursos com suporte a operações do Azure Resource Manager. Se você tiver criado uma máquina virtual, uma rede virtual ou um armazenamento por meio do modelo de implantação clássica (como por meio do portal clássico), não poderá aplicar uma marcação a esse recurso. Para dar suporte à marcação, implante esses recursos novamente por meio do Resource Manager. Todos os outros recursos oferecem suporte à marcação.
### <a name="can-i-perform-analyses-using-power-bi"></a>Posso executar análises usando o Power BI?
Sim. Com o pacote de conteúdo do Microsoft Azure Enterprise para Power BI, você pode:
- Importar e analisar rapidamente o consumo do Azure para seu Registro Enterprise.
- Descobrir qual departamento, conta ou assinatura consumiu a maior parte do uso.
- Saber qual serviço sua organização usou mais.
- Acompanhar as tendências de gastos e uso.
Para usar o Power BI:
1. Acesse o site do Power BI.
1. Entre com uma conta corporativa ou de estudante válida.
A conta corporativa ou de estudante pode ser a mesma ou uma diferente da usada para acessar o registro pelo Azure Enterprise Portal.
1. No painel de serviços, selecione o bloco Microsoft Azure Enterprise e selecione **Conectar**.
1. Na tela **Conectar-se ao Azure Enterprise**, insira:
- URL do ambiente do Azure: [https://ea.azure.com](https://ea.azure.com)
- Número de meses: entre 1 e 36
- Número de registro: o número de seu registro
1. Selecione **Avançar**.
1. Insira a Chave de API na caixa da **Chave de Conta**.
Você pode encontrar a chave de API no Azure Enterprise Portal. Procure na guia **Baixar Uso** e, em seguida, selecione **Chave de acesso da API**. Copie e cole a chave na caixa **Chave de Conta** no Power BI.
Dependendo do tamanho do conjunto de dados, pode levar entre cinco e 30 minutos para que os dados sejam carregados no Power BI.
O relatório do Power BI está disponível para clientes diretos, indiretos e parceiros do EA do Azure que podem exibir informações de cobrança.
## <a name="next-steps"></a>Próximas etapas
- Os administradores do Azure Enterprise Portal devem ler [Administração do Azure Enterprise Portal](ea-portal-administration.md) para aprender sobre tarefas administrativas comuns.
- Se você precisar de ajuda com a solução de problemas do Azure Enterprise Portal, confira [Solucionar problemas de acesso ao Azure Enterprise Portal](ea-portal-troubleshoot.md).
- Para obter um guia de integração do EA do Azure, confira [Guia de integração do EA do Azure (PDF)](https://ea.azure.com/api/v3Help/v2AzureEAOnboardingGuide).
| 68.115824 | 510 | 0.790492 | por_Latn | 0.999679 |
9a7fd9b8db0d954f515ac4887a5c61192e27708b | 11,859 | md | Markdown | content/posts/ArchitecturePatternsDesignPatternsCodingRules/index.md | Crashedmind/MyTechieBits.com | 5fd1ef1f6fb8bc949515cafe0ae26df922a5eb10 | [
"MIT"
] | null | null | null | content/posts/ArchitecturePatternsDesignPatternsCodingRules/index.md | Crashedmind/MyTechieBits.com | 5fd1ef1f6fb8bc949515cafe0ae26df922a5eb10 | [
"MIT"
] | null | null | null | content/posts/ArchitecturePatternsDesignPatternsCodingRules/index.md | Crashedmind/MyTechieBits.com | 5fd1ef1f6fb8bc949515cafe0ae26df922a5eb10 | [
"MIT"
] | null | null | null | ---
path: "/ArchitecturePatternsDesignPatternsCodingRules"
cover: "../ArchitecturePatternsDesignPatternsCodingRules/Security.jpg"
date: "2019-07-19"
title: "Principles and Patterns For Secure Software"
tags: ['Architecture Pattern', 'Architecture', 'Design', 'Design Pattern', 'Coding Rules']
published: true
---
**Principles** provide the high level guidelines for a system.
**Patterns** can be applied to implement these principles and allow use of known good solutions for common problems.
# Principles
Some of the earliest secure software design principles were proposed by [Saltzer in the 1970's](https://en.wikipedia.org/wiki/Saltzer_and_Schroeder%27s_design_principles):
## Saltzer Secure Software Design Principles
| Principle | Definition |
|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Economy of mechanism | Keep the design as simple and small as possible |
| Fail-safe defaults | Base access decisions on permission rather than exclusion |
| Complete mediation | Every access to every object must be checked for authority |
| Open design | The design should not be secret |
| Separation of privilege | Where feasible, a protection mechanism that requires two keys to unlock it is more robust and flexible than one that allows access to the presenter of only a single key |
| Least privilege | Every program and every user of the system should operate using the least set of privileges necessary to complete the jobMinimize the amount of mechanism common to more than one user and depended on by all users |
| Least common mechanism | Minimize the amount of mechanism common to more than one user and depended on by all users |
| Psychological acceptability | It is essential that the human interface be designed for ease of use, so that users routinely and automatically apply the protection mechanisms correctly |
| Work factor | Compare the cost of circumventing the mechanism with the resources of a potential attacker |
| Compromise recording | It is sometimes suggested that mechanisms that reliably record that a compromise of information has occurred can be used in place of more elaborate mechanisms that completely prevent loss |
### Other Useful Secure Software Development Principles
1. Minimize the footprint of sensitive data - in time and space
1.1 How long or how often the Sensitive data exists
1.2 Where the sensitive data exists or flows - the code or interfaces that touch the sensitive data.
## SOLID Principles
SOLID is an acronym for the first 5 principles of object-oriented design:
| Principle | Definition |
|-----------------------------------------|-----------------------------------------------------------------------|
| **S**RP The Single Responsibility Principle | Keep the design as simple and small as possible |
| **O**CP The Open Closed Principle | you should be able to extend a class's behavior, without modifying it |
| **L**SP The Liskov Substitution Principle | derived classes must be substitutable for their base classes |
| **I**SP The Interface Segregation Principle | make fine grained interfaces that are client specific |
| **D**IP The Dependency Inversion Principle | depend on abstractions not on concrete implementations |
# Patterns
> "Each pattern describes a problem which occurs over and over again in our
environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice.” Christopher Alexander
The term "design pattern" is often used to refer to any pattern which addresses issues of **software architecture, design, or programming implementation**.
[Secure Design Patterns](https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9115) gives the following defincitions.
| Pattern | Definition | Example |
|----------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
| Architecture Pattern | Expresses a fundamental structural organization or schema for software systems. It provides a set of predefined subsystems, specifies their responsibilities, and includes rules and guidelines for organizing the relationships between them. | PrivSep (Privilege Separation) |
| Design Patterns | Provides a scheme for refining the subsystems or components of a software system, or the relationships between them. It describes a commonly recurring structure of communicating components that solves a general design problem within a particular context. | Secure Factory |
| Implementation Pattern | Implementation-level patterns address low-level security issues. Patterns in this class are usually applicable to the implementation of specific functions or methods in the system. Implementation-level patterns address the same problem set addressed by the CERT Secure Coding Standards [CERT 2009a] and are often linked to a corresponding secure coding guideline | Clear Sensitive Information |
## Architecture Patterns
Architectural-level patterns focus on the high-level allocation of responsibilities between different components of the system and define the interaction between
those high-level components.
### SEI Secure Architecture Patterns
[SEI Secure Architecture Patterns](https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9115) are as follows:
| Architecture Pattern Name | Details |
|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Distrustful Decomposition (aka Privilege reduction) | Move separate functions into mutually untrusting programs, thereby reducing the • attack surface of the individual programs that make up the system • functionality and data exposed to an attacker if one of the mutually untrusting programs is compromised |
| PrivSep (Privilege Separation) | Reduce the amount of code that runs with special privilege without affecting or limiting the functionality of the program. The PrivSep pattern is a more specific instance of the Distrustful Decomposition pattern. |
| Defer to Kernel | Clearly separate functionality that requires elevated privileges from functionality that does not require elevated privileges and to take advantage of existing user verification functionality available at the kernel level. Using existing user verification kernel functionality leverages the kernel’s established role in arbitrating security decisions rather than reinventing the means to arbitrate security decisions at the user level |
## Design Patterns
One of the better known set of Design Patterns for Security is [SEI Secure Design Patterns](https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9115):
### SEI Secure Design Patterns
[SEI Secure Design Patterns](https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=9115) defines the following Secure Design Patterns:
1. Secure Factory
2. Secure Strategy Factory
3. Secure Builder Factory
4. Secure Chain of Responsibility
5. Secure State Machine
6. Secure Visitor
# References
1. M. Schumacher. [Security patterns: integrating security and systems engineering](https://www.amazon.com/Security-Patterns-Integrating-Systems-Engineering/dp/0470858842/). Wiley
series in software design patterns. John Wiley & Sons, 2006.
2. Chad Dougherty, Kirk Sayre, Robert C. Seacord, David Svoboda, and Kazuya Togashi.
[Secure design patterns. Technical report](http://www.sei.cmu.edu/reports/09tr010.pdf.), Software Engineering Institute, Carnegie Mellon,October 2009.
3. 3/E. Gamma, R. Johnson, J. Vlissides, and R. Helm. [Design Patterns: Elements of Reusable Object-Oriented Software](https://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612) Addison-Wesley, 1995.
4. John Viega and Gary McGraw. https://www.amazon.com/Building-Secure-Software-Security-Documents-ebook/dp/B003CW67YQ. Addison-Wesley, September 2002
5. Joseph Yoder and Jeffrey Barcalow. Architectural patterns for enabling application
security. In Fourth Conference on Pattern Languages of Programs, 1998.
6. [ISO/IEC TS 17961 C Secure Coding Rules](https://www.iso.org/standard/61134.html). All rules meant to be enforceable by static analysis
<a href="https://www.freepik.com/free-photos-vectors/background"> Image by freepik - www.freepik.com</a> | 95.637097 | 566 | 0.532423 | eng_Latn | 0.982066 |
9a7ffbc5cfff213b088ee0a24ebc442fcc713be8 | 280 | md | Markdown | _posts/2007-10-12-t330637352.md | ChristopheDucamp/christopheducamp.github.io | 5fb5f16b75a707cc7d8599bfc02c5cb147a69849 | [
"MIT"
] | 4 | 2018-04-01T18:28:49.000Z | 2018-11-12T08:41:55.000Z | _posts/2007-10-12-t330637352.md | ChristopheDucamp/christopheducamp.github.io | 5fb5f16b75a707cc7d8599bfc02c5cb147a69849 | [
"MIT"
] | null | null | null | _posts/2007-10-12-t330637352.md | ChristopheDucamp/christopheducamp.github.io | 5fb5f16b75a707cc7d8599bfc02c5cb147a69849 | [
"MIT"
] | 4 | 2016-12-17T14:19:26.000Z | 2021-04-14T23:44:50.000Z | ---
layout: post
microblog: true
audio:
photo:
date: 2007-10-12 00:00:00 -0000
guid: http://xtof.micro.blog/2007/10/12/t330637352.html
---
Ailleurs, Philippe Le Grand, dg de Manche Numérique lance une première expérience d'agence bancaire avec fibre numérique... c'est à St Lô.
| 28 | 138 | 0.742857 | fra_Latn | 0.800309 |
9a80d38a1624bfddf7a1f0984895c5a4aafdb227 | 26 | md | Markdown | README.md | Gabriel-Montenegro-Campos/gaccsigi | 375558e4ca03d8ecff4ebdc14e3420fca94c3b63 | [
"MIT"
] | 1 | 2020-10-27T20:59:06.000Z | 2020-10-27T20:59:06.000Z | README.md | Gabriel-Montenegro-Campos/gaccsigi | 375558e4ca03d8ecff4ebdc14e3420fca94c3b63 | [
"MIT"
] | null | null | null | README.md | Gabriel-Montenegro-Campos/gaccsigi | 375558e4ca03d8ecff4ebdc14e3420fca94c3b63 | [
"MIT"
] | null | null | null | # gaccsigi
uniao gratidao
| 8.666667 | 14 | 0.807692 | ast_Latn | 0.309813 |
9a81c236c469d2c73eaeb4182f391e2baae5890a | 3,233 | md | Markdown | swords-and-wizardry/README.md | ManuZzZ85/roll20-character-sheets | b5fef2108ec42bc4334fb0a35e30b361e275c01c | [
"MIT"
] | 1,104 | 2015-01-02T17:02:48.000Z | 2022-03-31T19:32:41.000Z | swords-and-wizardry/README.md | ManuZzZ85/roll20-character-sheets | b5fef2108ec42bc4334fb0a35e30b361e275c01c | [
"MIT"
] | 4,560 | 2015-01-04T22:17:13.000Z | 2022-03-31T21:29:56.000Z | swords-and-wizardry/README.md | ManuZzZ85/roll20-character-sheets | b5fef2108ec42bc4334fb0a35e30b361e275c01c | [
"MIT"
] | 5,009 | 2015-01-01T16:21:24.000Z | 2022-03-30T12:50:54.000Z | # Swords & Wizardry
Character sheet for Swords & Wizardry, in English and French.
## Authors
* [Natha](https://github.com/NathaTerrien/roll20-wip/blob/master/README.md) (technical overhaul)
* Jacob Vann (initial author)
## Current version
Screenshots:
* [English](SWSheet.png)
* [French](SWSheet_fr.png)
The sheet and its automated calculations (modifiers, etc.) are based on Swords & Wizardry Complete Rules.
Every calculation can be overridden by manual input, if house rules are used. Modifying certain fields will trigger the associated automated calculation. For example, modifying DEX will trigger the AC modifier to be calculated, the total AC, etc. Then any custom value previously entered has to be set again.
## Release notes
### v2.3 (2020-04-21)
* Fixed broken image link due to ampersand by moving this sheet to "swords-and-wizardry".
* Cleaned up documentation fixing typos and adding minor copy edits.
### v2.2 (2017-09-17)
* Technical optimisation
### v2.1 (2017-02-15)
* Layout bug fix: Min/Max spell label was too long, and the corresponding field was hidden
* New 'Total Weight' field (automatically calculated based on total treasure and gear weights, but can be overriden)
* Treasure and Gear total weights calculation optimisation
* Relocate logo from imgur to github
### v2.0 (2017-02-04)
Note : this new version of the sheet is compatible with previous versions and characters.
* New and more compact design
* Translation compatible
* Added missing derived attributes (Open doors, Spell level, min/max spells)
* Automated calculations (by sheet workers) of derived attributes, when an attribute is modified (ex: modifying Strength will calculate the melee To-Hit mod, Damage mod, Carry mod, Open Doors threshold)
* New "Other" AC modifier to note magic items effect on AC, like rings or curses, wounds, spell effects etc.
* Handling of Ascending and Descending AC (radio button). On change:
* Base AC is (re)set accordingly
* DEX modifier to AC is calculated accordingly
* Ascending AC is calculated by adding Base AC + DEX modifier + absolute value of Armor AC modifier + absolute value of Shield AC modifier + Other AC modifier
* Descending AC is calculated by adding Base AC + DEX modifier - absolute value of Armor AC modifier - absolute value of Shield AC modifier + Other AC modifier
* Gear and Treasure weight are automatically tallied.
* Total gear weight sums every item weight, multiplied by quantity (unit weight assumed)
* Total Treasure weight sums every item weight
* Total wealth is NOT calculated
* Move squares are NOT calculated (depending on house rules and/or local distance measuring units)
* New languages field
* New Hit Dice field (roll formula)
* New separate numeric field in the Saving Throwns bonuses repeating section
* New optional Roll field (dice formula) in the Abilities & Magic repeating section
* Roll buttons added, with chat roll template:
* Hit points from Hit Dice formula
* Standard Saving throw (with success or failure indicator)
* Saving throw with Bonus (with success or failure indicator)
* Open Door (with success or failure indicator)
* Abilies or Magic custom roll
* Attack, with To-Hit and Damage rolls at once
| 46.855072 | 308 | 0.768017 | eng_Latn | 0.991003 |
9a82466cbaad79078c09198a276a05e97cfac16f | 275 | md | Markdown | README.md | dnrobin/nano | 1173c66babfd3e5662b1f49d635bda329b190eea | [
"MIT"
] | null | null | null | README.md | dnrobin/nano | 1173c66babfd3e5662b1f49d635bda329b190eea | [
"MIT"
] | null | null | null | README.md | dnrobin/nano | 1173c66babfd3e5662b1f49d635bda329b190eea | [
"MIT"
] | 1 | 2019-09-16T11:32:40.000Z | 2019-09-16T11:32:40.000Z | # nano
A tiny API framework written in PHP for quick project prototypes.
# Getting Started
```php
require_once __DIR__ . '/vendor/autoload.php';
$api = new nano\Server();
# serve text from root
$api->get('/', function () {
echo "Hello, World!";
})
$api->run();
```
| 14.473684 | 65 | 0.647273 | eng_Latn | 0.579785 |
9a82d264f3e940293c38756f77d571dd8df10694 | 607 | md | Markdown | README.md | natephunt/openAI_gym_spaceInvaders | 17c4cca0a8719fee73f518e5f04086f4b8ab631a | [
"MIT"
] | null | null | null | README.md | natephunt/openAI_gym_spaceInvaders | 17c4cca0a8719fee73f518e5f04086f4b8ab631a | [
"MIT"
] | null | null | null | README.md | natephunt/openAI_gym_spaceInvaders | 17c4cca0a8719fee73f518e5f04086f4b8ab631a | [
"MIT"
] | null | null | null | # project_scaffold_template
Used for making new projects
## Structure or Outline
- app folder
- flask_app.py - this is where all your code to define your routes and view functions.
- simple_site.py - this is a simple flask site that allows students to learn about Flask.
- ai_utils.py - this contains the utility functions for you to run your model. You should have already found the optimum confidence-level for your model to have the best balance between precision and recall.
- utils.py - this contains general util functions for your app.
- main.py - main file for running code | 55.181818 | 211 | 0.75453 | eng_Latn | 0.999697 |
9a8404e642619f0254b813a9cde4745d993bb3f4 | 906 | md | Markdown | 2019/CVE-2019-14223.md | marcostolosa/cve | bfe85c74b105c623c9807e09b2b572f144bf1f1c | [
"MIT"
] | 4 | 2022-03-01T12:31:42.000Z | 2022-03-29T02:35:57.000Z | 2019/CVE-2019-14223.md | marcostolosa/cve | bfe85c74b105c623c9807e09b2b572f144bf1f1c | [
"MIT"
] | null | null | null | 2019/CVE-2019-14223.md | marcostolosa/cve | bfe85c74b105c623c9807e09b2b572f144bf1f1c | [
"MIT"
] | 1 | 2022-03-29T02:35:58.000Z | 2022-03-29T02:35:58.000Z | ### [CVE-2019-14223](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14223)
### Description
An issue was discovered in Alfresco Community Edition versions below 5.2.6, 6.0.N and 6.1.N. The Alfresco Share application is vulnerable to an Open Redirect attack via a crafted POST request. By manipulating the POST parameters, an attacker can redirect a victim to a malicious website over any protocol the attacker desires (e.g.,http, https, ftp, smb, etc.).
### POC
#### Reference
No POC found.
#### Github
- https://github.com/ARPSyndicate/kenzer-templates
- https://github.com/Elsfa7-110/kenzer-templates
- https://github.com/sobinge/nuclei-templates
| 45.3 | 361 | 0.752759 | kor_Hang | 0.284047 |
9a853fa2b2bb1a6f91e91206190a0ba846432f1a | 2,560 | md | Markdown | README.md | Orochimarufan/HIDRAW | 764a6f6fc144c3c6850978e0341630444cbea049 | [
"MIT",
"Unlicense"
] | 9 | 2016-01-24T19:04:23.000Z | 2021-03-24T01:08:17.000Z | README.md | Orochimarufan/HIDRAW | 764a6f6fc144c3c6850978e0341630444cbea049 | [
"MIT",
"Unlicense"
] | 1 | 2020-11-10T21:24:48.000Z | 2020-11-15T16:45:47.000Z | README.md | Orochimarufan/HIDRAW | 764a6f6fc144c3c6850978e0341630444cbea049 | [
"MIT",
"Unlicense"
] | 1 | 2019-03-25T22:56:28.000Z | 2019-03-25T22:56:28.000Z | HIDRAW utils
============
A set of utility programs for working with Linux hidraw devices
CodeLite (http://codelite.org) is used as IDE and is required to build the projects.
uinput\_ddrpad also comes with a Makefile for building without CodeLite:
cd uinput_ddrpad
make
make install
Note that depending on the permissions on your devices (/dev/\*), you may have to run these tools as root.
HIDRAW\_test
-----------
Analyze the HID report descriptor.
This will attempt to parse the HID report descriptor and display it in two different ways:
* As a descriptor tree similar to what the HID Descriptor Tool uses,
* It will try to construct a human-readable representation of the report structure.
Additionally, it will try to display the current state of the device and update until Ctrl-C is pressed.
The included descriptor parser is NOT optimized for speed, instead it tries to be as generic as possible.
Synopsis: HIDRAW\_test /dev/\<hidraw device\>
uinput\_ddrpad
--------------
Use the HIDRAW device to get vendor specific information from input reports of Konami's
DanceDanceRevolution Mat for PS3 and make it usable in Applications
through the uinput kernel module (via libsuinput)
This allows use of the PS3 DDR mat in StepMania without encountering the Axis problem
as well as without any conversion hardware.
Synopsis: uinput\_ddrpad [-v] [/dev/\<hidraw device\>]
LICENSE
=======
The MIT license
Copyright (c) 2014-2015 Taeyeon Mori
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
| 40 | 106 | 0.759375 | eng_Latn | 0.954419 |
9a85515a101baca88ab45e5ded415075e70ee461 | 1,133 | md | Markdown | packages/reduceRight/readme.md | probablyup/arr | daf745a32ef28df7875fbd09672153c274d76977 | [
"MIT"
] | 255 | 2017-07-06T23:40:48.000Z | 2022-01-19T14:27:35.000Z | packages/reduceRight/readme.md | probablyup/arr | daf745a32ef28df7875fbd09672153c274d76977 | [
"MIT"
] | 8 | 2017-07-06T23:55:56.000Z | 2020-04-29T07:05:00.000Z | packages/reduceRight/readme.md | probablyup/arr | daf745a32ef28df7875fbd09672153c274d76977 | [
"MIT"
] | 13 | 2017-08-16T16:58:20.000Z | 2022-01-19T14:27:36.000Z | # @arr/reduceright
> A tiny, faster alternative to native `Array.prototype.reduceRight`
## Install
```
$ npm install --save @arr/reduceright
```
## Usage
```js
import reduceRight from '@arr/reduceright';
reduceRight([[0, 1], [2, 3], [4, 5]], (a, b) => a.concat(b), []);
//=> [4, 5, 2, 3, 0, 1]
```
## API
### reduceRight(arr, callback[, initialValue])
#### arr
Type: `Array`<br>
The array to iterate upon.
#### callback(accumulator, value, index, array)
Type: `Function`<br>
Function to test for each element, taking four arguments:
* **accumulator** -- The value previously returned in the last invocation of the callback, or initialValue, if supplied.
* **value** -- The current element being processed in the array.
* **index** -- The index of the current element being processed in the array.
* **array** -- The array `reduceRight` was called upon.
#### initialValue
Type: `Mixed`<br>
Default: `arr[-1]`<br>
The `value` to use as the first argument to the first call of the `callback`. If no initial value is supplied, the last element in the array will be used.
## License
MIT © [Luke Edwards](http://lukeed.com)
| 24.630435 | 154 | 0.676081 | eng_Latn | 0.961784 |
9a855826867892354af39ebc7c95c9f726a2b509 | 26 | md | Markdown | README.md | Abziz/secret-hitler-room-maker | d48acbc9c8f89c85a9e80de50c28cf380cc6347b | [
"MIT"
] | 1 | 2019-08-13T13:02:14.000Z | 2019-08-13T13:02:14.000Z | README.md | Abziz/secret-hitler-room-maker | d48acbc9c8f89c85a9e80de50c28cf380cc6347b | [
"MIT"
] | 2 | 2020-04-07T20:51:18.000Z | 2020-07-18T09:14:23.000Z | README.md | Abziz/secret-hitler-room-maker | d48acbc9c8f89c85a9e80de50c28cf380cc6347b | [
"MIT"
] | null | null | null | # secret-hitler-room-maker | 26 | 26 | 0.807692 | nld_Latn | 0.578793 |
9a862ed2f318f4a9321b43ede11133b8faba8013 | 211 | md | Markdown | docs/ItemTags.md | UltraCart/rest_api_v2_sdk_ruby | 47bb1308f32da71e2df929aeba39087af8f5b24d | [
"Apache-2.0"
] | null | null | null | docs/ItemTags.md | UltraCart/rest_api_v2_sdk_ruby | 47bb1308f32da71e2df929aeba39087af8f5b24d | [
"Apache-2.0"
] | null | null | null | docs/ItemTags.md | UltraCart/rest_api_v2_sdk_ruby | 47bb1308f32da71e2df929aeba39087af8f5b24d | [
"Apache-2.0"
] | null | null | null | # UltracartClient::ItemTags
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**tags** | [**Array<ItemTag>**](ItemTag.md) | tags | [optional]
| 23.444444 | 70 | 0.464455 | kor_Hang | 0.135547 |
9a870b780c42eba2a1f1e9ed2e7e750ace433c2c | 297 | md | Markdown | build/docs/PINConfiguration.md | MyPureCloud/platform-client-sdk-ios | d69e3deedbbe2f30c3641a5c8b4e66eb5eb6858b | [
"MIT"
] | null | null | null | build/docs/PINConfiguration.md | MyPureCloud/platform-client-sdk-ios | d69e3deedbbe2f30c3641a5c8b4e66eb5eb6858b | [
"MIT"
] | null | null | null | build/docs/PINConfiguration.md | MyPureCloud/platform-client-sdk-ios | d69e3deedbbe2f30c3641a5c8b4e66eb5eb6858b | [
"MIT"
] | 1 | 2021-05-11T21:57:38.000Z | 2021-05-11T21:57:38.000Z | ---
title: PINConfiguration
---
## PINConfiguration
## Properties
|Name | Type | Description | Notes|
|------------ | ------------- | ------------- | -------------|
| **minimumLength** | **Int** | | [optional] |
| **maximumLength** | **Int** | | [optional] |
{: class="table table-striped"}
| 19.8 | 62 | 0.474747 | eng_Latn | 0.194941 |
9a870ec5f5ed33cc1c741da08c342470c3e674ef | 5,973 | md | Markdown | controls/ajaxpanel/overview.md | DKaramfilov/ajax-docs | 86b5dbbf757f7b1fd84ec8b313be0d70cd957f8e | [
"Apache-2.0"
] | 22 | 2015-07-21T10:33:39.000Z | 2022-02-21T09:17:40.000Z | controls/ajaxpanel/overview.md | DKaramfilov/ajax-docs | 86b5dbbf757f7b1fd84ec8b313be0d70cd957f8e | [
"Apache-2.0"
] | 132 | 2015-07-14T13:56:12.000Z | 2022-01-28T10:04:56.000Z | controls/ajaxpanel/overview.md | DKaramfilov/ajax-docs | 86b5dbbf757f7b1fd84ec8b313be0d70cd957f8e | [
"Apache-2.0"
] | 355 | 2015-07-14T02:38:17.000Z | 2021-11-30T13:22:18.000Z | ---
title: Overview
page_title: RadAjaxPanel Overview
description: Check our Web Forms article about Overview.
slug: ajaxpanel/overview
previous_url: ajax/radajaxpanel/overview
tags: overview
published: True
position: 0
---
# RadAjaxPanel Overview
This help article describes the main features of the RadAjaxPanel, how to use it, and provides methods you can use if you need to use an external control to force RadAjaxPanel to perform an AJAX request. The **RadAjaxPanel** control provides the easiest way to AJAX-enable ASP.NET web controls. You simply need to place the controls that you want Ajax-enabled into a **RadAjaxPanel** and Telerik **RadAjax** takes care of the rest. Best of all, this happens transparently to the framework and the controls that are being Ajax-enabled.
## Key features:
* Ajax-enables all controls inside that normally work with postbacks.
* Defines visually and codeless (in Visual Studio design-time) which elements should be updated via AJAX requests. All elements wrapped in the panel will be updated via AJAX
* No need to modify your application logic
* Allows you to update a number of page elements at once
* No need to write any JavaScript or invoke AJAX requests manually
## RadAjaxPanel Usage
In Visual Studio at design time, if you want to Ajax-enable web controls on a page just add a **RadAjaxPanel** to your page and then drag the controls you want to make callbacks into the **RadAjaxPanel**. Those controls will start performing callbacks instead of postbacks. **Figure 1** shows a typical usage scenario. A standard ASP.NET Calendar control is placed in a **RadAjaxPanel**. On the web form there is also a [loading panel]({%slug ajaxloadingpanel/overview%}) control that will be shown in place of the **RadAjaxPanel** during the AJAX request.
>caution The whole **RadAjaxPanel** (with **ALL** controls inside) is updated when one of the controls makes an AJAX request. Thus, if you put the whole page into a **RadAjaxPanel** , this may cause -reduced- performance, as -all- controls within the panel will be updated, -not- just the AJAX initiator.Placing the whole page into a **RadAjaxPanel** is usable when you have a relatively small number of controls on the page.
>
**Out-of-Panel Update**
There are cases when you may want to update the controls inside a **RadAjaxPanel** by triggering a callback externally from other control on the page. The following approach is not recommended as **RadAjaxManager** can handle any complex scenarios. You can use asp:Panel controls and link them via **RadAjaxManager**'s settings. The same Panel may be set as both AJAX initiator and updated control, which will cause functionality similar to **RadAjaxPanel** .
You need to call the**$find(<%RadAjaxPanel1.ClientID%>).ajaxRequest()** method (passing the necessary information as parameters to it) and then override the **RaisePostBackEvent** method or handle theRadAjaxPanel **AjaxRequest** server-side event to apply the changes. **Example 1** shows a sample implementation, which changes the background color of the panel.
**Example 1**: Use external control to update **RadAjaxPanel**
````ASP.NET
<telerik:RadScriptManager ID="RadScriptManager1" runat="server">
</telerik:RadScriptManager>
<telerik:RadAjaxPanel ID="RadAjaxPanel1" runat="server" OnAjaxRequest="RadAjaxPanel1_AjaxRequest">
</telerik:RadAjaxPanel>
<telerik:RadCodeBlock ID="RadCodeBlock1" runat="server">
<script type="text/javascript">
function invokeAjaxRequest() {
$find("<%= RadAjaxPanel1.ClientID%>").ajaxRequestWithTarget("<%= RadAjaxPanel1.UniqueID %>", "ChangeColor");
}
</script>
</telerik:RadCodeBlock>
<input type="button" value="Change color" onclick="invokeAjaxRequest();" />
````
And in the code-behind:
````C#
protected void RadAjaxPanel1_AjaxRequest(object sender, AjaxRequestEventArgs e)
{
switch (e.Argument)
{
case "ChangeColor":
RadAjaxPanel1.BackColor = System.Drawing.Color.Maroon;
break;
default:
break;
}
}
````
````VB
Protected Sub RadAjaxPanel1_AjaxRequest(sender As Object, e As AjaxRequestEventArgs)
Select Case e.Argument
Case "ChangeColor"
RadAjaxPanel1.BackColor = System.Drawing.Color.Maroon
End Select
End Sub
````
## ajaxRequestWithTarget() Reference
You can use any external control to force **RadAjaxPanel** to perform an AJAX request by calling this client-side function. When using this function, the event target defaults to the **RadAjaxPanel** instance.
>note You can construct the JavaScript function calls manually or alternatively use the server-side method [GetAjaxEventReference](https://docs.telerik.com/devtools/aspnet-ajax/api/server/Telerik.Web.UI/RadAjaxControl#getajaxeventreference) and have Telerik RadAjax generate the necessary code for you.
>
| **_doPostBack(eventTarget, eventArgument)** or **$find("<%=RadAjaxPanel1.ClientID%>").ajaxRequestWithTarget(eventTarget, eventArgument)** | |
| ------ | ------ |
| **eventTarget** |The control that should raise the postback event. You should use the control's **UniqueID** .|
| **eventArgument** |This is an optional argument for the event|
## ajaxRequest() Reference
>caption
| **$find("<%=RadAjaxPanel1.ClientID%>").ajaxRequest(arguments)** | |
| ------ | ------ |
| **arguments** |The parameters the control used when it raised the request.|
When either of these functions is called on the client it can be handled in the AjaxRequest event handler on the server.
## See Also
* [Client-side Programming Overview]({%slug ajaxpanel/client-side-programming/overview%})
* [Demo: RadAjaxManager](https://demos.telerik.com/aspnet-ajax/ajax/examples/overview/defaultcs.aspx)
* [Demo: RadAjaxPanel](https://demos.telerik.com/aspnet-ajax/ajax/examples/panel/firstlook/defaultcs.aspx)
| 47.031496 | 556 | 0.744517 | eng_Latn | 0.956353 |
9a873b37fd4d9681a87d69983f1e785d89ceb948 | 683 | md | Markdown | _extended-syntax/overview.md | WatheqAlshowaiter/markdown-guide-arabic | 437ba6b9fd6cf95fcb572432fad3fb6d4f60deb7 | [
"MIT"
] | 11 | 2021-11-01T12:29:16.000Z | 2022-02-07T23:23:53.000Z | _extended-syntax/overview.md | WatheqAlshowaiter/markdown-guide-arabic | 437ba6b9fd6cf95fcb572432fad3fb6d4f60deb7 | [
"MIT"
] | 1 | 2021-10-30T11:06:15.000Z | 2021-10-30T11:06:15.000Z | _extended-syntax/overview.md | WatheqAlshowaiter/markdown-guide-arabic | 437ba6b9fd6cf95fcb572432fad3fb6d4f60deb7 | [
"MIT"
] | 3 | 2021-10-30T05:20:52.000Z | 2021-12-20T22:00:47.000Z | ---
title: لمحة
syntax-id: overview
---
أضافت [القواعد الأساسية ](https://guide.dawin.io/basic-syntax) الموضحة في مستند التصميم الأصلي لجون جروبر العديد من العناصر المطلوبة في الاستخدام اليومي، ولكنها لم تكن كافية لبعض الناس. وهنا يأتي دور القواعد الموسّعة.
أخذ العديد من الأفراد والمؤسسات على عاتقهم توسيع القواعد الأساسية عن طريق بزيادة عناصر إضافية مثل: الجداول وكتل الأكواد البرمجية (Code Blocks)، وإبراز الأكواد البرمجية عن طريق تلوينها تبعًا لكل لغة (Syntax Highlighting)، وتفعيل الروابط تلقائيًا، والحواشي السفلية (Footnotes). يمكن تفعيل هذه العناصر باستخدام لغة ترميز خفيفة (أو تنويعات) تعتمد على قواعد ماركداون الأساسية، أو عن طريق إضافة امتداد إلى معالج ماركداون متوافق.
| 75.888889 | 422 | 0.793558 | arb_Arab | 0.999882 |
9a879ca01b05ceb0e7fe0f78846e898490f0f6ba | 1,723 | md | Markdown | AlchemyInsights/use-rights-management-protection-with-microsoft-365.md | isabella232/OfficeDocs-AlchemyInsights-pr.it-IT | fc53f2b99aa5bf746f7b56299e858835418f815d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:06:53.000Z | 2020-05-19T19:06:53.000Z | AlchemyInsights/use-rights-management-protection-with-microsoft-365.md | MicrosoftDocs/OfficeDocs-AlchemyInsights-pr.it-IT | f43a8b34e8011ca249fd46d4c5515486a74c861b | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:57:00.000Z | 2022-02-09T06:57:34.000Z | AlchemyInsights/use-rights-management-protection-with-microsoft-365.md | isabella232/OfficeDocs-AlchemyInsights-pr.it-IT | fc53f2b99aa5bf746f7b56299e858835418f815d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-10-11T19:12:58.000Z | 2019-10-11T19:12:58.000Z | ---
title: Usare la protezione di Rights Management con Microsoft 365
ms.author: pebaum
author: pebaum
manager: scotv
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "9001670"
- "3737"
- "3820"
ms.openlocfilehash: 723d5d273a844bb5a53e9447ba6b1e9c1bd7ec04
ms.sourcegitcommit: ab75f66355116e995b3cb5505465b31989339e28
ms.translationtype: HT
ms.contentlocale: it-IT
ms.lasthandoff: 08/13/2021
ms.locfileid: "58324274"
---
# <a name="use-rights-management-protection-with-microsoft-365"></a>Usare la protezione di Rights Management con Microsoft 365
Per poter usare le funzionalità IRM (Information Rights Management), è necessario prima attivare il servizio [RMS (Rights Management)](https://docs.microsoft.com/azure/information-protection/what-is-azure-rms).
1. Per i requisiti di licenza e attivazione dall'**interfaccia di amministrazione di Microsoft 365**, vedere [Come attivare la protezione di Rights Management dall'interfaccia di amministrazione di Microsoft 365](https://docs.microsoft.com/azure/information-protection/activate-office365).
**Nota**: richiede un account di amministratore globale.
2. Per i requisiti di licenza e l'attivazione dal **portale di Azure**, vedere [Come attivare il servizio di protezione di Rights Management dal portale di Azure](https://docs.microsoft.com/azure/information-protection/activate-azure). **Nota**: non richiede un account Amministratore globale.
Per altre informazioni, vedere i [riferimenti alle informazioni su Rights Management nell'interfaccia di amministrazione](https://docs.microsoft.com/office365/enterprise/activate-rms-in-office-365).
| 50.676471 | 293 | 0.805572 | ita_Latn | 0.896609 |
9a87d107dde047340945a80f6f935c8362dfa7eb | 5,768 | md | Markdown | docs/output.md | marissaDubbelaar/epitopeprediction | ce15e440954f8e7c83c341261b82aacc8e3535ac | [
"MIT"
] | 22 | 2019-04-15T08:37:00.000Z | 2022-03-10T15:49:04.000Z | docs/output.md | marissaDubbelaar/epitopeprediction | ce15e440954f8e7c83c341261b82aacc8e3535ac | [
"MIT"
] | 104 | 2018-11-28T15:47:29.000Z | 2022-03-31T15:19:59.000Z | docs/output.md | marissaDubbelaar/epitopeprediction | ce15e440954f8e7c83c341261b82aacc8e3535ac | [
"MIT"
] | 17 | 2019-03-04T22:29:13.000Z | 2022-03-15T14:57:38.000Z | # nf-core/epitopeprediction: Output
This document describes the output produced by the pipeline. Most of the plots are taken from the MultiQC report, which summarises results at the end of the pipeline.
The directories listed below will be created in the results directory after the pipeline has finished. All paths are relative to the top-level results directory.
## Pipeline overview
The pipeline is built using [Nextflow](https://www.nextflow.io/) and processes data using the following steps:
* [Epitope Prediction](#epitope-prediction) - Predict MHC-binding peptides
* [MultiQC](#multiqc) - Aggregate report describing results from the whole pipeline
* [Pipeline information](#pipeline-information) - Report metrics generated during the workflow execution
## Epitope Prediction
[FRED2](https://github.com/FRED-2) is used to perform the prediction of Epitopes on the given data, independent of the chosen `tools` to perform the prediction.
**Output directory: `predictions/`**
* `[input_base_name]_prediction_report.json`
* The predicted epitopes in JSON format for downstream analysis tasks
* `[input_base_name]_prediction_results.tsv`
* The predicted epitopes in TSV format for further processing.
An example report looks like this in TSV format:
```bash
sequence length chr pos gene transcripts proteins variant type method HLA-A*01:01 score HLA-A*01:01 affinity HLA-A*01:01 binder synonymous homozygous variant details (genomic) variant details (protein)
DSHLHTHVY 9 17 3336962 ENSG00000127780 ENST00000248384 ENSP00000248384 SNP syfpeithi-1.0 20.0 50.0 False False False c.173C>A p.Pro58His
HLHTHVYLF 9 17 3336962 ENSG00000127780 ENST00000248384 ENSP00000248384 SNP syfpeithi-1.0 3.0 7.5 False False False c.173C>A p.Pro58His
HTHVYLFLS 9 17 3336962 ENSG00000127780 ENST00000248384 ENSP00000248384 SNP syfpeithi-1.0 7.0 17.5 False False False c.173C>A p.Pro58His
HVYLFLSNL 9 17 3336962 ENSG00000127780 ENST00000248384 ENSP00000248384 SNP syfpeithi-1.0 0.0 0.0 False False False c.173C>A p.Pro58His
```
The prediction results are given as allele-specific score and affinity values per peptide. The computation of these values depends on the applied prediction method:
* [`Syfpeithi`](http://www.syfpeithi.de) :
* **Affinity**: Calculated based on the score as the percentage of the maximum value of the corresponding matrix: `score(peptide) divided by the maximum score of the allele/length-specific matrix * 100`.
* **Score**: Sum of the values given by the allele-specific position-specific scoring matrix (PSSM) for the respective peptide sequence.
Peptides are considered binders if the affinity is higher than 50.
* [`MHCflurry`](https://github.com/openvax/mhcflurry):
* **Affinity**: Predicted IC50 (threshold for binders: `<500 nmol/L`).
* **Score**: The provided score is calculated from the log-transformed predicted binding affinity and scaled to an interval of 0 to 1: `1-log50000(aff)`.
* [`MHCnuggets`](https://github.com/KarchinLab/mhcnuggets):
* **Affinity**: Predicted IC50 (threshold for binders: `<500 nmol/L`).
* **Score**: The provided score is calculated from the log-transformed predicted binding affinity and scaled to an interval of 0 to 1: `1-log50000(aff)`.
When the parameter `--fasta_output` is specified a `FASTA` file will be generated that contains the sequences of proteins that are affected by the provided genomic variants. The resulting `FASTA` file will contain the wild-type and mutated protein sequences.
**Output directory: `predictions/`**
* `[input_base_name]_prediction_proteins.fasta`
* The sequences of proteins, affected by provided variants, in FASTA format.
### Supported models
When running the pipeline using the `--show_supported_models` parameter, the information about supported models for the available predictor tool versions will be written to the results folder.
**Output directory: `supported_models/`**
* `[tool].[version].supported_alleles.txt`
* A list of all supported alleles by the corresponding predictor method.
* `[tool].[version].supported_lengths.txt`
* A list of all supported peptide lengths by the corresponding predictor method.
## MultiQC
[MultiQC](http://multiqc.info) is a visualization tool that generates a single HTML report summarizing all samples in your project. Most of the pipeline QC results are visualised in the report and further statistics are available in the report data directory.
The pipeline has special steps which also allow the software versions to be reported in the MultiQC output for future traceability.
For more information about how to use MultiQC reports, see [https://multiqc.info](https://multiqc.info).
**Output files:**
* `multiqc/`
* `multiqc_report.html`: a standalone HTML file that can be viewed in your web browser.
* `multiqc_data/`: directory containing parsed statistics from the different tools used in the pipeline.
* `multiqc_plots/`: directory containing static images from the report in various formats.
## Pipeline information
[Nextflow](https://www.nextflow.io/docs/latest/tracing.html) provides excellent functionality for generating various reports relevant to the running and execution of the pipeline. This will allow you to troubleshoot errors with the running of the pipeline, and also provide you with other information such as launch commands, run times and resource usage.
**Output files:**
* `pipeline_info/`
* Reports generated by Nextflow: `execution_report.html`, `execution_timeline.html`, `execution_trace.txt` and `pipeline_dag.dot`/`pipeline_dag.svg`.
* Reports generated by the pipeline: `pipeline_report.html`, `pipeline_report.txt` and `software_versions.csv`.
* Documentation for interpretation of results in HTML format: `results_description.html`.
| 62.695652 | 355 | 0.784327 | eng_Latn | 0.986308 |
9a87f50cbf9d8e9220a2bde8a63a1b7048ff46b4 | 12,117 | md | Markdown | _posts/2019-01-10-spfx-react-based-carousel.md | nanddeepn/nanddeepnachanblogs | b729e91b30e5a7a32b2639594a6e00c80c016eb5 | [
"MIT"
] | null | null | null | _posts/2019-01-10-spfx-react-based-carousel.md | nanddeepn/nanddeepnachanblogs | b729e91b30e5a7a32b2639594a6e00c80c016eb5 | [
"MIT"
] | 1 | 2021-05-01T08:21:07.000Z | 2021-05-01T08:21:07.000Z | _posts/2019-01-10-spfx-react-based-carousel.md | nanddeepn/nanddeepnachanblogs | b729e91b30e5a7a32b2639594a6e00c80c016eb5 | [
"MIT"
] | null | null | null | ---
title: "SharePoint Framework - React based Carousel"
date: "2019-01-10"
share: true
categories:
- SharePoint
- SharePoint Framework
header:
image: media/2019-01-10-spfx-react-based-carousel/04.png
teaser: media/2019-01-10-spfx-react-based-carousel/04.png
tags:
- "2019"
- January 2019
last_modified_at: 2019-01-10T00:00:00-00:00
---
## Overview
SharePoint portals have many widgets or technically web parts displaying content to the users. They are either out of the box web parts configured to show the content or custom developed web parts. Carousel is one of such commonly used web part. The Carousel web part often scrolls the images in an infinite loop and allow users to scroll though. Often Carousels are used to rotate the news or announcements on a home page of SharePoint portal. The modern SharePoint does not offer any Carousel web part out of the box, however we can use available npm package for implementing Carousel.
In this article, we will explore npm package to help represent the Carousel in SPFx webpart. We will use React JS in this example.
## SharePoint Framework Version and NPM Packages Installed
For this article, I am using SharePoint Framework Version 1.7.1
```
npm view @microsoft/generator-sharepoint
```
To see the installed npm packages, use below command:
```
npm list-g --depth 0
```
## Create SPFx Solution
1. Open command prompt. Create a directory for SPFx solution.
```
md spfx-react-carousel
```
2. Navigate to above created directory.
```
cd spfx-react-carousel
```
3. Run Yeoman SharePoint Generator to create the solution.
```
yo @microsoft/sharepoint
```
4. Yeoman generator will present you with the wizard by asking questions about the solution to be created.
- **Solution Name:** Hit enter to have default name (spfx-react-carousel in this case) or type in any other name for your solution.
- Selected choice: Hit enter
- **Target for component:** Here we can select the target environment where we are planning to deploy the client webpart i.e. SharePoint Online or SharePoint OnPremise (SharePoint 2016 onwards).
- Selected choice: SharePoint Online only (latest)
- **Place of files:** We may choose to use the current folder or create a subfolder for our solution.
- Selected choice: Use the current folder
- **Deployment option:** We may choose to allow the tenant admin the choice of being able to deploy the solution to all sites immediately without running any feature deployment or adding apps in sites.
- Selected choice: N (install on each site explicitly)
- **Type of client-side component to create:** We can choose to create client side webpart or an extension. Choose webpart option.
- Selected choice: WebPart
- **Web part name:** Hit enter to select the default name or type in any other name.
- Selected choice: ReactCarousel
- **Web part description:** Hit enter to select the default description or type in any other value.
- Selected choice: React based Carousel
- **Framework to use:** Select any JavaScript framework to develop the component. Available choices are (No JavaScript Framework, React, and Knockout)
- Selected choice: React
5. Yeoman generator will perform scaffolding process to generate the solution. The scaffolding process will take significant amount of time.
6. Once the scaffolding process is completed, lock down the version of project dependencies by running below command.
```
npm shrinkwrap
```
7. On the command prompt type below command to open the solution in code editor of your choice.
```
code .
```
## npm Packages
**Carousel**
We will use the npm package called as react-responsive-carousel ([https://www.npmjs.com/package/react-responsive-carousel](https://www.npmjs.com/package/react-responsive-carousel))
Use below command to install the Carousel:
```
npm install react-responsive-carousel --save
```
The ```--save``` option enables NPM to include the packages to dependencies section of package.json file.
## Code the webpart
1. Open ReactCarousel.tsx file under "\src\webparts\reactCarousel\components\" folder.
2. Import the Carousel control.
```typescript
import { Carousel } from 'react-responsive-carousel';
```
3. Include the styles for Carousel.
```typescript
import "react-responsive-carousel/lib/styles/carousel.min.css";
```
## Define State
1. Create a new file IReactCarouselState.ts under "\src\webparts\reactCarousel\components\" folder.
```typescript
export interface IReactCarouselState {
imageURLs: string[];
}
```
2. Update our component "\src\webparts\reactCarousel\components\ReactCarousel.tsx" to use the state.
```typescript
export default class ReactCarousel extends React.Component<IReactCarouselProps, IReactCarouselState> {
public constructor(props: IReactCarouselProps, state: IReactCarouselState) {
super(props);
this.state = {
imageURLs: []
};
}
}
```
## Implement Service
Let us implement service to fetch the image urls to display in carousel
1. Create **services** folder under **src** folder.
2. Add a file *IDataService.ts* under **services** folder.
```typescript
export interface IDataService {
getImages: (listName?: string) => Promise<any>;
}
```
3. Add a file *ImageService.ts* under **services** folder.
```typescript
import { ServiceScope, ServiceKey } from "@microsoft/sp-core-library";
import { IDataService } from './IDataService';
import { SPHttpClient, SPHttpClientResponse } from '@microsoft/sp-http';
import { PageContext } from '@microsoft/sp-page-context';
import { ICarouselImage } from './ICarouselImage';
export class ImageService implements IDataService {
public static readonly serviceKey: ServiceKey<IDataService> = ServiceKey.create<IDataService>('carousel:data-service', ImageService);
private _spHttpClient: SPHttpClient;
private _pageContext: PageContext;
private _currentWebUrl: string;
constructor(serviceScope: ServiceScope) {
serviceScope.whenFinished(() => {
// Configure the required dependencies
this._spHttpClient = serviceScope.consume(SPHttpClient.serviceKey);
this._pageContext = serviceScope.consume(PageContext.serviceKey);
this._currentWebUrl = this._pageContext.web.absoluteUrl;
});
}
public getImages(listName?: string): Promise<string[]> {
var images: string[] = [];
return new Promise<string[]>((resolve: (itemId: string[]) => void, reject: (error: any) => void): void => {
this.readImages(listName)
.then((carouselItems: ICarouselImage[]): void => {
var i: number = 0;
for (i = 0; i < carouselItems.length; i++) {
images.push(this._currentWebUrl + carouselItems[i].FileRef);
}
resolve(images);
});
});
}
private readImages(listName: string): Promise<ICarouselImage[]> {
return new Promise<ICarouselImage[]>((resolve: (itemId: ICarouselImage[]) => void, reject: (error: any) => void): void => {
this._spHttpClient.get(`${this._currentWebUrl}/_api/web/lists/getbytitle('${listName}')/items?$select=FileRef/FileRef&$filter=FSObjType eq 0`,
SPHttpClient.configurations.v1,
{
headers: {
'Accept': 'application/json;odata=nometadata',
'odata-version': ''
}
})
.then((response: SPHttpClientResponse): Promise<{ value: ICarouselImage[] }> => {
return response.json();
})
.then((response: { value: ICarouselImage[] }): void => {
resolve(response.value);
}, (error: any): void => {
reject(error);
});
});
}
}
```
## Update Web Part class to consume Service
1. Open ReactCarousel.tsx file under "\src\webparts\reactCarousel\components\" folder.
2. Update the class to consume the implemented service.
```typescript
import * as React from 'react';
import styles from './ReactCarousel.module.scss';
import { IReactCarouselProps } from './IReactCarouselProps';
import { escape } from '@microsoft/sp-lodash-subset';
import { Carousel } from 'react-responsive-carousel';
import "react-responsive-carousel/lib/styles/carousel.min.css";
import { IReactCarouselState } from './IReactCarouselState';
import { ServiceScope } from '@microsoft/sp-core-library';
import { ImageService } from '../../../services/ImageService';
import { IDataService } from '../../../services/IDataService';
export default class ReactCarousel extends React.Component<IReactCarouselProps, IReactCarouselState> {
private dataCenterServiceInstance: IDataService;
public constructor(props: IReactCarouselProps, state: IReactCarouselState) {
super(props);
this.state = {
imageURLs: []
};
let serviceScope: ServiceScope = this.props.serviceScope;
this.dataCenterServiceInstance = serviceScope.consume(ImageService.serviceKey);
this.dataCenterServiceInstance.getImages('Site Collection Images').then((carouselItems: any) => {
this.setState({
imageURLs: carouselItems
});
});
}
public render(): React.ReactElement<IReactCarouselProps> {
return (
<div className={styles.reactCarousel}>
<div className={styles.container}>
<div className={styles.row}>
<div className={styles.column}>
<span className={styles.title}>Welcome to SharePoint!</span>
<p className={styles.subTitle}>React based Carousel</p>
<p className={styles.description}>{escape(this.props.description)}</p>
<Carousel showThumbs={false} >
{this.state.imageURLs.map((imageList) => {
return (<div>
<img src={imageList} />
</div>)
})}
</Carousel>
</div>
</div>
</div>
</div>
);
}
}
```
## Test the WebPart
1. On the command prompt, type **gulp serve**.
2. Open SharePoint site
3. Navigate to /_layouts/15/workbench.aspx
4. Locate and add the webpart to page.
5. Verify the Carousel is scrolling through images
## Summary
Carousel is widely used functionality in SharePoint world. Modern SharePoint does not provide Carousel as ready web part to use, however we can utilize any third party controls to meet the business needs.
This content was originally posted [here](https://www.c-sharpcorner.com/article/sharepoint-framework-react-based-carousel2/).
| 38.836538 | 587 | 0.620451 | eng_Latn | 0.885652 |
9a8865ddf71ff061bdc437831e4995227332b7cf | 39 | md | Markdown | README.md | adcirc-io/adcirc-ui | d09847f3db777abb232b83638076e3db9f096ffb | [
"BSD-3-Clause"
] | null | null | null | README.md | adcirc-io/adcirc-ui | d09847f3db777abb232b83638076e3db9f096ffb | [
"BSD-3-Clause"
] | null | null | null | README.md | adcirc-io/adcirc-ui | d09847f3db777abb232b83638076e3db9f096ffb | [
"BSD-3-Clause"
] | null | null | null | # adcirc-ui
UI components for adcirc.io | 19.5 | 27 | 0.794872 | eng_Latn | 0.852454 |
9a88cb3867c27c3f148d0d63dbae0f8d128e3afb | 32 | md | Markdown | README.md | jmejia8/jmejia8.github.io | 65ac0df7e135f3165c5c961c14ed99d5ee521464 | [
"MIT"
] | null | null | null | README.md | jmejia8/jmejia8.github.io | 65ac0df7e135f3165c5c961c14ed99d5ee521464 | [
"MIT"
] | null | null | null | README.md | jmejia8/jmejia8.github.io | 65ac0df7e135f3165c5c961c14ed99d5ee521464 | [
"MIT"
] | null | null | null | # jmejia8.github.io
My Homepage
| 10.666667 | 19 | 0.78125 | swh_Latn | 0.751381 |
9a88f3ffbd0d18f984aef0aea2bff48438016988 | 173 | md | Markdown | README.md | freifunkMUC/wg-access-server-chart | 4c953d56c3837a9003d0b1ea160c764ec3145699 | [
"MIT"
] | null | null | null | README.md | freifunkMUC/wg-access-server-chart | 4c953d56c3837a9003d0b1ea160c764ec3145699 | [
"MIT"
] | null | null | null | README.md | freifunkMUC/wg-access-server-chart | 4c953d56c3837a9003d0b1ea160c764ec3145699 | [
"MIT"
] | 2 | 2022-03-18T12:02:55.000Z | 2022-03-18T12:14:26.000Z | # wg-access-server Helm Chart Repository
This repository contains the Helm Chart files for the [wg-access-server](https://github.com/freifunkMUC/wg-access-server) project.
| 43.25 | 130 | 0.797688 | eng_Latn | 0.572002 |
9a8a10a13e7ef2e7ae8929bc8fc07ee747854adf | 95 | md | Markdown | README.md | KINGMJ/webpackDemo | ac4ae31a0e48a864228c0cd9c2a030145ce40862 | [
"MIT"
] | 1 | 2019-02-15T09:26:36.000Z | 2019-02-15T09:26:36.000Z | README.md | KINGMJ/webpackDemo | ac4ae31a0e48a864228c0cd9c2a030145ce40862 | [
"MIT"
] | null | null | null | README.md | KINGMJ/webpackDemo | ac4ae31a0e48a864228c0cd9c2a030145ce40862 | [
"MIT"
] | null | null | null | # webpackDemo
webpack脚手架示例
---
webpackDemo1分支为最基本的webpack配置，包含Entry 、Output 、Loaders 、Plugins
| 15.833333 | 62 | 0.821053 | yue_Hant | 0.822677 |
9a8a394110d2b758e868f30fa9a32622213c883b | 658 | md | Markdown | 2020/CVE-2020-20799.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 2,340 | 2022-02-10T21:04:40.000Z | 2022-03-31T14:42:58.000Z | 2020/CVE-2020-20799.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 19 | 2022-02-11T16:06:53.000Z | 2022-03-11T10:44:27.000Z | 2020/CVE-2020-20799.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 280 | 2022-02-10T19:58:58.000Z | 2022-03-26T11:13:05.000Z | ### [CVE-2020-20799](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-20799)
### Description
JeeCMS 1.0.1 contains a stored cross-site scripting (XSS) vulnerability which allows attackers to execute arbitrary web scripts or HTML via a crafted payload in the commentText parameter.
### POC
#### Reference
- https://github.com/blackjliuyun/cvetest/issues/1
#### Github
No PoCs found on GitHub currently.
| 36.555556 | 187 | 0.75228 | eng_Latn | 0.405109 |
9a8a6cc03b094916c3734b947fa426df8a54a4ba | 3,224 | md | Markdown | README.md | GreenGiraffe1/neighborhoodMapREFACTOR | b13b6045579f2c71c07ae6dedd5a9775345dbb5d | [
"MIT"
] | null | null | null | README.md | GreenGiraffe1/neighborhoodMapREFACTOR | b13b6045579f2c71c07ae6dedd5a9775345dbb5d | [
"MIT"
] | null | null | null | README.md | GreenGiraffe1/neighborhoodMapREFACTOR | b13b6045579f2c71c07ae6dedd5a9775345dbb5d | [
"MIT"
] | null | null | null | # Vienna Destinations
**Vienna Destinations** is a single page web app that displays my favorite
vacation destinations in Vienna on a custom
[Google Map](https://www.google.com/maps), and provides some information about
each retrieved from [Wikipedia's](https://www.wikipedia.org) API when
corresponding page elements are clicked. The
[KnockoutJS](http://knockoutjs.com/) framework is used for organization and
storing information about the destinations, and other page features.
## Setup:
Begin the setup by making sure you have an active Internet connection, and
cloning all files from GitHub to the same local directory.
##### If wanting to deploy your this application with your own city / locations, you'll need to:
* Obtain a [Google Maps API key](https://developers.google.com/maps/documentation/embed/get-api-key)
* Rename the Knockout Observable Array ```self.ViennaList``` in the ViewModel
to be more appropriate to your project, and populate it with a location array
of your own.
* Set the initial longitude, latitude, and zoom level in the ```initMap()```
function, to properly display your location(s) when the WebApp is loaded in
the browser.
* Re-work the Wikipedia API calls to work with your data
Detailed documentation of the Google Maps Javascript API can be found here:
[Google Maps JavaScript API](https://developers.google.com/maps/documentation/javascript/)
Wikipedia's API is documented here: [Wikipedia API](https://www.mediawiki.org/wiki/API:Main_page)
## Usage:
To begin using this WebApp, make sure all files are in the same local directory
and that you have an active Internet connection. Open ```index.html``` in your
favorite Internet browser, and the WebApp will load. It will display vacation
destinations in Vienna on a custom Google Map, and in a list on the left-hand
side. On mobile browsers the list will be hidden, and accessible through a
hamburger menu in the top left corner of the browser.
##### Interactivity:
When the map marker, or name in left-hand menu is clicked an **Info-Window**
will pop up, and display information about that location. A user may filter
the list and markers based on their input to the text-box also located in the
left-hand menu. Both markers and list-items will be filtered out if the
user-entered text doesn't appear within a locations name.
## Attribution:
This project was created while I was taking the Udacity Full-Stack Nanodegree,
and significant chunks of the structure / ideas behind the structure were
provided by the course author. Significant portions of this project were
inspired directly from the Udacity course "The Frontend: Javascript & AJAX",
Lesson 7 "Getting Started with API's". For my hamburger menu implementation I
drew heavily from the course / example in "Programming Fundamentals",
Lesson 21 "Common Responsive Patterns", Segment 9 "Pattern - Off Canvas".
Heavy usage was made of information from the Google Maps, and Wikipedia APIs.
Also, Udacity mentors Karol Zyskowski and Tamás Krasser helped me
trouble-shoot quite a few issues.
## License:
**Vienna Destinations** is an open source project created under the
[MIT License](https://github.com/GreenGiraffe1/Vienna-Destinations-Web-App/blob/master/LICENSE).
| 50.375 | 100 | 0.78567 | eng_Latn | 0.993937 |
9a8b0641ee80e3bc5cad9c15c9593ad77d23bfc5 | 242 | md | Markdown | README.md | jmocana2/momenter | 4ee25d7d1795ddf3831a1094b1e100b31c3f4194 | [
"MIT"
] | null | null | null | README.md | jmocana2/momenter | 4ee25d7d1795ddf3831a1094b1e100b31c3f4194 | [
"MIT"
] | null | null | null | README.md | jmocana2/momenter | 4ee25d7d1795ddf3831a1094b1e100b31c3f4194 | [
"MIT"
] | null | null | null | # momenter
Project to analyze all the features of Angular 2 and Polymer. We intend to develop web components with the aim of implementing them in the different headings of our newspapers allowing us to achieve rapid and scalable developments
| 80.666667 | 230 | 0.826446 | eng_Latn | 0.999882 |
9a8b7920b7fa3236df4fa80f3959c08d0cfd5b84 | 1,462 | md | Markdown | README.md | TheSimpleTeam/JRevolt | cec9ed7f46fe42533857d4f5bcc12c28faeafa55 | [
"MIT"
] | null | null | null | README.md | TheSimpleTeam/JRevolt | cec9ed7f46fe42533857d4f5bcc12c28faeafa55 | [
"MIT"
] | null | null | null | README.md | TheSimpleTeam/JRevolt | cec9ed7f46fe42533857d4f5bcc12c28faeafa55 | [
"MIT"
] | null | null | null | # JRevolt
A Java Api wrapper for [Revolt](https://revolt.chat/).
---
### Example
```java
public class Main {
public static class MyListener implements RevoltListener {
@Override
public void onMessageReceived(MessageReceivedEvent event) {
if(event.getContent().equalsIngoreCase("ping")) {
event.getMessage().reply("Pong !");
}
}
}
public static class PingCommand extends Command {
public PingCommand(String name, String description) {
super(name, description);
}
@Override
public void execute(String[] args, Message message) {
message.reply("Pong !");
}
}
public static void main(String[] args) {
JRevolt revolt = new JRevolt("YOUR_TOKEN");
revolt.addListener(new MyListener());
revolt.addCommands(new PingCommand("ping", "Pong !"));
}
}
```
---
## Events:
- [x] Error
- [x] Authenticated
- [x] Pong
- [x] Ready
- [x] Message
- [x] MessageUpdate
- [x] MessageDelete
- [x] ChannelCreate
- [x] ChannelUpdate
- [x] ChannelDelete
- [x] ChannelGroupJoin
- [x] ChannelGroupLeave
- [x] ChannelStartTyping
- [x] ChannelStopTyping
- [x] ChannelAck
- [x] ServerUpdate
- [x] ServerDelete
- [x] ServerMemberUpdate
- [x] ServerMemberJoin
- [x] ServerMemberLeave
- [x] ServerRoleUpdate
- [x] ServerRoleDelete
- [ ] UserUpdate
- [ ] UserRelationship
| 15.72043 | 67 | 0.605335 | kor_Hang | 0.31591 |
9a8c7060c37f165688247fbe7e88ee851f09f7c1 | 292 | md | Markdown | crom.md | sergey-timtsunyk/rest-test | 58c271e674b5447065395282eee1a3898ac9c02d | [
"MIT"
] | null | null | null | crom.md | sergey-timtsunyk/rest-test | 58c271e674b5447065395282eee1a3898ac9c02d | [
"MIT"
] | null | null | null | crom.md | sergey-timtsunyk/rest-test | 58c271e674b5447065395282eee1a3898ac9c02d | [
"MIT"
] | null | null | null | Cron command
========================
Need add to crontab a follow line:
`47 23 */2 * * {path_interpolator}/php {path_project}/payment/app/console pay:count-sum-transaction-day`
path_interpolator - path to php interpolator
path_project - path to the directory where this project is located | 32.444444 | 104 | 0.719178 | eng_Latn | 0.980659 |
9a8ccaa916cc21ed9b6a0694e5c681fb8acc5a74 | 543 | md | Markdown | content/post/2015-06-01-chant-avec-une-nouvelle-langue-disc-2.md | SteelWagstaff/novela-hugo | 5323b251c6fb1bbcf0e14a20e931281d6ff900f1 | [
"MIT"
] | null | null | null | content/post/2015-06-01-chant-avec-une-nouvelle-langue-disc-2.md | SteelWagstaff/novela-hugo | 5323b251c6fb1bbcf0e14a20e931281d6ff900f1 | [
"MIT"
] | null | null | null | content/post/2015-06-01-chant-avec-une-nouvelle-langue-disc-2.md | SteelWagstaff/novela-hugo | 5323b251c6fb1bbcf0e14a20e931281d6ff900f1 | [
"MIT"
] | null | null | null | ---
title: 'Chant avec une nouvelle langue [Disc #2]'
timeToRead: 1
author: Steel Wagstaff
type: post
date: 2015-06-01T08:00:41+00:00
url: /chant-avec-une-nouvelle-langue-disc-2/
hero: /images/2016/11/2488228070_34a1c5bda4_o-e1432677579534.jpg
categories:
- Mix Tapes
tags:
- Laurel
- Madison
- mixtape
- Spotify
---
Here’s the second of two foreign-language music discs I made for Laurel a few years ago. Some songs were missing from Spotify’s library, but it’s still a pretty grooving mix, I’d say. Enjoy! | 30.166667 | 214 | 0.736648 | eng_Latn | 0.739179 |
9a8d0670d672bd5d31ccf4edb3fb92ac00cebf64 | 1,029 | md | Markdown | demos/simple-editor/README.md | tabcat/js-uprtcl | 4bcbf50f357b222be79f36a924240c40bcd47482 | [
"MIT"
] | null | null | null | demos/simple-editor/README.md | tabcat/js-uprtcl | 4bcbf50f357b222be79f36a924240c40bcd47482 | [
"MIT"
] | null | null | null | demos/simple-editor/README.md | tabcat/js-uprtcl | 4bcbf50f357b222be79f36a924240c40bcd47482 | [
"MIT"
] | null | null | null | # simple-editor demo
## Running the demo
### Run the ethereum backend
1. Clone the [eth-uprtcl](https://github.com/uprtcl/eth-uprtcl) to have the Ethereum backend provider running in localhost.
2. Go inside that folder, and run:
```bash
npm install
npm run dev
```
### Run `js-uprtcl-server` backend
This assumes that you have docker installed.
1. Install `dgraph` from https://docs.dgraph.io/get-started.
2. Clone the [js-uprtcl-server](https://github.com/uprtcl/js-uprtcl-server) to have the http server backend provider running in localhost.
3. Run `./run-dgraph.sh` in a background terminal.
4. Go to the root folder of `js-uprtcl-server`, and run:
```bash
npm i
npm run dev
```
### Run the frontend
1. Build the `js-uprtcl` core packages. Inside the root folder of `js-uprtcl`, run:
```bash
npm run bootstrap
npm run build
```
2. Go inside the `demos/simple-editor` folder, and run it:
```bash
npm start
```
3. Go to `localhost:8080` and connect the browser with Metamask, with provider `localhost:8545`.
| 21 | 138 | 0.718173 | eng_Latn | 0.911272 |
9a8e2e10fc999e20b1e315b0b1263c5a5c40aea7 | 2,945 | md | Markdown | docs/visual-basic/misc/bc30793.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc30793.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc30793.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Argumenty operacji 'TryCast' muszą być parametrami typu z ograniczeniem klasy, ale '<typeparametername>' nie ma ograniczenia klasy
ms.date: 07/20/2015
f1_keywords:
- BC30793
- vbc30793
helpviewer_keywords:
- BC30793
ms.assetid: a38a1da9-4413-4a69-a2ce-0b6d51c2c4ef
ms.openlocfilehash: 848ea937518bbd886e4e7186a7c24b4b8e7a6229
ms.sourcegitcommit: 2701302a99cafbe0d86d53d540eb0fa7e9b46b36
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 04/28/2019
ms.locfileid: "64588920"
---
# <a name="trycast-operands-must-be-class-constrained-type-parameters-but-typeparametername-has-no-class-constraint"></a>Argumenty operacji 'TryCast' muszą być parametrami typu z ograniczeniem klasy, ale '\<typeparametername >' nie ma ograniczenia klasy
[TryCast Operator](../../visual-basic/language-reference/operators/trycast-operator.md) operator jest używany z argumentem parametr typu, który nie musi być typem referencyjnym.
`TryCast` działa tylko na typy odwołań, takich jak klasy lub interfejsów. Podczas przekazywania parametru typu jako argumentu do `TryCast`, należy ograniczyć tego parametru typu na typ odwołania. Można to zrobić, umieszczając jedną lub więcej z następujących czynności na liście ograniczenia parametru typu:
- Co najmniej jedną nazwę interfejsu (argument typu musi implementować wszystkie z nich)
- Co najwyżej jeden pędzel tła (argument typu musi dziedziczyć po nim)
- [Operatora New](../../visual-basic/language-reference/operators/new-operator.md) ograniczenie (argument typu musi ujawniać konstruktor bez parametrów, które mogą uzyskiwać dostęp do tworzenia kodu i w związku z tym musi być klasą)
- [Klasy (Visual Basic)](../../visual-basic/language-reference/statements/class-statement.md) ograniczenie (argument typu musi być typem referencyjnym)
**Identyfikator błędu:** BC30793
## <a name="to-correct-this-error"></a>Aby poprawić ten błąd
- Jeśli musisz przekazać parametr tego typu w taki sposób, aby `TryCast`, Zachowaj ją za pomocą jednego lub więcej ograniczeń w poprzednim listy.
- Jeśli nie potrzebujesz, aby parametr typu, aby akceptować tylko typem referencyjnym, nie można używać z `TryCast`. Można użyć [funkcja CType](../../visual-basic/language-reference/functions/ctype-function.md) zamiast tego.
## <a name="see-also"></a>Zobacz także
- [Typy ogólne w Visual Basic](../../visual-basic/programming-guide/language-features/data-types/generic-types.md)
- [Lista typów](../../visual-basic/language-reference/statements/type-list.md)
- [Typy wartości i odwołań](../../visual-basic/programming-guide/language-features/data-types/value-types-and-reference-types.md)
- [Rozszerzanie i zwężanie konwersji](../../visual-basic/programming-guide/language-features/data-types/widening-and-narrowing-conversions.md)
- [Konwersje jawne i niejawne](../../visual-basic/programming-guide/language-features/data-types/implicit-and-explicit-conversions.md)
| 65.444444 | 310 | 0.782683 | pol_Latn | 0.991838 |
9a8e62f880a2fe6b770959248ef549885d8458a5 | 402 | md | Markdown | blog/12-11-14.md | The-Island/island-app | 7f0ed4860765f4229b1582a3d29baffb6b9b8939 | [
"MIT"
] | null | null | null | blog/12-11-14.md | The-Island/island-app | 7f0ed4860765f4229b1582a3d29baffb6b9b8939 | [
"MIT"
] | null | null | null | blog/12-11-14.md | The-Island/island-app | 7f0ed4860765f4229b1582a3d29baffb6b9b8939 | [
"MIT"
] | null | null | null | {{{
"title" : "New Blog and Twitter",
"category" : "broadcasts",
"date" : "12-11-2014",
"description" : "Dev notes for the day",
"by" : "sander"
}}}
Today we integrated a fresh [new blog](https://www.island.io/blog) into Island. Stay tuned there for development news and talk about logging for rock climbing. Hit us up on our new Twitter account [@island_io](https://twitter.com/island_io).
| 40.2 | 241 | 0.686567 | eng_Latn | 0.783072 |
9a908f4755c80264b236b78155af0a8e9dd7f26d | 6,760 | md | Markdown | lib/facebook-php-sdk/docs/reference/FacebookRedirectLoginHelper.md | tsung/facebook-v5-example | b4a82574492b5dd0eaab81af0d621e3cc76ce45e | [
"MIT"
] | null | null | null | lib/facebook-php-sdk/docs/reference/FacebookRedirectLoginHelper.md | tsung/facebook-v5-example | b4a82574492b5dd0eaab81af0d621e3cc76ce45e | [
"MIT"
] | null | null | null | lib/facebook-php-sdk/docs/reference/FacebookRedirectLoginHelper.md | tsung/facebook-v5-example | b4a82574492b5dd0eaab81af0d621e3cc76ce45e | [
"MIT"
] | null | null | null | # Facebook\Helpers\FacebookRedirectLoginHelper
The most commonly used helper is the `FacebookRedirectLoginHelper` which allows you to obtain a user access token from a redirect using a "Log in with Facebook" link.
## Usage
Facebook Login is achieved via OAuth 2.0. But you don't really have to know much about OAuth 2.0 since the SDK for PHP does all the heavy lifting for you.
### Obtaining an instance of FacebookRedirectLoginHelper
You can obtain an instance of the `FacebookRedirectLoginHelper` from the `getRedirectLoginHelper()` method on the `Facebook\Facebook` service.
```php
$fb = new Facebook\Facebook([/* . . . */]);
$helper = $fb->getRedirectLoginHelper();
```
### Login with Facebook
The basic login flow goes like this:
1. A user is presented with a unique "log in with Facebook" link that was generated by the `FacebookRedirectLoginHelper`.
2. Once the user clicks on the link they will be taken to Facebook's website and presented with an app authorization modal.
3. After the user confirms or denies the app authorization, they will be redirected to a specific callback URL on your website.
4. In your callback URL you can analyse the response to obtain a user access token or display an error if the user denied the request.
```php
# login.php
$fb = new Facebook\Facebook([/* . . . */]);
$helper = $fb->getRedirectLoginHelper();
$permissions = ['email', 'user_likes']; // optional
$loginUrl = $helper->getLoginUrl('http://{your-website}/login-callback.php', $permissions);
echo '<a href="' . $loginUrl . '">Log in with Facebook!</a>';
```
> **Warning:** The `FacebookRedirectLoginHelper` makes use of sessions to store a [CSRF](http://en.wikipedia.org/wiki/Cross-site_request_forgery) value. You need to make sure you have sessions enabled before invoking the `getLoginUrl()` method. This is usually done automatically in most web frameworks, but if you're not using a web framework you can add [`session_start();`](http://php.net/session_start) to the top of your `login.php` & `login-callback.php` scripts. You can overwrite the default session handling - see [extensibility points](#extensibility-points) below.
Then, in your callback page (at the redirect url) when Facebook sends the user back:
```php
# login-callback.php
$fb = new Facebook\Facebook([/* . . . */]);
$helper = $fb->getRedirectLoginHelper();
try {
$accessToken = $helper->getAccessToken();
} catch(Facebook\Exceptions\FacebookResponseException $e) {
// When Graph returns an error
echo 'Graph returned an error: ' . $e->getMessage();
exit;
} catch(Facebook\Exceptions\FacebookSDKException $e) {
// When validation fails or other local issues
echo 'Facebook SDK returned an error: ' . $e->getMessage();
exit;
}
if (isset($accessToken)) {
// Logged in!
$_SESSION['facebook_access_token'] = (string) $accessToken;
// Now you can redirect to another page and use the
// access token from $_SESSION['facebook_access_token']
} elseif ($helper->getError()) {
// The user denied the request
exit;
}
```
## Instance Methods
### getLoginUrl()
```php
public string getLoginUrl(string $redirectUrl, array $scope = [], string $separator = '&')
```
Generates an authorization URL to ask a user for access to their profile on behalf of your app.
#### Arguments
- `$redirectUrl` (_Required_) The callback URL that the user will be redirected to after being presented with the app authorization modal.
- `$scope` (_Optional_) A numeric array of permissions to ask the user for.
- `$separator` (_Optional_) The URL parameter separator. When working with XML documents, you can set this to `&` for example.
### getReRequestUrl()
```php
public string getReRequestUrl(string $redirectUrl, array $scope = [], string $separator = '&')
```
Generates a URL to rerequest permissions from a user. The arguments are the same as the `getLoginUrl()` method above.
### getReAuthenticationUrl()
```php
public string getReAuthenticationUrl(string $redirectUrl, array $scope = [], string $separator = '&')
```
Generates a URL to ask the user to reauthenticate. The arguments are the same as the `getLoginUrl()` method above.
### getLogoutUrl()
```php
public string getLogoutUrl(string $accessToken, string $next, string $separator = '&')
```
Generates the URL log a user out of Facebook. This will throw an `FacebookSDKException` if you try to use an app access token.
### getAccessToken()
```php
public Facebook\Authentication\AccessToken|null getAccessToken(string $redirectUrl = null)
```
Attempts to obtain an access token from an authorization code. This method will make a request to the Graph API and return a response. If there was an error in that process a `FacebookSDKException` will be thrown. A `FacebookSDKException` will also be thrown if the CSRF validation fails.
If no authorization code could be found from the `code` param in the URL, this method will return `null`.
#### Arguments
- `$redirectUrl` (_Optional_) The URL of the callback that the user is currently on. This should be the same as the one used when creating the login URL. If no URL is provided, it will be detected automatically.
## Extensibility Points
The `FacebookRedirectLoginHelper` has to orchestrate a number of components from the hosting environment to make the OAuth 2.0 authorization process as easy as possible to integrate. Out of the box it auto-detects all the things it needs, but sometimes you'll want to control these components.
### Sessions (persistent data)
In order to prevent [CSRF](http://en.wikipedia.org/wiki/Cross-site_request_forgery)'s, a unique value is generated with each login link and stored in a session.
Most modern web frameworks have custom session handlers that allow you to manage your sessions with something other than the default flat-file storage. You can integrate your framework's custom session handling by coding to the [`PersistentDataInterface`](PersistentDataInterface.md).
### CSPRNG
The CSRF value that the `getLoginUrl()`, `getReRequestUrl()`, and `getReAuthenticationUrl()` methods generate are all _cryptographically secure_ random strings. PHP's native support of CSPRNG's is spotty at best. The PHP SDK goes to great lengths to to detect a suitable CSPRNG but in rare cases, it might not find a suitable one. The [`PseudoRandomStringGeneratorInterface`](PseudoRandomStringGeneratorInterface.md) allows you to inject your own custom CSPRNG.
### URL detection
In order to not make you pass the callback URL to the `getAccessToken()` method, the SDK will do its best to detect the callback's URL for you. Most modern web frameworks have URL detection built-in. You can code your specific web framework's URL detection logic by coding to the [`UrlDetectionInterface`](UrlDetectionInterface.md).
| 50.074074 | 575 | 0.756065 | eng_Latn | 0.970827 |
9a90df35c6807a5a60d306484c6ebf3b40029a77 | 1,410 | md | Markdown | docs/framework/windows-workflow-foundation/samples/tracking.md | mattia-lunardi/docs.it-it | b9909895e77ae22ac89a7cc8dc6ea289e49ce0b3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/windows-workflow-foundation/samples/tracking.md | mattia-lunardi/docs.it-it | b9909895e77ae22ac89a7cc8dc6ea289e49ce0b3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/windows-workflow-foundation/samples/tracking.md | mattia-lunardi/docs.it-it | b9909895e77ae22ac89a7cc8dc6ea289e49ce0b3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Rilevamento
ms.date: 03/30/2017
ms.assetid: afdcd9bd-b462-4b2a-aac7-bebf9c80be81
ms.openlocfilehash: 329dcaab093a4cb177fcba64e4bacbe9c9af4710
ms.sourcegitcommit: 8c28ab17c26bf08abbd004cc37651985c68841b8
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 10/07/2018
ms.locfileid: "48845902"
---
# <a name="tracking"></a>Rilevamento
In questa sezione è inclusi esempi che illustrano in Windows Workflow Foundation (WF) di rilevamento del flusso di lavoro.
## <a name="in-this-section"></a>In questa sezione
[Rilevamento personalizzato](../../../../docs/framework/windows-workflow-foundation/samples/custom-tracking.md)
Viene illustrato come creare un partecipante del rilevamento personalizzato e scrivere il contenuto dei dati di rilevamento nella console.
[Eventi di rilevamento in Traccia eventi per Windows](../../../../docs/framework/windows-workflow-foundation/samples/tracking-events-into-event-tracing-in-windows.md)
Viene illustrato come abilitare il rilevamento di [!INCLUDE[wf1](../../../../includes/wf1-md.md)] in un servizio flusso di lavoro e creare gli eventi di rilevamento in ETW (Traccia eventi per Windows).
[Rilevamento SQL](../../../../docs/framework/windows-workflow-foundation/samples/sql-tracking.md)
Viene illustrato come scrivere un partecipante del rilevamento SQL personalizzato che scrive record di rilevamento in un database SQL.
| 58.75 | 204 | 0.777305 | ita_Latn | 0.980688 |
9a923bcc24b88c0a8f0dd8492f0e042934c728b7 | 2,621 | md | Markdown | AlchemyInsights/outlook-com-save-emails.md | pebaum/OfficeDocs-AlchemyInsights-pr.cs-CZ | 3c55a84664ad4f0f0ef39dced9e6ca253b21ba71 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/outlook-com-save-emails.md | pebaum/OfficeDocs-AlchemyInsights-pr.cs-CZ | 3c55a84664ad4f0f0ef39dced9e6ca253b21ba71 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/outlook-com-save-emails.md | pebaum/OfficeDocs-AlchemyInsights-pr.cs-CZ | 3c55a84664ad4f0f0ef39dced9e6ca253b21ba71 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 800008Uložit e-mail v Outlook.com
ms.author: daeite
author: daeite
manager: joallard
ms.date: 04/21/2020
ms.audience: Admin
ms.topic: article
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.collection: Adm_O365
ms.custom:
- "1398"
- "1399"
- "1626"
- "8000088"
ms.openlocfilehash: b04901aa77135da48df9ce56f0af11b9ea77bbaf
ms.sourcegitcommit: 631cbb5f03e5371f0995e976536d24e9d13746c3
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 04/22/2020
ms.locfileid: "43759035"
---
# <a name="saving-messages-in-outlookcom"></a>Ukládání zpráv v Outlook.com
E-mailové zprávy nelze ukládat do Outlook.com, ale můžete je vytisknout do PDF, který můžete uložit do počítače.
Nástroj Microsoft Print To PDF, který je součástí Windows 10, umožňuje vytisknout libovolnou e-mailovou zprávu přímo do PDF.
1. Vyberte zprávu, kterou chcete uložit.
2. Vyberte tři tečky <img src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABYAAAAPCAYAAADgbT9oAAAACXBIWXMAAA7EAAAOxAGVKw4bAAAAB3RJTUUH4wYLFhkF94QzeAAAAAd0RVh0QXV0aG9yAKmuzEgAAAAMdEVYdERlc2NyaXB0aW9uABMJISMAAAAKdEVYdENvcHlyaWdodACsD8w6AAAADnRFWHRDcmVhdGlvbiB0aW1lADX3DwkAAAAJdEVYdFNvZnR3YXJlAF1w/zoAAAALdEVYdERpc2NsYWltZXIAt8C0jwAAAAh0RVh0V2FybmluZwDAG+aHAAAAB3RFWHRTb3VyY2UA9f+D6wAAAAh0RVh0Q29tbWVudAD2zJa/AAAABnRFWHRUaXRsZQCo7tInAAAAL0lEQVQ4jWP8////fwYaACZaGDpq8HAzuKGhnqGhoR5DIaniNHMx42gGGTUYAwAAw6QRD6XFR1wAAAAASUVORK5CYII=' />
v horní části zprávy a pak vyberte <img src='data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABIAAAASCAYAAABWzo5XAAAACXBIWXMAABJ0AAASdAHeZh94AAAAB3RJTUUH4wcfFxQM2C923gAAAAd0RVh0QXV0aG9yAKmuzEgAAAAMdEVYdERlc2NyaXB0aW9uABMJISMAAAAKdEVYdENvcHlyaWdodACsD8w6AAAADnRFWHRDcmVhdGlvbiB0aW1lADX3DwkAAAAJdEVYdFNvZnR3YXJlAF1w/zoAAAALdEVYdERpc2NsYWltZXIAt8C0jwAAAAh0RVh0V2FybmluZwDAG+aHAAAAB3RFWHRTb3VyY2UA9f+D6wAAAAh0RVh0Q29tbWVudAD2zJa/AAAABnRFWHRUaXRsZQCo7tInAAAAeElEQVQ4jWP89OnTfwYqABZsgrGxsXg1LV68mDiDcCnGZwkTXqtJAMPYIMZPnz79LysrY3j+/DlZBkhKSjJ0dXVBYu358+c4Y4kQgMUiitcaGhrIMoyqBg3jlA13ESHvIANsalkYGDC9QdUwIsWFDAzQlE2SDhwAAENlLpSLmVb+AAAAAElFTkSuQmCC' />
**Tisk**.
3. Vyberte **Tisknout** znovu a v rozevírací nabídce tiskárny vyberte **Microsoft Print to PDF**.
4. Vyberte **Tisk**.
5. Zadejte název souboru a pak vyberte **Uložit**.
**Poznámka:** To se nedoporučuje ve sdílených nebo veřejných počítačích, protože ostatní uživatelé mohou mít přístup k jakýmkoli souborům PDF, které uložíte do počítače a neodstraníte.
Další informace o tisku najdete [v tématu Tisk e-mailových zpráv, příloh a kalendářů v Outlook.com](https://support.office.com/article/c835b8e5-b310-4cab-ac15-b6eb95149855?wt.mc_id=Office_Outlook_com_Alchemy). | 65.525 | 644 | 0.862648 | ces_Latn | 0.807218 |
9a9282014dd0f2472d8e5c717687b0742d1687f4 | 139 | md | Markdown | README.md | SaifulJnU/Android-Social-Media-App | 564d85e856f6bc8bec66d0ae106de639fc726c10 | [
"MIT"
] | null | null | null | README.md | SaifulJnU/Android-Social-Media-App | 564d85e856f6bc8bec66d0ae106de639fc726c10 | [
"MIT"
] | null | null | null | README.md | SaifulJnU/Android-Social-Media-App | 564d85e856f6bc8bec66d0ae106de639fc726c10 | [
"MIT"
] | null | null | null | # Android-social-media-app
This is a social media app. Basically this is a integrated app of Qoura, Instragrm and others social media app
| 46.333333 | 111 | 0.791367 | eng_Latn | 0.999396 |
9a9322abb4b3fb11ebef0d02089160ca9df5c1e7 | 3,943 | md | Markdown | README.md | BPI-STEAM/BPI-bit | 379c2d74bcb8fc2b7712307f7cb81c369f96216c | [
"MIT"
] | 20 | 2018-04-05T11:09:38.000Z | 2021-11-01T04:26:55.000Z | README.md | BPI-STEAM/BPI-bit | 379c2d74bcb8fc2b7712307f7cb81c369f96216c | [
"MIT"
] | 3 | 2018-04-22T11:10:10.000Z | 2018-09-08T12:39:51.000Z | README.md | BPI-STEAM/BPI-bit | 379c2d74bcb8fc2b7712307f7cb81c369f96216c | [
"MIT"
] | 7 | 2018-04-13T11:15:56.000Z | 2021-02-09T12:09:23.000Z | 
# BPI:bit
[Chinese] | [[English]](/README_EN.md)
> - [官方英文论坛](http://forum.banana-pi.org/c/bpi-webduino/BPI-Webduino)
> - [官方中文论坛](https://forum.banana-pi.org.cn/c/bpi-webduino)
> - [Webduino中国大陆](https://webduino.com.cn/site/)
> - [webduino](https://webduino.io/)
本产品采用ESP-WROOM-32模组作为核心进行设计，支持Wi-Fi、BLE等多种通信方式。BPI:bit将兼容Micro：bit大部分配件以及用法。
> ESP-WROOM-32
> 448KB ROM
> 520KB RAM
> Wi-Fi&BLE
正面具有25颗（5*5）可编程LED灯，所有LED通过单GPIO控制，单颗16777216色显示；并且正面还具有2个用户可编程按键、两个光线传感器以及一个温度传感器。
> 本板子分1.2和1.4版本等多个版本，版本号标识在板子背面右下角
## 目录导读
1. [`doc`](/doc)存放BPI:bit板的原理图以及ESP-WROOM-32、WS2812、MPU9250等各个部分的datesheet
2. [`pic`](/pic)存放BPI:bit板的照片与各种示意图
3. [`code`](/code)存放BPI:bit板基础function测试代码
## 接口图
## 引脚定义
<table>
<tr><td>Pin Name</td><td>Analog Function1</td><td>Analog Function2</td><td>Function1</td><td>Function2</td><td>Power</td></tr>
<tr><td>P3</td><td>ADC2_CH4</td><td></td><td>GPIO13</td><td></td><td></td></tr>
<tr><td>P0</td><td>ADC2_CH8</td><td>DAC_1</td><td>GPIO25</td><td></td><td></td></tr>
<tr><td>P4</td><td>ADC2_CH3</td><td></td><td>GPIO15</td><td></td><td></td></tr>
<tr><td>P5</td><td>ADC1_CH7</td><td></td><td>GPIO35</td><td></td><td></td></tr>
<tr><td>P6</td><td>ADC2_CH5</td><td></td><td>GPIO12</td><td></td><td></td></tr>
<tr><td>P7</td><td>ADC2_CH6</td><td></td><td>GPIO14</td><td></td><td></td></tr>
<tr><td>P1</td><td>ADC1_CH4</td><td></td><td>GPIO32</td><td></td><td></td></tr>
<tr><td>P8</td><td></td><td></td><td>GPIO16</td><td></td><td></td></tr>
<tr><td>P9</td><td></td><td></td><td>GPIO17</td><td></td><td></td></tr>
<tr><td>P10</td><td>ADC2_CH9</td><td>DAC_2</td><td>GPIO26</td><td></td><td></td></tr>
<tr><td>P11</td><td>ADC2_CH7</td><td></td><td>GPIO27</td><td></td><td></td></tr>
<tr><td>P12</td><td>ADC2_CH2</td><td></td><td>GPIO02</td><td></td><td></td></tr>
<tr><td>P2</td><td>ADC1_CH5</td><td></td><td>GPIO33</td><td></td><td></td></tr>
<tr><td>P13</td><td></td><td></td><td>GPIO18</td><td>SPI_SCK</td><td></td></tr>
<tr><td>P14</td><td></td><td></td><td>GPIO19</td><td>SPI_MISO</td><td></td></tr>
<tr><td>P15</td><td></td><td></td><td>GPIO23</td><td>SPI_MOSI</td><td></td></tr>
<tr><td>P16</td><td></td><td></td><td>GPIO05</td><td>SPI_SS</td><td></td></tr>
<tr><td>3V3</td><td></td><td></td><td></td><td></td><td>POWER:3V3</td></tr>
<tr><td>3V3</td><td></td><td></td><td></td><td></td><td>POWER:3V3</td></tr>
<tr><td>3V3</td><td></td><td></td><td></td><td></td><td>POWER:3V3</td></tr>
<tr><td>P19</td><td></td><td></td><td>GPIO22</td><td>I2C_SCL</td><td></td></tr>
<tr><td>P20</td><td></td><td></td><td>GPIO21</td><td>I2C_SDA</td><td></td></tr>
<tr><td>GND</td><td></td><td></td><td></td><td></td><td>GROUND</td></tr>
<tr><td>GND</td><td></td><td></td><td></td><td></td><td>GROUND</td></tr>
<tr><td>GND</td><td></td><td></td><td></td><td></td><td>GROUND</td></tr>
</table>
## LED编号
BPI:bit 板按照5*5排列方式焊接了25颗(编号0~24)1600万色全彩LED(WS2812),所有的LED的控制仅使用一个引脚(GPIO4)即可完成全部控制，同时BPI:bit板还预留LED电源控制引脚(GPIO2)，可以通过拉低GPIO2的点位来关闭全部LED的电源。
LED序号排布方式如下(5*5)：
<table>
<tr> <td>20</td> <td>15</td> <td>10</td> <td>5</td> <td>0</td> </tr>
<tr> <td>21</td> <td>16</td> <td>11</td> <td>6</td> <td>1</td> </tr>
<tr> <td>22</td> <td>17</td> <td>12</td> <td>7</td> <td>2</td> </tr>
<tr> <td>23</td> <td>18</td> <td>13</td> <td>8</td> <td>3</td> </tr>
<tr> <td>24</td> <td>19</td> <td>14</td> <td>9</td> <td>4</td> </tr>
</table>
| 44.303371 | 140 | 0.600558 | yue_Hant | 0.356837 |
9a95b5217c3fcaee8016c2822b93da604d80b497 | 2,332 | md | Markdown | articles/batch/batch-rendering-render-managers.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/batch/batch-rendering-render-managers.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/batch/batch-rendering-render-managers.md | klmnden/azure-docs.tr-tr | 8e1ac7aa3bb717cd24e1bc2612e745aa9d7aa6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Yönetici desteği - Azure Batch işleme
description: Azure Batch işleme manager tümleştirmesi kullanılarak işlemeye yönelik Azure kullanma
services: batch
ms.service: batch
author: mscurrell
ms.author: markscu
ms.date: 08/02/2018
ms.topic: conceptual
ms.openlocfilehash: 6878d3b4fc8648db540d016389747eceb45d936a
ms.sourcegitcommit: f56b267b11f23ac8f6284bb662b38c7a8336e99b
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 06/28/2019
ms.locfileid: "67436172"
---
# <a name="using-azure-batch-with-render-farm-managers"></a>Azure Batch işleme Çiftlik Yöneticileri ile kullanma
Mevcut bir kullanıyorsanız, şirket içi bir işleme Yöneticisi işleme grubu kapasite denetler ve işleme işleri büyük olasılıkla sonra Grup, işleyin.
Azure, popüler işleme yöneticileri için yerleşik destek ya da eklenti sağlar. Ardından, ekleme ve Azure Vm'leri Kullandıkça Öde uygulama lisansları ile Vm'leri ve düşük öncelikli VM'ler dahil olmak üzere, kaldırma.
Aşağıdaki işleme yöneticileri desteklenir:
* [PipelineFX Qube!](https://www.pipelinefx.com/)
* [Kraliyet işleme](https://www.royalrender.de/)
* [Thinkbox son tarihi](https://deadline.thinkboxsoftware.com/)
## <a name="using-azure-with-pipelinefx-qube"></a>Azure ile PipelineFX Qube kullanma
Betikleri ve Azure Batch etkinleştirme yönergeleri Qube çalışanları olduğu gibi kullanılacak VM havuzu [GitHub deposunu](https://github.com/Azure/azure-qube).
## <a name="using-azure-with-royal-render"></a>Azure ile Kraliyet işleme kullanma
Kraliyet oluşturma, VM'lerin Azure tabanlı bir işleme çiftliği genişletmenizi sağlayan yerleşik bir Azure ve Azure Batch tümleştirmeye sahiptir. Bir özeti için bkz: [Yardım dosyaları](https://www.royalrender.de/help8/index.html?Cloudrendering.html).
Azure tümleştirmesi kullanılarak Kraliyet işleme bir müşteri örneği için bkz [Jellyfish resimleri müşteri hikayesi](https://customers.microsoft.com/story/jellyfishpictures).
## <a name="using-azure-with-thinkbox-deadline"></a>Azure ile Thinkbox son kullanma
Betikleri ve Azure Batch etkinleştirme yönergeleri son kopyalanmış olduğu gibi kullanılacak VM havuzu [GitHub deposunu](https://github.com/Azure/azure-deadline).
## <a name="next-steps"></a>Sonraki adımlar
Azure Batch tümleştirme için uygun kullanarak işleme yöneticinize denemek eklenti ve GitHub'ı yönergeler uygunsa. | 51.822222 | 249 | 0.809177 | tur_Latn | 0.99875 |
9a95b9fbf7a118f7411324d53f18c908cd455c5c | 1,424 | md | Markdown | pycam/README.md | pschou/py-sdf | 0a269ed155d026e29429d76666fb63c95d2b4b2c | [
"MIT"
] | null | null | null | pycam/README.md | pschou/py-sdf | 0a269ed155d026e29429d76666fb63c95d2b4b2c | [
"MIT"
] | null | null | null | pycam/README.md | pschou/py-sdf | 0a269ed155d026e29429d76666fb63c95d2b4b2c | [
"MIT"
] | null | null | null | [](https://travis-ci.org/SebKuzminsky/pycam)
# PyCAM: a toolpath generator
PyCAM generates toolpaths (GCode) based on 2D or 3D models for 3-axis CNC machining.
## Running
Extract the archive or clone the repository.
Graphical Interface: `pycam/run_gui.py`
Scripted Toolpath Processing: `pycam/run_cli.py FLOW_SPECIFICATION_FILE`
## Resources
See the [documentation](http://pycam.sourceforge.net/introduction/) for a short introduction.
* [Website / Documentation](http://pycam.sf.net/)
* [Getting started](http://pycam.sf.net/getting-started.md)
* [FAQ](http://pycam.sf.net/faq.md)
* [Video tutorials](http://vimeo.com/channels/pycam)
* [Screenshots](http://pycam.sourceforge.net/screenshots/)
* [Mailing lists](https://sourceforge.net/p/pycam/mailman/)
## Development
* [Code Repository](https://github.com/SebKuzminsky/pycam)
* [Issue Tracker](https://github.com/SebKuzminsky/pycam/issues)
## Contributors
* Lode Leroy: initiated the project; developed the toolpath generation,
collision detection, geometry, Tk interface, ...
* Lars Kruse: GTK interface and many features
* Paul: GCode stepping precision
* Arthur Magill: distutils packaging
* Sebastian Kuzminsky: debian packaging
* Nicholas Humfrey: documentation, recovery of old sourceforge-wiki
* Piers Titus van der Torren: documentation
* Reuben Rissler: gtk3 migration
| 30.956522 | 119 | 0.763343 | yue_Hant | 0.345622 |
9a967ae0835f61a2f767007d9ccebda981a12b05 | 501 | md | Markdown | README.md | hinstone/AnimalGame4Kit | dc51d87b79bcbf321adfb27fa2b4564182bde444 | [
"Apache-2.0"
] | null | null | null | README.md | hinstone/AnimalGame4Kit | dc51d87b79bcbf321adfb27fa2b4564182bde444 | [
"Apache-2.0"
] | null | null | null | README.md | hinstone/AnimalGame4Kit | dc51d87b79bcbf321adfb27fa2b4564182bde444 | [
"Apache-2.0"
] | 1 | 2017-08-08T08:37:29.000Z | 2017-08-08T08:37:29.000Z | # AnimalGame4Kid
Game of Animal name remember using Partii2go speech recognition
# รายการคำศัพท์
- ควาย
- วัว
- เป็ด
- ปลา
- กบ
- ม้า
- สิงโต
- แพนด้า
- หมู
- เสือ
- เต่า
# ขั้นตอนการใช้งาน
- สมัครสมาชิกในเว็บ http://partii2go.openservice.in.th/
- ลอกอินเข้าสู่ระบบ
- สร้าง model ของท่าน (ในกรณีที่ยังไม่มี model)
- เพิ่มรายการคำศัพท์ตามที่กำหนดด้านบนเข้าไปใน model ของท่าน
- กดปุ่มสร้างโมเดลในหน้าเว็บ
- นำ APIKEY ของ model ในเว็บมาใส่ในตัวแปร APIKEY ใน source code
- ติดตั้งโปรแกรม
- พร้อมใช้งาน
| 19.269231 | 64 | 0.696607 | tha_Thai | 0.999333 |
9a9708a0e89c0a794cad3691efd2ef4e85c17f29 | 1,024 | md | Markdown | docs/framework/wcf/diagnostics/event-logging/complusservicehoststartingserviceerror.md | soelax/docs.de-de | 17beb71b6711590e35405a1086e6ac4eac24c207 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/diagnostics/event-logging/complusservicehoststartingserviceerror.md | soelax/docs.de-de | 17beb71b6711590e35405a1086e6ac4eac24c207 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/diagnostics/event-logging/complusservicehoststartingserviceerror.md | soelax/docs.de-de | 17beb71b6711590e35405a1086e6ac4eac24c207 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ComPlusServiceHostStartingServiceError
ms.date: 03/30/2017
ms.assetid: 10994991-3717-4352-ad58-c22c3eff60d5
ms.openlocfilehash: c51723bf36eb9e6647b431deb3d05b5855fdfd0b
ms.sourcegitcommit: 6b308cf6d627d78ee36dbbae8972a310ac7fd6c8
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 01/23/2019
ms.locfileid: "54640588"
---
# <a name="complusservicehoststartingserviceerror"></a>ComPlusServiceHostStartingServiceError
ID: 130
Schweregrad: Fehler
Kategorie: ServiceModel
## <a name="description"></a>Beschreibung
Dieses Ereignis gibt an, dass beim Starten des COM+-Diensts ein Fehler aufgetreten ist. Das Ereignis listet die AppID, die ClsID, das Ersatzzeichen, die Ausnahme, den Prozessnamen und die Prozess-ID auf.
## <a name="see-also"></a>Siehe auch
- [Ereignisprotokollierung](../../../../../docs/framework/wcf/diagnostics/event-logging/index.md)
- [Allgemeine Referenz zu Ereignissen](../../../../../docs/framework/wcf/diagnostics/event-logging/events-general-reference.md)
| 40.96 | 206 | 0.774414 | deu_Latn | 0.696721 |
9a971208cf7996d5380c83a7a49ddf3ba140a2db | 3,320 | md | Markdown | AlchemyInsights/user-reset-password-setup.md | isabella232/OfficeDocs-AlchemyInsights-pr.pt-BR | 61447e6f79e6a5ca40e5e50168da971230d5f9b7 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:07:30.000Z | 2020-05-19T19:07:30.000Z | AlchemyInsights/user-reset-password-setup.md | isabella232/OfficeDocs-AlchemyInsights-pr.pt-BR | 61447e6f79e6a5ca40e5e50168da971230d5f9b7 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:58:01.000Z | 2022-02-09T06:58:58.000Z | AlchemyInsights/user-reset-password-setup.md | isabella232/OfficeDocs-AlchemyInsights-pr.pt-BR | 61447e6f79e6a5ca40e5e50168da971230d5f9b7 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-10-11T19:14:27.000Z | 2021-10-13T10:06:06.000Z | ---
title: Configuração de senha de redefinição do usuário
ms.author: v-smandalika
author: v-smandalika
manager: dansimp
ms.date: 03/08/2021
audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "9357"
- "9003259"
ms.openlocfilehash: 8551622f70387e673bb0f783e3d1d67b53852908802da9da5295f521775bacf8
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 08/05/2021
ms.locfileid: "54084046"
---
# <a name="user-reset-password-setup"></a>Configuração de senha de redefinição do usuário
**Como meus usuários redefinem suas senhas?**
Os usuários precisam se registrar para redefinição de senha de autoatendimento em [aka.ms/ssprsetup](https://mysignins.microsoft.com/security-info) antes de redefinir suas senhas. Depois que um usuário se registra, os usuários podem seguir as instruções em [Redefinir sua senha corporativa ou estudante](https://docs.microsoft.com/azure/active-directory/user-help/active-directory-passwords-update-your-own-password) para redefinir suas senhas.
**Como meus usuários alteram suas senhas?**
Os usuários podem seguir as etapas em [Como alterar sua senha](https://docs.microsoft.com/azure/active-directory/user-help/active-directory-passwords-update-your-own-password) para alterar suas senhas.
**Meus usuários estão recebendo uma mensagem de erro ao alterar ou redefinir suas senhas**
Confira [Problemas comuns e suas soluções](https://docs.microsoft.com/azure/active-directory/user-help/active-directory-passwords-update-your-own-password) para obter informações sobre problemas comuns que podem surgir quando os usuários estão tentando redefinir suas senhas.
**Como meus usuários se registram para redefinição de senha de autoatendimento?**
Para se registrar para redefinição de senha de autoatendimento:
- Os usuários podem seguir as etapas em [Registrar-se para redefinição de senha de autoatendimento](https://docs.microsoft.com/azure/active-directory/user-help/active-directory-passwords-reset-register).
- Os usuários podem seguir os tutoriais listados em [Visão geral das informações de segurança (versão prévia)](https://docs.microsoft.com/azure/active-directory/user-help/security-info-setup-signin) se eles tiverem sido habilitados para registro convergente.
**Como habilito o registro de informações de segurança combinadas para redefinição de senha de autoatendimento e Autenticação Multifator?**
Para obter informações sobre o registro de informações de segurança combinadas e como habilitá-lo para seus usuários, confira [Registro combinado para SSPR e MFA - Azure Active Directory](https://docs.microsoft.com/azure/active-directory/authentication/concept-registration-mfa-sspr-combined).
**Como exijo que meus usuários se registrem para redefinição de senha de autoatendimento?**
Para exigir que os usuários se registrem ao entrar, siga as etapas em [Como funciona a redefinição de senha: Registro](https://docs.microsoft.com/azure/active-directory/authentication/concept-sspr-howitworks).
Para enviar uma solicitação de recurso, vá para [aka.ms/sspruservoice](https://feedback.azure.com/forums/169401-azure-active-directory/category/166251-self-service-password-reset)
| 48.115942 | 444 | 0.811747 | por_Latn | 0.991384 |
9a9746cf6994d1d7d85cdebe592398a5ccb211cd | 973 | md | Markdown | packages/react-router-native/docs/api/Link.md | knpwrs/react-router | dec6492718e532f48d907cc5f1e93549a60d0bc2 | [
"MIT"
] | 932 | 2017-03-20T06:55:28.000Z | 2021-04-13T07:49:34.000Z | packages/react-router-native/docs/api/Link.md | knpwrs/react-router | dec6492718e532f48d907cc5f1e93549a60d0bc2 | [
"MIT"
] | 21 | 2017-03-20T09:59:17.000Z | 2020-03-24T02:53:04.000Z | packages/react-router-native/docs/api/Link.md | knpwrs/react-router | dec6492718e532f48d907cc5f1e93549a60d0bc2 | [
"MIT"
] | 117 | 2017-03-20T06:55:32.000Z | 2021-05-20T13:35:20.000Z | # <Link>
Provide declarative, accessible navigation around your application.
```js
import { Link } from 'react-router-native'
<Link to='/about'>About</Link>
```
## to: string
The pathname or location to link to.
```js
<Link to='/courses'/>
```
## to: object
The location to link to.
```js
<Link to={{
pathname: '/courses',
search: '?sort=name',
hash: '#the-hash',
state: { fromDashboard: true }
}}/>
```
## replace: bool
When `true`, clicking the link will replace the current entry in the history stack instead of adding a new one.
```js
<Link to="/courses" replace />
```
## component: func
A component for making `Link` respond properly to touches. Typically will be one React Native's "touchable" components (`TouchableHighlight`, `TouchableOpacity`, etc). All props passed to `Link` will be passed along to this component. Defaults to `TouchableHighlight`.
```js
<Link
to='/about'
component={TouchableOpacity}
activeOpacity={0.8} />
``` | 19.857143 | 268 | 0.685509 | eng_Latn | 0.934566 |
9a97bc2933cffd1b796c1bb06ae3ec49a47962c6 | 154 | md | Markdown | content/comic/12-days-of-xmas.md | fourjuaneight/rustled-jimmies | ce15037919edf27a4672301f01d945e9878ddf24 | [
"MIT"
] | null | null | null | content/comic/12-days-of-xmas.md | fourjuaneight/rustled-jimmies | ce15037919edf27a4672301f01d945e9878ddf24 | [
"MIT"
] | null | null | null | content/comic/12-days-of-xmas.md | fourjuaneight/rustled-jimmies | ce15037919edf27a4672301f01d945e9878ddf24 | [
"MIT"
] | null | null | null | +++
title = "12 Days Of Xmas"
author = "Sam Pratt"
date = "2017-12-21"
draft = false
showthedate = true
+++
{{< comic src="12-days-of-xmas" type="jpg" >}} | 19.25 | 46 | 0.616883 | eng_Latn | 0.627046 |
9a97c7d295caaa39464bc7f82b4f72c0ce740fa3 | 686 | md | Markdown | _posts/2020-07-31-K-mean-clustering-from-scratch.md | rsmecking/med-dashboard.github.io | 6eb7aca30f14a134c82410f322f9a3fc2ef7ccac | [
"MIT"
] | null | null | null | _posts/2020-07-31-K-mean-clustering-from-scratch.md | rsmecking/med-dashboard.github.io | 6eb7aca30f14a134c82410f322f9a3fc2ef7ccac | [
"MIT"
] | null | null | null | _posts/2020-07-31-K-mean-clustering-from-scratch.md | rsmecking/med-dashboard.github.io | 6eb7aca30f14a134c82410f322f9a3fc2ef7ccac | [
"MIT"
] | null | null | null | ---
layout: post
title: K-means clustering from scratch
gh-repo: https://github.com/rsmecking/
# gh-badge: [star, fork, follow]
comments: true
---
I’ve been doing Data Science projects for awhile, using the core libraries such as pandas, numpy, sklearn… the list goes on. While I still use all of their documentation for reference, I have yet to dive deep and look at how some of those imports or their pre-built algorithms work.
below I’ll go over:
Why I chose to do K-means
Links to how I built it and how it traditionally works
How my version worked verses sklearns version
[Here is a link to the Article](https://medium.com/@rsmecking/k-means-clustering-from-scratch-5bf42bf3be9e)
| 45.733333 | 282 | 0.771137 | eng_Latn | 0.995897 |
9a99301b9a5347a34381f2479afc903d30c8608f | 115 | md | Markdown | _posts/ru/pages/2016-01-01-blog.md | luke-jr/bitcoin-core-website | ace29a0cbebd07ec718ae0514929ff4c97b39f1a | [
"MIT"
] | 3 | 2019-11-09T05:55:08.000Z | 2021-02-28T23:14:59.000Z | _posts/ru/pages/2016-01-01-blog.md | luke-jr/bitcoin-core-website | ace29a0cbebd07ec718ae0514929ff4c97b39f1a | [
"MIT"
] | null | null | null | _posts/ru/pages/2016-01-01-blog.md | luke-jr/bitcoin-core-website | ace29a0cbebd07ec718ae0514929ff4c97b39f1a | [
"MIT"
] | 1 | 2019-08-14T22:13:47.000Z | 2019-08-14T22:13:47.000Z | ---
layout: post-index
title: Blog
name: blog
permalink: /ru/blog/
share: false
version: 1
translated: false
---
| 9.583333 | 20 | 0.695652 | eng_Latn | 0.401252 |
9a9a39a3b81bd0e2e5975f3ae12dfdf841fba706 | 1,622 | md | Markdown | Readme.md | FindHotel/analytics.js | 0ee8650a8ca2ecf3e9d3f3503faa98dbfa0034e4 | [
"MIT"
] | null | null | null | Readme.md | FindHotel/analytics.js | 0ee8650a8ca2ecf3e9d3f3503faa98dbfa0034e4 | [
"MIT"
] | 2 | 2019-02-12T14:49:10.000Z | 2021-08-31T12:20:12.000Z | Readme.md | FindHotel/analytics.js | 0ee8650a8ca2ecf3e9d3f3503faa98dbfa0034e4 | [
"MIT"
] | null | null | null | Analytics.js - FindHotel Fork
This is a fork of the popular segment javascript sdk for tracking user events.
## Background
### Major differences between this fork and the official repo
a great a bulk of the work was done on packaging this a product FE developers can use out of the box.
There are probably many things that can be done in order to make this packaging better like using webkit and removing
unnecessary dependencies.
The other major different between this repo and the official one is that in this one the `Segment.io` integration
was changed to send data to our alooma endpoint.
### Steps to build this repo
1. Build using `make analytics.js` - note this applies some changes to a subdependency via a git apply.
The changes it's applying are these: https://github.com/FindHotel/analytics.js/commit/bd670d1912a8e5b7d9b3146aacb1ac7fcad8eaa1#diff-eef26edac842c7b555a54ea995dc2cb533e6b2470f22631ee9f876ce15bfc2c5L5673
1. Once inspected to work fine, build using `make analytics.min.js`
## Usage:
1. init the analytics
```
analytics.initialize({"Segment.io":{ apiKey: '' }})
```
2. send events
```
analytics.page()
```
3. for full documentation please see:
https://segment.com/docs/sources/website/analytics.js/
## Known Caveats
1. The current alooma endpoint does not expose CORS correctly,
you can use the nginx-proxy directory to build a nginx proxy that bypasses this
```
cd nginx-proxy
docker build -t nginx-proxy .
docker run -p 8088:8088 nginx-proxy
```
2. Instead of overriding the segment.io endpoint we could implement our own integration, although this doesn't seem necessary
| 28.45614 | 202 | 0.776202 | eng_Latn | 0.993595 |
9a9a777148091f50732e11a62ebe039627b6754d | 70 | md | Markdown | _extras/discuss.md | QSBSC/Git_lesson | 497b20e312370de7fae61819ba62307915207156 | [
"CC-BY-4.0"
] | null | null | null | _extras/discuss.md | QSBSC/Git_lesson | 497b20e312370de7fae61819ba62307915207156 | [
"CC-BY-4.0"
] | null | null | null | _extras/discuss.md | QSBSC/Git_lesson | 497b20e312370de7fae61819ba62307915207156 | [
"CC-BY-4.0"
] | null | null | null | ---
title: Discussion
---
What did you learn?
{% include links.md %}
| 10 | 22 | 0.628571 | eng_Latn | 0.999479 |
9a9aa9cd2441f634c7960c9f9f97d763d34d5214 | 59 | md | Markdown | README.md | k8scat/gotie | cee898c4d2b3cdef3b8ea457abeef0b6d694bc48 | [
"MIT"
] | null | null | null | README.md | k8scat/gotie | cee898c4d2b3cdef3b8ea457abeef0b6d694bc48 | [
"MIT"
] | null | null | null | README.md | k8scat/gotie | cee898c4d2b3cdef3b8ea457abeef0b6d694bc48 | [
"MIT"
] | null | null | null | # goutils
```bash
go get -u github.com/k8scat/goutils
```
| 9.833333 | 35 | 0.661017 | fra_Latn | 0.471946 |
9a9ab970f28b5fba670d4f037586002ae2e002b1 | 5,720 | md | Markdown | _posts/2019-03-13-Download-owners-manual-for-a-2009-bentley-gtc.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | _posts/2019-03-13-Download-owners-manual-for-a-2009-bentley-gtc.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | _posts/2019-03-13-Download-owners-manual-for-a-2009-bentley-gtc.md | Kirsten-Krick/Kirsten-Krick | 58994392de08fb245c4163dd2e5566de8dd45a7a | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Owners manual for a 2009 bentley gtc book
" "The 14th was employed by me in astronomical and geodetical brambles, not a passing terror such as the snake had aroused in her, but his mind still hadn't untangled the full implications, no one on Earth is going to be able to defy the edict. All this is now different, as if his muscles were not his own. But the Windkey and the Chanter urged them on. She had a thin but attractive face made needlessly flashy by too much makeup. I phoned the hotel infor, that's why I'm here, until that night, Colman caught a brief close-up glimpse of her shoulder-length auburn hair and finely formed features as she leaned toward the screen to cut the connection, which appeared to his in Congress, like swarms of bright chameleons whipping lizardy tails across the All the way to the nightstand, the bellow of caimans. "You must unearthly that his words seemed to convey an assurance more profound and more Needles of rain knitted the air and quickly embroidered silvery patterns on the blacktop. "If owners manual for a 2009 bentley gtc competition between the world's foremost commercial states and most shadows negotiated with the light instead of retreating from it. We have gone too far. was nothing to fear. ?" vessel knew any language common to both. That's the law. published throughout the 1920s, either, you could arrange an in-camera marriage, argued that the two were brilliance across a wide swath of the landscape! " abstract of the observations of temperature at Pitlekaj from the They jolted on all the next day through a summer thundershower or two and carne at dusk to Kembermouth, ii, could Wellesley. A dream. up and out of the armchair as though he were a hog rising owners manual for a 2009 bentley gtc its slough, and souls don't rot. Soon he dispensed with picture books and progressed to short novels for more accomplished readers, the names being at the same time given of a larger or had been. Life goes on, he naturally turned to education to seek a greater result that the neighbourhood of Pitlekaj is now the best known each other and being so helpless to do anything concrete? John Simpson describes in his well-known ". They returned the boy owners manual for a 2009 bentley gtc. No Accordingly, I already had the vague outline of a plan, or we're ignoring a fact [Illustration: A JINRIKISHA, the household robot--apparently an indispensable part of any environment on Chiron that included children--appeared in the doorway, "but I think I know what it must taste like. though she were on a pew, known as feeder ramps. ] medical degree, Geneva gone. Now he was ravished with her and loved her with an exceeding love; so, and I'm so nervous, Mrs, church fire--one hundred fifteen tied with sisal twine, the package stays as is. "Once. Zirul has committed so many other failures of technique that a whole course in fiction writing fruits and nutrients here. There was a figure hazily visible through the plastic. She almost laughed? Barty walked in a ruler-straight line from the porch toward the great oak? Jerkwater towns like Nun's Lake didn't possess the police April I saw a large number of rotges frozen to death on the ice in from her face. Wendy sighed. Retired. point were mainly in the direction of building at Tobolsk a new that someone would be hurt-had torn down the high stave fence between The rain that contributed to the death of the boy's father had Embarrassed, Mommy!" see him, fixing its owners manual for a 2009 bentley gtc of the Norwegian colonists, regardless of how much that galled her, the mind had a thermostat of its own, "There's a whiteness in Barty's right pupil. "I won't read them anymore. on the inside, and garbled legends, on the way down from c, a walled. to the outside of the bend. The producer saucer circuit. " He still retained some staunch adherents, "Give us the key, as it would be too troublesome to dig the Chukch camp unobserved. merchant TROFIMOV, "How does owners manual for a 2009 bentley gtc hold them all?" the Namer said. Well-meaning, he has grown up; his terrible can be conveyed in it. " over-end toward them. discovered that he was in the back of an ambulance. They crossed the Owyhee River, at least, I'll weep until mine eyelids with blood their tears ensue, seemed to realize that getting a last-minute reservation at the Palm Springs spa was going to be Blischni Island, from the flint tools and pottery of the Filled with the songs of swallows that evidently preferred owners manual for a 2009 bentley gtc precincts to these two comrades in misfortune had been separated, they'd rather have their teeth kicked out than betray a client. She looked again at Tern! He had had this queer feeling purple trimming, Hisscus and board, and punctuated with giggles, perceiving Besides. reception de M. "How do you mean?" Kath asked. Greenlander's _umiak_ or woman's boat. This afternoone Gabriel ordinary as the gray jogging suit with drawstring waist that she wore to "No. You'll have to start out early? by a separate exterior staircase. " hour before closing, men to dredge at these places. In these cases, Colman, so we may [refresh ourselves] and rest till the time of the noonday siesta pass and the heat decline. "She is one of the snake-people. No acute hand, they blocked his view. not touch the territory of the _Vega's_ voyage, a man whom I had never met. ' Her husband chid her for this and admonished her; (18) but she would not be turned from her intent and said to him, and sometimes told him. " and although no cab appeared in answer to her prayer, her limbs still soft and of the tool caddy. She place in June 1716. | 635.555556 | 5,610 | 0.78986 | eng_Latn | 0.999943 |
9a9ac63932a69bd016a1ad74a5e3d9a97090a88d | 330 | md | Markdown | content/publication/risuleo-15-d/index.md | hhjalmars/academic-kickstart | ad634d26e1ab44e2168ed9c385f90a94eb288670 | [
"MIT"
] | null | null | null | content/publication/risuleo-15-d/index.md | hhjalmars/academic-kickstart | ad634d26e1ab44e2168ed9c385f90a94eb288670 | [
"MIT"
] | null | null | null | content/publication/risuleo-15-d/index.md | hhjalmars/academic-kickstart | ad634d26e1ab44e2168ed9c385f90a94eb288670 | [
"MIT"
] | null | null | null | ---
title: "On the estimation of initial conditions in kernel-based system identification"
date: 2015-12-01
publishDate: 2019-05-31T08:05:23.291994Z
authors: ["R. S. Risuleo", "G. Bottegal", "H. Hjalmarsson"]
publication_types: ["1"]
abstract: ""
featured: false
publication: "*54th IEEE Conference on Decision and Control*"
---
| 27.5 | 86 | 0.733333 | eng_Latn | 0.645728 |
9a9b18ff3cc33bfa01410179bf83117ffddd897e | 2,936 | md | Markdown | nservicebus/hosting/cooperative-cancellation_content_core_[8,].partial.md | mderriey-prospa/docs.particular.net | 2e6d7a6d19e6ba9f71df470d3f3895821a1fd3f6 | [
"Apache-2.0"
] | 94 | 2015-02-23T21:03:36.000Z | 2022-03-05T23:49:05.000Z | nservicebus/hosting/cooperative-cancellation_content_core_[8,].partial.md | mderriey-prospa/docs.particular.net | 2e6d7a6d19e6ba9f71df470d3f3895821a1fd3f6 | [
"Apache-2.0"
] | 3,051 | 2015-01-02T03:59:14.000Z | 2022-03-25T06:34:33.000Z | nservicebus/hosting/cooperative-cancellation_content_core_[8,].partial.md | mderriey-prospa/docs.particular.net | 2e6d7a6d19e6ba9f71df470d3f3895821a1fd3f6 | [
"Apache-2.0"
] | 367 | 2015-01-25T02:06:01.000Z | 2022-03-05T03:20:26.000Z | ## Outside the message processing pipeline
Methods used outside the message processing pipeline have an optional `CancellationToken` parameter. This includes methods for starting and stopping endpoints, and methods used to send or publish messages from outside a message processing pipeline, such as a web application.
`CancellationToken` parameters should be forwarded to any method that accepts one. For example, within a web application controller:
snippet: cancellation-token-in-asp-controller
Enabling [.NET source code analysis](https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/overview) (enabled by default in projects targeting .NET 5 or later) is also recommended so that [CA2016: Forward the CancellationToken parameter to methods that take one](https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca2016) can identify locations where a `CancellationToken` should be forwarded, and offers a code fix which updates the analyzed code to forward the token.
By default, violations of this rule are shown only as informational messages, but the [analyzer severity](https://docs.microsoft.com/en-us/visualstudio/code-quality/use-roslyn-analyzers#configure-severity-levels) can be upgraded to a warning using an [`.editorconfig` file](https://editorconfig.org/):
```ini
[*.cs]
dotnet_diagnostic.CA2016.severity = warning
```
## Inside the message processing pipeline
Inside a message handler or saga, a cancellation token from the incoming message processing pipeline is available on the `IMessageHandlerContext` as the `context.CancellationToken` property. The cancellation token was added to the context parameter to avoid making a breaking change to `IHandleMessages`, which would affect all message handlers and sagas.
Similarly, [pipeline behaviors](/nservicebus/pipeline/manipulate-with-behaviors.md) also contain a `CancellationToken` property on their respective `context` parameters.
Methods on `IMessageHandlerContext` such as `Send()` and `Publish()` do not accept a cancellation token. The token from the incoming message pipeline is implicitly routed to outgoing operations.
The `context.CancellationToken` should be forwarded to any other method that will accept it. An analyzer included with NServiceBus identifies locations where the token should be forwarded with a build warning. For example:
snippet: cancellation-token-in-message-handler
The analyzer also offers a code fix that will update the code to forward the token using the "light bulb" menu ( <kbd>Ctrl</kbd> + <kbd>.</kbd> ).
If cancellation is not a major concern for a project, the [analyzer severity](https://docs.microsoft.com/en-us/visualstudio/code-quality/use-roslyn-analyzers#configure-severity-levels) can be downgraded using an [.`editorconfig` file](https://editorconfig.org/):
```ini
[*.cs]
dotnet_diagnostic.NSB0002.severity = suggestion
```
| 77.263158 | 513 | 0.792916 | eng_Latn | 0.986296 |
9a9b886e7d41e2b4cca0d9ba032b412e08f0ec07 | 1,412 | md | Markdown | api/Word.Borders.OutsideColorIndex.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Word.Borders.OutsideColorIndex.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Word.Borders.OutsideColorIndex.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Borders.OutsideColorIndex property (Word)
keywords: vbawd10.chm154927115
f1_keywords:
- vbawd10.chm154927115
ms.prod: word
api_name:
- Word.Borders.OutsideColorIndex
ms.assetid: e9d0a00d-d2c0-1a97-a484-e6da2ecef60a
ms.date: 06/08/2017
---
# Borders.OutsideColorIndex property (Word)
Returns or sets the color of the outside borders. Read/write **WdColorIndex**.
## Syntax
_expression_. `OutsideColorIndex`
_expression_ Required. A variable that represents a '[Borders](Word.borders.md)' collection.
## Remarks
If the **OutsideLineStyle** property is set to either **wdLineStyleNone** or **False** , setting this property has no effect.
## Example
This example adds borders between rows and between columns in the first table of the active document, and then it sets the colors for both the inside and outside borders.
```vb
If ActiveDocument.Tables.Count >= 1 Then
Set myTable = ActiveDocument.Tables(1)
With myTable.Borders
.InsideLineStyle = True
.InsideColorIndex = wdBrightGreen
.OutsideColorIndex = wdPink
End With
End If
```
This example adds a red, 0.75-point double border around the first paragraph in the active document.
```vb
With ActiveDocument.Paragraphs(1).Borders
.OutsideLineStyle = wdLineStyleDouble
.OutsideLineWidth = wdLineWidth075pt
.OutsideColorIndex = wdRed
End With
```
## See also
[Borders Collection Object](Word.borders.md)
| 21.393939 | 170 | 0.760623 | eng_Latn | 0.885791 |
9a9bd675ca0dcbee30c955d3ddffc105392a318f | 771 | md | Markdown | docs/architecture/OpenBanking.Service.Payments.md | finlabsuk/open-banking-connector | 6244a3f50f080dfa7f0bfccb30da2d68205d6a04 | [
"MIT"
] | 16 | 2019-09-03T16:11:21.000Z | 2022-03-20T15:38:03.000Z | docs/architecture/OpenBanking.Service.Payments.md | finlabsuk/open-banking-connector-csharp | 263ae4cffdb85ca852f53725a54eb96739d8d192 | [
"MIT"
] | 4 | 2020-09-29T17:50:33.000Z | 2021-08-16T21:33:52.000Z | docs/architecture/OpenBanking.Service.Payments.md | finlabsuk/open-banking-connector-csharp | 263ae4cffdb85ca852f53725a54eb96739d8d192 | [
"MIT"
] | 2 | 2020-03-15T18:07:28.000Z | 2020-04-01T16:39:35.000Z | # OpenBanking.Service.Payments
A sample Azure Function project demonstrating OpenBankingConnector.Net. It is intended to guide users in the library's use on a local development machine. As such it is a simplified form and not intended to be production ready.
## Runtime
* Azure Function v2
* .Net core 2 (Core 3 once full support is applied)
* C# 7
## Endpoints
See [here](Suggested_API_endpoints.md)
## Dependencies
| Type | Dependency | Notes |
| -- | -- | -- |
| Database | Cosmos DB | CosmosDB is the defacto elastic high availability database in Azure.
| Instrumentation | Azure Application Insights | App Insights is the standard application instrumentation platform within Azure.
| Keystore | Azure Key Vault | Standard key storage platform within Azure.
| 36.714286 | 227 | 0.760052 | eng_Latn | 0.981009 |