hexsha stringlengths 40 40 | size int64 5 1.04M | ext stringclasses 6 values | lang stringclasses 1 value | max_stars_repo_path stringlengths 3 344 | max_stars_repo_name stringlengths 5 125 | max_stars_repo_head_hexsha stringlengths 40 78 | max_stars_repo_licenses listlengths 1 11 | max_stars_count int64 1 368k ⌀ | max_stars_repo_stars_event_min_datetime stringlengths 24 24 ⌀ | max_stars_repo_stars_event_max_datetime stringlengths 24 24 ⌀ | max_issues_repo_path stringlengths 3 344 | max_issues_repo_name stringlengths 5 125 | max_issues_repo_head_hexsha stringlengths 40 78 | max_issues_repo_licenses listlengths 1 11 | max_issues_count int64 1 116k ⌀ | max_issues_repo_issues_event_min_datetime stringlengths 24 24 ⌀ | max_issues_repo_issues_event_max_datetime stringlengths 24 24 ⌀ | max_forks_repo_path stringlengths 3 344 | max_forks_repo_name stringlengths 5 125 | max_forks_repo_head_hexsha stringlengths 40 78 | max_forks_repo_licenses listlengths 1 11 | max_forks_count int64 1 105k ⌀ | max_forks_repo_forks_event_min_datetime stringlengths 24 24 ⌀ | max_forks_repo_forks_event_max_datetime stringlengths 24 24 ⌀ | content stringlengths 5 1.04M | avg_line_length float64 1.14 851k | max_line_length int64 1 1.03M | alphanum_fraction float64 0 1 | lid stringclasses 191 values | lid_prob float64 0.01 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
4bb3b0e978f5ea3e23a8ab0d2639fc2acf1613a3 | 4,489 | md | Markdown | src/tools-support/release-notes/api/2020-04-17.md | rlee-sap/developer.concur.com | ea17d718a6f840c024f7a943264ebedd5907e34a | [
"Apache-2.0"
] | 2 | 2020-12-27T05:53:47.000Z | 2021-03-19T04:42:45.000Z | src/tools-support/release-notes/api/2020-04-17.md | rlee-sap/developer.concur.com | ea17d718a6f840c024f7a943264ebedd5907e34a | [
"Apache-2.0"
] | 27 | 2021-06-04T17:29:08.000Z | 2021-06-04T17:29:58.000Z | src/tools-support/release-notes/api/2020-04-17.md | rlee-sap/developer.concur.com | ea17d718a6f840c024f7a943264ebedd5907e34a | [
"Apache-2.0"
] | 3 | 2020-12-16T17:53:39.000Z | 2021-01-09T22:18:17.000Z | ---
title: SAP Concur Developer Center - API Update, April 2020
layout: reference
---
## Contents
* [Ongoing: Quick Expense v1 and Quick Expense v3 Retirement and Decommission](#ongoing-quick-expense-v3)
* [Ongoing: Retirement and Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)](#ongoing-request-retirement)
* [Budget v4 API Available](#budget-v4)
* [New SSL Certificate for concursolutions.com](#ssl-cert)
## <a name="ongoing-quick-expense-v3"></a>Ongoing: Quick Expense v1 and Quick Expense v3 Retirement and Decommission
Effective March 31, 2020, the Quick Expense v1 and Quick Expense v3 APIs were retired and decommissioned. We encourage all current users to migrate to [Quick Expense v4](https://developer.concur.com/api-reference/expense/quick-expense/v4.quick-expense.html) as soon as possible.
Please refer to the [deprecation policy](https://developer.concur.com/tools-support/deprecation-policy.html) for definitions and additional information.
### Business Purpose / Client Benefit
This update removed two outdated APIs.
## <a name="ongoing-request-retirement"></a>Ongoing: Retirement and Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)
Effective December 1, 2020, SAP Concur will be retiring the existing Concur Request APIs (v1.0, v3.0, and v3.1). These APIs are replaced by the Concur Request v4 APIs.
### Business Purpose / Client Benefit
The Concur Request APIs v1.0, v3.0 and v3.1 only support the previous authentication method, which is not best security practice and does not meet the Oauth2 standards. In addition, the previous versions of the Concur Request APIs provided limited possibilities for moving a Request through the approval workflow, as well as managing custom simple & connected list fields. These issues are resolved with the new Concur Request v4 APIs.
In addition, SAP Concur has run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 APIs (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 APIs.
## <a name="budget-v4"></a>Budget v4 API Soon Available
SAP Concur has released the Budget v4 API. Budget v4 provides the following features:
* **Fiscal Calendar:** This API can GET, POST, and DELETE fiscal years and periods similar to the Fiscal Calendar UI in Budget Configuration.
* **Budget Category:** This API can GET, POST, and DELETE budget categories, and GET all expense types of a budget category.
* **Budget Items:** This API can GET, POST, and DELETE budget items including details such as period amounts, budget item tracking fields (cost objects), budget viewers, managers, and approvers.
* **Budget Tracking Field:** This API can GET all budget tracking fields.
* **Budget Adjustment:** This API can POST budget adjustments.
* **Global Availability:** Budget v4 API is supported in all SAP Concur data centers.
### Business Purpose / Client Benefit
This new Budget API enables users to integrate Budget with their
ERP and HR systems to automate budget configuration and maintenance as well as
importing external transactions not captured via SAP Concur through budget
adjustments.
## <a name="ssl-cert"></a>New SSL Certificate for concursolutions.com
In an effort to ensure the ongoing security of our products and services, SAP Concur has issued a new concursolutions.com SSL certificate. ***The current certificate expired on April 14, 2020.***
If the pinned certificate was not updated prior to April 14, 2020, your organization and users will experience disruption to SAP Concur products and services.
Customers who have not pinned the certificate do not need to take any action as the new certificate is updated automatically. Most customers do not pin the certificate.
Please be aware: As an enhancement to our Security and Compliance program, this certificate will be updated on an annual basis.
### Business Purpose / Client Benefit
This update provides ongoing security for our products and services.
### Configuration / Feature Activation
Please consult with your IT department to check if this applies to you.
The new SSL certificate can be accessed here: http://assets.concur.com/concurtraining/cte/en-us/concursolutions.cert.pem
Supply this URL to your IT department.
To save the certificate, click the link above, select all the text in the browser, copy it to a file, then name the file concursolutions.cert.pem.
| 61.493151 | 435 | 0.784807 | eng_Latn | 0.982675 |
4bb4083cf800db0786b898db479078dae850398b | 747 | md | Markdown | README.md | ProgTrade/TCalculator | 5a795aee851fdbfd6054d65a567aab066348484e | [
"MIT"
] | null | null | null | README.md | ProgTrade/TCalculator | 5a795aee851fdbfd6054d65a567aab066348484e | [
"MIT"
] | null | null | null | README.md | ProgTrade/TCalculator | 5a795aee851fdbfd6054d65a567aab066348484e | [
"MIT"
] | 1 | 2019-11-30T04:34:45.000Z | 2019-11-30T04:34:45.000Z | # TCalculator
TCalculator is a small calculator for OS X using a custom parser for simple term evaluation.
## Development
TCalculator is currently being developed. The core components are complete and seem to be working. It also contains a small window to provide a simple demonstration of the parser.
The code still needs to be improved a little bit and I should add some UnitTests.
## Motivation
Of course, I know that the default calculator of OS X has by far more functionality than mine, but I'm actually trying to learn Swift and I think this project gives me the possiblity to explore most of the features that Swift contains as I already implemented these specific algorithms in [SharpMath](https://github.com/ProgTrade/SharpMath) (C#).
| 74.7 | 346 | 0.800535 | eng_Latn | 0.99951 |
4bb45161e1b875c44b3bbea874d6e8c2daa92001 | 1,323 | md | Markdown | README.md | badu/microservices-demo | fe0b56ac33e1c87c8ea6fb3ff0f2312650322727 | [
"Apache-2.0"
] | 1 | 2021-07-29T00:16:21.000Z | 2021-07-29T00:16:21.000Z | README.md | badu/microservices-demo | fe0b56ac33e1c87c8ea6fb3ff0f2312650322727 | [
"Apache-2.0"
] | null | null | null | README.md | badu/microservices-demo | fe0b56ac33e1c87c8ea6fb3ff0f2312650322727 | [
"Apache-2.0"
] | null | null | null | # Demo Microservices
## Initial database setup
Run the following commands
`docker exec -it postgresql_comments bash`
`psql --host=localhost --username=postgres --password`
Type password `postgres`
`CREATE DATABASE comments;`
Type `\l` to see it created.
`docker exec -it postgresql_hotels bash`
`psql --host=localhost --username=postgres --password`
Type password `postgres`
`CREATE DATABASE hotels;`
Type `\l` to see it created.
`docker exec -it postgresql_images bash`
`psql --host=localhost --username=postgres --password`
Type password `postgres`
`CREATE DATABASE images;`
Type `\l` to see it created.
`docker exec -it postgresql_users bash`
`psql --host=localhost --username=postgres --password`
Type password `postgres`
`CREATE DATABASE users;`
Type `\l` to see it created.
## Migrate
Install [this](https://github.com/golang-migrate/migrate) and run make commands for each of the database to create tables.
## Generate Swagger
Install [this](https://github.com/swaggo/swag) then run: `make swagger_api`
### Jaeger UI:
http://localhost:16686
### Prometheus UI:
http://localhost:9090
### Grafana UI:
http://localhost:3000 user > admin password > admin
### RabbitMQ UI:
http://localhost:15672 user > guest password > guest
### Swagger UI:
* https://localhost:8081/swagger/index.html
| 17.878378 | 122 | 0.730159 | kor_Hang | 0.437691 |
4bb4a808a6b6dbb56bbfbc35abe131c4b6e8ef86 | 9,990 | md | Markdown | docs/de/3.1.0/guide/platforms/ios/plugin.md | jsoref/cordova-docs | bd265628de93a0cd2070e984cc0bb32448445494 | [
"Apache-2.0"
] | 1 | 2016-03-06T18:14:12.000Z | 2016-03-06T18:14:12.000Z | docs/de/3.1.0/guide/platforms/ios/plugin.md | jsoref/cordova-docs | bd265628de93a0cd2070e984cc0bb32448445494 | [
"Apache-2.0"
] | null | null | null | docs/de/3.1.0/guide/platforms/ios/plugin.md | jsoref/cordova-docs | bd265628de93a0cd2070e984cc0bb32448445494 | [
"Apache-2.0"
] | 1 | 2019-02-15T19:10:38.000Z | 2019-02-15T19:10:38.000Z | ---
license: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
---
# iOS Plugins
Eine Plugin ist eine Objective-C-Klasse, die erweitert die `CDVPlugin` Klasse.
Jedes Plugin-Klasse muss registriert sein, als ein `<feature>` tag-in der `config.xml` Datei. Es ist über diesen Mechanismus, dass JavaScript `exec` Methode `service` Parameter ordnet eine Objective-C-Klasse.
## Plugin-Klasse Zuordnung
Der JavaScript-Teil eines Plugins verwendet immer die `cordova.exec` Methode wie folgt:
exec(<successFunction>, <failFunction>, <service>, <action>, [<args>]);
Dies marshallt Ersuchen der `UIWebView` auf die iOS native Seite, mehr oder weniger kochendes bis Berufung der `action` -Methode für die `service` -Klasse mit der übergebenen Argumente der `args` Array.
Geben Sie das Plugin als ein `<feature>` Tag in Ihre Cordova-iOS-Anwendung-Projekt `config.xml` Datei.
<feature name="LocalStorage">
<param name="ios-package" value="CDVLocalStorage" />
</feature>
Das Feature `name` Attribut sollte übereinstimmen, was Sie in der JavaScript verwenden `exec` Anruf `service` Parameter, und das `value` -Attribut den Namen des Plugins Objective-C Klasse übereinstimmen sollte. `<param name>`sollte ich `"ios-package"` . Wenn Sie dieses Setup nicht folgen, wird das Plugin kann kompiliert, aber werden nicht von Cordova erreichbar.
## Plugin-Initialisierung und Lebensdauer
Wird eine Instanz eines Plugin-Objekts erstellt, für das Leben eines jeden `UIWebView` . Plugins werden nicht instanziiert bis sie zuerst durch einen Aufruf von JavaScript, verwiesen wird, es sei denn, `<param>` mit einem `onload` `name` Attribut auf festgelegt ist `"true"` in `config.xml` . Z.B.:
<feature name="Echo">
<param name="ios-package" value="Echo" />
<param name="onload" value="true" />
</feature>
Es gibt *keine* benannten Initialisierer für Plugins. Stattdessen sollten die Plugins verwenden die `pluginInitialize` -Methode für ihre Start-up-Logik.
Plugins mit langer Laufzeit-Anforderungen, elektronische Aktivität (z. B. spielen Medien), Zuhörer oder internen Zustand sollten implementieren die `onReset` Methode und stoppen oder Bereinigen Sie diese Tätigkeiten. Diese Methode wird ausgeführt, wenn die `UIWebView` navigiert zu einer neuen Seite oder Aktualisierungen, die das JavaScript lädt.
## Ein iOS Cordova Plugin schreiben
Wir haben JavaScript Feuer aus eine Plugin-Anforderung an die systemeigene Seite. Wir haben das iOS Objective-C-Plugin richtig zugeordnet, über die `config.xml` Datei. Also sieht die letzte iOS Objective-C-Plugin-Klasse wie?
Was an das Plugin per JavaScript gesendet ruft `exec` Funktion übergeben wird, in der entsprechenden Plugin-Klasse `action` Methode. Eine Plugin-Methode hat diese Signatur:
- (void)myMethod:(CDVInvokedUrlCommand*)command
{
CDVPluginResult* pluginResult = nil;
NSString* myarg = [command.arguments objectAtIndex:0];
if (myarg != nil) {
pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK];
} else {
pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_ERROR messageAsString:@"Arg was null"];
}
[self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
}
1. [CDVInvokedUrlCommand.h][1]
2. [CDVPluginResult.h][2]
3. [CDVCommandDelegate.h][3]
[1]: https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVInvokedUrlCommand.h
[2]: https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPluginResult.h
[3]: https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVCommandDelegate.h
## iOS CDVPluginResult Message-Typen
Mit CDVPluginResult können Sie zurückgeben eine Vielzahl von Ergebnistypen zurück an Ihre JavaScript-Rückrufe mit Klassenmethoden, die aussehen wie:
+ (CDVPluginResult*)resultWithStatus:(CDVCommandStatus)statusOrdinal messageAs...
Sie können erstellen, `String` , `Int` , `Double` , `Bool` , `Array` , `Dictionary` , `ArrayBuffer` , und `Multipart` Arten. Oder keine Argumente (nur senden einen Status) anfügen. Oder ein Fehler zurückgegeben. Sie können auch keines Plugin-Ergebnis gesendet werden, in diesem Fall wird der Rückruf nicht ausgelöst.
### Notizen
* `messageAsArrayBuffer`erwartet `NSData*` und konvertiert in eine `ArrayBuffer` für Ihre JavaScript-Rückruf (und `ArrayBuffers` von JavaScript zu einem Plugin gesendet werden`NSData*`).
* `messageAsMultipart` erwartet ein `NSArray *` Typen und sendet das gesamte Array als mit allen anderen unterstützt die `Argumente` um Ihre JavaScript-Rückruf.
* Besonderheit: Dies ist nicht nur syntaktischer Zucker (auch wenn es süß ist). Auf diese Weise sind alle Argumente serialisiert oder deserialisiert wie nötig. Z.B. gefahrlos zurück `NSData*` als mehrteilige, aber nicht als `Array` /`Dictionary`.
## Echo-Plugin iOS Plugin
Wir würden fügen Sie Folgendes in des Projekts `config.xml` Datei:
<feature name="Echo">
<param name="ios-package" value="Echo" />
</feature>
Dann wir die folgenden Dateien fügen würden ( `Echo.h` und `Echo.m` ) in das Plugins-Verzeichnis unserer Cordova-iOS-Anwendung-Verzeichnis:
/********* Echo.h Cordova Plugin Header *******/
#import <Cordova/CDV.h>
@interface Echo : CDVPlugin
- (void)echo:(CDVInvokedUrlCommand*)command;
@end
/********* Echo.m Cordova Plugin Implementation *******/
#import "Echo.h"
#import <Cordova/CDV.h>
@implementation Echo
- (void)echo:(CDVInvokedUrlCommand*)command
{
CDVPluginResult* pluginResult = nil;
NSString* echo = [command.arguments objectAtIndex:0];
if (echo != nil && [echo length] > 0) {
pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:echo];
} else {
pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_ERROR];
}
[self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
}
@end
Werfen Sie einen Blick auf den Code. An der Spitze haben wir alle notwendigen Cordova Einfuhren. Unsere Klasse erstreckt sich von `CDVPlugin` (sehr wichtig).
Dieses Plugin unterstützt nur eine Aktion, die `echo` Aktion. Zuerst, wir holen die Echo-Zeichenfolge unter Verwendung der `objectAtIndex` -Methode für unsere `args` , es zu sagen, wir wollen den 10. Parameter im Array Argumente zu bringen. Wir machen ein bisschen Parameterüberprüfung: Stellen Sie sicher, es ist nicht `nil` , und stellen Sie sicher, es ist keine Zeichenfolge der Länge Null.
Wenn es ist, wir zurück ein `PluginResult` mit einem `ERROR` Status. Wenn alle diese Prüfungen bestehen, dann kehren wir zurück ein `PluginResult` mit einer `OK` Status, und übergeben Sie die `echo` Zeichenfolge wir in erster Linie als Parameter empfangen.
Endlich, wir senden das Ergebnis an `self.commandDelegate` , die führt die `exec` Methode Erfolg oder Misserfolg Rückrufe auf der Seite JavaScript. Wenn der Erfolg-Rückruf aufgerufen wird, übergibt es in die `echo` Parameter.
## Threading
Plugin-Methoden werden in demselben Thread wie die Benutzeroberfläche ausgeführt. Wenn Ihr Plugin ein hohes Maß an Verarbeitung erfordert oder einen blockierenden Aufruf erfordert, verwenden Sie einen Hintergrund-Thread. Zum Beispiel:
- (void)myPluginMethod:(CDVInvokedUrlCommand*)command
{
// Check command.arguments here.
[self.commandDelegate runInBackground:^{
NSString* payload = nil;
// Some blocking logic...
CDVPluginResult* pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:payload];
// The sendPluginResult method is thread-safe.
[self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
}];
}
## Erweiterte Plugin-Funktionalität
Sehen Sie andere Methoden, denen Sie, in überschreiben können:
* [CDVPlugin.h][4]
* [CDVPlugin.m][5]
[4]: https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.h
[5]: https://github.com/apache/cordova-ios/blob/master/CordovaLib/Classes/CDVPlugin.m
Beispielsweise können Sie Haken in die `pause` , `resume` , app beenden und `handleOpenURL` Ereignisse.
## Debuggen von Plugins
Zum Debuggen der Objective-C-Seite verwenden Sie Xcodes integrierten Debuggers. Für JavaScript auf iOS können 5,0 [Weinre, einem Apache-Cordova-Projekt][6] oder [iWebInspector, ein Drittanbieter - Dienstprogramm][7] Sie
[6]: https://github.com/apache/cordova-weinre
[7]: http://www.iwebinspector.com/
Für iOS 6 würden Sie Safari 6.0 verwenden, einfach an Ihre Anwendung, die in das iOS 6 Simulator ausgeführt.
## Häufige Probleme
* Vergessen Sie nicht, Ihr Plugin Zuordnung zu "config.xml" hinzugefügt werden. Wenn Sie vergessen haben, wird ein Fehler in der Xcode-Konsole protokolliert.
* Vergessen Sie nicht, alle Hosts, die Verbindung in die Whitelist hinzufügen, wie in Domain-Whitelist-Handbuch beschrieben. Wenn Sie vergessen haben, wird ein Fehler in der Xcode-Konsole protokolliert. | 50.969388 | 406 | 0.74034 | deu_Latn | 0.948192 |
4bb4c7dfbf0bcdd503935aa900f798e0369650e5 | 2,166 | md | Markdown | pi/_posts/2019-06-30-pi_4b.md | chaidouzi/chaidouzi.github.io | 0bdeedb7edcc2ece9fe293fea06594a3c5e9c173 | [
"MIT"
] | null | null | null | pi/_posts/2019-06-30-pi_4b.md | chaidouzi/chaidouzi.github.io | 0bdeedb7edcc2ece9fe293fea06594a3c5e9c173 | [
"MIT"
] | null | null | null | pi/_posts/2019-06-30-pi_4b.md | chaidouzi/chaidouzi.github.io | 0bdeedb7edcc2ece9fe293fea06594a3c5e9c173 | [
"MIT"
] | null | null | null | ---
title: 树莓派 4b
typora-root-url: ../..
---
> 6 月 24 日，树莓派悄然发布了第四代产品 Raspberry Pi 4。
>
> 新一代开发板经过了从里到外的全面革新，得益于制程和架构的提升，4 代性能预计可比上代树莓派 3B+提升 2-4 倍。
>
> 树莓派开发机构（Raspberry Pi Foundation）称，这款设备可以提供「与入门级 x86 PC 系统相媲美的桌面性能」。
X光下的树莓派4
| **配置** | **树莓派4 B** | **树莓派3 B+** |
| -------------- | --------------------------------------------- | ---------------------------------------------- |
| **CPU** | 1.5-GHz，4核 Broadcom BCM2711B0 (Cortex A-72) | 1.4-GHz，4核 Broadcom BCM2837B0 (Cortex A-53) |
| **内存** | 1 - 4GB DDR4 | 1GB DDR2 |
| **GPU** | 500 MHz VideoCore VI | 400 MHz VideoCore IV |
| **视频输出** | 双 micro HDMI 端口 | 单 HDMI 端口 |
| **最大分辨率** | 4K 60 Hz + 1080p 或 2x 4K 30 Hz | 2560 x 1600 |
| **USB端口** | 2x USB 3.0 / 2x USB 2.0 | 4x USB 2.0 |
| **有线网络** | 千兆以太网 | 330Mbps 以太网 |
| **无线网络** | 蓝牙 5.0，802.11ac (2.4 / 5 GHz) | 蓝牙 4.1，802.11ac (2.4 / 5 GHz) |
| **供电端口** | USB Type-C | micro USB |
| **电源要求** | 5V-3A | 5V-2.5A |
| **尺寸** | 88 x 58 x 19.5mm | 82 x 56 x 19.5mm |
| **重量** | 46g | 50g |
树莓派4的性能已经赶上我们大学时代的PC了。这里是一份4G内存版的对比测评：[Raspberry Pi 4 Review: The New Gold Standard for Single-Board Computing](https://www.tomshardware.com/reviews/raspberry-pi-4-b,6193.html)
便宜的价格、便携的尺寸、pc级别的性能以及可扩展性，占领家庭娱乐市场、移动端市场、教学市场只是一个时间问题了。
目前是学生学习计算机、老人上网机的首选。树莓派4（￥300上下）+SD卡+显示器+硬盘+键鼠，很低的成本就可以组装一台Linux系统电脑。 | 42.470588 | 176 | 0.366113 | yue_Hant | 0.810386 |
4bb4c8b8ddc06a302399939d49e364d51256ad48 | 1,636 | md | Markdown | docs/visual-basic/programming-guide/language-features/strings/introduction-to-strings.md | felpasl/docs.pt-br | 1b47adcbc2e400f937650f9de1cd0c511e80738e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/programming-guide/language-features/strings/introduction-to-strings.md | felpasl/docs.pt-br | 1b47adcbc2e400f937650f9de1cd0c511e80738e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/programming-guide/language-features/strings/introduction-to-strings.md | felpasl/docs.pt-br | 1b47adcbc2e400f937650f9de1cd0c511e80738e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Introdução a cadeias de caracteres no Visual Basic
ms.date: 07/20/2015
helpviewer_keywords:
- strings [Visual Basic], about strings
ms.assetid: c1b0f6b4-9717-426b-a3db-957e57a60764
ms.openlocfilehash: 63a2020fe89d0e0d101ce2eda20506a446e102f3
ms.sourcegitcommit: 6b308cf6d627d78ee36dbbae8972a310ac7fd6c8
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 01/23/2019
ms.locfileid: "54640375"
---
# <a name="introduction-to-strings-in-visual-basic"></a>Introdução a cadeias de caracteres no Visual Basic
Esta seção descreve os conceitos básicos por trás do uso de cadeias de caracteres no Visual Basic.
## <a name="in-this-section"></a>Nesta seção
[Noções Básicas de Cadeias de Caracteres](../../../../visual-basic/programming-guide/language-features/strings/string-basics.md)
Apresenta os conceitos básicos por trás do uso de cadeias de caracteres e variáveis de cadeia de caracteres.
[Tipos de métodos de manipulação de cadeia de caracteres no Visual Basic](../../../../visual-basic/programming-guide/language-features/strings/types-of-string-manipulation-methods.md)
Apresenta várias maneiras diferentes de analisar e manipular cadeias de caracteres.
[Como a cultura afeta cadeias de caracteres no Visual Basic](../../../../visual-basic/programming-guide/language-features/strings/how-culture-affects-strings.md)
Discute como o Visual Basic usa informações de cultura para executar comparações e conversões de cadeia de caracteres.
## <a name="see-also"></a>Consulte também
- [Cadeias de Caracteres](../../../../visual-basic/programming-guide/language-features/strings/index.md)
| 56.413793 | 186 | 0.775672 | por_Latn | 0.90064 |
4bb4cf89b32ac468b133346985a25ef11a6678f5 | 4,643 | md | Markdown | brands/icon/skype-for-business.md | liuwave/icon-helper | 6339786f595d6f12a432db71e7aaccb693b9fe59 | [
"MIT"
] | 2 | 2020-10-26T16:32:26.000Z | 2021-01-13T09:28:45.000Z | brands/icon/skype-for-business.md | liuwave/icon-helper | 6339786f595d6f12a432db71e7aaccb693b9fe59 | [
"MIT"
] | 48 | 2020-04-04T12:39:59.000Z | 2022-02-27T01:30:09.000Z | brands/icon/skype-for-business.md | liuwave/icon-helper | 6339786f595d6f12a432db71e7aaccb693b9fe59 | [
"MIT"
] | null | null | null | ---
title: Skype for Business(Skype for Business) ICON转svg、png下载
name: skype-for-business
zhTips: Skype for Business
search:
image: https://iconhelper.cn/svg/brands/skype-for-business.svg
---
# Skype for Business <small style="font-size: 60%;font-weight: 100">Skype for Business</small>
<div id="svg" class="svg-wrap">
<svg role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><title>Skype for Business icon</title><path d="M14.04 10.92l-2.52-.56c-.96-.24-2.04-.52-2.04-1.44 0-.92.76-1.56 2.16-1.56 2.84 0 2.6 1.96 4 1.96.72 0 1.36-.4 1.36-1.16 0-1.76-2.8-3.08-5.2-3.08-2.56 0-5.28 1.08-5.28 4 0 1.4.48 2.92 3.24 3.64l3.44.88c1.04.24 1.36.84 1.36 1.36 0 .88-.92 1.84-2.48 1.84-3.08 0-2.64-2.44-4.28-2.44-.72 0-1.32.52-1.32 1.24 0 1.44 1.76 3.4 5.6 3.4 3.68 0 5.52-1.84 5.52-4.24-.04-1.6-.76-3.2-3.56-3.84zm9.08 3.04c.12-.64.16-1.28.16-1.96C23.28 5.76 18.24.72 12 .72c-.68 0-1.32.04-1.96.16C9.04.32 7.92 0 6.72 0 3 0 0 3 0 6.72c0 1.2.32 2.36.88 3.32-.12.64-.16 1.28-.16 1.96 0 6.24 5.04 11.28 11.28 11.28.68 0 1.32-.04 1.96-.16 1 .56 2.12.88 3.32.88C21 24 24 21 24 17.28c0-1.2-.32-2.36-.88-3.32zm-5.84 8.32c-.88 0-1.72-.24-2.48-.64l-.52-.32-.6.12c-.52.08-1.08.16-1.68.16a9.56 9.56 0 01-9.56-9.56c0-.56.04-1.12.16-1.68l.12-.6-.32-.52c-.44-.76-.64-1.6-.64-2.48 0-2.76 2.24-5 5-5 .88 0 1.72.24 2.48.64l.52.32.6-.12c.56-.08 1.12-.16 1.68-.16A9.56 9.56 0 0121.6 12c0 .56-.04 1.12-.16 1.68l-.12.6.32.52c.44.76.64 1.6.64 2.48 0 2.76-2.24 5-5 5Z"/></svg>
</div>
<detail full-name='skype-for-business'></detail>
<div class="detail-page">
<p>
<span><span class="badge-success badge">免费图标</span> <span class="badge-success badge">免费修改</span> <span class="badge-success badge">免费下载</span> </span>
<br/>
<span>
ICON库：
<span class="badge-secondary badge">品牌图标(Simple Icon)</span>
</span>
<br/>
<span>
CSS名称：
<span class="badge-secondary badge">skype-for-business</span>
</span>
<br/>
<span>
版本：
<span class="badge-secondary badge">2.8.0</span>
</span>
<br/>
<span>图标来源/作者：<span class="badge-light badge">Simple Icon</span></span>
<br/>
<span class="zh-detail">中文描述：<span class="badge-primary badge">Skype for Business</span><span class="help-link"><span>帮助改进</span>(<a href="https://gitee.com/liuwave/icon-helper/edit/master/json/brands/skype-for-business.json" target="_blank" rel="noopener noreferrer">gitee</a><a href="https://github.com/liuwave/icon-helper/edit/master/json/brands/skype-for-business.json" target="_blank" rel="noopener noreferrer">github</a></span>)</span><br/>
</p>
</div><div class="description description alert alert-light"><p>图标来源地址：<a href="https://en.wikipedia.org/wiki/Skype_for_Business_Server" target="_blank" rel="noopener noreferrer">https://en.wikipedia.org/wiki/Skype_for_Business_Server</a></p></div>
<div class="alert alert-dark">
<img height="21" width="21" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />
<img height="24" width="24" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />
<img height="32" width="32" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />
<img height="48" width="48" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />
<img height="64" width="64" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />
<img height="96" width="96" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />
</div>
<div>
<p>可以像图片那样使用：
</p>
<div class="alert alert-primary" style="font-size: 14px">
<img height="32" width="32" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />
<copy-btn content='<img height="32" width="32" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />'></copy-btn>
</div>
<div class="alert alert-secondary">
<img height="32" width="32" src="https://cdn.jsdelivr.net/npm/simple-icons@latest/icons/skypeforbusiness.svg" />skypeforbusiness
<copy-btn content="skypeforbusiness" btn-title="复制图标名称"></copy-btn>
</div>
</div>
<div class="icon-detail__container">
<p>关于“<b>Skype for Business</b>”的评论:</p>
</div>
<Vssue title="关于“Skype for Business”的评论" />
<div><p>Simple Icon是一个免费的品牌图标库。图标Skype for Business可以免费下载使用。更多关于 Simple Icon的信息，参见：<a target="_blank" href="https://iconhelper.cn/brands.html">品牌图标(Simple Icon)</a>
</p></div>
<div style="padding:2rem 0 " class="page-nav"><p class="inner"><span class="prev">←<router-link to="/icon/skype.html">Skype</router-link></span> <span class="next"><router-link to="/icon/slack.html">Slack</router-link>→</span></p></div>
| 63.60274 | 1,139 | 0.689856 | yue_Hant | 0.265856 |
4bb4efd513c8d82a13fa0e6b1aaaccff77d82abf | 5,157 | markdown | Markdown | _posts/2011-07-11-faster-edits-with-inline-editing.markdown | NaeemShaikh/git-github.com-StackExchange-stack-blog | 04f94931e5c99cfe434124225353992cb34cb735 | [
"MIT"
] | 176 | 2015-07-14T06:39:15.000Z | 2021-11-14T17:39:32.000Z | _posts/2011-07-11-faster-edits-with-inline-editing.markdown | NaeemShaikh/git-github.com-StackExchange-stack-blog | 04f94931e5c99cfe434124225353992cb34cb735 | [
"MIT"
] | 71 | 2015-07-13T14:09:09.000Z | 2019-02-25T21:23:16.000Z | _posts/2011-07-11-faster-edits-with-inline-editing.markdown | NaeemShaikh/git-github.com-StackExchange-stack-blog | 04f94931e5c99cfe434124225353992cb34cb735 | [
"MIT"
] | 145 | 2015-07-15T06:53:49.000Z | 2022-03-29T09:58:26.000Z | ---
author: jeffatwood
comments: true
date: 2011-07-11 08:55:43+00:00
layout: post
redirect_from: /2011/07/faster-edits-with-inline-editing
hero:
slug: faster-edits-with-inline-editing
title: Faster Edits with Inline Editing
wordpress_id: 8702
tags:
- company
- community
- design
- stackexchange
---
Every Stack Exchange question and answer pair is intended to be an [evergreen, editable resource for future travelers](http://blog.stackoverflow.com/2011/01/the-wikipedia-of-long-tail-programming-questions/):
>
The editing feature is there so that old question/answer pairs can get better and better. For every person who asks a question and gets an answer on Stack Exchange, hundreds or thousands of people will come read that conversation later. Even if the original asker got a decent answer and moved on, the question lives on and may continue to be useful for decades.
>
This is fundamentally different from Usenet or any of the web-based forums. It means that Stack Exchange is not just a historical record of questions and answers. It's a lot more than that: it's actually a community-edited wiki of narrow, "long-tail" questions -- questions that aren’t quite important enough to deserve a page on Wikipedia, but which come up over and over again.
**Editing is what you might call a [family value](http://blog.stackoverflow.com/2009/04/in-defense-of-editing/) on our network.** All the content you generously contribute to any [Stack Exchange site](http://stackexchange.com/sites) is licensed to us, you, and the rest of the world [under Creative Commons](http://blog.stackoverflow.com/2009/06/stack-overflow-creative-commons-data-dump/) with the explicit promise that future visitors can help us improve it and keep it up to date -- largely through editing.
To get an idea of just how much editing goes on, here's a snapshot of edits performed on Stack Overflow between February 1, 2011 and July 8, 2011:
One of the primary ways we try to encourage editing is by **making it easier to edit**:
* We added [inline tagging](http://blog.stackoverflow.com/2010/04/new-10k-feature-inline-tagging/) in April 2010, which made it much faster for high reputation users to retag questions.
* We added [suggested edits](http://blog.stackoverflow.com/2011/02/suggested-edits-and-edit-review/) in February 2011, which opened up the world of edits to anonymous users and users with 2,000 or less reputation.
How much of the editing total do anonymous and regular users contribute? Here's a snapshot of suggested edits performed on Stack Overflow for the same time period; the green line is registered users, and the blue line is anonymous users.
So, about **one quarter** of all edits are suggestions from anonymous and regular users. Only a tiny trickle are from anonymous users, on the order of 10 to 30 per day. (If you're wondering why anonymous edits doubled in June, we made a copy change on the site that helped. Try browsing the site in incognito / inprivate / private browsing mode and see if you can tell what it is.)
We think the current level of editing is admirable -- and climbing -- but we are deeply concerned that there's not nearly enough editing to keep up with the corpus of almost 2 million questions on Stack Overflow. The English Wikipedia currently has [about 3.6 million articles](http://meta.wikimedia.org/wiki/List_of_Wikipedias#All_Wikipedias_ordered_by_number_of_articles), so **if you think of every Stack Overflow question as a potentially editable article, we _already_ have more than half the footprint of Wikipedia to maintain and keep up to date**. A scary thought as Stack Overflow nears its [third birthday](http://blog.stackoverflow.com/2009/08/one-year-of-stack-overflow/).
To address this concern, we relied on another of our core family values: [performance is a feature](http://www.codinghorror.com/blog/2011/06/performance-is-a-feature.html). That is, if you want more editing … _make editing faster!_
That's why I'm pleased to announce that **we now support inline editing on all Stack Exchange sites**. There's no longer any need to visit a separate editing page; simply click "edit" and begin editing the post _right there on the question page_.
This is a much faster method of editing, as the above animation demonstrates. (And for optimal speed, remember to press tab, tab, space to save your edit -- we even built in a little ctrl+enter shortcut to jump right to saving the edit.)
We've only opened up inline editing to editors (users with 2,000+ reputation) for now, but we might extend it to all users eventually. And if you prefer the old editing page for whatever reason, just hold down ctrl when clicking on edit to get it.
What’s so special about editing? You might as well ask what’s so special about editing on Wikipedia? Uh... _everything?_ So go forth, [be bold](http://en.wikipedia.org/wiki/Wikipedia:Be_bold), and **exercise your new, faster inline editing skills!**
| 75.838235 | 684 | 0.780493 | eng_Latn | 0.996347 |
4bb53d5a213554ce2ea2dfd5e46cb84f922ea3a9 | 339 | markdown | Markdown | _posts/0011-01-01-email-template.markdown | oncletom/innovation-lab-brand-guidelines | 39e6e8f97f02e58b2a0b210f0297ed1820b08108 | [
"MIT"
] | 1 | 2016-12-30T16:47:50.000Z | 2016-12-30T16:47:50.000Z | _posts/0011-01-01-email-template.markdown | oncletom/innovation-lab-brand-guidelines | 39e6e8f97f02e58b2a0b210f0297ed1820b08108 | [
"MIT"
] | 1 | 2016-09-28T14:58:14.000Z | 2016-09-28T21:35:06.000Z | _posts/0011-01-01-email-template.markdown | oncletom/innovation-lab-brand-guidelines | 39e6e8f97f02e58b2a0b210f0297ed1820b08108 | [
"MIT"
] | 1 | 2018-10-09T08:44:43.000Z | 2018-10-09T08:44:43.000Z | ---
layout: post
title: "Email template"
date: 0011-01-01 12:23:49
categories: website
---
Email fields will consist of four main elements: the brand logo, a title, content and the footer.
<div class="c-image">
<img src="/innovation-lab-brand-guidelines/images/02-website/02-04-email-template/2-10-a.png" alt="2-10-a.png">
</div>
| 22.6 | 113 | 0.707965 | eng_Latn | 0.598405 |
4bb60a65cf3e1b75e5c0f6b68960826f3413fbb3 | 1,180 | md | Markdown | README.md | blockhead404/cryptocoin-price | 03c6ad6f90646eca33f06accbf291ae9bf40c5e1 | [
"Apache-2.0"
] | null | null | null | README.md | blockhead404/cryptocoin-price | 03c6ad6f90646eca33f06accbf291ae9bf40c5e1 | [
"Apache-2.0"
] | null | null | null | README.md | blockhead404/cryptocoin-price | 03c6ad6f90646eca33f06accbf291ae9bf40c5e1 | [
"Apache-2.0"
] | null | null | null | # Cryptocoin price statusbar widget
## Introduction
LIVE CRYPTOCOIN PRICE INDICATION for Ubuntu 17.x
## The application
Following coins are currently supported:
+ Bitcoin
+ Dogecoin
+ Ethereum
+ Litecoin
+ Navcoin
More will follow.
## Dependencies
### Python libraries
The python application uses the 'requests' library. This library can be easily installed using pip.
## Supported Linux distros
### Ubuntu 17.04 (Unity)
The appindicator runs out of the box on Ubuntu 17.04 with a Unity shell. Multiple instances can be run next to eachother without any problem.
## Running the app
You can run this application without debug messages with following command in a terminal:
```bash
nohup python3 /path/to/cryptocoin_price.py &
```
If you want to see the debug messages, run following command:
```bash
python3 /path/to/cryptocoin_price.py
```
## Contribute
Want to work on the project? Any kind of contribution is welcome!
Follow these steps:
- Fork the project.
- Create a new branch.
- Make your changes and write tests when practical.
- Commit your changes to the new branch.
- Send a pull request.
## Authors
***[Debjyoti Guha](https://github.com/debajyotiguha11/)***
| 24.583333 | 141 | 0.761017 | eng_Latn | 0.991438 |
4bb6a33f9086020cc5e7ffc1a7429d65a35e2045 | 1,419 | md | Markdown | _posts/2008/2008-10-02-event_reminder_barn_dance.md | barrymcgee/stmgrts | 53fadf731262e07b748cad455563c2f45fb80db5 | [
"CC0-1.0"
] | null | null | null | _posts/2008/2008-10-02-event_reminder_barn_dance.md | barrymcgee/stmgrts | 53fadf731262e07b748cad455563c2f45fb80db5 | [
"CC0-1.0"
] | 4 | 2016-09-11T07:52:02.000Z | 2019-10-03T10:10:25.000Z | _posts/2008/2008-10-02-event_reminder_barn_dance.md | barrymcgee/stmgrts | 53fadf731262e07b748cad455563c2f45fb80db5 | [
"CC0-1.0"
] | 3 | 2018-05-11T06:33:27.000Z | 2019-08-05T11:39:02.000Z | ---
layout: post
title: "Event Reminder: Barn Dance"
permalink: /archives/2008/10/event_reminder_barn_dance.html
commentfile: 2008-10-02-event_reminder_barn_dance
category: around_town
date: 2008-10-02 22:11:38
image: "/assets/images/2008/SMFBarnDance_thumb.gif"
excerpt: |
Come and enjoy a barn dance celebration to welcome in the Autumn!
Dance your socks off on <a href="https://stmargarets.london/event/concert/200705141984">Friday 17th October 2008, from 7.30pm until late</a>
£10 per person (includes live music, full dancing instructions (caller!), cheese board and good priced drinks)
---
<a href="/assets/images/2008/SMFBarnDance.gif" title="See larger version of - Barn Dance poster"><img src="/assets/images/2008/SMFBarnDance_thumb.gif" width="106" height="150" alt="Barn Dance poster" class="photo right" /></a>
Come and enjoy a barn dance celebration to welcome in the Autumn!
Dance your socks off on [Friday 17th October 2008, from 7.30pm until late](/event/concert/200705141984).
£10 per person (includes live music, full dancing instructions (caller!), cheese board and good priced drinks)
At St Stephen's School Hall, St Margarets, Twickenham (entrance on A316)
All money raised goes to the St Margaret's Fair senior citizen's Christmas dinner!
For further details and to reserve a table, please call John I'Anson (07880 796174) or Zeph King (07977 298045).
| 44.34375 | 226 | 0.758985 | eng_Latn | 0.855377 |
4bb7a18ac1befb9c4a13fc67005e4fa52f9fe111 | 1,997 | md | Markdown | README.md | ricardocrudo/button | 889d3840f76527b2338ef3a34aca23c7a0b0735a | [
"MIT"
] | null | null | null | README.md | ricardocrudo/button | 889d3840f76527b2338ef3a34aca23c7a0b0735a | [
"MIT"
] | null | null | null | README.md | ricardocrudo/button | 889d3840f76527b2338ef3a34aca23c7a0b0735a | [
"MIT"
] | 1 | 2020-11-22T05:16:54.000Z | 2020-11-22T05:16:54.000Z | button
======
Library to control push buttons, implemented in C. The library is designed to use only static
memory allocation and it can be used with any microcontroller.
Features
---
* CPU agnostic implementation
* use only static memory allocation
* configurable via macros
* support press, release and hold events
* support callback function for events
How to install
---
Simply copy the content of src directory to your work directory.
Configuration
---
The configuration of the library is done by setting 'define' macros in the header file,
under the configuration section.
There are two mandatory configurations before the use, the GPIO include file and the
setting of the *BUTTON_GPIO_GET* macro. In the include files section replace the line
`#include "gpio.h"` with the include of your GPIO library. Then, in the configuration
section, adjust the macro *BUTTON_GPIO_GET* to the "get gpio" function of your library.
To use the library with an Arduino the configuration would be:
#include <Arduino.h> // replace the "gpio.h"
// ...
#define BUTTON_GPIO_GET(port,pin) digitalRead(pin)
The other settings are preset and can be adjusted as needed. The macro *BUTTON_MAX_INSTANCES*
is used to define the total amount of buttons being controlled by the library.
The macro *BUTTON_PRESSED_VALUE* defines if the logic value read when the button is pressed
and the *BUTTON_TICK_PERIOD* macro is used to set the interrupt service routine (ISR) period.
How to use
---
Once the configuration is done the last required step, before start to use the library, is to
place the function `button_tick` inside one timer ISR. Remember that the period of this timer must
match with the value in *BUTTON_TICK_PERIOD* macro.
Remark: this library does not configure the GPIO direction, you have to do it before use the library
functions.
To see more details how to use the library, please check the online
[API documentation](http://ricardocrudo.github.io/button).
License
---
MIT
| 32.737705 | 100 | 0.776665 | eng_Latn | 0.99869 |
4bb8371abd0f8c2d61eef28a3a53253148ed0d3b | 1,335 | md | Markdown | exampleSite/content_meta/movies/veritatis-aut-sed-1969.md | muthukrishnandev/review-theme | 8518a9461abbd1888208881f328496015bbc5db6 | [
"MIT"
] | null | null | null | exampleSite/content_meta/movies/veritatis-aut-sed-1969.md | muthukrishnandev/review-theme | 8518a9461abbd1888208881f328496015bbc5db6 | [
"MIT"
] | null | null | null | exampleSite/content_meta/movies/veritatis-aut-sed-1969.md | muthukrishnandev/review-theme | 8518a9461abbd1888208881f328496015bbc5db6 | [
"MIT"
] | null | null | null | ---
title: "Veritatis Aut Sed"
slug: "veritatis-aut-sed-1969"
date: 2015-11-06T11:40:58Z
lastmod: "2016-06-05T11:02:56Z"
meta:
title: "Veritatis aut sed"
tagline: "Molestias vel laborum recusandae culpa"
storyline: "Omnis similique et esse voluptatem animi quia et natus voluptatum iste laborum laborum ut doloribus ut tenetur laudantium et deserunt"
year: 1969
released_on: "1969-03-30T09:16:02Z"
running_time: 95
certificate: "U"
trailer: "https://youtube.com/watch?v="
poster: "/images/posters/poster-sample.png"
external_links:
imdb: "https://imdb.com/"
rotten_tomatoes: "https://rottentomatoes.com/"
meta_critic: "https://metacritic.com/"
wikipedia: "https://wikipedia.org"
genres:
- Drama
actors:
- Janiya Keeling
- Brendan Braun
- Carmelo Greenholt
- Lemuel Rohan
- Guido Swaniawski
directors:
- Winona Brekke
writers:
- Denis Abshire
- Lavern Bergstrom
- Yoshiko Padberg
- Jairo Volkman
- Krystina Schuppe
cinematographers:
- Christop Roob
- Lavina McLaughlin
- Cyrus Oberbrunner
musicdirectors:
- Krystal Ziemann
- Estefania Ledner
- Lola Thompson
languages:
- Malagasy
- Tahitian
- Polish
productions:
- Quos perferendis hic
- Dignissimos quis rerum
- Qui voluptas
plottags:
- population
- screen
- slip
---
| 18.287671 | 148 | 0.698876 | kor_Hang | 0.149597 |
4bb87f5174026d79cb3ea3edb0bd360818fa4772 | 3,717 | md | Markdown | _posts/2018-12-01-geoserver-gwc.md | AllanHao/allanhao.github.io | ff18fa513333f48b8108e0fb4c944578f10df169 | [
"MIT"
] | null | null | null | _posts/2018-12-01-geoserver-gwc.md | AllanHao/allanhao.github.io | ff18fa513333f48b8108e0fb4c944578f10df169 | [
"MIT"
] | 13 | 2018-08-30T06:06:30.000Z | 2022-02-26T08:55:35.000Z | _posts/2018-12-01-geoserver-gwc.md | AllanHao/allanhao.github.io | ff18fa513333f48b8108e0fb4c944578f10df169 | [
"MIT"
] | 1 | 2018-09-10T10:11:50.000Z | 2018-09-10T10:11:50.000Z | ---
layout: post
title: GeoServer中GeoWebCache(GWC)的使用
categories: [GeoServer]
description: 利用GeoWebCache实现WebGIS地形图展示的缓存优化
keywords: GeoServer, GeoWebCache
---
本文介绍GeoWebCache的使用方法，包括如何切缓存，访问缓存wms/wmts服务，如何复用栅格缓存等。
> 文章大部分内容转载自<a href='https://www.cnblogs.com/naaoveGIS/p/4195008.html' target='_blank'>https://www.cnblogs.com/naaoveGIS/p/4195008.html</a>
## 1.前言
在geoserver1.7版本之后，geoserver本身集成了GeoWebCache这个模块。本文介绍的是geoserver2.2版本，其本身自带有GeoWebCache。不过如果你的geoserver版本比较老，或者想使用最新的GeoWebCache，可以自行在网上下载此工具，然后根据说明按照和配置，这里不做描述。
## 2.GeoWebCache简介
### 2.1 总体描述
GeoWebCache(GWC)是一个采用Java实现用于缓存WMS（Web Map Service）Tile的开源项目。当地图客户端请求一张新地图和Tile时，GeoWebCache将拦截这些调用然后返回缓存过的Tiles。如果找不到缓存再调用服务器上的Tiles，从而提高地图展示的速度。实现更好的用户体验。
### 2.2特点描述
a.GWC支持多种来源的瓦片，比如ArcGIS的瓦片。
b.GWC支持多种请求，比如WMS、WMS-C、WMTS、TMS、Googl Maps KML和Virtual Earth。
c.GWC支持在第一次请求地图某范围时，将此范围内的地图按照配置的信息进行切图缓存。第二次同样请求此范围的地图时，直接读取缓存瓦片进行加速显示。此功能类似于AGS的动态出图。
d.GWC同时也支持预先将瓦片按照配置信息切完，地图加载时直接读取瓦片。此功能类似于AGS的瓦片缓存出图。
## 3.具体配置
由于我所用的Geoserver本身自带有此功能，所以配置相对容易。
### 3.1配置瓦片存放地址
在GeoServer的web.xml文件中加上如下配置，便可以控制瓦片存放的目录：
### 3.2瓦片详细信息配置
当我们配置好3.1中的地址项后，重启tomcat，可以发现在指定的瓦片存放文件夹下产生了这样三个文件：
其中的GeoWebCache.xml便是瓦片的详细配置文档。此配置项在支持使用其他来源的瓦片进行显示上非常重要。不过，目前Geoserver中的集成版本不支持此功能，GeoWebCache的独立版本可以支持，在以后的章节里跟我跟大家一起探讨此功能。
## 4.切图操作
### 4.1.进入gwc页面
启动tomcat后，在浏览器中直接输入http://localhost:8680/geoserver/gwc/，可进入如下页面：
### 4.2选择需要切图的服务
点击list选项，可以看到能够进行切图的服务：
### 4.3进行预切图（非必须）
如果想实现类似于AGS中预先将所有瓦片全部进行切图的效果，可以点击要进行切图的图层下的Seed this layer：
点击Submit后，开始进行预切图，在页面中可以看到切图进程：
在瓦片缓存目录下可以看到切图结果：
**注意**：在切图页面上，也可以停止切图进程：
## 5.使用切图服务探究
### 5.1如果我们的WMS请求为一般性url，是否可以自动开启瓦片缓存服务？——不能
点击Geoserver中的layer preview，查看某一图层，某一URL为：http://localhost:8680/geoserver/wms?LAYERS=tilelayer&STYLES=&FORMAT=image%2Fpng&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS=EPSG%3A4326&BBOX=104.07920033743,30.648478876565,104.08458074933,30.652787409535&WIDTH=512&HEIGHT=410。
效果如下：
查看我们的瓦片缓存文件，并没有任何跟改图层服务相关的瓦片缓存生成：
### 5.2使用特殊的WMS的url，是否可以自动开启瓦片缓存服务？——可以
点击此项中的png，在弹出的页面中放大缩小，某一URL为：http://localhost:8680/geoserver/gwc/service/wms?LAYERS=urbanlayer%3Atilelayer&FORMAT=image%2Fpng&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&STYLES=&SRS=EPSG%3A4326&BBOX=104.1943359375,30.5419921875,104.23828125,30.5859375&WIDTH=256&HEIGHT=256
效果如下：
此时，在瓦片缓存文件夹中我们可以明显的看到生成的对应缓存：
### 5.3由以上例子总结
对比以上两个服务的url：
http://localhost:8680/geoserver/wms
http://localhost:8680/geoserver/gwc/service/wms
可以看见两者的区别仅仅在于，当请求的URL中加上gwc/service后，便可以开启瓦片缓存服务了。
## 6.可能存在的问题
### 6.1效率问题
如果使用动态切图，即非预切图。当需要切图的数据（图层或图层组）很大时，会不会地图第一次显示比较慢？
### 6.2切图效果失真问题
网上有人提出这样一个问题：问题是GeoWebCache切片后的图片质量降低，缩放的时候图片像素都拥挤在一起，没有像windows图片查看器或者ps那样缩小的图片还那样保持清晰。
原图：
GWC瓦片：
**注意：**针对此问题，有网友给出了解决方案：尝试使用maptiler切片工具，不过 maptiler工具有局限，无法整合多张图后一起切图。 | 30.219512 | 270 | 0.76056 | yue_Hant | 0.874971 |
4bb94e12541b997a052880e7abb74fab5a09561f | 1,101 | md | Markdown | CONTRIBUTING.md | Iraecio/laravel-selfupdater | b19c86a9eda1b0b67e8041592b52715735f387a4 | [
"MIT"
] | 238 | 2016-08-03T21:24:53.000Z | 2022-03-29T21:09:00.000Z | CONTRIBUTING.md | Iraecio/laravel-selfupdater | b19c86a9eda1b0b67e8041592b52715735f387a4 | [
"MIT"
] | 219 | 2016-08-03T22:38:15.000Z | 2022-03-25T13:41:03.000Z | CONTRIBUTING.md | Iraecio/laravel-selfupdater | b19c86a9eda1b0b67e8041592b52715735f387a4 | [
"MIT"
] | 70 | 2016-11-09T01:26:33.000Z | 2022-03-26T08:21:43.000Z | # Contributing
Contributions are welcome, and are accepted via pull requests.
Please review these guidelines before submitting any pull requests.
- Please follow the [PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)
and [PHP-FIG Naming Conventions](https://github.com/php-fig/fig-standards/blob/master/bylaws/002-psr-naming-conventions.md).
- Remember to follow [SemVer](http://semver.org). If you are changing the behavior,
or the public api, you may need to update the docs.
- Make sure that the current tests pass, and if you have added something new, add the tests where relevant.
- Send a coherent commit history, making sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [squash](http://git-scm.com/book/en/Git-Tools-Rewriting-History) them before submitting.
- You may also need to [rebase](http://git-scm.com/book/en/Git-Branching-Rebasing) to avoid merge conflicts.
StyleCI is set up to automatically check and fix any code style issues.
| 78.642857 | 267 | 0.787466 | eng_Latn | 0.988167 |
4bb995c74fb91956cfe59b8c68f6f090b63dd685 | 725 | md | Markdown | README.md | ouyangshangwen/lemon | fa326fd9ef636badf64e91baa42cd9e1d4d41cda | [
"Apache-2.0"
] | 3 | 2015-05-29T07:08:40.000Z | 2018-03-22T07:09:05.000Z | README.md | ouyangshangwen/lemon | fa326fd9ef636badf64e91baa42cd9e1d4d41cda | [
"Apache-2.0"
] | null | null | null | README.md | ouyangshangwen/lemon | fa326fd9ef636badf64e91baa42cd9e1d4d41cda | [
"Apache-2.0"
] | null | null | null | Lemon Web Server
=======
lemon 是go语言开发的web框架，是对``net/http``的简单封装，它的设计完全来自于python 的web框架tornado，同时在beego，revel中吸收了一些思想。
lemon的设计目标，设计最小，最精简的框架，所有无关的部分，采用组件的形式使用。
简单的web应用
-------
这是一个简单的 “Hello World“ web 应用
```
package main
import (
"github.com/ouyangshangwen/lemon"
)
func main() {
settings := map[string]interface{}{
"IsGzip": false,
"NUMCPU": 8,
}
handlers := []lemon.UrlSpec{
lemon.AddRouter("/", &HelloWorldHandler{}, lemon.NullDictionary(), ""),
}
server := lemon.NewLemon().Instance(handlers, settings)
server.Listen("", 8080)
server.Loop()
}
type HelloWorldHandler struct {
lemon.RequestHandler
}
func (hw *HelloWorldHandler) Get(_ ...string) {
hw.WriteString("Hello, world")
}
```
| 16.860465 | 93 | 0.688276 | yue_Hant | 0.411066 |
4bba050cbe34a045c45a1b901ebac05e0612752f | 5,221 | markdown | Markdown | _posts/2008-10-28-asp-net-mvc-captcha.markdown | hackerhasid/hackerhasid.github.io | 404eabe0275c5f7e8ec607849c04adcbd86bdc81 | [
"MIT"
] | null | null | null | _posts/2008-10-28-asp-net-mvc-captcha.markdown | hackerhasid/hackerhasid.github.io | 404eabe0275c5f7e8ec607849c04adcbd86bdc81 | [
"MIT"
] | null | null | null | _posts/2008-10-28-asp-net-mvc-captcha.markdown | hackerhasid/hackerhasid.github.io | 404eabe0275c5f7e8ec607849c04adcbd86bdc81 | [
"MIT"
] | null | null | null | ---
layout: post
status: publish
published: true
title: ASP.NET MVC Captcha
author: noah
author_login: noah
author_email: noah@statichippo.com
wordpress_id: 183
wordpress_url: http://statichippo.com/blog/archive/2008/10/28/asp.net-mvc-captcha.aspx
date: 2008-10-28 21:53:00.000000000 -04:00
categories:
- ASP.NET
tags: []
comments: []
---
I was looking for an ASP.NET MVC Captcha control and stumbled upon Nick Berardi's ([http://www.coderjournal.com/2008/06/mvc-captcha-for-preview-release-3/](http://www.coderjournal.com/2008/06/mvc-captcha-for-preview-release-3/)).
First of all I'm using IIS7 and had trouble getting the HttpHandler to register properly. I ended up with the following steps to get it to work:
1. Add <add verb="GET" path="captcha.ashx" validate="false" type="ManagedFusion.Web.Handlers.CaptchaImageHandler, ManagedFusion.Web.Captcha" /> to <httphandlers> in Web.config </httphandlers>
2. Add <add name="CaptchaImageHandler" verb="GET" path="captcha.ashx" type="ManagedFusion.Web.Handlers.CaptchaImageHandler, ManagedFusion.Web.Captcha" /> to the <handlers> section within <system.webserver> in Web.config </system.webserver></handlers>
3. Add routes.IgnoreRoute("{handler}.ashx"); to Global.asax
### So that got it working, but there were a few pieces of functionality I felt were missing:
#### 1) I wanted the ability to style the CaptchaTextBox
The site I'm working with is pretty design intensive and I needed a way to inject CSS information into the CaptchaTextBox Html Helper. I reworked the CaptchaHelper and modified the CaptchaTextBox as well as added some overloads:
{% highlight csharp %}
public static string CaptchaTextBox(this HtmlHelper helper, string name)
{
return helper.CaptchaTextBox(name, null);
}
public static string CaptchaTextBox(this HtmlHelper helper, string name, Object htmlAttributes)
{
return helper.CaptchaTextBox(name, ((IDictionary<string, object>)new RouteValueDictionary(htmlAttributes)));
}
public static string CaptchaTextBox(this HtmlHelper helper, string name, IDictionary<String, Object> htmlAttributes)
{
ModelState state;
TagBuilder builder = new TagBuilder("input");
builder.MergeAttributes<string, object>(htmlAttributes);
builder.MergeAttribute("type", "text");
builder.MergeAttribute("name", name);
builder.MergeAttribute("id", name);
builder.MergeAttribute("value", "");
builder.MergeAttribute("maxlength", ManagedFusion.Web.Controls.CaptchaImage.TextLength.ToString());
builder.MergeAttribute("autocomplete", "off");
if (helper.ViewData.ModelState.TryGetValue(name, out state) && (state.Errors.Count > 0))
{
builder.AddCssClass("input-validation-error");
}
return builder.ToString(TagRenderMode.SelfClosing);
}
{% endhighlight %}
I got the TagBuilder idea from checking out the Reflector on System.Web.MVC. Pretty cool stuff there. So now I can use the CaptchaTextBox like so:
`<%= Html.CaptchaTextBox("captcha", new { @class = "field" })%>`
#### 2) I wanted the CaptchaValidationAttribute to invalidate my Model if the captcha isn't valid
(instead of inject a captchaValid with a value of false into my routedata which is what it does off the shelf)
For this I modified the CaptchaValidationAttribute class. The first thing I did was make add an ErrorMessage string property. Then I modified the OnActionExecutingContext method to look like this:
{% highlight csharp %}
public override void OnActionExecuting(ActionExecutingContext filterContext)
{
// get the guid from the post back
string guid = filterContext.HttpContext.Request.Form["captcha-guid"];
// check for the guid because it is required from the
//rest of the opperation
if (String.IsNullOrEmpty(guid))
{
filterContext.Controller.ViewData.ModelState.AddModelError(Field, ErrorMessage);
return;
}
// get values
CaptchaImage image = CaptchaImage.GetCachedCaptcha(guid);
string actualValue = filterContext.HttpContext.Request.Form[Field];
string expectedValue = image == null ? String.Empty : image.Text;
// removes the captch from cache so it cannot be used again
filterContext.HttpContext.Cache.Remove(guid);
// validate the captch
if (String.IsNullOrEmpty(actualValue) || String.IsNullOrEmpty(expectedValue) || !String.Equals(actualValue, expectedValue, StringComparison.OrdinalIgnoreCase))
{
filterContext.Controller.ViewData.ModelState.AddModelError(Field, ErrorMessage);
return;
}
{% endhighlight %}
Now I can use the CaptchaValidationAttribute like this:
{% highlight csharp %}
[CaptchaValidationAttribute()]
public ActionResult Register(FormCollection form)
{
// INCREDIBLY OVER-SIMPLIFIED BUT YOU GET THE IDEA
if (!ViewData.ModelState.IsValid)
return View();
}
}
{% endhighlight %} | 45.4 | 254 | 0.696227 | eng_Latn | 0.620919 |
4bbc1d8ff00271b12d50ee61b1e1bf386f321a57 | 5,351 | md | Markdown | articles/azure-monitor/vm/vminsights-health-alerts.md | tokawa-ms/azure-docs.ja-jp | c1db876db6cde4ac449e959e3bfe39f941660f8a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/vm/vminsights-health-alerts.md | tokawa-ms/azure-docs.ja-jp | c1db876db6cde4ac449e959e3bfe39f941660f8a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/vm/vminsights-health-alerts.md | tokawa-ms/azure-docs.ja-jp | c1db876db6cde4ac449e959e3bfe39f941660f8a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: VM insights のゲストの正常性アラート (プレビュー)
description: VM insights のゲストの正常性によって作成されるアラートについて、それを有効にする方法と通知を構成する方法を含めて説明します。
ms.topic: conceptual
author: bwren
ms.author: bwren
ms.date: 11/10/2020
ms.openlocfilehash: 1b5fd10b3e0bd84aa7d34a918f4f2376130d2e45
ms.sourcegitcommit: f3ec73fb5f8de72fe483995bd4bbad9b74a9cc9f
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 03/04/2021
ms.locfileid: "102052264"
---
# <a name="vm-insights-guest-health-alerts-preview"></a>VM insights のゲストの正常性アラート (プレビュー)
VM insights のゲストの正常性を使用すると、一定間隔でサンプリングされる一連のパフォーマンス測定値によって定義される、仮想マシンの正常性を表示できます。 アラートは、仮想マシンまたはモニターが異常な状態に変化するときに作成されます。 [Azure Monitor のアラート ルールによって作成されるもの](../alerts/alerts-overview.md)を含むこれらのアラートを表示して管理し、新しいアラートが作成されたときに事前に通知されるように選択できます。
## <a name="configure-alerts"></a>アラートを構成する
この機能がプレビュー段階の間は、VM insights のゲストの正常性に対して明示的なアラート ルールを作成することはできません。 既定では、アラートはモニターごとではなく、各仮想マシンに対して作成されます。 これは、モニターが仮想マシンの現在の状態に影響を与えない状態に変化した場合、仮想マシンの状態が変化しなかったためにアラートが作成されないことを意味します。
特定の仮想マシンまたは仮想マシン上の特定のモニターに対するアラートは、Azure portal の仮想マシンの構成にある **[アラートの状態]** 設定から無効にできます。 Azure portal でモニターを構成することの詳細については、「[VM insights のゲストの正常性 (プレビュー) で監視を構成する](vminsights-health-configure.md)」を参照してください。 一連の仮想マシンにわたってモニターを構成することの詳細については、「[データ収集ルールを使用して VM insights のゲストの正常性 (プレビュー) での監視を構成する](vminsights-health-configure-dcr.md)」を参照してください。
## <a name="alert-severity"></a>アラートの重大度
ゲストの正常性によって作成されるアラートの重要度は、アラートをトリガーしている仮想マシンまたはモニターの重要度に直接マッピングされています。
| モニター状態 | アラートの重大度 |
|:---|:---|
| Critical | Sev1 |
| 警告 | Sev2 |
| Healthy | Sev4 |
## <a name="alert-lifecycle"></a>アラートのライフサイクル
[Azure のアラート](../alerts/alerts-overview.md)は、各仮想マシンが **警告** または **クリティカル** の状態に変化するときはいつでも作成されます。 アラートは、Azure portal の、 **[Azure Monitor]** メニューまたは仮想マシンのメニューの **[アラート]** から表示します。
仮想マシンの状態が変化したときにアラートが既に **発生** 状態になっている場合、2 番目のアラートは作成されませんが、同じアラートの重要度は仮想マシンの状態に合わせて変更されます。 たとえば、**警告** アラートが既に **発生** 状態にあったときに、仮想マシンが **クリティカル** 状態に変化した場合、そのアラートの重要度は **Sev1** に変更されます。 **Sev1** アラートが既に **発生** 状態にあったときに、仮想マシンが **警告** 状態に変化した場合、そのアラートの重要度は **Sev2** に変更されます。 仮想マシンが **正常** 状態に戻った場合、重要度が **Sev4** に変更されてアラートは解除されます。
## <a name="viewing-alerts"></a>アラートの表示
[Azure portal](../platform/alerts-overview.md#alerts-experience) で、VM insights のゲストの正常性によって作成されたアラートを他の アラートと共に表示します。 **[Azure Monitor]** メニューから **[アラート]** を選択して、すべての監視対象リソースのアラートを表示するか、仮想マシンのメニューから **[アラート]** を選択して、その仮想マシンについてのみアラートを表示することができます。
## <a name="alert-properties"></a>[アラートのプロパティ]
### <a name="properties-in-the-azure-portal"></a>Azure portal でのプロパティ
次の表で、Azure portal で表示したときのアラートのプロパティについて説明します。
| プロパティ | Description |
|:---|:---|
| アラートが作成される前のモニター状態 | このアラートが初めて発生する前のモニターまたは仮想マシンの状態。 |
| アラートが作成されたときのモニター状態 | アラートが初めて発生したときのモニターまたは仮想マシンの状態。 これが、アラートが発生する原因となった状態です。 |
| アラートが作成されたときの状態遷移に関する詳細を確認するには | 正確な状態遷移を確認できる [VM の正常性] ページへのリンク。 この状態遷移は、モニターが最初に **正常** 状態から正常でない状態になったときのインスタンスを表しています。 |
たとえば、あるモニターが、時刻 t0 に **健全** から **クリティカル** に移行し、**Sev1** の新しいアラートが発生します。 次に、時刻 t1 に **クリティカル** から **警告** に移行し、アラートの重要度が **Sev2** に更新されます。 時刻 t2 には **正常** になり、アラートが解除されます。
このシーケンス全体の間に、アラートのプロパティ値は次のようになります。
- アラートが作成される前のモニター状態:Healthy
- アラートが作成されたときのモニター状態:Critical
- アラートが作成されたときの状態遷移に関する詳細を確認するには:時刻 t0 に発生した状態遷移へのナビゲーション リンク。
### <a name="properties-in-notifications"></a>通知内のプロパティ
次の表で、通知に含まれるアラートのプロパティについて説明します。
| プロパティ | Description |
|:---|:---|
| 以前のモニター状態 | 状態が変化する前のモニターまたは仮想マシンの状態。 アラートの重要度の更新によってこの通知がトリガーされる場合、このプロパティは、重要度更新の直前の状態を表します。 |
| 現在のモニター状態 | 状態が変化したときのモニターまたは仮想マシンの状態。 アラートの重要度の更新によってこの通知がトリガーされる場合、このプロパティは、新しい状態を表します。 |
| この状態遷移に関する詳細を確認するには | 正確な状態遷移を確認できる [VM の正常性] ページへのリンク。 この状態遷移は、この通知をトリガーした状態がモニターによって変更されたときのインスタンスを表します。 |
上の例を使用すると、それぞれの時点で、通知には以下のプロパティが含まれます。
時刻 t0 に受信した通知
- 以前のモニター状態:Healthy
- 現在のモニター状態:Critical
- この状態遷移に関する詳細を確認するには:時刻 t0 に発生した状態遷移へのナビゲーション リンク。
時刻 t1 に受信した通知
- 以前のモニター状態:Critical
- 現在のモニター状態:警告
- この状態遷移に関する詳細を確認するには:時刻 t1 に発生した状態遷移へのナビゲーション リンク。
時刻 t2 に受信した通知
- 以前のモニター状態:警告
- 現在のモニター状態:Healthy
- この状態遷移に関する詳細を確認するには:時刻 t2 に発生した状態遷移へのナビゲーション リンク。
## <a name="configure-notifications"></a>通知の構成
ゲストの正常性によってトリガーされるアラートの通知を事前に受け取るには、[アクション グループ](../alerts/action-groups.md) を作成して、SMS メッセージの送信やロジック アプリの起動などを実行するさまざまなアクションを定義します。 次に、モニターや仮想マシンのスコープを指定し、そのアクション グループを使用する[アクション ルール](../alerts/alerts-action-rules.md) を作成します。
Azure portal の **[モニター]** メニューで、 **[アラート]** を選択します。 **[アクションの管理]** を選択してから、 **[アクション ルール (プレビュー)]** を選択します。
**[新しいアクション ルール]** をクリックして新しいルールを作成します。 スコープの横にある **[選択]** をクリックして、サブスクリプション、リソース グループ、または 1 つ以上の特定の仮想マシンを選択します。 通知は、スコープ内にある仮想マシンに対してのみ発生します。
**[フィルター]** の横にある **[追加]** をクリックします。 **[モニター サービス] [と等しい] [VM Insights-正常]** というフィルターを作成します。 その他のフィルターを追加して、通知をトリガーする必要がある特定のアラートを指定します。 たとえば **[重要度]** を使用して、特定の重要度に一致するすべてのモニターからのアラートを照合できます。
**[このスコープでの定義]** で **[アクション グループ]** を選択してから、モニターに関連付けるアクション グループを選択します。 ルールに名前を付けて、その保存場所にするリソース グループを選択します。 **[作成]** をクリックしてルールを作成します。
## <a name="next-steps"></a>次のステップ
- [VM insights とオンボード エージェントでゲストの正常性を有効にします。](vminsights-health-enable.md)
- [Azure portal を使用してモニターを構成します。](vminsights-health-configure.md)
- [データ収集ルールを使用してモニターを構成します。](vminsights-health-configure-dcr.md) | 48.645455 | 341 | 0.786769 | jpn_Jpan | 0.754707 |
4bbcc7259862daa7bedbe1a9f5eb376f533b93e3 | 20,114 | md | Markdown | powerapps-docs/developer/data-platform/scalable-customization-design/database-transactions.md | rspannuth/powerapps-docs | 6c6548ce9883c16df3cfedf63d0917f71ffd87e1 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-07-13T07:06:52.000Z | 2021-07-13T07:06:52.000Z | powerapps-docs/developer/data-platform/scalable-customization-design/database-transactions.md | ManuSquall/powerapps-docs | 03b397e8433de3383648e5dea9178163380890d0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | powerapps-docs/developer/data-platform/scalable-customization-design/database-transactions.md | ManuSquall/powerapps-docs | 03b397e8433de3383648e5dea9178163380890d0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Scalable Customization Design: Database Transactions (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
description: "The second in a series of topics. This topic focuses on the impact of database transactions on scalable customization design" # 115-145 characters including spaces. This abstract displays in the search result.
ms.custom: ""
ms.date: 1/15/2019
ms.reviewer: "pehecke"
ms.service: powerapps
ms.topic: "article"
author: "rogergilchrist" # GitHub ID
ms.author: "jdaly" # MSFT alias of Microsoft employees only
manager: "ryjones" # MSFT alias of manager or PM counterpart
search.audienceType:
- developer
search.app:
- PowerApps
- D365CE
---
# Scalable Customization Design: Database transactions
[!INCLUDE[cc-data-platform-banner](../../../includes/cc-data-platform-banner.md)]
> [!NOTE]
> This is the second in a series of topics about scalable customization design. To start at the beginning, see [Scalable Customization Design in Microsoft Dataverse](overview.md).
One of the most fundamental concepts behind many of the challenges faced here is that of the database transaction. In Dataverse the database is at the heart of almost all requests to the system and the place data consistency is primarily enforced.
- No Dataverse data operations, either internal or part of code customizations, work completely in isolation.
- All Dataverse data operations interact with the same database resources, either at a data level or an infrastructure level such as processor, memory, or I/O usage.
- To protect against conflicting changes, each request takes locks on resources to be viewed or changed.
- Those locks are taken within a transaction and not released until the transaction is committed or aborted.
## Transaction and locking awareness
A common reason that problems can occur in this area is the lack of awareness of how customizations can affect transactions.
Although the details of how this is done is beyond the scope of this topic, the most simple element to consider is that as Dataverse interacts with data in its database. SQL Server determines the appropriate locks to be taken by transactions on that data such as:
- When retrieving a particular record, SQL Server takes a read lock on that record.
- When retrieving a range of records, in some scenarios it can take a read lock on that range of records or the entire table.
- When creating a record, it generates a write lock against that record.
- When updating a record, it takes a write lock against the record.
- When a lock is taken against a table or record, it’s also taken against any corresponding index records.
However, it’s possible to influence the scope and duration of these locks. It’s also possible to indicate to SQL Server that no lock is required for certain scenarios.
Let’s consider SQL Server database locking and the impact of separate requests trying to access the same data. In the following example, creating an account has set up a series of processes, some with plug-ins that are triggered as soon as the record is created, and some in a related asynchronous workflow that is initiated at creation.
The example shows the consequences when an account update process has complex post processing while other activity also interacts with the same account record. If an asynchronous workflow is processed while the account update transaction is still in progress, this workflow could be blocked waiting to obtain an update lock to change the same account record, which is still locked.
It should be noted that transactions are only held within the lifetime of a particular request to the platform.
Locks aren’t held at a user session level or while information is being shown in the user interface. As soon as the platform has completed the request, it releases the database connection, the related transaction, and any locks it has taken.
## Blocking
While the kind of blocking in the previous example can be inconvenient in and of itself, this can also lead to more serious consequences when you consider that Dataverse is a platform that can process hundreds of concurrent actions. While holding a lock on an individual account record may have reasonably limited implications, what happens when a resource is more heavily contested?
For example, when each account is given a unique reference number it may lead to a single resource that is tracking the used reference numbers being blocked by every account creation process. As described in the [Auto-numbering example](auto-numbering-example.md), if a lot of accounts are generated in parallel, overlapping requests will all need to access that auto-numbering resource and will block it until they complete their action. The longer each account creation process takes, and the more concurrent requests there are, the more blocking occurs.
While the first request to grab the auto-number resource lock can easily be completed, the second request will need to wait for the first to complete before it can check what the next unique reference number is. The third request will have to wait for both the first and second requests to complete. The more requests there are, the longer blocking will occur. If there are enough requests, and each request takes long enough, this can push the later requests to the point that they time out, even though individually they may complete correctly.
## Lock release
There are two primary reasons why a lock isn’t released but is held until the transaction is completed:
- The database server holds onto the lock for consistency in case the transaction will later make another request to update the data item.
- The database server also has to allow for the fact that an error or abort command issued later can cause it to roll the entire transaction back, so it needs to hold onto the locks for the entire lifetime of the transaction to ensure consistency.
It is important to recognize that even though your process may have completed any interactions with a particular piece of data, the lock will be held until the entire transaction is complete and committed. The longer the transaction is extended, the longer the lock will be held, preventing other threads from interacting with that data.
As will be shown later, this also includes related customizations that work within the same transaction and can significantly extend the lifetime of transactions such as synchronous workflows.
In the following example, the write lock on a custom entity in the pre create plug-in for an account is locked until all logic tied to the creation of the account is completed.
## Intermittent errors: timing
Intermittent behavior is an obvious symptom of blocking from concurrent activity. If repeating exactly the same action later succeeds when earlier it failed, there is a very strong likelihood that the error or slowness was caused by something else occurring at the same time.
That is important to realize as debugging a problem often involves stripping the offending functionality back to the bare minimum. However, when the problem only occurs intermittently, you may need to look at where the failing action is conflicting with another activity in the system, and you need to look at potential contention points. You can mitigate conflict by optimizing an individual process; however, the shorter the processing time, the less likely the activity will conflict with other processes.
## Transaction control
While in most cases the way transactions are used can simply be left to the platform to manage, there are scenarios where the logic needed is complex enough that understanding and influence over transactions is required to achieve the desired results. Dataverse offers a number of different customization approaches that impact differently on the way transactions are used.
When you understand how each type of customization participates in the platform transactions, you can model complex scenarios effectively in Dataverse and predict their behavior.
As mentioned earlier, a transaction is only held during the lifetime of a request to the platform, it is not something that is maintained once the platform step is completed. This avoids transactions being held by an external client for long periods and blocking other platform activities.
The job of the platform is to maintain consistency throughout the platform transaction pipeline and where appropriate allow customizations to participate in that same transaction.
## How Model-driven Apps use transactions
Before understanding how customizations interact with the platform, it is useful to understand how model-driven apps use requests to the platform, and how it affects transaction use.
|Operation|Description|
|--|--|
|Forms (Retrieve)|• Takes a read lock on the record shown.<br />• Low impact on other uses.|
|Create|• Performs a create request through the platform<br />• Low impact on other activities, as a new record nothing else blocking on it<br />• Can potentially block locking queries to the whole table until it is complete.<br />• Often can trigger related actions in customization which can have an impact.|
|Update|• Performs an update request through the platform.<br />• More likely to have conflicts. An update lock will block anything else updating or reading that record. Also blocks anything taking a broad read lock on that table.<br />• Often triggers other activities.|
|View (RetrieveMultiple)|• Would think this would block lots of other activity.<br />• But deliberately passes `nolock` hints to queries<br />• So typically does not lock other activities.<br />• Although poor query optimization can affect DB resource usage and possibly hit timeouts.|
## Event pipeline: platform step
When an event pipeline is initiated, a SQL transaction is created to include the platform step. This ensures that all database activity performed by the platform is acted on consistently. The transaction is created at the start of the event pipeline and either committed or aborted when the processing is completed, depending on whether it was successful.
## Customization requests
It’s also possible to participate in the platform initiated transaction within customizations. Each type of customization participates in transactions in a different way. The following sections will describe each in turn.
- [Sync plug-ins (pre or post operation: in transaction context)](#sync-plug-ins-pre-or-post-operation-in-transaction-context)
- [Sync plug-ins (pre and post operation: in transaction context)](#sync-plug-ins-pre-and-post-operation-in-transaction-context)
- [Sync plug-ins (**PreValidation**: outside transaction context)](#sync-plug-ins-prevalidation-outside-transaction-context)
- [Sync plug-ins (**PreValidation**: in transaction context)](#sync-plug-ins-prevalidation-in-transaction-context)
- [Async plug-ins](#async-plug-ins)
- [Plug-in transaction use summary](#plug-in-transaction-use-summary)
- [Synchronous workflows](#synchronous-workflows)
- [Asynchronous workflows](#asynchronous-workflows)
- [Custom workflow activity](#custom-workflow-activity)
- [Custom actions](#custom-actions)
- [Web service requests](#web-service-requests)
### Sync plug-ins (pre or post operation: in transaction context)
When plug-ins are registered for an event, they can be registered against a **PreOperation** or **PostOperation** stage that is within the transaction. Any message requests from the plug-in will be performed within the transaction. This means the lifetime of the transaction, and any locks taken, will be extended.
### Sync plug-ins (pre and post operation: in transaction context)
Plug-ins can be registered against both the **PreOperation** and **PostOperation** stages. In this case the transaction can extend even further because it will extend from the start of the **PreOperation** plug-in until the **PostOperation** plug-in completes.
### Sync plug-ins (**PreValidation**: outside transaction context)
A plug-in can also be registered to act outside of the platform transaction by being registered on the **PreValidation** stage.
> [!NOTE]
> It does NOT create its own transaction. As a result, each message request within the plug-in is acted upon independently within the database.
This scenario only applies when the **PreValidation** is called as the first stage of a pipeline event . Even though the plug-in is registered on the **PreValidation** stage, it is possible it will participate in a transaction as the next section describes. It can’t be assumed that a **PreValidation** plug-in doesn’t participate in a transaction, although it is possible to check from the execution context if this is the case.
### Sync plug-ins (**PreValidation**: in transaction context)
The related scenario occurs when a **PreValidation** plug-in is registered but the related pipeline event is triggered by message request from within an existing transaction.
As the following diagram shows, creating an account can cause a **PreValidation** plug-in to perform initially outside of a transaction when the initial create is performed. If, as part of the post plug-in, a message request is made to create a related child account because that second event pipeline is initiated from within the parent pipeline, it will participate in the same transaction.
In that case, the **PreValidation** plug-in will discover that a transaction already exists and so will participate in that transaction even though it’s registered on the **PreValidation** stage.
As previously mentioned, the plug-in can check the execution context for the <xref:Microsoft.Xrm.Sdk.IExecutionContext.IsInTransaction> property, which will indicate if this plug-in is performing within a transaction or not.
### Async plug-ins
A plug-in can also be registered to act asynchronously. In this case, the plug-in also acts outside of the platform transaction.
> [!NOTE]
> The plug-in doesn’t create its own transaction; each message request within the plug-in is acted upon independently.
### Plug-in transaction use summary
To summarize:
- Synchronous plug-ins typically participate in transactions.
- Async plug-ins never participate in a platform transaction; each request is performed independently.
- **PreValidation** plug-ins don’t create a transaction but participate if one already exists.
|Event|Stage name|Transaction does not yet exist|Transaction already exists|
|--|--|--|--|
|Pre-Event|**PreValidation**|No transaction is created. Does not participate in transaction; each request uses independent transaction to the database|Participates in existing transaction|
|Pre-Event|**PreOperation**|Participates in existing transaction|Participates in existing transaction|
|Post-Event|**PostOperation**|Participates in existing transaction|Participates in existing transaction|
|Async|N/A|No transaction is created. Does not participate in transaction; each request uses independent transaction to the database|N/A|
### Synchronous workflows
From the perspective of transactions, synchronous workflows act as pre/post operation plug-ins. They therefore act within the platform pipeline transaction and can have the same effect on the length of the overall transaction.
### Asynchronous workflows
Asynchronous workflows are triggered outside of the platform transaction.
> [!NOTE]
> The workflow also does NOT create its own transaction and therefore each message request within the workflow is acted upon independently.
The following diagram shows the asynchronous workflow acting outside of the platform transaction and each step initiating its own independent transaction.
### Custom workflow activity
Custom workflow activities act within the parent workflow context.
- Sync workflow: Acts within the transaction
- Async workflow: Acts outside the transaction
The following diagram shows custom activities first acting within a synchronous workflow and then within an asynchronous workflow.
### Custom actions
Custom actions can create their own transactions. This is a key feature. A custom action can create a separate transaction outside of the platform step depending on whether it is configured to Enable Rollback.
- Enable Rollback set
- If called through a message request from a plug-in running within the transaction, and Enable Rollback is set, the custom action will act within the existing transaction.
- The custom action will otherwise create a new transaction and run within that.
- Enable Rollback not set
- The custom action won’t act within a transaction.
### Web service requests
When requests are made externally through web services, a pipeline is created and transaction handling within the pipeline occurs as previously discussed, but a transaction is not maintained once the response is returned. Since how long it will be until the next request is an unknown, the platform does not allow locking of resources which would block other activities.
When multiple requests are made within a plug-in using the same execution context, it is the common execution context that maintains the transaction reference and in synchronous plug-ins ensures each request is made within the same transaction. The ability to maintain an execution context across requests is not available outside of plug-ins and therefore a transaction cannot be maintained across separate requests made externally.
There are two special messages where multiple actions can be passed to the Dataverse platform as part of a single web service request.
|Message|Description|
|--|--|
|`ExecuteMultiple`|This allows multiple independent actions to be passed within the same web service request. Each of these requests is performed independently within the platform so there is no transaction context held between requests.|
|`ExecuteTransaction`|This allows multiple actions to be processed within the same database transaction, in a similar way to multiple message requests made from within a synchronous plug-in.<br /> <br />This ability would also have implications similar to multiple message requests; that is, if each action takes a long time (such as by making expensive queries or triggering a long chain of related synchronous plug-ins or workflows) this could lead to blocking issues in the broader platform.|
#### Web API (OData) Requests in plug-ins
Do not use Web API (OData) requests within a plug-in to the same organization as the plug-in. Always use the <xref:Microsoft.Xrm.Sdk.IOrganizationService> methods. This allows for the transaction context to be passed so that the operation can participate in the pipeline transaction.
## Next steps
In addition to database transactions, it is important to appreciate the impact of multiple concurrent data operations can have on the system. More information: [Scalable Customization Design: Concurrency issues](concurrency-issues.md)
[!INCLUDE[footer-include](../../../includes/footer-banner.md)] | 79.501976 | 556 | 0.799145 | eng_Latn | 0.999025 |
4bbd01187a632842c5c4fe26e00b29713175e57e | 13,035 | md | Markdown | src/site/content/en/blog/optimize-fid/index.md | JackJey/web.dev | 93b79df17c35aec60233cdae242f72c5f3458c71 | [
"Apache-2.0"
] | null | null | null | src/site/content/en/blog/optimize-fid/index.md | JackJey/web.dev | 93b79df17c35aec60233cdae242f72c5f3458c71 | [
"Apache-2.0"
] | null | null | null | src/site/content/en/blog/optimize-fid/index.md | JackJey/web.dev | 93b79df17c35aec60233cdae242f72c5f3458c71 | [
"Apache-2.0"
] | null | null | null | ---
title: Optimize First Input Delay
subhead: How to respond faster to user interactions.
authors:
- houssein
- addyosmani
date: 2020-05-05
hero: image/admin/WH0KlcJXJlxvsxU9ow2i.jpg
alt: A hand touching a smartphone screen
description: |
First Input Delay (FID) measures the time from when a user first interacts with your site
to the time when the browser is actually able to respond to that interaction. Learn how to
optimize FID by minimizing unused JavaScript, breaking up Long Tasks, and improving interaction
readiness.
tags:
- blog
- performance
- web-vitals
---
<blockquote>
<p>
I clicked but nothing happened! Why can't I interact with this page? 😢
</p>
</blockquote>
[First Contentful Paint](/fcp/) (FCP) and [Largest Contentful
Paint](/lcp/) (LCP) are both metrics that measure the time it takes for content to
visually render (paint) on a page. Although important, paint times do not capture _load
responsiveness_: or how quickly a page responds to user interaction.
[First Input Delay](/fid/) (FID) is a [Core Web Vitals](/vitals/) metric that captures a user's
first impression of a site's interactivity and responsiveness. It measures the time from when a user
first interacts with a page to the time when the browser is actually able to respond to that
interaction. FID is a [field metric](/user-centric-performance-metrics/#in-the-field) and cannot be
simulated in a lab environment. **A real user interaction** is required in order to measure the
response delay.
<picture>
<source srcset="{{ "image/tcFciHGuF3MxnTr1y5ue01OGLBn2/eXyvkqRHQZ5iG38Axh1Z.svg" | imgix }}" media="(min-width: 640px)">
{% Img src="image/tcFciHGuF3MxnTr1y5ue01OGLBn2/Se4TiXIdp8jtLJVScWed.svg", alt="Good fid values are 2.5 seconds, poor values are greater than 4.0 seconds and anything in between needs improvement", width="384", height="96" %}
</picture>
To help predict FID in the [lab](/how-to-measure-speed/#lab-data-vs-field-data), we
recommend [Total Blocking Time (TBT)](/tbt/). They measure different things, but
improvements in TBT usually correspond to improvements in FID.
The main cause of a poor FID is **heavy JavaScript execution**. Optimizing how JavaScript parses,
compiles, and executes on your web page will directly reduce FID.
## Heavy JavaScript execution
The browser cannot respond to most user input while it's executing JavaScript on the main thread. In other words, the
browser can't respond to user interactions while the main thread is busy. To improve this:
- [Break up Long Tasks](#long-tasks)
- [Optimize your page for interaction readiness](#optimize-interaction-readiness)
- [Use a web worker](#use-a-web-worker)
- [Reduce JavaScript execution time](#reduce-javascript-execution)
## Break up Long Tasks {: #long-tasks }
If you've already attempted to reduce the amount of JavaScript that loads on a single page, it can
be useful to break down long-running code into **smaller, asynchronous tasks**.
[**Long Tasks**](/custom-metrics/#long-tasks-api) are JavaScript execution periods where users may
find your UI unresponsive. Any piece of code that blocks the main thread for 50 ms or more can be
characterized as a Long Task. Long Tasks are a sign of
potential JavaScript bloat (loading and executing more than a user may need right now).
Splitting up long tasks can reduce input delay on your site.
<figure>
{% Img src="image/admin/THLKu0sOPhSghNr0XkP1.png", alt="Long Tasks in Chrome DevTools", width="800", height="132" %}
<figcaption>Chrome DevTools <a href="https://developers.google.com/web/updates/2020/03/devtools#long-tasks">visualizes Long Tasks</a> in the Performance Panel</figcaption>
</figure>
FID should improve noticeably as you adopt best practices like code-splitting and breaking up your
Long Tasks. While TBT is not a field metric, it's useful for checking progress towards ultimately
improving both Time To Interactive (TTI) and FID.
{% Aside %}
For more information, take a look at [Are long JavaScript tasks delaying your Time to
Interactive?](/long-tasks-devtools/).
{% endAside %}
## Optimize your page for interaction readiness
There are a number of common causes for poor FID and TBT scores in web apps that rely heavily on
JavaScript:
### First-party script execution can delay interaction readiness
- JavaScript size bloat, heavy execution times and inefficient chunking can slow down how soon a
page can respond to user input and impact FID, TBT, and TTI. Progressive loading of code and
features can help spread this work out and improve interaction readiness.
- Server-side rendered apps may look like they're getting pixels painted on the screen
quickly, but beware of user interactions being blocked by large script executions (e.g.
re-hydration to wire up event listeners). This can take several hundred milliseconds, sometimes
even seconds, if route-based code splitting is being used. Consider shifting more logic
server-side or generating more content statically during build time.
Below are the TBT scores before and after optimizing first-party script loading for an
application. By moving costly script loading (and execution) for a non-essential component off the
critical path, users were able to interact with the page much sooner.
{% Img src="image/tcFciHGuF3MxnTr1y5ue01OGLBn2/TEIbBnIAyfzIoQtvXvMk.png", alt="Improvements in TBT score in Lighthouse after optimizing the first-party script.", width="800", height="148" %}
### Data-fetching can impact many aspects of interaction readiness
- Waiting on a waterfall of cascading fetches (e.g. JavaScript and data fetches for components) can
impact interaction latency. Aim to minimize a reliance on cascading data fetches.
- Large inline datastores can push out HTML parsing time and impact both paint and interaction
metrics. Aim to minimize how much data needs to be post-processed on the client-side.
### Third-party script execution can delay interaction latency too
- Many sites include third-party tags and analytics which can keep the network busy and
make the main thread periodically unresponsive, impacting interaction latency. Explore
on-demand loading of third-party code (e.g. maybe don't load those below-the-fold ads until
they're scrolled closer to the viewport).
- In some cases, third-party scripts can pre-empt first-party ones in terms of priority and
bandwidth on the main thread, also delaying how soon a page is interaction-ready. Attempt to
prioritize loading what you believe offers the greatest value to users first.
## Use a web worker
A blocked main thread is one of the main causes of input delay. [Web
workers](https://developer.mozilla.org/docs/Web/API/Worker) make it possible to run JavaScript
on a background thread. Moving non-UI operations to a separate worker thread can cut down main
thread blocking time and consequently improve FID.
Consider using the following libraries to make it easier to use web workers on your site:
- [Comlink](https://github.com/GoogleChromeLabs/comlink): A helper library that abstracts
`postMessage` and makes it easier to use
- [Workway](https://github.com/WebReflection/workway): A general purpose web worker exporter
- [Workerize](https://github.com/developit/workerize): Move a module into a web worker
{% Aside %}
To learn more about how web workers can execute code off the main thread, refer to [Use Web Workers
to run JavaScript off the browser's main thread](/off-main-thread/).
{% endAside %}
### Reduce JavaScript execution time {: #reduce-javascript-execution }
Limiting the amount of JavaScript on your page reduces the amount of time that the browser needs to
spend executing JavaScript code. This speeds up how fast the browser can begin to respond to any
user interactions.
To reduce the amount of JavaScript executed on your page:
- Defer unused JavaScript
- Minimize unused polyfills
#### Defer unused JavaScript
By default all JavaScript is render-blocking. When the browser encounters a script tag that links to
an external JavaScript file, it must pause what it's doing and download, parse, compile, and execute
that JavaScript. Therefore you should only load the code that's needed for the page or
responding to user input.
The [Coverage](https://developer.chrome.com/docs/devtools/coverage/) tab in Chrome
DevTools can tell you how much JavaScript is not being used on your web page.
{% Img src="image/admin/UNEigFiwsGu48rtXMZM4.png", alt="The Coverage tab.", width="800", height="559" %}
To cut down on unused JavaScript:
- Code-split your bundle into multiple chunks
- Defer any non-critical JavaScript, including third-party scripts, using `async` or `defer`
**Code-splitting** is the concept of splitting a single large JavaScript bundle into smaller chunks
that can be conditionally loaded (also known as lazy-loading).
[Most newer browsers support dynamic import syntax](https://caniuse.com/#feat=es6-module-dynamic-import),
which allows for module fetching on demand:
```js
import('module.js').then((module) => {
// Do something with the module.
});
```
Dynamically importing JavaScript on certain user interactions (such as changing a route or
displaying a modal) will make sure that code not used for the initial page load is only fetched when
needed.
Aside from general browser support, dynamic import syntax can be used in many different build
systems.
- If you use [webpack](https://webpack.js.org/guides/code-splitting/),
[Rollup](https://medium.com/rollup/rollup-now-has-code-splitting-and-we-need-your-help-46defd901c82),
or [Parcel](https://parceljs.org/code_splitting.html) as a module bundler, take advantage of
their dynamic import support.
- Client-side frameworks, like
[React](https://reactjs.org/docs/code-splitting.html#reactlazy),
[Angular](https://angular.io/guide/lazy-loading-ngmodules), and
[Vue](https://vuejs.org/v2/guide/components-dynamic-async.html#Async-Components) provide
abstractions to make it easier to lazy-load at the component-level.
{% Aside %}
Take a look at [Reduce JavaScript payloads with code
splitting](/reduce-javascript-payloads-with-code-splitting/) to learn more about code-splitting.
{% endAside %}
Aside from code-splitting, always use [async or
defer](https://javascript.info/script-async-defer) for scripts that are not necessary for
critical-path or above-the-fold content.
```html
<script defer src="…"></script>
<script async src="…"></script>
```
Unless there is a specific reason not to, all third-party scripts should be loaded with either `defer`
or `async` by default.
#### Minimize unused polyfills
If you author your code using modern JavaScript syntax and reference modern browsers APIs, you will
need to transpile it and include polyfills in order for it to work in older browsers.
One of the main performance concerns of including polyfills and transpiled code in your site is that
newer browsers shouldn't have to download it if they do not need it. To cut down on the JavaScript
size of your application, minimize unused polyfills as much as possible and restrict their usage to
environments where they're needed.
To optimize polyfill usage on your site:
- If you use [Babel](https://babeljs.io/docs/en/index.html) as a transpiler, use
[`@babel/preset-env`](https://babeljs.io/docs/en/babel-preset-env) to only include the polyfills
needed for the browsers you plan on targeting. For Babel 7.9, enable the
[`bugfixes`](https://babeljs.io/docs/en/babel-preset-env#bugfixes) option to further cut down
on any unneeded polyfills
- Use the module/nomodule pattern to deliver two separate bundles (`@babel/preset-env` also
supports this via [`target.esmodules`](https://babeljs.io/docs/en/babel-preset-env#targetsesmodules))
```html
<script type="module" src="modern.js"></script>
<script nomodule src="legacy.js" defer></script>
```
Many newer ECMAScript features compiled with Babel are already supported in environments
that support JavaScript modules. So by doing this, you simplify the process of making sure that
only transpiled code is used for browsers that actually need it.
{% Aside %}
The [Serve modern code to modern browsers for faster page
loads](/serve-modern-code-to-modern-browsers/) guide goes into more detail about this topic.
{% endAside %}
## Developer tools
A number of tools are available to measure and debug FID:
- [Lighthouse 6.0](https://developer.chrome.com/docs/lighthouse/overview/) does not include
support for FID since it is a field metric. However, [Total Blocking
Time](/tbt/) (TBT) can be used as a proxy. Optimizations that improve TBT should
also improve FID in the field.
{% Img src="image/admin/FRM9kHWmsDv9dddGMgwu.jpg", alt="Lighthouse 6.0.", width="800", height="309" %}
- [Chrome User Experience Report](https://developers.google.com/web/tools/chrome-user-experience-report)
provides real-world FID values aggregated at the origin-level
_With thanks to Philip Walton, Kayce Basques, Ilya Grigorik, and Annie Sullivan for their reviews._
| 49.003759 | 226 | 0.773533 | eng_Latn | 0.9926 |
4bbdb77016bb0b13f8dc586ea2e1af764a5ee601 | 2,497 | md | Markdown | pay-per-follow.md | danielarmengolaltayo/me | dd2c0020fc4ef4f05556d4d56d95d2a1dc528879 | [
"MIT"
] | null | null | null | pay-per-follow.md | danielarmengolaltayo/me | dd2c0020fc4ef4f05556d4d56d95d2a1dc528879 | [
"MIT"
] | null | null | null | pay-per-follow.md | danielarmengolaltayo/me | dd2c0020fc4ef4f05556d4d56d95d2a1dc528879 | [
"MIT"
] | 2 | 2019-08-19T18:18:13.000Z | 2020-03-05T13:02:45.000Z | # Pay-Per-Follow, 2018
*Pay-Per-Follow* is a [reperformance](https://www.nytimes.com/video/multimedia/100000002717833/timestalks-marina-abramovic-part-8.html) of [Follow](https://armengol-altayo.com/follow), by [Daniel Armengol Altayó](https://armengol-altayo.com).
From March 24 to May 13, 2018, for six days per week, around seven hours and a half per day, Daniel was following the movements of the audience in a delimited space, using a VR headset and two controllers. In this free exhibition, people make him move more than 4,800 times, at an average of 1:00 min each interaction.
*Pay-Per-Follow* is a partnership between [Kai Corvus](https://twitter.com/KaiCorvus) and Daniel to bring the experience back, shifting the context to extend the conversation and ask new questions.
[A black market for selling internet-ish things](https://yami-ichi.biz/) was the context and the setup consisted of two performers, one forced to connect with the public, the other inviting people to connect. The proposal: 1,00 eur x 1:00 min. Pay one euro to control a person for one minute.
When the countdown of sixty seconds finished, after paying to control a person and indeed controlled one of the performers for one minute, the participant is paid back the same euro by the second performer and faced with the question, “how much would you be willing to pay to have control over another person?”, and the options “a) less than one euro, b) one euro, c) more than one euro” to gave a response and act accordingly.
The performance is divided in two acts. First, naively seduce the public to cash one euro out from their pockets, and then, confront anyone who took part with an uncomfortable truth.
In the same way [that Amazon may withdraw one euro from your bank account to give it back to you later as a measure to confirm the validity of your payment card](https://www.amazon.co.uk/gp/help/customer/display.html?nodeId=201895660), the transaction happening in the performance directs the attention of the public and the tone for the subsequent conversation. *Pay-Per-Follow* is about money as a medium to exchange value from one person to another and its power over people.
At what price would you let them control you? Are you aware of the value of your actions?
—
📸 📹 **[Gallery](https://www.flickr.com/photos/danielarmengolaltayo/albums/72157709918895281)**
###### *The Internet Yami-Ichi at Tentacular, Matadero Madrid, ES*<br>*24 November 2018* | 99.88 | 478 | 0.778935 | eng_Latn | 0.997854 |
4bbde97070202f7d4274dad0df84d282233da245 | 854 | md | Markdown | docs/README.md | jpyatachkov/nestjs-api-tools | dca31141b2d146a5384687302a95e5b9dc675c09 | [
"MIT"
] | 1 | 2020-11-23T14:25:20.000Z | 2020-11-23T14:25:20.000Z | docs/README.md | jpyatachkov/nestjs-api-tools | dca31141b2d146a5384687302a95e5b9dc675c09 | [
"MIT"
] | null | null | null | docs/README.md | jpyatachkov/nestjs-api-tools | dca31141b2d146a5384687302a95e5b9dc675c09 | [
"MIT"
] | null | null | null | # NestJS API tools documentation
The set of tools available consists of the following:
- [Decorators](./decorators.md) - [@nestjs/swagger](https://docs.nestjs.com/openapi/introduction) wrappers and pagination, serialization, validation wrappers.
- [Errors](./errors.md) - exception classes to throw.
- [Guards](./guards.md) - guards for access restriction.
- [Operators](./operators.md) - operator functions for data transformation.
- [Pipes](./pipes.md) - date parsing and transforming pipes.
- [Services](./services.md) - injectables for utility operations, for example, sending messages (error messages least) to Discord channel.
- [Settings](./setings.md) - DTOs for settings placement.
- [Transformers](./transformers.md) - TypeORM value transformers.
- [Utils](./utils.md) - set of helpful functions for string, object transformations and so on.
| 61 | 158 | 0.751756 | eng_Latn | 0.82891 |
4bbe435e34f47d248263450d2a691b03e90f4b6d | 5,264 | md | Markdown | docs/IPack.md | nftlabs/nftlabs-protocols | 2a207b56da8a64f4e37953db3da0f0b0c7175871 | [
"Apache-2.0"
] | 191 | 2021-10-31T04:40:12.000Z | 2022-02-15T22:31:52.000Z | docs/IPack.md | nftlabs/nftlabs-protocols | 2a207b56da8a64f4e37953db3da0f0b0c7175871 | [
"Apache-2.0"
] | 40 | 2021-10-14T21:58:24.000Z | 2022-01-20T08:33:23.000Z | docs/IPack.md | nftlabs/nftlabs-protocols | 2a207b56da8a64f4e37953db3da0f0b0c7175871 | [
"Apache-2.0"
] | 47 | 2021-10-31T06:46:46.000Z | 2022-02-15T03:27:12.000Z | # IPack
## Methods
### contractType
```solidity
function contractType() external pure returns (bytes32)
```
*Returns the module type of the contract.*
#### Returns
| Name | Type | Description |
|---|---|---|
| _0 | bytes32 | undefined
### contractURI
```solidity
function contractURI() external view returns (string)
```
*Returns the metadata URI of the contract.*
#### Returns
| Name | Type | Description |
|---|---|---|
| _0 | string | undefined
### contractVersion
```solidity
function contractVersion() external pure returns (uint8)
```
*Returns the version of the contract.*
#### Returns
| Name | Type | Description |
|---|---|---|
| _0 | uint8 | undefined
### createPack
```solidity
function createPack(IPack.PackContents contents, string uri, uint128 openStartTimestamp, uint128 nftsPerOpen) external nonpayable
```
Creates a pack with the stated contents.
#### Parameters
| Name | Type | Description |
|---|---|---|
| contents | IPack.PackContents | The contents of the packs to be created.
| uri | string | The (metadata) URI assigned to the packs created.
| openStartTimestamp | uint128 | The timestamp after which a pack is opened.
| nftsPerOpen | uint128 | The number of NFTs received on opening one pack.
### getDefaultRoyaltyInfo
```solidity
function getDefaultRoyaltyInfo() external view returns (address, uint16)
```
*Returns the royalty recipient and fee bps.*
#### Returns
| Name | Type | Description |
|---|---|---|
| _0 | address | undefined
| _1 | uint16 | undefined
### getRoyaltyInfoForToken
```solidity
function getRoyaltyInfoForToken(uint256 tokenId) external view returns (address, uint16)
```
*Returns the royalty recipient for a particular token Id.*
#### Parameters
| Name | Type | Description |
|---|---|---|
| tokenId | uint256 | undefined
#### Returns
| Name | Type | Description |
|---|---|---|
| _0 | address | undefined
| _1 | uint16 | undefined
### openPack
```solidity
function openPack(uint256 packId, uint256 amountToOpen) external nonpayable
```
Lets a pack owner open a pack and receive the pack's NFTs.
#### Parameters
| Name | Type | Description |
|---|---|---|
| packId | uint256 | The identifier of the pack to open.
| amountToOpen | uint256 | The number of packs to open at once.
### owner
```solidity
function owner() external view returns (address)
```
*Returns the owner of the contract.*
#### Returns
| Name | Type | Description |
|---|---|---|
| _0 | address | undefined
### royaltyInfo
```solidity
function royaltyInfo(uint256 tokenId, uint256 salePrice) external view returns (address receiver, uint256 royaltyAmount)
```
*Returns how much royalty is owed and to whom, based on a sale price that may be denominated in any unit of exchange. The royalty amount is denominated and should be payed in that same unit of exchange.*
#### Parameters
| Name | Type | Description |
|---|---|---|
| tokenId | uint256 | undefined
| salePrice | uint256 | undefined
#### Returns
| Name | Type | Description |
|---|---|---|
| receiver | address | undefined
| royaltyAmount | uint256 | undefined
### setContractURI
```solidity
function setContractURI(string _uri) external nonpayable
```
*Sets contract URI for the storefront-level metadata of the contract. Only module admin can call this function.*
#### Parameters
| Name | Type | Description |
|---|---|---|
| _uri | string | undefined
### setDefaultRoyaltyInfo
```solidity
function setDefaultRoyaltyInfo(address _royaltyRecipient, uint256 _royaltyBps) external nonpayable
```
*Lets a module admin update the royalty bps and recipient.*
#### Parameters
| Name | Type | Description |
|---|---|---|
| _royaltyRecipient | address | undefined
| _royaltyBps | uint256 | undefined
### setOwner
```solidity
function setOwner(address _newOwner) external nonpayable
```
*Lets a module admin set a new owner for the contract. The new owner must be a module admin.*
#### Parameters
| Name | Type | Description |
|---|---|---|
| _newOwner | address | undefined
### setRoyaltyInfoForToken
```solidity
function setRoyaltyInfoForToken(uint256 tokenId, address recipient, uint256 bps) external nonpayable
```
*Lets a module admin set the royalty recipient for a particular token Id.*
#### Parameters
| Name | Type | Description |
|---|---|---|
| tokenId | uint256 | undefined
| recipient | address | undefined
| bps | uint256 | undefined
## Events
### DefaultRoyalty
```solidity
event DefaultRoyalty(address newRoyaltyRecipient, uint256 newRoyaltyBps)
```
#### Parameters
| Name | Type | Description |
|---|---|---|
| newRoyaltyRecipient | address | undefined |
| newRoyaltyBps | uint256 | undefined |
### OwnerUpdated
```solidity
event OwnerUpdated(address prevOwner, address newOwner)
```
#### Parameters
| Name | Type | Description |
|---|---|---|
| prevOwner | address | undefined |
| newOwner | address | undefined |
### RoyaltyForToken
```solidity
event RoyaltyForToken(uint256 indexed tokenId, address royaltyRecipient, uint256 royaltyBps)
```
#### Parameters
| Name | Type | Description |
|---|---|---|
| tokenId `indexed` | uint256 | undefined |
| royaltyRecipient | address | undefined |
| royaltyBps | uint256 | undefined |
| 17.14658 | 203 | 0.682941 | eng_Latn | 0.802291 |
4bbefadce00842358dc5239cecabfc804db30c1b | 2,469 | md | Markdown | docs/requirements/5-30_Cleaner_Workflow/cleaner_workflow_5-30.md | jmgrady/TheCombine | 4645d891f4825458553b94119a7b5731bed715d3 | [
"MIT"
] | 14 | 2019-06-14T23:18:04.000Z | 2021-09-04T03:28:32.000Z | docs/requirements/5-30_Cleaner_Workflow/cleaner_workflow_5-30.md | jmgrady/TheCombine | 4645d891f4825458553b94119a7b5731bed715d3 | [
"MIT"
] | 1,114 | 2019-06-05T15:40:26.000Z | 2022-03-29T16:07:37.000Z | docs/requirements/5-30_Cleaner_Workflow/cleaner_workflow_5-30.md | jmgrady/TheCombine | 4645d891f4825458553b94119a7b5731bed715d3 | [
"MIT"
] | 9 | 2019-07-31T13:41:15.000Z | 2021-12-06T16:50:02.000Z | Questions:
- [Kinds of Cards](#units-and-exercises)
- [Order of Cards](#card-ordering)
- [Get More out of Each Card](#get-more-from-each-card)
- [Show Progress](#show-progress)
- [When to Stop](#when-to-stop)
## Tasks, Units and Exercises
The following cards are discrete actions we came up with. Included are some crazy-8s sketches we did.
 
We have broken cards into a hierarchy which helps facilitate workflow:
- `Tasks` represent broad, complex changes which affect the entire dataset.
- `Units` break tasks into discrete actions.
- `Exercises` accomplish tasks on manageable subsets of the complete dataset.
> As of 5-31, these categories have been renamed to `Tools`, `Goals` and `Steps`.
## Card Ordering
Our basic consensus for card ordering was this:
We break the workflow into distinct `tasks` that the cleaner may want to use the app to accomplish. At any point the
user can break out of the current task and switch into a new one, but we orient the UI to suggest they follow our
ordering and finish each task before moving on to the next.
Each `task` is broken down into `units`. The units are ordered within a task as such:
- An optional training unit to familiarize the user with the work they will do in that unit.
- The body of units which effect the desired change.
- Optionally merging any duplicates found in the database.
- An optional spot testing unit to evaluate the quality of the data corpus.
Within each `unit` are one or more `exercises` which break up the `unit` into manageably sized chunks of work.
The ordering within this structure will be simple to begin. If we have enough time, we can devote time to making more
complex orders based on:
- Better Workflow
- Qualitative Productivity
- Quantitative Productivity
Here is a collection of sketches that we took to get to that point. 
## Get More from Each Card
> Left for future consideration
## Show Progress
Below are the results of brainstorming for ways of showing progress to the user. These eventually led to the UI sketches
shown above.
 
## When to Stop
If a spot testing unit returns a score above a certain threshold, prompt the user to export his data.
Beyond that, the user has access to the export function at all times, but will never have it suggested.
<!-- TODO: (set export as final suggested task?) -->
| 36.850746 | 120 | 0.758202 | eng_Latn | 0.999147 |
4bbf5308704d80fce6e2c936f6ac2ceb84d8dd81 | 3,888 | md | Markdown | README.md | quest/cakephp-indicadores | 78ff968228383f9c855545858fcefd910adee44b | [
"MIT"
] | 1 | 2015-05-27T19:41:45.000Z | 2015-05-27T19:41:45.000Z | README.md | quest/cakephp-indicadores | 78ff968228383f9c855545858fcefd910adee44b | [
"MIT"
] | null | null | null | README.md | quest/cakephp-indicadores | 78ff968228383f9c855545858fcefd910adee44b | [
"MIT"
] | null | null | null | [](https://travis-ci.org/quest/cakephp-indicadores)
# Plugin de Indicadores Económicos de Chile para CakePHP #
Con este Plugin puedes obtener información para enriquecer su sitio web o tienda virtual, agregándole indicadores económicos,
santoral o honomástico, valor de las divisas más importantes, indicadores de la bolsa y restricción automotriz.
La información es obtenida de [http://indicadoresdeldia.cl](http://indicadoresdeldia.cl/pages/code/).
**Indicadores del Día** provee diariamente información de indicadores económicos actualizados y de manera gratuita, proporcionando ésta
por medio de su sitio web y como webservice para desarrolladores.
## Requerimientos ##
* PHP version: PHP 5.2+
* CakePHP version: 2.x Stable
## Instalación ##
### Usando Composer ###
Agregar al archivo `composer.json` de tu proyecto lo siguiente, en caso de no tenerlo deberás crearlo:
```composer
{
"require": {
"quest/cakephp-indicadores": "master"
}
}
```
### Manual ###
* Descargar: [http://github.com/quest/cakephp-indicadores/zipball/master](http://github.com/quest/cakephp-indicadores/zipball/master)
* Descomprime el archivo
* Copia el directorio a `app/Plugin`
* Renombra la carpeta que copiaste a `Indicadores`
### GIT Submodule ###
En el directorio de tu aplicación:
```bash
git submodule add -b master git://github.com/quest/cakephp-indicadores.git Plugin/Indicadores
git submodule init
git submodule update
```
### GIT Clone ###
En tu carpeta `Plugin`:
```bash
git clone -b master git://github.com/quest/cakephp-indicadores.git Indicadores
```
## Habilitar Plugin ##
Para habilitar el plugin escribe lo siguiente en tu archivo `app/Config/bootstrap.php`:
```php
CakePlugin::load('Indicadores');
```
O puedes habilitar todos tus Plugins:
```php
CakePlugin::loadAll();
```
## Uso ##
Lo puede ocupar en el Controlador como Componente y en la Vista como Helper, para esto debes activarlo en tu `app/Controller/AppController.php` usando `$helpers` o `$components`
```php
public $helpers = array('Indicadores.Indicadores');
public $components = array('Indicadores.Indicadores');
```
### Métodos ###
#### Indicadores::read(string $key) ####
Con este método puedes obtener el valor de los indicadores económicos disponibles:
En la vista:
```php
echo $this->Indicadores->read('moneda.dolar');
```
En el controlador:
```php
$this->Indicadores->read('moneda.dolar');
```
Si $key viene vacío, devuelve en un arreglo todos los valores disponibles.
Los valores que puede tener $key son:
* moneda.dolar
* moneda.euro
* indicador.uf
* indicador.ipc
* indicador.utm
* indicador.imacec
* santoral.ayer
* santoral.hoy
* santoral.maniana
* bolsa.igpa
* bolsa.ipsa
* bolsa.banca
* bolsa.utilities
* bolsa.commodities
* bolsa.consumo
* bolsa.retail
#### Indicadores::check(string $key) ####
Para validar si un indicador existe, está disponible el método `check()`, devuelve `true` si existe el indicador, en caso contrario retorna `false`.
En la vista:
```php
if ($this->Indicadores->check('moneda.dolar')) {
//algo
}
```
En el controlador:
```php
if ($this->Indicadores->check('moneda.dolar')) {
//algo
}
```
## TODO ##
* Cache
* Modelo
## Support ##
Para reportar un bug o solicitar una mejores, ingrea al [Issue Tracker](https://github.com/quest/cakephp-environment/issues).
## Contribuye con este Plugin ##
Sientete libre de contribuir con el plugin para mejorar con nuevos issues, peticiones de mejoras, test de unidad y arreglo de errores o nuevas mejoras.
Toda ayuda o mejora es bienvenida :)
## Licencia ##
Copyright 2014, [Victor San Martín](http://twitter.com/questchile)
Proyecto licenciado bajo [The MIT License](http://www.opensource.org/licenses/mit-license.php)
La redistribución de los archivos deben conservar el aviso de copyright anterior.
| 25.411765 | 177 | 0.736883 | spa_Latn | 0.921594 |
4bc184013c3b40caa08c926757c1d17c4bba24c0 | 9,691 | md | Markdown | README.md | Ibsciss/ruby-middleware | 51bb6504737b126fcfb9c4845a806244fad3493b | [
"MIT"
] | 76 | 2015-04-08T13:33:05.000Z | 2022-03-24T15:54:00.000Z | README.md | Ibsciss/ruby-middleware | 51bb6504737b126fcfb9c4845a806244fad3493b | [
"MIT"
] | 8 | 2015-08-24T08:42:50.000Z | 2018-03-06T16:12:00.000Z | README.md | Ibsciss/ruby-middleware | 51bb6504737b126fcfb9c4845a806244fad3493b | [
"MIT"
] | 13 | 2015-05-18T21:36:47.000Z | 2021-02-12T15:59:43.000Z | [](https://codeclimate.com/github/Ibsciss/ruby-middleware)
[](https://codeclimate.com/github/Ibsciss/ruby-middleware)
[](https://semaphoreci.com/lilobase/ruby-middleware)
# Middleware
[](https://gitter.im/Ibsciss/ruby-middleware?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
`Middleware` is a library which provides a generalized implementation
of the [chain of responsibility pattern](http://en.wikipedia.org/wiki/Chain-of-responsibility_pattern) for Ruby.
This pattern is used in `Rack::Builder` or `ActionDispatch::MiddlewareStack` to manage a stack of middlewares. This gem is a generic implementation for any Ruby project.
The middleware pattern is a useful
abstraction tool in various cases, but is specifically useful for splitting
large sequential chunks of logic into small pieces.
This is an updated version of the original Mitchell Hashimoto's library: https://github.com/mitchellh/middleware
## Installing
Middleware is distributed as a RubyGem, so simply gem install:
```console
$ gem install ibsciss-middleware
```
Or, in your Gemfile:
```
gem 'ibsciss-middleware', '~> 0.4.2'
```
Then, you can add it to your project:
```ruby
require 'middleware'
```
## A Basic Example
Below is a basic example of the library in use. If you don't understand
what middleware is, please read below. This example is simply meant to give
you a quick idea of what the library looks like.
```ruby
# Basic middleware that just prints the inbound and
# outbound steps.
class Trace
def initialize(app, value)
@app = app
@value = value
end
def call(env)
puts "--> #{@value}"
@app.call(env)
puts "<-- #{@value}"
end
end
# Build the actual middleware stack which runs a sequence
# of slightly different versions of our middleware.
stack = Middleware::Builder.new do |b|
b.use Trace, "A"
b.use Trace, "B"
b.use Trace, "C"
end
# Run it!
stack.call(nil)
```
And the output:
```
--> A
--> B
--> C
<-- C
<-- B
<-- A
```
## Middleware
### What is it?
Middleware is a reusable chunk of logic that is called to perform some
action. The middleware itself is responsible for calling up the next item
in the middleware chain using a recursive-like call. This allows middleware
to perform logic both _before_ and _after_ something is done.
The canonical middleware example is in web request processing, and middleware
is used heavily by both [Rack](#) and [Rails](#).
In web processing, the first middleware is called with some information about
the web request, such as HTTP headers, request URL, etc. The middleware is
responsible for calling the next middleware, and may modify the request along
the way. When the middlewares begin returning, the state now has the HTTP
response, so that the middlewares can then modify the response.
Cool? Yeah! And this pattern is generally usable in a wide variety of
problems.
### Middleware Classes
One method of creating middleware, and by far the most common, is to define
a class that duck types to the following interface:
```ruby
class MiddlewareExample
def initialize(app); end
def call(env); end
end
```
Therefore, a basic middleware example follows:
```ruby
class Trace
def initialize(app)
@app = app
end
def call(env)
puts "Before next middleware execution"
@app.call(env)
puts "After next middleware execution"
end
end
```
A basic description of the two methods that a middleware must implement:
* **initialize(app)** - The first argument sent will always be the next middleware to call, called
`app` for historical reasons. This should be stored away for later.
* **call(env)** - This is what is actually invoked to do work. `env` is just some
state sent in (defined by the caller, but usually a Hash). This call should also
call `app.call(env)` at some point to move on.
This architecture offers the biggest advantage of letting you enhance the `env` variable before passing it to the next middleware, and giving you the ability to change the returned data, as follows:
```ruby
class Greeting
def initialize(app, datas = nil)
@app = app
@datas = datas
end
def call(env)
env = "#{@datas} #{env}"
result = @app(env)
"#{result} !"
end
end
Middleware::Builder.new { |b|
b.use Greeting, 'Hello'
}.call('John') #return "Hello John !"
```
### Middleware Lambdas
A middleware can also be a simple lambda. The downside of using a lambda is that
it only has access to the state on the initial call, there is no "post" step for
lambdas:
```ruby
Middleware::Builder.new { |b|
b.use -> (env) { env + 3 }
b.use -> (env) { env * 2 }
}.call(1) #return 8
```
## Middleware Stacks
Middlewares on their own are useful as small chunks of logic, but their real
power comes from building them up into a _stack_. A stack of middlewares are
executed in the order given.
### Basic Building and Running
The middleware library comes with a `Builder` class which provides a nice DSL
for building a stack of middlewares:
```ruby
stack = Middleware::Builder.new do |d|
d.use Trace
d.use ->(env) { puts "LAMBDA!" }
end
```
This `stack` variable itself is now a valid middleware and has the same interface,
so to execute the stack, just call `call` on it, so can compose middleware stack between them:
```ruby
Middleware::Builder.new do |d|
d.use stack
end.call()
```
The call method takes an optional parameter which is the state to pass into the
initial middleware.
You can optionally set a name, that will be displayed in inspect and for logging purpose:
```ruby
Middleware::Builder.new(name: 'MyPersonalMiddleware')
```
### Manipulating a Stack
Stacks also provide a set of methods for manipulating the middleware stack. This
lets you insert, replace, and delete middleware after a stack has already been
created. Given the `stack` variable created above, we can manipulate it as
follows. Please imagine that each example runs with the original `stack` variable,
so that the order of the examples doesn't actually matter:
#### Insert before
```ruby
# Insert a new item before the Trace middleware
stack.insert_before Trace, SomeOtherMiddleware
# Insert a new item at the top of the middleware stack
stack.insert_before 0, SomeOtherMiddleware
```
#### Insert after
```ruby
# Insert a new item after the Trace middleware
stack.insert_after(Trace, SomeOtherMiddleware)
# Insert a new item after the first middleware
stack.insert_after(0, SomeOtherMiddleware)
```
#### Insert after each
```ruby
logger = -> (env) { p env }
# Insert the middleware (can be also a middleware object) after each existing middleware
stack.insert_after_each logger
```
#### Insert before each
```ruby
logger = -> (env) { p env }
# Insert the middleware (can be also a middleware object) before each existing middleware
stack.insert_before_each logger
```
#### Replace
```ruby
# Replace the second middleware
stack.replace(1, SomeOtherMiddleware)
# Replace the Trace middleware
stack.replace(Trace, SomeOtherMiddleware)
```
#### Delete
```ruby
# Delete the second middleware
stack.delete(1)
# Delete the Trace middleware
stack.delete(Trace)
```
### Passing Additional Constructor Arguments
When using middleware in a stack, you can also pass in additional constructor
arguments. Given the following middleware:
```ruby
class Echo
def initialize(app, message)
@app = app
@message = message
end
def call(env)
puts @message
@app.call(env)
end
end
```
We can initialize `Echo` with a proper message as follows:
```ruby
Middleware::Builder.new do
use Echo, "Hello, World!"
end
```
Then when the stack is called, it will output "Hello, World!"
Note that you can also pass blocks in using the `use` method.
#### Lambda
Lambda work the same, with additional arguments:
```ruby
Middleware::Builder.new { |b|
# arrow syntax for lambda construction
b.use ->(env, msg) { puts msg }, 'some message'
}.call(1) #will print "some message"
```
### Debug
You can see the content of a given stack using the `inspect` method
```ruby
Middleware::Builder.new { |b|
b.use Trace
b.use Echo, "Hello, World!"
}.inspect
```
It will output:
```ruby
Middleware[Trace(), Echo("Hello, World!")]
```
_If you have set a name, it will be displayed instead of `Middleware`_.
#### Logging
A built-in logging mechanism is provided, it will output for each provider of the stack:
- The provided arguments
- The returned values (the first 255 chars) and the time (in milliseconds) elapsed in the call method
To initialize the logging you must provide a valid logger instance to `#inject_logger`.
It is also recommended to give a name to your middleware stack.
```ruby
require 'logger'
class UpperCaseMiddleware
def initialize app
@app = app
end
def call env
sleep(1)
env.upcase
end
end
# Build the middleware:
Middleware::Builder.new(name: 'MyMiddleware') { |b|
b.use UpperCaseMiddleware
}.inject_logger(Logger.new(STDOUT)).call('a message')
```
It will output something like:
```
INFO -- MyMiddleware: UpperCaseMiddleware has been called with: "a message"
INFO -- MyMiddleware: UpperCaseMiddleware finished in 1001 ms and returned: "A MESSAGE"
```
_Note: the provided logger instance must respond to `#call(level severity, message, app name)`_ | 25.637566 | 222 | 0.733154 | eng_Latn | 0.993084 |
4bc1d35e872c82974f63e3cda75faed655d98f0f | 6,003 | md | Markdown | docs/developpers/guides/module/custom.md | intendantio/intendant-docs | d71017d509c354e808135886f5e5f1880fc87f1f | [
"MIT"
] | 1 | 2021-12-04T15:58:11.000Z | 2021-12-04T15:58:11.000Z | docs/developpers/guides/module/custom.md | intendantio/intendant-docs | d71017d509c354e808135886f5e5f1880fc87f1f | [
"MIT"
] | null | null | null | docs/developpers/guides/module/custom.md | intendantio/intendant-docs | d71017d509c354e808135886f5e5f1880fc87f1f | [
"MIT"
] | null | null | null | ---
title: Custom Module
sidebar_position: 2
---
Intendant proposes to create custom module easily and quickly.
Javascript skills will be necessary to create a custom module.
## Structure
- `index.js` is the entry point of module.
- `package.json` is a file configuration.
```txt
/my-custom-module
|-index.js
|-package.json
```
## package.json
You can generate `package.json` file with command `npm init`.
The file define :
- Name
- Version
- Module
- Actions
### Name
Name is the reference of the module which represents the package name, it must be unique.
```json
{
"name" : "@author/my-perfect-module"
}
```
### Version
Version is version of the module with usual format `x.x.x`
```json
{
"version" : "0.0.1"
}
```
### Module
Module is type of library, you must set `module` value
```json
{
"module" : "module"
}
```
### Actions
Each module action must be define.
An actions is an array of javascript object :
```json
{
"actions" : [
{
"id" : "module", // Unique action reference (type String)
"name" : "", // Usual name (type String)
"description": "", // Usual description (type String)
"settings": [ // List of settings (type Array)
{
"id" : "module", // Unique setting reference (type String)
"default" : "", // Default value (type Any) (optional)
"type": "", // Setting type (type Type)
},
{ ... } // Action can have unlimited settings
]
},
{ ... } // Module can have unlimited actions
]
}
```
#### Type
Type |Description| Option | Web interface|
|--------|--------|--------|--------|
| text | Textinput | | <img src="/img/type/textinput.png" style={{borderRadius: '5px'}} width="160" height="75" /> |
| number | Textinput with only numbers | | <img src="/img/type/textinput.png" style={{borderRadius: '5px'}} width="160" height="75" />
| slider | Slider with minimum, maximum and step value | `min` `max` `step` | <img style={{borderRadius: '5px'}} src="/img/type/slider.png" width="150" height="70" /> |
| colorpicker | List of 10 selectable colors | | <img src="/img/type/colorpicker.png" style={{borderRadius: '5px'}} width="220" height="85" /> |
| select | Picker is included in a list of values | `values` | <img src="/img/type/select.png" style={{borderRadius: '5px'}} width="170" height="75" /> |
| cron | Crontab picker ( **[wiki](https://crontab.guru/crontab.5.html)** ) | | <img src="/img/type/textinput.png" width="160" height="75" style={{borderRadius: '5px'}} />
| checkbox | Checkbox with two value (true, false) | | <img src="/img/type/checkbox.png" width="105" style={{borderRadius: '5px'}} height="100" /> |
### Example
```json
{
"name": "@intendant/reminder-module",
"author": "Clément MERLET",
"version": "0.0.4",
"dependencies": {
"moment": "^2.29.1",
"node-schedule": "^2.0.0"
},
"module": "module",
"actions": [
{
"id": "getAll",
"name": "Get all reminder",
"description": "Get all reminder in storage",
"settings": []
},
{
"id": "getOne",
"name": "Get one reminder",
"description": "Get one reminder in storage",
"settings": [
{
"id": "reference",
"type": "text",
"default": ""
}
]
},
{
"id": "create",
"name": "Add reminder",
"description": "Add reminder in storage",
"settings": [
{
"id": "reference",
"type": "text",
"default": ""
},
{
"id": "information",
"type": "text",
"default": ""
},
{
"id": "repeating",
"type": "checkbox",
"default": ""
},
{
"id": "cron",
"type": "cron",
"default": ""
}
]
},
{
"id": "removeOne",
"name": "Remove reminder",
"description": "Remove one reminder in storage",
"settings": [
{
"id": "reference",
"type": "text",
"default": ""
}
]
}
]
}
```
## index.js
### Class
You must create a simple class
```js
class MyCustomModule {
}
```
### Methods
To define an action, you must create an methode with signature `__{id}`.
You muste replace `{id}` by action reference
```javascript
// Action getExample
// Settings {name : ""}
async __getExample(settings = {}) {
console.log("Hello World")
console.log("Welcome " + settings.name)
return {
code: "ok",
message: "",
error: false,
data: {}
}
}
```
```json
{
"actions" : [
{
"id" : "getExample",
"name" : "Get example action",
"description": "Equivalent at Hello world action",
"settings": [
{
"id" : "name",
"default" : "",
"type": "text",
}
]
}
]
}
```
Return format must be an object :
```js
{ code: String, message: String, error: Boolean, data?: Object }
```
| 26.328947 | 186 | 0.449109 | eng_Latn | 0.655684 |
4bc235f455c7b1c2ff7a87e8ef4efc85015d69ad | 873 | md | Markdown | conduit-combos/results/Results_Single_am_kyrian.md | cixel/sl-shadow-priest | 3159c79fb305a226aeddfa6b884734ddfc108ccd | [
"MIT"
] | null | null | null | conduit-combos/results/Results_Single_am_kyrian.md | cixel/sl-shadow-priest | 3159c79fb305a226aeddfa6b884734ddfc108ccd | [
"MIT"
] | null | null | null | conduit-combos/results/Results_Single_am_kyrian.md | cixel/sl-shadow-priest | 3159c79fb305a226aeddfa6b884734ddfc108ccd | [
"MIT"
] | null | null | null | # Single - am - kyrian
| Actor | DPS | Increase |
|---|:---:|:---:|
|HA_DE_CA_3|8349|10.02%|
|HA_RS_CA_3|8326|9.72%|
|HA_CA_AAF_3|8325|9.71%|
|MD_CA_AAF_3|8246|8.67%|
|DE_MD_CA_3|8245|8.65%|
|MD_RS_CA_3|8242|8.61%|
|DE_RS_CA_3|8239|8.58%|
|DE_CA_AAF_3|8239|8.58%|
|RS_CA_AAF_3|8222|8.35%|
|HA_DE_MD_3|8203|8.10%|
|HA_DE_AAF_3|8188|7.91%|
|HA_DE_RS_3|8188|7.90%|
|HA_MD_AAF_3|8184|7.85%|
|HA_MD_RS_3|8182|7.82%|
|HA_CA_2|8169|7.65%|
|HA_RS_AAF_3|8159|7.53%|
|DE_MD_AAF_3|8086|6.56%|
|DE_MD_RS_3|8084|6.54%|
|MD_CA_2|8083|6.52%|
|DE_CA_2|8082|6.50%|
|MD_RS_AAF_3|8078|6.46%|
|DE_RS_AAF_3|8073|6.39%|
|CA_AAF_2|8068|6.33%|
|RS_CA_2|8064|6.27%|
|HA_DE_2|8036|5.89%|
|HA_MD_2|8024|5.74%|
|HA_RS_2|8001|5.44%|
|HA_AAF_2|7999|5.41%|
|DE_MD_2|7930|4.51%|
|MD_AAF_2|7920|4.37%|
|MD_RS_2|7920|4.37%|
|DE_AAF_2|7914|4.29%|
|DE_RS_2|7913|4.28%|
|RS_AAF_2|7898|4.08%|
|Base|7588|0.00%|
| 22.384615 | 26 | 0.67583 | yue_Hant | 0.320289 |
4bc26a8c2b428a34f944e9f7f82d1919ba1f3cc2 | 198 | md | Markdown | examples/run-in-electron/README.md | Prabhakar-Poudel/js-ipfs | f596b01fc1dab211c898244151017867d182909d | [
"MIT"
] | 2 | 2020-11-08T15:05:25.000Z | 2021-07-08T01:59:14.000Z | examples/run-in-electron/README.md | Prabhakar-Poudel/js-ipfs | f596b01fc1dab211c898244151017867d182909d | [
"MIT"
] | 4 | 2019-12-08T06:20:24.000Z | 2020-03-12T03:53:19.000Z | examples/run-in-electron/README.md | Prabhakar-Poudel/js-ipfs | f596b01fc1dab211c898244151017867d182909d | [
"MIT"
] | 7 | 2020-04-22T08:31:52.000Z | 2021-09-07T06:38:05.000Z | # js-ipfs in Electron
> This example is heavily inspired by [electron-quick-start](https://github.com/electron/electron-quick-start).
To try it by yourself, do:
```
> npm install
> npm start
```
| 18 | 111 | 0.712121 | eng_Latn | 0.982742 |
4bc2a6d9dd1e265c832b9ade4011c1f7e2d6ef82 | 69 | md | Markdown | README.md | calibrae-project/contrib | 9daf75cb11bad6d98696ed2b88f1cc4ab6d0dd10 | [
"Unlicense"
] | null | null | null | README.md | calibrae-project/contrib | 9daf75cb11bad6d98696ed2b88f1cc4ab6d0dd10 | [
"Unlicense"
] | null | null | null | README.md | calibrae-project/contrib | 9daf75cb11bad6d98696ed2b88f1cc4ab6d0dd10 | [
"Unlicense"
] | null | null | null | # contrib
User contributed scripts and executables and documentation
| 23 | 58 | 0.855072 | eng_Latn | 0.996003 |
4bc315f8eb4805253cb8976864edb2dbdf0d5083 | 3,545 | md | Markdown | README.md | Seledonia/desafio-frontend | bc81d9cf21d71dd6e3006ab09200968b6c44e2c2 | [
"MIT"
] | null | null | null | README.md | Seledonia/desafio-frontend | bc81d9cf21d71dd6e3006ab09200968b6c44e2c2 | [
"MIT"
] | null | null | null | README.md | Seledonia/desafio-frontend | bc81d9cf21d71dd6e3006ab09200968b6c44e2c2 | [
"MIT"
] | null | null | null | # Desafio-Frontend
Este repositório contém a resolução do desafio FrontEnd para a oportunidade de Front-end Developer na Partner Programmer, seguindo a orientação do recrutador escolhi este desafio https://github.com/1STi/desafio-frontend da lista de desafios sugeridos.
## Como utilizar esta solução
Para executar essa solução é necessário obter as credencias de acesso de API de clima do Yahoo no endereço https://developer.yahoo.com/weather/ e alterar o seguinte trecho com as tuas credenciais.
```javascript
const credentials = {
app_id: '',
consumer_key : '',
consumer_secret : '',
};
```
Para o correto funcionamento os arquivos devem ser acessados de um servidor Web (ex. Apache, Nginx, lighttpd, etc)
## Bem-vindo
A 1STi é uma consultoria em tecnologias digitais emergentes que tem a missão de aproximar a tecnologia das reais necessidades sociais. Nós enxergamos a tecnologia como um presente à humanidade dado pela expressão de nosso próprio intelecto, realizando uma síntese entre arte, humanidade e ciência.
Nosso modelo de negócios combina projetos de valor compartilhado com consultoria nas tecnologias mais avançadas. Esse desafio é uma oportunidade para fazer parte do nosso time em uma jornada de aprendizado e desenvolvimento de interfaces web!
## Aprendizado e desenvolvimento
Você pode esperar um trabalho intenso em projetos HTML5/CSS3 com o framework React, do facebook, e boas práticas em Redux, um mecanismo de gerenciamento de estado de aplicações, além de diversos componentes javascript.
O aprendizado se dá através de projetos reais, na construção de sites e aplicações que ajudem causas sociais de impacto. Conforme a evolução, serão feitas transições para projetos de consultoria em ambientes de negócio complexos. Temos o suporte de vídeo aulas em inglês para apoiar os estudos e montamos um plano individual em conjunto.
O trabalho é home office, com carga horária de 6 horas por dia e comunicação intensa via slack e sala de vídeo no appear. Espere uma equipe engajada e ideológica, mas muito mão na massa e com sólidos princípios de arquitetura de aplicações web.
O valor da bolsa de estágio por 01 ano é de R$ 1.000,00/mês.
Serão dois selecionados e apos o desafio técnico teremos conversas por skype, mas fique à vontade para já ir nos conhecendo no slack.
## Como participar
* Crie um novo fork e branch com seu nome-sobrenome e faça um pull request quando estiver pronto. Iremos fazer code review.
* Envie um email para ola@1sti.com.br para te adicionarmos ao time slack do desafio.
## O desafio
Vamos dar uma olhada na previsão do tempo? A meta é criarmos uma página simples, que consuma a API do Yahoo de previsão do tempo (https://developer.yahoo.com/weather/). O layout final deverá ficar o mais próximo possível da versão abaixo (sim, vamos ter a versão responsiva mobile e a versão desktop):
Web:
Mobile responsivo:
## Dicas
* Tudo bem, até pode usar jquery. Se você não quiser usar (bônus), uma sugestão: Axios para a comunicação com a API.
* HTML o mais semântico possível.
* Branches com readme e instruções de implantação serão bem vindos.
* Pré-processadores CSS como Stylus ou LESS também.
* Que tal utilizar BEM nos identificadores css? http://getbem.com/naming/
| 57.177419 | 337 | 0.785049 | por_Latn | 0.999935 |
4bc3c5797220f63ef5af5747a1a5aed182cbedbc | 17,294 | md | Markdown | docs/jsdocs/gooddapp/lib/gundb/user-storage.md | dOrgTech/GoodBootstrap | 4d763937dbc49e61ffc4034bd3326c4981b30a25 | [
"MIT"
] | null | null | null | docs/jsdocs/gooddapp/lib/gundb/user-storage.md | dOrgTech/GoodBootstrap | 4d763937dbc49e61ffc4034bd3326c4981b30a25 | [
"MIT"
] | null | null | null | docs/jsdocs/gooddapp/lib/gundb/user-storage.md | dOrgTech/GoodBootstrap | 4d763937dbc49e61ffc4034bd3326c4981b30a25 | [
"MIT"
] | null | null | null | # user-storage
### Table of Contents
* [GunDBUser](user-storage.md#gundbuser)
* [Properties](user-storage.md#properties)
* [FieldPrivacy](user-storage.md#fieldprivacy)
* [ProfileField](user-storage.md#profilefield)
* [Properties](user-storage.md#properties-1)
* [FeedEvent](user-storage.md#feedevent)
* [Properties](user-storage.md#properties-2)
* [TransactionEvent](user-storage.md#transactionevent)
* [getReceiveDataFromReceipt](user-storage.md#getreceivedatafromreceipt)
* [Parameters](user-storage.md#parameters)
* [UserStorage](user-storage.md#userstorage)
* [Parameters](user-storage.md#parameters-1)
* [wallet](user-storage.md#wallet)
* [gunuser](user-storage.md#gunuser)
* [profile](user-storage.md#profile)
* [feed](user-storage.md#feed)
* [feedIndex](user-storage.md#feedindex)
* [user](user-storage.md#user)
* [ready](user-storage.md#ready)
* [init](user-storage.md#init)
* [getFeedItemByTransactionHash](user-storage.md#getfeeditembytransactionhash)
* [Parameters](user-storage.md#parameters-2)
* [getAllFeed](user-storage.md#getallfeed)
* [getProfileFieldValue](user-storage.md#getprofilefieldvalue)
* [Parameters](user-storage.md#parameters-3)
* [getProfileField](user-storage.md#getprofilefield)
* [Parameters](user-storage.md#parameters-4)
* [getDisplayProfile](user-storage.md#getdisplayprofile)
* [Parameters](user-storage.md#parameters-5)
* [getPrivateProfile](user-storage.md#getprivateprofile)
* [Parameters](user-storage.md#parameters-6)
* [setProfile](user-storage.md#setprofile)
* [Parameters](user-storage.md#parameters-7)
* [setProfileField](user-storage.md#setprofilefield)
* [Parameters](user-storage.md#parameters-8)
* [indexProfileField](user-storage.md#indexprofilefield)
* [Parameters](user-storage.md#parameters-9)
* [setProfileFieldPrivacy](user-storage.md#setprofilefieldprivacy)
* [Parameters](user-storage.md#parameters-10)
* [getFeedPage](user-storage.md#getfeedpage)
* [Parameters](user-storage.md#parameters-11)
* [getFormattedEvents](user-storage.md#getformattedevents)
* [Parameters](user-storage.md#parameters-12)
* [getUserAddress](user-storage.md#getuseraddress)
* [Parameters](user-storage.md#parameters-13)
* [getUserProfile](user-storage.md#getuserprofile)
* [Parameters](user-storage.md#parameters-14)
* [formatEvent](user-storage.md#formatevent)
* [Parameters](user-storage.md#parameters-15)
* [enqueueTX](user-storage.md#enqueuetx)
* [Parameters](user-storage.md#parameters-16)
* [dequeueTX](user-storage.md#dequeuetx)
* [Parameters](user-storage.md#parameters-17)
* [peekTX](user-storage.md#peektx)
* [Parameters](user-storage.md#parameters-18)
* [updateFeedEvent](user-storage.md#updatefeedevent)
* [Parameters](user-storage.md#parameters-19)
* [getLastBlockNode](user-storage.md#getlastblocknode)
* [saveLastBlockNumber](user-storage.md#savelastblocknumber)
* [Parameters](user-storage.md#parameters-20)
* [deleteAccount](user-storage.md#deleteaccount)
* [maskField](user-storage.md#maskfield)
* [Parameters](user-storage.md#parameters-21)
* [Parameters](user-storage.md#parameters-22)
## GunDBUser
User details returned from Gun SEA
Type: {alias: [string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String), epub: [string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String), pub: [string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String), sea: any}
### Properties
* `alias` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
* `epub` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
* `pub` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
* `sea` **any**
## FieldPrivacy
possible privacy level for profile fields
Type: \(`"private"` \| `"public"` \| `"masked"`\)
## ProfileField
User's profile field data
Type: {value: EncryptedField, display: [string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String), privacy: [FieldPrivacy](user-storage.md#fieldprivacy)}
### Properties
* `value` **EncryptedField**
* `display` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
* `privacy` [**FieldPrivacy**](user-storage.md#fieldprivacy)
## FeedEvent
User's feed event data
Type: {id: [string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String), type: [string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String), date: [string](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String), data: any}
### Properties
* `id` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
* `type` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
* `date` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
* `data` **any**
## TransactionEvent
Blockchain transaction event data
Type: any
## getReceiveDataFromReceipt
Extracts transfer events sent to the current account
### Parameters
* `receipt` [**object**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) Receipt event
Returns [**object**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) {transferLog: event: \[{evtName: evtValue}\]}
## UserStorage
Users gundb to handle user storage. User storage is used to keep the user Self Soverign Profile and his blockchain transcation history
### Parameters
* `wallet` **GoodWallet**
### wallet
wallet an instance of GoodWallet
Type: GoodWallet
### gunuser
a gun node refering to gun.user\(\)
Type: Gun
### profile
a gun node refering to gun.user\(\).get\('profile'\)
Type: Gun
### feed
a gun node refering to gun.user\(\).get\('feed'\)
Type: Gun
### feedIndex
In memory array. keep number of events per day
Type: [Array](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Array)<\[[Date](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Date), [number](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Number)\]>
### user
object with Gun SEA user details
Type: [GunDBUser](user-storage.md#gundbuser)
### ready
A promise which is resolved once init\(\) is done
Type: [Promise](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)<[boolean](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Boolean)>
### init
Initialize wallet, gundb user, feed and subscribe to events
### getFeedItemByTransactionHash
Find feed by transaction hash in array, and returns feed object
#### Parameters
* `transactionHash` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) transaction identifier
Returns [**object**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) feed item or null if it doesn't exist
### getAllFeed
Returns a Promise that, when resolved, will have all the feeds available for the current user
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<**[**Array**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Array)**<**[**FeedEvent**](user-storage.md#feedevent)**>>**
### getProfileFieldValue
Returns profile attribute
#### Parameters
* `field` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile attribute
Returns [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Decrypted profile value
### getProfileField
Returns progfile attribute value
#### Parameters
* `field` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile attribute
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) Gun profile attribute object
### getDisplayProfile
Return display attribute of each profile property
#### Parameters
* `profile` [**object**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) User profile
Returns [**object**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) User model with display values
### getPrivateProfile
Returns user model with attribute values
#### Parameters
* `profile` [**object**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) user profile
Returns [**object**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) UserModel with some inherit functions
### setProfile
Save profile with all validations and indexes It saves only known profile fields
#### Parameters
* `profile` **UserModel** User profile
* Throws **any** Error if profile is invalid
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) Promise with profile settings updates and privacy validations
### setProfileField
Set profile field with privacy settings
#### Parameters
* `field` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile attribute
* `value` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile attribute value
* `privacy` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) \(private \| public \| masked\) \(optional, default `'public'`\)
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) Promise with updated field value, secret, display and privacy.
### indexProfileField
Generates index by field if privacy is public, or empty index if it's not public
#### Parameters
* `field` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile attribute
* `value` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile attribute value
* `privacy` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) \(private \| public \| masked\)
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<ACK>** Gun result promise after index is generated
### setProfileFieldPrivacy
Set profile field privacy.
#### Parameters
* `field` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile attribute
* `privacy` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) \(private \| public \| masked\)
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) Promise with updated field value, secret, display and privacy.
### getFeedPage
Returns the next page in feed. could contain more than numResults. each page will contain all of the transactions of the last day fetched even if > numResults
#### Parameters
* `numResults` [**number**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Number) return at least this number of results if available
* `reset` [**boolean**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Boolean) should restart cursor \(optional, default `false`\)
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) Promise with an array of feed events
### getFormattedEvents
Return all feed events
#### Parameters
* `numResults` [**number**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Number)
* `reset` [**boolean**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Boolean)
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) Promise with array of standarised feed events
### getUserAddress
#### Parameters
* `field` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile field value \(email, mobile or wallet address value\)
Returns [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) address
### getUserProfile
Returns name and avatar from profile based filtered by received value
#### Parameters
* `field` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Profile field value \(email, mobile or wallet address value\)
Returns [**object**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) profile - { name, avatar }
### formatEvent
Returns the feed in a standard format to be loaded in feed list and modal
#### Parameters
* `param` [**FeedEvent**](user-storage.md#feedevent) Feed event with data, type, date and id props
* `param.data`
* `param.type`
* `param.date`
* `param.id`
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) Promise with StandardFeed object, with props { id, date, type, data: { amount, message, endpoint: { address, fullName, avatar, withdrawStatus }}}
### enqueueTX
enqueue a new pending TX done on DAPP, to be later merged with the blockchain tx the DAPP event can contain more details than the blockchain tx event
#### Parameters
* `event` [**FeedEvent**](user-storage.md#feedevent)
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<>**
### dequeueTX
remove and return pending TX
#### Parameters
* `eventId` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
* `event` **any**
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<**[**FeedEvent**](user-storage.md#feedevent)**>**
### peekTX
lookup a pending tx
#### Parameters
* `eventId` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<**[**FeedEvent**](user-storage.md#feedevent)**>**
### updateFeedEvent
Update feed event
#### Parameters
* `event` [**FeedEvent**](user-storage.md#feedevent) Event to be updated
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) Promise with updated feed
### getLastBlockNode
Returns the 'lastBlock' gun's node
Returns **any**
### saveLastBlockNumber
Saves block number in the 'lastBlock' node
#### Parameters
* `blockNumber` **\(**[**number**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Number) **\|** [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String)**\)**
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<\(**[**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<any> \|** [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<\(R \| any\)>\)>**
### deleteAccount
Delete the user account. Deleting gundb profile and clearing local storage Calling the server to delete their data
Returns [**Promise**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise)**<**[**boolean**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Boolean)**>**
### maskField
Returns phone with last 4 numbers, and before that \*\*\*, and hide email user characters leaving visible only first and last character
#### Parameters
* `fieldType` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) \(Email, mobile or phone\) Field name
* `value` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Field value
Returns [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Returns masked value with \*\*\* to hide characters
Clean string removing blank spaces and special characters, and converts to lower case
### Parameters
* `field` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Field name
* `value` [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Field value
Returns [**string**](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String) Value without '+' \(plus\), '-' \(minus\), '\_' \(underscore\), ' ' \(space\), in lower case
## Source
[https://github.com/GoodDollar/GoodDAPP/src/lib/gundb/UserStorage.js](https://github.com/GoodDollar/GoodDAPP/src/lib/gundb/UserStorage.js)
| 40.501171 | 358 | 0.752342 | yue_Hant | 0.332895 |
4bc3eecbd550d430f825a28dcd4b4272cb2f291d | 159 | md | Markdown | docs/kf.dev/content/en/docs/developers/develop-and-manage-apps/env-vars.md | henrybell/kf | 23c5ffded7b3ef07112a5b680f3aa44c40d1724d | [
"Apache-2.0"
] | 5 | 2019-04-30T20:46:30.000Z | 2019-05-27T14:25:56.000Z | docs/kf.dev/content/en/docs/developers/develop-and-manage-apps/env-vars.md | henrybell/kf | 23c5ffded7b3ef07112a5b680f3aa44c40d1724d | [
"Apache-2.0"
] | 165 | 2019-05-01T15:50:40.000Z | 2019-06-25T16:29:17.000Z | docs/kf.dev/content/en/docs/developers/develop-and-manage-apps/env-vars.md | henrybell/kf | 23c5ffded7b3ef07112a5b680f3aa44c40d1724d | [
"Apache-2.0"
] | 3 | 2019-05-01T21:48:38.000Z | 2019-06-05T18:51:27.000Z | ---
title: "Environment Variables"
linkTitle: "Environment Variables"
weight: 100
description: >
Configure and use environment variables with your app.
---
| 19.875 | 57 | 0.754717 | eng_Latn | 0.974172 |
4bc49779ae3d35cd4baa527ef59f02cfe9713685 | 736 | md | Markdown | tagged/threat-model.md | Uvacoder/bookmarks-codever | 8ed80e068d8d46825ca4678c73e3eba1e4d3aaab | [
"X11"
] | 125 | 2021-06-10T21:50:49.000Z | 2022-03-24T09:01:56.000Z | tagged/threat-model.md | Uvacoder/bookmarks-codever | 8ed80e068d8d46825ca4678c73e3eba1e4d3aaab | [
"X11"
] | 2 | 2019-11-23T14:32:57.000Z | 2020-01-23T05:23:36.000Z | tagged/threat-model.md | Uvacoder/bookmarks-codever | 8ed80e068d8d46825ca4678c73e3eba1e4d3aaab | [
"X11"
] | 17 | 2021-08-03T14:03:06.000Z | 2022-03-21T15:49:09.000Z | ## Bookmarks tagged [[threat-model]](https://www.codever.land/search?q=[threat-model])
_<sup><sup>[www.codever.land/bookmarks/t/threat-model](https://www.codever.land/bookmarks/t/threat-model)</sup></sup>_
---
#### [Threat Dragon home page](https://threatdragon.org/)
_<sup>https://threatdragon.org/</sup>_
Threat Dragon is a free, open-source threat modeling tool from OWASP. It can be used as a standalone desktop app for Windows and MacOS (Linux coming soon) or as a web application. The desktop app is g...
* **tags**: [security](../tagged/security.md), [security-tools](../tagged/security-tools.md), [threat-model](../tagged/threat-model.md)
* :octocat: **[source code](https://github.com/mike-goodwin/owasp-threat-dragon)**
---
| 61.333333 | 203 | 0.71875 | yue_Hant | 0.2691 |
4bc4bcb0bbeefa4825c289a0ae7048543e78f23b | 442 | md | Markdown | CHANGELOG.md | wiisportsresort/vscode-node-snippets | 333019b0230d75727862bb0b21fb710e52829f20 | [
"MIT"
] | null | null | null | CHANGELOG.md | wiisportsresort/vscode-node-snippets | 333019b0230d75727862bb0b21fb710e52829f20 | [
"MIT"
] | null | null | null | CHANGELOG.md | wiisportsresort/vscode-node-snippets | 333019b0230d75727862bb0b21fb710e52829f20 | [
"MIT"
] | null | null | null | # Change Log
All notable changes to the "node-snippets" extension will be documented in this file.
## v0.1.1
- Remove newlines after snippets
- Remove tabstops for names
- Generic module snippets
## v0.1.0
- Initial release
- CJS Module snippets:
- promisify, path, fs, crypto, http, https, express, webpack, lodash, chalk, moment, async, axios, inquirer, mkdirp, glob, dotenv, fs-extra, node-fetch, handlebars, mongoose, jsonwebtoken | 29.466667 | 189 | 0.742081 | eng_Latn | 0.553439 |
4bc543f3e5f0edee7422871d027e589406db394f | 958 | md | Markdown | formValidation/README.md | mashery/portal-code-snippets | 6223e40b8142ca17cada5ad7f76d1999f15bcd7e | [
"BSD-3-Clause"
] | 2 | 2020-07-24T19:25:25.000Z | 2021-03-10T10:00:14.000Z | formValidation/README.md | mashery/portal-code-snippets | 6223e40b8142ca17cada5ad7f76d1999f15bcd7e | [
"BSD-3-Clause"
] | null | null | null | formValidation/README.md | mashery/portal-code-snippets | 6223e40b8142ca17cada5ad7f76d1999f15bcd7e | [
"BSD-3-Clause"
] | null | null | null | # formValidation.js
Augment server-side validation with form validation. This replicates the Mashery server validation with JS when you need to conditionally require fields.
## Getting Started
### 1. Include the script in your Portal.
Add the script under `Manage` > `Portal` > `Portal Settings`. You can either add it as an external script or inline the code.
### 2. Initialize the script.
Call `formValidation(form, checkGroup)` for form you want to validate.
```js
/**
* Validate a form with JS
* @param {String} form A selector for the form
* @param {Array} checkGroup Checkbox groups to validate
*/
formValidation(form, checkGroup);
// Example
formValidation('[action*="/member/register"]');
// Example with checkboxes
formValidation('[action="http://trainingarea6.mashery.com/member/register"]', [{
checkboxes: ['#checkbox-1', '#checkbox-2', '#checkbox-3'],
legend: '#the-field-legend' // The error message will go here
}]);
``` | 30.903226 | 153 | 0.720251 | eng_Latn | 0.938905 |
4bc5bfe68f6b804ab8a2eff5ab62850ee1f03111 | 1,652 | md | Markdown | _janbrueghel/3669.md | brueghelfamily/brueghelfamily.github.io | a73351ac39b60cd763e483c1f8520f87d8c2a443 | [
"MIT"
] | null | null | null | _janbrueghel/3669.md | brueghelfamily/brueghelfamily.github.io | a73351ac39b60cd763e483c1f8520f87d8c2a443 | [
"MIT"
] | null | null | null | _janbrueghel/3669.md | brueghelfamily/brueghelfamily.github.io | a73351ac39b60cd763e483c1f8520f87d8c2a443 | [
"MIT"
] | null | null | null | ---
pid: '3669'
label: Travelers on a Hilltop Road
object_type: Painting
genre: Landscape
worktags: Traveling|Dog|Horse|Forest|Road|Wagon
iconclass_code:
height_cm: '21'
width_cm: '30'
diameter_cm:
location_country: Germany
location_city: Munich
location_collection: Alte Pinakothek
accession_nos_and_notes: 'inv. #821'
private_collection_info:
collection_type: Public
realdate: '1610'
numeric_date: '1610'
medium: Oil
support:
support_notes:
signature: BRUEGHEL 1610
signature_location:
support_marks: Mark of Peeter Stas on reverse
further_inscription:
print_notes:
print_type:
plate_dimensions:
states:
printmaker:
publisher:
series:
collaborators:
collaborator_notes:
collectors_patrons:
our_attribution: Jan Brueghel the Elder
other_attribution_authorities: 'Ertz 2008-10, #24|Ertz 1979, #216'
bibliography: 'Thiéry 1953, p. 176|Ertz 1979, cat. #216, pp. 50, 594, fig. 18|Essen/Vienna
1997, p. 98, fig. 2|Renger/Denk 2002, p. 108|Ertz 2008-10, cat. #24, p. 114'
biblio_reference: 8808|8809|8810|8811|8812
exhibition_history: 'Munich 2013, cat. #55'
ertz_1979: '216'
ertz_2008: '24'
bailey_walker:
hollstein_no:
bad_copy:
exclude_from_browsing: '0'
provenance: '6253'
provenance_text: 'In Munich Gallery by 1799, cat. #470 as Jan Brueghel'
related_works: 3050|3499
related_works_notes:
copies_and_variants:
curatorial_files:
general_notes:
discussion: '578'
external_resources_title:
external_resources_url:
thumbnail: "/img/derivatives/simple/3669/thumbnail.jpg"
fullwidth: "/img/derivatives/simple/3669/fullwidth.jpg"
collection: janbrueghel
layout: janbrueghel_item
order: '704'
permalink: "/janbrueghel/travelers-on-a-hilltop-road"
full:
---
| 25.030303 | 90 | 0.799031 | eng_Latn | 0.220728 |
4bc5eb6e3ea1fe7336b2ab3689f6ac5053e5ef54 | 1,411 | md | Markdown | Anka Build Cloud/Troubleshooting/controller/ui-strangeness.md | veertuinc/anka-docs | 90c10feb7fdd31b024a7ea49850c603cb6ea9b56 | [
"BSD-2-Clause"
] | 1 | 2021-11-08T00:55:45.000Z | 2021-11-08T00:55:45.000Z | Anka Build Cloud/Troubleshooting/controller/ui-strangeness.md | veertuinc/anka-docs | 90c10feb7fdd31b024a7ea49850c603cb6ea9b56 | [
"BSD-2-Clause"
] | 1 | 2022-03-11T02:56:35.000Z | 2022-03-11T13:11:21.000Z | Anka Build Cloud/Troubleshooting/controller/ui-strangeness.md | veertuinc/anka-docs | 90c10feb7fdd31b024a7ea49850c603cb6ea9b56 | [
"BSD-2-Clause"
] | 1 | 2022-02-15T13:57:04.000Z | 2022-02-15T13:57:04.000Z | ---
title: "UI Slowness, Nodes temporarily showing Offline, or Instances temporarily showing Error"
linkTitle: "UI Slowness, Nodes temporarily showing Offline, or Instances temporarily showing Error"
weight: 1
---
## Scenarios
1. Loading the UI seems to be very slow
2. Node status all seem to be delayed or alternating between different states randomly
3. Instance states all seem to be delayed or alternating between different states randomly
> Confirm an `average_queue_time` of > 5 when curling the controller's `api/v1/stats` endpoint
## Common Causes
1. Lots of VMS, Nodes, and not enough load balancing/instances of the controller, etcd, etc.
2. ETCD is very sensitive to disk latency; not using SSDs for the etcd storage
## Solutions:
1. Increase the space quota from the default 2GB: [https://etcd.io/docs/current/op-guide/maintenance/#space-quota]
2. Rejoin your nodes with a higher `--heartbeat` value (> 20s)
3. Upgrade the host's disk to an SSD or faster disk
4. Set `ANKA_NUM_WORKERS` to more than the default 2 in the Controller configuration.
> State changes can also be caused by network issues between the Node and the controller. Check the node's `/var/log/veertu/anka_agent.ERROR` log to confirm you're not seeing timeouts or connection errors.
## Still experiencing problems?
Talk to us! we are available via [slack](https://slack.veertu.com/) or [email](mailto:support@veertu.com) | 47.033333 | 205 | 0.77321 | eng_Latn | 0.993359 |
4bc601b8211b2e4e7f29776941bd5c22ae1758a5 | 1,564 | md | Markdown | pages/twitch-pinterest-reddit-y-mas-caen-en-la-interrupcion-de-fastly-cdn.md | Focustecno/incredible-parsley | dd7aff673b01e2b37a2dcecb6c5ecf41d1e2d57a | [
"MIT"
] | null | null | null | pages/twitch-pinterest-reddit-y-mas-caen-en-la-interrupcion-de-fastly-cdn.md | Focustecno/incredible-parsley | dd7aff673b01e2b37a2dcecb6c5ecf41d1e2d57a | [
"MIT"
] | null | null | null | pages/twitch-pinterest-reddit-y-mas-caen-en-la-interrupcion-de-fastly-cdn.md | Focustecno/incredible-parsley | dd7aff673b01e2b37a2dcecb6c5ecf41d1e2d57a | [
"MIT"
] | null | null | null | ---
layout: page
menu: false
date: 2021-08-25 01:53:59
title: Twitch, Pinterest, Reddit y más caen en la interrupción de Fastly CDN
subtitle: Los sitios web de noticias y contenido sufren una interrupción global debido
a fallas de Fastly CDN
description: Reddit, Spotify y Twitch, Hulu y HBO Max, así como Financial Times, NYT
y Bloomberg, enfrentaron cortes globales después de que Fastly enfrentara fallas
en sus redes de entrega de contenido.
image: "/uploads/reddit_spotify_y_twitch_hulu_y_hbo_max_asi_como_financial_times_nyt_y_bloomberg_enfrentaron_cortes_globales_despues_de_que_fastly_enfrentara_fallas_en_sus_redes_de_entrega_de_contenido_focus_tecno_wt.jpg"
optimized_image: "/uploads/reddit_spotify_y_twitch_hulu_y_hbo_max_asi_como_financial_times_nyt_y_bloomberg_enfrentaron_cortes_globales_despues_de_que_fastly_enfrentara_fallas_en_sus_redes_de_entrega_de_contenido_focus_tecn-1.jpg"
category:
- Conectados
tags:
- fallas
- github
- Fastly cdn
author: FocusTecno
permalink: "/twitch-pinterest-reddit-y-mas-caen-en-la-interrupcion-de-fastly-cdn/"
redirection: <meta http-equiv="refresh" content="0;url=https://focustecno.com/conectados/twitch-pinterest-reddit-y-mas-caen-en-la-interrupcion-de-fastly-cdn/"/>
<link rel="canonical" href="https://focustecno.com/conectados/twitch-pinterest-reddit-y-mas-caen-en-la-interrupcion-de-fastly-cdn/"/>
<script type="text/javascript">
window.location.href = "https://focustecno.com/conectados/twitch-pinterest-reddit-y-mas-caen-en-la-interrupcion-de-fastly-cdn/"
</script>
---
| 55.857143 | 229 | 0.815217 | spa_Latn | 0.512622 |
4bc6e8e6ca89ffd96dd639da3034e81f2a6e8681 | 270 | md | Markdown | src/zstd/README.md | trollcop/usbimager | d74e402d741d1ed64000409cbe72c7b291e2c020 | [
"MIT"
] | 7 | 2021-03-14T16:46:09.000Z | 2022-02-04T09:14:02.000Z | src/zstd/README.md | trollcop/usbimager | d74e402d741d1ed64000409cbe72c7b291e2c020 | [
"MIT"
] | null | null | null | src/zstd/README.md | trollcop/usbimager | d74e402d741d1ed64000409cbe72c7b291e2c020 | [
"MIT"
] | null | null | null | ZStandard
=========
This is a stripped down version of [zstd](https://github.com/facebook/zstd), which only contains the decompressor but nothing else.
Compilation
-----------
```
make libzstd.a ZSTD_LIB_COMPRESSION=0 ZSTD_LIB_DICTBUILDER=0 ZSTD_LIB_DEPRECATED=0
```
| 22.5 | 131 | 0.733333 | eng_Latn | 0.674497 |
4bc703511605c1e1ad0cd87542a0a25142da7b81 | 5,463 | md | Markdown | docs/en-US/Resolve-IdentityReference.md | IMJLA/PsAdsi | a0051fa74677535d2dad9d821c7116da2a4f6753 | [
"MIT"
] | null | null | null | docs/en-US/Resolve-IdentityReference.md | IMJLA/PsAdsi | a0051fa74677535d2dad9d821c7116da2a4f6753 | [
"MIT"
] | null | null | null | docs/en-US/Resolve-IdentityReference.md | IMJLA/PsAdsi | a0051fa74677535d2dad9d821c7116da2a4f6753 | [
"MIT"
] | null | null | null | ---
external help file: Adsi-help.xml
Module Name: Adsi
online version:
schema: 2.0.0
---
# Resolve-IdentityReference
## SYNOPSIS
Add more detail to IdentityReferences from Access Control Entries in NTFS Discretionary Access Lists
## SYNTAX
```
Resolve-IdentityReference [[-LiteralPath] <String>] [-FileSystemAccessRule <FileSystemAccessRule[]>]
[-KnownServers <Hashtable>] [<CommonParameters>]
```
## DESCRIPTION
Resolve generic defaults like 'NT AUTHORITY' and 'BUILTIN' to the applicable computer or domain name
Resolve SID to NT account name and vise-versa
Resolve well-known SIDs
## EXAMPLES
### EXAMPLE 1
```
$FolderPath = 'C:\Test'
(Get-Acl $FolderPath).Access | Resolve-IdentityReference $FolderPath
```
Use Get-Acl as the source of the access list
This works in either Windows Powershell or in Powershell
Get-Acl does not support long paths (\>256 characters)
That was why I originally used the .Net Framework method
### EXAMPLE 2
```
$FolderPath = 'C:\Test'
if ($FolderPath.Length -gt 255) {
$FolderPath = "\\?\$FolderPath"
}
[System.IO.DirectoryInfo]$DirectoryInfo = Get-Item -LiteralPath $FolderPath
[System.Security.AccessControl.DirectorySecurity]$DirectorySecurity = $DirectoryInfo.GetAccessControl('Access')
[System.Security.AccessControl.AuthorizationRuleCollection]$AuthRules = $DirectorySecurity.Access
$AuthRules | Resolve-IdentityReference -LiteralPath $FolderPath
```
Use the .Net Framework (or legacy .Net Core up to 2.2) as the source of the access list
Only works in Windows PowerShell
Those versions of .Net had a GetAccessControl method on the \[System.IO.DirectoryInfo\] class
This method is missing in modern versions of .Net Core
### EXAMPLE 3
```
$FolderPath = 'C:\Test'
if ($FolderPath.Length -gt 255) {
$FolderPath = "\\?\$FolderPath"
}
[System.IO.DirectoryInfo]$DirectoryInfo = Get-Item -LiteralPath $FolderPath
$Sections = [System.Security.AccessControl.AccessControlSections]::Access
$FileSecurity = [System.Security.AccessControl.FileSecurity]::new($DirectoryInfo,$Sections)
$IncludeExplicitRules = $true
$IncludeInheritedRules = $true
$AccountType = [System.Security.Principal.SecurityIdentifier]
$FileSecurity.GetAccessRules($IncludeExplicitRules,$IncludeInheritedRules,$AccountType) |
Resolve-IdentityReference -LiteralPath $FolderPath
```
This uses .Net Core as the source of the access list
It uses the GetAccessRules method on the \[System.Security.AccessControl.FileSecurity\] class
The targetType parameter of the method is used to specify that the accounts in the ACL are returned as SIDs
### EXAMPLE 4
```
$FolderPath = 'C:\Test'
if ($FolderPath.Length -gt 255) {
$FolderPath = "\\?\$FolderPath"
}
[System.IO.DirectoryInfo]$DirectoryInfo = Get-Item -LiteralPath $FolderPath
$Sections = [System.Security.AccessControl.AccessControlSections]::Access
$FileSecurity = [System.Security.AccessControl.FileSecurity]::new($DirectoryInfo,$Sections)
$IncludeExplicitRules = $true
$IncludeInheritedRules = $true
$AccountType = [System.Security.Principal.NTAccount]
$FileSecurity.GetAccessRules($IncludeExplicitRules,$IncludeInheritedRules,$AccountType) |
Resolve-IdentityReference -LiteralPath $FolderPath
```
This uses .Net Core as the source of the access list
It uses the GetAccessRules method on the \[System.Security.AccessControl.FileSecurity\] class
The targetType parameter of the method is used to specify that the accounts in the ACL are returned as NT account names (DOMAIN\User)
## PARAMETERS
### -FileSystemAccessRule
Access Control Entry from an NTFS Access List whose IdentityReferences to resolve
Accepts FileSystemAccessRule objects from Get-Acl or otherwise
```yaml
Type: System.Security.AccessControl.FileSystemAccessRule[]
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: True (ByValue)
Accept wildcard characters: False
```
### -KnownServers
Dictionary to cache known servers to avoid redundant lookups
Defaults to an empty thread-safe hashtable
```yaml
Type: System.Collections.Hashtable
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: [hashtable]::Synchronized(@{})
Accept pipeline input: False
Accept wildcard characters: False
```
### -LiteralPath
Path to the file or folder associated with the Access Control Entries passed to the AccessControlEntry parameter
This will be used to determine local vs.
remote computer, and then WinNT vs.
LDAP
```yaml
Type: System.String
Parameter Sets: (All)
Aliases:
Required: False
Position: 1
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```
### CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).
## INPUTS
### [System.Security.AccessControl.DirectorySecurity]$AccessControlEntry
## OUTPUTS
### [System.Security.AccessControl.DirectorySecurity] Original object plus ResolvedIdentityReference and AdsiProvider properties
## NOTES
Dependencies:
Get-DirectoryEntry
Add-SidInfo
Get-TrustedDomainSidNameMap
Find-AdsiProvider
## RELATED LINKS
| 33.310976 | 316 | 0.760937 | yue_Hant | 0.449388 |
4bc71e98e9cc32d2c9ee429fd28748fb7cad2349 | 3,147 | md | Markdown | i18n/locales/es-MX/hourofcode/promote/official-press-release.md | pickettd/code-dot-org | 20a6b232178e4389e1189b3bdcf0dc87ba59ec90 | [
"Apache-2.0"
] | null | null | null | i18n/locales/es-MX/hourofcode/promote/official-press-release.md | pickettd/code-dot-org | 20a6b232178e4389e1189b3bdcf0dc87ba59ec90 | [
"Apache-2.0"
] | null | null | null | i18n/locales/es-MX/hourofcode/promote/official-press-release.md | pickettd/code-dot-org | 20a6b232178e4389e1189b3bdcf0dc87ba59ec90 | [
"Apache-2.0"
] | null | null | null | * * *
title: <%= hoc_s(:title_press_release) %> layout: wide nav: promote_nav
* * *
<%= view :signup_button %>
# Muestra del comunicado a la prensa para los funcionarios electos
Para publicación inmediata
[**FECHA**]
Contacto: [**INFORMACIÓN DE CONTACTO**]
**
<center>
GOBERNADOR/SENADOR/MIEMBRO DE LA ASAMBLEA/REPRESENTANTE/ALCALDE/ MIEMBRO DEL CONSEJO [INSERTE NOMBRE][PARTICIPANTE EN LA HORA DE CÓDIGO CON ESTUDIANTES LOCALES]</strong><br /> La comunidad se une para crear conciencia sobre la importancia de la enseñanza de las Ciencias de la Computación, al participar en la Semana de la Educación Ciencias de la Computación
</center>
</p>
**FECHA** - [**INSERTE NOMBRE**] se unió a los directores y miembros de la Facultad de[**INSERTE NOMBRE DE LA ESCUELA**], líderes empresariales y familias locales hoy en [**NOMBRE DEL EVENTO**] para participar en la Hora de Código como parte de la Semana Educativa de Ciencias de Computación. [INSERTE NOMBRE] y miembros de la comunidad que están entre las decenas de millones de personas alrededor del mundo que participan en el mayor evento de aprendizaje de la historia.
[**INSERTE DETALLES DEL EVENTO, USE LENGUAJE DESCRIPTIVO Y CUANTIFICABLE. POR EJEMPLO:**]
"La escuela primaria Daniels Run celebró en toda la escuela un evento de la Hora de Código para exponer a sus estudiantes a las Ciencias de la Computación. Más de 700 estudiantes de todos los grados hicieron al menos una Hora del Código. Y una docena de padres y voluntarios de la comunidad ayudaron durante el día y reunieron a los niños para una demostración de por qué ciencias de la computación es importante en la vida de estos estudiantes"
[**TEXTO COMÚN DE MUESTRA PARA EL CONTEXTO:**]
Los ordenadores están por todas partes, pero menos escuelas enseñan Ciencias de la Computación que hace 10 años. Las chicas y los estudiantes de color están severamente subrepresentados. La buena noticia es que lo estamos cambiando para mejor. La Hora del Código es una puerta de entrada para proveer a todos los estudiantes el acceso de alta calidad a la educación en Ciencias de la Computación.
Más de 100 millones de estudiantes de todo el mundo ya hicieron una Hora del Código. Gracias a la Hora del Código, las Ciencias de la Computación estuvieron en las páginas principales de Google, MSN, Yahoo! y Disney. El Presidente Obama, Shakira y Ashton Kutcher dieron inicio a la Hora del Código con vídeos. Más de 100 socios aunaron esfuerzos para apoyar este movimiento.
[**INSERTAR CITA DEL PORTAVOZ, EJEMPLO DEBAJO:**]
"Tenemos que fomentar y adoptar el interés de los estudiantes en las Ciencias de la Computación," dijo [**INSERTAR NOMBRE**]. "Cada estudiante merece la oportunidad de aprender las Ciencias de Computación para acceder a las mejores carreras del siglo XXI".
[**INSERTE MÁS INFORMACIÓN ACERCA DE SU EVENTO Y/O DE SU ORGANIZACIÓN**]
[**INSERTE CITA DE OTRA ORGANIZACIÓN O ALGUIEN QUE ASISTIÓ AL EVENTO**
Para obtener más información sobre [**EVENTO/PROGRAMA/ETC**], visite [**INSERTE SITIO WEB**] o contacte [**INSERTE INFORMATION DE CONTACTO**]
<%= view :signup_button %> | 62.94 | 473 | 0.771211 | spa_Latn | 0.990578 |
4bc79102d70a2074d17efad05053910777dd483b | 2,293 | md | Markdown | cfp/WDV-004-009-058.md | lisa-todd/cfp | a611d4bc1a2f312490a61e6b4188342b10957a5e | [
"CC0-1.0"
] | 5 | 2021-04-21T09:02:31.000Z | 2021-04-26T08:22:47.000Z | cfp/WDV-004-009-058.md | lisa-todd/cfp | a611d4bc1a2f312490a61e6b4188342b10957a5e | [
"CC0-1.0"
] | 7 | 2021-04-23T03:40:02.000Z | 2021-05-19T02:56:46.000Z | cfp/WDV-004-009-058.md | lisa-todd/cfp | a611d4bc1a2f312490a61e6b4188342b10957a5e | [
"CC0-1.0"
] | 74 | 2021-04-14T10:00:22.000Z | 2021-07-27T13:42:46.000Z | ---
score1: 90
score2: 80
comments: "主题描述清楚，内容组织不够完善"
organizers:
-
name: 何子恒
id: 2020xxxxxx058
-
name: 罗海入
id: 2020xxxxxx004
-
name: 钟远鑫
id: 2020xxxxxx009
title: Workshop On Vulnerability Detection
shorttitle: WVD
only-for-homework: false
accept-chinese-submission: true
---
## Call for paper
The asymmetry of vulnerability information has become the key factor leading to the disparity of power in network war. Worms, shock waves, concussion viruses, and wannacry viruses that broke out in recent years have been transmitted by software or system vulnerabilities. In addition, advanced network attacks (such as apt attacks) even cross and combine multiple vulnerabilities, aiming to bypass the firewall, antivirus software, intrusion detection system, destroy the security of the isolation network, break through the core network nodes and enter the intranet, and carry out subsequent penetration attacks (such as stealing, modifying, encrypting important data, destroying core facilities, etc.). In particular, the undisclosed 0day vulnerability is often used as the ultimate secret weapon, and sometimes even plays a decisive role.
In view of the importance of software vulnerability in network attack and defense, researchers from major software manufacturers, universities and scientific research institutes have carried out a lot of research on vulnerability mining technology.
The purpose of this issue is to promote the research progress in the field of vulnerability mining. We welcome novel research on modelling, algorithm design and implementation, optimization, and applications in the use of these technologies to vulnerability research.
Topics of particular interest include, but are not limited to:
- Vulnerability prevention
- Vulnerability analysis
- Exploitation and defenses
- Hardware vulnerabilities
- Situational awareness
- Active probinga
## Important Date
Submission Deadline: 1 June 2021
Initial Decision Date: 1 July 2021
Revised Manuscript Due: 1 August 2021
Final Decision Date: 15 August 2021
Final Manuscript Due: 15 September 2021
Publication Date: January 2022
## Guest Editors
Ziheng He
Sichuan University, Chengdu, China
Hairu Luo
Sichuan University, Chengdu, China
Yuanxin Zhong
Sichuan University, Chengdu, China
| 40.946429 | 841 | 0.804187 | eng_Latn | 0.99517 |
4bc8463ff89fefe0b211279c71166d2698972686 | 55 | md | Markdown | docs/database_migrations.md | Dev-Lucid/lucid | cedb2cd3b2a1a1022fc620402a507f365e3f0505 | [
"MIT"
] | null | null | null | docs/database_migrations.md | Dev-Lucid/lucid | cedb2cd3b2a1a1022fc620402a507f365e3f0505 | [
"MIT"
] | null | null | null | docs/database_migrations.md | Dev-Lucid/lucid | cedb2cd3b2a1a1022fc620402a507f365e3f0505 | [
"MIT"
] | null | null | null | {{nav1 nav1_main}}
{{nav2 nav2_database}}
## Migrations | 18.333333 | 22 | 0.727273 | slv_Latn | 0.162866 |
4bc8eaf7599e3864420795ff8e7ad10a42683885 | 88 | md | Markdown | breaching/attacks/auxiliaries/README.md | ZHTushar23/breaching | cbed82882c736fd9a80d3032b120a02bf3bdb52b | [
"MIT"
] | 72 | 2022-02-15T23:59:21.000Z | 2022-03-29T07:05:32.000Z | breaching/attacks/auxiliaries/README.md | Conan-saber/breaching | 3e4d336ed3c631b8bf70974a9a5e1f923ddb039a | [
"MIT"
] | null | null | null | breaching/attacks/auxiliaries/README.md | Conan-saber/breaching | 3e4d336ed3c631b8bf70974a9a5e1f923ddb039a | [
"MIT"
] | 13 | 2022-02-16T06:39:35.000Z | 2022-03-29T11:57:39.000Z | # Auxiliaries for Attacks
This sub-module implements helper functionality for attacks.
| 22 | 60 | 0.829545 | eng_Latn | 0.922161 |
4bc924a4becec8a80a000eddc85f811b00ba5fe0 | 3,072 | md | Markdown | _posts/2017-01-19-on-ithaka.md | twentysix10/twentysix10.github.io | 11c16356333c6782fa9fc97b231d3b34568ba0de | [
"CC0-1.0"
] | null | null | null | _posts/2017-01-19-on-ithaka.md | twentysix10/twentysix10.github.io | 11c16356333c6782fa9fc97b231d3b34568ba0de | [
"CC0-1.0"
] | null | null | null | _posts/2017-01-19-on-ithaka.md | twentysix10/twentysix10.github.io | 11c16356333c6782fa9fc97b231d3b34568ba0de | [
"CC0-1.0"
] | null | null | null | ---
layout: post
title: "On Ithaka"
date: 2017-01-19 22:03
published: true
tags:
- Ithaka
- Siddhartha
excerpt: “As you set out for Ithaka hope your road is a long one...
---
## [](#header-2)On Ithaka
>As you set out for Ithaka<br/>
>hope your road is a long one,<br/>
>full of adventure, full of discovery.<br/>
>Laistrygonians, Cyclops,<br/>
>angry Poseidon - don't be afraid of them:<br/>
>you'll never find things like that on your way<br/>
>as long as you keep your thoughts raised high<br/>
>as long as a rare excitement<br/>
>stirs your spirit and your body.<br/>
>Laistrygonians, Cyclops,<br/>
>wild Poseidon - you won't encounter them<br/>
>unless you bring them along inside your soul,<br/>
>unless your soul sets them up in front of you.<br/>
>
>Hope your road is a long one.<br/>
>May there be many summer mornings when,<br/>
>with what pleasure, what joy,<br/>
>you enter harbors you're seeing for the first time;<br/>
>may you stop at Phoenician trading stations<br/>
>to buy fine things,<br/>
>mother of pearl and coral, amber and ebony,<br/>
>sensual perfume of every kind -<br/>
>as many sensual perfumes as you can;<br/>
>and may you visit many Egyptian cities<br/>
>to learn and go on learning from their scholars.<br/>
>
>Keep Ithaka always in your mind.<br/>
>Arriving there is what you're destined for.<br/>
>But don't hurry the journey at all.<br/>
>Better if it lasts for years,<br/>
>so you're old by the time you reach the island,<br/>
>wealthy with all you've gained on the way,<br/>
>not expecting Ithaka to make you rich.<br/>
>
>Ithaka gave you the marvelous journey.<br/>
>Without her you wouldn't have set out.<br/>
>She has nothing left to give you now.<br/>
>
>And if you find her poor, Ithaka won't have fooled you.<br/>
>Wise as you will have become, so full of experience,<br/>
>you'll have understood by then what these Ithakas mean.<br/>
>
>-- C.P. Cavafy,translated by Edmund Keeley
In Siddhartha (Herman Hesse), our protagonist spends his years searching for enlightenment. In this pursuit, he goes from Brahmin to Samana, from Samana to merchant, from merchant to ferryman. Only when he has fully embraced and fully forsaken each experience does he come to the conclusion that:
>I have experienced on my body and on my soul that I needed sin very much, I needed lust, the desire for possessions, vanity, and needed the most shameful despair, in order to learn how to give up all resistance, in order to stop comparing it to some world I wished, I imagined, some kind of perfection I had made up, but to leave it as it is and to love it and to enjoy being a part of it.
It takes Siddhartha years to reach his enlightenment, and we find that at the end of the day, his enlightenment simply means a love for his world here and now, with all its flaws, and its imperfections, and its sins, and its beauty.
Until recently, I find that I have been single-mindedly racing toward my Ithaka. In my last semester of college, it seems like a ripe time to make my "[stops] at Phoenician trading stations."
190117 22:03
[back](/index)
| 44.521739 | 390 | 0.737956 | eng_Latn | 0.999502 |
4bc993243c3754422fb3f9eda3084a12473f0a6b | 1,348 | md | Markdown | README.md | wemerson-santos/paa-viewer | 2faa41f3dc2bd0cd01d250660c46302836c5dfcd | [
"MIT"
] | null | null | null | README.md | wemerson-santos/paa-viewer | 2faa41f3dc2bd0cd01d250660c46302836c5dfcd | [
"MIT"
] | null | null | null | README.md | wemerson-santos/paa-viewer | 2faa41f3dc2bd0cd01d250660c46302836c5dfcd | [
"MIT"
] | null | null | null | # PAA-Viewer
O software tem o objetivo de auxiliar os coordenadores municipais do PAA (Programa de Aquisição de Alimentos). Esses profissionais têm acesso à plataforma SISPAA, que é utilizada para registrar a compra de produtos hortifrutigranjeiros de pequenos produtores rurais e também realizar as doações desses alimentos para entidades sociais. O sistema, entretanto, não conta com recursos "amigáveis" de visualização de relatórios, o que dificulta o controle das quantidades entre o que foi comprado e doado, gerendo muitas vezes "quebra de estoque". Com base nessa deficiência, surgiu o PAA Viewer, uma alternativa elegante que analisa planilhas excel retiradas do SISPAA e as apresenta de forma simples e objetiva.
## Sobre o PAA:
O Programa de Aquisição de Alimentos (PAA) tem como finalidades básicas promover o acesso à informação e incentivar a agricultura familiar. Para o alcance desses objetivos, o programa compra alimentos produzidos pela agricultura familiar e destina às pessoas em situação de insegurança alimentar e nutricional e àquelas atendidas pela rede socioassistencial, pelos equipamentos públicos de segurança alimentar e nutricional e pela rede pública e filantrópica de ensino.
[Leia mais](http://mds.gov.br/assuntos/seguranca-alimentar/programa-de-aquisicao-de-alimentos-paa)
## Tecnologias:
- Javascript
- React
| 122.545455 | 710 | 0.821217 | por_Latn | 0.999824 |
4bcac08fb307237b435e069a88fa781990c14b81 | 3,738 | md | Markdown | docs/index.md | byuids-resumes/swanson_resume | db25a090654f9f7a7ee362ffc7ef5636655980c8 | [
"MIT"
] | null | null | null | docs/index.md | byuids-resumes/swanson_resume | db25a090654f9f7a7ee362ffc7ef5636655980c8 | [
"MIT"
] | null | null | null | docs/index.md | byuids-resumes/swanson_resume | db25a090654f9f7a7ee362ffc7ef5636655980c8 | [
"MIT"
] | 2 | 2021-12-07T20:21:56.000Z | 2021-12-07T20:44:05.000Z | ---
layout: cv
title: Robbie Swanson's Resume..................
---
# Robbie Swanson
Computer Science Student at Brigham Young University - Idaho
<div id="webaddress">
<a href="datascience@byui.edu">larocarobbie@gmail.com</a>
| <a href="https://www.linkedin.com/in/robbie-swanson-17661a194/">LinkedIn</a>
| <a href="https://github.com/robbieswan/swanson_resume">GitHub</a>
</div>
<!-- https://www.monique.tech/the-art-of-markdown -->
## Education
`2019-2023`
__Brigham Young University - Idaho__, Rexburg, ID
- ● Accumulative GPA: 4.0
- ● Presidency member of Artificial Intelligence Society (Mar. 2021 – present)
- ● Student Representative Council (Sept. 2019 – Dec. 2019)
- ● Relevant Coursework: Parallelism & Concurrency, Data Structures (Python & currently C#), Database Design
## Related Experience
### Backend Software Engineer
`September 2020 - Present`
__Market Turning Points Trading__ Lehi, UT
- ● Integrated Python scripts to stock forecasting web application, creating brand new product for company.
- ● Transformed thousands of data points from member retention and survey feedback into simplistic onboarding
retention charts using Python Matplotlib and Pandas packages.
- ● Pivoted the onboarding experience of 300 monthly members to include updated UX/UI designs for membership
pages as well as building brand new membership courses with defined feature sets working with Project Manager.
- ● Implemented API fed web application using proprietary algorithms that created hundreds of stock market
projections.
### ACA Reporting Specialist
`Jan. 2020 – Mar. 2020`
__HR Service Inc__
- ● Created hundreds to thousands of data entries for 21 companies and manually manipulated company reports to
ensure the security and accuracy of data for each client.
- ● Cultivated relationships working directly with CEO’s, heads of Human Resources, and operational managers,
maintaining efficiency in meeting all time sensitive sprint deadlines.
- ● Represented over 20 companies, handling all Affordable Care Act reports for each business
## Projects
__Using: OOP, Python, SQL, NEAT algorithms, AI, SCRUM__
- ● Executed comprehensive tutorials with interactive assignments for all major data structures (i.e., stacks, queues,
linked lists, and binary search trees).
- ● Used NEAT algorithm to create neural network AI that beats the game, Flappy Bird.
- ● Led team of 4 engineers using SCRUM methodology in agile framework to create an AI snake game over a 4-
month period, leading team meetings and organizing 2-week sprints.
- ● Built relational Database model analyzing a complex 5 table Family History database.
## Activities & Awards
### Volunteer Service
`2017 - 2019`
__The Church of Jesus Christ of Latter-Day Saints__ Macon, Georgia
- ● Appointed as Assistant to the President, overseeing all 145 volunteers training as well as orchestrating mission
data reporting for over 7 and a half months.
- ● Maintained rigorous volunteer schedule, working 15 hours daily for 2 years.
- ● Designed and headed relocation effort for over 130 individuals displaced by Hurricane Ida.
- ● Developed public speaking and team management skills, leading and training teams to expand our influence in
new geographical areas
### Awards & Accomplishments
- ● Eagle Scout Award – Boy Scouts of America.
- ● COO of national club, Technology Students Association (TSA) at Lone Peak High School.
- ● Selected as a Hugh O’Brian Youth Leader.
- ● Awarded by American Legion Veterans Association as chapters Boys State Representative.
- ● Volunteer Leader at People Helping People Utah – Led over 40 people in project supporting single mothers.
- ● Special Olympics volunteer
<!-- ### Footer
Last updated: December 2021 -->
| 42 | 119 | 0.772873 | eng_Latn | 0.975974 |
4bcad83bc5d9e67ff15fd56ea9d0bbce86301327 | 6,383 | md | Markdown | README.md | impunitus/arkserver | a6fcbfb4410344225b8040a5ccd277eb9cdf23fe | [
"MIT"
] | 1 | 2021-12-18T08:54:47.000Z | 2021-12-18T08:54:47.000Z | README.md | impunitus/arkserver | a6fcbfb4410344225b8040a5ccd277eb9cdf23fe | [
"MIT"
] | 1 | 2021-12-29T21:22:19.000Z | 2022-01-02T13:38:35.000Z | README.md | calebbutcher/arkserver | a6fcbfb4410344225b8040a5ccd277eb9cdf23fe | [
"MIT"
] | null | null | null | 
# arkserver
Container to run an Ark Server, built off steamcmd base image with arkmanager
## Overview
This is an image for running an ARK: Survival Evolved server in a Docker container. It is heavily influenced by [thmhoag](https://github.com/thmhoag)'s [thmhoag/arkserverr](https://github.com/thmhoag/arkserver). We are also using [FezVrasta](https://github.com/FezVrasta)'s [arkmanager](https://github.com/FezVrasta/ark-server-tools) (ark-server-tools) to manage a single-instance ARK: Survival Evolved Server inside a docker container.
We are inheriting from [calebbutcher/steamcmd](https://github.com/calebbutcher/steamcmd) to ensure we have the latest version of `steamcmd`
For additional information on `arkmanager`, see: https://github.com/FezVrasta/ark-server-tools
### Features
* Auto install
* Configuration via Environment Variables
* Easy crontab manipulation for automated backups, updates, daily restarts, weekly dino wipes, etc
* Simple volume structure for server files, config, logs, backups, etc
* All features present in `arkmanager`
### Tags
* latest
## Usage
### Pulling container
```bash
docker pull impunitus/arkserver:latest
```
### Running the ARK Server
To run a basic server with no configuration changes:
```bash
$ docker run -d \
-v steam:/home/steam/Steam \ # mounted so that workshop downloads are persisted
-v ark:/ark \ # mounted as the directory to contain the server/backup/log/config files
-p 27015:27015 -p 27015:27015/udp \ # steam query port
-p 7778:7778 -p 7778:7778/udp \ # gameserver port
-p 7777:7777 -p 7777:7777/udp \ # gameserver port
impunitus/arkserver
```
### docker-compose (recommended, [see linuxserver's docs for more info](https://docs.linuxserver.io/general/docker-compose))
```yaml
version: "3.4"
services:
ark-server:
container_name: arkserver
image: impunitus/arkserver:latest
restart: unless-stopped
environment:
- PUID=${PUID} # default user id, defined in .env
- PGID=${PGID} # default group id, defined in .env
- TZ=${TZ} # timezone, defined in .env
volumes:
- /dockerMounts/steam:/home/steam/Steam # Mounted for workshop and mod persistance
- /dockerMounts/ark:/ark
ports:
- 7777:7777/tcp
- 7777:7777/udp
- 7778:7778/tcp
- 7778:7778/udp
- 27015:27015/tcp
- 27015:27015/udp
```
If the exposed ports are modified (in the case of multiple containers/servers on the same host) the `arkmanager` config will need to be modified to reflect the change as well. This is required so that `arkmanager` can properly check the server status and so that the ARK server itself can properly publish its IP address and query port to steam.
## Environment Variables
A set of required environment variables have default values provided as part of the image. You can edit these after first run of the container assuming you have persistant storage. More on that below:
| Variable | Value | Description |
| - | - | - |
| am_ark_SessionName | `Ark Server` | Server name as it will show on the steam server list |
| am_serverMap | `TheIsland` | Game map to load |
| am_ark_ServerAdminPassword | `k3yb04rdc4t` | Admin password to be used via ingame console or RCON |
| am_ark_MaxPlayers | `70` | Max concurrent players in the game |
| am_ark_QueryPort | `27015` | Steam query port (allows the server to show up on the steam list) |
| am_ark_Port | `7778` | Game server port (allows clients to connect to the server) |
| am_ark_RCONPort | `32330` | RCON port |
| am_arkwarnminutes | `15` | Number of minutes to wait/warn players before updating/restarting |
| am_arkflag_crossplay | `false` | Allow crossyplay with Players on Epic |
### Adding Additional Variables
Any configuration value that is available via `arkmanager` can be set using an environment variable. This works by taking any environment variable on the container that is prefixed with `am_` and mapping it to the corresponding environment variable in the `arkmanager.cfg` file.
For a complete list of configuration values available, please see [FezVrasta](https://github.com/FezVrasta)'s great documentation here: [arkmanager Configuration Files](https://github.com/FezVrasta/ark-server-tools#configuration-files)
## Volumes
This image has two main volumes that should be mounted as named volumes or host directories for the persistence of the server install and all related configuration files. More information on Docker volumes here: [Docker: Use Volumes](https://docs.docker.com/storage/volumes/)
| Path | Description |
| - | - |
| /home/steam/Steam | Directory of steam cache and other steamcmd-related files. Should be mounted so that mod installs are persisted between container runs/restarts |
| /ark | Directory that will contain the server files, config files, logs and backups. More information below |
### Subdirectories of /ark
Inside the `/ark` volume there are several directories containing server related files:
| Path | Description |
| - | - |
| /ark/backup | Location of the zipped backups genereated from the `arkmanager backup` command. Compressed using bz2. |
| /ark/config | Location of server config files. More information: |
| /ark/log | Location of the arkmanager and arkserver log files |
| /ark/server | Location of the server installation performed by `steamcmd`. This will contain the ShooterGame directory and the actual server binaries. |
| /ark/staging | Default directory for staging game and mod updates. Can be changed using in `arkmanager.cfg` |
### Editing arkmanager.cfg
I had two primary reasons for creating my own image for this was due to how the information in arkmanager.cfg was being overwriten on container restarts. The `run.sh` was taking values from the initial config and ignoring if the file it was creating already existed or not. I wanted to allow that data to persist so modified the script slightly to do so. The other issue was the base image of steamcmd was built on an out of date build of Ubuntu, and I wished to standardize this container on the same build of Ubuntu I run in my labs currently.
| 55.991228 | 546 | 0.750117 | eng_Latn | 0.98134 |
4bcbc012945f7246b0b0f44a995bd6f9685672aa | 88 | md | Markdown | README.md | yvrl/bios-backup | 7b9e7041ef1c1b687d49ad4f61e8b36495dcce29 | [
"BSD-3-Clause"
] | null | null | null | README.md | yvrl/bios-backup | 7b9e7041ef1c1b687d49ad4f61e8b36495dcce29 | [
"BSD-3-Clause"
] | null | null | null | README.md | yvrl/bios-backup | 7b9e7041ef1c1b687d49ad4f61e8b36495dcce29 | [
"BSD-3-Clause"
] | null | null | null | # bios-backup
A dump of a Thinkpad T420 bios chip in preparation for flashing Coreboot.
| 29.333333 | 73 | 0.795455 | eng_Latn | 0.914316 |
4bcbf686f732bf5a4fcd2c27631573fedc3c731d | 1,684 | md | Markdown | docs/dos-guidelines.md | radio24/onionjuggler | a297a0a16bcbc90a009f1d7be95a44d0a049b2ec | [
"MIT"
] | 17 | 2021-12-20T08:34:50.000Z | 2022-02-04T11:19:43.000Z | docs/dos-guidelines.md | nyxnor/onion-cli | a297a0a16bcbc90a009f1d7be95a44d0a049b2ec | [
"MIT"
] | 47 | 2021-11-29T02:15:46.000Z | 2022-02-23T11:54:11.000Z | docs/dos-guidelines.md | nyxnor/onion-cli | a297a0a16bcbc90a009f1d7be95a44d0a049b2ec | [
"MIT"
] | 2 | 2021-09-26T07:32:45.000Z | 2021-11-12T13:14:46.000Z | ## Onionbalance
[Onionbalance](https://onionbalance-v3.readthedocs.io/en/latest/v3/tutorial-v3.html) allows onion service operators to achieve the property of high availability by allowing multiple machines to handle requests for an onion service.
You can use Onionbalance to scale horizontally.
The more you scale, the harder it is for attackers to overwhelm you.
Onionbalance is available for [v3 onion services](https://blog.torproject.org/cooking-onions-reclaiming-onionbalance).
## Client authorization or multiple onion addresses to compartmentalize your users
If you have users you trust, give them dedicated onion service and client authorization credentials so that it can always be available.
For users you don't trust, split them into multiple addresses.
That said, having too many onion addresses is actually bad for your security (because of the use of many guard nodes), so try to use [client authorization](https://community.torproject.org/onion-services/advanced/client-auth) when possible.
## Webserver rate limiting
If attackers are overwhelming you with aggressive circuits that perform too many queries, try to detect that overuse and kill them using the `HiddenServiceExportCircuitID` torrc option.
You can use your own heuristics or use your web server's [rate limiting module](https://www.nginx.com/blog/rate-limiting-nginx/).
The above tips should help you keep afloat in turbulent times.
At the same time [we are working on more advanced defenses](https://blog.torproject.org/stop-the-onion-denial), so that less manual configuration and tinkering is needed by onion operators.
## Source
https://community.torproject.org/onion-services/advanced/dos/
| 64.769231 | 240 | 0.806413 | eng_Latn | 0.990298 |
4bcc19ea6c5868c1dbf8491d3dd0275f9161c154 | 385 | md | Markdown | README.md | wwyf/Waterfall | 8fc8b62d9e3c53fc2e63b9bc7fd8a115c7a37905 | [
"MIT"
] | null | null | null | README.md | wwyf/Waterfall | 8fc8b62d9e3c53fc2e63b9bc7fd8a115c7a37905 | [
"MIT"
] | null | null | null | README.md | wwyf/Waterfall | 8fc8b62d9e3c53fc2e63b9bc7fd8a115c7a37905 | [
"MIT"
] | 1 | 2019-07-07T16:23:47.000Z | 2019-07-07T16:23:47.000Z | # Waterfall
"鲜天下" 平台
## Prerequisite
- `docker : >= 18.09.6`
- `docker-compose : >= 1.8`
## How to deploy
You can deploy the frontend, the backend and the database with just three command.
```
git clone https://github.com/wwyf/Waterfall
cd Waterfall
docker-compose up -d
```
Then, the port 80 will be exposed to the port which docker selects. You can find it with `docker ps`. | 18.333333 | 101 | 0.698701 | eng_Latn | 0.984471 |
4bcc362fa3bb29394d10b65fac828669d2d9489b | 529 | md | Markdown | content/nagoya2e.md | hidienet/Hugo | 5e7f211db507e2298e2f9694416f0129211e1782 | [
"Apache-2.0"
] | null | null | null | content/nagoya2e.md | hidienet/Hugo | 5e7f211db507e2298e2f9694416f0129211e1782 | [
"Apache-2.0"
] | null | null | null | content/nagoya2e.md | hidienet/Hugo | 5e7f211db507e2298e2f9694416f0129211e1782 | [
"Apache-2.0"
] | 1 | 2020-11-24T12:08:27.000Z | 2020-11-24T12:08:27.000Z | ---
title: '[GO! GO! NaGoYa～] Day2：俺の 杏仁豆腐'
date: 2015-10-01T23:39:00.000+08:00
draft: false
aliases: [ "/2015/10/go-go-nagoya-day2_1.html" ]
tags : [travel-日本-名古屋, flavor - 螞蟻族]
---
繼續邪惡的宵夜時間
雖然「杏仁亦要花氣力」（！）
但不妨礙我對這味道的熱愛
一大大大杯的杏仁豆腐！
**445g！** 大概是平日分量的兩倍多
平時很怕杏仁豆腐會太硬
然而這杯不會啊
也沒有水汪汪的情況
吃到一半，發現還有好多好多椰果
不會因為整杯都是同一樣東西（很悶的）
完成了整杯都沒有覺得太甜
但就有滿滿的杏仁味
啊～ 還滿足呢（飽）
\-----------------------------------------------
延伸閱讀：[GO! GO! NaGoYa～（8D7N）](https://hidie.net/nagoya8d7n/)
| 17.633333 | 59 | 0.595463 | yue_Hant | 0.677431 |
4bccbc13d11fae4dd376db85e6d7eb96a026b0c7 | 10,964 | md | Markdown | Documentation/Advanced_Logging.md | naxos/NXLogging | 037448a06f343cd028db65de7ff4b57092372496 | [
"BSD-2-Clause",
"Unlicense"
] | null | null | null | Documentation/Advanced_Logging.md | naxos/NXLogging | 037448a06f343cd028db65de7ff4b57092372496 | [
"BSD-2-Clause",
"Unlicense"
] | null | null | null | Documentation/Advanced_Logging.md | naxos/NXLogging | 037448a06f343cd028db65de7ff4b57092372496 | [
"BSD-2-Clause",
"Unlicense"
] | null | null | null | Advanced Logging
================
This is about
- [Using different log levels](#log_levels)
- [Logging errors](#logging_errors)
- [Logging exceptions](#logging_exceptions)
- [Using variables in your log messages](#log_variables)
<a name="log_levels"></a>
Log Levels
----------
NXLogging supports the eight log levels first introduced with syslog back in the 1980s. The Apple System Log (ASL) uses the same:
- Debug
- Info
- Notice
- Warning
- Error
- Critical
- Alert
- Emergency
In your code you will use these log levels with the prefix _NXLogLevel_. In Objective C you could write
```objectivec
NXLogLevel level = NXLogLevelWarning;
```
and in Swift
```swift
let level: NXLogLevel = NXLogLevel.Warning // or for short: .Warning
```
On a side note: In our documentation ---and partially in the API--- we will use the terms _log level_ and _severity_, which refer to the same concept but counter-directional: _Debug_ is the __highest log level__ (most detailled) but has the __lowest severity__ (least impact). Therefore, if you configure a log target's __maximum log level__ to _Error_, it will log only log messages with a __level up to__ _Error_ (_Error_, _Critical_, _Alert_ and _Emergency_). For adjusting the maximum log level, refer to [Customisation](Customisation.md).
The log levels are defined in the public header file _NXLogTypes.h_. You will also find some additional documentation there.
You can use the log levels to your liking but know, that some backends might filter log messages according to their severity. The Apple System Log, e.g. by default only accepts messages with a severity of _Notice_ or higher.
The standard log configured in NXLogging logs to the _console_ (usually the Xcode debug console) and to the _system_ (ASL, usually what you see accessing the system) log. The maximum log level for the _console_ is preconfigured to _Debug_ and for the _system_ to _Notice_ (the latter coinsides with the default setting of ASL).
<a name="logging_errors"></a>
Logging errors
--------------
Here is an example on error handling and logging in Objective C:
```objectivec
NSString *path = [[NSBundle mainBundle] pathForResource:@"test" ofType:@"txt"];
NSError *error = nil;
NSString *content = [NSString stringWithContentsOfFile:path encoding:NSUTF8StringEncoding error:&error];
if(error) {
NXLogError(NXLogLevelError, error, @"Unable to read file %@", path.lastPathComponent);
} else {
NXLog(NXLogLevelDebug, @"Got content:'%@' from file %@", content, path.lastPathComponent);
}
```
and here in Swift:
```swift
let path : NSString! = NSBundle.mainBundle().pathForResource("test", ofType: "txt")
do {
let content = try NSString(contentsOfFile: path as String, encoding: NSUTF8StringEncoding)
NXLogger.log(.Debug, format: "Got content '%@' from file %@", content, path.lastPathComponent)
} catch {
NXLogger.log(.Error, error: error, format: "Unable to read file %@", path.lastPathComponent)
}
```
Appart from the obviously different error handling in the two languages, the logging is pretty much the same. If the encoding file in the examples is not UTF-8, you'll get a log message like this:
<pre style="font-size: 11px">2016-03-12 16:37:43 <Error>: com.naxos-software.NXLoggingSample logSomething()(LogClientSwift.swift:92) - Unable to read file test.txt
Error: The operation couldn’t be completed. (NSCocoaErrorDomain, error 261)
</pre>
Here's another Swift example. Assume the implementation of a vending machine (adopted from Apple's [error handling guide](https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/ErrorHandling.html)):
```swift
enum VendingMachineError: ErrorType {
case InvalidSelection
case InsufficientFunds(coinsNeeded: Int, coinsInserted: Int)
case OutOfStock
}
func buyBeer(coins: Int) throws {
if (coins < 5) {
throw VendingMachineError.InsufficientFunds(coinsNeeded: 5, coinsInserted: coins)
} else {
ejectBeer();
}
}
```
As a caller, you can simply log an error like this:
```swift
do {
try buyBeer(3)
} catch {
NXLogger.log(error: error)
}
```
In Swift, you can omit the log level for the log method and leave it to the logger to find a suitable one. Here it will use _NXLogLevel.Error_, because an _ErrorType_ was logged. Also note the details of the error message, which you get in the second line of the log output even though the error was just an enum value:
<pre style="font-size: 11px">2016-03-12 16:37:43 <Error>: com.naxos-software.NXLoggingSample swiftSpecificExamples()(LogClientSwift.swift:130)
Error: InsufficientFunds(5, 3) (NXLoggingSample.VendingMachineError, error 1)
</pre>
You can also handle the error in a slightly more elaborate way and add some information to the log by using the _NSError_ extension of NXLogging:
```swift
do {
try buyBeer(3)
} catch VendingMachineError.InsufficientFunds(let p) {
NXLogger.log(error: NSError(VendingMachineError.InsufficientFunds(p),
reason: "\(p.coinsInserted) coins inserted but \(p.coinsNeeded) coins are needed",
suggestion: "Insert \(p.coinsNeeded - p.coinsInserted) more coins"))
} catch let error as VendingMachineError {
NXLogger.log(error: NSError(error, suggestion: "Try banging the machine"))
} catch {
NXLogger.log(error: error)
}
```
The result will look something like this:
<pre style="font-size: 11px">2016-03-12 16:37:43 <Error>: com.naxos-software.NXLoggingSample swiftSpecificExamples()(LogClientSwift.swift:145)
Error: InsufficientFunds(5, 3) (NXLoggingSample.VendingMachineError, error 1)
Reason: 3 coins inserted but 5 coins are needed
Suggestion: Insert 2 more coins
</pre>
Especially in Objective C, where you are stuck with _NSError_, NXLogging's extension makes it more convenient creating _NSError_ instances:
```objectivec
NSError *err = [NSError errorWithCode: -2
description: @"Unable to complete this operation"
reason: @"The request timed out"
suggestion: @"Try again later"
underlyingError: [NSError errorWithCode: -1 description: @"Time-out error"]];
```
In most cases you don't have to deal with the _userInfo_ dictionary and if omitted, _NSError_ will use an error domain derived from the bundle identifier of your application. Logging the error above will result in log output similar to the one below (note how underlying errors are included recursively):
<pre style="font-size: 11px">2016-03-12 16:37:43 <Error>: com.naxos-software.NXLoggingSample [LogClientObjC logSomething](LogClientObjC.m:33)
Error: Unable to complete this operation (NXLoggingSampleErrorDomain, error -2)
Reason: The request timed out
Suggestion: Try again later
Caused by: Time-out error (NXLoggingSampleErrorDomain, error -1)
</pre>
<a name="logging_exceptions"></a>
Logging exceptions
------------------
We don't want to encourage you to raise and catch exceptions all over your Objective-C or (even worse) Swift code. In rare cases however, exception handling might be necessary. NXLogging comes with an extension to the _NSException_ class, which allows for __nested exceptions__ by adding the property __cause__. It also adds a static method __probe__, which is particular useful in Swift, because Swift does not come with a standard way to catch a raised _NSException_.
In Objective C you can create and raise and catch exceptions like this:
```objectivec
- (void)badGuy {
[NSException raise:@"BadGuyException" format:@"Trouble is my middle name"];
}
- (void)handleBadGuy {
NSException *exception = [NSException probe:^{ [self badGuy]; }];
[NSException raise:@"TooBadException" cause:exception format:@"Can't handle the %@", @"bad guy"];
}
```
And the equivalent in Swift:
```swift
func badGuy() {
NSException.raise("BadGuyException", format: "Trouble is my middle name")
}
func handleBadGuy() {
let exception = NSException.probe(badGuy)
NSException.raise("TooBadException", cause: exception, format: "Can't handle the %@", "bad guy")
}
```
Now, if you log an exception in Objective C:
```objectivec
NSException *exception = [NSException probe:^{ [self handleBadGuy]; }]; // We could also do @try @catch here
NXLogException(NXLogLevelNotice, exception, @"Something sinister is going on");
```
or in Swift:
```swift
let exception = NSException.probe(handleBadGuy)
NXLogger.log(.Notice, exception: exception, format: "Something sinister is going on")
```
you'll end up with log like this:
<pre style="font-size: 11px">2016-03-12 16:37:43 <Notice>: com.naxos-software.NXLoggingSample logSomething()(LogClientSwift.swift:90) - Something sinister is going on
Exception: Can't handle the bad guy (TooBadException)
Caused by: Trouble is my middle name (BadGuyException)
>> Log with severity Error or higher to enable call stack symbols <<
</pre>
As the last line of the log output states, logging an exception with the severity _Error_ or above, will cause the logger to include the __call stack symbols__ in the log. You can configure this threshold on the log target (see [Customisation](Customisation.md)).
<a name="log_variables"></a>
Log variables
-------------
Let us assume, that you don't want every line in your logs to include a lot of information on the client's environment, which sometimes might be advisable for a production system (see [Customisation](Customisation.md) on how to achieve this). Let us also assume, that for some particular log messages you _do_ want to include some info. In such a case, you can make use of __log variables__:
```swift
NXLogger.log(.Warning, format: "This feature is not available in $(systemName) $(systemVersion).")
NXLogger.log(.Error, format: "Sorry, this device ($(deviceModel)) does not make coffee.")
// You can also put variables in the format arguments ...
NXLogger.log(.Info, format: "Application %@ started on %@ with process ID %@.", "$(processName)", "$(deviceName)", "$(processID)")
// ... or even mix it like this
NXLogger.log(.Emergency, format: "HELP WANTED: Can some Swift expert fix function $(%@) in file $(%@)?", "function", "file")
```
The variables currently supported are:
- file
- function
- line
- module
- date
- processName
- processID
- deviceName
- deviceModel
- systemName
- systemVersion
Logging with the statements above, will result in log lines like this:
<pre style="font-size: 11px">2016-03-12 16:37:43 <Warning>: This feature is not available in iPhone OS 9.2.
2016-03-12 16:37:43 <Error>: Sorry, this device (x86_64) does not make coffee.
2016-03-12 16:37:43 <Info>: Application NXLoggingSample started on iPhone Simulator with process ID 63132.
2016-03-12 16:37:43 <Emergency>: HELP WANTED: Can some Swift expert fix function logSomething() in file LogClientSwift.swift?
</pre>
| 42.332046 | 543 | 0.738234 | eng_Latn | 0.952914 |
4bccf99e1e626676ecbc2b74111f01c5105e3bc7 | 2,079 | md | Markdown | _posts/2018-07-11-whats-your-developer-identity.md | arshad115/arshad115.github.io | 40b18e442efabb6cc4a78c1ba523d9d10ddd4dc9 | [
"MIT"
] | 1 | 2018-06-06T23:57:47.000Z | 2018-06-06T23:57:47.000Z | _posts/2018-07-11-whats-your-developer-identity.md | arshad115/arshad115.github.io | 40b18e442efabb6cc4a78c1ba523d9d10ddd4dc9 | [
"MIT"
] | 1 | 2018-08-16T13:42:15.000Z | 2018-08-20T12:13:09.000Z | _posts/2018-07-11-whats-your-developer-identity.md | arshad115/arshad115.github.io | 40b18e442efabb6cc4a78c1ba523d9d10ddd4dc9 | [
"MIT"
] | null | null | null | ---
title: Whats your identity?
tags: Developer Identity
header:
image: /assets/images/ariana.jpg
caption: "Photo credit: [**Vevo/Ariana Grande**](https://www.youtube.com/watch?v=ffxKSjUwKdU)"
comments: true
---
We have many identities, identity for work, identity for friends and a different identity for home. But, I want to write about the developer identity, what is your software developer identity?
I recently read a blog post from Sittiphol Phanvilai with the title ["Introduce yourself as a single message" … A secret of identity building.](https://medium.com/@nuuneoi/introduce-yourself-as-a-single-message-a-secret-of-identity-building-f24ff06c345f) and sort of came to the same conclusion.
Just 10 years ago there weren't as many frameworks and programming languages as there are now. Back then you could easily say that I have worked with this, this, this and this technology. I also used to say the same exact thing. But now, the times have changed and everyday there is a new framework or a programming language. Its hard to keep up to date with all of them. In my opinion what matters now is that you should know how to acquire a certain skill rather than knowing the complete skill in depth.
I self taught myself Android development but then I started my career as a C# and ASP.Net developer. At that time my android skills weren't as polished so my developer identity was a web developer for ASP.NET. You always have multiple identities, though it also depends on the context, for my second job, I was looking for mobile app development jobs, so at that time my developer identity was that of an Android developer. So, depending on the context you should represent your strongest identity with which you can related to the discussion at hand. If I meet someone now and they tell me if they work on Angular, I would say "High five! I am also and Angular developer!", since it is my strongest identity to connect with.
TLDR; You should represent your strongest developer identity with which you can related to the discussion at hand.
| 109.421053 | 727 | 0.780664 | eng_Latn | 0.999828 |
4bcd9f3249c78bbeaa3e57ba4a82868614f34546 | 2,402 | md | Markdown | Human Technology Interaction/Advanced Cognitive Engineering/presentations/README.md | Ohara124c41/Seminar_Papers | ef08e5810e4fea7b4d66073e0a37e96c714909dd | [
"MIT"
] | 1 | 2019-09-25T06:33:23.000Z | 2019-09-25T06:33:23.000Z | Human Technology Interaction/Advanced Cognitive Engineering/presentations/README.md | Ohara124c41/Seminar_Papers | ef08e5810e4fea7b4d66073e0a37e96c714909dd | [
"MIT"
] | null | null | null | Human Technology Interaction/Advanced Cognitive Engineering/presentations/README.md | Ohara124c41/Seminar_Papers | ef08e5810e4fea7b4d66073e0a37e96c714909dd | [
"MIT"
] | 1 | 2020-11-14T20:08:08.000Z | 2020-11-14T20:08:08.000Z | 
| 184.769231 | 205 | 0.860117 | yue_Hant | 0.653127 |
4bcda0d99c929268b721f229a3876f44d9bd4bbb | 1,919 | md | Markdown | rpc_lib/README.md | deacon-ralph/irc_bot | 62c8a6d0f9890b3fbfd356f533e9d58c38bbc176 | [
"WTFPL"
] | 2 | 2021-09-30T03:19:15.000Z | 2021-12-30T04:18:46.000Z | rpc_lib/README.md | deacon-ralph/irc_bot | 62c8a6d0f9890b3fbfd356f533e9d58c38bbc176 | [
"WTFPL"
] | 7 | 2021-10-01T02:38:39.000Z | 2022-02-17T04:58:48.000Z | rpc_lib/README.md | deacon-ralph/irc_bot | 62c8a6d0f9890b3fbfd356f533e9d58c38bbc176 | [
"WTFPL"
] | null | null | null | # RPC Module
## Installing from PyPi
`pip3 install nooscope_rpc`
Example implementation
```python
import asyncio
import nooscope_rpc.api as api
class Impl(api.IrcImpl):
async def on_message(self, target, by, message):
print(target, by, message)
# do some shit like
if message == 'hack_a_gibson':
await self.rpc.send_message(target, 'hacking gibson from RPC')
elif message.startswith('dieplz'):
await self.rpc.disconnect()
exit(1)
async def main():
# endless loop to always try and connect
while True:
tcp = api.TcpClient(
'127.0.0.1', # use your bots host ip
12345,
Impl(),
cafile='path/to/yourcafile.cert'
)
await tcp.connect()
await tcp.read()
loop = asyncio.get_event_loop()
loop.run_until_complete(main())
```
<br/>
<br/>
#### 🚨Important info before starting to implement your own client not using this library🚨
*Messages are terminated by a nullbyte 0x00.
This means at the end of any message you send, add 0x00 byte. Any message you
receive from the server will be ended with 0x00*
## Info for those who want to implement their own client
### Supported Messages you can send from the client
1. Sending a message to a channel or user
- `CLIENT_CMD:SEND_MESSAGE:{"target": "#channel/user", "message": "hello world:"}`
2. Telling the server you are disconnecting
- `CLIENT_END:`
### Supported Message you can receive from the server
1. On message in a channel or from user
- `SERVER_EVENT:ON_MESSAGE:{"target": "#channel/user", "by": "user_who_sent_msg", "message": "hello world"}`
2. On RPC Server restarting
- `SERVER_EVENT:RESTARTING`
<br/>
<br/>
## Building wheel + src
```bash
# https://packaging.python.org/tutorials/packaging-projects/
python3.9 -m pip install --upgrade build
python3.9 -m build
python3.9 -m twine upload --repository testpypi dist/*
``` | 25.586667 | 111 | 0.684732 | eng_Latn | 0.946741 |
4bcda26f7f536769cb1e08a4daeed692f528d939 | 3,850 | md | Markdown | CONTRIBUTING.md | lineagech/gds-nvidia-fs | 61efcb66ed986ae1e4d73c6b1652fa0e3d65142d | [
"MIT"
] | 1 | 2021-05-23T02:02:54.000Z | 2021-05-23T02:02:54.000Z | CONTRIBUTING.md | lineagech/gds-nvidia-fs | 61efcb66ed986ae1e4d73c6b1652fa0e3d65142d | [
"MIT"
] | null | null | null | CONTRIBUTING.md | lineagech/gds-nvidia-fs | 61efcb66ed986ae1e4d73c6b1652fa0e3d65142d | [
"MIT"
] | null | null | null | # Contributing to gds-nvidia-fs
Contributions are always welcome!
Your contributions will have the best chance of being addressed and accepted
smoothly if you understand and follow our guidelines.
## General Guidelines
#### File Issue First
Any suggestions or bug reports should start with issue for tracking and
discussion. We want to know about bugs as soon as possible.
Features or changes should have discussion before you get started, so we can
be sure they fit the overall goals and scope of the project
(GPUDirect Storage).
#### Versioning
Versioning follows [Semantic Versioning](https://semver.org/).
#### Releace Cycle and Flow
The `master` branch will alwys have the latest code.
Standard fork and pull request workflow.
Version bumps will have seperate commits and tags. So please do not include
a version change in your pull request.
Not every change will get a PATCH version bump and GitHub release.
MINOR version releases, where we reconsider what filesystems and minor features are supported
without change in protocols and public interfaces.
MAJOR version releases - aiming to never break backward compatability.
#### Commit Messages
All commit messages should follow
[Conventional Commits](https://www.conventionalcommits.org/).
#### Pull Request Scope & Method
Each pull request should address a single overall feature or bug if possible.
If the change requires documentation updates those should be in the SAME
pull request.
This makes reviews easier, rollbacks manageable, and the history clearer.
Merges will be done as "Squash and Merge" in most cases, so do not worry
about having multiple commits.
#### Formatting
Try to follow the existing formats of files you modify.
* Clarity over brevity.
* Less than 80 columns whenever reasonable.
## Sign your work
The sign-off is a simple line at the end of the explanation for the patch.
Your signature certifies that you wrote the patch or otherwise have the right
to pass it on as an open-source patch. The rules are pretty simple: if you
can certify the below
(from [developercertificate.org](http://developercertificate.org/)):
```
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
```
Then you just add a line to every git commit message:
Signed-off-by: Joe Smith <joe.smith@email.com>
Use your real name (sorry, no pseudonyms or anonymous contributions.)
If you set your `user.name` and `user.email` git configs, you can sign your
commit automatically with `git commit -s`.
| 34.375 | 93 | 0.773766 | eng_Latn | 0.999645 |
4bcdf610b1f81094560a016b925c099a0d853d82 | 531 | md | Markdown | readme/functions.md | TomoakiNagahara/op-core | 6d70a60e5c5b5e5b99fc8f00f212e7698bd50486 | [
"Apache-2.0"
] | 3 | 2015-02-19T07:03:34.000Z | 2015-04-07T13:42:01.000Z | readme/functions.md | TomoakiNagahara/op-core | 6d70a60e5c5b5e5b99fc8f00f212e7698bd50486 | [
"Apache-2.0"
] | 1 | 2015-09-26T13:09:42.000Z | 2015-09-27T13:56:03.000Z | readme/functions.md | TomoakiNagahara/op-core | 6d70a60e5c5b5e5b99fc8f00f212e7698bd50486 | [
"Apache-2.0"
] | null | null | null | onepiece-framework's standard functions
===
## Meta path
### RootPath()
`RootPath()` is register function of meta path.
```php
\OP\RootPath('test', __DIR__);
```
### ConvertPath()
`ConvertPath()` is convert meta path to real path.
That is registered by RootPath.
```php
\OP\ConvertPath('test:/');
```
### ConvertURL()
`ConvertURL()` is convert meta path to URL.
However domain name is not included.
```php
\OP\ConvertURL('test:/');
```
### Html()
```php
\OP\Html('Hello, world.', 'DIV #id .class_1 .class_2');
```
| 14.351351 | 55 | 0.638418 | eng_Latn | 0.717201 |
4bcea114963c1475f9b9d534862c1e0d804966ed | 422 | md | Markdown | pages/system-components/ansible-tower/controls/NIST-800-53-MP-6 8.md | ComplianceAsCode/uswds-opencontrol | 0b068f8433018c4b603057e1088a9930e9b303c5 | [
"CC0-1.0"
] | null | null | null | pages/system-components/ansible-tower/controls/NIST-800-53-MP-6 8.md | ComplianceAsCode/uswds-opencontrol | 0b068f8433018c4b603057e1088a9930e9b303c5 | [
"CC0-1.0"
] | null | null | null | pages/system-components/ansible-tower/controls/NIST-800-53-MP-6 8.md | ComplianceAsCode/uswds-opencontrol | 0b068f8433018c4b603057e1088a9930e9b303c5 | [
"CC0-1.0"
] | null | null | null | #NIST-800-53-MP-6 8
##Remote Purging / Wiping Of Information
#### Description
"The organization provides the capability to purge/wipe information from [Assignment: organization-defined information systems, system components, or devices] either remotely or under the following conditions: [Assignment: organization-defined conditions]."
No information found for the combination of standard NIST-800-53 and control MP-6 (8)
| 70.333333 | 257 | 0.805687 | eng_Latn | 0.992289 |
4bcf2b641bf14b3b51fff0eed423a9bd3789f630 | 733 | md | Markdown | data/content/lord-el-melloi-ii-case-files-material/trisha-fellows.ja.md | tmdict/tmdict | c2f8ddb7885a91d01343de4ea7b66fea78351d94 | [
"MIT"
] | 3 | 2022-02-25T11:13:45.000Z | 2022-02-28T11:55:41.000Z | data/content/lord-el-melloi-ii-case-files-material/trisha-fellows.ja.md | SomiaWhiteRing/tmdict | 13c6c818c84a65ee956535e08d20246bde87dd48 | [
"MIT"
] | null | null | null | data/content/lord-el-melloi-ii-case-files-material/trisha-fellows.ja.md | SomiaWhiteRing/tmdict | 13c6c818c84a65ee956535e08d20246bde87dd48 | [
"MIT"
] | 2 | 2022-02-25T09:59:50.000Z | 2022-02-28T11:55:09.000Z | ---
parent: trisha-fellows
source: lord-el-melloi-ii-case-files-material
id: lord-el-melloi-ii-case-files-glossary
language: ja
weight: 36
category:
- person
---
オルガマリーの従者。未来視の魔眼を持つ、不思議髪型系。
属性は水。
作中に描かれた通り、彼女の予測の未来視はより遠い未来ほど曖昧となり、場所については未来の自分自身が存在するか、現在自分がいる（と彼女が認識している）座標に限定される。
魔眼オークシヨンで虹の魔眼が出品されると予測したのは、これによる錯誤だ。
つまりは「トリシャ自身とオルガマリーがオークションに参加して、虹に匹敵する魔眼が出品される未来」を視たためだが……おそらく、この予測自体が視界を狂わせるハートレスの魔眼の影響を受けていたのだろう。虹の魔眼の視界さえ簒奪しうる、ハートレスの魔眼の情報を、トリシャは間違えて読んでしまったのだ。
魔眼蒐集列車に乗り込んだのは、虹の魔眼ほどの神秘を手に入れて、マリスビリーに愛されなくなったオルガマリーに、それでも戦うための手段を与えてやりたかったため。また、マリスビリーに疑念を抱いた彼女が、七年前の連続殺人事件の真相を暴くためでもあった。
連続殺人事件の関係者と出会う、という未来視は正しかった。魔眼に対してさまざまな防御手段も講じていたが……結局、未来視では防御できぬ過去からの刃によって命を奪われることとなった。「お馬鹿なマリー。しゃんとなさい」
家庭教師として厳しくあたっていたが、彼女のオルガマリーへの愛情は本物であった。
| 38.578947 | 145 | 0.877217 | jpn_Jpan | 0.886747 |
4bcf9edb93caa85d61d84b4b15c628b44ea9bf01 | 901 | md | Markdown | README.md | jredrado/wapc-guest-rust | a35162a9151866bd983635cba688e3ec419c5ae4 | [
"Apache-2.0"
] | 21 | 2019-11-06T16:15:15.000Z | 2021-12-22T07:13:44.000Z | README.md | jredrado/wapc-guest-rust | a35162a9151866bd983635cba688e3ec419c5ae4 | [
"Apache-2.0"
] | 3 | 2020-03-17T17:18:20.000Z | 2021-08-30T13:53:46.000Z | README.md | jredrado/wapc-guest-rust | a35162a9151866bd983635cba688e3ec419c5ae4 | [
"Apache-2.0"
] | 9 | 2019-09-23T20:57:16.000Z | 2022-01-19T18:27:40.000Z | 
# waPC Guest SDK
The waPC Guest SDK is used by Rust developers building workloads for the `wasm32-unknown-unknown` target that will conform to the [waPC](https://wascap.io/comms) (WebAssembly Procedure Calls) specification.
This crate is used by [waSCC](https://wascc.dev) as a foundation for its secure, dynamic binding of cloud capabilities on top of the **waPC** spec.
# Example
```rust
extern crate wapc_guest as guest;
use guest::prelude::*;
#[no_mangle]
pub extern "C" fn wapc_init() {
register_function("sample:Guest!Hello", hello_world);
}
fn hello_world(_msg: &[u8]) -> CallResult {
let _res = host_call("myBinding", "sample:Host", "Call", b"hello")?;
Ok(vec![])
}
```
| 32.178571 | 207 | 0.715871 | eng_Latn | 0.791632 |
4bd27dfb2b695ae76c439e4335cb55fda069d717 | 583 | md | Markdown | README.md | 07septiembre/Host-Scanner | 8d4433330d8eab7a68bb1129e3ab89971a85dfa3 | [
"MIT"
] | null | null | null | README.md | 07septiembre/Host-Scanner | 8d4433330d8eab7a68bb1129e3ab89971a85dfa3 | [
"MIT"
] | null | null | null | README.md | 07septiembre/Host-Scanner | 8d4433330d8eab7a68bb1129e3ab89971a85dfa3 | [
"MIT"
] | null | null | null | # Host-Scanner
Este script busca host de subdominios, para Internet gratis con http injector etc.
# comandos a instalar:
# pkg update
# pkg upgrade
# pkg install ruby
# gem install lolcat
# git clone https://github.com/07septiembre/Host-Scanner.git
# cd Host-Scanner
# chmod 777 Host-Scanner.sh
# bash Host-Scanner.sh
# Ejemplo de uso.
#╔────── ¤ ¤ ──────╗
# Ingresa tu URL
#╚────── ¤ ¤ ──────╝
# www.movistar.com
#╔────── ¤ ¤ ──────╗
# Ingresa un puerto
#╚────── ¤ ¤ ──────╝
# 443
Esto es un ejemplo.
#canal de youtube.
https://youtube.com/channel/UCgv0D7I9EWLKrx6ckA3pUoQ
| 20.103448 | 82 | 0.643225 | spa_Latn | 0.35419 |
4bd2b53bf3acf695070b2d0584a7b833f48ed9e6 | 170 | md | Markdown | README.md | rajatvd/WriteFileAndRun | cf0ca4d06b188d4160e76e0a839be2fdcb03a8e5 | [
"MIT"
] | null | null | null | README.md | rajatvd/WriteFileAndRun | cf0ca4d06b188d4160e76e0a839be2fdcb03a8e5 | [
"MIT"
] | null | null | null | README.md | rajatvd/WriteFileAndRun | cf0ca4d06b188d4160e76e0a839be2fdcb03a8e5 | [
"MIT"
] | null | null | null | # IPython cell magic to write to a file and run a cell
Usage:
%%writefile_run \<filename\> \<options\>
Options:
* -a Append to the end of file
* -dr Don't run the cell
| 18.888889 | 54 | 0.694118 | eng_Latn | 0.93969 |
4bd363593bc861492118c721ed310c8ae4ccf1f8 | 84 | md | Markdown | README.md | hpennington/Shapes | bc67ac69a4362a9489461bb30667bf60cbc26277 | [
"MIT"
] | null | null | null | README.md | hpennington/Shapes | bc67ac69a4362a9489461bb30667bf60cbc26277 | [
"MIT"
] | null | null | null | README.md | hpennington/Shapes | bc67ac69a4362a9489461bb30667bf60cbc26277 | [
"MIT"
] | null | null | null | # Shapes
A simple example demonstrating SwiftBook with both iOS and macOS targets.
| 21 | 73 | 0.809524 | eng_Latn | 0.99576 |
4bd3d025702c950cc20a48f97622096d5b7f2a40 | 58 | md | Markdown | README.md | zhaozzq/EventBaseOnResponderChain | 2fa9d2a3785b328423b37c2ff2ca44ca47f0ca27 | [
"MIT"
] | null | null | null | README.md | zhaozzq/EventBaseOnResponderChain | 2fa9d2a3785b328423b37c2ff2ca44ca47f0ca27 | [
"MIT"
] | null | null | null | README.md | zhaozzq/EventBaseOnResponderChain | 2fa9d2a3785b328423b37c2ff2ca44ca47f0ca27 | [
"MIT"
] | null | null | null | #EventBaseOnResponderChain
Event base on responder chain. | 29 | 30 | 0.862069 | fra_Latn | 0.254786 |
4bd3d4608a54634de75af40040a3aea6a5588217 | 587 | md | Markdown | content/home/contact.md | multimethods/multimethods.github.io | 789e87577fc1cb79c63b1104f730a610a3c48a6b | [
"MIT"
] | null | null | null | content/home/contact.md | multimethods/multimethods.github.io | 789e87577fc1cb79c63b1104f730a610a3c48a6b | [
"MIT"
] | null | null | null | content/home/contact.md | multimethods/multimethods.github.io | 789e87577fc1cb79c63b1104f730a610a3c48a6b | [
"MIT"
] | null | null | null | +++
# Contact page.
widget = "blank"
headless = true # This file represents a page section.
weight = 300
active = true
# ... Put Your Section Options Here (title etc.) ...
title = "Contact"
[design]
# Choose how many columns the section has. Valid values: 1 or 2.
columns = "2"
+++
Dr. Christine Bauer\
Utrecht University\
Department of Information and Computing Sciences\
c.bauer\@uu.nl\
https://christinebauer.eu/
Dr. Eva Zangerle\
Universität Innsbruck\
Department of Computer Science\
Databases and Information Systems\
eva.zangerle\@uibk.ac.at\
https://www.evazangerle.at
| 20.241379 | 66 | 0.727428 | eng_Latn | 0.492598 |
4bd473b993e57eb762816be6ccc1ce63dfff570f | 2,917 | md | Markdown | _posts/2018-11-29-nextjs-with-jest.md | min9nim/smg.github.io | 2252d76d2b0f4c71900a1f4b59669b9803f1c9e0 | [
"MIT"
] | null | null | null | _posts/2018-11-29-nextjs-with-jest.md | min9nim/smg.github.io | 2252d76d2b0f4c71900a1f4b59669b9803f1c9e0 | [
"MIT"
] | 18 | 2020-05-13T21:24:07.000Z | 2022-02-28T01:41:38.000Z | _posts/2018-11-29-nextjs-with-jest.md | min9nim/smg.github.io | 2252d76d2b0f4c71900a1f4b59669b9803f1c9e0 | [
"MIT"
] | 2 | 2020-05-30T11:22:49.000Z | 2020-06-26T08:37:57.000Z | ---
layout: post
title: "[JEST] Nextjs 에서 jest 사용하기"
date: 2018-11-29 00:10
categories: jest
tags: [jest, TDD, node, Nextjs]
---
Nextjs 프로젝트에서 [지난 포스트의 방법](/2018/11/jest-module/)대로 jest 구성을 하니 Nextjs 프로젝트를 빌드할 때 아래와 같은 오류가 발생했다.
```
$ npm run build
> sharelink-nextjs@1.0.0 build /Users/songmingu/Documents/project/sharelink-nextjs
> next build
[12:28:59] Compiling server
[12:28:59] Compiling client
> Using external babel configuration
> Location: "/Users/songmingu/Documents/project/sharelink-nextjs/.babelrc"
[12:28:59] Compiled server in 476ms
[12:29:01] Compiled client in 2s
> Failed to build
{ Error: (client) ./pages/index.js
Module build failed (from ./node_modules/next/dist/build/webpack/loaders/next-babel-loader.js):
SyntaxError: /Users/songmingu/Documents/project/sharelink-nextjs/pages/index.js: Unexpected token (91:6)
89 | //console.log("@@ app.state.totalCount = " + app.state.totalCount);
90 | return (
> 91 | <Layout>
| ^
92 | <div className="intro">{"* " + intro + "(" + app.state.totalCount + "개)"}</div>
93 | {/* <div className="intro">{"* " + intro}</div> */}
94 | <ul className="PostList">
at Parser.raise (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:3939:15)
at Parser.unexpected (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:5248:16)
at Parser.parseExprAtom (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:6328:20)
at Parser.parseExprSubscripts (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:5924:21)
at Parser.parseMaybeUnary (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:5903:21)
at Parser.parseExprOps (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:5812:21)
at Parser.parseMaybeConditional (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:5784:21)
at Parser.parseMaybeAssign (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:5731:21)
at Parser.parseParenAndDistinguishExpression (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:6482:28)
at Parser.parseExprAtom (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:6284:21)
at Parser.parseExprSubscripts (/Users/songmingu/Documents/project/sharelink-nextjs/node_modules/@babel/parser/lib/index.js:5924:21)
=== 중략 ===
```
<br>
구글링 결과 Nextjs 에서 jest 를 사용하려면 `babel-plugin-transform-es2015-modules-commonjs` 를 추가로 설치할 필요 없이 그냥 아래와 같이 `.babelrc` 를 설정하면 되더라
```
{
"presets": ["next/babel"]
}
```
<br>
#### Ref.
<https://github.com/zeit/next.js/tree/canary/examples/with-jest> | 49.440678 | 150 | 0.737059 | kor_Hang | 0.367637 |
4bd481c12368453935219399a744169f8ee727f1 | 3,095 | md | Markdown | 0501-0600/510-Inorder Successor in BST II/README.md | jiadaizhao/LeetCode | 4ddea0a532fe7c5d053ffbd6870174ec99fc2d60 | [
"MIT"
] | 49 | 2018-05-05T02:53:10.000Z | 2022-03-30T12:08:09.000Z | 0501-0600/510-Inorder Successor in BST II/README.md | jolly-fellow/LeetCode | ab20b3ec137ed05fad1edda1c30db04ab355486f | [
"MIT"
] | 11 | 2017-12-15T22:31:44.000Z | 2020-10-02T12:42:49.000Z | 0501-0600/510-Inorder Successor in BST II/README.md | jolly-fellow/LeetCode | ab20b3ec137ed05fad1edda1c30db04ab355486f | [
"MIT"
] | 28 | 2017-12-05T10:56:51.000Z | 2022-01-26T18:18:27.000Z | # 510. Inorder Successor in BST II
Difficulty: Medium
https://leetcode.com/problems/inorder-successor-in-bst-ii/
Given a binary search tree and a node in it, find the in-order successor of that node in the BST.
The successor of a node p is the node with the smallest key greater than p.val.
You will have direct access to the node but not to the root of the tree. Each node will have a reference to its parent node.
**Examples 1:**
```
Input:
root = {"$id":"1","left":{"$id":"2","left":null,"parent":{"$ref":"1"},"right":null,"val":1},"parent":null,"right":{"$id":"3","left":null,"parent":{"$ref":"1"},"right":null,"val":3},"val":2}
p = 1
Output: 2
Explanation: 1's in-order successor node is 2. Note that both p and the return value is of Node type.
```
**Examples 2:**
```
Input:
root = {"$id":"1","left":{"$id":"2","left":{"$id":"3","left":{"$id":"4","left":null,"parent":{"$ref":"3"},"right":null,"val":1},"parent":{"$ref":"2"},"right":null,"val":2},"parent":{"$ref":"1"},"right":{"$id":"5","left":null,"parent":{"$ref":"2"},"right":null,"val":4},"val":3},"parent":null,"right":{"$id":"6","left":null,"parent":{"$ref":"1"},"right":null,"val":6},"val":5}
p = 6
Output: null
Explanation: There is no in-order successor of the current node, so the answer is null.
```
**Examples 3:**
```
Input:
root = {"$id":"1","left":{"$id":"2","left":{"$id":"3","left":{"$id":"4","left":null,"parent":{"$ref":"3"},"right":null,"val":2},"parent":{"$ref":"2"},"right":{"$id":"5","left":null,"parent":{"$ref":"3"},"right":null,"val":4},"val":3},"parent":{"$ref":"1"},"right":{"$id":"6","left":null,"parent":{"$ref":"2"},"right":{"$id":"7","left":{"$id":"8","left":null,"parent":{"$ref":"7"},"right":null,"val":9},"parent":{"$ref":"6"},"right":null,"val":13},"val":7},"val":6},"parent":null,"right":{"$id":"9","left":{"$id":"10","left":null,"parent":{"$ref":"9"},"right":null,"val":17},"parent":{"$ref":"1"},"right":{"$id":"11","left":null,"parent":{"$ref":"9"},"right":null,"val":20},"val":18},"val":15}
p = 15
Output: 17
```
**Examples 4:**
```
Input:
root = {"$id":"1","left":{"$id":"2","left":{"$id":"3","left":{"$id":"4","left":null,"parent":{"$ref":"3"},"right":null,"val":2},"parent":{"$ref":"2"},"right":{"$id":"5","left":null,"parent":{"$ref":"3"},"right":null,"val":4},"val":3},"parent":{"$ref":"1"},"right":{"$id":"6","left":null,"parent":{"$ref":"2"},"right":{"$id":"7","left":{"$id":"8","left":null,"parent":{"$ref":"7"},"right":null,"val":9},"parent":{"$ref":"6"},"right":null,"val":13},"val":7},"val":6},"parent":null,"right":{"$id":"9","left":{"$id":"10","left":null,"parent":{"$ref":"9"},"right":null,"val":17},"parent":{"$ref":"1"},"right":{"$id":"11","left":null,"parent":{"$ref":"9"},"right":null,"val":20},"val":18},"val":15}
p = 13
Output: 15
```
**Note:**
1. If the given node has no in-order successor in the tree, return null.
2. It's guaranteed that the values of the tree are unique.
3. Remember that we are using the Node type instead of TreeNode type so their string representation are different. | 57.314815 | 692 | 0.574798 | eng_Latn | 0.472433 |
4bd58b4305e4549e918a85aa466a990650b66980 | 4,446 | md | Markdown | data_processing/README.md | ffaltings/WikiCommentEdit | 28a31fe5bd25c6cc988cdd7408064990a46ff797 | [
"MIT"
] | 5 | 2019-10-31T05:50:15.000Z | 2022-02-28T07:46:25.000Z | data_processing/README.md | ffaltings/WikiCommentEdit | 28a31fe5bd25c6cc988cdd7408064990a46ff797 | [
"MIT"
] | null | null | null | data_processing/README.md | ffaltings/WikiCommentEdit | 28a31fe5bd25c6cc988cdd7408064990a46ff797 | [
"MIT"
] | 7 | 2019-11-07T21:09:23.000Z | 2021-09-13T12:50:10.000Z | Wikipedia Revision Data Extractor
======
This is a python implementation of the data extractor tool set for wikipedia revision data, as described in our EMNLP 2019 paper:
**Modeling the Relationship between User Comments and Edits in Document Revision**, Xuchao Zhang, Dheeraj Rajagopal, Michael Gamon, Sujay Kumar Jauhar and ChangTien Lu, 2019 Conference on Empirical Methods in Natural Language Processing (EMNLP), Hongkong, China, Nov 3-7, 2019.
We provide three tools to extract and preprocess the wikipedia revision history data from scratch:
- download entire enwiki revision dumps from wikipedia
- extract the revision data for comment modeling task from wiki dump files
- extract the summeration task dataset from wiki dump
Note: The collected wikipedia revision data can be used as the input for the proposed models in our EMNLP paper or used individually for other tasks.
## Requirements
- python 3.6
- [tqdm](https://github.com/noamraph/tqdm)
- [numpy v1.13+](http://www.numpy.org/)
- [scipy](https://www.scipy.org/)
- [scikit-learn](http://scikit-learn.org/stable/)
- [spacy v2.0.11](https://spacy.io/)
- and some basic packages.
## Usage
### Download Wiki dump files
First, choose a dump such as ```https://dumps.wikimedia.org/enwiki/20190801``` (the latest version of wiki dump when our code is released). You can check all the information related to dump files from this page such as the list of files generated in this dump. Then download a machine-readable dump status file ```dumpstatus.json``` from the Wikipedia dump page. Next copy the status file into the default data path, e.g., ```./data/```.
###### Important Note:
* Check the dump files must contain the complete page edit history: ```All pages with complete page edit history (.bz2)```. The edit history is sometimes skipped by some specific versions.
* Always choose the recent dumps since Wikipedia cleans the old dumps and make the old one deprecated.
Finally, run our wiki dump download script to download dump files as follows:
```
python wiki_dump_download.py --data_path="./data/raw/" --compress_type="bz2" --threads=3
```
You need to specify the data path and compress type (by default choose bz2 ). Since the download process will be extremely slow, you can use multiple threads to download the dump files. However, Wikipedia only allows three http connections to download simultaneously for each IP address. The maximum threads I recommend is three unless you can assign different IP address for each threads.
At the beginning of download process, all the files are listed with unique Ids as follows:
```
All files to download ...
1 enwiki-20190801-pages-meta-history1.xml-p1043p2036.bz2
2 enwiki-20190801-pages-meta-history1.xml-p10675p11499.bz2
3 enwiki-20190801-pages-meta-history1.xml-p10p1042.bz2
4 enwiki-20190801-pages-meta-history1.xml-p11500p12310.bz2
...
...
648 enwiki-20190801-pages-meta-history9.xml-p2326206p2336422.bz2
```
Usually, the entire download process takes one to two days to be done. You can download each file individually by specifying the ```--start``` and ```--end``` parameters. You can also use ```--verify``` parameter to verify the completeness of your dump files.
### Revision Data Preprocessing
For preprocessing the revision data, we provide both single-thread and multi-thread versions.
To preprocess a single dump file, we specify the file index of the dump file by the parameter ```--single_thread``` as follows:
```
python3 wikicmnt_extractor.py --single_thread=5
```
Here the number 5 in the example means the 5th dump file in the data folder of dump files.
To preprocess multiple dump files,
```
python3 wikicmnt_extractor.py --threads=10
```
You need to specify some common parameters:
```
--data_path="../data/raw/"
--output_path="../data/processed/"
--sample_ratio=0.1
--ctx_window=5
--min_page_tokens=50
--max_page_tokens=2000
--min_cmnt_length=8
```
Last, if you use the single thread mode to generate the processed files one by one, you need to merge the outputs of all the dump files together by running the following command:
```
python3 wikicmnt_extractor.py --merge_only
```
The output of the command is a processed file ```wikicmnt.json``` which includes all the processed data.
## Author
If you have any troubles or questions, please contact [Xuchao Zhang](xuczhang@gmail.com).
August, 2019
| 48.326087 | 438 | 0.752137 | eng_Latn | 0.983798 |
4bd5ea274cb59bdf7b2fb61a45af6ddc7723e70c | 1,246 | md | Markdown | docs/code-quality/c28253.md | yoichinak/cpp-docs.ja-jp | 50048c3d1101537497403efb4e7b550108f3a8f0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/code-quality/c28253.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/code-quality/c28253.md | yoichinak/cpp-docs.ja-jp | 50048c3d1101537497403efb4e7b550108f3a8f0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: '詳細情報: C28253'
title: C28253
ms.date: 11/04/2016
ms.topic: reference
f1_keywords:
- C28253
helpviewer_keywords:
- C28253
ms.assetid: df049e53-aab7-4914-b5f6-81ebe8ee989b
ms.openlocfilehash: 4544d0e6b1ed20b2185941beab1912e5f12099ec
ms.sourcegitcommit: d6af41e42699628c3e2e6063ec7b03931a49a098
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 12/11/2020
ms.locfileid: "97168515"
---
# <a name="c28253"></a>C28253
> 警告 C28253: 関数に対する一貫性のない注釈: このインスタンスでパラメーターに別の注釈があります
この警告は注釈のエラーを示し、関数が関係している場合を除き、関数宣言の注釈が定義上の注釈と一致する必要があるという要件を反映して **`typedef`** います。 この場合、関数は、 **`typedef`** 宣言と定義の両方に対して明確であると見なされます。
通常、注釈はマクロとして実装され、1つのマクロでは通常、いくつかの下位レベルの注釈が生成されることに注意してください。 この警告は、不一致の下位の注釈ごとに報告されます。したがって、1つの一致しない注釈マクロによって、一致しない低レベルの注釈が多数生成される可能性があります。 宣言と定義のソースコードを比較して、それらが同じであることを確認することをお勧めします。 (注釈の順序の自明な違いは報告されません)。
最初に見つかった宣言と現在の宣言の間の比較は常にです。 追加の宣言がある場合は、各宣言が2つのグループにチェックインされます。 現在、ペアではなく比較を行うことはできませんが、宣言/定義が3つ以上あることを識別することはできます。 エラーメッセージには、2つのインスタンスの間で (かなり低いレベルで) 異なる注釈の一覧が含まれています。
この警告メッセージには、コンパイラに送信された、基になるコードのテキストが表示されます。これは、(マクロが使用される場合のように) 実際に注釈をソースコードに挿入するために使用されるマクロではありません。 一般に、下位レベルの注釈を理解する必要はありませんが、エラーメッセージに報告された行番号の間に注釈が不整合として報告されていることを認識しておく必要があります。 ほとんどの場合、ソースコードを検査することで、不整合が存在する理由を明確にすることができます。
| 42.965517 | 231 | 0.857945 | jpn_Jpan | 0.78238 |
4bd60acd2df4072cbc09d04e0ae83495e83f052e | 920 | md | Markdown | developer-guides/mobile-apps/supported-servers-versions/README.md | maiki/docs | 353856fc95de3888c6269dd62ddaed1f54ffbe87 | [
"MIT"
] | null | null | null | developer-guides/mobile-apps/supported-servers-versions/README.md | maiki/docs | 353856fc95de3888c6269dd62ddaed1f54ffbe87 | [
"MIT"
] | null | null | null | developer-guides/mobile-apps/supported-servers-versions/README.md | maiki/docs | 353856fc95de3888c6269dd62ddaed1f54ffbe87 | [
"MIT"
] | null | null | null | # Supported Servers Versions
Our native mobile applications have a maximum of 3 major servers versions being supported on each release, all the past releases are not officially supported and may cause problems. The reason for that is that our APIs are evolving a lot on each release and sometimes is really hard to maintain the compatibility with older versions when they don’t have support to specific feature.
## iOS
| iOS Version | Supported releases |
|:-----------:|:------------------:|
| 2.5.0 | 0.62+ |
| 2.4.1 | 0.62+ |
| 2.4.0 | 0.62+ |
| 2.3.0 | 0.61+ |
## Android
| Android Version | Supported releases |
|:-----------:|:------------------:|
| 2.4.0 | 0.62+ |
| 2.3.2 | 0.62+ |
| 2.3.1 | 0.62+ |
| 2.3.0 | 0.62+ |
| 2.2.0 | 0.62+ |
| 40 | 382 | 0.501087 | eng_Latn | 0.998759 |
4bd64c3c271fa1b89fea9d750dc64bc769386e3b | 8,870 | md | Markdown | articles/automation/automation-certificates.md | Almulo/azure-docs.es-es | f1916cdaa2952cbe247723758a13b3ec3d608863 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/automation/automation-certificates.md | Almulo/azure-docs.es-es | f1916cdaa2952cbe247723758a13b3ec3d608863 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/automation/automation-certificates.md | Almulo/azure-docs.es-es | f1916cdaa2952cbe247723758a13b3ec3d608863 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Activos de certificados en Azure Automation
description: Los certificados se pueden almacenar de manera segura en Azure Automation, de manera que los runbooks o configuraciones de DSC pueden tener acceso a ellos para realizar la autenticación respecto de Azure y recursos de terceros. Este artículo explica los detalles de los certificados y cómo trabajar con ellos en la creación de textos y de gráficos.
services: automation
ms.service: automation
ms.component: shared-capabilities
author: georgewallace
ms.author: gwallace
ms.date: 03/15/2018
ms.topic: conceptual
manager: carmonm
ms.openlocfilehash: c13da6ff7c864ffa365dbad33d6eb0cf2e35fa42
ms.sourcegitcommit: 744747d828e1ab937b0d6df358127fcf6965f8c8
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 08/16/2018
ms.locfileid: "42146819"
---
# <a name="certificate-assets-in-azure-automation"></a>Activos de certificados en Azure Automation
Los certificados se pueden almacenar de manera segura en Azure Automation de manera que los runbooks o las configuraciones de DSC pueden tener acceso a ellos mediante el uso de la actividad **Get-AzureRmAutomationCertificate** para recursos de Azure Resource Manager. Esta funcionalidad le permite crear runbooks y configuraciones de DSC que usan certificados para autenticación o agregarlos a Azure o a recursos de terceros.
>[!NOTE]
>Los recursos protegidos en Azure Automation incluyen credenciales, certificados, conexiones y variables cifradas. Estos recursos se cifran y se almacenan en Azure Automation con una clave única que se genera para cada cuenta de Automation. Esta clave se almacena en Key Vault. Antes de almacenar un recurso seguro, la clave se carga desde Key Vault y luego se usa para cifrar el recurso.
## <a name="azurerm-powershell-cmdlets"></a>Cmdlets de AzureRM PowerShell
En AzureRM, los cmdlets de la tabla siguiente se usan para crear y administrar recursos de credenciales de automatización con Windows PowerShell. Se incluyen como parte del [módulo de AzureRM Automation](/powershell/azure/overview) que está disponible para su uso en las configuraciones de DSC y los runbooks denominados "Automation".
|Cmdlets|DESCRIPCIÓN|
|:---|:---|
|[Get-AzureRmAutomationCertificate](https://docs.microsoft.com/powershell/module/azurerm.automation/get-azurermautomationcertificate)|Recupera información sobre un certificado para utilizarlo en un runbook o en la configuración de DSC. Solo puede recuperar el certificado mismo desde la actividad Get-AutomationCertificate.|
|[New-AzureRmAutomationCertificate](https://docs.microsoft.com/powershell/module/azurerm.automation/new-azurermautomationcertificate)|Crea un certificado nuevo en Azure Automation.|
[Remove-AzureRmAutomationCertificate](https://docs.microsoft.com/powershell/module/azurerm.automation/remove-azurermautomationcertificate)|Quita un certificado de Azure Automation.|Crea un certificado nuevo en Azure Automation.
|[Set-AzureRmAutomationCertificate](https://docs.microsoft.com/powershell/module/azurerm.automation/set-azurermautomationcertificate)|Establece las propiedades de un certificado existente, incluyendo la carga del archivo de certificado y el establecimiento de la contraseña de un .pfx.|
|[Add-AzureCertificate](https://msdn.microsoft.com/library/azure/dn495214.aspx)|Carga un certificado de servicio para el servicio en la nube especificado.|
## <a name="activities"></a>Actividades
Las actividades de la tabla siguiente se usan para obtener acceso a los certificados de un runbook y las configuraciones de DSC.
| Actividades | DESCRIPCIÓN |
|:---|:---|
|Get-AutomationCertificate|Obtiene un certificado para usarlo en un runbook o una configuración de DSC. Devuelve un objeto [System.Security.Cryptography.X509Certificates.X509Certificate2](https://msdn.microsoft.com/library/system.security.cryptography.x509certificates.x509certificate2.aspx).|
> [!NOTE]
> Debe evitar el uso de variables en el parámetro –Name de **Get-AutomationCertificate** en los runbooks o en las configuraciones de DSC, ya que complica la detección de dependencias entre ellos y las variables de Automation durante el diseño.
## <a name="python2-functions"></a>Funciones de Python2
La función de la tabla siguiente se usa para obtener acceso a los certificados de un runbook de Python2.
| Función | DESCRIPCIÓN |
|:---|:---|
| automationassets.get_automation_certificate | Recupera información de un recurso de certificado. |
> [!NOTE]
> Debe importar el módulo **automationassets** al principio del runbook de Python para poder tener acceso a las funciones del recurso.
## <a name="creating-a-new-certificate"></a>Creación de un certificado nuevo
Cuando crea un certificado nuevo, debe cargar un archivo .cer o .pfx a Azure Automation. Si marca el certificado como exportable, podrá transferirlo fuera del almacén de certificados de Azure Automation. Si no es exportable, solo se puede usar para firmar dentro del runbook o la configuración de DSC. Azure Automation requiere que el certificado tenga el **proveedor de servicios criptográficos AES y RSA mejorado de Microsoft**.
### <a name="to-create-a-new-certificate-with-the-azure-portal"></a>Para crear un certificado nuevo con el portal de Azure
1. En la cuenta de Automation, haga clic en el icono **Activos** para abrir la hoja **Activos**.
1. Haga clic en el icono **Certificados** para abrir la hoja **Certificados**.
1. Haga clic en **Agregar un certificado** en la parte superior del cuadro.
1. Escriba un nombre para el certificado en el cuadro **Nombre** .
1. Para buscar un archivo .cer o .pfx, haga clic en **Seleccione un archivo** en **Cargar un archivo de certificado**. Si selecciona un archivo .pfx, especifique una contraseña y si va permitir o no que se exporte.
1. Haga clic en **Crear** para guardar el recurso de certificado nuevo.
### <a name="to-create-a-new-certificate-with-windows-powershell"></a>Para crear un certificado nuevo con Windows PowerShell
En el ejemplo siguiente se muestra cómo crear un nuevo certificado de Automation y marcarlo como exportable. Esta acción importa un archivo pfx ya existente.
```powershell-interactive
$certName = 'MyCertificate'
$certPath = '.\MyCert.pfx'
$certPwd = ConvertTo-SecureString -String 'P@$$w0rd' -AsPlainText -Force
$ResourceGroup = "ResourceGroup01"
New-AzureRmAutomationCertificate -AutomationAccountName "MyAutomationAccount" -Name $certName -Path $certPath –Password $certPwd -Exportable -ResourceGroupName $ResourceGroup
```
## <a name="using-a-certificate"></a>Uso de un certificado
Para usar un certificado, use la actividad **Get-AutomationCertificate**. No puede usar el cmdlet [Get-AzureRmAutomationCertificate](https://docs.microsoft.com/powershell/module/azurerm.automation/get-azurermautomationcertificate?view=azurermps-6.6.0), debido a que devuelve información sobre el activo de certificado, pero no el certificado mismo.
### <a name="textual-runbook-sample"></a>Ejemplo de runbook de texto
El código de ejemplo siguiente muestra cómo agregar un certificado a un servicio en la nube en un runbook. En este ejemplo, la contraseña se recupera a partir de una variable de automatización cifrada.
```powershell-interactive
$serviceName = 'MyCloudService'
$cert = Get-AutomationCertificate -Name 'MyCertificate'
$certPwd = Get-AzureRmAutomationVariable -ResourceGroupName "ResouceGroup01" `
–AutomationAccountName "MyAutomationAccount" –Name 'MyCertPassword'
Add-AzureCertificate -ServiceName $serviceName -CertToDeploy $cert
```
### <a name="graphical-runbook-sample"></a>Ejemplo de runbook gráfico
Para agregar **Get-AutomationCertificate** a un runbook gráfico, haga clic con el botón derecho en el certificado en el panel Biblioteca del editor gráfico y, después, seleccione **Agregar al lienzo**.
La imagen siguiente muestra un ejemplo de cómo usar un certificado en un runbook gráfico. Este es el mismo ejemplo anteriormente mostrado para agregar un certificado a un servicio en la nube desde un runbook textual.
### <a name="python2-sample"></a>Ejemplo de Python2
En el ejemplo siguiente se muestra cómo obtener acceso a los certificados en runbooks de Python2.
```python
# get a reference to the Azure Automation certificate
cert = automationassets.get_automation_certificate("AzureRunAsCertificate")
# returns the binary cert content
print cert
```
## <a name="next-steps"></a>Pasos siguientes
- Para obtener más información sobre cómo trabajar con vínculos para controlar el flujo lógico de las actividades que su runbook está diseñado para efectuar, consulte el tema sobre los [vínculos en la creación gráfica](automation-graphical-authoring-intro.md#links-and-workflow).
| 71.532258 | 430 | 0.801353 | spa_Latn | 0.958363 |
4bd7061053ad3daf5adfeca3e49ee166e8876b46 | 1,868 | md | Markdown | tutorials/katacoda/4-eventing-intro-broker/step1.md | brunoborges/docs | a4d3e3af4e3b6510f9812082e9f92e5853067eea | [
"Apache-2.0"
] | 3,383 | 2018-07-23T21:00:17.000Z | 2022-03-30T17:13:52.000Z | tutorials/katacoda/4-eventing-intro-broker/step1.md | brunoborges/docs | a4d3e3af4e3b6510f9812082e9f92e5853067eea | [
"Apache-2.0"
] | 4,617 | 2018-07-23T21:55:06.000Z | 2022-03-31T21:52:36.000Z | tutorials/katacoda/4-eventing-intro-broker/step1.md | brunoborges/docs | a4d3e3af4e3b6510f9812082e9f92e5853067eea | [
"Apache-2.0"
] | 1,240 | 2018-07-23T20:36:04.000Z | 2022-03-30T20:03:07.000Z | ## Installation
> The startup script running on the right will wait for kubernetes to start and knative serving to be installed. (Although Serving is not required for Eventing to work, we install it here for creating consumers succinctly).
> Once you see a prompt, you can click on the commands below at your own pace, and they will be copied and run for you in the terminal on the right.
1. Install Knative Eventing's core components
```
kubectl apply --filename https://github.com/knative/eventing/releases/download/${latest_version}/eventing-crds.yaml
kubectl apply --filename https://github.com/knative/eventing/releases/download/${latest_version}/eventing-core.yaml
```{{execute}}
1. Install an in-memory channel. (Knative also supports Apache Kafka Channel, Google Cloud Pub/Sub Channel and NATS Channel as options)
```
kubectl apply --filename https://github.com/knative/eventing/releases/download/${latest_version}/in-memory-channel.yaml
```{{execute}}
1. Install a Broker
```
kubectl apply --filename https://github.com/knative/eventing/releases/download/${latest_version}/mt-channel-broker.yaml
```{{execute}}
## Event Driven Architecture
In an event driven architecture, microservice and functions execute business logic when they are triggered by an event.
The source that generates the event is called the "Producer" of the event and the microservice/function is the "consumer".
The microservices/functions in an event-driven architecture are constantly reacting to and producing events themselves.
Producers should send their event data in a specific format, like [Cloud Events](https://cloudevents.io/), to make it easier
for consumers to handle the data. By default, Knative Eventing works with Cloud Events as a standard format for event data.
In the next section we will look at the broker-trigger model.
| 64.413793 | 223 | 0.773555 | eng_Latn | 0.989486 |
4bd71c88497b29b61930118b6c2a357aa52d889b | 42 | md | Markdown | README.md | ACEBASS/ConveTec | c2f69dc2481d5dc00b0a18b99a477cd10ca83c43 | [
"Apache-2.0"
] | null | null | null | README.md | ACEBASS/ConveTec | c2f69dc2481d5dc00b0a18b99a477cd10ca83c43 | [
"Apache-2.0"
] | null | null | null | README.md | ACEBASS/ConveTec | c2f69dc2481d5dc00b0a18b99a477cd10ca83c43 | [
"Apache-2.0"
] | null | null | null | # ConveTec
Conveniently Connecting People
| 14 | 30 | 0.857143 | eng_Latn | 0.990932 |
4bd81bcf89c7eb44ae3ba8bdb2683d44d5cdc466 | 26 | md | Markdown | 2021/07/15/941ValidMountainArray/941_valid_mountain_array.md | PseudoCowboy/lose-love-algorithm | 82aefb31956239d6b890ec81fac844beff7174c0 | [
"MIT"
] | 2 | 2021-04-14T18:37:54.000Z | 2021-04-15T09:13:01.000Z | 2021/07/15/941ValidMountainArray/941_valid_mountain_array.md | PseudoCowboy/lose-love-algorithm | 82aefb31956239d6b890ec81fac844beff7174c0 | [
"MIT"
] | 20 | 2021-04-07T07:56:15.000Z | 2021-05-05T10:37:16.000Z | 2021/07/15/941ValidMountainArray/941_valid_mountain_array.md | PseudoCowboy/streak-algorithm | 82aefb31956239d6b890ec81fac844beff7174c0 | [
"MIT"
] | null | null | null | 941. Valid Mountain Array
| 13 | 25 | 0.807692 | eng_Latn | 0.595063 |
4bd88e3e874a6e9ea88f4aac750668f8a115debe | 3,327 | md | Markdown | docs/deployment/clickonce-deployment-on-windows-vista.md | Kaunaj/visualstudio-docs | 47ed61d95acbb33fbdfa8ed43934cbdb451ad97c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/deployment/clickonce-deployment-on-windows-vista.md | Kaunaj/visualstudio-docs | 47ed61d95acbb33fbdfa8ed43934cbdb451ad97c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/deployment/clickonce-deployment-on-windows-vista.md | Kaunaj/visualstudio-docs | 47ed61d95acbb33fbdfa8ed43934cbdb451ad97c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "ClickOnce Deployment on Windows Vista | Microsoft Docs"
ms.custom: ""
ms.date: "11/04/2016"
ms.technology: vs-ide-deployment
ms.topic: "conceptual"
dev_langs:
- "VB"
- "CSharp"
- "C++"
helpviewer_keywords:
- "UAC manifest generation"
- "ClickOnce deployment, Windows"
- "manifest generation"
- "Windows, ClickOnce deployment"
ms.assetid: b21a0ebc-0ff6-4f49-8993-7d1ad3f8cac2
author: mikejo5000
ms.author: mikejo
manager: douge
ms.workload:
- "multiple"
---
# ClickOnce deployment on Windows Vista
Building applications in Visual Studio for User Account Control (UAC) on Windows Vista normally generates an embedded manifest, encoded as binary XML data in the application's executable file. ClickOnce and Registration-Free COM applications require an external manifest, so Visual Studio generates a file for these projects containing the UAC data instead of an embedded manifest. For ClickOnce and Registration-Free COM deployments, Visual Studio uses information from a file called *app.manifest* to generate external UAC manifest information. For all other cases, Visual Studio embeds the UAC data in the application's executable file.
Visual Studio provides the following options for manifest generation:
- Use an embedded manifest. Embed UAC data in the application's executable file and run as a normal user.
This is the default setting (unless you use ClickOnce). This setting supports the usual manner in which Visual Studio operates on Windows Vista, with the generation of both an internal and an external manifest using `AsInvoker`.
- Use an external manifest. Generate an external manifest by using *app.manifest*.
This generates only the external manifest by using the information in *app.manifest*. When you publish an application by using ClickOnce or Registration-Free COM, Visual Studio adds *app.manifest* to the project and then adds this option.
- Use no manifest. Create the application without a manifest.
This approach is also known as *virtualization*. Use this option for compatibility with existing applications from earlier versions of Visual Studio.
The new properties are available on the **Application** page of the Project Designer (for Visual C# projects only) and in the MSBuild project file format.
The method for configuring UAC manifest generation in the Visual Studio IDE differs depending on the project type (Visual C# or Visual Basic).
* For information about configuring Visual C# projects for manifest generation, see [Application Page, Project Designer (C#)](../ide/reference/application-page-project-designer-csharp.md).
* For information about configuring Visual Basic projects for manifest generation, see [Application Page, Project Designer (Visual Basic)](../ide/reference/application-page-project-designer-visual-basic.md).
## See also
[ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md)
[User permissions and Visual Studio](https://msdn.microsoft.com/library/d5c55084-1e7b-4b61-b478-137db01c0fc0)
[Application Page, Project Designer (C#)](../ide/reference/application-page-project-designer-csharp.md)
[Application Page, Project Designer (Visual Basic)](../ide/reference/application-page-project-designer-visual-basic.md) | 62.773585 | 642 | 0.774271 | eng_Latn | 0.953756 |
4bd95fe6d07760214a3056ba93bda847fff55ee7 | 687 | md | Markdown | apiary/toast.md | invinst/CPDBv2_backend | b4e96d620ff7a437500f525f7e911651e4a18ef9 | [
"Apache-2.0"
] | 25 | 2018-07-20T22:31:40.000Z | 2021-07-15T16:58:41.000Z | apiary/toast.md | invinst/CPDBv2_backend | b4e96d620ff7a437500f525f7e911651e4a18ef9 | [
"Apache-2.0"
] | 13 | 2018-06-18T23:08:47.000Z | 2022-02-10T07:38:25.000Z | apiary/toast.md | invinst/CPDBv2_backend | b4e96d620ff7a437500f525f7e911651e4a18ef9 | [
"Apache-2.0"
] | 6 | 2018-05-17T21:59:43.000Z | 2020-11-17T00:30:26.000Z | ## Desktop Toast [/v2/toast/]
### Get toast [GET]
+ Response 200 (application/json)
[
{
"name": "OFFICER",
"template": "**{rank} {full_name}** {age} {race} {gender}, with *{complaint_count} complaints*, *{sustained_count} sustained* {action_type}.",
},
{
"name": "CR",
"template": "**CR #{crid}** *categorized as {category}* happened in {incident_date} {action_type}.",
},
{
"name": "TRR",
"template": "**TRR #{id}** *categorized as {force_type}* happened in {incident_date} {action_type}.",
}
]
| 29.869565 | 158 | 0.461426 | eng_Latn | 0.467775 |
4bd9ff8dc832dff95425650f6c43bb5a2fd5752a | 1,492 | md | Markdown | README.md | peter-amerkhanian/councilmatic | 6e2ab050b8bf7a7a7aa34e7569bb319c1d7e69ea | [
"MIT"
] | null | null | null | README.md | peter-amerkhanian/councilmatic | 6e2ab050b8bf7a7a7aa34e7569bb319c1d7e69ea | [
"MIT"
] | null | null | null | README.md | peter-amerkhanian/councilmatic | 6e2ab050b8bf7a7a7aa34e7569bb319c1d7e69ea | [
"MIT"
] | null | null | null | # Councilmatic
# Setup
#
# IF pip (My prefered method):
1. Download Python
2. make sure you're in the project directory
and download the packages like so:
```
pip install -r requirements.txt
```
Disregard below
# IF Conda:
1. Install Anaconda
* https://www.anaconda.com/download
2. Create conda env
* conda env create -f environment.yml
3. Download geckodriver and add to path. Make sure to install Firefox if you don't have it as well.
* https://github.com/mozilla/geckodriver/releases
<br>
note: We used Katalon IDE brower plugin to easy generate some of python selenium statements the normal selenium IDE no longer supports Python code exports.
# start up conda env
```
source activate new_councilmatic
```
# update conda env
```
source activate new_councilmatic
conda env update -f=environment.yml
```
# install conda env into jupyter notebook
```
source activate new_councilmatic
python -m ipykernel install --user --name new_councilmatic --display-name "new councilmatic"
```
```
### By Year and Search Words Example (2018)
```
python run_calendar.py -d 2018 -s "parking"
```
### Save as CSV Example (deprecated)
```
python run_calendar.py -d 2018 -s "parking" > parking2018.csv
```
### To create the web page
```
Run ScraperUpdate_AWS.sh on Amazon Server
```
# To run in jupyter notebook
```
jupyter notebook calendar.ipynb
```
# Web location of production site
https://oaklandcouncil.net
| 20.438356 | 157 | 0.699062 | eng_Latn | 0.824747 |
4bda997ec4255376f632aabeeb156d42d3930972 | 4,918 | md | Markdown | README.md | robertpeteuil/docker-nginx-uwsgi-flask-mssql | ce043ed476ec9bb92c509c694ebcdbb8cd5aa0c1 | [
"Apache-2.0"
] | 9 | 2018-12-07T11:09:15.000Z | 2021-08-10T23:21:15.000Z | README.md | robertpeteuil/docker-nginx-uwsgi-flask-mssql | ce043ed476ec9bb92c509c694ebcdbb8cd5aa0c1 | [
"Apache-2.0"
] | 2 | 2019-01-10T01:14:02.000Z | 2019-11-13T02:53:45.000Z | README.md | robertpeteuil/docker-nginx-uwsgi-flask-mssql | ce043ed476ec9bb92c509c694ebcdbb8cd5aa0c1 | [
"Apache-2.0"
] | 3 | 2018-12-08T09:03:10.000Z | 2019-01-06T17:50:04.000Z | # Supported tags and `Dockerfile` links
- `2.7`, `py2.7`, `python2.7` [_(python2.7/Dockerfile)_](https://github.com/robpco/docker-nginx-uwsgi-flask-mssql/blob/master/python2.7/Dockerfile)
- `3.6`, `py3.6`, `python3.6` [_(python3.6/Dockerfile)_](https://github.com/robpco/docker-nginx-uwsgi-flask-mssql/blob/master/python3.6/Dockerfile)
- `3.7`, `py3.7`, `python3.7` [_(python3.6/Dockerfile)_](https://github.com/robpco/docker-nginx-uwsgi-flask-mssql/blob/master/python3.7/Dockerfile)
**You must explicitly use one of the tags above.** The `latest` tag is not assigned since each tag represents a different variant, not an incremental version.
## NGINX-UWSGI-FLASK-MSSQL
**Docker** image for Python Apps with **Nginx**, **uWSGI**, **Flask**, **MS SQL Driver** and **pyodbc** running in a single container to enable Python Flask Web Apps that require MS SQL connectivity and scaling for production with Nginx.
**GitHub Repo**: <https://github.com/robpco/docker-nginx-uwsgi-flask-mssql>
**Docker Hub Images**: <https://hub.docker.com/r/robpco/nginx-uwsgi-flask-mssql/>
## Overview
This Docker image allow the creation of Python Web Apps with MS SQL connectivity to run on Nginx via uWSGI. It simplifies the task of using Flask Web Apps with MS SQL and serves web requests via Nginx which is recommended for production deployment. These images use `pythonx.x-stretch` images as the base, so additional packages are installed from Debian stretch.
- This image is similar to my [nginx-uwsgi-flask](https://github.com/robpco/docker-nginx-uwsgi-flask) image but includes the official Microsoft SQL Driver, unixODBC Driver and pyodbc library.
- Installing the official Microsoft SQL Driver in a container can be tricky as it requires installation from a distribution specific Microsoft repository, and installation and special configuration of `locales`.
This repo auto-generates images to [Docker-Hub](https://hub.docker.com/r/robpco/nginx-uwsgi-flask-mssql/). It currently supports Python 2.7, 3.6 and 3.7.
## Usage
Basic usage information is provided below.
### Run a local application using the container
This is useful during development as you can edit the code on your local machine.
``` shell
docker run --name webapp -d -p 8080:80 -v ./app:/app robpco/nginx-uwsgi-flask-mssql:python2.7
```
- The name of your application should be `main.py`
- The folder containing it must be mapped to `/app` folder in the container.
- The default filename can be changed by creating a custom [`uwsgi.ini`](https://github.com/robpco/docker-nginx-uwsgi-flask-mssql/blob/master/python2.7/app/uwsgi.ini) file
- place it into the folder containing the application.
### Create an image for your **Flask Web-App** using this image as a base
In this example, the app directory contains the application, named `main.py`, and any python library requirements are stated inside the `requirements.txt` file included in the app directory.
``` Dockerfile
FROM robpco/nginx-uwsgi-flask-mssql:python2.7
COPY ./app /app
WORKDIR /app
RUN pip install -r requirements.txt
```
## Custom Environment Variables
This image can be customized by setting the following custom environment variables:
The variables that begin with `STATIC_` allow configuring Nginx to relay "static content" directly without going through uWSGI or Flask. This is advantageous for basic HTML pages, css and js files, that don't need their output adjusted by your Flask App.
- **STATIC_INDEX** - serve '/' directly from `/app/static/index.html`
- 0 = disabled (default)
- 1 = enabled - the file `index.html` located in the `/app/static` directory (in the container) will be forwarded to any requests to the root of your server (`/`) will
- **STATIC_URL** - external URL where requests for static files originate
- **STATIC_PATH** - container location of static files (absolute path)
- **UWSGI_INI** - the path and file of the configuration info
- default: `/app/uwsgi.ini`
- **NGINX_MAX_UPLOAD** - the maximum file upload size allowed by Nginx
- 0 = unlimited (image default)
- 1m = normal Nginx default
- **LISTEN_PORT** - custom port that Nginx should listen on
- 80 = Nginx default
## Setting Environment Variables
Environment variables can be set in multiple ways. The following examples, demonstrate setting the `LISTEN_PORT` environment variable via three different methods. These methods apply to the other Environment Variables as well.
### Setting in a `Dockerfile`
```dockerfile
# ... (snip) ...
ENV LISTEN_PORT 8080
# ... (snip) ...
```
### Setting during [`docker run`](https://docs.docker.com/engine/reference/commandline/run/#options) with the `-e` option
```shell
docker run -e LISTEN_PORT=8080 -p 8080:8080 myimage
```
### Setting in `docker-compose` file using the `environment:` keyword in a `docker-compose` file
```yml
version: '2.2'
services:
web:
image: myapp
environment:
LISTEN_PORT: 8080
```
| 47.747573 | 364 | 0.749288 | eng_Latn | 0.955898 |
4bdc1397ae977cb624d264ed561d243524a341bd | 47 | md | Markdown | README.md | NuwanJ/VoCe | 2ef3e06ff56fe9cd235a68bbfbc029da105a76bf | [
"Apache-2.0"
] | null | null | null | README.md | NuwanJ/VoCe | 2ef3e06ff56fe9cd235a68bbfbc029da105a76bf | [
"Apache-2.0"
] | null | null | null | README.md | NuwanJ/VoCe | 2ef3e06ff56fe9cd235a68bbfbc029da105a76bf | [
"Apache-2.0"
] | 1 | 2019-08-26T02:45:20.000Z | 2019-08-26T02:45:20.000Z | # Voce
Voice Conference Application using java
| 15.666667 | 39 | 0.829787 | ita_Latn | 0.873063 |
4bdcd5df766beef6ed3660de49e1ebf816f9b81f | 5,838 | md | Markdown | CHANGELOG.md | niniemann/sempr | 2f3b04c031d70b9675ad441f97728a8fb839abed | [
"BSD-3-Clause"
] | 8 | 2018-03-28T19:45:47.000Z | 2022-03-23T16:53:24.000Z | CHANGELOG.md | niniemann/sempr | 2f3b04c031d70b9675ad441f97728a8fb839abed | [
"BSD-3-Clause"
] | 58 | 2018-01-31T11:10:04.000Z | 2021-08-13T11:48:31.000Z | CHANGELOG.md | niniemann/sempr | 2f3b04c031d70b9675ad441f97728a8fb839abed | [
"BSD-3-Clause"
] | 1 | 2018-07-04T12:30:06.000Z | 2018-07-04T12:30:06.000Z | # Changelog
## [0.15.0] - 2021-08-11
- added WMEToJSON-Converters to support new json-explanation feature in rete
## [0.14.0] - 2021-06-28
- create temporary (i.e., non-persistent) entities with Entity::createTemporary
- added `EC<Component>` to UtilBuildin
## [0.13.0] - 2021-05-31
- changed plugin structure to separate plugin instances for multiple sempr cores
- added `componentQuery` to RDFPlugin: An extended SPARQL query that also
fetches c++ objects associated with ids
- added builtins to deal with dates
## [0.12.0] - 2021-03-15
- added createEntity builtin
- added idIsURI flag to entity, to allow skipping the automatic "sempr:" prefix
- added geometry builtins:
- geo:buffer
- geo:difference
- geo:fromWKT
- geo:toWKT
- geo:WGSFromUTM
## [0.11.0] - 2021-02-19
- added geo:intersects builtin
- added createEntity builtin
- load plugins from SEMPR\_PLUGINS\_PATH env variable
- changed ECWME to include tags. This allows inferring a tag in rules
## [0.10.0] - 2020-11-19
- Added several geometry builtins:
- geo:area
- geo:intersection
- geo:union
- geo:unionAll (union on GROUP BY results)
## [0.9.3] - 2020-10-14
- Added (template) method to access loaded plugins
## [0.9.2] - 2020-10-09
- Fix: LoadTriplesFromFile builtin support for constants
- (Mainly releasing this to trigger a build with rete 0.7.0)
## [0.9.1] - 2020-09-04
- GeoDistanceNode now returns float values, for compatibility with rete
comparison builtins (le, ge, lt, gt, eq, neq).
At some point I should probably change it all to doubles...
- Fixed: URI representation of entities is now properly returned in an
interpretation of rete::TriplePart (previously: std::string), whereas the
std::string interpretation now returns the pure id.
- For compatibility with newer geos versions, the geometry component now
contains a unique\_ptr to geos::geom::Geometry.
## [0.9.0] - 2020-09-01
- Added: Plugins that register node builders and default rules
- Fixed/Updated: Using rete v0.6.0 with a new accessor system and fixed
string/triple handling.
- Requires C++14 now.
## [0.8.2] - 2020-07-31
- Fix: Removed leftover -std=c++17 flag from and added missing flag to link
boost\_system to the pkg config file
- Updated/fixed: sempr.hpp had some old includes and missed some new ones
- Updated README
## [0.8.1] - 2020-05-27
- Changed install path of the library, in order to not having to mess with
LD\_LIBRARY\_PATH. (It's <install-dir\>/lib/libsempr\_core.so now, instead of
<install-dir\>/lib/sempr/libsempr\_core.so)
## [0.8.0] - 2020-05-12
- Added FindCereal.cmake
- Fix/Adjustment: Let the core explicitely handle rules. This is a change done
together with rete v0.3.0 since which the RuleParser no longer adds the
production nodes to the rete::Network, but instead returns Rule-objects which
when deconstructed also remove the respective nodes from the network.
This fix keeps those alive.
- Added ConstructRules-Node. This allows us to handle rules as data, by only
hard-coding a single rule (or a very limited set of rules) that has a
ConstructRules-effect and thus creates/removes rules as a result of the
inference process.
- Added a simple TextComponent (in order to store rules as data).
- Added toString method for ECNode. (Requires rete v0.4.0)
## [0.7.0] - 2020-04-24
- Fix: Wrong relative include path in a header file
- Fix: Added a specialization of rete::util::to\_string for GeosGeometryInterface
- EntityAccessor now inherits StringAccessor, in which case it returns the
entity id in a URI format, i.e.: `Entity_1` -> `<sempr:Entity_1>`. This allows
an easy usage in rules without an extra builtin to extract the id.
- Added geo:distance(?dist ?geo1 ?geo2)
- Added geo:UTMFromWGS(?geoOut ?geoIn ?utmZone) which transforms a geometry that
is specified in WGS84 lon/lat coordinates into a UTM coordinate system, in
which e.g. distance calculations with geo:distance make sense.
## [0.6.0] - 2020-04-08
- Added method to TriplePropertyMapEntry that returns the current type
- Added loadFromJSON and saveToJSON methods to component. These are implemented
in a `SEMPR_COMPONENT` macro that needs to be added to all components
## [0.5.1] - 2020-03-27
- Fix: Multiple wrong include paths
- Fix: Some ComponentName defs were missing
- Fix: ECAccessor now registers its type, making it usable in rules/builders
## [0.5.0] - 2020-03-24
- Removed dependency to ODB
- Added serialization with cereal
- Added SeparateFileStorage module
## [0.4.0] - 2020-03-23
- Added components and nodes to use with RDF triples:
TripleDocument, TriplePropertyMap
- Added FileWatcher and a corresponding file:exists builtin to trigger rules
when a local file changes
- Changed gitlab-ci to use a qt5 build of soprano
## [0.3.1] - 2020-03-05
There has been a complete rework of the internal structure.
Entities are only containers for components, which in turn
represent (independent) data types. The core of sempr is a
rule based rete reasoner, and entity-component pairs are made
accessible to it. What has former been thought of as a
processing module is now supposed to be implemented in a rule,
as a combination of complex preconditions (previously implemented
by listening to entity-events) and the rules effect (previously
the body of the processEvent method).
## [0.2.0] - 2018-08-09
### Added
- SemanticEntity for typesafe RDF-exposure of member variables
- RDFVector (previously RDFEntity)
### Changed
- GEOS as replacement for GDAL
- Global coordinate systems now based on geographiclib
- RDFEntity is now an interface for iterable RDF containers
- registerChildEntity now public
### Fixed
- Problems with accessing/comparing RDFPropertyMap-entries
- libsqlite3-dev dependency in CMakeLists
## [0.1.0] - 2018-07-06 - Initial Release with GDAL support.
| 34.75 | 81 | 0.749572 | eng_Latn | 0.990641 |
4bdd68781ce0607d190fb6a4559d089566c58ced | 3,392 | md | Markdown | AlchemyInsights/how-to-update-mca-billing-acc.md | isabella232/OfficeDocs-AlchemyInsights-pr.sl-SI | 11a4d6bfb0580342f538adc12818d1a86ddcdac3 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:07:51.000Z | 2020-05-19T19:07:51.000Z | AlchemyInsights/how-to-update-mca-billing-acc.md | MicrosoftDocs/OfficeDocs-AlchemyInsights-pr.sl-SI | feeebbc38a3aeca0b2a03f49e3cab735f0ea4069 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-06-02T23:33:13.000Z | 2022-02-09T06:51:06.000Z | AlchemyInsights/how-to-update-mca-billing-acc.md | isabella232/OfficeDocs-AlchemyInsights-pr.sl-SI | 11a4d6bfb0580342f538adc12818d1a86ddcdac3 | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-10-11T19:12:12.000Z | 2021-10-09T10:38:29.000Z | ---
title: Posodobitev naslova prodajo in računa, povezanega s storitvijo MCA – priporočeni koraki
ms.author: v-aiyengar
author: AshaIyengar21
manager: dansimp
ms.date: 12/11/2020
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.collection: Adm_O365
ms.custom:
- "9004166"
- "7325"
ms.openlocfilehash: 5c0f4e7e92081a60be1f6930100ed08ce91ad545
ms.sourcegitcommit: ab75f66355116e995b3cb5505465b31989339e28
ms.translationtype: MT
ms.contentlocale: sl-SI
ms.lasthandoff: 08/13/2021
ms.locfileid: "58320046"
---
# <a name="update-sold-to-and-bill-to-address-associated-to-your-mca---recommended-steps"></a>Posodobitev naslova prodajo in računa, povezanega s storitvijo MCA – priporočeni koraki
Posodobite lahko naslov kupca in naslov za obračun, ki je povezan z Microsoftovo pogodbo za stranke (MCA).
**Opomba:** Podatke o uporabniškem profilu lahko spremeni le Azure Active Directory uporabniškega profila. Če vam ni dodeljena vloga skrbnika uporabnika, se obrnite na skrbnika uporabnika. Če želite več informacij o spreminjanju uporabniškega profila, glejte Dodajanje ali posodabljanje informacij o profilu [uporabnika Azure Active Directory.](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-users-profile-azure-portal)
**Naslov kupca** – naslov kupca je naslov in podatki za stik organizacije ali posameznika, ki je odgovoren za račun za obračunavanje. Prikazana je na vseh računih, ustvarjenih za račun za obračunavanje.
**Naslov plačnika** – naslov plačnika računa je naslov in podatki za stik organizacije ali posameznika, ki je odgovoren za račune, ustvarjene za račun za obračunavanje. Za račun za obračunavanje za MCA je naslov plačnika računa za vsak profil za obračunavanje, ki je prikazan na računu, ustvarjenem za profil za obračunavanje.
**Če želite posodobiti naslov plačnika računa MCA:**
1. Vpišite se v portal Azure z e-poštnim naslovom, ki ima vlogo lastnika ali sodelavca v računu za obračunavanje za MCA.
1. Poiščite **Obračunavanje upravljanja** + **stroškov.**
1. Kliknite **Posodobitev** > **lastnosti, ki je bila prodana.**
1. Vnesite nov naslov in kliknite **Shrani.**
Nekateri računi zahtevajo dodatno preverjanje, preden je mogoče posodobiti naslov prodajo. Če vaš račun zahteva ročno odobritev, boste pozvani, da se obrnete na podporo za Azure.
**Če želite posodobiti naslov računa za obračunavanje MCA:**
1. Vpišite se v portal Azure z e-poštnim naslovom, ki ima vlogo lastnika ali sodelavca v računu za obračunavanje ali profilu za obračunavanje za mca.
1. Poiščite **Obračunavanje upravljanja** + **stroškov.**
1. Kliknite **Profili za** obračunavanje in izberite izberite profil za obračunavanje, da posodobite naslov za obračunavanje.
1. Kliknite **Posodobi naslov** > **lastnosti.**
1. Vnesite nov naslov in kliknite **Shrani**.
**Priporočeni dokumenti**
[Spreminjanje podatkov za stik za račun za obračunavanje azure](https://docs.microsoft.com/azure/cost-management-billing/manage/change-azure-account-profile)
[Posodobitev nastavitev računa za obračunavanje](https://docs.microsoft.com/microsoft-store/update-microsoft-store-for-business-account-settings)
[Razumevanje skrbniških vlog v Microsoftovi pogodbi za stranke v storitvi Azure](https://docs.microsoft.com/azure/cost-management-billing/manage/understand-mca-roles) | 62.814815 | 452 | 0.798939 | slv_Latn | 0.992419 |
4bddabaf72b4edcc3341f438637bdf04213d23f0 | 179 | md | Markdown | README.md | Cepheid-UK/channel-diorama | 1576dadd06dc6811f29b0db0dd55892f579d938e | [
"MIT"
] | null | null | null | README.md | Cepheid-UK/channel-diorama | 1576dadd06dc6811f29b0db0dd55892f579d938e | [
"MIT"
] | null | null | null | README.md | Cepheid-UK/channel-diorama | 1576dadd06dc6811f29b0db0dd55892f579d938e | [
"MIT"
] | null | null | null | # English Channel Diorama
Creating a 3D printable diorama of the English Channel
Data for this project is from the General Bathymetric Chart of the Oceans https://www.gebco.net/
| 35.8 | 96 | 0.804469 | eng_Latn | 0.954732 |
4bddaf430b0f69c67cec90a5e5f4038c94dd997b | 2,383 | md | Markdown | src/code/language/python/function/recursive.md | List-Jiang/list-jiang.github.com | c3febf3e7f08800424dc8e414fd2232e403f89f4 | [
"MIT"
] | 9 | 2020-11-28T16:11:22.000Z | 2022-03-26T05:04:13.000Z | src/code/language/python/function/recursive.md | List-Jiang/list-jiang.github.com | c3febf3e7f08800424dc8e414fd2232e403f89f4 | [
"MIT"
] | 117 | 2020-11-24T09:08:51.000Z | 2022-03-25T18:15:49.000Z | src/code/language/python/function/recursive.md | List-Jiang/list-jiang.github.com | c3febf3e7f08800424dc8e414fd2232e403f89f4 | [
"MIT"
] | 41 | 2020-11-24T08:55:43.000Z | 2022-03-26T11:05:46.000Z | ---
title: 递归函数
icon: refresh
author: 廖雪峰
time: 2020-05-27
category: Python
---
在函数内部，可以调用其他函数。如果一个函数在内部调用自身本身，这个函数就是递归函数。
<!-- more -->
举个例子，我们来计算阶乘 $n! = 1 \times 2 \times 3 \times \cdots \times n$ ，用函数 `fact(n)` 表示，可以看出:
$$
fact(n)= n! =1 \times 2 \times 3 \times \cdots \times (n -1 ) \times n \\
= (n - 1)! \times n = fact(n - 1) \times n
$$
所以，`fact(n)` 可以表示为 $n \times fact(n-1)$，只有 n=1 时需要特殊处理。
于是，`fact(n)` 用递归的方式写出来就是:
```py
def fact(n):
if n==1:
return 1
return n * fact(n - 1)
```
上面就是一个递归函数。可以试试:
```py
>>> fact(1)
1
>>> fact(5)
120
>>> fact(100)
93326215443944152681699238856266700490715968264381621468592963895217599993229915608941463976156518286253697920827223758251185210916864000000000000000000000000
```
如果我们计算 `fact(5)`，可以根据函数定义看到计算过程如下:
```text
===> fact(5)
===> 5 *fact(4)
===> 5* (4 *fact(3))
===> 5* (4 *(3* fact(2)))
===> 5 *(4* (3 *(2* fact(1))))
===> 5 *(4* (3 *(2* 1)))
===> 5 *(4* (3 *2))
===> 5* (4 *6)
===> 5* 24
===> 120
```
递归函数的优点是定义简单，逻辑清晰。理论上，所有的递归函数都可以写成循环的方式，但循环的逻辑不如递归清晰。
使用递归函数需要注意防止栈溢出。在计算机中，函数调用是通过栈(stack)这种数据结构实现的，每当进入一个函数调用，栈就会加一层栈帧，每当函数返回，栈就会减一层栈帧。由于栈的大小不是无限的，所以，递归调用的次数过多，会导致栈溢出。可以试试 `fact(1000)`:
```sh
>>> fact(1000)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<stdin>", line 4, in fact
...
File "<stdin>", line 4, in fact
RuntimeError: maximum recursion depth exceeded in comparison
```
解决递归调用栈溢出的方法是通过尾递归优化，事实上尾递归和循环的效果是一样的，所以，把循环看成是一种特殊的尾递归函数也是可以的。
尾递归是指，在函数返回的时候，调用自身本身，并且，return 语句不能包含表达式。这样，编译器或者解释器就可以把尾递归做优化，使递归本身无论调用多少次，都只占用一个栈帧，不会出现栈溢出的情况。
上面的 `fact(n)` 函数由于 `return n * fact(n - 1)` 引入了乘法表达式，所以就不是尾递归了。要改成尾递归方式，需要多一点代码，主要是要把每一步的乘积传入到递归函数中:
```py
def fact(n):
return fact_iter(n, 1)
def fact_iter(num, product):
if num == 1:
return product
return fact_iter(num - 1, num *product)
```
可以看到，`return fact_iter(num - 1, num* product)` 仅返回递归函数本身，`num - 1` 和 `num * product` 在函数调用前就会被计算，不影响函数调用。
`fact(5)` 对应的 `fact_iter(5, 1)` 的调用如下:
```text
===> fact_iter(5, 1)
===> fact_iter(4, 5)
===> fact_iter(3, 20)
===> fact_iter(2, 60)
===> fact_iter(1, 120)
===> 120
```
尾递归调用时，如果做了优化，栈不会增长，因此，无论多少次调用也不会导致栈溢出。
遗憾的是，大多数编程语言没有针对尾递归做优化，Python 解释器也没有做优化，所以，即使把上面的 `fact(n)` 函数改成尾递归方式，也会导致栈溢出。
## 小结
使用递归函数的优点是逻辑简单清晰，缺点是过深的调用会导致栈溢出。
针对尾递归优化的语言可以通过尾递归防止栈溢出。尾递归事实上和循环是等价的，没有循环语句的编程语言只能通过尾递归实现循环。
Python 标准的解释器没有针对尾递归做优化，任何递归函数都存在栈溢出的问题。
| 21.468468 | 158 | 0.672262 | yue_Hant | 0.403732 |
4bddbe70cd0bf2271ad715c6525bf776e8f5736e | 1,205 | md | Markdown | concepts/products/coding-systems.md | nnikolov-erp-bg/tech | dcbd94d4c24ecfb838b9ed5436f654426c463b2e | [
"CC-BY-4.0"
] | null | null | null | concepts/products/coding-systems.md | nnikolov-erp-bg/tech | dcbd94d4c24ecfb838b9ed5436f654426c463b2e | [
"CC-BY-4.0"
] | null | null | null | concepts/products/coding-systems.md | nnikolov-erp-bg/tech | dcbd94d4c24ecfb838b9ed5436f654426c463b2e | [
"CC-BY-4.0"
] | 3 | 2020-09-24T12:24:40.000Z | 2021-03-23T12:41:55.000Z | # Coding systems
*Coding Systems* group together multiple [product codes](product-codes.md) according to different criteria. All product codes are grouped in coding systems. Product codes are codes other than the part numbers that bring meaning to the company such as supplier codes, customer codes, barcodes and more.
A *default measurement unit* could also be specified in coding systems. If a product code relating to a coding system with a default measurement unit is selected, then this unit must load in the document instead of the product's default unit.
For example, if in the products definition "Measurement Unit = Pcs" is set, and for this product there is also a product code that relates to a coding system with a "Default Measurement Unit = Package", then we expect the following behavior:
When a product in the sales order is selected through product code via barcode, then:
- Product’s part number loads in the Product field in the particular sales order line;
- "Quantity Unit = Package", which corresponds to the default measurement unit in the coding system’s definition;
- "Unit Price" must be recalculated according to the [product dimensions](product-dimensions.md).
| 70.882353 | 302 | 0.788382 | eng_Latn | 0.999684 |
4bde032af0d3b8621f695beed4ca6bfedeb6051d | 273 | md | Markdown | translations/ru/docs/Mods/CompatSkills/Supports/Baubles.md | kindlich/CraftTweaker-Documentation | 3579ab48d05731d9b9175fe65fb6d3c856f60a9b | [
"MIT"
] | 1 | 2017-10-21T12:33:53.000Z | 2017-10-21T12:33:53.000Z | translations/ru/docs/Mods/CompatSkills/Supports/Baubles.md | kindlich/CraftTweaker-Documentation | 3579ab48d05731d9b9175fe65fb6d3c856f60a9b | [
"MIT"
] | 1 | 2017-07-16T09:55:12.000Z | 2017-07-16T11:37:55.000Z | translations/ru/docs/Mods/CompatSkills/Supports/Baubles.md | kindlich/CraftTweaker-Documentation | 3579ab48d05731d9b9175fe65fb6d3c856f60a9b | [
"MIT"
] | 2 | 2017-07-16T00:14:53.000Z | 2017-12-31T14:04:05.000Z | # Бубли
## Поддержка бубликов
Baubles-Support является частью стандартной блокировки ItemStack-Requirement locks. Это означает, что любой предмет, который у вас нет необходимых требований в инвентаре, будет выброшен автоматически, а сообщение об ошибке будет распечатано! | 54.6 | 241 | 0.831502 | rus_Cyrl | 0.990305 |
4bde190fd18ccb26f0515bc423ebf20e1efda3d6 | 64 | md | Markdown | README.md | miradam/openstack-ansible-os_murano | 6b17de665f66f23b5e0170f7b42cde56678a6d13 | [
"Apache-2.0"
] | null | null | null | README.md | miradam/openstack-ansible-os_murano | 6b17de665f66f23b5e0170f7b42cde56678a6d13 | [
"Apache-2.0"
] | null | null | null | README.md | miradam/openstack-ansible-os_murano | 6b17de665f66f23b5e0170f7b42cde56678a6d13 | [
"Apache-2.0"
] | null | null | null | # openstack-ansible-os_murano
Murano role for OpenStack Ansible
| 21.333333 | 33 | 0.84375 | eng_Latn | 0.363321 |
4bde8674d9c3a250c6d216d558aee423d303d45b | 356 | md | Markdown | README.md | segmentio/analytics-java-high-throughput-example | ce3dd2533e272e588d74d96b7afaf8ee2c8149f6 | [
"MIT"
] | null | null | null | README.md | segmentio/analytics-java-high-throughput-example | ce3dd2533e272e588d74d96b7afaf8ee2c8149f6 | [
"MIT"
] | null | null | null | README.md | segmentio/analytics-java-high-throughput-example | ce3dd2533e272e588d74d96b7afaf8ee2c8149f6 | [
"MIT"
] | 1 | 2019-12-30T19:30:30.000Z | 2019-12-30T19:30:30.000Z | # analytics-java example
> sample app written in Java which sends data to Segment at high throughput (10k reqs/second)
## Pre-req
```
0. *nix
1. Maven
2. JDK 8+
3. Docker
```
## Build and run inside container
```
make
```
__For reference only and not to be used in production env. Code quality == PM Code. Please add your own write key under `main()`__ | 19.777778 | 130 | 0.705056 | eng_Latn | 0.997012 |
4bde8b0be378c6aa530241b89a2b9c1090d190da | 411 | md | Markdown | doc_source/doc-history.md | ckesser/cloudformation-cli | f01309eae0962419700198520243bbe8604e52b7 | [
"Apache-2.0"
] | null | null | null | doc_source/doc-history.md | ckesser/cloudformation-cli | f01309eae0962419700198520243bbe8604e52b7 | [
"Apache-2.0"
] | null | null | null | doc_source/doc-history.md | ckesser/cloudformation-cli | f01309eae0962419700198520243bbe8604e52b7 | [
"Apache-2.0"
] | null | null | null | # Document History for User Guide<a name="doc-history"></a>
The following table describes the documentation for this release of the CloudFormation Command Line Interface \(CLI\)\.
+ **Latest documentation update:** November 14, 2019
| Change | Description | Date |
| --- |--- |--- |
| [General Availability](#doc-history) | Initial publication of the CloudFormation CLI documentation\. | November 14, 2019 | | 51.375 | 125 | 0.722628 | eng_Latn | 0.672658 |
4bde9de7ab88febb8e0d5e9ad72c232a07a5a47b | 1,151 | md | Markdown | README.md | harisethuram/CS-Lessons | 48ada6f13bd7f4d3ca09b893c8de826243288cb7 | [
"MIT"
] | null | null | null | README.md | harisethuram/CS-Lessons | 48ada6f13bd7f4d3ca09b893c8de826243288cb7 | [
"MIT"
] | null | null | null | README.md | harisethuram/CS-Lessons | 48ada6f13bd7f4d3ca09b893c8de826243288cb7 | [
"MIT"
] | null | null | null | # Lessons on getting started with Computer Science
Lessons are taught in C and are meant for beginners
An eight week course with assignments, and will cover many important concepts up till recursion.
Week 1 ([slides](https://github.com/harisethuram/CS-Lessons/blob/main/Week%201.pdf))
- Scratch
Week 2 ([slides](https://github.com/harisethuram/CS-Lessons/blob/main/Week%202.pdf))
- Binary system
- Intro to datatypes
Week 3 ([slides](https://github.com/harisethuram/CS-Lessons/blob/main/Week%203.pdf))
- More datatypes
- Intro to C
Week 4 ([slides](https://github.com/harisethuram/CS-Lessons/blob/main/Week%204.pdf))
- Operators
- If/Else conditions
Week 5 ([slides](https://github.com/harisethuram/CS-Lessons/blob/main/Week%205.pdf))
- Loops (While)
- Arrays
- Brief intro to Algorithms
Week 6 ([slides](https://github.com/harisethuram/CS-Lessons/blob/main/Week%206.pdf))
- Recap of everything so far
Week 7 ([slides](https://github.com/harisethuram/CS-Lessons/blob/main/Week%207.pdf))
- The stack
- Functions
Week 8 ([slides](https://github.com/harisethuram/CS-Lessons/blob/main/Week%208.pdf))
- Recursion
- Sigma, Largest number in array
| 31.972222 | 97 | 0.754127 | yue_Hant | 0.298263 |
4bdebd7509fbf27860829e795764b71ded1e60af | 1,090 | md | Markdown | _posts/development-java/2021-02-10-보다_덜_구체적인_것을_타입으로_참조해서_선언해라.md | jaeseongDev/jaeseongdev.github.io | 46a46b94106485a88660465a9338e4f556a41270 | [
"MIT"
] | 2 | 2021-07-02T01:45:55.000Z | 2021-07-15T15:50:29.000Z | _posts/development-java/2021-02-10-보다_덜_구체적인_것을_타입으로_참조해서_선언해라.md | jaeseongDev/jaeseongdev.github.io | 46a46b94106485a88660465a9338e4f556a41270 | [
"MIT"
] | 14 | 2021-01-04T12:49:34.000Z | 2021-07-02T01:35:59.000Z | _posts/development-java/2021-02-10-보다_덜_구체적인_것을_타입으로_참조해서_선언해라.md | jaeseongDev/jaeseongdev.github.io | 46a46b94106485a88660465a9338e4f556a41270 | [
"MIT"
] | 1 | 2021-07-02T01:38:00.000Z | 2021-07-02T01:38:00.000Z | ---
layout: post
title: "보다 덜 구체적인 것(추상적인 것)을 타입으로 참조해서 선언해라."
subtitle: "보다 덜 구체적인 것(추상적인 것)을 타입으로 참조해서 선언해라."
categories: development
tags: java
comments: false
---
### 객체는 클래스(구체적인 것)가 아닌 인터페이스(덜 구체적인 것)로 참조해라.
```java
Set<Son> sonSet = new LinkedHashSet<>(); // Good!
LinkedHashSet<Son> sonSet = new LinkedHashSet<>(); // Bad!
```
인터페이스를 타입으로 사용하는 습관을 길러두면 프로그램이 훨씬 유연해질 것이다. 나중에 구현 클래스(`new LinkedHashsSet`)를 교체하고자 한다면 밑의 코드처럼 그저 새 클래스의 생성자(`new HashSet`) 혹은 다른 정적 팩터리를 호출해주기만 하면 된다.
```java
Set<Son> sonSet = new HashSet<>();
```
단, 주의할 점이 하나 있다. 원래의 클래스가 인터페이스의 일반 규약 이외의 특별한 기능을 제공하며, 주변 코드가 이 기능에 기대어 동작한다면 새로운 클래스도 반드시 같은 기능을 제공해야 한다. 예를 들어, LinkedHashSet이 따르는 순서 정책을 정하고 동작하는 상황에서 이를 HashSet으로 바꾸면 문제가 될 수 있다. HashSet은 반복자의 순회 순서를 보장하지 않기 때문이다.
### 인터페이스가 없다면 덜 구체적인 클래스로 참조해라.
인터페이스가 없는 클래스도 있을 것이다. 그 때에는 클래스의 계층 구조 중 필요한 기능을 만족하는 가장 덜 구체적인(상위의) 클래스를 타입으로 사용해라.
# References
- [Effective Java(이펙티브 자바) - 조슈아 블로크, 인사이트](http://www.kyobobook.co.kr/product/detailViewKor.laf?ejkGb=KOR&mallGb=KOR&barcode=9788966262281&orderClick=LEa&Kc=) → [아이템 63. 문자열 연결은 느리니 주의하라.] | 35.16129 | 220 | 0.700917 | kor_Hang | 1.00001 |
4bdf85bca7e56e29d83381dc4dfd7476ab06f871 | 332 | md | Markdown | haskell/README.md | m13m/.dotfiles | 7ed95f4b35e92c744d2c16ae8dde640359036b70 | [
"MIT"
] | null | null | null | haskell/README.md | m13m/.dotfiles | 7ed95f4b35e92c744d2c16ae8dde640359036b70 | [
"MIT"
] | null | null | null | haskell/README.md | m13m/.dotfiles | 7ed95f4b35e92c744d2c16ae8dde640359036b70 | [
"MIT"
] | null | null | null | ## Install ghcup
```bash
curl https://get-ghcup.haskell.org -sSf | sh
```
## Setup the Haskell Hie for SublimeText3
```bash
{
"clients": {
"haskell-ide-engine": {
"command": ["hie"],
"scopes": ["source.haskell"],
"syntaxes": ["Packages/Haskell/Haskell.sublime-syntax"],
"languageId": "haskell",
},
},
}
```
| 15.090909 | 60 | 0.593373 | eng_Latn | 0.149472 |
4be04d2d758240458bf7f07250063b3ee8fe2a74 | 6,660 | md | Markdown | packages/build/tests/error/stack/snapshots/tests.js.md | jlengstorf/build | 19cc97b4dc1571a0a0ac187640251516f9876205 | [
"MIT"
] | null | null | null | packages/build/tests/error/stack/snapshots/tests.js.md | jlengstorf/build | 19cc97b4dc1571a0a0ac187640251516f9876205 | [
"MIT"
] | null | null | null | packages/build/tests/error/stack/snapshots/tests.js.md | jlengstorf/build | 19cc97b4dc1571a0a0ac187640251516f9876205 | [
"MIT"
] | null | null | null | # Snapshot report for `packages/build/tests/error/stack/tests.js`
The actual snapshot is saved in `tests.js.snap`.
Generated by [AVA](https://ava.li).
## Print stack trace of Build command UI settings
> Snapshot 1
`␊
┌─────────────────────────────┐␊
│ Netlify Build │␊
└─────────────────────────────┘␊
␊
> Version␊
@netlify/build 1.0.0␊
␊
> Flags␊
repositoryRoot: /file/path␊
␊
> Current directory␊
/file/path␊
␊
> Config file␊
No config file was defined: using default values.␊
␊
> Resolved config␊
build:␊
command: node --invalid␊
␊
> Context␊
production␊
␊
┌────────────────────────────────┐␊
│ 1. Build command from settings │␊
└────────────────────────────────┘␊
␊
$ node --invalid␊
␊
┌─────────────────────────────┐␊
│ "build.command" failed │␊
└─────────────────────────────┘␊
␊
Error message␊
Command failed with exit code 9: node --invalid␊
␊
Error location␊
In Build command from settings:␊
node --invalid␊
␊
Resolved config␊
build:␊
command: node --invalid␊
␊
node: bad option: --invalid`
## Print stack trace of build.command errors
> Snapshot 1
`␊
┌─────────────────────────────┐␊
│ Netlify Build │␊
└─────────────────────────────┘␊
␊
> Version␊
@netlify/build 1.0.0␊
␊
> Flags␊
repositoryRoot: /file/path␊
␊
> Current directory␊
/file/path␊
␊
> Config file␊
/file/path␊
␊
> Resolved config␊
build:␊
command: node --invalid␊
␊
> Context␊
production␊
␊
┌────────────────────────────────────┐␊
│ 1. build.command from netlify.toml │␊
└────────────────────────────────────┘␊
␊
$ node --invalid␊
␊
┌─────────────────────────────┐␊
│ "build.command" failed │␊
└─────────────────────────────┘␊
␊
Error message␊
Command failed with exit code 9: node --invalid␊
␊
Error location␊
In build.command from netlify.toml:␊
node --invalid␊
␊
Resolved config␊
build:␊
command: node --invalid␊
␊
node: bad option: --invalid`
## Print stack trace of build.command errors with stack traces
> Snapshot 1
`␊
┌─────────────────────────────┐␊
│ Netlify Build │␊
└─────────────────────────────┘␊
␊
> Version␊
@netlify/build 1.0.0␊
␊
> Flags␊
repositoryRoot: /file/path␊
␊
> Current directory␊
/file/path␊
␊
> Config file␊
/file/path␊
␊
> Resolved config␊
build:␊
command: node command.js␊
␊
> Context␊
production␊
␊
┌────────────────────────────────────┐␊
│ 1. build.command from netlify.toml │␊
└────────────────────────────────────┘␊
␊
$ node command.js␊
Error: test␊
STACK TRACE␊
␊
┌─────────────────────────────┐␊
│ "build.command" failed │␊
└─────────────────────────────┘␊
␊
Error message␊
Command failed with exit code 2: node command.js␊
␊
Error location␊
In build.command from netlify.toml:␊
node command.js␊
␊
Resolved config␊
build:␊
command: node command.js`
## Print stack trace of plugin errors
> Snapshot 1
`␊
┌─────────────────────────────┐␊
│ Netlify Build │␊
└─────────────────────────────┘␊
␊
> Version␊
@netlify/build 1.0.0␊
␊
> Flags␊
repositoryRoot: /file/path␊
␊
> Current directory␊
/file/path␊
␊
> Config file␊
/file/path␊
␊
> Resolved config␊
plugins:␊
- inputs: {}␊
origin: config␊
package: /file/path␊
␊
> Context␊
production␊
␊
> Loading plugins␊
- /file/path from netlify.toml␊
␊
┌─────────────────────────────────────┐␊
│ 1. onPreBuild command from /file/path │␊
└─────────────────────────────────────┘␊
␊
␊
┌──────────────────────────────────┐␊
│ Plugin "/file/path" internal error │␊
└──────────────────────────────────┘␊
␊
Error message␊
Error: test␊
␊
Plugin details␊
Package: /file/path␊
Version: 1.0.0␊
Repository: git+https://github.com/netlify/build.git␊
npm link: https://www.npmjs.com/package/@netlify/build␊
Report issues: https://github.com/netlify/build/issues␊
␊
Error location␊
In "onPreBuild" event in "/file/path" from netlify.toml␊
STACK TRACE␊
␊
Resolved config␊
plugins:␊
- inputs: {}␊
origin: config␊
package: /file/path`
## Print stack trace of plugin errors during load
> Snapshot 1
`␊
┌─────────────────────────────┐␊
│ Netlify Build │␊
└─────────────────────────────┘␊
␊
> Version␊
@netlify/build 1.0.0␊
␊
> Flags␊
repositoryRoot: /file/path␊
␊
> Current directory␊
/file/path␊
␊
> Config file␊
/file/path␊
␊
> Resolved config␊
plugins:␊
- inputs: {}␊
origin: config␊
package: /file/path␊
␊
> Context␊
production␊
␊
> Loading plugins␊
- /file/path from netlify.toml␊
␊
┌──────────────────────────────────┐␊
│ Plugin "/file/path" internal error │␊
└──────────────────────────────────┘␊
␊
Error message␊
Error: Could not import plugin:␊
test␊
␊
Plugin details␊
Package: /file/path␊
Version: 1.0.0␊
Repository: git+https://github.com/netlify/build.git␊
npm link: https://www.npmjs.com/package/@netlify/build␊
Report issues: https://github.com/netlify/build/issues␊
␊
Error location␊
While loading "/file/path" from netlify.toml␊
STACK TRACE␊
␊
Resolved config␊
plugins:␊
- inputs: {}␊
origin: config␊
package: /file/path`
## Print stack trace of validation errors
> Snapshot 1
`␊
┌─────────────────────────────┐␊
│ Netlify Build │␊
└─────────────────────────────┘␊
␊
> Version␊
@netlify/build 1.0.0␊
␊
> Flags␊
config: /file/path␊
␊
┌─────────────────────────────┐␊
│ Configuration error │␊
└─────────────────────────────┘␊
␊
Error message␊
When resolving config file /file/path␊
Configuration file does not exist␊
`
| 21.980198 | 67 | 0.423423 | eng_Latn | 0.229513 |
4be16868ece54b0ce83dcf5271be6bdf0a3b7912 | 6,406 | md | Markdown | _posts/2018/2018-02-04-自我总结-设计模式总结(一).md | uniquezhangqi/uniquezhangqi.github.io | b5bd9b2dc13da2fa6706be054b3de2f1e96d1ee9 | [
"MIT"
] | 5 | 2018-02-03T03:48:11.000Z | 2022-03-20T06:24:20.000Z | _posts/2018/2018-02-04-自我总结-设计模式总结(一).md | uniquezhangqi/uniquezhangqi.github.io | b5bd9b2dc13da2fa6706be054b3de2f1e96d1ee9 | [
"MIT"
] | 1 | 2020-07-22T11:19:04.000Z | 2020-07-22T11:19:04.000Z | _posts/2018/2018-02-04-自我总结-设计模式总结(一).md | uniquezhangqi/uniquezhangqi.github.io | b5bd9b2dc13da2fa6706be054b3de2f1e96d1ee9 | [
"MIT"
] | 1 | 2021-10-05T02:12:49.000Z | 2021-10-05T02:12:49.000Z | ---
layout: post # 使用的布局（不需要改）
title: 设计模式总结(一) # 标题
subtitle: Always on the way of programming.
date: 2018-02-04 # 时间
author: Ian # 作者
header-img: img/post-bg-hacker.jpg #这篇文章标题背景图片
catalog: true # 是否归档
iscopyright: true # 是否版权
tags: #标签
- 自我总结
- 编程之路
- 设计模式
---
<br>
> <br>
> 右侧可以看`目录`，点击直接跳转，这个系列一共写了4篇(可以点击下面直接跳转然后看右侧目录)：<br>
* [自我总结-设计模式总结(二)](http://uniquezhangqi.top/2018/03/02/自我总结-设计模式总结(二))<br>
* [自我总结-设计模式总结(三)](http://uniquezhangqi.top/2018/03/05/编程之路-设计模式总结(三))<br>
* [自我总结-设计模式总结(四)](http://uniquezhangqi.top/2018/03/08/编程之路-设计模式总结(四)/)<br>
## 前言
这是 阿琦 第一次写博客([做Java的](http://uniquezhangqi.top/about/))，这篇设计模式呢主要是针对面向对象语言，比如：.NET、C#、JAVA等等；面向对象编程需要尽量做到程序的**可维护**、**可复用**、**可扩展**，Java可以通过封装、继承、多态把程序的耦合度降低再合理使用设计模式使得程序更加灵活，容易修改，并且易于复用。
## 简单工厂模式
先上代码(商场促销)：
```java
// 现金收费抽象类,现金收取超类的抽象方法，收取现金，参数为原价，返回为当前价
public abstract class CashSuper {
public abstract double acceptCash(double money);
}
```
```java
// 正常收费子类，原价返回
public class CashNormal extends CashSuper {
@Override
public double acceptCash(double money) {
return money;
}
}
```
```java
// 打折收费子类，初始化时，必需要输入折扣率，如八折就是0.8
public class CashRebate extends CashSuper {
private double moneyRebate = 1d;
public CashRebate(String moneyRebate){
this.moneyRebate = Double.parseDouble(moneyRebate);
}
@Override
public double acceptCash(double money) {
return money * moneyRebate;
}
}
```
```java
// 返利收费子类，初始化时必须要输入返利条件和返利值，比如满300返100，则moneyCondition为300,moneyReturn为100
public class CashReturn extends CashSuper {
private double moneyCondition = 0.0d;
private double moneyReturn = 0.0d;
public CashReturn(String moneyCondition, String moneyReturn) {
this.moneyCondition = Double.parseDouble(moneyCondition);
this.moneyReturn = Double.parseDouble(moneyReturn);
}
@Override
public double acceptCash(double money) {
double result = money;
if (money >= moneyCondition) {
result = money - (money / moneyCondition) * moneyReturn;
}
return result;
}
}
```
```java
// 现金收费工厂类
public class CashFactory {
public static CashSuper createCashAccept(String type){
CashSuper cs = null;
switch (type){
case "正常收费":
cs = new CashNormal();
break;
case "满300返100":
CashReturn cr1 = new CashReturn("100","100");
cs = cr1;
break;
case "打8折":
CashRebate cr2 = new CashRebate("0,8");
cs = cr2;
break;
}
return cs;
}
}
```
上图代码设计：是先写一个父类，在继承它的实现多个打折和返利的子类，利用多态，完成这个代码。
> `聚合：`表示一种弱的‘拥有’关系，体现在A对象可以包含B对象，但是B对象不是A对象的一部分。
>
> `合成：`是一种强的‘拥有’关系，体现了严格的部分和整体的关系，部分和整体的生命周期都一样。
## 策略模式
> `策略模式`：它定义算法家族，分别封装起来，让它们之间可以互相替换，此模式让算法的变化不会影响到使用算法的客户。
#### 为什么要使用这个
策略模式是一种定义一系列算法的方法，从概念上来看，所有这些算法完成的都是相同的工作，只是实现不同，它可以以相同的方式调用所有的算法，减少了各种算法类与使用算法类之间的耦合。
#### 优点
策略模式简化了单元测试，因为每个算法都有自己的类，可以通过自己的接口单独测试。
#### 使用场景
策略模式就是用来封装算法的，在实践中，我们发现可以用它来封装几乎任何类型的规则，只要在分析过程中听到需要在不同时间应用不同的业务规则，就可以考虑使用策略模式处理这种变化的可能性。
#### 例子：
```java
//抽象算法类
public abstract class Strategy {
//算法方法
public abstract void algorithmInterface();
}
```
```java
//封装类具体的算法或者行为
public class ConcreteStrategyA extends Strategy {
//算法A实现方法
@Override
public void algorithmInterface() {
System.out.println("算法A实现");
}
}
public class ConcreteStrategyB extends Strategy{
//算法B实现方法
@Override
public void algorithmInterface() {
System.out.println("算法B实现");
}
}
public class ConcreteStrategyC extends Strategy{
//算法C实现方法
@Override
public void algorithmInterface() {
System.out.println("算法C实现");
}
}
```
```java
//上下文
public class Context {
Strategy strategy;
//初始化时，传入具体的策略对象
public Context(Strategy strategy){
this.strategy = strategy;
}
//上下文接口
public void ContextInterface(){
strategy.algorithmInterface();
}
}
```
```java
//“客户端代码”由于实例化不同的策略，所以最终在调用context.ContextInterface();时，所获得的结果就不尽相同。
public class Main {
public static void main(String[] args){
Context context;
context = new Context(new ConcreteStrategyA());
context.ContextInterface();
context = new Context(new ConcreteStrategyB());
context.ContextInterface();
context = new Context(new ConcreteStrategyC());
context.ContextInterface();
}
}
```
客户端只需要认识一个类Context就可以了，耦合更加降低。
## 单一职责原则
> `单一职责原则`：就一个类而言，应该仅有一个引起它变化的原因。如果一个类承担的职责过多，就等于把这些职责耦合在一起，一个职责的变化可能会削弱或者抑制这个类完成其它职责的能力。这种耦合会导致脆弱的设计，当变化发生时，设计会遭受到意想不到的破坏。
`总结`：工作中软件设计真正要做的许多内容，就是发现职责并把那些职责相互分离。如果你能够想到多于一个的动机去改变一个类，那么这个类就具有多于一个的职责，就应该考虑类的职责分离----**单一的职责这样的代码才是真正的易维护、易扩展、易复用、灵活多样。**
## 开放-封闭原则
> `开放--封闭原则`：是说软件实体(类、模块、函数等等)应该是可以扩展、但是不可修改。**对于扩展是开放的，对于更改是封闭的。**
- `会出现的问题`：绝对的对修改关闭是不可能的，无论模块是多么的‘封闭’，都会存在一些无法封闭的变化。既然不可能完全封闭，设计人员必须对于他设计的模块应该对哪种变化封闭做出选择。他必须先猜测出最有可能发生的变化种类，然后构造抽象来隔离那些变化。
- `核心`：开放--封闭原则 *是面向对象设计的核心所在*。遵循这个原则可以带来面向对象技术所声称的巨大好处，也就是*可维护、可扩展、可复用、灵活性好。*开发人员应该仅对程序中呈现出频繁变化的那些部分做出抽象，然而，对于应用程序中的每个部分都刻意地进行抽象同样不是一个好主意。*拒绝不成熟的抽象和抽象本身一样重要*。
- `总结`：面对需求，对程序的改动是通过增加新代码进行的，而不是更改现有的代码。
希望各位读者能对痛苦关闭，对快乐开放～😁
## 依赖倒转原则
> `依赖倒转原则`：高层模块不应该依赖低层模块，两个都应该依赖抽象。抽象不应该依赖细节，细节应该依赖抽象。
>
> `里氏代换原则`：子类型必须能够替换掉它们的父类型。
里氏代换原则解释：一个软件实体如果使用的是一个父类的话，那么一定适用于其子类，而且它察觉不出父类对象和子类对象的区别。也就是说，在软件里面，把父类都替换成它子类，程序的行为没有变化--简单地说，子类型必须能够替换掉它们的父类型。
- `影响`：也正因为这个原则，使得继承复用成为了可能，只有当子类可以替换掉父类，如软件单位的功能不收到影响时，父类才能真正被复用，而子类也能够在父类的基础上增加新的行为。
- 由于有里氏代换原则，才使得*开放-封闭成为了可能。*也可以这样说由于子类的可替代性才使得父类类型的模块在无需修改的情况下就可以扩展。
- `标志`：依赖倒转其实可以说是面向对象设计的标志，用哪种语言来编写程序都不重要，如果编写时考虑的都是如何针对抽象编程而不是针对细节编程，即程序中所有的依赖关系都是终止于抽象类或者接口，那就是面向对象设计，反之那就是过程化的设计了。
- `结语`：依赖倒转其实就是谁也不要依靠谁，除了约定的接口，大家都可以灵活自如。<br><br>
> 右侧可以看`目录`，点击直接跳转，这个系列一共写了4篇(可以点击下面直接跳转然后看右侧目录)：<br>
* [自我总结-设计模式总结(二)](http://uniquezhangqi.top/2018/03/02/自我总结-设计模式总结(二))<br>
* [自我总结-设计模式总结(三)](http://uniquezhangqi.top/2018/03/05/编程之路-设计模式总结(三))<br>
* [自我总结-设计模式总结(四)](http://uniquezhangqi.top/2018/03/08/编程之路-设计模式总结(四)/)<br>
***
### 结语
每个人吸收知识的时候，都要有抽取精华，去除糟粕的能力。作者所说的，可能有些是对的，有些是错的，有些是适合你的，有些是不太适合你的，你要自己能够判断。
其实你在生活和工作当中也是一样的，你身边的人形形色色，有的人你喜欢，有的人你很讨厌。但其实你喜欢的人也有缺点，你讨厌的人也有优点。你要学会从你讨厌的人身上学会他的优点，千万不要一棒子打死，这只会让你失去很多学习成长的机会。
希望本文可以帮助到作为程序猿或即将成为程序猿的你。
| 27.029536 | 187 | 0.682329 | yue_Hant | 0.55876 |
4be331d1873ec43fa8b3db7276faab312ef1bd14 | 3,480 | md | Markdown | README.md | abelbrencsan/boiled-page-image-component | ec9389ac22c8745adbf44d6aa0b766e2bdeb0ef9 | [
"MIT"
] | null | null | null | README.md | abelbrencsan/boiled-page-image-component | ec9389ac22c8745adbf44d6aa0b766e2bdeb0ef9 | [
"MIT"
] | null | null | null | README.md | abelbrencsan/boiled-page-image-component | ec9389ac22c8745adbf44d6aa0b766e2bdeb0ef9 | [
"MIT"
] | null | null | null | # Boiled Page image component
Image SCSS component for Boiled Page frontend framework. It is intended to place, format and and align images.
## Install
Place `_image.scss` file to `/assets/css/components` directory, and add its path to components block in `assets/css/app.scss` file.
## Usage
### Classes
Class name | Description | Example
---------- | ----------- | -------
`image` | Applies an image. | `<div class="image"></div>`
`image--left` | Sets image left aligned. | `<div class="image image--left"></div>`
`image--right` | Sets image right aligned. | `<div class="image image--right"></div>`
`image--center` | Sets image center aligned. | `<div class="image image--right"></div>`
`image--fit` | Sets image width to fit parent element. | `<div class="image image--fit"></div>`
### Examples
#### Example 1
The following example shows a fitted image.
```html
<div class="image image--fit">
<img src="https://picsum.photos/800/400" alt="Sample image" />
</div>
```
#### Example 2
The following example shows an image floats to the left in a text.
```html
<div class="image image--left">
<img src="https://picsum.photos/400/300" alt="Sample image" />
</div>
<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. In nec ex quam. Sed maximus maximus arcu, at tempor quam accumsan eleifend. Ut dictum mattis est, id porta velit tempus sit amet. Donec efficitur eu mauris nec cursus. Phasellus a ligula sit amet nibh egestas varius. Aenean malesuada turpis sapien, vel pellentesque dui viverra maximus. Vestibulum convallis erat ex, non varius justo bibendum sit amet. Nulla malesuada enim sed neque interdum, id laoreet libero dignissim. Maecenas fermentum tincidunt urna. Nullam volutpat ex a mi sollicitudin gravida a ac ipsum.</p>
<p>Quisque egestas gravida nisi, in cursus sem sagittis eu. Vestibulum lacinia ex mauris. Vivamus sit amet ante vel sem egestas pharetra non sed diam. Vivamus nec sapien at turpis semper vehicula a et purus. Ut nec magna arcu. Aenean elementum ex a risus placerat, sit amet tincidunt turpis pulvinar. Aliquam erat volutpat. Suspendisse nisl massa, sagittis sed consectetur vel, tempus vel odio. Vestibulum dictum odio sem, eu efficitur velit ultricies id. Aenean leo metus, egestas a sapien quis, scelerisque venenatis nisl. Donec tincidunt quam ac justo tincidunt pharetra. Nam vehicula augue a tortor condimentum, ut faucibus urna egestas.</p>
```
### Extension ideas
#### Cover image
```scss
// Image component variables
$image-cover-transition: 200ms ease;
/* Image component extensions */
div.image {
// Image cover effect
&.image--cover {
position: relative;
&:before {
background-color: rgba($bg-color, 0);
content: '';
display: block;
height: 100%;
left: 0;
position: absolute;
top: 0;
transition: background-color $image-cover-transition;
width: 100%;
}
body.no-touch &:hover:before {
background-color: rgba($bg-color,0.3);
}
}
}
```
#### Circle image
```scss
/* Image component extensions */
div.image {
// Circle image
&.image--circle {
img, canvas {
border-radius: 50%;
}
}
}
```
#### Lazy image
Use this extension idea for lazy image script.
```scss
/* Image component extensions */
div.image {
// Lazy image
&.image--lazy {
overflow: hidden;
img {
filter: blur(40px);
transition: filter 1.5s;
&.is-loaded {
filter: none;
}
}
}
}
```
| 29.243697 | 645 | 0.684483 | eng_Latn | 0.293952 |
4be351a6124fcb1fd0f0d9acd5d7e541ce28ba51 | 237 | md | Markdown | README.md | SWosnik/MyApplicationTest | 31b1e82af9f1f7af3650ff869676becffc78ad33 | [
"MIT"
] | null | null | null | README.md | SWosnik/MyApplicationTest | 31b1e82af9f1f7af3650ff869676becffc78ad33 | [
"MIT"
] | null | null | null | README.md | SWosnik/MyApplicationTest | 31b1e82af9f1f7af3650ff869676becffc78ad33 | [
"MIT"
] | null | null | null | 
# MyApplicationTest
This is only a test repo to play with github features.
| 29.625 | 82 | 0.793249 | eng_Latn | 0.402715 |
4be36e995e4893106b260ca510d7f02a407a975c | 2,781 | md | Markdown | docs/vs-2015/debugger/debug-interface-access/vtableshape.md | hericlesme/visualstudio-docs.pt-br | 086d2f88af868af84582bc7f1d50ffc5ea14b11f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/debugger/debug-interface-access/vtableshape.md | hericlesme/visualstudio-docs.pt-br | 086d2f88af868af84582bc7f1d50ffc5ea14b11f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/debugger/debug-interface-access/vtableshape.md | hericlesme/visualstudio-docs.pt-br | 086d2f88af868af84582bc7f1d50ffc5ea14b11f | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-07-26T14:58:39.000Z | 2021-07-26T14:58:39.000Z | ---
title: VTableShape | Microsoft Docs
ms.custom: ''
ms.date: 2018-06-30
ms.prod: visual-studio-dev14
ms.reviewer: ''
ms.suite: ''
ms.technology:
- vs-ide-debug
ms.tgt_pltfrm: ''
ms.topic: article
dev_langs:
- C++
helpviewer_keywords:
- VTableShape symbol
- SymTagVTableShape tag
ms.assetid: dd97f4c3-115d-46a9-b506-2531e30a0d8f
caps.latest.revision: 20
author: mikejo5000
ms.author: mikejo
manager: ghogen
ms.openlocfilehash: e2f40c276cbbac7815c3a21778e7980616c879cc
ms.sourcegitcommit: 55f7ce2d5d2e458e35c45787f1935b237ee5c9f8
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 08/22/2018
ms.locfileid: "47462843"
---
# <a name="vtableshape"></a>VTableShape
[!INCLUDE[vs2017banner](../../includes/vs2017banner.md)]
A versão mais recente deste tópico pode ser encontrada em [VTableShape](https://docs.microsoft.com/visualstudio/debugger/debug-interface-access/vtableshape).
O [VTable](../../debugger/debug-interface-access/vtable.md) símbolo tem um símbolo de filho de classe identificado pelo `SymTagVTableShape` marca.
## <a name="properties"></a>Propriedades
A tabela a seguir mostra as propriedades adicionais de válido para esse tipo de símbolo.
|Propriedade|Tipo de dados|Descrição|
|--------------|---------------|-----------------|
|[IDiaSymbol::get_constType](../../debugger/debug-interface-access/idiasymbol-get-consttype.md)|`BOOL`|`TRUE` Se a classe de VTable é marcada como uma constante.|
|[IDiaSymbol::get_count](../../debugger/debug-interface-access/idiasymbol-get-count.md)|`DWORD`|Número de entradas no VTable.|
|[IDiaSymbol::get_lexicalParent](../../debugger/debug-interface-access/idiasymbol-get-lexicalparent.md)|`IDiaSymbol*`|Símbolo compiland delimitador.|
|[IDiaSymbol::get_lexicalParentId](../../debugger/debug-interface-access/idiasymbol-get-lexicalparentid.md)|`DWORD`|ID do símbolo léxico pai.|
|[IDiaSymbol::get_symIndexId](../../debugger/debug-interface-access/idiasymbol-get-symindexid.md)|`DWORD`|ID de índice de símbolo.|
|[IDiaSymbol::get_symTag](../../debugger/debug-interface-access/idiasymbol-get-symtag.md)|`DWORD`|Retorna `SymTagVTableShape` (um dos [enumeração SymTagEnum](../../debugger/debug-interface-access/symtagenum.md) valores).|
|[IDiaSymbol::get_unalignedType](../../debugger/debug-interface-access/idiasymbol-get-unalignedtype.md)|`BOOL`|`TRUE` Se a classe de VTable é não alinhada.|
|[IDiaSymbol::get_volatileType](../../debugger/debug-interface-access/idiasymbol-get-volatiletype.md)|`BOOL`|`TRUE` Se a classe de VTable é marcada como volátil.|
## <a name="see-also"></a>Consulte também
[Hierarquia de classes de tipos de símbolo](../../debugger/debug-interface-access/class-hierarchy-of-symbol-types.md)
[VTable](../../debugger/debug-interface-access/vtable.md)
| 49.660714 | 223 | 0.746854 | por_Latn | 0.177559 |
4be3827b19627c46fbecc31ef11369eba7d29418 | 1,054 | md | Markdown | CONTRIBUTING.md | sotostzam/acumen | a8ae372544e348a939d00861bff256d1c6242820 | [
"BSD-3-Clause"
] | null | null | null | CONTRIBUTING.md | sotostzam/acumen | a8ae372544e348a939d00861bff256d1c6242820 | [
"BSD-3-Clause"
] | null | null | null | CONTRIBUTING.md | sotostzam/acumen | a8ae372544e348a939d00861bff256d1c6242820 | [
"BSD-3-Clause"
] | 2 | 2020-07-30T08:20:29.000Z | 2020-12-13T12:10:32.000Z | # Contributing
## COPYRIGHT ISSUES - Read carefully before working on code
By agreeing to contribute to the development of this software, the
authors agree that Walid Taha:
1. Is the contact person for anyone interested in the software,
2. Represents the copyright that contributors own to work that
appears in the software,
3. Is responsible for licensing the software, and does not
need to consult with all contributors to make licensing
arrangements for the software
If you have any questions, please contact Walid Taha at
(maroneal@gmail.com).
---
## TECHNICAL TIPS
| Code | Description |
|---------------------------|:----------------------------------------------|
| ```sbt run``` | builds and runs Acumen from source |
| ```sbt test``` | runs the standard test suite (do before push) |
| ```sbt assembly``` | builds a jar file for Acumen |
| ```sbt "run --newplot"``` | runs acumen with experimental plot function |
| 37.642857 | 77 | 0.601518 | eng_Latn | 0.995618 |
4be3cfaafdef5937eb1643f8ec19f3b0193eaabd | 9,944 | md | Markdown | articles/site-recovery/hyper-v-vmm-azure-tutorial.md | beatrizmayumi/azure-docs.pt-br | ca6432fe5d3f7ccbbeae22b4ea05e1850c6c7814 | [
"CC-BY-4.0",
"MIT"
] | 39 | 2017-08-28T07:46:06.000Z | 2022-01-26T12:48:02.000Z | articles/site-recovery/hyper-v-vmm-azure-tutorial.md | beatrizmayumi/azure-docs.pt-br | ca6432fe5d3f7ccbbeae22b4ea05e1850c6c7814 | [
"CC-BY-4.0",
"MIT"
] | 562 | 2017-06-27T13:50:17.000Z | 2021-05-17T23:42:07.000Z | articles/site-recovery/hyper-v-vmm-azure-tutorial.md | beatrizmayumi/azure-docs.pt-br | ca6432fe5d3f7ccbbeae22b4ea05e1850c6c7814 | [
"CC-BY-4.0",
"MIT"
] | 113 | 2017-07-11T19:54:32.000Z | 2022-01-26T21:20:25.000Z | ---
title: Configurar a recuperação de desastre do Hyper-V (com VMM) usando o Azure Site Recovery
description: Saiba como configurar a recuperação de desastre de VMs locais do Hyper-V em nuvens do System Center VMM para o Azure usando o Site Recovery.
ms.topic: tutorial
ms.date: 03/19/2020
ms.custom: MVC
ms.openlocfilehash: c806f968bc6530879f64ddbf6fd4c7d45aa7a8d3
ms.sourcegitcommit: f28ebb95ae9aaaff3f87d8388a09b41e0b3445b5
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 03/29/2021
ms.locfileid: "89442813"
---
# <a name="set-up-disaster-recovery-of-on-premises-hyper-v-vms-in-vmm-clouds-to-azure"></a>Configurar a recuperação de desastre de VMs locais do Hyper-V em nuvens do VMM para o Azure
Este tutorial descreve como habilitar a replicação de VMs (máquinas virtuais) Hyper-V locais gerenciadas pelo System Center VMM (Virtual Machine Manager) para o Azure, usando o [Azure Site Recovery](site-recovery-overview.md). Se você não estiver usando o VMM, [siga este tutorial](hyper-v-azure-tutorial.md).
Neste tutorial, você aprenderá como:
> [!div class="checklist"]
> * Selecionar a origem e o destino de replicação.
> * Configurar o ambiente de replicação de origem, incluindo componentes de Site Recovery locais e o ambiente de replicação de destino.
> * Configurar o mapeamento de rede entre as redes de VM do VMM e as redes virtuais do Azure.
> * Criar uma política de replicação.
> * Habilitar a replicação para uma VM.
> [!NOTE]
> Os tutoriais mostram o caminho de implantação mais simples para um cenário. Eles usam opções padrão quando possível e não mostram todas as possíveis configurações e caminhos. Para obter instruções detalhadas, leia o artigo na seção **Guias de Instruções** da [documentação do Site Recovery](./index.yml).
## <a name="prerequisites"></a>Pré-requisitos
Este tutorial supõe que você já concluiu as seguintes etapas:
1. [Preparar o Azure](tutorial-prepare-azure.md)
1. [Preparar servidores Hyper-V locais](hyper-v-prepare-on-premises-tutorial.md)
## <a name="select-a-replication-goal"></a>Selecione uma meta de replicação
1. No portal do Azure, acesse **Cofres dos Serviços de Recuperação** e selecione o cofre **ContosoVMVault** que foi criado no tutorial [Preparar o Azure](tutorial-prepare-azure.md#create-a-recovery-services-vault).
1. Em **Introdução**, selecione **Site Recovery** > **Preparar Infraestrutura** e defina as seguintes configurações:
1. Em **Meta de proteção** > **Em que local os seus computadores estão?** , selecione **Local**.
1. Em **Para que local deseja replicar os seus computadores?** , selecione **Para o Azure**.
1. Em **Os seus computadores estão virtualizados?** , selecione **Sim, com o Hyper-V**.
1. Em **Você está usando o VMM do System Center para gerenciar seus hosts Hyper-V**, selecione **Sim**.
1. Selecione **OK**.
## <a name="confirm-deployment-planning"></a>Confirmar planejamento de implantação
1. Em **Planejamento de implantação**, se você estiver planejando uma implantação grande, baixe o Planejador de Implantações do Hyper-V usando o link na página. [Saiba mais](hyper-v-deployment-planner-overview.md) sobre o planejamento de implantação do Hyper-V.
1. Para este tutorial, não precisamos do Planejador de Implantações. Em **Você concluiu o planejamento de implantação?** , selecione **Farei isso mais tarde** e, em seguida, selecione **OK**.
## <a name="set-up-the-source-environment"></a>Configurar o ambiente de origem
Quando configurar o ambiente de origem, instale o Provedor do Azure Site Recovery no servidor do VMM e registre o servidor no cofre. Você instala o agente de Serviços de Recuperação do Azure em cada host Hyper-V.
1. **Preparar a Infraestrutura**. Selecione **Origem**.
1. **Preparar a origem**. Selecione **+VMM** para adicionar um servidor do VMM. Em **Adicionar Servidor**, verifique se o **Servidor do System Center VMM** aparece em **Tipo de servidor**.
1. Baixe o instalador do Provedor do Microsoft Azure Site Recovery.
1. Baixe a chave do registro do cofre. Você precisará dessa chave quando executar a instalação do Provedor. A chave é válida por cinco dias após ser gerada.
1. Baixe o instalador do agente dos Serviços de Recuperação do Microsoft Azure.
### <a name="install-the-provider-on-the-vmm-server"></a>Instalar o Provedor no servidor VMM
1. No **Microsoft Update** do assistente de instalação do Provedor do Azure Site Recovery. Escolher usar o Microsoft Update para verificar atualizações do Provedor.
1. **Instalação**. Aceite a localização de instalação padrão do Provedor e selecione **Instalar**.
1. Após a instalação, no Assistente de Registro do Microsoft Azure Site Recovery, selecione **Configurações do Cofre**, **Procurar** e, em **Arquivo de chave**, selecione a chave do cofre do arquivo que você baixou.
1. Especifique a assinatura do Azure Site Recovery e o nome do cofre (**ContosoVMVault**). Especifique um nome amigável para o servidor de VMM para identificá-lo no cofre.
1. **Configurações de Proxy**. Selecione **Conectar-se diretamente ao Azure Site Recovery sem um proxy**.
1. Aceite o local padrão para o certificado que é usado para criptografar dados. Dados criptografados serão descriptografados quando você executar o failover.
1. **Sincronizar metadados da nuvem**. Selecione **Sincronizar os metadados da nuvem com o portal do Site Recovery**. Esta ação só precisa acontecer uma vez em cada servidor. Em seguida, selecione **Registrar**.
1. Depois que o servidor foi registrado no cofre, selecione **Concluir**.
Após a conclusão do registro, os metadados do servidor são recuperados pelo Azure Site Recovery e o servidor VMM é exibido em **Infraestrutura do Site Recovery**.
### <a name="install-the-recovery-services-agent-on-hyper-v-hosts"></a>Instalar o agente dos Serviços de Recuperação em hosts do Hyper-V
Instale o agente em cada host Hyper-V que contém máquinas virtuais que você deseja replicar.
No Assistente de Instalação do Agente de Serviços de Recuperação do Microsoft Azure, defina estas configurações:
1. **Verificação de Pré-requisitos**. Selecione **Avançar**. Pré-requisitos faltantes serão instalados automaticamente.
1. **Configurações de Instalação**. Aceite o local da instalação. Em seguida, selecione **Instalar**.
>[!NOTE]
>Pra o Azure Site Recovery, o **Local do Cache** não é necessário.
1. **Instalação**. Quando a instalação for concluída, selecione **Fechar** para concluir o assistente.
## <a name="set-up-the-target-environment"></a>Configurar o ambiente de origem
1. Selecione **Preparar infraestrutura** > **Destino**.
1. Selecione a assinatura e o grupo de recursos **ContosoRG**, em que as VMs do Azure serão criadas após o failover.
1. Selecione o modelo de implantação do **Resource Manager**.
O Site Recovery verifica se você tem uma ou mais contas de armazenamento e redes do Azure compatíveis.
## <a name="configure-network-mapping"></a>Configurar o mapeamento de rede
1. Acesse **Infraestrutura do Site Recovery** > **Mapeamentos de rede** > **Mapeamento de Rede**. Selecione o ícone **+ Mapeamento de Rede**.
1. **Adicionar mapeamento de rede**. Selecione o servidor de **Origem do System Center VMM**. Em **Destino**, selecione Azure.
1. Verifique a assinatura e o modelo de implantação após o failover.
1. **Rede de origem**. Selecione a rede de VMs locais de origem.
1. **Rede de destino**. Selecione a rede do Azure na qual as VMs do Azure de réplica estarão localizadas quando criadas após o failover. Depois, selecione **OK**.
## <a name="set-up-a-replication-policy"></a>Configurar uma política de replicação
1. Selecione **Preparar a Infraestrutura** > **Configurações de Replicação** > **+Criar e associar**.
1. Em **Criar e associar política**, especifique um nome de política. Estamos usando **ContosoReplicationPolicy**.
1. Aceite as configurações padrão e selecione **OK**:
- **Frequência de cópia** indica que, após a replicação inicial, os dados delta serão replicadas a cada cinco minutos.
- **Retenção do ponto de recuperação** indica que cada ponto de recuperação será mantido por duas horas.
- **Frequência do instantâneo consistente com o aplicativo** indica que os pontos de recuperação contendo instantâneos consistentes com aplicativos serão criados a cada hora.
- **Hora de início para replicação inicial** indica que a replicação inicial deve começar imediatamente.
- **Criptografar dados armazenados no Azure** é definido para o padrão (**Desativado**) e indica que dados em repouso no Azure não são criptografados.
1. Depois que a política for criada, selecione **OK**. Quando você cria uma nova política, ela é automaticamente associada à nuvem do VMM.
## <a name="enable-replication"></a>Habilitar a replicação
1. **Replicar aplicativo**. Selecione **Origem**.
1. **Fonte**. Selecione a nuvem do VMM. Depois, selecione **OK**.
1. **Destino**. Verifique o destino (Azure), a assinatura do cofre e selecione o modelo do **Resource Manager**.
1. Selecione a conta de armazenamento **contosovmsacct1910171607** e a rede do Azure **ContosoASRnet**.
1. **Máquinas virtuais** > **Selecionar**. Selecione a VM que você deseja replicar. Depois, selecione **OK**.
É possível acompanhar o progresso da ação **Habilitar Proteção** em **Trabalhos** > **Trabalhos do Site Recovery**. Depois que o trabalho **Finalizar Proteção** for concluído, a replicação inicial será concluída e a VM estará pronta para failover.
## <a name="next-steps"></a>Próximas etapas
> [!div class="nextstepaction"]
> [Realizar uma simulação de recuperação de desastre](tutorial-dr-drill-azure.md)
| 71.539568 | 309 | 0.759453 | por_Latn | 0.9991 |