hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
e05cd1530112e1df3611dbcfd4e6912e4cf034e8 | 4,821 | md | Markdown | business-central/design-details-active-versus-historic-item-tracking-entries.md | MicrosoftDocs/dynamics365smb-docs-pr.de-at | b0eb0b81121f257c8272d66cd8dea9dfd8738f35 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2017-08-28T10:38:25.000Z | 2021-04-20T21:13:46.000Z | business-central/design-details-active-versus-historic-item-tracking-entries.md | MicrosoftDocs/dynamics365smb-docs-pr.de-at | b0eb0b81121f257c8272d66cd8dea9dfd8738f35 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | business-central/design-details-active-versus-historic-item-tracking-entries.md | MicrosoftDocs/dynamics365smb-docs-pr.de-at | b0eb0b81121f257c8272d66cd8dea9dfd8738f35 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Design-Details – Aktive versus historische Elemente zur Verfolgung von Einträgen
description: Wenn Teile einer Beleg-Zeilen-Menge gebucht werden, wird nur diese Menge in die Artikel-Ledger-Einträge und ihre Artikelverfolgungsnummern übertragen.
author: SorenGP
ms.service: dynamics365-business-central
ms.topic: conceptual
ms.devlang: na
ms.tgt_pltfrm: na
ms.workload: na
ms.search.keywords: ''
ms.date: 06/15/2021
ms.author: edupont
ms.openlocfilehash: 167a765774d365a7890fa39a20923ab0c78e53a4
ms.sourcegitcommit: e562b45fda20ff88230e086caa6587913eddae26
ms.translationtype: HT
ms.contentlocale: de-AT
ms.lasthandoff: 06/30/2021
ms.locfileid: "6326155"
---
# <a name="design-details-active-versus-historic-item-tracking-entries"></a>Designdetails: Aktive vs. historische Artikelverfolgungsposten
Wenn Teile einer Belegzeilenmenge gebucht werden, wird nur diese bestimmte Menge in Artikelposten und deren Artikelverfolgungsnummern übertragen. Jedoch möchten Sie sicher auf alle relevanten Nachverfolgungsinformationen des Artikels direkt aus der aktiven Belegzeile heraus zugreifen. Anders ausgedrückt, Sie möchten nicht nur die Posten, die mit der Restmenge verbunden sind, sondern Sie wünschen auch Informationen über die gebuchten Einheiten. Wenn Sie die Seite **Artikelverfolgungszeilen** anzeigen oder ändern, werden die Kollektivinhalte der Tabelle **Verfolgungsspezifikation** (T336) und der Tabelle **Reservierungsposten** (T337) in einer temporären Version von T336 dargestellt. Dadurch ist sichergestellt, dass auf historische und aktive Artikelverfolgungsdaten als Einheit zugegriffen wird.
Die nachstehende Tabelle zeigt, wie T336 und T337 in einem Einkaufsszenario verwendet werden. Die fettgedruckten Zahlen stellen Werte dar, die der Benutzer manuell auf der **Artikelnachverfolgungszeilen**-Seite eingibt.
Schritt 1: Erstellen Sie eine Einkaufszeile von sieben Stück mit Artikelverfolgungsnummern.
||**Menge (Basis)**|**Bewegungsmge.**|**Zu fakturieren (Basis)**|**Geb. Bewegungsmenge (Basis)**|**Bereits berech. Menge (Basis)**|
|-|----------------------------------------------|--------------------------------------------|------------------------------------------------------|-------------------------------------------------------|--------------------------------------------------------|
|**T337**|7|0|0|0|0|
|**T336**|0|0|0|0|0|
Schritt 2: Empfangen Sie vier Teile.
||**Menge (Basis)**|**Bewegungsmge.**|**Zu fakturieren (Basis)**|**Geb. Bewegungsmenge (Basis)**|**Bereits berech. Menge (Basis)**|
|-|----------------------------------------------|--------------------------------------------|------------------------------------------------------|-------------------------------------------------------|--------------------------------------------------------|
|**Logistik Artikelverf.-Zeilen** Seite|7|**4**|**0**|0|0|
|**T337**|3|0|0|0|0|
|**T336**|4|0|0|4|0|
Schritt 3: Empfangen Sie zwei Teile, und fakturieren Sie zwei Teile.
||**Menge (Basis)**|**Bewegungsmge.**|**Zu fakturieren (Basis)**|**Geb. Bewegungsmenge (Basis)**|**Bereits berech. Menge (Basis)**|
|-|----------------------------------------------|--------------------------------------------|------------------------------------------------------|-------------------------------------------------------|--------------------------------------------------------|
|**Logistik Artikelverf.-Zeilen** Seite|7|**2**|**2**|4|0|
|**T337**|1|0|0|0|0|
|**T336**|6|0|0|6|2|
Schritt 4: Empfangen Sie ein Stück.
||**Menge (Basis)**|**Bewegungsmge.**|**Zu fakturieren (Basis)**|**Geb. Bewegungsmenge (Basis)**|**Bereits berech. Menge (Basis)**|
|-|----------------------------------------------|--------------------------------------------|------------------------------------------------------|-------------------------------------------------------|--------------------------------------------------------|
|**Logistik Artikelverf.-Zeilen** Seite|7|**1**|**0**|6|2|
|**T336**|7|0|0|7|2|
Fakturieren von 5 Stück.
||**Menge (Basis)**|**Bewegungsmge.**|**Zu fakturieren (Basis)**|**Geb. Bewegungsmenge (Basis)**|**Bereits berech. Menge (Basis)**|
|-|----------------------------------------------|--------------------------------------------|------------------------------------------------------|-------------------------------------------------------|--------------------------------------------------------|
|**Logistik Artikelverf.-Zeilen** Seite|7|0|**5**|7|2|
|**T336**|7|0|0|7|7|
## <a name="see-also"></a>Siehe auch
[Designdetails: Artikelnachverfolgung](design-details-item-tracking.md)
[Designdetails – Artikelverfolgungszeilenfenster-Seite](design-details-item-tracking-lines-window.md)
[!INCLUDE[footer-include](includes/footer-banner.md)] | 71.955224 | 806 | 0.537233 | deu_Latn | 0.707764 |
e05d2f79ae4409dd5336eea2a4edd9e59c4dbef8 | 301 | md | Markdown | ru/ydb/reference/ydb-sdk/example/_includes/steps/08_scan_query.md | vadamlyuk/docs | 3cffa8176b1427fd4181b3c6bfb6d4a46caf071e | [
"CC-BY-4.0"
] | null | null | null | ru/ydb/reference/ydb-sdk/example/_includes/steps/08_scan_query.md | vadamlyuk/docs | 3cffa8176b1427fd4181b3c6bfb6d4a46caf071e | [
"CC-BY-4.0"
] | null | null | null | ru/ydb/reference/ydb-sdk/example/_includes/steps/08_scan_query.md | vadamlyuk/docs | 3cffa8176b1427fd4181b3c6bfb6d4a46caf071e | [
"CC-BY-4.0"
] | null | null | null | ---
sourcePath: ru/ydb/ydb-docs-core/ru/core/reference/ydb-sdk/example/_includes/steps/08_scan_query.md
---
## Скан запросы {#scan-query}
Результатом выполнения [скан запроса](../../../../../concepts/scan_query.md) является стрим данных. Далее приведен пример обработки результата такого запроса.
| 43 | 158 | 0.747508 | rus_Cyrl | 0.437678 |
e05d3a742d782423860a206a719637da2a5d05c4 | 16,310 | md | Markdown | Agile/spotifycasestudy.md | uk-gov-mirror/SkillsFundingAgency.das-technical-guidance | 95ca67ee87f5e5ca7f7168acff25a49d3e4c4fb5 | [
"MIT"
] | 1 | 2020-04-07T10:05:29.000Z | 2020-04-07T10:05:29.000Z | Agile/spotifycasestudy.md | uk-gov-mirror/SkillsFundingAgency.das-technical-guidance | 95ca67ee87f5e5ca7f7168acff25a49d3e4c4fb5 | [
"MIT"
] | 8 | 2020-05-04T15:25:32.000Z | 2021-04-08T13:47:27.000Z | Agile/spotifycasestudy.md | uk-gov-mirror/SkillsFundingAgency.das-technical-guidance | 95ca67ee87f5e5ca7f7168acff25a49d3e4c4fb5 | [
"MIT"
] | 3 | 2020-04-20T10:22:28.000Z | 2021-06-28T21:26:18.000Z | ---
layout: default
title: "Spotify Case Study"
---
# Case Study - Spotify
> [There is No Spotify Model](https://www.infoq.com/presentations/spotify-culture-stc/)
As with any case study the goal is not to replicate exactly what is seen but rather to take inspiration from and choose those parts that fit into our organisation and extend it further with our own ideas and practices.
Our culture is not the same as the Spotify culture that created this model, if we try to emulate it verbatim we will likely end in failure.
## Squads
The basic unit at Spotify is the squad
A Squad is similar to a Scrum team, and is designed to feel like a mini-startup. They sit together, and they have all the skills and tools needed to design, develop, test, and release to production. They are a self-organizing team and decide their own way of working – some use Scrum sprints, some use Kanban, some use a mix of these approaches.
Each squad has a long-term mission such as building and improving the Android client, creating the Spotify radio experience, scaling the backend systems, or providing payment solutions. The picture below
illustrates how different squads take responsibility for different parts of the user experience.
Squads are encouraged to apply Lean Startup principles such as MVP (minimum viable product) and validated learning. MVP means releasing early and often, and validated learning means using metrics and
A/B testing to find out what really works and what doesn’t. This is summarized in the slogan “Think it, build it, ship it, tweak it”.
Because each squad sticks with one mission and one part of the product for a long time, they can really become experts in that area - for example what it means to build an awesome radio experience.
Most squads have an awesome workspace including a desk area, a lounge area, and a personal "huddle" room. Almost all walls are whiteboards. We've never seen a better collaboration space!
To promote learning and innovation, each squad is encouraged to spend roughly 10% of their time on “hack days”. During hack days people do whatever they want, typically trying out new ideas and sharing with their buddies. Some teams do 1 hack day every second week, others save up for a whole “hack week”. Hack days are not only fun, they are also a great way to stay up-to-date with new tools and techniques and
sometimes lead to important product innovations! A squad doesn’t have a formally appointed squad leader, but it does have a product owner. The product owner is responsible for prioritizing the work to be done by the team, but is not involved with how they do their work. The product owners of different squads collaborate with each other to maintain a high-level roadmap document that shows where Spotify as a whole is heading, and each product owner is responsible for maintaining a matching product backlog for their squad.
A squad also has access to an agile coach, who helps them evolve and improve their way of working. The coaches run retrospectives, sprint planning meetings, do 1-on-1 coaching, etc.
Ideally each squad is fully autonomous with direct contact with their stakeholders, and no blocking dependencies to other squads. Basically a mini-startup. With over 30 teams, that is a challenge! We have come a long way, but there are still plenty of improvements to be made. To aid in this, we run a quarterly survey with each squad. This helps focus our improvement efforts and find out what kind of organizational support is needed. Here’s a visual summary of one such survey, showing 5
squads within a tribe:
_The circles show the current state, arrows show the trend. For example we can see a pattern where three
squads reports problems around releasing and that it does not seem to improve - this area needs urgent
focus! We also see that squad 4 does not have a great situation with agile coach support, but that it is
already improving._
* Product owner - The squad has a dedicated product owner that prioritizes the work and takes both
business value and tech aspects into consideration.
* Agile coach - The squad has an agile coach that helps them identify impediments and coaches
them to continuously improve their process.
* Influencing work - Each squad member can influence his/her work, be an active part in planning
and choose which tasks to work on. Every squad member can spend 10% of his/her time on hack
days.
* Easy to release - The squad can (and does!) get stuff live with minimal hassle and sync.
* Process that fits the team - The squad feels ownership of their process and continuously improves
it.
* Mission - The squad has a mission that everyone knows and cares about, and stories on the
backlog are related to the mission.
* Organizational support - The squad knows where to turn to for problem solving support, for
technical issues as well as “soft” issues.
## Tribes
A tribe is a collection of squads that work in related areas – such as the music player, or backend
infrastructure.
The tribe can be seen as the “incubator” for the squad mini-startups. , and have a fair degree of freedom and autonomy. Each tribe has a tribe lead who is responsible for providing the best possible habitat for the
squads within that tribe. The squads in a tribe are all physically in the same office, normally right next to each other, and the lounge areas nearby promote collaboration between the squads.
Tribes are sized based on the concept of the “Dunbar number”, which says that most people cannot maintain a social relationship with more than 100 people or so (the number is actually larger for groups that
are under intense survival pressure, which isn’t really the case at Spotify, believe it or not...). When groups get too big, we start seeing more things like restrictive rules, bureaucracy, politics, extra layers of management, and other waste.
So tribes are designed to be smaller than 100 people or so.
Tribes hold gatherings on a regular basis, an informal get-together where they show the rest of the tribe (or whoever shows up) what they are working on, what they have delivered and what others can learn from
what they are currently doing. This includes live demos of working software, new tools and techniques, cool hack-day projects, etc.
## Squad Dependencies
With multiple squads there will always be dependencies. Dependencies are not necessarily bad - squads sometimes need to work together to build something truly awesome. Nevertheless, our goal is to have
squads be as autonomous as possible, especially minimizing dependencies that are blocking or slowing a squad down.
To aid in this, we regularly ask all our squads which other squads they depend on, and to what extent those dependencies are blocking or slowing the squad down. Here’s an example:
We then discuss ways to eliminate the problematic dependencies, especially blocking and cross-tribe dependencies. This often leads to reprioritization, reorganization, architectural changes or technical
solutions.
The survey also helps us see patterns around how squads depend on each other - for example that more and more squads seems to be slowed down by operations. We use a simple graph to track how the various
types of dependencies increase or decrease over time.
Scrum has a practice called “scrum of scrums”, a synchronization meeting where one person from each
team meets to discuss dependencies. We don’t usually do scrum of scrums at Spotify, mainly because most of the squads are fairly independent and don’t need such a coordination meeting.
Instead, scrum of scrums happens “on demand”. For example we recently had a large project that required the coordinated work of multiple squads for a few months.
To make this work, the teams had a daily sync meeting where they identified and resolved dependencies between the squads, and used a board with sticky notes to keep track of unresolved dependencies.
A common source of dependency issues at many companies is development vs operations. Most companies we’ve worked with have some kind of a handoff from dev to ops, with associated friction and
delays.
At Spotify there is a separate operations team, but their job is not to make releases for the squads - their job is to give the squads the support they need to release code themselves;; support in the form of
infrastructure, scripts, and routines. They are, in a sense, “building the road to production”.
It’s an informal but effective collaboration, based on face-to-face communication rather than detailed process documentation.
## Chapters and guilds
There is a downside to everything, and the potential downside to full autonomy is a loss of economies of scale. The tester in squad A may be wrestling with a problem that the tester in squad B solved last week. If
all testers could get together, across squads and tribes, they could share knowledge and create tools for the benefit of all squads.
If each squad was fully autonomous and had no communication with other squads, then what is the point of having a company? Spotify might as well be chopped into 30 different small companies.
That’s why we have Chapters and Guilds. This is the glue that keeps the company together, it gives us some economies of scale without sacrificing too much autonomy.
The chapter is your small family of people having similar skills and working within the same general competency area, within the same tribe.
Each chapter meets regularly to discuss their area of expertise and their specific challenges - for example the testing chapter, the web developer chapter or the backend chapter.
The chapter lead is line manager for his chapter members, with all the traditional responsibilities such as developing people, setting salaries, etc. However, the chapter lead is also part of a squad and is involved in the day-to-day work, which helps him stay in touch with reality.
Now, reality is always messier than pretty pictures like the one above. For example, chapter members are not evenly distributed across the squads;; some squads have lots of web developers, some have none. But
the picture should give you the general idea.
A Guild is a more organic and wide-reaching “community of interest”, a group of people that want to share knowledge, tools, code, and practices. Chapters are always local to a Tribe, while a guild usually cuts across the whole organization. Some examples are: the web technology guild, the tester guild, the agile coach guild, etc.
A guild often includes all the chapters working in that area and their members, for example the testing guild includes all the testers in all testing chapters, but anybody who is interested can join any guild.
Each guild has a “guild coordinator” who, well, does just that :o)
As an example of guild work, we recently had a “Web Guild Unconference”, an open space event where all web developers at Spotify gathered up in Stockholm to discuss challenges and solutions within their field.
Another example is the agile coach guild. The coaches are spread all over the organization, but share knowledge continuously and meet regularly to collaborate on the high level organizational improvement
areas, which we track on an improvement board.
*Wait a sec, isn’t this just a matrix org?*
Yes. Well, sort of. It’s a different type of matrix than what most of us are used to though.
In many matrix organizations people with similar skills are “pooled” together into functional departments, and “assigned” to projects, and “report to” a functional manager.
Spotify rarely does any of this. Our matrix is weighted towards delivery.
That is, people are grouped into stable co-located squads, where people with different skill sets collaborate and self-organize to deliver a great product. That’s the vertical dimension in the matrix, and it is the primary one since that is how people are physically grouped and where they spend most of their time.
The horizontal dimension is for sharing knowledge, tools, and code. The job of the chapter lead is to facilitate and support this.
In matrix terms, think of the vertical dimension as “what” and the horizontal dimension as “how”. The matrix structure ensures that each squad member can get guidance on “what to build next” as well as “how to build it well”.
This matches the “professor and entrepreneur” model recommended by Mary and Tom Poppendieck. The PO is the “entrepreneur” or “product champion”, focusing on delivering a great product, while the chapter lead is the “professor” or “competency leader”, focusing on technical excellence.
There is a healthy tension between these roles, as the entrepreneur tends to want to speed up and cut corners, while the professor tends to want to slow down and build things properly. Both aspects are needed,
that’s why it is a “healthy” tension.
## What about architecture?
Spotify technology is highly service-oriented. We have over 100 distinct systems, and each can be maintained and deployed separately. This includes backend services such as playlist management or
search or payment, and clients such as the iPad player, and specific components such as the radio, or the “what’s new” section of the music player.
Technically, anyone is allowed to edit any system. Since the squads are effectively feature teams, they normally need to update multiple systems to get a new feature into production.
The risk with this model is that the architecture of a system gets messed up if nobody focuses on the integrity of the system as a whole.
To mitigate this risk, we have a role called “System Owner”. All systems have a system owner, or a pair of system owners (we encourage pairing). For operationally critical systems, the System Owner is a Dev-Ops pair – that is, one person with a developer perspective and one person with an operations perspective.
The system owner is the “go to” person(s) for any technical or architectural issues related to that system.
He is a coordinator and guides people who code in that system to ensure that they don’t stumble over each other. He focuses on things like quality, documentation, technical debt, stability, scalability, and release process.
The System Owner is not a bottleneck or ivory tower architect. He does not personally have to make all decisions, or write all code, or do all releases. He is typically a squad member or chapter lead who has other day-to-day responsibilities in addition to the system ownership.
However, from time to time he will take a “system owner day” and do housekeeping work on that system. Normally we try to keep this system
ownership to less than a tenth of a person’s time, but it varies a lot between systems of course.
We also have a chief architect role, a person who coordinates work on high-level architectural issues that cut across multiple systems. He reviews development of new systems to make sure they avoid common mistakes, and that they are aligned with our architectural vision. The feedback is always just suggestions and input - the decision for the final design of the system still lies with the squad building it.
## How is this all working out?
Spotify has grown very fast - over 3 years we have grown from 30 to 250 people in tech - so we have our share of growth pain! This scaling model – with Squads, Tribes, Chapters, and Guilds – is something that
was introduced gradually over the past year, so people are still getting used to it. But so far, based on surveys and retrospectives, the scaling model seems to be working quite well! And it gives us something to “grow into”. Despite the fast growth the employee satisfaction has continuously increased;; in April 2012 it
was 4.4 out of 5.
However, as with any growing organization, today’s solutions give birth to tomorrow’s problems. So stay tuned, the story isn’t over :o)
/Henrik & Anders
[email protected]
[email protected] | 80.742574 | 526 | 0.792581 | eng_Latn | 0.999951 |
e05d99024d31152d231f2006d930a896f915f2a0 | 7,670 | md | Markdown | README.md | testigos2022/colombia | 71f91fb3fee8f35d3321c08b154a1b6c84d5811c | [
"MIT"
] | 1 | 2022-03-15T04:55:53.000Z | 2022-03-15T04:55:53.000Z | README.md | testigos2022/colombia | 71f91fb3fee8f35d3321c08b154a1b6c84d5811c | [
"MIT"
] | null | null | null | README.md | testigos2022/colombia | 71f91fb3fee8f35d3321c08b154a1b6c84d5811c | [
"MIT"
] | 1 | 2021-09-24T04:18:54.000Z | 2021-09-24T04:18:54.000Z | English version below
# Testigos electorales Colombia 2022
Este es un sistema que permite construir un registro instantáneo e inmutable de votos. Se usará en las elecciones de Presidente y Congreso 2022-2026 en Colombia. Los registros son creados con reportes de testigos electorales.
# Contexto
El Consejo de Estado ha indicado que el software que se usa en Colombia para contabilizar los votos de las elecciones es fraudulento. En mayo 2022 hay elecciones de Presidente y Congreso en Colombia. Por lo tanto, se espera que haya un nuevo fraude electoral.
Más información en:
- https://www.lasillavacia.com/historias/silla-nacional/reglas-electorales-clave-para-la-oposicion-no-alcanzaran-a-aplicarse-en-2022/
- https://pares.com.co/2018/04/27/asi-se-roban-las-elecciones-en-colombia/
- https://www.semana.com/elecciones-presidenciales2018/candidatos-elecciones-presidencia-2018/articulo/polemica-por-auditoria-al-software-de-la-registraduria/568155/
# Problema
En Colombia, el conteo de votos se hace en tres etapas:
- Conteo en mesas de votación.
- Consolidado por zonas de votación (sumatoria de mesas).
- Consolidado por municipios (sumatoria de zonas).
Hay pruebas que indican que el conteo registrado en cada una de las etapas de conteo no coincide con los votos registrados en las otras etapas. Para los testigos electorales es imposible identificar estas inconsistencias en el momento en que se hace el conteo porque hay demasiada información que tienen que verificar en pocas horas.
# Solución
Crear un registro de los votos registrados en cada mesa de votación, usando información reportada por los testigos electorales. El reporte de los testigos ubicados en cada mesa de votación será accesible inmediatamente para los testigos zonales. De la misma forma, los reportes creados por los testigos zonales serán accesibles inmediatamente para los testigos municipales. De esta forma, se automatizará parte del trabajo de los testigos electorales y se garantizará que el conteo que se hace en todas las etapas sea consistente.
Además, la aplicación permitirá tomar fotografías de los documentos oficiales que se usan durante el conteo de votos (formularios E-14 y E-24). Estas fotos podrán ser usadas por los testigos zonales y municipales para hacer reclamos durante el día de las elecciones. Así mismo, las fotografías podrán ser usadas después del día de las elecciones para hacer las denuncias respectivas.
# Usuarios
## Testigos electorales
- Digitan en la aplicación los votos obtenidos por cada candidato en su mesa / zona / municipio.
- Toman fotos de los formularios E-14 y/o E-24.
- Reportan inconsistencias en cada etapa del conteo de votos.
- Reportan anomalías en los puestos de votación.
## Ciudadanos
- Reciben reportes de los resultados de las elecciones.
- Obtienen reportes de fraude electoral.
## Agente KYC
- Válida Cédula de Ciudadanía del usuario.
## Organización acreditadora
- Otorga credenciales a testigos electorales.
# Beneficios
- Registro público e inmodificable.
- Costo nulo para los observadores electorales.
- Control y participación ciudadana sobre el proceso electoral.
- Registro digital de formularios E-14 y E-24, los cuales se pueden usar como evidencia para denunciar fraude electoral.
- Software de código abierto, que puede ser auditado por cualquier persona.
- Software gratuito, creado por la sociedad civil.
# ¿Quién puede acreditar testigos electorales?
- Partidos y movimientos políticos con o sin personería jurídica.
- Movimientos sociales.
- Grupos significativos de ciudadanos que inscriban candidatos a cargos o corporaciones públicas o promuevan el voto en blanco.
- Comités independientes de promotores del voto en blanco
Fuente: https://pdf.usaid.gov/pdf_docs/PA00MVGB.pdf
<img src="https://github.com/testigos2022/colombia/blob/main/assets/img/flowchart-es.png" alt="" width="550px">
------------------------------------------------------------------------------------------------------------------------------------------------------------
English version
# Electoral observers Colombia 2022
Testigos 2022 is a system that allows building instantaneously an immutable record of votes. The system is designed for the 2022-2026 Presidential and Congressional elections in Colombia. The votes record is built with reports from electoral observers.
# Context
The Council of the Colombian Estate has indicated that the software used in Colombia to count election votes is fraudulent. In May 2022, elections for President and Congress in Colombia will take place. Therefore, it is expected that there will be a new electoral fraud.
More information at:
- https://www.lasillavacia.com/historias/silla-nacional/reglas-electorales-clave-para-la-oposicion-no-alcanzaran-a-aplicarse-en-2022/
- https://pares.com.co/2018/04/27/asi-se-roban-las-elecciones-en-colombia/
- https://www.semana.com/elecciones-presidenciales2018/candidatos-elecciones-presidencia-2018/articulo/polemica-por-auditoria-al-software-de-la-registraduria/568155/
# Problem
In Colombia, vote counting consists of three phases:
- Counting at voting tables.
- Aggregated by voting zones (sum of voting tables).
- Aggregated by municipalities (sum of voting zones).
Most often, the vote-count results at each phase do not match with the other phases. For the electoral observers it is impossible to identify these inconsistencies during the vote-counting process because there is too much information that they have to verify in a few hours (thousands of paper forms).
# Solution
Build an immutable record of the votes registered at each voting table, using information reported by the election observers. The reports of the observers located at each voting table will be immediately accessible to the zonal observers. Likewise, the reports created by the zonal witnesses will be immediately accessible to the municipal observers. Thus, part of the work of the election observers will be automatized, contributing to guarantee that the results are consistent across all the stages of the vote-counting process.
Additionally, the system allows taking photographs of the official documents used during the vote-count (E-14 and E-24 forms). These photos can be used by observers to make official complaints during election day. Likewise, the photographs may be used after election day to make lawsuits.
# Users
## Electoral observers
- Enter in the application the votes obtained by each candidate in their table / zone / municipality.
- Take photos of the E-14 and/or E-24 forms.
- Report inconsistencies at each stage of the vote-counting process.
- Report anomalies at the voting stations.
## Citizens
- Receive reports of election results.
- Obtain reports of electoral fraud.
## KYC Agent
- Validate the user's citizenship card.
## Accrediting Organization
- Provides credentials to electoral observers.
## Benefits
- Public and unchangeable registry.
- Null cost for the electoral observers.
- Citizen control and participation in the electoral process.
- Digital registry of E-14 and E-24 forms that can be used as evidence to denounce electoral fraud.
- Open-source software that anyone can audit.
- Free software, created by civil society.
# Who can issue credentials of electoral observers?
- Political parties and movements with or without legal status.
- Social movements.
- Significant groups of citizens that register candidates for public offices or corporations or promote the blank vote.
- Independent committees of blank vote promoters.
Source: https://pdf.usaid.gov/pdf_docs/PA00MVGB.pdf
<img src="https://github.com/testigos2022/colombia/blob/main/assets/img/flowchart-en.png" alt="" width="550px">
| 60.873016 | 530 | 0.788266 | spa_Latn | 0.777452 |
e05dca30a17ff83471734fffbc8e7407ac9ed65b | 226 | md | Markdown | src/contents/food/2020-08-01-rad-bowl.md | mpezzi/prettyradbar.com | 1979ca0016cca5b0f0ef27028f23170def03c8cf | [
"MIT"
] | null | null | null | src/contents/food/2020-08-01-rad-bowl.md | mpezzi/prettyradbar.com | 1979ca0016cca5b0f0ef27028f23170def03c8cf | [
"MIT"
] | 8 | 2020-10-10T23:52:53.000Z | 2022-02-27T00:11:17.000Z | src/contents/food/2020-08-01-rad-bowl.md | mpezzi/prettyradbar.com | 1979ca0016cca5b0f0ef27028f23170def03c8cf | [
"MIT"
] | null | null | null | ---
templateKey: food
title: Rad Bowl
date: 2020-08-01T01:56:04.230Z
price: 16
---
jasmine rice / carrots / onions/ avocado / watermelon radish / edamame / sunny side up egg / nori / gochujang shallot dressing / sesame seeds
| 25.111111 | 141 | 0.725664 | eng_Latn | 0.539122 |
e05de02b2596b9c12b904144dd9c42509100a337 | 1,604 | md | Markdown | docs/other/auto_watch_video.md | huskyAreYouScared/blog | 27a3897b7949749470e56e834bb49b8b2a37d8c3 | [
"MIT"
] | 4 | 2020-01-20T13:42:02.000Z | 2020-12-04T06:43:52.000Z | docs/other/auto_watch_video.md | huskyAreYouScared/blog | 27a3897b7949749470e56e834bb49b8b2a37d8c3 | [
"MIT"
] | 24 | 2020-03-16T11:51:59.000Z | 2022-02-26T22:36:58.000Z | docs/other/auto_watch_video.md | huskyAreYouScared/blog | 27a3897b7949749470e56e834bb49b8b2a37d8c3 | [
"MIT"
] | null | null | null | # Auto.js自动刷短视频
## 首先要获取到软件
* [传送门](https://pan.baidu.com/s/1IG1J1ewAVFmTgcY4uE-hGw)提取码: ygpq
## 设备要求
* \>= Android7.0
## 编程语言要求
* javascript 不熟悉也没关系
## 使用讲解
* 1.安装之后打开Auto.js需要给予权限，注意这里每个手机给与权限的界面不一致，只需要找到给autojs赋权限的地方即可
<br/>
<img style="width:300px;" :src="$withBase('/image/autojs-1.jpg')" alt="dock">
* 如果没有提示这个赋予权限的弹框，那么点开左上角折叠即可看到无障碍服务
* 2.点击右下角加号新建文件
<br/>
<img style="width:300px;" :src="$withBase('/image/autojs-2.jpg')" alt="dock">
* 3.点击图中标红位置的铅笔图标进行脚本编写，播放按钮运行脚本
<br/>
<img style="width:300px;" :src="$withBase('/image/autojs-3.jpg')" alt="dock">
* 4.在空白处写入代码，代码我会粘贴在下面，写好代码之后点击保存,这里代码很简单就是对定时器的利用配合滑屏API来完成，如果对脚本不是很熟悉直接复制即可
<br/>
<img style="width:300px;" :src="$withBase('/image/autojs-4.jpg')" alt="dock">
```js{3}
var i = 0
setInterval(function(){i++
if(i%2){ // 根据i的变化，来改变每次滑屏的位置
swipe(500,2000,500,500,600); // 滑屏
}else{
swipe(500,2050,500,400,650); // 滑屏
}
},15000) // 滑屏间隔，可调节改变时间间隔（eg: 15000->10000 ,将15s变为10s）
```
[滑屏的api](https://hyb1996.github.io/AutoJs-Docs/#/coordinatesBasedAutomation?id=swipex1-y1-x2-y2-duration)
* 5.两种运行方式一种是在步骤三点击运行，另一种是在步骤四编写完代码后在上方点击运行
* 6.在管理里面查看当前运行的脚本
<br/>
<img style="width:300px;" :src="$withBase('/image/autojs-5.jpg')" alt="dock">
* 7.关闭脚本，在管理界面->运行中的脚本->每个脚本后面对应的叉号点击即可关闭
## 相关文章
* [autojs文档](https://hyb1996.github.io/AutoJs-Docs/#/)
## 声明
* 版权归原作者所有，如有侵权联系删除 issue即可
* [项目地址](https://github.com/huskyAreYouScared/blog)
* 软件虽好，不要干坏事哦
## 其他脚本
* 自动翻看小说`横屏翻页 `
```js
var i = 0
setInterval(function(){i++
if(i%2==0){
swipe(500,2000,500,500,600);
}else{
swipe(500,2050,500,400,650);
}
},10000)
```
| 24.676923 | 105 | 0.683292 | yue_Hant | 0.410508 |
e05e838f20e9435e5dbf383a2d5a22c2240d6a14 | 512 | md | Markdown | docs/oci-storage-get-container-run-dir.md | vbatts/containers-storage | d10d8680af74070b362637408a7fe28c4b1f1eff | [
"Apache-2.0"
] | 1 | 2018-07-02T13:02:19.000Z | 2018-07-02T13:02:19.000Z | docs/oci-storage-get-container-run-dir.md | vbatts/containers-storage | d10d8680af74070b362637408a7fe28c4b1f1eff | [
"Apache-2.0"
] | null | null | null | docs/oci-storage-get-container-run-dir.md | vbatts/containers-storage | d10d8680af74070b362637408a7fe28c4b1f1eff | [
"Apache-2.0"
] | null | null | null | ## oci-storage-get-container-run-dir 1 "Sepember 2016"
## NAME
oci-storage get-container-run-dir - Find runtime lookaside directory for a container
## SYNOPSIS
**oci-storage** **get-container-run-dir** [*options* [...]] *containerNameOrID*
## DESCRIPTION
Prints the location of a directory which the caller can use to store lookaside
information which should be cleaned up when the host is rebooted.
## EXAMPLE
**oci-storage get-container-run-dir my-container**
## SEE ALSO
oci-storage-get-container-dir(1)
| 28.444444 | 84 | 0.75 | eng_Latn | 0.925526 |
e05ea9754cb5c2e62bde5f825efd76db7a4fcbeb | 19,934 | md | Markdown | articles/cognitive-services/personalizer/ethics-responsible-use.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | 7,073 | 2017-06-27T08:58:22.000Z | 2022-03-30T23:19:23.000Z | articles/cognitive-services/personalizer/ethics-responsible-use.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | 87,608 | 2017-06-26T22:11:41.000Z | 2022-03-31T23:57:29.000Z | articles/cognitive-services/personalizer/ethics-responsible-use.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | 17,093 | 2017-06-27T03:28:18.000Z | 2022-03-31T20:46:38.000Z | ---
title: Ethics and responsible use - Personalizer
titleSuffix: Azure Cognitive Services
description: These guidelines are aimed at helping you to implement personalization in a way that helps you build trust in your company and service. Be sure to pause to research, learn and deliberate on the impact of the personalization on people's lives. When in doubt, seek guidance.
author: jeffmend
ms.author: jeffme
ms.manager: nitinme
ms.service: cognitive-services
ms.subservice: personalizer
ms.topic: conceptual
ms.date: 06/12/2019
---
# Guidelines for responsible implementation of Personalizer
For people and society to realize the full potential of AI, implementations need to be designed in such a way that they earn the trust of those adding AI to their applications and the users of applications built with AI. These guidelines are aimed at helping you to implement Personalizer in a way that helps you build trust in your company and service. Be sure to pause to research, learn and deliberate on the impact of the personalization on people's lives. When in doubt, seek guidance.
These guidelines are not intended as legal advice and you should separately ensure that your application complies with the fast-paced developments in the law in this area and in your sector.
Also, in designing your application using Personalizer, you should consider a broad set of responsibilities you have when developing any data-centric AI system, including ethics, privacy, security, safety, inclusion, transparency and accountability. You can read more about these in the [Recommended reading](#recommended-reading) section.
You can use the following content as a starter checklist, and customize and refine it to your scenario. This document has two main sections: The first is dedicated to highlighting responsible use considerations when choosing scenarios, features and rewards for Personalizer. The second take a set of values Microsoft believes should be considered when building AI systems, and provides actionable suggestions and risks on how your use of Personalizer influences them.
## Your responsibility
All guidelines for responsible implementation build on the foundation that developers and businesses using Personalizer are responsible and accountable for the effects of using these algorithms in society. If you are developing an application that your organization will deploy, you should recognize your role and responsibility for its operation and how it affects people. If you are designing an application to be deployed by a third party, come to a shared understanding with them of who is ultimately responsible for the behavior of the application, and document that understanding.
Trust is built on the notion of fulfilled commitments - consider your users, society, and the legal framework your applications works in, to identify explicit and implicit commitments they may have.
Microsoft is continuously putting effort into its tools and documents to help you act on these responsibilities. [Provide feedback to Microsoft](mailto:[email protected]?subject%3DPersonalizer%20Responsible%20Use%20Feedback&body%3D%5BPlease%20share%20any%20question%2C%20idea%20or%20concern%5D) if you believe additional tools, product features and documents would help you implement these guidelines for using Personalizer.
## Factors for responsibly implementing Personalizer
Implementing Personalizer can be of great value to your users and your business. To implement Personalizer responsibly, start by considering the following guidelines when:
* Choosing use cases to apply Personalization.
* Building [reward functions](concept-rewards.md).
* Choosing which [features](concepts-features.md) about the context and possible actions you will use for personalization.
## Choosing use cases for Personalizer
Using a service that learns to personalize content and user interfaces is useful. It can also be misapplied if the way the personalization creates negative side effects in the real world, including if users are unaware of content personalization.
Examples of uses of Personalizer with heightened potential for negative side effects or a lack of transparency include scenarios where the "reward" depends on many long-term complex factors that, when over-simplified into an immediate reward can have unfavorable results for individuals. These tend to be considered "consequential" choices, or choices that involve a risk of harm. For example:
* **Finance**: Personalizing offers on loan, financial, and insurance products, where risk factors are based on data the individuals don't know about, can't obtain, or can't dispute.
* **Education**: Personalizing ranks for school courses and education institutions where recommendations may propagate biases and reduce users' awareness of other options.
* **Democracy and Civic Participation**: Personalizing content for users with the goal of influencing opinions is consequential and manipulative.
* **Third-party reward evaluation**: Personalizing items where the reward is based on a latter 3rd party evaluation of the user, instead of having a reward generated by the user's own behavior.
* **Intolerance to Exploration**: Any situation where the exploration behavior of Personalizer may cause harm.
When choosing use cases for Personalizer:
* Start the design process considering how the personalization helps your users.
* Consider the negative consequences in the real world if some items aren't ranked for users due to personalization patterns or exploration.
* Consider whether your use case constitutes automated processing which significantly affects data subjects that is regulated under [GDPR](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016R0679) Article 22 or other laws.
* Consider self-fulfilling prophecy loops. This may happen if a personalization reward trains a model so it may subsequently further exclude a demographic group from accessing relevant content. For example, most people in a low-income neighborhood don't obtain a premium insurance offer, and slowly nobody in the neighborhood tends to see the offer at all if there isn't enough exploration.
* Save copies of models and learning policies in case it is necessary to reproduce Personalizer in the future. You can do this periodically or every model refresh period.
* Consider the level of exploration adequate for the space and how to use it as a tool to mitigate "echo chamber" effects.
## Selecting features for Personalizer
Personalizing content depends on having useful information about the content and the user. Keep in mind, for some applications and industries, some user features can be directly or indirectly considered discriminatory and potentially illegal.
Consider the effect of these features:
* **User demographics**: Features regarding sex, gender, age, race, religion: These features may be not allowed in certain applications for regulatory reasons, and it may not be ethical to personalize around them because the personalization would propagate generalizations and bias. An example of this bias propagation is a job posting for engineering not being shown to elderly or gender-based audiences.
* **Locale information**: In many places of the world, location information (such as a zip code, postal code, or neighborhood name) can be highly correlated with income, race and religion.
* **User Perception of Fairness**: Even in cases where your application is making sound decisions, consider the effect of users perceiving that content displayed in your application changes in a way that appears to be correlated to features that would be discriminatory.
* **Unintended Bias in Features**: There are types of biases that may be introduced by using features that only affect a subset of the population. This requires extra attention if features are being generated algorithmically, such as when using image analysis to extract items in a picture or text analytics to discover entities in text. Make yourself aware of the characteristics of the services you use to create these features.
Apply the following practices when choosing features to send in contexts and actions to Personalizer:
* Consider the legality and ethics of using certain features for some applications, and whether innocent-looking features may be proxies for others you want to or should avoid,
* Be transparent to users that algorithms and data analysis are being used to personalize the options they see.
* Ask yourself: Would my users care and be happy if I used this information to personalize the content for them? Would I feel comfortable showing them how the decision was made to highlight or hide certain items?
* Use behavioral rather than classification or segmentation data based on other characteristics. Demographic information was traditionally used by retailers for historical reasons – demographic attributes seemed simple to collect and act upon before a digital era, - but question how relevant demographic information is when you have actual interaction, contextual, and historical data that relates more closely to the preferences and identity of users.
* Consider how to prevent features from being 'spoofed' by malicious users, which if exploited in large numbers can lead to training Personalizer in misleading ways to purposefully disrupt, embarrass and harass certain classes of users.
* When appropriate and feasible, design your application to allow your users to opt in or opt out of having certain personal features used. These could be grouped, such as "Location information", "Device Information", "Past Purchase History" etc.
## Computing rewards for Personalizer
Personalizer strives to improve the choice of which action to reward based on the reward score provided by your application business logic.
A well-built reward score will act as a short-term proxy to a business goal, that is tied to an organization's mission.
For example, rewarding on clicks will make the Personalizer Service seek clicks at the expense of everything else, even if what is clicked on is distracting or not tied to a business outcome.
As a contrasting example, a news site may want to set rewards tied to something more meaningful than clicks, such as "Did the user spend enough time to read the content?" "Did they click on relevant articles or references?". With Personalizer it is easy to tie metrics closely to rewards. But be careful not to confound short-term user engagement with good outcomes.
### Unintended consequences from reward scores
Reward scores may be built with the best of intentions, but can still create unexpected consequences or unintended results on how Personalizer ranks content.
Consider the following examples:
* Rewarding video content personalization on the percentage of the video length watched will probably tend to rank shorter videos.
* Rewarding social media shares, without sentiment analysis of how it's shared or the content itself, may lead to ranking offensive, unmoderated, or inflammatory content, which tends to incite a lot of "engagement", but adds little value.
* Rewarding the action on user interface elements that users don't expect to change may interfere with the usability and predictability of the user interface, where buttons are surprisingly changing location or purpose without warning, making it harder for certain groups of users to stay productive.
Implement these best practices:
* Run offline experiments with your system using different reward approaches to understand impact and side-effects.
* Evaluate your reward functions and ask yourself how would an extremely naïve person bend its interpretation and reach undesirable outcomes with it.
## Responsible design considerations
The following are areas of design for responsible implementations of AI. Learn more abut this framework in [The Future Computed](https://news.microsoft.com/futurecomputed/).
### Accountability
*People who design and deploy AI Systems must be accountable for how their systems operate*.
* Create internal guidelines on how to implement Personalizer, document, and communicate them to your team, executives, and suppliers.
* Perform periodic reviews of how reward scores are computed, perform offline evaluations to see what features are affecting Personalizer, and use the results to eliminate unneeded and unnecessary features.
* Communicate clearly to your users how Personalizer is used, to what purpose, and with what data.
* Archive information and assets - such as models, learning policies, and other data - that Personalizer uses to function, to be able to reproduce results.
### Transparency
*AI Systems Should be Understandable*. With Personalizer:
* *Give users information about how the content was personalized.* For example, you can show your users a button labeled `Why These Suggestions?` showing which top features of the user and actions played a role in the results of Personalizer.
* Make sure your terms of use make mention that you will use information about users and their behavior to personalize the experience.
### Fairness
*AI Systems should treat all people fairly*.
* Don't use Personalizer for use cases where the outcomes are long-term, consequential, or involve real harm.
* Don't use features that are not appropriate to personalize content with, or that may help propagate undesired biases. For example, anyone with similar financial circumstances should see the same personalized recommendations for financial products.
* Understand biases that may exist in features that are sourced from editors, algorithmic tools, or users themselves.
### Reliability and safety
*AI Systems should perform reliably and safely*. For Personalizer:
* *Don't provide actions to Personalizer that shouldn't be chosen*. For example, inappropriately movies should be filtered out of the actions to personalize if making a recommendation for an anonymous or under-age user.
* *Manage your Personalizer model as a business asset*. Consider how often to save and back up the model and learning policies behind your Personalizer Loop, and otherwise treat it as an important business asset. Reproducing past results is important for self-audit and measuring improvement.
* *Provide channels to get direct feedback from users*. In addition to coding safety checks to make sure only the right audiences see the right content, provide a feedback mechanism for users to report content that may be surprising or disturbing. Especially if your content comes from users or 3rd parties, consider using Microsoft Content Moderator or additional tools to review and validate content.
* *Perform frequent offline Evaluations*. This will help you monitor trends and make sure effectiveness is known.
* *Establish a process to detect and act on malicious manipulation*. There are actors that will take advantage of machine learning and AI systems' ability to learn from their environment to shift the outcome towards their goals. If your use of Personalizer is in a position to influence important choices, make sure to have appropriate means to detect and mitigate these classes of attacks, including human review in appropriate circumstances.
### Security and privacy
*AI Systems should be secure and respect privacy*. When using Personalizer:
* *Inform users up front about the data that is collected and how it is used and obtain their consent beforehand*, following your local and industry regulations.
* *Provide privacy-protecting user controls.* For applications that store personal information, consider providing an easy-to-find button for functions such as:
* `Show me all you know about me`
* `Forget my last interaction`
* `Delete all you know about me`
In some cases, these may be legally required. Consider the tradeoffs in retraining models periodically so they don't contain traces of deleted data.
### Inclusiveness
*Address a broad range of human needs and experiences*.
* *Provide personalized experiences for accessibility-enabled interfaces.* The efficiency that comes from good personalization - applied to reduce the amount of effort, movement, and needless repetition in interactions- can be especially beneficial to people with disabilities.
* *Adjust application behavior to context*. You can use Personalizer to disambiguate between intents in a chat bot, for example, as the right interpretation may be contextual and one size may not fit all.
## Proactive readiness for increased data protection and governance
It is hard to predict specific changes in regulatory contexts, but in general it would be wise to go beyond the minimum legal framework in ensuring respectful use of personal data, and providing transparency and choice related to algorithmic decision making.
* Consider planning ahead to a situation where there may be new restrictions on data collected from individuals, and there is a need to show how it was used to make decisions.
* Consider extra readiness where users may include marginalized vulnerable populations, children, users in economic vulnerability, or users otherwise susceptible to influence from algorithmic manipulation.
* Consider the widespread dissatisfaction with how audience-targeting and audience-influencing data collection programs and algorithms have played out, and how to avoid proven strategic errors.
## Proactive assessments during your project lifecycle
Consider creating methods for team members, users and business owners to report concerns regarding responsible use, and creating a process that prioritizes their resolution and prevents retaliation.
Any person thinking about side effects of use of any technology is limited by their perspective and life experience. Expand the range of opinions available by bringing in more diverse voices into your teams, users, or advisory boards; such that it is possible and encouraged for them to speak up. Consider training and learning materials to further expand the team knowledge in this domain, and to add capability to discuss complex and sensitive topics.
Consider treating tasks regarding responsible use just like other crosscutting tasks in the application lifecycle, such as tasks related to user experience, security, or DevOps. These tasks and their requirements can't be an afterthought. Responsible use should be discussed and verified throughout the application lifecycle.
## Questions and feedback
Microsoft is continuously putting effort into tools and documents to help you act on these responsibilities. Our team invites you to [provide feedback to Microsoft](mailto:[email protected]?subject%3DPersonalizer%20Responsible%20Use%20Feedback&body%3D%5BPlease%20share%20any%20question%2C%20idea%20or%20concern%5D) if you believe additional tools, product features, and documents would help you implement these guidelines for using Personalizer.
## Recommended reading
* See Microsoft's six principles for the responsible development of AI published in the January 2018 book, [The Future Computed](https://news.microsoft.com/futurecomputed/)
* [Who Owns the Future?](https://www.goodreads.com/book/show/15802693-who-owns-the-future) by Jaron Lanier.
* [Weapons of Math Destruction](https://www.goodreads.com/book/show/28186015-weapons-of-math-destruction) by - Cathy O'Neil
* [Ethics and Data Science](https://www.oreilly.com/library/view/ethics-and-data/9781492043898/) by DJ Patil, Hilary Mason, Mike Loukides.
* [ACM Code of Ethics](https://www.acm.org/code-of-ethics)
* [Genetic Information Nondiscrimination Act - GINA](https://en.wikipedia.org/wiki/Genetic_Information_Nondiscrimination_Act)
* [FATML Principles for Accountable Algorithms](https://www.fatml.org/resources/principles-for-accountable-algorithms)
## Next steps
[Features: action and context](concepts-features.md).
| 99.174129 | 586 | 0.813284 | eng_Latn | 0.999597 |
e05f0d47baff7c079f3705e1aab8b24befc97f1a | 947 | md | Markdown | api/Project.Application.SaveStartingToServer.md | CeptiveYT/VBA-Docs | 1d9c58a40ee6f2d85f96de0a825de201f950fc2a | [
"CC-BY-4.0",
"MIT"
] | 283 | 2018-07-06T07:44:11.000Z | 2022-03-31T14:09:36.000Z | api/Project.Application.SaveStartingToServer.md | CeptiveYT/VBA-Docs | 1d9c58a40ee6f2d85f96de0a825de201f950fc2a | [
"CC-BY-4.0",
"MIT"
] | 1,457 | 2018-05-11T17:48:58.000Z | 2022-03-25T22:03:38.000Z | api/Project.Application.SaveStartingToServer.md | CeptiveYT/VBA-Docs | 1d9c58a40ee6f2d85f96de0a825de201f950fc2a | [
"CC-BY-4.0",
"MIT"
] | 469 | 2018-06-14T12:50:12.000Z | 2022-03-27T08:17:02.000Z | ---
title: Application.SaveStartingToServer event (Project)
ms.prod: project-server
api_name:
- Project.Application.SaveStartingToServer
ms.assetid: e9d19b19-b916-a85d-486a-4a8676998b6c
ms.date: 06/08/2017
ms.localizationpriority: medium
---
# Application.SaveStartingToServer event (Project)
Occurs when Project Professional starts to save project changes to the Project Server queue.
## Syntax
_expression_. `SaveStartingToServer`( `_bstrName_`, `_bstrprojGuid_` )
_expression_ A variable that represents an **[Application](Project.Application.md)** object.
## Parameters
|Name|Required/Optional|Data type|Description|
|:-----|:-----|:-----|:-----|
| _bstrName_|Required|**String**|Name of the project.|
| _bstrprojGuid_|Required|**String**|GUID of the project.|
## Return value
**Nothing**
## Remarks
The **SaveStartingToServer** event cannot be cancelled.
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 22.547619 | 93 | 0.749736 | eng_Latn | 0.418469 |
e05fa29e4b1089f5baf5c5f80710278d4e929c79 | 580 | md | Markdown | docs/API/interfaces/akashaproject_ui_awf_testing_utils._internal_.VoidFunction.md | ethereum-world/Ethereum.World.github.io | 6781a73d21ef729e0b3ff741d2c4087fd86fc5a8 | [
"Apache-2.0"
] | null | null | null | docs/API/interfaces/akashaproject_ui_awf_testing_utils._internal_.VoidFunction.md | ethereum-world/Ethereum.World.github.io | 6781a73d21ef729e0b3ff741d2c4087fd86fc5a8 | [
"Apache-2.0"
] | null | null | null | docs/API/interfaces/akashaproject_ui_awf_testing_utils._internal_.VoidFunction.md | ethereum-world/Ethereum.World.github.io | 6781a73d21ef729e0b3ff741d2c4087fd86fc5a8 | [
"Apache-2.0"
] | null | null | null | [AWF](../README.md) / [Modules](../modules.md) / [@akashaproject/ui-awf-testing-utils](../modules/akashaproject_ui_awf_testing_utils.md) / [<internal\>](../modules/akashaproject_ui_awf_testing_utils._internal_.md) / VoidFunction
# Interface: VoidFunction
[@akashaproject/ui-awf-testing-utils](../modules/akashaproject_ui_awf_testing_utils.md).[<internal>](../modules/akashaproject_ui_awf_testing_utils._internal_.md).VoidFunction
## Callable
### VoidFunction
▸ **VoidFunction**(): `void`
#### Returns
`void`
#### Defined in
node_modules/typescript/lib/lib.dom.d.ts:18068
| 29 | 228 | 0.75 | yue_Hant | 0.396952 |
e05fbfc7aea68005ad69c7f146568b6ece3a2087 | 4,993 | md | Markdown | website/versioned_docs/version-5.2.0/sso.md | tomassatinsky/gooddata-ui | 9c00e5272db2bab5821dcd37615706c7ec45e457 | [
"BSD-3-Clause"
] | null | null | null | website/versioned_docs/version-5.2.0/sso.md | tomassatinsky/gooddata-ui | 9c00e5272db2bab5821dcd37615706c7ec45e457 | [
"BSD-3-Clause"
] | null | null | null | website/versioned_docs/version-5.2.0/sso.md | tomassatinsky/gooddata-ui | 9c00e5272db2bab5821dcd37615706c7ec45e457 | [
"BSD-3-Clause"
] | null | null | null | ---
title: Set Up Authentication and Single Sign-On
sidebar_label: Set Up Authentication and Single Sign-On
copyright: (C) 2007-2018 GoodData Corporation
id: version-5.2.0-sso
original_id: sso
---
Depending on whether SSO is implemented on your site, you can use one of the following to authenticate your users:
* GoodData login page and registration page
* GoodData SSO process
## Prerequisites
Before you start, verify that your site meets the following requirements:
* Cross-Origin Resource Sharing (CORS) is set up. The URL where your analytical application runs is whitelisted in the CORS settings.
If CORS is not set up, contact [GoodData Support](https://support.gooddata.com/hc/en-us/requests/new?ticket_form_id=582387) and request them to set up CORS and whitelist the URL where your analytical application runs in the CORS settings. Optionally, ask them to enable cross-origin redirects to sites allowed by your CORS settings.
* All your users have a GoodData account and have access to your GoodData project.
If some users do not have a GoodData account or do not have access to the project, see [Grant users access to your project](#Grant-users-access-to-your-project).
## Implementing authentication
Choose the use case depending on whether SSO is implemented on your site.
### SSO is implemented on your site
Update your application code so that the application calls the GoodData SSO resource for authentication. For more information about GoodData SSO setup, see [SAML SSO with GoodData](https://help.gooddata.com/display/doc/SAML+SSO+with+GoodData) and [GoodData PGP Single Sign-On](https://help.gooddata.com/display/doc/GoodData+PGP+Single+Sign-On).
This is how authentication process works:
1. The user goes to the URL where your analytical application runs. For example:
`https://my.app.com/`
2. The SSO authentication process authenticates the user.
3. If authentication is successful, the SSO provider redirects the user to the GoodData platform.
4. The GoodData platform verifies whether the application is allowed and redirects the user to the analytical application.
### SSO is not implemented on your site
You do not have to perform any steps for authentication to start working. It is automatically enabled as long as the [prerequisites](#Prerequisites) are met.
This is how authentication process works:
1. The user goes to the URL where your analytical application runs. For example:
`https://my.app.com/`
2. Your application verifies whether the user is logged in. For example:
```javascript
import { factory } from '@gooddata/gooddata-js';
const domain = 'https://my.app.com/';
const sdk = factory({ domain });
sdk.user.isLoggedIn().then((isLogged) => {
if (isLogged) {
// write your own application logic for logged-in users here
} else {
// redirect to the login page providing the URL to redirect to upon a successful login
window.location.replace(`${domain}/account.html?lastUrl=${encodeURIComponent(window.location)}`);
}
};
```
**NOTE:** If you want to pass multiple arguments in `lastUrl`, protect them by using `encodeURIComponent`.
3. If the user is not logged in, the application redirects the user to the GoodData login page (white-labeled with your domain name) with the appended `lastUrl` parameter that points to the URL where your analytical application runs:
`https://my.company.com/account.html?lastUrl=https://my.app.com/`
4. The user logs in to the GoodData Portal.
5. If authentication is successful, the GoodData Portal redirects the user back to the URL where your analytical application runs:
`https://my.app.com/`
### Grant users access to your project
For authentication to work correctly, all users of your application must have a GoodData account and be able to access your GoodData project.
If some users do not have a GoodData account or do not have access to your project, you have to invite them to your project and make sure that the users with no GoodData account create one.
To do so, follow these steps:
1. Customize the link in the invitation email: set the `invitationWelcomePage` platform setting to the URL where your application runs. For example:
`"invitationWelcomePage": "https://my.app.com"`
For more information, see [Configure Various Features via Platform Settings](https://help.gooddata.com/display/doc/Configure+Various+Features+via+Platform+Settings) and the [API for updating the platform settings](https://help.gooddata.com/display/doc/API+Reference#/reference/hierarchical-configuration).
2. Invite the users to your GoodData project via the [GoodData Portal](https://help.gooddata.com/display/doc/Managing+Users+in+Projects).
The link in the invitation email will redirect an invited user to the URL where your application runs. The users with no GoodData account will additionally be asked to create a GoodData account.
| 60.156627 | 344 | 0.759664 | eng_Latn | 0.987703 |
e05fdc387e90ef809724994a6b2e8a79f0eede5f | 4,405 | md | Markdown | articles/storage/files/storage-files-how-to-mount-nfs-shares.md | majacQ/azure-docs.fr-fr | 7d9b6e9689de261ce63ac9d6de8894c5ff2ec608 | [
"CC-BY-4.0",
"MIT"
] | 43 | 2017-08-28T07:44:17.000Z | 2022-02-20T20:53:01.000Z | articles/storage/files/storage-files-how-to-mount-nfs-shares.md | majacQ/azure-docs.fr-fr | 7d9b6e9689de261ce63ac9d6de8894c5ff2ec608 | [
"CC-BY-4.0",
"MIT"
] | 676 | 2017-07-14T20:21:38.000Z | 2021-12-03T05:49:24.000Z | articles/storage/files/storage-files-how-to-mount-nfs-shares.md | majacQ/azure-docs.fr-fr | 7d9b6e9689de261ce63ac9d6de8894c5ff2ec608 | [
"CC-BY-4.0",
"MIT"
] | 153 | 2017-07-11T00:08:42.000Z | 2022-01-05T05:39:03.000Z | ---
title: Monter un partage de fichiers Azure NFS (préversion) - Azure Files
description: Apprenez à monter un partage NFS (Network File System).
author: roygara
ms.service: storage
ms.topic: how-to
ms.date: 07/01/2021
ms.author: rogarana
ms.subservice: files
ms.custom: references_regions
ms.openlocfilehash: 8f3565f05fc04a74e761b1070f0374677703d225
ms.sourcegitcommit: f4e04fe2dfc869b2553f557709afaf057dcccb0b
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 07/02/2021
ms.locfileid: "113225249"
---
# <a name="how-to-mount-an-nfs-file-share-preview"></a>Comment monter un partage de fichiers NFS (préversion)
[Azure Files](storage-files-introduction.md) est le système de fichiers cloud facile à utiliser de Microsoft. Les partages de fichiers Azure peuvent être montés dans des distributions Linux à l'aide du protocole SMB (Server Message Block) ou du protocole NFS (Network File System) (préversion). Cet article est consacré au montage avec NFS. Pour en savoir plus sur le montage avec SMB, consultez [Utiliser Azure Files avec Linux](storage-how-to-use-files-linux.md). Pour plus d'informations sur chacun des protocoles disponibles, consultez [Protocoles de partage de fichiers Azure](storage-files-planning.md#available-protocols).
## <a name="limitations"></a>Limites
[!INCLUDE [files-nfs-limitations](../../../includes/files-nfs-limitations.md)]
### <a name="regional-availability"></a>Disponibilité régionale
[!INCLUDE [files-nfs-regional-availability](../../../includes/files-nfs-regional-availability.md)]
## <a name="prerequisites"></a>Prérequis
- [Créez un partage NFS](storage-files-how-to-create-nfs-shares.md).
> [!IMPORTANT]
> Les partages NFS ne sont accessibles qu'à partir de réseaux approuvés. Les connexions à votre partage NFS doivent provenir de l'une des sources suivantes :
- Utilisez l'une des solutions de mise en réseau suivantes :
- [Créez un point de terminaison privé](storage-files-networking-endpoints.md#create-a-private-endpoint) (recommandé) ou [restreignez l'accès à votre point de terminaison public](storage-files-networking-endpoints.md#restrict-public-endpoint-access).
- [Configurer un VPN point à site (P2S) sous Linux pour une utilisation avec Azure Files](storage-files-configure-p2s-vpn-linux.md).
- [Configurer un VPN site à site pour une utilisation avec Azure Files](storage-files-configure-s2s-vpn.md).
- Configurez [ExpressRoute](../../expressroute/expressroute-introduction.md).
## <a name="disable-secure-transfer"></a>Désactiver le transfert sécurisé
1. Connectez-vous au portail Azure et accédez au compte de stockage contenant le partage NFS que vous avez créé.
1. Sélectionnez **Configuration**.
1. Sous **Transfert sécurisé requis**, sélectionnez **Désactivé**.
1. Sélectionnez **Enregistrer**.
:::image type="content" source="media/storage-files-how-to-mount-nfs-shares/storage-account-disable-secure-transfer.png" alt-text="Capture de l'écran de configuration du compte de stockage, sur lequel le transfert sécurisé est désactivé. ":::
## <a name="mount-an-nfs-share"></a>Monter un partage NFS
1. Une fois le partage de fichiers créé, sélectionnez-le et choisissez **Se connecter à partir de Linux**.
1. Entrez le chemin de montage que vous souhaitez utiliser, puis copiez le script.
1. Connectez-vous à votre client et utilisez le script de montage fourni.
:::image type="content" source="media/storage-files-how-to-create-mount-nfs-shares/mount-nfs-file-share-script.png" alt-text="Capture d’écran du panneau de connexion du partage de fichiers.":::
Votre partage NFS est désormais monté.
### <a name="validate-connectivity"></a>Valider la connectivité
En cas d’échec de votre montage, il est possible que votre point de terminaison privé n’ait pas été correctement configuré ou qu’il soit inaccessible. Pour plus d’informations sur la vérification de la connectivité, consultez la section [Vérifier la connectivité](storage-files-networking-endpoints.md#verify-connectivity) de l’article relatif aux points de terminaison de mise en réseau.
## <a name="next-steps"></a>Étapes suivantes
- Pour plus d'informations sur Azure Files, consultez notre article [Planifier un déploiement Azure Files](storage-files-planning.md).
- Si vous rencontrez des problèmes, consultez [Résoudre les problèmes liés aux partages de fichiers Azure NFS](storage-troubleshooting-files-nfs.md). | 63.84058 | 629 | 0.776163 | fra_Latn | 0.884564 |
e0601258454ca07f7800de6e98663de74b0aaa82 | 146 | md | Markdown | doc/PersonalLog/XiangLi/PersonalLog1128-1204.md | BILLXZY1215/QuizApp | 870de7af6028660ad371b95bd74e4765a07d6a0c | [
"MIT"
] | 1 | 2021-06-07T10:22:21.000Z | 2021-06-07T10:22:21.000Z | doc/PersonalLog/XiangLi/PersonalLog1128-1204.md | BILLXZY1215/QuizApp | 870de7af6028660ad371b95bd74e4765a07d6a0c | [
"MIT"
] | null | null | null | doc/PersonalLog/XiangLi/PersonalLog1128-1204.md | BILLXZY1215/QuizApp | 870de7af6028660ad371b95bd74e4765a07d6a0c | [
"MIT"
] | 1 | 2021-04-22T02:45:24.000Z | 2021-04-22T02:45:24.000Z | # Personal Log 1128-1204
## Work
1. Continue to perfect Interim Report
2. Solve problem for Interim Report in LaTex
## Study
## Next Week
TBC
| 12.166667 | 44 | 0.726027 | kor_Hang | 0.713532 |
e06052d40d79d5140c2325082c04be21d0843878 | 1,661 | md | Markdown | docs/extensibility/debugger/reference/idebugqueryengine2-getengineinterface.md | G-arj/visualstudio-docs | 4c58c63b87a0613962a9b5d67ae116e98c48f4e5 | [
"CC-BY-4.0",
"MIT"
] | 834 | 2017-06-24T10:40:36.000Z | 2022-03-31T19:48:51.000Z | docs/extensibility/debugger/reference/idebugqueryengine2-getengineinterface.md | G-arj/visualstudio-docs | 4c58c63b87a0613962a9b5d67ae116e98c48f4e5 | [
"CC-BY-4.0",
"MIT"
] | 7,042 | 2017-06-23T22:34:47.000Z | 2022-03-31T23:05:23.000Z | docs/extensibility/debugger/reference/idebugqueryengine2-getengineinterface.md | G-arj/visualstudio-docs | 4c58c63b87a0613962a9b5d67ae116e98c48f4e5 | [
"CC-BY-4.0",
"MIT"
] | 1,640 | 2017-06-23T22:31:39.000Z | 2022-03-31T02:45:37.000Z | ---
description: "Gets a custom debug engine (DE) interface."
title: IDebugQueryEngine2::GetEngineInterface | Microsoft Docs
ms.date: 11/04/2016
ms.topic: reference
f1_keywords:
- IDebugQueryEngine2::GetEngineInterface
helpviewer_keywords:
- IDebugQueryEngine2::GetEngineInterface
ms.assetid: ed84aa98-7ec7-48f3-97ae-821090bc3664
author: leslierichardson95
ms.author: lerich
manager: jmartens
ms.technology: vs-ide-debug
ms.workload:
- vssdk
dev_langs:
- CPP
- CSharp
---
# IDebugQueryEngine2::GetEngineInterface
Gets a custom debug engine (DE) interface.
## Syntax
```cpp
HRESULT GetEngineInterface(
IUnknown** ppUnk
);
```
```csharp
int GetEngineInterface(
out object ppUnk
);
```
## Parameters
`ppUnk`\
[out] Returns an `IUnknown` object represents the debug engine (DE), and which can be queried for any other valid interface associated with a DE (for example [IDebugEngine2](../../../extensibility/debugger/reference/idebugengine2.md) or [IDebugEngineLaunch2](../../../extensibility/debugger/reference/idebugenginelaunch2.md)).
## Return Value
If successful, returns `S_OK`; otherwise, returns an error code.
## Remarks
The resulting interface should be used with care because calling through interfaces retrieved from this method circumvents the session debug manager's processing and may result in the SDM getting into a bad state or generating errors while debugging.
## See also
- [IDebugQueryEngine2](../../../extensibility/debugger/reference/idebugqueryengine2.md)
- [IDebugEngine2](../../../extensibility/debugger/reference/idebugengine2.md)
- [IDebugEngineLaunch2](../../../extensibility/debugger/reference/idebugenginelaunch2.md)
| 31.942308 | 326 | 0.774834 | eng_Latn | 0.516305 |
e060697fe61fb19fab73463cba1c76d5d276ad12 | 91 | md | Markdown | NEWS.md | jeksterslabds/jeksterslabRpar | c5c7dbb2a1c454806506748de513995939de947e | [
"MIT"
] | null | null | null | NEWS.md | jeksterslabds/jeksterslabRpar | c5c7dbb2a1c454806506748de513995939de947e | [
"MIT"
] | 1 | 2020-07-16T06:56:45.000Z | 2020-07-16T06:56:45.000Z | NEWS.md | jeksterslabds/jeksterslabRpar | c5c7dbb2a1c454806506748de513995939de947e | [
"MIT"
] | null | null | null | # jeksterslabRpar 0.9.0
## Major changes
* This is the first release of jeksterslabRpar.
| 15.166667 | 47 | 0.747253 | eng_Latn | 0.963972 |
e06143ea613e32e94468fab38c9730093516a508 | 1,316 | md | Markdown | docs/classes/_timeouterror_.timeouterror.md | SergeyCherman/sequelize-pool | b1b34dc47cb49fb770a4733fece4d3ce0e7b3b14 | [
"MIT"
] | null | null | null | docs/classes/_timeouterror_.timeouterror.md | SergeyCherman/sequelize-pool | b1b34dc47cb49fb770a4733fece4d3ce0e7b3b14 | [
"MIT"
] | null | null | null | docs/classes/_timeouterror_.timeouterror.md | SergeyCherman/sequelize-pool | b1b34dc47cb49fb770a4733fece4d3ce0e7b3b14 | [
"MIT"
] | null | null | null | [sequelize-pool](../README.md) › ["TimeoutError"](../modules/_timeouterror_.md) › [TimeoutError](_timeouterror_.timeouterror.md)
# Class: TimeoutError
Error which is thrown by pool when acquire request timeouts
## Hierarchy
* [Error](_timeouterror_.timeouterror.md#static-error)
↳ **TimeoutError**
## Index
### Properties
* [message](_timeouterror_.timeouterror.md#message)
* [name](_timeouterror_.timeouterror.md#name)
* [stack](_timeouterror_.timeouterror.md#optional-stack)
* [Error](_timeouterror_.timeouterror.md#static-error)
## Properties
### message
• **message**: *string*
*Inherited from [TimeoutError](_timeouterror_.timeouterror.md).[message](_timeouterror_.timeouterror.md#message)*
Defined in node_modules/typescript/lib/lib.es5.d.ts:974
___
### name
• **name**: *string*
*Inherited from [TimeoutError](_timeouterror_.timeouterror.md).[name](_timeouterror_.timeouterror.md#name)*
Defined in node_modules/typescript/lib/lib.es5.d.ts:973
___
### `Optional` stack
• **stack**? : *string*
*Inherited from [TimeoutError](_timeouterror_.timeouterror.md).[stack](_timeouterror_.timeouterror.md#optional-stack)*
Defined in node_modules/typescript/lib/lib.es5.d.ts:975
___
### `Static` Error
▪ **Error**: *ErrorConstructor*
Defined in node_modules/typescript/lib/lib.es5.d.ts:984
| 22.305085 | 128 | 0.75 | eng_Latn | 0.190358 |
e06195c45c72f4a571538dab8608ee528bc596bd | 269 | md | Markdown | README.md | project-fifo/fifoi_lager | a56c1631fc1a72a2db5f3ae2443c2ad5679620d2 | [
"BSD-3-Clause"
] | 1 | 2016-09-17T02:18:54.000Z | 2016-09-17T02:18:54.000Z | README.md | project-fifo/fifoi_lager | a56c1631fc1a72a2db5f3ae2443c2ad5679620d2 | [
"BSD-3-Clause"
] | null | null | null | README.md | project-fifo/fifoi_lager | a56c1631fc1a72a2db5f3ae2443c2ad5679620d2 | [
"BSD-3-Clause"
] | 3 | 2016-02-23T23:06:32.000Z | 2022-03-06T10:01:51.000Z | fifo_lager
=====
A lager 'template' that includes graylog, logstash, and the required config for cuttlefish.
The following overlays are used:
* `service` - name of the service of thise node
* `log_path` - path of the log file root
Build
-----
$ rebar3 compile
| 17.933333 | 91 | 0.710037 | eng_Latn | 0.997851 |
e062368dc1342c6b97071e77e4251bd3eb5d8ebf | 1,125 | md | Markdown | README.md | vaeum/react-octicons-svg | 871af0dedf2d771a1c444ed99a9b9fa148b0b70e | [
"MIT"
] | 8 | 2017-02-10T02:46:25.000Z | 2017-09-02T19:51:27.000Z | README.md | vaeum/react-octicons-svg | 871af0dedf2d771a1c444ed99a9b9fa148b0b70e | [
"MIT"
] | null | null | null | README.md | vaeum/react-octicons-svg | 871af0dedf2d771a1c444ed99a9b9fa148b0b70e | [
"MIT"
] | null | null | null | # react-octicons-svg
Octicons React version
Source [https://octicons.github.com/](https://octicons.github.com/)
[](https://nodei.co/npm/react-octicons-svg/)
[![NPM version][npm-image]][npm-url]
[![Downloads][downloads-image]][npm-url]
[](https://travis-ci.org/vaeum/react-octicons-svg)
### Install
```
npm i --save react-octicons-svg
```
### Prefix
In version 1.0.10 add prefix **Icon** to icon name
Example:
settings - in source repo
SettingsIcon - in React Component
### Usage
```
import { SettingsIcon } from 'react-octicons-svg';
<SettingsIcon /> // Create svg icon with classes octicons octicons-settings
```
### Props
- className
### Deploy
```
$ git add . && git commit -m "my message"
$ git tag 0.1234
$ git push origin --tags
$ git push origin master
```
[downloads-image]: https://img.shields.io/npm/dm/react-octicons-svg.svg
[npm-url]: https://www.npmjs.com/package/react-octicons-svg
[npm-image]: https://img.shields.io/npm/v/react-octicons-svg.svg
| 20.833333 | 131 | 0.699556 | kor_Hang | 0.238514 |
e0627a6d8db18caf75a9dcd333d3debee074fbb0 | 1,779 | md | Markdown | README.md | Gagniuc/Bioinformatics-Algorithms-in-Java-Script | 8297fc1cb60e2c17684431955131ab365f4d0db6 | [
"MIT"
] | null | null | null | README.md | Gagniuc/Bioinformatics-Algorithms-in-Java-Script | 8297fc1cb60e2c17684431955131ab365f4d0db6 | [
"MIT"
] | null | null | null | README.md | Gagniuc/Bioinformatics-Algorithms-in-Java-Script | 8297fc1cb60e2c17684431955131ab365f4d0db6 | [
"MIT"
] | null | null | null | # Bioinformatics Algorithms in Java Script
These Bioinformatics HTML5/JS files accompany the book entitled: <i>Algorithms in Bioinformatics: Theory and Implementation</i>, and they are compatible with all internet browsers. These algorithms include more than 120 open-source implementations that describe the following: a) A detailed presentation of new methods, such as Self-sequence alignment, Objective Digital Stains and Spectral Forecast. b) A treatment of sequence alignment, including local sequence alignment, global sequence alignment and forced sequence alignment with full implementations. c) Discussions of position-specific weight matrices, including the count, weight, relative frequencies, and log-likelihoods matrices. d) A detailed presentation of the methods related to Markov Chains as well as a description of their implementation in Bioinformatics and adjacent fields. e) An examination of information and entropy, including sequence logos and explanations related to their meaning. f) An exploration of the current state of bioinformatics, including what is known and what issues are usually avoided in the field. g) Native computer implementations in the context of the field of Bioinformatics. h) Extensive worked examples with detailed case studies that point out the meaning of different results. Demo applications that make direct use of these algorithms, with full GUI interactivity, can be found [here](https://github.com/Gagniuc/Bioinformatics-HTML5-Implementations).
# References
- <i>Paul A. Gagniuc. Algorithms in Bioinformatics: Theory and Implementation. John Wiley & Sons, Hoboken, NJ, USA, 2021, ISBN: 9781119697961.</i>
| 177.9 | 1,454 | 0.817875 | eng_Latn | 0.992003 |
e06288fa02e2bf5273f6dd0cf712070f3fd3b05b | 2,720 | md | Markdown | articles/lab-services/devtest-lab-upload-vhd-using-azcopy.md | p770820/azure-docs.zh-tw | dd2bd917784a4df8b52787a299a3df42e05642fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/lab-services/devtest-lab-upload-vhd-using-azcopy.md | p770820/azure-docs.zh-tw | dd2bd917784a4df8b52787a299a3df42e05642fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/lab-services/devtest-lab-upload-vhd-using-azcopy.md | p770820/azure-docs.zh-tw | dd2bd917784a4df8b52787a299a3df42e05642fe | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 使用 AzCopy 將 VHD 檔案上傳到 Azure DevTest Labs | Microsoft Docs
description: 本文提供逐步解說，說明如何使用 AzCopy 命令列公用程式，將 VHD 檔案上傳至 Azure DevTest Labs 中的實驗室儲存體帳戶。
services: devtest-lab,virtual-machines,lab-services
documentationcenter: na
author: spelluru
manager: femila
editor: ''
ms.assetid: ''
ms.service: lab-services
ms.workload: na
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: article
ms.date: 01/24/2020
ms.author: spelluru
ms.openlocfilehash: 49dc70788bf2a44b6925c5f3f8226fdadab8768c
ms.sourcegitcommit: b5d646969d7b665539beb18ed0dc6df87b7ba83d
ms.translationtype: MT
ms.contentlocale: zh-TW
ms.lasthandoff: 01/26/2020
ms.locfileid: "76757417"
---
# <a name="upload-vhd-file-to-labs-storage-account-using-azcopy"></a>使用 AzCopy 將 VHD 檔案上傳到實驗室的儲存體帳戶
[!INCLUDE [devtest-lab-upload-vhd-selector](../../includes/devtest-lab-upload-vhd-selector.md)]
在 Azure DevTest Labs 中，可以使用 VHD 檔案來建立自訂映像，這些映像可用來佈建虛擬機器。 下列步驟將逐步引導您使用 AzCopy 命令列公用程式，將 VHD 檔案上傳到實驗室的儲存體帳戶。 在您上傳 VHD 檔案之後，[後續步驟](#next-steps)一節會列出一些說明如何從所上傳的 VHD 檔案建立自訂映像的文章。 如需 Azure 中磁碟和 VHD 的詳細資訊，請參閱[受控磁碟簡介](../virtual-machines/linux/managed-disks-overview.md)
> [!NOTE]
>
> AzCopy 是一個僅適用於 Windows 的命令列公用程式。
## <a name="step-by-step-instructions"></a>逐步指示
下列步驟將逐步引導您使用 [AzCopy](https://aka.ms/downloadazcopy) 將 VHD 檔案上傳到 Azure DevTest Labs。
1. 使用 Azure 入口網站來取得實驗室的儲存體帳戶名稱：
1. 登入 [Azure 入口網站](https://go.microsoft.com/fwlink/p/?LinkID=525040)。
1. 選取 [所有服務]，然後從清單中選取 [DevTest Labs]。
1. 從實驗室清單中，選取所需的實驗室。
1. 在實驗室的刀鋒視窗上，選取 [組態]。
1. 在實驗室的 [組態] 刀鋒視窗上，選取 [自訂映像 (VHD)]。
1. 在 [自訂映像] 刀鋒視窗上，選取 [+新增]。
1. 在 [自訂映像] 刀鋒視窗上，選取 [VHD]。
1. 在 [VHD] 刀鋒視窗上，選取 [使用 PowerShell 上傳 VHD]。
1. [使用 PowerShell 上傳映像] 刀鋒視窗會顯示一個對 **Add-AzureVhd** Cmdlet 的呼叫。 第一個參數 (*Destination*) 包含 Blob 容器 (*uploads*) 的 URI，其格式如下：
```
https://<STORAGE-ACCOUNT-NAME>.blob.core.windows.net/uploads/...
```
1. 記下完整的 URI，因為在稍後的步驟中將會用到。
1. 使用 AzCopy 來上傳 VHD 檔案：
1. [下載並安裝最新版的 AzCopy](https://aka.ms/downloadazcopy)。
1. 開啟命令視窗，然後瀏覽至 AzCopy 安裝目錄。 您可以視需要將 AzCopy 安裝位置新增到您的系統路徑。 AzCopy 預設會安裝到下列目錄：
```command-line
%ProgramFiles(x86)%\Microsoft SDKs\Azure\AzCopy
```
1. 使用儲存體帳戶金鑰和 Blob 容器 URI，在命令提示字元中執行下列命令。 *vhdFileName* 值必須包含在引號中。 視 VHD 檔案大小及您的連線速度而定，上傳 VHD 檔案的程序可能會相當長。
```command-line
AzCopy /Source:<sourceDirectory> /Dest:<blobContainerUri> /DestKey:<storageAccountKey> /Pattern:"<vhdFileName>" /BlobType:page
```
## <a name="next-steps"></a>後續步驟
- [使用 Azure 入口網站在 Azure DevTest Labs 中從 VHD 檔案建立自訂映像](devtest-lab-create-template.md)
- [使用 PowerShell 在 Azure DevTest Labs 中從 VHD 檔案建立自訂映像](devtest-lab-create-custom-image-from-vhd-using-powershell.md) | 32 | 262 | 0.739338 | yue_Hant | 0.935652 |
e06296beb595d7f1afef2bdfc16356a043d86c38 | 159 | md | Markdown | data/redis/README.md | alancleary/microservices | 6132a76aa063b749bada17fe98415cd8d5d4fb17 | [
"Apache-2.0"
] | null | null | null | data/redis/README.md | alancleary/microservices | 6132a76aa063b749bada17fe98415cd8d5d4fb17 | [
"Apache-2.0"
] | null | null | null | data/redis/README.md | alancleary/microservices | 6132a76aa063b749bada17fe98415cd8d5d4fb17 | [
"Apache-2.0"
] | null | null | null | `docker-compose[.prod].yml` mounts this directory as a volume in the RediSearch Docker container, allowing the database to persist between container restarts.
| 79.5 | 158 | 0.81761 | eng_Latn | 0.996179 |
e062c2ae683ef5c9a4a013b564700f3f5fbe7ab4 | 70 | md | Markdown | README.md | sormuras/bach-jni | 4132e691145a93f8ded6f2aab8811a516fc20754 | [
"MIT"
] | null | null | null | README.md | sormuras/bach-jni | 4132e691145a93f8ded6f2aab8811a516fc20754 | [
"MIT"
] | null | null | null | README.md | sormuras/bach-jni | 4132e691145a93f8ded6f2aab8811a516fc20754 | [
"MIT"
] | null | null | null | # bach-jni
Load shared platform library in a service providing module
| 23.333333 | 58 | 0.814286 | eng_Latn | 0.993212 |
e062d72777328cefebd609257073c5ed24ab602f | 5,405 | md | Markdown | docs/standard/data/xml/copying-existing-nodes-from-one-document-to-another.md | douglasbreda/docs.pt-br | f92e63014d8313d5e283db2e213380375cea9a77 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/data/xml/copying-existing-nodes-from-one-document-to-another.md | douglasbreda/docs.pt-br | f92e63014d8313d5e283db2e213380375cea9a77 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/data/xml/copying-existing-nodes-from-one-document-to-another.md | douglasbreda/docs.pt-br | f92e63014d8313d5e283db2e213380375cea9a77 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Copiando nós existentes de um documento para outro
ms.date: 03/30/2017
ms.technology: dotnet-standard
ms.assetid: 3caa78c1-3448-4b7b-b83c-228ee857635e
author: mairaw
ms.author: mairaw
ms.openlocfilehash: 744c97e8728d0a65bff8e7bb7a7dbb298afe1800
ms.sourcegitcommit: 64f4baed249341e5bf64d1385bf48e3f2e1a0211
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 09/07/2018
ms.locfileid: "44088083"
---
# <a name="copying-existing-nodes-from-one-document-to-another"></a>Copiando nós existentes de um documento para outro
O método **ImportNode** é o mecanismo pelo qual um nó ou uma subárvore inteira do nó são copiados de um **XmlDocument** para outro. O nó retornado de chamada é uma cópia do nó do documento de origem, incluindo valores de atributo, nome de nó, tipo de nó, e todos os atributos URL relacionados como o prefixo, o nome local, e namespace Uniform Resource Identifier (URI). O documento de origem não é alterado. Depois que você importou o nó, você ainda precisará adicioná-lo à árvore usando um dos métodos usados para nós de inserção.
Quando o nó é anexado ao novo documento, o novo documento possui o nó. O motivo é que cada nó, quando criado, tem um documento proprietário, mesmo se os nós são criados em partes separados do documento. Esse é um requisito do DOM (Modelo de Objeto do Documento) e é imposto pelo design de criação de fábrica na classe **XmlDocument**. Por exemplo, **CreateElement** é a única maneira de criar novos nós.
Dependendo do tipo do nó importado e do valor do parâmetro *deep*, informações adicionais são copiadas conforme apropriado. Este método tenta espelhar o comportamento esperado se um fragmento XML ou de código HTML foi copiado de um documento para outro, responsabilizando-se pelo fato que para XML, os dois documentos pode ter definições de tipos diferentes (DTDs) do documento.
A tabela a seguir descreve o comportamento específico para cada tipo de nó que pode ser importado.
|Tipo de nó|O parâmetro *deep* é true|O parâmetro *deep* é false|
|---------------|------------------------------|-------------------------------|
|XmlAttribute|O <xref:System.Xml.XmlAttribute.Specified%2A> é definido como **true** no XmlAttribute. Os descendentes da origem **XmlAttribute** são importados recursivamente, e os nós resultantes são remontados para formar a subárvore correspondente.|O parâmetro *deep* não se aplica a nós **XmlAttribute**, pois eles sempre levam seus filhos quando importados.|
|XmlCDataSection|Copia o nó, incluindo seus dados.|Copia o nó, incluindo seus dados.|
|XmlComment|Copia o nó, incluindo seus dados.|Copia o nó, incluindo seus dados.|
|XmlDocumentFragment|Os descendentes nó de origem recursivamente serão importados e os nós resultantes são remontados para formar a subárvore correspondente.|Um **XmlDocumentFragment** vazio é criado.|
|XmlDocumentType|Copia o nó, incluindo seu data.*|Copia o nó, incluindo seu data.*|
|XmlElement|Os descendentes do elemento de origem recursivamente serão importados e os nós resultantes são remontados para formar a subárvore correspondente. **Observação:** os atributos padrão não são copiados. Se o documento que está sendo importado define atributos padrão para este nome de elemento, esses são atribuídos.|Os nós de atributo especificados do elemento de origem são importados, e os nós **XmlAttribute** gerados são anexados ao novo elemento. Os nós descendentes não são copiados. **Observação:** os atributos padrão não são copiados. Se o documento que está sendo importado define atributos padrão para este nome de elemento, esses são atribuídos.|
|XmlEntityReference|Como os documentos de origem e destino podem ter as entidades definidas de maneira diferente, esse método copia somente o nó **XmlEntityReference**. O texto de substituição não é incluído. Se o documento de destino tem a entidade definida, o valor é atribuído.|Como os documentos de origem e destino podem ter as entidades definidas de maneira diferente, esse método copia somente o nó **XmlEntityReference**. O texto de substituição não é incluído. Se o documento de destino tem a entidade definida, o valor é atribuído.|
|XmlProcessingInstruction|Copia o destino e o valor do nó importado.|Copia o destino e o valor do nó importado.|
|XmlText|Copia o nó, incluindo seus dados.|Copia o nó, incluindo seus dados.|
|XmlSignificantWhitespace|Copia o nó, incluindo seus dados.|Copia o nó, incluindo seus dados.|
|XmlWhitespace|Copia o nó, incluindo seus dados.|Copia o nó, incluindo seus dados.|
|XmlDeclaration|Copia o destino e o valor do nó importado.|Copia o destino e o valor do nó importado.|
|Todos os outros tipos de nó|Esses tipos de nós não podem ser importados.|Esses tipos de nós não podem ser importados.|
> [!NOTE]
> Embora os nós de DocumentType possam ser importados, um documento pode ter apenas um DocumentType. Assim, uma vez que você importou o tipo de documento, antes de inseri-lo na árvore você precisará certificar-se que não há documento tipo no documento. Para saber mais sobre como remover nós, confira [Removendo nós, conteúdo e valores de um documento XML](../../../../docs/standard/data/xml/removing-nodes-content-and-values-from-an-xml-document.md).
## <a name="see-also"></a>Consulte também
- [DOM (Modelo de Objeto do Documento) de XML](../../../../docs/standard/data/xml/xml-document-object-model-dom.md)
| 117.5 | 670 | 0.772063 | por_Latn | 0.998523 |
e062ee3456463b09385868f069dbd9c9d12e2a2a | 2,701 | md | Markdown | manual.md | zhc0757/intersim | 83ea424f9a7b0a09cc3b1bc15068a23d2517ec6e | [
"MIT"
] | null | null | null | manual.md | zhc0757/intersim | 83ea424f9a7b0a09cc3b1bc15068a23d2517ec6e | [
"MIT"
] | null | null | null | manual.md | zhc0757/intersim | 83ea424f9a7b0a09cc3b1bc15068a23d2517ec6e | [
"MIT"
] | null | null | null | Intersim说明书（英文）
the Manual of Intersim
# 1. Dependency
A. libzmq
B. cppzmq
C. boost
Additionally, cmake is used to build.
# 2. Module
## A. interchiplet
To forward messages between chiplet simulater instances.
## B. sniper
A chiplet simulater.
## C. interchiplet_app
A library for benchmark to communicate between chiplet simulater instances.
## D. record_combine
To transfer trace files.
## E. popnet
To calculate delay.
## F. power_calculate
To calculate power.
# 3. How to Build
Use the script "build.sh" in the catalogs of modules.
# 4. How to Run
## A. interchiplet
Enter the catalog "build" and create a text file "interchiplet.ini" as fellowing:
```
[config]
inter_address=tcp://*
port_base=8000
subnet_count=8
```
It means to open the ports in [port_base, port_base + subnet_count).
Run the executive file in the catalog "build".
## B. sniper
How many simulated chiplets, how many copies of sniper.
Create a text file "zmq_pro.ini" in the catalog "changes" as fellowing:
```
[config]
subnet_id=0
inter_address=tcp://localhost:8000
```
The port in the property "inter_address" should be equal to subnet_id + port_base.
Read sniper-mamual.pdf to get more information.
After running, run changes/build/record_transfer.
## C. interchiplet_app
Include the head file "interchiplet_app.h" and link the library file "libinerchiplet_app.a".
## D. record_combine
1) record_combine
It can combine trace files from different simulater instances. Run after copying "record_n.txt" from the catalogs of sniper instances. "n" is subnet_id.
Only one command line parameter "number of chiplets".
2) popnet_trace_transfer
It transfers the format of trace files.
3 parameters: chiplet count per line, core count per line in a chiplet and frequency by GHz.
3) random_phy_records
It produces random trace files, which need to be transfered by popnet_trace_transfer.
5 parameters: chiplet count, core count per chiplet, message count per period, period by ns and total time by ns.
## E. popnet
Just like original popnet. But c=4 and R=2 or 3. R=2 for mesh topology and R=3 for star topology between chiplets.
If you want to change delay per hop, change the function `void sim_router_template::flit_traversal(long i)` in the source file "sim_router.cc" and rebuild it.
## F. power_calculate
1) power_calculate
It is for mesh networks between chiplets.
3 parameters: trace file path, work per hop between chiplets and work per hop between cores.
2) star_topo_power_calculate
It is for star network between chiplets. It can only calculate counts of different hops.
1 parameter: trace file path.
Change `size_t chipletType(int64_t chipletX,int64_t chipletY)` to set different types of hops between chiplets.
| 33.7625 | 158 | 0.77786 | eng_Latn | 0.983477 |
e06302285656befe4b8e986a897bd5b79303666c | 3,940 | md | Markdown | _posts/2013-09-14-line-length-guidelines.md | lee-dohm/lee-dohm.github.io | 44a075f414dfceaaa8d6a29cfd102d740117fc26 | [
"CC-BY-4.0"
] | 2 | 2020-06-02T18:26:27.000Z | 2021-02-23T07:28:40.000Z | _posts/2013-09-14-line-length-guidelines.md | lee-dohm/lee-dohm.github.io | 44a075f414dfceaaa8d6a29cfd102d740117fc26 | [
"CC-BY-4.0"
] | 30 | 2015-01-13T04:46:55.000Z | 2022-02-26T02:35:05.000Z | _posts/2013-09-14-line-length-guidelines.md | lee-dohm/lee-dohm.github.io | 44a075f414dfceaaa8d6a29cfd102d740117fc26 | [
"CC-BY-4.0"
] | 4 | 2016-08-04T16:01:14.000Z | 2021-04-15T16:25:55.000Z | ---
layout: post
title: Line Length Guidelines
tags: Coder Geeky
date: 2013-09-14 16:10:09.236039000 -07:00
redirect_from: /2013/09/14/line-length-guidelines.html
---
I contribute as I can to the [Ruby Style Guide][guide] maintained by [Bozhidar Batsov][batsov]. One of the most hotly debated topics is the guideline of keeping lines of code to eighty characters or fewer. Bozhidar even discussed maximum line length in [his first blog post][reasoning] explaining the reasoning behind some of the guidelines. He, and the commenters on that post, bring up some points in support of the eighty-character limit but I wanted to take a look at "representative" code and see what line length people naturally kept themselves within. I believe most good coders naturally keep themselves to shorter lines except when they need to have a longer line to properly express an idea.
The first problem was how to find representative code. I naturally turned to [GitHub][github] to use their new API for search to get the list of the ten most popular Ruby projects. Most popular is defined as having the most "stars", a mechanism on GitHub whereby people mark a project as a favorite of theirs. The more favorites, the more popular.
Now that I had a corpus of code to look at, I wanted to ensure reasonably easily that I was looking at *code*. So I excluded all lines that:
* Consist solely of whitespace
* Consist solely of comments
* Contain only the keyword `end`
* Exceed 200 characters in length[^1]
After some messing around I built a program to query GitHub, download the latest version of the code and parse all the files. You can find my project on GitHub: [Line Length Miner][miner]. When I ran the script, these are the results I found:
* Count: 257,344 lines examined
* Mean: 44.73162 characters
* Standard Deviation: 42.37547
* 95<sup>th</sup> percentile: ~90 characters
* 99<sup>th</sup> percentile: ~123 characters
* 99.9<sup>th</sup> percentile: ~176 characters
* Percentile of 80 characters: 91.82262
* Percentile of 100 characters: 96.88238
* Percentile of 120 characters: 98.81598
* Percentile of 132 characters: 99.31609
And here is the histogram of the data:
It would appear that the length of lines of code do not follow specifically a [normal distribution][normal], though we could still use a normal distribution to approximate it. Because I wanted to have things be as accurate as possible, for all my percentile calculations I worked directly from the dataset and did not approximate based on the mean and standard deviation.
The most interesting thing to note is that representative Ruby code has a hard time staying under eighty characters. If we were to force all ten projects to stay within eighty characters, no exceptions, over eight percent of their code would need to be touched ... over twenty thousand lines! :fearful:
So if the line length limit shouldn't be eighty characters, what should it be? The vast majority of code can stay within 132 characters, so I don't think it should be any higher than that. And only the tiniest fraction less code can stay within 120 characters. So it is really a choice between 100 and 120 characters for Ruby code. 100 to allow those with small monitors to be able to work more easily or 120 to err on the side of permissiveness. I've reconfigured my editor for 100 characters.
[^1]: The assumption here is that lines that are beyond 200 characters in length aren't actually lines of code, but strings or other encoded data.
[batsov]: http://batsov.com
[github]: https://github.com
[guide]: https://github.com/bbatsov/ruby-style-guide
[miner]: https://github.com/lee-dohm/line-length-miner
[normal]: http://en.wikipedia.org/wiki/Normal_distribution
[reasoning]: http://batsov.com/articles/2013/06/26/the-elements-of-style-in-ruby-number-1-maximum-line-length/
| 77.254902 | 702 | 0.781472 | eng_Latn | 0.999112 |
e06306aba9a07954ed1d1cae25d0bcfde31a7adb | 942 | md | Markdown | docs/error-messages/compiler-warnings/compiler-warning-level-4-c4211.md | Chrissavi/cpp-docs.de-de | 6cc90f896a0a1baabb898a00f813f77f058bb7e5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/error-messages/compiler-warnings/compiler-warning-level-4-c4211.md | Chrissavi/cpp-docs.de-de | 6cc90f896a0a1baabb898a00f813f77f058bb7e5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/error-messages/compiler-warnings/compiler-warning-level-4-c4211.md | Chrissavi/cpp-docs.de-de | 6cc90f896a0a1baabb898a00f813f77f058bb7e5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Compilerwarnung (Stufe 4) C4211
ms.date: 11/04/2016
f1_keywords:
- C4211
helpviewer_keywords:
- C4211
ms.assetid: 3eea3455-6faa-4cdb-8730-73db7026bd1f
ms.openlocfilehash: df19f90e17d6737a2639eb1245da197881e35c96
ms.sourcegitcommit: 1f009ab0f2cc4a177f2d1353d5a38f164612bdb1
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 07/27/2020
ms.locfileid: "87218103"
---
# <a name="compiler-warning-level-4-c4211"></a>Compilerwarnung (Stufe 4) C4211
nicht dem Standard entsprechende Erweiterung: Neudefinition von extern in static
Mit den standardmäßigen Microsoft-Erweiterungen (/Ze) können Sie einen **`extern`** Bezeichner als neu definieren **`static`** .
## <a name="example"></a>Beispiel
```c
// C4211.c
// compile with: /W4
extern int i;
static int i; // C4211
int main()
{
}
```
Diese Neudefinitionen sind unter ANSI-Kompatibilität ([/Za](../../build/reference/za-ze-disable-language-extensions.md)) ungültig.
| 26.166667 | 130 | 0.762208 | deu_Latn | 0.452202 |
e0631592539520f775ffd1a52b20b9be0450f579 | 14,563 | md | Markdown | src/pages/practice/social-contract.md | tim-stasse/openpracticelibrary | 1c160ce1d3a579050db5e01fae235a68958ac8f4 | [
"Apache-2.0"
] | null | null | null | src/pages/practice/social-contract.md | tim-stasse/openpracticelibrary | 1c160ce1d3a579050db5e01fae235a68958ac8f4 | [
"Apache-2.0"
] | 1 | 2022-01-27T06:36:11.000Z | 2022-01-27T06:36:11.000Z | src/pages/practice/social-contract.md | tim-stasse/openpracticelibrary | 1c160ce1d3a579050db5e01fae235a68958ac8f4 | [
"Apache-2.0"
] | null | null | null | ---
templateKey: practice-page
title: Social Contract
subtitle: Build a constructive, fun team culture
date: 2017-11-21T05:00:00.000Z
authors:
- mtakane
- tdbeattie
- rdebeasi
- springdo
- infosec812
- ilaria66
- kattekrab
tags:
- culture
mobiusTag: foundation
icon: /images/social-contract.jpg
whatIs: >-
The Social Contract is a simple and effective way to enable team autonomy and
self accountability for engagements. The Social Contract or Agreement is
created by and for the team. It looks to codify the behaviors and
expectations of the team. It also provides a mechanism for the team to radiate
and share its desired behaviours with management and other stakeholders.
To effectively use this practice you should look to create the following outcomes:
* Public display of the social contract
* Nobody is above the contract
* The team agreed holds each other accountable to the contract. Having every team member physically sign the contract can provide a good starting point for this.
* Revisit the social contract often and update it as necessary
whyDo: |-
* Quick means to clearly determine team dynamics and expectations
* Promote autonomy and self governing of team behavior
* The contract keeps the team consciously aware of how they work together
* Establish empathy and context for future conversations between team members
howTo: >-
## Materials Needed
* Wall space which will hold sticky notes.
* Whiteboard markers
* Stickies (preferably a wide variety)
* Large poster paper
Stick the large poster paper on the wall and label it "Social Contract."
Explain to the team that we're going to:
* Define the kind of culture we want our team to have
* Set some general guidelines
* Hold one another accountable to these guidelines
Ask open-ended questions about the team's desired way of working. If the team agrees to an answer, write the decision on a sticky note and put the note on the poster paper. If there's not consensus, throw the sticky note away or put it in the parking lot for later discussion.
At the end, ask the team to sign the contract, and keep it in a visible place. Note that this is a living document so the team can revisit it later, change it, and initial it to indicate that everyone has agreed to the change.
As the team moves forward, encourage them to refer back to the contract when there are disagreements.
## Example Questions
Try to guide the team to a contract that encourages positivity, autonomy, and respect.
* What sort of team culture do you want to build?
* Open, positive, blame-free, constructive
* Fun!
* No magic, no wizardry, no ninjas - build shared understanding
* Celebrate success
* What core hours do you want to work? 10am - 3pm?
* The idea is *not* to encourage a clock-in/clock-out mindset. It's about giving people the freedom to work the hours that make sense for them while ensuring that the team can still meet together.
* What are your thoughts on pair programming? Mob programming? Mob to learn; pair to build? Focus, then share what you learned?
* Respect individual working styles
* How should we handle devices in meetings? Laptops closed and phones down? Step out if you need to work on something else?
* How do you want to track tasks? Jira? Paper stickies? This helps us avoid missing important stuff or duplicating work.
* Embrace creative chaos
## Don't do this
Avoid building a social contract that encourages antagonistic, command-and-control behavior. Here's an example of a really bad social contract:
* Core hours are 9am-7pm. The more time you spend at a desk, the more you'll accomplish.
* Be more productive by juggling several projects at once.
* Ensure accountability by finding someone to blame when things break.
* Deploying to production is scary because it's an opportunity to get blamed for something (see above). Code should be deployed as infrequently as possible.
* When you learn something, be sure to keep it to yourself so that everyone can see what a ninja rockstar wizard unicorn you are.
## Tips for remote sessions
1. Consider to have a “pre-canned” social contract that is good for remote meetings, then allow people to add/change based on their thoughts.
2. Everyone signs with a Sticky-note with his/her name.
3. Add remote working elements to the social contract (mute on entry, video on etc).
4. Establish global communication norms and individual teams exceptions: response time, writing style, and tone, etc.
5. Use examples:
> * One conversation at a time
> * Assume positive intent
> * Do not delete or move others contribution
> * Stay focused on our goal working iteratively
> * Respect breaks
> * Avoid other distractions like mail, and chat
> * A contract can be updated based on needs...
> * Agree on the above adding a sticky w/name & location
mediaGallery:
- link: https://www.youtube.com/o1le81ZgVLk
- link: https://openpracticelibrary.github.io/opl-media/images/social-contract.jpg
resources:
- link: https://anchor.fm/openpracticelibrary/embed/episodes/Social-Contracts-w-Omar-McNeil-ecf9e1
linkType: podcast
description: Learn more by listening to the Open Practice Podcast episode!
- link: https://medium.com/@springdo/social-contracts-6c62c4588b6e
linkType: web
description: Social Contracts - The best thing your teams aren't doing
- link: https://theagileexecutive.com/tag/social-contract/
linkType: web
description: Social Contract - The Agile Executive
- link: https://resources.scrumalliance.org/Article/facilitate-powerful-working-agreements
linkType: web
description: Facilitate powerful working agreements - Scrum Alliance
- link: https://www.oreilly.com/library/view/dynamic-reteaming-2nd/9781492061281/
linkType: purchase
description: Dynamic Reteaming - Book - Heidi Helfand
participants:
- Facilitator
- Team Members
- Stakeholders
jumbotron: /images/social-contract.jpg
area: foundation-culture-and-collaboration
people: 3+
time: 10 minutes
perspectives:
- facilitation-tips-for-remote-sessions
difficulty: moderate
---
## What is it?
The Social Contract is a simple, yet highly effective manner to enable team autonomy and self accountability for engagements. The Social Contract is created by and for the team. It looks to codify the behaviors and expectations of the team. It also provides a mechanism for the team to radiate and share its desired behaviours with management and other stakeholders.
To effectively use this practice you should look to create the following outcomes:
- Public display of the social contract
- Nobody is above the contract
- The team agreed holds each other accountable to the contract. Having every team member physically sign the contract can provide a good starting point for this.
- Revisit the social contract often and update it as necessary
<iframe width="560" height="315" src="https://www.youtube.com/embed/o1le81ZgVLk" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
**<div align="center">Learn more by listening to the Open Practice Podcast episode! 🎙️🌠</div>**
<div align="center"><iframe src="https://anchor.fm/openpracticelibrary/embed/episodes/Social-Contracts-w-Omar-McNeil-ecf9e1" height="102px" width="400px" frameborder="0" scrolling="no"></iframe></div>
## Example Questions
Try to guide the team to a contract that encourages positivity, autonomy, and respect.
- What sort of team culture do you want to build?
- Open, positive, blame-free, constructive
- Fun!
- No magic, no wizardry, no ninjas - build shared understanding
- Celebrate success
- What core hours do you want to work?
- 10am - 3pm?
- The idea is _not_ to encourage a clock-in/clock-out mindset. It's about giving people the freedom to work the hours that make sense for them while ensuring that the team can still meet together.
- What are your thoughts on pair programming? Mob programming?
- Mob to learn; pair to build?
- Focus, then share what you learned?
- Respect individual working styles
- How should we handle devices in meetings?
- Laptops closed and phones down?
- Step out if you need to work on something else?
- How do you want to track tasks?
- Jira?
- Paper stickies?
- This helps us avoid missing important stuff or duplicating work.
- Embrace creative chaos
## Don't do this
Avoid building a social contract that encourages antagonistic, command-and-control behavior. Here's an example of a really bad social contract:
- Core hours are 9am-7pm. The more time you spend at a desk, the more you'll accomplish.
- Be more productive by juggling several projects at once.
- Ensure accountability by finding someone to blame when things break.
- Deploying to production is scary because it's an opportunity to get blamed for something (see above). Code should be deployed as infrequently as possible.
- When you learn something, be sure to keep it to yourself so that everyone can see what a ninja rockstar wizard unicorn you are.
## Why use a Social Contract?
- Quick means to clearly determine team dynamics and expectations
- Promote autonomy and self governing of team behavior
- The contract keeps the team consciously aware of how they work together
- Establish empathy and context for future conversations between team members
## Materials Needed
- Wall space which will hold sticky notes.
- Whiteboard markers
- Stickies (preferably a wide variety)
- Large poster paper
## How To
Stick the large poster paper on the wall and label it "Social Contract."
Explain to the team that we're going to:
- Define the kind of culture we want our team to have
- Set some general guidelines
- Hold one another accountable to these guidelines
Ask open-ended questions about the team's desired way of working. If the team agrees to an answer, write the decision on a sticky note and put the note on the poster paper. If there's not consensus, throw the sticky note away or put it in the parking lot for later discussion.
At the end, ask the team to sign the contract, and keep it in a visible place. Note that this is a living document so the team can revisit it later, change it, and initial it to indicate that everyone has agreed to the change.
As the team moves forward, encourage them to refer back to the contract when there are disagreements.
## Tips for remote sessions
1. Consider to have a “pre-canned” social contract that is good for remote meetings, then allow people to add/change based on their thoughts
2. Everyone signs with a Sticky-note with his/her name.
3. Add remote working elements to the social contract (mute on entry, video on etc)
4. Establish global communication norms and individual teams exceptions: response time, writing style, and tone, etc
5. Use examples:
- One conversation at a time
- Assume positive intent
- Do not delete or move others contribution
- Stay focused on our goal working iteratively
- Respect breaks
- Avoid other distractions like mail, and chat
- A contract can be updated based on needs...
- Agree on the above adding a sticky w/name & location
**Want to run this practice remotely? Here's some help to jump start your session 💻🙏**
<div style="width: 600px;"> <h1 style="position: relative;vertical-align: middle;display: inline-block; font-size: 24px; line-height:28px; color: #393939;margin-bottom: 14px; font-weight: 300;font-family: Proxima Nova, sans-serif;"> <span style="padding-left: 46px; display: inline-block;"> Social Contract Template <span style="font-size: 16px; color: #393939; font-weight: 300;"> by MURAL </span> </span> </h1> <div style="position: relative;padding-bottom: 56.25%;height: 0; overflow: hidden; max-width: 800px; min-width: 320px; border-width: 1px; border-style: solid; border-color: #d8d8d8;"> <div style="position: absolute;top: 0;left: 0;z-index: 10; width: 100%; height: 100%;background: url(https://murally.blob.core.windows.net/thumbnails/warhw2023/murals/warhw2023.1584980422653-5e78e1c615ecf04b79d06958.png?v=81b1d81d-fe4a-41b7-906b-e6656cc94f79) no-repeat center center; background-size: cover;"> <div style="position: absolute;top: 0;left: 0;z-index: 20;width: 100%; height: 100%;background-color: white;-webkit-filter: opacity(.4);"> </div> <a href="https://app.mural.co/template/ad9c8315-03b7-4f21-98b0-a8dac0d56601/f5a36cb3-25d3-4014-bf46-34417b460d29" target="_blank" style="transform: translate(-50%, -50%);top: 50%;left: 50%; position: absolute; z-index: 30; border: none; background: transparent;"> <img src="https://app.mural.co/static/images/button-template-large.png" alt="GET STARTED FROM TEMPLATE" width="347" height="50" style="width: 347px !important; height: 50px !important"> </a> </div> </div> <p style="margin-top: 7px;margin-bottom: 60px;line-height: 18px; font-size: 14px;font-family: Proxima Nova, sans-serif;font-weight: 400; color: #888888;"> Open to create a mural from this template in your workspace. <span style="color: #393939;"> Powered by </span> <a href="https://mural.co/" target="_blank" style="text-decoration: none;"> <span style="color: #ff0065;">MURAL</span> </a> </p></div>
## Related Practices
- Collaborative Face Drawing[<sup>1</sup>](#footnote-1) is a great ice breaker or after lunch activity. Your Social Contract can be a nicely decorated with the faces of the team to show their commitment to the contract.
- Working Agreements[<sup>2</sup>](#footnote-2) are a form of social contract often used to help establish behavioral standards between peers on a team. This is a great alternative if you do not have stakeholders or sponsors buying in to a Social Contract.
- Use [retrospectives](/practice/retrospectives/) as a tool to revisit and update Social Contract based on learnings of team members working with each other
## External References
1. <a name="footnote-1"></a>[Collaborative Face Drawing](http://www.funretrospectives.com/collaborative-face-drawing/)
2. <a name="footnote-2"></a>[Working Agreements for a Scrum Team](https://www.scrumalliance.org/community/articles/2014/january/work-agreements-for-a-scrum-team)
3. <a name="footnote-3"></a>[Social Contract](https://theagileexecutive.com/tag/social-contract/)
4. [Dynamic Reteaming](https://leanpub.com/dynamicreteaming)
5. [Social Contracts - The best thing your teams aren't doing](https://medium.com/@springdo/social-contracts-6c62c4588b6e)
| 46.231746 | 1,924 | 0.758498 | eng_Latn | 0.99501 |
e063ce31ac0fdf6f61338cc8b093ac999ec516fb | 3,053 | md | Markdown | README.md | BarbzYHOOL/awesome-fish-shell | 04a1069b7061da3a8894c6bc5e7db5f40c1dc0e1 | [
"CC0-1.0"
] | null | null | null | README.md | BarbzYHOOL/awesome-fish-shell | 04a1069b7061da3a8894c6bc5e7db5f40c1dc0e1 | [
"CC0-1.0"
] | null | null | null | README.md | BarbzYHOOL/awesome-fish-shell | 04a1069b7061da3a8894c6bc5e7db5f40c1dc0e1 | [
"CC0-1.0"
] | null | null | null | # Awesome fish-shell
A curated list of awesome tools, prompts and other cool nuggets for the amazing [fish-shell](https://github.com/fish-shell/fish-shell).
To contribute, fork this repository, add your amazing nugget and send a PR.
## Community
* [<samp>#fish</samp> on OFTC](https://webchat.oftc.net/?channels=fish)
* [Gitter.im Channel](https://gitter.im/fish-shell/fish-shell)
* [StackOverflow](http://stackoverflow.com/questions/tagged/fish)
* [r/fishshell](https://www.reddit.com/r/fishshell/)
## Learning
* [Official Documentation](http://fishshell.com/docs/current/index.html)
* [The fish-shell cookbook](https://github.com/jorgebucaran/fish-shell-cookbook)
## Plugin Managers & Frameworks
* [Fisherman](https://github.com/fisherman/fisherman) - The fish-shell plugin manager.
* [Oh My Fish!](https://github.com/oh-my-fish/oh-my-fish) - The fish-shell framework.
## Plugins
* [rodrigobdz/fish-apple-touchbar](https://github.com/rodrigobdz/fish-apple-touchbar) - Customize your Touch Bar in iTerm2 using fish.
* [edc/bass](https://github.com/edc/bass) - Make Bash utilities usable in fish.
* [fisherman/fishtape](https://github.com/fisherman/fishtape) - TAP producing test runner.
* [fisherman/fnm](https://github.com/fisherman/fnm) - Node.js version manager.
* [fisherman/getopts](https://github.com/fisherman/getopts) - Command line options parser.
* [laughedelic/pisces](https://github.com/laughedelic/pisces) - Autocloses parentheses, braces, quotes and other paired symbols.
* [fisherman/shark](https://github.com/fisherman/shark) - Sparkline generator, inspired by @holman's Spark.
* [fisherman/z](https://github.com/fisherman/z) - Pure-fish z directory jumping.
* [smh/base16-shell-fish](https://github.com/smh/base16-shell-fish) - Fast and easy fisherman plugin for switching your [base16-shell theme](https://github.com/chriskempson/base16-shell)
**Various links with plugin lists:**
* [Oh My Fish packages](https://github.com/oh-my-fish/packages-main/tree/master/packages): Package list compatible with Oh My Fish and Fisher (note: to install you need the repository owner/name).
* [Fundle wiki](https://github.com/danhper/fundle/wiki): Another list of Fisher/Fundle/OhMyFish compatible packages.
* [fish-plugins topic](https://github.com/topics/fish-plugins): Repos tagged with the `fish-plugins` topic.
* [fish-plugin topic](https://github.com/topics/fish-plugin): Repos tagged with the `fish-plugin` topic.
* [fisherman topic](https://github.com/topics/fisherman): Repos tagged with the `fisherman` topic.
## Simple Prompts
* [fisherman/metro](https://github.com/fisherman/metro) - Powerline prompt optimized for speed and space.
* [rafaelrinaldi/pure](https://github.com/rafaelrinaldi/pure) - Port of the <samp>pure</samp> ZSH prompt to Fish.
* [oh-my-fish/theme-bobthefish](https://github.com/oh-my-fish/theme-bobthefish) - A Powerline-style, Git-aware fish theme optimized for awesome.
* [oh-my-fish/theme-cbjohnson](https://github.com/oh-my-fish/theme-cbjohnson)
* [fisherman/sol](https://github.com/fisherman/sol)
| 59.862745 | 196 | 0.75303 | eng_Latn | 0.330163 |
e063d86561cd149ac325ff6fb7390af35fcd9949 | 24 | md | Markdown | README.md | charlottegracia/MMD1 | 40a39377dddadef5154b66b126e9e149f47b864f | [
"MIT"
] | null | null | null | README.md | charlottegracia/MMD1 | 40a39377dddadef5154b66b126e9e149f47b864f | [
"MIT"
] | null | null | null | README.md | charlottegracia/MMD1 | 40a39377dddadef5154b66b126e9e149f47b864f | [
"MIT"
] | null | null | null | # MMD1
eksamensprojekt
| 8 | 16 | 0.791667 | dan_Latn | 0.289563 |
e064450441cd0da0ca1848ca08fd08c9c3951078 | 3,546 | md | Markdown | articles/storsimple/storsimple-virtual-array-update-12-release-notes.md | youngick/azure-docs.ko-kr | b6bc928fc360216bb122e24e225a5b7b0ab51d7e | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-03-12T23:37:18.000Z | 2021-03-12T23:37:18.000Z | articles/storsimple/storsimple-virtual-array-update-12-release-notes.md | zoonoo/azure-docs.ko-kr | 3ca44c0720204e9f9a6ef9fe2c73950aa17251c1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storsimple/storsimple-virtual-array-update-12-release-notes.md | zoonoo/azure-docs.ko-kr | 3ca44c0720204e9f9a6ef9fe2c73950aa17251c1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Microsoft Azure StorSimple 가상 배열 업데이트 1.2 릴리스 정보 | Microsoft Docs
description: 업데이트 1.2를 실행 하는 StorSimple 가상 배열에 대 한 중요 한 미해결 문제 및 해결 방법을 설명 합니다.
services: storsimple
author: alkohli
ms.service: storsimple
ms.topic: article
ms.date: 05/29/2019
ms.author: alkohli
ms.openlocfilehash: 1118dfcec67a49365f1f6e5e522e98b97694d052
ms.sourcegitcommit: 867cb1b7a1f3a1f0b427282c648d411d0ca4f81f
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 03/19/2021
ms.locfileid: "94960194"
---
# <a name="storsimple-virtual-array-update-12-release-notes"></a>StorSimple 가상 배열 업데이트 1.2 릴리스 정보
다음 릴리스 정보는 Microsoft Azure StorSimple 가상 배열 업데이트에 대한 중요한 미해결 문제 및 해결된 문제를 식별합니다.
릴리스 정보는 지속적으로 업데이트 됩니다. 해결 방법이 필요한 중요한 문제가 발견되면 추가됩니다. StorSimple 가상 배열을 배포하기 전에 릴리스 정보에 포함된 정보를 주의 깊게 검토하세요.
업데이트 1.2는 소프트웨어 버전 **10.0.10311.0** 에 해당 합니다.
> [!IMPORTANT]
> - 업데이트는 작업 중단 업데이트이며 디바이스를 다시 시작합니다. I/O가 진행 중인 경우 디바이스에 가동 중지 시간이 발생합니다. 이 업데이트를 적용 하는 데 사용 되는 패키지에 대 한 자세한 지침을 보려면 [업데이트 1.2 다운로드](#download-update-12)로 이동 하세요.
> - 업데이트 1.2는 장치에서 업데이트 1.0 또는 1.1를 실행 하는 경우에만 Azure Portal를 통해 사용할 수 있습니다.
## <a name="whats-new-in-update-12"></a>업데이트 1.2의 새로운 기능
이 업데이트에는 다음 버그 수정이 포함 되어 있습니다.
- 삭제 된 파일을 처리할 때 복원 력이 향상 되었습니다.
- 코드 시작 경로의 처리 기능이 향상 되어 백업, 복원, 클라우드 읽기 및 자동화 된 공간 재사용에 대 한 오류를 줄일 수 있습니다.
## <a name="download-update-12"></a>업데이트 1.2 다운로드
이 업데이트를 다운로드 하려면 [Microsoft 업데이트 카탈로그](https://www.catalog.update.microsoft.com/Home.aspx) 서버로 이동 하 여 KB4502035 패키지를 다운로드 합니다. 이 패키지에는 다음 패키지가 포함 됩니다.
- 2012 r 2에 대 한 누적 Windows 업데이트를 포함 하는 **KB4493446** 최대 4 월 2019입니다. 이 롤업에 포함 된 내용에 대 한 자세한 내용은 [4 월 월간 보안 롤업](https://support.microsoft.com/help/4493446/windows-8-1-update-kb4493446)로 이동 합니다.
- **KB3011067** 독립 실행형 패키지 파일인 WINDOWSTH-KB3011067-x 64 인 Microsoft 업데이트. 이 파일은 디바이스 소프트웨어를 업데이트하는 데 사용됩니다.
KB4502035를 다운로드 하 고 다음 지침에 따라 [로컬 웹 UI를 통해 업데이트를 적용](storsimple-virtual-array-install-update-11.md#use-the-local-web-ui)합니다.
## <a name="issues-fixed-in-update-12"></a>업데이트 1.2에서 해결된 문제
다음 표에서는 이 릴리스에서 수정된 문제를 간략하게 설명합니다.
| 아니요. | 기능 | 문제 |
| --- | --- | --- |
| 1 |삭제| 이전 버전의 소프트웨어에서는 파일이 삭제 된 경우에도 장치의 사용이 변경 되지 않은 경우 문제가 발생 했습니다. 이 문제는이 버전에서 해결 되었습니다. 삭제 된 파일을 처리 하는 경우 계층화 된 코드 경로를 더 탄력적으로 만들었습니다.|
| 2 |예외 처리| 이전 버전의 소프트웨어에서는 시스템을 다시 부팅 한 후 백업, 복원, 클라우드에서 읽기 및 자동화 된 공간 재사용으로 인해 발생할 수 있는 문제가 발생 했습니다. 이 릴리스에는 시작 경로에서 예외가 처리 된 방법에 대 한 변경 내용이 포함 되어 있습니다.|
## <a name="known-issues-in-update-12"></a>업데이트 1.2의 알려진 문제
업데이트 1.2에서 발표 된 새로운 문제가 없습니다. 모든 릴리스를 기록한 문제는 이전 릴리스에서 수행 됩니다. 이전 릴리스에 포함 된 알려진 문제에 대 한 요약을 보려면 [업데이트 1.1의 알려진 문제](storsimple-virtual-array-update-11-release-notes.md#known-issues-in-update-11)를 참조 하세요.
## <a name="next-steps"></a>다음 단계
KB4502035를 다운로드 하 고 [로컬 웹 UI를 통해 업데이트를 적용](storsimple-virtual-array-install-update-11.md#use-the-local-web-ui)합니다.
## <a name="references"></a>참조
이전 릴리스 정보를 찾으시나요? 다음으로 이동합니다.
* [StorSimple 가상 배열 업데이트 1.1 릴리스 정보](storsimple-virtual-array-update-11-release-notes.md)
* [StorSimple 가상 배열 업데이트 1.0 릴리스 정보](storsimple-virtual-array-update-1-release-notes.md)
* [StorSimple 가상 배열 업데이트 0.6 릴리스 정보](storsimple-virtual-array-update-06-release-notes.md)
* [StorSimple 가상 배열 업데이트 0.5 릴리스 정보](storsimple-virtual-array-update-05-release-notes.md)
* [StorSimple 가상 배열 업데이트 0.4 릴리스 정보](storsimple-virtual-array-update-04-release-notes.md)
* [StorSimple 가상 배열 업데이트 0.3 릴리스 정보](storsimple-ova-update-03-release-notes.md)
* [StorSimple 가상 배열 업데이트 0.1 및 0.2 릴리스 정보](storsimple-ova-update-01-release-notes.md)
* [StorSimple 가상 배열 일반 공급 릴리스 정보](./storsimple-virtual-array-update-06-release-notes.md) | 49.25 | 202 | 0.722786 | kor_Hang | 1.00001 |
e064711a630711829c21a0ce510ef443045b8f77 | 4,075 | md | Markdown | docs/src/main/markdown/sbt-settings.md | eugeneatnezasa/ScalaPB | 2a9dc21936afff6c41998ffba770d12e2ff2ad80 | [
"Apache-2.0"
] | null | null | null | docs/src/main/markdown/sbt-settings.md | eugeneatnezasa/ScalaPB | 2a9dc21936afff6c41998ffba770d12e2ff2ad80 | [
"Apache-2.0"
] | null | null | null | docs/src/main/markdown/sbt-settings.md | eugeneatnezasa/ScalaPB | 2a9dc21936afff6c41998ffba770d12e2ff2ad80 | [
"Apache-2.0"
] | null | null | null | ---
title: "SBT Settings"
layout: docs
---
# SBT Settings
## Basic Installation
To automatically generate Scala case classes for your messages add ScalaPB's
sbt plugin to your project. Create a file named `project/scalapb.sbt`
containing the following line:
```scala
addSbtPlugin("com.thesamet" % "sbt-protoc" % "{{site.data.version.sbt_protoc}}")
libraryDependencies += "com.thesamet.scalapb" %% "compilerplugin" % "{{site.data.version.scalapb}}"
```
Add the following line to your `build.sbt`:
```scala
PB.targets in Compile := Seq(
scalapb.gen() -> (sourceManaged in Compile).value
)
```
Running the `compile` command in sbt will both generate Scala sources from
your protos and compile them. If you just want to generate Scala sources for
your protocol buffers without compiling them, run `protoc-generate`
Additionally, if you need [customizations]({{site.baseurl}}/customizations.html) from
scalapb/scalapb.proto or anything from `google/protobuf/*.proto`, add the
following to your `build.sbt`:
```scala
libraryDependencies += "com.thesamet.scalapb" %% "scalapb-runtime" % scalapb.compiler.Version.scalapbVersion % "protobuf"
```
## Defaults
The plugin assumes your `proto` files are under `src/main/protobuf`,
however this is configurable using the `PB.protoSources in Compile` setting.
By default, `sbt-protoc` invokes `protoc` 3.x that is shipped with `protoc-jar`.
If you would like to run a different version of `protoc`:
```scala
PB.protocVersion := "-v3.10.0"
```
See all available options in [sbt-protoc documentation](https://github.com/thesamet/sbt-protoc)
## Running on Windows
Before sbt-protoc 0.99.15, generating Scala code on Windows required Python 2.x
to be installed on your system. If you are using sbt-protoc 0.99.15 or later,
then things should just work.
If you are using an older version of sbt-protoc and unable to upgrade, then
you must have Python 2.x installed on your system. If Python is not installed
on your system, you can [download it from here](https://www.python.org/downloads/windows/).
If Python.exe can be found in your PATH, then ScalaPB should just work. If
not, you can set the location of the Python executable explicitly:
```scala
PB.pythonExe := "C:\\Python27\\Python.exe"
```
## Java Conversions
To enable Java conversions add the following to your build.sbt:
```scala
PB.targets in Compile := Seq(
PB.gens.java -> (sourceManaged in Compile).value,
scalapb.gen(javaConversions=true) -> (sourceManaged in Compile).value
)
```
## gRPC
Generating gRPC stubs for services is enabled by default. To disable:
```scala
PB.targets in Compile := Seq(
scalapb.gen(grpc=false) -> (sourceManaged in Compile).value
)
```
## Additional options to the generator
```scala
scalapb.gen(
flatPackage: Boolean = false,
javaConversions: Boolean = false,
grpc: Boolean = true,
singleLineToProtoString: Boolean = false,
asciiFormatToString: Boolean = false,
lenses: Boolean = true,
retainSourceCodeInfo: Boolean = false
)
```
Note that in ScalaPB 0.7, `singleLineToString` has been renamed to
`singleLineToProtoString`.
**`flatPackage`**: When true, ScalaPB will not append the protofile base name
to the package name.
**`singleLineToProtoString`**: By default, ScalaPB generates a `toProtoString()` method
that renders the message as a multi-line format (using `TextFormat.printToUnicodeString`).
Set to true If you would like ScalaPB to generate `toString()` methods that use the single line
format.
**`asciiFormatToString`**: Setting this to true, overrides `toString` to
return a standard ASCII representation of the message by calling
`toProtoString`.
**`lenses`**: By default, ScalaPB generates lenses for each message for easy
updating. If you are not using this feature and would like to reduce code size
or compilation time, you can set this to `false` and lenses will not be
generated.
**`retainSourceCodeInfo`**: Retain source code information (locations,
comments) provided by protoc in the descriptors. Use the `location` accessor
to get that information from a descriptor.
| 31.589147 | 121 | 0.752883 | eng_Latn | 0.966029 |
e064991d95e5d3e78653b07ac2d8752f8e535e38 | 241 | md | Markdown | source/_courses/Agriculture-and-Horticulture-Level-3.md | RuapehuCollege/Website | 2cf4122115ea0a3bcfc0059f3ad17f23df79729b | [
"MIT"
] | null | null | null | source/_courses/Agriculture-and-Horticulture-Level-3.md | RuapehuCollege/Website | 2cf4122115ea0a3bcfc0059f3ad17f23df79729b | [
"MIT"
] | 1 | 2020-12-04T17:56:25.000Z | 2020-12-04T17:56:25.000Z | source/_courses/Agriculture-and-Horticulture-Level-3.md | RuapehuCollege/Website | 2cf4122115ea0a3bcfc0059f3ad17f23df79729b | [
"MIT"
] | 1 | 2019-11-13T11:20:34.000Z | 2019-11-13T11:20:34.000Z | ---
title: "Agriculture and Horticulture Level 3"
description: ""
year: "13"
credits: "15"
course_fees: ""
course_code: <course_code>
course_level: "NCEA 3"
assessment_type: "Achievement Standard"
subject: "Agriculture and Horticulture"
---
| 20.083333 | 45 | 0.746888 | eng_Latn | 0.79621 |
a6edaf008989cae1a9076fd082fddc69df755e1b | 2,811 | md | Markdown | 101-recovery-services-backup-vms/README.md | kollexy/azure-quickstart-templates | 02dd10e4004db1f52e772a474d460620ff975270 | [
"MIT"
] | 2 | 2018-02-12T15:33:16.000Z | 2019-06-03T15:18:16.000Z | 101-recovery-services-backup-vms/README.md | kollexy/azure-quickstart-templates | 02dd10e4004db1f52e772a474d460620ff975270 | [
"MIT"
] | 3 | 2020-07-07T20:40:19.000Z | 2022-03-08T21:12:04.000Z | 101-recovery-services-backup-vms/README.md | kollexy/azure-quickstart-templates | 02dd10e4004db1f52e772a474d460620ff975270 | [
"MIT"
] | 2 | 2020-10-24T13:29:25.000Z | 2022-01-03T04:13:00.000Z | # Backup Resource Manager VMs to Recovery Services Vault
<IMG SRC="https://azurequickstartsservice.blob.core.windows.net/badges/101-recovery-services-backup-vms/PublicLastTestDate.svg" />
<IMG SRC="https://azurequickstartsservice.blob.core.windows.net/badges/101-recovery-services-backup-vms/PublicDeployment.svg" />
<IMG SRC="https://azurequickstartsservice.blob.core.windows.net/badges/101-recovery-services-backup-vms/FairfaxLastTestDate.svg" />
<IMG SRC="https://azurequickstartsservice.blob.core.windows.net/badges/101-recovery-services-backup-vms/FairfaxDeployment.svg" />
<IMG SRC="https://azurequickstartsservice.blob.core.windows.net/badges/101-recovery-services-backup-vms/BestPracticeResult.svg" />
<IMG SRC="https://azurequickstartsservice.blob.core.windows.net/badges/101-recovery-services-backup-vms/CredScanResult.svg" />
<a href="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F101-recovery-services-backup-vms%2Fazuredeploy.json" target="_blank">
<img src="https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/1-CONTRIBUTION-GUIDE/images/deploytoazure.png"/>
</a>
<a href="http://armviz.io/#/?load=https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F101-recovery-services-backup-vms%2Fazuredeploy.json" target="_blank">
<img src="https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/1-CONTRIBUTION-GUIDE/images/visualizebutton.png"/>
</a>
This template will use existing recovery services vault and backup policy, and enables backup of VMs belonging to same Resource Group. Recovery Services vault and VMs should be in same Geo. When selecting Resource Group to which this template needs to be deployed, please select Resource Group corresponding to the vault.
To create new Recovery Services Vault, please use this existing template: [Create Recovery Services Vault] (https://github.com/Azure/azure-quickstart-templates/tree/master/101-recovery-services-vault-create)
To create Recovery Services Vault and Weekly Backup Policy, please use this existing template: [Create Recovery Services Vault and Weekly Backup Policy] (https://github.com/Azure/azure-quickstart-templates/tree/master/101-recovery-services-weekly-backup-policy-create)
To create Recovery Services Vault and Daily Backup Policy, please use this existing template: [Create Recovery Services Vault and Daily Backup Policy] (https://github.com/Azure/azure-quickstart-templates/tree/master/101-recovery-services-daily-backup-policy-create)
For more information, Visit [Back up Resource Manager VMs to a Recovery Services vault] https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm)
| 96.931034 | 322 | 0.810032 | yue_Hant | 0.252159 |
a6ee442f064a00579c5c69dec0f9ba327a786930 | 4,904 | md | Markdown | articles/azure-sql/database/arm-templates-content-guide.md | SkyChang/azure-docs.zh-tw | 549d15e2207fd02b09ecfad7768e6e960957939b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-sql/database/arm-templates-content-guide.md | SkyChang/azure-docs.zh-tw | 549d15e2207fd02b09ecfad7768e6e960957939b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-sql/database/arm-templates-content-guide.md | SkyChang/azure-docs.zh-tw | 549d15e2207fd02b09ecfad7768e6e960957939b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Resource Manager 範本 - Azure SQL Database 與 SQL 受控執行個體
description: 使用 Azure Resource Manager 範本建立並設定 Azure SQL Database 與 Azure SQL 受控執行個體。
services: sql-database
ms.service: sql-db-mi
ms.subservice: service
ms.custom: overview-samples sqldbrb=2
ms.devlang: ''
ms.topic: guide
author: jovanpop-msft
ms.author: jovanpop
ms.reviewer: sstein
ms.date: 02/04/2019
ms.openlocfilehash: 48a2c00f7ff487def13e9872c4f43a3ca36809ba
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: HT
ms.contentlocale: zh-TW
ms.lasthandoff: 10/09/2020
ms.locfileid: "91444639"
---
# <a name="azure-resource-manager-templates-for-azure-sql-database--sql-managed-instance"></a>適用於 Azure SQL Database 與 SQL 受控執行個體的 Azure Resource Manager 範本
[!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
Azure Resource Manager 範本可讓您定義基礎結構即程式碼，並將解決方案部署至 Azure 雲端，以供 Azure SQL Database 與 SQL 受控執行個體使用。
## <a name="azure-sql-database"></a>[Azure SQL Database](#tab/single-database)
下表包含適用於 Azure SQL Database 的 Azure Resource Manager 範本的連結。
|連結 |描述|
|---|---|
| [SQL Database](https://github.com/Azure/azure-quickstart-templates/tree/master/201-sql-database-transparent-encryption-create) | 此 Azure Resource Manager 範本可在 Azure SQL Database 中建立單一資料庫，並設定伺服器層級 IP 防火牆規則。 |
| [Server](https://github.com/Azure/azure-quickstart-templates/tree/master/101-sql-logical-server) | 此 Azure Resource Manager 範本可建立 Azure SQL Database 的伺服器。 |
| [彈性集區](https://github.com/Azure/azure-quickstart-templates/tree/master/101-sql-elastic-pool-create) | 此範本可讓您部署彈性集區，並對其指派資料庫。 |
| [容錯移轉群組](https://github.com/Azure/azure-quickstart-templates/tree/master/101-sql-with-failover-group) | 此範本可在 Azure SQL Database 中建立兩部伺服器、單一資料庫與一個容錯移轉群組。|
| [威脅偵測](https://github.com/Azure/azure-quickstart-templates/tree/master/201-sql-threat-detection-db-policy-multiple-databases) | 此範本可讓您部署啟用「威脅偵測」的伺服器與一組資料庫，並且為每個資料庫部署警示的電子郵件地址。 「威脅偵測」包含在 SQL 進階威脅防護 (ATP) 供應項目中，可提供一層安全性來防禦伺服器與資料庫所受到的潛在威脅。|
| [將稽核資料移至 Azure Blob 儲存體](https://github.com/Azure/azure-quickstart-templates/tree/master/201-sql-auditing-server-policy-to-blob-storage) | 此範本可讓您部署啟用稽核的伺服器，以將稽核記錄寫入至 Blob 儲存體。 Azure SQL Database 的稽核可追蹤資料庫事件，並將其寫入至可存放在 Azure 儲存體帳戶、OMS 工作區或事件中樞的稽核記錄中。|
| [將稽核資料移至 Azure 事件中樞](https://github.com/Azure/azure-quickstart-templates/tree/master/201-sql-auditing-server-policy-to-eventhub) | 此範本可讓您部署啟用稽核的伺服器，以將稽核記錄寫入至現有的事件中樞。 若要將稽核事件傳送到事件中樞，請設定 `Enabled` `State` 的稽核設定，並將 `IsAzureMonitorTargetEnabled` 設為 `true`。 此外，請在 `master` 資料庫上設定 `SQLSecurityAuditEvents` 記錄類別的診斷設定 (用於服務層級稽核)。 稽核可追蹤資料庫事件，並將其寫入至可存放在 Azure 儲存體帳戶、OMS 工作區或事件中樞的稽核記錄中。|
| [Azure Web 應用程式與 SQL Database](https://github.com/Azure/azure-quickstart-templates/tree/master/201-web-app-sql-database) | 此範本可在「基本」服務層級，於 Azure SQL Database 中建立免費的 Azure Web 應用程式與資料庫。|
| [Azure Web 應用程式、Redis 快取與 SQL Database](https://github.com/Azure/azure-quickstart-templates/tree/master/201-web-app-redis-cache-sql-database) | 此範本可在相同的資源群組中建立 Web 應用程式、Redis 快取和資料庫，並且在 Web 應用程式中針對資料庫和 Redis 快取建立兩個連接字串。|
| [使用 ADF V2 從 Blob 儲存體匯入資料](https://github.com/Azure/azure-quickstart-templates/tree/master/101-data-factory-v2-blob-to-sql-copy) | 此 Azure Resource Manager 範本可建立能夠將資料從 Azure Blob 儲存體複製到 SQL Database 的 Azure Data Factory V2 執行個體。|
| [HDInsight 叢集與資料庫](https://github.com/Azure/azure-quickstart-templates/tree/master/101-hdinsight-linux-with-sql-database) | 此範本可讓您建立 HDInsight 叢集、邏輯 SQL 伺服器、資料庫與兩個資料表。 [搭配使用 Sqoop 與 HDInsight 中的 Hadoop](https://docs.microsoft.com/azure/hdinsight/hadoop/hdinsight-use-sqoop) 一文中使用了此範本。 |
| [依排程執行 SQL 預存程序的 Azure 邏輯應用程式](https://github.com/Azure/azure-quickstart-templates/tree/master/101-logic-app-sql-proc) | 此範本可讓您建立會依排程執行 SQL 預存程序的邏輯應用程式。 此程序的任何引數都可放入範本的本文區段中。|
## <a name="azure-sql-managed-instance"></a>[Azure SQL 受控執行個體](#tab/managed-instance)
下表包含適用於 Azure SQL 受控執行個體之 Azure Resource Manager 範本的連結。
|連結|描述|
|---|---|
| [新 VNet 中的 SQL 受控執行個體](https://github.com/Azure/azure-quickstart-templates/tree/master/101-sqlmi-new-vnet) \(英文\) | 此 Azure Resource Manager 範本可在虛擬網路中建立新設定的 Azure 虛擬網路和受控執行個體。 |
| [SQL 受控執行個體的網路環境](https://github.com/Azure/azure-quickstart-templates/tree/master/101-sql-managed-instance-azure-environment) \(英文\) | 此部署會建立已設定的 Azure 虛擬網路和兩個子網路，一個專門用於您的受控執行個體，另一個則可用來放置其他資源 (例如 VM、App Service 環境等)。 此範本會建立已適當設定的網路環境，供您在其中部署受控執行個體。 |
| [具有 P2S 連線的 SQL 受控執行個體](https://github.com/Azure/azure-quickstart-templates/tree/master/201-sqlmi-new-vnet-w-point-to-site-vpn) \(英文\) | 此部署會建立具有兩個子網路 `ManagedInstance` 和 `GatewaySubnet` 的 Azure 虛擬網路。 SQL 受控執行個體將部署在 ManagedInstance 子網路中。 虛擬網路閘道會建立在 `GatewaySubnet` 子網路中，並設定點對站 VPN 連線。 |
| [SQL 受控執行個體與虛擬機器](https://github.com/Azure/azure-quickstart-templates/tree/master/201-sqlmi-new-vnet-w-jumpbox) | 此部署會建立具有兩個子網路 `ManagedInstance` 和 `Management` 的 Azure 虛擬網路。 SQL 受控執行個體將部署在 `ManagedInstance` 子網路中。 具有最新版 SQL Server Management Studio (SSMS) 的虛擬機器會部署在 `Management` 子網路中。 |
---
| 84.551724 | 378 | 0.789152 | yue_Hant | 0.641814 |
a6ee9eda40e0e10d18de79362ec78dc7ab269411 | 122 | md | Markdown | src/posts/day83.md | annaaleksandra/155-days-of-lock-down | 6134ce56a75e2e6d6b2acef46a36eb527fc37e6b | [
"RSA-MD"
] | null | null | null | src/posts/day83.md | annaaleksandra/155-days-of-lock-down | 6134ce56a75e2e6d6b2acef46a36eb527fc37e6b | [
"RSA-MD"
] | null | null | null | src/posts/day83.md | annaaleksandra/155-days-of-lock-down | 6134ce56a75e2e6d6b2acef46a36eb527fc37e6b | [
"RSA-MD"
] | null | null | null | ---
title: "Another Boring Day"
date: "08-06-2020"
id: 83
---
Anna's shopping day. <br><br>
Pokemon, Brooklyn 99 and GTA. | 15.25 | 29 | 0.655738 | eng_Latn | 0.695047 |
a6eef454ece27c9c869f2d9dfe806d7edbcac089 | 6,802 | md | Markdown | aws/solutions_architect_exam.md | richard-sistern/aleph | 94c560ccc3b79d0a524abfa4c7c44375974d7882 | [
"MIT"
] | 1 | 2021-03-09T12:18:23.000Z | 2021-03-09T12:18:23.000Z | aws/solutions_architect_exam.md | richard-sistern/aleph | 94c560ccc3b79d0a524abfa4c7c44375974d7882 | [
"MIT"
] | null | null | null | aws/solutions_architect_exam.md | richard-sistern/aleph | 94c560ccc3b79d0a524abfa4c7c44375974d7882 | [
"MIT"
] | null | null | null | # AWS: Solutions Architect Exam
*Architect and deploy secure and robust solutions on AWS*
Useful Links
- [AWS exam resources](https://aws.amazon.com/certification/certified-solutions-architect-associate/)
- [AWS training and certification](https://aws.amazon.com/training/)
- [Self-paced labs](https://aws.amazon.com/training/self-paced-labs/)
- [Exam preparation](https://aws.amazon.com/certification/certification-prep/)
Re-certification is every 3 years. A **discount** is available in the benefits section of the certification site.
## Exam Overview
### Question Domains
- Design resilient architectures
- Design high performing architectures
- Design secure applications and architectures
- Design cost optimised architectures
### Considerations
- Expect 'single AZ' will never be a right answer
- Use of AWS managed services should always be preferred
- Fault tolerant and high availability are not the same thing
- Expect that everything will fail at some point and design accordingly
- Using caching strategies to improve performance
- If data in unstructured S3 is generally the storage solution
- IAM roles are easier and safer than keys and passwords
- Monitor metrics across the system
- Provide alerts for anomalous consideration
- Lock down AWS account root user
- Security groups only allow. Network ACLs allow explicit deny
- Prefer IAM Roles to access keys
- If you know it's going to be on, reserve it
- Determine the most cost-effective EC2 pricing model and instance type for each workload
- Unused CPU time is a waste of money
- Use the most cost-effective data storage service and class
## Services and Concepts
### General
AMI IDs are different in each region as stored in regional S3 buckets.
#### Scaling
Can have for multiple resources or EC2 specific
**Vertical:** Small to Large
**Horizontal**: 1 to x
### EC2 Instance Store
Some can have `ephemeral` volumes for buffer, scratch type data.
### Elastic Block Store (EBS)
Attaches in same availability zone. `Persistent` storage independent of instances. Several types
- General purpose SSD (gp2)
- Provisioned IOPS SSD (io1)
- Throughput optimised HDD (st1)
- Cold HDD (sc1)
By default EBS can't be attached to more than one EC2 instance. Automatically replicated within an availability zone
Amazon EBS FAQs: https://aws.amazon.com/ebs/faqs/
Whitepaper – AWS Storage Services Overview: https://d0.awsstatic.com/whitepapers/Storage/AWS Storage Services Whitepaper-v9.pdf
SPL Lab – Introduction to Amazon Elastic Block Store: https://amazon.qwiklabs.com/catalog?keywords=Introduction+to+Amazon+Elastic+Block+Store+(EBS)&format[]=any&level[]=any&duration[]=any&price[]=any&modality[]=any&language[]=any
Amazon EC2 Instance Store: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html
### Simple Queue Service (SQS)
Helps to decouple services.
Web Server > ELB > Logging Service [1, 2, 3] > Dynamo DB
### Elastic Load Balancing (ELB)
- Network load balancer (OSI layer 4). Suitable for TCP packets and high performance applications
- Application load balancer (OSI layer 7). Suitable for HTTP/HTTPS and supports TLS
Elastic Load Balancing Documentation: https://aws.amazon.com/documentation/elastic-load-balancing/
Amazon SQS FAQs: https://aws.amazon.com/sqs/faqs/
Elastic Load Balancing FAQs: https://aws.amazon.com/elasticloadbalancing/faqs/
Amazon EC2 FAQs: https://aws.amazon.com/ec2/faqs/
Amazon Route 53 Documentation: https://aws.amazon.com/documentation/route53/
### Elastic File System (EFS)
Shared storage with elastic capacity. Create and mount EFS in VPC, can spread across availability zones to numerous EC2 instances. Recommended to access file system from a mount target in the same availability zone.
### Simple Storage Services (S3)
Encryption at rest (SSE-S3, SSE-KMS, SSE-C)
Encryption in transit (TLS)
Allows versioning, has immutable objects. Doesn't span across regions
**Access Control**
- Object ACL
- Bucket ACL
- Bucket policies
- IAM policies
**Costs**
- GBs per month
- Transfer out of region
- PUT, COPY, POST, LIST, and GET requests
**Free**
- Transfer into S3
- Transfer out from S3 to another service in region
**Storage Classes**
- General Purpose (standard)
- Infrequently Accessed Data (Standard-infrequent access)
Lifecycle Policies
Allows you to delete or move objects based on age.
### Glacier
Data backup and archive storage.
### Fault Tolerance
Loosely couple service tiers, for example:
Web Servers [1 ,2 ,3] > Load Balancer > Application Servers [1, 2, 3]
[AWS Well Architected Framework](https://aws.amazon.com/architecture/well-architected/)
### CloudFormation
Service for deploying and managing AWS resources in a consistent and reproducible manner. Infrastructure as Code.
- Template (definition of resources to create in JSON)
- Stack (collection of AWS resources)
Use mappings to specify base AMI ID if working across regions.
### Lambda
Fully managed compute service to run stateless code.
Use CloudWatch Logs to view output of print statements.
### RDS (SQL)
Can have read replicas for enhanced performance.
Host primary and standby in different availability zones.
Supports complex transactions and a medium-to-high query/write rate
### Dynamo DB (NoSQL)
Has provisioned throughput
### CloudFront
Hosts static and dynamic content at edge locations.
### ElastiCache
Sits in front of read heavy services like RDS, DyamoDB and MongoDB.
Also supports Memcached and Redis
### CloudWatch
Monitoring service which can trigger alarms to start an auto-scaling event.
Example Metrics
- CPU %
- Read throughput
- Write throughput
### Security
**Shared Responsibility Model**
Customers are responsible for security `in` the cloud
AWS are responsible for the security `of` the cloud
**Identity and Access Management (IAM)**
Least privilege management of users, groups, roles
**Key Management Service (KMS)**
Multi-tenant
Managed keys and can host customer key data
Can be used to encrypt EBS volumes
**Cloud HSM**
Single-tenant
Hardware based key management. Can only be managed by the customer
### Virtual Private Cloud (VPC)
Design network architecture in the cloud, covers:
- Security
- Network isolation
- Management of IP addresses
- Internet accessibility (subnet)
- Routing
Security group is associated with an elastic network interface and only support allow rules. Stateful (if allowed in then allowed out)
Network ACLs are associated with a subnet and supports allow and deny rules. Stateless (have to allow both in and out)
### Cost Optimisation
Serverless provides an opportunity to reduce compute spend.
The are no costs between S3 and CloudFront. This can also reduce compute on EC2 instances.
Reserved and spot EC2 instances
| 26.570313 | 229 | 0.769921 | eng_Latn | 0.944178 |
a6ef3046e63c763edbeec9ee3e995758938afa04 | 9,021 | md | Markdown | content/practices/ipm/index.md | ekultails/tanzu-dev-portal | 056b029524b5e8e0becd932c7dd135bc1e8f9e5b | [
"Apache-2.0"
] | null | null | null | content/practices/ipm/index.md | ekultails/tanzu-dev-portal | 056b029524b5e8e0becd932c7dd135bc1e8f9e5b | [
"Apache-2.0"
] | null | null | null | content/practices/ipm/index.md | ekultails/tanzu-dev-portal | 056b029524b5e8e0becd932c7dd135bc1e8f9e5b | [
"Apache-2.0"
] | null | null | null | ---
title: "Iteration Planning Meetings (IPM)"
linkTitle: "Iteration Planning Meetings (IPM)"
description: "A regular meeting for the core team to understand and align on the work to be done."
# Note: remove any tags that are not relevant.
tags: ["Delivery"]
length: "1 Hour"
participants: "Core delivery team"
# custom "cover" image example: "boris/boris.png"
image: "default-cover.png"
lastmod: "2021-06-17"
date: "2021-06-17"
why:
- Regular planning meetings help ensure the product backlog is well-understood by all team members and always reflects the current priorities. By discussing and sizing product backlog items, the team may align on the delivery impact of the work to be done.
when:
- Iteration Planning Meetings should generally follow the cadence of product iterations (e.g. weekly) or should be held as often as needed to maintain a well-sized and well-understood product backlog.
what:
- A product backlog
- A prepared set of prioritized user stories to be reviewed and potentially promoted to the product backlog
# If this practice or workshop has a Miro template: remote: true
remote: false
miro_template_url: "URL for related Miro template"
---
## How to Use this Method
### Sample Agenda & Prompts
1. Start by framing the conversation for the meeting. Help to set overall project context as needed by briefly recapping recently accepted and in-progress stories or the current state of the newest capabilities in your acceptance environment, to get everyone aligned on where things currently stand as you enter this next iteration. Review the arc of new user stories by outlining what they will add to the product. Present user interface mockups, if available.
1. Read through the first user story to explain the business value, the user value, and the acceptance criteria. Allow participants to ask questions, providing clarifications as needed.
{{< callout >}}
Tip: Allow space for all members of the team to get the clarifications they need to provide an estimate they feel comfortable with. Beware of individual personalities taking over the conversation or dictating approaches that prevent full team understanding.
{{< /callout >}}
1. Prompt the engineers to indicate if they are ready to estimate the user story and if so, to estimate the relative complexity of the story by simultaneously voting on a story point estimate.
Please see the [short guide to estimation](#estimation) below for estimation tips.
1. If there is a consensus on the estimation, label the user story with the estimation result and promote it to the backlog, indicating to the team the priority of this story. Otherwise, if there is no consensus, prompt the engineers to discuss, and re-estimate if necessary until there is a consensus that the team is happy with.
{{< callout >}}
Tip 1: Try to prevent the conversation from taking too long or veering too far from the scope of this user story. If there is a large amount of uncertainty or disagreement on the scope of this story, it may be necessary to add a chore to the product backlog for investigating or experimenting before this story can be reasonably estimated in a future IPM.
{{< /callout >}}
{{< callout >}}
Tip 2: User stories should remain implementation-agnostic. While some discussion on implementation will naturally arise when estimating relative complexity, try and keep these discussions high-level and park any deep dives on implementation.
{{< /callout >}}
1. Repeat steps 2-4 for the remaining user stories that were prepared for this meeting.
{{< callout >}}
Tip: Use the time available to discuss and estimate as many user stories as were prepared. If necessary, some user stories may be deferred to the next Iteration Planning Meeting. Avoid taking more time than planned, sapping valuable energy from the team
{{< /callout >}}
1. In the final 10 minutes of the meeting, review and discuss the relative priorities of product backlog items, including any engineering chores.
{{< callout >}}
Tip: Prompt the engineers to advise on the scope and importance of chores they wish to promote to the product backlog.
{{< /callout >}}
### Success/Expected Outcomes
Firstly, the team should have a shared understanding of the scope and relative complexity of the product backlog items that were discussed. Secondly, items should have been added to the product backlog, which remains sorted according to current priorities. The team should come away from IPM feeling aligned and energized about the work coming up in the next iteration.
## Facilitator Notes & Tips
- To make IPMs run more efficiently, try to ensure the user stories to be discussed in the meeting have been suitably groomed beforehand. Collaborate with a designer and an engineer to ensure the stories are actionable and meet the INVEST criteria. Avoid trying to hurriedly write stories during the meeting.
- Encourage engineers to create necessary chores and if necessary, work with the engineers to prioritize and groom those chores before the IPM.
- Only hold an IPM if you have already prepared user stories to be discussed and estimated, and your product backlog contains less than 3 iterations of work, according to average team velocity. If you estimate too far out, then estimates may be less accurate and the team may forget the context by the time they begin work on those user stories.
### A Short Guide to Estimation {id=estimation}
- If there are user stories in the product backlog that were estimated more than 3 iterations ago, consider spending time scheduled for the IPM to review and re-estimate upcoming user stories, if the team agrees it would be helpful.
- Complexity can be estimated relative to other user stories in the product backlog, or relative to a baseline user story.
- Relative complexity is an easier and more reliable way to estimate the size of a user story than the time it may take to complete the work.
- Estimates are typically quantified using “story points”, and the team should align beforehand on the point scale they will use throughout the project, for consistency (e.g. Fibonacci, linear, exponential).
- It’s important that the estimation be done simultaneously in order to avoid bias. A good way to do this is to have participants vote on the count of 3.
- Large story point estimates may suggest the user story should be broken down if the resulting smaller stories can still be valuable to users.
- User stories may be estimated to have 0 story points when there is little or no work to be done beyond acceptance testing/verification.
- It’s OK for story point estimations to be imprecise. The same team working on the same product generally makes more accurate and consistent estimates over time as discrepancies average out.
- Estimation should typically be done only by engineers, or those who will be delivering the work. Other roles, such as Testers and Architects, may contribute when they have a sufficient understanding of the relative complexity.
## Related Practices
### Sprint Planning vs. Iteration Planning
[Scrum “Sprints”](https://en.wikipedia.org/wiki/Scrum_(software_development)#Sprint_planning) and “Iterations” are both timeboxed activities but with some differences that impact how planning is done:
{{< table "table" >}}
| | Sprint Planning | Iteration Planning |
| ---- | ---- | ---- |
| **Prerequisites** | • A Sprint Goal<br>• A prioritized Product Backlog | • A prioritized Product Backlog<br>• User stories to be reviewed |
| **Objective** | • Align on a goal for the Sprint<br>• Negotiate and plan the scope for the Sprint (a.k.a. the Sprint Backlog) | • Maintain a shared understanding of the current scope and priorities (i.e. the Product Backlog) |
| **Activities** | • Review user stories<br>• Pull user stories from the Product Backlog to the Sprint Backlog | • Review user stories<br> • Estimate user stories<br> • Promote user stories to the Product Backlog according to priority |
| **Outputs** | • An unprioritized Sprint Backlog that the team commits to deliver and demonstrate at the end of the Sprint | • A prioritized Product Backlog<br> • An estimation of the work that may be delivered and demonstrated during the Iteration |
| **Participants** | • Product Owner<br> • Engineers | • Core team |
{{</ table >}}
### Variations
None at the moment.
### Preceding
[Iteration pre-planning](/practices/iteration-pre-planning) (optional)
### Following
None at the moment.
## Real World Examples
## Recommended Reading
[Agile Estimating and Planning](https://www.amazon.com/Agile-Estimating-Planning-Mike-Cohn/dp/0131479415) by Mike Cohn
[Yesterday’s Weather](http://wiki.c2.com/?YesterdaysWeather)
[Planning Poker](https://en.wikipedia.org/wiki/Planning_poker)
Chapter 12 of [Extreme Programming Explained](https://www.goodreads.com/book/show/67833.Extreme_Programming_Explained) by Kent Beck, Cynthia Andres
[ExtremeProgramming.org](http://www.extremeprogramming.org/rules/iterationplanning.html) | 75.175 | 461 | 0.776743 | eng_Latn | 0.998853 |
a6ef61cbb9bb59d45a4a52984f06ce8740c650c6 | 405 | md | Markdown | _posts/2019-09-15-COMP051-Project-One.md | Ambamore2000/Ambamore2000.github.io | 2e84d015f95fd43af55240943477132744fa3a82 | [
"MIT"
] | null | null | null | _posts/2019-09-15-COMP051-Project-One.md | Ambamore2000/Ambamore2000.github.io | 2e84d015f95fd43af55240943477132744fa3a82 | [
"MIT"
] | 4 | 2020-02-26T13:11:19.000Z | 2021-09-28T00:07:05.000Z | _posts/2019-09-15-COMP051-Project-One.md | Ambamore2000/Ambamore2000.github.io | 2e84d015f95fd43af55240943477132744fa3a82 | [
"MIT"
] | null | null | null | ---
layout: runc++
title: COMP051 - Project One
code: http://onlinegdb.com/embed/js/BJOrW1h0B?theme=light
tags: [COMP051]
---
## Project Task
{: .center-block :}
{: .center-block :}
{: .center-block :}
## Program
| 27 | 82 | 0.708642 | yue_Hant | 0.261516 |
a6ef88097e3bb947fe634be7686a3e52877d3fab | 3,134 | md | Markdown | README.md | CPwithAJ/DailyOneCodingQuestion | a8c0d168e127b24694d6cd54d9022d6313b27176 | [
"MIT"
] | 2 | 2019-08-12T04:27:47.000Z | 2019-08-12T12:28:53.000Z | README.md | CPwithAJ/DailyOneCodingQuestion | a8c0d168e127b24694d6cd54d9022d6313b27176 | [
"MIT"
] | null | null | null | README.md | CPwithAJ/DailyOneCodingQuestion | a8c0d168e127b24694d6cd54d9022d6313b27176 | [
"MIT"
] | 3 | 2019-08-03T16:03:48.000Z | 2019-08-12T05:52:20.000Z | # Daily One Coding Question
This repository is collection of solutio asked in Competitive programming group https://t.me/cpwithaj
## Here's the list of Questions (for easy access)
[Day 1 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day1/README.md)
[Day 2 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day2/README.md)
[Day 3 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day3/README.md)
[Day 4 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day4/README.md)
[Day 5 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day5/README.md)
[Day 6 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day6/README.md)
[Day 7 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day7/README.md)
[Day 8 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day8/README.md)
[Day 9 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day9/README.md)
[Day 10 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day10/README.md)
[Day 11 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day11/README.md)
[Day 12 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day12/README.md)
[Day 13 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day13/README.md)
[Day 14 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day14/README.md)
[Day 15 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day15/README.md)
[Day 16 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day16/README.md)
[Day 17 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day17/README.md)
[Day 18 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day18/README.md)
[Day 19 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day19/README.md)
[Day 20 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day20/README.md)
[Day 21 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day21/README.md)
[Day 22 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day22/README.md)
[Day 23 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day23/README.md)
[Day 24 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day24/README.md)
[Day 25 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day25/README.md)
[Day 26 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day26/README.md)
[Day 27 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day27/README.md)
[Day 28 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day28/README.md)
[Day 29 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day29/README.md)
[Day 30 Question](https://github.com/CPwithAJ/DailyOneCodingQuestion/blob/master/Day30/README.md)
| 47.484848 | 101 | 0.80568 | yue_Hant | 0.982149 |
a6f07877b454517ef3b9a1336fce1e549d37435d | 1,376 | md | Markdown | class-week-06/references.md | flavio92ux/aceleracao-DataScience | 2b2e41ec6c9184e161bdc66af0063792f09ce88d | [
"MIT"
] | 2 | 2020-06-16T00:59:25.000Z | 2020-07-03T23:26:36.000Z | class-week-06/references.md | flavio92ux/aceleracao-DataScience | 2b2e41ec6c9184e161bdc66af0063792f09ce88d | [
"MIT"
] | 9 | 2020-11-18T23:24:00.000Z | 2022-01-13T02:51:57.000Z | class-week-06/references.md | flavio92ux/aceleracao-DataScience | 2b2e41ec6c9184e161bdc66af0063792f09ce88d | [
"MIT"
] | 5 | 2020-06-25T21:29:06.000Z | 2022-03-13T18:10:50.000Z | # Referências (Semana 6)
- _StackExchange - Relationship between SVD and PCA. How to use SVD to perform PCA?_
(StackExchange - Relação entre SVD e PCA. Como usar o SVD para executar o PCA?)
Link: https://stats.stackexchange.com/questions/134282/relationship-between-svd-and-pca-how-to-use-svd-to-perform-pca
- _In Depth: Principal Component Analysis_ (Em Profundidade: Análise de Componentes Principais)
Link: https://jakevdp.github.io/PythonDataScienceHandbook/05.09-principal-component-analysis.html
- _In-Depth: Manifold Learning_ (Em Profundidade: Aprendizagem Múltipla)
Link: https://jakevdp.github.io/PythonDataScienceHandbook/05.10-manifold-learning.html
- _Recursive Feature Elimination_ (Eliminação Recursiva de Recursos)
Link: https://bookdown.org/max/FES/recursive-feature-elimination.html
- _A Tutorial on Principal Component Analysis_ (Um tutorial sobre análise de componentes principais)
Link: http://www.cs.otago.ac.nz/cosc453/student_tutorials/principal_components.pdf
- _Principal Component Analysis Explained_ (Análise dos componentes principais explicada)
Link: https://www.kaggle.com/nirajvermafcb/principal-component-analysis-explained
- _Step Forward Feature Selection: A Practical Example in Python_ (Seleção avançada de recursos: um exemplo prático em Python)
Link: https://www.kdnuggets.com/2018/06/step-forward-feature-selection-python.html
| 57.333333 | 126 | 0.8125 | por_Latn | 0.452578 |
a6f111e02ef0aed0279d96516ac5dd37d1ab4600 | 219 | md | Markdown | README.md | andrewthad/unlifted | 9a103c71157f3001d73729fb4640db9a1f87f640 | [
"BSD-3-Clause"
] | 2 | 2019-09-11T17:55:06.000Z | 2019-11-27T05:22:02.000Z | README.md | andrewthad/unlifted | 9a103c71157f3001d73729fb4640db9a1f87f640 | [
"BSD-3-Clause"
] | null | null | null | README.md | andrewthad/unlifted | 9a103c71157f3001d73729fb4640db9a1f87f640 | [
"BSD-3-Clause"
] | null | null | null | # unlifted
Sadly, the library is currently useless and will not be released to
hackage any time soon.
[GHC issue #17178](https://gitlab.haskell.org/ghc/ghc/issues/17178)
is a problem that renders this library useless.
| 31.285714 | 67 | 0.780822 | eng_Latn | 0.997241 |
a6f13fbe69dc77f8fd8d9609abc363d968108253 | 649 | md | Markdown | README.md | LukasBicus/wedding | 4cc96e59c6883c1653cf84e6377264234c1c919a | [
"MIT"
] | null | null | null | README.md | LukasBicus/wedding | 4cc96e59c6883c1653cf84e6377264234c1c919a | [
"MIT"
] | null | null | null | README.md | LukasBicus/wedding | 4cc96e59c6883c1653cf84e6377264234c1c919a | [
"MIT"
] | null | null | null | <!-- AUTO-GENERATED-CONTENT:START (STARTER) -->
<p align="center">
<a href="https://janka-a-lukas.sk/">
<img alt="My wedding" src="src/images/postavicky-v-srdci.svg" width="147" height="150"/>
</a>
</p>
<h1 align="center">
My Wedding page
</h1>
## 🚀 Quick start
1. **Set up env**
Run command
```nvm use```
```npm config set ignore-scripts false``` // sharp plugin needs to run post-instalation scripts
```npm install```
```npm config set ignore-scripts true``` // disable npm scripts again
2. **Use standard gatsby commands and have fun**
```gatsby develop```
```gatsby build```
```gatsby serve```
| 22.37931 | 99 | 0.616333 | eng_Latn | 0.312065 |
a6f18aec1f979f5fb6b466328776acea8602a280 | 797 | md | Markdown | programming/java/git-eclipse/clone.repo.ru.md | unikondy/EDUQATION | 722f7d8b4a5a484ae692f4d47fa1d7e1736acec5 | [
"MIT"
] | 5 | 2020-03-05T17:49:11.000Z | 2021-08-08T09:40:31.000Z | programming/java/git-eclipse/clone.repo.ru.md | unikondy/EDUQATION | 722f7d8b4a5a484ae692f4d47fa1d7e1736acec5 | [
"MIT"
] | 2 | 2019-10-13T13:00:36.000Z | 2019-10-16T20:05:52.000Z | programming/java/git-eclipse/clone.repo.ru.md | unikondy/EDUQATION | 722f7d8b4a5a484ae692f4d47fa1d7e1736acec5 | [
"MIT"
] | 23 | 2019-08-02T15:31:07.000Z | 2022-03-29T08:59:01.000Z | # Как получить репо (репозиторий - master)
1. Заходим в поиск (Quick access) пишем - git. Выпадает меню - выбирвает "Git Repositories". Это панель управления git - репозивотиями [image 1](./1.jpg).
2. В панели выбираем - "Clone Git Repository" и указываем адресс (ссылку на него) [image 2](./2.jpg) "NEXT"
3. Выбираем источник **master**, вбиваем свои данные и сохранить пароль "NEXT"
4. Выбираем путь для локальной копии проекта, следим чтобы было уточнено что мы читаем с **origin** отмечаем "Import All Projects ..." "NEXT" [image 3](./3.jpg)
5. Правый на соединение с панели репозиторий и выбираем - "Import Projects" [image 4](./4.jpg)
6. Проверяем путь, выбираем проект, и смотрим чтобы было отмечено "Detect and Configure project natures" - [image 5](./5.jpg) "FINISH"
7. Запускаем ПРОЕКТ | 99.625 | 160 | 0.735257 | rus_Cyrl | 0.931641 |
a6f18f1994e7fa7e68c1f3798e56e8abffa4f3c6 | 4,265 | md | Markdown | _posts/2016-07-13-DDCA.md | olympuslegum/olympuslegum.github.io | c2aae90c87fa38a953ce3cf845b2254afecf12ec | [
"MIT"
] | null | null | null | _posts/2016-07-13-DDCA.md | olympuslegum/olympuslegum.github.io | c2aae90c87fa38a953ce3cf845b2254afecf12ec | [
"MIT"
] | null | null | null | _posts/2016-07-13-DDCA.md | olympuslegum/olympuslegum.github.io | c2aae90c87fa38a953ce3cf845b2254afecf12ec | [
"MIT"
] | null | null | null | ---
layout: single
title: "DDCA and the shady business: Retd Justice Mudgal report suggests to bring the DDCA under the BCCI ambit"
comments: true
share: true
date: 2016-07-13 14:05:18 +0530
author_profile: true
author: Pranav Pathak
tags: Sports
header:
teaser: posts/DDCAMudgal/1.jpg
---
In the harshest criticism yet, Retd Justice Mukul Mudgal in his report on the working of Delhi District Cricket Association (DDCA) on behalf of the Delhi High Court made scathing comments and recommendations of the murky/shady business at the District Cricket Association. The report openly named BCCI’s & DDCA’s Vice President C. K. Khanna in the report in promoting corruption with lack of transparency and accountability.
The report has been filed after overseeing the working of the World T-20 tournament and the IPL matches in 2016. It outlines issues such as the Tendering process, Conflict of Interest, proxy voting etc are few of the biggest detriments in combating corruption in the tainted organization. The first mandate which the reports gives is to bring the DDCA under an ad-hoc body or a committee appointed by the BCCI in order to manage the daily affair of the DDCA under its arm.
<figure class="half">
<a href="/images/posts/DDCAMudgal/1.jpg"><img src="/images/posts/DDCAMudgal/1.jpg"></a>
<figcaption>Retd Justice Mukul Mudgal (Picture credit: NEWS18)</figcaption>
</figure>
Further, the report also suggested of disbanding/abolishing the Sports Working Committee (SWC) of the DDCA as it clearly infringes into the working of the DDCA executive committee or constituting a separate committee with 5 international or national cricketers of repute, one senior coach, two members of affiliated clubs and members of institutional clubs with BCCI as the parent body governing the District association.
The report also calls for a ban on alcohol, which was served during the time of the matches to the executive committee members as well as the other people of the organization. The various office bearers also came under the scanner for trying to gain as many free passes and accreditations cards as possible, which entitle the holder to watch the match for free and allowed freeholders enjoy hospitality at DDCA’s account.
In case of DDCA’s & BCCI’s Vice President C. K. Khanna, the criticism seemed like never ending as in order to protect his position on several occasions the proxy votes were used. It is because of these proxies that, he holds a strong influence and further getting things done via devious and conniving means. Mr Khanna had no interest whatsoever in promoting cricket in Delhi and is a credit monger, looking for Photo ops everywhere.
<blockquote>
Further, Mr. Khanna’s interests were strengthening his position in exchange of complimentaries to gain favor and in order to protect the proxies.
</blockquote>
There were several complaints made against Mr. Khanna in regards to the various kits, which were supposed to be distributed amongst the staff member. Some were distributed while to this day nobody knows where the rest of the kits went.
Mr. Khanna was in further controversy, as there is a humongous amount of Conflict of Interest in the organization with many of Mr. Khanna’s family members are being placed in the DDCA, also to bring in notice Mr. Khanna also himself is a part of the BCCI and one of its affiliated organization, that in itself is a violation of the Conflict of Interest policy. The report openly names him as an impediment for the development of cricket and asks for his removal for Cricket to prosper in the Capital. The allegations are however contradicted by Mr. Khanna.
The report also names finance committee member Mr. Subhash Sharma along with some other executive committee member influencing the tendering process and also helping a particular vendor in landing the catering contract. The committee’s recommendation is for the purpose of credibility, accountability and transparency in the tendering process, BCCI should intervene in order to meet the fair requirement of the tendering process free from the glitches of undue advantage and corruption.
All of the recommendations are based upon the daily working of the organization and are subjected at the perusal of the BCCI.
| 109.358974 | 557 | 0.805393 | eng_Latn | 0.999893 |
a6f1b361f84d1e60e8c13e0c61a4bea18dbf3029 | 4,301 | md | Markdown | docs/2014/relational-databases/databases/database-properties-transaction-log-shipping-page.md | sql-aus-hh/sql-docs.de-de | edfac31211cedb5d13440802f131a1e48934748a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-02-25T18:10:29.000Z | 2022-02-25T18:10:29.000Z | docs/2014/relational-databases/databases/database-properties-transaction-log-shipping-page.md | sql-aus-hh/sql-docs.de-de | edfac31211cedb5d13440802f131a1e48934748a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/relational-databases/databases/database-properties-transaction-log-shipping-page.md | sql-aus-hh/sql-docs.de-de | edfac31211cedb5d13440802f131a1e48934748a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Datenbankeigenschaften (Seite Protokollversand) | Microsoft-Dokumentation
ms.custom: ''
ms.date: 06/13/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology:
- database-engine
ms.topic: conceptual
f1_keywords:
- sql12.swb.databaseproperties.logshipping.f1
ms.assetid: 72c4e539-fe11-4d57-b977-65b418d5916f
author: stevestein
ms.author: sstein
manager: craigg
ms.openlocfilehash: 535e42083acf7f03c2fece85849b4298525213a3
ms.sourcegitcommit: 3da2edf82763852cff6772a1a282ace3034b4936
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 10/02/2018
ms.locfileid: "48169112"
---
# <a name="database-properties-transaction-log-shipping-page"></a>Datenbankeigenschaften (Seite Protokollversand)
Mithilfe dieser Seite können Sie die Eigenschaften des Protokollversands einer Datenbank konfigurieren und ändern.
Eine Erläuterung zu den Konzepten des Protokollversands finden Sie unter [Informationen zum Protokollversand (SQL Server)](../../database-engine/log-shipping/about-log-shipping-sql-server.md).
## <a name="options"></a>Tastatur
**Diese Datenbank als primäre Datenbank in einer Protokollversandkonfiguration aktivieren**
Aktiviert diese Datenbank als primäre Datenbank im Protokollversand. Aktivieren Sie dieses Kontrollkästchen, und konfigurieren Sie anschließend die übrigen Optionen auf dieser Seite. Wenn Sie dieses Kontrollkästchen deaktivieren, wird die Protokollversandkonfiguration für diese Datenbank aufgehoben.
**Sicherungseinstellungen**
Klicken Sie auf **Sicherungseinstellungen** , um die Parameter für Sicherungszeitplan, Speicherort, Warnung und Archivierung zu konfigurieren.
**Sicherungszeitplan**
Zeigt den zurzeit ausgewählten Sicherungszeitplan der primären Datenbank an. Zum Ändern dieser Einstellungen klicken Sie auf **Sicherungseinstellungen** .
**Letzte erstellte Sicherung**
Zeigt Uhrzeit und Datum der letzten Transaktionsprotokollsicherung an, die für die primäre Datenbank vorgenommen wurde.
**Sekundäre Serverinstanzen und Datenbanken**
Führt die für die primäre Datenbank zurzeit konfigurierten sekundären Serverinstanzen und Datenbanken auf. Markieren Sie eine Datenbank, und klicken Sie dann auf **...** , um Änderungen an den für diese sekundäre Datenbank verfügbaren Parametern vorzunehmen.
**Hinzufügen**
Klicken Sie auf **Hinzufügen** , um der Protokollversandkonfiguration der primären Datenbank eine sekundäre Datenbank hinzuzufügen.
**Entfernen**
Entfernt eine ausgewählte Datenbank aus dieser Protokollversandkonfiguration. Wählen Sie zuerst die Datenbank aus, und klicken Sie dann auf **Entfernen**.
**Überwachungsserverinstanz verwenden**
Richtet eine Überwachungsserverinstanz für die Protokollversandkonfiguration ein. Aktivieren Sie das Kontrollkästchen **Überwachungsserverinstanz verwenden** , und klicken Sie dann auf **Einstellungen** , um die Überwachungsserverinstanz anzugeben.
**Überwachungsserverinstanz**
Zeigt die für die Protokollversandkonfiguration zurzeit konfigurierte Überwachungsserverinstanz an.
**Einstellungen**
Konfiguriert die Überwachungsserverinstanz für eine Protokollversandkonfiguration. Klicken Sie auf **Einstellungen** , um die Überwachungsserverinstanz zu konfigurieren.
**Skript für Konfiguration erstellen**
Generiert ein Skript, das den Protokollversand mit den ausgewählten Parametern konfiguriert. Klicken Sie auf **Skript für Konfiguration erstellen**, und wählen Sie dann ein Ausgabeziel für das Skript aus.
> [!IMPORTANT]
> Bevor Sie ein Skript für die Einstellungen einer sekundären Datenbank erstellen, müssen Sie das Dialogfeld **Einstellungen für die sekundäre Datenbank** aufrufen. Durch das Aufrufen dieses Dialogfelds wird eine Verbindung mit dem sekundären Server hergestellt, und die aktuellen Eigenschaften der sekundären Datenbank, die zum Generieren des Skripts erforderlich sind, werden abgerufen.
## <a name="see-also"></a>Siehe auch
[Gespeicherte Prozeduren für den Protokollversand (Transact-SQL)](/sql/relational-databases/system-stored-procedures/log-shipping-stored-procedures-transact-sql)
[Protokollversandtabellen (Transact-SQL)](/sql/relational-databases/system-tables/log-shipping-tables-transact-sql)
| 61.442857 | 391 | 0.803069 | deu_Latn | 0.988678 |
a6f1d39be0691a4c151e2dea4bc49232c82a75b7 | 1,991 | md | Markdown | README.md | songxinglie/intrest | 1a08603f958122cdefc8b632a06e723c2648f5cd | [
"Apache-2.0"
] | null | null | null | README.md | songxinglie/intrest | 1a08603f958122cdefc8b632a06e723c2648f5cd | [
"Apache-2.0"
] | null | null | null | README.md | songxinglie/intrest | 1a08603f958122cdefc8b632a06e723c2648f5cd | [
"Apache-2.0"
] | null | null | null | # Intrest List
## CI/CD
- Drone
- Tekton
- https://github.com/hashicorp/waypoint
## ORM/CRUD
- sqltoy
## Infra
- https://github.com/GoogleContainerTools/jib/
- https://www.infoq.cn/article/hyi6km1EbkOeswFdVTy6 Redis 多租户集群的容器化实践
- https://www.infoq.cn/article/K49aV8ZQq08439D2kbiJ 5 款好用且有代表性的 GraphQL 工具
- https://www.aliyun.com/product/edas 云原生应用 PaaS
- https://www.aliyun.com/product/aliware/product/sae
```
Serverless 应用引擎（Serverless App Engine，简称 SAE）实现了Serverless 架构 + 微服务架构的完美融合，真正按需使用、按量计费，节省闲置计算资源，同时免去 IaaS 运维，有效提升开发运维效率。SAE 支持 Spring Cloud、Dubbo 等流行的微服务架构，支持控制台、Jenkins、云效、插件等部署方式。除了微服务应用外，您还能通过 Docker 镜像部署任何语言的应用
```
- https://github.com/quarkusio/quarkus
Quarkus is a Cloud Native, Container First framework for writing Java applications
- https://baijiahao.baidu.com/s?id=1688177068605201115 解读容器的 2020：寻找云原生的下一站
```
本地开发与测试
使能开发者面向 Kubernetes 进行本地开发和测试正在开始成为一个备受关注的话题，在这个领域中，来自纽约的 Tilt 项目是其中的佼佼者。阿里云和腾讯云有也分别有这个话题下的不同维度的解决方案，比如 KT Connet 和 Nocalhost。
```
- https://www.toutiao.com/a6881914961598087694/ 本地开发的微服务如何调用k8s的微服务
- https://github.com/didi/LogicFlow
- https://github.com/TommyLemon/APIAuto
- Spring Native
- https://github.com/fluxcd/flux
- https://github.com/derailed/popeye
-
## Event/Message
- https://github.com/kedacore/keda
- https://keda.sh/
- https://github.com/dapr/dapr
## Job/Task/Workflow
- https://github.com/apache/airflow/
- https://github.com/PowerJob/PowerJob
- https://cloud.tencent.com/developer/article/1676120 工作流和状态机
- https://github.com/serverlessworkflow/specification/blob/0.5.x/specification.md
- https://www.aliyun.com/product/fnf?spm=a2c4g.11174283.2.1.7857512bBEIku6 阿里Serverless 工作流
- https://github.com/zeebe-io/zeebe
## Mesh
- https://github.com/openservicemesh/osm
- https://github.com/kumahq/kuma
## Importance
- https://www.toutiao.com/a6881914961598087694/
- https://github.com/AliyunContainerService/kube-eventer
- https://github.com/json-path/JsonPath
## Misc
- https://github.com/521xueweihan/HelloGitHub
| 33.745763 | 218 | 0.771974 | yue_Hant | 0.822608 |
a6f1dd2e58ec24f8d50156f2f00ab0d83af65964 | 9,490 | md | Markdown | docs/nukkit_plugin.md | spigradle/spigradle | e42a3fe8d8d48c9b406e535dd5b84b3c981ebc8f | [
"Apache-2.0"
] | 65 | 2020-07-07T09:24:19.000Z | 2022-02-17T07:04:53.000Z | docs/nukkit_plugin.md | spigradle/spigradle | e42a3fe8d8d48c9b406e535dd5b84b3c981ebc8f | [
"Apache-2.0"
] | 60 | 2020-07-01T21:06:38.000Z | 2022-03-24T11:42:06.000Z | docs/nukkit_plugin.md | spigradle/spigradle | e42a3fe8d8d48c9b406e535dd5b84b3c981ebc8f | [
"Apache-2.0"
] | 11 | 2020-10-31T16:26:49.000Z | 2022-03-04T17:17:34.000Z | # Nukkit Plugin
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
The [NukkitX](https://github.com/NukkitX/Nukkit#introduction) plugin provides you to:
- Generate 'plugin.yml' with less configuration.
- Shortcuts for [dependency](../README.md#dependencies) and [repository](../README.md#repositories).
- Tasks for run server with your plugins for debug.
## Table of contents
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
- [Requirements](#requirements)
- [Usage](#usage)
- [Description file generation](#description-file-generation)
- [Main class detection](#main-class-detection)
- [Debug your plugin](#debug-your-plugin)
- [Configuration](#configuration)
- [Tasks](#tasks)
- [See also](#see-also)
## Requirements
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
The plugin requires Gradle 5.4.2+, recommends the latest.
To update your gradle wrapper:
```
gradlew wrapper --gradle-version 6.9.1 --distribution-type all
```
## Usage
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
[Full Example Here](https://github.com/spigradle/spigradle-sample/tree/master/nukkit)
Groovy DSL
```groovy
plugins {
id 'kr.entree.spigradle.nukkit' version '2.3.3'
}
```
Kotlin DSL
```kotlin
plugins {
id("kr.entree.spigradle.nukkit") version "2.3.3"
}
```
<details>
<summary>Groovy Legacy</summary>
```groovy
buildscript {
repositories {
gradlePluginPortal()
}
dependencies {
classpath 'kr.entree:spigradle:2.3.3'
}
}
apply plugin: 'kr.entree.spigradle.nukkit'
```
</details>
<details>
<summary>Kotlin Legacy</summary>
```groovy
buildscript {
repositories {
gradlePluginPortal()
}
dependencies {
classpath("kr.entree:spigradle:2.3.3")
}
}
apply(plugin = "kr.entree.spigradle.nukkit")
```
</details>
## Description file generation
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
The `plugin.yml` file will be generated by task `generateNukkitDescription` based on the [configuration of `nukkit`](#configuration), included into output jars automatically.
Basically the properties 'main', 'name' and 'version' defaults to [auto-detected main](#main-class-detection), [project.name](https://docs.gradle.org/current/javadoc/org/gradle/api/Project.html#getName--), [project.version](https://docs.gradle.org/current/javadoc/org/gradle/api/Project.html#getName--) respectively. So if we create a simple plugin that just needs those properties, we don't need any configuration. Only pay attention to your unique implementation.
You can configure all properties of `plugin.yml` in [nukkit {} block](#configuration).
## Main class detection
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
The plugin automatically finds the main class extends [PluginBase](https://ci.nukkitx.com/job/NukkitX/job/Nukkit/job/master/javadoc/index.html?overview-summary.html), and set the 'main' property to the class found.
You may present the main class using `@NukkitPlugin` or `@PluginMain`:
```java
import kr.entree.spigradle.annotations.NukkitPlugin;
@NukkitPlugin
public class SamplePlugin extends PluginBase { }
```
## Debug your plugin
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
Run your plugin with just execute single gradle task.
The `debugNukkit` performs to download Nukkit, copy it with your plugins into the default path `debug/nukkit`, and run it.
> These tasks copy your plugin and its dependency plugins.
You can pass (jvm)arguments:
```groovy
nukkit {
debug {
args '--nojline', '--max-players', '100'
jvmArgs '-Xmx16G'
}
}
```
This affects to `debugNukkit`, also `RunNukkit` [IDEA RunConfiguration](https://www.jetbrains.com/help/idea/run-debug-configuration-application.html).
More information: [Tasks](#tasks)
## Configuration
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
### nukkit - [NukkitExtension](TODO Javadoc)
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
The description of your plugin for a 'plugin.yml'.
About the `plugin.yml`, See [Official Sample](https://github.com/NukkitX/ExamplePlugin/blob/master/src/main/resources/plugin.yml#L1)
<details>
<summary>Groovy Example</summary>
```groovy
nukkit {
authors 'Me'
depends 'ProtocolLib', 'Vault'
api '1.0.5'
load STARTUP
commands {
give {
aliases 'giv', 'i'
description 'Give command.'
permission 'test.foo'
permissionMessage 'You do not have the permission!'
usage '/<command> [item] [amount]'
}
}
permissions {
'test.foo' {
description 'Allows foo command'
defaults 'true'
}
'test.*' {
description 'Wildcard permission'
defaults 'op'
children = ['test.foo': true]
}
}
}
```
</details>
<details>
<summary>Kotlin Example</summary>
```kotlin
nukkit {
authors = listOf("Me")
depends = listOf("SomePlugin")
api = listOf("1.0.5")
load = Load.STARTUP
commands {
create("give") {
aliases = listOf("i")
description = "Give command."
permission = "test.foo"
permissionMessage = "You do not have the permission!"
usage = "/<command> [item] [amount]"
}
}
permissions {
create("test.foo") {
description = "Allows foo command"
defaults = "true"
}
create("test.*") {
description = "Wildcard permission"
defaults = "op"
children = mapOf("test.foo" to true)
}
}
}
```
Without [type-safe accessors](https://docs.gradle.org/current/userguide/kotlin_dsl.html#sec:kotlin_using_standard_api):
```kotlin
configure<NukkitExtension> {
description = "A NukkitX plugin."
// ...
}
```
</details>
## Tasks
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
All tasks supports [UP-TO-DATE check](https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:up_to_date_checks).
<details>
<summary>Configuration Guide</summary>
Groovy:
```groovy
runNukkit {
jvmArgs('-Xmx8G')
}
```
Kotlin with type-safe accessors:
```kotlin
tasks {
runNukkit {
jvmArgs("-Xmx8G")
}
}
```
Kotlin without [type-safe accessors](https://docs.gradle.org/current/userguide/kotlin_dsl.html#sec:kotlin_using_standard_api):
```kotlin
tasks {
named<JavaExec>("runNukkit") {
jvmArgs("-Xmx8G")
}
}
```
Kotlin with property delegation
```kotlin
tasks {
val runNukkit by existing(JavaExec::clas) {
jvmArgs("-Xmx8G")
}
// Do something with 'runNukkit'
}
```
</details>
### detectNukkitMain - [SubclassDetection](TODO)
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
Finds the main class extends [cn.nukkit.plugin.PluginBase](https://ci.nukkitx.com/job/NukkitX/job/Nukkit/job/master/javadoc/index.html?overview-summary.html).
### generateNukkitDescription - [YamlGenerate](TODO)
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
*Depends on: `detectNukkitMain`*
Generates the description file 'plugin.yml'.
### debugNukkit
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
*Depends on: `prepareNukkitPlugins`, `downloadNukkit`, `runNukkit`*
Downloads NukkitX and runs it with your plugin and dependency plugins.
### prepareNukkitPlugins - [Copy](https://docs.gradle.org/current/dsl/org.gradle.api.tasks.Copy.html)
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
*Depends on: `build`*
Copies project plugin jar and its dependency plugins into the server plugins directory.
### downloadNukkit - [Download](TODO)
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
Downloads NukkitX.
### runNukkit - [JavaExec](https://docs.gradle.org/current/dsl/org.gradle.api.tasks.JavaExec.html)
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
Just runs the NukkitX jar at configured path even there's no executable file.
NOTE: Use `debugNukkit` instead of `runNukkit` if you need prepare process like download NukkitX jar, copy plugins.
### cleanDebug
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
Deletes all server files.
## See also
[comment]: <> (!! Do not edit this file but 'docs/templates' or 'docs/root-templates', See [CONTRIBUTING.md] !!)
- [The Spigot plugin](spigot_plugin.md)
- [The Bungeecord plugin](bungeecord_plugin.md)
- [README.md](../README.md)
- [Gradle Kotlin DSL Primer](https://docs.gradle.org/current/userguide/kotlin_dsl.html) | 27.270115 | 466 | 0.677555 | eng_Latn | 0.358764 |
a6f21988a47fcb4ba2802238d4286aba6bceddcd | 5,218 | md | Markdown | articles/virtual-machines/linux/move-vm.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | 43 | 2017-08-28T07:44:17.000Z | 2022-02-20T20:53:01.000Z | articles/virtual-machines/linux/move-vm.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | 676 | 2017-07-14T20:21:38.000Z | 2021-12-03T05:49:24.000Z | articles/virtual-machines/linux/move-vm.md | KreizIT/azure-docs.fr-fr | dfe0cb93ebc98e9ca8eb2f3030127b4970911a06 | [
"CC-BY-4.0",
"MIT"
] | 153 | 2017-07-11T00:08:42.000Z | 2022-01-05T05:39:03.000Z | ---
title: Déplacer une machine virtuelle à l’aide d’Azure CLI
description: Déplacez une machine virtuelle vers un autre abonnement ou groupe de ressources Azure à l’aide d’Azure CLI.
author: cynthn
ms.service: virtual-machines
ms.workload: infrastructure-services
ms.topic: how-to
ms.date: 09/12/2018
ms.author: cynthn
ms.openlocfilehash: b237c0a8cd6d242541b70f33e977287fe1a9d378
ms.sourcegitcommit: 557ed4e74f0629b6d2a543e1228f65a3e01bf3ac
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 10/05/2021
ms.locfileid: "129454940"
---
# <a name="move-a-vm-to-another-subscription-or-resource-group"></a>Déplacer une machine virtuelle vers un autre abonnement ou groupe de ressources
**S’applique à :** :heavy_check_mark: Machines virtuelles Linux :heavy_check_mark: Groupes identiques flexibles
Cet article vous explique comment déplacer une machine virtuelle entre des groupes de ressources ou des abonnements. Le déplacement d’une machine virtuelle entre abonnements peut être pratique si vous avez créé une machine virtuelle dans un abonnement personnel, et que vous souhaitez à présent la déplacer vers l’abonnement de votre entreprise.
> [!IMPORTANT]
>De nouveaux ID de ressource sont créés dans le cadre du déplacement. Une fois que la machine virtuelle a été déplacée, vous devez mettre à jour vos outils et vos scripts pour utiliser les nouveaux ID de ressource.
>
## <a name="use-the-azure-cli-to-move-a-vm"></a>Utiliser l’interface CLI Azure pour déplacer une machine virtuelle
Pour pouvoir déplacer votre machine virtuelle à l’aide de l’interface Azure CLI, vous devez vous assurer que les abonnements source et de destination se trouvent dans le même locataire. Pour vérifier que les deux abonnements ont le même ID de locataire, utilisez la commande [az account show](/cli/azure/account).
```azurecli-interactive
az account show --subscription mySourceSubscription --query tenantId
az account show --subscription myDestinationSubscription --query tenantId
```
Si les ID clients des abonnements source et de destination ne sont pas identiques, vous devez contacter le [support technique](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) pour déplacer les ressources vers un nouveau client.
Pour déplacer avec succès une machine virtuelle, vous devez déplacer la machine virtuelle et toutes les ressources qui l’accompagnent. Utilisez la commande [azure resource list](/cli/azure/resource) pour lister toutes les ressources d’un groupe de ressources et leurs ID. Cela permet de diriger la sortie de cette commande dans un fichier. Vous pouvez ainsi copier et coller les ID dans des commandes ultérieures.
```azurecli-interactive
az resource list --resource-group "mySourceResourceGroup" --query "[].{Id:id}" --output table
```
La sortie `table` n’est pas disponible si vous utilisez `--interactive`. Remplacez la sortie par une autre option comme `json`.
Pour déplacer une machine virtuelle et ses ressources dans un autre groupe de ressources, utilisez la commande [az resource move](/cli/azure/resource). L’exemple suivant montre comment déplacer une machine virtuelle et les ressources courantes nécessaires. Utilisez le paramètre **-ids** et transmettez la liste des ID des ressources à déplacer, séparée par des virgules (sans espaces).
```azurecli-interactive
vm=/subscriptions/mySourceSubscriptionID/resourceGroups/mySourceResourceGroup/providers/Microsoft.Compute/virtualMachines/myVM
nic=/subscriptions/mySourceSubscriptionID/resourceGroups/mySourceResourceGroup/providers/Microsoft.Network/networkInterfaces/myNIC
nsg=/subscriptions/mySourceSubscriptionID/resourceGroups/mySourceResourceGroup/providers/Microsoft.Network/networkSecurityGroups/myNSG
pip=/subscriptions/mySourceSubscriptionID/resourceGroups/mySourceResourceGroup/providers/Microsoft.Network/publicIPAddresses/myPublicIPAddress
vnet=/subscriptions/mySourceSubscriptionID/resourceGroups/mySourceResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet
diag=/subscriptions/mySourceSubscriptionID/resourceGroups/mySourceResourceGroup/providers/Microsoft.Storage/storageAccounts/mydiagnosticstorageaccount
storage=/subscriptions/mySourceSubscriptionID/resourceGroups/mySourceResourceGroup/providers/Microsoft.Storage/storageAccounts/mystorageaccountname
az resource move \
--ids $vm $nic $nsg $pip $vnet $storage $diag \
--destination-group "myDestinationResourceGroup"
```
Si vous souhaitez déplacer la machine virtuelle et ses ressources vers un autre abonnement, ajoutez le paramètre **--destination-subscriptionId** pour spécifier l’abonnement de destination.
Lorsque vous devrez confirmer que vous souhaitez déplacer les ressources spécifiées, saisissez **Y** pour confirmer.
[!INCLUDE [virtual-machines-common-move-vm](../../../includes/virtual-machines-common-move-vm.md)]
## <a name="next-steps"></a>Étapes suivantes
Vous pouvez déplacer de nombreux types de ressources différents entre les groupes de ressources et les abonnements. Pour plus d’informations, consultez la page [Déplacer des ressources vers un nouveau groupe de ressources ou un abonnement](../../azure-resource-manager/management/move-resource-group-and-subscription.md).
| 74.542857 | 413 | 0.819854 | fra_Latn | 0.927914 |
a6f225ebee2ee1031110c7c39cfd9167ce1b8231 | 8,515 | md | Markdown | WindowsServerDocs/storage/storage-replica/storage-replica-overview.md | huache/windowsserverdocs.zh-cn | a39065b2fd3ef28c99a27b6c91372b058e4422f8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/storage/storage-replica/storage-replica-overview.md | huache/windowsserverdocs.zh-cn | a39065b2fd3ef28c99a27b6c91372b058e4422f8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/storage/storage-replica/storage-replica-overview.md | huache/windowsserverdocs.zh-cn | a39065b2fd3ef28c99a27b6c91372b058e4422f8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 存储副本概述
manager: siroy
ms.author: nedpyle
ms.topic: get-started-article
author: nedpyle
ms.date: 4/26/2019
ms.assetid: e9b18e14-e692-458a-a39f-d5b569ae76c5
ms.openlocfilehash: 1d8997edf1354a49b9b67e417906eeaa307fdee6
ms.sourcegitcommit: dfa48f77b751dbc34409aced628eb2f17c912f08
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 08/07/2020
ms.locfileid: "87961221"
---
# <a name="storage-replica-overview"></a>存储副本概述
>适用于：Windows Server 2019、Windows Server 2016、Windows Server（半年频道）
存储副本 (Storage Replica) 是一种 Windows Server 技术，它允许针对灾难恢复在服务器或群集之间进行卷的复制。 它还允许你创建跨越两个站点的拉伸故障转移群集，同时保持所有节点同步。
存储副本支持同步和异步复制：
* **同步复制**映射低延迟网络站点中的数据和在崩溃时保持一致的卷，以确保在故障发生过程中文件系统级别的数据损失为零。
* **异步复制**通过较高延迟网络链接映射都市范围外的站点之间的数据，但不保证在出现故障时两个站点具有完全相同的数据副本。
## <a name="why-use-storage-replica"></a>为什么要使用存储副本？
存储副本在 Windows Server 中提供灾难恢复和准备功能。 Windows Server 提供了无数据丢失的和平，能够以同步方式保护不同机架、地面、建筑物、校园、县和城市的数据。 发生灾难后，所有数据都存在于其他位置，而不会造成任何损失。 这同样适用灾难发生*前*；在授予片刻警告时，存储副本会在在灾难发生前切换到安全位置 - 再次声明，不会有数据丢失。
存储副本允许更有效地利用多个数据中心。 通过拉伸或复制群集，工作负荷可在多个数据中心中运行，以使本地邻近用户和应用程序能够更加快速地对其进行访问，以及更好地分布负载和使用计算资源。 如果灾难导致一个数据中心脱机，可以将其典型的工作负载暂时移动到另一个站点。
存储副本可能会允许取消配置作为低端灾难恢复解决方案的现有文件复制系统，如 DFSR。 DFS 复制在极低带宽网络上运行非常出色，同时其延迟时间很高 - 通常以小时或天为单位。 这是由文件关闭需求和防止网络拥塞的人为限制所引起。 正因具有这些设计特性，因此最不可能复制 DFS 复制副本中最新和最热门的文件。 存储副本在文件级别以下运行，并且没有这些限制。
存储副本还支持适用于更长范围和更高延迟网络的异步复制。 由于它不是基于检查点的，而是连续复制，因此更改的差异往往比基于快照的产品要低得多。 此外，存储副本在分区层进行操作，因此它将复制由 Windows Server 或备份软件创建的所有 VSS 快照；这允许将应用程序一致的数据快照用于时间点恢复，尤其是异步复制的非结构化用户数据。
## <a name="supported-configurations"></a><a name="BKMK_SRSupportedScenarios"></a>支持的配置
你可以在拉伸群集中、在群集到群集之间和服务器到服务器配置之间部署存储副本 (参阅图 1-3) 。
**拉伸群集**允许在单个群集中配置计算机和存储，其中某些节点共享一组非对称存储，而另一些节点共享另一组，然后通过站点感知进行同步或异步复制。 此方案可以利用具有共享的 SAS 存储的存储空间、连接了 SAN 和 iSCSI 的 LUN。 它通过 PowerShell 和故障转移群集管理器图形工具进行管理，并允许自动化工作负载故障转移。
**图 1：在拉伸群集中使用存储副本的存储复制**
**群集到群集**允许两个独立群集之间的复制，其中一个群集与另一个群集进行同步复制或异步复制。 此方案可以利用存储空间直通、具有共享的 SAS 存储的存储空间以及连接了 SAN 和 iSCSI 的 LUN。 它通过 Windows 管理中心和 PowerShell 进行管理，并且需要手动干预以进行故障转移。
**图 2：使用存储副本的群集到群集存储复制**
**服务器到服务器**允许使用具有共享的 SAS 存储的存储空间、连接了 SAN 和 iSCSI 的 LUN 以及本地驱动器，在两个独立服务器之间进行同步和异步复制。 它通过 Windows 管理中心和 PowerShell 进行管理，并且需要手动干预以进行故障转移。
**图 3：使用存储副本的服务器到服务器存储复制**
> [!NOTE]
> 还可以在一台计算机上使用四个单独的卷配置服务器到自我复制。 但是，本指南不涉及这种情况。
## <a name="storage-replica-features"></a><a name="BKMK_SR2"> </a>存储副本功能
* **零数据丢失、块级复制**。 使用同步复制，不可能丢失数据。 使用块级复制，不可能锁定文件。
* **简单部署和管理。** 存储副本具有易于使用的设计要求。 在两个服务器之间创建复制合作关系可以利用 Windows 管理中心。 拉伸群集的部署在熟悉的故障转移群集管理器工具中使用直观向导。
* **来宾和主机**。 存储副本的所有功能均将在基于虚拟化来宾和主机的部署中公开。 这意味着，只要在来宾中使用 Windows Server，来宾也可以复制其数据卷，即使在非 Windows 虚拟化平台或公有云中运行。
* **基于 SMB3。** 存储副本使用 SMB 3 这一公认的成熟技术，该技术在 Windows Server 2012 中首次推出。 这意味着 SMB 的所有高级特性（如RoCE、iWARP 和 InfiniBand RDMA 网卡上的多通道和 SMB 直通支持）均可用于存储副本。
* **安全性**。 与许多供应商的产品不同，存储副本由行业领先的安全技术提供支持。 这包括数据包签名、AES-128-GCM 完整数据加密、对 Intel AES-NI 加密加速的支持和完整预身份验证中间人攻击防护。 存储副本利用 Kerberos AES256 进行节点之间所有的身份验证。
* **高性能初始同步**。存储副本支持种子初始同步，其中，数据的一个子集已存在于较旧的副本、备份或随附驱动器上的目标中。 初始复制仅复制不同的块，这可能会缩短初始同步时间并防止数据占用有限的带宽。 存储副本阻止校验和计算，聚合意味着初始同步性能只受存储和网络速度限制。
* **一致性组**。 写入顺序保证应用程序（如 Microsoft SQL Server）可以写入多个复制的卷，并知道数据是按顺序写入到目标服务器上的。
* **用户委派**。 可对不是复制的节点上内置管理员组成员的用户委派管理复制的权限，从而限制他们对不相关区域的访问。
* **网络约束**。 为了提供应用程序、备份和管理软件带宽，可由服务器和已复制的卷将存储副本限制到独立网络。
* **精简预配**。 在很多情况下，为了提供近乎瞬间的初始复制时间，支持在存储空间和 SAN 设备中进行精简配置。
存储副本包含以下功能：
| 功能 | 详细信息 |
| ----------- | ----------- |
| 类型 | 基于主机 |
| Synchronous | 是 |
| 异步 | 是 |
| 存储硬件不可知 | 是 |
| 复制单元 | 卷（分区） |
| Windows Server stretch 群集创建 | 是 |
| 服务器到服务器复制 | 是 |
| 群集到群集复制 | 是 |
| 传输 | SMB3 |
| 网络 | TCP/IP 或 RDMA |
| 网络约束支持 | 是 |
| RDMA* | iWARP、InfiniBand、RoCE v2 |
| 复制网络端口防火墙要求 | 单个 IANA 端口（TCP 445 或 5445） |
| 多路径/多通道 | 是 (SMB3) |
| Kerberos 支持 | 是 (SMB3) |
| 通过有线加密和签名|是 (SMB3) |
| 允许按每个卷进行故障转移 | 是 |
| 精简配置的存储支持 | 是 |
| 管理 UI 内部 | PowerShell、故障转移群集管理器 |
*可能需要其他远程设备和电缆线路。
## <a name="storage-replica-prerequisites"></a><a name="BKMK_SR3"></a>存储副本必备组件
* Active Directory 域服务林。
* 具有 SAS JBOD 的存储空间、存储空间直通、光纤通道 SAN、共享 VHDX、iSCSI 目标或本地 SAS/SCSI/SATA 存储。 对于复制日志驱动器，建议使用 SSD 或更快速度。 Microsoft 建议日志存储应比数据存储速度快。 日志卷不得用于其他工作负荷。
* 每个服务器上必须具有至少一个用于同步复制的以太网/TCP 连接，但最好是 RDMA。
* 至少 2 GB 的 RAM 且每台服务器具有两个内核。
* 服务器间的网络具有足够的带宽，以包含 IO 写入工作负载和平均值为 5 毫秒或更低的往返行程延迟（对于同步复制）。 异步复制没有延迟建议。
* Windows Server、Datacenter Edition 或 Windows Server Standard Edition。 Windows Server Standard Edition 上运行的存储副本具有以下限制：
* 必须使用 Windows Server 2019 或更高版本
* 存储副本复制单个卷而不是无限数量的卷。
* 卷的大小最大可达 2 TB，而不是无限大小。
## <a name="background"></a><a name="BKMK_SR4"> </a>背景
本节包括有关高级行业术语、同步和异步复制以及关键行为的信息。
### <a name="high-level-industry-terms"></a>高级行业术语
灾难恢复 (DR) 是指从站点灾难恢复，以便业务继续运行的应急计划。 数据 DR 表示单独物理位置中的多个生产数据副本。 例如延伸群集，其中一半的节点在一个站点中，另一半则在另一个站点中。 灾难预防 (DP) 是指在灾难到来前（如飓风），提前将工作负载移动到另一个位置的应急计划。
服务级别协议 (SLA) 表示在已计划和非计划停机期间，企业的应用程序的可用性及其停机时间和数据丢失容差。 恢复时间目标 (RTO) 表示业务对数据不可访问的总承受时间。 恢复点目标 (RPO) 表示业务对丢失数据的承受量。
### <a name="synchronous-replication"></a>同步复制
同步复制可确保应用程序在 IO 完成之前将数据一次写入两个位置。 由于这种复制要求网络和存储投资且有降低应用程序性能的风险，所以它更适合于任务关键数据。
当源数据副本上发生应用程序写入操作时，源存储不会立即确认 IO。 相反，那些数据更改对远程目标副本的复制，并返回一条确认。 此时，应用程序才会收到 IO 确认。 这可确保远程站点与源站点的固定同步，有效地跨网络扩展存储 IO。 在源站点故障时，应用程序可以故障转移到远程站点并恢复其运行，同时保证零数据丢失。
| 模式 | 图表 | 步骤 |
| -------- | ----------- | --------- |
| **Synchronous**<p>零数据丢失<p>RPO |  | 1.应用程序写入数据<br />2.写入日志数据，并将数据复制到远程站点<br />3.在远程站点写入日志数据<br />4.从远程站点确认<br />5.确认应用程序写入<p>t & t1：数据刷新到该卷，始终写入日志 |
### <a name="asynchronous-replication"></a>异步复制
相反，异步复制意味着当应用程序写入数据时，将在没有立即确认保证的情况下将该数据复制到远程站点。 此模式允许更迅速地响应应用程序以及按地理位置工作的 DR 解决方案。
当应用程序写入数据时，复制引擎将捕获该写入并立即向应用程序确认。 然后，捕获的数据将复制到远程位置。 远程节点处理数据的副本，并延迟返回向源副本确认。 由于复制性能不再处于应用程序 IO 路径中，因此远程站点的响应速度和距离都是不太重要的因素。 如果源数据丢失，并且数据的目标副本仍在缓冲区而没有离开源，则存在数据丢失的风险。
使用其比 zero RPO 更高的版本，异步复制不太适用于 HA 解决方案，如故障转移群集，因为它们是为具有冗余和无数据丢失的连续操作而设计。
| 模式 | 图表 | 步骤 |
| -------- | ----------- | --------- |
| **异步**<p>几乎零数据丢失<p>（取决于多种因素）<p>RPO | |1.应用程序写入数据<br />2.写入日志数据<br />3.确认应用程序写入<br />4.数据复制到远程站点<br />5.日志数据在远程站点写入<br />6.从远程站点确认<p>t & t1：数据刷新到该卷，始终写入日志 |
### <a name="key-evaluation-points-and-behaviors"></a>关键评估点和行为
- 具备最快存储速度的网络带宽和延迟。 同步复制方面存在一些物理限制。 因为存储副本实现使用日志和要求网络往返行程的 IO 筛选机制，同步复制可能会使应用程序写入速度较慢。 通过为日志使用低延迟、高带宽网络以及高吞吐量磁盘子系统，可以最大程度地降低性能开销。
- 在 Windows Server 2016 中复制时目标卷不可访问。 在配置复制时，目标卷将卸除，这使得用户无法进行任何读取或写入。 其驱动器号可以显示在文件资源管理器等常见界面中，但是，应用程序无法访问卷本身。 块级别复制技术与卷中允许访问的目标已装载文件系统不兼容；当块在其下更改时，NTFS 和 ReFS 不支持用户将数据写入该卷中。
Windows Server 版本1709中的**测试故障转移**cmdlet debuted 也包含在 windows server 2019 中。 这现在支持暂时装载目标卷的读写快照，以便进行备份、测试等。https://aka.ms/srfaq有关详细信息，请参阅。
- 异步复制的 Microsoft 实现与大多数不同。 异步复制的大多数行业实现依赖于基于快照的复制，其中周期性差异传输移动到另一个节点并进行合并。 存储副本异步复制的操作与同步复制相同，只是它不需要从目标进行序列化同步确认。 这意味着存储副本理论上具有较低的 RPO，因为它会持续进行复制。 但是，这也意味着它依赖于内部应用程序一致性保证，而不是使用快照来强制实现应用程序文件一致性。 存储副本保证所有复制模式中的故障一致性
- 许多客户使用 DFS 复制作为灾难恢复解决方案，即使往往在这种情况下不切实际 - DFS 复制不能复制打开的文件，它旨在最小化带宽使用量，这会降低性能，从而导致较大的恢复点增量。 存储副本可能允许从这些类型的灾难恢复职责停用 DFS 复制。
- 存储副本不是备份解决方案。 某些 IT 环境部署复制系统作为备份解决方案，因为相比每日备份，它们具有零数据丢失选项。 存储副本将所有更改都复制到卷上的数据块，而不考虑更改类型。 如果用户从卷中删除所有数据，则存储副本会将删除操作立即复制到另一卷，不可撤销从两个服务器中删除数据。 不要使用存储副本来替换时间点备份解决方案。
- 存储副本不是 Hyper-V 副本或 Microsoft SQL AlwaysOn 可用性组。 存储副本是存储不可知的常规用途引擎。 根据定义，它不能像应用程序级别的复制一样理想地定制其行为。 这可能导致特定功能差距，它鼓励你部署或保持特定的应用程序复制技术。
> [!NOTE]
> 本文档包含[已知问题](storage-replica-known-issues.md)和预期行为列表，以及[常见问题](storage-replica-frequently-asked-questions.md)部分。
### <a name="storage-replica-terminology"></a>存储副本术语
本指南经常使用以下术语：
- 源是计算机的卷，它允许本地写入和出站复制， 也称为“主要”。
- 目标是计算机的卷，它不允许本地写入和入站复制， 也称为“次要”。
- 复制合作关系是对一个或多个卷的源和目标计算机之间的同步关系，并利用单个日志。
- 复制组是合作关系内的卷及其复制配置的组织，在每个服务器上有所不同。 组可以包含一个或多个卷。
### <a name="whats-new-for-storage-replica"></a>存储副本的新增功能
有关 Windows Server 2019 中的存储副本中新功能的列表，请参阅[存储中的新增](../whats-new-in-storage.md#storage-replica2019)功能
## <a name="additional-references"></a>其他参考
- [使用共享存储拉伸群集复制](stretch-cluster-replication-using-shared-storage.md)
- [服务器到服务器存储复制](server-to-server-storage-replication.md)
- [群集到群集存储复制](cluster-to-cluster-storage-replication.md)
- [存储副本：已知问题](storage-replica-known-issues.md)
- [存储副本：常见问题解答](storage-replica-frequently-asked-questions.md)
- [Windows Server 2016 中的存储空间直通](../storage-spaces/storage-spaces-direct-overview.md)
- [Windows IT 专业人员支持](https://www.microsoft.com/itpro/windows/support)
| 43.005051 | 246 | 0.782032 | yue_Hant | 0.764347 |
a6f31c3a9cc00dd784c1194b216579178930e91f | 2,416 | md | Markdown | docs/mfc/files-in-mfc.md | yoichinak/cpp-docs.ja-jp | 50048c3d1101537497403efb4e7b550108f3a8f0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/files-in-mfc.md | yoichinak/cpp-docs.ja-jp | 50048c3d1101537497403efb4e7b550108f3a8f0 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-01T04:17:07.000Z | 2021-04-01T04:17:07.000Z | docs/mfc/files-in-mfc.md | yoichinak/cpp-docs.ja-jp | 50048c3d1101537497403efb4e7b550108f3a8f0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: 詳細については、「MFC でのファイル」を参照してください。
title: MFC のファイル
ms.date: 11/04/2016
helpviewer_keywords:
- serialization [MFC], MFC files
- I/O [MFC], MFC classes
- files [MFC], MFC
- files [MFC], serialization
- binary access, binary file operations in MFC
- file I/O classes [MFC]
- I/O [MFC]
- persistence [MFC]
- MFC, file operations
- files [MFC], manipulating
- binary access [MFC]
ms.assetid: ae25e2c5-2859-4679-ab97-438824e93ce1
ms.openlocfilehash: 47fab5876efd7d06ec4364721a09b7ed09da9744
ms.sourcegitcommit: d6af41e42699628c3e2e6063ec7b03931a49a098
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 12/11/2020
ms.locfileid: "97155047"
---
# <a name="files-in-mfc"></a>MFC のファイル
Microsoft Foundation Class ライブラリ (MFC) では、クラス [CFile](reference/cfile-class.md) は通常のファイル i/o 操作を処理します。 この記事の記事では、ファイルを開いたり閉じたりする方法について説明し、これらのファイルに対するデータの読み取りと書き込みを行う方法について説明します。 また、ファイルの状態の操作についても説明します。 ファイル内のデータの読み取りと書き込みを行う別の方法として、MFC のオブジェクトベースのシリアル化機能を使用する方法の詳細については、「 [シリアル化](serialization-in-mfc.md)」を参照してください。
> [!NOTE]
> MFC オブジェクトを使用すると、フレームワークによって `CDocument` 多くのシリアル化が機能します。 特に、フレームワークによってオブジェクトが作成され、使用され `CFile` ます。 クラスのメンバー関数のオーバーライドでコードを記述するだけで済み `Serialize` `CDocument` ます。
クラスは、 `CFile` 汎用のバイナリファイル操作のためのインターフェイスを提供します。 から派生したクラスと、から派生したクラスは、 `CStdioFile` `CMemFile` `CFile` `CSharedFile` `CMemFile` より専門的なファイルサービスを提供します。
MFC ファイル処理の代替方法の詳細については、「*ランタイムライブラリリファレンス*」の「[ファイル処理](../c-runtime-library/file-handling.md)」を参照してください。
派生クラスの詳細については、 `CFile` 「 [MFC 階層図](hierarchy-chart.md)」を参照してください。
## <a name="what-do-you-want-to-do"></a>どうしたいんですか
*CFile を使用する*
- [CFile でファイルを開きます。](opening-files.md)
- [CFile を使用したファイルの読み取りと書き込み](reading-and-writing-files.md)
- [CFile でファイルを閉じます](closing-files.md)
- [CFile でファイルの状態にアクセスする](accessing-file-status.md)
*MFC シリアル化の使用 (オブジェクトの永続化)*
- [Serializable クラスを作成する](serialization-making-a-serializable-class.md)
- [CArchive オブジェクトを介してオブジェクトをシリアル化する](serialization-serializing-an-object.md)
- [CArchive オブジェクトを作成する](two-ways-to-create-a-carchive-object.md)
- [CArchive <> 演算子を使用する \< and >](using-the-carchive-output-and-input-operators.md)
- [アーカイブを使用して通じた cobject および CObject から派生したオブジェクトを格納して読み込む](storing-and-loading-cobjects-via-an-archive.md)
## <a name="see-also"></a>関連項目
[概念](mfc-concepts.md)<br/>
[MFC の一般的なトピック](general-mfc-topics.md)<br/>
[CArchive クラス](reference/carchive-class.md)<br/>
[CObject クラス](reference/cobject-class.md)
| 35.529412 | 317 | 0.775662 | yue_Hant | 0.825029 |
a6f39aea4c2f1942c9a60ed70ce5168dc663a2e6 | 2,662 | md | Markdown | articles/iot-develop/tutorial-multiple-components.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-07-31T17:49:12.000Z | 2021-08-03T13:32:39.000Z | articles/iot-develop/tutorial-multiple-components.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-develop/tutorial-multiple-components.md | BaherAbdullah/azure-docs | 65d82440dd3209697fdb983ef456b0a2293e270a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-07-10T20:21:56.000Z | 2020-07-10T20:21:56.000Z | ---
title: Tutorial - Connect an IoT Plug and Play multiple component device applications to IoT Hub | Microsoft Docs
description: Tutorial - Build and run IoT Plug and Play sample device code (C, C#, Java, JavaScript, or Python) that uses multiple components and connects to an IoT hub. Use the Azure IoT explorer tool to view the information sent by the device to the hub.
author: ericmitt
ms.author: ericmitt
ms.date: 07/22/2020
ms.topic: tutorial
ms.service: iot-develop
services: iot-develop
zone_pivot_groups: programming-languages-set-twenty-six
#- id: programming-languages-set-twenty-six
## Owner: dobett
# title: Programming languages
# prompt: Choose a programming language
# pivots:
# - id: programming-language-ansi-c
# title: C
# - id: programming-language-csharp
# title: C#
# - id: programming-language-java
# title: Java
# - id: programming-language-javascript
# title: JavaScript
# - id: programming-language-python
# title: Python
#Customer intent: As a device builder, I want to see a working IoT Plug and Play device sample connecting to IoT Hub and using multiple components to send properties and telemetry, and responding to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to.
---
# Tutorial: Connect an IoT Plug and Play multiple component device applications running on Linux or Windows to IoT Hub
:::zone pivot="programming-language-ansi-c"
[!INCLUDE [iot-pnp-multiple-components-csharp](../../includes/iot-pnp-multiple-components-c.md)]
:::zone-end
:::zone pivot="programming-language-csharp"
[!INCLUDE [iot-pnp-multiple-components-csharp](../../includes/iot-pnp-multiple-components-csharp.md)]
:::zone-end
:::zone pivot="programming-language-java"
[!INCLUDE [iot-pnp-multiple-components-java](../../includes/iot-pnp-multiple-components-java.md)]
:::zone-end
:::zone pivot="programming-language-javascript"
[!INCLUDE [iot-pnp-multiple-components-node](../../includes/iot-pnp-multiple-components-node.md)]
:::zone-end
:::zone pivot="programming-language-python"
[!INCLUDE [iot-pnp-multiple-components-python](../../includes/iot-pnp-multiple-components-python.md)]
:::zone-end
## Clean up resources
[!INCLUDE [iot-pnp-clean-resources](../../includes/iot-pnp-clean-resources.md)]
## Next steps
In this tutorial, you've learned how to connect an IoT Plug and Play device with components to an IoT hub. To learn more about IoT Plug and Play device models, see:
> [!div class="nextstepaction"]
> [IoT Plug and Play modeling developer guide](concepts-developer-guide-device.md)
| 36.465753 | 367 | 0.749437 | eng_Latn | 0.899741 |
a6f3aa13ef12d471341b7ff12a94863e3d5ffbec | 1,152 | md | Markdown | desktop-src/WMP/equalizersettings-normalizationpeak.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 4 | 2021-07-26T16:18:49.000Z | 2022-02-19T02:00:21.000Z | desktop-src/WMP/equalizersettings-normalizationpeak.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-04-09T17:00:51.000Z | 2020-04-09T18:30:01.000Z | desktop-src/WMP/equalizersettings-normalizationpeak.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-07-19T02:58:48.000Z | 2021-03-06T21:09:47.000Z | ---
title: EQUALIZERSETTINGS.normalizationPeak
description: The normalizationPeak attribute retrieves the peak normalization value.
ms.assetid: edc914a8-5e80-41a2-b60e-a8bd481e2d11
keywords:
- EQUALIZERSETTINGS.normalizationPeak Windows Media Player
topic_type:
- apiref
api_name:
- EQUALIZERSETTINGS.normalizationPeak
api_type:
- NA
ms.topic: reference
ms.date: 05/31/2018
---
# EQUALIZERSETTINGS.normalizationPeak
The **normalizationPeak** attribute retrieves the peak normalization value.
``` syntax
elementID.normalizationPeak
```
## Possible Values
This attribute is a read-only **Number** (**float**).
## Requirements
| | |
|--------------------|---------------------------------------------------|
| Version<br/> | Windows Media Player 9 Series or later<br/> |
## See also
<dl> <dt>
[**EQUALIZERSETTINGS Element**](equalizersettings-element.md)
</dt> <dt>
[**EQUALIZERSETTINGS.normalization**](equalizersettings-normalization.md)
</dt> <dt>
[**EQUALIZERSETTINGS.normalizationAverage**](equalizersettings-normalizationaverage.md)
</dt> </dl>
| 19.2 | 87 | 0.65625 | kor_Hang | 0.142155 |
a6f3af89f69f3dd872a97df5405747f135a8b8e2 | 5,864 | md | Markdown | docs/t-sql/statements/alter-partition-scheme-transact-sql.md | conky77/sql-docs.it-it | 43be0950d07b85a6566f565206630912ec8c3197 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/t-sql/statements/alter-partition-scheme-transact-sql.md | conky77/sql-docs.it-it | 43be0950d07b85a6566f565206630912ec8c3197 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/t-sql/statements/alter-partition-scheme-transact-sql.md | conky77/sql-docs.it-it | 43be0950d07b85a6566f565206630912ec8c3197 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ALTER PARTITION SCHEME (Transact-SQL) | Microsoft Docs
ms.custom: ''
ms.date: 03/06/2017
ms.prod: sql
ms.prod_service: sql-database
ms.reviewer: ''
ms.technology: t-sql
ms.topic: language-reference
f1_keywords:
- ALTER PARTITION SCHEME
- ALTER_PARTITION_SCHEME_TSQL
dev_langs:
- TSQL
helpviewer_keywords:
- ALTER PARTITION SCHEME statement
- partition schemes [SQL Server], modifying
- modifying partition schemes
- adding filegroups
- NEXT USED filegroups
ms.assetid: f01d6880-9800-4cfb-8d11-d4be21efc8ca
author: CarlRabeler
ms.author: carlrab
ms.openlocfilehash: 593c2d8bf9cff3e10aaafc339aa82ef16c4bc09f
ms.sourcegitcommit: b2e81cb349eecacee91cd3766410ffb3677ad7e2
ms.translationtype: HT
ms.contentlocale: it-IT
ms.lasthandoff: 02/01/2020
ms.locfileid: "68071246"
---
# <a name="alter-partition-scheme-transact-sql"></a>ALTER PARTITION SCHEME (Transact-SQL)
[!INCLUDE[tsql-appliesto-ss2008-asdb-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-asdb-xxxx-xxx-md.md)]
Aggiunge un filegroup a uno schema di partizione oppure modifica la designazione del filegroup NEXT USED per lo schema di partizione.
>[!NOTE]
>Nel database SQL di Azure sono supportati solo i filegroup primari.
 [Convenzioni della sintassi Transact-SQL](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
## <a name="syntax"></a>Sintassi
```
ALTER PARTITION SCHEME partition_scheme_name
NEXT USED [ filegroup_name ] [ ; ]
```
## <a name="arguments"></a>Argomenti
*partition_scheme_name*
Nome dello schema di partizione che si desidera modificare.
*filegroup_name*
Specifica il filegroup che si desidera contrassegnare come NEXT USED nello schema di partizione. Questo significa che il filegroup accetterà una nuova partizione creata tramite un'istruzione [ALTER PARTITION FUNCTION](../../t-sql/statements/alter-partition-function-transact-sql.md).
In uno schema di partizione è possibile designare come NEXT USED un solo filegroup. È possibile specificare un filegroup non vuoto. Se viene specificato *filegroup_name* e attualmente nessun filegroup è contrassegnato come NEXT USED, il contrassegno NEXT USED verrà applicato a *filegroup_name*. Se viene specificato *filegroup_name* ed esiste già un filegroup con la proprietà NEXT USED, questo contrassegno verrà trasferito dal filegroup esistente a *filegroup_name*.
Se *filegroup_name* viene omesso ed esiste già un filegroup con la proprietà NEXT USED, questo filegroup perderà lo stato NEXT USED, in modo che non esistano filegroup NEXT USED in *filegroup_name*.
Se *filegroup_name* viene omesso e non esistono filegroup contrassegnati come NEXT USED, ALTER PARTITION SCHEME restituirà un avviso.
## <a name="remarks"></a>Osservazioni
Tutti i filegroup a cui viene applicata l'istruzione ALTER PARTITION SCHEME devono essere online.
## <a name="permissions"></a>Autorizzazioni
Per eseguire l'istruzione ALTER PARTITION SCHEME, è possibile utilizzare le autorizzazioni seguenti:
- Autorizzazione ALTER ANY DATASPACE. Questa autorizzazione viene concessa per impostazione predefinita al ruolo predefinito del server **sysadmin** e ai ruoli predefiniti del database **db_owner** e **db_ddladmin** .
- Autorizzazione CONTROL o ALTER per il database nel quale viene creato lo schema di partizione.
- Autorizzazione CONTROL SERVER o ALTER ANY DATABASE per il server del database nel quale è stato creato lo schema di partizione.
## <a name="examples"></a>Esempi
Nell'esempio seguente si presuppone che lo schema di partizione `MyRangePS1` e il filegroup `test5fg` esistano già nel database corrente.
```
ALTER PARTITION SCHEME MyRangePS1
NEXT USED test5fg;
```
Il filegroup `test5fg` riceverà tutte le partizioni aggiuntive di una tabella o un indice partizionato create tramite un'istruzione ALTER PARTITION FUNCTION.
## <a name="see-also"></a>Vedere anche
[CREATE PARTITION SCHEME (Transact-SQL)](../../t-sql/statements/create-partition-scheme-transact-sql.md)
[DROP PARTITION SCHEME (Transact-SQL)](../../t-sql/statements/drop-partition-scheme-transact-sql.md)
[CREATE PARTITION FUNCTION (Transact-SQL)](../../t-sql/statements/create-partition-function-transact-sql.md)
[ALTER PARTITION FUNCTION (Transact-SQL)](../../t-sql/statements/alter-partition-function-transact-sql.md)
[DROP PARTITION FUNCTION (Transact-SQL)](../../t-sql/statements/drop-partition-function-transact-sql.md)
[CREATE TABLE (Transact-SQL)](../../t-sql/statements/create-table-transact-sql.md)
[CREATE INDEX (Transact-SQL)](../../t-sql/statements/create-index-transact-sql.md)
[EVENTDATA (Transact-SQL)](../../t-sql/functions/eventdata-transact-sql.md)
[sys.partition_schemes (Transact-SQL)](../../relational-databases/system-catalog-views/sys-partition-schemes-transact-sql.md)
[sys.data_spaces (Transact-SQL)](../../relational-databases/system-catalog-views/sys-data-spaces-transact-sql.md)
[sys.destination_data_spaces (Transact-SQL)](../../relational-databases/system-catalog-views/sys-destination-data-spaces-transact-sql.md)
[sys.partitions (Transact-SQL)](../../relational-databases/system-catalog-views/sys-partitions-transact-sql.md)
[sys.tables (Transact-SQL)](../../relational-databases/system-catalog-views/sys-tables-transact-sql.md)
[sys.indexes (Transact-SQL)](../../relational-databases/system-catalog-views/sys-indexes-transact-sql.md)
[sys.index_columns (Transact-SQL)](../../relational-databases/system-catalog-views/sys-index-columns-transact-sql.md)
| 56.932039 | 472 | 0.757162 | ita_Latn | 0.568699 |
a6f5bcf93b4a411eb26ee9da64f82cbb34c34511 | 445 | md | Markdown | README.md | datnp1003/contractoflove | 6d319f2797ee6ca63d395e69cadb2e4faf4743e5 | [
"MIT"
] | 1 | 2022-03-26T03:00:51.000Z | 2022-03-26T03:00:51.000Z | README.md | datnp1003/contractoflove | 6d319f2797ee6ca63d395e69cadb2e4faf4743e5 | [
"MIT"
] | null | null | null | README.md | datnp1003/contractoflove | 6d319f2797ee6ca63d395e69cadb2e4faf4743e5 | [
"MIT"
] | 2 | 2022-03-26T01:14:15.000Z | 2022-03-27T12:58:34.000Z | HELLO ALL.
I'M DATNGUYEN, FROM VIETNAM, I'M LOVING.
THIS PROJECT OPENSOURCE, THIS'S NAME: CONTRACT OF LOVE.
I WRITE THIS CONTRACT HOPE ALL SO HAPPINESS, AND FIND ANY FUNNY IN LOVE.
I'M VERY BAD ENGLISH, HOPE EVERYONE UNDERSTAND.
PROJECT PROCESS:
1: CREATE SMARTCONTRACT: DONE 24/03/2022.
2: WEBSITE.
3: ANY UPDATE LATER.
ONE LAST THING, HOPE YOU GUYS HAVE UPDATES FOR THIS PROJECT AND THOSE WHO ARE FA SOON FIND THE LOVE OF THEIR LIVES.
| 23.421053 | 115 | 0.757303 | yue_Hant | 0.999882 |
a6f5f6f747127d66d2f00272cf3019b31a7e3978 | 3,370 | md | Markdown | docs/contribution/COMPONENT-SPEC-EXAMPLE.md | omrigilad/wix-style-react | 13875c6af998becf99d70019d3eed4a401bd6656 | [
"MIT"
] | null | null | null | docs/contribution/COMPONENT-SPEC-EXAMPLE.md | omrigilad/wix-style-react | 13875c6af998becf99d70019d3eed4a401bd6656 | [
"MIT"
] | 1 | 2019-05-11T12:54:22.000Z | 2019-05-11T12:54:22.000Z | docs/contribution/COMPONENT-SPEC-EXAMPLE.md | omrigilad/wix-style-react | 13875c6af998becf99d70019d3eed4a401bd6656 | [
"MIT"
] | null | null | null | # `<NumberInput/>` Specification
## Description
This is a controlled NumberInput component, with increase, decrease buttons.
It supports integer values only.
## Basic Usage
```js
import React from 'react';
import NumberInput from 'wix-style-react/NumberInput';
class ProductQuantity extends React.Component {
state = {quantity: 1}
render() {
return (
<NumberInput
value={this.state.quantity}
onChange={(value) => this.setState({quantity: value})}
maxValue={100}
/>
)
}
}
```
## `<NumberInput/>` Props
| propName | propType | defaultValue | isRequired | description |
| --- | --- | --- | --- | --- |
| value | number | | Yes | counter value |
| onChange | func | | Yes | A callback when the value changes. Signature (value) => void |
| minValue | number | 0 | | manimum counter value (inclusive)|
| maxValue | number | 100 | | maximum counter value (inclusive)|
| step | number | 1 | | increase/decrease step |
| inputProps | object | | | Object with HTML attributes to be placed onto the native `<input/>`
## Behavior
- Clicking on increase button increases value by `step` prop
- Clicking on decrease button decrease value by `step` prop
- When `maxValue` is reached, the further clicking on increase/decrease buttons will not trigger the `onChange` callback.
## Style API
### Selectors (pseudo-elements)
| selector | description | type | children pseudo-states |
|:------------------|:-----------------------------------|:-----|:-----------------------|
| root | Allows styling the size, background and border | | |
| ::increaseButton | | | |
| ::decreaseButton | | | |
| ::input | targets the input area | | |
### States
| state | description | type |
|:-------------|:-----------------------------------|:-----|
| disabled | Input and buttons are disabled | boolean |
| active | true when one of the buttons is active (pressed down) | boolean |
### Style Code Example
```css
:import {
-st-from: './components/number-input';
-st-default: NumberInput;
}
.root {
}
.quantity {
-st-extends: NumberInput;
width: 200px;
border: 1px solid black;
}
.quantity:disabled {
border: 1px solid grey;
}
.quantity::increaseButton, .quantity::decreaseButton {
background-color: green;
}
```
## Accessibility & Keyboard Navigation
### Keyboard Navigation
- Tab order: `input` is the only focusable element
- Pressing up/down arrows increases/decreases the value by `step`
- Pressing right/left arrows increases/decreases the value by `step`
### Accessibility
- increase/decrease buttons should have appropriate aria-label
## RTL Support
- increase/decrease buttons layout should be switch in RTL mode.
- right/left arrows are switched as well.
## Rational (optional)
Here you can optionaly describe important rational of API decissions.
| 29.823009 | 123 | 0.555786 | eng_Latn | 0.960032 |
a6f5ff50e47f880fd0937ec3d268cba649e414c8 | 164 | md | Markdown | README.md | akbrooke/chineapplepunks | db5e8897b212adaf21055ecd971e874fdf38dff1 | [
"Unlicense"
] | null | null | null | README.md | akbrooke/chineapplepunks | db5e8897b212adaf21055ecd971e874fdf38dff1 | [
"Unlicense"
] | null | null | null | README.md | akbrooke/chineapplepunks | db5e8897b212adaf21055ecd971e874fdf38dff1 | [
"Unlicense"
] | null | null | null | # pygames
One hacked together Space Invaders clone exists in this repo.
### Requirements
Python3 (tested with version 3.7.3)
PyGame (tested with version 1.9.6)
| 20.5 | 61 | 0.75 | eng_Latn | 0.996052 |
a6f705176c25ec64297481a4b4fa91dd08117070 | 120,367 | md | Markdown | lib/hipfort/SUPPORTED_API_ROCSOLVER.md | arvindcheru/hipfort | fa6628bfc876db72e98fd5eb36cb88f3038a4f80 | [
"MIT"
] | null | null | null | lib/hipfort/SUPPORTED_API_ROCSOLVER.md | arvindcheru/hipfort | fa6628bfc876db72e98fd5eb36cb88f3038a4f80 | [
"MIT"
] | null | null | null | lib/hipfort/SUPPORTED_API_ROCSOLVER.md | arvindcheru/hipfort | fa6628bfc876db72e98fd5eb36cb88f3038a4f80 | [
"MIT"
] | null | null | null | \# | API Name | Variants
----|---------------|---------
1 | [rocsolver_create_handle](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__create__handle.html "Interface documentation") | C binding
2 | [rocsolver_destroy_handle](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__destroy__handle.html "Interface documentation") | C binding
3 | [rocsolver_set_stream](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__set__stream.html "Interface documentation") | C binding
4 | [rocsolver_get_stream](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__get__stream.html "Interface documentation") | C binding
5 | [rocsolver_set_matrix](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__set__matrix.html "Interface documentation") | C binding
6 | [rocsolver_get_matrix](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__get__matrix.html "Interface documentation") | C binding
7 | [rocsolver_get_version_string](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__get__version__string.html "Interface documentation") | C binding
8 | [rocsolver_get_version_string_size](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__get__version__string__size.html "Interface documentation") | C binding
9 | [rocsolver_log_begin](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__log__begin.html "Interface documentation") | C binding
10 | [rocsolver_log_end](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__log__end.html "Interface documentation") | C binding
11 | [rocsolver_log_set_layer_mode](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__log__set__layer__mode.html "Interface documentation") | C binding
12 | [rocsolver_log_set_max_levels](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__log__set__max__levels.html "Interface documentation") | C binding
13 | [rocsolver_log_restore_defaults](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__log__restore__defaults.html "Interface documentation") | C binding
14 | [rocsolver_log_write_profile](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__log__write__profile.html "Interface documentation") | C binding
15 | [rocsolver_log_flush_profile](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__log__flush__profile.html "Interface documentation") | C binding
16 | [rocsolver_clacgv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__clacgv.html "Interface documentation") | C binding, rank_0, rank_1
17 | [rocsolver_zlacgv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlacgv.html "Interface documentation") | C binding, rank_0, rank_1
18 | [rocsolver_slaswp](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__slaswp.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
19 | [rocsolver_dlaswp](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dlaswp.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
20 | [rocsolver_claswp](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__claswp.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
21 | [rocsolver_zlaswp](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlaswp.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
22 | [rocsolver_slarfg](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__slarfg.html "Interface documentation") | C binding, rank_0, rank_1
23 | [rocsolver_dlarfg](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dlarfg.html "Interface documentation") | C binding, rank_0, rank_1
24 | [rocsolver_clarfg](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__clarfg.html "Interface documentation") | C binding, rank_0, rank_1
25 | [rocsolver_zlarfg](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlarfg.html "Interface documentation") | C binding, rank_0, rank_1
26 | [rocsolver_slarft](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__slarft.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
27 | [rocsolver_dlarft](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dlarft.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
28 | [rocsolver_clarft](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__clarft.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
29 | [rocsolver_zlarft](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlarft.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
30 | [rocsolver_slarf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__slarf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
31 | [rocsolver_dlarf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dlarf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
32 | [rocsolver_clarf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__clarf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
33 | [rocsolver_zlarf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlarf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
34 | [rocsolver_slarfb](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__slarfb.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
35 | [rocsolver_dlarfb](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dlarfb.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
36 | [rocsolver_clarfb](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__clarfb.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
37 | [rocsolver_zlarfb](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlarfb.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
38 | [rocsolver_slabrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__slabrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
39 | [rocsolver_dlabrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dlabrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
40 | [rocsolver_clabrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__clabrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
41 | [rocsolver_zlabrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlabrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
42 | [rocsolver_slatrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__slatrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
43 | [rocsolver_dlatrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dlatrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
44 | [rocsolver_clatrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__clatrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
45 | [rocsolver_zlatrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlatrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
46 | [rocsolver_slasyf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__slasyf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
47 | [rocsolver_dlasyf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dlasyf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
48 | [rocsolver_clasyf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__clasyf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
49 | [rocsolver_zlasyf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zlasyf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
50 | [rocsolver_sorg2r](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorg2r.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
51 | [rocsolver_dorg2r](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorg2r.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
52 | [rocsolver_cung2r](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cung2r.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
53 | [rocsolver_zung2r](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zung2r.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
54 | [rocsolver_sorgqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorgqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
55 | [rocsolver_dorgqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorgqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
56 | [rocsolver_cungqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cungqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
57 | [rocsolver_zungqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zungqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
58 | [rocsolver_sorgl2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorgl2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
59 | [rocsolver_dorgl2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorgl2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
60 | [rocsolver_cungl2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cungl2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
61 | [rocsolver_zungl2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zungl2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
62 | [rocsolver_sorglq](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorglq.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
63 | [rocsolver_dorglq](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorglq.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
64 | [rocsolver_cunglq](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunglq.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
65 | [rocsolver_zunglq](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunglq.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
66 | [rocsolver_sorg2l](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorg2l.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
67 | [rocsolver_dorg2l](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorg2l.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
68 | [rocsolver_cung2l](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cung2l.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
69 | [rocsolver_zung2l](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zung2l.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
70 | [rocsolver_sorgql](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorgql.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
71 | [rocsolver_dorgql](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorgql.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
72 | [rocsolver_cungql](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cungql.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
73 | [rocsolver_zungql](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zungql.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
74 | [rocsolver_sorgbr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorgbr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
75 | [rocsolver_dorgbr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorgbr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
76 | [rocsolver_cungbr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cungbr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
77 | [rocsolver_zungbr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zungbr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
78 | [rocsolver_sorgtr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorgtr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
79 | [rocsolver_dorgtr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorgtr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
80 | [rocsolver_cungtr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cungtr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
81 | [rocsolver_zungtr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zungtr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
82 | [rocsolver_sorm2r](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorm2r.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
83 | [rocsolver_dorm2r](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorm2r.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
84 | [rocsolver_cunm2r](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunm2r.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
85 | [rocsolver_zunm2r](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunm2r.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
86 | [rocsolver_sormqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sormqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
87 | [rocsolver_dormqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dormqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
88 | [rocsolver_cunmqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunmqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
89 | [rocsolver_zunmqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunmqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
90 | [rocsolver_sorml2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorml2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
91 | [rocsolver_dorml2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorml2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
92 | [rocsolver_cunml2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunml2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
93 | [rocsolver_zunml2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunml2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
94 | [rocsolver_sormlq](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sormlq.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
95 | [rocsolver_dormlq](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dormlq.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
96 | [rocsolver_cunmlq](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunmlq.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
97 | [rocsolver_zunmlq](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunmlq.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
98 | [rocsolver_sorm2l](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sorm2l.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
99 | [rocsolver_dorm2l](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dorm2l.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
100 | [rocsolver_cunm2l](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunm2l.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
101 | [rocsolver_zunm2l](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunm2l.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
102 | [rocsolver_sormql](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sormql.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
103 | [rocsolver_dormql](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dormql.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
104 | [rocsolver_cunmql](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunmql.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
105 | [rocsolver_zunmql](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunmql.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
106 | [rocsolver_sormbr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sormbr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
107 | [rocsolver_dormbr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dormbr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
108 | [rocsolver_cunmbr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunmbr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
109 | [rocsolver_zunmbr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunmbr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
110 | [rocsolver_sormtr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sormtr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
111 | [rocsolver_dormtr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dormtr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
112 | [rocsolver_cunmtr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cunmtr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
113 | [rocsolver_zunmtr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zunmtr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
114 | [rocsolver_sbdsqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sbdsqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
115 | [rocsolver_dbdsqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dbdsqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
116 | [rocsolver_cbdsqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cbdsqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
117 | [rocsolver_zbdsqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zbdsqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
118 | [rocsolver_ssterf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssterf.html "Interface documentation") | C binding, rank_0, rank_1
119 | [rocsolver_dsterf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsterf.html "Interface documentation") | C binding, rank_0, rank_1
120 | [rocsolver_ssteqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssteqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
121 | [rocsolver_dsteqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsteqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
122 | [rocsolver_csteqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__csteqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
123 | [rocsolver_zsteqr](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zsteqr.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
124 | [rocsolver_sstedc](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sstedc.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
125 | [rocsolver_dstedc](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dstedc.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
126 | [rocsolver_cstedc](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cstedc.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
127 | [rocsolver_zstedc](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zstedc.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
128 | [rocsolver_sgetf2_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetf2__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
129 | [rocsolver_dgetf2_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetf2__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
130 | [rocsolver_cgetf2_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetf2__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
131 | [rocsolver_zgetf2_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetf2__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
132 | [rocsolver_sgetf2_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetf2__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
133 | [rocsolver_dgetf2_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetf2__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
134 | [rocsolver_cgetf2_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetf2__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
135 | [rocsolver_zgetf2_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetf2__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
136 | [rocsolver_sgetf2_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetf2__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
137 | [rocsolver_dgetf2_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetf2__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
138 | [rocsolver_cgetf2_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetf2__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
139 | [rocsolver_zgetf2_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetf2__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
140 | [rocsolver_sgetrf_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrf__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
141 | [rocsolver_dgetrf_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrf__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
142 | [rocsolver_cgetrf_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrf__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
143 | [rocsolver_zgetrf_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrf__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
144 | [rocsolver_sgetrf_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrf__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
145 | [rocsolver_dgetrf_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrf__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
146 | [rocsolver_cgetrf_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrf__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
147 | [rocsolver_zgetrf_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrf__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
148 | [rocsolver_sgetrf_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrf__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
149 | [rocsolver_dgetrf_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrf__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
150 | [rocsolver_cgetrf_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrf__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
151 | [rocsolver_zgetrf_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrf__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
152 | [rocsolver_sgetf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
153 | [rocsolver_dgetf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
154 | [rocsolver_cgetf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
155 | [rocsolver_zgetf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
156 | [rocsolver_sgetf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
157 | [rocsolver_dgetf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
158 | [rocsolver_cgetf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
159 | [rocsolver_zgetf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
160 | [rocsolver_sgetf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
161 | [rocsolver_dgetf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
162 | [rocsolver_cgetf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
163 | [rocsolver_zgetf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
164 | [rocsolver_sgetrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
165 | [rocsolver_dgetrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
166 | [rocsolver_cgetrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
167 | [rocsolver_zgetrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
168 | [rocsolver_sgetrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
169 | [rocsolver_dgetrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
170 | [rocsolver_cgetrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
171 | [rocsolver_zgetrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
172 | [rocsolver_sgetrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
173 | [rocsolver_dgetrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
174 | [rocsolver_cgetrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
175 | [rocsolver_zgetrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
176 | [rocsolver_sgeqr2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqr2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
177 | [rocsolver_dgeqr2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqr2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
178 | [rocsolver_cgeqr2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqr2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
179 | [rocsolver_zgeqr2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqr2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
180 | [rocsolver_sgeqr2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqr2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
181 | [rocsolver_dgeqr2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqr2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
182 | [rocsolver_cgeqr2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqr2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
183 | [rocsolver_zgeqr2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqr2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
184 | [rocsolver_sgeqr2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqr2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
185 | [rocsolver_dgeqr2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqr2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
186 | [rocsolver_cgeqr2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqr2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
187 | [rocsolver_zgeqr2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqr2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
188 | [rocsolver_sgerq2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgerq2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
189 | [rocsolver_dgerq2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgerq2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
190 | [rocsolver_cgerq2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgerq2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
191 | [rocsolver_zgerq2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgerq2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
192 | [rocsolver_sgerq2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgerq2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
193 | [rocsolver_dgerq2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgerq2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
194 | [rocsolver_cgerq2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgerq2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
195 | [rocsolver_zgerq2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgerq2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
196 | [rocsolver_sgerq2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgerq2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
197 | [rocsolver_dgerq2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgerq2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
198 | [rocsolver_cgerq2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgerq2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
199 | [rocsolver_zgerq2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgerq2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
200 | [rocsolver_sgeql2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeql2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
201 | [rocsolver_dgeql2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeql2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
202 | [rocsolver_cgeql2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeql2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
203 | [rocsolver_zgeql2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeql2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
204 | [rocsolver_sgeql2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeql2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
205 | [rocsolver_dgeql2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeql2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
206 | [rocsolver_cgeql2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeql2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
207 | [rocsolver_zgeql2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeql2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
208 | [rocsolver_sgeql2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeql2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
209 | [rocsolver_dgeql2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeql2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
210 | [rocsolver_cgeql2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeql2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
211 | [rocsolver_zgeql2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeql2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
212 | [rocsolver_sgelq2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgelq2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
213 | [rocsolver_dgelq2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgelq2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
214 | [rocsolver_cgelq2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgelq2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
215 | [rocsolver_zgelq2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgelq2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
216 | [rocsolver_sgelq2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgelq2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
217 | [rocsolver_dgelq2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgelq2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
218 | [rocsolver_cgelq2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgelq2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
219 | [rocsolver_zgelq2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgelq2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
220 | [rocsolver_sgelq2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgelq2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
221 | [rocsolver_dgelq2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgelq2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
222 | [rocsolver_cgelq2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgelq2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
223 | [rocsolver_zgelq2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgelq2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
224 | [rocsolver_sgeqrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
225 | [rocsolver_dgeqrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
226 | [rocsolver_cgeqrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
227 | [rocsolver_zgeqrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
228 | [rocsolver_sgeqrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
229 | [rocsolver_dgeqrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
230 | [rocsolver_cgeqrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
231 | [rocsolver_zgeqrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
232 | [rocsolver_sgeqrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
233 | [rocsolver_dgeqrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
234 | [rocsolver_cgeqrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
235 | [rocsolver_zgeqrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
236 | [rocsolver_sgerqf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgerqf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
237 | [rocsolver_dgerqf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgerqf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
238 | [rocsolver_cgerqf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgerqf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
239 | [rocsolver_zgerqf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgerqf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
240 | [rocsolver_sgerqf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgerqf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
241 | [rocsolver_dgerqf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgerqf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
242 | [rocsolver_cgerqf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgerqf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
243 | [rocsolver_zgerqf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgerqf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
244 | [rocsolver_sgerqf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgerqf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
245 | [rocsolver_dgerqf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgerqf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
246 | [rocsolver_cgerqf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgerqf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
247 | [rocsolver_zgerqf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgerqf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
248 | [rocsolver_sgeqlf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqlf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
249 | [rocsolver_dgeqlf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqlf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
250 | [rocsolver_cgeqlf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqlf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
251 | [rocsolver_zgeqlf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqlf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
252 | [rocsolver_sgeqlf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqlf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
253 | [rocsolver_dgeqlf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqlf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
254 | [rocsolver_cgeqlf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqlf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
255 | [rocsolver_zgeqlf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqlf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
256 | [rocsolver_sgeqlf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgeqlf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
257 | [rocsolver_dgeqlf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgeqlf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
258 | [rocsolver_cgeqlf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgeqlf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
259 | [rocsolver_zgeqlf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgeqlf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
260 | [rocsolver_sgelqf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgelqf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
261 | [rocsolver_dgelqf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgelqf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
262 | [rocsolver_cgelqf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgelqf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
263 | [rocsolver_zgelqf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgelqf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
264 | [rocsolver_sgelqf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgelqf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
265 | [rocsolver_dgelqf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgelqf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
266 | [rocsolver_cgelqf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgelqf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
267 | [rocsolver_zgelqf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgelqf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
268 | [rocsolver_sgelqf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgelqf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
269 | [rocsolver_dgelqf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgelqf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
270 | [rocsolver_cgelqf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgelqf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
271 | [rocsolver_zgelqf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgelqf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
272 | [rocsolver_sgebd2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgebd2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
273 | [rocsolver_dgebd2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgebd2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
274 | [rocsolver_cgebd2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgebd2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
275 | [rocsolver_zgebd2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgebd2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
276 | [rocsolver_sgebd2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgebd2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
277 | [rocsolver_dgebd2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgebd2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
278 | [rocsolver_cgebd2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgebd2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
279 | [rocsolver_zgebd2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgebd2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
280 | [rocsolver_sgebd2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgebd2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
281 | [rocsolver_dgebd2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgebd2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
282 | [rocsolver_cgebd2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgebd2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
283 | [rocsolver_zgebd2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgebd2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
284 | [rocsolver_sgebrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgebrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
285 | [rocsolver_dgebrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgebrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
286 | [rocsolver_cgebrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgebrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
287 | [rocsolver_zgebrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgebrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
288 | [rocsolver_sgebrd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgebrd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
289 | [rocsolver_dgebrd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgebrd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
290 | [rocsolver_cgebrd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgebrd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
291 | [rocsolver_zgebrd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgebrd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
292 | [rocsolver_sgebrd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgebrd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
293 | [rocsolver_dgebrd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgebrd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
294 | [rocsolver_cgebrd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgebrd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
295 | [rocsolver_zgebrd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgebrd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
296 | [rocsolver_sgetrs](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrs.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
297 | [rocsolver_dgetrs](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrs.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
298 | [rocsolver_cgetrs](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrs.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
299 | [rocsolver_zgetrs](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrs.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
300 | [rocsolver_sgetrs_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrs__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
301 | [rocsolver_dgetrs_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrs__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
302 | [rocsolver_cgetrs_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrs__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
303 | [rocsolver_zgetrs_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrs__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
304 | [rocsolver_sgetrs_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetrs__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
305 | [rocsolver_dgetrs_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetrs__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
306 | [rocsolver_cgetrs_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetrs__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
307 | [rocsolver_zgetrs_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetrs__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
308 | [rocsolver_sgesv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgesv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
309 | [rocsolver_dgesv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgesv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
310 | [rocsolver_cgesv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgesv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
311 | [rocsolver_zgesv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgesv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
312 | [rocsolver_sgesv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgesv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
313 | [rocsolver_dgesv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgesv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
314 | [rocsolver_cgesv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgesv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
315 | [rocsolver_zgesv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgesv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
316 | [rocsolver_sgesv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgesv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
317 | [rocsolver_dgesv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgesv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
318 | [rocsolver_cgesv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgesv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
319 | [rocsolver_zgesv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgesv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
320 | [rocsolver_sgetri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
321 | [rocsolver_dgetri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
322 | [rocsolver_cgetri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
323 | [rocsolver_zgetri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
324 | [rocsolver_sgetri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
325 | [rocsolver_dgetri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
326 | [rocsolver_cgetri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
327 | [rocsolver_zgetri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
328 | [rocsolver_sgetri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
329 | [rocsolver_dgetri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
330 | [rocsolver_cgetri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
331 | [rocsolver_zgetri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
332 | [rocsolver_sgetri_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
333 | [rocsolver_dgetri_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
334 | [rocsolver_cgetri_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
335 | [rocsolver_zgetri_npvt](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__npvt.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
336 | [rocsolver_sgetri_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
337 | [rocsolver_dgetri_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
338 | [rocsolver_cgetri_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
339 | [rocsolver_zgetri_npvt_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__npvt__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
340 | [rocsolver_sgetri_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
341 | [rocsolver_dgetri_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
342 | [rocsolver_cgetri_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
343 | [rocsolver_zgetri_npvt_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__npvt__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
344 | [rocsolver_sgels](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgels.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
345 | [rocsolver_dgels](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgels.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
346 | [rocsolver_cgels](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgels.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
347 | [rocsolver_zgels](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgels.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
348 | [rocsolver_sgels_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgels__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
349 | [rocsolver_dgels_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgels__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
350 | [rocsolver_cgels_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgels__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
351 | [rocsolver_zgels_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgels__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
352 | [rocsolver_sgels_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgels__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
353 | [rocsolver_dgels_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgels__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
354 | [rocsolver_cgels_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgels__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
355 | [rocsolver_zgels_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgels__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
356 | [rocsolver_spotf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
357 | [rocsolver_dpotf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
358 | [rocsolver_cpotf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
359 | [rocsolver_zpotf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
360 | [rocsolver_spotf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
361 | [rocsolver_dpotf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
362 | [rocsolver_cpotf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
363 | [rocsolver_zpotf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
364 | [rocsolver_spotf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
365 | [rocsolver_dpotf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
366 | [rocsolver_cpotf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
367 | [rocsolver_zpotf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
368 | [rocsolver_spotrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
369 | [rocsolver_dpotrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
370 | [rocsolver_cpotrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
371 | [rocsolver_zpotrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
372 | [rocsolver_spotrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
373 | [rocsolver_dpotrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
374 | [rocsolver_cpotrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
375 | [rocsolver_zpotrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
376 | [rocsolver_spotrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
377 | [rocsolver_dpotrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
378 | [rocsolver_cpotrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
379 | [rocsolver_zpotrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
380 | [rocsolver_spotrs](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotrs.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
381 | [rocsolver_dpotrs](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotrs.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
382 | [rocsolver_cpotrs](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotrs.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
383 | [rocsolver_zpotrs](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotrs.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
384 | [rocsolver_spotrs_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotrs__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
385 | [rocsolver_dpotrs_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotrs__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
386 | [rocsolver_cpotrs_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotrs__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
387 | [rocsolver_zpotrs_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotrs__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
388 | [rocsolver_spotrs_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotrs__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
389 | [rocsolver_dpotrs_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotrs__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
390 | [rocsolver_cpotrs_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotrs__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
391 | [rocsolver_zpotrs_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotrs__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
392 | [rocsolver_sposv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sposv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
393 | [rocsolver_dposv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dposv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
394 | [rocsolver_cposv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cposv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
395 | [rocsolver_zposv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zposv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
396 | [rocsolver_sposv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sposv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
397 | [rocsolver_dposv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dposv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
398 | [rocsolver_cposv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cposv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
399 | [rocsolver_zposv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zposv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
400 | [rocsolver_sposv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sposv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
401 | [rocsolver_dposv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dposv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
402 | [rocsolver_cposv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cposv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
403 | [rocsolver_zposv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zposv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
404 | [rocsolver_spotri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
405 | [rocsolver_dpotri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
406 | [rocsolver_cpotri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
407 | [rocsolver_zpotri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
408 | [rocsolver_spotri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
409 | [rocsolver_dpotri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
410 | [rocsolver_cpotri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
411 | [rocsolver_zpotri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
412 | [rocsolver_spotri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__spotri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
413 | [rocsolver_dpotri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dpotri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
414 | [rocsolver_cpotri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cpotri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
415 | [rocsolver_zpotri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zpotri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
416 | [rocsolver_sgesvd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgesvd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
417 | [rocsolver_dgesvd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgesvd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
418 | [rocsolver_cgesvd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgesvd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
419 | [rocsolver_zgesvd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgesvd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
420 | [rocsolver_sgesvd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgesvd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
421 | [rocsolver_dgesvd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgesvd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
422 | [rocsolver_cgesvd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgesvd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
423 | [rocsolver_zgesvd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgesvd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
424 | [rocsolver_sgesvd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgesvd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
425 | [rocsolver_dgesvd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgesvd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
426 | [rocsolver_cgesvd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgesvd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
427 | [rocsolver_zgesvd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgesvd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
428 | [rocsolver_ssytd2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytd2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
429 | [rocsolver_dsytd2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytd2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
430 | [rocsolver_chetd2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chetd2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
431 | [rocsolver_zhetd2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhetd2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
432 | [rocsolver_ssytd2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytd2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
433 | [rocsolver_dsytd2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytd2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
434 | [rocsolver_chetd2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chetd2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
435 | [rocsolver_zhetd2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhetd2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
436 | [rocsolver_ssytd2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytd2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
437 | [rocsolver_dsytd2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytd2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
438 | [rocsolver_chetd2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chetd2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
439 | [rocsolver_zhetd2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhetd2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
440 | [rocsolver_ssytrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
441 | [rocsolver_dsytrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
442 | [rocsolver_chetrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chetrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
443 | [rocsolver_zhetrd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhetrd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
444 | [rocsolver_ssytrd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytrd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
445 | [rocsolver_dsytrd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytrd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
446 | [rocsolver_chetrd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chetrd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
447 | [rocsolver_zhetrd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhetrd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
448 | [rocsolver_ssytrd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytrd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
449 | [rocsolver_dsytrd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytrd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
450 | [rocsolver_chetrd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chetrd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
451 | [rocsolver_zhetrd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhetrd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
452 | [rocsolver_ssygs2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygs2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
453 | [rocsolver_dsygs2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygs2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
454 | [rocsolver_chegs2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegs2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
455 | [rocsolver_zhegs2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegs2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
456 | [rocsolver_ssygs2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygs2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
457 | [rocsolver_dsygs2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygs2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
458 | [rocsolver_chegs2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegs2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
459 | [rocsolver_zhegs2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegs2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
460 | [rocsolver_ssygs2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygs2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
461 | [rocsolver_dsygs2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygs2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
462 | [rocsolver_chegs2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegs2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
463 | [rocsolver_zhegs2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegs2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
464 | [rocsolver_ssygst](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygst.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
465 | [rocsolver_dsygst](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygst.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
466 | [rocsolver_chegst](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegst.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
467 | [rocsolver_zhegst](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegst.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
468 | [rocsolver_ssygst_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygst__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
469 | [rocsolver_dsygst_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygst__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
470 | [rocsolver_chegst_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegst__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
471 | [rocsolver_zhegst_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegst__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
472 | [rocsolver_ssygst_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygst__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
473 | [rocsolver_dsygst_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygst__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
474 | [rocsolver_chegst_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegst__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
475 | [rocsolver_zhegst_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegst__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
476 | [rocsolver_ssyev](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssyev.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
477 | [rocsolver_dsyev](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsyev.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
478 | [rocsolver_cheev](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cheev.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
479 | [rocsolver_zheev](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zheev.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
480 | [rocsolver_ssyev_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssyev__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
481 | [rocsolver_dsyev_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsyev__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
482 | [rocsolver_cheev_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cheev__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
483 | [rocsolver_zheev_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zheev__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
484 | [rocsolver_ssyev_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssyev__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
485 | [rocsolver_dsyev_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsyev__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
486 | [rocsolver_cheev_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cheev__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
487 | [rocsolver_zheev_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zheev__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
488 | [rocsolver_ssyevd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssyevd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
489 | [rocsolver_dsyevd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsyevd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
490 | [rocsolver_cheevd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cheevd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
491 | [rocsolver_zheevd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zheevd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
492 | [rocsolver_ssyevd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssyevd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
493 | [rocsolver_dsyevd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsyevd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
494 | [rocsolver_cheevd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cheevd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
495 | [rocsolver_zheevd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zheevd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
496 | [rocsolver_ssyevd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssyevd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
497 | [rocsolver_dsyevd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsyevd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
498 | [rocsolver_cheevd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cheevd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
499 | [rocsolver_zheevd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zheevd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
500 | [rocsolver_ssygv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
501 | [rocsolver_dsygv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
502 | [rocsolver_chegv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
503 | [rocsolver_zhegv](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegv.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
504 | [rocsolver_ssygv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
505 | [rocsolver_dsygv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
506 | [rocsolver_chegv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
507 | [rocsolver_zhegv_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegv__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
508 | [rocsolver_ssygv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
509 | [rocsolver_dsygv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
510 | [rocsolver_chegv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
511 | [rocsolver_zhegv_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegv__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
512 | [rocsolver_ssygvd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygvd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
513 | [rocsolver_dsygvd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygvd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
514 | [rocsolver_chegvd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegvd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
515 | [rocsolver_zhegvd](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegvd.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
516 | [rocsolver_ssygvd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygvd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
517 | [rocsolver_dsygvd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygvd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
518 | [rocsolver_chegvd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegvd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
519 | [rocsolver_zhegvd_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegvd__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
520 | [rocsolver_ssygvd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssygvd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
521 | [rocsolver_dsygvd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsygvd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
522 | [rocsolver_chegvd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__chegvd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
523 | [rocsolver_zhegvd_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zhegvd__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
524 | [rocsolver_sgetri_outofplace](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__outofplace.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
525 | [rocsolver_dgetri_outofplace](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__outofplace.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
526 | [rocsolver_cgetri_outofplace](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__outofplace.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
527 | [rocsolver_zgetri_outofplace](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__outofplace.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
528 | [rocsolver_sgetri_outofplace_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__outofplace__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
529 | [rocsolver_dgetri_outofplace_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__outofplace__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
530 | [rocsolver_cgetri_outofplace_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__outofplace__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
531 | [rocsolver_zgetri_outofplace_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__outofplace__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
532 | [rocsolver_sgetri_outofplace_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__outofplace__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
533 | [rocsolver_dgetri_outofplace_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__outofplace__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
534 | [rocsolver_cgetri_outofplace_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__outofplace__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
535 | [rocsolver_zgetri_outofplace_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__outofplace__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
536 | [rocsolver_sgetri_npvt_outofplace](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__npvt__outofplace.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
537 | [rocsolver_dgetri_npvt_outofplace](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__npvt__outofplace.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
538 | [rocsolver_cgetri_npvt_outofplace](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__npvt__outofplace.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
539 | [rocsolver_zgetri_npvt_outofplace](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__npvt__outofplace.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
540 | [rocsolver_sgetri_npvt_outofplace_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__npvt__outofplace__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
541 | [rocsolver_dgetri_npvt_outofplace_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__npvt__outofplace__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
542 | [rocsolver_cgetri_npvt_outofplace_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__npvt__outofplace__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
543 | [rocsolver_zgetri_npvt_outofplace_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__npvt__outofplace__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
544 | [rocsolver_sgetri_npvt_outofplace_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__sgetri__npvt__outofplace__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
545 | [rocsolver_dgetri_npvt_outofplace_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dgetri__npvt__outofplace__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
546 | [rocsolver_cgetri_npvt_outofplace_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__cgetri__npvt__outofplace__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
547 | [rocsolver_zgetri_npvt_outofplace_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zgetri__npvt__outofplace__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
548 | [rocsolver_strtri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__strtri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
549 | [rocsolver_dtrtri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dtrtri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
550 | [rocsolver_ctrtri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ctrtri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
551 | [rocsolver_ztrtri](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ztrtri.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
552 | [rocsolver_strtri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__strtri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
553 | [rocsolver_dtrtri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dtrtri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
554 | [rocsolver_ctrtri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ctrtri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
555 | [rocsolver_ztrtri_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ztrtri__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
556 | [rocsolver_strtri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__strtri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
557 | [rocsolver_dtrtri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dtrtri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
558 | [rocsolver_ctrtri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ctrtri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
559 | [rocsolver_ztrtri_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ztrtri__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
560 | [rocsolver_ssytf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
561 | [rocsolver_dsytf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
562 | [rocsolver_csytf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__csytf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
563 | [rocsolver_zsytf2](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zsytf2.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
564 | [rocsolver_ssytf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
565 | [rocsolver_dsytf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
566 | [rocsolver_csytf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__csytf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
567 | [rocsolver_zsytf2_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zsytf2__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
568 | [rocsolver_ssytf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
569 | [rocsolver_dsytf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
570 | [rocsolver_csytf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__csytf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
571 | [rocsolver_zsytf2_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zsytf2__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
572 | [rocsolver_ssytrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
573 | [rocsolver_dsytrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
574 | [rocsolver_csytrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__csytrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
575 | [rocsolver_zsytrf](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zsytrf.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
576 | [rocsolver_ssytrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
577 | [rocsolver_dsytrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
578 | [rocsolver_csytrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__csytrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
579 | [rocsolver_zsytrf_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zsytrf__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
580 | [rocsolver_ssytrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__ssytrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
581 | [rocsolver_dsytrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__dsytrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
582 | [rocsolver_csytrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__csytrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1
583 | [rocsolver_zsytrf_strided_batched](https://rocmsoftwareplatform.github.io/hipfort/interfacehipfort__rocsolver_1_1rocsolver__zsytrf__strided__batched.html "Interface documentation") | C binding, full_rank, rank_0, rank_1 | 205.755556 | 259 | 0.855243 | yue_Hant | 0.182102 |
a6f71597000630732ae034e458200997c4441f31 | 450 | md | Markdown | README.md | andr-ik/yii2-demo-news-site | ef0006142c78801a82e19efd9ae97235312b1e5c | [
"BSD-3-Clause"
] | 1 | 2015-10-27T14:24:01.000Z | 2015-10-27T14:24:01.000Z | README.md | andr-ik/yii2-demo-news-site | ef0006142c78801a82e19efd9ae97235312b1e5c | [
"BSD-3-Clause"
] | null | null | null | README.md | andr-ik/yii2-demo-news-site | ef0006142c78801a82e19efd9ae97235312b1e5c | [
"BSD-3-Clause"
] | null | null | null | YII 2 Demo news site
============================
Демо сайт новостей с категориями на yii2
Установка
------------
Клон
~~~
git clone [email protected]:andr-ik/yii2-demo-news-site.git
~~~
Миграции
~~~
yii migrate
yii migrate --migrationPath=@yii/rbac/migrations/
~~~
Фикстуры пользователей
~~~
yii fixture User --namespace='app\fixtures'
~~~
Фикстуры данных
~~~
yii data-load
~~~
Инициализация RBAC
~~~
yii rbac/init
~~~
...
...
...
Profit! | 10.227273 | 56 | 0.622222 | kor_Hang | 0.057665 |
a6f73cfb0a465e4450499de3a5a3f6392244ec66 | 24 | md | Markdown | README.md | linx05/dijkstras-distance-es6 | 346aeab21837fa42d960e32ad341bef3de200ce5 | [
"MIT"
] | null | null | null | README.md | linx05/dijkstras-distance-es6 | 346aeab21837fa42d960e32ad341bef3de200ce5 | [
"MIT"
] | null | null | null | README.md | linx05/dijkstras-distance-es6 | 346aeab21837fa42d960e32ad341bef3de200ce5 | [
"MIT"
] | null | null | null | # dijkstras-distance-es6 | 24 | 24 | 0.833333 | lvs_Latn | 0.31747 |
a6f7a5068177c323dfd9404d67a19329231d5c31 | 9,558 | md | Markdown | docs/connect/jdbc/use-spatial-datatypes.md | EddieBreeveld/sql-docs | e821cd8e5daf95721caa1e64c2815a4523227aa4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/connect/jdbc/use-spatial-datatypes.md | EddieBreeveld/sql-docs | e821cd8e5daf95721caa1e64c2815a4523227aa4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/connect/jdbc/use-spatial-datatypes.md | EddieBreeveld/sql-docs | e821cd8e5daf95721caa1e64c2815a4523227aa4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Using Spatial Datatypes | Microsoft Docs"
ms.custom: ""
ms.date: "01/21/2018"
ms.prod: sql
ms.prod_service: connectivity
ms.reviewer: ""
ms.technology: connectivity
ms.topic: conceptual
ms.assetid:
author: MightyPen
ms.author: genemi
---
# Using Spatial Datatypes
[!INCLUDE[Driver_JDBC_Download](../../includes/driver_jdbc_download.md)]
Spatial datatypes (Geometry and Geography) are supported starting JDBC Driver preview release 6.5.0. Spatial datatypes are currently not supported with stored procedures, Table Valued Parameters (TVP), BulkCopy, and Always Encrypted. This page shows various use cases of Geometry and Geography data types with the JDBC Driver. For an overview on spatial datatypes, check [Spatial Data Types Overview](https://docs.microsoft.com/sql/relational-databases/spatial/spatial-data-types-overview) page.
## Creating a Geometry / Geography object
There are two main ways to create a Geometry / Geography object - either convert from a Well-Known Text (WKT) or a Well-Known Binary (WKB).
### Creating from WKT
```java
String geoWKT = "LINESTRING(1 0, 0 1, -1 0)";
Geometry geomWKT = Geometry.STGeomFromText(geoWKT, 0);
Geography geogWKT = Geography.STGeomFromText(geoWKT, 4326);
```
This will create a LINESTRING Geometry object with Spatial Reference System Identifier (SRID) 0, and a Geography object with SRID 4326.
### Creating from WKB
```java
byte[] geomWKB = Hex.decodeHex("00000000010403000000000000000000F03F00000000000000000000000000000000000000000000F03F000000000000F0BF000000000000000001000000010000000001000000FFFFFFFF0000000002".toCharArray());
byte[] geogWKB = Hex.decodeHex("E61000000104030000000000000000000000000000000000F03F000000000000F03F00000000000000000000000000000000000000000000F0BF01000000010000000001000000FFFFFFFF0000000002".toCharArray());
Geometry geomWKT = Geometry.deserialize(geomWKB);
Geography geogWKT = Geography.deserialize(geogWKB);
```
This will create a Geometry and Geography object that is equivalent to the ones created from the WKT previously.
## Working with a Geometry / Geography object
Assuming the user has a table on SQL Server like below:
```sql
CREATE TABLE sampleTable (c1 geometry)
```
A sample script to insert a Geometry value would be:
```java
String geoWKT = "LINESTRING(1 0, 0 1, -1 0)";
Geometry geomWKT = Geometry.STGeomFromText(geoWKT, 0);
SQLServerPreparedStatement pstmt = (SQLServerPreparedStatement) connection.prepareStatement("insert into sampleTable values (?)");
pstmt.setGeometry(1, geomWKT);
pstmt.execute();
```
The same can be done for the Geography counterpart, using a Geography column and **setGeography()** method.
To read a Geometry / Geography column:
```java
try(SQLServerResultSet rs = (SQLServerResultSet)stmt.executeQuery("select * from geomTable")) {
while(rs.next()){
rs.getGeometry(1);
}
}
```
The same can be done for the Geography counterpart, using a Geography column and **getGeography()** method.
## Newly introduced APIs
These are the new public APIs that have been introduced with this addition, in the classes **SQLServerPreparedStatement**, **SQLServerResultSet**, **Geometry**, and **Geography**.
### SQLServerPreparedStatement
|Method|Description|
|:------|:----------|
|void setGeometry(int n, Geometry x)| Sets the designated parameter to the given microsoft.sql.Geometry Class object.
|void setGeography(int n, Geography x)| Sets the designated parameter to the given microsoft.sql.Geography Class object.
### SQLServerResultSet
|Method|Description|
|:------|:----------|
|Geometry getGeometry(int colunIndex)| Returns the value of the designated column in the current row of this ResultSet object as a com.microsoft.sqlserver.jdbc.Geometry object in the Java programming language.
|Geometry getGeometry(String columnName)| Returns the value of the designated column in the current row of this ResultSet object as a com.microsoft.sqlserver.jdbc.Geometry object in the Java programming language.
|Geography getGeography(int colunIndex)| Returns the value of the designated column in the current row of this ResultSet object as a com.microsoft.sqlserver.jdbc.Geography object in the Java programming language.
|Geography getGeography(String columnName)| Returns the value of the designated column in the current row of this ResultSet object as a com.microsoft.sqlserver.jdbc.Geography object in the Java programming language.
### Geometry
|Method|Description|
|:------|:----------|
|Geometry STGeomFromText(String wkt, int SRID)| Constructor for a Geometry instance from an Open Geospatial Consortium (OGC) Well-Known Text (WKT) representation augmented with any Z (elevation) and M (measure) values carried by the instance.
|Geometry STGeomFromWKB(byte[] wkb)| Constructor for a Geometry instance from an Open Geospatial Consortium (OGC) Well-Known Binary (WKB) representation.
|Geometries deserialize(byte[] wkb)| Constructor for a Geometry instance from an internal SQL Server format for spatial data.
|Geometry parse(String wkt)| Constructor for a Geometry instance from an Open Geospatial Consortium (OGC) Well-Known Text (WKT) representation. Spatial Reference Identifier is defaulted to 0.
|Geometry point(double x, double y, int SRID)| Constructor for a Geometry instance that represents a Point instance from its X and Y values and a Spatial Reference Identifier.
|String STAsText()| Returns the Open Geospatial Consortium (OGC) Well-Known Text (WKT) representation of a Geometry instance. This text will not contain any Z (elevation) or M (measure) values carried by the instance.
|byte[] STAsBinary()| Returns the Open Geospatial Consortium (OGC) Well-Known Binary (WKB) representation of a Geometry instance. This value will not contain any Z or M values carried by the instance.
|byte[] serialize()| Returns the bytes that represent an internal SQL Server format of Geometry type.
|boolean hasM()| Returns if the object contains an M (measure) value.
|boolean hasZ()| Returns if the object contains a Z (elevation) value.
|Double getX()| Returns the X coordinate value.
|Double getY()| Returns the Y coordinate value.
|Double getM()| Returns the M (measure) value of the object.
|Double getZ()| Returns the Z (elevation) value of the object.
|int getSrid()| Returns the Spatial Reference Identifier (SRID) value.
|boolean isNull()| Returns if the Geometry object is null.
|int STNumPoints()| Returns the number of points in the Geometry object.
|String STGeometryType()| Returns the Open Geospatial Consortium (OGC) type name represented by a geometry instance.
|String asTextZM()| Returns the Well-Known Text (WKT) representation of the Geometry object.
|String toString()| Returns the String representation of the Geometry object.
### Geography
|Method|Description|
|:------|:----------|
|Geography STGeomFromText(String wkt, int SRID)| Constructor for a Geography instance from an Open Geospatial Consortium (OGC) Well-Known Text (WKT) representation augmented with any Z (elevation) and M (measure) values carried by the instance.
|Geography STGeomFromWKB(byte[] wkb)| Constructor for a Geography instance from an Open Geospatial Consortium (OGC) Well-Known Binary (WKB) representation.
|Geography deserialize(byte[] wkb)| Constructor for a Geography instance from an internal SQL Server format for spatial data.
|Geography parse(String wkt)| Constructor for a Geography instance from an Open Geospatial Consortium (OGC) Well-Known Text (WKT) representation. Spatial Reference Identifier is defaulted to 0.
|Geography point(double lon, double lat, int SRID)| Constructor for a Geography instance that represents a Point instance from its longitude and latitude and a Spatial Reference Identifier.
|String STAsText()| Returns the Open Geospatial Consortium (OGC) Well-Known Text (WKT) representation of a Geography instance. This text will not contain any Z (elevation) or M (measure) values carried by the instance.
|byte[] STAsBinary())| Returns the Open Geospatial Consortium (OGC) Well-Known Binary (WKB) representation of a Geography instance. This value will not contain any Z or M values carried by the instance.
|byte[] serialize()| Returns the bytes that represent an internal SQL Server format of Geography type.
|boolean hasM()| Returns if the object contains an M (measure) value.
|boolean hasZ()| Returns if the object contains a Z (elevation) value.
|Double getLatitude()| Returns the latitude value.
|Double getLongitude()| Returns the longitude value.
|Double getM()| Returns the M (measure) value of the object.
|Double getZ()| Returns the Z (elevation) value of the object.
|int getSrid()| Returns the Spatial Reference Identifier (SRID) value.
|boolean isNull()| Returns if the Geography object is null.
|int STNumPoints()| Returns the number of points in the Geography object.
|String STGeographyType()| Returns the Open Geospatial Consortium (OGC) type name represented by a geography instance.
|String asTextZM()| Returns the Well-Known Text (WKT) representation of the Geography object.
|String toString()| Returns the String representation of the Geography object.
## Limitations of Spatial Datatypes
1. The spatial sub-datatypes **CircularString**, **CompoundCurve**, **CurvePolygon**, and **FullGlobe** are only supported starting from SQL Server 2012 and above.
2. Always Encrypted cannot be used with spatial datatypes.
3. Stored procedures, TVP, and BulkCopy operations are currently not supported with spatial datatypes.
## See Also
[Spatial Data Types Sample (JDBC)](../../connect/jdbc/spatial-data-types-sample.md)
| 60.113208 | 495 | 0.781335 | eng_Latn | 0.852667 |
a6f7fbbfe1025725f18d490aeacb4aeb0509a4d5 | 6,926 | md | Markdown | docs/database-engine/configure-windows/affinity-input-output-mask-server-configuration-option.md | way0utwest/sql-docs | c5224ee523e9d5b95f1bb9a2a07699a1ea11cf6d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-01T15:27:25.000Z | 2021-04-01T15:27:25.000Z | docs/database-engine/configure-windows/affinity-input-output-mask-server-configuration-option.md | way0utwest/sql-docs | c5224ee523e9d5b95f1bb9a2a07699a1ea11cf6d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/database-engine/configure-windows/affinity-input-output-mask-server-configuration-option.md | way0utwest/sql-docs | c5224ee523e9d5b95f1bb9a2a07699a1ea11cf6d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "affinity Input-Output mask Server Configuration Option | Microsoft Docs"
ms.custom: ""
ms.date: "07/06/2017"
ms.prod: "sql-non-specified"
ms.prod_service: "database-engine"
ms.service: ""
ms.component: "configure-windows"
ms.reviewer: ""
ms.suite: "sql"
ms.technology:
- "database-engine"
ms.tgt_pltfrm: ""
ms.topic: "article"
helpviewer_keywords:
- "affinity I/O mask option"
- "processor affinity [SQL Server]"
- "binding processors [SQL Server]"
- "CPU affinity mask option"
ms.assetid: 9950a8c9-9fe0-4003-95df-6f0d1becb0e7
caps.latest.revision: 29
author: "BYHAM"
ms.author: "rickbyh"
manager: "jhubbard"
ms.workload: "Inactive"
---
# affinity Input-Output mask Server Configuration Option
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
To carry out multitasking, [!INCLUDE[msCoName](../../includes/msconame-md.md)] Windows sometimes move process threads among different processors. Although efficient from an operating system point of view, this activity can reduce [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] performance under heavy system loads, as each processor cache is repeatedly reloaded with data. Assigning processors to specific threads can improve performance under these conditions by eliminating processor reloads; such an association between a thread and a processor is called processor affinity.
[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] supports processor affinity by means of two affinity mask options: **affinity mask** (also known as **CPU affinity mask**) and **affinity I/O mask**. For more information on the **affinity mask** option, see [affinity mask Server Configuration Option](../../database-engine/configure-windows/affinity-mask-server-configuration-option.md). CPU and I/O affinity support for servers with 33 to 64 processors requires the additional use of the [affinity64 mask Server Configuration Option](../../database-engine/configure-windows/affinity64-mask-server-configuration-option.md) and [affinity64 Input-Output mask Server Configuration Option](../../database-engine/configure-windows/affinity64-input-output-mask-server-configuration-option.md) respectively.
> [!NOTE]
> Affinity support for servers with 33 to 64 processors is only available on 64-bit operating systems.
The **affinity I/O mask** option binds [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] disk I/O to a specified subset of CPUs. In high-end [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] online transactional processing (OLTP) environments, this extension can enhance the performance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] threads issuing I/Os. This enhancement does not support hardware affinity for individual disks or disk controllers.
The value for **affinity I/O mask** specifies which CPUs in a multiprocessor computer are eligible to process [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] disk I/O operations. The mask is a bitmap in which the rightmost bit specifies the lowest-order CPU(0), the bit to its immediate left specifies the next-lowest-order CPU(1), and so on. To configure more than 32 processors, set both the **affinity I/O mask** and the **affinity64 I/O mask**.
The values for **affinity I/O mask** are as follows:
- A 1-byte **affinity I/O mask** covers up to 8 CPUs in a multiprocessor computer.
- A 2-byte **affinity I/O mask** covers up to 16 CPUs in a multiprocessor computer.
- A 3-byte **affinity I/O mask** covers up to 24 CPUs in a multiprocessor computer.
- A 4-byte **affinity I/O mask** covers up to 32 CPUs in a multiprocessor computer.
- To cover more than 32 CPUs, configure a four-byte **affinity I/O mask** for the first 32 CPUs and up to a four-byte **affinity64 I/O mask** for the remaining CPUs.
A 1 bit in the affinity I/O pattern specifies that the corresponding CPU is eligible to perform [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] disk I/O operations; a 0 bit specifies that no [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] disk I/O operations should be scheduled for the corresponding CPU. When all bits are set to zero, or **affinity I/O mask** is not specified, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] disk I/O is scheduled to any of the CPUs eligible to process [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] threads.
Because setting the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] **affinity I/O mask** option is a specialized operation, it should be used only when necessary. In most cases, the Windows 2000 or Windows Server 2003 default affinity provides the best performance.
When specifying the **affinity I/O mask** option, you must use it with the **affinity mask** configuration option. Do not enable the same CPU in both the **affinity I/O mask** switch and the **affinity mask** option. The bits corresponding to each CPU should be in one of the following three states:
- 0 in both the **affinity I/O mask** option and the **affinity mask** option.
- 1 in the **affinity I/O mask** option and 0 in the **affinity mask** option.
- 0 in the **affinity I/O mask** option and 1 in the **affinity mask** option.
The **affinity I/O mask** option is an advanced option. If you are using the **sp_configure** system stored procedure to change the setting, you can change **affinity I/O mask** only when **show advanced options** is set to 1. In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], reconfiguring the **affinity I/O mask** option requires a restart of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance.
> [!CAUTION]
> Do not configure CPU affinity in the Windows operating system and also configure the affinity mask in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. These settings are attempting to achieve the same result, and if the configurations are inconsistent, you may have unpredictable results. [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] CPU affinity is best configured using the **sp_configure** option in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
## See Also
[Monitor Resource Usage (System Monitor)](../../relational-databases/performance-monitor/monitor-resource-usage-system-monitor.md)
[RECONFIGURE (Transact-SQL)](../../t-sql/language-elements/reconfigure-transact-sql.md)
[Server Configuration Options (SQL Server)](../../database-engine/configure-windows/server-configuration-options-sql-server.md)
[sp_configure (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-configure-transact-sql.md)
| 89.948052 | 813 | 0.734768 | eng_Latn | 0.957581 |
a6f816c3493e15dab1bf4dafc102036ee3c51a3c | 3,102 | md | Markdown | articles/hdinsight/hdinsight-sdk-dotnet-samples.md | ZetaPR/azure-docs.es-es | 0e2bf787d1d9ab12065fcb1091a7f13b96c6f8a2 | [
"CC-BY-4.0",
"MIT"
] | 66 | 2017-07-09T03:34:12.000Z | 2022-03-05T21:27:20.000Z | articles/hdinsight/hdinsight-sdk-dotnet-samples.md | ZetaPR/azure-docs.es-es | 0e2bf787d1d9ab12065fcb1091a7f13b96c6f8a2 | [
"CC-BY-4.0",
"MIT"
] | 671 | 2017-06-29T16:36:35.000Z | 2021-12-03T16:34:03.000Z | articles/hdinsight/hdinsight-sdk-dotnet-samples.md | ZetaPR/azure-docs.es-es | 0e2bf787d1d9ab12065fcb1091a7f13b96c6f8a2 | [
"CC-BY-4.0",
"MIT"
] | 171 | 2017-07-25T06:26:46.000Z | 2022-03-23T09:07:10.000Z | ---
title: 'Azure HDInsight: ejemplos de .NET'
description: Busque ejemplos de .NET de C# en GitHub de tareas comunes mediante el SDK de HDInsight para .NET.
ms.service: hdinsight
ms.topic: sample
ms.date: 12/06/2019
ms.openlocfilehash: 9d32bdb5653d0744448acc50ca2f79d680ad14dc
ms.sourcegitcommit: 91fdedcb190c0753180be8dc7db4b1d6da9854a1
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 06/17/2021
ms.locfileid: "122643554"
---
# <a name="azure-hdinsight-net-samples"></a>Azure HDInsight: ejemplos de .NET
> [!div class="op_single_selector"]
> * [Ejemplos de .NET](hdinsight-sdk-dotnet-samples.md)
> * [Ejemplos de Python](hdinsight-sdk-python-samples.md)
> * [Ejemplos de Java](hdinsight-sdk-java-samples.md)
<!-- * [Go Examples](hdinsight-sdk-go-samples.md)-->
En este artículo se proporciona:
* Vínculos a ejemplos de tareas de creación de clústeres.
* Vínculos a contenido de referencia de otras tareas de administración.
Puede [activar los beneficios de suscripción a Visual Studio](https://azure.microsoft.com/pricing/member-offers/msdn-benefits-details/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio): su suscripción a Visual Studio le proporciona créditos todos los meses que puede usar para servicios de Azure de pago.
[!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)]
## <a name="prerequisite"></a>Requisito previo
[SDK de HDInsight de Azure para .NET](/dotnet/api/overview/azure/hdinsight#sdk-installation)
## <a name="cluster-management---creation"></a>Administración de clústeres: creación
* [Creación de un clúster de Kafka](https://github.com/Azure-Samples/hdinsight-dotnet-sdk-samples/blob/master/Management/Microsoft.Azure.Management.HDInsight.Samples/Microsoft.Azure.Management.HDInsight.Samples/CreateKafkaClusterSample.cs)
* [Creación de un clúster de Spark](https://github.com/Azure-Samples/hdinsight-dotnet-sdk-samples/blob/master/Management/Microsoft.Azure.Management.HDInsight.Samples/Microsoft.Azure.Management.HDInsight.Samples/CreateSparkClusterSample.cs)
* [Creación de un clúster de Spark con Azure Data Lake Storage Gen2](https://github.com/Azure-Samples/hdinsight-dotnet-sdk-samples/blob/master/Management/Microsoft.Azure.Management.HDInsight.Samples/Microsoft.Azure.Management.HDInsight.Samples/CreateHadoopClusterWithAdlsGen2Sample.cs)
* [Creación de un clúster de Spark con Enterprise Security Package (ESP)](https://github.com/Azure-Samples/hdinsight-dotnet-sdk-samples/blob/master/Management/Microsoft.Azure.Management.HDInsight.Samples/Microsoft.Azure.Management.HDInsight.Samples/CreateEspClusterSample.cs)
Para obtener estos ejemplos para .NET, clone el repositorio de GitHub [hdinsight-dotnet-sdk-samples](https://github.com/Azure-Samples/hdinsight-dotnet-sdk-samples).
[!INCLUDE [hdinsight-sdk-additional-functionality](includes/hdinsight-sdk-additional-functionality.md)]
En la [documentación de referencia de SDK de HDInsight para .-NET](/dotnet/api/overview/azure/hdinsight) puede encontrar fragmentos de código para esta funcionalidad adicional de SDK.
| 66 | 340 | 0.805287 | spa_Latn | 0.445369 |
a6f8282074ff0ea9c73139b5c5c8dfc8c9ab3115 | 7,208 | md | Markdown | readme.md | bnomei/kirby3-htmlhead | 15cdb377e71145fb0c0f125a0447ed4e31086b24 | [
"MIT"
] | 13 | 2018-12-04T15:22:07.000Z | 2022-02-23T22:21:52.000Z | readme.md | bnomei/kirby3-htmlhead | 15cdb377e71145fb0c0f125a0447ed4e31086b24 | [
"MIT"
] | 24 | 2018-07-27T06:39:16.000Z | 2022-02-22T16:20:58.000Z | readme.md | bnomei/kirby3-htmlhead | 15cdb377e71145fb0c0f125a0447ed4e31086b24 | [
"MIT"
] | 2 | 2019-03-08T08:11:08.000Z | 2020-04-24T07:52:45.000Z | # Kirby 3 HTMLHead
[](https://travis-ci.com/bnomei/kirby3-htmlhead)
[](https://coveralls.io/github/bnomei/kirby3-htmlhead)
[](https://codeclimate.com/github/bnomei/kirby3-htmlhead)
[](https://twitter.com/bnomei)
Kirby 3 Plugin for a best-practice HTML Head Element extendable with snippets.
## Commercial Usage
> <br>
><b>Support open source!</b><br><br>
> This plugin is free but if you use it in a commercial project please consider to sponsor me or make a donation.<br>
> If my work helped you to make some cash it seems fair to me that I might get a little reward as well, right?<br><br>
> Be kind. Share a little. Thanks.<br><br>
> ‐ Bruno<br>
>
| M | O | N | E | Y |
|---|----|---|---|---|
| [Github sponsor](https://github.com/sponsors/bnomei) | [Patreon](https://patreon.com/bnomei) | [Buy Me a Coffee](https://buymeacoff.ee/bnomei) | [Paypal dontation](https://www.paypal.me/bnomei/15) | [Buy a Kirby license using this affiliate link](https://a.paddle.com/v2/click/1129/35731?link=1170) |
## Installation
- unzip [master.zip](https://github.com/bnomei/kirby3-htmlhead/archive/master.zip) as folder `site/plugins/kirby3-htmlhead` or
- `git submodule add https://github.com/bnomei/kirby3-htmlhead.git site/plugins/kirby3-htmlhead` or
- `composer require bnomei/kirby3-htmlhead`
## Works well with
- [pedroborges/kirby-meta-tags](https://github.com/pedroborges/kirby-meta-tags) to add OpenGraph, Twitter and JSON-ld
- and some of my [other Plugins](https://github.com/bnomei/kirby3-htmlhead/blob/master/composer.json#L76)
## Usage
### Page Method: htmlhead
In any template or your `header` snippet call the page method right after the tags that should come first.
```diff
<!DOCTYPE html>
- <html>
+ <html <?= site()->langAttr() ?>>
<head>
- <meta charset="utf-8">
- <meta http-equiv="x-ua-compatible" content="ie=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1 shrink-to-fit=no">
- <base href="<?= site()->url() ?>'">'
- <title><?= $page->title() ?></title>
+ <?= $page->htmlhead() ?>
+ <?= $page->metaTags(['og', 'twitter', 'json-ld']) ?>
```
> TIP: `$page->metaTags()` is from [pedroborges/kirby-meta-tags](https://github.com/pedroborges/kirby-meta-tags) which you will probably install for OpenGraph, Twitter and JSON-ld. But you will have to either set the `title` and `base` option to `null` in its config or specify which tags to render and omit `title` and `base`.
You can also override any defaults in forwarding the **new or additional** data to the page method.
```php
<?= $page->htmlhead([
// override defaults
'htmlhead/meta-robots' => function ($kirby, $site, $page) {
return ['content' => 'noindex']; // do not index this page
},
// add new
'htmlhead/link-feedrss' => function ($kirby, $site, $page) {
return []; // use defaults of snippet
},
]) ?>
```
### Site Method: attrLang
There is a language helper available as well.
```php
<?php ?>
<html <?= site()->langAttr() ?>>
<!-- ... -->
</html>
```
## Setting
There is only one setting called `bnomei.htmlhead.snippets` and it takes an array of callbacks. It has [sensible defaults](https://github.com/bnomei/kirby3-htmlhead/blob/master/index.php) but you can add any of [the provided snippets](https://github.com/bnomei/kirby3-htmlhead/blob/master/snippets/htmlhead) or your own snippets. The unittests for this plugin have a [more specific example](https://github.com/bnomei/kirby3-htmlhead/blob/master/tests/config/config.php) for you to explore.
**https://github.com/bnomei/kirby3-htmlhead/blob/master/tests/config/config.php**
```php
<?php
return [
'bnomei.htmlhead.snippets' => [
/********************************
* IMPORTANT: order matters!
*/
'htmlhead/recommended-minimum' => null,
'htmlhead/title' => function ($kirby, $site, $page) {
return ['title' => $page->title()];
},
'htmlhead/base' => function ($kirby, $site, $page) {
return ['href' => kirby()->site()->url()];
},
'htmlhead/link-preload' => function ($kirby, $site, $page) {
return ['files' => ['/assets/app.css', '/endpoint/data.json']];
},
'htmlhead/link-prefetch' => function ($kirby, $site, $page) {
return ['files' => ['/assets/next-page.js']];
},
'htmlhead/meta-robots' => function ($kirby, $site, $page) {
return ['content' => 'index, follow, noodp'];
},
'htmlhead/meta-author' => function ($kirby, $site, $page) {
return ['content' => $site->author()];
},
'htmlhead/meta-description' => function ($kirby, $site, $page) {
return ['content' => Str::unhtml($page->seodesc())];
},
'htmlhead/link-css' => function ($kirby, $site, $page) {
return ['files' => ['/assets/app.css']];
},
'htmlhead/script-js' => function ($kirby, $site, $page) {
return ['files' => [
[
'src' => '//unpkg.com/alpinejs',
'defer' => true,
],
'/assets/app.js',
'https://cdn.jsdelivr.net/npm/[email protected]/webfontloader.min.js|sha256-4O4pS1SH31ZqrSO2A/2QJTVjTPqVe+jnYgOWUVr7EEc=',
]];
},
'htmlhead/script-webfontloader' => function ($kirby, $site, $page) {
return [
'nonce' => null, // $page->nonceAttr('my-webfontloader-nonce') from https://github.com/bnomei/kirby3-security-headers#setter
'json' => [
'google' => [
'families' => ['Montserrat']
],
],
];
},
'htmlhead/link-a11ycss' => function ($kirby, $site, $page) {
return ['url' => 'https://github.com/ffoodd/a11y.css/blob/master/css/a11y-en_errors-only.css'];
},
'htmlhead/link-feedrss' => function ($kirby, $site, $page) {
// defaults
return [
'url' => url('/feed'),
'title' => $page->title(),
];
},
],
// ... other options
];
```
## Disclaimer
This plugin is provided "as is" with no guarantee. Use it at your own risk and always test it yourself before using it in a production environment. If you find any issues, please [create a new issue](https://github.com/bnomei/kirby3-htmlhead/issues/new).
## License
[MIT](https://opensource.org/licenses/MIT)
It is discouraged to use this plugin in any project that promotes racism, sexism, homophobia, animal abuse, violence or any other form of hate speech.
| 43.161677 | 489 | 0.615844 | eng_Latn | 0.380915 |
a6f9b4c7f0b1891f143f8284d6510ab4e25c7bc4 | 3,634 | md | Markdown | docs/runtimes/function.md | kpicaza/bref | 728df2cc4650f90a58b3ec5fb5d07381b26f1734 | [
"MIT"
] | 2 | 2020-08-11T16:13:52.000Z | 2020-08-11T22:40:37.000Z | docs/runtimes/function.md | kpicaza/bref | 728df2cc4650f90a58b3ec5fb5d07381b26f1734 | [
"MIT"
] | 1 | 2021-05-11T23:31:18.000Z | 2021-05-11T23:31:18.000Z | docs/runtimes/function.md | kpicaza/bref | 728df2cc4650f90a58b3ec5fb5d07381b26f1734 | [
"MIT"
] | 1 | 2019-12-03T14:22:48.000Z | 2019-12-03T14:22:48.000Z | ---
title: PHP functions
current_menu: php-functions
introduction: Learn how to run serverless PHP functions on AWS Lambda using Bref.
previous:
link: /docs/runtimes/
title: What are runtimes?
next:
link: /docs/runtimes/http.html
title: HTTP applications
---
The simplest way to write a lambda is to write one in the form of a PHP function:
```php
<?php
require __DIR__.'/vendor/autoload.php';
lambda(function ($event) {
return 'Hello ' . ($event['name'] ?? 'world');
});
```
This form is very similar to lambdas written in other languages, [for example JavaScript](https://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-handler.html):
```javascript
exports.myHandler = async function (event, context) {
return "Hello " + event.name;
}
```
## The function
A function can be defined by calling Bref's `lambda()` function and passing it a *callable*. The callable can be an anonymous function or [any kind of callable supported by PHP](http://php.net/manual/en/language.types.callable.php).
```php
<?php
require __DIR__.'/vendor/autoload.php';
lambda(function ($event) {
return /* response */;
});
```
The function:
- takes an `$event` parameter which contains data from the event that triggered the function ([list of examples here](https://docs.aws.amazon.com/lambda/latest/dg/eventsources.html))
- can optionally return a response: the response must be serializable to JSON
There must be only one function defined per PHP file.
### Context
The function is invoked with the `$event` parameter as well a `$context` parameter that can be optionally declared if you want to use it:
```php
<?php
use Bref\Context\Context;
require __DIR__.'/vendor/autoload.php';
lambda(function ($event, Context $context) {
return /* response */;
});
```
The `Context` object is inspired from the [`context` parameter in other languages](https://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-context.html) and provides information about the current lambda invocation (the request ID, the X-Ray trace ID, etc.).
## `serverless.yml` configuration
Below is a minimal `serverless.yml` to deploy a function. To create it automatically run `vendor/bin/bref init`.
```yaml
service: app
provider:
name: aws
runtime: provided
plugins:
- ./vendor/bref/bref
functions:
hello:
handler: index.php
layers:
- ${bref:layer.php-73}
```
The runtime to use is `php`. To learn more check out [the runtimes documentation](/docs/runtimes/README.md).
## Invocation
A PHP function must be invoked via the AWS Lambda API. If you instead want to write a classic HTTP application read the [HTTP guide](http.md).
### CLI
A PHP function can be triggered manually from the CLI using the [`serverless invoke` command](https://serverless.com/framework/docs/providers/aws/cli-reference/invoke/):
```bash
$ serverless invoke -f <function-name>
"Hello world"
```
To pass event data to the lambda use the `--data` option. For example:
```bash
serverless invoke -f <function-name> --data='{"name": "John" }'
```
Run `serverless invoke --help` to learn more about the `invoke` command.
### From PHP applications
A PHP function can be triggered from another PHP application using the AWS PHP SDK:
```php
$lambda = new \Aws\Lambda\LambdaClient([
'version' => 'latest',
'region' => <region>,
]);
$result = $lambda->invoke([
'FunctionName' => '<function-name>',
'InvocationType' => 'RequestResponse',
'LogType' => 'None',
'Payload' => json_encode(/* event data */),
]);
$result = json_decode($result->get('Payload')->getContents(), true);
```
| 27.530303 | 264 | 0.706109 | eng_Latn | 0.886942 |
a6f9c2d1d90f11fa89c998686d23b20040072b6f | 2,634 | md | Markdown | docs/release-process.md | casuallc/mop | 71504552f5770bca2b87ad06d84e7d1f63b23f4c | [
"Apache-2.0"
] | 97 | 2020-09-24T19:29:54.000Z | 2022-03-31T01:11:39.000Z | docs/release-process.md | casuallc/mop | 71504552f5770bca2b87ad06d84e7d1f63b23f4c | [
"Apache-2.0"
] | 233 | 2020-09-28T03:39:35.000Z | 2022-03-31T06:11:17.000Z | docs/release-process.md | casuallc/mop | 71504552f5770bca2b87ad06d84e7d1f63b23f4c | [
"Apache-2.0"
] | 32 | 2020-09-29T08:10:32.000Z | 2022-03-24T15:06:47.000Z | # Release process
This guide illustrates how to perform a release for mop.
## Making the release
The steps for releasing are as follows:
1. Prepare for a release
2. Create the release branch
3. Update project version and tag
4. Write a release note
5. Move master branch to next version
6. Announce the release
## Steps in detail
1. Prepare for a release
Create a new milestone and move the pull requests that can not
be published in this release to the new milestone.
2. Create the release branch
We are going to create a branch from `master` to `branch-x.y`
where the tag will be generated and where new fixes will be
applied as part of the maintenance for the release. `x.y.z`
is the version of the release.
The branch needs only to be created when creating major releases,
and not for patch releases.
Eg: When creating `v0.1.0` release, will be creating
the branch `branch-0.1`, but for `v0.1.1` we
would keep using the old `branch-0.1`.
In these instructions, I'm referring to an fictitious release `x.y.z`.
Change the release version in the examples accordingly with the real version.
It is recommended to create a fresh clone of the repository to
avoid any local files to interfere in the process:
```shell
$ git clone [email protected]:streamnative/mop.git
$ cd mop
# Create a branch
$ git checkout -b branch-x.y origin/master
# Create a tag
$ git tag -u [email protected] vx.y.z -m 'Release vx.y.z'
```
3. Update project version and tag
In this process the maven version of the project will always be the final one.
```bash
# Bump to the release version
$ ./scripts/set-project-version.sh x.y.z
# Commit
$ git commit -m 'Release x.y.z' -a
# Push both the branch and the tag to Github repo
$ git push origin branch-x.y
$ git push origin vx.y.z
```
4. Publish a release note
Check the milestone in GitHub associated with the release.
In the released item, add the list of the most important changes
that happened in the release and a link to the associated milestone,
with the complete list of all the changes.
Update the release draft at [the release homepage of mop](https://github.com/streamnative/mop/releases)
Then the release draft, binary, and command doc will be published
o that release automatically.
5. Move master branch to next version
We need to move master version to next iteration `X + 1`.
```bash
$ git checkout master
$ ./scripts/set-project-version.sh X.(Y+1).0-SNAPSHOT
$ git commit -m 'Bumped version to 0.Y.0-SNAPSHOT' -a
```
6. Announce the release
After publishing and checking the release, work with Growth team
to announce that a new version of mop is released.
| 26.877551 | 103 | 0.752468 | eng_Latn | 0.999393 |
a6f9d419356ecb3b6684927a352f1e93def9fe8b | 5,448 | md | Markdown | docs/specs/D-kit/Lidar_Based_Auto_Driving/Sensor_Calibration_cn.md | Self-Driving-Car-Algorithms/apollo | 49e3015f7708d39b53af0516f34291a457f90495 | [
"Apache-2.0"
] | 2 | 2020-06-24T20:00:42.000Z | 2020-07-08T08:53:10.000Z | docs/specs/D-kit/Lidar_Based_Auto_Driving/Sensor_Calibration_cn.md | Self-Driving-Car-Algorithms/apollo | 49e3015f7708d39b53af0516f34291a457f90495 | [
"Apache-2.0"
] | null | null | null | docs/specs/D-kit/Lidar_Based_Auto_Driving/Sensor_Calibration_cn.md | Self-Driving-Car-Algorithms/apollo | 49e3015f7708d39b53af0516f34291a457f90495 | [
"Apache-2.0"
] | null | null | null | # 基于激光雷达的封闭园区自动驾驶搭建--感知设备标定
## 前提条件
- 完成了[基于激光雷达的封闭园区自动驾驶搭建--感知设备标定](../Waypoint_Following/Start_Waypoint_Following_cn.md)
- 完成了[基于激光雷达的封闭园区自动驾驶搭建--感知设备集成](Sensor_Integration_cn.md)
## 主要步骤
- Lidar-GNSS标定初始外参测量
- Lidar-GNSS标定数据包录制
- Lidar-GNSS标定数据预处理
- 使用标定云服务生成外参文件
## 修改配置文件
|修改文件名称 | 修改内容 |
|---|---|
| `modules/localization/conf/localization.conf`|`enable_lidar_localization`为`false`|
**注意**：所有传感器标定完成后，如果用户要使用msf定位，则需要再改为`true`。
## Lidar-GNSS标定初始外参测量
### 各传感器坐标系的定义及初始化外参文件的配置
#### 1. IMU、Lidar的坐标系定义如下图所示：
#### 2. Lidar坐标系原点在传感器的位置
Lidar坐标系原点位于Lidar底部向上37.7mm的平面所在的中心点，如下图所示 (注意：下图仅为表示坐标系圆点，坐标系的定义以上图中的定义为准)
#### 3. IMU坐标系原点在传感器的位置
IMU坐标系原点位于IMU的几何中心上(中心点在Z轴方向上的位置为IMU高度的一半，在XY轴上的位置已在IMU上标出，如下图所示)
#### 4. 手动测量Lidar-GNSS的初始化外参文件
这里默认用户按照感知设备集成文档的要求正确安装了传感器，即传感器坐标系的定义与上文中的定义相同，且安装误差满足文档中的要求。
- rotation:在传感器的安装满足感知设备集成文档要求的情况下，用户无需测量该值，可直接使用如下的默认值即可
```
rotation:
w: 0.7071
x: 0.0
y: 0.0
z: 0.7071
```
- translation:用户需要手动测量以IMU坐标系为基坐标系，以Velodyne16坐标系为目标坐标系的位移变换，一个IMU-Velodyne16位移变换的示例如下所示：
```
translation:
x: 0.0
y: 0.38
z: 1.33
```
## Lidar-GNSS标定数据包录制
#### 1. 准备标定所需channel
进行Lidar-GNSS的标定，需要录制包含传感器信息的数据包作为数据输入，所需的`channel`及`channel频率`如下表所示：
| 模块 | Topic名称 | Topic发送频率（Hz） |
| --------- | ---------------------------------------- | ------------- |
| VLP-16 | /apollo/sensor/lidar16/PointCloud2 | 10 |
| Localization | /apollo/localization/pose | 100 |
为获取上述`channel`，需要启动`GPS`、`Localization`、`Velodyne`三个模块，`GPS`、`Localization`模块的启动请参考[定位模块配置](Waypoint_Following--Localization_Configuration_cn.md)文档，Velodyne`模块的启动请参考[激光雷达感知设备集成](Lidar_Based_Auto_Driving--Sensor_Integration_cn.md)文档。
**注意**：在正式开始录制前，务必确保以上channel能正常输出数据。
#### 2. 使用Apollo录制数据包的方法
- 确保相关模块正常启动，想要录制的channel数据能正常输出
- 打开新的终端，并使用如下命令进入docker环境
```
budaoshi@budaoshi:~/apollo$ bash docker/scripts/dev_into.sh
```
- 在上一步新打开的终端中，输入如下命令，开始录制数据包
其中， `-i 60`表示每60秒分割一次数据包，`-m 1000`代表每1000M分割一次数据包，`-a`代表录制所有channel，具体数值用户可自行指定，更多信息可使用`cyber_recorder record -h`命令查看：
- 录制完成后，使用`Ctrl + C`停止录制，在Apollo代码根目录下会生成数据包。
#### 3. 录制数据包
待channel数据正常输出后，可以开始录制数据包。录制期间，需要控制车辆以8字形轨迹缓慢行驶，并使转弯半径尽量小 ，至少包含5圈完整的8字轨迹数据。
**注意**：场地周围需要有静态参照物，如电线杆、建筑物、车辆，避免过多动态障碍物。
## Lidar-GNSS标定数据预处理
该步骤将通过提取工具将record数据包中的点云和定位数据进行预处理，以方便通过云服务进行在线标定。
#### 1. 按照目录结构放置好Lidar-GNSS标定数据包
下载[配置样例目录包](sensor_calibration.zip)并放置于apollo根目录下，其目录结构如下：
本小节重点关注红色框线中的lidar_to_gnss目录，把前面录制的Lidar-GNSS标定数据包放置于`sensor_calibration/lidar_to_gnss/records`目录中。
#### 2. 修改抽取工具配置文件 lidar_to_gnss.config
根据实际情况，修改配置文件`lidar_to_gnss.config`中预处理数据产出目录（output_path）和待处理数据包目录（record_path），参考下图：
**注意**：以上目录需要指定绝对路径。
#### 3. 运行数据抽取工具
**进入docker环境**，执行如下命令：
```
budaoshi@in_dev_docker:/apollo$ cd /apollo/modules/tools/sensor_calibration
budaoshi@in_dev_docker:/apollo/modules/tools/sensor_calibration$ python extract_data.py --config /apollo/sensor_calibration/lidar_to_gnss/lidar_to_gnss.config
```
**注意**：--config参数指定了配置文件路径，必须为绝对路径，用户根据情况自行修改。
等待终端中显示`Data extraction is completed successfully!`的提示代表数据提取成功，提取出的数据被存储到配置文件中指定的`output_path`路径下。运行数据抽取工具后的目录如下图红框所示：
#### 4. 修改云标定配置文件 sample_config.yaml
修改数据抽取工具生成的sample_config.yaml文件。把前面步骤手动测量的Lidar-GNSS标定初始外参信息填入，仅需要填写`translation`字段。修改完之后把`lidar16_to_gnss_calibration`目录准备后续待用。
## 使用标定云服务生成外参文件
#### 1. 准备百度云对象存储BOS服务
在使用云标定服务前，需要准备[百度云对象存储BOS服务](https://cloud.baidu.com/product/bos.html)用于存放标定预处理后的数据。
#### 2. 和Apollo开发套件商务联系开通云标定服务账号
#### 3. 上传预处理后的数据至BOS
在BOS bucket中新建目录sensor_calibration，作为后续云标定服务读取数据的`Input Data Path`，把前面预处理生成的数据拷贝至该目录。目录结构如下：
#### 4. 提交云标定任务
打开Apollo云服务页面，如下图：
在New Job下拉框中选择Sensor Calibration选项，根据实际情况填写Partner ID（请与商务联系）、Access Key（按BOS账号实际情况填写）、Secret Key（按BOS账号实际情况填写）、Input Data Path（在本例中为"sensor_calibration"）、Output Data Path（用户需要在BOS中指定一个目录，用于存储验证标定效果的pcd文件）最后点击Submit Job按钮提交。
#### 5. 获取标定结果验证及标定外参文件
云标定任务完成后，将在注册的邮箱（请与商务联系）中收到一封标定结果邮件。如果标定任务成功，将包含标定外参文件。
**Lidar-GNSS标定结果验证**：
- BOS中用户指定的Output Data Path路径下包含了后缀名为.pcd的点云文件，使用点云查看工具检查pcd文件，如果点云文件中周围障碍物清晰、锐利，边缘整齐表示标定结果准确，否则请重新标定。
- 在ubuntu系统下，可以使用`pcl-tools`工具查看点云文件
```bash
sudo apt-get update
sudo apt-get install pcl-tools
pcl_viewer xxx.pcd
```
**Lidar-GNSS标定外参文件**：
确认邮件得到的外参文件合理后，将邮件发送的外参文件的`rotation`、`translation`的值替换掉`modules/calibration/data/dev_kit/velodyne_params/velodyne16_novatel_extrinsics.yaml`中对应的`rotation`、`translation`值。注意不要修改`frame_id`、不要直接替换文件。 | 28.082474 | 232 | 0.778084 | yue_Hant | 0.551822 |
a6fa23f44c0b95c6e67c5dbffd7f98f98e0b3366 | 2,636 | md | Markdown | README.md | camsys/gtfs-realtime | 1d04f27ec43c694d13a40af36c5b9f90d7794fa5 | [
"MIT"
] | 1 | 2019-05-16T14:00:03.000Z | 2019-05-16T14:00:03.000Z | README.md | camsys/gtfs-realtime | 1d04f27ec43c694d13a40af36c5b9f90d7794fa5 | [
"MIT"
] | null | null | null | README.md | camsys/gtfs-realtime | 1d04f27ec43c694d13a40af36c5b9f90d7794fa5 | [
"MIT"
] | 1 | 2019-09-06T15:06:03.000Z | 2019-09-06T15:06:03.000Z | # gtfs-realtime
[gfts-realtime](https://github.com/rofreg/gtfs-realtime) is a gem to interact with realtime transit data presented in the [GTFS Realtime format](https://developers.google.com/transit/gtfs-realtime/). It was built in order to interact with the RIPTA realtime data API for the public bus system in Providence, RI.
This gem has been forked by Cambridge Systematics and updated to archive realtime transit data rather than just getting the latest feed. It saves the data into a partitioned postgres database.
## Installation
Add to your application's Gemfile:
```ruby
gem 'bulk_data_methods', github: 'AirHelp/bulk_data_methods', branch: 'rails5'
gem 'partitioned', github: 'AirHelp/partitioned', branch: 'rails-5-1'
gem 'gtfs-realtime', path: '../gtfs-realtime'
gem 'crono'
```
Add your feeds:
```ruby
GTFS::Realtime.configure([{name: 'feed_name', trip_updates_feed: 'xxx', vehicle_positions_feed: 'xxx', service_alerts_feed: 'xxx', interval_seconds: '###'}])
```
where you pass to `configure` an array of hashes for all your feeds
* feed_name - some identifier of this feed such as "Subway", "Buses", "Elevators"
* xxx - URL of feed
* interval seconds - how often you ping the URL to pull latest feed data, in seconds
You can re-run `configure` as many times as you want to add new feeds. TODO: currently, you cannot delete feeds.
In your application, run
```ruby
rails g gtfs_realtime:initialize
```
or
```ruby
rails g gtf_realtime:initialize feed_name
```
## Limitations
* Assumes all feeds have a header gtfs_realtime_version of 1.0
* Partitions are not configurable. All realtime tables are partitioned by feed, and a week of data.
## Development
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
## Contributing
Bug reports and pull requests are welcome on GitHub at https://github.com/camsys/gtfs-realtime. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
## License
The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
| 47.071429 | 324 | 0.762898 | eng_Latn | 0.985245 |
a6faee522a905c188ba7b7198a3c181c55665564 | 1,373 | md | Markdown | docs/framework/unmanaged-api/metadata/imetadatatables-getnextblob-method.md | pirluq/docs | 820adc9b585ecb5691957cd2a00906ad56fe826c | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-08-24T01:59:10.000Z | 2021-08-28T11:20:15.000Z | docs/framework/unmanaged-api/metadata/imetadatatables-getnextblob-method.md | pirluq/docs | 820adc9b585ecb5691957cd2a00906ad56fe826c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/metadata/imetadatatables-getnextblob-method.md | pirluq/docs | 820adc9b585ecb5691957cd2a00906ad56fe826c | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-05T18:09:45.000Z | 2020-12-05T05:11:12.000Z | ---
title: "IMetaDataTables::GetNextBlob Method"
ms.date: "03/30/2017"
api_name:
- "IMetaDataTables.GetNextBlob"
api_location:
- "mscoree.dll"
api_type:
- "COM"
f1_keywords:
- "IMetaDataTables::GetNextBlob"
helpviewer_keywords:
- "IMetaDataTables::GetNextBlob method [.NET Framework metadata]"
- "GetNextBlob method [.NET Framework metadata]"
ms.assetid: 017c8ab4-4c09-4754-9935-5b0b49cabecb
topic_type:
- "apiref"
---
# IMetaDataTables::GetNextBlob Method
Gets the index of the next binary large object (BLOB) in the table.
## Syntax
```cpp
HRESULT GetNextBlob (
[in] ULONG ixBlob,
[out] ULONG *pNext
);
```
## Parameters
`ixBlob`
[in] The index, as returned from a column of BLOBs.
`pNext`
[out] A pointer to the index of the next BLOB.
## Requirements
**Platforms:** See [System Requirements](../../../../docs/framework/get-started/system-requirements.md).
**Header:** Cor.h
**Library:** Used as a resource in MsCorEE.dll
**.NET Framework Versions:** [!INCLUDE[net_current_v20plus](../../../../includes/net-current-v20plus-md.md)]
## See also
- [IMetaDataTables Interface](../../../../docs/framework/unmanaged-api/metadata/imetadatatables-interface.md)
- [IMetaDataTables2 Interface](../../../../docs/framework/unmanaged-api/metadata/imetadatatables2-interface.md)
| 26.921569 | 111 | 0.676621 | yue_Hant | 0.584283 |
a6fb381461d3f94777b02e5e11ffacee0ab8a602 | 290 | md | Markdown | README.md | JamesLaverack/hsluv | 0d4b94d1ee9ada47d5fc7fdb92f3548bfa57f9c4 | [
"MIT"
] | 1 | 2021-04-11T16:19:38.000Z | 2021-04-11T16:19:38.000Z | README.md | JamesLaverack/hsluv | 0d4b94d1ee9ada47d5fc7fdb92f3548bfa57f9c4 | [
"MIT"
] | null | null | null | README.md | JamesLaverack/hsluv | 0d4b94d1ee9ada47d5fc7fdb92f3548bfa57f9c4 | [
"MIT"
] | null | null | null | [](https://travis-ci.org/JamesLaverack/hsluv) [](https://clojars.org/hsluv)
# HSLuv
A pure Clojure implementation of [HSLuv](http://www.hsluv.org/).
| 41.428571 | 213 | 0.737931 | yue_Hant | 0.355437 |
a6fbbf510e6156461db3d108a513fbc0fc235552 | 105 | md | Markdown | content/muscle/legs.md | amrushaban/site | a3f00854b90cc1f14d270e399f91e4b356566513 | [
"MIT"
] | 3 | 2019-04-02T09:10:17.000Z | 2019-10-21T04:46:33.000Z | content/muscle/legs.md | amrushaban/site | a3f00854b90cc1f14d270e399f91e4b356566513 | [
"MIT"
] | null | null | null | content/muscle/legs.md | amrushaban/site | a3f00854b90cc1f14d270e399f91e4b356566513 | [
"MIT"
] | 4 | 2017-02-07T17:52:05.000Z | 2020-09-19T07:04:16.000Z | ---
{created: ! '2015-08-25 15:52:15.817377', description: '', template: muscle.html,
title: Legs}
---
| 21 | 81 | 0.619048 | yue_Hant | 0.199046 |
a6fbd209ed2e868a3e368048c0db854884ff7e25 | 242 | md | Markdown | README.md | rDunn28/studybuddy | da46c8e7c3bd641d2b7bb1c83e5e3aad87b55f8c | [
"Apache-2.0"
] | null | null | null | README.md | rDunn28/studybuddy | da46c8e7c3bd641d2b7bb1c83e5e3aad87b55f8c | [
"Apache-2.0"
] | null | null | null | README.md | rDunn28/studybuddy | da46c8e7c3bd641d2b7bb1c83e5e3aad87b55f8c | [
"Apache-2.0"
] | null | null | null | # Study Buddy - Cobra CLI Tutorial
Project based learning, following "How to build an interactive CLI app with Cobra and Promptui | Go tutorial" on Youtube.
https://divrhino.com/articles/build-interactive-cli-app-with-go-cobra-promptui/
| 34.571429 | 123 | 0.77686 | eng_Latn | 0.757096 |
a6fbe122e1d4da4396e8a120ab4ee3a9c4debfb7 | 1,572 | md | Markdown | README.md | jam1garner/another-simple-bytecode | 22912967cc7d8db2ad010b709a02339b72b897f2 | [
"MIT"
] | 3 | 2018-01-02T07:29:35.000Z | 2021-02-18T09:50:07.000Z | README.md | jam1garner/another-simple-bytecode | 22912967cc7d8db2ad010b709a02339b72b897f2 | [
"MIT"
] | null | null | null | README.md | jam1garner/another-simple-bytecode | 22912967cc7d8db2ad010b709a02339b72b897f2 | [
"MIT"
] | null | null | null | # Another Simple Bytecode
A simple bytecode language I designed with an included assembler and virtual machine interpreter.
### Features include:
* 10 32-bit free use registers (r0-r9)
* Ability to input/output characters and numbers to the console as well as print a string to the console
* Most standard operations
* Ability to access memory to store/load variables
#### Requirements:
* Requires python 2 for assembler
* Any C compiler for virtual machine
#### Compiling using GCC:
Command: `gcc virtual_machine.c`
### Available opcodes:
* nop
* load constant (lc)
* load constant upper (lcu)
* load variable (lv)
* store variable (str)
* push to stack (push)
* pop from stack (pop)
* branch if not equal (bin)
* branch if less than (bil)
* branch if equal (bie)
* branch if greater (big)
* branch without condition (b)
* compare (cmp)
* syscall (sys)
* increment counter (inc)
* decrement counter (dec)
* copy register (copy)
* swap register (swap)
* add (add)
* subtract (sub)
* multiply (mult)
* divide (div)
* modulus (mod)
* or (or)
* and (and)
* xor (xor)
* not (not)
* left shift (ls)
* right shift (rs)
### Available registers:
* r0-r9
* acc
* br (branch conditional is stored here, cmp has less than = -1, greater than = 1, equal to = 0)
* c (counter)
* ss (stack start)
* se (stack end)
### Available syscalls:
* 0 - pop value and output it to console
* 1 - pop char and output it to console
* 2 - input value from console and push it
* 3 - input char from console and push it
* 4 - print string from stack
| 15.115385 | 104 | 0.681934 | eng_Latn | 0.992685 |
a6fc2fb296fb8fd44498704597d4c4b6480350ad | 546 | md | Markdown | _posts/2021-03-29-抵制H&M后去逛商场,看国内和国外品牌店人流对比,盘点熟悉的那些“洋品牌”(小叔TV EP130).md | NodeBE4/society | 20d6bc69f2b0f25d6cc48a361483263ad27f2eb4 | [
"MIT"
] | 1 | 2020-09-16T02:05:28.000Z | 2020-09-16T02:05:28.000Z | _posts/2021-03-29-抵制H&M后去逛商场,看国内和国外品牌店人流对比,盘点熟悉的那些“洋品牌”(小叔TV EP130).md | NodeBE4/society | 20d6bc69f2b0f25d6cc48a361483263ad27f2eb4 | [
"MIT"
] | null | null | null | _posts/2021-03-29-抵制H&M后去逛商场,看国内和国外品牌店人流对比,盘点熟悉的那些“洋品牌”(小叔TV EP130).md | NodeBE4/society | 20d6bc69f2b0f25d6cc48a361483263ad27f2eb4 | [
"MIT"
] | null | null | null | ---
layout: post
title: "抵制H&M后去逛商场,看国内和国外品牌店人流对比,盘点熟悉的那些“洋品牌”(小叔TV EP130)"
date: 2021-03-29T08:22:47.000Z
author: 小叔TV
from: https://www.youtube.com/watch?v=aYxX-dyyD-Q
tags: [ 小叔TV ]
categories: [ 小叔TV ]
---
<!--1617006167000-->
[抵制H&M后去逛商场,看国内和国外品牌店人流对比,盘点熟悉的那些“洋品牌”(小叔TV EP130)](https://www.youtube.com/watch?v=aYxX-dyyD-Q)
------
<div>
因禁用新疆产棉花H&M、耐克、阿迪达斯等被大家抵制，我没事去北京顺义金街的商场逛逛，看到了H&M，、优衣库、Nike、Adidas、匡威，还有李宁、回力等品牌店，感受不同的人流，有的冷冷清清，有的则门庭若市。最后盘点一下熟悉的那些"洋品牌“，其实很多都是国产，你是否真的意识到了？(本人不授权任何人引用视频片段哦)支持我的方式可以请我喝杯咖啡：http://paypal.me/beitong
</div>
| 32.117647 | 196 | 0.745421 | yue_Hant | 0.512341 |
a6fc442a67cfc3d2d0fe4399ccde58ed4cb81889 | 74 | md | Markdown | JSON-data-search.md | zcattacz/alasql_wiki | 20bdc49c075aa951a08a163902f132052f682996 | [
"MIT"
] | 1 | 2021-08-31T14:07:50.000Z | 2021-08-31T14:07:50.000Z | JSON-data-search.md | zcattacz/alasql_wiki | 20bdc49c075aa951a08a163902f132052f682996 | [
"MIT"
] | 2 | 2020-06-11T23:29:28.000Z | 2020-09-08T23:28:43.000Z | JSON-data-search.md | zcattacz/alasql_wiki | 20bdc49c075aa951a08a163902f132052f682996 | [
"MIT"
] | null | null | null | # JSON data search
Please see [`JSON`](json) and [`SEARCH`](Search) pages | 24.666667 | 54 | 0.689189 | eng_Latn | 0.547342 |
a6ff2f3c4a7f0ad029e6d64816ce676cf3be292a | 679 | md | Markdown | CHANGELOG.md | morpheus-org/morpheus-interoperability | 66161199fa1926914e16c1feb02eb910ffef5ed4 | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | morpheus-org/morpheus-interoperability | 66161199fa1926914e16c1feb02eb910ffef5ed4 | [
"Apache-2.0"
] | 3 | 2021-10-09T16:17:19.000Z | 2021-10-12T21:31:23.000Z | CHANGELOG.md | morpheus-org/morpheus-fortran-interop | 66161199fa1926914e16c1feb02eb910ffef5ed4 | [
"Apache-2.0"
] | null | null | null | # Changelog
## Current - Version 0.1.0
- C interface for `CooMatrix`, `CsrMatrix`, `DiaMatrix`,`DenseMatrix` and `DenseVector` containers.
- Currently it is assumed that containers hold *double* value types, *int* index types and are stored on *host* with *row-major* layout.
- `print`, `multiply`, `dot`, `waxpy`, `reduce` and `scan` algorithms used by the above containers enalbed in C.
- Enabled interface for `DynamicMatrix` for format switching. Shallow constructors and assignments from concrete formats are supported.
- Algorithms for concrete matrix containers are supported by dynamic interface too.
- Enabled `convert` interface for concrete and dynamic containers. | 75.444444 | 139 | 0.765832 | eng_Latn | 0.992673 |
a6ff5553fdc07ef73aac1db4fdb5eeb1fb9811bd | 3,711 | md | Markdown | docs/code-quality/ca2120.md | MicrosoftDocs/visualstudio-docs.cs-cz | 3861d52726f1a515cfa62d590513a3c7a1b8019b | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-20T07:48:22.000Z | 2020-05-20T07:48:22.000Z | docs/code-quality/ca2120.md | MicrosoftDocs/visualstudio-docs.cs-cz | 3861d52726f1a515cfa62d590513a3c7a1b8019b | [
"CC-BY-4.0",
"MIT"
] | 7 | 2018-10-02T15:01:11.000Z | 2021-11-05T20:25:20.000Z | docs/code-quality/ca2120.md | MicrosoftDocs/visualstudio-docs.cs-cz | 3861d52726f1a515cfa62d590513a3c7a1b8019b | [
"CC-BY-4.0",
"MIT"
] | 7 | 2018-10-01T22:49:53.000Z | 2021-10-09T11:24:44.000Z | ---
title: 'CA2120: Zabezpečte serializační konstruktory'
description: Typ implementuje rozhraní System. Runtime. Serialization. ISerializable, není delegát ani rozhraní a je deklarován v sestavení, které umožňuje částečně důvěryhodné volající.
ms.date: 11/04/2016
ms.topic: reference
f1_keywords:
- CA2120
- SecureSerializationConstructors
helpviewer_keywords:
- SecureSerializationConstructors
- CA2120
ms.assetid: e9989da1-55a0-43f8-9aa9-da86afae3b41
author: mikejo5000
ms.author: mikejo
manager: jmartens
ms.technology: vs-ide-code-analysis
ms.workload:
- multiple
ms.openlocfilehash: 41ddbe0ec3675bdf2950414c6f1d3fdd3d3b0d67
ms.sourcegitcommit: b12a38744db371d2894769ecf305585f9577792f
ms.translationtype: MT
ms.contentlocale: cs-CZ
ms.lasthandoff: 09/13/2021
ms.locfileid: "126621703"
---
# <a name="ca2120-secure-serialization-constructors"></a>CA2120: Zabezpečte serializační konstruktory
|Položka|Hodnota|
|-|-|
|RuleId|CA2120|
|Kategorie|Microsoft.Security|
|Zásadní změna|Narušující|
## <a name="cause"></a>Příčina
Typ implementuje <xref:System.Runtime.Serialization.ISerializable?displayProperty=fullName> rozhraní, není delegát ani rozhraní a je deklarován v sestavení, které umožňuje částečně důvěryhodné volající. Typ má konstruktor, který přebírá <xref:System.Runtime.Serialization.SerializationInfo?displayProperty=fullName> objekt a <xref:System.Runtime.Serialization.StreamingContext?displayProperty=fullName> objekt (signatura konstruktoru serializace). Tento konstruktor není zabezpečen kontrolou zabezpečení, ale jeden nebo více regulárních konstruktorů v typu je zabezpečeno.
> [!NOTE]
> Toto pravidlo je zastaralé. Další informace najdete v tématu [zastaralá pravidla](fxcop-unported-deprecated-rules.md).
## <a name="rule-description"></a>Popis pravidla
Toto pravidlo je relevantní pro typy, které podporují vlastní serializaci. Typ podporuje vlastní serializaci, pokud implementuje <xref:System.Runtime.Serialization.ISerializable?displayProperty=fullName> rozhraní. Konstruktor serializace je vyžadován a používá se k deserializaci nebo opětovnému vytvoření objektů, které byly serializovány pomocí <xref:System.Runtime.Serialization.ISerializable.GetObjectData%2A?displayProperty=fullName> metody. Vzhledem k tomu, že konstruktor serializace přiděluje a inicializuje objekty, kontroly zabezpečení, které jsou přítomny u regulárních konstruktorů, musí být také přítomny v konstruktoru serializace. Pokud toto pravidlo porušíte, volající, které by jinak nebylo možné vytvořit instanci, by k tomu mohli použít konstruktor serializace.
## <a name="how-to-fix-violations"></a>Jak opravit porušení
Chcete-li opravit porušení tohoto pravidla, zajistěte ochranu konstruktoru serializace pomocí požadavků na zabezpečení, které jsou stejné jako při ochraně jiných konstruktorů.
## <a name="when-to-suppress-warnings"></a>Kdy potlačit upozornění
Potlačit porušení pravidla
## <a name="example"></a>Příklad
Následující příklad ukazuje typ, který je v rozporu s pravidlem.
:::code language="csharp" source="../snippets/csharp/VS_Snippets_CodeAnalysis/FxCop.Security.SerialCtors/cs/FxCop.Security.SerialCtors.cs" id="Snippet1":::
## <a name="related-rules"></a>Související pravidla
[CA2229: Implementujte serializační konstruktory](/dotnet/fundamentals/code-analysis/quality-rules/ca2229)
[CA2237: Označte typy ISerializable pomocí SerializableAttribute](/dotnet/fundamentals/code-analysis/quality-rules/ca2237)
## <a name="see-also"></a>Viz také
- <xref:System.Runtime.Serialization.ISerializable?displayProperty=fullName>
- <xref:System.Runtime.Serialization.SerializationInfo?displayProperty=fullName>
- <xref:System.Runtime.Serialization.StreamingContext?displayProperty=fullName>
| 57.984375 | 780 | 0.823228 | ces_Latn | 0.993272 |
47001fc4bcf298b3e7b5ac617c5bfa258131e546 | 2,489 | md | Markdown | articles/active-directory/privileged-identity-management/pim-roles.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/privileged-identity-management/pim-roles.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/privileged-identity-management/pim-roles.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Privileged Identity Management で管理できないロール - Azure Active Directory | Microsoft Docs
description: Azure AD Privileged Identity Management (PIM) で管理できないロールについて説明します。
services: active-directory
documentationcenter: ''
author: curtand
manager: KarenH444
editor: ''
ms.service: active-directory
ms.topic: conceptual
ms.workload: identity
ms.subservice: pim
ms.date: 10/07/2021
ms.author: curtand
ms.reviewer: shaunliu
ms.custom: pim ; H1Hack27Feb2017;oldportal;it-pro;
ms.collection: M365-identity-device-management
ms.openlocfilehash: 89cd7e3cfac71e194d8f32ae8b15c26da7f0615d
ms.sourcegitcommit: 677e8acc9a2e8b842e4aef4472599f9264e989e7
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 11/11/2021
ms.locfileid: "132336470"
---
# <a name="roles-you-cant-manage-in-privileged-identity-management"></a>Privileged Identity Management で管理できないロール
Azure Active Directory (Azure AD) Privileged Identity Management (PIM) を使用すると、すべての [Azure AD ロール](../roles/permissions-reference.md)とすべての [Azure ロール](../../role-based-access-control/built-in-roles.md)を管理できます。 Azure ロールには、管理グループ、サブスクリプション、リソース グループ、およびリソースに関連付けられているカスタム ロールも含めることができます。 ただし、管理できないロールがいくつかあります。 この記事では、Privileged Identity Management で管理できないロールについて説明します。
## <a name="classic-subscription-administrator-roles"></a>従来のサブスクリプション管理者ロール
Privileged Identity Management では、次の従来のサブスクリプション管理者ロールを管理することはできません。
- アカウント管理者
- サービス管理者
- 共同管理者
従来のサブスクリプション管理者ロールの詳細については、[従来のサブスクリプション管理者ロール、Azure ロール、および Azure AD 管理者ロール](../../role-based-access-control/rbac-and-directory-admin-roles.md)に関する記事を参照してください。
## <a name="what-about-microsoft-365-admin-roles"></a>Microsoft 365 管理者ロールについて
Exchange 管理者や SharePoint 管理者など、Azure AD ロールと管理者ポータルのエクスペリエンスでは、すべての Microsoft 365 のロールがサポートされていますが、Exchange RBAC および SharePoint RBAC 内の特定のロールはサポートされていません。 これらの Microsoft 365 サービスの詳細については、[Microsoft 365 の管理者ロール](/office365/admin/add-users/about-admin-roles)に関するページをご覧ください。
> [!NOTE]
> - SharePoint 管理者ロール、デバイス管理者ロール、および Microsoft セキュリティ センターとコンプライアンス センターにアクセスしようとしているすべてのロールの対象ユーザーは、ロールをアクティブ化した後、最大で数時間の遅延に遭遇する可能性があります。 これらのチームと協力して問題の解決に取り組んでいます。
> - Azure AD 参加済みデバイスのローカル管理者ロールのアクティブ化遅延について詳しくは、「[Azure AD 参加済みデバイスのローカル管理者グループの管理方法](../devices/assign-local-admin.md#manage-the-device-administrator-role)」をご覧ください。
## <a name="next-steps"></a>次のステップ
- [Privileged Identity Management で Azure AD ロールを割り当てる](pim-how-to-add-role-to-user.md)
- [Privileged Identity Management で Azure リソース ロールを割り当てる](pim-resource-roles-assign-roles.md) | 49.78 | 368 | 0.819204 | yue_Hant | 0.686352 |
47002d8b30f771200902343ecaac2511ce8df527 | 451 | md | Markdown | .github/ISSUE_TEMPLATE/new_cam_offset.md | Asu4ni/CitiesSkylines-FPSCamera | fe3b884f1e476f917d4ebafdc471b5bc7bf326c1 | [
"MIT"
] | 2 | 2022-03-02T22:50:49.000Z | 2022-03-05T18:11:03.000Z | .github/ISSUE_TEMPLATE/new_cam_offset.md | Asu4ni/CitiesSkylines-FPSCamera | fe3b884f1e476f917d4ebafdc471b5bc7bf326c1 | [
"MIT"
] | 12 | 2022-03-03T04:43:16.000Z | 2022-03-29T05:10:47.000Z | .github/ISSUE_TEMPLATE/new_cam_offset.md | Asu4ni/CitiesSkylines-FPSCamera | fe3b884f1e476f917d4ebafdc471b5bc7bf326c1 | [
"MIT"
] | null | null | null | ---
name: Suggest default camera settings
about: Offer missing or better default camera position offsets & angles for some followed targets
title: 'Default camera settings for ...'
labels: enhancement
assignees: ''
---
## Setting Entries
The settings from `FPSCameraOffset.xml`:
```
<_Bus>2.55,0.42,0,0,0</_Bus>
<_Biofuel_032Bus_03201>2.1,0.2,0,0,0</_Biofuel_032Bus_03201>
...
```
## Explanation
Reasons or some information you'd like to offer ...
| 22.55 | 97 | 0.733925 | eng_Latn | 0.925697 |
47003b2f0b0c3a9e99cd69f3b29dac0c0a28d282 | 3,842 | md | Markdown | README.md | cclauss/discovery-artifact-manager | 9eb6bcef290ef87006758349c725d440fbfc85d6 | [
"Apache-2.0"
] | null | null | null | README.md | cclauss/discovery-artifact-manager | 9eb6bcef290ef87006758349c725d440fbfc85d6 | [
"Apache-2.0"
] | null | null | null | README.md | cclauss/discovery-artifact-manager | 9eb6bcef290ef87006758349c725d440fbfc85d6 | [
"Apache-2.0"
] | null | null | null | # Introduction
The Discovery Artifact Manager is intended to facilitate testing, publishing, and synchronization of generators and artifacts for client libraries and generated code samples of Google APIs defined by the API Discovery Service.
This repo includes copies of the following in separate top-level directories:
- Discovery files from the [API Discovery Service](https://developers.google.com/discovery/)
- the Google API client library generator (used to generate Java and PHP client libraries)
- some of the [Discovery-based Google API client libraries](https://developers.google.com/discovery/libraries), along with their generators
- the code generation [toolkit](https://github.com/googleapis/toolkit/) used to generate code samples for client libraries.
**NOTE**: This repo only contains a cache of the above items; it is not their source of truth. Changes to Toolkit and Discovery-based Google API client libraries should be directed to their respective repos. There is no guarantee that sources or Discovery files in this repo are up to date.
## Local machine setup
Install [git-subrepo](https://github.com/ingydotnet/git-subrepo) on your local machine.
## Adding a new client library repo
Use the `git subrepo clone` command, from the root directory of this repository. The NodeJS library, for example, is installed using:
``` shell
git subrepo clone https://github.com/google/google-api-nodejs-client.git clients/nodejs/google-api-nodejs-client
```
## Modifying a client library repo
To make changes to a repo, use the `git subrepo pull` and `git subrepo push` commands. The former will merge your local client with fetched upstream changes, and the latter will actually do the push to the upstream sub-repo. For example, to push the PHP client library:
``` shell
git subrepo pull clients/php/google-api-php-client-services
git subrepo push clients/php/google-api-php-client-services
```
During the course of your local work, you may find yourself deciding to reset your HEAD locally. If you do this after a subrepo push, trying to reset your HEAD to before the push, then this can cause some complications: you would not want `github subrepo` to subsequently pull again, as it normally does when pushing (since that will merge the upstream changes you pushed earlier). Instead, you can force-push your changes by using `git subrepo push --force`. We're still learning the quirks of `git subrepo`, but a good rule of thumb is to be extremely careful when manipulating references that have already been synced (push or pull) with the external subrepo locations.
After you push your subrepo, you should also push `discovery-artifact-manager` to your review branch.
## Pushing changes for review
When you make a change to code that lives in `discovery-artifact-manager`, either directly or via subrepos, you should stage your code to your own Github review branch and then create a Pull Request from there to the Github `master` branch.
1. Create a review branch on Github. We'll refer to the name of the branch as `${REVIEW_BRANCH}`.
1. Decide what local branch you'll push. Often, this will be master. We'll refer to this branch as `${LOCAL_BRANCH}`
1. From your local machine, push to the review branch:
```
git push origin ${LOCAL_BRANCH}:${REVIEW_BRANCH}
```
1. On Github, issue a Pull Request against the `master` branch.
## Updating local Discovery doc cache
To aid hermetic testing of client libraries and samples (avoiding synchronization issues), the `discoveries` directory hosts a local cache of Discovery docs from the Discovery service. This cache may be updated from current live versions by running
``` shell
./src/main/updatedisco/updatedisco
```
from any subdirectory. **This cache is not yet used for testing by other tools.**
## Running tests
```bash
cd toolkit
./gradlew test
```
| 54.885714 | 672 | 0.782145 | eng_Latn | 0.994812 |
47008e3cdbf1b15d77179a43df8be02e98521000 | 9,161 | md | Markdown | _posts/2021-5-18-NLP-Projects.md | polzinben/polzinben.github.io | 84c0f6eab9aaba37718833723052549ac9d188f2 | [
"MIT"
] | null | null | null | _posts/2021-5-18-NLP-Projects.md | polzinben/polzinben.github.io | 84c0f6eab9aaba37718833723052549ac9d188f2 | [
"MIT"
] | null | null | null | _posts/2021-5-18-NLP-Projects.md | polzinben/polzinben.github.io | 84c0f6eab9aaba37718833723052549ac9d188f2 | [
"MIT"
] | null | null | null | ---
layout: post
title: TensorFlow Natural Language Processing (NLP) Project (6-min read)
comments: true
---
By now you may be pretty familiar with my story so I will skip ahead to the good stuff, with just a brief refresher that I am now preparing for the <a href="https://www.tensorflow.org/certificate" target="_blank">TensorFlow Developer Certificate</a> and really falling in love with deep learning. It has many useful applications, and one in particular is Natural Language Processing. When you combine computer vision, NLP and voice recognition, artificial intelligence is really starting to feel like the sci-fi movies that inspired us as kids. I also have a video overview on my YouTube channel <a href="https://youtu.be/v4C6G5TCfno" target="_blank">Part 1 (introduction)</a>, <a href="https://youtu.be/Ub_DpG9lZoQ" target="_blank">Part 2 (optimization, predictions, and ocr)</a>.
This project explored the fundamentals of NLP using the great IMDB reviews dataset. It is another very popular dataset in machine learning research and contains 50,000 reviews labeled as positive or negative to be used for training and testing as well as an additional 50,000 unlabeled reviews to be used for predictions if desired (I did not use them at this time). Below is a simple graphic outlying the basic NLP workflow.
<p align="center">
<img src="../images/nlp.jpeg" id="dnlp" alt="NLP Workflow">
</p>
Choosing the right model for the job is one of the fun challenges of data science. Natural language processing can be very challenging because of the nuance of the english language. Some words have multiple meanings, and context matters greatly. The placement of words within a sentence defines their meaning.
To build a model that can recognize this contextual meaning of our words we will use what is called a Recurrent Neural Network. An RNN is able to pass information learned through to the model, allowing it to learn the sequences and contexts of the words within the sentences. This is much more powerful for NLP than a traditional deep learning network. The image below is an example of an effective NLP deep learning network, showing how information is passed both directions. This is what gives the model the power to learn the nuances of the sentences.
<p align="center">
<img src="../images/lstm.png" id="lstm" alt="LSTM Example">
</p>
Bear with me on the acronyms for a moment. To begin, we will use a Gated Recurrent Unit, or GRU. This is actually a streamlined version of the Long Short-Term Momry algorithm, more commonly referred to as an LSTM and is shown in the image above. Because it is slightly watered-down so to speak, it should perform a bit faster on the dataset but may not achieve as high of accuracy. Let's take a look at the two and compare.
<p align="center">
<img src="../images/lstm_gru.jpg" id="lstm_gru" alt="LSTM and GRU Model Summary">
</p>
Okay let's take a look and compare these two basic models for our baseline shown above. If you just looked at the accuracy ~81% would seem pretty decent, but the diverging loss function and clear overfitting show room for improvement. It is also always important to consider how our model performance compares to that of an expert level human. In this case, someone very familiar with movie reviews would likely achieve a much higher accuracy than 81%, so we know we can do a lot better. Comparing the two models, the more streamlined GRU model was slightly more efficient with the shorter runtime. Interestingly, the accuracy performance is almost the same. This is not always the case, but with our very simple model and relatively straightforward input sequences the GRU was quite effective.
With much larger, more complex problems it is very common that you will need to make a decision between performance and efficiency. There is no "silver bullet" to answer the question of which model is "best" for the situation. It always depends on the business case. There are instances where efficiency will be optimized and you simply need to satisfy a given accuracy threshold, and vice versa. Certain architectures will apply more favorably to specific situations but not others.
Although the GRU model would be preferable between the two, before we get too far into the weeds let's step back and think about optimization as a concept in terms of NLP.
More specifically, I like to try to use a **data centric** approach to optimization whenever possible compared to a **model centric** approach.
## Data Centric Development ##
Think of it this way, there are two fundamentally separate ways to optimize your overall performance. You can fine-tune the parameters and layers of your algorithm, or you can go get more and better data! And of course most often a combination of both is key.
In the NLP space, when you consider how many words there are in the English language and the intricate semantics, you would want to train on as large of a corpus (collection of text data) as possible. And that is a perfect seqway into the next phase of this project, **Transfer Learning**.
# Transfer Learning with BERT #
We will be utilizing the **Bidirectional Encoder Representations from Transformers**, better known as our good friend **BERT**. This will give an excellent opportunity to utilize **Transfer Learning**, a very powerful technique used in deep learning to fast track progress using previously trained models such as BERT.
BERT is a cutting edge NLP model developed by Jacob Devlin and his team at Google in 2018. The model was trained on English Wikipedia (2,500M words) and BooksCorpus (800M words). As we have come to realize, that type of training would take massive compute power and time. Luckily we can just import the model and run with it! It is worth noting there are two models of BERT, the base model and the large model. We will be using the base model.
## Working with BERT and ktrain ##
BERT is great. A very powerful NLP model pretrained on millions of words and a large variety of contexts make it very effective at deciphering the English language.
However the downside of BERT and other pretrained NLP models is you need to follow very specific preprocessing steps to use the BERT tokenizer on your train and test data.
That is where **ktrain** comes in. ktrain is a keras wrapper used to help build, train, optimize, debug, and deploy deep learning models. ktrain is fully integrated with our good buddy BERT and will make streamline dozens of lines of code into a few easy operations. Let's take a look.
## BERT Results ##
Utilizing the BERT model and retraining on our dataset we were able to achieve an accuracy of 94%! Incredible gains! Now it did come at a steep increase in runtime, going from 12 minutes to nearly 5 hours. This is because the BERT model is significantly more complex than the simple model we defined previously, and we allowed for much longer reviews with max length of 500. Now that we have our model, ktrain makes it easy to predict on new text. With just a couple lines of code we had our predictor up and running, and making successful predictions!
<p align="center">
<img src="../images/predictor.jpg" id="predictor" alt="Final Model - Predictor">
</p>
## Optical Character Recognition with PyTesseract ##
Now one very cool convergence of deep learning technologies is Optical Character Recognition, or OCR. Imagine a world where you had a notebook full handwritten movie reviews (for some reason...) or better yet you had a folder full of movie posters with critics quotes on them. You could read in the images, extract the text from the images, and make the sentiment prediction based on that text. It is actually easier than it sounds thanks to the team at Google and another powerful tool, the Tesseract. It is designed specifically to make OCR more accessible, and it is a great starter kit. Combining the predictor from the BERT model with the pytesseract text extractor, I was able to make a prediction based on this MacGruber poster!
<p align="center">
<img src="../images/macgruber.jpg" id="macgruber" alt="MacGruber Poster">
</p>
This has been really fun. We started by just playing around with different deep learning networks best suited to handle the nuance of the English language and really took off from there, bringing in **transfer learning with BERT and ktrain** as well as **optical character recognition with pytesseract**. Improved a baseline model from 81% to 95% and built a fun interactive function to cap it off. All told the notebook takes about 5 hours to run, once again not bad for a (half) days work!
If you would like to dive into the code please check out the <a href="https://github.com/polzinben/TensorFlow_NLP" target="_blank">GitHub repo.</a>
Resources:
- https://datascience.stackexchange.com/questions/14581/when-to-use-gru-over-lstm
- https://arxiv.org/abs/1810.04805
- https://pypi.org/project/ktrain/
- https://morioh.com/p/12f182398dc4
- https://github.com/lmoroney/dlaicourse/blob/master/TensorFlow%20In%20Practice/Course%203%20-%20NLP/Course%203%20-%20Week%202%20-%20Lesson%203.ipynb
| 111.719512 | 800 | 0.780155 | eng_Latn | 0.999363 |
47009c4dde3984954a715aa95a13525631b90e3f | 15,339 | md | Markdown | articles/data-factory/v1/data-factory-onprem-cassandra-connector.md | ebibibi/azure-docs.ja-jp | ef49e9766dd3dc5a825ea3b19b9c526e2c37faba | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/v1/data-factory-onprem-cassandra-connector.md | ebibibi/azure-docs.ja-jp | ef49e9766dd3dc5a825ea3b19b9c526e2c37faba | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/v1/data-factory-onprem-cassandra-connector.md | ebibibi/azure-docs.ja-jp | ef49e9766dd3dc5a825ea3b19b9c526e2c37faba | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Data Factory を使用して Cassandra からデータを移動する | Microsoft Docs"
description: "Azure Data Factory を使用してオンプレミスの Cassandra データベースからデータを移動する方法について説明します。"
services: data-factory
documentationcenter:
author: linda33wj
manager: jhubbard
editor: monicar
ms.assetid: 085cc312-42ca-4f43-aa35-535b35a102d5
ms.service: data-factory
ms.workload: data-services
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: article
ms.date: 01/10/2018
ms.author: jingwang
robots: noindex
ms.openlocfilehash: c8f61cb165b0bfffe2f42b060cdbd666fff3a8b3
ms.sourcegitcommit: 9cc3d9b9c36e4c973dd9c9028361af1ec5d29910
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 01/23/2018
---
# <a name="move-data-from-an-on-premises-cassandra-database-using-azure-data-factory"></a>Azure Data Factory を使用してオンプレミスの Cassandra データベースからデータを移動する
> [!div class="op_single_selector" title1="Select the version of Data Factory service you are using:"]
> * [バージョン 1 - 一般公開](data-factory-onprem-cassandra-connector.md)
> * [バージョン 2 - プレビュー](../connector-cassandra.md)
> [!NOTE]
> この記事は、一般公開 (GA) されている Data Factory のバージョン 1 に適用されます。 プレビュー段階にある Data Factory サービスのバージョン 2 を使用している場合は、[V2 での Cassandra コネクタ](../connector-cassandra.md)を参照してください。
この記事では、Azure Data Factory のコピー アクティビティを使って、オンプレミスの Cassandra データベースからデータを移動する方法について説明します。 この記事は、コピー アクティビティによるデータ移動の一般的な概要について説明している、[データ移動アクティビティ](data-factory-data-movement-activities.md)に関する記事に基づいています。
オンプレミスの Cassandra データ ストアから、サポートされている任意のシンク データ ストアにデータをコピーできます。 コピー アクティビティによってシンクとしてサポートされているデータ ストアの一覧については、[サポートされているデータ ストア](data-factory-data-movement-activities.md#supported-data-stores-and-formats)の表をご覧ください。 Data Factory が現在サポートしているのは、Cassandra データ ストアから他のデータ ストアへのデータの移動だけで、他のデータ ストアから Cassandra データ ストアへの移動はサポートしていません。
## <a name="supported-versions"></a>サポートされているバージョン
Cassandra コネクタでは、Cassandra バージョン 2.X がサポートされます。
## <a name="prerequisites"></a>前提条件
Azure Data Factory サービスをオンプレミスの Cassandra データベースに接続できるようにするには、データベースとのリソースの競合を避けるため、データベースをホストするコンピューターと同じコンピューターまたは別のコンピューターに Data Management Gateway をインストールする必要があります。 Data Management Gateway は、安全かつ管理された方法でオンプレミスのデータ ソースをクラウド サービスに接続するコンポーネントです。 Data Management Gateway の詳細については、「 [Data Management Gateway](data-factory-data-management-gateway.md) 」をご覧ください。 データを移動するデータ パイプラインにゲートウェイをセットアップする手順については、[オンプレミスからクラウドへのデータ移動](data-factory-move-data-between-onprem-and-cloud.md)に関する記事をご覧ください。
Cassandra データベースが Azure IaaS VM などのクラウドでホストされている場合でも、データベースへの接続にはゲートウェイを使用する必要があります。 ゲートウェイは、データベースをホストする VM で使用できます。また、そのゲートウェイがデータベースに接続できれば別の VM で使用することもできます。
ゲートウェイをインストールすると、Cassandra データベースへの接続に使用される Microsoft Cassandra ODBC ドライバーが自動的にインストールされます。 したがって、Cassandra データベースからデータをコピーするときに、ドライバーをゲートウェイ コンピューターに手動でインストールする必要はありません。
> [!NOTE]
> 接続/ゲートウェイに関する問題のトラブルシューティングのヒントについては、 [ゲートウェイの問題のトラブルシューティング](data-factory-data-management-gateway.md#troubleshooting-gateway-issues) に関するセクションをご覧ください。
## <a name="getting-started"></a>使用の開始
さまざまなツールまたは API を使用して、オンプレミスの Cassandra データ ストアからデータを移動するコピー アクティビティでパイプラインを作成できます。
- パイプラインを作成する最も簡単な方法は、**コピー ウィザード**を使うことです。 データのコピー ウィザードを使用してパイプラインを作成する簡単な手順については、「 [チュートリアル: コピー ウィザードを使用してパイプラインを作成する](data-factory-copy-data-wizard-tutorial.md) 」をご覧ください。
- 次のツールを使ってパイプラインを作成することもできます。**Azure Portal**、**Visual Studio**、**Azure PowerShell**、**Azure Resource Manager テンプレート**、**.NET API**、**REST API**。 コピー アクティビティを含むパイプラインを作成するための詳細な手順については、[コピー アクティビティのチュートリアル](data-factory-copy-data-from-azure-blob-storage-to-sql-database.md)をご覧ください。
ツールと API のいずれを使用する場合も、次の手順を実行して、ソース データ ストアからシンク データ ストアにデータを移動するパイプラインを作成します。
1. **リンクされたサービス**を作成し、入力データ ストアと出力データ ストアをデータ ファクトリにリンクします。
2. コピー操作用の入力データと出力データを表す**データセット**を作成します。
3. 入力としてのデータセットと出力としてのデータセットを受け取るコピー アクティビティを含む**パイプライン**を作成します。
ウィザードを使用すると、Data Factory エンティティ (リンクされたサービス、データセット、パイプライン) に関する JSON の定義が自動的に作成されます。 (.NET API を除く) ツールまたは API を使う場合は、JSON 形式でこれらの Data Factory エンティティを定義します。 オンプレミスの Cassandra データ ストアからデータをコピーするときに使用する Data Factory エンティティの JSON 定義のサンプルについては、この記事の「[JSON の使用例: Cassandra から Azure BLOB へのデータのコピー](#json-example-copy-data-from-cassandra-to-azure-blob)」を参照してください。
次のセクションでは、Cassandra データ ストアに固有のデータ ファクトリ エンティティの定義に使用される JSON プロパティについて詳しく説明します。
## <a name="linked-service-properties"></a>リンクされたサービスのプロパティ
次の表は、Cassandra のリンクされたサービスに固有の JSON 要素の説明をまとめたものです。
| プロパティ | [説明] | 必須 |
| --- | --- | --- |
| 型 |type プロパティを **OnPremisesCassandra** |[はい] |
| host |Cassandra サーバーの 1 つまたは複数の IP アドレスかホスト名。<br/><br/>IP アドレスまたはホスト名のコンマ区切りのリストを指定して、すべてのサーバーに同時に接続します。 |[はい] |
| ポート |Cassandra サーバーがクライアント接続のリッスンに使用する TCP ポート。 |いいえ、既定値: 9042 |
| authenticationType |Basic、または匿名 |[はい] |
| username |ユーザー アカウントのユーザー名を指定します。 |はい (authenticationType が Basic に設定されている場合)。 |
| password |ユーザー アカウントのパスワードを指定します。 |はい (authenticationType が Basic に設定されている場合)。 |
| gatewayName |オンプレミスの Cassandra データベースへの接続に使用されるゲートウェイの名前。 |[はい] |
| encryptedCredential |ゲートウェイによって暗号化された資格情報。 |いいえ |
## <a name="dataset-properties"></a>データセットのプロパティ
データセットの定義に利用できるセクションとプロパティの完全な一覧については、「[データセットの作成](data-factory-create-datasets.md)」という記事を参照してください。 データセット JSON の構造、可用性、ポリシーなどのセクションは、データセットのすべての型 (Azure SQL、Azure BLOB、Azure テーブルなど) でほぼ同じです。
**typeProperties** セクションはデータセット型ごとに異なり、データ ストアのデータの場所などに関する情報を提供します。 **CassandraTable** 型のデータセットの typeProperties セクションには次のプロパティがあります。
| プロパティ | [説明] | 必須 |
| --- | --- | --- |
| keyspace |Cassandra データベースのkeyspace またはスキーマの名前。 |はい (**CassandraSource** の**クエリ**が定義されていない場合)。 |
| tableName |Cassandra データベースのテーブル名。 |はい (**CassandraSource** の**クエリ**が定義されていない場合)。 |
## <a name="copy-activity-properties"></a>コピー アクティビティのプロパティ
アクティビティの定義に利用できるセクションとプロパティの完全な一覧については、「[パイプラインの作成](data-factory-create-pipelines.md)」という記事を参照してください。 名前、説明、入力テーブル、出力テーブル、ポリシーなどのプロパティは、あらゆる種類のアクティビティで使用できます。
一方、アクティビティの typeProperties セクションで使用できるプロパティは、各アクティビティの種類によって異なります。 コピー アクティビティの場合、ソースとシンクの種類によって異なります。
コピー アクティビティで、source の種類が **CassandraSource**である場合は、typeProperties セクションで次のプロパティを使用できます。
| プロパティ | [説明] | 使用できる値 | 必須 |
| --- | --- | --- | --- |
| クエリ |カスタム クエリを使用してデータを読み取ります。 |SQL-92 クエリまたはCQL クエリ。 「 [CQL reference (CQL リファレンス)](https://docs.datastax.com/en/cql/3.1/cql/cql_reference/cqlReferenceTOC.html)」をご覧ください。 <br/><br/>SQL クエリを使用する場合は、クエリを実行するテーブルを表す **keyspace name.table name** を指定します。 |いいえ (データセットの tableName と keyspace が定義されていない場合)。 |
| consistencyLevel |一貫性レベルは、データがクライアント アプリケーションに返される前に、読み取り要求に応答する必要があるレプリカの数を指定します。 Cassandra は読み取り要求を満たすために、データの指定された数のレプリカを確認します。 |ONE、TWO、THREE、QUORUM、ALL、 LOCAL_QUORUM、EACH_QUORUM、 LOCAL_ONE。 詳細については、「 [Configuring data consistency (データ整合性の構成)](http://docs.datastax.com/en//cassandra/2.0/cassandra/dml/dml_config_consistency_c.html) 」をご覧ください。 |
いいえ。 既定値は ONE です。 |
## <a name="json-example-copy-data-from-cassandra-to-azure-blob"></a>JSON の使用例: Cassandra から Azure BLOB へのデータのコピー
次の例は、[Azure Portal](data-factory-copy-activity-tutorial-using-azure-portal.md)、[Visual Studio](data-factory-copy-activity-tutorial-using-visual-studio.md)、または [Azure PowerShell](data-factory-copy-activity-tutorial-using-powershell.md) を使用してパイプラインを作成する際に使用できるサンプルの JSON 定義です。 ここでは、オンプレミスの Cassandra データベースから Azure Blob Storage にデータをコピーする方法を示します。 ただし、Azure Data Factory のコピー アクティビティを使用して、 [こちら](data-factory-data-movement-activities.md#supported-data-stores-and-formats) に記載されているシンクのいずれかにデータをコピーすることができます。
> [!IMPORTANT]
> このサンプルでは、JSON のスニペットを使用します。 データ ファクトリを作成する手順は含まれてません。 手順については、記事「 [Data Management Gateway を使用してオンプレミスのソースとクラウドの間でデータを移動する](data-factory-move-data-between-onprem-and-cloud.md) 」を参照してください。
このサンプルでは、次の Data Factory のエンティティがあります。
* [OnPremisesCassandra](#linked-service-properties)型のリンクされたサービス。
* [AzureStorage](data-factory-azure-blob-connector.md#linked-service-properties)型のリンクされたサービス。
* [CassandraTable](#dataset-properties) 型の入力[データセット](data-factory-create-datasets.md)。
* [AzureBlob](data-factory-azure-blob-connector.md#dataset-properties) 型の出力[データセット](data-factory-create-datasets.md)。
* [CassandraSource](#copy-activity-properties) と [BlobSink](data-factory-azure-blob-connector.md#copy-activity-properties) を使用するコピー アクティビティを含む [パイプライン](data-factory-create-pipelines.md)。
**Cassandra のリンクされたサービス:**
この例では、 **Cassandra** のリンクされたサービスを使用します。 このリンクされたサービスでサポートされているプロパティについては、 [Cassandra のリンクされたサービス](#linked-service-properties) に関するセクションをご覧ください。
```json
{
"name": "CassandraLinkedService",
"properties":
{
"type": "OnPremisesCassandra",
"typeProperties":
{
"authenticationType": "Basic",
"host": "mycassandraserver",
"port": 9042,
"username": "user",
"password": "password",
"gatewayName": "mygateway"
}
}
}
```
**Azure Storage のリンクされたサービス:**
```json
{
"name": "AzureStorageLinkedService",
"properties": {
"type": "AzureStorage",
"typeProperties": {
"connectionString": "DefaultEndpointsProtocol=https;AccountName=<accountname>;AccountKey=<accountkey>"
}
}
}
```
**Cassandra の入力データセット:**
```json
{
"name": "CassandraInput",
"properties": {
"linkedServiceName": "CassandraLinkedService",
"type": "CassandraTable",
"typeProperties": {
"tableName": "mytable",
"keySpace": "mykeyspace"
},
"availability": {
"frequency": "Hour",
"interval": 1
},
"external": true,
"policy": {
"externalData": {
"retryInterval": "00:01:00",
"retryTimeout": "00:10:00",
"maximumRetry": 3
}
}
}
}
```
**external** を **true** に設定すると、データセットが Data Factory の外部にあり、Data Factory のアクティビティによって生成されたものではないことが Data Factory サービスに通知されます。
**Azure BLOB の出力データセット:**
データは新しい BLOB に 1 時間おきに書き込まれます (頻度: 時間、間隔: 1)。
```json
{
"name": "AzureBlobOutput",
"properties":
{
"type": "AzureBlob",
"linkedServiceName": "AzureStorageLinkedService",
"typeProperties":
{
"folderPath": "adfgetstarted/fromcassandra"
},
"availability":
{
"frequency": "Hour",
"interval": 1
}
}
}
```
**Cassandra ソースおよび BLOB シンクを使用するパイプラインでのコピー アクティビティ:**
パイプラインには、入力データセットと出力データセットを使用するように構成され、1 時間おきに実行するようにスケジュールされているコピー アクティビティが含まれています。 パイプライン JSON 定義で、**source** の型が **CassandraSource** に設定され、**sink** の型が **BlobSink** に設定されています。
RelationalSource でサポートされるプロパティの一覧については、「 [RelationalSource type プロパティ](#copy-activity-properties) 」をご覧ください。
```json
{
"name":"SamplePipeline",
"properties":{
"start":"2016-06-01T18:00:00",
"end":"2016-06-01T19:00:00",
"description":"pipeline with copy activity",
"activities":[
{
"name": "CassandraToAzureBlob",
"description": "Copy from Cassandra to an Azure blob",
"type": "Copy",
"inputs": [
{
"name": "CassandraInput"
}
],
"outputs": [
{
"name": "AzureBlobOutput"
}
],
"typeProperties": {
"source": {
"type": "CassandraSource",
"query": "select id, firstname, lastname from mykeyspace.mytable"
},
"sink": {
"type": "BlobSink"
}
},
"scheduler": {
"frequency": "Hour",
"interval": 1
},
"policy": {
"concurrency": 1,
"executionPriorityOrder": "OldestFirst",
"retry": 0,
"timeout": "01:00:00"
}
}
]
}
}
```
### <a name="type-mapping-for-cassandra"></a>Cassandra の型マッピング
| Cassandra の型 | .Net ベースの型 |
| --- | --- |
| ASCII |String |
| BIGINT |Int64 |
| BLOB |Byte[] |
| BOOLEAN |BOOLEAN |
| DECIMAL |Decimal |
| DOUBLE |DOUBLE |
| FLOAT |Single |
| INET |String |
| INT |Int32 |
| TEXT |String |
| TIMESTAMP |Datetime |
| TIMEUUID |Guid |
| UUID |Guid |
| VARCHAR |String |
| VARINT |DECIMAL |
> [!NOTE]
> コレクションの種類 (マップ、セット、リストなど) については、 [仮想テーブルを使用した Cassandra コレクションの種類の取り扱い](#work-with-collections-using-virtual-table) に関するセクションをご覧ください。
>
> ユーザー定義型はサポートされていません。
>
> バイナリ列と文字列の列の長さは 4000 バイト以内である必要があります。
>
>
## <a name="work-with-collections-using-virtual-table"></a>仮想テーブルを使用したコレクションの取り扱い
Azure Data Factory では、ビルトインの ODBC ドライバーを使用して Cassandra データベースへの接続や、Cassandra データベースからのデータのコピーを行います。 マップ、セット、およびリストを含むコレクションの種類については、ODBC ドライバーが、対応する仮想テーブルへのデータの再正規化を行います。 具体的には、テーブルにコレクション列が含まれている場合に、ドライバーが次の仮想テーブルを生成します。
* 実テーブルと同じデータ (コレクション列を除く) を含む **ベース テーブル**。 ベース テーブルには、それが表す実テーブルと同じ名前が使用されます。
* 入れ子になったデータを展開する、各コレクション列の **仮想テーブル** 。 コレクションを表す仮想テーブルには、実テーブルの名前、区切り文字の "*vt*"、および列の名前を使用して名前が付けられます。
仮想テーブルは、非正規化データへのドライバーのアクセスを有効にして、実テーブルのデータを参照します。 詳細については、「例」セクションを参照してください。 仮想テーブルのクエリや結合により、Cassandra コレクションの内容にアクセスできます。
[コピー ウィザード](data-factory-data-movement-activities.md#create-a-pipeline-with-copy-activity)を使用して、仮想テーブルを含む Cassandra データベースのテーブルの一覧を直感的に表示し、内部データをプレビューすることができます。 また、コピー ウィザードでクエリを構築して検証し、結果を確認することもできます。
### <a name="example"></a>例
たとえば、次の "ExampleTable" は、整数の主キー列 ("pk_int" という名前)、テキスト列 (値という名前)、リスト列、 マップ列、 およびセット列 ("StringSet" という名前) で構成された、Cassandra データベース テーブルです。
| pk_int | 値 | 一覧表示 | マップ | StringSet |
| --- | --- | --- | --- | --- |
| 1 |"サンプル値 1" |["1", "2", "3"] |{"S1": "a", "S2": "b"} |{"A", "B", "C"} |
| 3 |"サンプル値 3" |["100", "101", "102", "105"] |{"S1": "t"} |{"A", "E"} |
ドライバーによって、この単一のテーブルを表す複数の仮想テーブルが生成されます。 仮想テーブルの外部キー列は、実テーブルの主キー列を参照して、仮想テーブルの行が対応する実テーブルの行を示します。
最初の仮想テーブルは、次の表に示す "ExampleTable" という名前のベース テーブルです。 ベース テーブルには、元のデータベース テーブルと同じデータ (コレクションを除く) が含まれています。このテーブルで省略されたコレクションは、他の仮想テーブルで展開されます。
| pk_int | 値 |
| --- | --- |
| 1 |"サンプル値 1" |
| 3 |"サンプル値 3" |
次のテーブルは、リスト、マップ、および StringSet の列からのデータを再正規化した仮想テーブルを表しています。 "_index" や "_key" で終わる名前の列は、元のリストまたはマップ内のデータの位置を示しています。 "_value" で終わる名前の列には、コレクションから展開されたデータが含まれています。
#### <a name="table-exampletablevtlist"></a>テーブル "ExampleTable_vt_List":
| pk_int | List_index | List_value |
| --- | --- | --- |
| 1 |0 |1 |
| 1 |1 |2 |
| 1 |2 |3 |
| 3 |0 |100 |
| 3 |1 |101 |
| 3 |2 |102 |
| 3 |3 |103 |
#### <a name="table-exampletablevtmap"></a>テーブル "ExampleTable_vt_Map":
| pk_int | Map_key | Map_value |
| --- | --- | --- |
| 1 |S1 |A |
| 1 |S2 |b |
| 3 |S1 |t |
#### <a name="table-exampletablevtstringset"></a>テーブル "ExampleTable_vt_StringSet":
| pk_int | StringSet_value |
| --- | --- |
| 1 |A |
| 1 |b |
| 1 |C |
| 3 |A |
| 3 |E |
## <a name="map-source-to-sink-columns"></a>ソース列からシンク列へのマップ
ソース データセット列のシンク データセット列へのマッピングの詳細については、[Azure Data Factory のデータセット列のマッピング](data-factory-map-columns.md)に関するページをご覧ください。
## <a name="repeatable-read-from-relational-sources"></a>リレーショナル ソースからの反復可能読み取り
リレーショナル データ ストアからデータをコピーする場合は、意図しない結果を避けるため、再現性に注意する必要があります。 Azure Data Factory では、スライスを手動で再実行できます。 障害が発生したときにスライスを再実行できるように、データセットの再試行ポリシーを構成することもできます。 いずれかの方法でスライスが再実行された際は、何度スライスが実行されても同じデータが読み込まれることを確認する必要があります。 [リレーショナル ソースからの反復可能読み取り](data-factory-repeatable-copy.md#repeatable-read-from-relational-sources)に関するページをご覧ください。
## <a name="performance-and-tuning"></a>パフォーマンスとチューニング
Azure Data Factory でのデータ移動 (コピー アクティビティ) のパフォーマンスに影響する主な要因と、パフォーマンスを最適化するための各種方法については、「[コピー アクティビティのパフォーマンスとチューニングに関するガイド](data-factory-copy-activity-performance.md)」を参照してください。
| 43.453258 | 503 | 0.713475 | yue_Hant | 0.605665 |
47012d164ab867938315e8ef75ae18e9bb6cdbbc | 16,904 | md | Markdown | content/resources/ui-galleries.md | balsamiqLeon/balsamiq-support-site | 233c0efb71be44284750b8f3e19ae02357abe4e4 | [
"MIT"
] | null | null | null | content/resources/ui-galleries.md | balsamiqLeon/balsamiq-support-site | 233c0efb71be44284750b8f3e19ae02357abe4e4 | [
"MIT"
] | null | null | null | content/resources/ui-galleries.md | balsamiqLeon/balsamiq-support-site | 233c0efb71be44284750b8f3e19ae02357abe4e4 | [
"MIT"
] | null | null | null | ---
date: 2017-03-01T16:27:09-08:00
menu: "menuresources"
draft: ''
product: "Resources"
title: User Interface Galleries
weight: 55
---
Are you looking for **best practices** or inspiration while working on your wireframes? The Design Pattern Libraries and Galleries section below provide examples of how interfaces are used to solve specific kinds of design problems. These sites may include examples of design solutions, and annotated breakdowns describing why the solution is appropriate.
<div class="row">
<div class="col-xs-12 col-sm-10">
<h2 class="mt0">Design Pattern Libraries & UI Galleries</h2>
</div>
<div class="col-xs-12 col-sm-2">
<ul id="filter" class="menubar">
<li class="current"><a href="#" title="All"><span class="icon-devices"></span><span class="label">All</span></a></li>
<li><a href="#" title="Mobile"><span class="icon-mobile"></span><span class="label">Mobile</span></a></li>
<li><a href="#" title="Desktop"><span class="icon-desktop"></span><span class="label">Desktop</span></a></li>
</ul>
</div>
</div>
<div id="filterlist" class="row gallery">
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://appuid.janole.com/"><img src="//media.balsamiq.com/img/support/uigalleries/app-ui-design.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://appuid.janole.com/">App & UI Design</a></h4>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.flickr.com/photos/factoryjoe/collections/72157600001823120/"><img src="//media.balsamiq.com/img/support/uigalleries/factoryjoe-design-patterns.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.flickr.com/photos/factoryjoe/collections/72157600001823120/">Design Patterns</a></h4>
Flickr Collection by Chris Messina
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.amazon.com/gp/product/1449379702"><img src="//media.balsamiq.com/img/support/uigalleries/designing-interfaces.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.amazon.com/gp/product/1449379702">Designing Interfaces: Patterns for Effective Interaction Design</a></h4>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.amazon.com/Designing-Web-Interfaces-Principles-Interactions/dp/0596516258/ref=sr_1_1?s=books&ie=UTF8&qid=1488409488&sr=1-1&keywords=designing+web+interfaces"><img src="//media.balsamiq.com/img/support/uigalleries/designing-web-interfaces.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.amazon.com/Designing-Web-Interfaces-Principles-Interactions/dp/0596516258/ref=sr_1_1?s=books&ie=UTF8&qid=1488409488&sr=1-1&keywords=designing+web+interfaces">Designing Web Interfaces: Principles and Patterns for Rich Interactions</a></h4>
See also: <a href="http://www.flickr.com/photos/designingwebinterfaces/collections/">Flickr collection</a>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://ecommerceuxdesign.com/"><img src="//media.balsamiq.com/img/support/uigalleries/ecommerce-ux-design.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://ecommerceuxdesign.com/">eCommerce UX Design</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.smileycat.com/category/elements-of-design/"><img src="//media.balsamiq.com/img/support/uigalleries/smiley-cat-elements.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.smileycat.com/category/elements-of-design/">Elements of Design on Smiley Cat</a></h4>
</div>
</div>
</div>
<div class="fitem mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://inspired-ui.com/"><img src="//media.balsamiq.com/img/support/uigalleries/inspired-ui.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://inspired-ui.com/">Insipired UI</a></h4>
</div>
</div>
</div>
<div class="fitem mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.iospirations.com/"><img src="//media.balsamiq.com/img/support/uigalleries/iospirations.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.iospirations.com/">iOSpirations</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://littlebigdetails.com/"><img src="//media.balsamiq.com/img/support/uigalleries/littlebigdetails.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://littlebigdetails.com/">Little Big Details</a></h4>
</div>
</div>
</div>
<div class="fitem mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.lovelyui.com/"><img src="//media.balsamiq.com/img/support/uigalleries/lovelyui.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.lovelyui.com/">Lovely UI</a></h4>
</div>
</div>
</div>
<div class="fitem mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.amazon.com/dp/1449336442/ref=cm_sw_su_dp"><img src="//media.balsamiq.com/img/support/uigalleries/mobile-design-pattern-gallery.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.amazon.com/dp/1449336442/ref=cm_sw_su_dp">Mobile Design Pattern Gallery</a></h4>
See also: <a href="https://theresaneil.wordpress.com/category/design-patterns/">Patterns on Book Site</a>
</div>
</div>
</div>
<div class="fitem mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.mobile-patterns.com/"><img src="//media.balsamiq.com/img/support/uigalleries/mobile-ui-patterns.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.mobile-patterns.com/">Mobile UI Patterns</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://patterntap.com/"><img src="//media.balsamiq.com/img/support/uigalleries/patterntap.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://patterntap.com/">Pattern Tap</a></h4>
</div>
</div>
</div>
<div class="fitem mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.uxpin.com/patterns/"><img src="//media.balsamiq.com/img/support/uigalleries/patterns-uxpin.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.uxpin.com/patterns/">Patterns by UXPin</a></h4>
</div>
</div>
</div>
<div class="fitem mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://pttrns.com/"><img src="//media.balsamiq.com/img/support/uigalleries/pttrns.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://pttrns.com/">pttrns</a></h4>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.flickr.com/groups/uipatternfactory/"><img src="//media.balsamiq.com/img/support/uigalleries/patternry.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.flickr.com/groups/uipatternfactory/">Patterny Flickr Collection</a></a></h4>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://searchpatterns.org/library.php"><img src="//media.balsamiq.com/img/support/uigalleries/search-patterns.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://searchpatterns.org/library.php">Search Patterns</a></h4>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.designingsocialinterfaces.com/patterns.wiki/index.php?title=Main_Page"><img src="//media.balsamiq.com/img/support/uigalleries/designing-social-interfaces.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.designingsocialinterfaces.com/patterns.wiki/index.php?title=Main_Page">Social Patterns</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.instagram.com/ui.inspirations/"><img src="//media.balsamiq.com/img/support/uigalleries/ig-uiinspirations.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.instagram.com/ui.inspirations/">ui.inspirations</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.uiparade.com/"><img src="//media.balsamiq.com/img/support/uigalleries/ui-parade.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.uiparade.com/">UI Parade</a></h4>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://ui-patterns.com/patterns"><img src="//media.balsamiq.com/img/support/uigalleries/ui-patterns.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://ui-patterns.com/patterns">UI Patterns</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.instagram.com/uipatterns/"><img src="//media.balsamiq.com/img/support/uigalleries/ig-uipatterns.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.instagram.com/uipatterns/">uipatterns</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.instagram.com/ui__ux/"><img src="//media.balsamiq.com/img/support/uigalleries/ig-uiux.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.instagram.com/ui__ux/">ui__ux</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://uiuxart.tumblr.com/"><img src="//media.balsamiq.com/img/support/uigalleries/uiuxart.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://uiuxart.tumblr.com/">UI/UX Art</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.instagram.com/uiuxgifs/"><img src="//media.balsamiq.com/img/support/uigalleries/ig-uiuxgifs.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.instagram.com/uiuxgifs/">uiuxgifs</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.instagram.com/uiuxdesigns/"><img src="//media.balsamiq.com/img/support/uigalleries/ig-uiuxdesigns.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.instagram.com/uiuxdesigns/">uiuxdesigns</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.useronboard.com/onboarding-teardowns/"><img src="//media.balsamiq.com/img/support/uigalleries/useronboard.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.useronboard.com/onboarding-teardowns/">Useronboard</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.instagram.com/uxpiration/"><img src="//media.balsamiq.com/img/support/uigalleries/ig-uxpiration.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.instagram.com/uxpiration/">uxpiration</a></h4>
</div>
</div>
</div>
<div class="fitem desktop mobile col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://www.instagram.com/uzers.co/"><img src="//media.balsamiq.com/img/support/uigalleries/ig-uzersco.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://www.instagram.com/uzers.co/">uzers.co</a></h4>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.lukew.com/resources/web_form_design.asp"><img src="//media.balsamiq.com/img/support/uigalleries/web-form-design.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.lukew.com/resources/web_form_design.asp">Web Form Design: Filling in the Blanks</a></h4>
See also: <a href="https://www.flickr.com/photos/rosenfeldmedia/sets/72157604272550634/">Flickr collection</a>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="http://www.welie.com/patterns/"><img src="//media.balsamiq.com/img/support/uigalleries/welie.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="http://www.welie.com/patterns/">Welie Interaction Design Pattern Library</a></h4>
</div>
</div>
</div>
<div class="fitem desktop col-xs-12 col-sm-6 col-md-4 col-lg-4">
<div class="gallery-item">
<a href="https://wireframestogo.com"><img src="//media.balsamiq.com/img/support/uigalleries/wtg.jpg" alt="screenshot" /></a>
<div class="meta">
<h4><a href="https://wireframestogo.com">Wireframes To Go</a></h4>
</div>
</div>
</div>
</div>
<hr>
You may also be interested in <a href="/resources/ui-guidelines/">User Interface Guidelines</a>.
<script>
// filters
$('ul#filter a').click(function() {
$(this).css('outline','none');
$('ul#filter .current').removeClass('current');
$(this).parent().addClass('current');
var filterVal = $(this).text().toLowerCase().replace(' ','-');
if(filterVal === 'all') {
$('#filterlist .fitem.hidden').removeClass('hidden');
} else {
$('#filterlist .fitem').each(function() {
if(!$(this).hasClass(filterVal)) {
$(this).addClass('hidden');
} else {
$(this).removeClass('hidden');
}
});
}
return false;
});
</script>
<style>
.gallery-item {
min-height: 360px;
width: 100%;
}
.gallery-item img {
max-height: 180px;
width: auto;
/* padding: 10px; */
}
@media (min-width: 1200px) {
.gallery-item img {
max-height: 300px;
width: 100%;
}
}
.meta h4 {
font-weight: normal;
margin-bottom: 0;
}
</style>
| 50.309524 | 355 | 0.586962 | kor_Hang | 0.084312 |
47013c3a4546a82402b2c22dce33cb0fa78703c5 | 3,492 | md | Markdown | docs/extensibility/debugger/reference/idebugdocumenttextevents2.md | Dragollla16/visualstudio-docs | 53fc727cc744ddd3f4baeb36085deac7d8db7b94 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/debugger/reference/idebugdocumenttextevents2.md | Dragollla16/visualstudio-docs | 53fc727cc744ddd3f4baeb36085deac7d8db7b94 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/debugger/reference/idebugdocumenttextevents2.md | Dragollla16/visualstudio-docs | 53fc727cc744ddd3f4baeb36085deac7d8db7b94 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "IDebugDocumentTextEvents2 | Microsoft Docs"
ms.date: "11/04/2016"
ms.topic: "conceptual"
f1_keywords:
- "IDebugDocumentTextEvents2"
helpviewer_keywords:
- "IDebugDocumentTextEvents2 interface"
ms.assetid: a10cbb6b-11a8-4056-b42a-2ecebf0e690d
author: "gregvanl"
ms.author: "gregvanl"
manager: jillfra
ms.workload:
- "vssdk"
---
# IDebugDocumentTextEvents2
This interface is used to notify Visual Studio about changes to the source document that are supplied by the debug engine.
## Syntax
```
IDebugDocumentTextEvents2 : IUnknown
```
## Notes for Implementers
The DE implements this interface to support making changes to the source code. This interface is typically implemented on the same object that implements the [IDebugDocument2](../../../extensibility/debugger/reference/idebugdocument2.md) interface.
## Notes for Callers
[!INCLUDE[vsprvs](../../../code-quality/includes/vsprvs_md.md)] obtains this interface through a call to the <xref:System.Runtime.InteropServices.ComTypes.IConnectionPoint.Advise%2A> method. The <xref:System.Runtime.InteropServices.ComTypes.IConnectionPoint> interface is obtained from a call to the <xref:System.Runtime.InteropServices.ComTypes.IConnectionPointContainer.EnumConnectionPoints%2A> method. The <xref:System.Runtime.InteropServices.ComTypes.IConnectionPointContainer> interface is obtained by calling the [QueryInterface](/cpp/atl/queryinterface) method on an [IDebugDocument2](../../../extensibility/debugger/reference/idebugdocument2.md) interface.
## Methods in Vtable Order
The following table shows the methods of `IDebugDocumentTextEvents2`.
|Method|Description|
|------------|-----------------|
|[onDestroy](../../../extensibility/debugger/reference/idebugdocumenttextevents2-ondestroy.md)|Indicates that the entire document has been destroyed.|
|[onInsertText](../../../extensibility/debugger/reference/idebugdocumenttextevents2-oninserttext.md)|Notifies the debug package that text has been inserted into the document.|
|[onRemoveText](../../../extensibility/debugger/reference/idebugdocumenttextevents2-onremovetext.md)|Notifies the debug package that text has been removed from the document.|
|[onReplaceText](../../../extensibility/debugger/reference/idebugdocumenttextevents2-onreplacetext.md)|Notifies the debug package that text has been replaced in the document.|
|[onUpdateTextAttributes](../../../extensibility/debugger/reference/idebugdocumenttextevents2-onupdatetextattributes.md)|Notifies the debug package that text attributes have been updated in the document.|
|[onUpdateDocumentAttributes](../../../extensibility/debugger/reference/idebugdocumenttextevents2-onupdatedocumentattributes.md)|Notifies receiver of the event that the document attributes have been updated.|
## Remarks
Only debug engines that supply their own documents would take advantage of the `IDebugDocumentTextEvent2` interface. An example of this would be a scripting debug engine. In the process of interpreting scripts, new source code can be generated that is not present in any disk file and is known only to the DE.
## Requirements
Header: msdbg.h
Namespace: Microsoft.VisualStudio.Debugger.Interop
Assembly: Microsoft.VisualStudio.Debugger.Interop.dll
## See Also
[IDebugDocumentText2](../../../extensibility/debugger/reference/idebugdocumenttext2.md)
[IDebugDocument2](../../../extensibility/debugger/reference/idebugdocument2.md) | 63.490909 | 667 | 0.777778 | eng_Latn | 0.649028 |
4701772129aa9b660c85385e8b14cf59fcf79887 | 218 | md | Markdown | _watches/M20190825_044157_TLP_7.md | Meteoros-Floripa/meteoros.floripa.br | 7d296fb8d630a4e5fec9ab1a3fb6050420fc0dad | [
"MIT"
] | 5 | 2020-01-22T17:44:06.000Z | 2020-01-26T17:57:58.000Z | _watches/M20190825_044157_TLP_7.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | null | null | null | _watches/M20190825_044157_TLP_7.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | 2 | 2020-05-19T17:06:27.000Z | 2020-09-04T00:00:43.000Z | ---
layout: watch
title: TLP7 - 25/08/2019 - M20190825_044157_TLP_7T.jpg
date: 2019-08-25 04:41:57
permalink: /2019/08/25/watch/M20190825_044157_TLP_7
capture: TLP7/2019/201908/20190824/M20190825_044157_TLP_7T.jpg
---
| 27.25 | 62 | 0.784404 | yue_Hant | 0.055628 |
4701a185c21f745380d426fd5847b462be681e68 | 4,435 | md | Markdown | README.md | jimmyland/voro | 6a8cc0a5bb215300adfcabab4f52239093398b9a | [
"MIT"
] | 12 | 2017-10-10T23:53:02.000Z | 2021-06-17T11:28:16.000Z | README.md | jimmyland/voro | 6a8cc0a5bb215300adfcabab4f52239093398b9a | [
"MIT"
] | 3 | 2017-07-23T21:08:34.000Z | 2019-02-22T22:38:50.000Z | README.md | jimmyland/voro-experiment | 6a8cc0a5bb215300adfcabab4f52239093398b9a | [
"MIT"
] | 2 | 2017-10-11T03:22:16.000Z | 2019-07-01T18:54:56.000Z | # Voro
## Cellular 3D Modeling using Voronoi Diagrams
Built on top of threejs and voro++ (used in js via emscripten), this is a simple 3D modeling program that lets you make shapes out of voronoi cells. Try it out on the live github pages page ( http://jimmyland.github.io/voro/ ), and click the HELP? link there for more practical usage advice.
Any new code here from me is released under the standard open source MIT license.
# Developer Instructions
So far this has been mostly just one person developing, but help is certainly welcome! I will list some getting started / install instructions below -- please let me know if you try them, and if there are any issues or fixes needed to make them work for you!
## Building and running:
### Compiling the C++ code
Note that the repository includes a pre-compiled `vorowrap.js`, so you can skip compiling the C++ code unless you plan to edit it.
If you do need to edit the C++ code:
1. Acquire Emscripten: http://kripken.github.io/emscripten-site/ (or `brew install emscripten` on Mac if you have homebrew)
2. Run `make`.
### Running the JS code
You basically just need to open index.html in a browser, BUT for the browser to successfully load all the other resource and js files it needs, you'll need to serve that file from a local server instead of opening it directly. What I do is install the super-basic `http-server` and use that to serve index.html on localhost:
1. Install node.js: https://nodejs.org/en/download/ (or `brew install node` on Mac if you have homebrew)
2. Install http-server globally: `npm install http-server -g`
3. cd to the directory where you've downloaded the voro project files, and run `http-server`
4. While the server is running, open `http:127.0.0.1:8080` in your web browser
When developing and testing the code, I like to use Chrome and have the developer tools open, and go to the Network tab of the developer tools and make sure 'Disable cache' is checked. That way, when I edit a javascript file and refresh the browser, it will reliably pick up my changes.
## Code overview:
The core voronoi diagram computation code is all from an academic C++ library called voro++, which lives in the voro++ subdirectory. This code is only minimally changed in this project to allow more efficient editing of an already-constructed diagram -- I added functions to efficiently move and delete cells.
This functionality is exposed to javascript by vorowrap.cpp, which defines a `Voro` class with a suite of helper functions to add, move, and delete voronoi cells. It then exposes buffers of triangles and vertices defining those cells to javascript via the `gl_*` functions (so-called because they expose buffers that webgl could use). The gl_* functions pass buffers back to javascript via the black magic of casting pointers to `uintptr_t`, which javascript can then understand as an array via HEAP functions like `Module.HEAPF32.subarray` -- this is super gross, but as far as I could tell there wasn't actually a non-gross way to get a big buffer of array data back to js, so it is what it is.
Vorowrap is used by voro3.js -- so named because it wraps together correct usage of the C++ Voro class with the lovely webgl 3D library threejs, which is what I use for all the 3D rendering and UI. voro3.js also layers additional higher-level features on top of the basic voronoi diagram functionality: It has features to track and enforce various symmetry modes, and it defines operations in terms of *Act classes (e.g., `AddAct`, `DeleteAct`) that can be tracked and undone/redone, so you can build undo/redo functionality if you want it.
voro3.js is used by main.js -- the code that sets up the 3D scene, the 3D UI interactions, the actual undo queue, etc.
Finally, index.html sets up the window, all the 2D UI that needs html definition, and starts main.js running.
Note that all js dependencies are generally just copied into the js folder, rather than using any kind of package manager. Most of these are just downloaded snapshots of libraries, with no changes. (The main exception is threejs, for which I maintain a monkeypatch to fix up their raycasting, and I also manually copy some of their useful 3D UI code that is not included in the main distribution into js/controls/*)
I include some compiled data (vorowrap.js and associated mem and map files) in the repo just to make http://jimmyland.github.io/voro/ work easily. | 90.510204 | 698 | 0.77407 | eng_Latn | 0.999144 |
4701d19c71b5e97e22c66f930234e8c06400dfad | 4,940 | md | Markdown | docs/relational-databases/replication/administration/enable-coordinated-backups-for-transactional-replication.md | ZubriQ/sql-docs.ru-ru | 50559946dabe5fce9eef251a637dc2e3fd305908 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/replication/administration/enable-coordinated-backups-for-transactional-replication.md | ZubriQ/sql-docs.ru-ru | 50559946dabe5fce9eef251a637dc2e3fd305908 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/replication/administration/enable-coordinated-backups-for-transactional-replication.md | ZubriQ/sql-docs.ru-ru | 50559946dabe5fce9eef251a637dc2e3fd305908 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Включение скоординированного резервного копирования (транзакции)
description: Узнайте, как включить в базе данных распространителя функции скоординированного резервного копирования, при которых журнал транзакций в базе данных публикации репликации транзакций не подвергается усечению до получения резервных копий транзакций, переданных распространителю.
ms.custom: seo-lt-2019
ms.date: 03/07/2017
ms.prod: sql
ms.prod_service: database-engine
ms.reviewer: ''
ms.technology: replication
ms.topic: conceptual
dev_langs:
- TSQL
helpviewer_keywords:
- transactional replication, backup and restore
- sp_replicationdboption
- sync with backup [SQL Server replication]
- coordinated backups [SQL Server replication]
- backups [SQL Server replication], transactional replication
ms.assetid: 73a914ba-8b2d-4f4d-ac1b-db9bac676a30
author: MashaMSFT
ms.author: mathoma
ms.openlocfilehash: 96fa2e96021f0390fcc1cf15eb3aba2fd6b55e42
ms.sourcegitcommit: 58158eda0aa0d7f87f9d958ae349a14c0ba8a209
ms.translationtype: HT
ms.contentlocale: ru-RU
ms.lasthandoff: 03/30/2020
ms.locfileid: "75322059"
---
# <a name="enable-coordinated-backups-for-transactional-replication"></a>Включение скоординированного резервного копирования для репликации транзакций
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
При подготовке базы данных к репликации транзакций можно указать, что перед отправкой в базу данных распространителя со всех транзакций должны быть сняты резервные копии. Кроме того, существует возможность включения в базе данных распространителя функции скоординированного резервного копирования, при которой журнал транзакций в базе данных публикации не подвергается усечению до получения резервных копий транзакций, переданных распространителю. Дополнительные сведения см. в статье [Стратегии резервного копирования и восстановления из копии репликации моментальных снимков и репликации транзакций](../../../relational-databases/replication/administration/strategies-for-backing-up-and-restoring-snapshot-and-transactional-replication.md).
### <a name="to-enable-coordinated-backups-for-a-database-published-with-transactional-replication"></a>Включение функции скоординированного резервного копирования для базы данных, опубликованной с использованием репликации транзакций
1. В издателе с помощью функции[DATABASEPROPERTYEX (Transact-SQL)](../../../t-sql/functions/databasepropertyex-transact-sql.md) получите значение свойства **IsSyncWithBackup** для базы данных издателя. Если функция возвратила значение **1**, то это означает, что скоординированное резервное копирование опубликованной базы данных уже включено.
2. Если функция, выполненная на шаге 1, возвратила значение **0**, выполните хранимую процедуру [sp_replicationdboption (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql.md) в базе данных издателя в издателе. Укажите значение **sync with backup** в параметре **\@optname** и значение **true** в параметре **\@value**.
> [!NOTE]
> Если значение параметра **sync with backup** заменить на **false**, то точка усечения базы данных публикации будет обновлена после запуска агента чтения журнала или по истечении определенного интервала в случае, если агент чтения журнала выполняется постоянно. Максимальное значение интервала управляется параметром агента **–MessageInterval** , значение которого по умолчанию составляет 30 секунд.
### <a name="to-enable-coordinated-backups-for-a-distribution-database"></a>Включение скоординированного резервного копирования базы данных распространителя
1. На распространителе с помощью функции[DATABASEPROPERTYEX (Transact-SQL)](../../../t-sql/functions/databasepropertyex-transact-sql.md) получите значение свойства **IsSyncWithBackup** для базы данных распространителя. Если функция возвратила значение **1**, то это означает, что скоординированное резервное копирование базы данных распространителя уже включено.
2. Если функция, выполненная на шаге 1, возвратила значение **0**, выполните хранимую процедуру [sp_replicationdboption (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql.md) в базе данных распространителя на распространителе. Укажите значение **sync with backup** в параметре **\@optname** и значение **true** в параметре **\@value**.
### <a name="to-disable-coordinated-backups"></a>Отключение скоординированного резервного копирования
1. В издателе в базе данных публикации или в распространителе в базе данных распространителя выполните хранимую процедуру [sp_replicationdboption (Transact-SQL)](../../../relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql.md). Укажите значение **sync with backup** в параметре **\@optname** и значение **false** в параметре **\@value**.
| 93.207547 | 746 | 0.800202 | rus_Cyrl | 0.830245 |
4701d270158b1bb52f28201e0f2e3e36b011f02f | 66 | md | Markdown | README.md | zs-liu/Pytorch-AS | 4e41f96522cce7a35f6625bdbe3863c0b74ee0ca | [
"MIT"
] | null | null | null | README.md | zs-liu/Pytorch-AS | 4e41f96522cce7a35f6625bdbe3863c0b74ee0ca | [
"MIT"
] | null | null | null | README.md | zs-liu/Pytorch-AS | 4e41f96522cce7a35f6625bdbe3863c0b74ee0ca | [
"MIT"
] | null | null | null | # QA
## InsuranceQA Dataset
## Answer-Selection Task
## By Pytorch | 16.5 | 24 | 0.727273 | kor_Hang | 0.391227 |
470227eadec54be282cbcbf3f9e32d0d4eb9c565 | 4,583 | md | Markdown | articles/virtual-machines/windows/run-scripts-in-vm.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/windows/run-scripts-in-vm.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/windows/run-scripts-in-vm.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Windows VM'de komut dosyaları çalıştırma
description: Bu konu, Windows sanal makine içinde komut dosyalarının nasıl çalıştırılabildiğini açıklar
services: automation
ms.service: automation
author: bobbytreed
ms.author: robreed
ms.date: 05/02/2018
ms.topic: article
manager: carmonm
ms.openlocfilehash: e10cab5261d6bd970135273bd4632b7c916641de
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/27/2020
ms.locfileid: "67476754"
---
# <a name="run-scripts-in-your-windows-vm"></a>Windows VM'nizde komut dosyaları çalıştırma
Görevleri otomatikleştirmek veya sorunları gidermek için vm komutları çalıştırmanız gerekebilir. Aşağıdaki makalede, VM'lerinizde komut dosyaları ve komutları çalıştırmak için kullanılabilen özellikler hakkında kısa bir genel bakış sunulmaktadır.
## <a name="custom-script-extension"></a>Özel Betik Uzantısı
[Özel Komut Dosyası Uzantısı](../extensions/custom-script-windows.md) öncelikle dağıtım sonrası yapılandırma ve yazılım yüklemesi için kullanılır.
* Azure sanal makinelerinde komut dosyalarını indirin ve çalıştırın.
* Azure Kaynak Yöneticisi şablonları, Azure CLI, REST API, PowerShell veya Azure portalı kullanılarak çalıştırılabilir.
* Komut dosyası dosyaları Azure depolama veya GitHub'dan indirilebilir veya Azure portalından çalıştırıldığında bilgisayarınızdan sağlanabilir.
* Windows makinelerinde PowerShell komut dosyasını ve Linux makinelerinde Bash komut dosyasını çalıştırın.
* Dağıtım sonrası yapılandırma, yazılım yüklemesi ve diğer yapılandırma veya yönetim görevleri için kullanışlıdır.
## <a name="run-command"></a>Çalıştır komutu
[Çalıştır Komutu](run-command.md) özelliği, komut dosyalarını kullanarak sanal makine ve uygulama yönetimi ve sorun giderme olanağı sağlar ve örneğin konuk güvenlik duvarı RDP veya SSH bağlantı noktası açık değilse, makineye erişilemese bile kullanılabilir.
* Azure sanal makinelerinde komut dosyaları çalıştırın.
* [Azure portalı](run-command.md), [REST API](/rest/api/compute/virtual%20machines%20run%20commands/runcommand), [Azure CLI](/cli/azure/vm/run-command?view=azure-cli-latest#az-vm-run-command-invoke)veya [PowerShell](https://docs.microsoft.com/powershell/module/az.compute/invoke-azvmruncommand) kullanılarak çalıştırılabilir
* Hızlı bir şekilde bir komut dosyası çalıştırın ve çıktıgörüntülemek ve Azure portalında gerektiği gibi tekrarlayın.
* Komut dosyası doğrudan yazılabilir veya yerleşik komut dosyalarından birini çalıştırabilirsiniz.
* Windows makinelerinde PowerShell komut dosyasını ve Linux makinelerinde Bash komut dosyasını çalıştırın.
* Sanal makine ve uygulama yönetimi ve ulaşılamayan sanal makinelerde komut dosyaları çalıştırmak için yararlıdır.
## <a name="hybrid-runbook-worker"></a>Karma Runbook Çalışanı
[Karma Runbook Worker,](../../automation/automation-hybrid-runbook-worker.md) genel makine, uygulama ve ortam yönetimini, kullanıcının otomasyon hesabında depolanan özel komut dosyalarıyla birlikte sağlar.
* Azure ve Azure olmayan makinelerde komut dosyaları çalıştırın.
* Azure portalı, Azure CLI, REST API, PowerShell, webhook kullanılarak çalıştırılabilir.
* Bir Otomasyon Hesabında depolanan ve yönetilen komut dosyaları.
* PowerShell, PowerShell İş Akışı, Python veya Grafik çalışma kitaplarını çalıştırın
* Komut dosyası çalışma süresinde zaman sınırı yok.
* Birden çok komut dosyası aynı anda çalıştırılabilir.
* Tam komut dosyası çıktısı döndürülür ve depolanır.
* İş geçmişi 90 gün için kullanılabilir.
* Komut dosyaları Yerel Sistem olarak veya kullanıcı tarafından sağlanan kimlik bilgileriyle çalıştırılabilir.
* [Manuel kurulum](../../automation/automation-windows-hrw-install.md) gerektirir
## <a name="serial-console"></a>Seri konsol
[Seri konsol,](serial-console.md) VM'ye bağlı bir klavyeye sahip olmaya benzer bir VM'ye doğrudan erişim sağlar.
* Azure sanal makinelerinde komutları çalıştırın.
* Azure portalındaki makineye metin tabanlı bir konsol kullanılarak çalıştırılabilir.
* Yerel bir kullanıcı hesabıyla makineye giriş yapın.
* Makinenin ağ veya işletim sistemi durumuna bakılmaksızın sanal makineye erişim gerektiğinde kullanışlıdır.
## <a name="next-steps"></a>Sonraki adımlar
VM'lerinizde komut dosyalarını ve komutları çalıştırmak için kullanılabilen farklı özellikler hakkında daha fazla bilgi edinin.
* [Özel Komut Dosyası Uzantısı](../extensions/custom-script-windows.md)
* [Çalıştır Komutu](run-command.md)
* [Karma Runbook Çalışanı](../../automation/automation-hybrid-runbook-worker.md)
* [Seri konsol](serial-console.md)
| 61.106667 | 324 | 0.819987 | tur_Latn | 0.999912 |
4702832bead0d670fad94c6798b332c3a91f1fce | 6,230 | md | Markdown | _posts/2019-11-04-october-2019-book-reading-list.md | hendrixjoseph/hendrixjoseph.github.io | 8ed2a62d528d97c6134e81fc67d1c472cba16a59 | [
"MIT"
] | null | null | null | _posts/2019-11-04-october-2019-book-reading-list.md | hendrixjoseph/hendrixjoseph.github.io | 8ed2a62d528d97c6134e81fc67d1c472cba16a59 | [
"MIT"
] | 8 | 2019-04-20T11:41:19.000Z | 2019-08-16T14:23:39.000Z | _posts/2019-11-04-october-2019-book-reading-list.md | hendrixjoseph/hendrixjoseph.github.io | 8ed2a62d528d97c6134e81fc67d1c472cba16a59 | [
"MIT"
] | 3 | 2019-07-02T15:13:32.000Z | 2021-07-06T15:39:33.000Z | ---
layout: post
title: October 2019 Book Reading List
tags: [books, reading list]
keywords: [book, read, books, reading, book reading, books i read]
hashtags: [books, reading]
image: /images/books/first-words-the-farm/front.jpg
---
Another month over, another book reading list.
It's crazy I've been doing these "book reading lists" for almost two years now - my first was in [January 2018](https://www.joehxblog.com/january-2018-book-reading-list/) - although I did skip the month of February 2019.
## Books I Read to My Son
What's also crazy is that I've been consistently reading to my son almost since the day he was born.
My first "book reading list" that mentions reading to him is [April 2018](https://www.joehxblog.com/april-2018-book-reading-list/) - and really couldn't have been any sooner, since he was born at the end of March.
Here's what I read to him this month:
* [A Picnic with Monet](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780811840460/22797475605)
* [Brown Bear, Brown Bear, What Do You See?](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780805047905/30449175727)
* [Dear Zoo by Rod Campbell](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780140504460/30342770212)
* First Words The Farm
* [Giraffes Can't Dance](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780439287197/22590290202)
* [Goodnight Moon](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780694003617/22680933528)
* [Good Night, New Baby](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9781602191884/30461426321)
* [Harry the Dirty Dog](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780060842444/30318576098)
* [Hooray For Wonderful Me!](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/servlet/BookDetailsPL?bi=30408124302)
* [I Love My Puppy by Caroline Jayne Church](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780545835947/30232218640)
* [I Love You This Much](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780310709619/22823417234)
* [Newtonian Physics for Babies](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9781492656203/30369022981)
* [Pat Them Gently](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9781581174625/30437603088)
* [Peekaboo in the Jungle](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780760760772/30350745445)
* [Pooh's Best Day A Book About Weather](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9789999030168/22925034702)
* [Spot Loves His Daddy](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780399243516/30277992672)
* [Tails Are Not For Pulling](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9781575421803/22550815426)
* [The Very Best Daddy of All](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780689841781/30339258990)
* [When? Slide N' Peek](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9781934650721/30331161552)
* [Where is Baby's Pumpkin?](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9781416909705/22742985323)
* [You Are My Sunshine by Caroline Jayne Church](https://affiliates.abebooks.com/c/2462910/77416/2029?u=https://www.abebooks.com/products/isbn/9780545075527/30332237361)
You'll notice one item on the list isn't linked - *First Words The Farm*. Despite having an ISBN on the book (9784577558972) I can't find *any* evidence the book even exists on the Internet.
*Front of the mystery book.*
*Back of the mystery book.*
I was able to find the publisher's website - [Flying Frog Publishing](https://www.flyingfrogpub.com/). And plenty of books pop up when searching [Flying Frog Publishing](https://www.amazon.com/Flying-Frog-Publishing-Books/s?k=Flying+Frog+Publishing&rh=n%3A283155&tag=hendrixjoseph-20) on Amazon.
*Publication details - including ISBN "9784577558972", barcode "082116032472", publisher name, etc.*"
## The ~~Books~~ Stories I Read for Me
I've trying to finish the "book" I'm reading now - [99 Classic Science-Fiction Short Stories](https://www.amazon.com/gp/product/B07RKSDTFP/?tag=hendrixjoseph-20) - as quickly as possible.
I've been [working on it since July](https://www.joehxblog.com/july-2019-book-reading-list/) and am itching to get to another book.
This month I read stories fifty-three through seventy-four:
{:start="53"}
53. *Youth* by Isaac Asimov
54. *Advanced Chemistry* by Jack G. Huekels
55. *A Relic of the Pliocene* by Jack London
56. *A Thousand Deaths* by Jack London
57. *Planchette* by Jack London
58. *The Curious Fragment* by Jack London
59. *The Man With the Gash* by Jack London
60. *The Red One* by Jack London
61. *The Shadow and the Flash* by Jack London
62. *The Strength of the Strong* by Jack London
63. *The Unparalleled Invasion* by Jack London
64. *When the World Was Young* by Jack London
65. *The Pygmy Planet* by Jack Williamson
66. *Regeneration* by Katherine MacLean & Charles Dye
67. *Games* by Katherine MacLean
68. *The Carnivore* by Katherine MacLean
69. *The Natives* by Katherine MacLean
70. *Report on Grand Central Terminal Miles* by Leo Szilard
71. *The Gostak and the Doshes* by John Breuer
72. *Uncommon Castaway* by Nelson Slade Bond
73. *The Last Survivor* by Peter B. Kyne
74. *Adjustment Team* by Philip K. Dick
That leaves, what, 25 stories left? I can do it! | 70 | 295 | 0.771429 | yue_Hant | 0.717738 |
47029e1f1d722b7c21538eaf1db22c8f994cbe58 | 321 | md | Markdown | site2/docs/reference-connector-admin.md | 262986832/pulsar | 5ce099bb316409a548a84c309a9386a6b7eed407 | [
"Apache-2.0"
] | 9,156 | 2018-09-23T14:10:46.000Z | 2022-03-31T07:17:16.000Z | site2/docs/reference-connector-admin.md | 262986832/pulsar | 5ce099bb316409a548a84c309a9386a6b7eed407 | [
"Apache-2.0"
] | 10,453 | 2018-09-22T00:31:02.000Z | 2022-03-31T20:02:09.000Z | site2/docs/reference-connector-admin.md | 262986832/pulsar | 5ce099bb316409a548a84c309a9386a6b7eed407 | [
"Apache-2.0"
] | 2,730 | 2018-09-25T05:46:22.000Z | 2022-03-31T06:48:59.000Z | ---
id: reference-connector-admin
title: Connector Admin CLI
sidebar_label: Connector Admin CLI
---
> **Important**
>
> For the latest and complete information about `Pulsar admin`, including commands, flags, descriptions, and more information, see [Pulsar admin doc](https://pulsar.apache.org/tools/pulsar-admin/).
>
| 26.75 | 197 | 0.750779 | eng_Latn | 0.944559 |
4702afbd21e4529369ae9982c6a36cedf607f73e | 8,405 | md | Markdown | WindowsServerDocs/administration/windows-server-update-services/manage/wid-to-sql-migration.md | laknight5/windowsserverdocs | c0e8d4108691a3e625579f3a0057d1ffe0496128 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-11T23:19:24.000Z | 2020-06-11T23:19:24.000Z | WindowsServerDocs/administration/windows-server-update-services/manage/wid-to-sql-migration.md | laknight5/windowsserverdocs | c0e8d4108691a3e625579f3a0057d1ffe0496128 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/administration/windows-server-update-services/manage/wid-to-sql-migration.md | laknight5/windowsserverdocs | c0e8d4108691a3e625579f3a0057d1ffe0496128 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Migrating the WSUS Database from (Windows Internal Database) WID to SQL
description: Windows Server Update Service (WSUS) topic - How to migrate the WSUS database (SUSDB) from a Windows Internal Database instance to a Local or Remote instance of SQL Server.
ms.prod: windows-server
ms.technology: manage-wsus
ms.topic: get-started article
ms.assetid: 90e3464c-49d8-4861-96db-ee6f8a09g7dr
author: coreyp-at-msft
ms.author: coreyp
manager: dougkim
ms.date: 07/25/2018
---
>Applies to: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016
# Migrating the WSUS Database from WID to SQL
Use the following steps to migrate the WSUS database (SUSDB) from a Windows Internal Database instance to a Local or Remote instance of SQL Server.
## Prerequisites
- SQL Instance. This can be the default **MSSQLServer** or a custom Instance.
- SQL Server Management Studio
- WSUS with WID role installed
- IIS (This is normally included when you install WSUS through Server Manager). It is not already installed, it will need to be.
## Migrating the WSUS database
### Stop the IIS and WSUS services on the WSUS server
From PowerShell (elevated), run:
```powershell
Stop-Service IISADMIN
Stop-Service WsusService
```
### Detach SUSDB from the Windows Internal Database
#### Using SQL Management Studio
1. Right-click **SUSDB** -> **Tasks** -> click **Detach**:
2. Check **Drop Existing Connections** and click **OK** (optional, if active connections exist).
#### Using Command Prompt
> [!IMPORTANT]
> These steps show how to detach the WSUS database (SUSDB) from the Windows Internal Database instance by using the **sqlcmd** utility. For more information about the **sqlcmd** utility, see [sqlcmd Utility](https://go.microsoft.com/fwlink/?LinkId=81183).
> 1. Open an elevated command prompt
> 2. Run the following SQL command to detach the WSUS database (SUSDB) from the Windows Internal Database instance by using the **sqlcmd** utility:
```batchfile
sqlcmd -S \\.\pipe\Microsoft##WID\tsql\query
use master
GO
alter database SUSDB set single_user with rollback immediate
GO
sp_detach_db SUSDB
GO
```
### Copy the SUSDB files to the SQL Server
1. Copy **SUSDB.mdf** and **SUSDB\_log.ldf** from the WID Data Folder (**%SystemDrive%**\**Windows\WID\Data**) to the SQL Instance Data Folder.
> [!TIP]
> For example, if your SQL Instance Folder is **C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL**, and the WID Data folder is **C:\Windows\WID\Data,** copy the SUSDB files from **C:\Windows\WID\Data** to **C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data**
### Attach SUSDB to the SQL Instance
1. In **SQL Server Management Studio**, under the **Instance** node, right-click **Databases**, and then click **Attach**.
2. In the **Attach Databases** box, under **Databases to attach**, click the **Add** button and locate the **SUSDB.mdf** file (copied from the WID Folder), and then click **OK**.
> [!TIP]
> This is also able to be done using Transact-Sql. Please see the [SQL documentation for attaching a database](https://docs.microsoft.com/sql/relational-databases/databases/attach-a-database) for its instructions.
>
> Example (using paths from previous example):
> ```sql
> USE master;
> GO
> CREATE DATABASE SUSDB
> ON
> (FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\SUSDB.mdf'),
> (FILENAME = 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\SUSDB_Log.ldf')
> FOR ATTACH;
> GO
>```
### Verify SQL Server and Database Logins and Permissions
#### SQL Server Login Permissions
After attaching the SUSDB, verify that **NT AUTHORITY\NETWORK SERVICE** has login permissions to the instance of SQL Server by doing the following:
1. Go into SQL Server Management Studio
2. Opening the Instance
3. Click **Security**
4. Click **Logins**
The **NT AUTHORITY\NETWORK SERVICE** account should be listed. If it is not, you need to add it by adding New Login Name.
> [!IMPORTANT]
> If the SQL Instance is on a different machine from WSUS, the WSUS Server's computer account should be listed in the format **[FQDN]\\[WSUSComputerName]$**. If not, the steps below can be used to add it, replacing **NT AUTHORITY\NETWORK SERVICE** with the WSUS Server's computer account (**[FQDN]\\[WSUSComputerName]$**) This would be ***in addition to*** granting rights to **NT AUTHORITY\NETWORK SERVICE**
##### Adding NT AUTHORITY\NETWORK SERVICE and granting it rights
1. Right Click **Logins** and click **New Login…**
2. On the **General** page, fill out the **Login name** (**NT AUTHORITY\NETWORK SERVICE**), and set the **Default database** to SUSDB.
3. On the **Server Roles** page, ensure **public** and **sysadmin** are selected.
4. On the **User Mapping** page:
- Under **Users mapped to this login**: select **SUSDB**
- Under **Database role membership for: SUSDB**, ensure the following are checked:
- **public**
- **webService**
5. Click **OK**
You should now see **NT AUTHORITY\NETWORK SERVICE** under Logins.
#### Database Permissions
1. Right-click the SUSDB
2. Select **Properties**
3. Click **Permissions**
The **NT AUTHORITY\NETWORK SERVICE** account should be listed.
1. If it is not, add the account.
2. On the Login name textbox, enter the WSUS machine in the following format:
> [**FQDN]\\[WSUSComputerName]$**
3. Verify that the **Default database** is set to **SUSDB**.
> [!TIP]
> In the following example, the FQDN is **Contosto.com** and the WSUS machine name is **WsusMachine**:
>
> 
4. On the **User Mapping** page, select the **SUSDB** Database under **Users mapped to this login**
5. Check **webservice** under the **Database role membership for: SUSDB**:
6. Click **OK** to save settings.
> [!NOTE]
> You may need to restart the SQL Service for the changes to take effect.
### Edit the registry to point WSUS to the SQL Server Instance
> [!IMPORTANT]
> Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, [back up the registry for restoration](https://support.microsoft.com/help/322756) in case problems occur.
1. Click **Start**, click **Run**, type **regedit**, and then click **OK**.
2. Locate the following key: **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName**
3. In the **Value** text box, type **[ServerName]\\[InstanceName]**, and then click **OK**. If the instance name is the default instance, type **[ServerName]**.
4. Locate the following key: **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\Installed Role Services\UpdateServices-WidDatabase**
5. Rename the Key to **UpdateServices-Database**
> [!NOTE]
> If you do not update this key, then **WsusUtil** will attempt to service the WID rather than the SQL Instance to which you have migrated.
### Start the IIS and WSUS services on the WSUS server
From PowerShell (elevated), run:
```powershell
Start-Service IISADMIN
Start-Service WsusService
```
> [!NOTE]
> If you are using the WSUS Console, close and restart it.
## Uninstalling the WID role (not recommended)
> [!WARNING]
> Removing the WID role also removes a database folder (**%SystemDrive%\Program Files\Update Services\Database**) that contains scripts required by WSUSUtil.exe for post-installation tasks. If you choose to uninstall the WID role, make sure you back up the **%SystemDrive%\Program Files\Update Services\Database** folder beforehand.
Using PowerShell:
```powershell
Uninstall-WindowsFeature -Name 'Windows-Internal-Database'
```
After the WID role is removed, verify that the following registry key is present: **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\Installed Role Services\UpdateServices-Database** | 43.776042 | 410 | 0.72207 | eng_Latn | 0.737271 |
4702c5c7db758273e4e7e666432bec4decbf4c08 | 2,599 | markdown | Markdown | _portfolio/6_TechnicalWritingExamples.markdown | melsuit/melsuit.github.io | ba320515ba4cfad4effdae568c82ad300ddcfd39 | [
"MIT",
"Unlicense"
] | null | null | null | _portfolio/6_TechnicalWritingExamples.markdown | melsuit/melsuit.github.io | ba320515ba4cfad4effdae568c82ad300ddcfd39 | [
"MIT",
"Unlicense"
] | null | null | null | _portfolio/6_TechnicalWritingExamples.markdown | melsuit/melsuit.github.io | ba320515ba4cfad4effdae568c82ad300ddcfd39 | [
"MIT",
"Unlicense"
] | null | null | null | ---
layout: post
title: Technical Writing Examples
description: Click to View Projects
img: /img/FeatureProjectImages/Technical Writing Paper Icon.jpg
---
Click on the arrow next to the title to learn more about each project.
<details>
<summary> Scenerio Writing Storyboard/Script Example </summary>
<ul style ="list-style'type:disc">
<li>Here is a sample from my latest project that has been genericized to demonstrate this writing style in a Storyboard/Script.</li>
</ul>
Files
<ul style="list-style'type:none">
<li>
<a href="/docs/TechnicalWritingExamples/S SB&Script Example.docx" download> Scenerio Writing Storyboard/Script Example
</a></li>
</ul>
</details>
<details>
<summary> Straight Informational Writing Storyboard/Script Example </summary>
<ul style ="list-style'type:disc">
<li>Here is a sample from my latest project that has been genericized to demonstrate this writing style in a Storyboard/Script.</li>
</ul>
Files
<ul style="list-style'type:none">
<li>
<a href="/docs/TechnicalWritingExamples/SI SB&Script Example.docx" download> Straight Informational Writing Storyboard/Script Example
</a></li>
</ul>
</details>
<details>
<summary> Straight Informational Writing Text Reference Example </summary>
<ul style ="list-style'type:disc">
<li>Here is a sample from my latest project that has been genericized to demonstrate this writing style in a Text Reference that would accompany the Video Training.</li>
</ul>
Files
<ul style="list-style'type:none">
<li>
<a href="/docs/TechnicalWritingExamples/S Text Reference Example.docx" download> Straight Informational Writing Text Reference Example
</a></li>
</ul>
</details>
<details>
<summary> Text Editing and Condensing Example </summary>
<ul style ="list-style'type:disc">
<li>A short exercise that shows some text editing and condensing skills.</li>
</ul>
Files
<ul style="list-style'type:none">
<li>
<a href="/docs/TechnicalWritingExamples/Editing and Condensing Text Example.docx" download> Editing and Condensing Text Example
</a></li>
</ul>
</details>
<details>
<summary> Writing Samples </summary>
<ul style ="list-style'type:disc">
<li>A short exercise that shows a concise 1 pg writing sample for a new employee guide.</li>
</ul>
Files
<ul style="list-style'type:none">
<li>
<a href="/docs/TechnicalWritingExamples/New Employee Guidelines - High School Teacher.docx" download> New Employee Guidelines - High School Teacher
</a></li>
</ul>
</details> | 35.60274 | 173 | 0.710273 | eng_Latn | 0.899779 |
4702e0bacb8a4dec7dd05f13b3711818a799204a | 4,961 | md | Markdown | _includes/stats/et/dep/dep.md | xidongbo/docs | 2745640d072534cb19e632c75ed255b82b8ddbfc | [
"Apache-2.0"
] | 1 | 2021-08-18T08:52:27.000Z | 2021-08-18T08:52:27.000Z | _includes/stats/et/dep/dep.md | xidongbo/docs | 2745640d072534cb19e632c75ed255b82b8ddbfc | [
"Apache-2.0"
] | null | null | null | _includes/stats/et/dep/dep.md | xidongbo/docs | 2745640d072534cb19e632c75ed255b82b8ddbfc | [
"Apache-2.0"
] | null | null | null |
--------------------------------------------------------------------------------
## Treebank Statistics (UD_Estonian)
This relation is universal.
9 nodes (0%) are attached to their parents as `dep`.
8 instances of `dep` (89%) are right-to-left (child precedes parent).
Average distance between parent and child is 6.55555555555556.
The following 5 pairs of parts of speech are connected with `dep`: [et-pos/VERB]()-[et-pos/VERB]() (5; 56% instances), [et-pos/ADV]()-[et-pos/X]() (1; 11% instances), [et-pos/NOUN]()-[et-pos/VERB]() (1; 11% instances), [et-pos/PROPN]()-[et-pos/PROPN]() (1; 11% instances), [et-pos/VERB]()-[et-pos/NOUN]() (1; 11% instances).
~~~ conllu
# visual-style 6 bgColor:blue
# visual-style 6 fgColor:white
# visual-style 9 bgColor:blue
# visual-style 9 fgColor:white
# visual-style 9 6 dep color:blue
1 - -- PUNCT punc/-- _ 6 punct _ _
2 Raha raha+0 NOUN n/com,sg,gen,%cap Case=Gen|Number=Sing 6 nmod _ _
3 taga taga+0 ADP prp/post,%gen AdpType=Post 2 case _ _
4 asi asi+0 NOUN n/com,sg,nom Case=Nom|Number=Sing 6 nsubj _ _
5 ei ei+0 AUX v/aux,neg Negative=Neg 6 neg _ _
6 seisa seis+0 VERB v/main,indic,pres,ps,neg Mood=Ind|Negative=Neg|Tense=Pres|VerbForm=Fin 9 dep _ _
7 , -- PUNCT punc/-- _ 6 punct _ _
8 - -- PUNCT punc/-- _ 6 punct _ _
9 omandab omanda+b VERB v/main,indic,pres,ps3,sg,ps,af Mood=Ind|Negative=Pos|Number=Sing|Person=3|Tense=Pres|VerbForm=Fin 0 root _ _
10 Paltsi Palts+0 PROPN prop/prop,sg,gen,%cap Case=Gen|Number=Sing 11 nmod _ _
11 jutt jutt+0 NOUN n/com,sg,nom Case=Nom|Number=Sing 9 nsubj _ _
12 laia lai+0 ADJ adj/pos,sg,gen Case=Gen|Degree=Pos|Number=Sing 13 amod _ _
13 joone joon+0 NOUN n/com,sg,gen Case=Gen|Number=Sing 9 dobj _ _
14 . -- PUNCT punc/-- _ 9 punct _ _
~~~
~~~ conllu
# visual-style 2 bgColor:blue
# visual-style 2 fgColor:white
# visual-style 6 bgColor:blue
# visual-style 6 fgColor:white
# visual-style 6 2 dep color:blue
1 Mare Mare+0 PROPN prop/prop,sg,nom,.cap Case=Nom|Number=Sing 2 nsubj _ _
2 on ole+0 VERB v-fin/main,indic,pres,ps3,sg,ps,af,.FinV,.Intr Mood=Ind|Negative=Pos|Number=Sing|Person=3|Tense=Pres|VerbForm=Fin 6 dep _ _
3 Mare Mare+0 PROPN prop/prop,sg,nom,.cap Case=Nom|Number=Sing 6 nsubj _ _
4 on ole+0 VERB v-fin/main,indic,pres,ps3,sg,ps,af,.FinV,.Intr Mood=Ind|Negative=Pos|Number=Sing|Person=3|Tense=Pres|VerbForm=Fin 6 cop _ _
5 nigu nigu+0 PART b/-- _ 6 cc _ _
6 tehnikaekspert tehnika-ekspert+0 NOUN n/com,sg,nom Case=Nom|Number=Sing 0 root _ _
7 , -- PUNCT punc/-- _ 6 punct _ _
8 mõtsime mõtle+sime VERB v-fin/main,indic,impf,ps1,pl,ps,af,.FinV,.NGP-P,.InfP,.El,.All Mood=Ind|Negative=Pos|Number=Plur|Person=1|Tense=Imp|VerbForm=Fin 6 conj _ _
9 et et+0 SCONJ conj-c/sub _ 10 mark _ _
10 pöördume pöördu+me VERB v-fin/main,indic,pres,ps1,pl,ps,af,.FinV,.Intr Mood=Ind|Negative=Pos|Number=Plur|Person=1|Tense=Pres|VerbForm=Fin 8 ccomp _ _
11 nagu nagu+0 PART b/-- _ 10 cc _ _
12 tehnilistes tehniline+tes ADJ adj/pos,pl,in Case=Ine|Degree=Pos|Number=Plur 13 amod _ _
13 küsimustes küsimus+tes NOUN n/com,pl,in Case=Ine|Number=Plur 10 nmod _ _
14 tema tema+0 PRON pron-pers/pers,ps3,sg,gen Case=Gen|Number=Sing|Person=3|PronType=Prs 10 nmod _ _
15 poole poole+0 ADP pst/post,.gen AdpType=Post|Case=Gen 14 case _ _
16 . -- PUNCT punc/-- _ 6 punct _ _
~~~
~~~ conllu
# visual-style 20 bgColor:blue
# visual-style 20 fgColor:white
# visual-style 21 bgColor:blue
# visual-style 21 fgColor:white
# visual-style 21 20 dep color:blue
1 jah jah+0 PART b/-- _ 2 cc _ _
2 jaa jaa+0 PART b/-- _ 0 root _ _
3 ja ja+0 CONJ conj-c/crd _ 2 cc _ _
4 Mare Mare+0 PROPN prop/prop,sg,nom,.cap Case=Nom|Number=Sing 5 nsubj _ _
5 ütleb ütle+b VERB v-fin/main,indic,pres,ps3,sg,ps,af,.FinV,.NGP-P Mood=Ind|Negative=Pos|Number=Sing|Person=3|Tense=Pres|VerbForm=Fin 2 conj _ _
6 et et+0 SCONJ conj-s/sub _ 8 mark _ _
7 ei ei+0 AUX v/aux,neg Negative=Neg 8 neg _ _
8 saa saa+0 VERB v-fin/main,indic,pres,ps,neg,.FinV,.NGP-P Mood=Ind|Negative=Neg|Tense=Pres|VerbForm=Fin 5 ccomp _ _
9 kuivaks kuiv+ks ADJ adj/pos,sg,tr Case=Tra|Degree=Pos|Number=Sing 8 advmod _ _
10 pesu pesu+0 NOUN n/com,sg,part Case=Par|Number=Sing 8 dobj _ _
11 et et+0 SCONJ conj-c/sub _ 13 mark _ _
12 tema tema+0 PRON pron-pers/pers,ps3,sg,nom Case=Nom|Number=Sing|Person=3|PronType=Prs 13 nsubj _ _
13 teeb tege+b VERB v-fin/main,indic,pres,ps3,sg,ps,af,.FinV,.NGP-P Mood=Ind|Negative=Pos|Number=Sing|Person=3|Tense=Pres|VerbForm=Fin 5 ccomp _ _
14 hh hh+0 PART b/-- _ 13 cc _ _
15 kaks kaks+0 NUM num/card,sg,nom,l Case=Nom|Number=Sing|NumForm=Word|NumType=Card 13 advmod _ _
16 korda kord+0 NOUN n/com,sg,part Case=Par|Number=Sing 15 nmod _ _
17 noh noh+0 PART b/-- _ 18 cc _ _
18 laseb lask+b VERB v-fin/main,indic,pres,ps3,sg,ps,af,.FinV,.NGP-P,.InfP Mood=Ind|Negative=Pos|Number=Sing|Person=3|Tense=Pres|VerbForm=Fin 5 ccomp _ _
19 uuesti uuesti+0 ADV adv/-- _ 18 advmod _ _
20 ta- ta X x/-- _ 21 dep _ _
21 tagasi tagasi+0 ADV adv/-- _ 18 advmod _ _
22 . -- PUNCT punc/-- _ 2 punct _ _
~~~
| 50.111111 | 324 | 0.709333 | yue_Hant | 0.644234 |
4703226a2094e3db248de0972827a026dadbbcc8 | 623 | md | Markdown | src/marketing/README.md | Muflhi01/css | f544ef8574a4d6e12cccf94d534ad66df3e9249a | [
"MIT"
] | 7,431 | 2015-03-23T19:10:53.000Z | 2019-02-08T08:05:59.000Z | src/marketing/README.md | Muflhi01/css | f544ef8574a4d6e12cccf94d534ad66df3e9249a | [
"MIT"
] | 1,295 | 2019-02-08T19:37:08.000Z | 2022-03-29T21:01:37.000Z | src/marketing/README.md | check-spelling/primer-css | 5353210fde40c248058a45560d07a5ac33444a0a | [
"MIT"
] | 742 | 2015-03-23T19:36:27.000Z | 2019-02-07T23:17:10.000Z | ---
bundle: "marketing"
generated: true
---
# Primer CSS: `marketing` bundle
## Usage
Primer CSS source files are written in [SCSS]. To include this Primer CSS module in your own build, ensure that your `node_modules` directory is listed in your Sass include paths, then import it with:
```scss
@import "@primer/css/marketing/index.scss";
```
## Build
The `@primer/css` npm package includes a standalone CSS build of this module in `dist/marketing.css`.
## License
[MIT](https://github.com/primer/css/blob/main/LICENSE) © [GitHub](https://github.com/)
[scss]: https://sass-lang.com/documentation/syntax#scss
| 23.961538 | 200 | 0.725522 | eng_Latn | 0.850696 |
4703a04cce97d82fa449650b50681ae7613a9c6b | 6,635 | md | Markdown | .github/workflows/README.md | Krrunal/Expensify.cash | ae6e3f4e95870d2eb6a89a9c95bed068c12f40ac | [
"MIT"
] | null | null | null | .github/workflows/README.md | Krrunal/Expensify.cash | ae6e3f4e95870d2eb6a89a9c95bed068c12f40ac | [
"MIT"
] | null | null | null | .github/workflows/README.md | Krrunal/Expensify.cash | ae6e3f4e95870d2eb6a89a9c95bed068c12f40ac | [
"MIT"
] | null | null | null | # [Expensify.cash](https://expensify.cash) GitHub Workflows
## Security Rules 🔐
1. Do **not** use `pull_request_target` trigger unless an external fork needs access to secrets, or a _write_ `GITHUB_TOKEN`.
1. Do **not ever** write a `pull_request_target` trigger with an explicit PR checkout, e.g. using `actions/checkout@v2`. This is [discussed further here](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)
1. **Do use** the `pull_request` trigger as it does not send internal secrets and only grants a _read_ `GITHUB_TOKEN`.
1. If an external action needs access to any secret (`GITHUB_TOKEN` or internal secret), use the commit hash of the workflow to prevent a modification of underlying source code at that version. For example:
1. **Bad:** `hmarr/[email protected]` Relies on the tag
1. **Good:** `hmarr/auto-approve-action@7782c7e2bdf62b4d79bdcded8332808fd2f179cd` Explicit Git hash
1. When creating secrets, use tightly scoped secrets that only allow access to that specific action's requirement
1. Review all modifications to our workflows with extra scrutiny, it is important to get it correct the first time.
1. Test workflow changes in your own public fork, for example: https://github.com/Andrew-Test-Org/Public-Test-Repo
1. Only trusted users will be allowed write access to the repository, however, it's good to add logic checks in actions to prevent human error.
## Further Reading 📖
1. https://securitylab.github.com/research/github-actions-preventing-pwn-requests
1. https://stackoverflow.com/a/62143130/1858217
## Secrets
The GitHub workflows require a large list of secrets to deploy, notify and test the code:
1. `LARGE_SECRET_PASSPHRASE` - decrypts secrets stored in various encrypted files stored in GitHub repository. To create updated versions of these encrypted files, refer to steps 1-4 of [this encrypted secrets help page](https://docs.github.com/en/actions/reference/encrypted-secrets#limits-for-secrets) using the `LARGE_SECRET_PASSPHRASE`.
1. `android/app/my-upload-key.keystore.gpg`
2. `android/app/android-fastlane-json-key.json.gpg`
3. `ios/chat_expensify_appstore.mobileprovision`
4. `ios/Certificates.p12.gpg`
2. `SLACK_WEBHOOK` - Sends Slack notifications via Slack WebHook https://expensify.slack.com/services/B01AX48D7MM
3. `OS_BOTIFY_TOKEN` - Personal access token for @OSBotify user in GitHub
4. `CLA_BOTIFY_TOKEN` - Personal access token for @CLABotify user in GitHub
5. `CSC_LINK` - Required to be set for desktop code signing: https://www.electron.build/code-signing.html#travis-appveyor-and-other-ci-servers
6. `CSC_KEY_PASSWORD` - Required to be set for desktop code signing: https://www.electron.build/code-signing.html#travis-appveyor-and-other-ci-servers
7. `APPLE_ID` - Required for notarizing desktop code in `desktop/notarize.js`
8. `APPLE_ID_PASSWORD` - Required for notarizing desktop code in `desktop/notarize.js`
9. `AWS_ACCESS_KEY_ID` - Required for hosting website and desktop compiled code
10. `AWS_SECRET_ACCESS_KEY` - Required for hosting website and desktop compiled code
11. `CLOUDFLARE_TOKEN` - Required for hosting website
12. `APPLE_CONTACT_EMAIL` - Email used for contact between Expensify and Apple for https://appstoreconnect.apple.com/
13. `APPLE_CONTACT_PHONE` - Phone number used for contact between Expensify and Apple for https://appstoreconnect.apple.com/
14. `APPLE_DEMO_EMAIL` - Demo account email used for https://appstoreconnect.apple.com/
15. `APPLE_DEMO_PASSWORD` - Demo account password used for https://appstoreconnect.apple.com/
## Actions
All these _workflows_ are comprised of atomic _actions_. Most of the time, we can use pre-made and independently maintained actions to create powerful workflows that meet our needs. However, when we want to do something very specific or have a more complex or robust action in mind, we can create our own _actions_.
All our actions are stored in the neighboring directory [`.github/actions`](https://github.com/Expensify/Expensify.cash/tree/main/.github/actions). Each action is a module comprised of three parts:
1) An [action metadata file](https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/creating-a-javascript-action#creating-an-action-metadata-file) called `action.yml`. This describes the action, gives it a name, and defines its inputs and outputs.
2) A Node.js script, whose name matches the module. This is where you can implement the custom logic for your action.
3) A compiled file called index.js. This is a compiled output of the file from (2) and should _NEVER_ be directly modified.
### Why do actions need to be compiled?
From the [GitHub Actions documentation](https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/creating-a-javascript-action#commit-tag-and-push-your-action-to-github):
> GitHub downloads each action run in a workflow during runtime and executes it as a complete package of code before you can use workflow commands like run to interact with the runner machine. This means you must include any package dependencies required to run the JavaScript code. You'll need to check in the toolkit core and github packages to your action's repository.
If you make any changes to an action's implementation, you must always recompile it in order for the changes to take effect. The action metadata file should use the compiled node.js executable script (`index.js`), _not_ the source file.
### How are actions compiled?
In order to bundle actions with their dependencies into a single Node.js executable script, we use [`ncc`](https://github.com/vercel/ncc). In order to make this easier, we've added an `npm` script to `package.json`, so you can just run `npm run gh-actions-build`. If you create a new action, make sure that you update `.github/scripts/buildActions.sh` to include your new action. Also, be sure that you always run `npm install` before recompiling if you added new dependencies, or they won't be included in the bundled executable. :)
### Important tips about creating GitHub Actions
- When calling your GitHub Action from one of our workflows, you must:
- First call `@actions/checkout`.
- Use the absolute path of the action in GitHub, including the repo name, path, and branch ref, like so:
```yaml
- name: Generate Version
uses: Expensify/Expensify.cash/.github/actions/bumpVersion@main
```
Do not try to use a relative path.
- Confusingly, paths in action metadata files (`action.yml`) _must_ use relative paths.
- You can't use any dynamic values or environment variables in a `uses` statement
| 88.466667 | 533 | 0.7789 | eng_Latn | 0.971866 |
4703cde5120807cc35b164577bc61b983b062de4 | 13,379 | md | Markdown | README.md | memoryruins/rasn | e3be7dbd94a59bdf8a40b930886953bca0c39140 | [
"Apache-2.0",
"MIT"
] | null | null | null | README.md | memoryruins/rasn | e3be7dbd94a59bdf8a40b930886953bca0c39140 | [
"Apache-2.0",
"MIT"
] | null | null | null | README.md | memoryruins/rasn | e3be7dbd94a59bdf8a40b930886953bca0c39140 | [
"Apache-2.0",
"MIT"
] | null | null | null | # Rasn
[](https://crates.io/crates/rasn)
[](https://github.com/XAMPPRocky/rasn/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
[](https://github.com/XAMPPRocky/tokei)
[](https://docs.rs/rasn/)
Welcome to `rasn` (pronounced "raisin"), a safe `#[no_std]` ASN.1 codec framework.
That enables you to safely create, share, and handle ASN.1 data types from and to different encoding rules. If you are unfamiliar with ASN.1 and encoding formats like BER/DER, I would recommend reading [*"A Warm Welcome to ASN.1 and DER"*][lenc] by Let's Encrypt as a quick introduction before continuing. In short it is an "Interface Description Language" (and data model) with a set of encoding formats (called rules) for that model. It was originally designed in the late 1980s and is used throughout the industry especially in telecommunications and cryptography.
[ghs]: https://github.com/sponsors/XAMPPRocky
[lenc]: https://letsencrypt.org/docs/a-warm-welcome-to-asn1-and-der/
## Features
### Abstract Codec Data Model
There are quite a few existing ASN.1 related Rust crates already, however they are currently specific to a single format or even a single standard, this makes it hard to share and re-use standards that are specified in ASN.1. Now with `rasn`'s abstract model you can build and share ASN.1 data types as crates that work with any encoder or decoder regardless of the underlying encoding rules, whether it's BER, CER, DER, or your own custom encoding.
### `#[no_std]` Support
Rasn is entirely `#[no_std]`, so you can handle and share the same ASN.1 code with a wide variety of platforms and devices.
### Rich Data Types
Rasn currently has support for nearly all of ASN.1's data types. `rasn` uses popular community libraries such as `bitvec`, `bytes`, and `chrono` for some of its data types as well as providing a couple of its own. Check out the [`types`][mod:types] module for what's currently available.
[mod:types]: http://docs.rs/rasn/0.2.0/rasn/types/index.html
### Safe BER, CER, and DER Codecs
Included with the framework is a implementation of the X.690 standard also known as the Basic Encoding Rules, Canonical Encoding Rules, and Distinguished Encoding Rules codecs. The encoder and decoder have been written in 100% safe Rust and fuzzed with [American Fuzzy Lop][bun] to ensure that the decoder correctly handles random input, and if valid that the encoder can correctly re-encode that value.
[bun]: https://lcamtuf.coredump.cx/afl/
### RFC implementations
Rasn also provides implementations for a number of IETF RFCs using the `rasn`
framework for use out of the box. These crates provide strongly typed
definitions for the necessary data types. Like `rasn` they are `#[no_std]`,
transport layer, and encoding rule agnostic.
- [LDAP](https://docs.rs/rasn-ldap)
- [MIB-II](https://docs.rs/rasn-mib)
- [PKIX](https://docs.rs/rasn-pkix)
- [SMI](https://docs.rs/rasn-smi)
- [SNMP](https://docs.rs/rasn-snmp)
### Powerful Derive Macros
Easily model your structs and enums with derive equivalents of all of the traits. These macros provide a automatic implementation that ensures your model is a valid ASN.1 type at *compile-time*. To explain that though, first we have to explain…
## How It Works
The codec API has been designed for ease of use, safety, and being hard to *misuse*. The most common mistakes are around handling the length and ensuring it's correctly encoded and decoded. In `rasn` this is completely abstracted away letting you focus on the abstract model. Let's look at what decoding a simple custom `SEQUENCE` type looks like.
```asn1
Person ::= SEQUENCE {
age INTEGER,
name UTF8String
}
```
Which we want to map to the following equivalent Rust code.
```rust
struct Person {
age: rasn::types::Integer,
name: String, // or rasn::types::Utf8String
}
```
### Implementing The Traits
When modelling an ASN.1 data type, there are three traits we'll need to implement. `Decode` and `Encode` for converting to and from encoding rules, and the shared `AsnType` trait; which defines some associated data needed to be given to the encoder and decoder. Currently the only thing we have define is the tag to use to identify our type.
```rust
# struct Person;
use rasn::{AsnType, Tag};
impl AsnType for Person {
// Default tag for sequences.
const TAG: Tag = Tag::SEQUENCE;
}
```
Next is the `Decode` and `Encode` traits. These are mirrors of each other and both have one provided method (`decode`/`encode`) and one required method (`decode_with_tag`/`encode_with_tag`). Since in ASN.1 nearly every type can be implicitly tagged allowing anyone to override the tag associated with the type, having `*_with_tag` as a required method requires the implementer to correctly handle this case, and the provided methods simply calls `*_with_tag` with the type's associated `AsnType::TAG`. Let's look at what the codec implementation of `Person` looks like.
```rust
# struct Person { name: Utf8String, age: Integer }
# impl rasn::AsnType for Person { const TAG: Tag = Tag::SEQUENCE; }
use rasn::{Decode, Decoder, Encode, Encoder, Tag, types::{Integer, Utf8String}};
impl Decode for Person {
fn decode_with_tag<D: Decoder>(decoder: &mut D, tag: Tag) -> Result<Self, D::Error> {
// Accepts a closure that decodes the contents of the sequence.
decoder.decode_sequence(tag, |decoder| {
let age = Integer::decode(decoder)?;
let name = Utf8String::decode(decoder)?;
Ok(Self { age, name })
})
}
}
impl Encode for Person {
fn encode_with_tag<E: Encoder>(&self, encoder: &mut E, tag: Tag) -> Result<(), E::Error> {
// Accepts a closure that encodes the contents of the sequence.
encoder.encode_sequence(tag, |encoder| {
self.age.encode(encoder)?;
self.name.encode(encoder)?;
Ok(())
})?;
Ok(())
}
}
```
That's it! We've just created a new ASN.1 that be encoded and decoded to BER, CER, and DER; and nowhere did we have to check the tag, the length, or whether the string was primitive or constructed encoded. All those nasty encoding rules details are completely abstracted away so your type only has handle how to map to and from ASN.1's data model.
With all the actual conversion code isolated to the codec implementations you can know that your model is always safe to use. The API has also been designed to prevent you from making common logic errors that can lead to invalid encoding. For example; if we look back our `Encode` implementation, and what if we forgot to use the encoder we were given in `encode_sequence` and tired to use the parent instead?
```text
error[E0501]: cannot borrow `*encoder` as mutable because previous closure requires unique access
--> tests/derive.rs:122:9
|
122 | encoder.encode_sequence(tag, |sequence| {
| ^ --------------- ---------- closure construction occurs here
| | |
| _________| first borrow later used by call
| |
123 | | self.age.encode(encoder)?;
| | ------- first borrow occurs due to use of `encoder` in closure
124 | | self.name.encode(sequence)?;
125 | | Ok(())
126 | | })?;
| |__________^ second borrow occurs here
error[E0500]: closure requires unique access to `encoder` but it is already borrowed
--> tests/derive.rs:122:38
|
122 | encoder.encode_sequence(tag, |sequence| {
| ------- --------------- ^^^^^^^^^^ closure construction occurs here
| | |
| | first borrow later used by call
| borrow occurs here
123 | self.age.encode(encoder)?;
| ------- second borrow occurs due to use of `encoder` in closure
```
Our code fails to compile! Which, in this case is great, there's no chance that our contents will accidentally be encoded in the wrong sequence because we forgot to change the name of a variable. These ownership semantics also mean that an `Encoder` can't accidentally encode the contents of a sequence multiple times in their implementation. Let's see how we can try to take this even further.
### Compile-Safe ASN.1 With Macros
So far we've shown how rasn's API takes steps to be safe and protect from accidentally creating an invalid model. However, it's often hard to cover everything in an imperative API. Something that is important to understand about ASN.1 that isn't obvious in the above examples is that; in ASN.1, all types can be identified by a tag (essentially two numbers e.g. `INTEGER`'s tag is `0, 2`). Field and variant names are not transmitted in most encoding rules, so this tag is also used to identify fields or variants in a `SEQUENCE` or `CHOICE`. This means that every that in a ASN.1 struct or enum every field and variant **must have** a distinct tag for the whole type to be considered valid. For example ; If we changed `age` in `Person` to be a `String` like below it would be invalid ASN.1 even though it compiles and runs correctly, we have to either use a different type or override `age`'s tag to be distinct from `name`'s. When implementing the `AsnType` trait yourself this requirement must checked by manually, however as we'll see you generally won't need to do that.
Included with rasn is a set of derive macros that enable you to have your ASN.1 model implementation implemented declaratively. The `Encode` and `Decode` macros will essentially auto-generate the implementations we showed earlier, but the real magic is the `AsnType` derive macro. Thanks to the `static-assertations` crate and recent developments in `const fn`; the `AsnType` derive will not only generate your `AsnType` implementation, it will also generate a check that asserts that every field or variant has a distinct tag at *compile-time*. This means now if for some reason we made a change to one of the types in person, we don't have re-check that our model is still valid, the compiler takes care of that for us.
```no_compile
// Invalid
#[derive(rasn::AsnType)]
struct Person {
age: Option<String>,
name: Option<String>,
}
```
We'll now get the following error trying to compile the above definition.
```text
error[E0080]: evaluation of constant value failed
--> tests/derive.rs:80:14
|
80 | #[derive(AsnType, Debug, Default, Decode, Encode, PartialEq)]
| ^^^^^^^ attempt to compute `0_usize - 1_usize` which would overflow
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
```
While not the most obvious error message at the moment, validating your model at compile-time enables you to work on ASN.1 code without fear that you're unintentionally changing something in the background. I bet you're wondering now though, how we are supposed to have a struct with two strings for fields? The answer is thankfully pretty simple, you just add `#[rasn(tag)]` attribute to override the tags of one or more of the types. However we can actually go further, because in ASN.1 there's the concept of having `AUTOMATIC TAGS` which essentially tells your ASN.1 compiler to automatically generate distinct tags for your ASN.1 definition. Now with rasn you can do that in Rust! Applying `#[rasn(automatic_tags)]` to the container automatically generate tags will apply the same automatic tagging transformation you'd expect from an ASN.1 compiler.
```rust
use rasn::AsnType;
// Valid
#[derive(AsnType)]
struct Person {
#[rasn(tag(context, 0))] // or just #[rasn(tag(0))]
age: Option<String>,
name: Option<String>,
}
// Also valid
#[derive(AsnType)]
#[rasn(automatic_tags)]
struct Person2 {
age: Option<String>,
name: Option<String>,
}
```
### What's Missing & What's Next?
While rasn is starting out relatively full featured, there are still plenty of missing features and types. The main limitation that exists currently, is the lack of support for constraints. In ASN.1 you can arbitrarily put constraints on types (e.g. array always of length 4, or a number between 1–10). There are encoding rules that take advantage of these constraints to save space, and you can't currently you can't communicate those constraints to a codec in a safe abstract fashion. So this means for example you wouldn't be able to implement a Packed Encoding Rules (PER) codec that handles constraints correctly. I want to eventually support constraints and PER directly, but it still requires a lot of design work to be thought through first.
## Disclaimer
The software is provided "as is" and the authors disclaim all warranties with regard to this software including all implied warranties of merchant-ability and fitness. In no event shall the authors be liable for any special, direct, indirect, or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortuous action, arising out of or in connection with the use or performance of this software.
| 66.895 | 1,077 | 0.727633 | eng_Latn | 0.99829 |
47046dd4ba94ef091d46e6fff8289c4a99533de9 | 498 | md | Markdown | src/environments/README.md | sambwest/zce | c7688cf985f5d79a48bdbd49eef03f2e34c584b1 | [
"MIT"
] | 126 | 2019-03-22T08:44:03.000Z | 2022-03-10T17:24:38.000Z | src/environments/README.md | sambwest/zce | c7688cf985f5d79a48bdbd49eef03f2e34c584b1 | [
"MIT"
] | 13 | 2020-06-19T21:34:32.000Z | 2022-02-02T04:35:11.000Z | src/environments/README.md | sambwest/zce | c7688cf985f5d79a48bdbd49eef03f2e34c584b1 | [
"MIT"
] | 18 | 2019-11-28T17:14:56.000Z | 2022-03-22T07:21:46.000Z | ## Firebase config
> create `configFirebase.ts` with your Firebase config
```js
export const configFirebase = {
apiKey: 'api-key',
authDomain: 'project-id.firebaseapp.com',
databaseURL: 'https://project-id.firebaseio.com',
projectId: 'project-id',
storageBucket: 'project-id.appspot.com',
messagingSenderId: 'sender-id',
appId: 'app-id',
measurementId: 'G-measurement-id'
};
```
> see how to set [Firebase config object](https://firebase.google.com/docs/web/setup#config-object)
| 26.210526 | 99 | 0.716867 | eng_Latn | 0.233408 |
4704d25dcccc9c5d38be7c51f86dd006ab072d79 | 411 | md | Markdown | cats/Amora/README.md | DestructHub/cats | 5620a38a23bee46eb709992a6747ba670f2ebf8d | [
"MIT"
] | 7 | 2019-10-18T11:39:05.000Z | 2021-11-04T20:25:16.000Z | cats/Amora/README.md | DestructHub/cats | 5620a38a23bee46eb709992a6747ba670f2ebf8d | [
"MIT"
] | 9 | 2019-10-18T04:53:39.000Z | 2020-10-18T10:41:38.000Z | cats/Amora/README.md | DestructHub/cats | 5620a38a23bee46eb709992a6747ba670f2ebf8d | [
"MIT"
] | 4 | 2019-10-18T14:31:20.000Z | 2021-11-04T20:25:20.000Z | # Meet Amora
<img src="Amora_1.jpg" width="250">
<img src="Amora_10.jpg" width="250">
<img src="Amora_11.jpg" width="250">
<img src="Amora_2.jpg" width="250">
<img src="Amora_3.jpg" width="250">
<img src="Amora_4.jpg" width="250">
<img src="Amora_5.jpg" width="250">
<img src="Amora_6.jpg" width="250">
<img src="Amora_7.jpg" width="250">
<img src="Amora_8.jpg" width="250">
<img src="Amora_9.jpg" width="250">
| 31.615385 | 36 | 0.6691 | pol_Latn | 0.121162 |
4705135268128650309cf0b3456f7e2f2804581c | 2,466 | md | Markdown | Exchange/ExchangeServer2013/enable-um-ip-gateway-exchange-2013-help.md | msbemba/OfficeDocs-Exchange | aab19f2bb72cfe2854808b8a2545dcbdf8233cb6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange/ExchangeServer2013/enable-um-ip-gateway-exchange-2013-help.md | msbemba/OfficeDocs-Exchange | aab19f2bb72cfe2854808b8a2545dcbdf8233cb6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange/ExchangeServer2013/enable-um-ip-gateway-exchange-2013-help.md | msbemba/OfficeDocs-Exchange | aab19f2bb72cfe2854808b8a2545dcbdf8233cb6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Enable a UM IP gateway: Exchange 2013 Help'
TOCTitle: Enable a UM IP gateway
ms.author: dmaguire
author: msdmaguire
manager: dansimp
ms.date: 11/17/2014
ms.reviewer:
ms.assetid: 2706ae06-c45d-41b7-abbe-378a9fca104a
mtps_version: v=EXCHG.150
---
# Enable a UM IP gateway in Exchange Server
_**Applies to:**: Exchange Server 2013, Exchange Server 2016_
By default, when a Unified Messaging (UM) IP gateway is created, its status is set to enabled. However, you might need to disable the UM IP gateway to take it offline and not allow it to take incoming or outgoing calls. After you create a UM IP gateway, you can control its operation and functionality by setting its status variable to enabled or disabled.
For additional management tasks related to UM IP gateways, see [UM IP gateway procedures](um-ip-gateway-procedures-exchange-2013-help.md).
## What do you need to know before you begin?
- Estimated time to complete: Less than 1 minute.
- You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "UM IP gateways" entry in the [Unified Messaging Permissions](http://technet.microsoft.com/library/d326c3bc-8f33-434a-bf02-a83cc26a5498.aspx) topic.
- Before you perform these procedures, confirm that a UM dial plan has been created. For detailed steps, see [Create a UM dial plan](create-um-dial-plan-exchange-2013-help.md).
- Before you perform these procedures, confirm that a UM IP gateway has been created and has been disabled. For detailed steps, see [Create a UM IP gateway](create-um-ip-gateway-exchange-2013-help.md).
- For information about keyboard shortcuts that may apply to the procedures in this topic, see [Keyboard shortcuts for the Exchange admin center in Exchange 2013](keyboard-shortcuts-in-the-exchange-admin-center-2013-help.md).
> [!TIP]
> Having problems? Ask for help in the Exchange forums. Visit the forums at [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612).
## Use the EAC to enable a UM IP gateway
1. In the EAC, navigate to \> **Unified Messaging** \> **UM IP Gateways**, select the UM IP gateway you want to enable, and then click the **Up arrow** .
2. On the **Warning** page, click **Yes**.
## Use the Shell to enable a UM IP gateway
This example enables a UM IP gateway named `MyUMIPGateway`.
```powershell
Enable-UMIPGateway -Identity MyUMIPGateway
```
| 50.326531 | 356 | 0.766423 | eng_Latn | 0.986414 |
47051e545e939e26ff6530df37a23fa5e9eee2e4 | 1,859 | md | Markdown | docs/csharp/language-reference/operators/assignment-operator.md | BeanHsiang/docs | 79c0f681b69d90a5251ed9aa9789b8f957c7b2ff | [
"CC-BY-4.0",
"MIT"
] | 1 | 2016-10-12T19:10:30.000Z | 2016-10-12T19:10:30.000Z | docs/csharp/language-reference/operators/assignment-operator.md | BeanHsiang/docs | 79c0f681b69d90a5251ed9aa9789b8f957c7b2ff | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/language-reference/operators/assignment-operator.md | BeanHsiang/docs | 79c0f681b69d90a5251ed9aa9789b8f957c7b2ff | [
"CC-BY-4.0",
"MIT"
] | 2 | 2016-11-06T09:42:50.000Z | 2016-11-06T18:28:18.000Z | ---
title: "= Operator (C# Reference)"
ms.date: 10/31/2018
f1_keywords:
- "=_CSharpKeyword"
helpviewer_keywords:
- "= operator [C#]"
ms.assetid: d802a6d5-32f0-42b8-b180-12f5a081bfc1
---
# = Operator (C# Reference)
The assignment operator `=` assigns the value of its right-hand operand to a variable, a [property](../../programming-guide/classes-and-structs/properties.md), or an [indexer](../../../csharp/programming-guide/indexers/index.md) element given by its left-hand operand. The result of an assignment expression is the value assigned to the left-hand operand. The type of the right-hand operand must be the same as the type of the left-hand operand or implicitly convertible to it.
The assignment operator is right-associative, that is, an expression of the form
```csharp
a = b = c
```
is evaluated as
```csharp
a = (b = c)
```
The following example demonstrates the usage of the assignment operator to assign values to a local variable, a property, and an indexer element:
[!code-csharp-interactive[assignment operator](~/samples/snippets/csharp/language-reference/operators/AssignmentExamples.cs#Assignments)]
## Operator overloadability
A user-defined type cannot overload the assignment operator. However, a user-defined type can define an implicit conversion to another type. That way, the value of a user-defined type can be assigned to a variable, a property, or an indexer element of another type. For more information, see the [implicit](../keywords/implicit.md) keyword article.
## C# language specification
For more information, see the [Simple assignment](~/_csharplang/spec/expressions.md#simple-assignment) section of the [C# language specification](../language-specification/index.md).
## See also
- [C# Reference](../index.md)
- [C# Programming Guide](../../programming-guide/index.md)
- [C# Operators](index.md)
| 43.232558 | 477 | 0.754169 | eng_Latn | 0.983127 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.