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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
fadeaa86cf9dc3c4804ec3a112aa9cbb55aec350 | 29 | md | Markdown | README.md | godofwasabi/Liberty_Prime | 3c3dea0d0ec896ffd1ebb542144074cce7e39e39 | [
"MIT"
] | null | null | null | README.md | godofwasabi/Liberty_Prime | 3c3dea0d0ec896ffd1ebb542144074cce7e39e39 | [
"MIT"
] | null | null | null | README.md | godofwasabi/Liberty_Prime | 3c3dea0d0ec896ffd1ebb542144074cce7e39e39 | [
"MIT"
] | null | null | null | # Liberty_Prime
memes.drop()
| 9.666667 | 15 | 0.758621 | lit_Latn | 0.123846 |
fadf0302e95bf2e2e4c903c225c099c1f2625f99 | 1,473 | md | Markdown | AlchemyInsights/addressing-teams-sign-in-error-aadsts9000411.md | pebaum/OfficeDocs-AlchemyInsights-pr.sk-SK | dc2b4209619dc1eaac602b2a4302f5516ffd37c4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/addressing-teams-sign-in-error-aadsts9000411.md | pebaum/OfficeDocs-AlchemyInsights-pr.sk-SK | dc2b4209619dc1eaac602b2a4302f5516ffd37c4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | AlchemyInsights/addressing-teams-sign-in-error-aadsts9000411.md | pebaum/OfficeDocs-AlchemyInsights-pr.sk-SK | dc2b4209619dc1eaac602b2a4302f5516ffd37c4 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Riešenie tímov Sign-in chyba AADSTS9000411
ms.author: pebaum
author: pebaum
manager: mnirkhe
ms.audience: Admin
ms.topic: article
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Priority
ms.collection: Adm_O365
ms.custom:
- "9000744"
- "5689"
ms.openlocfilehash: b70f1320ea1dfa29e6fa489bd02acfcd1d92971b
ms.sourcegitcommit: 88d2918aa51f4ba10771527380c3e0db0f5a9147
ms.translationtype: MT
ms.contentlocale: sk-SK
ms.lasthandoff: 05/20/2020
ms.locfileid: "44358371"
---
# <a name="addressing-teams-sign-in-error-aadsts9000411"></a>Riešenie tímov Sign-in chyba AADSTS9000411
Pri prihlasovaní do Microsoft teams sa môže zobraziť chyba: **Ľutujeme, ale máme problémy s prihlásením sa do AADSTS9000411: požiadavka nie je správne naformátovaná. Parameter "login_hint" sa duplikuje.**
Ak chcete vyriešiť tento problém, uistite sa, že vaši klienti Microsoft teams sú aktualizované. Ďalšie informácie o aktualizácii klienta nájdete v téme [Aktualizácia tímov Microsoft teams](https://support.office.com/article/Update-Microsoft-Teams-535a8e4b-45f0-4f6c-8b3d-91bca7a51db1).
Ak nie je možné aktualizovať klienta z nejakého dôvodu, odhlásenie klienta bude jasné väčšina cache údajov. Avšak, ak máte stále problémy po odhlásenie/prihlásenie, ukončite tímy a vymažte vyrovnávaciu pamäť klienta vykonaním nasledujúcich krokov:
1. Zatvorte program Microsoft teams.
2. Prejdite na:%AppData%\microsoft\teams a odstráňte všetky súbory.
3. Znova otvorte program Microsoft teams.
| 47.516129 | 285 | 0.818737 | slk_Latn | 0.983061 |
fadfab0d35130535e58ad90d78d4c383a6d08a3d | 747 | md | Markdown | includes/cognitive-services-luis-qs-endpoint-luis-repo-note.md | changeworld/azure-docs.pt-pt | 8a75db5eb6af88cd49f1c39099ef64ad27e8180d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/cognitive-services-luis-qs-endpoint-luis-repo-note.md | changeworld/azure-docs.pt-pt | 8a75db5eb6af88cd49f1c39099ef64ad27e8180d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/cognitive-services-luis-qs-endpoint-luis-repo-note.md | changeworld/azure-docs.pt-pt | 8a75db5eb6af88cd49f1c39099ef64ad27e8180d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: incluir ficheiro
description: incluir ficheiro
services: cognitive-services
author: diberry
manager: cgronlun
ms.custom: include file
ms.service: cognitive-services
ms.subservice: luis
ms.topic: include
ms.date: 08/16/2018
ms.author: diberry
ms.openlocfilehash: ed1baef31d91ea09e48e6c9b4b2b402818675d1d
ms.sourcegitcommit: 778e7376853b69bbd5455ad260d2dc17109d05c1
ms.translationtype: MT
ms.contentlocale: pt-PT
ms.lasthandoff: 05/23/2019
ms.locfileid: "66237976"
---
> [!NOTE]
> A solução completa está disponível a partir da [ **cognitivos-services--compreensão de idiomas** repositório do GitHub](https://github.com/Azure-Samples/cognitive-services-language-understanding/blob/master/documentation-samples/quickstarts/analyze-text/).
| 33.954545 | 258 | 0.817938 | por_Latn | 0.272575 |
fadfbe5a2607f7712f3dc58610de419a9f58fc01 | 1,130 | md | Markdown | src/components/destinationsCatalogue/destinationsConfigure/SEGMENT.md | daniel-statsig/config-generator | 4dceb72e9a11d560a1b0da0c99b2def960bc9a0e | [
"MIT"
] | 10 | 2020-10-12T08:48:01.000Z | 2022-03-09T11:32:09.000Z | src/components/destinationsCatalogue/destinationsConfigure/SEGMENT.md | daniel-statsig/config-generator | 4dceb72e9a11d560a1b0da0c99b2def960bc9a0e | [
"MIT"
] | 5 | 2021-05-29T12:31:18.000Z | 2022-03-28T19:36:53.000Z | src/components/destinationsCatalogue/destinationsConfigure/SEGMENT.md | daniel-statsig/config-generator | 4dceb72e9a11d560a1b0da0c99b2def960bc9a0e | [
"MIT"
] | 21 | 2020-11-06T07:24:12.000Z | 2022-03-07T19:27:26.000Z | ## Segment
Segment is a Customer Data Platform (CDP) that allows you to collect your customer data, while giving you complete control over how you use it. It is a popular tool that is used by many businesses to collect and send event data to various platforms, such as Zendesk, Optimizely, Google Analytics, and more.
### Get More Out of Segment With RudderStack
You can now use RudderStack to capture your event data across various sources, and route them to Segment in real-time. Simply add Segment as a destination on the RudderStack dashboard, configure the integration using your Segment write key, and get started in no time.
### Useful Links
[Segment Website][]
[Documentation and Setup guide](): Coming Soon
[View on GitHub][]
[//]: # "These are reference links used in the body of this note and get stripped out when the markdown processor does its job. There is no need to format nicely because it shouldn't be seen. Thanks SO - http://stackoverflow.com/questions/4823468/store-comments-in-markdown-syntax"
[segment website]: https://segment.com/
[view on github]: https://github.com/rudderlabs/rudder-server
| 59.473684 | 306 | 0.773451 | eng_Latn | 0.995677 |
fae0510cecf1370db98482c099b51be031c6c6be | 574 | md | Markdown | class_prep/p-use-javascript-for-interactivity.md | UCB-INFO-FRONTEND-WEBARCH/ucb-info-frontend-webarch.github.io | dcc62239e1999dd7d10107067c4dced82b0c63c3 | [
"MIT"
] | 9 | 2019-09-01T23:49:42.000Z | 2021-09-18T23:05:28.000Z | class_prep/p-use-javascript-for-interactivity.md | UCB-INFO-FRONTEND-WEBARCH/ucb-info-frontend-webarch.github.io | dcc62239e1999dd7d10107067c4dced82b0c63c3 | [
"MIT"
] | 6 | 2019-12-03T13:41:48.000Z | 2022-02-10T19:11:26.000Z | class_prep/p-use-javascript-for-interactivity.md | UCB-INFO-FRONTEND-WEBARCH/ucb-info-frontend-webarch.github.io | dcc62239e1999dd7d10107067c4dced82b0c63c3 | [
"MIT"
] | null | null | null | # Class Prep: Use JavaScript for interactivity
## Learn more about the DOM and Events
- [The Document Object Model](http://eloquentjavascript.net/14_dom.html)
- [Handling Events](http://eloquentjavascript.net/15_event.html)
## Tutorial to try out DOM manipulation
- [Build a simple color game](https://www.freecodecamp.org/news/learn-how-to-manipulate-the-dom-by-building-a-simple-javascript-color-game-1a3aec1d109a)
## References
- [HTML Forms](http://www.w3schools.com/html/html_forms.asp)
- [JavaScript in Forms (Part 2: Browser)](http://eloquentjavascript.net)
| 41 | 153 | 0.761324 | yue_Hant | 0.528194 |
fae16aff90678d87db0a8263ee6c6a0cc019f1c7 | 657 | md | Markdown | ansible/roles/hackforclues.hackforclues/README.md | myrjola/hackforclues | 7eddb63236421c634e1ade28ebce14ba99aa4d76 | [
"MIT"
] | null | null | null | ansible/roles/hackforclues.hackforclues/README.md | myrjola/hackforclues | 7eddb63236421c634e1ade28ebce14ba99aa4d76 | [
"MIT"
] | null | null | null | ansible/roles/hackforclues.hackforclues/README.md | myrjola/hackforclues | 7eddb63236421c634e1ade28ebce14ba99aa4d76 | [
"MIT"
] | null | null | null | HackForClues deployer
=====================================
Deploys the hackforclues service using nginx, postgresql and gunicorn.
Certificates are set up with Let's Encrypt.
Requirements
------------
Ubuntu Xenial server.
Role Variables
--------------
These secrets are good to store in a vault outside of the repo
- vault_hackforclues_secret_key: Django secret key
- vault_hackforclues_psql_password: password for postgres
- vault_hackforclues_hostname: Domain for the service
- vault_hackforclues_email: Email that is reported to letsencrypt
License
-------
MIT
Author Information
------------------
Martin Yrjölä <https://github.com/myrjola>
| 20.53125 | 70 | 0.707763 | eng_Latn | 0.825403 |
fae2f11b98a2c0e44d8f10b236ab2048e0cc3ea9 | 604 | md | Markdown | docs/0.Prepare/1.Prepare.md | usedtolove/ros-study | 4fa70c9c9f1aad6de879e7de6d2d95bbe9b3a36d | [
"Apache-2.0"
] | null | null | null | docs/0.Prepare/1.Prepare.md | usedtolove/ros-study | 4fa70c9c9f1aad6de879e7de6d2d95bbe9b3a36d | [
"Apache-2.0"
] | null | null | null | docs/0.Prepare/1.Prepare.md | usedtolove/ros-study | 4fa70c9c9f1aad6de879e7de6d2d95bbe9b3a36d | [
"Apache-2.0"
] | null | null | null | # Prepare Dev Env
1. sudo apt install git git-gui
2. install apps from shell
`sudo apt install shutter guake`
3. Enable show desktop shortcut
`Appearance > behavior > Add show desktop icon to the Launcher`
4. Add guake to startup
----------
## optional
1. install apps from software center(with addons)
GIMP – Advanced image editor similar to Photoshop
SMPlayer
VLC
2. install apps from shell
`sudo apt install p7zip-full`
3. install chrome
`wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb`
`sudo dpkg -i ./google-chrome-stable_current_amd64.deb`
| 24.16 | 80 | 0.736755 | eng_Latn | 0.573596 |
fae32ff400443afe81168960d6ab821953c6a95d | 804 | md | Markdown | _posts/archive/20/2017-08-12-Why-we-desperately-need-women-to-design-AI.md | polgarp/alg-exp | 07822f0707d09dd12c1d76dd5e438e866b865470 | [
"MIT"
] | null | null | null | _posts/archive/20/2017-08-12-Why-we-desperately-need-women-to-design-AI.md | polgarp/alg-exp | 07822f0707d09dd12c1d76dd5e438e866b865470 | [
"MIT"
] | null | null | null | _posts/archive/20/2017-08-12-Why-we-desperately-need-women-to-design-AI.md | polgarp/alg-exp | 07822f0707d09dd12c1d76dd5e438e866b865470 | [
"MIT"
] | null | null | null | ---
layout: post
title: "Why we desperately need women to design AI"
posturl: https://medium.freecodecamp.org/why-we-desperately-need-women-to-design-ai-72cb061051df
tags:
- Woman in tech
- Assistant
- Bias
---
{% include post_info_header.md %}
This article makes some nice points, and diverse teams do create better products. But there is actually more. Due to the nature of AI tech, it's not just a strictly interface question (like pre-programmed answers in an assistant) if a product can be well designed without women. The data collection and learning methods are just as important and can make or break a diverse enough product. So if anything issues from not having women (or diverse teams in general) in product teams will just grow in magnitude.
<!--more-->
{% include post_info_footer.md %}
| 47.294118 | 509 | 0.773632 | eng_Latn | 0.998377 |
fae4e600bfb9fcd9e2ea8636d2e7b0c6aefa0d5e | 136 | md | Markdown | README.md | jerossh/mingpian | 2168df25cc5d0ae824d054b8947502ed4457b052 | [
"MIT"
] | null | null | null | README.md | jerossh/mingpian | 2168df25cc5d0ae824d054b8947502ed4457b052 | [
"MIT"
] | null | null | null | README.md | jerossh/mingpian | 2168df25cc5d0ae824d054b8947502ed4457b052 | [
"MIT"
] | null | null | null | # express init
### About
This program creates by express + jade + mongodb
### History
* 2016-11-28 Finish v0.0.1
### License
MIT
| 9.714286 | 48 | 0.654412 | eng_Latn | 0.916173 |
fae4f06dc6e0f5d38f95f0dc8fd644e966241c9f | 1,942 | md | Markdown | README.md | hevily/vue-sui-demo | fb67db4304585766d88e408b3b5878ff3b1db034 | [
"MIT"
] | 45 | 2016-05-23T09:53:12.000Z | 2019-07-18T11:33:30.000Z | README.md | andyphp/vue-sui-demo | fb67db4304585766d88e408b3b5878ff3b1db034 | [
"MIT"
] | null | null | null | README.md | andyphp/vue-sui-demo | fb67db4304585766d88e408b3b5878ff3b1db034 | [
"MIT"
] | 19 | 2016-03-31T08:08:28.000Z | 2019-11-24T00:52:17.000Z | # vue-sui-demo
> 持续更新，如果对您有帮助，您可以点右上角 "Star" 支持一下 谢谢！ ^_^
> 后面有空再写学习历程和遇到的问题
---
Vue很轻量，易定制，比较适合移动端，很喜欢Vue写组件的方式，
所有用[VUE](http://cn.vuejs.org/) 和 [SUI-Mobile](http://m.sui.taobao.org/) 写了一个移动端demo，用来反馈vue的学习成果（禁用了SUI自带的路由，使用[Vue-router](https://github.com/vuejs/vue-router)）
##### 环境
1. node v5.5.0
2. npm 3.3.9
##### 技术栈
> [vue](https://github.com/vuejs/vue)
> [vue-router](https://github.com/vuejs/vue-router)
> [vue-resource](https://github.com/vuejs/vue-resource)
> [webpack](http://webpack.github.io/docs/)
> [sui-mobile](http://m.sui.taobao.org/)
> [es6-babel](https://babeljs.io/docs/learn-es2015/)
---
### 截图
---
---
### 安装
项目地址：（使用`git clone`）
```shell
git clone https://github.com/eteplus/vue-sui-demo.git
```
通过`npm`安装本地服务第三方依赖模块(需要已安装[Node.js](https://nodejs.org/))，使用npm安装依赖模块可能会很慢，建议换成[cnpm](http://cnpmjs.org/)
```shell
npm install -g cnpm --registry=http://registry.npm.taobao.org
```
```bash
# 安装依赖模块
cnpm install
# 启动服务
npm run dev
# 发布代码
npm run build
# 发布后启动服务
npm run main
```
### 开发
### 目录结构
<pre>
.
├── README.md
├── dist // 项目build目录
├── build // 项目的配置文件目录
│ ├── dev-server.js // 开发的服务配置
│ ├── webpack-dev-conf.js // 开发的Webpack 配置文件
│ ├── webpack-prod-conf.js // 生产的Webpack 配置文件
│ ├── webpack-base-conf.js // 基本的Webpack 配置文件
├── index.js // 项目发布后的启动文件
├── package.json // 项目配置文件
├── src // 生产目录
│ ├── assets // css js 和图片资源
│ ├── data // 数据文件
│ ├── components // 各种组件
│ ├── views // 各种页面
│ ├── directives // 各种指令
│ ├── filters.js // 各种过滤器
│ ├── router.js // 路由配置
│ └── main.vue // 根组件
│ └── app.js // Webpack 预编译入口
│ └── index.html // 项目入口文件
.
</pre>
### 更新记录
参看 [CHANGELOG.md](./CHANGELOG.md)
| 20.229167 | 161 | 0.547374 | yue_Hant | 0.352055 |
fae509388ffa258eab50903d62e9e7687e0c944e | 252 | md | Markdown | packages/kafka-management-sdk/docs/ServiceAccountList.md | k-wall/app-services-sdk-java | 95d1eedf580ff1b87dde9a5df9dcaa2a291099ee | [
"Apache-2.0"
] | 6 | 2021-05-27T10:57:28.000Z | 2022-02-23T10:00:32.000Z | packages/kafka-management-sdk/docs/ServiceAccountList.md | k-wall/app-services-sdk-java | 95d1eedf580ff1b87dde9a5df9dcaa2a291099ee | [
"Apache-2.0"
] | 57 | 2021-05-12T15:35:56.000Z | 2022-03-12T11:07:48.000Z | packages/kafka-management-sdk/docs/ServiceAccountList.md | k-wall/app-services-sdk-java | 95d1eedf580ff1b87dde9a5df9dcaa2a291099ee | [
"Apache-2.0"
] | 8 | 2021-06-04T12:56:06.000Z | 2022-03-11T17:44:57.000Z |
# ServiceAccountList
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**kind** | **String** | |
**items** | [**List<ServiceAccountListItem>**](ServiceAccountListItem.md) | |
| 16.8 | 85 | 0.480159 | yue_Hant | 0.746828 |
fae66f7fea5df045eee2c58fbeea8c1c0104503f | 1,807 | md | Markdown | Site/BSSwFellowshipProgram/People/Rubio-GonzalezCi.md | danielskatz/bssw.io | 6299644272b15f08ec775598078717571a34f1a6 | [
"MIT"
] | 1 | 2021-10-15T04:40:53.000Z | 2021-10-15T04:40:53.000Z | Site/BSSwFellowshipProgram/People/Rubio-GonzalezCi.md | danielskatz/bssw.io | 6299644272b15f08ec775598078717571a34f1a6 | [
"MIT"
] | null | null | null | Site/BSSwFellowshipProgram/People/Rubio-GonzalezCi.md | danielskatz/bssw.io | 6299644272b15f08ec775598078717571a34f1a6 | [
"MIT"
] | null | null | null | **Year:** 2020
**Name:** Cindy Rubio-Gonzalez
**Affiliation:** University of California, Davis
**Image:** /images/blob/master/People_CindyRubioGonzalez.jpg
**URL:** https://web.cs.ucdavis.edu/~rubio
**LinkedIn:** https://www.linkedin.com/in/cindy-rubio-gonz%C3%A1lez-32769a2b/
**Github:** https://github.com/crubiog
**Short Bio:** Improving the reliability and performance of numerical software
**Long Bio:**
### Improve the correctness of numerical software and the effective use of mixed floating-point precision for better performance.
Cindy is organizing events and developing educational materials on the correctness of numerical software and improving performance through effective use of mixed floating-point precision. Scope includes the use and evaluation of program-analysis techniques to improve the reliability and performance of numerical software.
Cindy is an Assistant Professor of Computer Science at the University of California, Davis. Her research spans the areas of Programming Languages and Software Engineering, with a focus on program analysis for automated bug finding and program optimization. She is particularly interested in the reliability and performance of systems software and scientific applications. Cindy is a recipient of a DOE Early Career Award 2019 and an NSF CAREER Award 2018.
### Selected resources
<a href="https://ideas-productivity.org/events/hpc-best-practices-webinars/#webinar045" class="link-row">HPC Best Practices Webinar: Scalable Precision Tuning of Numerical Software</a>
<a href="https://figshare.com/collections/SIAM_CSE21_Minisymposium_Better_Scientific_Software_Fellowship/5321426" class="link-row">Improving the Reliability and Performance of Numerical Software, SIAM CSE21 Minisymposium: Better Scientific Software Fellowship</a>
| 64.535714 | 455 | 0.805755 | eng_Latn | 0.943776 |
fae6743e58659461e95702c0fc3c654006035755 | 722 | md | Markdown | _posts/2006-07-16-%e6%b2%a1%e6%9c%89%e4%b8%96%e7%95%8c%e6%9d%af%e7%9a%84%e6%97%a5%e5%ad%90%ef%bc%8c%e5%8f%aa%e5%a5%bd%e6%8b%bffifa%e6%9d%a5yy.md | kongchen/kongchen.github.io | 2746e9232546d042ce49db54ddfb4a7ba82d59ed | [
"MIT"
] | null | null | null | _posts/2006-07-16-%e6%b2%a1%e6%9c%89%e4%b8%96%e7%95%8c%e6%9d%af%e7%9a%84%e6%97%a5%e5%ad%90%ef%bc%8c%e5%8f%aa%e5%a5%bd%e6%8b%bffifa%e6%9d%a5yy.md | kongchen/kongchen.github.io | 2746e9232546d042ce49db54ddfb4a7ba82d59ed | [
"MIT"
] | null | null | null | _posts/2006-07-16-%e6%b2%a1%e6%9c%89%e4%b8%96%e7%95%8c%e6%9d%af%e7%9a%84%e6%97%a5%e5%ad%90%ef%bc%8c%e5%8f%aa%e5%a5%bd%e6%8b%bffifa%e6%9d%a5yy.md | kongchen/kongchen.github.io | 2746e9232546d042ce49db54ddfb4a7ba82d59ed | [
"MIT"
] | null | null | null | ---
layout: post
title: 没有世界杯的日子，只好拿FIFA来yy
date: 2006-07-16 22:31:00.000000000 +08:00
categories:
- 非技术
tags:
- Football
status: publish
type: post
published: true
meta:
_edit_last: '1'
author:
login: admin
email: kongchen@gmail.com
display_name: KONG
first_name: ''
last_name: ''
---
人家都说实况玩的是足球，而fifa玩的是游戏
无奈T30显卡困惑，玩不成足球，只好玩游戏
FIFA World Cup 2006有个GlobalChallenge的模块，里面全是类似于残局的比赛。比如67分钟克罗地亚1：2落后法国，然后要求你进球来个逆转；瑞典和罗马尼亚120分钟踢成0：0，让你进去踢点球。数十个这样的残局，每个残局都有自己的名字，似乎都有典故将两个队联系起来，玩起来倒是蛮有意思。不过唯一的一个有中国队的局比较郁闷，似乎是拿04年的亚洲杯决赛说事：45分钟，中国队1：0领先日本，要求你终场前不被日本反超。nnd，除掉这个都是要求玩家逆转的，只有这个是让人控制球队不被反超的。这不明摆着瞧不起中国足球么，瞧不起也就罢了，你把日本换成巴西我也认了，可又偏偏是日本，ft，EA太不知趣了......
真是怒啊，于是WorldClass难度进去，居然踢了日本个6：0。张玉宁进了4个。
中国队里，两个带☆的球员：郑智、孙继海 | 25.785714 | 314 | 0.800554 | yue_Hant | 0.616875 |
fae973352e6917cb2a836c8007fa81e6d5af0db3 | 23,114 | md | Markdown | docs/ru/adapterref/iobroker.nuki2/README.md | fincha/ioBroker.docs | 2932915142441673abfb82faae39c0e27240b778 | [
"MIT"
] | null | null | null | docs/ru/adapterref/iobroker.nuki2/README.md | fincha/ioBroker.docs | 2932915142441673abfb82faae39c0e27240b778 | [
"MIT"
] | null | null | null | docs/ru/adapterref/iobroker.nuki2/README.md | fincha/ioBroker.docs | 2932915142441673abfb82faae39c0e27240b778 | [
"MIT"
] | null | null | null | ---
translatedFrom: en
translatedWarning: Если вы хотите отредактировать этот документ, удалите поле «translationFrom», в противном случае этот документ будет снова автоматически переведен
editLink: https://github.com/ioBroker/ioBroker.docs/edit/master/docs/ru/adapterref/iobroker.nuki2/README.md
title: ioBroker.nuki2
hash: 6qE+p3V1jrJEc9IQbXpYVXxRdP8+xVmErjqgHFZd4go=
---
# IoBroker.nuki2 Этот адаптер ioBroker позволяет контролировать и контролировать [Nuki Smart Lock] (https://nuki.io/de/) с использованием [API-интерфейса Nuki Bridge (v1.8.0, 06.03.2019)] (https://developer.nuki.io/page/nuki-bridge -http-api-170/4 / # заголовок - введение) и [Nuki Web API (v1.1.1, 30.08.2018)](https://developer.nuki.io/page/nuki-web-api-111/3/).
**Оглавление**
1. [Установка] (# установка)
1. [Получить токен API] (# get-a-api-token)
2. [Функция обратного вызова] (# функция обратного вызова)
3. [Штаты] (# штаты)
2. [Умный дом / интеграция Alexa с использованием ioBroker.javascript] (# smart-home - alexa -gration-using-iobrokerjavascript)
1. [Закрывайте дверь в 10 вечера вечером] (# запирайте дверь в 10 вечера вечером)
2. [Пусть Alexa сообщит вам об изменениях блокировки] (# let-alexa-inform-you-about-lock-changes)
3. [Пусть Telegram сообщит вам об изменениях блокировки] (# let-telegram-inform-you-about-about-lock-changes)
3. [Журнал изменений] (# changelog)
4. [Кредиты] (# кредитов)
5. [Лицензия] (# лицензия)
## Монтаж
### Получить API-токен
Как получить свой токен мостов:
1. Вызвать `` `http:// <bridge_ip>: <bridge_port> / auth``` из любого браузера в вашей сети
2. Мост включает светодиод
2. Нажмите кнопку моста в течение 30 секунд
3. Результат вызова браузера должен выглядеть примерно так: `` `
{"token": "token123", "success": true} `` `
### Функция обратного вызова
Если используется функция обратного вызова, адаптер попытается автоматически установить обратный вызов на мосту Nuki при сохранении экземпляра. Соответствующие состояния Nuki ([увидеть ниже](#locks-with-nuki-bridge-api)) будут обновляться мостом Nuki, пока активирован обратный вызов.
Обратные вызовы также можно устанавливать и удалять вручную из любого браузера со следующими URL-адресами:
* установить обратный вызов: `` `http:// <bridge_ip>: <bridge_port> / callback / add? url = http% 3A% 2F% 2F <host_ip>% 3A <host_port>% 2Fnuki-api-bridge & token = <bridgeToken> `` `
* Remove Callback: `` `http:// <bridge_ip>: <bridge_port> / callback / remove? id = <callback_id> & token = <bridgeToken>` ``
* перечислить все обратные вызовы: `` `http:// <bridge_ip>: <bridge_port> / callback / list? token = <bridgeToken>` ``
### Состояния
Если вы успешно настроили ioBroker.nuki2, будут созданы следующие каналы и состояния:
#### Мосты (с Nuki Bridge API)
Мост будет создан как устройство с шаблоном имени ```bridge__<name of bridge>```. Следующие каналы / состояния будут созданы в каждом мосту:
| Канал | Государство | Описание |
|:------- |:----- |:----------- |
| обратные вызовы | - | Обратные вызовы моста |
| обратные вызовы | список | Список обратных вызовов (в формате JSON) |
| обратные вызовы ._ \ <UniqueIdOfCallback \> _ | - | Обратный звонок |
| обратные вызовы ._ \ <UniqueIdOfCallback \> _ | \ _delete | Действие для удаления обратного вызова из Bridge |
| обратные вызовы ._ \ <UniqueIdOfCallback \> _ | URL | URL обратного вызова |
| - | \ _connected | Флаг, указывающий, подключен ли мост к серверу Nuki |
| - | bridgeId | ID моста / сервера |
| - | bridgeIp | IP-адрес моста |
| - | bridgePort | Порт моста |
| - | bridgeType | Тип моста |
| - | ID оборудования | Идентификатор аппаратного моста (только аппаратный мост) |
| - | обновленный | Отметка времени последнего обновления |
| - | время работы | Время работы моста в секундах |
| - | Версия Прошивки | Версия прошивки мостов (только аппаратный мост) |
| - | versWifi | Версия прошивки модулей WiFi (только аппаратный мост) |
| - | versApp | Версия приложения моста (только программный мост) |
#### Замки (с помощью API Nuki Bridge)
Блокировка будет создана как устройство с шаблоном имени ```door__<name of door>```. Следующие каналы / состояния будут создаваться в каждой блокировке (при использовании Nuki Bridge API):
| Канал | Государство | Описание |
|:------- |:----- |:----------- |
| - | действие | Запустить действие на замке |
| - | мост | Мост Нуки |
| - | id | ID Нуки |
| - | имя | Имя Нуки |
| статус | - | Текущее состояние блокировки |
| статус | BatteryCritical ** | Состояния критического уровня заряда батареи |
| статус | lockState ** | Текущее состояние блокировки Nuki |
| статус | заблокирован ** | Индикация, если дверь заперта |
| статус | обновился ** | Отметка времени последнего обновления |
_ ** отмеченные состояния будут обновлены в действии Nuki, если обратный вызов установлен_
#### Блокировки (с помощью Nuki Web API)
Блокировка будет создана как устройство с шаблоном имени ```door__<name of door>```. Следующие каналы / состояния будут создаваться в каждой блокировке (при использовании Nuki Web API):
| Канал | Государство | Описание (возможные значения) |
|:------- |:----- |:----------------------------- |
| - | действие | Запустить действие на замке |
| - | id | ID Нуки |
| - | имя | Имя Нуки |
| статус | - | Текущее состояние блокировки |
| статус | BatteryCritical | Состояния критического уровня заряда батареи |
| статус | закрыто | Индикация, если дверь закрыта (логическое значение doorState) |
| статус | doorState | Текущее состояние дверей Нуки |
| статус | lastAction | Последнее инициированное действие |
| статус | lockState | Текущее состояние блокировки Nuki |
| статус | заблокирован | Индикация, если дверь заперта |
| статус | режим | Режим smartlock <br> `{"0": 'UNINITIALIZED', "1": 'PAIRING', "2": 'NORMAL', "3": 'UNKNOWN', "4": 'MAINTENANCE'}` |
| статус | триггер | Государственный триггер <br> `{"0": 'SYSTEM', "1": 'MANUAL', "2": 'BUTTON', "3": 'AUTOMATIC', "4": 'WEB', "5": 'APP'}` |
| статус | триггер | Государственный триггер <br> `{" 0 ": 'SYSTEM'," 1 ":" MANUAL "," 2 ":" BUTTON "," 3 ":" AUTOMATIC "," 4 ":" WEB "," 5 ":" APP "} `|
| конфиг | - | Конфигурация замка |
| конфиг | gpsLatitude | Широта |
| конфиг | gpsLongitude | Долгота |
| конфиг | autoUnlatch | True, если дверь должна быть разблокирована при разблокировке (ручка) |
| конфиг | pairingEnabled | True, если спаривание разрешено с помощью кнопки Smartlock |
| конфиг | buttonEnabled | Истина, если кнопка на Smartlock включена |
| конфиг | ledEnabled | Истина, если включен светодиод на смарт-блокировке |
| конфиг | ledBrightness | Яркость светодиода: от 0 (выключен) до 5 (максимум) |
| конфиг | fobAction1 | Действие брелка, если кнопка нажата один раз <br> `{"0": 'NONE', "1": 'UNLOCK', "2": 'LOCK', "3": 'LOCK_N_GO', "4": 'INTELLIGENT'}` |
| конфиг | fobAction2 | Действие брелка, если кнопка нажата дважды <br> `{"0": 'NONE', "1": 'UNLOCK', "2": 'LOCK', "3": 'LOCK_N_GO', "4": 'INTELLIGENT'}` |
| конфиг | fobAction3 | Действие брелка, если кнопка нажата 3 раза <br> `{"0": 'NONE', "1": 'UNLOCK', "2": 'LOCK', "3": 'LOCK_N_GO', "4": 'INTELLIGENT'}` |
| конфиг | fobAction3 | Действие брелка, если кнопка нажата 3 раза <br> `{" 0 ": 'NONE'," 1 ": 'UNLOCK'," 2 ": 'LOCK'," 3 ": 'LOCK_N_GO'," 4 ": 'INTELLIGENT'}` |
| конфиг | AdvertisingMode | Режим рекламы (экономия батареи) <br> `{"0": 'AUTOMATIC', "1": 'NORMAL', "2": 'SLOW', "3": 'SLOWEST'}` |
| конфиг | AdvertisingMode | Режим рекламы (экономия батареи) <br> `{" 0 ": 'AUTOMATIC'," 1 ": 'NORMAL'," 2 ": 'SLOW'," 3 ": 'SLOWEST'}` |
| конфиг | homekitState | Государство homekit <br> `{"0": 'UNAVAILABLE', "1": 'DISABLED', "2": 'ENABLED', "3": 'ENABLED & PAIRED'}` |
| конфиг | homekitState | Государство homekit <br> `{" 0 ": 'НЕДОСТУПЕН'," 1 ":" ОТКЛЮЧЕНО "," 2 ":" ВКЛЮЧЕНО "," 3 ":" ВКЛЮЧЕНО И СОЕДИНЕНО "}` |
| конфиг | timezoneId | ID часового пояса |
| config.advanced | - | Расширенная настройка замка |
| config.advanced | totalDegrees | Абсолютная общая позиция в градусах, которая была достигнута во время калибровки |
| config.advanced | unlockedPositionOffsetDegrees | Смещение, которое изменяет разблокированное положение |
| config.advanced | lockedPositionOffsetDegrees | Смещение, изменяющее заблокированное положение |
| config.advanced | singleLockedPositionOffsetDegrees | Смещение, изменяющее одиночную заблокированную позицию |
| config.advanced | unlockedToLockedTransitionOffsetDegrees | Смещение, изменяющее положение, в котором происходит переход из разблокированного в заблокированный |
| config.advanced | singleButtonPressAction | Желаемое действие, если кнопка нажата один раз <br> `{"0": "NO_ACTION", "1": "INTELLIGENT", "2": "UNLOCK", "3": "LOCK", "4": "UNLATCH", "5": "LOCK_N_GO", "6": "SHOW_STATUS"}` |
| config.advanced | doubleButtonPressAction | Желаемое действие, если кнопка нажата дважды <br> `{"0": "NO_ACTION", "1": "INTELLIGENT", "2": "UNLOCK", "3": "LOCK", "4": "UNLATCH", "5": "LOCK_N_GO", "6": "SHOW_STATUS"}` |
| config.advanced | doubleButtonPressAction | Желаемое действие, если кнопка нажата дважды <br> `{" 0 ":" NO_ACTION "," 1 ":" INTELLIGENT "," 2 ":" UNLOCK "," 3 ":" LOCK "," 4 ":" UNLATCH "," 5 ":" LOCK_N_GO ", "6": "SHOW_STATUS"} `|
| config.advanced | batteryType | Тип батарей, присутствующих в умном замке <br> `{"0": 'ALKALI', "1": 'ACCUMULATOR', "2": 'LITHIUM'}` |
| config.advanced | batteryType | Тип батарей, присутствующих в умном замке <br> `{" 0 ": 'ALKALI'," 1 ": 'ACCUMULATOR'," 2 ": 'LITHIUM'}` |
| config.advanced | automaticBatteryTypeDetection | Флаг, указывающий, включено ли автоматическое определение типа батареи |
| config.advanced | unlatchDuration | Продолжительность в секундах для удержания защелки в открытом положении |
| config.advanced | autoLockTimeout | Секунды, пока умная блокировка не разблокируется после того, как она была разблокирована. Нет автоматической блокировки, если значение равно 0. |
| пользователи | - | Пользователи замка |
| users._userName_ | - | Пользователь _userName_ |
| users._userName_ | тип | Тип авторизации <br> `{"0": 'APP', "1": 'BRIDGE', "2": 'FOB', "3": 'KEYPAD', "13": 'KEYPAD CODE', "14": 'Z-KEY', "15": 'VIRTUAL'}` |
| users._userName_ | тип | Тип авторизации <br> `{" 0 ": 'APP'," 1 ":" МОСТ "," 2 ":" FOB "," 3 ":" КЛАВИАТУРА "," 13 ":" КОД КЛАВИАТУРЫ "," 14 ":" Z- KEY ', "15":' VIRTUAL '} `|
| users._userName_ | id | Уникальный идентификатор пользователя |
| users._userName_ | authId | Идентификатор авторизации Smartlock |
| users._userName_ | включен | True, если пользователь включен |
| users._userName_ | RemoteAllowed | Истинно, если авторизация имеет удаленный доступ |
| users._userName_ | lockCount | Количество блокировок |
| users._userName_ | dateLastActive | Последняя активная дата |
| users._userName_ | dateCreated | Дата создания |
| users._userName_ | dateUpdated | Дата обновления |
| users._userName_ | allowFromDate | Разрешено с даты |
| users._userName_ | allowWeekDays | Разрешенные будни <br> `{64: 'Monday', 32: 'Tuesday', 16: 'Wednesday', 8: 'Thursday', 4: 'Friday', 2: 'Saturday', 1: 'Sunday'}` |
| users._userName_ | allowWeekDays | Разрешенные будни <br> `{64:« Понедельник », 32:« Вторник », 16:« Среда », 8:« Четверг », 4:« Пятница », 2:« Суббота », 1:« Воскресенье »}` |
| users._userName_ | allowFromTime | Разрешенное время (в минутах с полуночи) |
| users._userName_ | allowUntilTime | Разрешено до времени (в минутах от полуночи) |
## Умный дом / интеграция с Alexa с использованием ioBroker.javascript
Некоторые примеры возможной интеграции в вашем умном доме.
### Закрывать дверь в 10 вечера вечером
```javascript
var states = {
"0": "uncalibrated",
"1": "locked",
"2": "unlocking",
"3": "unlocked",
"4": "locking",
"5": "unlatched",
"6": "unlocked (lock n go)",
"7": "unlatching",
"254": "motor blocked",
"255": "undefined"
};
schedule('0 22 * * *', function()
{
var status = (getState('nuki2.0.door__home_door.status.lockState').val);
var msg = 'Main Door door is ' + (states[status]) + '. ';
if (status == '3')
{
setState('nuki2.0.door__home_door.action', 2);
msg += 'Locking door..'
}
else
msg += 'No action taken.'
log(msg, {m: 'Nuki', o: ['msg']});
});
```
__Заменить `nuki2.0.door__home_door.status.lockState` на lockState вашей блокировки! __ Вы также можете настроить сообщение через `msg`.
### Пусть Alexa сообщит вам об изменениях блокировки
Для этого требуется адаптер ioBroker ioBroker.alexa2 (https://github.com/Apollon77/ioBroker.alexa2).
Чтобы использовать голосовой вывод Alexa, мы определяем функцию ```say```. Поместите следующую функцию в скрипт в «глобальную» папку ioBroker.javascript. ВАЖНО: замените #YOUR ALEXA ID # (также замените #) своим Alexa ID. Вы можете найти Alexa ID в дереве объектов ioBroker ```alexa2.0.Echo-Devices```.
```javascript
/**
* Say something with Alexa.
*
* @param {string} message Message to say
* @param {string|array} alexas Alexa Device to say the voice message
* @return void
*
*/
function say(message, alexas = '#YOUR ALEXA ID#') // use alexas = ['#YOUR ALEXA ID 1#', '#YOUR ALEXA ID 2#'] for default voice output from multiple devices (also replace #)
{
alexas = typeof alexas === 'string' ? [alexas] : alexas;
alexas.forEach(function(alexa)
{
setState('alexa2.0.Echo-Devices.' + alexa + '.Commands.speak', message);
});
}
```
Вы можете использовать эту функцию в ioBroker.javascript, чтобы произнести фразу, используя Alexa ```say('Hello World')``` или ```say('Hello World', ['#YOUR ALEXA ID 1#', '#YOUR ALEXA ID 2#'])``` для голосового вывода с нескольких устройств.
Создайте сценарий в «общей» папке ioBroker.javascript и добавьте в него следующего слушателя. ВАЖНО: Замените #LOCK STATE ID # (также замените #) на состояние, содержащее состояние блокировки (например, ```nuki2.0.door__home_door.status.lockState```):
```javascript
const DOOR_STATES = {
"0": "uncalibrated",
"1": "locked",
"2": "unlocking",
"3": "unlocked",
"4": "locking",
"5": "unlatched",
"6": "unlocked (lock n go)",
"7": "unlatching",
"254": "motor blocked",
"255": "undefined"
};
/*
* LISTEN TO CHANGES TO LOCK STATE
*
*/
on({id: '#LOCK STATE ID#', change: 'any'}, function(obj)
{
if (obj !== undefined && obj.state !== undefined)
say('Door is ' + DOOR_STATES[obj.state.val] + '!')
});
```
### Пусть Telegram сообщит вам об изменениях блокировки
Для этого требуется адаптер ioBroker ioBroker.telegram (https://github.com/iobroker-community-adapters/ioBroker.telegram).
Чтобы использовать вывод сообщений Telegram, мы определяем функцию ```msg``` и ```messenger```. Поместите следующую функцию в скрипт в «глобальную» папку ioBroker.javascript:
```javascript
/**
* Send something via telegram.
*
* @param {string} message Message to print
* @param {string|array} receiver Users to send the message to
* @return void
*
*/
function msg(message, receiver = 'ALL')
{
if (receiver == 'ALL')
messenger(message);
else
{
receiver = typeof receiver == 'string' ? [receiver] : receiver;
receiver.forEach(function(user)
{
messenger(message, user);
});
}
}
```
```javascript
/**
* Sends a message / text.
*
* @param {string} content Message to send
* @param {string} user (optional) Specific user to send the message to (defaults to all registered users)
* @return void
*
*/
function messenger(content, user = '')
{
var config = {
text: content,
parse_mode: 'HTML',
reply_markup: {
resize_keyboard: true,
one_time_keyboard: false
}
};
sendTo('telegram', user ? Object.assign({user: user}, config) : config);
}
```
Вы можете использовать эту функцию в ioBroker.javascript для отправки чего-либо в Telegram через ```msg('Hello World')``` (всем пользователям) или ```msg('Hello World', 'Zefau')``` (конкретным пользователям).
Создайте сценарий в «общей» папке ioBroker.javascript и добавьте в него следующего слушателя. ВАЖНО: Замените #LOCK STATE ID # (также замените #) на состояние, содержащее состояние блокировки (например, ```nuki2.0.door__home_door.status.lockState```):
```javascript
const DOOR_STATES = {
"0": "uncalibrated",
"1": "locked",
"2": "unlocking",
"3": "unlocked",
"4": "locking",
"5": "unlatched",
"6": "unlocked (lock n go)",
"7": "unlatching",
"254": "motor blocked",
"255": "undefined"
};
/*
* LISTEN TO CHANGES TO LOCK STATE
*
*/
on({id: '#LOCK STATE ID#', change: 'any'}, function(obj)
{
if (obj !== undefined && obj.state !== undefined)
msg('Door is ' + DOOR_STATES[obj.state.val] + '!')
});
```
ПРИМЕЧАНИЕ. Если вы используете как скрипт Alexa, так и скрипт Telegram, вы можете определить только одного слушателя для обоих действий:
```javascript
const DOOR_STATES = {
"0": "uncalibrated",
"1": "locked",
"2": "unlocking",
"3": "unlocked",
"4": "locking",
"5": "unlatched",
"6": "unlocked (lock n go)",
"7": "unlatching",
"254": "motor blocked",
"255": "undefined"
};
/*
* LISTEN TO CHANGES TO LOCK STATE
*
*/
on({id: '#LOCK STATE ID#', change: 'any'}, function(obj)
{
if (obj !== undefined && obj.state !== undefined)
{
say('Door is ' + DOOR_STATES[obj.state.val] + '!')
msg('Door is ' + DOOR_STATES[obj.state.val] + '!')
}
});
```
## Кредиты
Благодаря [@ Mik13] (https://github.com/Mik13) для [реализации API Nuki Bridge](https://github.com/Mik13/nuki-bridge-api#nuki-bridge-api).
Иконки, сделанные <a href="https://www.flaticon.com/authors/smashicons" title="Smashicons">Smashicons</a> ([Essential Set] (https://www.flaticon.com/packs/essential-set-2)) и <a href="https://www.freepik.com/" title="Freepik">Freepik</a> ([Двери](https://www.flaticon.com/packs/doors)) с <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a> , лицензированы <a href="http://creativecommons.org/licenses/by/3.0/" title="Creative Commons BY 3.0" target="_blank">CC 3.0 BY</a>
## Changelog
### 1.0.0 (2019-05-xx) [IN DEVELOPMENT]
- (Zefau) support for hashed token for hardware bridges (see https://developer.nuki.io/page/nuki-bridge-http-api-180/4/#heading--token) in the [nuki-bridge-api](https://github.com/Mik13/nuki-bridge-api/pull/9)
- (Zefau) bump to stable release
### 0.9.12 (2019-05-16)
- (Zefau) fixed an issue causing the same callback set multiple times (see [#9](https://github.com/Zefau/ioBroker.nuki2/issues/9#issuecomment-493148883))
### 0.9.11 (2019-05-13)
- (Zefau) added info-message when setting refresh rate to less than 10 seconds
### 0.9.10 (2019-05-10)
- (Zefau) added states to reflect current callbacks set on the Nuki Bridge as well as action to delete the callbacks
- (Zefau) updated dependency of `nuki-bridge-api` to v1.5.0
### 0.9.9 (2019-05-05)
- (Zefau) updated dependency of `nuki-bridge-api` to v1.4.0
### 0.9.8 (2019-05-05)
Thanks to [@systemofapwne](https://github.com/systemofapwne) for testing and identifying quite a few bugs.
- (Zefau) added delay between requests / actions applied on the Nuki Bridge (to prevent overload, see [#9](https://github.com/Zefau/ioBroker.nuki2/issues/9))
- (Zefau) fixed an issue causing the adapter to crash when polling was enabled, but Web API is not used (see [#10](https://github.com/Zefau/ioBroker.nuki2/issues/10))
### 0.9.7 (2019-05-05)
- (Zefau) added verification if callback URL is already added on Nuki Bridge (see [#9](https://github.com/Zefau/ioBroker.nuki2/issues/9))
### 0.9.6 (2019-05-03)
- (Zefau) added Web Adapter as dependency
- (Zefau) add warning when opening web / log view but Nuki Web API has not been setup
- (Zefau) removed empty folders when Nuki Web API has not been setup
- (Zefau) fixed an issue with Webhook when time for refreshing all settings was set ([#9](https://github.com/Zefau/ioBroker.nuki2/issues/9))
### 0.9.4 / 0.9.5 (2019-03-22)
- (Zefau) Useless versions to fix incorrect configuration in `io-package.json`
### 0.9.3 (2019-03-22)
- (Zefau) Limited log retrieval to 1000 entries
### 0.9.2 (2019-02-11)
- (Zefau) Updated dependency
### 0.9.1 (2019-02-10)
- (Zefau) Added Web Interface to view logs
### 0.9.0 (2019-02-09)
- (Zefau) Using both Bridge API and Web API
- (Zefau) Support for multiple bridges
- (Zefau) Support for discovery within admin panel
- (Zefau) Additional states for bridges and better separation between software / hardware bridge
- retrieve the basic and advanced configuration from your lock
- retrieve all users having access to your lock
## License
The MIT License (MIT)
Copyright (c) 2019 Zefau <zefau@mailbox.org>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE. | 52.058559 | 493 | 0.685299 | rus_Cyrl | 0.181791 |
fae98ef536eea85962d5014089a9c4258302d3d5 | 817 | md | Markdown | docs/visual-basic/misc/bc2006.md | zabereznikova/docs.de-de | 5f18370cd709e5f6208aaf5cf371f161df422563 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc2006.md | zabereznikova/docs.de-de | 5f18370cd709e5f6208aaf5cf371f161df422563 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc2006.md | zabereznikova/docs.de-de | 5f18370cd709e5f6208aaf5cf371f161df422563 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Option "<optionname>" erfordert ""<argument>
ms.date: 07/20/2015
f1_keywords:
- vbc2006
- bc2006
helpviewer_keywords:
- BC2006
ms.assetid: 36d7d25d-8da4-4b06-847f-f59b1d681224
ms.openlocfilehash: 71e5ae7b6fa640796645708a15575000a5739a8b
ms.sourcegitcommit: bf5c5850654187705bc94cc40ebfb62fe346ab02
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 09/23/2020
ms.locfileid: "91082993"
---
# <a name="option-optionname-requires-argument"></a>Option "\<optionname>" erfordert ""\<argument>
Ein erforderliches Argument wurde ausgelassen.
**Fehler-ID:** BC2006
## <a name="to-correct-this-error"></a>So beheben Sie diesen Fehler
- Geben Sie das fehlende Argument an.
## <a name="see-also"></a>Siehe auch
- [Fehlertypen](../programming-guide/language-features/error-types.md)
| 27.233333 | 98 | 0.75153 | deu_Latn | 0.392442 |
faea4241721c1bca227f24c78555d779090088e5 | 1,457 | md | Markdown | README.md | standardplatform/standardplatform | ccb1688e21e0e5a40fc6080792e02b8ccc520f13 | [
"CC0-1.0"
] | 1 | 2020-12-11T18:49:20.000Z | 2020-12-11T18:49:20.000Z | README.md | clusterplatform/clusterplatform | ccb1688e21e0e5a40fc6080792e02b8ccc520f13 | [
"CC0-1.0"
] | null | null | null | README.md | clusterplatform/clusterplatform | ccb1688e21e0e5a40fc6080792e02b8ccc520f13 | [
"CC0-1.0"
] | null | null | null | # Cluster Platform
The Futurist's Approach to System Design.
## Features
See [Home](./packages/site/src/index.md).
## Licenses
These licences apply, unless specified otherwise, to all packages of the Cluster Platform.
### Code
[](./LICENSE.md)
Cluster Platform (C) 2014-2019 Felix Pojtinger
SPDX-License-Identifier: AGPL-3.0
This program is free software: you can redistribute it and/or modify it under the terms of the GNU/Linux Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU/Linux Affero General Public License for more details.
You should have received a copy of the GNU/Linux Affero General Public License along with this program. If not, see [https://www.gnu.org/licenses/](https://www.gnu.org/licenses/).
### Media
[](./LICENSE_MEDIA.md)
Cluster Platform (C) 2014-2019 Felix Pojtinger
SPDX-License-Identifier: CC-BY-SA-4.0
This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/).
| 38.342105 | 252 | 0.765957 | eng_Latn | 0.871624 |
faea794e144a614a615732de13510ae6c2c187ed | 2,857 | md | Markdown | docs/wrappers/peer_chaincode_preamble.md | tianyaliu/fabric | 70ace58ae902318489894a5cd7b4e6ecea00bb5e | [
"Apache-2.0"
] | 15,003 | 2016-04-02T22:48:14.000Z | 2022-03-31T23:25:24.000Z | docs/wrappers/peer_chaincode_preamble.md | tianyaliu/fabric | 70ace58ae902318489894a5cd7b4e6ecea00bb5e | [
"Apache-2.0"
] | 3,187 | 2016-04-02T20:48:22.000Z | 2022-03-31T16:11:52.000Z | docs/wrappers/peer_chaincode_preamble.md | tianyaliu/fabric | 70ace58ae902318489894a5cd7b4e6ecea00bb5e | [
"Apache-2.0"
] | 10,753 | 2016-04-03T14:17:07.000Z | 2022-03-31T12:19:56.000Z | # peer chaincode
The `peer chaincode` command allows administrators to perform chaincode
related operations on a peer, such as installing, instantiating, invoking,
packaging, querying, and upgrading chaincode.
## Syntax
The `peer chaincode` command has the following subcommands:
* install
* instantiate
* invoke
* list
* package
* query
* signpackage
* upgrade
The different subcommand options (install, instantiate...) relate to the
different chaincode operations that are relevant to a peer. For example, use the
`peer chaincode install` subcommand option to install a chaincode on a peer, or
the `peer chaincode query` subcommand option to query a chaincode for the
current value on a peer's ledger.
Some subcommands take flag `--ctor`, of which the value must be a JSON string
that has either key 'Args' or 'Function' and 'Args'. These keys are
case-insensitive.
If the JSON string only has the Args key, the key value is an array, where the
first array element is the target function to call, and the subsequent elements
are arguments of the function. If the JSON string has both 'Function' and
'Args', the value of Function is the target function to call, and the value of
Args is an array of arguments of the function. For instance,
`{"Args":["GetAllAssets"]}` is equivalent to
`{"Function":"GetAllAssets", "Args":[]}`.
Each peer chaincode subcommand is described together with its options in its own
section in this topic.
## Flags
Each `peer chaincode` subcommand has both a set of flags specific to an
individual subcommand, as well as a set of global flags that relate to all
`peer chaincode` subcommands. Not all subcommands would use these flags.
For instance, the `query` subcommand does not need the `--orderer` flag.
The individual flags are described with the relevant subcommand. The global
flags are
* `--cafile <string>`
Path to file containing PEM-encoded trusted certificate(s) for the ordering
endpoint
* `--certfile <string>`
Path to file containing PEM-encoded X509 public key to use for mutual TLS
communication with the orderer endpoint
* `--keyfile <string>`
Path to file containing PEM-encoded private key to use for mutual TLS
communication with the orderer endpoint
* `-o` or `--orderer <string>`
Ordering service endpoint specified as `<hostname or IP address>:<port>`
* `--ordererTLSHostnameOverride <string>`
The hostname override to use when validating the TLS connection to the orderer
* `--tls`
Use TLS when communicating with the orderer endpoint
* `--transient <string>`
Transient map of arguments in JSON encoding
Flags of type stringArray are to be repeated rather than concatenating their
values. For example, you will use `--peerAddresses localhost:9051
--peerAddresses localhost:7051` rather than `--peerAddresses "localhost:9051
localhost:7051"`.
| 33.22093 | 80 | 0.763738 | eng_Latn | 0.998621 |
faeae159d9e47ff8d0921bda136c8a31e0eb3b49 | 161 | md | Markdown | README.md | Hulkt1m0Hom8r3/npm_init | 5d806bbb5e79373a4a58e740c855f00d27647a9a | [
"MIT"
] | null | null | null | README.md | Hulkt1m0Hom8r3/npm_init | 5d806bbb5e79373a4a58e740c855f00d27647a9a | [
"MIT"
] | null | null | null | README.md | Hulkt1m0Hom8r3/npm_init | 5d806bbb5e79373a4a58e740c855f00d27647a9a | [
"MIT"
] | null | null | null | # npm_init
a BASH file that automates everything in opening a node.js project<br>
inspired by
https://philna.sh/blog/2019/01/10/how-to-start-a-node-js-project/
| 32.2 | 70 | 0.770186 | eng_Latn | 0.752025 |
faeae83721d0c26fcc04e51b6ff0e02426accf59 | 1,881 | md | Markdown | README.md | YitingLiu97/End-to-End-In-Game-Style-Transfer-Tutorial | b94d97d422d63ddf805f77d399958818d80f45ac | [
"MIT"
] | null | null | null | README.md | YitingLiu97/End-to-End-In-Game-Style-Transfer-Tutorial | b94d97d422d63ddf805f77d399958818d80f45ac | [
"MIT"
] | null | null | null | README.md | YitingLiu97/End-to-End-In-Game-Style-Transfer-Tutorial | b94d97d422d63ddf805f77d399958818d80f45ac | [
"MIT"
] | null | null | null | # End-to-End-In-Game-Style-Transfer-Tutorial
**Note:** Complete the following steps before running the project for the first time.
1. Open the Kinematica folder in the Assets section.
2. Double-click on the `Unit` asset.
3. Click `Build` in the pop-up window.
4. Close the pop-up window once the build is complete.
5. Back in the `Assets` section, open the `Biped` scene in the `Scenes` folder.
The project should run normally now. However, there might be some stuttering the first time it is run.
## Tutorial Links
[Part 1](https://christianjmills.com/End-To-End-In-Game-Style-Transfer-Tutorial-1/): This tutorial series covers how to train your own style transfer model with PyTorch and implement it in Unity using the Barracuda library.
[Part 1.5](https://christianjmills.com/End-To-End-In-Game-Style-Transfer-Tutorial-1-5/): This post covers how to use the Unity Recorder tool to generate additional training data for our style transfer model.
[Part 2](https://christianjmills.com/End-To-End-In-Game-Style-Transfer-Tutorial-2/): This post covers how to train an artistic style transfer model with PyTorch in Google Colab.
[Part 3](https://christianjmills.com/End-To-End-In-Game-Style-Transfer-Tutorial-3/): This post covers how implement the style transfer model in Unity with the Barracuda library.
## Follow Ups
### Targeted In-Game Style Transfer
* [GitHub Branch](https://github.com/cj-mills/End-to-End-In-Game-Style-Transfer-Tutorial-Intel/blob/targeted-style-transfer/README.md)
* [Tutorial](https://christianjmills.com/Targeted-In-Game-Style-Transfer-Tutorial/)
*
### Barracuda Style Transfer HDRP - 12/7/21
* [GitHub Repository](https://github.com/cj-mills/Barracuda-Style-Transfer-HDRP)
| 62.7 | 223 | 0.774056 | eng_Latn | 0.502921 |
faebb7a52eb678aff567b21a31bf9f9c8dc9fff8 | 768 | md | Markdown | 2013/CVE-2013-1642.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 2,340 | 2022-02-10T21:04:40.000Z | 2022-03-31T14:42:58.000Z | 2013/CVE-2013-1642.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 19 | 2022-02-11T16:06:53.000Z | 2022-03-11T10:44:27.000Z | 2013/CVE-2013-1642.md | justinforbes/cve | 375c65312f55c34fc1a4858381315fe9431b0f16 | [
"MIT"
] | 280 | 2022-02-10T19:58:58.000Z | 2022-03-26T11:13:05.000Z | ### [CVE-2013-1642](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-1642)
### Description
Multiple cross-site scripting (XSS) vulnerabilities in QuiXplorer before 2.5.5 allow remote attackers to inject arbitrary web script or HTML via the (1) dir, (2) item, (3) order, (4) searchitem, (5) selitems[], or (6) srt parameter to index.php or (7) the QUERY_STRING to index.php.
### POC
#### Reference
- https://www3.trustwave.com/spiderlabs/advisories/TWSL2013-030.txt
#### Github
No PoCs found on GitHub currently.
| 42.666667 | 282 | 0.734375 | eng_Latn | 0.362146 |
faebf87351884e2668ad64babe07ec73ba4cf054 | 1,658 | md | Markdown | PROJECT-GOVERNING-BOARD.md | eea-oasis/oasis-open-project | 799fe463211484e4d818d7f8ae31e951314fd1ea | [
"Apache-2.0"
] | 4 | 2021-07-26T23:41:40.000Z | 2022-01-10T19:58:40.000Z | PROJECT-GOVERNING-BOARD.md | eea-oasis/oasis-open-project | 799fe463211484e4d818d7f8ae31e951314fd1ea | [
"Apache-2.0"
] | 5 | 2021-07-01T14:33:34.000Z | 2022-03-11T11:47:58.000Z | PROJECT-GOVERNING-BOARD.md | eea-oasis/oasis-open-project | 799fe463211484e4d818d7f8ae31e951314fd1ea | [
"Apache-2.0"
] | 2 | 2021-12-18T03:19:49.000Z | 2022-03-27T09:27:33.000Z | <img src="artwork/eea-oneline.png" width="400">
# EEA Community Projects Governing Board (PGB)
The Project Governing Board sets overall strategic direction for the EEA Community Projects and formally approves released work products.
PGB members include representatives of [EEA Community Projects sponsor organizations]() and representatives from the community at-large who serve on the Technical Steering Committee:
* Daniel Burnett, Enterprise Ethereum Alliance ([@burnburn](https://github.com/burnburn))
* Tas Dienes, Ethereum Foundation ([@tasdienes](https://github.com/tasdienes))
* Dan Kochis, Chainlink ([@dk21dk](https://github.com/dk21dk))
* Tracy Kuhrt, Accenture ([@tkuhrt](https://github.com/tkuhrt))
* Chaals Nevile, ConsenSys ([@chaals](https://github.com/chaals))
* Antonio Sabado, Nethermind ([@asabado](https://github.com/asabado))
* Stefan Schmidt, Unibright ([@stefschmidt](https://github.com/stefschmidt))
* Kyle Thomas, Provide ([@kthomas](https://github.com/kthomas))
* John Wolpert, Baseline TSC Chair ([@humbitious](https://github.com/humbitious))
* James Canterbury, Ernst & Young LLP ([@jamescbury](https://github.com/jamescbury))
* Noam Eppel, Morpheus.Network ([@MorpheusNetwork](https://github.com/MorpheusNetwork))
* Melanie Marsollier, Splunk ([@Mel-Marsollier](https://github.com/Mel-Marsollier))
* Olumide Akinwande, Montech ([@MontechStudiosINC](https://github.com/MontechStudiosINC))
* Matt Hepler, Arca
* Anton Mozgovoy, Mover
* Marcus Krug, SAP
For information on joining sponsoring these projects or joining the governing board, please contact [communications@oasis-open.org](mailto:communications@oasis-open.org).
| 61.407407 | 182 | 0.768396 | eng_Latn | 0.277909 |
faec4bcbabd98ee824bc2c52cbadcc09bc61cd09 | 224 | md | Markdown | pages/prodNuapay/np_secjwsgenerator.md | tommycurnyn/developer-docs | c233952028c19c55934c30f25e6b175d5ea36682 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | pages/prodNuapay/np_secjwsgenerator.md | tommycurnyn/developer-docs | c233952028c19c55934c30f25e6b175d5ea36682 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | pages/prodNuapay/np_secjwsgenerator.md | tommycurnyn/developer-docs | c233952028c19c55934c30f25e6b175d5ea36682 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | ---
title: JWS Generator
keywords: JWS Generator Utility
summary: "JWS Generator Utility"
sidebar: np_sidebar
permalink: np_secjwsgenerator.html
folder: prodNuapay
toc: false
---
<p>TO BE ADDED</p>
{% include links.html %} | 17.230769 | 34 | 0.754464 | kor_Hang | 0.39185 |
faec5835b544394e6c1e254960ffc02bb45afd4c | 1,361 | md | Markdown | content/ats/index.md | MansystemsCorp/mendix-docs-backup-11-Feb-2019 | fbc19af4e8d60fc94e9f861310cf808699329434 | [
"CC-BY-4.0"
] | null | null | null | content/ats/index.md | MansystemsCorp/mendix-docs-backup-11-Feb-2019 | fbc19af4e8d60fc94e9f861310cf808699329434 | [
"CC-BY-4.0"
] | null | null | null | content/ats/index.md | MansystemsCorp/mendix-docs-backup-11-Feb-2019 | fbc19af4e8d60fc94e9f861310cf808699329434 | [
"CC-BY-4.0"
] | null | null | null | ---
title: "ATS"
---
The Mendix Application Test Suite (ATS) is a suite of tools for embedding (automated) testing in your application life cycle. These tools are built by Mansystems in Mendix on top of Selenium.
ATS provides a powerful solution for automation of not only your functional and regression tests, but also non-functional tests like availability, security, and performance testing. Furthermore, with functions like test case recording and data-driven testing, it provides you with everything you need to make testing your Mendix apps quick, easy, and versatile.
A small investment in setting up ATS, which is very easy to learn, will save you a lot of (re)testing time in the long run. This will help your team and its stakeholders to have the right insights into the quality off your apps at any time and at the press of a button.
All of the available documents to help you use ATS are located in this space. Please select a category to specify your search:
* [General](general)
* [ATS 1 Reference Guide](refguide/rg-version-1/rg-version-1)
* [ATS 2 Reference Guide](refguide/rg-version-2/rg-version-2)
* [ATS 1 How-to's](howtos/ht-version-1/ht-version-1)
* [ATS 2 How-to's](howtos/ht-version-2/ht-version-2)
* [ATS 1 Best Practices](bestpractices/bp-version-1/bp-version-1)
* [ATS 2 Best Practices](bestpractices/bp-version-2/bp-version-2)
| 68.05 | 361 | 0.772226 | eng_Latn | 0.994969 |
faec9600092fe34877dba86402bea5171178469f | 14,201 | md | Markdown | Cosmere/Aviar.md | Malthemester/CoppermindScraper | 1a1d70a6a1e0aff2d8e8cf5d124da3c16c061a43 | [
"MIT"
] | null | null | null | Cosmere/Aviar.md | Malthemester/CoppermindScraper | 1a1d70a6a1e0aff2d8e8cf5d124da3c16c061a43 | [
"MIT"
] | null | null | null | Cosmere/Aviar.md | Malthemester/CoppermindScraper | 1a1d70a6a1e0aff2d8e8cf5d124da3c16c061a43 | [
"MIT"
] | null | null | null | |**Aviar**|
|-|-|
|by Matthew Johnson |
|**Abilities**|Aviar talents|
|**World**|[[First of the Sun\|First of the Sun]]|
|**Universe**|[[Cosmere\|Cosmere]]|
|**Featured In**|*Sixth of the Dusk, The Stormlight Archive[1]*|
>“*The world is changing, Sixth of the Dusk. The people of the mainland grow hungry for Aviar companions; things once restricted to the very wealthy are within the reach of ordinary people. We've learned so much, yet the Aviar are still an enigma.*”
\-Vathi[2]
**Aviar** are birds that have gained magical powers, or "talents", on the island of [[Patji (island)\|Patji]] on [[First of the Sun\|First of the Sun]]. They are capable of sharing their powers with humans. Aviar were long thought to be exclusively native to the [[Pantheon\|Pantheon]] archipelago, but other birds can become Aviar if they visit the island and ingest the fruit of [[Patji's Finger\|Patji's Fingers]].
## Contents
1 Appearance and Anatomy
2 Behavior
2.1 Nature of Abilities
2.2 Abilities
2.2.1 Bonds
2.2.2 Cognitive Concealment
2.2.3 Future Sight
2.2.4 Other Abilities
3 Ecology
4 Domestication
5 History
6 Known Varieties
7 Notable Aviar
8 Trivia
9 Notes
## Appearance and Anatomy
by Dragontrill [[Gereh\|Gereh]] with his [[Gereh's Aviar\|Aviar]]
Most Aviar are relatively large birds, approximately three fists tall. Some species may be smaller or larger. Their appearance varies between species, with colors including red, green, black, blue, and white, sometimes in combination. Some Aviar have sharp raptor-like talons and beaks. Juvenile Aviar are barely able to fly, but healthy adults are typically good fliers unless their wings are clipped.
## Behavior
Aviar are more intelligent than ordinary animals. Wild Aviar exhibit behaviors similar to other birds. They live in flocks, roost in trees, and build nests where they lay eggs and raise their young. Their mating behavior somehow involves long single feathers known as "mating plumes", which are usually found near nests. Although their powers give them some protection from predators, they will quickly flee if startled. They are known to eat fresh fruit, and will also eat seeds, dried fruit, and fish.
They display distinct personalities; for example, [[Kokerlii\|Kokerlii]] is oblivious and happy, while [[Sak\|Sak]] is far more reserved. They seem to understand some human speech, as they can respond to commands or other sounds from their master. They can be trained to perform specific behaviors, such as returning to their master if they whistle, or even to attack other animals.
### Nature of Abilities
Juvenile birds can gain magical powers, or "talents", by consuming special worms that live on the island of [[Patji (island)\|Patji]]. Aviar from the various islands of the [[Pantheon\|Pantheon]] migrate to Patji to gain their talent. The worms infest fruit that falls from [[Patji's Finger\|Patji's Finger]] trees that grow next to [[Patji's Eye\|Patji's Eye]]; the birds then consume the worms when they eat the fruit. Birds that are not native to the Pantheon usually do not develop these unique powers. However, [[Sixth of the Dusk (character)\|Sixth of the Dusk]] raised a non-native bird on the isles, [[Sak\|Sak]], and found that she also developed a unique talent.
>“*The Aviar are special. Everyone knows the separate breeds and what they do. Why assume that a fish would learn to breathe air, if raised on land? Why assume a non-Aviar would become one if raised on Patji...*”
\-Vathi, after learning of Sak's talent[2]
The abilities of the Aviar stem from a symbiosis with the worms that they eat. The worms are [[Investiture\|Invested]]; once eaten, the worms grant the birds access to certain magical powers depending on their species. The Aviar can then serve as an intermediary to allow humans to use or benefit from their powers.
Aviar do not seem to have to continue eating worms to allow their powers to function, as they are often exported from the Pantheon to the distant mainland. Trappers have established that the birds must be juveniles to gain talents; it is not clear what would happen if an adult bird ate the worms. Aviar can be transported to other planets in the [[Cosmere\|cosmere]], although this is difficult and very rare. It is unclear if taking Aviar to other worlds has an effect on their abilities. However, individuals that are not native to [[First of the Sun\|First of the Sun]] are able to bond Aviar, even individuals that have access to other manifestations of Investiture such as [[Feruchemy\|Feruchemy]].
A human cannot eat the worms or an Aviar in order to gain powers, as the symbiosis is specific to the worms and the birds. It would be theoretically possible for other organisms to evolve a similar symbiosis, but it would take many generations. A [[Kandra\|kandra]] in the form of an Aviar would not be able to gain their powers, even if they ate the worms. It is possible to steal an Aviar talent through [[Hemalurgy\|Hemalurgy]], but it would be very difficult to do so.
### Abilities
The power obtained by Aviar is different for each species of bird. Many Aviar have abilities related to the [[Cognitive Realm\|Cognitive Realm]], but [[Spiritual Realm\|Spiritual]] and even [[Physical Realm\|Physical]] powers also exist. Some abilities work passively, while others must be intentionally activated by the Aviar, sometimes at the request of a bonded person. At least one unknown Aviar ability could assist with "navigation". Aviar abilities are usually very reliable, although they were disrupted by an unusual device that was given to the [[Northern Interests Trading Company\|Northern Interests Trading Company]] by the [[Ones Above\|Ones Above]].
Aviar are able to share their powers with humans through a Spiritual [[Connection\|Connection]] similar to the [[Nahel bond\|Nahel bond]]. This bond is not as powerful as the Nahel bond, but because of that it can be shifted between people at its owner's will. The bond includes a mental connection; Dusk refers to Sak "sending" him her visions. Aviar are also able to sense the location of the person they have bonded with. The nature of the bond allows some Aviar to share their talents with people other than their usual master. Most people bond a single Aviar, but some [[Trapper\|trappers]] have bonded at least three Aviar at the same time.
>“*It was fortunate [Kokerlii's] breed was so mind-invisible, even deathants would consider him no more edible than a piece of bark.*”
\-Dusk[2]
[[Kokerlii\|Kokerlii]] and [[Mirris\|Mirris]] have a Cognitive ability to conceal their mental activity and those of others around them. This ability seems to work passively, as Dusk never needs to ask Kokerlii to use it or wait for him to do so. Some version of this ability appears to be relatively common, as flocks of wild Aviar are able to conceal themselves from mind-sensing predators such as [[Nightmaw\|nightmaws]]. [[Krell (cosmere)\|Krell]] are known to sleep near Aviar roosts in order to take advantage of the mental shield that they provide.
Additionally, Aviar Cognitive concealment impedes the ability of others to sense the use of Investiture, much like an Allomantic [[Copper\|coppercloud]]. They would be able to block an [[Awakener\|Awakener's]] [[Heightening\|life sense]] and interfere with other methods of detecting Investiture, such as Allomantic [[Bronze\|bronze]] and secretspren.
[[Sak\|Sak's]] ability allows her to glimpse into the future, using the property of [[Fortune\|Fortune]] to glimpse the [[Spiritual Realm\|Spiritual Realm]]. She is able to see potential deaths of a person, and manifest these potential deaths as visions of corpses wherever they could be killed. The corpses are only visible to those with whom Sak chooses to share her talent. If the danger passes, the pertinent corpse will disappear. Sak is able to turn this ability on or off at will. She is even able to show Vathi the visions at Dusk's request. Sak, whose species is not native to the Pantheon, is the only known Aviar that has ever possessed this ability.
Aviar talents have some parallels to other manifestations of [[Investiture\|Investiture]] in the cosmere. Aviar exist in the same universe as other manifestations of Investiture, so the powers that they provide share some characteristics with other magics such as [[Allomancy\|Allomancy]] and [[Surgebinding\|Surgebinding]]. Although known Aviar powers are similar to Allomantic [[Copper\|copper]] and [[Electrum\|electrum]], not every Aviar talent has an Allomantic counterpart, and vice versa.
## Ecology
Many species of birds in the Pantheon can become Aviar; neither trappers nor scholars are immediately familiar with every species. Each species is typically found on a specific island. They can be sent to live in the [[Homeisles\|homeisles]] or the [[Mainland\|mainland]] without issue, but wild Aviar are only found in the Pantheon.
## Domestication
>“*An Aviar raised around humans never quite fit back in among their own kind. The same could be said of a man raised around Aviar.*”
\-Dusk[2]
When Aviar are raised by someone from birth, they form a bond with them and prefer to stay nearby, treating them as part of their flock. Due to the incredibly dangerous conditions in the Pantheon, highly trained outdoorsmen known as trappers are the only people that can survive in the islands and raise the birds. Aviar that are raised by the same trapper usually get along. They often enjoy being scratched affectionately, and may show displeasure by lightly biting. They do well living in nesting boxes in [[Safecamp\|safecamps]]; trappers can allow them to come and go freely with no concern that they will not return. Trappers use Aviar as their personal companions, and also breed and sell them as their trade. Each trapper chooses a specific island to live on and becomes most familiar with the species that live on their chosen island.
## History
Aviar is presumably an [[Eelakin\|Eelakin]] term, and throughout First of the Sun's history they were found only in the Pantheon. The magical abilities and the various species of birds had been well documented by the people of First of the Sun, and centuries passed without the discovery of a new type of Aviar. The people who were most familiar with Aviar were the trappers, who underwent extensive training in order to survive on the islands and had no qualms about killing each other when they got there. They were strongly bound by tradition, and had a reverence for the islands, particularly Patji. Trappers were notoriously reticent and stubborn, and detailed information about the Aviar and their powers remained their secret.
At some point, several Aviar were taken to other planets. During the [[True Desolation\|True Desolation]] on [[Roshar\|Roshar]], Aviar were seen in the possession of [[Mraize\|Mraize]] and [[Gereh\|Gereh]], both [[Worldhoppers\|Worldhoppers]] that were not from First of the Sun. It is not clear how the Aviar were taken off-world, as this was very difficult at the time. Gereh's Aviar was later cared for by [[Lift\|Lift]]. Like other birds, Aviar are referred to as "chickens" by most Rosharans.
On First of the Sun, Aviar had always been exported from the Pantheon exclusively by trappers. Mercantile companies long desired to find a way to set up operations on the islands so they could raise Aviar and sell them. However, trappers refused to help them, and commercial expeditions to the islands failed due to [[Deepwalker\|deepwalkers]] and other dangerous animals. Aviar therefore remained relatively rare in the homeisles and the mainland, since trappers could only provide a limited supply. After the arrival of the mysterious [[Ones Above\|Ones Above]], companies quickly developed new technologies such as warships with marine propulsion. This emboldened the Northern Interests Trading Company to undertake the [[Patji expedition\|Patji expedition]].
>“*We can’t fight them. They’ll find an excuse, they’ll seize the Aviar. It makes perfect sense. The Aviar use the worms. We use the Aviar. The Ones Above use us. It’s inevitable, isn’t it?*”
\-Vathi, on the Ones Above[2]
During the expedition, a scientist and explorer employed by the company named [[Vathi\|Vathi]] befriended a trapper named [[Sixth of the Dusk\|Sixth of the Dusk]] and learned several facts about the islands and Aviar that were previously unknown to the general public. Notably, Dusk told her about the fruit of [[Patji's Finger\|Patji's Fingers]] that gave Aviar their powers; Vathi was able to deduce that [[Sak\|Sak]] became a new type of Aviar despite her origins in the mainland. She was shocked by these revelations, which contradicted centuries of assumptions by the Eelakin people.
The Company had several devices given to them by the Ones Above, including one that could detect Aviar on the islands. When they engaged this device on Patji, all of the Aviar became agitated, and their powers were disrupted. Dusk and Vathi eventually realized that the Ones Above desired the Aviar but were somehow prohibited from taking them from a less civilized culture. They were trying to furtively accelerate the industrial development of First of the Sun in order to skirt these rules. Dusk and Vathi vowed to try and stop them.
## Known Varieties
[[Mirris\|Mirris]] is a member of a green and white species known as "streamers" that have Cognitive concealment abilities. Various other species with different types of plumage have been observed, but the names of their species are unknown.
## Notable Aviar
For a full list, see :Category: Aviar.
[[Gereh's Aviar\|Gereh's Aviar]]
[[Kokerlii\|Kokerlii]]
[[Mirris\|Mirris]]
[[Mraize\|Mraize's]] Aviar
[[Sisisru\|Sisisru]]
[[Sak\|Sak]]
## Trivia
[[Jeksonofnone\|Jeksonofnone]] is not an Aviar.
A crow named [[Lyndip\|Lyndip]] supposedly spoke to [[Allomancer Jak\|Allomancer Jak]], but Brandon has not commented on whether she is a kandra, an Aviar, or if she even exists.
Aviar were presumably inspired by Brandon's love of pet birds including macaws and cockatiels; he has owned birds since he was a child. His birds can sometimes be seen on his YouTube livestreams.
https://coppermind.net/wiki/Aviar | 120.347458 | 843 | 0.780368 | eng_Latn | 0.999789 |
faecc862de7f1d80daf22890f087ccc91345a5f8 | 2,096 | md | Markdown | README.md | webmasterish/vuepress-plugin-autonav | 3c062d6e4ca5c271de56841988419abd4513613c | [
"MIT"
] | 13 | 2019-01-10T20:05:29.000Z | 2020-08-28T01:50:10.000Z | README.md | webmasterish/vuepress-plugin-autonav | 3c062d6e4ca5c271de56841988419abd4513613c | [
"MIT"
] | null | null | null | README.md | webmasterish/vuepress-plugin-autonav | 3c062d6e4ca5c271de56841988419abd4513613c | [
"MIT"
] | 1 | 2019-02-13T19:39:36.000Z | 2019-02-13T19:39:36.000Z | # VuePress Plugin Auto Nav Links
> Auto nav links plugin for VuePress 1.x
[](https://travis-ci.org/webmasterish/vuepress-plugin-autonav)
[](http://npm.im/vuepress-plugin-autonav)
[](https://greenkeeper.io/)
[](http://opensource.org/licenses/MIT)
## What
Auto populates `themeConfig.nav` with top level pages if it's not already set.
Using a page `frontmatter` you can:
- Enable/disable adding a link to the navbar - a typical would be if you don't
want to add the home page
- Page order
## Install
```sh
$ npm install -D vuepress-plugin-autonav
# or
$ yarn add -D vuepress-plugin-autonav
```
## Usage
Add `vuepress-plugin-autonav` in your site or theme config file.
> See [official docs on using a plugin](https://vuepress.vuejs.org/plugin/using-a-plugin.html)
```js
// .vuepress/config.js
// or
// .vuepress/theme/index.js
// set your global autonav options - override in page frontmatter `autonav`
const autonav_options = {
enable: true
};
module.exports = {
plugins: [
[ 'autonav', autonav_options ]
]
}
```
### Page `frontmatter`
```md
---
title: Page Title
autonav:
enable: true
order: -1
---
```
## Reference
- VuePress official [plugin docs](https://vuepress.vuejs.org/plugin/)
- VuePress official [Navbar Links](https://vuepress.vuejs.org/theme/default-theme-config.html#navbar-links)
- VuePress official [Front Matter](https://vuepress.vuejs.org/guide/frontmatter.html)
## Related Plugins
- [VuePress Plugin Auto Meta](https://github.com/webmasterish/vuepress-plugin-autometa)
- [VuePress Plugin Minimal Google Analytics](https://github.com/webmasterish/vuepress-plugin-minimal-analytics)
## License
MIT © [webmasterish](https://webmasterish.com)
| 22.782609 | 174 | 0.729962 | kor_Hang | 0.304461 |
faecd3c8d5ca48df4e0e27b2abeee5d252c2883a | 692 | md | Markdown | advanced/full-db.md | vizh/docs | e987449df8abc9a30bcfed4d38b239b4d9b7c670 | [
"MIT"
] | null | null | null | advanced/full-db.md | vizh/docs | e987449df8abc9a30bcfed4d38b239b4d9b7c670 | [
"MIT"
] | null | null | null | advanced/full-db.md | vizh/docs | e987449df8abc9a30bcfed4d38b239b4d9b7c670 | [
"MIT"
] | null | null | null | # Database - Full documentation
You can find the full documentation on `spiral/database` here:
* [Installation and Configuration](https://spiral.dev/docs/database-configuration)
* [Access Database](https://spiral.dev/docs/database-access)
* [Database Isolation](https://spiral.dev/docs/database-isolation)
* [Query Builders](https://spiral.dev/docs/database-query-builders)
* [Transactions](https://spiral.dev/docs/database-transactions)
* [Schema Introspection](https://spiral.dev/docs/database-introspection)
* [Schema Declaration](https://spiral.dev/docs/database-declaration)
* [Migrations](https://spiral.dev/docs/database-migrations)
* [Errata](https://spiral.dev/docs/database-errata)
| 57.666667 | 82 | 0.777457 | hun_Latn | 0.289577 |
faece43ff09c4e0c8b7525c965a2d6df94195d66 | 545 | md | Markdown | _posts/2016-05-01-mac-startup-options.md | evilz/evilz.github.io | 2c2acae18422d2b91507b2e9dd84f26574c05964 | [
"MIT"
] | null | null | null | _posts/2016-05-01-mac-startup-options.md | evilz/evilz.github.io | 2c2acae18422d2b91507b2e9dd84f26574c05964 | [
"MIT"
] | null | null | null | _posts/2016-05-01-mac-startup-options.md | evilz/evilz.github.io | 2c2acae18422d2b91507b2e9dd84f26574c05964 | [
"MIT"
] | null | null | null | ---
layout: post
title: Options de démarrage pour Mac
date: 2016-05-01
author: evilz
comments: true
tags: [Mac, Informatique]
image: https://farm5.staticflickr.com/4636/39324318452_0a701c928c_n.jpg
---
Voici un récapitulatif des options de démarrage qu'il est bon de connaître pour dépanner votre Mac. Dans mon cas mon Macbook Air :)
Laissez les touches enfoncées pendant de le boot.
---
<amp-gist
data-gistid="8e9d099fefbaa161a82929506dd6e20e"
data-file="mac-boot-options.csv"
layout="fixed-height"
height="978">
</amp-gist>
| 24.772727 | 131 | 0.748624 | fra_Latn | 0.719289 |
faecf6e4eb0a860bfafb69ef6cc837cadbaeb476 | 464 | md | Markdown | curriculum/challenges/chinese/01-responsive-web-design/basic-html-and-html5/create-a-text-field.md | stevending1st/freeCodeCamp | a32784fe808b74a1d578a1371e10a934e1f3a448 | [
"BSD-3-Clause"
] | 2 | 2021-01-10T09:21:53.000Z | 2021-01-10T09:22:11.000Z | curriculum/challenges/chinese/01-responsive-web-design/basic-html-and-html5/create-a-text-field.md | stevending1st/freeCodeCamp | a32784fe808b74a1d578a1371e10a934e1f3a448 | [
"BSD-3-Clause"
] | null | null | null | curriculum/challenges/chinese/01-responsive-web-design/basic-html-and-html5/create-a-text-field.md | stevending1st/freeCodeCamp | a32784fe808b74a1d578a1371e10a934e1f3a448 | [
"BSD-3-Clause"
] | null | null | null | ---
id: bad87fee1348bd9aedf08829
title: 创建一个输入框
challengeType: 0
videoUrl: 'https://scrimba.com/p/pVMPUv/c2EVnf6'
forumTopicId: 16823
---
# --description--
现在让我们来创建一个 `form` 表单。
`input` 输入框可以让你轻松获得用户的输入。
你可以像这样创建一个文本输入框：
`<input type="text">`
**注意：**`input` 输入框是没有结束标签的。
# --instructions--
在列表下面创建一个 `type` 为 `text` 的 `input` 输入框。
# --hints--
网页中应存在一个 `type` 为 `text` 的 `input` 输入框。
```js
assert($('input[type=text]').length > 0);
```
# --solutions--
| 13.257143 | 48 | 0.661638 | yue_Hant | 0.214489 |
faed583cc8412d3e34079806cbb61913d8c54ab0 | 2,758 | md | Markdown | README.md | big-data-lab-umbc/MODIS_Aggregation | 43b79c44b0f62affdc3befb9c089a296e840893a | [
"Apache-2.0"
] | 3 | 2021-05-02T10:11:19.000Z | 2021-12-24T22:00:10.000Z | README.md | big-data-lab-umbc/MODIS_Aggregation | 43b79c44b0f62affdc3befb9c089a296e840893a | [
"Apache-2.0"
] | 5 | 2019-11-26T21:09:35.000Z | 2022-03-03T19:23:25.000Z | README.md | big-data-lab-umbc/MODIS-Aggregation | 43b79c44b0f62affdc3befb9c089a296e840893a | [
"Apache-2.0"
] | 4 | 2019-03-12T00:45:54.000Z | 2019-09-29T23:13:07.000Z | # Description
This repository does NASA MODIS data aggregation from level 2 to level 3 in a flexible and parallel approach.
Please check documents in examples folder to see examples on how to use our software.
### Installation
#### Conda environment setup
```
conda create -n MODIS_Aggregation -c conda-forge python=3.7 libnetcdf netCDF4 h5py
>> git clone https://github.com/big-data-lab-umbc/MODIS_Aggregation.git
>> cd MODIS_Aggregation
>> python setup.py install
```
The code is tested with Python 3.7
### Usage examples
Please check the [examples](examples) folder to see sample codes to import the library and use its functions for specific aggregation requirements. The examples mainly demonstrate how to conduct local execution, Dask-based distributed execution and MPI-based distributed execution. Besides these core usage examples, we also show examples for result comparison and service based deployment.
Before running the aggregation example, please read the README.md in the [examples](examples) folder for the instruction on downloading the Level-2 input data.
To run the aggregation example in local environment:
```
>> cd examples/local_execution
>> sh MODIS_Aggregation_Local_Commands.sh
```
# Team members
- Faculty: [Dr. Jianwu Wang](https://userpages.umbc.edu/~jianwu/), Department of Information Systems, UMBC
- Faculty: [Dr. Zhibo Zhang](https://physics.umbc.edu/people/faculty/zhang/), Department of Physics, UMBC
- PhD student: [Jianyu Zheng](https://acros.umbc.edu/group-members/), Department of Physics, UMBC
- PhD student: Chamara Rajapakshe, Department of Physics, UMBC
- PhD student: Pei Guo, Department of Information Systems, UMBC
- PhD student: Xin Huang, Department of Information Systems, UMBC
- MS student: Supriya Sangondimath, Department of Information Systems, UMBC
- MS student: [Savio Kay](https://saviokay.com), Department of Information Systems, UMBC
- MS student: Deepak Prakash, Department of Information Systems, UMBC
- MS student: Lakshmi Priyanka Kandoor, Department of Information Systems, UMBC
# Publications
- Jianyu Zheng, Xin Huang, Supriya Sangondimath, Jianwu Wang, and Zhibo Zhang. Efficient and Flexible Aggregation and Distribution of MODIS Atmospheric Products Based on Climate Analytics as a Service Framework. Remote Sensing 13, no. 17: 3541. https://doi.org/10.3390/rs13173541, 2021.
- Jianwu Wang, Xin Huang, Jianyu Zheng, Chamara Rajapakshe, Savio Kay, Lakshmi Kandoor, Thomas Maxwell, Zhibo Zhang. Scalable Aggregation Service for Satellite Remote Sensing Data. In Proceedings of the 20th International Conference on Algorithms and Architectures for Parallel Processing (ICA3PP 2020), pages 184-199, Springer, 2020.
# Acknowledgement
The project is mainly funded by NASA CMAC program
| 58.680851 | 390 | 0.791878 | eng_Latn | 0.827479 |
faee505ca90f778cf63339828b3ad6019cf7bd4c | 833 | md | Markdown | methods/transformers/model_cards/facebook/rag-token-nq_new/README.md | INK-USC/RiddleSense | a3d57eaf084da9cf6b77692c608e2cd2870fbd97 | [
"MIT"
] | 3 | 2021-07-06T20:02:31.000Z | 2022-03-27T13:13:01.000Z | methods/transformers/model_cards/facebook/rag-token-nq_new/README.md | INK-USC/RiddleSense | a3d57eaf084da9cf6b77692c608e2cd2870fbd97 | [
"MIT"
] | null | null | null | methods/transformers/model_cards/facebook/rag-token-nq_new/README.md | INK-USC/RiddleSense | a3d57eaf084da9cf6b77692c608e2cd2870fbd97 | [
"MIT"
] | null | null | null | The model can be loaded and used as follows on [this branch](https://github.com/huggingface/transformers/tree/finalize_rag) as follows.
# Load model
```python
from transformers import RagTokenizer, RagTokenForGeneration, RagRetriever
# create Retriever augmented model
retriever = RagRetriever.from_pretrained("facebook/rag-token-nq_new", use_dummy_dataset=True)
model = RagTokenForGeneration.from_pretrained("facebook/rag-token-nq_new", retriever=retriever)
tokenizer = RagTokenizer.from_pretrained("facebook/rag-token-nq_new")
# create input ids and labels
input_ids = tokenizer("who sings does he love me with reba", return_tensors="pt").input_ids
# use labels
labels = tokenizer.generator("Linda Davis", return_tensors="pt").input_ids
# compute loss
outputs = model(input_ids, labels=labels)
```
| 33.32 | 136 | 0.773109 | eng_Latn | 0.477025 |
faeec2834e8208760ddc19cc9a7c81824aa781f1 | 1,123 | md | Markdown | 2015/06-30-configuration/issue-2199-samples.md | MSDN-WhiteKnight/apireviews | 7be741f6d6cee4ba59cfc1b8b5e7020c1d4d3eb3 | [
"MIT"
] | 182 | 2015-01-09T05:30:01.000Z | 2022-03-31T03:11:14.000Z | 2015/06-30-configuration/issue-2199-samples.md | AzureMentor/apireviews | 33bb59f308d30d83b48f5db331630e79dbc5ab30 | [
"MIT"
] | 50 | 2015-01-16T23:27:10.000Z | 2022-03-23T18:23:26.000Z | 2015/06-30-configuration/issue-2199-samples.md | AzureMentor/apireviews | 33bb59f308d30d83b48f5db331630e79dbc5ab30 | [
"MIT"
] | 35 | 2015-01-16T23:02:28.000Z | 2022-03-23T18:08:20.000Z | # Sample Usages
For related issues see the [ASP.NET repo](https://github.com/aspnet/Configuration/issues?utf8=%E2%9C%93&q=is%3Aissue+bcl+).
## Configuration sample usage
```CSharp
// providers setup
var configuration =
new ConfigurationBuilder(appEnv.ApplicationBasePath)
.AddJsonFile("config.json")
.AddEnvironmentVariables()
.Build();
// reading a value
var connectionString = configuration["Data:DefaultConnection:ConnectionString"];
// writing a value (to memory)
configuration.Set("AppSettings:BackgroundColor", "Blue");
// accessing a group of values
var applicationSettings = configuration.GetSection("AppSettings");
```
## Options sample usage
```CSharp
// setup with configuration binding
services.Configure<AppSettings>(Configuration.GetSection("AppSettings"));
// setup with an Action<T>
services.Configure<AppSettings>(as => as.BackgrounColorName = "Blue");
// access
public class Window
{
private string _backgroundColorName;
public Window(IOptions<AppSettings> appSettings)
{
_backgroundColorName = appSettings.Options.BackgroundColorName;
}
...
```
| 24.955556 | 123 | 0.741763 | kor_Hang | 0.366193 |
faeed7bff73941405bc78e73c905bada33401c50 | 3,437 | md | Markdown | vendor/kreait/firebase-php/README.md | Marseven/GTIME | 5d31e59737aa6dcde52465e040990e134e737d6a | [
"MIT"
] | 1,795 | 2015-01-23T14:55:19.000Z | 2022-03-31T04:44:50.000Z | vendor/kreait/firebase-php/README.md | Marseven/GTIME | 5d31e59737aa6dcde52465e040990e134e737d6a | [
"MIT"
] | 590 | 2015-01-09T13:13:32.000Z | 2022-03-29T08:29:27.000Z | vendor/kreait/firebase-php/README.md | Marseven/GTIME | 5d31e59737aa6dcde52465e040990e134e737d6a | [
"MIT"
] | 463 | 2015-01-09T13:17:41.000Z | 2022-03-29T06:54:08.000Z | # Firebase Admin PHP SDK
[](https://packagist.org/packages/kreait/firebase-php)
[](https://packagist.org/packages/kreait/firebase-php)
[](https://packagist.org/packages/kreait/firebase-php/stats)
[](https://packagist.org/packages/kreait/firebase-php/stats)
[](https://github.com/kreait/firebase-php/actions)
[](https://github.com/kreait/firebase-php/actions)
[](https://codecov.io/gh/kreait/firebase-php)
[](https://discord.gg/Yacm7unBsr)
[](https://github.com/sponsors/jeromegamez)
## Table of Contents
- [Overview](#overview)
- [Installation](#installation)
- [Documentation](#documentation)
- [Support](#support)
- [License](#license)
## Overview
[Firebase](https://firebase.google.com/) provides the tools and infrastructure you need to develop your app, grow your user base, and earn money. The Firebase Admin PHP SDK enables access to Firebase services from privileged environments (such as servers or cloud) in PHP.
For more information, visit the [Firebase Admin PHP SDK documentation](https://firebase-php.readthedocs.io/).
## Installation
The Firebase Admin PHP SDK is available on Packagist as [`kreait/firebase-php`](https://packagist.org/packages/kreait/firebase-php):
```bash
composer require kreait/firebase-php
```
Integrations for Laravel, Lumen and Symfony are available:
- [kreait/laravel-firebase](https://packagist.org/packages/kreait/laravel-firebase)
- [kreait/firebase-bundle](https://packagist.org/packages/kreait/firebase-bundle)
## Documentation
- [Authentication Guide](https://firebase-php.readthedocs.io/en/stable/authentication.html)
- [Cloud Messaging Guide](https://firebase-php.readthedocs.io/en/stable/cloud-messaging.html)
- [Cloud Storage Guide](https://firebase-php.readthedocs.io/en/stable/cloud-storage.html)
- [Dynamic Links Guide](https://firebase-php.readthedocs.io/en/stable/dynamic-links.html)
- [Firestore Guide](https://firebase-php.readthedocs.io/en/stable/cloud-firestore.html)
- [Realtime Database Guide](https://firebase-php.readthedocs.io/en/stable/realtime-database.html)
- [Remote Config Guide](https://firebase-php.readthedocs.io/en/stable/remote-config.html)
## Support
- [Issue Tracker](https://github.com/kreait/firebase-php/issues/)
- [Feature Requests and Discussions](https://github.com/kreait/firebase-php/discussions)
- [Discord Community](https://discord.gg/Yacm7unBsr)
- [Stack Overflow](https://stackoverflow.com/questions/tagged/firebase+php)
## License
Firebase Admin PHP SDK is licensed under the [MIT License](LICENSE).
Your use of Firebase is governed by the [Terms of Service for Firebase Services](https://firebase.google.com/terms/).
| 55.435484 | 272 | 0.772767 | kor_Hang | 0.236442 |
faef1379c46f4f40d311ce9bd86a10b7b885d2b6 | 2,494 | md | Markdown | README.md | netshiaMR/league-ranking | c684c9cba9f9c6b72abaa9ad27cb0ad159e6e897 | [
"Apache-2.0"
] | null | null | null | README.md | netshiaMR/league-ranking | c684c9cba9f9c6b72abaa9ad27cb0ad159e6e897 | [
"Apache-2.0"
] | 1 | 2021-11-23T21:19:03.000Z | 2021-11-23T21:19:03.000Z | README.md | netshiaMR/league-ranking | c684c9cba9f9c6b72abaa9ad27cb0ad159e6e897 | [
"Apache-2.0"
] | null | null | null | # League-ranking
** Rendani Netshai ** </br>
A command-line application that will calculate the ranking table for a soccer league
**Input/output** </br>
The input and output will be text. Either using stdin/stdout or taking filenames on the command
line is fine. </br>
The input contains results of games, one per line. See “Sample input” for details. </br>
The output should be ordered from most to least points, following the format specified in
“Expected output”. </br>
You can expect that the input will be well-formed. There is no need to add special handling for
malformed input files. </br>
**The rules** </br>
In this league, a draw (tie) is worth 1 point and a win is worth 3 points. A loss is worth 0 points. </br>
If two or more teams have the same number of points, they should have the same rank and be </br>
printed in alphabetical order (as in the tie for 3rd place in the sample data). </br>
**Software requirements**
- Java JDK 11 or higher
- [Maven 3.8.0] (https://maven.apache.org/install.html)
**Installation Instructions**
1. Clone the *League-ranking* or download the zip file from github
2. Navigate to the project root folder *League-ranking* and open terminal/command line from there
3. Build the by running bat script of maven command :
> build_leagueranking.bat
4. Use the follow command to run run an application after a successful build then
5. cd to the target then run the following command
> java -jar soccer-league-1.0-SNAPSHOT-jar-with-dependencies.jar -file `{{path of input file}}`
e.g for the running and application command
>java -jar ./target/leaguerankingApp-jar-with-dependencies.jar -file C:\input.txt
note that run_app.bat script is not fully completed
**Test** </br>
***Sample input:*** </br>
============================ Fixture Input==================================================== </br>
Lions 3, Snakes 3 </br>
Tarantulas 1, FC Awesome 0 </br>
Lions 1, FC Awesome 1 </br>
Tarantulas 3, Snakes 1 </br>
Lions 4, Grouches 0 </br>
=============================================================================================== </br>
***Expected output:*** </br>
============================League Table Results============================================== </br>
1. Tarantulas, 6 pts </br>
2. Lions, 5 pts </br>
3. FC Awesome, 1 pt </br>
4. Snakes, 1 pt </br>
5. Grouches, 0 pts </br>
============================================================================================== </br>
</br>
| 41.566667 | 107 | 0.613071 | eng_Latn | 0.9726 |
faef1fcac35ecb1c626a620175720a1fb3b77b79 | 755 | md | Markdown | components/badge/demo/overflow.md | wuyun1/choerodon-hap-ui | 74499757091e1b3da4139b17b8a30b6aa87e7f97 | [
"MIT"
] | null | null | null | components/badge/demo/overflow.md | wuyun1/choerodon-hap-ui | 74499757091e1b3da4139b17b8a30b6aa87e7f97 | [
"MIT"
] | null | null | null | components/badge/demo/overflow.md | wuyun1/choerodon-hap-ui | 74499757091e1b3da4139b17b8a30b6aa87e7f97 | [
"MIT"
] | null | null | null | ---
order: 2
title:
zh-CN: 封顶数字
en-US: Overflow Count
---
## zh-CN
超过 `overflowCount` 的会显示为 `${overflowCount}+`，默认的 `overflowCount` 为 `99`。
## en-US
`${overflowCount}+` is displayed when count is larger than `overflowCount`. The default value of `overflowCount` is `99`.
````jsx
import { Badge } from 'choerodon-hap-ui';
ReactDOM.render(
<div>
<Badge count={99}>
<a href="#" className="head-example" />
</Badge>
<Badge count={100}>
<a href="#" className="head-example" />
</Badge>
<Badge count={99} overflowCount={10}>
<a href="#" className="head-example" />
</Badge>
<Badge count={1000} overflowCount={999}>
<a href="#" className="head-example" />
</Badge>
</div>,
mountNode);
````
| 20.972222 | 121 | 0.597351 | eng_Latn | 0.704731 |
faef9389378a178778c2131d804a4fef730a5f9d | 155 | md | Markdown | _posts/0000-01-10-EllanReddy.md | thisismuralim/twenty-seven | 17c01fe232c555457501a219ff84943ba2227739 | [
"MIT"
] | 4 | 2020-11-30T21:48:21.000Z | 2020-12-10T23:52:43.000Z | _posts/0000-01-10-EllanReddy.md | thisismuralim/twenty-seven | 17c01fe232c555457501a219ff84943ba2227739 | [
"MIT"
] | 17 | 2018-11-27T14:10:22.000Z | 2018-11-27T21:51:24.000Z | _posts/0000-01-10-EllanReddy.md | thisismuralim/twenty-seven | 17c01fe232c555457501a219ff84943ba2227739 | [
"MIT"
] | 5 | 2019-10-03T14:13:42.000Z | 2019-10-03T14:50:38.000Z | ---
layout: slide
title: "Welcome to our slide deck!"
---
Caption here
{: .center}
| 15.5 | 69 | 0.683871 | eng_Latn | 0.335723 |
faf0e2735c52a86be398dc9b7408b8cfd07ede32 | 537 | md | Markdown | src/pages/services/individual-and-small-group-training.md | sscaff1/dsc-website | 554b4658e227706441aabce74629076d3ce41d11 | [
"MIT"
] | null | null | null | src/pages/services/individual-and-small-group-training.md | sscaff1/dsc-website | 554b4658e227706441aabce74629076d3ce41d11 | [
"MIT"
] | null | null | null | src/pages/services/individual-and-small-group-training.md | sscaff1/dsc-website | 554b4658e227706441aabce74629076d3ce41d11 | [
"MIT"
] | null | null | null | ---
templateKey: service-section
title: Individual and small group training
---
Players will participate in specific on field training tailored to improve any identified key qualities (behaviors) or technical requirements of a position or positions that are linked to the game situations they would likely experience in attacking, defending and transition.
Within these moments of the game, six areas will be focused on in training:
1. Communication
2. Position
3. Timing
4. Direction
5. Speed
6. Execution – Technique
| 33.5625 | 277 | 0.780261 | eng_Latn | 0.999601 |
faf12e11fb4a46070fdda1a8b4acfabf0e538a43 | 818 | md | Markdown | personal/docs/Model/Transaction.md | yuikurozumi/gmo-aozora-api-php | ccc81612a2647ffb70bc43075d241d18d05a26da | [
"MIT"
] | 7 | 2019-05-24T08:17:23.000Z | 2021-08-16T01:19:14.000Z | personal/docs/Model/Transaction.md | yuikurozumi/gmo-aozora-api-php | ccc81612a2647ffb70bc43075d241d18d05a26da | [
"MIT"
] | null | null | null | personal/docs/Model/Transaction.md | yuikurozumi/gmo-aozora-api-php | ccc81612a2647ffb70bc43075d241d18d05a26da | [
"MIT"
] | 8 | 2019-11-01T05:25:03.000Z | 2022-01-12T02:35:53.000Z | # Transaction
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**transaction_date** | **string** | 取引日 半角文字 YYYY-MM-DD形式 |
**value_date** | **string** | 起算日 半角文字 YYYY-MM-DD形式 |
**transaction_type** | **string** | 入払コード 半角数字 ・1=入金 ・2=出金 |
**amount** | **string** | 取引金額 半角数字 マイナス含む |
**remarks** | **string** | 摘要内容 全半角文字 該当データがない場合は項目自体を設定しません | [optional]
**balance** | **string** | 取引後残高 半角数字 マイナス含む |
**item_key** | **string** | 明細キー 半角数字 口座の科目が01=普通預金（有利息）または02=普通預金（決済用）の場合は口座ID毎に設定される明細キー（明細データtimestamp（μs）） 該当データがない場合または、つかいわけ口座の場合は項目自体を設定しません | [optional]
[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)
| 48.117647 | 171 | 0.627139 | yue_Hant | 0.671759 |
faf15e858b0e48adab97ec7f8a26465ee5fbb5bb | 4,271 | md | Markdown | React-为什么要设计React hooks.md | zhangjing9898/FE | 72954b202a5320051c58023fe627c40a246398b9 | [
"MIT"
] | 2 | 2020-12-04T09:06:55.000Z | 2021-03-29T12:00:59.000Z | React-为什么要设计React hooks.md | zhangjing9898/FE | 72954b202a5320051c58023fe627c40a246398b9 | [
"MIT"
] | null | null | null | React-为什么要设计React hooks.md | zhangjing9898/FE | 72954b202a5320051c58023fe627c40a246398b9 | [
"MIT"
] | null | null | null | # 基础知识
React-Hooks 这个东西比较特别，这背后其实涉及对**类组件**和**函数组件**两种组件形式的思考和侧重。
## 类组件（Class Component）
基于 ES6 Class 这种写法，通过继承 React.Component 得来的 React 组件。以下是一个典型的类组件
```
class dongmaoTest extends React.Component {
// 初始化类组件的 state
state = {
text: ''
}
// 编写生命周期方法 didMount
componentDidMount() {
// 省略业务逻辑
}
// 编写自定义的实例方法
changeText = newText => {
// 更新 state
this.setState({
text: newText
})
}
// 编写生命周期方法 render
render() {
return (
<div className="demoClass">
<p>{this.state.text}</p>
<button onClick={this.changeText}>点我</button>
</div>
)
}
}
```
##
## 函数组件（Function Component）
#### 函数组件也可以叫做无状态组件
顾名思义，就是**以函数的形态**存在的组件。早期没有 React-Hooks ，函数组件内部是无法定义和维护 state，所以也可以称为“无状态组件”。
```
const dongmaoTest = (props) => {
const { text } = props
return (
<div className="demoFunction">
<p>{`文本内容是：[${text}]`}</p>
</div>
);
}
```
## 对比 类和函数组件
简单罗列一下：
- 类组件需要继承 class，函数组件不需要；
- 类组件可以访问生命周期方法，函数组件不能；
- 类组件中可以获取到实例化后的 this，并基于这个 this 做各种各样的事情，函数组件不可以；
- 类组件中可以定义并维护 state，函数组件不可以；
- ... and so on
# 深入
### 理解类组件
**包裹在面向对象思想下的“重装战舰”**
类组件是面向对象编程思想的一种表征，面向对象2大特征：
- 封装：将一类属性和方法，“聚拢抽象”到一个 Class 里去。
- 继承：新的 Class 可以通过继承现有 Class，实现对某一类属性和方法的复用。
#### 一个例子🌰
```
class dongmaoTest extends React.Component {
// 初始化类组件的 state
state = {
text: ''
}
// 编写生命周期方法 didMount
componentDidMount() {
// 省略业务逻辑
}
// 编写自定义的实例方法
changeText = newText => {
// 更新 state
this.setState({
text: newText
})
}
// 编写生命周期方法 render
render() {
return (
<div className="demoClass">
<p>{this.state.text}</p>
<button onClick={this.changeText}>点我</button>
</div>
)
}
}
```
类组件内部有相当多的“已有的东西”等着你去使用，state 和生命周期就是这些“现成东西”中的典型。如何得到这些东西？你只需要**继承**一个 React.Component
React 类组件，它提供了多少东西，你就需要学多少东西。假如背不住生命周期，你的组件逻辑顺序大概率会变成一团糟。**“大而全”的背后，是不可忽视的学习成本**。这也是类组件的一个不便，**它太重了**，对于解决许多问题来说，编写一个类组件实在是一个过于复杂的姿势。复杂的姿势必然带来高昂的理解成本。
由于开发者编写的逻辑在**封装**后是和组件粘在一起的，这就使得类组件内部的逻辑难以实现拆分和复用。
如果你想要打破这个僵局，则需要进一步学习更加复杂的设计模式（比如高阶组件、Render Props 等），用更高的学习成本来交换一点点编码的灵活度。让人头秃
### 理解函数组件
**呼应 React 设计思想的 轻巧、简洁**
```
const dongmaoTest = props => {
const { text } = props
const showAlert = () => {
alert(`我接收到的文本是${text}`)
}
return (
<div className="demoFunction">
<p>{`function 组件所接收到的来自外界的文本内容是：[${text}]`}</p>
<button onClick={showAlert}>点击弹窗</button>
</div>
)
}
```
相比于类组件，函数组件肉眼可见的特质自然包括轻量、灵活、易于组织和维护、较低的学习成本等
推荐一篇[文章](https://overreacted.io/how-are-function-components-different-from-classes/)
总结一下，文章的核心点是：**函数组件会捕获 render 内部的状态，这是两类组件最大的不同。**这句话可能有点抽象，下面会有一个例子来专门讲
#### React公式
**React 组件本身的定位就是函数，一个吃进数据、吐出 UI 的函数**
React 的数据应该总是紧紧地和渲染绑定在一起的，而类组件做不到这一点。
为什么类组件做不到？
参考上面文章中的一个例子，我们先看功能的内部实现
```
import React from 'react';
class ProfilePage extends React.Component {
showMessage = () => {
alert('Followed ' + this.props.user);
};
handleClick = () => {
setTimeout(this.showMessage, 3000);
};
render() {
return <button onClick={this.handleClick}>Follow</button>;
}
}
export default ProfilePage;
```
[在线Demo](https://codesandbox.io/s/pjqnl16lm7?file=/src/index.js)
尝试点击基于类组件形式编写的 ProfilePage 按钮，点击的时候是Dan，点击后 3s 内把用户切换为 Sophie
这是class
这是function
明明我们是在 Dan 的主页点击的关注，结果却提示了“Followed Sophie”
> **虽然 props 本身是不可变的，但 this 却是可变的，this 上的数据是可以被修改的**，this.props 的调用每次都会获取最新的 props，而这正是 React 确保数据实时性的一个重要手段。
>
>
>
> 这个案例中，**我们通过 setTimeout 将预期中的渲染推迟了 3s，打破了 this.props 和渲染动作之间的这种时机上的关联**，进而导致渲染时捕获到的是一个错误的、修改后的 this.props
函数组件会捕获 render 内部的状态，这句话也就是：**函数组件真正地把数据和渲染绑定到了一起**
**
**
## 总结
函数组件比起类组件“少”了很多东西，比如生命周期、对 state 的管理等。这就给函数组件的使用带来了非常多的局限性。
React-Hooks 的出现，就是为了帮助函数组件补齐这些（相对于类组件来说）缺失的能力
| 14.189369 | 170 | 0.673379 | yue_Hant | 0.506835 |
faf195257a83b4eb646c64b3572b3d6e9f18c2fe | 2,475 | md | Markdown | Azure-Storage/ADLS2/Browser/README.md | XavierGeerinck/PublicProjects | 616cab28d0103b6e825ee9a1442d1beadf189bd5 | [
"MIT"
] | 2 | 2020-10-17T08:59:13.000Z | 2021-06-09T06:10:24.000Z | Azure-Storage/ADLS2/Browser/README.md | XavierGeerinck/PublicProjects | 616cab28d0103b6e825ee9a1442d1beadf189bd5 | [
"MIT"
] | 12 | 2020-07-16T23:26:05.000Z | 2021-04-23T09:16:48.000Z | Azure-Storage/ADLS2/Browser/README.md | XavierGeerinck/PublicProjects | 616cab28d0103b6e825ee9a1442d1beadf189bd5 | [
"MIT"
] | 4 | 2020-06-15T15:18:54.000Z | 2021-06-09T06:10:27.000Z | # Readme
## Introduction
The code here allows you to interface with an Azure Datalake Gen 2 through a web interface, where you are able to utilize certain features:
* Filesystems (List/Delete)
* Directory (List/Delete/Create)
* File (List/Delete/Upload/Download)
**Example Use Case:** You as a company want to allow your customers that are registered in your Active Directory to upload files easily through a web portal.
## Preview
## Installation
To utilize this application, certain changes are required and an application has to be registered in your Active Directory. Here a short summary for what is required:
* Azure Active Directory Application
* Adding Azure Active Directory Application to Data Lake
* Redirect URL Added
* API Permissions Added
* Implicit Grant Enabled
* Users Allowed on Datalake
### 1. Azure Active Directory (AAD) Registering Application
#### 1.1. Creation
First start by creating an application in the AAD, where you will then find the Tenant ID and Client ID.
#### 1.2. Configuring App API Permissions
Then go to the API Permissions to grant access to the data lake
#### 1.3. Configure how the authentication works
A last thing for the application registration is to allow the implicit flow and set the redirect url to your domain.
### 2. Azure Datalake
#### 2.1. Configuring IAM
Give your application access to manage the datalake through the Blob Storage Data Contributor role
#### 2.2. Configuring CORS
Allow the web application to communicate with the REST api by configuring the CORS
### 3. Configuring the Web Application
A final thing to do is to copy the `config.templ.js` to `config.js` and fill in the parameters as found before:
* `tenantId`: your Azure Active Directory Tenant ID
* `clientId`: your configured application id
* `storageAccountName`: the account name for the storage account | 35.357143 | 166 | 0.786263 | eng_Latn | 0.949487 |
faf223aa28d069134f480efcdc50abba19db6a93 | 3,344 | md | Markdown | 1417/en.md | Retarrd/problem-tutorials | f9e49ad1ae3870ccee40983c95b56be1873a9a05 | [
"CC0-1.0"
] | 166 | 2020-11-13T12:38:52.000Z | 2022-03-04T05:45:05.000Z | 1417/en.md | Retarrd/problem-tutorials | f9e49ad1ae3870ccee40983c95b56be1873a9a05 | [
"CC0-1.0"
] | 302 | 2020-11-14T05:55:43.000Z | 2022-03-21T07:58:21.000Z | 1417/en.md | Retarrd/problem-tutorials | f9e49ad1ae3870ccee40983c95b56be1873a9a05 | [
"CC0-1.0"
] | 168 | 2020-11-14T07:12:11.000Z | 2022-03-12T16:41:03.000Z | # LOJ 1417 - Forwarding Emails
First of all, there are some people and you have to send them some mail.
Now suppose you know that, if you send a mail to the 1st person, he will be able to forward the mail to the 2nd person.
Here, one can send mail to another only when there is a connection between them.
Suppose, there is connection between 1st person and 2nd person and there is connection between 2nd and 3rd person but there is no connection between 1st and 3rd person.
If you want to send mail to 1st person to 3rd person, you have to send it through 2nd person.
Now in this problem you have to find the first person so that, you may send mail to maximum number of people.
We may try to understand the problem through an example.
Example:
1 2 - 1st person can send mail to 2nd person
2 1 - 2nd person can send mail to 1st person
5 3 - 5th person can send mail to 3rd person
3 4 - 3rd person can send mail to 4th person
4 5 - 4th person can send mail to 5th person
Here the graph is:
So here, if I send mail to the 1st person first, then he can only send the 2nd person, then the mail will reach to 2 people in total.
If I send mail to the 2nd person first, then he can only send the 1st person, then the mail will reach to 2 people in total.
If I send mail to the 3rd person first, then he can only send the 4th and 5th person, then the mail will reach to 3 people in total.
Similarly, even if the mail is sent to the 4th and 5th people first, the mail will reach to 3 people in total.
That means I can send mail to maximum three people when I send mail 3rd, 4th or 5th person first.
Since we have to print the minimum value or person who can send mail to the maximum people so the answer is 3.
Here the answer is only if we can find out all the maximum connected groups.
Then 1,2 will be in the same group and 3,4,5 will be in another group, which can be easily implemented by using BFS or DFS algorithm.
If we run a loop from the first and run a DFS from the 1st person, we can visit 1,2, then we don't need to run the DFS from the 2nd person anymore,
In the same way, if we run a DFS with 3rd person, we can visit 3,4,5, then we don't need to run DFS from 4th, 5th person.
So, DFS will run 2 times, from 1st and 3rd person. Since the maximum number of people can be mailed by 3rd person, then the last answer is 3rd.
If you are still stuck with this problem, check the codes below:
### C++
```c++
#include<bits/stdc++.h>
using namespace std;
int vis[50005],dist[50005],adjacent[50005],cnt=0;
int dfs(int uu)
{
vis[uu]=1;
int vv=adjacent[uu];
if(!vis[vv])
{
cnt++;
dfs(vv);
}
vis[uu]=0;
return dist[uu]=cnt;
}
main()
{
int ts,cs=1;
scanf("%d",&ts);
while(ts--)
{
int n,u,v,mx=0,ans=0;
scanf("%d",&n);
for(int i=1;i<=n;i++)
{
scanf("%d%d",&u,&v);
adjacent[u]=v;
}
memset(vis,0,sizeof(vis));
memset(dist,-1,sizeof(dist));
for(int i=1;i<=n; i++)
{
cnt=1;
if(dist[i]==-1)
{
dfs(i);
dist[i]=cnt;
}
if(cnt>mx)
{
mx=cnt;
ans=i;
}
}
printf("Case %d: %d\n",cs++,ans);
}
}
```
| 36.747253 | 168 | 0.650419 | eng_Latn | 0.999445 |
faf22ab4aba6196c29bca49236f1ccf86f8562a2 | 117 | md | Markdown | Doc/G/NW-NDA/99/WiP/DataSharing.md | Ralph-Diab/Cmacc-Org | 8842eace9159ded10791d2385b871f6aafc46e4e | [
"MIT"
] | null | null | null | Doc/G/NW-NDA/99/WiP/DataSharing.md | Ralph-Diab/Cmacc-Org | 8842eace9159ded10791d2385b871f6aafc46e4e | [
"MIT"
] | null | null | null | Doc/G/NW-NDA/99/WiP/DataSharing.md | Ralph-Diab/Cmacc-Org | 8842eace9159ded10791d2385b871f6aafc46e4e | [
"MIT"
] | null | null | null | Data Sharing:
Query:
1. Are NDAs <em>purely</em> a point-to-point example of a data sharing agreement?
1. | 16.714286 | 85 | 0.666667 | eng_Latn | 0.862117 |
faf239a7e56424d4384724a17a375c36508cd89b | 255 | md | Markdown | README.md | HealthByRo/react-auth | 78f6d2345c9dd24b359f4571bd1c8f0c2d3d27c7 | [
"MIT"
] | 1 | 2020-07-21T19:43:24.000Z | 2020-07-21T19:43:24.000Z | README.md | HealthByRo/react-auth | 78f6d2345c9dd24b359f4571bd1c8f0c2d3d27c7 | [
"MIT"
] | 1 | 2019-10-02T13:44:25.000Z | 2019-10-02T13:44:25.000Z | README.md | HealthByRo/react-auth | 78f6d2345c9dd24b359f4571bd1c8f0c2d3d27c7 | [
"MIT"
] | null | null | null |
# This repository is depreacted. This module has been moved to this https://github.com/HealthByRo/roman mono repo
## Quick start
## Install react-auth in your project
1. Run `yarn add https://github.com/HealthByRo/react-auth`
| 25.5 | 113 | 0.745098 | eng_Latn | 0.889411 |
faf3fac94079868c0cd87b21f1c60f8eca7fd653 | 18,576 | md | Markdown | mobile/v1/snowflake/README.md | jrpeck1989/data-models | 847a2e686978e79bfed195d212d7676a6fe7f36d | [
"Apache-2.0"
] | 31 | 2020-10-14T11:06:50.000Z | 2022-01-28T14:39:39.000Z | mobile/v1/snowflake/README.md | jrpeck1989/data-models | 847a2e686978e79bfed195d212d7676a6fe7f36d | [
"Apache-2.0"
] | 116 | 2020-10-14T11:06:43.000Z | 2022-03-08T11:44:23.000Z | mobile/v1/snowflake/README.md | jrpeck1989/data-models | 847a2e686978e79bfed195d212d7676a6fe7f36d | [
"Apache-2.0"
] | 8 | 2021-01-29T14:09:32.000Z | 2022-01-14T19:09:43.000Z | # Snowflake v1 mobile model README
This readme contains a quickstart guide, and details of how the modules interact with each other. For a guide to configuring each module, there is a README in each of the modules' `playbooks` directory.
To customise the model, we recommend following the guidance found in the README in the `sql/custom` directory.
## Quickstart
### Prerequisites
[SQL-runner 0.9.3](https://github.com/snowplow/sql-runner) or later must be installed, and a dataset of mobile events from either the Snowplow [iOS tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/objective-c-tracker/) or [Android tracker](https://docs.snowplowanalytics.com/docs/collecting-data/collecting-from-own-applications/android-tracker/) must be available in the database. The session context and screen view events most both be enabled for the mobile model to run.
### Configuration
#### Authentication
First, fill in the connection details for the target database in the relevant template in `.scripts/template/snowflake.yml.tmpl`.
Set an environment variable, `SNOWFLAKE_PASSWORD`, to your Snowflake password. See the README in `.scripts` for more detail.
#### Contexts
The following contexts can be enabled depending on your tracker configuration:
- Mobile context
- Geolocation context
- Application context
- Screen context
By default they are disabled. For more details on how to enable please see the [README](sql-runner/playbooks/standard/01-base/README.md) in the Base module's playbooks folder.
#### Optional Modules
Currently the app errors module for crash reporting is the only optional module. More will be added in the future as the tracker's functionality expands.
Assuming your tracker is capturing `application_error` events, the module can be enabled within the app errors playbook. For more details on how to enable please see the [README](sql-runner/playbooks/standard/03-optional-modules/01-app-errors/README.md) in the app errors module's playbooks folder.
#### Variables
Variables in each module's playbook can also optionally be configured also. See each playbook directory's README for more detail on configuration of each module.
### Run using the `run_config.sh` script
To run the entire standard model, end to end:
```bash
bash .scripts/run_config.sh -b ~/pathTo/sql-runner -c mobile/v1/snowflake/sql-runner/configs/datamodeling.json -t .scripts/templates/snowflake.yml.tmpl;
```
See the README in the `.scripts/` directory for more details.
## Custom Modules
A guide to creating custom modules can be found in the README of the `sql/custom/` directory of the relevant model. Each custom module created must consist of a set of sql files and a playbook, or set of playbooks. The helper scripts described above can also be used to run custom modules.
## Testing
### Setup
Python3 is required.
Install Great Expectations and dependencies, and configure a datasource:
```bash
cd .test
pip3 install -r requirements.txt
great_expectations datasource new
```
Follow the CLI guide to configure access to your database. The configuration for your datasource will be generated in `.test/great_expectations/config/config_variables.tml` - these values can be replaced by environment variables if desired.
Please be aware that the names of the tables to test have been hardcoded in the [validation configs](.test/great_expectations/validation_configs). If you are using a custom values for any of the `entropy`, `scratch_schema` or `output_schema` variables within your playbooks, you will need to manually ammend the validation configs accordingly.
If you have enabled any optional modules within the main mobile model, you will need to enable tests on these modules too. For more details on how to enable please see the [README](sql-runner/playbooks/tests/00-staging-reconciliation/README.md) in the staging reconciliation module's playbooks folder.
### Using the helper scripts
To run the test suites alone:
```bash
bash .scripts/run_test.sh -d snowflake -c perm_tables -m mobile -a {credentials (optional)}
bash .scripts/run_test.sh -d snowflake -c temp_tables -m mobile -a {credentials (optional)}
```
To run an entire run of the standard model, and tests end to end:
```bash
bash .scripts/e2e.sh -b {path_to_sql_runner} -d snowflake -m mobile -a {credentials (optional)}
```
To run a full battery of ten runs of the standard model, and tests:
```bash
bash .scripts/pr_check.sh -b {path_to_sql_runner} -d snowflake -m mobile -a {credentials (optional)}
```
### Adding to tests
Check out the [Great Expectations documentation](https://docs.greatexpectations.io/en/latest/) for guidance on using it to run existing test suites directly, create new expectations, use the profiler, and autogenerate data documentation.
Quickstart to create a new test suite:
`great_expectations suite new`
## Modules detail
### 01-base
Inputs: atomic tables, `{{.output_schema}}.mobile_base_event_id_manifest`, `{{.output_schema}}.mobile_base_session_id_manifest`
Persistent Outputs: `{{.scratch_schema}}.mobile_events_staged`,
Temporary Outputs: `{{.scratch_schema}}.mobile_events_this_run`, `{{.scratch_schema}}.mobile_base_duplicates_this_run`
The base module executes the incremental logic of the model - it retrieves all events for sessions with new data, deduplicates, and adds any enabled contexts.
The base module's 'complete' playbook (`99-base-complete.yml.tmpl`) updates the two relevant manifests, and cleans up temporary tables. The lifecycle of the `{{.scratch_schema}}.mobile_events_staged` table is completed by the `99-sessions-complete.yml.tmpl` step of the sessions module, when the table is truncated. This truncation can only occur during the completion step of the sessions module as `{{.scratch_schema}}.mobile_events_staged` is required as an input to the sessions module. This differs to the web model where the page views module's complete step would contain the truncation step.
The `{{.scratch_schema}}.mobile_events_this_run` table contains all events relevant only to this run of the model (since the last time the `99-base-complete.yml.tmpl` playbook has run). This table is dropped and recomputed _every_ run of the module, regardless of whether another module has used the data.
If there is a requirement that a custom module consumes data _more frequently than the screen views module for example_, the `{{.scratch_schema}}.mobile_events_this_run` table may be used for this purpose.
The `{{.scratch_schema}}.mobile_events_staged` table is incrementally updated to contain all events relevant to any run of the base module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` has run). This allows one to run the base module more frequently than the subsequent modules (if, for example, a custom module reads from events_this_run).
Detail on configuring the base module's playbook can be found [in the relevant playbook directory's README](sql-runner/playbooks/standard/01-base).
### 02-screen-views
Inputs: atomic tables, `{{.scratch_schema}}.mobile_events_staged`
Persistent Outputs: `{{.output_schema}}.mobile_screen_views`, `{{.scratch_schema}}.mobile_screen_views_staged`
Temporary Outputs: `{{.scratch_schema}}.mobile_screen_views_this_run`
The screen views module takes `{{.scratch_schema}}.mobile_events_staged` as its input, joins in and deduplicates screen_view_id, calculates the standard mobile screen views model, and updates the production mobile_screen_views table. It also produces the `{{.scratch_schema}}.mobile_screen_views_staged` and `{{.scratch_schema}}.mobile_screen_views_this_run` tables.
The screen views module's 'complete' playbook `99-screen-views-complete.yml.tmpl` cleans up temporary tables. The lifecycle of the `{{.scratch_schema}}.mobile_screen_views_staged` table is completed by the `99-sessions-complete.yml.tmpl` step (of the subsequent module).
The `{{.scratch_schema}}.mobile_screen_views_this_run` table contains all events relevant only to this run of the model (since the last time the `99-screen-views-complete.yml.tmpl` playbook has run). This table is dropped and recomputed _every_ run of the module, regardless of whether another module has used the data.
If there is a requirement that a custom module consumes data _more frequently than the sessions module_, the `{{.scratch_schema}}.mobile_screen_views_this_run` table may be used for this purpose.
The `{{.scratch_schema}}.mobile_screen_views_staged` table is incrementally updated to contain all events relevant to any run of the screen views module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` playbook has run). This allows one to run the screen views module more frequently than the sessions module (if, for example, a custom module reads from mobile_screen_views_this_run).
Detail on configuring the screen views module's playbook can be found [in the relevant playbook directory's README](sql-runner/playbooks/02-screen-views).
### 03-optional-modules
#### 01-app-errors
Inputs: atomic tables, `{{.scratch_schema}}.mobile_events_staged`
Persistent Outputs: `{{.output_schema}}.mobile_app_errors`, `{{.scratch_schema}}.mobile_app_errors_staged`
Temporary Outputs: `{{.scratch_schema}}.mobile_app_errors_this_run`
The app errors module takes `{{.scratch_schema}}.mobile_events_staged` as its input, joins in the app errors context, calculates the app errors model, and updates the production mobile_app_errors table. It also produces the `{{.scratch_schema}}.mobile_app_errors_staged` and `{{.scratch_schema}}.mobile_app_errors_this_run` tables.
This crash reporting module is disabled by default since it is not a requirement to run the mobile model. Despite this, the `{{.scratch_schema}}.mobile_app_errors_staged` table will be created irrespectively. This is to allow the sessions module to run correctly where the `{{.scratch_schema}}.mobile_app_errors_staged` table is required as an input.
The app errors module's 'complete' playbook `99-app-errors-complete.yml.tmpl` cleans up temporary tables. The lifecycle of the `{{.scratch_schema}}.mobile_app_errors_staged` table is completed by the `99-sessions-complete.yml.tmpl` step (of the subsequent module).
The `{{.scratch_schema}}.mobile_app_errors_this_run` table contains all events relevant only to this run of the model (since the last time the `99-app-errors-complete.yml.tmpl` playbook has run). This table is dropped and recomputed _every_ run of the module, regardless of whether another module has used the data.
If there is a requirement that a custom module consumes data _more frequently than the sessions module_, the `{{.scratch_schema}}.mobile_app_errors_this_run` table may be used for this purpose.
The `{{.scratch_schema}}.mobile_app_errors_staged` table is incrementally updated to contain all events relevant to any run of the screen views module _since the last time the sessions module consumed it_ (ie since the last time the `99-sessions-complete.yml.tmpl` playbook has run). This allows one to run the app errors module more frequently than the sessions module (if, for example, a custom module reads from mobile_app_errors_this_run).
Detail on configuring the app errors module's playbook can be found [in the relevant playbook directory's README](sql-runner/playbooks/03-optional-modules/01-app-errors).
### 04-sessions
Inputs: `{{.scratch_schema}}.mobile_screen_views_staged`, `{{.scratch_schema}}.mobile_app_errors_staged`, `{{.scratch_schema}}.mobile_events_staged`
Persistent Outputs: `{{.output_schema}}.mobile_sessions`, `{{.scratch_schema}}.mobile_sessions_userid_manifest_staged`
Temporary Outputs: `{{.scratch_schema}}.mobile_sessions_this_run`
The sessions module takes the `_staged` output tables of the upstream modules as its input, calculates the standard sessions model, and updates the production sessions table. It also produces the `{{.scratch_schema}}.mobile_sessions_userid_manifest_staged` and `{{.scratch_schema}}.mobile_sessions_this_run{{.entropy}}` tables.
Unlike the other modules, the sessions module outputs a manifest of IDs as its staged table rather than a table containing all unprocessed data - this is due to the fact that the users step requires a longer lookback than the incremental structure contains, so there are obviously efficiency limitations.
The sessions module's 'complete' playbook `99-sessions-complete.yml.tmpl` truncates the input tables, and cleans up temporary tables. The lifecycle of the `{{.scratch_schema}}.mobile_sessions_userid_manifest_staged` table is completed by the `99-users-complete.yml.tmpl` step (of the subsequent module).
The `{{.scratch_schema}}.mobile_sessions_this_run` table contains all events relevant only to this run of the model (since the last time the `99-sessions-complete.yml.tmpl` playbook has run). This table is dropped and recomputed _every_ run of the module, regardless of whether another module has used the data.
If there is a requirement that a custom module consumes data _more frequently than the users module_, the `{{.scratch_schema}}.mobile_sessions_this_run` table may be used for this purpose.
The `{{.scratch_schema}}.mobile_sessions_userid_manifest_staged` table is incrementally updated to contain all IDs relevant to any run of the sessions module _since the last time the users module consumed it_ (ie since the last time the `99-users-complete.yml.tmpl` playbook has run). This allows one to run the sessions module more frequently than the users module (if, for example, a custom module reads from sessions_this_run and is more frequent than the page views module).
Detail on configuring the sessions module's playbook can be found [in the relevant playbook directory's README](sql-runner/playbooks/04-sessions).
### 05-users
Inputs: `{{.scratch_schema}}.mobile_sessions_userid_manifest_staged`, `{{.output_schema}}.mobile_users_manifest`
Persistent Outputs: `{{.output_schema}}.mobile_users`
Temporary Outputs: `{{.scratch_schema}}.mobile_users_this_run`
The sessions module takes `{{.scratch_schema}}.mobile_sessions_userid_manifest_staged` as its input, alongside the `{{.output_schema}}.mobile_users_manifest` table (which is self-maintained within the users module). It calculates the standard users model, and updates the production users table. It also produces the `{{.scratch_schema}}.mobile_users_this_run` table.
Unlike the other modules, the users module doesn't take an input that contains all information required to run the module. It uses the `{{.output_schema}}.mobile_users_manifest` table to manage efficiency, and queries the sessions table to process data as far back in history as is required.
The users module's 'complete' playbook `99-users-complete.yml.tmpl` truncates the `{{.scratch_schema}}.mobile_sessions_userid_manifest_staged` table, commits to the `{{.output_schema}}.mobile_users_manifest` and cleans up temporary tables. There is no `_staged` table for this module, as there are no subsequent modules.
The `{{.scratch_schema}}.mobile_users_this_run` table contains all events relevant only to this run of the model (since the last time the `99-users-complete.yml.tmpl` playbook has run). This table is dropped and recomputed _every_ run of the module, regardless of whether another module has used the data.
Detail on configuring the users module's playbook can be found [in the relevant playbook directory's README](sql-runner/playbooks/standard/05-users).
## Scheduling
### Asynchronous Runs
While the model is configured by default to run the entire way through, i.e. from the base module through to the users module, it is possible to run each module independently. For instance one could run the screen views module hourly while only running the sessions module daily. To do so you should run hourly all modules up to and including the desired module i.e. the base and screen view modules. The sessions module can then be run on a daily schedule. A few points to note:
- It is only when the sessions module is run that the `{{.scratch_schema}}.mobile_events_staged` is truncated. As a result, the hourly runs of the screen views module will both process new events data as well as re-process data stored in `mobile_events_staged` since the last time the sessions module ran.
- Prior to running sessions module ensure that all input modules have been run i.e. base, screen views and _any enabled optional modules_. This ensures all the inputs are up to date and in-sync.
### Incomplete Runs
It is not a requirement to run every module. For example you may decide you do not need sessions or users data and only want screen view data. To do so:
- Set `stage_next` to `False` and `:ends_run:` to true in the screen views module. See the [README](sql-runner/playbooks/02-screen-views) for more details.
- Run all modules up to and including the screen views module.
- Ensure that the sessions 'complete' playbook, `99-sessions-complete.yml.tmpl`, is the last step in the run. This playbook includes the truncation of the `mobile_events_staged` table. Without this truncation _each subsequent run will re-process data severely impacting performance._
## A note on duplicates
This version of the model (1.0.0) contains deduplication steps in both the base and screen views modules. The base module deduplicates on `event_id`, where _only_ the first row per `event_id` is kept (ordered by `collector_tstamp`).
The screen view module deduplicates on `screen_view_id`, where _only_ the first row per `screen_view_id` is kept (ordered by `derived_tstamp`).
## A note on Constraints and Clustering keys
This 1.0.0 version of the Snowflake mobile model does not use Constraints or Clustering keys in the table definitions, even though it could.
Concerning [clustering keys](https://docs.snowflake.com/en/user-guide/tables-clustering-keys.html#strategies-for-selecting-clustering-keys), Snowflake's naturally clusters the tables on insertion order, and there hasn't been evidence so far suggesting a change towards another manual clustering strategy.
Concerning table [constraints](https://docs.snowflake.com/en/sql-reference/constraints-overview.html), it is a fact that Snowflake enforces **only** the `NOT NULL` constraint. Therefore, in this 1.0.0 version we decided to include only this constraint that is actually enforced, for clarity on the model's assumptions.
| 77.078838 | 599 | 0.792259 | eng_Latn | 0.991067 |
faf416198d9f58e061f57fe949f34f964d0e1b9a | 10,247 | md | Markdown | changelog/nl.md | TomHennen/AntennaPod | e9b655b92e291d08a93fbc9de2355a4944a393ab | [
"MIT"
] | 1 | 2015-04-24T22:29:56.000Z | 2015-04-24T22:29:56.000Z | changelog/nl.md | TomHennen/AntennaPod | e9b655b92e291d08a93fbc9de2355a4944a393ab | [
"MIT"
] | null | null | null | changelog/nl.md | TomHennen/AntennaPod | e9b655b92e291d08a93fbc9de2355a4944a393ab | [
"MIT"
] | null | null | null | Changelog
==========
Versie 1.4
-----------
* BLUETOOTH TOESTEMMING: Vereist om afspelen te kunnen hervatten wanneer een Bluetooth-apparaat opnieuw verbind met uw telefoon
* TRILLINGEN TOESTEMMING: Optioneel gebruik bij de slaap timer
* Variabele speelsnelheid via 'native' Android mediaspeler (experimenteel, zie instellingen)
* Verbeterde slaap timer
* Afleveringen tevoegen als 'favoriet'
* Afleveringen overslaan vanaf het notificatiecentrum
* Afleveringen niet verwijderen bij overslaan
* Afbeelding van de aflevering tonen op het vergendelingsscherm
* Slimme 'auto-cleanup' van afleveringen
* Kort terugspoelen na pauzeren
* Verbeterd gebruiksgemak
* Bugfixes
Versie 1.3
-----------
* Bulk-aanpassingen van afleveringen (downloaden, in wachtrij zetten, verwijderen)
* Minder geheugengebruik voor afbeeldingen
* Automatisch vernieuwen op bepaald tijdstip
* Nieuwe tellers en nieuwe mogelijkheden om feeds in het menu te sorteren
* Delen van feeds URLs
* Automatisch downloaden verbeterd
* Veel bugfixes en verbeterde gebruiksvriendelijkheid
Version 1.2
-----------
* Optionally disable swiping and dragging in the queue
* Resume playback after phone call
* Filter episodes in the Podcast feed
* Hide items in the Nav drawer
* Customize times for fast forward and rewind
* Resolved issues with opening some OPML files
* Various bug fixes and usability improvements
Version 1.1
-----------
* iTunes podcast integration
* Swipe to remove items from the queue
* Set the number of parallel downloads
* Fix for gpodder.net on old devices
* Fixed date problems for some feeds
* Display improvements
* Verbeterd gebruiksgemak
* Several other bugfixes
Version 1.0
-----------
* The queue can now be sorted
* Added option to delete episode after playback
* Fixed a bug that caused chapters to be displayed multiple times
* Several other improvements and bugfixes
Version 0.9.9.6
---------------
* Fixed problems related to variable playback speed plugins
* Fixed automatic feed update problems
* Several other bugfixes and improvements
Version 0.9.9.5
---------------
* Added support for paged feeds
* Verbeterde gebruikersinterface
* Added Japanese and Turkish translations
* Fixed more image loading problems
* Andere bugfixes en verbeteringen
Version 0.9.9.4
---------------
* Added option to keep notification and lockscreen controls when playback is paused
* Fixed a bug where episode images were not loaded correctly
* Fixed battery usage problems
Version 0.9.9.3
---------------
* Fixed video playback problems
* Improved image loading
* Andere bugfixes en verbeteringen
Version 0.9.9.2
---------------
* Added support for feed discovery if a website URL is entered
* Added support for 'next'/'previous' media keys
* Verbeterde slaap timer
* Timestamps in shownotes can now be used to jump to a specific position
* Automatic Flattring is now configurable
* Diverse bugfixes en verbeteringen
Version 0.9.9.1
---------------
* Diverse bugfixes en verbeteringen
Version 0.9.9.0
---------------
* New user interface
* Failed downloads are now resumed when restarted
* Added support for Podlove Alternate Feeds
* Added support for "pcast"-protocol
* Added backup & restore functionality. This feature has to be enabled in the Android settings in order to work
* Diverse bugfixes en verbeteringen
Version 0.9.8.3
---------------
* Ondersteuning toegevoegd voor wachtwoord-beveiligde feeds en afleveringen
* Ondersteuning toegevoegd voor meer soorten episode beelden
* Hebreeuwse vertaling toegevoegd
* Diverse bugfixes en verbeteringen
Version 0.9.8.2
---------------
* Diverse bugfixes en verbeteringen
* Koreaanse vertaling toegevoegd
Version 0.9.8.1
---------------
* Optie toegevoegde om een aflevering automatisch te Flattren nadat 80 procent van de episode gespeeld is
* Poolse vertaling toegevoegd
* Diverse bugfixes en verbeteringen
Versie 0.9.8.0
---------------
* Toegang toegevoegd tot de gpodder.net gids
* Mogelijkheid toegevoegd om podcast abonnementen met de gpodder.net dienst te synchroniseren
* Automatisch downloaden kan nu voor specifieke podcasts ingeschakeld of uitgeschakeld worden
* Optie toegevoegd om het afspelen te pauzeren wanneer een andere app geluiden speelt
* Nederlandse en Hindi vertalingen toegevoegd
* Probleem met automatische podcast updates opgelost
* Probleem met de zichtbaarheid van de knoppen in de episode scherm opgelost
* Probleem opgelost waarbij afleveringen onnodig opnieuw gedownload zouden worden
* Diverse andere bugfixes en usability verbeteringen
Versie 0.9.7.5
---------------
* Opstarttijd van de app verminderd
* Minder geheugengebruik
* Optie toegevoegd om de afspeelsnelheid te veranderen
* Zweedse vertaling toegevoegd
* Diverse bugfixes en verbeteringen
Versie 0.9.7.4
---------------
* De groote van de episode cache kan nu op onbeperkt worden ingesteld
* Het verwijderen via sliding van een episode in de wachtrij kan nu ongedaan gemaakt worden
* Ondersteuning toegevoegd voor links in MP3 hoofdstukken
* Tsjechische (Tsjechië), Azerbeidzjaanse en Portugese vertalingen toegevoegd
* Diverse bugfixes en verbeteringen
Versie 0.9.7.3
---------------
* Bluetooth-apparaten geven nu metagegevens weer tijdens het afspelen (AVRCP 1.3 of hoger vereist)
* Verbeteringen in de user interface
* Diverse bugfixes
Versie 0.9.7.2
---------------
* Automatisch downloaden kan nu worden uitgeschakeld
* Italiaanse (Italië) vertaling toegevoegd
* Diverse bugfixes
Versie 0.9.7.1
---------------
* Automatisch downloaden van nieuwe afleveringen toegevoegd
* Optie toegevoegd om in te kunnen stellen hoeveel gedownloade afleveringen op het apparaat behouden moeten worden
* Ondersteuning toegevoegd voor het afspelen van externe mediabestanden
* Diverse verbeteringen en bugfixes
* Catalaanse vertaling toegevoegd
Versie 0.9.7
-------------
* Verbeterde gebruikersinterface
* OPML-bestanden kunnen nu geïmporteerd worden door ze in een file browser te selecteren
* De wachtrij kan nu via drag & drop georganiseerd worden
* Uitbreidbaar meldingen toegevoegd (alleen op Android 4.1 en hoger ondersteund)
* Deens, Frans, Roemeens (Roemenië) en Oekraïense (Oekraïne) vertalingen toegevoegd (met dank aan alle vertalers!)
* Diverse bugfixes en kleine verbeteringen
Versie 0.9.6.4
---------------
* Chinese vertaling toegevoegd (Bedankt tupunco!)
* Portugeese (Brazilië) vertaling toegevoegd (Bedankt mbaltar!)
* Diverse bugfixes
Versie 0.9.6.3
---------------
* Mogelijkheid toegevoegd om de locatie van de data map van AntennaPod te veranderen
* Spaanse vertaling toegevoegd (Bedankt frandavid100!)
* Problemen opgeloste met meerdere feeds
Versie 0.9.6.2
---------------
* Import problemen met sommige OPML-bestanden opgelost
* Download problemen opgelost
* AntennaPod herkent nu veranderingen in episode informatie
* Andere verbeteringen en bugfixes
Versie 0.9.6.1
---------------
* Donkere theme toegevoegd
* Diverse bugfixes en verbeteringen
Versie 0.9.6
-------------
* Ondersteuning voor VorbisComment hoofdstukken toegevoegd
* AntennaPod toont nu items als 'in progress' wanneer het afspelen is gestart
* Minder geheugengebruik
* Ondersteuning toegevoegd voor meer feed soorten
* Diverse bugfixes
Versie 0.9.5.3
---------------
* Crash op sommige apparaten bij het proberen te starten van het afspelen opgelost
* Problemen met sommige feeds opgelost
* Andere bugfixes en verbeteringen
Versie 0.9.5.2
---------------
* Media player gebruikt nu geen netwerkbandbreedte meer indien niet in gebruik
* Andere verbeteringen en bugfixes
Versie 0.9.5.1
---------------
* Afspeelgeschiedenis toegevoegd
* Gedrag van download meldingen verbeterd
* Verbeterde ondersteuning voor headset controles
* Bugfixes in de feed parser
* Knoppen 'OPML import' naar het 'Feed' scherm en 'OPML export' naar de instellingenscherm verplaatst
Versie 0.9.5
-------------
* Experimentele ondersteuning voor MP3 hoofdstukken
* Nieuwe menu-opties voor de 'nieuwe' lijst en de wachtrij
* Auto-delete functie
* Betere downloadfout rapportages
* Diverse bugfixes
Versie 0.9.4.6
---------------
* Ondersteuning voor apparaten met kleine schermen geactiveerd
* Het uitschakelen van de slaaptimer moet nu weer werken
Versie 0.9.4.5
---------------
* Russische vertaling toegevoegd (Bedankt older!)
* Duitse vertaling toegevoegd
* Diverse bugfixes
Versie 0.9.4.4
---------------
* Speler controles toegevoegd aan de onderkant van het hoofdscherm en de feedlijst schermen
* Afspelen van media verbeterd
Versie 0.9.4.3
---------------
* Enkele bugs in de feed parser opgelost
* Verbeterd gedrag van downloaden rapporten
Versie 0.9.4.2
---------------
* Bug in de OPML-importeur opgelost
* Minder geheugengebruik van beelden
* Download problemen op sommige apparaten opgelost
Versie 0.9.4.1
---------------
* Gedrag van downloaden meldingen gewijzigd
Versie 0.9.4
-------------
* Snellere en betrouwbaardere downloads
* Lockscreen player controls voor Android 4.x-apparaten toegevoegd
* Diverse bugfixes
Versie 0.9.3.1
---------------
* Optie toegevoegd om feeds die geen episode hebben te verbergen
* Verbeterde beeldformaat voor sommige schermformaten
* Grid weergave voor grote schermen toegevoegd
* Diverse bugfixes
Versie 0.9.3
-------------
* integratie met de MiroGuide
* Bugfixes in de audio- en videospeler
* Feeds automatisch aan de wachtrij toevoegen wanneer ze zijn gedownload
Versie 0.9.2
-------------
* Bugfixes in de gebruikersinterface
* GUID en ID attributen worden nu door de feedparser erkend
* Stabiliteit verbeteringen bij het toevoegen van meerdere feeds tegelijk
* Bugs die opgetreden bij het toevoegen van bepaalde feeds opgelost
Versie 0.9.1.1
--------------------
* Flattr credentials veranderd
* Verbeterde lay-out van de Feed informatie scherm
* AntennaPod is nu open source! De broncode is beschikbaar op https://github.com/danieloeh/AntennaPod
Versie 0.9.1
-----------------
* Ondersteuning toegevoegd voor koppelingen in SimpleChapters
* Bugfix: Huidige hoofdstuk werd niet altijd correct weergegeven
Versie 0.9
--------------
* OPML export
* Flattr integratie
* Slaaptimer
Versie 0.8.2
-------------
* Zoeken toegevoegd
* Verbeterde OPML import ervaring
* Meer bugfixes
Versie 0.8.1
------------
* Ondersteuning toegevoegd voor SimpleChapters
* OPML import | 31.336391 | 127 | 0.752415 | nld_Latn | 0.997626 |
faf42ce479d6349c9eb3e0b9798aa6a4444618a7 | 366 | md | Markdown | README.md | josemiguesuarez/customisableSlideber | 7083cae2d357b99d937308644a87d4c633fdf0f7 | [
"Apache-2.0"
] | null | null | null | README.md | josemiguesuarez/customisableSlideber | 7083cae2d357b99d937308644a87d4c633fdf0f7 | [
"Apache-2.0"
] | null | null | null | README.md | josemiguesuarez/customisableSlideber | 7083cae2d357b99d937308644a87d4c633fdf0f7 | [
"Apache-2.0"
] | null | null | null | # customisableSlideber
It is a customisable slide bar madden to works perfectly whit Angular.js. You can create multiple sliders and change all css styles.
* This project allow you to edit all styles to integrate the slide bar perfectly to your site.
* You can create many sliders in a single slide bar as you want.
* To run:
+ $ npm install -g serve
+ $ serve
| 36.6 | 132 | 0.759563 | eng_Latn | 0.999587 |
faf57b35e237f59563a9063a027df081d9ce580d | 3,100 | md | Markdown | README.md | pallad-ts/secret | f87a674235e9c54aa61e274e4431d774ae453988 | [
"MIT"
] | 6 | 2020-01-03T10:46:52.000Z | 2022-02-22T19:59:18.000Z | README.md | pallad-ts/secret | f87a674235e9c54aa61e274e4431d774ae453988 | [
"MIT"
] | 5 | 2021-05-10T23:10:52.000Z | 2021-11-09T19:18:08.000Z | README.md | pallad-ts/secret | f87a674235e9c54aa61e274e4431d774ae453988 | [
"MIT"
] | null | null | null | <div align="center">
<h1>Secret 🤫</h1>
<p>Prevent your secrets from accidental leak</p>
</div>
---
[](https://circleci.com/gh/pallad-ts/secret/tree/master)
[](https://badge.fury.io/js/@pallad%2Fsecret)
[](https://coveralls.io/github/pallad-ts/secret?branch=master)
[](https://opensource.org/licenses/MIT)
---
Wraps any value and prevents it to:
* be converted to string
* serialized (for example by `JSON.stringify`)
* inspected (through `util.inspect`)
* logged (through `console.log`) or debugged.
# Use cases
* Passing around un/encrypted passwords
* Storing confidential credentials (api keys, database passwords)
* Wrapping config values
# Features
* 👷 Built with Typescript - full type friendly
* ✅ Supports auto wrapping functions results with Secret
* 😍 Easy integration with literally any library/framework
# Community
Join our [discord server](https://discord.gg/paTBKBxXnA)
# Installation
```shell
npm install @pallad/secret
```
# Usage
Just wrap it with `secret` or `new Secret`. It order to retrieve value you need to explicitly call `getValue` method
```typescript
import {Secret, secret} from '@pallad/secret';
const SECRET = 'someProtectedValue!3234#@#%4';
const protectedValue = new Secret(SECRET);
// or
const protectedValue2 = secret(SECRET);
protectedValue + ''; // '**SECRET**'
protectedValue.toString(); // '**SECRET**'
util.inspect(protectedValue); // **SECRET**
console.log(protectedValue); // **SECRET**
util.inspect(protectedValue, {customInspect: false}); // Secret [**SECRET**] {}
console.log(protectedValue.getValue()); // 'someProtectedValue!3234#@#%4'
```
## Custom description
Instead of `'**SECRET**'` you can print something else.
```typescript
import {Secret} from '@pallad/secret';
const protectedValue = new Secret(SECRET, 'CustomDescription');
String(protectedValue); // 'CustomDescription'
console.log(protectedValue); // CustomDescription
util.inspect(protectedValue, {customInspect: false}); // CustomDescription
```
## Wrapping function result
`protect` wraps a function with another function that wraps returned value with secret for you.
```typescript
import {protect, Secret} from '@pallad/secret';
const result1 = protect(x => 'protectedValue')();
Secret.is(result1); // true
result1.getValue(); // 'protectedValue')
```
Promises are also handled (full type support)
```typescript
const result2 = protect(x => Promise.resolve('protectedValue'))();
result2.then(x => {
Secret.is(x); // true
x.getValue(); // 'protectedValue'
})
```
## Checking if value is Secret
```typescript
import {Secret, secret} from '@pallad/secret';
Secret.is(new Secret('test')) // true
Secret.is(secret('test')) // true
Secret.is(protect(() => 'test')()) // true
Secret.is('secret') // false
```
| 26.956522 | 156 | 0.719355 | eng_Latn | 0.631694 |
faf65b60078eb61e5c562d62c7720f55dc03ba66 | 32 | md | Markdown | content/templates/_components/c-message/01-message.md | syedahmedhussaini/tag-system | 02ddb504ceb4d079129f4bed6b1f273037fb259b | [
"MIT"
] | null | null | null | content/templates/_components/c-message/01-message.md | syedahmedhussaini/tag-system | 02ddb504ceb4d079129f4bed6b1f273037fb259b | [
"MIT"
] | null | null | null | content/templates/_components/c-message/01-message.md | syedahmedhussaini/tag-system | 02ddb504ceb4d079129f4bed6b1f273037fb259b | [
"MIT"
] | null | null | null | ---
title: Feedback Message
---
| 8 | 23 | 0.625 | eng_Latn | 0.742339 |
faf7a9cfc7d28756b5149362d56bbd89d2b2d171 | 1,277 | md | Markdown | gatsby-plugin-percy/README.md | jmf-85/gatsby-starter-netlify-cms | 6a3598492d5983e31c709908bd144f9881119c95 | [
"MIT"
] | null | null | null | gatsby-plugin-percy/README.md | jmf-85/gatsby-starter-netlify-cms | 6a3598492d5983e31c709908bd144f9881119c95 | [
"MIT"
] | null | null | null | gatsby-plugin-percy/README.md | jmf-85/gatsby-starter-netlify-cms | 6a3598492d5983e31c709908bd144f9881119c95 | [
"MIT"
] | null | null | null | # gatsby-plugin-percy
A Gatsby plugin for automatically taking Percy snapshots after a build.
### Dependencies
- [@percy/agent](https://github.com/percy/percy-agent)
## Install
```shell
$ npm install --save @percy/agent gatsby-plugin-percy
```
## Usage
```javascript
// In your gatsby-config.js
module.exports = {
plugins: [
{
resolve: `gatsby-plugin-percy`,
options: {
// example options:
// files: [`dir/*.html`],
// ignore: [`ignore/*.html`],
// config: `config/.percy.yaml`,
},
},
],
}
```
## Options
Options are not required. Percy searches the current working directory and up
for a [matching config file](https://docs.percy.io/docs/sdk-configuration#section-configuration-files).
The `files` and `ignore` options can be specified within a
[`static-snapshots` section](https://docs.percy.io/docs/sdk-configuration#section-static-snapshots)
of your Percy config file as `snapshot-files` and `ignore-files` respectively.
- `files` - A single file glob or array of file globs to snapshot within the `public` directory
- `ignore` - A single file glob or array of file globs to ignore within the `public` directory
- `config` - Path to a [Percy config file](https://docs.percy.io/docs/sdk-configuration)
| 28.377778 | 103 | 0.688332 | eng_Latn | 0.800979 |
faf7dadda25a4cb6d3cdc5d76a7743bc97485c54 | 6,208 | md | Markdown | doc/sprint0/PB.md | aviral25/SportCredAPP | 68c8a81d316b6d949ec065fd9ee8d2d0845b031c | [
"MIT"
] | null | null | null | doc/sprint0/PB.md | aviral25/SportCredAPP | 68c8a81d316b6d949ec065fd9ee8d2d0845b031c | [
"MIT"
] | null | null | null | doc/sprint0/PB.md | aviral25/SportCredAPP | 68c8a81d316b6d949ec065fd9ee8d2d0845b031c | [
"MIT"
] | null | null | null | # Product Backlog
### Estimation method
The team came to a conclusive decision to use the Fibonacci series as the numerical scale to estimate the user stories.
### User Stories
These user stories are listed in order of priority
1. Register
* Description:
As an unregistered user, Thomas/Rebecca wants to be able to register an account and have it save his/her info and current/past ACS scores so that he/she can monitor his/her score’s development over time.
* Acceptance Criteria:
Given that I am an unregistered/new user and am on the register page, when I fill in my wanted username (which is unique), preferred authentication details (password and email), and click on the register button, The app will register me as a user and send me to the home page.
* Priority: Highest
* Estimate: 3
2. Log in
* Description:
As a logged-out user, Peter/Rebecca wants to be able to log back into his/her profile, so that he/she can check his/her account at any time and on any device.
* Acceptance Criteria:
As a logged-out user with an existing profile, when I fill in my username and password I will log in to my profile and be able to access the app’s functions.
* Priority: Highest
* Estimate: 3
3. Profile Details
* Description:
As a user, Peter/Thomas/Rebecca wants to be able to view and change his/her profile details so that it will accurately represent their information.
* Acceptance Criteria:
As a logged-in user, when I go to settings and choose one of the account settings, I will be able to change my profile details without delay and correctly.
* Priority: High
* Estimate: 3
4. Picks
* Description:
As a user, Peter/Rebecca wants to be able to pick the teams he/she predicts to win and where they’ll place so that they can gain ACS scores if predicted accurately.
* Acceptance Criteria:
As a logged-in user, if I am in picks, I can pick teams and make predictions and gain ACS scores on making accurate picks.
* Priority: High
* Estimate: 5
5. Open Court
* Description:
As a logged-in user, Peter/Thomas wants to be able to discuss with other users the current state of basketball games by posting and commenting, and gain likes on the posts/comments so that they can discuss similar interests and share knowledge.
* Acceptance Criteria:
Given that I am a logged-in user, when I open the open court page, then I can see trending discussions, upvote/downvote them, and create my posts to share publicly.
* Priority: High
* Estimate: 13
6. Solo Trivia
* Description:
As a logged-in user, Thomas wants to be able to play solo trivia so that he can test and gain basketball knowledge as well as earn ACS from answering questions correctly.
* Acceptance Criteria:
Given that I am logged into the app and on the trivia page, if I click on the single-player tab, the app starts a single-player trivia game and modifies my ACS accordingly.
* Priority: Medium
* Estimate: 5
7. Compete against Random Users
* Description:
As a logged-in user, Thomas wants to be able to compete against a random user in his skill level in a trivia contest so that he can compete for ACS against people he does not know.
* Acceptance Criteria:
Given that I am a logged-in user, when I go to the Trivia page, then click on “Multiplayer”, then I will be brought to a trivia game against a random player in my skill level and be given ACS points according to the results when compared to the opponent.
* Priority: Medium
* Estimate: 8
8. Debates
* Description:
As a user, Peter wants to be able to engage in healthy debates with other users in the app so that Peter can gain further knowledge on basketball topics and express his opinions on basketball topics.
* Acceptance Criteria:
Given I am a registered and logged-in user and in the "debates" section, when I want to have a debate with other users, I can post or comment on others' posts or continue a discussion/debate or see other discussions.
* Priority: Medium
* Estimate: 8
9. Challenge Friends
* Description:
As a user with friends on the platform, Thomas wants to be able to invite a friend to a trivia contest so that he can show off and be recognized for his vast sports knowledge.
* Acceptance Criteria:
Given that I am a logged-in user with friends on the app, when I go to the "friends" page, select a friend, and click “play trivia”, the app will send an invitation to the friend and start a trivia game once the friend accepts the invite.
* Priority: Low
* Estimate: 3
10. View Previous Picks
* Description:
As a logged-in user, Peter/Rebecca wants to be able to view past picks of other users and himself/herself, so that he/she can review if he/she has improved or not.
* Acceptance Criteria: As a logged in user, if I go to my profile and choose to view my past picks, I will be shown a list of picks I made in the past years and their results.
* Priority: Low
* Estimate: 3
11. Notifications
* Description:
As a user, Peter would like to be notified if he has/will miss anything on the app (e.g. unread reply to his posts/comments, unanswered debate question, trivia battle invitation, upcoming picks deadlines, picks results) so that he can act accordingly.
* Acceptance Criteria:
Given that I am a logged-in user, when I am not on the app, then I will receive periodic notifications informing me about replies to posts, results from picks, and invites to trivia.
* Priority: Low
* Estimate: 3
12. Share Posts
* Description:
As a user, Peter/Thomas wants to share posts from other social platforms and view the posts of others so that he can be updated on the latest posts from other platforms as well.
* Acceptance Criteria:
Given that I am a registered and logged-in user, when I am on the discussion page, then I can see shared posts of others, and share my own with the option of adding tags so that my posts can be easily found and referred to later.
* Priority: Lowest
* Estimate: 21
Total number of user stories: 12
| 56.436364 | 280 | 0.736147 | eng_Latn | 0.998691 |
faf93085f369074b7579333d11d9e80f6e68107b | 1,576 | md | Markdown | docs/gtk_vs_views_gtk.md | google-ar/chromium | 2441c86a5fd975f09a6c30cddb57dfb7fc239699 | [
"Apache-2.0",
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 2,151 | 2020-04-18T07:31:17.000Z | 2022-03-31T08:39:18.000Z | docs/gtk_vs_views_gtk.md | harrymarkovskiy/WebARonARCore | 2441c86a5fd975f09a6c30cddb57dfb7fc239699 | [
"Apache-2.0",
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 395 | 2020-04-18T08:22:18.000Z | 2021-12-08T13:04:49.000Z | docs/gtk_vs_views_gtk.md | harrymarkovskiy/WebARonARCore | 2441c86a5fd975f09a6c30cddb57dfb7fc239699 | [
"Apache-2.0",
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 338 | 2020-04-18T08:03:10.000Z | 2022-03-29T12:33:22.000Z | # Gtk vs ViewsGtk
## Benefits of ViewsGtk
* Better code sharing. For example, don't have to duplicate tab layout or
bookmark bar layout code.
* Tab Strip
* Drawing
* All the animationy bits
* Subtle click selection behavior (curved corners)
* Drag behavior, including dropping of files onto the URL bar
* Closing behavior
* Bookmarks bar
* drag & drop behavior, including menus
* chevron?
* Easier for folks to work on both platforms without knowing much about the
underlying toolkits.
* Don't have to implement ui features twice.
## Benefits of Gtk
* Dialogs
* Native feel layout
* Font size changes (e.g., changing the system font size will apply to our
dialogs)
* Better RTL (e.g., https://crbug.com/2822 https://crbug.com/5729
https://crbug.com/6082 https://crbug.com/6103 https://crbug.com/6125
https://crbug.com/8686 https://crbug.com/8649)
* Being able to obey the user's system theme
* Accessibility for buttons and dialogs (but not for tabstrip and bookmarks)
* A better change at good remote X performance?
* We still would currently need Pango / Cairo for text layout, so it will be
more efficient to just draw that during the Gtk pipeline instead of with
Skia.
* Gtk widgets will automatically "feel and behave" like Linux. The behavior of
our own Views system does not necessarily feel right on Linux.
* People working on Windows features don't need to worry about breaking the
Linux build.
| 40.410256 | 80 | 0.684645 | eng_Latn | 0.978788 |
faf96c6877e5dcd464fbdc9ce15e6b874ec48986 | 10,084 | md | Markdown | repos/openjdk/remote/8u322-jre-buster.md | Mattlk13/repo-info | 734e8af562852b4d6503f484be845727b88a97ae | [
"Apache-2.0"
] | null | null | null | repos/openjdk/remote/8u322-jre-buster.md | Mattlk13/repo-info | 734e8af562852b4d6503f484be845727b88a97ae | [
"Apache-2.0"
] | 1 | 2020-11-05T19:56:17.000Z | 2020-11-12T13:09:29.000Z | repos/openjdk/remote/8u322-jre-buster.md | Mattlk13/repo-info | 734e8af562852b4d6503f484be845727b88a97ae | [
"Apache-2.0"
] | 1 | 2017-02-09T22:16:59.000Z | 2017-02-09T22:16:59.000Z | ## `openjdk:8u322-jre-buster`
```console
$ docker pull openjdk@sha256:5147aa9a158338cbf87f0388421d8ff34dc98747467ddeecfcd9d0f1367e556b
```
- Manifest MIME: `application/vnd.docker.distribution.manifest.list.v2+json`
- Platforms: 2
- linux; amd64
- linux; arm64 variant v8
### `openjdk:8u322-jre-buster` - linux; amd64
```console
$ docker pull openjdk@sha256:31315f9779b4758de3c20f57ef13d6e392a9a3f9366f0051993ec5bba8bc0121
```
- Docker Version: 20.10.12
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **115.2 MB (115195787 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:db145a7e123c33820e5c6f7f98e45226661026a841a0cab8d68e65e6e19d0d90`
- Default Command: `["bash"]`
```dockerfile
# Tue, 01 Mar 2022 02:13:41 GMT
ADD file:e8b516b464e535b435a6ed8609bac98acc90ee30e2a0667f68932f0d924f6e49 in /
# Tue, 01 Mar 2022 02:13:42 GMT
CMD ["bash"]
# Tue, 01 Mar 2022 06:27:54 GMT
RUN set -eux; apt-get update; apt-get install -y --no-install-recommends ca-certificates curl netbase wget ; rm -rf /var/lib/apt/lists/*
# Tue, 01 Mar 2022 06:28:02 GMT
RUN set -ex; if ! command -v gpg > /dev/null; then apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr ; rm -rf /var/lib/apt/lists/*; fi
# Tue, 01 Mar 2022 14:30:35 GMT
RUN set -eux; apt-get update; apt-get install -y --no-install-recommends bzip2 unzip xz-utils fontconfig libfreetype6 ca-certificates p11-kit ; rm -rf /var/lib/apt/lists/*
# Tue, 01 Mar 2022 14:34:27 GMT
ENV JAVA_HOME=/usr/local/openjdk-8
# Tue, 01 Mar 2022 14:34:28 GMT
RUN { echo '#/bin/sh'; echo 'echo "$JAVA_HOME"'; } > /usr/local/bin/docker-java-home && chmod +x /usr/local/bin/docker-java-home && [ "$JAVA_HOME" = "$(docker-java-home)" ] # backwards compatibility
# Tue, 01 Mar 2022 14:34:28 GMT
ENV PATH=/usr/local/openjdk-8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
# Tue, 01 Mar 2022 14:34:28 GMT
ENV LANG=C.UTF-8
# Tue, 01 Mar 2022 14:34:28 GMT
ENV JAVA_VERSION=8u322
# Tue, 01 Mar 2022 14:34:34 GMT
RUN set -eux; arch="$(dpkg --print-architecture)"; case "$arch" in 'amd64') downloadUrl='https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u322-b06/OpenJDK8U-jre_x64_linux_8u322b06.tar.gz'; ;; 'arm64') downloadUrl='https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u322-b06/OpenJDK8U-jre_aarch64_linux_8u322b06.tar.gz'; ;; *) echo >&2 "error: unsupported architecture: '$arch'"; exit 1 ;; esac; wget --progress=dot:giga -O openjdk.tgz "$downloadUrl"; wget --progress=dot:giga -O openjdk.tgz.asc "$downloadUrl.sign"; export GNUPGHOME="$(mktemp -d)"; gpg --batch --keyserver keyserver.ubuntu.com --recv-keys EAC843EBD3EFDB98CC772FADA5CD6035332FA671; gpg --batch --keyserver keyserver.ubuntu.com --keyserver-options no-self-sigs-only --recv-keys CA5F11C6CE22644D42C6AC4492EF8D39DC13168F; gpg --batch --list-sigs --keyid-format 0xLONG CA5F11C6CE22644D42C6AC4492EF8D39DC13168F | tee /dev/stderr | grep '0xA5CD6035332FA671' | grep 'Andrew Haley'; gpg --batch --verify openjdk.tgz.asc openjdk.tgz; gpgconf --kill all; rm -rf "$GNUPGHOME"; mkdir -p "$JAVA_HOME"; tar --extract --file openjdk.tgz --directory "$JAVA_HOME" --strip-components 1 --no-same-owner ; rm openjdk.tgz*; { echo '#!/usr/bin/env bash'; echo 'set -Eeuo pipefail'; echo 'trust extract --overwrite --format=java-cacerts --filter=ca-anchors --purpose=server-auth "$JAVA_HOME/lib/security/cacerts"'; } > /etc/ca-certificates/update.d/docker-openjdk; chmod +x /etc/ca-certificates/update.d/docker-openjdk; /etc/ca-certificates/update.d/docker-openjdk; find "$JAVA_HOME/lib" -name '*.so' -exec dirname '{}' ';' | sort -u > /etc/ld.so.conf.d/docker-openjdk.conf; ldconfig; java -version
```
- Layers:
- `sha256:1c9a8b42b5780ac49c71f392c9512c0167ecc23de9b30b1b5f38747b73097d1a`
Last Modified: Tue, 01 Mar 2022 02:19:43 GMT
Size: 50.4 MB (50437046 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:163066942b43a00ba7f4674c4c1ca90eccc8d99366a3dc47cb64e06ad79c36e5`
Last Modified: Tue, 01 Mar 2022 06:37:36 GMT
Size: 7.8 MB (7834052 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:cf70e03a8272d87e65c7b1592f97f6e739cf1f5d13cc536670f41c28b086b4cb`
Last Modified: Tue, 01 Mar 2022 06:37:37 GMT
Size: 10.0 MB (9997298 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:d4a0aebff17902b5ae62c7128c8a267d2e6000eccb66e0ba4b6ea1033eb5d2a3`
Last Modified: Tue, 01 Mar 2022 14:53:28 GMT
Size: 5.5 MB (5532021 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:0c64b6508806fe3b66717b7b5aa79a958648317b2967b528f492f335f95e77d2`
Last Modified: Tue, 01 Mar 2022 14:56:47 GMT
Size: 211.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:17ea8df420a28fb3612f5cc6098356be9e1476ccf00ca90535c4a22aebd69669`
Last Modified: Tue, 01 Mar 2022 14:56:52 GMT
Size: 41.4 MB (41395159 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
### `openjdk:8u322-jre-buster` - linux; arm64 variant v8
```console
$ docker pull openjdk@sha256:4708683dacf52474ad28cec8b4ca35d9bc93e10076dfb74820770dd545d0fed9
```
- Docker Version: 20.10.12
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **112.9 MB (112851451 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:63ddd3351d326633b7c7f9646755198cc06f1d298ab81d16364fe2bede0abbcd`
- Default Command: `["bash"]`
```dockerfile
# Tue, 01 Mar 2022 02:11:41 GMT
ADD file:ec3d90624857dbfae217c1372a38966f453fcd51282379652f07d2ccf6fcc67e in /
# Tue, 01 Mar 2022 02:11:42 GMT
CMD ["bash"]
# Tue, 01 Mar 2022 10:35:16 GMT
RUN set -eux; apt-get update; apt-get install -y --no-install-recommends ca-certificates curl netbase wget ; rm -rf /var/lib/apt/lists/*
# Tue, 01 Mar 2022 10:35:21 GMT
RUN set -ex; if ! command -v gpg > /dev/null; then apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr ; rm -rf /var/lib/apt/lists/*; fi
# Tue, 01 Mar 2022 13:59:08 GMT
RUN set -eux; apt-get update; apt-get install -y --no-install-recommends bzip2 unzip xz-utils fontconfig libfreetype6 ca-certificates p11-kit ; rm -rf /var/lib/apt/lists/*
# Tue, 01 Mar 2022 14:03:33 GMT
ENV JAVA_HOME=/usr/local/openjdk-8
# Tue, 01 Mar 2022 14:03:34 GMT
RUN { echo '#/bin/sh'; echo 'echo "$JAVA_HOME"'; } > /usr/local/bin/docker-java-home && chmod +x /usr/local/bin/docker-java-home && [ "$JAVA_HOME" = "$(docker-java-home)" ] # backwards compatibility
# Tue, 01 Mar 2022 14:03:35 GMT
ENV PATH=/usr/local/openjdk-8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
# Tue, 01 Mar 2022 14:03:36 GMT
ENV LANG=C.UTF-8
# Tue, 01 Mar 2022 14:03:37 GMT
ENV JAVA_VERSION=8u322
# Tue, 01 Mar 2022 14:03:52 GMT
RUN set -eux; arch="$(dpkg --print-architecture)"; case "$arch" in 'amd64') downloadUrl='https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u322-b06/OpenJDK8U-jre_x64_linux_8u322b06.tar.gz'; ;; 'arm64') downloadUrl='https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u322-b06/OpenJDK8U-jre_aarch64_linux_8u322b06.tar.gz'; ;; *) echo >&2 "error: unsupported architecture: '$arch'"; exit 1 ;; esac; wget --progress=dot:giga -O openjdk.tgz "$downloadUrl"; wget --progress=dot:giga -O openjdk.tgz.asc "$downloadUrl.sign"; export GNUPGHOME="$(mktemp -d)"; gpg --batch --keyserver keyserver.ubuntu.com --recv-keys EAC843EBD3EFDB98CC772FADA5CD6035332FA671; gpg --batch --keyserver keyserver.ubuntu.com --keyserver-options no-self-sigs-only --recv-keys CA5F11C6CE22644D42C6AC4492EF8D39DC13168F; gpg --batch --list-sigs --keyid-format 0xLONG CA5F11C6CE22644D42C6AC4492EF8D39DC13168F | tee /dev/stderr | grep '0xA5CD6035332FA671' | grep 'Andrew Haley'; gpg --batch --verify openjdk.tgz.asc openjdk.tgz; gpgconf --kill all; rm -rf "$GNUPGHOME"; mkdir -p "$JAVA_HOME"; tar --extract --file openjdk.tgz --directory "$JAVA_HOME" --strip-components 1 --no-same-owner ; rm openjdk.tgz*; { echo '#!/usr/bin/env bash'; echo 'set -Eeuo pipefail'; echo 'trust extract --overwrite --format=java-cacerts --filter=ca-anchors --purpose=server-auth "$JAVA_HOME/lib/security/cacerts"'; } > /etc/ca-certificates/update.d/docker-openjdk; chmod +x /etc/ca-certificates/update.d/docker-openjdk; /etc/ca-certificates/update.d/docker-openjdk; find "$JAVA_HOME/lib" -name '*.so' -exec dirname '{}' ';' | sort -u > /etc/ld.so.conf.d/docker-openjdk.conf; ldconfig; java -version
```
- Layers:
- `sha256:72f0eb753e825356fa0fef854ac259cc8eefdb0f689516f29b13da8b1595c342`
Last Modified: Tue, 01 Mar 2022 02:18:46 GMT
Size: 49.2 MB (49223022 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:93053a54416be8288cbcc300d0a929f1279cceff9eb11ad9c080fe5439d62dbd`
Last Modified: Tue, 01 Mar 2022 10:45:39 GMT
Size: 7.7 MB (7695236 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:2387f0e2dcc6f4271b34d3158d1768015e4424839f06ae428f4e22de8a5c1542`
Last Modified: Tue, 01 Mar 2022 10:45:40 GMT
Size: 9.8 MB (9767253 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:37fd7cb2a892d9067394a0609355afafe5337c3293a821ecfc941c3b47dc3507`
Last Modified: Tue, 01 Mar 2022 14:26:20 GMT
Size: 5.5 MB (5505844 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:570854edc867997edb34fcd6d6f35138c5944bdf2f411fa7fcc7ebf0e687faaf`
Last Modified: Tue, 01 Mar 2022 14:30:04 GMT
Size: 210.0 B
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:4f7bc8e0c6e5caa8e24d82a71d75976cda605cda6ba715f4e3ff1c662562d563`
Last Modified: Tue, 01 Mar 2022 14:30:09 GMT
Size: 40.7 MB (40659886 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
| 72.546763 | 1,771 | 0.731654 | yue_Hant | 0.175092 |
faf99908e977be5a808bdbc37afb2383732ee363 | 822 | md | Markdown | README.md | DaniloLima122/Snake-game | 6cd62e8876ccb185d50f7a45ce557a69b2b97655 | [
"MIT"
] | null | null | null | README.md | DaniloLima122/Snake-game | 6cd62e8876ccb185d50f7a45ce557a69b2b97655 | [
"MIT"
] | null | null | null | README.md | DaniloLima122/Snake-game | 6cd62e8876ccb185d50f7a45ce557a69b2b97655 | [
"MIT"
] | null | null | null | ## Jogo da cobrinha
#### Jogo da cobrinha construído com usando o canvas do HTML e JavaScript.
## Tecnologias utilizadas
- HTML5 e CSS3
- JavaScript
## Começando
Como rodar o projeto na sua máquina:
1º - Baixe o projeto direto pelo link clicando no botão verde escrito "Code" nessa página.
ou instale o Git e digite o seguinte no seu terminal:
~~~shell
git clone https://github.com/DaniloLima122/Snake-game.git
~~~
Caso você não tenha o Git e queira instalar, acesse https://git-scm.com/downloads e baixe-o
2º Acesse a pasta do projeto que você acabou de baixar ou clonar
3º - E para ver o projeto rodando localize o arquivo index.html e abra ele no seu navegador. Divirta-se!!.
## Contribuições
Fique a vontade para contribuir ou notificar sobre bugs e dicas para melhorá-lo!
## Licença
- MIT | 22.833333 | 106 | 0.746959 | por_Latn | 0.999632 |
faf9d4e88c3eabdb5b98e8f441e17458309b3b33 | 10,793 | md | Markdown | docs/dea/database-experimentation-assistant-configure-replay.md | IgorBasmanov/sql-docs.ru-ru | 6b10902df1c7ed345d7eeb65a22360a7158ddea6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/dea/database-experimentation-assistant-configure-replay.md | IgorBasmanov/sql-docs.ru-ru | 6b10902df1c7ed345d7eeb65a22360a7158ddea6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/dea/database-experimentation-assistant-configure-replay.md | IgorBasmanov/sql-docs.ru-ru | 6b10902df1c7ed345d7eeb65a22360a7158ddea6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Настройка воспроизведения в помощнике по базе данных службы "Экспериментирование" для обновления до SQL Server
description: Настройка воспроизведения в помощнике по базе данных службы "Экспериментирование"
ms.custom: ''
ms.date: 10/22/2018
ms.prod: sql
ms.prod_service: dea
ms.suite: sql
ms.technology: dea
ms.tgt_pltfrm: ''
ms.topic: conceptual
author: HJToland3
ms.author: ajaykar
ms.reviewer: mathoma
ms.openlocfilehash: 9166265dad077d4a3e83cc300868607d001ef233
ms.sourcegitcommit: b2464064c0566590e486a3aafae6d67ce2645cef
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 07/15/2019
ms.locfileid: "68058962"
---
# <a name="configure-replay-in-database-experimentation-assistant"></a>Настройка воспроизведения в помощнике по базе данных службы "Экспериментирование"
Помощник по базе данных службы "Экспериментирование" (веб) использует средства распределенного воспроизведения из экземпляра SQL Server для воспроизведения записанной трассировки в обновленной тестовой среде. Мы советуем применить этот тестовый запуск с помощью небольших трассировки файла перед выполнением полного воспроизведения для обеспечения правильного воспроизведения запросов.
## <a name="distributed-replay-requirements"></a>Требования распределенного воспроизведения
- Дополнительные 78% места на жестком диске требуется для создания файлов IRF на компьютере контроллера распределенного воспроизведения.
- 200 МБ или 512 МБ — размер смены идеальный трассировки для трассировки производительности или производства.
- Минимальные требования к ЦП и ОЗУ для компьютеров, контроллера и клиента распределенного воспроизведения — это для одного ядра ЦП 3,5 ГБ ОЗУ.
- Время воспроизведения приблизительно принимает 1,55 раз больше, чем время записи, так как один контроллер и четыре дочерних машины используются для воспроизведения трассировки рабочей.
- При использовании нашей «опубликованные» версии рабочей среде и файлов определения трассировки производительности и фильтры определение трассировки производительности, данные трассировки для одной базы данных, интерес, анализ показывает, что **трассировки производительности** размер около 15 раз выше, чем **трассировки рабочей** размер.
## <a name="set-up-a-virtual-network-or-domain"></a>Настройка виртуальной сети или домена
Распределенное воспроизведение требует использования общих учетных записей между компьютерами. Из-за этого требования, а также по соображениям безопасности рекомендуется запускать распределенного воспроизведения, в виртуальной сети или сети управлением домена:
- Создание контроллера и клиентских компьютеров в среде.
- Убедитесь, что компьютеры контроллера и клиента можно проверить связь с друг с другом по сети.
- Клиентских компьютеров распределенного воспроизведения должны иметь подключение к целевому компьютеру воспроизведения под управлением SQL Server.
## <a name="set-up-the-controller-service"></a>Настроить службу контроллера
Чтобы настроить службу контроллера:
1. Установите контроллер распределенного воспроизведения с помощью установщика SQL Server. Если вы пропустили шаг мастера установщик SQL Server, который настраивает контроллер распределенного воспроизведения, можно настроить через файл конфигурации контроллера. При обычной установке, файл конфигурации расположен в C:\Program Files (x86) \Microsoft SQL Server\<версии\>\Tools\DReplayController\DReplayController.config.
1. Журналы контроллера распределенного воспроизведения находятся в C:\Program Files (x86) \Microsoft SQL Server\<версии\>\Tools\DReplayController\Log.
1. Откройте оснастку Services.msc и перейти к **контроллера распределенного воспроизведения SQL Server** службы.
1. Щелкните правой кнопкой мыши в службе, а затем выберите **свойства**. Настройка учетной записи службы учетную запись, которая являются общими для контроллера и клиентских компьютеров в сети.
1. Выберите **ОК** закрыть **свойства** окна.
1. Перезапустите **контроллера распределенного воспроизведения SQL Server** службы с помощью команды Services.msc. Вы также выполните следующие команды в командной строке, чтобы перезапустить службу:<br/>
`NET STOP "SQL Server Distributed Replay Controller"`<br/>
`NET START "SQL Server Distributed Replay Controller"`
1. Дополнительные параметры конфигурации, см. в разделе [Настройка распределенного воспроизведения](https://docs.microsoft.com/sql/tools/distributed-replay/configure-distributed-replay).
## <a name="configure-dcom"></a>Настройка DCOM
Эта конфигурация требуется только на компьютере контроллера.
1. Откройте dcomcnfg.exe.
1. Разверните **службы компонентов** > **компьютеров** > **компьютер** > **DCOM Config**.
1. В разделе **DCOM Config**, щелкните правой кнопкой мыши **DReplayController**, а затем выберите **свойства**.
1. Перейдите на вкладку **Безопасность** .
1. В разделе **разрешения запуска и активации**выберите **Настройка**, а затем выберите **изменить**.
1. Добавьте пользователя, и начинается воспроизведение. Предоставьте разрешения локальный запуск и Локальная активация пользователя. Если пользователь планирует запустить или удаленной активации, предоставляются разрешения на удаленный запуск и удаленная активация.
1. Выберите **ОК** чтобы зафиксировать изменения и вернуться к **безопасности** вкладки.
1. В разделе **разрешения на доступ**выберите **Настройка**, а затем выберите **изменить**.
1. Добавьте пользователя, и начинается воспроизведение. Предоставьте разрешения на доступ для локального пользователя. Если пользователь планирует для удаленного доступа к службе контроллера, предоставляются разрешения удаленного доступа.
1. Выберите **ОК** чтобы зафиксировать изменения и вернуться к **безопасности** вкладки.
1. Выберите **ОК** для фиксации изменений.
1. Перезапустите службу контроллера распределенного воспроизведения SQL Server с помощью команды Services.msc. Вы также выполните следующие команды в командной строке, чтобы перезапустить службу:<br/>
`NET STOP "SQL Server Distributed Replay Controller"`<br/>
`NET START "SQL Server Distributed Replay Controller"`
## <a name="set-up-the-client-service"></a>Настройка службы клиента
Перед настройкой службы клиента с помощью средства работы с сетью, такие как ping убедитесь, что машины контроллере и клиенте могут взаимодействовать.
1. Установка клиента распределенного воспроизведения с помощью установщика SQL Server.
1. Откройте оснастку Services.msc и перейдите к службе клиента распределенного воспроизведения SQL Server.
1. Щелкните правой кнопкой мыши в службе, а затем выберите **свойства**. Настройка учетной записи службы учетную запись, которая часто на компьютерах контроллера и клиента в сети.
1. Выберите **ОК** закрыть **свойства** окна. Если вы пропустили шаг мастера установки SQL Server для настройки клиента распределенного воспроизведения, его можно настроить в файле конфигурации. При обычной установке, файл конфигурации расположен в C:\Program Files (x86) \Microsoft SQL Server\<версии\>\Tools\DReplayClient\DReplayClient.config.
1. Убедитесь, что файл DReplayClient.config содержит имя компьютера контроллера как его контроллер для регистрации.
1. Перезапустите службу клиента распределенного воспроизведения SQL Server с помощью команды Services.msc. Вы также выполните следующие команды из командной строки, чтобы перезапустить службу:<br/>
`NET STOP "SQL Server Distributed Replay Client"`<br/>
`NET START "SQL Server Distributed Replay Client"`
1. Журналы контроллера распределенного воспроизведения находятся в C:\Program Files (x86) \Microsoft SQL Server\<версии\>\Tools\DReplayClient\Log. В журналах указывается ли клиент может зарегистрироваться с контроллером.
1. При успешном выполнении конфигурации журнала отображается сообщение «зарегистрирован с контроллером < имя контроллера\>«.
1. Дополнительные параметры конфигурации, см. в разделе [Настройка распределенного воспроизведения](https://docs.microsoft.com/sql/tools/distributed-replay/configure-distributed-replay).
## <a name="set-up-distributed-replay-administration-tools"></a>Настройка средства администрирования распределенного воспроизведения
Чтобы быстро проверить правильность работы в среде распределенного воспроизведения можно использовать средства администрирования распределенного воспроизведения. Тестирование конфигурации может быть особенно полезно в среде, в которой несколько клиентских компьютеров зарегистрированных в контроллере. Может потребоваться установить SQL Server Management Studio (SSMS) для получения средств администрирования.
1. Перейдите в папку установки SSMS и найдите dreplay.exe средство администрирования распределенного воспроизведения и его зависимые компоненты.
1. Откройте окно командной строки и выполните `dreplay.exe status -f 1`.
1. Если приведенные выше действия выполняются успешно, в выходных данных консоли означает, что контроллер может видеть своих клиентов в `READY` состояние.
## <a name="configure-the-firewall-for-remote-distributed-replay-access"></a>Настройка брандмауэра для удаленного доступа распределенного воспроизведения
Удаленный доступ к распределенного воспроизведения требует открытия портов, которые видимы в домене или виртуальной сети.
1. Откройте **брандмауэра Windows** с **повышенной безопасности**.
1. Перейдите к **правила для входящего трафика**.
1. Создать новое правило брандмауэра для входящих подключений для программы C:\Program Files (x86) \Microsoft SQL Server\<версии\>\Tools\DReplayController\DReplayController.exe.
1. Разрешите режим домена доступ ко всем портам для DReplayController.exe иметь возможность удаленно взаимодействовать со службой контроллера.
1. Сохраните правило.
## <a name="set-up-target-computers"></a>Настройка целевых компьютерах
Два воспроизведения необходимы для запуска A / B-тестирования или эксперимента. То есть может потребоваться два отдельных экземпляра из экземпляров SQL Server для сценария миграции.
Можно также установить две версии экземпляров SQL Server на одном компьютере. Будьте осторожны — убедиться, что экземпляры полностью изолированы во время воспроизведения.
Для каждого воспроизведения необходимо выполнить следующие действия:
1. Восстановите резервную копию базы данных.
1. Предоставьте разрешения для пользователя учетной записи службы клиента для доступа к базе данных в экземпляре SQL Server. Разрешения требуются для запросов, которые будут выполнены в экземпляре SQL Server.
1. Запустите воспроизведение.
## <a name="next-steps"></a>Следующие шаги
- Чтобы узнать, как для воспроизведения записанной трассировки в обновленной тестовой среде, см. в разделе [воспроизведения трассировки](database-experimentation-assistant-replay-trace.md).
- 19-минутный введение Инициатив и демонстрации в следующем видео:
> [!VIDEO https://channel9.msdn.com/Shows/Data-Exposed/Introducing-the-Database-Experimentation-Assistant/player]
| 84.320313 | 420 | 0.820995 | rus_Cyrl | 0.963592 |
fafa174a0e45e32403d31d6d652e010210271a1b | 797 | md | Markdown | src/Multiplicity of Numbers/README.md | Pustur/edabit-js-challenges | 1539fa6eb2ef6e1f61cb4cc02ed3a3eb382bae5b | [
"MIT"
] | 7 | 2019-11-10T21:42:30.000Z | 2022-02-17T14:26:03.000Z | src/Multiplicity of Numbers/README.md | Pustur/edabit-js-challenges | 1539fa6eb2ef6e1f61cb4cc02ed3a3eb382bae5b | [
"MIT"
] | null | null | null | src/Multiplicity of Numbers/README.md | Pustur/edabit-js-challenges | 1539fa6eb2ef6e1f61cb4cc02ed3a3eb382bae5b | [
"MIT"
] | 3 | 2020-05-11T11:01:37.000Z | 2021-05-07T09:48:10.000Z | # Multiplicity of Numbers
`Arrays` `Language Fundamentals`
[View on Edabit](https://edabit.com/challenge/PgNvoxjjy7Gx6zDni)
Write a function that returns an array of elements `[number, multiplicity]`. The `multiplicity` of a number refers to the number of times it occurs in the array.
To illustrate:
```js
[5, 5, 1, 1, 5, 5, 3];
[
[5, 4],
[1, 2],
[3, 1],
];
// Since 5 appears 4 times, 1 appears twice, and 3 appears once.
```
The final array should only include unique elements, and the elements should be ordered by when they first appeared in the original array.
### Examples
```js
multiplicity([1, 1, 1, 2, 2, 3]) ➞ [[1, 3], [2, 2], [3, 1]]
multiplicity([1, 1, 1, 1, 1]) ➞ [[1, 5]]
multiplicity([1, 5, 4, 3, 2]) ➞ [[1, 1], [5, 1], [4, 1], [3, 1], [2, 1]]
```
### Notes
N/A
| 21.540541 | 161 | 0.627353 | eng_Latn | 0.986647 |
fafaa66efe376ef4f012b0c45eda0f0d9f1318b5 | 5,730 | md | Markdown | README.md | liyasthomas/mnmlurl-extension | cf99d1d1151d877a668d4223e132be0838eaf025 | [
"MIT"
] | 26 | 2019-04-10T18:56:16.000Z | 2021-11-23T23:28:12.000Z | README.md | liyasthomas/mnmlurl-extension | cf99d1d1151d877a668d4223e132be0838eaf025 | [
"MIT"
] | 4 | 2019-07-11T03:17:56.000Z | 2020-02-18T00:53:38.000Z | README.md | liyasthomas/mnmlurl-extension | cf99d1d1151d877a668d4223e132be0838eaf025 | [
"MIT"
] | 7 | 2019-07-13T06:39:34.000Z | 2021-09-14T05:50:10.000Z | ```
When I wrote this, only God and I understood what I was doing. Now, only God knows.
```
<div align="center">
<a href="https://liyas-thomas.firebaseapp.com"><img src="https://raw.githubusercontent.com/liyasthomas/templates/master/assets/logo.gif" alt="Liyas Thomas" width="200"></a>
<br>
<h1>Liyas Thomas</h1>
<sub>Built with ❤︎ by
<a href="https://github.com/liyasthomas">liyasthomas</a> and
<a href="https://github.com/liyasthomas/mnmlurl-extension/graphs/contributors">contributors</a>
</sub>
</div>
---
[](https://travis-ci.org/liyasthomas/mnmlurl-extension) [](https://github.com/liyasthomas/mnmlurl-extension/releases/latest) [](https://github.com/liyasthomas/mnmlurl-extension/archive/master.zip) [](https://github.com/liyasthomas/mnmlurl-extension/blob/master/LICENSE) [](https://github.com/liyasthomas/mnmlurl-extension/issues) [](https://mnmlurl.ml) [](https://www.paypal.me/liyascthomas)
# <img src="https://raw.githubusercontent.com/liyasthomas/mnmlurl-extension/master/icons/icon-48x48.png" alt="mnmlurl-extension" width="32"> mnmlurl-extension
### :information_desk_person: Browser extension for mnmlurl by [Liyas Thomas](https://github.com/liyasthomas)
<div align="center">
<br>
<img src="icons/screely.png" alt="mnmlurl-extension" width="100%">
<img src="icons/screely2.png" alt="mnmlurl-extension" width="100%">
<br>
</div>
### Features :sparkles:
:eyeglasses: **Free and open source.**: [mnmlurl](https://mnmlurl.ml) is a modern URL shortener with support for custom alias.
:globe_with_meridians: **Custom alias support**: Choose your own alias or get a random one!
:electric_plug: **Lighting fast**: No ads, no logging, no BS!
:zap: **Performance**: Uses [jsonstore.io](https://www.jsonstore.io) for data storage.
:heart: **Free**: It's free and always will be.
---
## Getting started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
### Prerequisites
What things you need to install the extension and how to install them.
* Internet connection
* Browser
* [Wonder](https://en.wikipedia.org/wiki/Wonder_(emotion))! :heart:
### Installing
1. Download the [latest release](https://github.com/liyasthomas/mnmlurl-extension/releases/latest) on this repository.
2. Unzip.
3. Load extension locally on your computer:
> #  **Chrome:**
1. Visit: chrome://extensions
2. Enable "Developer mode".
3. Click: Load unpacked > choose extension's folder > Ok.
> #  **Firefox:** [Download add-on](https://addons.mozilla.org/en-US/firefox/addon/mnmlurl)
1. Visit: about:debugging
2. Click: Load Temporary Add-on > choose manifest.json within the extension's folder > Ok.
> #  **Opera:**
1. Visit: opera://extensions
2. Enable "Developer mode".
3. Click: Load unpacked > choose extension's folder > Ok.
> #  **Edge:**
1. Visit: about:flags
2. Check the "Enable extension developer features".
3. Click on "…" in the Edge’s navigation bar > Extensions.
4. Click: Load extension > choose extension's folder > Ok.
4. Done!
---
## Built with
* **[Chromium](https://github.com/chromium/chromium)** - Thanks for being so fast!
* HTML - For the web framework
* CSS - For styling components
* JavaScript - For magic!
---
## Contributing
Please read [CONTRIBUTING](CONTRIBUTING.md) for details on our [CODE OF CONDUCT](CODE_OF_CONDUCT.md), and the process for submitting pull requests to us.
---
## Continuous Integration
We use [Travis CI](https://travis-ci.com) for continuous integration. Check out our [Travis CI Status](https://travis-ci.org/liyasthomas/mnmlurl-extension).
---
## Versioning
This project is developed by [Liyas Thomas](https://github.com/liyasthomas) using the [Semantic Versioning specification](https://semver.org). For the versions available, see the [releases on this repository](https://github.com/liyasthomas/mnmlurl-extension/releases).
---
## Change log
See the [CHANGELOG](CHANGELOG.md) file for details.
---
## Authors
### Lead Developers
* [**Liyas Thomas**](https://github.com/liyasthomas) - *Author*
### Testing and Debugging
* [Liyas Thomas](https://github.com/liyasthomas)
### Contributors
* [Liyas Thomas](https://github.com/liyasthomas)
### Thanks
* [Google](https://www.google.com) - For samples
See the list of [contributors](https://github.com/liyasthomas/mnmlurl-extension/graphs/contributors) who participated in this project.
---
## License
This project is licensed under the [MIT License](https://opensource.org/licenses/MIT) - see the [LICENSE](LICENSE) file for details.
---
## Acknowledgments
* Hat tip to anyone who's code was used
* Inspirations:
* [Kutt.it](https://kutt.it/)
| 38.456376 | 998 | 0.733159 | eng_Latn | 0.422233 |
fafae146e9e3554c6ee3df25ef5cf943c3167f32 | 89 | md | Markdown | machine.md | d3n-nc/d3n-nc.github.io | f694c6fd498cd66883f7c9e98fb70b9e8c2d143b | [
"MIT"
] | null | null | null | machine.md | d3n-nc/d3n-nc.github.io | f694c6fd498cd66883f7c9e98fb70b9e8c2d143b | [
"MIT"
] | null | null | null | machine.md | d3n-nc/d3n-nc.github.io | f694c6fd498cd66883f7c9e98fb70b9e8c2d143b | [
"MIT"
] | null | null | null | # Work
Станок
## 2019
2019-10-14 - KAFO VMC-116B, Siemens 828D (НПП "Старт", 1 день)
| 11.125 | 62 | 0.640449 | kor_Hang | 0.218192 |
269e7f2d716b1e672e1067c7b1d4bce5e5d29ba1 | 756 | md | Markdown | joplin-sync/79b9a533fa9b4fefa1e9383017534ec2.md | blake2002/xiezuo | bd301ddd622681194545cd2fbbae3fd8e91ee70a | [
"Apache-2.0"
] | null | null | null | joplin-sync/79b9a533fa9b4fefa1e9383017534ec2.md | blake2002/xiezuo | bd301ddd622681194545cd2fbbae3fd8e91ee70a | [
"Apache-2.0"
] | null | null | null | joplin-sync/79b9a533fa9b4fefa1e9383017534ec2.md | blake2002/xiezuo | bd301ddd622681194545cd2fbbae3fd8e91ee70a | [
"Apache-2.0"
] | null | null | null | id: 79b9a533fa9b4fefa1e9383017534ec2
parent_id: b71a74e121604ab8ad673fe63146c6cd
item_type: 1
item_id: 7db43430f3134cdd9561739ef15e092d
item_updated_time: 1637244532109
title_diff: "[]"
body_diff: "[{\"diffs\":[[0,\"ce sheet\"],[1,\" 是以资产=负责+所有者权益为平衡关系，反映企业在某一特定日期财务状况的报表\\\n 1. 资产 是企业因过去的交易或事项所形成的并由企业拥有或控制，能以货币计量，预期会给企业带来经济利益的资源\\\n 2. 债权\\\n 3. 其他权利\"],[0,\"\\\n - 利润表\"]],\"start1\":1481,\"start2\":1481,\"length1\":16,\"length2\":135},{\"diffs\":[[0,\"holder‘ \"],[1,\"equity\"],[0,\"\\\n+ 报表附注\\\n\"]],\"start1\":1761,\"start2\":1761,\"length1\":16,\"length2\":22}]"
metadata_diff: {"new":{},"deleted":[]}
encryption_cipher_text:
encryption_applied: 0
updated_time: 2021-11-18T14:17:26.061Z
created_time: 2021-11-18T14:17:26.061Z
type_: 13 | 58.153846 | 396 | 0.690476 | yue_Hant | 0.100836 |
269f72d400a0b13c95a4a2fe27db4b7939140ed1 | 402 | md | Markdown | README.md | Ahmedc2l/one-pin | e9f0e9b57b031e4f3c4ca7edbd73dfd72917c571 | [
"MIT"
] | null | null | null | README.md | Ahmedc2l/one-pin | e9f0e9b57b031e4f3c4ca7edbd73dfd72917c571 | [
"MIT"
] | null | null | null | README.md | Ahmedc2l/one-pin | e9f0e9b57b031e4f3c4ca7edbd73dfd72917c571 | [
"MIT"
] | null | null | null | # One Pin
One Pin is an Android Game where the player should shoot at a rotating square with as much pins as he could without any pins intersecting.
showcasing:
- Canvas :zap:
- Spawn Points :running:
- Rotations :star:
- Events :ok_hand:
## Screenshots
Game |
:-------------------------:|
 |
License
----
MIT
| 19.142857 | 138 | 0.624378 | eng_Latn | 0.953096 |
269fc6ed3b2990d59671946ad6bf40bedc67959d | 773 | md | Markdown | example/en/views/UE4/DRAFT-build-plugin-for-source-built-engine.md | Zenahr/personal-blog | ca15a7a13d16d55461171ffc6a0c2c0fc80405c3 | [
"MIT"
] | null | null | null | example/en/views/UE4/DRAFT-build-plugin-for-source-built-engine.md | Zenahr/personal-blog | ca15a7a13d16d55461171ffc6a0c2c0fc80405c3 | [
"MIT"
] | null | null | null | example/en/views/UE4/DRAFT-build-plugin-for-source-built-engine.md | Zenahr/personal-blog | ca15a7a13d16d55461171ffc6a0c2c0fc80405c3 | [
"MIT"
] | null | null | null | ---
title: How To Build A Plugin From GitHub For Your Engine Built From Source
date: 2019-08-08
categories:
- UE4
- Guide
tags:
- Game Development
- Advanced
isShowComments: false
publish: false
---
below the fold
::: tip TIP
some content
:::
::: warning Warning
This is a warning
:::
::: danger
This is a dangerous warning
:::
::: theorem 牛顿第一定律
假若施加于某物体的外力为零，则该物体的运动速度不变。
::: right
来自 [维基百科](https://zh.wikipedia.org/wiki/%E7%89%9B%E9%A1%BF%E8%BF%90%E5%8A%A8%E5%AE%9A%E5%BE%8B)
:::
::: details On Windows
这是一个详情块，在 IE / Edge 中不生效
:::
::: details On Linux
这是一个详情块，在 IE / Edge 中不生效
:::
::: details On Mac
这是一个详情块，在 IE / Edge 中不生效
:::
@flowstart
cond=>condition: Process?
process=>operation: Process
e=>end: End
cond(yes)->process->e
cond(no)->e
@flowend | 13.101695 | 95 | 0.679172 | yue_Hant | 0.608315 |
26a0a9aac1d5cf6d095f9a97f4ba7ece1c13b738 | 14 | md | Markdown | docs/en-us/eosforce_http_api_develop.md | eostio/Documentation | 430ac151dc01672009e36b358feba5909e590c2a | [
"Apache-2.0"
] | 1 | 2018-08-08T12:30:30.000Z | 2018-08-08T12:30:30.000Z | docs/zh-cn/eosforce_http_api_develop.md | eostio/Documentation | 430ac151dc01672009e36b358feba5909e590c2a | [
"Apache-2.0"
] | 1 | 2018-07-30T06:10:16.000Z | 2018-08-01T06:07:54.000Z | docs/zh-cn/eosforce_http_api_develop.md | eostio/Documentation | 430ac151dc01672009e36b358feba5909e590c2a | [
"Apache-2.0"
] | null | null | null | # HTTP API请求流程 | 14 | 14 | 0.785714 | kor_Hang | 0.990196 |
26a1b3f5bb83e240c60df5adde208d8143f28346 | 573 | md | Markdown | src/main/README.md | BlkPingu/VoiceControl | f6a32d4307812c19d82cc997433271cc5a282f2b | [
"Apache-2.0"
] | null | null | null | src/main/README.md | BlkPingu/VoiceControl | f6a32d4307812c19d82cc997433271cc5a282f2b | [
"Apache-2.0"
] | null | null | null | src/main/README.md | BlkPingu/VoiceControl | f6a32d4307812c19d82cc997433271cc5a282f2b | [
"Apache-2.0"
] | null | null | null | #### interfaces
**transcriberinterface:** provide method stubs for what transcriber does. at least a `transcribe()` method
**processors:** provide methods that process the transcriptions via NLP
#### transcribers:
- batch transcriber transcribes a batch of string
- streaming transcriber transcribers a stream of strings
#### processors
- processes with basic recognition
- processes with advanced recorgnition
#### `Application.py`
singleton that executes the classes in the combination they are wanted
#### `main.py`
loads `application.py` with args
| 17.363636 | 106 | 0.750436 | eng_Latn | 0.997591 |
26a2718905e713d3eb1ec62c44647eecea0c8f11 | 1,918 | md | Markdown | src/ko/2018-03/10/01.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 68 | 2016-10-30T23:17:56.000Z | 2022-03-27T11:58:16.000Z | src/ko/2018-03/10/01.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 367 | 2016-10-21T03:50:22.000Z | 2022-03-28T23:35:25.000Z | src/ko/2018-03/10/01.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 109 | 2016-08-02T14:32:13.000Z | 2022-03-31T10:18:41.000Z | ---
title: 3차 선교 여행
date: 01/09/2018
---
### TMI 실천해 보세요
- 107\. 이웃의 이름을 묻고 그를 위해 기도하세요.
- 108\. 카톡 친구에게 용기가 되는 성경절을 보내세요.
- 109\. 마음이 열린 이에게 찬양 CD나 MP3를 구입하여 선물하세요.
### 연구 범위
행 18:24~28, 행 19장, 행 20:7~12, 15~27, 고후 4:8~14, 행 21:1~15
### 기 억 절
누가는 바울의 3차 여행을 다소 성급하게 시작된 것처럼 묘사한다. 바
울은 자신의 선교 중심지인 안디옥에서 얼마 동안 머문 뒤에 다시 여정에
올라 “갈라디아와 브루기아 땅을 차례로 다니며 모든 제자를 굳건하게”
(행 18:23) 했다. 이 한 문장 속에서 그가 다닌 길은 무려 240㎞가 넘는다.
그럴 수밖에 없었던 것은 이 여행의 초점이 에베소에 맞춰져 있었기 때
문이다. 바울은 3차 여행 중 다른 도시에서보다 많은 시간을 에베소에 할
애한다. 전도의 관점에서 에베소에서의 사역은 결실이 풍성했다. 바울이
전하는 복음은 소아시아 전 지역에 영향을 끼쳤다(행 19:10, 26). 아마도
이 기간에 바울의 동역자였던 에바브라의 노력으로(골 1:7, 몬 23) 골로새,
히에라볼리, 라오디게아 교회가 설립되었을 것이다(골 4:12~13).
우리는 이것이 사도행전에 기록된 바울의 여정 중에 그가 자유인으로
다니는 마지막 여행임을 주목해야 한다. 물론 누가는 나중에 죄수의 신분
으로 로마를 향해 가는 바울의 여정도 소개할 것이다.
### TMI Time
#### ※ 학습 목표
- **깨닫기**: 기꺼이 자신을 바쳐서 하나님 나라의 복음을 전
했던 바울의 삶을 이해한다.
- **느끼기**: 바울처럼 하나님을 섬기는 삶에서 인생의 목적
을 깨닫기를 열망한다.
- **행하기**: 희생이 너무 크다고 생각되면 바울을 기억하며
온 힘을 다해서 하나님의 부르심에 충성한다.
#### TMI 안으로 : 안교소그룹이 함께 서로를 돌보고 연합함
- 1\. 서로 인사를 나누고
손님을 환영해 줍니다.
- 2\. 출석과 공부를 확인하고
안교헌금을 걷습니다.
- 3\. 결석자와 구도자에
대한 보고를 듣고
방문 계획을 세웁니다.
#### TMI 위로 : 안교소그룹이 함께 말씀과 기도로 하나님께 나아감
`➊ 그대는 걸어서 또는 자전거로 얼마나 멀리까지 가 보았습니까?`
`➋ 바울의 세 번째 선교 여행의 주된 목적지는 어디였습니까?(행 19:1)`
`➌ 바울은 에베소에서 어떻게 사역했으며 어떤 특별한 성과를 거두었습니까?(행 19:9, 10)`
`➍ 에베소의 일화처럼 복음이 지역 사회에 강력한 감화를 끼칠 때에 어떤 변화가 일어날 수 있다고
생각합니까?(행 19:12~41)`
`➎ 그대는 에베소 교회 장로들과 작별하는 바울에게서 진정한 영적 지도자에게 있어야 할 어떤 면모
를 보게 됩니까?(행 20:28~31)`
`➏ 우리 교회가 이 지역을 복음화하기 위해서 차근차근 시도해야 할 일들은 무엇일까요?`
**결론**: 바울의 3차 선교 여행은 그가 장차 받을 고난의 원인이 되었습니다. 그럼에도 그는 줄기차게 자
신의 사명을 완수하며 죽음도 그를 단념시키지 못할 것이라고 고백했습니다.
#### TMI 밖으로 : 안교소그룹이 함께 지역사회에 복음을 전하고 봉사함
`➊ ‘내가 실천한 TMI 활동 : (___)’을 적고 함께 나눕니다.`
`➋ 안식일학교·선교부 홈페이지 ‘TMI Time 게시판’에 우리 활동 소식을 사진과 함께 올립니다.`
`➌ 우리가 오늘 오후에 실천할 TMI 활동 계획을 구체적으로 안내하고 함께 기도합니다.`
**TMI**(Total Member Involvement)는 전 교인이 ‘**모두 참여 함께 나눔**’의 정신으로 실천하는 ‘**관계 중심 생활 전도**’ 운동입니다. | 22.302326 | 94 | 0.637643 | kor_Hang | 1.00001 |
26a2dee7a685bef50603619bdf84d64af9bf52fd | 6,978 | md | Markdown | README.md | jam-tech/elm-neo | 875728a51910744e46840f68f2fd421423d191f9 | [
"BSD-3-Clause"
] | null | null | null | README.md | jam-tech/elm-neo | 875728a51910744e46840f68f2fd421423d191f9 | [
"BSD-3-Clause"
] | 1 | 2018-05-27T14:28:27.000Z | 2018-05-27T14:28:27.000Z | README.md | kingsleyh/elm-neo | 875728a51910744e46840f68f2fd421423d191f9 | [
"BSD-3-Clause"
] | null | null | null | # Elm Neo
[](https://opensource.org/licenses/BSD-3-Clause)
This project provides elm tools for the Neo blockchain
## Usage
There are 6 areas:
* Private and public keys
* Accounts
* Transactions
* Signatures
* Contracts
* Format validations
* Ciphers
### Private and public keys
* generating keys produces a task so needs to be handled in an update function e.g.
```
genKeyMsg : Cmd Msg
genKeyMsg =
Task.perform CreateWalletResponse Neo.generateHexPrivateKey
update msg model =
case msg of
CreateWalletResponse hexPrivateKey ->
(model, Cmd.none)
```
* all the other functions return a Result **Error** **Item**
```
import Neo as Neo
-- generating private keys
Neo.generateBinaryPrivateKey
Neo.generateHexPrivateKey
-- getting a wif from a private key
Neo.getWIFFromBinaryPrivateKey
Neo.getWIFFromHexPrivateKey
-- getting a private key from a wif
Neo.getBinaryPrivateKeyFromWIF
Neo.getHexPrivateKeyFromWIF
-- get binary public key from private key
Neo.getBinaryPublicKeyFromHexPrivateKey hexPrivateKey True
Neo.getBinaryPublicKeyFromBinaryPrivateKey binaryPrivateKey True
-- get hex public key from private key
Neo.getHexPublicKeyFromBinaryPrivateKey binaryPrivateKey True
Neo.getHexPublicKeyFromHexPrivateKey hexPrivateKey True
```
* Key conversions
```
Neo.getBinaryPrivateKeyFromHexPrivateKey hexPrivateKey
Neo.getHexPrivateKeyFromBinaryPrivateKey binaryPrivateKey
Neo.getBinaryPublicKeyFromHexPublicKey hexPublicKey
Neo.getHexPublicKeyFromBinaryPublicKey binaryPublicKey
```
### Accounts
* all the functions here return a Result **Error** **Item**
```
import Neo as Neo
-- get wallet account from a private key
Neo.getAccountFromBinaryPrivateKey binaryPrivateKey
Neo.getAccountFromHexPrivateKey hexPrivateKey
-- get wallet account from a public key
Neo.getAccountFromBinaryPublicKey binaryPublicKey
Neo.getAccountFromHexPublicKey hexPublicKey
-- returns Account
type alias Account =
{ binaryPrivateKey : BinaryPrivateKey
, hexPrivateKey : HexPrivateKey
, binaryPublicKey : BinaryPublicKey
, hexPublicKey : HexPublicKey
, publicKeyHash : PublicKeyHash
, programHash : ProgramHash
, address : Address
}
```
### Transactions
* all the functions here return a Result **Error** **Item**
```
import Neo as Neo
-- create transfer data
transactionTransferData : AssetName -> AssetId -> Float -> TransactionData
transactionTransferData assetName assetId amount =
let
fromHexPrivateKey =
getHexPrivateKeyFromWIF "L1QqQJnpBwbsPGAuutuzPTac8piqvbR1HRjrY5qHup48TBCBFe4g"
fromAccount =
getAccountFromHexPrivateKey (fromHexPrivateKey)
toAddress =
"ALfnhLg7rUyL6Jr98bzzoxz5J7m64fbR4s"
balance =
getUnspentAmount
coinData =
CoinData assetId orderedUnspentTransactions balance assetName
in
getTransferData coinData fromAccount.binaryPublicKey toAddress amount
orderedUnspentTransactions : Transactions
orderedUnspentTransactions =
[ Transaction 0 "2570f939f56afa58b2e1a0bca2d092d6b6d2f73dce26089a768bee7fa61875fd" 10.4
, Transaction 0 "32a741037084da00d46798f78c2c03f73dd2f760f5ad3d47bca6805a5be421dc" 7.0
, Transaction 0 "9c295ac33a7948cf80fff907991bbbbad690850d15fb1529e986644a4926e38b" 3.343242
, Transaction 0 "704c4d20b8072da67d954ab3ea1fd36f75d0d74445184e8e25817629a7945b6f" 2.89898
, Transaction 0 "3372a67a1b5a382c4ad2caa4ebebd494b0fe944049f55b0b6e62569de1a7841a" 1.56536
]
-- relevant type alias are below:
type alias CoinData =
{ assetId : AssetId
, unspent : Transactions
, balance : Float
, name : AssetName
}
type alias Transaction =
{ index : Int
, transactionId : TransactionId
, value : Float
}
```
### Signatures
* all the functions here return a Result **Error** **Item**
```
import Neo as Neo
signatureData : SignatureData
signatureData =
let
fromBinaryPrivateKey =
getBinaryPrivateKeyFromWIF "L1QqQJnpBwbsPGAuutuzPTac8piqvbR1HRjrY5qHup48TBCBFe4g"
transactionData =
expectedTransactionDataGasNotEqual
in
getSignatureData transactionData fromBinaryPrivateKey
```
### Contracts
* all the functions here return a Result **Error** **Item**
```
contractData : ContractData
contractData =
let
fromBinaryPrivateKey =
getBinaryPrivateKeyFromWIF "L1QqQJnpBwbsPGAuutuzPTac8piqvbR1HRjrY5qHup48TBCBFe4g"
fromBinaryPublicKey =
getBinaryPublicKeyFromBinaryPrivateKey fromBinaryPrivateKey True
transactionData =
expectedTransactionDataGasNotEqual
signatureData =
expectedSignatureData
in
getContractData transactionData signatureData fromBinaryPublicKey
```
### Format validations
* all the functions here return Bool
```
isValidBinaryPublicKey binaryPublicKey
isValidHexPublicKey hexPublicKey
isValidAddress address
isValidHexPrivateKey hexPrivateKey
isValidBinaryPrivateKey binaryPrivateKey
isValidWif wif
```
### Ciphers
* all the functions here return Result String String
```
encrypt "a secret" "passphrase"
decrypt "encrypted string" "passphrase"
encryptAsJson "a secret" "passphrase"
-- {"ci":"fdfasfsa","vi":"dfasdfas","s":"dfafasas"}
decryptAsJson "json string" "passphrase"
```
## Install
you must use [elm-github-install](https://github.com/gdotdesign/elm-github-install) and include in your elm-package.json as follows:
```
"dependencies": {
"kingsleyh/elm-neo": "1.0.9 <= v < 2.0.0"
}
```
Then run elm-install
## Example
See the [tests](https://github.com/kingsleyh/elm-neo/blob/master/tests/NeoTests.elm) for example usage
## Testing
There are tests in the tests folder which run in the browser - this is because the native code doesn't want to run in elm-test so running in the browser was the only way I could get the tests running.
However this means that they can't be hooked up to travis-ci - maybe I'll be able to resolve this in the future - but for now to see the tests
```
cd tests
elm-reactor
```
Then fire up the browser on localhost:8000 and visit the NeoTest.elm
## Dev
In the JS folder is a native.js with all the native code in it. There is a main.js with exports that are used in the native.js.
These two files must be concatenated and output to Native/Neo.js - this is what gen.sh does. So after making changes to either main.js or native.js make sure to run
gen.sh to see the changes. Fire up the tests as described above during dev to keep on the straight and narrow.
So this all works by using browserify to package up all the required node_modules into a single js with standalone exports as all_crypto. To access the packaged libs from the
native.js you just prepend it with all_crypto.**name of export in main.js**.**lib**
so you'll have to yarn install in the JS folder to get all the deps
| 25.100719 | 200 | 0.753941 | eng_Latn | 0.601965 |
26a37be7f6c346ff0b4924c11d249c653efae9d5 | 424 | md | Markdown | _vendor/github.com/habitat-sh/habitat/components/docs-chef-io/content/habitat/docker_flow.md | stelgote/chef-web-docs | 395f2bb89b3abe03ff87081e9d3d8d079925c2e6 | [
"CC-BY-3.0"
] | 2,577 | 2016-06-14T08:17:26.000Z | 2022-03-30T00:50:41.000Z | _vendor/github.com/habitat-sh/habitat/components/docs-chef-io/content/habitat/docker_flow.md | stelgote/chef-web-docs | 395f2bb89b3abe03ff87081e9d3d8d079925c2e6 | [
"CC-BY-3.0"
] | 7,145 | 2016-06-14T06:59:55.000Z | 2022-03-31T20:38:29.000Z | _vendor/github.com/habitat-sh/habitat/components/docs-chef-io/content/habitat/docker_flow.md | unixorn/chef-web-docs | 896367530e4436f3948c91793d50c7147de41b2c | [
"CC-BY-3.0"
] | 613 | 2015-10-02T18:02:48.000Z | 2022-03-05T06:48:00.000Z | +++
title = "Docker Container Publishing Flow"
description = "Docker Container Publishing Flow"
gh_repo = "habitat"
[menu]
[menu.habitat]
title = "Docker Container Publishing Flow"
identifier = "habitat/diagrams/docker-flow"
parent = "habitat/diagrams"
weight = 50
+++
| 28.266667 | 134 | 0.740566 | eng_Latn | 0.272207 |
26a3f34bf3ecd5d1dc83edad6f1bb528666dc5d9 | 2,023 | md | Markdown | README.md | paliari-ti/php-acl | 13e1c0a799a51fb4ea6099972e6a2ccfd2b51775 | [
"MIT"
] | 1 | 2019-05-23T20:54:23.000Z | 2019-05-23T20:54:23.000Z | README.md | paliari-ti/php-acl | 13e1c0a799a51fb4ea6099972e6a2ccfd2b51775 | [
"MIT"
] | null | null | null | README.md | paliari-ti/php-acl | 13e1c0a799a51fb4ea6099972e6a2ccfd2b51775 | [
"MIT"
] | null | null | null | # php-acl
Simple ACL control for PHP
# Install
```bash
composer require paliari/php-acl
```
# Usage
You can set permissions for a namespace, controller, and even a specific method
```php
$user_permissions = [
'customers' => [
'products' => [
'index' => true,
'show' => true
],
'services' => true
],
'admin' => true
];
$acl = new Paliari\PhpAcl\Acl($user_permissions);
// With permission
$callable = 'Customers\\Products:index';
$response = $acl->allowed(Paliari\PhpAcl\AclOperator::keys($callable));
var_export($response); // true
// Without permission
$callable = 'Customers\\Products:destroy';
$response = $acl->allowed(Paliari\PhpAcl\AclOperator::keys($callable));
var_export($response); // false
```
## Using as a middleware in Slim Framework
```php
<?php
namespace Middlewares;
use Slim\Http\Response,
Slim\Http\Request,
Paliari\PhpAcl\Acl,
Paliari\PhpAcl\AclOperator;
class AclMiddleware
{
public function __invoke(Request $request, Response $response, $next)
{
// Set the "route" and "user" in a previous middleware
$route = $request->getAttribute('route');
$callable = $route->getCallable();
$user = $request->getAttribute('user');
$acl = new Acl($user->permissions);
if (!$acl->allowed(AclOperator::keys($callable))) {
return $response->withJson(['error' => 'Permission denied'], 403);
}
return $next($request, $response);
}
}
```
## Define a white list to skip the acl check for a specific method
```php
$user_permissions = [
'customers' => [
'products' => [
'show' => true
],
],
];
$acl = new Paliari\PhpAcl\Acl($user_permissions);
$callable = 'Customers\\Products:index';
\Paliari\PhpAcl\AclWhiteList::setKey($callable, true);
$response = \Paliari\PhpAcl\AclWhiteList::isSkip($callable) || $acl->allowed(Paliari\PhpAcl\AclOperator::keys($callable));
var_export($response); // true
``` | 22.477778 | 122 | 0.628769 | eng_Latn | 0.581505 |
26a4feb38fdf54f533c44b906681c0d8658e053c | 3,048 | md | Markdown | src/080-ingress.md | masci/k8s101 | a6af514172793996cd96814018c2270ad7e27be8 | [
"CC0-1.0"
] | null | null | null | src/080-ingress.md | masci/k8s101 | a6af514172793996cd96814018c2270ad7e27be8 | [
"CC0-1.0"
] | 1 | 2020-09-19T00:19:11.000Z | 2020-09-19T00:19:11.000Z | src/080-ingress.md | masci/k8s101 | a6af514172793996cd96814018c2270ad7e27be8 | [
"CC0-1.0"
] | 1 | 2020-08-26T01:45:01.000Z | 2020-08-26T01:45:01.000Z | # Ingress
In Kubernetes, an **Ingress** is an object that allows access to your Kubernetes
services from outside the Kubernetes cluster.
You might say this is also true for deployments exposed through a service of type
`LoadBalancer`, but there's a big difference: an ingress is not tied to any
particular service.
Similarly to “virtual hosts” on a traditional HTTP server, Kubernetes can use an
ingress as an HTTP-based load balancer to “inspect” the requests and route them
to the right service depending on user's configuration.
An ingress usually consists of an application called _Ingress Controller_ deployed
in the cluster itself. It's important to remember that Kubernetes doesn't ship any
Ingress Controller out of the box, so you will always need to install this additional
component behind an **Ingress** object. There is plenty of Ingress Controllers
available on the market: Nginx, Traefik, Ambassador just to name a few, so you can
pick the one that better suits your use case.
For the scope of this course, we'll see how to deploy Nginx as an Ingress Controller
for our local tiny cluster.
## Exercise n.1: deploy an ingress controller
There is a specific manifest we can use to install Nginx as an Ingress Controller
in a Kind cluster, so the installation step is just:
```sh
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/kind/deploy.yaml
namespace/ingress-nginx created
<snip>
```
Kubernetes is pretty fast to create the objects needed but the ingress will take
a while to start. To be sure that the cluster is ready, run this command that will
wait until the Ingress Controller is ready:
```sh
$ kubectl wait --namespace ingress-nginx \
--for=condition=ready pod \
--selector=app.kubernetes.io/component=controller \
--timeout=90s
pod/ingress-nginx-controller-6b69c57f44-8xxpw condition met
```
With the ingress up and running, we can move to the next exercise.
## Exercise n.2
> Change directory into the folder `definitions` before running the commands.
Now that we have an Ingress Controller, let's deploy an ingress resource to route
requests from outside our cluster to 2 different services.
We're going to deploy 2 services exposing 2 pods that will simply echo a string
in response of an HTTP request. The ingress will process the request and forward
urls ending with `/foo` to one service and urls ending with `/bar` to the other
one according to our `rules` specification:
```sh
$ kubectl apply -f ingress-example.yaml
pod/foo-app created
service/foo-service created
pod/bar-app created
service/bar-service created
ingress.extensions/example-ingress created
```
To confirm it's working, run `curl` on localhost:
```sh
$ curl http://localhost/foo
foo
$ curl http://localhost/bar
bar
```
If no rule is matched, Nginx will respond with its notorious 404 page:
```sh
$ curl http://localhost/
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.19.1</center>
</body>
</html>
```
| 35.44186 | 124 | 0.774934 | eng_Latn | 0.996435 |
26a5a462c84c449d01dc02e4090a85cdfa850c24 | 1,776 | md | Markdown | _posts/2020-04-16-bgs-and-you.md | redshiftlogistics/redshiftlogistics.github.io | 88443f551cdb122c1b5006931c1298f1b72b2b40 | [
"CC-BY-3.0"
] | null | null | null | _posts/2020-04-16-bgs-and-you.md | redshiftlogistics/redshiftlogistics.github.io | 88443f551cdb122c1b5006931c1298f1b72b2b40 | [
"CC-BY-3.0"
] | 1 | 2020-10-16T21:45:47.000Z | 2020-10-16T21:45:47.000Z | _posts/2020-04-16-bgs-and-you.md | redshiftlogistics/redshiftlogistics.github.io | 88443f551cdb122c1b5006931c1298f1b72b2b40 | [
"CC-BY-3.0"
] | null | null | null | ---
layout: post
title: BGS & You
description: Our BGS guidelines
image: https://cdn.discordapp.com/attachments/678270161995956225/700498043593687080/latest.png
show_tile: true
author: CMDR Tenacious C
---
It's no surprise to anyone that the BGS (background simulation) in Elite Dangerous is an incredibly complicated aspect of the game. No one person has a full understanding of how it works, however some know more than others. With this guide I intend to share with you the basics on how you can help the cause, or at the very least, prevent yourself from accidentally harming it.
## To understand what helps, one must first understand what hinders.
- Selling commodities at any non-Redshift controlled station
- Selling exploration data at any non-Redshift controlled station
- Completing missions for any faction besides Redshift Logistics
- Handing in bounty vouchers for other factions _(be sure to check which faction vouchers belong to in your transactions panel)_
These actions all **hurt our influence** in systems **where we are present and not in control**, therefore should be avoided.
## Now, what helps?
- Selling commodities at Redshift controlled stations
- Selling exploration data at Redshift controlled stations
- Completing missions for Redshift Logistics and prioritising high influence rewards
- Handing in bounty vouchers for Redshift Logistics _(be sure to check which faction vouchers belong to in your transactions panel)_
While this may all seem rather restrictive, do keep in mind that this only applies to systems where our faction is present. Assuming you are in an unrelated system then you are free to do as you please.
All we ask is that you are aware of your actions and do not do anything which would harm our influence.
Thank you.
| 57.290323 | 377 | 0.801239 | eng_Latn | 0.999608 |
26a5c391b0b4216350481b7fd0c28e46d05be8ad | 1,453 | md | Markdown | _posts/2018-08-01-snsnews-Marketing_News_Collection20180801.md | mskim-itso/mskim-itso.github.io | 45958c9425fd3de86c16e64c25e59e077c63e45f | [
"MIT"
] | null | null | null | _posts/2018-08-01-snsnews-Marketing_News_Collection20180801.md | mskim-itso/mskim-itso.github.io | 45958c9425fd3de86c16e64c25e59e077c63e45f | [
"MIT"
] | null | null | null | _posts/2018-08-01-snsnews-Marketing_News_Collection20180801.md | mskim-itso/mskim-itso.github.io | 45958c9425fd3de86c16e64c25e59e077c63e45f | [
"MIT"
] | null | null | null | ---
layout: post
current: post
cover: assets/images/marketing_new20180801.png
navigation: True
title: 일일 마케팅 뉴스 모음 - 8월1일
date: 2018-08-01 10:00:00
tags: [SNS News]
class: post-template
subclass: 'post tag-getting-started'
author: snsmanual
categories:
- SNS News
video_url:
---
### **마케팅 플랫폼 ‘LITER 프로젝트’ 런칭 예정**
구글에 대항하는 마케팅 플랫폼 ‘LITER 프로젝트’가 발표되어 투자자와 사용자들에게 큰 관심을 끌고 있다.
LITER 프로젝트는 기존의 단순한 리뷰 마케팅과는 달리 리뷰 소비에 따라 보상이 주어지는 ‘친광고주’성의 효율적인 플랫폼이다.
누구나 쉽게 리뷰를 작성할 수 있고, 소비자가 작성된 리뷰에 좋아요를 통해 리뷰를 소비하면 보상이 주어진다.
즉 광고주는 기존의 광고보다 더 효율적인 광고를 더 저렴하게 할 수 있다. 이렇듯 기존의 중앙화된 광고플랫폼의 문제점을 완벽하게 보완하여
구성원이 모두 Win-Win 할 수 있는 플랫폼이 바로 탈 중앙화된 LITER 프로젝트이다.
### **’메모리 반도체의 미래’..차량용 제품 韓·美 경쟁 본격화**
4차 산업 혁명의 핵심 기술이 집약될 ‘자율주행차’ 시대가 현실로 성큼 다가오면서, 차량용 메모리 반도체 시장 선점 경쟁도 본격화되고 있다.
5세대 이동통신(5G) 기반의 자율주행차는 ‘데이터 홍수’를 일으켜, 메모리 수요의 폭발적인 증가로 이어질 전망이다.
삼성전자는 올 들어 D램과 낸드플래시 모두 차세대 차량용 메모리의 규격을 업계에 제시하는 신제품을 연이어 내놓고 있다.
지난 2월엔 업계 최초로 첨단운전보조시스템(ADAS)와 인포테인먼트, 대시보드 시스템 등에 적용되는 낸드플래시 기반 ‘256GB eUFS’ 선보였다.
이 제품은 내열성을 -40도에서 105도까지 확장한 것이 특징이다.
또 4월엔 125도까지 견디는 자동차용 ‘10나노급 16b LPDDR4X D램’의 본격 양산을 시작하며,
자율주행을 위한 중앙제어 시스템 등 10나노급 D램 라인업 공급을 지속 확대하고 있다.
### **구글 인공지능스피커가 한국에 온다**
구글이 인공지능 스피커 ‘구글홈’을 앞세워 한국 스마트홈시장을 공략한다.
구글홈은 음악, 동영상 등 콘텐츠에 강점이 있는 반면 네이버와 카카오는
건설회사 등과 손잡고 인공지능 스피커의 사물인터넷(IoT) 서비스를 강화하고 있다.
구글은 자회사 유튜브와 연계를 통해 음악듣기 서비스를 제공할 수 있어
구글홈을 이용하면 별도의 비용을 지불할 필요가 없을 것으로 전망된다.
만약 유튜브레드에 가입했다면 원하는 음악을 골라 들을 수 있다.
세계 1위 음악 재생 서비스 스포티파이와 연계돼있다는 것도 무시할 수 없는 강점이다. | 30.914894 | 83 | 0.71576 | kor_Hang | 1.00001 |
26a62ab773bc9b10b754f6e983226c7edee000c4 | 1,121 | md | Markdown | en/ydb/yql/reference/syntax/update.md | k0t3n/docs | c56671784cfbd1978e1fe11834fef65539014d84 | [
"CC-BY-4.0"
] | null | null | null | en/ydb/yql/reference/syntax/update.md | k0t3n/docs | c56671784cfbd1978e1fe11834fef65539014d84 | [
"CC-BY-4.0"
] | null | null | null | en/ydb/yql/reference/syntax/update.md | k0t3n/docs | c56671784cfbd1978e1fe11834fef65539014d84 | [
"CC-BY-4.0"
] | null | null | null | ---
__system: {"dislikeVariants":["No answer to my question","Recomendations didn't help","The content doesn't match title","Other"]}
---
# UPDATE
Updates the data in the table. After the `SET` keyword, enter the columns where you want to update values and the new values themselves. The list of rows is defined by the `WHERE` clause. If `WHERE` is omitted, the updates are applied to all the rows of the table.
`UPDATE` can't change the value of `PRIMARY_KEY`.
{% note info %}
The changes of the table state can't be tracked within a single transaction. If the table has already been changed, use [`UPDATE ON`](#update-on) to update the data within the same transaction.
{% endnote %}
**Example**
```sql
UPDATE my_table
SET Value1 = YQL::ToString(Value2 + 1), Value2 = Value2 - 1
WHERE Key1 > 1;
```
## UPDATE ON {#update-on}
Used to update the data within a same transaction, if the table has already been changed.
**Example**
```sql
$to_update = (
SELECT Key, SubKey, "Updated" AS Value FROM my_table
WHERE Key = 1
);
SELECT * FROM my_table;
UPDATE my_table ON
SELECT * FROM $to_update;
```
| 26.069767 | 264 | 0.708296 | eng_Latn | 0.698179 |
26a6518d8857e8de24b56987021aa2087ab34008 | 3,395 | md | Markdown | _posts/2014-05-17-installing-django-with-virtualenv.md | lpatmo/lpatmo.github.io | e5170f99542803a129ef642ba4070ddaad12acfc | [
"MIT"
] | null | null | null | _posts/2014-05-17-installing-django-with-virtualenv.md | lpatmo/lpatmo.github.io | e5170f99542803a129ef642ba4070ddaad12acfc | [
"MIT"
] | null | null | null | _posts/2014-05-17-installing-django-with-virtualenv.md | lpatmo/lpatmo.github.io | e5170f99542803a129ef642ba4070ddaad12acfc | [
"MIT"
] | null | null | null | ---
title: '<span data-rel="title">Installing Django With Virtualenv</span>'
author: LP
layout: post
permalink: /installing-django-with-virtualenv/
wiziapp_processed:
- 1
dsq_thread_id:
- 2693068727
---
<p>
I’ve been looking at a couple of other Django tutorials lately, and recently — thanks to David, another Django learner I talked to at a Python meetup — I started making do with two great resources:
</p>
<p>
<strong>A) Youtube Series with Mike Hibbert:</strong>
</p>
<p>
</p>
<p>
<strong>B) <a href="http://www.tangowithdjango.com/book/index.html" target="_blank">Tango with Django</a> by Leif Azzopardi and David Maxwell.</strong>
</p>
<p>
The Tango with Django book initially looked great, but I was disappointed to find that it doesn’t start off showing users how to run develop their app using virtualenv. (Some brief notes about using virtualenv doesn’t come until <a href="http://www.tangowithdjango.com/book/chapters/deploy.html#creating-a-virtual-environment" target="_blank">later in the book</a>.) Mike Hibbert’s video series, on the other hand, *starts off* walking the user through installation and virtualenv.
</p>
<p>
For the sake of my own memory and to save myself some time from having to go play/pause through all 17 minutes of the installation video again, I decided to jot down the steps to creating a new Django application using virtualenv:
</p>
<p>
<strong>1) Create a virtualenv:<br /> </strong>
</p>
<pre class="prettyprint">$ virtualenv --no-site-packages NAME-OF-VIRTUALENV</pre>
<p>
Replace all capital letters with a name of your choosing.
</p>
<p>
<strong>2) Activate your virtualenv:</strong>
</p>
<pre class="prettyprint">$ source NAME-OF-VIRTUALENV/bin/activate</pre>
<p>
This gets you into the virtual environment. You’ll notice that your command line now has this prefix:
</p>
<pre class="prettyprint">(NAME-OF-VIRTUALENV)Your-MacBook-Air:$</pre>
<p>
<strong>3) Change directory into your project folder and install Django:</strong>
</p>
<pre class="prettyprint">$ cd NAME-OF-VIRTUALENV
$ easy_install django</pre>
<p>
You can also run <code> pip install -U django==1.5.4</code> instead of <code> easy_install django</code> if you want to install a specific version of Django instead of the latest version.
</p>
<p>
<strong>4) Start a new project:</strong>
</p>
<pre class="prettyprint">$ django-admin.py startproject YOURPROJECTNAME</pre>
<p>
You’re creating a new project.
</p>
<p>
<strong>5) Preview your project in the browser:</strong>
</p>
<pre class="prettyprint">$ cd YOURPROJECTNAME
$ python manage.py runserver</pre>
<p>
After you type the second command, you’ll be able to preview your app in your local browser.
</p>
<p>
<span style="color: #000000;"><b>6) Create a new application within your Django project (think of an application as an ice crem tub inside your Django freezer — thanks for the metaphor, <a href="http://pydanny.com/announcing-two-scoops-of-django-1.6.html" target="_blank">Two Scoops of Django</a>!):</b></span>
</p>
<pre class="prettyprint">$ python manage.py startapp APPNAME</pre>
<hr />
<strong>Update:</strong> I found another good tutorial! The founder behind Coding for Entrepreneurs Youtube series demonstrates the creation of a Django project in virtualenv on his mac:</p>
<p>
</p> | 33.95 | 501 | 0.729013 | eng_Latn | 0.933434 |
26a7860f252cc43a5b2a4a0e4eab7a1136207aa5 | 658 | md | Markdown | README.md | demobo-com/fancyLightbox | 41363b5a60f62c01e96038aeab9999b73d18de52 | [
"MIT"
] | 1 | 2015-11-06T00:25:21.000Z | 2015-11-06T00:25:21.000Z | README.md | demobo-com/fancyLightbox | 41363b5a60f62c01e96038aeab9999b73d18de52 | [
"MIT"
] | null | null | null | README.md | demobo-com/fancyLightbox | 41363b5a60f62c01e96038aeab9999b73d18de52 | [
"MIT"
] | null | null | null | Fancy Lightbox
=============
https://github.com/demobo-com/fancyLightbox
This is a handy widget that we build for our presentation app de Mobo Slides.
FancyLightbox supports multi-state in-out transitions and consists a collection of 72 prebuilt show/hide transitions.
## Demo
http://demobo-com.github.io/fancyLightbox/
## Contributing
All contributions are welcome! The simplest way to show your support for this project is to **"star" it**.
* You can support us more by voting for us on [http://siliconimage.challengepost.com/submissions/25524-de-mobo-slides]
* or like our project on [http://challengepost.com/software/de-mobo-slides]
##License
MIT
| 32.9 | 118 | 0.765957 | eng_Latn | 0.950494 |
26a7ec43f685fbe8fb4620ff7a25fcb7ab3577e7 | 1,089 | md | Markdown | README.md | rtugeek/PercentProgressBar | b28942ae7bd92b3f331906c90b164149dee6d5c8 | [
"WTFPL"
] | null | null | null | README.md | rtugeek/PercentProgressBar | b28942ae7bd92b3f331906c90b164149dee6d5c8 | [
"WTFPL"
] | null | null | null | README.md | rtugeek/PercentProgressBar | b28942ae7bd92b3f331906c90b164149dee6d5c8 | [
"WTFPL"
] | null | null | null | # PercentProgressBar
<a href="https://jitpack.io/#rtugeek/PercentProgressBar"></a>
### ScreenShot:
<img src="https://github.com/rtugeek/PercentProgressBar/blob/master/screenshot/snapshot.jpeg" width="400">
### Step 1. Add the JitPack repository in your root build.gradle at the end of repositories:
```
allprojects {
repositories {
...
maven { url "https://jitpack.io" }
}
}
```
### Step 2. Add the dependency
```
implementation 'com.github.rtugeek:PercentProgressBar:${version}'
```
## License
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
Version 2, December 2004
Copyright (C) 2004 Leon Fu <rtugeek@gmail.com>
Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as long
as the name is changed.
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. You just DO WHAT THE FUCK YOU WANT TO.
| 28.657895 | 126 | 0.685032 | yue_Hant | 0.487031 |
26a8fd84bf75d3d76bf9a6b7c924fa07200a1d71 | 818 | md | Markdown | _posts/2016-05-12-Enzo-Miccio-Calicanto.md | eudanceyou/eudanceyou.github.io | 9d81bccab5dd52c95c99495c5800da809ea32ed7 | [
"MIT"
] | null | null | null | _posts/2016-05-12-Enzo-Miccio-Calicanto.md | eudanceyou/eudanceyou.github.io | 9d81bccab5dd52c95c99495c5800da809ea32ed7 | [
"MIT"
] | null | null | null | _posts/2016-05-12-Enzo-Miccio-Calicanto.md | eudanceyou/eudanceyou.github.io | 9d81bccab5dd52c95c99495c5800da809ea32ed7 | [
"MIT"
] | null | null | null | ---
layout: post
date: '2016-05-12'
title: "Enzo Miccio Calicanto"
category: Enzo Miccio
tags: [Enzo Miccio]
---
### Enzo Miccio Calicanto
Just **$339.99**
###
<table><tr><td>BRANDS</td><td>Enzo Miccio</td></tr></table>
<a href="https://www.antebrands.com/en/enzo-miccio/62489-enzo-miccio-calicanto.html"><img src="//static.msromantic.com/144977/enzo-miccio-calicanto.jpg" alt="Enzo Miccio Calicanto" style="width:100%;" /></a>
<!-- break --><a href="https://www.antebrands.com/en/enzo-miccio/62489-enzo-miccio-calicanto.html"><img src="//static.msromantic.com/144976/enzo-miccio-calicanto.jpg" alt="Enzo Miccio Calicanto" style="width:100%;" /></a>
Buy it: [https://www.antebrands.com/en/enzo-miccio/62489-enzo-miccio-calicanto.html](https://www.antebrands.com/en/enzo-miccio/62489-enzo-miccio-calicanto.html)
| 51.125 | 221 | 0.716381 | yue_Hant | 0.152161 |
26a9b2780a7b2ec4140150a8c1852ffb2098153b | 923 | md | Markdown | README.md | rgiordan/LinearResponseVariationalBayes.cpp | 99b0666bbb9e1c8a1b020b133bcc289f894c07c4 | [
"Apache-2.0"
] | null | null | null | README.md | rgiordan/LinearResponseVariationalBayes.cpp | 99b0666bbb9e1c8a1b020b133bcc289f894c07c4 | [
"Apache-2.0"
] | null | null | null | README.md | rgiordan/LinearResponseVariationalBayes.cpp | 99b0666bbb9e1c8a1b020b133bcc289f894c07c4 | [
"Apache-2.0"
] | null | null | null | # LinearResponseVariationalBayes.cpp
This contains a C++ library with tools for doing linear response variational
Bayes calculations, especially using the Stan autodiff libraries.
It will require Stan and Stan math (as well as Eigen and boost, which are
by default installed with Stan math).
* [Stan repo](https://github.com/stan-dev/stan)
* [Stan math repo](https://github.com/stan-dev/math)
Install these libraries to wherever you keep your git repos. Cmake will work
automatically if you set an environment variable to your git repo location,
e.g. in bash:
```
export GIT_REPO_LOC=/full/path/to/your/git/repos
```
Finally, in a build directory, run cmake then make install:
```bash
cd $GIT_REPO_LOC/LinearResponseVariationalBayes.cpp
mkdir build
cd build
cmake ..
sudo make install
```
If there are problems, check that CMakeLists.txt in the root directory has the
correct directory locations for the libraries.
| 29.774194 | 78 | 0.782232 | eng_Latn | 0.988333 |
26aa058c260df4e947905400a71b0fe6fce8e75d | 1,360 | md | Markdown | README.md | JoseIgnacioE/Spectral-Clustering | 07014a7a66dd48d9b522d2fe99e3a4118f405fb0 | [
"CC0-1.0"
] | null | null | null | README.md | JoseIgnacioE/Spectral-Clustering | 07014a7a66dd48d9b522d2fe99e3a4118f405fb0 | [
"CC0-1.0"
] | null | null | null | README.md | JoseIgnacioE/Spectral-Clustering | 07014a7a66dd48d9b522d2fe99e3a4118f405fb0 | [
"CC0-1.0"
] | 1 | 2021-08-22T14:45:51.000Z | 2021-08-22T14:45:51.000Z | # Spectral-Clustering
Spectral clustering for image segmentation and graph partition. This work is based on the works by Ulrike von Luxburg [1], Shi and Malik [2] and Ng, Jordan and Weiss [3].
# Contents
In this repository, we've put together some Jupyter notebooks and MAtlab codes to give an example of Spectral Clustering Algorithms. This repository is aimed at illustrating people who want to learn the basic algorithms of this family of algorithms.
# Contribution and Author
If you'd like to contribute and/or correct any code of this repository, you are free to message or mail me at joignacioespinoza@gmail.com. This repository is part of the thesis on Quantum Spectral Clustering for Image Segmentation at Tecnológico de Monterrey for the degree of Master in Nanotechnology.
# References
[1] Ulrike von Luxburg. A tutorial on spectral clustering.Statistics and Computing,17(4):395–416, Dec 2007
[2] Jianbo Shi and J. Malik. Normalized cuts and image segmentation.IEEE Trans-actions on Pattern Analysis and Machine Intelligence, 22(8):888–905, 2000.
[3] Andrew Y. Ng, Michael I. Jordan, and Yair Weiss. On spectral clustering: Analysis and an algorithm. InProceedings of the 14th International Conference onNeural Information Processing Systems: Natural and Synthetic, NIPS’01, page849–856, Cambridge, MA, USA, 2001. MIT Press.
| 68 | 303 | 0.786029 | eng_Latn | 0.962234 |
26ab9f80a5109e42addca9b0576cb1d2f4a3c509 | 4,472 | md | Markdown | README.md | sbender9/concentrate2 | 59da2cc26bb5350bfe66143dfb4bd26cd8d69c82 | [
"BSD-3-Clause"
] | 25 | 2015-03-06T21:25:10.000Z | 2021-10-17T08:15:44.000Z | README.md | sbender9/concentrate2 | 59da2cc26bb5350bfe66143dfb4bd26cd8d69c82 | [
"BSD-3-Clause"
] | 5 | 2015-01-10T05:28:17.000Z | 2019-03-30T03:18:17.000Z | README.md | sbender9/concentrate2 | 59da2cc26bb5350bfe66143dfb4bd26cd8d69c82 | [
"BSD-3-Clause"
] | 7 | 2015-01-09T22:42:45.000Z | 2020-08-11T01:25:55.000Z | Concentrate
===========
Produce binary data with a neat DSL.
Overview
--------
Concentrate allows you to efficiently create buffers by chaining together calls
to write numbers, strings and even other buffers! Concentrate is also easily
extendable so you can implement your own custom types.
If you want to parse binary data, might I suggest [dissolve](https://github.com/deoxxa/dissolve)?
Features
--------
* Accurate handling of [u]int{8,16,32} numbers in both signed and unsigned
variants using fast, built-in [Buffer](http://nodejs.org/docs/latest/api/buffer.html)
methods
* Fast and reliable operation through lazy compilation of results
* Tiny (<150 LoC) implementation, allowing for easy debugging
* Stream interface with explicit flushing for maximum speeeeeeed (inspired by
felixge, so you know it's good!)
Installation
------------
Available via [npm](http://npmjs.org/):
> $ npm install concentrate
Or via git:
> $ git clone git://github.com/deoxxa/concentrate.git node_modules/concentrate
Usage
-----
Also see [example.js](https://github.com/deoxxa/concentrate/blob/master/example.js) and
[example-complex.js](https://github.com/deoxxa/concentrate/blob/master/example-complex.js).
```javascript
#!/usr/bin/env node
var Concentrate = require("./index");
var data = Concentrate().uint8(1).uint8(2).uint32be(555).string("hi there", "utf8").result();
console.log(data);
```
```
<Buffer 01 02 00 00 02 2b 68 69 20 74 68 65 72 65 40 06 66 66 40 00 cc cc cc cc cc cd>
```
Oh look! Streams! Also see [example-stream.js](https://github.com/deoxxa/concentrate/blob/master/example-stream.js).
```javascript
#!/usr/bin/env node
var Concentrate = require("./index");
var c = Concentrate();
c.on("end", function() {
console.log("ended");
});
c.on("readable", function() {
var e;
while (e = c.read()) {
console.log(e);
}
});
c.uint8(1).uint8(2).uint32be(555).string("hi there", "utf8").floatbe(2.1).doublebe(2.1).flush();
c.uint8(5).uint8(6);
c.uint8(7);
c.uint8(30);
c.flush().end();
```
```
<Buffer 01 02 00 00 02 2b 68 69 20 74 68 65 72 65 40 06 66 66 40 00 cc cc cc cc cc cd>
<Buffer 05 06 07 1e>
ended
```
Methods
-------
All methods aside from `result` are chainable and all except `copy` return the
same Concentrate instance they were called on.
Execution Methods
-----------------
* `copy()` - returns a new copy of the current Concentrate instance, copying the
state of the current job list
* `reset()` - resets the job list
* `result()` - compiles the job list into a buffer and returns that buffer
* `flush()` - compiles the current job list, emits it via the stream API, then
clears the current job list
* `end()` - ends the stream part of Concentrate (basically makes it emit "end")
Writing methods
---------------
* `buffer(data)`
* `string(data, encoding)` - write a string with the given encoding
* `int8(data)` - signed 8 bit integer
* `sint8(data)` - signed 8 bit integer
* `uint8(data)` - unsigned 8 bit integer
* `int16(data)` - signed, little endian 16 bit integer
* `int16le(data)` - signed, little endian 16 bit integer
* `int16be(data)` - signed, big endian 16 bit integer
* `sint16(data)` - signed, little endian 16 bit integer
* `sint16le(data)` - signed, little endian 16 bit integer
* `sint16be(data)` - signed, big endian 16 bit integer
* `uint16(data)` - unsigned, little endian 16 bit integer
* `uint16le(data)` - unsigned, little endian 16 bit integer
* `uint16be(data)` - unsigned, big endian 16 bit integer
* `int32(data)` - signed, little endian 32 bit integer
* `int32le(data)` - signed, little endian 32 bit integer
* `int32be(data)` - signed, big endian 32 bit integer
* `sint32(data)` - signed, little endian 32 bit integer
* `sint32le(data)` - signed, little endian 32 bit integer
* `sint32be(data)` - signed, big endian 32 bit integer
* `uint32(data)` - unsigned, little endian 32 bit integer
* `uint32le(data)` - unsigned, little endian 32 bit integer
* `uint32be(data)` - unsigned, big endian 32 bit integer
* `floatbe(data)` - big endian 32 bit float
* `floatle(data)` - little endian 32 bit float
* `doublebe(data)` - big endian 64 bit double
* `doublele(data)` - little endian 64 bit double
License
-------
3-clause BSD. A copy is included with the source.
Contact
-------
* GitHub ([deoxxa](http://github.com/deoxxa))
* Twitter ([@deoxxa](http://twitter.com/deoxxa))
* ADN ([@deoxxa](https://alpha.app.net/deoxxa))
* Email ([deoxxa@fknsrs.biz](mailto:deoxxa@fknsrs.biz))
| 29.813333 | 116 | 0.698122 | eng_Latn | 0.851533 |
26aba9089b6384ae525ed218db91699e31f243f9 | 995 | md | Markdown | add/metadata/System.Configuration/TimeSpanSecondsConverter.meta.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Configuration/TimeSpanSecondsConverter.meta.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/System.Configuration/TimeSpanSecondsConverter.meta.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-01-06T09:36:01.000Z | 2021-01-06T09:36:01.000Z | ---
uid: System.Configuration.TimeSpanSecondsConverter
ms.technology:
- "dotnet-standard"
ms.author: "riande"
manager: "wpickett"
---
---
uid: System.Configuration.TimeSpanSecondsConverter.#ctor
ms.technology:
- "dotnet-webforms"
ms.author: "riande"
manager: "wpickett"
---
---
uid: System.Configuration.TimeSpanSecondsConverter.ConvertFrom
ms.technology:
- "dotnet-standard"
---
---
uid: System.Configuration.TimeSpanSecondsConverter.ConvertFrom(System.ComponentModel.ITypeDescriptorContext,System.Globalization.CultureInfo,System.Object)
ms.technology:
- "dotnet-webforms"
ms.author: "riande"
manager: "wpickett"
---
---
uid: System.Configuration.TimeSpanSecondsConverter.ConvertTo
ms.technology:
- "dotnet-standard"
---
---
uid: System.Configuration.TimeSpanSecondsConverter.ConvertTo(System.ComponentModel.ITypeDescriptorContext,System.Globalization.CultureInfo,System.Object,System.Type)
ms.technology:
- "dotnet-webforms"
ms.author: "riande"
manager: "wpickett"
---
| 22.613636 | 165 | 0.773869 | yue_Hant | 0.399117 |
26ac5623ffbd317923aca77ef9143fc5873d0b86 | 2,673 | md | Markdown | business-central/production-how-to-post-capacities.md | MicrosoftDocs/dynamics365smb-docs-pr.en-ca | 06b3cc522f21be4a69886591dcd74a1fbcea445c | [
"CC-BY-4.0",
"MIT"
] | 3 | 2017-08-28T10:40:03.000Z | 2021-04-20T21:13:46.000Z | business-central/production-how-to-post-capacities.md | MicrosoftDocs/dynamics365smb-docs-pr.en-ca | 06b3cc522f21be4a69886591dcd74a1fbcea445c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | business-central/production-how-to-post-capacities.md | MicrosoftDocs/dynamics365smb-docs-pr.en-ca | 06b3cc522f21be4a69886591dcd74a1fbcea445c | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-10T09:23:01.000Z | 2021-11-10T09:23:01.000Z | ---
title: How to Post Capacities
description: Post consumed capacities that are not assigned to the production order in the capacity journal and view posted capacities on the capacity ledger entries page.
author: SorenGP
ms.service: dynamics365-business-central
ms.topic: conceptual
ms.devlang: na
ms.tgt_pltfrm: na
ms.workload: na
ms.search.keywords: ''
ms.date: 06/22/2021
ms.author: edupont
ms.openlocfilehash: 024985cb4a2615f374465e5a387901976509a5db
ms.sourcegitcommit: a7cb0be8eae6ece95f5259d7de7a48b385c9cfeb
ms.translationtype: HT
ms.contentlocale: en-CA
ms.lasthandoff: 07/08/2021
ms.locfileid: "6444214"
---
# <a name="post-capacities"></a>Post Capacities
In the capacity journal, you post consumed capacities that are not assigned to the production order. For example, maintenance work must be assigned to capacity, but not to a production order.
## <a name="to-post-capacities"></a>To post capacities
1. Choose the  icon, enter **Capacity Journals**, and then choose the related link.
2. Fill in the **Posting Date** and **Document No.** fields.
3. In the **Type** field, enter the type of the capacity, either **Machine centre** or **Work centre**, that you are posting.
4. In the **No.** field, enter the number of the machine centre or work centre.
5. Enter the relevant data in the other fields, such as **Starting Time**, **Ending Time**, **Quantity**, and **Scrap**.
6. Choose the **Post** action to post the capacities.
## <a name="to-view-work-center-ledger-entries"></a>To view work centre ledger entries
In the **Work Centre Card** and **Machine Centre Card** pages, you can view the posted capacities as a result of finished production orders.
1. Choose the  icon, enter **Work Centres**, and then choose the related link.
2. Open the relevant **Work Centre** card from the list, and then choose the **Capacity Ledger Entries** action.
The **Capacity Ledger Entries** page displays the posted entries from the work centre in the order they were posted.
## <a name="see-also"></a>See Also
[Manufacturing](production-manage-manufacturing.md)
[Setting Up Manufacturing](production-configure-production-processes.md)
[Planning](production-planning.md)
[Inventory](inventory-manage-inventory.md)
[Purchasing](purchasing-manage-purchasing.md)
[Working with [!INCLUDE[prod_short](includes/prod_short.md)]](ui-work-product.md)
[!INCLUDE[footer-include](includes/footer-banner.md)] | 56.87234 | 194 | 0.750094 | eng_Latn | 0.966414 |
26ac74c1ecb0f6214b697c60b83d14c6139823e6 | 2,716 | md | Markdown | controls/splitter/client-side-programming/events/onclientexpanding.md | mohdjuwaiser/ajax-docs | 56376e3c2d405a948ecd88828c75fa73d3602422 | [
"MIT"
] | null | null | null | controls/splitter/client-side-programming/events/onclientexpanding.md | mohdjuwaiser/ajax-docs | 56376e3c2d405a948ecd88828c75fa73d3602422 | [
"MIT"
] | null | null | null | controls/splitter/client-side-programming/events/onclientexpanding.md | mohdjuwaiser/ajax-docs | 56376e3c2d405a948ecd88828c75fa73d3602422 | [
"MIT"
] | null | null | null | ---
title: OnClientExpanding
page_title: OnClientExpanding | RadSplitter for ASP.NET AJAX Documentation
description: OnClientExpanding
slug: splitter/client-side-programming/events/onclientexpanding
tags: onclientexpanding
published: True
position: 10
---
# OnClientExpanding
The **OnClientExpanding** client-side event handler is called when a pane is about to be expanded. The expansion can occur because of a user action such as clicking an expand button or sliding zone tab, on page load, or as the result of a a call to a client-side method.
>note The **OnClientExpanding** event is supported by **RadPane** and **RadSlidingPane** . It takes the place of the deprecated OnClientBeforeExpand event.
The following two parameters are passed to the event handler:
* **sender** is the pane that is about to be expanded.
* **eventArgs** has the following methods:
* **set_cancel()** lets you prevent the pane from being expanded.
* **get_cancel()** returns whether the operation was cancelled.
The following example uses the **OnClientExpanding** event to show a confirmation dialog:
````ASP.NET
<script type="text/javascript">
function confirmExpand(sender, eventArgs)
{
eventArgs.set_cancel(!confirm("Are you sure you want to open " + sender.get_id() + "?"));
}
</script>
<telerik:RadSplitter runat="server" id="RadSplitter1" Orientation="Horizontal" >
<telerik:RadPane
runat="server"
id="RadPane1"
Height="80px"
OnClientBeforeExpand="confirmExpand" >
<telerik:RadSlidingZone runat="server" id="RadSlidingZone1" >
<telerik:RadSlidingPane
runat="server"
Title="Sliding Pane 1"
id="SlidingPane1"
Height="50px"
OnClientBeforeExpand="confirmExpand" >
</telerik:RadSlidingPane>
<telerik:RadSlidingPane
runat="server"
Title="Sliding Pane 2"
id="SlidingPane2"
Height="50px"
OnClientBeforeExpand="confirmExpand" >
</telerik:RadSlidingPane>
</telerik:RadSlidingZone>
</telerik:RadPane>
<telerik:RadSplitBar runat="server" id="RadSplitBar1" CollapseMode="Both" />
<telerik:RadPane
runat="server"
id="RadPane2"
Height="90px"
OnClientBeforeExpand="confirmExpand" >
</telerik:RadPane>
</telerik:RadSplitter>
````
## See Also
* [Overview]({%slug splitter/client-side-programming/overview%})
* [RadPane Object]({%slug splitter/client-side-programming/radpane-object%})
* [RadSlidingPane Object]({%slug splitter/client-side-programming/radslidingpane-object%})
* [OnClientCollapsing]({%slug splitter/client-side-programming/events/onclientcollapsing%})
* [OnClientExpanded]({%slug splitter/client-side-programming/events/onclientexpanded%})
| 34.379747 | 271 | 0.724963 | eng_Latn | 0.67517 |
26ac91e47541d7ced9974fdd8f52183ea4ec5103 | 1,900 | md | Markdown | examples/06_benchmarks/README.md | enowy/Recommenders | 60033231b9167438032843c23158c0c776856e0e | [
"MIT"
] | 10,147 | 2019-05-07T07:24:36.000Z | 2022-03-31T21:16:41.000Z | examples/06_benchmarks/README.md | enowy/Recommenders | 60033231b9167438032843c23158c0c776856e0e | [
"MIT"
] | 750 | 2019-05-07T07:34:33.000Z | 2022-03-31T10:11:55.000Z | examples/06_benchmarks/README.md | enowy/Recommenders | 60033231b9167438032843c23158c0c776856e0e | [
"MIT"
] | 1,983 | 2019-05-07T08:56:48.000Z | 2022-03-31T16:43:00.000Z | # Benchmarks
In this folder we show benchmarks using different algorithms. To facilitate the benchmark computation, we provide a set of wrapper functions that can be found in the file [benchmark_utils.py](benchmark_utils.py).
The machine we used to perform the benchmarks is a Standard NC6s_v2 [Azure DSVM](https://azure.microsoft.com/en-us/services/virtual-machines/data-science-virtual-machines/) (6 vCPUs, 112 GB memory and 1 P100 GPU). Spark ALS is run in local standalone mode.
## MovieLens
[MovieLens](https://grouplens.org/datasets/movielens/) is one of the most common datasets used in the literature in Recommendation Systems. The dataset consists of a collection of users, movies and movie ratings, there are several available sizes:
* MovieLens 100k: 100,000 ratings from 1000 users on 1700 movies.
* MovieLens 1M: 1 million ratings from 6000 users on 4000 movies.
* MovieLens 10M: 10 million ratings from 72000 users on 10000 movies.
* MovieLens 20M: 20 million ratings from 138000 users on 27000 movies
The MovieLens benchmark can be seen at [movielens.ipynb](movielens.ipynb). In this notebook, the MovieLens dataset is split into training / test sets using a stratified splitting method that takes 75% of each user's ratings as training data, and the remaining 25% ratings as test data. For ranking metrics we use `k=10` (top 10 recommended items). The algorithms used in this benchmark are [ALS](../00_quick_start/als_movielens.ipynb), [SVD](../02_model_collaborative_filtering/surprise_svd_deep_dive.ipynb), [SAR](../00_quick_start/sar_movielens.ipynb), [NCF](../00_quick_start/ncf_movielens.ipynb), [BPR](../02_model_collaborative_filtering/cornac_bpr_deep_dive.ipynb), [BiVAE](../02_model_collaborative_filtering/cornac_bivae_deep_dive.ipynb), [LightGCN](../02_model_collaborative_filtering/lightgcn_deep_dive.ipynb) and [FastAI](../00_quick_start/fastai_movielens.ipynb).
| 100 | 875 | 0.798421 | eng_Latn | 0.907887 |
26adec4f07cd43c804207d6706acff436d69e1f5 | 1,758 | md | Markdown | _posts/dir1-linux/2019-08-01-Ubuntu-set-rc.local.md | lyc10031/lyc10031.github.io | c0858623e736fa1a26b7a63790b81599db16f274 | [
"MIT"
] | null | null | null | _posts/dir1-linux/2019-08-01-Ubuntu-set-rc.local.md | lyc10031/lyc10031.github.io | c0858623e736fa1a26b7a63790b81599db16f274 | [
"MIT"
] | null | null | null | _posts/dir1-linux/2019-08-01-Ubuntu-set-rc.local.md | lyc10031/lyc10031.github.io | c0858623e736fa1a26b7a63790b81599db16f274 | [
"MIT"
] | null | null | null | ---
layout: article
title: ubuntu1804 设置开机启动脚本
mode: immersive
tag: linux
header:
theme: dark
background: 'linear-gradient(135deg, rgb(34, 139, 87), rgb(139, 34, 139))'
article_header:
type: overlay
theme: dark
background_color: '#203028'
background_image:
gradient: 'linear-gradient(135deg, rgba(34, 139, 87 , .4), rgba(139, 34, 139, .4))'
src: /assets/images/img/xiongmao1.png
---
<!--  -->
## 在Ubuntu 1804 中使用/etc/rc.local
### 1、systemd默认读取/etc/systemd/system下的配置文件，该目录下的文件会链接/lib/systemd/system/下的文件。一般系统安装完/lib/systemd/system/下会有rc-local.service文件，即我们需要的配置文件。
可以复制一份 不去动/lib/systemd/system/下面的文件
cp /lib/systemd/system/rc-local.service /etc/systemd/system/
{% highlight txt linenos %}
# SPDX-License-Identifier: LGPL-2.1+
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# This unit gets pulled automatically into multi-user.target by
# systemd-rc-local-generator if /etc/rc.local is executable.
[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
After=network.target
[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no
[Install]
WantedBy=multi-user.target
Alias=rc-local.service
{% endhighlight %}
默认是没有Install 部分的，在文件中添加
### 2、创建/etc/rc.local文件，赋予权限，在文件中添加要开机执行的命令.
touch /etc/rc.local
chmod 755 /etc/rc.local
在rc.local文件中添加想要开机执行的命令重启系统查看是否设置成功。
<a href="javascript:scroll(0,0)">-- 返回顶部 --</a>
| 25.478261 | 138 | 0.74744 | eng_Latn | 0.505137 |
26ae3aea7059ad5369f00579a7517e5cc8798bfd | 1,513 | md | Markdown | _posts/2010-03-16-med-v-v1-sp1-1-5-rc.md | mcpjanmarek/mcpjanmarek.github.io | 54fd6881db3aa9d3814b78b09919aec1d3b681d7 | [
"MIT"
] | null | null | null | _posts/2010-03-16-med-v-v1-sp1-1-5-rc.md | mcpjanmarek/mcpjanmarek.github.io | 54fd6881db3aa9d3814b78b09919aec1d3b681d7 | [
"MIT"
] | null | null | null | _posts/2010-03-16-med-v-v1-sp1-1-5-rc.md | mcpjanmarek/mcpjanmarek.github.io | 54fd6881db3aa9d3814b78b09919aec1d3b681d7 | [
"MIT"
] | null | null | null | ---
id: 23
title: MED-V v1 SP1 (1.5) RC
date: 2010-03-16T22:07:38+02:00
author: Jan Marek
layout: post
guid: http://jmarek.wordpress.com/2010/03/16/med-v-v1-sp1-1-5-rc
permalink: /2010/03/16/med-v-v1-sp1-1-5-rc/
spaces_1d3f038117de6df561f7bf0516bb226c_permalink:
- "http://cid-6e7b9216726d07b8.users.api.live.net/Users(7961117391414167480)/Blogs('6E7B9216726D07B8!242')/Entries('6E7B9216726D07B8!276')?authkey=EpZNAU0huAk%24"
- "http://cid-6e7b9216726d07b8.users.api.live.net/Users(7961117391414167480)/Blogs('6E7B9216726D07B8!242')/Entries('6E7B9216726D07B8!276')?authkey=EpZNAU0huAk%24"
tagazine-media:
- 'a:7:{s:7:"primary";s:0:"";s:6:"images";a:0:{}s:6:"videos";a:0:{}s:11:"image_count";s:1:"0";s:6:"author";s:8:"17238236";s:7:"blog_id";s:8:"16623371";s:9:"mod_stamp";s:19:"2010-03-16 21:08:43";}'
- 'a:7:{s:7:"primary";s:0:"";s:6:"images";a:0:{}s:6:"videos";a:0:{}s:11:"image_count";s:1:"0";s:6:"author";s:8:"17238236";s:7:"blog_id";s:8:"16623371";s:9:"mod_stamp";s:19:"2010-03-16 21:08:43";}'
categories:
- Desktop Virtualization
- Nezařazené
- Uncategorized
tags:
- MDOP
- MED-V
---
<div id="msgcns!6E7B9216726D07B8!276" class="bvMsg">
<div>
New RC is available for download on <a href="https://connect.microsoft.com/site/sitehome.aspx?SiteID=665" target="_blank">Microsoft Connect</a>. You can try new SP1 which provides support for new Windows 7 (as a client OS) and Windows Server 2008 R2 (as a server OS). New documentation (in chm format) is available as well.
</div>
</div>
| 54.035714 | 327 | 0.70456 | yue_Hant | 0.215991 |
26af4113c5f2383097c053311d7f0a9e764715dc | 322 | md | Markdown | sms/README.md | agus7fauzi/services | 163c24dc17b3565ee20dd9c76f03f5a1b16768fa | [
"Apache-2.0"
] | null | null | null | sms/README.md | agus7fauzi/services | 163c24dc17b3565ee20dd9c76f03f5a1b16768fa | [
"Apache-2.0"
] | null | null | null | sms/README.md | agus7fauzi/services | 163c24dc17b3565ee20dd9c76f03f5a1b16768fa | [
"Apache-2.0"
] | null | null | null | Send SMS messages
# SMS Service
Send SMS messages in seconds. Integrate into any product for verification codes, links, reminders and more.
Powered by [twilio.com](https://twilio.com).
Use this API from your bubble.io app with [the Bubble plugin](https://bubble.io/plugin/micro-sms-1631540206323x798031923148226600).
| 32.2 | 131 | 0.782609 | eng_Latn | 0.788699 |
26afd7b12029d7f08405132deadcc8e620fbcdbc | 440 | md | Markdown | _posts/2020-02-22-a-new-reading.md | sdeehub/i-learn-type-theme | 0b019d3d16d37bb7a458e870cccdd42b6afa2dc9 | [
"MIT"
] | null | null | null | _posts/2020-02-22-a-new-reading.md | sdeehub/i-learn-type-theme | 0b019d3d16d37bb7a458e870cccdd42b6afa2dc9 | [
"MIT"
] | 49 | 2019-09-17T05:13:50.000Z | 2020-01-15T15:34:31.000Z | _posts/2020-02-22-a-new-reading.md | sdeehub/i.learn | 0b019d3d16d37bb7a458e870cccdd42b6afa2dc9 | [
"MIT"
] | null | null | null | ---
title: Public Speaking
date: 2020-02-22 16:21:14 Z
tags:
- Mindset
layout: post
feature-img: https://res.cloudinary.com/sdees-reallife/image/upload/v1555658919/sample_feature_img.png
---
Don't speak until you are sure you have something to say, and know just what it is; then say it, and sit down.
<i class="fa fa-child" style="color:plum"></i>
Attitude is a choice. Think positive thoughts daily. Believe in yourself. ~ Pat Summitt
| 29.333333 | 110 | 0.747727 | eng_Latn | 0.962421 |
26b002e4d6c35828dbf3898164e8dc5c83bb9643 | 873 | md | Markdown | Readme.md | FlorianCassayre/scallion | 101711b5263a76fbd0e339e96de24a9931f7bf97 | [
"Apache-2.0"
] | null | null | null | Readme.md | FlorianCassayre/scallion | 101711b5263a76fbd0e339e96de24a9931f7bf97 | [
"Apache-2.0"
] | null | null | null | Readme.md | FlorianCassayre/scallion | 101711b5263a76fbd0e339e96de24a9931f7bf97 | [
"Apache-2.0"
] | null | null | null | <p align="center">
<img src="images/scallion.png" width="300px" alt="SCALL1ON" />
</p>
# Overview
Scallion is a library for writing parsers and pretty printers for LL(1) languages in Scala.
# Documentation
A comprehensive Scaladoc API is [available online](https://epfl-lara.github.io/scallion/).
# Examples
* [JSON](example/json/JSON.scala): This example showcases how to build a basic JSON lexer & parser using Scallion.
* [Lambda Calculus](example/lambda/Lambda.scala): This example shows how to get a pretty printer *almost for free* alongside your parser.
* [Calculator](example/calculator/Calculator.scala): This example shows how to use the `operators` combinator to easily handle operators with various associativities and priorities.
* [Roman Numerals](example/roman/Roman.scala): This example presents a simple parser and pretty printer for roman numerals. | 48.5 | 181 | 0.774341 | eng_Latn | 0.972057 |
26b04489dcfa0c2631492c29fb491833a892bcf2 | 1,024 | md | Markdown | includes/app-service-web-deploy-web-host.md | changeworld/azure-docs.de-de | 26492264ace1ad4cfdf80e5234dfed9a106e8012 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-03-12T23:37:21.000Z | 2021-03-12T23:37:21.000Z | includes/app-service-web-deploy-web-host.md | changeworld/azure-docs.de-de | 26492264ace1ad4cfdf80e5234dfed9a106e8012 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/app-service-web-deploy-web-host.md | changeworld/azure-docs.de-de | 26492264ace1ad4cfdf80e5234dfed9a106e8012 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
author: cephalin
ms.service: app-service-web
ms.topic: include
ms.date: 11/03/2016
ms.author: cephalin
ms.openlocfilehash: 4108aca3e5f1d944005f02e56964687c75162b41
ms.sourcegitcommit: e41827d894a4aa12cbff62c51393dfc236297e10
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 11/04/2021
ms.locfileid: "131571339"
---
### <a name="app-service-plan"></a>App Service-Plan
Erstellt den Dienstplan zum Hosten der Web-App. Geben Sie den Namen des Plans über den **hostingPlanName** -Parameter an. Der Speicherort des Plans ist mit demjenigen für die Ressourcengruppe identisch. Der Tarif und die Workergröße werden in den Parametern **sku** und **workerSize** angegeben.
```config
{
"apiVersion": "2015-08-01",
"name": "[parameters('hostingPlanName')]",
"type": "Microsoft.Web/serverfarms",
"location": "[resourceGroup().location]",
"sku": {
"name": "[parameters('sku')]",
"capacity": "[parameters('workerSize')]"
},
"properties": {
"name": "[parameters('hostingPlanName')]"
}
},
```
| 31.030303 | 295 | 0.72168 | deu_Latn | 0.577146 |
26b0f2f3cb223ab6f1903569736c3f301de9878b | 1,877 | md | Markdown | articles/lab-services/connect-virtual-machine-mac-remote-desktop.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 15 | 2017-08-28T07:46:17.000Z | 2022-02-03T12:49:15.000Z | articles/lab-services/connect-virtual-machine-mac-remote-desktop.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 407 | 2018-06-14T16:12:48.000Z | 2021-06-02T16:08:13.000Z | articles/lab-services/connect-virtual-machine-mac-remote-desktop.md | pmsousa/azure-docs.pt-pt | bc487beff48df00493484663c200e44d4b24cb18 | [
"CC-BY-4.0",
"MIT"
] | 17 | 2017-10-04T22:53:31.000Z | 2022-03-10T16:41:59.000Z | ---
title: Como ligar-se a um VM de Serviços de Laboratório Azure da Mac | Microsoft Docs
description: Saiba como ligar-se de um Mac a uma máquina virtual nos Serviços de Laboratório Azure.
ms.topic: article
ms.date: 06/26/2020
ms.openlocfilehash: 674bea13093e185ae991148c2cf96599a273d0bc
ms.sourcegitcommit: f28ebb95ae9aaaff3f87d8388a09b41e0b3445b5
ms.translationtype: MT
ms.contentlocale: pt-PT
ms.lasthandoff: 03/29/2021
ms.locfileid: "85444629"
---
# <a name="connect-to-a-vm-using-remote-desktop-protocol-on-a-mac"></a>Ligue-se a um VM utilizando o Protocolo de Ambiente de Trabalho Remoto num Mac
Esta secção mostra como um aluno pode ligar-se a um laboratório de sala de aula VM de um Mac usando RDP.
## <a name="install-microsoft-remote-desktop-on-a-mac"></a>Instale o Microsoft Remote Desktop num Mac
1. Abra a App Store no seu Mac e procure o **Microsoft Remote Desktop**.
1. Instale a versão mais recente do Microsoft Remote Desktop.
## <a name="access-the-vm-from-your-mac-using-rdp"></a>Aceda ao VM a partir do seu Mac utilizando RDP
1. Abra o ficheiro **RDP** que é descarregado no seu computador com **o Microsoft Remote Desktop** instalado. Deve começar a ligar-se ao VM.
1. **Selecione Continue** se receber o seguinte aviso.
1. Devia ver o VM.
> [!NOTE]
> O exemplo a seguir é para um CentOS Linux VM.
## <a name="next-steps"></a>Passos seguintes
Para aprender a ligar-se aos VMs Do Linux utilizando RDP, consulte [utilizar o ambiente de trabalho remoto para máquinas virtuais Linux](how-to-use-remote-desktop-linux-student.md)
| 45.780488 | 180 | 0.751199 | por_Latn | 0.938451 |
26b1341d2c711c9192ead0438730a2d532df0045 | 3,033 | md | Markdown | src/content/articles/java/spring-basic-2.md | morethanmin/til-hub | ba646046690724f8ebbc2cbcc2a3b5997809d807 | [
"MIT"
] | null | null | null | src/content/articles/java/spring-basic-2.md | morethanmin/til-hub | ba646046690724f8ebbc2cbcc2a3b5997809d807 | [
"MIT"
] | 13 | 2021-05-22T16:08:39.000Z | 2021-06-30T13:19:31.000Z | src/content/articles/java/spring-basic-2.md | morethanmin/til-hub | ba646046690724f8ebbc2cbcc2a3b5997809d807 | [
"MIT"
] | 1 | 2021-09-21T09:13:48.000Z | 2021-09-21T09:13:48.000Z | ---
title: "[Spring Basic 2] api 작성해보기"
description: "스프링 공부해보기"
category: java
createdAt: "2021-12-18"
---
> spring.io에 있는 document를 보고 나름 정리한 글입니다.
> 소스코드는 [이곳](https://github.com/morethanmin/study-spring/tree/main/%5BSpring%20Basic%202%5D%20api%20%EC%9E%91%EC%84%B1%ED%95%B4%EB%B3%B4%EA%B8%B0) 에서 확인하실 수 있습니다
스프링 기반 웹서비스를 빌드하고 시작하는 부분까지 마쳤으니, RESTful한 api를 구성해 보자.
## 목표
[`http://localhost:8080/greeting`](http://localhost:8080/greeting)주소로 HTTP GET request를 요청했을 때 아래와 같은 JSON을 return하게끔 만들어 볼 것이다.
```json
{ "id": 1, "content": "Hello, World!" }
```
또한 `name` parameter도 넣어 줄 수 있게끔 할 것이다.
```json
{ "id": 1, "content": "Hello, User!" }
```
## **Representation Class 생성**
우리의 웹서비스가 어떠게 동작해야 할지 생각해봅시다. http request가 `route: /greeting` 으로 get 요청이 들어올 때, `status 200` 와 함께 body에 `JSON data`를 넣어주어야 한다.
이를 구현하기 위해 우선 JSON data를 생성할 수 있도록 greeting class를 만들어 주자.
> Greeting.java
```java
package com.example.restservice;
public class Greeting {
private final long id;
private final String content;
public Greeting(long id, String content) {
this.id = id;
this.content = content;
}
public long getId() {
return id;
}
public String getContent() {
return content;
}
}
```
## **Resource Controller Class 생성**
이제 http request를 감지하고 greeting 객체를 보내주는 class를 생성하자. 보통 이러한 클래스를 controller라고 부른다.
각각의 코드들에 내 나름의 주석을 달아두었다.
> GreetingController.java
```java
package com.jade.studyspring;
import java.util.concurrent.atomic.AtomicLong;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RequestParam;
import org.springframework.web.bind.annotation.RestController;
//GreetingController 클래스를 RestController로 정의해주는 annotation
@RestController
public class GreetingController {
private static final String template = "Hello, %s!";
private final AtomicLong counter = new AtomicLong();
//greeting 함수를 /greeting route에 mapping해주는 annotation
@GetMapping("/greeting")
//Gretting을 반환하는 greeting 함수 정의, String name의 값엔 annotation에 명시된 값이 들어감.
public Greeting greeting(@RequestParam(value = "name", defaultValue = "World") String name) {
return new Greeting(counter.incrementAndGet(), String.format(template, name));
}
}
```
spring에서 제공하는 각각의 애노테이션에 대해 추가 설명하겠다.
`@GetMapping` 은 http get request가 요청될 경우 해당 함수를 실행하도록 명시해준다.
좀더 응용해서 `@PostMapping` 은 http post request가 요청될 경우 일 것이고, `@RequestMapping(method=GET)` 다음과 같이 애노테이션을 정의해 줄 수도있다.
물론 이 용어를 다 알고있어야 하는건 아니고, 개념을 이해하고 doc에서 활용해 사용할 수 있기만 하면 될 것이다.
매핑된 함수같은 경우는 `Greeting` 을 반환하는 `greeting` 함수이고, parameter는 `String name` 이 들어가 있는데, 해당 변수에는 `@RequestParam` 이라는 애노테이션이 들어가 있는 형태이고, 해당 애노테이션 이름에서 유추할 수 있듯이 http request에서 name parameter를 가져오고 없는경우엔 `World` 로 선언해주는 것을 볼 수 있다.
이후 Greeting 객체를 반환하고 있는 모습이다. 이때 반환되는 값은 `JSON` 형태여야 하는데 이는 HTTP message converter의 도움으로 알아서 반환해준다고 한다.
## 프로젝트 빌드 및 실행
프로젝트 빌드는 이전에 했던 것처럼 `./gradlew build` 를 입력해 빌드하고, `java -jar {파일명}.jar` 를 입력하여 실행해주면 된다.
이제 [`http://localhost:8080/greeting`](http://localhost:8080/greeting) 으로 접속해보면 정상적으로 동작하는 것을 확인할 수 있다!
| 28.083333 | 224 | 0.729641 | kor_Hang | 0.999981 |
26b1644209bf92f10d6e37b45da8ff33defe9ec1 | 4,020 | md | Markdown | articles/azure-netapp-files/configure-unix-permissions-change-ownership-mode.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-netapp-files/configure-unix-permissions-change-ownership-mode.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-netapp-files/configure-unix-permissions-change-ownership-mode.md | KazuOnuki/azure-docs.ja-jp | 4dc313dec47a4efdb0258a8b21b45c5376de7ffc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Unix のアクセス許可を構成し、Azure NetApp Files NFS およびデュアル プロトコル ボリュームの所有権モードを変更する | Microsoft Docs
description: Unix のアクセス許可の設定方法と、Azure NetApp Files NFS およびデュアル プロトコル ボリュームの所有権モードの変更オプションについて説明します。
services: azure-netapp-files
documentationcenter: ''
author: b-juche
manager: ''
editor: ''
ms.assetid: ''
ms.service: azure-netapp-files
ms.workload: storage
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: how-to
ms.date: 08/06/2021
ms.author: b-juche
ms.openlocfilehash: bfb794b1344dbc4723ca699f572b487b54d60c77
ms.sourcegitcommit: 0046757af1da267fc2f0e88617c633524883795f
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 08/13/2021
ms.locfileid: "121781318"
---
# <a name="configure-unix-permissions-and-change-ownership-mode-for-nfs-and-dual-protocol-volumes"></a>Unix のアクセス許可を構成し、NFS およびデュアル プロトコル ボリュームの所有権モードを変更する
`Unix` セキュリティ スタイルの Azure NetApp Files NFS ボリュームまたはデュアル プロトコル ボリュームの場合、**Unix のアクセス許可** を設定するオプションと、**所有権モードの変更** ( **`Chown Mode`** ) オプションがあります。 これらの設定は、ボリュームの作成時またはボリュームの作成後に指定できます。
## <a name="unix-permissions"></a>Unix のアクセス許可
Azure NetApp Files の **Unix のアクセス許可** 機能を使用すると、マウント パスの変更アクセス許可を指定できます。 この設定は、マウント パスの下のファイルには適用されません。
Unix のアクセス許可設定は、既定で `0770` に設定されています。 この既定の設定では、所有者とグループに読み取り、書き込み、実行のアクセス許可が付与されますが、他のユーザーにはアクセス許可は付与されません。
カスタム Unix アクセス許可の値 (例: `0755`) を指定して、所有者、グループ、または他のユーザーに必要なアクセス許可を付与できます。
## <a name="change-ownership-mode"></a>所有権モードの変更
所有権モードの変更 ( **`Chown Mode`** ) 機能を使用すると、ファイルとディレクトリの所有権管理機能を設定できます。 ボリュームのエクスポート ポリシーで設定を指定または変更できます。 **`Chown Mode`** には、次の 2 つのオプションを使用できます。
* `Restricted` (既定値) - ルート ユーザーのみがファイルとディレクトリの所有権を変更できます。
* `Unrestricted` - ルート以外のユーザーは、自身が所有するファイルとディレクトリの所有権を変更できます。
## <a name="considerations"></a>考慮事項
* 指定した Unix アクセス許可は、ボリューム マウント ポイント (ルート ディレクトリ) にのみ適用されます。
* リージョン間レプリケーション構成内のソースまたは宛先のボリュームに対する Unix アクセス許可を変更することはできません。
## <a name="steps"></a>手順
1. Unix のアクセス許可と所有権モードの変更機能は、現在プレビュー段階です。 これらの機能を初めて使用する場合は、事前にこれらの機能を登録する必要があります。
1. **Unix のアクセス許可** 機能を登録します。
```azurepowershell-interactive
Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFUnixPermissions
```
2. **所有権モードの変更** 機能を登録します。
```azurepowershell-interactive
Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFChownMode
```
3. 機能の登録の状態を確認します。
> [!NOTE]
> **RegistrationState** が `Registering` 状態から `Registered` に変化するまでに最大 60 分間かかる場合があります。 この状態が `Registered` になってから続行してください。
```azurepowershell-interactive
Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFUnixPermissions
Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFChownMode
```
また、[Azure CLI のコマンド](/cli/azure/feature) `az feature register` と `az feature show` を使用して、機能を登録し、登録状態を表示することもできます。
2. [NFS ボリュームを作成する](azure-netapp-files-create-volumes.md)とき、または [デュアル プロトコル ボリュームを作成する](create-volumes-dual-protocol.md)ときに、 **[プロトコル]** タブで **Unix のアクセス許可** を指定し、所有権モード ( **`Chown Mode`** ) の設定を変更できます。
次の例は、NFS ボリュームの [ボリュームの作成] 画面を示しています。
![NFS の [ボリュームの作成] 画面を示すスクリーンショット。](../media/azure-netapp-files/unix-permissions-create-nfs-volume.png)
3. 既存の NFS またはデュアル プロトコル ボリュームの場合、**Unix のアクセス許可** を設定または変更し、次のように **所有権モードを変更** できます。
1. Unix のアクセス許可を変更するには、その **ボリューム** を右クリックし、 **[編集]** を選択します。 表示される [編集] ウィンドウで、 **[Unix のアクセス許可]** の値を指定します。
![[Unix のアクセス許可] の [編集] 画面を示すスクリーンショット。](../media/azure-netapp-files/unix-permissions-edit.png)
2. 所有権モードの変更を修正するには、その **ボリューム** をクリックし、 **[ポリシーのエクスポート]** をクリックして **`Chown Mode`** 設定を変更します。
![[ポリシーのエクスポート] 画面を示すスクリーンショット。](../media/azure-netapp-files/chown-mode-edit.png)
## <a name="next-steps"></a>次のステップ
* [Azure NetApp Files の NFS ボリュームを作成する](azure-netapp-files-create-volumes.md)
* [Azure NetApp Files のデュアルプロトコル ボリュームを作成する](create-volumes-dual-protocol.md)
* [エクスポート ポリシーを構成する](azure-netapp-files-configure-export-policy.md)
| 42.315789 | 203 | 0.741045 | yue_Hant | 0.805185 |
26b1ace10395924254df4e8ceb6238c747d7e135 | 106 | md | Markdown | README.md | rksharma1401/spring-cloud-config-client | 6363782fe9170d80266951f259d925702ee845b5 | [
"MIT"
] | 1 | 2021-06-09T14:17:10.000Z | 2021-06-09T14:17:10.000Z | README.md | rksharma1401/spring-cloud-config-client | 6363782fe9170d80266951f259d925702ee845b5 | [
"MIT"
] | null | null | null | README.md | rksharma1401/spring-cloud-config-client | 6363782fe9170d80266951f259d925702ee845b5 | [
"MIT"
] | null | null | null | # spring-cloud-config-client
client for spring cloud server
# connect to Eureka register and call service
| 26.5 | 45 | 0.811321 | eng_Latn | 0.981628 |
26b1db08efb20772bbb63f7da3acc41d01084369 | 17 | md | Markdown | README.md | kangkona/awesome-abtest | aa81aa55f1f4251043668c2ef2d91b62d1bd56ce | [
"Unlicense"
] | null | null | null | README.md | kangkona/awesome-abtest | aa81aa55f1f4251043668c2ef2d91b62d1bd56ce | [
"Unlicense"
] | null | null | null | README.md | kangkona/awesome-abtest | aa81aa55f1f4251043668c2ef2d91b62d1bd56ce | [
"Unlicense"
] | null | null | null | # awesome-abtest
| 8.5 | 16 | 0.764706 | deu_Latn | 0.599054 |
26b265e584ff843712fbb971cf9ccf5f7b3a23de | 730 | md | Markdown | docs/api.md | bemoje/bemoje-arr-partition-index | d8c4b47589ef4fe900377975f9ea74c953f23992 | [
"MIT"
] | null | null | null | docs/api.md | bemoje/bemoje-arr-partition-index | d8c4b47589ef4fe900377975f9ea74c953f23992 | [
"MIT"
] | null | null | null | docs/api.md | bemoje/bemoje-arr-partition-index | d8c4b47589ef4fe900377975f9ea74c953f23992 | [
"MIT"
] | null | null | null | <!-- Generated by documentation.js. Update this documentation by updating the source code. -->
### Table of Contents
- [arrPartitionIndex][1]
- [Parameters][2]
## arrPartitionIndex
Linear-time Partitioning. Runtime: O(n). Chooses a pivot and re-arrages the array so that everything on the left is <= pivot and everything on the right is > pivot
### Parameters
- `arr` **[Array][3]**
- `lo` **[number][4]** start index
- `hi` **[number][4]** end index
Returns **[number][4]** pivot index
[1]: #arrpartitionindex
[2]: #parameters
[3]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Array
[4]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Number
| 27.037037 | 166 | 0.69863 | eng_Latn | 0.578231 |
26b2f4697d60d34be02dcc11acb3ac4067347732 | 571 | md | Markdown | docs/resizeArea(images:size:alignCorners:).md | ematejska/swift-1 | e7464be4052a93553c82b3e2e67ba670e45f0c5c | [
"Apache-2.0"
] | null | null | null | docs/resizeArea(images:size:alignCorners:).md | ematejska/swift-1 | e7464be4052a93553c82b3e2e67ba670e45f0c5c | [
"Apache-2.0"
] | null | null | null | docs/resizeArea(images:size:alignCorners:).md | ematejska/swift-1 | e7464be4052a93553c82b3e2e67ba670e45f0c5c | [
"Apache-2.0"
] | null | null | null | # resizeArea(images:size:alignCorners:)
Resize images to size using area interpolation.
``` swift
@inlinable public func resizeArea<Scalar: TensorFlowNumeric>(images: Tensor<Scalar>, size: (newHeight: Int, newWidth: Int), alignCorners: Bool = false) -> Tensor<Float>
```
> Precondition: The images must have rank \`3\` or \`4\`.
> Precondition: The size must be positive.
## Parameters
- images: - images: 4-D `Tensor` of shape `[batch, height, width, channels]` or 3-D `Tensor` of shape `[height, width, channels]`.
- size: - size: The new size of the images.
| 33.588235 | 168 | 0.704028 | eng_Latn | 0.873759 |
26b3addaf2363493fa634e5576644916f0d6ebcc | 311 | md | Markdown | markdown/2-milestone.md | Redislabs-Solution-Architects/azure-openshift-redis-enterprise-delivery | a78ec7df300735171810862bc095db4547a80300 | [
"MIT"
] | null | null | null | markdown/2-milestone.md | Redislabs-Solution-Architects/azure-openshift-redis-enterprise-delivery | a78ec7df300735171810862bc095db4547a80300 | [
"MIT"
] | null | null | null | markdown/2-milestone.md | Redislabs-Solution-Architects/azure-openshift-redis-enterprise-delivery | a78ec7df300735171810862bc095db4547a80300 | [
"MIT"
] | 1 | 2021-08-16T23:22:21.000Z | 2021-08-16T23:22:21.000Z | ## Redis Enterprise via OpenShift Marketplace
#### Enablement Session
---
#### Redis OSS
- Ubiquitous
- In-memory data structure store
- Cache
- Database
- Message Broker
- Low Latency
---
### Redis Enterprise
- Geo-Replication
- Conflict Resolution Data Types
- Enterprise Flash
- Modules
---
### Q&A | 15.55 | 45 | 0.691318 | kor_Hang | 0.694489 |
26b3e3fac4dc5a9a81e358266bb3693c950b6d02 | 19,735 | md | Markdown | HIP/hip-336.md | Ashe-Oro/hedera-improvement-proposal | 9699eac916cc7f82cce1b32338bd7136b1b40b76 | [
"Apache-2.0"
] | null | null | null | HIP/hip-336.md | Ashe-Oro/hedera-improvement-proposal | 9699eac916cc7f82cce1b32338bd7136b1b40b76 | [
"Apache-2.0"
] | null | null | null | HIP/hip-336.md | Ashe-Oro/hedera-improvement-proposal | 9699eac916cc7f82cce1b32338bd7136b1b40b76 | [
"Apache-2.0"
] | 1 | 2021-10-13T07:21:34.000Z | 2021-10-13T07:21:34.000Z | ---
hip: 336
title: Approval and Allowance API for Tokens
author: Albert Tam <albert.tam@hedera.com>
type: Standards Track
category: Service
needs-council-approval: Yes
last-call-date-time: 2021-02-14T07:00:00Z
status: Approved
created: 2022-01-11
discussions-to: https://github.com/hashgraph/hedera-improvement-proposal/discussions/337
updated: 2022-04-11
---
## Abstract
Describes the addition of Services APIs to approve and exercise allowances to a third party account. The allowances grant another account the right to transfer hbar, fungible and non-fungible tokens from your account.
## Motivation
The current Services CryptoTransfer API allows a user to transfer hbar, fungible and non-fungible tokens but does not permit any other account to act as a delegate or proxy. The addition of the allowance APIs will permit cryptocurrency exchanges and wallets to trade on their customer's behalf without requiring the customer to sign every transaction in advance.
## User stories
As a user, I want to enable another user the ability to spend `x` tokens (hbar and fungible tokens) from my account so that they can trade on my behalf without requiring that I expose my private key to them.
As a user, I want to enable another user the ability to spend specific non-fungible tokens from my account so that they can trade on my behalf without requiring that I expose my private key to them.
As a user, I want to enable another user the ability to spend all instances of a particular non-fungible token that I currently or may in the future hold in my account so that they can trade on my behalf without requiring that I expose my private key to them.
As a user, I want to modify or remove an allowance I have granted to another user so that I can manage that user's ability to spend my tokens over time.
As a user that has been granted an allowance, I want to be able to transfer tokens owned by the owner account as if they were my tokens so that I can issue transfers on their behalf without them having to expose their private key.
## Specification
### Terminology
The following terms will be used repeatedly throughout this section:
- owner: the account that owns the tokens.
- spender: the delegate account, the account being granted the power to spend the owner’s tokens.
- recipient: the receiver of tokens when the spender issues a `CryptoTransfer` operation.
### Add CryptoApproveAllowance API
A new Hedera API will be added under the Crypto Service called `CryptoApproveAllowance`. This function is called by the token owner to create a series of allowances for a spender account.
```protobuf
message CryptoAllowance {
AccountID owner = 1;
AccountID spender = 2;
int64 amount = 3;
}
message TokenAllowance {
TokenID tokenId = 1;
AccountID owner = 2;
AccountID spender = 3;
int64 amount = 4;
}
message NftAllowance {
TokenID tokenId = 1;
AccountID owner = 2;
AccountID spender = 3;
repeated int64 serial_numbers = 4;
google.protobuf.BoolValue approved_for_all = 5;
AccountID delegating_spender = 6;
}
message CryptoApproveAllowanceTransactionBody {
repeated CryptoApproval cryptoAllowances = 1;
repeated NftAllowance nftAllowances = 2;
repeated TokenAllowance tokenAllowances = 3;
}
```
This function contains a list of hbar and/or token approval messages. The `CryptoAllowance` and `TokenAllowance` messages will set an allowance of `amount` hbar or fungible tokens that can be transferred from the owner's account to another account by the `spender` account. The `NftAllowance` message sets an allowance for specific NFT serial numbers within the owner's account. Each of the hbar/token approvals in the list do not need to refer to the same spender. The owner can establish different allowances for various spenders in a single transaction.
The total number of approvals contained within the transaction body cannot exceed 20. This number includes all hbar, fungible and non-fungible token approvals. Note that each NFT serial number counts as a single approval, hence a transaction granting 20 serial numbers to a spender will use all of the approvals permitted for the transaction.
The `amount` must be specified in terms of the `decimals` value for the token. If `amount` is 0 the transaction will remove the `spender`'s allowance from the owner's account, thereby freeing an allowance for future use.
A single NFT serial number can only be granted to one spender at a time. If an approval assigns a previously approved NFT serial number to a new user, the old user will have their approval removed. For example, if the following scenario were to occur:
1. *userA* approves *userB* to use NFT *T* with serial *S*
2. *userA* approves *userC* to use NFT *T* with serial *S*
the end result will be that *userC* will hold an allowance to NFT *T* serial *S* while *userB* will have their allowance for NFT *T* serial *S* removed.
In order to grant the `spender` access to *all* of the owner's instances of a particular NFT, the `approved_for_all` field in the `NftAllowance` message should be set to `true`.
If the `spender` has already been granted `approved_for_all` for an owner's NFT and another transaction granting `approved_for_all` is sent for the same NFT, the transaction will be accepted and fees charged but it will effectively be a no-op. Similarly if multiple transactions to remove `approved_for_all` on the same NFT are received the effect will be idempotent.
If the `spender` has been granted `approved_for_all` for an owner's NFT, the `spender` will in turn be permitted to approve an NFT serial number be spent by yet another spender. In other words, an `approved_for_all` spender effectively has the same privileges as the owner of the NFT. This behavior is consistent with the ERC721 implementation and is included here for backward compatibility of Ethereum smart contracts being ported over to Hedera. For signature checking performance considerations, the `spender` must set the `delegating_spender` field to their account and sign the transaction when spending using an `approved_for_all` privilege. Failure to do so will result in an `INVALID_SIGNATURE` error. If the `spender` does not set the `delegating_spender` field, the transaction will be treated as if it were a regular approval, meaning the `owner` signature will be required.
For hbar and fungible token approvals, the amounts specified in the transaction will overwrite the current value of the `spender`'s allowance with the `owner`. For NFT approvals, each approval will add the specified serial numbers to the `spender`'s allowance.
It is not an error if the total token amount in the owner's account is less than the specified allowance `amount`. If the `spender` tries to transfer more tokens than exists in the owner's account that transaction will fail.
It *IS* an error if an NFT allowance specifies a serial number that the owner does not have possession of.
It is not an error if either the spender or owner's accounts are frozen or KYC-revoked for the specified token type. If the `spender` tries to transfer a token under these conditions, the transaction will fail anyway.
It is not an error if the token is paused and an allowance approval is submitted.
Duplicate approvals are permitted although they will count against the 20 approval limit per transaction. In the event of a duplicate approval, the last occurrence of the spender's approval will be used.
The transaction must be signed by the owner's account and the account paying the transaction fees for the transaction. If the owner is paying the transaction fees only their signature is required.
Each account is limited to 100 allowances. This limit spans hbar and fungible token allowances and non-fungible token `approved_for_all` grants. There is no limit on the number of NFT serial number approvals an owner may grant.
The number of allowances set on an account will increase the auto renewal fee for the account. Conversely, removing allowances will decrease the auto renewal fee for the account.
The allowance approval transaction will fail under the following circumstances:
- The `spender` account is the same as the owner's account.
- The `amount` will exceed the maximum supply of the token.
- `amount` is negative.
- The owner account is not associated with the specified token.
- The owner account does not own the specified NFT serial numbers.
- A serial number for an NFT does not exist.
- The token referenced in an NFT allowance is fungible.
- No allowances are specified.
### Add CryptoDeleteAllowance API
A new Hedera API will be added under the Crypto Service called `CryptoDeleteAllowance`. This function is called by the token owner to delete allowances for NFTs only. In order to delete an existing hbar or fungible token allowance the `CryptoApproveAllowance` API should be used with an `amount` of 0.
```protobuf
// new message
message NftRemoveAllowance {
TokenID token_id = 1;
AccountID owner = 2;
repeated int64 serial_numbers = 3;
}
// new message
message CryptoDeleteAllowanceTransactionBody {
repeated NftRemoveAllowance nftAllowances = 2;
}
```
The `NftWipeAllowance` message is used to remove a number of NFT serial number allowances regardless of who the spender currently is.
A single `CryptoDeleteAllowanceTransactionBody` can specify the removal of allowances belonging to multiple owners so long as all parties sign the transaction.
The total number of NFT serial number deletions contained within the transaction body cannot exceed 20.
The transaction will not fail if the owner has not granted any allowances and a deletion is attempted.
It is not an error if the owner's account is frozen or KYC-revoked for the specified token type.
It is not an error if the token is paused and an allowance deletion is submitted.
Duplicate deletions are permitted although they will count against the 20 deletion limit per transaction. In the event of a duplicate deletion, the last occurrence of the spender's deletion will be used.
The transaction must be signed by the owner's account and the account paying the transaction fees for the transaction. If the owner is paying the transaction fees only their signature is required.
The deletion transaction will fail under the following circumstances:
- The owner account is not associated with the specified token.
- The owner account does not own the specified NFT serial numbers.
- A serial number for an NFT does not exist.
- The token referenced is fungible.
- No allowances are specified.
### Change CryptoTransfer to Support Approved Allowances
The existing CryptoTransfer API will be used to support the transfer of tokens by a `spender` under their approved allowance. The existing protobuf message for `CryptoTransfer` will be reused with one minor change to the `AccountAmount` and `NftTransfer` messages - the addition of an `is_approval` field to indicate whether the transfer involves an approved transfer or not.
```protobuf
// existing protobuf
message CryptoTransferTransactionBody {
TransferList transfers = 1;
repeated TokenTransferList tokenTransfers = 2;
}
// existing protobuf
message TransferList {
repeated AccountAmount accountAmounts = 1;
}
// changed protobuf
message AccountAmount {
// existing fields
AccountID accountID = 1;
sint64 amount = 2;
// new field
bool is_approval = 3;
}
// existing protobuf
message TokenTransferList {
TokenID token = 1;
repeated AccountAmount transfers = 2;
repeated NftTransfer nftTransfers = 3;
}
// changed protobuf
message NftTransfer {
// existing fields
AccountID senderAccountID = 1;
AccountID receiverAccountID = 2;
int64 serialNumber = 3;
// new field
bool is_approval = 4;
}
```
To treat a transfer as an allowance transfer, we have to check if the transaction is signed by the debiting account. It is costly to expand signatures and verify this again during the balance adjustments. So to help us avoid this, a new boolean flag `is_approval` is added to the `AccountAmount` and `NftTransfer` messages which denotes that the transfer has to be treated as allowance transfer if it set to `true`. This gives a lot of flexibility now as a transaction can contain a list of regular transfers and approved transfers, each potentially referencing a different token and/or owner.
The `is_approval` field must be set to `true` for transfers that will involve an approved allowance otherwise a regular transfer will be assumed. For hbar and fungible transfers the `is_approval` field must be set on the debiting `AccountAmount` while for NFTs the `is_approval` field is set on the transfer message itself. Multiple owner accounts can be involved in a single transfer by setting `is_approval` to `true` for each of the owner `AccountAmount` messages.
The spender (acting here as the caller) must sign the transaction. The owner of the token (the party that approved the spender's allowance) is not required to sign the transaction.
The transaction fees will be paid from the caller's account and not the owner's. This behavior is similar to regular crypto/token transfers as well as Ethereum-based ERC20 tokens transferred under `transferFrom`.
Custom fees are charged in exactly the same manner as regular transfers are.
- If `net_of_transfers` is enabled for fractional fees, the recipient will receive the complete `amount` during the transfer; otherwise a portion of the `amount` will be deducted from the recipient.
- The limit for multi-level custom fees still remains at 2 with no cycles permitted (other than the case of a token paying fees in its own units).
The spender's token allowance with the owner will be decreased by the transfer `amount` and will **not** include the customFees involved in the transfer. If the transfer `amount` will decrease the spender's allowance to zero, this transaction will effectively remove the spender's allowance from the owner’s account.
If NFTs are transferred, the spender's claim on each of the serial numbers will be removed from the NFT object itself. Since the exact list of granted serial numbers is not tracked on the owner account, no allowance update needs to be made to the owner account. Note that once an NFT is transferred from the owner's account, any associated allowance for the pertinent serial numbers will be removed. **An NFT approval will only exist so long as the owner maintains possession of the NFT serial number.**
The transfer transaction will fail under the following circumstances:
- The `accountID` sending and receiving the token cannot be the same address.
- The recipient account does not have an association with the token yet.
- If the recipient account has auto-association enabled, at least one open slot must be available for the transfer to succeed.
- The recipient account has `receiverSigRequired` enabled and the recipient has not signed the transaction.
- The owner account does not have `amount` of token available.
- The transfer `amount` plus custom fixed fees will exceed the total amount of token available.
- The spender does not have an allowance established with the owner for the specified token.
- The `amount` to transfer exceeds the spender's available allowance.
- An NFT serial number is being transferred and the owner does not have possession of it.
- Either the owner or recipient accounts are frozen for the specified token.
- The specified `token` is paused.
### Add Spender ID to TokenNftInfo
The current spender that has been approved access to an NFT serial number will be added to the `TokenNftInfo` message that is returned as part of the `TokenGetNftInfoResponse` and `TokenGetNftInfosResponse`.
```protobuf
// existing message
message TokenNftInfo {
// existing fields
NftID nftID = 1;
AccountID accountID = 2; // current owner
Timestamp creationTime = 3;
bytes metadata = 4;
bytes ledger_id = 5;
// new field
AccountID spender_id = 6;
}
```
Only one spender can be assigned to an NFT serial number at a time.
If the NFT serial number has not been approved to spend by an account, the `spender_id` field will not be included.
## Backwards Compatibility
The CryptoApproveAllowance and CryptoDeleteAllowance transactions are new additions to the API and will not have any backward compatibility issues to address.
The CryptoTransfer transaction is not incurring any API/signature changes but the backend implementation is being changed to accommodate the proposed allowance/approval mechanism. Transactions submitted by the spender that seek to utilize the allowance feature before the feature is enabled will fail validation since the owner has not signed the transaction. Once the feature is enabled, regular transfers will still be handled in the same manner and spender approved transfers will also be permitted.
## Security Implications
The approved allowances APIs discussed herein were inspired by ERC-20. The attack vector related to the ERC-20 `approve()` method is not relevant to the Hedera implementation since the former's vulnerability is the result of possible transaction ordering by the miner while the Hedera hashgraph consensus protocol does not permit reordering of transactions.
## Rejected Ideas
### Introduce New API for Approved Transfers
The initial proposal introduced a new transaction API for transferring tokens that would support an approved transfer list. This API would only allow a spender to submit approved transfers and did not include regular crypto or token transfers. During design review several Hedera engineers felt that there should only be a single transfer API rather than two. Upon further inspection it was found that the current CryptoTransfer message format could support approved transfers in addition to regular transfers.
### Support One Allowance in Approval API
The approval API introduced in the initial proposal only permitted one allowance to be specified via a `oneof`, either an hbar or a token allowance. During internal design reviews, it was felt that since the `oneof` was the only field in the `CryptoApproveAllowanceTransactionBody` message, it would make more sense to separate the `CryptoAllowance` and `TokenAllowance` messages into distinct transaction body messages. Additionally, specifying both hbar and token approvals (as lists) within a single transaction permits the caller to specify multiple approvals in bulk rather than issuing many calls.
### Maintain List of Approved NFTs in Account
The initial proposal maintained an `Account` mapping that would track all NFT serial numbers that were approved. Each map entry consisted of an NFT tokenId-spenderAccountId composite key and an array of NFT serial numbers. This approach would consume 16 bytes per NFT serial number in the worst case (assuming a different NFT token per serial number). The current approach does not keep track of the approved NFTs from the `Account` but rather tracks the spender on the NFT serial number object itself and only incurs a cost of 4 bytes per NFT serial number. The loss of the NFT approval list on the `Account` is a potential usability issue but this same deficiency is found in the ERC721 implementation so migrating users will not be losing any functionality. Additionally this same query could be served by a mirror node API in the future.
## Open Issues
## References
- [ERC20 Specification](https://ethereum.org/en/developers/docs/standards/tokens/erc-20/)
- [ERC20 API](https://docs.openzeppelin.com/contracts/2.x/api/token/erc20)
- [ERC721 API](https://docs.openzeppelin.com/contracts/2.x/api/token/erc721)
## Copyright/license
This document is licensed under the Apache License, Version 2.0 -- see [LICENSE](../LICENSE) or (https://www.apache.org/licenses/LICENSE-2.0)
| 65.132013 | 886 | 0.794223 | eng_Latn | 0.999071 |
26b42fc2590750cbd3e34cf28d9b93651685675a | 2,515 | md | Markdown | README.md | tungvoduc/DTParallaxViewController | a04c3e549667cbac735158b5287eb0ecbff84925 | [
"MIT"
] | null | null | null | README.md | tungvoduc/DTParallaxViewController | a04c3e549667cbac735158b5287eb0ecbff84925 | [
"MIT"
] | null | null | null | README.md | tungvoduc/DTParallaxViewController | a04c3e549667cbac735158b5287eb0ecbff84925 | [
"MIT"
] | null | null | null | # DTParallaxScrollViewController
[](https://travis-ci.org/Tung Vo/DTParallaxScrollViewController)
[](http://cocoapods.org/pods/DTParallaxScrollViewController)
[](http://cocoapods.org/pods/DTParallaxScrollViewController)
[](http://cocoapods.org/pods/DTParallaxScrollViewController)
## Example
DTParallaxScrollView is a custom UIView that creates parallax scroll view vertical effects. You can use it to apply the effect to your UITableView or UICollectionView or UIScrollView in general.
For example, if you want to have a map view on top of a table view and you want to be able to interact with both the map view and table view without any conflictions.
You can subclass DTParallaxScrollViewController, and then call this in initializer:
```
super.init(scrollView: tableView, headerHeight: kHeaderHeight)
```
where scrollView is the view you want to apply parallax effect and headerHeight is height of header.
set delegate for parallax scroll view controller
```
self.delegate = object
```
conforms DTParallaxScrollViewDelegate in deleget object
```
func parallaxScrollViewViewForHeader(viewController: DTParallaxScrollView) -> UIView {
return mapView
}
```
Here is how you make parallax effect
```
self.updateBlock = {(yOffset: CGFloat, visible: Bool) -> Void in
if yOffset < 0 {
let scaleFactor = 1 + abs(yOffset/self.headerHeight)
self._mapView.transform = CGAffineTransformMakeScale(scaleFactor, scaleFactor)
}
else {
self._mapView.transform = CGAffineTransformIdentity
}
}
```
Instead of using DTParallaxScrollViewController, you can also use DTParallaxScrollView to achieve the same effect.
To run the example project, clone the repo, and run `pod install` from the Example directory first.
## Requirements
## Installation
DTParallaxScrollViewController is available through [CocoaPods](http://cocoapods.org). To install
it, simply add the following line to your Podfile:
```ruby
pod "DTParallaxScrollViewController"
```
## Author
Tung Vo, tung98.dn@gmail.com
## License
DTParallaxScrollViewController is available under the MIT license. See the LICENSE file for more info.
| 38.106061 | 195 | 0.785288 | eng_Latn | 0.697981 |
26b47da21d745afb9c52f7a18c988572352f4bc5 | 2,516 | md | Markdown | _posts/2016-05-21-censorthis-censor-the-words-cf.md | limsoo5788/limsoo5788.github.io | 69f28b5d084160fc4095d87c7f94248b117b9823 | [
"MIT"
] | 1 | 2018-10-12T11:43:30.000Z | 2018-10-12T11:43:30.000Z | _posts/2016-05-21-censorthis-censor-the-words-cf.md | limsoo5788/limsoo5788.github.io | 69f28b5d084160fc4095d87c7f94248b117b9823 | [
"MIT"
] | null | null | null | _posts/2016-05-21-censorthis-censor-the-words-cf.md | limsoo5788/limsoo5788.github.io | 69f28b5d084160fc4095d87c7f94248b117b9823 | [
"MIT"
] | null | null | null | ---
layout: post
title: "CensorThis - Censor the words [CF]"
date: 2016-05-22 04:17:54 +0700
categories: [python, codefights]
---
Author Question: **Argaen**
Code Fights Weekly has gained popularity in the past months and is receiving lots of fan letters. Unfortunately, some of the readers use offensive words and the editor wants to keep the magazine family friendly.
To manage this, you have been asked to implement a censorship algorithm. You will be given the fan letter `text` and a list of `forbiddenWords`. Your algorithm should replace all occurrences of the forbidden words in the text with sequences of asterisks of the same length.
Be careful to censor only words, no one want to see `"classic"` spelled as `"cl***ic"`.
**Example**
For text = "The cat does not like the fire" and
forbiddenWords = ["cat","fire"], the output should be
`CensorThis(text, forbiddenWords) = "The *** does not like the ****".
* **[input] string text**
Text to censor, composed of mixed case English words separated by a single whitespace character each.
* **[input] array.string forbiddenWords**
The list of words to censor, all in lowercase.
* **[output] string**
The censored text. Its length should be the same as the length of text.
**Solution:**
```python
def CensorThis(text, forbiddenWords):
return ' '.join([ t.replace(t, "*" * len(t)) if t.lower() in forbiddenWords else t for t in text.split() ])
```
**Test 1**
```
text: "The cat does not like the fire"
forbiddenWords: ["cat", "fire"]
Expected Output: "The *** does not like the ****"
```
**Test 2**
```
text: "The cat does not like the therapy"
forbiddenWords: ["the", "like"]
Expected Output: "*** cat does not **** *** therapy"
```
**Test 3**
```
text: "Python is the BEST programming language and LOLCODE is the Worst"
forbiddenWords: ["worst", "best"]
Expected Output: "Python is the **** programming language and LOLCODE is the *****"
```
**Test 4**
```
text: "A bald eagle is a worthy adversary"
forbiddenWords: ["bald", "a"]
Expected Output: "* **** eagle is * worthy adversary"
```
**Test 5**
```
text: "The MAGIC words are fiz buzz and plaf"
forbiddenWords: []
Expected Output: "The MAGIC words are fiz buzz and plaf"
```
**Test 6**
```
text: "The MAGIC words are fiz buzz and plaf"
forbiddenWords: ["fluzz", "z", "ping", "narf", "tedd", "troz", "zort"]
Expected Output: "The MAGIC words are fiz buzz and plaf"
```
Thanks to **GOD**. | 28.269663 | 274 | 0.664944 | eng_Latn | 0.987676 |
26b4b944d5f5b9d87340bf0010e42e2b2bb3a0f8 | 442 | md | Markdown | README.md | mcnegan/Portfolio | ef8568b3595bec271e7a28c68f2cf68014afb69a | [
"MIT"
] | null | null | null | README.md | mcnegan/Portfolio | ef8568b3595bec271e7a28c68f2cf68014afb69a | [
"MIT"
] | null | null | null | README.md | mcnegan/Portfolio | ef8568b3595bec271e7a28c68f2cf68014afb69a | [
"MIT"
] | null | null | null | # portfólio
Portfólio do desenvolvedor Mauricio Pantoja formado em Graduação no Curso Superior Tecnológico em Análise e Desenvolvimento de Sistemas e com Pós-Graduação em Desenvolvimento Mobile na Universidade Anhanguera UNIDERP.
## Tarefas
O controle das tarefas desse projeto será realizado no GitHub
## Ícones
- :package: nova funcionalidade
- :up: atualização
- :panda_face: correção de bug
- :checkered_flag: release
| 29.466667 | 218 | 0.778281 | por_Latn | 0.999759 |
26b4c257d630659dc833507a115fe517847701b4 | 1,030 | markdown | Markdown | oldposts/2015-10-17-3d-touch-ios9.markdown | DanBennettUK/danbennettuk.github.io | 9dee62a744fd4cea107bc8744cea291044ea5dbd | [
"MIT"
] | null | null | null | oldposts/2015-10-17-3d-touch-ios9.markdown | DanBennettUK/danbennettuk.github.io | 9dee62a744fd4cea107bc8744cea291044ea5dbd | [
"MIT"
] | 73 | 2019-07-18T14:17:12.000Z | 2022-03-05T03:46:18.000Z | oldposts/2015-10-17-3d-touch-ios9.markdown | DanBennettUK/danbennettuk.github.io | 9dee62a744fd4cea107bc8744cea291044ea5dbd | [
"MIT"
] | null | null | null | ---
layout: post
published: true
title: "3D Touch on iOS 9"
date: "2015-10-17 11:00"
---
### 3D Touch is amazing.
It's such a little addition but with such a big advantage for power users. It is essentially a *right click* for the iPhone.
So many apps are implementing it well. Quick shortcuts to things within the app. However, I do feel Apple missed a trick out here ...
Apps can only interact for the user when they are open. This makes sense. But with 3D Touch, it would make sense if apps could show a modal window on screen.
For example, Tweetbot. If I 3D Touch on the app I get a shortcut to post a new tweet. Pressing this will load the app then take me to the New Tweet screen.
However, surely this would be better if pressing New Tweet would just load up their own custom New Tweet modal window on the Home Screen. This way, you don't leave the place you're at and it goes away once you've sent that tweet. A great replacement for the - now missing - Post Tweet widget in the Notification Centre.
Apple, pls?
| 49.047619 | 320 | 0.751456 | eng_Latn | 0.999074 |
26b4fb1c5d170911d8129017286c00d4276770a8 | 1,414 | md | Markdown | README.md | Ryanyntc2013/influxdb1-client | 1c6febd6572fb680869eb880edde45734a1e68a8 | [
"MIT"
] | null | null | null | README.md | Ryanyntc2013/influxdb1-client | 1c6febd6572fb680869eb880edde45734a1e68a8 | [
"MIT"
] | null | null | null | README.md | Ryanyntc2013/influxdb1-client | 1c6febd6572fb680869eb880edde45734a1e68a8 | [
"MIT"
] | null | null | null | # influxdb1-clientv2
influxdb1-client is the current Go client API for InfluxDB 1.x. A Go client for the 2.0 API will be coming soon.
InfluxDB is an open-source distributed time series database, find more about [InfluxDB](https://www.influxdata.com/time-series-platform/influxdb/) at https://docs.influxdata.com/influxdb/latest
## Usage
To import into your Go project, run the following command in your terminal:
`go get github.com/Ryanyntc2013/influxdb1-client`
Then, in your import declaration section of your Go file, paste the following:
`import "github.com/Ryanyntc2013/influxdb1-client"`
If you get the error `build github.com/user/influx: cannot find module for path github.com/Ryanyntc2013/influxdb1-client` when trying to build:
change your import to:
```go
import(
client "github.com/Ryanyntc2013/influxdb1-client"
)
```
## Example
The following example creates a new client to the InfluxDB host on localhost:8086 and runs a query for the measurement `cpu_load` from the `mydb` database.
``` go
func ExampleClient_query() {
c, err := client.NewHTTPClient(client.HTTPConfig{
Addr: "http://localhost:8086",
})
if err != nil {
fmt.Println("Error creating InfluxDB Client: ", err.Error())
}
defer c.Close()
q := client.NewQuery("SELECT count(value) FROM cpu_load", "mydb", "")
if response, err := c.Query(q); err == nil && response.Error() == nil {
fmt.Println(response.Results)
}
}
```
| 37.210526 | 193 | 0.743989 | eng_Latn | 0.829657 |