hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
549463b929996d940378be7ab6bdfb6a51e78631 | 1,160 | md | Markdown | _posts/2020-11-03-2020年10月复盘.md | ketra21/ketra21.github.io | cb7792f7f5cbca912fe13f28646cab59f20b3d4a | [
"MIT"
] | null | null | null | _posts/2020-11-03-2020年10月复盘.md | ketra21/ketra21.github.io | cb7792f7f5cbca912fe13f28646cab59f20b3d4a | [
"MIT"
] | null | null | null | _posts/2020-11-03-2020年10月复盘.md | ketra21/ketra21.github.io | cb7792f7f5cbca912fe13f28646cab59f20b3d4a | [
"MIT"
] | null | null | null | ---
layout: post
title: 2020年10月复盘
subtitle:
date: 2020-11-03
author: 阳光和鱼
header-img: img/post-bg-desk.jpg
catalog: true
tags:
- 复盘
---
- # 2020年10月复盘
## 1. 回顾目标
- [x] 月输出3000字
- [x] 学习和读书日均各1 h
- [x] 运动日均15 min
## 2. 评估结果
-----
### 2.1 知识管理
**阅读**
- 乡土中国
大家小书，社会学入门必读，然而没看懂~
- 逻辑新引
采用对话的形式，利用日常生活的内容不断引出逻辑思考及其含义，作为入门的好书。
作者殷海光，是1950-1960年代台湾最有影响力的知识份子，李敖的老师，台湾白色恐怖受难者，著作颇丰。
**学习**
- 诗经11（-50%）小时;
- 史记线上读书会3.5小时(感兴趣可以加入QQ群号：641688853，目前在研读论语、传习录、史记)；
- 机器学习10.5小时;
**推荐**
> - 10月观影单：**失信的村庄**（从电影中可以看到中美关系的30年~）、麻将（杨德昌）、**龙门客栈**（胡金铨武侠电影）、女人国的污染事件（农村女人之口讲网络暴力）
### 2.2 时间管理
- 闲置时间日均一小时，娱乐时间日均50分钟(+125%);
- 读书31小时（+0%），学习42小时（-7%）；
<img src="https://i.niupic.com/images/2020/11/03/8WOH.jpg" alt="sdf" style="zoom:50%;" />
### 2.3身体管理
10月，体重由69kg减到67.5kg，体脂率由上月19.9%下降到19.6%。
9月体检时医生说要定期洗牙—>10月洗牙医生让做刮治—>最终得知自己有比较严重的牙周炎（最突破我常识的是，牙不疼不代表牙没问题），希望大家善待牙齿，才能吃嘛嘛香：
- 每年洗牙；
- 每天两次（有条件可3次）**科学地**刷牙，并经常使用牙线；
- 有牙龈出血等症状，及时就医~
## 3. 改善措施
----
- 2020年还剩两个月，得努力下，收尾了~
### 10月计划
- 月码字3000字
- 学习和读书日均合计2 h
- 运动日均20 min
| 13.488372 | 91 | 0.641379 | yue_Hant | 0.449084 |
549498b25023b3606ada4d12cd2bd3a780c20c30 | 1,304 | md | Markdown | README.md | rbaltrusch/python_interpreter | 7329c02222aeab014024c877c2e39866d5166a3e | [
"MIT"
] | 1 | 2022-02-02T05:43:55.000Z | 2022-02-02T05:43:55.000Z | README.md | rbaltrusch/python_interpreter | 7329c02222aeab014024c877c2e39866d5166a3e | [
"MIT"
] | 8 | 2021-06-19T09:08:46.000Z | 2022-01-09T21:13:38.000Z | README.md | rbaltrusch/python_interpreter | 7329c02222aeab014024c877c2e39866d5166a3e | [
"MIT"
] | 1 | 2021-06-19T15:21:23.000Z | 2021-06-19T15:21:23.000Z | # Natscript Interpreter
This is an interpreter written in Python for a custom interpreted language, Natscript, which is to be very close to natural English. It is currently still in development and supports very little functionality, but will receive more over time.
## Getting started
To get a copy of this repository, simply open up git bash in an empty folder and use the command:
$ git clone https://github.com/rbaltrusch/python_interpreter
To run the interpreter, run interpreter/main.py. At the moment, it is configured to only parse in and interpret file contents, rather than an interactive console.
## Documentation
### Available commands
A list of the currently available Natscript commands can be found in the [wiki](https://github.com/rbaltrusch/python_interpreter/wiki).
### Examples
Examples can be found [here](https://github.com/rbaltrusch/python_interpreter/tree/main/examples).
### Tutorials
Tutorials will be written once more commands are supported by Natscript.
## Python
Written in Python 3.8.3.
## License
This repository is open-source software available under the [MIT license](https://github.com/rbaltrusch/python_interpreter/blob/main/LICENSE).
## Contact
Please raise an issue for code changes. To reach out, please send an email to [email protected].
| 34.315789 | 242 | 0.785276 | eng_Latn | 0.993625 |
5495fa9aa097543b0e1905f9efb7a91ada4705b5 | 181 | md | Markdown | docs/orderBy.md | xingpengcheng/easy-es | 6a4a9213ce3fc00838e91f5595387a8ebbc0e872 | [
"Apache-2.0"
] | 216 | 2021-12-10T02:57:31.000Z | 2022-03-21T13:30:26.000Z | docs/orderBy.md | xingpengcheng/easy-es | 6a4a9213ce3fc00838e91f5595387a8ebbc0e872 | [
"Apache-2.0"
] | 4 | 2021-12-13T07:56:33.000Z | 2022-03-09T06:53:54.000Z | docs/orderBy.md | xingpengcheng/easy-es | 6a4a9213ce3fc00838e91f5595387a8ebbc0e872 | [
"Apache-2.0"
] | 65 | 2021-12-10T02:32:17.000Z | 2022-03-20T13:08:45.000Z | ```java
orderBy(boolean condition, boolean isAsc, R... columns)
```
- 排序：ORDER BY 字段, ...
- 例: orderBy(true, true, Document::getId,Document::getTitle)--->order by id ASC,title ASC
| 25.857143 | 89 | 0.679558 | yue_Hant | 0.317259 |
5496014bc50e02adf36f383a5c7919428bd727f7 | 100 | md | Markdown | README.md | seabourne/nxus-contact-form | cde19f875d046b33ed9af89f8356b1aba41851f9 | [
"MIT"
] | null | null | null | README.md | seabourne/nxus-contact-form | cde19f875d046b33ed9af89f8356b1aba41851f9 | [
"MIT"
] | null | null | null | README.md | seabourne/nxus-contact-form | cde19f875d046b33ed9af89f8356b1aba41851f9 | [
"MIT"
] | null | null | null | # nxus-contact-form
##
## Installation
npm install nxus-contact-form --save
## API
* * *
| 8.333333 | 41 | 0.59 | ast_Latn | 0.299846 |
54960b91d1daa85e2d3527a113ef3b446dc97962 | 2,910 | md | Markdown | src/blog/2016/03/09-migrating-to-chruby.md | chrissearle/www_cso | 35f143cfd123ab791d7345dbe88bbea73f4943d9 | [
"MIT"
] | null | null | null | src/blog/2016/03/09-migrating-to-chruby.md | chrissearle/www_cso | 35f143cfd123ab791d7345dbe88bbea73f4943d9 | [
"MIT"
] | 44 | 2018-11-09T07:15:13.000Z | 2022-02-19T10:40:26.000Z | src/blog/2016/03/09-migrating-to-chruby.md | chrissearle/www_cso | 35f143cfd123ab791d7345dbe88bbea73f4943d9 | [
"MIT"
] | null | null | null | ---
title: Migrating to chruby
date: 2016-03-09 08:54 +0100
tags: ruby, rvm, rbenv, chruby, ruby-build, ruby-install, bundler
---
### Migration
Up until recently I have been using [rbenv](https://github.com/rbenv/rbenv) as my ruby install manager (along with [ruby-build](https://github.com/rbenv/ruby-build)).
I switched to this a long time back from [rvm](https://rvm.io/) - with rvm I was having a number of issues with library versions of iconv, xml etc that rbenv didn't seem to have.
Yesterday I heard about [chruby](https://github.com/postmodern/chruby) - which does not rely on shimmed binaries - it simply changes the environment (PATH etc) to point to the ruby you want. This seems a lot simpler/cleaner conceptually.
Since ruby-build is written alongside rbenv and the chruby dev writes [ruby-install](https://github.com/postmodern/ruby-install) alongside chruby we might as well change to that too.
So I decided to try it out.
This is on OSX using homebrew (my normal development setup).
Let's get rid of the rbenv bits
brew uninstall rbenv ruby-build
Now install chruby and ruby-install
brew install chruby ruby-install
Now - you then can add the following to your bashrc/zshrc:
source /usr/local/share/chruby/chruby.sh
But - for zsh I'm using [zprezto](https://github.com/sorin-ionescu/prezto) with ruby module loaded and this has support for rvm, rbenv and chruby built in - so I didn't need that.
In any case - start a new instance of the shell and then install the latest ruby - I wanted both 2.3.0 and 2.2.4
ruby-install ruby 2.3.0
chruby ruby-2.3.0
gem install bundler
ruby-install ruby 2.2.4
chruby ruby-2.2.4
gem install bundler
Since all my projects use bundler/Gemfile - I do need bundler installed for each ruby
Now - all I wanted to add was default to 2.3.0 - so at the end of my zsh initialization I just added
chruby ruby-2.3.0
And finally - I want it to pay attention to .ruby_version files - which you can do by adding the following to bashrc/zshrc
source /usr/local/share/chruby/auto.sh
In zprezto's ruby module - instead all you need to do is to add the following to .zpreztorc
zstyle ':prezto:module:ruby:chruby' auto-switch 'yes'
You can configure chruby to see the rbenv/rvm installed rubies - but I chose to reinstall and to remove the older ruby installations - seems cleaner.
### Bundler
Slightly related - I use the following in my ~/.bundle/config file
---
BUNDLE_PATH: vendor/bundle
This means that when I run bundle in the root of a project - all gems are installed to vendor/bundle in that project directory.
And then in my ~/.gitignore I add
vendor/bundle
This gives me a completely separate bundle for each project - but makes sure that the git repository doesn't get the files. The only thing it then requires is that you run things with bundle exec - which has become a habit.
| 39.324324 | 237 | 0.746392 | eng_Latn | 0.99778 |
54961f1bd4e884abf0e90cea450e9ed6d5fd1d5a | 2,029 | md | Markdown | README.md | guidoMueller/cf-banking-fints-example | 08a2b97f4e87e3de08becfbed296ec24c46ec4c7 | [
"MIT"
] | null | null | null | README.md | guidoMueller/cf-banking-fints-example | 08a2b97f4e87e3de08becfbed296ec24c46ec4c7 | [
"MIT"
] | 3 | 2021-03-09T12:11:56.000Z | 2022-02-12T17:07:56.000Z | README.md | guidoMueller/cf-banking-fints-example | 08a2b97f4e87e3de08becfbed296ec24c46ec4c7 | [
"MIT"
] | null | null | null | # Example FinTs Client Application for Sap Cloud Foundry NodeJs with ES6 and SAPUI5 with ES6
[App Example](https://cf-banking-fints-example.cfapps.eu10.hana.ondemand.com)
## FinTs Application Features
- List bank accounts
- view all transactions from your bank accounts with date range
- show in chart all transactions from your bank accounts with date range
- show a list from all available banks from the service
## FinTs Application Middleware Features
- Authentication with your bank account data
- GET a JSON List from all available banks from the service
- GET/POST all bank accounts, Post is with Auth. data
- GET all transactions from your bank accounts with date range
- GET all transactions and Accounts withe demo data (HEADER Parameter 'demo-mode'='true')
## Getting Started with Cloud Foundry on SAP Cloud Platform
In this Example, you will view more about Cloud Foundry. In particular, you will get familiar with:
- the official CF CLI (cf-*.sh files)
- Login on Sap Cloud Foundry (cf-login.sh)
- Push App to Sap Cloud Foundry (cf-push.sh)
- create a ui5 app with es6
- create your own online banking (finTs Api) app with Sapui5 and nodeJs
## Installation
```sh
$ yarn install
```
## Build with Gulp (Recommended)
```sh
yarn build:app
yarn build:server
```
`gulp clean` and `gulp build` are supported, and module-based building command `gulp build:example` is also supported
## Run
```sh
yarn start:server
```
Open [http://localhost:4000/](http://localhost:4000/) in your browser.
## Debug / Develop
```sh
yarn watch:app
yarn watch:app:Login
yarn watch:server
yarn start:server
```
### Step 1 For Push Sap Cloud Foundry
setup [Config File](/cf.conf) for Sap Cloud Foundry Deployment
* USER = SAP User
* PASS = SAp USer Password
* ORG = Sap cloud Foundry Subaccount Organization
* API = Sap cloud Foundry Subaccount API Endpoint
* SPACE = Sap cloud Foundry Subaccount selected Space
### Step 2 For Push Sap Cloud Foundry
Deploy Application to Sap Cloud Foundry
```bash
bash cf-push.sh
``` | 27.053333 | 117 | 0.74963 | eng_Latn | 0.941217 |
549658f5d0f5f6d6e0a80df38c5840a64b0ea5ce | 142 | md | Markdown | _posts/2019-05-13-python-badges.md | gabrielehackl/gabrielehackl.github.io | aee2a99810eef30b03b54ec787a06ca1db815298 | [
"MIT"
] | null | null | null | _posts/2019-05-13-python-badges.md | gabrielehackl/gabrielehackl.github.io | aee2a99810eef30b03b54ec787a06ca1db815298 | [
"MIT"
] | null | null | null | _posts/2019-05-13-python-badges.md | gabrielehackl/gabrielehackl.github.io | aee2a99810eef30b03b54ec787a06ca1db815298 | [
"MIT"
] | null | null | null | ---
layout: post
title: Python becoming a challenge
---
Codacademy Units 7-8 on Python
| 7.473684 | 42 | 0.669014 | eng_Latn | 0.865866 |
549672fc56f76492f48ef45eb89220b811ef880f | 14,240 | md | Markdown | 2021-01/2021-01-08_short.md | admariner/trending_archive | ffca6522c4fdaa5203c3f18d9a5a7d7da098169c | [
"MIT"
] | 80 | 2015-02-13T16:52:22.000Z | 2022-03-10T20:13:08.000Z | 2021-01/2021-01-08_short.md | admariner/trending_archive | ffca6522c4fdaa5203c3f18d9a5a7d7da098169c | [
"MIT"
] | 65 | 2021-10-02T05:54:01.000Z | 2021-12-28T22:50:23.000Z | 2021-01/2021-01-08_short.md | admariner/trending_archive | ffca6522c4fdaa5203c3f18d9a5a7d7da098169c | [
"MIT"
] | 16 | 2015-10-08T11:06:28.000Z | 2021-06-30T07:26:49.000Z | ### 2021-01-08
diff between today and yesterday
#### python
* [lucidrains/DALLE-pytorch](https://github.com/lucidrains/DALLE-pytorch): Implementation / replication of DALL-E, OpenAI's Text to Image Transformer, in Pytorch
* [who0sy/jd_kill](https://github.com/who0sy/jd_kill): mainolddocker
* [ElvinC/gyroflow](https://github.com/ElvinC/gyroflow): WIP Video stabilization using gyro data from GoPro or external log
* [volotat/DiffMorph](https://github.com/volotat/DiffMorph): Image morphing without reference points by applying warp maps and optimizing over them.
* [FengQuanLi/ResnetGPT](https://github.com/FengQuanLi/ResnetGPT): Resnet101+GPTAI
* [persepolisdm/persepolis](https://github.com/persepolisdm/persepolis): Persepolis Download Manager is a GUI for aria2.
* [microsoft/DeBERTa](https://github.com/microsoft/DeBERTa): The implementation of DeBERTa
* [lvgithub/jd_seckill_new](https://github.com/lvgithub/jd_seckill_new):
* [ASAS1314/jd_subscribe_seckill](https://github.com/ASAS1314/jd_subscribe_seckill): js_seckill
* [RasaHQ/rasa](https://github.com/RasaHQ/rasa): Open source machine learning framework to automate text- and voice-based conversations: NLU, dialogue management, connect to Slack, Facebook, and more - Create chatbots and voice assistants
* [The-Art-of-Hacking/h4cker](https://github.com/The-Art-of-Hacking/h4cker): This repository is primarily maintained by Omar Santos and includes thousands of resources related to ethical hacking / penetration testing, digital forensics and incident response (DFIR), vulnerability research, exploit development, reverse engineering, and more.
* [Tianxiaomo/pytorch-YOLOv4](https://github.com/Tianxiaomo/pytorch-YOLOv4): PyTorch ,ONNX and TensorRT implementation of YOLOv4
* [sqlalchemy/sqlalchemy](https://github.com/sqlalchemy/sqlalchemy): The Database Toolkit for Python
* [ArchiveBox/ArchiveBox](https://github.com/ArchiveBox/ArchiveBox): The open source self-hosted web archive. Takes browser history/bookmarks/Pocket/Pinboard/etc., saves HTML, JS, PDFs, media, and more...
* [vishnubob/wait-for-it](https://github.com/vishnubob/wait-for-it): Pure bash script to test and wait on the availability of a TCP host and port
#### go
* [aws/aws-sdk-go](https://github.com/aws/aws-sdk-go): AWS SDK for the Go programming language.
* [argoproj/argo-cd](https://github.com/argoproj/argo-cd): Declarative continuous deployment for Kubernetes.
* [matrix-org/dendrite](https://github.com/matrix-org/dendrite): Dendrite is a second-generation Matrix homeserver written in Go!
* [quay/clair](https://github.com/quay/clair): Vulnerability Static Analysis for Containers
* [weaveworks/eksctl](https://github.com/weaveworks/eksctl): The official CLI for Amazon EKS
* [cortexproject/cortex](https://github.com/cortexproject/cortex): A horizontally scalable, highly available, multi-tenant, long term Prometheus.
* [databus23/helm-diff](https://github.com/databus23/helm-diff): A helm plugin that shows a diff explaining what a helm upgrade would change
* [GoogleContainerTools/kaniko](https://github.com/GoogleContainerTools/kaniko): Build Container Images In Kubernetes
* [panjf2000/ants](https://github.com/panjf2000/ants): ants is a high-performance and low-cost goroutine pool in Go, inspired by fasthttp./ ants goroutine
* [derailed/k9s](https://github.com/derailed/k9s): Kubernetes CLI To Manage Your Clusters In Style!
* [evanw/esbuild](https://github.com/evanw/esbuild): An extremely fast JavaScript bundler and minifier
* [DataDog/datadog-agent](https://github.com/DataDog/datadog-agent): Datadog Agent
* [kubernetes/kube-state-metrics](https://github.com/kubernetes/kube-state-metrics): Add-on agent to generate and expose cluster-level metrics.
* [gravitational/teleport](https://github.com/gravitational/teleport): Secure Access for Developers that doesn't get in the way.
* [awslabs/amazon-ecr-credential-helper](https://github.com/awslabs/amazon-ecr-credential-helper): Automatically gets credentials for Amazon ECR on docker push/docker pull
* [roboll/helmfile](https://github.com/roboll/helmfile): Deploy Kubernetes Helm Charts
* [golang/go](https://github.com/golang/go): The Go programming language
* [helm/helm](https://github.com/helm/helm): The Kubernetes Package Manager
* [google/pprof](https://github.com/google/pprof): pprof is a tool for visualization and analysis of profiling data
#### rust
* [blockstack/stacks-blockchain](https://github.com/blockstack/stacks-blockchain): The Stacks 2.0 blockchain implementation
* [LemmyNet/lemmy](https://github.com/LemmyNet/lemmy): Building a federated alternative to reddit in rust
* [dabreegster/abstreet](https://github.com/dabreegster/abstreet): A traffic simulation game exploring how small changes to roads affect cyclists, transit users, pedestrians, and drivers.
* [alacritty/alacritty](https://github.com/alacritty/alacritty): A cross-platform, OpenGL terminal emulator.
* [hyperium/tonic](https://github.com/hyperium/tonic): A native gRPC client & server implementation with async/await support.
* [snapview/tungstenite-rs](https://github.com/snapview/tungstenite-rs): Lightweight stream-based WebSocket implementation for Rust.
* [wasmerio/wasmer-python](https://github.com/wasmerio/wasmer-python): WebAssembly runtime for Python
* [paritytech/polkadot](https://github.com/paritytech/polkadot): Polkadot Node Implementation
* [rust-lang/libc](https://github.com/rust-lang/libc): Raw bindings to platform APIs for Rust
* [tauri-apps/tauri](https://github.com/tauri-apps/tauri): Build smaller, faster, and more secure desktop applications with a web frontend.
* [rust-lang/rustlings](https://github.com/rust-lang/rustlings): Small exercises to get you used to reading and writing Rust code!
* [vi/websocat](https://github.com/vi/websocat): Command-line client for WebSockets, like netcat (or curl) for ws:// with advanced socat-like functions
* [timberio/vector](https://github.com/timberio/vector): A high-performance observability data pipeline.
* [datenlord/datenlord](https://github.com/datenlord/datenlord): DatenLord, Computing Defined Storage, an application-orientated, cloud-native distributed storage system
* [tower-rs/tower](https://github.com/tower-rs/tower): async fn(Request) -> Result<Response, Error>
* [tokio-rs/io-uring](https://github.com/tokio-rs/io-uring): The `io_uring` library for Rust
* [rust-lang/book](https://github.com/rust-lang/book): The Rust Programming Language
#### cpp
* [Tencent/rapidjson](https://github.com/Tencent/rapidjson): A fast JSON parser/generator for C++ with both SAX/DOM style API
* [google/googletest](https://github.com/google/googletest): Googletest - Google Testing and Mocking Framework
* [grpc/grpc](https://github.com/grpc/grpc): The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
* [ceph/ceph](https://github.com/ceph/ceph): Ceph is a distributed object, block, and file storage platform
* [android/ndk-samples](https://github.com/android/ndk-samples): Android NDK samples with Android Studio
* [OSGeo/gdal](https://github.com/OSGeo/gdal): GDAL is an open source X/MIT licensed translator library for raster and vector geospatial data formats.
* [electron/electron](https://github.com/electron/electron): Build cross-platform desktop apps with JavaScript, HTML, and CSS
* [weidai11/cryptopp](https://github.com/weidai11/cryptopp): free C++ class library of cryptographic schemes
* [catchorg/Catch2](https://github.com/catchorg/Catch2): A modern, C++-native, header-only, test framework for unit-tests, TDD and BDD - using C++11, C++14, C++17 and later (or C++03 on the Catch1.x branch)
* [apple/swift](https://github.com/apple/swift): The Swift Programming Language
* [nanocurrency/nano-node](https://github.com/nanocurrency/nano-node): Nano is a cryptocurrency
* [TheCherno/Hazel](https://github.com/TheCherno/Hazel): Hazel Engine
* [apache/arrow](https://github.com/apache/arrow): Apache Arrow is a cross-language development platform for in-memory data. It specifies a standardized language-independent columnar memory format for flat and hierarchical data, organized for efficient analytic operations on modern hardware. It also provides computational libraries and zero-copy streaming messaging and interprocess communication
* [grpc/grpc-web](https://github.com/grpc/grpc-web): gRPC for Web Clients
* [project-chip/connectedhomeip](https://github.com/project-chip/connectedhomeip): Project Connected Home over IP is a new Working Group within the Zigbee Alliance. This Working Group plans to develop and promote the adoption of a new connectivity standard to increase compatibility among smart home products, with security as a fundamental design tenet.
* [SFML/SFML](https://github.com/SFML/SFML): Simple and Fast Multimedia Library
* [ApolloAuto/apollo](https://github.com/ApolloAuto/apollo): An open autonomous driving platform
* [DrKLO/Telegram](https://github.com/DrKLO/Telegram): Telegram for Android source
#### javascript
* [Asabeneh/30-Days-Of-JavaScript](https://github.com/Asabeneh/30-Days-Of-JavaScript): 30 days of JavaScript programming challenge is a step by step guide to learn JavaScript programming language in 30 days
* [LasCC/Hack-Tools](https://github.com/LasCC/Hack-Tools): The all-in-one Red Team extension for Web Pentester
* [lowlighter/metrics](https://github.com/lowlighter/metrics): An image generator with 20+ metrics about your GitHub account such as activity, community, repositories, coding habits, website performances, music played, starred topics, etc. that you can put on your profile or elsewhere !
* [jamstack-cms/jamstack-ecommerce](https://github.com/jamstack-cms/jamstack-ecommerce): A starter project for building performant ECommerce applications with Next.js and React
* [adam-p/markdown-here](https://github.com/adam-p/markdown-here): Google Chrome, Firefox, and Thunderbird extension that lets you write email in Markdown and render it before sending.
* [Rob--W/cors-anywhere](https://github.com/Rob--W/cors-anywhere): CORS Anywhere is a NodeJS reverse proxy which adds CORS headers to the proxied request.
* [xuedingmiaojun/wxappUnpacker](https://github.com/xuedingmiaojun/wxappUnpacker): ()
* [facebook/create-react-app](https://github.com/facebook/create-react-app): Set up a modern web app by running one command.
* [signalapp/Signal-Desktop](https://github.com/signalapp/Signal-Desktop): Signal Private Messenger for Windows, Mac, and Linux
* [inertiajs/inertia](https://github.com/inertiajs/inertia): Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
* [portainer/portainer](https://github.com/portainer/portainer): Making Docker and Kubernetes management easy.
* [external-secrets/kubernetes-external-secrets](https://github.com/external-secrets/kubernetes-external-secrets): Integrate external secret management systems with Kubernetes
* [semantic-release/semantic-release](https://github.com/semantic-release/semantic-release): Fully automated version management and package publishing
* [unbug/codelf](https://github.com/unbug/codelf): A search tool helps dev to solve the naming things problem.
* [WordPress/gutenberg](https://github.com/WordPress/gutenberg): The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
* [reduxjs/react-redux](https://github.com/reduxjs/react-redux): Official React bindings for Redux
* [d3/d3](https://github.com/d3/d3): Bring data to life with SVG, Canvas and HTML.
* [nodejs/node](https://github.com/nodejs/node): Node.js JavaScript runtime
* [reactchartjs/react-chartjs-2](https://github.com/reactchartjs/react-chartjs-2): React wrapper for Chart.js
#### typescript
* [lensapp/lens](https://github.com/lensapp/lens): Lens - The Kubernetes IDE
* [Chocobozzz/PeerTube](https://github.com/Chocobozzz/PeerTube): ActivityPub-federated video streaming platform using P2P directly in your web browser
* [aws/aws-cdk](https://github.com/aws/aws-cdk): The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
* [firebase/firebase-tools](https://github.com/firebase/firebase-tools): The Firebase Command Line Tools
* [microsoft/fluentui](https://github.com/microsoft/fluentui): Fluent UI web represents a collection of utilities, React components, and web components for building web applications.
* [palantir/blueprint](https://github.com/palantir/blueprint): A React-based UI toolkit for the web
* [ianstormtaylor/slate](https://github.com/ianstormtaylor/slate): A completely customizable framework for building rich text editors. (Currently in beta.)
* [grafana/grafana](https://github.com/grafana/grafana): The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
* [hotwired/stimulus](https://github.com/hotwired/stimulus): A modest JavaScript framework for the HTML you already have
* [typeorm/typeorm](https://github.com/typeorm/typeorm): ORM for TypeScript and JavaScript (ES7, ES6, ES5). Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
* [microsoft/TypeScript](https://github.com/microsoft/TypeScript): TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
* [microsoft/playwright](https://github.com/microsoft/playwright): Node.js library to automate Chromium, Firefox and WebKit with a single API
* [google/model-viewer](https://github.com/google/model-viewer): Easily display interactive 3D models on the web and in AR!
* [elastic/kibana](https://github.com/elastic/kibana): Your window into the Elastic Stack
* [reduxjs/redux](https://github.com/reduxjs/redux): Predictable state container for JavaScript apps
* [Azure/azure-rest-api-specs](https://github.com/Azure/azure-rest-api-specs): The source for REST API specifications for Microsoft Azure.
* [umijs/qiankun](https://github.com/umijs/qiankun): Blazing fast, simple and completed solution for micro frontends.
* [antvis/X6](https://github.com/antvis/X6): JavaScript diagramming library that uses SVG and HTML for rendering.
| 117.68595 | 398 | 0.783006 | eng_Latn | 0.47919 |
54975912dae3994a2508e9c3c86d932551254200 | 951 | md | Markdown | docs/src/teardown/about.md | hgeorgako/Rocket.jl | 9661dad340e9a079ebd6ed57dcf9e5db31af637f | [
"MIT"
] | null | null | null | docs/src/teardown/about.md | hgeorgako/Rocket.jl | 9661dad340e9a079ebd6ed57dcf9e5db31af637f | [
"MIT"
] | null | null | null | docs/src/teardown/about.md | hgeorgako/Rocket.jl | 9661dad340e9a079ebd6ed57dcf9e5db31af637f | [
"MIT"
] | null | null | null | # [Subscription](@id section_subscription)
A __Subscription__ represents a disposable resource, usually the execution of an Observable. A Subscription has one important method: `unsubscribe!(teardown)`, which takes some teardown logic object as one argument and disposes the resource held by the subscription.
```julia
using Rocket
source = Subject(Int)
next!(source, 0) # Logs nothing as there is no subscribers
subscription = subscribe!(source, logger())
next!(source, 1) # Logs [LogActor] Data: 1 into standard output
unsubscribe!(subscription)
next!(source, 2) # Logs nothing as a single one actor has unsubscribed
```
!!! note
A Subscription essentially just has its own specific method for `unsubscribe!()` function which releases resources or cancel Observable executions. Any Observable has to return a valid `Teardown` object.
For more information about subscription and teardown logic see the [API Section](@ref teardown_api)
| 36.576923 | 266 | 0.778128 | eng_Latn | 0.991135 |
549776c7bb2e5ddf4c1dbee1809f3861a9e9855b | 626 | md | Markdown | docs/vim/macro.md | liuz2/hello | d93659bacdc2f2cf02e818396ec0a8c8b189e0e9 | [
"MIT"
] | null | null | null | docs/vim/macro.md | liuz2/hello | d93659bacdc2f2cf02e818396ec0a8c8b189e0e9 | [
"MIT"
] | null | null | null | docs/vim/macro.md | liuz2/hello | d93659bacdc2f2cf02e818396ec0a8c8b189e0e9 | [
"MIT"
] | null | null | null | # Macro
Macro is record and play feature.
## Start recording
To start recording press <kbd>q</kbd> followed by any lower case letter as a macro name.
## Perform Vim actions
In this step you can perform any Vim actions. You can see these actions by executing following command:
```sh
:registers
```
## Stop recording
Once you are done with actions, press <kbd>q</kbd> again to stop recording.
## Play recording
To play execute below command:
```sh
@{macro-name}
```
For example to execute macro "a", execute below command:
```sh
@a
```
## REF
1. [Vim - Macros](https://www.tutorialspoint.com/vim/vim_macros.htm)
| 16.473684 | 103 | 0.71246 | eng_Latn | 0.996438 |
5498f29a16e465b4ea93d808124b4572c24153af | 13,509 | md | Markdown | README.md | live-asif/uppy | 184570d26611030dd5f487925ef68eeb332c4737 | [
"MIT"
] | null | null | null | README.md | live-asif/uppy | 184570d26611030dd5f487925ef68eeb332c4737 | [
"MIT"
] | null | null | null | README.md | live-asif/uppy | 184570d26611030dd5f487925ef68eeb332c4737 | [
"MIT"
] | null | null | null | # [Uppy](https://uppy.io)
<img src="https://uppy.io/images/logos/uppy-dog-head-arrow.svg" width="120" alt="Uppy logo: a superman puppy in a pink suit" align="right">
<a href="https://www.npmjs.com/package/uppy"><img src="https://img.shields.io/npm/v/uppy.svg?style=flat-square"></a>
<a href="https://travis-ci.org/transloadit/uppy"><img src="https://img.shields.io/travis/transloadit/uppy/master.svg?style=flat-square" alt="Build Status"></a>
Uppy is a sleek, modular JavaScript file uploader that integrates seamlessly with any application. It’s fast, easy to use and lets you worry about more important problems than building a file uploader.
- **Fetch** files from local disk, remote urls, Google Drive, Dropbox, Instagram, or snap and record selfies with a camera;
- **Preview** and edit metadata with a nice interface;
- **Upload** to the final destination, optionally process/encode
<img src="https://github.com/transloadit/uppy/raw/master/assets/uppy-demo-oct-2018.gif">
**[Read the docs](https://uppy.io/docs)** | **[Try Uppy](https://uppy.io/examples/dashboard/)**
<a href="https://transloadit.com" target="_blank"><img width="185" src="https://github.com/transloadit/uppy/raw/master/assets/developed-by-transloadit.png"></a>
Uppy is being developed by the folks at [Transloadit](https://transloadit.com), a versatile file encoding service.
## Example
Code used in the above example:
```js
const Uppy = require('@uppy/core')
const Dashboard = require('@uppy/dashboard')
const GoogleDrive = require('@uppy/google-drive')
const Instagram = require('@uppy/instagram')
const Webcam = require('@uppy/webcam')
const Tus = require('@uppy/tus')
const uppy = Uppy({ autoProceed: false })
.use(Dashboard, { trigger: '#select-files' })
.use(GoogleDrive, { target: Dashboard, companionUrl: 'https://companion.uppy.io' })
.use(Instagram, { target: Dashboard, companionUrl: 'https://companion.uppy.io' })
.use(Webcam, { target: Dashboard })
.use(Tus, { endpoint: 'https://master.tus.io/files/' })
.on('complete', (result) => {
console.log('Upload result:', result)
})
```
**[Try it online](https://uppy.io/examples/dashboard/)** or **[read the docs](https://uppy.io/docs)** for more details on how to use Uppy and its plugins.
## Features
- Lightweight, modular plugin-based architecture, easy on dependencies :zap:
- Resumable file uploads via the open [tus](https://tus.io/) standard, so large uploads survive network hiccups
- Supports picking files from: Webcam, Dropbox, Google Drive, Instagram, bypassing the user’s device where possible, syncing between servers directly via [@uppy/companion](https://uppy.io/docs/companion)
- Works great with file encoding and processing backends, such as [Transloadit](https://transloadit.com), works great without (just roll your own Apache/Nginx/Node/FFmpeg/etc backend)
- Sleek user interface :sparkles:
- Optional file recovery (after a browser crash) with [Golden Retriever](https://uppy.io/docs/golden-retriever/)
- Speaks multiple languages (i18n) :earth_africa:
- Built with accessibility in mind
- Free for the world, forever (as in beer 🍺, pizza 🍕, and liberty 🗽)
- Cute as a puppy, also accepts cat pictures :dog:
## Installation
``` bash
$ npm install @uppy/core @uppy/dashboard @uppy/tus
```
We recommend installing from npm and then using a module bundler such as [Webpack](https://webpack.js.org/), [Browserify](http://browserify.org/) or [Rollup.js](http://rollupjs.org/).
Add CSS [uppy.min.css](https://transloadit.edgly.net/releases/uppy/v1.0.0/uppy.min.css), either to `<head>` of your HTML page or include in JS, if your bundler of choice supports it — transforms and plugins are available for Browserify and Webpack.
Alternatively, you can also use a pre-built bundle from Transloadit's CDN: Edgly. In that case `Uppy` will attach itself to the global `window.Uppy` object.
> ⚠️ The bundle currently consists of most Uppy plugins, so this method is not recommended for production, as your users will have to download all plugins when you are likely using just a few.
```html
<!-- 1. Add CSS to `<head>` -->
<link href="https://transloadit.edgly.net/releases/uppy/v1.0.0/uppy.min.css" rel="stylesheet">
<!-- 2. Add JS before the closing `</body>` -->
<script src="https://transloadit.edgly.net/releases/uppy/v1.0.0/uppy.min.js"></script>
<!-- 3. Initialize -->
<div class="UppyDragDrop"></div>
<script>
var uppy = Uppy.Core()
uppy.use(Uppy.DragDrop, { target: '.UppyDragDrop' })
uppy.use(Uppy.Tus, { endpoint: '//master.tus.io/files/' })
</script>
```
## Documentation
- [Uppy](https://uppy.io/docs/uppy/) — full list of options, methods, and events.
- [Plugins](https://uppy.io/docs/plugins/) — list of Uppy plugins and their options.
- [Companion](https://uppy.io/docs/companion/) — setting up and running an Companion instance, which adds support for Instagram, Dropbox, Google Drive and remote urls.
- [React](https://uppy.io/docs/react/) — components to integrate Uppy UI plugins with React apps.
- [Architecture & Writing a Plugin](https://uppy.io/docs/writing-plugins/) — how to write a plugin for Uppy.
## Plugins
[List of plugins and their common options](https://uppy.io/docs/plugins/).
### Local Sources
- [`Dashboard`](https://uppy.io/docs/dashboard/) — universal UI with previews, progress bars, metadata editor and all the cool stuff
- [`Drag & Drop`](https://uppy.io/docs/drag-drop/) — plain and simple drag and drop area
- [`File Input`](https://uppy.io/docs/file-input/) — even plainer “select files” button
- [`Webcam`](https://uppy.io/docs/webcam/) — snap and record those selfies 📷
### Remote Providers
- [`Google Drive`](https://uppy.io/docs/google-drive/), [`Dropbox`](https://uppy.io/docs/dropbox/), [`Instagram`](https://uppy.io/docs/instagram/), [`Import From URL`](https://uppy.io/docs/url/) — support picking files from remote providers or direct URLs from anywhere on the web. Note that [`@uppy/companion`](https://uppy.io/docs/companion) is needed for these.
### Uploaders
- [`Tus`](https://uppy.io/docs/tus/) — resumable uploads via the open [tus](http://tus.io) standard
- [`XHR Upload`](https://uppy.io/docs/xhr-upload/) — regular uploads for any backend out there (like Apache, Nginx)
- [`AWS S3`](https://uppy.io/docs/aws-s3/) and [`AWS S3 Multipart`](https://uppy.io/docs/aws-s3-multipart/) — upload to AWS S3.
### UI Elements
- [`Progress Bar`](https://uppy.io/docs/progress-bar/) — minimal progress bar that fills itself when upload progresses
- [`Status Bar`](https://uppy.io/docs/status-bar/) — more detailed progress, pause/resume/cancel buttons, percentage, speed, uploaded/total sizes (included by default with `Dashboard`)
- [`Informer`](https://uppy.io/docs/informer/) — send notifications like “smile” before taking a selfie or “upload failed” when all is lost (also included by default with `Dashboard`)
### File Processing
- [`Transloadit`](https://uppy.io/docs/transloadit/) — support for [Transloadit](http://transloadit.com)’s robust file uploading and encoding backend
### Miscellaneous
- [`Golden Retriever`](https://uppy.io/docs/golden-retriever/) — restores files after a browser crash, like it’s nothing
- `Thumbnail Generator` — generates image previews (included by default with `Dashboard`)
- [`Form`](https://uppy.io/docs/form/) — collects metadata from `<form>` right before an Uppy upload, then optionally appends results back to the form
- [`Redux`](https://uppy.io/docs/redux/) — for your emerging [time traveling](https://github.com/gaearon/redux-devtools) needs
## Browser Support
<a href="https://saucelabs.com/u/transloadit-uppy">
<img src="https://saucelabs.com/browser-matrix/transloadit-uppy.svg" alt="Sauce Test Status"/>
</a>
We aim to support IE10+ and recent versions of Safari, Edge, Chrome, Firefox, and Opera.
### Polyfills
Uppy heavily uses Promises. If your target environment [does not support Promises](https://caniuse.com/#feat=promises), use a polyfill like `es6-promise` before initialising Uppy.
When using remote providers like Google Drive or Dropbox, the Fetch API is used. If your target environment does not support the [Fetch API](https://caniuse.com/#feat=fetch), use a polyfill like `whatwg-fetch` before initialising Uppy. The Fetch API polyfill must be loaded _after_ the Promises polyfill, because Fetch uses Promises.
With a module bundler, you can use the required polyfills like so:
```shell
npm install es6-promise whatwg-fetch
```
```js
require('es6-promise/auto')
require('whatwg-fetch')
const Uppy = require('@uppy/core')
```
If you're using Uppy via a script tag, you can load the polyfills from [JSDelivr](https://www.jsdelivr.com/) like so:
```html
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/es6-promise.auto.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/fetch.umd.min.js"></script>
<script src="https://transloadit.edgly.net/releases/uppy/v1.0.0/uppy.min.js"></script>
```
## FAQ
### Why not just use `<input type="file">`?
Having no JavaScript beats having a lot of it, so that’s a fair question! Running an uploading & encoding business for ten years though we found that in cases, the file input leaves some to be desired:
- We received complaints about broken uploads and found that resumable uploads are important, especially for big files and to be inclusive towards people on poorer connections (we also launched [tus.io](https://tus.io) to attack that problem). Uppy uploads can survive network outages and browser crashes or accidental navigate-aways.
- Uppy supports editing meta information before uploading (and e.g. cropping is planned).
- There’s the situation where people are using their mobile devices and want to upload on the go, but they have their picture on Instagram, files in Dropbox, or just a plain file url from anywhere on the open web. Uppy allows to pick files from those and push it to the destination without downloading it to your mobile device first.
- Accurate upload progress reporting is an issue on many platforms.
- Some file validation — size, type, number of files — can be done on the client with Uppy.
- Uppy integrates webcam support, in case your users want to upload a picture/video/audio that does not exist yet :)
- A larger drag & drop surface can be pleasant to work with. Some people also like that you can control the styling, language, etc.
- Uppy is aware of encoding backends. Often after an upload, the server needs to rotate, detect faces, optimize for iPad, or what have you. Uppy can track progress of this and report back to the user in different ways.
- Sometimes you might want your uploads to happen while you continue to interact on the same single page.
Not all apps need all of these features. A `<input type="file">` is fine in many situations. But these were a few things that our customers hit / asked about enough to spark us to develop Uppy.
### Why is all this goodness free?
Transloadit’s team is small and we have a shared ambition to make a living from open source. By giving away projects like [tus.io](https://tus.io) and [Uppy](https://uppy.io), we’re hoping to advance the state of the art, make life a tiny little bit better for everyone, and in doing so have rewarding jobs and get some eyes on our commercial service: [a content ingestion & processing platform](https://transloadit.com).
Our thinking is that if just a fraction of our open source userbase can see the appeal of hosted versions straight from the source, that could already be enough to sustain our work. So far this is working out! We’re able to dedicate 80% of our time to open source and haven’t gone bankrupt just yet :D
### Does Uppy support React?
Yep, we have Uppy React components, please see [Uppy React docs](https://uppy.io/docs/react/).
### Does Uppy support S3 uploads?
Yes, there is an S3 plugin, please check out the [docs](https://uppy.io/docs/aws-s3/) for more.
### Do I need to install special service/server for Uppy? Can I use it with Rails/Node/Go/PHP?
Yes, whatever you want on the backend will work with `@uppy/xhr-upload` plugin, since it just does a `POST` or `PUT` request. Here’s a [PHP backend example](https://uppy.io/docs/xhr-upload/#Uploading-to-a-PHP-Server).
If you want resumability with the Tus plugin, use [one of the tus server implementations](https://tus.io/implementations.html) 👌🏼
And you’ll need [`@uppy/companion`](https://uppy.io/docs/companion) if you’d like your users to be able to pick files from Instagram, Google Drive, Dropbox or via direct urls (with more services coming).
## Contributions are welcome
- Contributor’s guide in [`.github/CONTRIBUTING.md`](.github/CONTRIBUTING.md)
- Changelog to track our release progress (we aim to roll out a release every month): [`CHANGELOG.md`](CHANGELOG.md)
## Used by
Uppy is used by: [Photobox](http://photobox.com), [Issuu](https://issuu.com/), [Law Insider](https://lawinsider.com), [Cool Tabs](https://cool-tabs.com), [Soundoff](https://soundoff.io), [Scrumi](https://www.scrumi.io/), [Crive](https://crive.co/) and others.
Use Uppy in your project? [Let us know](https://github.com/transloadit/uppy/issues/769)!
<!--contributors-->
## Contributors
<!--/contributors-->
## Software
We use Browserstack for manual testing
<a href="https://www.browserstack.com" target="_blank">
<img align="left" width="117" alt="BrowserStack logo" src="https://i.ibb.co/HDRDHmx/Browserstack-logo-2x.png">
</a>
## License
[The MIT License](LICENSE).
| 57.241525 | 421 | 0.735806 | eng_Latn | 0.89952 |
5499fc5f2d3578651fe7d0ae69954cd15ed93444 | 330 | md | Markdown | src/content/2017-10-08-the-beginning/index.md | jmenglis/blog | 7f6dda31827d827fafff89aeca5b5660bda4f12e | [
"MIT"
] | null | null | null | src/content/2017-10-08-the-beginning/index.md | jmenglis/blog | 7f6dda31827d827fafff89aeca5b5660bda4f12e | [
"MIT"
] | 4 | 2019-01-23T02:16:22.000Z | 2022-02-28T03:38:44.000Z | src/content/2017-10-08-the-beginning/index.md | jmenglis/blog | 7f6dda31827d827fafff89aeca5b5660bda4f12e | [
"MIT"
] | null | null | null | ---
title: The beginning
date: 2017-10-08
path: /the-beginning
---
We all have a story to tell and I figured why not tell mine. Occasionally I will tell my tips and tricks about Javascript, natural language processing, and much much more. I figure you may find some humor in the things I have to say and I hope you enjoy them.
| 41.25 | 261 | 0.754545 | eng_Latn | 0.999893 |
549a370a2af04002175e11a12c4461033d350755 | 224 | md | Markdown | cachecloud-web/src/main/resources/static/wiki/function/client-register.md | Mu-L/cachecloud | 6b21290b17702ace3bf97cbe2e2e7c673a1adf70 | [
"Apache-2.0"
] | 6,497 | 2016-01-26T05:52:40.000Z | 2022-03-31T15:06:39.000Z | cachecloud-web/src/main/resources/static/wiki/function/client-register.md | Mu-L/cachecloud | 6b21290b17702ace3bf97cbe2e2e7c673a1adf70 | [
"Apache-2.0"
] | 251 | 2016-01-26T06:17:03.000Z | 2022-03-07T02:26:27.000Z | cachecloud-web/src/main/resources/static/wiki/function/client-register.md | Mu-L/cachecloud | 6b21290b17702ace3bf97cbe2e2e7c673a1adf70 | [
"Apache-2.0"
] | 2,166 | 2016-01-26T09:50:51.000Z | 2022-03-31T06:45:36.000Z | ## 账户申请
用户首次使用CacheCloud执行所有操作之前，用户首先需要申请一个系统账号。当需要开通账户时，填写相关信息。管理员收到申请邮件时确认开通。
- 进入CacheCloud首页，点击注册按钮
- 填写用户相关信息并提交申请
| 18.666667 | 71 | 0.75 | yue_Hant | 0.736409 |
549affafdbfcd0c78669a635c3df0aef87fe5709 | 578 | md | Markdown | README.md | mattpolzin/JSONAPI-Arbitrary | 9d7478b38936df3496719fa9f3504f23d1696f31 | [
"MIT"
] | null | null | null | README.md | mattpolzin/JSONAPI-Arbitrary | 9d7478b38936df3496719fa9f3504f23d1696f31 | [
"MIT"
] | null | null | null | README.md | mattpolzin/JSONAPI-Arbitrary | 9d7478b38936df3496719fa9f3504f23d1696f31 | [
"MIT"
] | null | null | null | # JSONAPI+Arbitrary
See parent project: https://github.com/mattpolzin/JSONAPI
The `JSONAPIArbitrary` framework adds `Arbitrary` support via `SwiftCheck`. With a little extra work on your part, this framework will allow you to create "arbitrary" (i.e. randomly generated) instances of your JSONAPI entities, includes, documents, etc.
This Framework is currently undocumented, but familiarity with `SwiftCheck` will likely afford the user enough information to use this library to aid in the generation of arbitrary JSONAPI Resource Objects and Documents for testing purposes.
| 72.25 | 254 | 0.809689 | eng_Latn | 0.98564 |
549b606d9da9000a7962c7ad741e5067aef9fb7c | 41,872 | md | Markdown | aspnetcore/blazor/state-management.md | albx/AspNetCore.Docs.it-it | db59890a11ee14a7b12a8673f7253aa6d0e4a0c0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnetcore/blazor/state-management.md | albx/AspNetCore.Docs.it-it | db59890a11ee14a7b12a8673f7253aa6d0e4a0c0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnetcore/blazor/state-management.md | albx/AspNetCore.Docs.it-it | db59890a11ee14a7b12a8673f7253aa6d0e4a0c0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: BlazorGestione dello stato ASP.NET Core
author: guardrex
description: Informazioni su come salvare in modo permanente lo stato nelle Blazor Server app.
monikerRange: '>= aspnetcore-3.1'
ms.author: riande
ms.custom: mvc
ms.date: 10/29/2020
no-loc:
- appsettings.json
- ASP.NET Core Identity
- cookie
- Cookie
- Blazor
- Blazor Server
- Blazor WebAssembly
- Identity
- Let's Encrypt
- Razor
- SignalR
uid: blazor/state-management
zone_pivot_groups: blazor-hosting-models
ms.openlocfilehash: 5b7a6fefd13d7255fbe3ae7010df48c6211fa755
ms.sourcegitcommit: 3593c4efa707edeaaceffbfa544f99f41fc62535
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 01/04/2021
ms.locfileid: "97854332"
---
# <a name="aspnet-core-no-locblazor-state-management"></a>BlazorGestione dello stato ASP.NET Core
Di [Steve Sanderson](https://github.com/SteveSandersonMS) e [Luke Latham](https://github.com/guardrex)
::: zone pivot="webassembly"
Lo stato utente creato in un' Blazor WebAssembly app viene mantenuto nella memoria del browser.
Esempi di stato utente contenuti nella memoria del browser includono:
* La gerarchia delle istanze dei componenti e l'output di rendering più recente nell'interfaccia utente sottoposta a rendering.
* Valori dei campi e delle proprietà nelle istanze del componente.
* Dati contenuti nelle istanze del servizio [di inserimento delle dipendenze](xref:fundamentals/dependency-injection) .
* Valori impostati tramite chiamate di [interoperabilità JavaScript](xref:blazor/call-javascript-from-dotnet) .
Quando un utente chiude e riapre il browser o ricarica la pagina, lo stato utente contenuto nella memoria del browser viene perso.
> [!NOTE]
> L' [archiviazione del browser protetto](xref:blazor/state-management?pivots=server#aspnet-core-protected-browser-storage) ( <xref:Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage?displayProperty=fullName> spazio dei nomi) si basa sulla protezione dei dati ASP.NET Core ed è supportata solo per le Blazor Server app.
## <a name="persist-state-across-browser-sessions"></a>Mantieni stato tra le sessioni del browser
In genere, mantenere lo stato tra le sessioni del browser in cui gli utenti stanno creando attivamente dati, non semplicemente leggendo i dati già esistenti.
Per mantenere lo stato tra le sessioni del browser, l'app deve salvare in modo permanente i dati in un'altra posizione di archiviazione rispetto alla memoria del browser. La persistenza dello stato non è automatica. È necessario eseguire i passaggi quando si sviluppa l'app per implementare la persistenza dei dati con stato.
La persistenza dei dati è in genere necessaria solo per uno stato di valore elevato che gli utenti hanno impiegato per creare. Negli esempi seguenti lo stato di salvataggio permanente Risparmia tempo o facilita le attività commerciali:
* Web Form in più passaggi: è necessario che un utente immetta nuovamente i dati per diversi passaggi completati di un modulo Web in più passaggi se il relativo stato viene perso. Un utente perde lo stato in questo scenario se si allontana dal modulo e viene restituito in un secondo momento.
* Carrelli acquisti: è possibile mantenere un componente commercialmente importante di un'app che rappresenti potenziali ricavi. Un utente che perde il proprio stato e quindi il carrello della spesa può acquistare un minor numero di prodotti o servizi quando ritornano al sito in un secondo momento.
Un'app può solo salvare *lo stato dell'app*. Non è possibile rendere permanente le interfacce utente, ad esempio le istanze dei componenti e le relative strutture di rendering. I componenti e gli alberi di rendering non sono in genere serializzabili. Per salvare in modo permanente lo stato dell'interfaccia utente, ad esempio i nodi espansi di un controllo di visualizzazione albero, l'app deve usare codice personalizzato per modellare il comportamento dello stato dell'interfaccia utente come stato dell'app serializzabile.
## <a name="where-to-persist-state"></a>Posizione in cui salvare lo stato
Esistono località comuni per lo stato permanente:
* [Archiviazione sul lato server](#server-side-storage-wasm)
* [URL](#url-wasm)
* [Archiviazione del browser](#browser-storage-wasm)
* [Servizio contenitore stato in memoria](#in-memory-state-container-service-wasm)
<h2 id="server-side-storage-wasm">Archiviazione sul lato server</h2>
Per la persistenza permanente dei dati che si estende su più utenti e dispositivi, l'app può usare l'archiviazione indipendente del lato server a cui si accede tramite un'API Web. Le opzioni includono:
* Archiviazione BLOB
* Archiviazione chiave-valore
* Database relazionale
* Archiviazione tabelle
Dopo il salvataggio dei dati, lo stato dell'utente viene mantenuto e disponibile in qualsiasi nuova sessione del browser.
Poiché Blazor WebAssembly le app vengono eseguite interamente nel browser dell'utente, richiedono misure aggiuntive per accedere a sistemi esterni protetti, ad esempio i servizi di archiviazione e i database. Blazor WebAssembly le app sono protette in modo analogo alle applicazioni a pagina singola (Spa). In genere, un'app autentica un utente tramite [OAuth](https://oauth.net) / [OpenID Connect (OIDC)](https://openid.net/connect/) e quindi interagisce con i servizi di archiviazione e i database tramite chiamate API Web a un'app sul lato server. L'app sul lato server media il trasferimento dei dati tra l' Blazor WebAssembly app e il servizio di archiviazione o il database. L'app Blazor WebAssembly mantiene una connessione temporanea all'app sul lato server, mentre l'app sul lato server dispone di una connessione permanente alla risorsa di archiviazione.
Per altre informazioni, vedere le risorse seguenti:
* <xref:blazor/call-web-api>
* <xref:blazor/security/webassembly/index>
* Blazor*Sicurezza e Identity* articoli
Per ulteriori informazioni sulle opzioni di archiviazione dei dati di Azure, vedere gli argomenti seguenti:
* [Database di Azure](https://azure.microsoft.com/product-categories/databases/)
* [Documentazione di archiviazione di Azure](/azure/storage/)
<h2 id="url-wasm">URL</h2>
Per i dati temporanei che rappresentano lo stato di navigazione, modellare i dati come parte dell'URL. Esempi di stato utente modellati nell'URL includono:
* ID di un'entità visualizzata.
* Numero di pagina corrente in una griglia di paging.
Il contenuto della barra degli indirizzi del browser viene mantenuto se l'utente ricarica manualmente la pagina.
Per informazioni sulla definizione di modelli URL con la [`@page`](xref:mvc/views/razor#page) direttiva, vedere <xref:blazor/fundamentals/routing> .
<h2 id="browser-storage-wasm">Archiviazione del browser</h2>
Per i dati temporanei che l'utente sta creando attivamente, un percorso di archiviazione di uso comune è costituito dalle [`localStorage`](https://developer.mozilla.org/docs/Web/API/Window/localStorage) raccolte e del browser [`sessionStorage`](https://developer.mozilla.org/docs/Web/API/Window/sessionStorage) :
* `localStorage` ha come ambito la finestra del browser. Se l'utente ricarica la pagina o chiude e riapre il browser, lo stato è permanente. Se l'utente apre più schede del browser, lo stato viene condiviso tra le schede. I dati rimangono in `localStorage` fino a quando non vengono cancellati in modo esplicito.
* `sessionStorage` ha come ambito la scheda Esplorazione. Se l'utente ricarica la scheda, lo stato è permanente. Se l'utente chiude la scheda o il browser, lo stato viene perso. Se l'utente apre più schede del browser, ogni scheda ha una propria versione indipendente dei dati.
> [!NOTE]
> `localStorage` e `sessionStorage` possono essere usati nelle Blazor WebAssembly app, ma solo scrivendo codice personalizzato o usando un pacchetto di terze parti.
In genere, `sessionStorage` è più sicuro da usare. `sessionStorage` evita il rischio che un utente apra più schede e riscontri quanto segue:
* Bug nell'archiviazione dello stato tra le schede.
* Comportamento confuso quando una scheda sovrascrive lo stato di altre schede.
`localStorage` è la scelta migliore se l'app deve conservare lo stato tra la chiusura e la riapertura del browser.
> [!WARNING]
> Gli utenti possono visualizzare o manomettere i dati archiviati in `localStorage` e `sessionStorage` .
<h2 id="in-memory-state-container-service-wasm">Servizio contenitore stato in memoria</h2>
[!INCLUDE[](~/blazor/includes/state-container.md)]
## <a name="additional-resources"></a>Risorse aggiuntive
* [Salva lo stato dell'app prima di un'operazione di autenticazione](xref:blazor/security/webassembly/additional-scenarios#save-app-state-before-an-authentication-operation)
* <xref:blazor/call-web-api>
* <xref:blazor/security/webassembly/index>
::: zone-end
::: zone pivot="server"
Blazor Server è un Framework di app con stato. Nella maggior parte dei casi, l'app mantiene una connessione al server. Lo stato dell'utente viene mantenuto nella memoria del server in un *circuito*.
Esempi di stato utente contenuti in un circuito includono:
* La gerarchia delle istanze dei componenti e l'output di rendering più recente nell'interfaccia utente sottoposta a rendering.
* Valori dei campi e delle proprietà nelle istanze del componente.
* Dati contenuti nelle istanze del servizio [di inserimento delle dipendenze](xref:fundamentals/dependency-injection) che hanno come ambito il circuito.
Lo stato utente potrebbe trovarsi anche in variabili JavaScript nel set di memoria del browser tramite chiamate di [interoperabilità JavaScript](xref:blazor/call-javascript-from-dotnet) .
Se un utente riscontra una perdita di connessione di rete temporanea, Blazor tenta di riconnettere l'utente al circuito originale con lo stato originale. Tuttavia, la riconnessione di un utente al circuito originale nella memoria del server non è sempre possibile:
* Il server non è in grado di mantenere sempre un circuito disconnesso. Il server deve rilasciare un circuito disconnesso dopo un timeout o quando il server è sottoposto a un numero eccessivo di richieste di memoria.
* Negli ambienti di distribuzione con bilanciamento del carico multiserver, i singoli server possono avere esito negativo o essere rimossi automaticamente quando non sono più necessari per gestire il volume complessivo delle richieste. Le richieste di elaborazione del server originale per un utente potrebbero non essere più disponibili quando l'utente tenta di riconnettersi.
* L'utente potrebbe chiudere e riaprire il browser o ricaricare la pagina, che rimuove qualsiasi stato contenuto nella memoria del browser. Ad esempio, i valori delle variabili JavaScript impostati tramite le chiamate di interoperabilità JavaScript vengono persi.
Quando un utente non può essere riconnesso al circuito originale, l'utente riceve un nuovo circuito con uno stato vuoto. Questa operazione equivale a chiudere e riaprire un'app desktop.
## <a name="persist-state-across-circuits"></a>Mantieni lo stato tra circuiti
In genere, mantenere lo stato nei circuiti in cui gli utenti stanno creando attivamente dati, non semplicemente leggendo i dati già esistenti.
Per mantenere lo stato tra circuiti, l'app deve salvare in modo permanente i dati in un'altra posizione di archiviazione rispetto alla memoria del server. La persistenza dello stato non è automatica. È necessario eseguire i passaggi quando si sviluppa l'app per implementare la persistenza dei dati con stato.
La persistenza dei dati è in genere necessaria solo per uno stato di valore elevato che gli utenti hanno impiegato per creare. Negli esempi seguenti lo stato di salvataggio permanente Risparmia tempo o facilita le attività commerciali:
* Web Form in più passaggi: è necessario che un utente immetta nuovamente i dati per diversi passaggi completati di un modulo Web in più passaggi se il relativo stato viene perso. Un utente perde lo stato in questo scenario se si allontana dal modulo e viene restituito in un secondo momento.
* Carrelli acquisti: è possibile mantenere un componente commercialmente importante di un'app che rappresenti potenziali ricavi. Un utente che perde il proprio stato e quindi il carrello della spesa può acquistare un minor numero di prodotti o servizi quando ritornano al sito in un secondo momento.
Un'app può solo salvare *lo stato dell'app*. Non è possibile rendere permanente le interfacce utente, ad esempio le istanze dei componenti e le relative strutture di rendering. I componenti e gli alberi di rendering non sono in genere serializzabili. Per salvare in modo permanente lo stato dell'interfaccia utente, ad esempio i nodi espansi di un controllo di visualizzazione albero, l'app deve usare codice personalizzato per modellare il comportamento dello stato dell'interfaccia utente come stato dell'app serializzabile.
## <a name="where-to-persist-state"></a>Posizione in cui salvare lo stato
Esistono località comuni per lo stato permanente:
* [Archiviazione sul lato server](#server-side-storage-server)
* [URL](#url-server)
* [Archiviazione del browser](#browser-storage-server)
* [Servizio contenitore stato in memoria](#in-memory-state-container-service-server)
<h2 id="server-side-storage-server">Archiviazione sul lato server</h2>
Per la persistenza permanente dei dati che si estende su più utenti e dispositivi, l'app può usare l'archiviazione sul lato server. Le opzioni includono:
* Archiviazione BLOB
* Archiviazione chiave-valore
* Database relazionale
* Archiviazione tabelle
Dopo il salvataggio dei dati, lo stato dell'utente viene mantenuto e disponibile in qualsiasi nuovo circuito.
Per ulteriori informazioni sulle opzioni di archiviazione dei dati di Azure, vedere gli argomenti seguenti:
* [Database di Azure](https://azure.microsoft.com/product-categories/databases/)
* [Documentazione di archiviazione di Azure](/azure/storage/)
<h2 id="url-server">URL</h2>
Per i dati temporanei che rappresentano lo stato di navigazione, modellare i dati come parte dell'URL. Esempi di stato utente modellati nell'URL includono:
* ID di un'entità visualizzata.
* Numero di pagina corrente in una griglia di paging.
Il contenuto della barra degli indirizzi del browser viene mantenuto:
* Se l'utente ricarica manualmente la pagina.
* Se il server Web non è più disponibile e l'utente è costretto a ricaricare la pagina per connettersi a un server diverso.
Per informazioni sulla definizione di modelli URL con la [`@page`](xref:mvc/views/razor#page) direttiva, vedere <xref:blazor/fundamentals/routing> .
<h2 id="browser-storage-server">Archiviazione del browser</h2>
Per i dati temporanei che l'utente sta creando attivamente, un percorso di archiviazione di uso comune è costituito dalle [`localStorage`](https://developer.mozilla.org/docs/Web/API/Window/localStorage) raccolte e del browser [`sessionStorage`](https://developer.mozilla.org/docs/Web/API/Window/sessionStorage) :
* `localStorage` ha come ambito la finestra del browser. Se l'utente ricarica la pagina o chiude e riapre il browser, lo stato è permanente. Se l'utente apre più schede del browser, lo stato viene condiviso tra le schede. I dati rimangono in `localStorage` fino a quando non vengono cancellati in modo esplicito.
* `sessionStorage` ha come ambito la scheda Esplorazione. Se l'utente ricarica la scheda, lo stato è permanente. Se l'utente chiude la scheda o il browser, lo stato viene perso. Se l'utente apre più schede del browser, ogni scheda ha una propria versione indipendente dei dati.
In genere, `sessionStorage` è più sicuro da usare. `sessionStorage` evita il rischio che un utente apra più schede e riscontri quanto segue:
* Bug nell'archiviazione dello stato tra le schede.
* Comportamento confuso quando una scheda sovrascrive lo stato di altre schede.
`localStorage` è la scelta migliore se l'app deve conservare lo stato tra la chiusura e la riapertura del browser.
Avvertenze per l'uso dell'archiviazione del browser:
* Analogamente all'utilizzo di un database lato server, il caricamento e il salvataggio dei dati sono asincroni.
* A differenza di un database lato server, l'archiviazione non è disponibile durante il prerendering perché la pagina richiesta non esiste nel browser durante la fase di pre-rendering.
* L'archiviazione di alcuni kilobyte di dati è ragionevole per la permanenza per le Blazor Server app. Oltre alcuni kilobyte, è necessario considerare le implicazioni relative alle prestazioni perché i dati vengono caricati e salvati in rete.
* Gli utenti possono visualizzare o manomettere i dati. [ASP.NET Core protezione dei dati](xref:security/data-protection/introduction) può ridurre il rischio. Ad esempio, [ASP.NET Core archiviazione del browser protetta](#aspnet-core-protected-browser-storage) utilizza ASP.NET Core la protezione dei dati.
I pacchetti NuGet di terze parti forniscono le API per l'uso di `localStorage` e `sessionStorage` . Vale la pena considerare la scelta di un pacchetto che usa in modo trasparente [ASP.NET Core la protezione dei dati](xref:security/data-protection/introduction). La protezione dei dati consente di crittografare i dati archiviati e riduce il rischio potenziale di manomissione dei dati archiviati. Se i dati serializzati in JSON vengono archiviati in testo normale, gli utenti possono visualizzare i dati usando gli strumenti di sviluppo del browser e modificare anche i dati archiviati. La protezione dei dati non è sempre un problema perché i dati potrebbero essere di natura banale. Ad esempio, la lettura o la modifica del colore archiviato di un elemento dell'interfaccia utente non costituisce un rischio di sicurezza significativo per l'utente o l'organizzazione. Evitare di consentire agli utenti di ispezionare o manomettere *i dati sensibili*.
::: moniker range=">= aspnetcore-5.0"
## <a name="aspnet-core-protected-browser-storage"></a>ASP.NET Core archiviazione del browser protetta
ASP.NET Core archiviazione del browser protetta sfrutta la [protezione dei dati ASP.NET Core](xref:security/data-protection/introduction) per [`localStorage`](https://developer.mozilla.org/docs/Web/API/Window/localStorage) e [`sessionStorage`](https://developer.mozilla.org/docs/Web/API/Window/sessionStorage) .
> [!NOTE]
> L'archiviazione del browser protetto si basa sulla protezione dei dati ASP.NET Core ed è supportata solo per le Blazor Server app.
### <a name="save-and-load-data-within-a-component"></a>Salvare e caricare i dati all'interno di un componente
In tutti i componenti che richiedono il caricamento o il salvataggio dei dati nell'archiviazione del browser, utilizzare la [`@inject`](xref:mvc/views/razor#inject) direttiva per inserire un'istanza di uno dei seguenti elementi:
* `ProtectedLocalStorage`
* `ProtectedSessionStorage`
La scelta dipende dal percorso di archiviazione del browser che si desidera utilizzare. Nell'esempio seguente `sessionStorage` viene usato:
```razor
@using Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage
@inject ProtectedSessionStorage ProtectedSessionStore
```
La `@using` direttiva può essere inserita nel file dell'app `_Imports.razor` anziché nel componente. L'uso del `_Imports.razor` file rende lo spazio dei nomi disponibile a segmenti più grandi dell'app o dell'intera app.
Per salvare in modo permanente il `currentCount` valore nel `Counter` componente di un'app in base al Blazor Server modello di progetto, modificare il `IncrementCount` metodo in modo da usare `ProtectedSessionStore.SetAsync` :
```csharp
private async Task IncrementCount()
{
currentCount++;
await ProtectedSessionStore.SetAsync("count", currentCount);
}
```
Nelle app più grandi e più realistiche, l'archiviazione dei singoli campi è uno scenario improbabile. È più probabile che le app memorizzino interi oggetti modello che includono lo stato complesso. `ProtectedSessionStore` serializza e deserializza automaticamente i dati JSON per archiviare oggetti di stato complessi.
Nell'esempio di codice precedente i `currentCount` dati vengono archiviati come `sessionStorage['count']` nel browser dell'utente. I dati non vengono archiviati in testo normale ma sono invece protetti tramite la protezione dei dati ASP.NET Core. I dati crittografati possono essere controllati se `sessionStorage['count']` viene valutato nella console per sviluppatori del browser.
Per ripristinare i `currentCount` dati se l'utente torna al `Counter` componente in un secondo momento, anche se l'utente si trova in un nuovo circuito, usare `ProtectedSessionStore.GetAsync` :
```csharp
protected override async Task OnInitializedAsync()
{
var result = await ProtectedSessionStore.GetAsync<int>("count");
currentCount = result.Success ? result.Value : 0;
}
```
Se i parametri del componente includono lo stato di navigazione, chiamare `ProtectedSessionStore.GetAsync` e assegnare un non `null` risultato in <xref:Microsoft.AspNetCore.Components.ComponentBase.OnParametersSetAsync%2A> , non <xref:Microsoft.AspNetCore.Components.ComponentBase.OnInitializedAsync%2A> . <xref:Microsoft.AspNetCore.Components.ComponentBase.OnInitializedAsync%2A> viene chiamato una sola volta al momento della creazione di un'istanza del componente. <xref:Microsoft.AspNetCore.Components.ComponentBase.OnInitializedAsync%2A> non viene chiamato di nuovo in un secondo momento se l'utente passa a un URL diverso rimanendo nella stessa pagina. Per altre informazioni, vedere <xref:blazor/components/lifecycle>.
> [!WARNING]
> Gli esempi in questa sezione funzionano solo se per il server non è abilitato il prerendering. Con il prerendering abilitato, viene generato un errore che indica che non è possibile eseguire chiamate di interoperabilità JavaScript perché è in corso il rendering del componente.
>
> Disabilitare il prerendering o aggiungere altro codice per lavorare con il prerendering. Per ulteriori informazioni sulla scrittura di codice che funziona con il prerendering, vedere la sezione [handle prerendering](#handle-prerendering) .
### <a name="handle-the-loading-state"></a>Gestire lo stato di caricamento
Poiché l'accesso all'archiviazione del browser avviene in modo asincrono tramite una connessione di rete, è sempre necessario un certo periodo di tempo prima che i dati vengano caricati e disponibili per un componente. Per ottenere risultati ottimali, è possibile eseguire il rendering di un messaggio di stato di caricamento mentre è in corso il caricamento anziché visualizzare dati vuoti o predefiniti.
Un approccio consiste nel rilevare se i dati sono `null` , il che significa che i dati sono ancora in corso di caricamento. Nel componente predefinito `Counter` , il conteggio viene mantenuto in un oggetto `int` . [Rendere `currentCount` Nullable](/dotnet/csharp/language-reference/builtin-types/nullable-value-types) aggiungendo un punto interrogativo ( `?` ) al tipo ( `int` ):
```csharp
private int? currentCount;
```
Anziché visualizzare in modo incondizionato il conteggio e il **`Increment`** pulsante, visualizzare questi elementi solo se i dati vengono caricati controllando <xref:System.Nullable%601.HasValue%2A> :
```razor
@if (currentCount.HasValue)
{
<p>Current count: <strong>@currentCount</strong></p>
<button @onclick="IncrementCount">Increment</button>
}
else
{
<p>Loading...</p>
}
```
### <a name="handle-prerendering"></a>Gestione preliminare
Durante il prerendering:
* Una connessione interattiva al browser dell'utente non esiste.
* Il browser non dispone ancora di una pagina in cui è possibile eseguire il codice JavaScript.
`localStorage` o `sessionStorage` non sono disponibili durante il prerendering. Se il componente tenta di interagire con l'archiviazione, viene generato un errore che indica che non è possibile eseguire chiamate di interoperabilità JavaScript perché è in corso il rendering del componente.
Un modo per risolvere l'errore consiste nel disabilitare il prerendering. Questa è in genere la scelta migliore se l'app usa in modo intensivo l'archiviazione basata su browser. Il prerendering aggiunge complessità e non è vantaggioso per l'app perché l'app non può prerenderizzare contenuti utili fino a quando non `localStorage` `sessionStorage` sono disponibili o.
Per disabilitare il prerendering, aprire il `Pages/_Host.cshtml` file e modificare l' `render-mode` attributo dell' [Helper tag dei componenti](xref:mvc/views/tag-helpers/builtin-th/component-tag-helper) in <xref:Microsoft.AspNetCore.Mvc.Rendering.RenderMode.Server> :
```cshtml
<component type="typeof(App)" render-mode="Server" />
```
Il prerendering può essere utile per altre pagine che non utilizzano `localStorage` o `sessionStorage` . Per mantenere il prerendering, rinviare l'operazione di caricamento finché il browser non è connesso al circuito. Di seguito è riportato un esempio per l'archiviazione di un valore del contatore:
```razor
@using Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage
@inject ProtectedLocalStorage ProtectedLocalStore
@if (isConnected)
{
<p>Current count: <strong>@currentCount</strong></p>
<button @onclick="IncrementCount">Increment</button>
}
else
{
<p>Loading...</p>
}
@code {
private int currentCount;
private bool isConnected;
protected override async Task OnAfterRenderAsync(bool firstRender)
{
if (firstRender)
{
isConnected = true;
await LoadStateAsync();
StateHasChanged();
}
}
private async Task LoadStateAsync()
{
var result = await ProtectedLocalStore.GetAsync<int>("count");
currentCount = result.Success ? result.Value : 0;
}
private async Task IncrementCount()
{
currentCount++;
await ProtectedLocalStore.SetAsync("count", currentCount);
}
}
```
### <a name="factor-out-the-state-preservation-to-a-common-location"></a>Fattorizzare la conservazione dello stato in una posizione comune
Se molti componenti si basano sull'archiviazione basata su browser, la reimplementazione del codice del provider di stato più volte crea una duplicazione del codice. Un'opzione per evitare la duplicazione del codice consiste nel creare un *componente padre del provider di stato* che incapsula la logica del provider di stato. I componenti figlio possono funzionare con i dati persistenti senza considerare il meccanismo di persistenza dello stato.
Nell'esempio seguente di un `CounterStateProvider` componente, i dati del contatore vengono salvati in modo permanente in `sessionStorage` :
```razor
@using Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage
@inject ProtectedSessionStorage ProtectedSessionStore
@if (isLoaded)
{
<CascadingValue Value="@this">
@ChildContent
</CascadingValue>
}
else
{
<p>Loading...</p>
}
@code {
private bool isLoaded;
[Parameter]
public RenderFragment ChildContent { get; set; }
public int CurrentCount { get; set; }
protected override async Task OnInitializedAsync()
{
var result = await ProtectedSessionStore.GetAsync<int>("count");
currentCount = result.Success ? result.Value : 0;
isLoaded = true;
}
public async Task SaveChangesAsync()
{
await ProtectedSessionStore.SetAsync("count", CurrentCount);
}
}
```
Il `CounterStateProvider` componente gestisce la fase di caricamento non eseguendo il rendering del relativo contenuto figlio fino al completamento del caricamento.
Per utilizzare il `CounterStateProvider` componente, eseguire il wrapping di un'istanza del componente intorno a qualsiasi altro componente che richiede l'accesso allo stato del contatore. Per rendere lo stato accessibile a tutti i componenti di un'app, eseguire il wrapping del `CounterStateProvider` componente intorno all'oggetto <xref:Microsoft.AspNetCore.Components.Routing.Router> nel `App` componente ( `App.razor` ):
```razor
<CounterStateProvider>
<Router AppAssembly="@typeof(Program).Assembly">
...
</Router>
</CounterStateProvider>
```
[!INCLUDE[](~/blazor/includes/prefer-exact-matches.md)]
I componenti di cui è stato eseguito il wrapper ricevono e possono modificare lo stato del contatore permanente. Il `Counter` componente seguente implementa il modello:
```razor
@page "/counter"
<p>Current count: <strong>@CounterStateProvider.CurrentCount</strong></p>
<button @onclick="IncrementCount">Increment</button>
@code {
[CascadingParameter]
private CounterStateProvider CounterStateProvider { get; set; }
private async Task IncrementCount()
{
CounterStateProvider.CurrentCount++;
await CounterStateProvider.SaveChangesAsync();
}
}
```
Il componente precedente non è necessario per interagire con `ProtectedBrowserStorage` , né gestire una fase di "caricamento".
Per gestire il prerendering come descritto in precedenza, `CounterStateProvider` può essere modificato in modo che tutti i componenti che utilizzano i dati del contatore funzionino automaticamente con il prerendering. Per ulteriori informazioni, vedere la sezione [handle prerendering](#handle-prerendering) .
In generale, è consigliabile usare il modello di *componente padre del provider di stato* :
* Per utilizzare lo stato tra molti componenti.
* Se è presente un solo oggetto di stato di primo livello da salvare in modo permanente.
Per salvare in modo permanente molti oggetti di stato diversi e utilizzare subset diversi di oggetti in posizioni diverse, è preferibile evitare di salvare in modo permanente lo stato a livello globale.
::: moniker-end
::: moniker range="< aspnetcore-5.0"
## <a name="protected-browser-storage-experimental-nuget-package"></a>Pacchetto NuGet sperimentale di archiviazione del browser protetto
ASP.NET Core archiviazione del browser protetta sfrutta la [protezione dei dati ASP.NET Core](xref:security/data-protection/introduction) per [`localStorage`](https://developer.mozilla.org/docs/Web/API/Window/localStorage) e [`sessionStorage`](https://developer.mozilla.org/docs/Web/API/Window/sessionStorage) .
> [!WARNING]
> `Microsoft.AspNetCore.ProtectedBrowserStorage` è un pacchetto sperimentale non supportato non adatto per l'uso in ambiente di produzione.
>
> Il pacchetto è disponibile solo per l'uso in app ASP.NET Core 3,1 Blazor Server .
### <a name="configuration"></a>Configurazione
1. Aggiungere un riferimento al pacchetto a [`Microsoft.AspNetCore.ProtectedBrowserStorage`](https://www.nuget.org/packages/Microsoft.AspNetCore.ProtectedBrowserStorage) .
1. Nel `Pages/_Host.cshtml` file aggiungere il seguente script all'interno del tag di chiusura `</body>` :
```cshtml
<script src="_content/Microsoft.AspNetCore.ProtectedBrowserStorage/protectedBrowserStorage.js"></script>
```
1. In `Startup.ConfigureServices` chiamare `AddProtectedBrowserStorage` per aggiungere `localStorage` e `sessionStorage` servizi alla raccolta di servizi:
```csharp
services.AddProtectedBrowserStorage();
```
### <a name="save-and-load-data-within-a-component"></a>Salvare e caricare i dati all'interno di un componente
In tutti i componenti che richiedono il caricamento o il salvataggio dei dati nell'archiviazione del browser, utilizzare la [`@inject`](xref:mvc/views/razor#inject) direttiva per inserire un'istanza di uno dei seguenti elementi:
* `ProtectedLocalStorage`
* `ProtectedSessionStorage`
La scelta dipende dal percorso di archiviazione del browser che si desidera utilizzare. Nell'esempio seguente `sessionStorage` viene usato:
```razor
@using Microsoft.AspNetCore.ProtectedBrowserStorage
@inject ProtectedSessionStorage ProtectedSessionStore
```
L' `@using` istruzione può essere inserita in un `_Imports.razor` file anziché nel componente. L'uso del `_Imports.razor` file rende lo spazio dei nomi disponibile a segmenti più grandi dell'app o dell'intera app.
Per salvare in modo permanente il `currentCount` valore nel `Counter` componente di un'app in base al Blazor Server modello di progetto, modificare il `IncrementCount` metodo in modo da usare `ProtectedSessionStore.SetAsync` :
```csharp
private async Task IncrementCount()
{
currentCount++;
await ProtectedSessionStore.SetAsync("count", currentCount);
}
```
Nelle app più grandi e più realistiche, l'archiviazione dei singoli campi è uno scenario improbabile. È più probabile che le app memorizzino interi oggetti modello che includono lo stato complesso. `ProtectedSessionStore` serializza e deserializza automaticamente i dati JSON.
Nell'esempio di codice precedente i `currentCount` dati vengono archiviati come `sessionStorage['count']` nel browser dell'utente. I dati non vengono archiviati in testo normale ma sono invece protetti tramite la protezione dei dati ASP.NET Core. I dati crittografati possono essere controllati se `sessionStorage['count']` viene valutato nella console per sviluppatori del browser.
Per ripristinare i `currentCount` dati se l'utente torna al `Counter` componente in un secondo momento, anche se si trovano in un circuito completamente nuovo, usare `ProtectedSessionStore.GetAsync` :
```csharp
protected override async Task OnInitializedAsync()
{
currentCount = await ProtectedSessionStore.GetAsync<int>("count");
}
```
Se i parametri del componente includono lo stato di navigazione, chiamare `ProtectedSessionStore.GetAsync` e assegnare il risultato in <xref:Microsoft.AspNetCore.Components.ComponentBase.OnParametersSetAsync%2A> , non <xref:Microsoft.AspNetCore.Components.ComponentBase.OnInitializedAsync%2A> . <xref:Microsoft.AspNetCore.Components.ComponentBase.OnInitializedAsync%2A> viene chiamato una sola volta al momento della creazione di un'istanza del componente. <xref:Microsoft.AspNetCore.Components.ComponentBase.OnInitializedAsync%2A> non viene chiamato di nuovo in un secondo momento se l'utente passa a un URL diverso rimanendo nella stessa pagina. Per altre informazioni, vedere <xref:blazor/components/lifecycle>.
> [!WARNING]
> Gli esempi in questa sezione funzionano solo se per il server non è abilitato il prerendering. Con il prerendering abilitato, viene generato un errore che indica che non è possibile eseguire chiamate di interoperabilità JavaScript perché è in corso il rendering del componente.
>
> Disabilitare il prerendering o aggiungere altro codice per lavorare con il prerendering. Per ulteriori informazioni sulla scrittura di codice che funziona con il prerendering, vedere la sezione [handle prerendering](#handle-prerendering) .
### <a name="handle-the-loading-state"></a>Gestire lo stato di caricamento
Poiché l'accesso all'archiviazione del browser avviene in modo asincrono tramite una connessione di rete, è sempre necessario un certo periodo di tempo prima che i dati vengano caricati e disponibili per un componente. Per ottenere risultati ottimali, è possibile eseguire il rendering di un messaggio di stato di caricamento mentre è in corso il caricamento anziché visualizzare dati vuoti o predefiniti.
Un approccio consiste nel rilevare se i dati sono `null` , il che significa che i dati sono ancora in corso di caricamento. Nel componente predefinito `Counter` , il conteggio viene mantenuto in un oggetto `int` . [Rendere `currentCount` Nullable](/dotnet/csharp/language-reference/builtin-types/nullable-value-types) aggiungendo un punto interrogativo ( `?` ) al tipo ( `int` ):
```csharp
private int? currentCount;
```
Anziché visualizzare in modo non condizionale il numero e il **`Increment`** pulsante, scegliere di visualizzare questi elementi solo se i dati vengono caricati:
```razor
@if (currentCount.HasValue)
{
<p>Current count: <strong>@currentCount</strong></p>
<button @onclick="IncrementCount">Increment</button>
}
else
{
<p>Loading...</p>
}
```
### <a name="handle-prerendering"></a>Gestione preliminare
Durante il prerendering:
* Una connessione interattiva al browser dell'utente non esiste.
* Il browser non dispone ancora di una pagina in cui è possibile eseguire il codice JavaScript.
`localStorage` o `sessionStorage` non sono disponibili durante il prerendering. Se il componente tenta di interagire con l'archiviazione, viene generato un errore che indica che non è possibile eseguire chiamate di interoperabilità JavaScript perché è in corso il rendering del componente.
Un modo per risolvere l'errore consiste nel disabilitare il prerendering. Questa è in genere la scelta migliore se l'app usa in modo intensivo l'archiviazione basata su browser. Il prerendering aggiunge complessità e non è vantaggioso per l'app perché l'app non può prerenderizzare contenuti utili fino a quando non `localStorage` `sessionStorage` sono disponibili o.
Per disabilitare il prerendering, aprire il `Pages/_Host.cshtml` file e modificare l' `render-mode` attributo dell' [Helper tag dei componenti](xref:mvc/views/tag-helpers/builtin-th/component-tag-helper) in <xref:Microsoft.AspNetCore.Mvc.Rendering.RenderMode.Server> :
```cshtml
<component type="typeof(App)" render-mode="Server" />
```
Il prerendering può essere utile per altre pagine che non utilizzano `localStorage` o `sessionStorage` . Per mantenere il prerendering, rinviare l'operazione di caricamento finché il browser non è connesso al circuito. Di seguito è riportato un esempio per l'archiviazione di un valore del contatore:
```razor
@using Microsoft.AspNetCore.ProtectedBrowserStorage
@inject ProtectedLocalStorage ProtectedLocalStore
@if (isConnected)
{
<p>Current count: <strong>@currentCount</strong></p>
<button @onclick="IncrementCount">Increment</button>
}
else
{
<p>Loading...</p>
}
@code {
private int? currentCount;
private bool isConnected = false;
protected override async Task OnAfterRenderAsync(bool firstRender)
{
if (firstRender)
{
isConnected = true;
await LoadStateAsync();
StateHasChanged();
}
}
private async Task LoadStateAsync()
{
currentCount = await ProtectedLocalStore.GetAsync<int>("count");
}
private async Task IncrementCount()
{
currentCount++;
await ProtectedLocalStore.SetAsync("count", currentCount);
}
}
```
### <a name="factor-out-the-state-preservation-to-a-common-location"></a>Fattorizzare la conservazione dello stato in una posizione comune
Se molti componenti si basano sull'archiviazione basata su browser, la reimplementazione del codice del provider di stato più volte crea una duplicazione del codice. Un'opzione per evitare la duplicazione del codice consiste nel creare un *componente padre del provider di stato* che incapsula la logica del provider di stato. I componenti figlio possono funzionare con i dati persistenti senza considerare il meccanismo di persistenza dello stato.
Nell'esempio seguente di un `CounterStateProvider` componente, i dati del contatore vengono salvati in modo permanente in `sessionStorage` :
```razor
@using Microsoft.AspNetCore.ProtectedBrowserStorage
@inject ProtectedSessionStorage ProtectedSessionStore
@if (isLoaded)
{
<CascadingValue Value="@this">
@ChildContent
</CascadingValue>
}
else
{
<p>Loading...</p>
}
@code {
private bool isLoaded;
[Parameter]
public RenderFragment ChildContent { get; set; }
public int CurrentCount { get; set; }
protected override async Task OnInitializedAsync()
{
CurrentCount = await ProtectedSessionStore.GetAsync<int>("count");
isLoaded = true;
}
public async Task SaveChangesAsync()
{
await ProtectedSessionStore.SetAsync("count", CurrentCount);
}
}
```
Il `CounterStateProvider` componente gestisce la fase di caricamento non eseguendo il rendering del relativo contenuto figlio fino al completamento del caricamento.
Per utilizzare il `CounterStateProvider` componente, eseguire il wrapping di un'istanza del componente intorno a qualsiasi altro componente che richiede l'accesso allo stato del contatore. Per rendere lo stato accessibile a tutti i componenti di un'app, eseguire il wrapping del `CounterStateProvider` componente intorno all'oggetto <xref:Microsoft.AspNetCore.Components.Routing.Router> nel `App` componente ( `App.razor` ):
```razor
<CounterStateProvider>
<Router AppAssembly="@typeof(Program).Assembly">
...
</Router>
</CounterStateProvider>
```
[!INCLUDE[](~/blazor/includes/prefer-exact-matches.md)]
I componenti di cui è stato eseguito il wrapper ricevono e possono modificare lo stato del contatore permanente. Il `Counter` componente seguente implementa il modello:
```razor
@page "/counter"
<p>Current count: <strong>@CounterStateProvider.CurrentCount</strong></p>
<button @onclick="IncrementCount">Increment</button>
@code {
[CascadingParameter]
private CounterStateProvider CounterStateProvider { get; set; }
private async Task IncrementCount()
{
CounterStateProvider.CurrentCount++;
await CounterStateProvider.SaveChangesAsync();
}
}
```
Il componente precedente non è necessario per interagire con `ProtectedBrowserStorage` , né gestire una fase di "caricamento".
Per gestire il prerendering come descritto in precedenza, `CounterStateProvider` può essere modificato in modo che tutti i componenti che utilizzano i dati del contatore funzionino automaticamente con il prerendering. Per ulteriori informazioni, vedere la sezione [handle prerendering](#handle-prerendering) .
In generale, è consigliabile usare il modello di *componente padre del provider di stato* :
* Per utilizzare lo stato tra molti componenti.
* Se è presente un solo oggetto di stato di primo livello da salvare in modo permanente.
Per salvare in modo permanente molti oggetti di stato diversi e utilizzare subset diversi di oggetti in posizioni diverse, è preferibile evitare di salvare in modo permanente lo stato a livello globale.
::: moniker-end
<h2 id="in-memory-state-container-service-server">Servizio contenitore stato in memoria</h2>
[!INCLUDE[](~/blazor/includes/state-container.md)]
::: zone-end
| 58.562238 | 952 | 0.788594 | ita_Latn | 0.998005 |
549b7347238719861d3e94b83c4a887876a3eff8 | 2,198 | md | Markdown | .github/ISSUE_TEMPLATE/bug_report.md | shlomiv/papiea | 81efe9447a55c1ffed8f389cbddf0990097b512a | [
"Apache-2.0"
] | null | null | null | .github/ISSUE_TEMPLATE/bug_report.md | shlomiv/papiea | 81efe9447a55c1ffed8f389cbddf0990097b512a | [
"Apache-2.0"
] | null | null | null | .github/ISSUE_TEMPLATE/bug_report.md | shlomiv/papiea | 81efe9447a55c1ffed8f389cbddf0990097b512a | [
"Apache-2.0"
] | null | null | null | ---
name: Bug report
about: Create a report to help us improve
---
<!-- NOTE: Please put only ONE problem per bug report. If you're not sure whether you have one problem or multiple problems, please err on the side of filing more bug reports. It's much easier to close duplicates than split a single issue into multiple issues. -->
### System Details
<!-- THIS SECTION IS REQUIRED. Please fill in the necessary information -->
- **Papiea Engine version**: [e.g. 1.0.62]
- **Papiea SDK version:** [e.g. 1.0.62]
- **Papiea Client version:** [e.g. 1.0.62]
### Describe the Bug
<!-- A short description of what the problem is and/or what happened. -->
### Bug information
<!-- Yaml files (spec, metadata extension, auth if present) and Code samples that caused the malfunction (procedure
handlers/intent handlers/etc) -->
### Expected/Actual Behavior
<!-- A short description of what you expected to happen and what happened instead. -->
### Steps to Reproduce
<!-- Steps to reproduce the problem. The more detailed and concrete you can be, the better. Logs are welcome if
appropriate/helpful. -->
1. Defined a provider X
2. Defined a procedure Y,
3. Provided input of spec to the procedure
`{"input": {"x": 10, "y": 20}}`
### Impact
<!-- [optional] If you tried anything to work around or recover from the bug, or if the bug caused additional problems, discuss it here. Be as concrete, specific and detailed as possible. For example, "I spent an hour trying to restart the encabulator to retrieve my data after the crash" clearly illustrates the scale and scope of the problem. Whereas, "This is a huge problem and should be fixed ASAP" is likely to be ignored because it doesn't provide any detail about WHY the problem is huge. -->
### Additional Details
<!-- [optional] Any other context that might be helpful. -->
<!----- PLEASE LEAVE THE FOLLOWING TEXT IN PLACE ----->
<hr>
<em>Readers: If you are also experiencing this bug, please vote for it by giving the ORIGINAL POST a thumbs-up using the :smiley: button. You are welcome to leave comments and discuss the issue if you have more details to add, but "Me too!" comments are not counted by the voting system.</em>
| 43.96 | 503 | 0.72293 | eng_Latn | 0.997568 |
549b839e8bcd013437395098396f15df34434593 | 15,414 | md | Markdown | docs/docs/developers/templates.md | usablica/kissui-doc42 | 5cdf3fe5d347443797cc188950606176e70697c1 | [
"MIT"
] | 27 | 2016-10-18T22:04:08.000Z | 2020-06-01T17:51:48.000Z | docs/docs/developers/templates.md | usablica/kissui-doc42 | 5cdf3fe5d347443797cc188950606176e70697c1 | [
"MIT"
] | null | null | null | docs/docs/developers/templates.md | usablica/kissui-doc42 | 5cdf3fe5d347443797cc188950606176e70697c1 | [
"MIT"
] | 8 | 2016-10-19T23:29:18.000Z | 2021-03-28T02:45:50.000Z | ---
layout: doc
weight: 1
title: Templates
categories: developers
permalink: /developers/templates/
---
Jekyll uses the [Liquid](https://shopify.github.io/liquid/) templating language to
process templates. All of the standard Liquid [tags](https://shopify.github.io/liquid/tags/) and
[filters](https://shopify.github.io/liquid/filters/) are
supported. Jekyll even adds a few handy filters and tags of its own to make
common tasks easier.
#### Filters
<div class="mobile-side-scroller">
<table>
<thead>
<tr>
<th>Description</th>
<th><span class="filter">Filter</span> and <span class="output">Output</span></th>
</tr>
</thead>
<tbody>
<tr>
<td>
<p class="name"><strong>Relative URL</strong></p>
<p>Prepend the <code>baseurl</code> value to the input. Useful if your site is hosted at a subpath rather than the root of the domain.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ "/assets/style.css" | relative_url }}{% endraw %}</code>
</p>
<p>
<code class="output">/my-baseurl/assets/style.css</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Absolute URL</strong></p>
<p>Prepend the <code>url</code> and <code>baseurl</code> value to the input.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ "/assets/style.css" | absolute_url }}{% endraw %}</code>
</p>
<p>
<code class="output">http://example.com/my-baseurl/assets/style.css</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Date to XML Schema</strong></p>
<p>Convert a Date into XML Schema (ISO 8601) format.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.time | date_to_xmlschema }}{% endraw %}</code>
</p>
<p>
<code class="output">2008-11-07T13:07:54-08:00</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Date to RFC-822 Format</strong></p>
<p>Convert a Date into the RFC-822 format used for RSS feeds.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.time | date_to_rfc822 }}{% endraw %}</code>
</p>
<p>
<code class="output">Mon, 07 Nov 2008 13:07:54 -0800</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Date to String</strong></p>
<p>Convert a date to short format.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.time | date_to_string }}{% endraw %}</code>
</p>
<p>
<code class="output">07 Nov 2008</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Date to Long String</strong></p>
<p>Format a date to long format.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.time | date_to_long_string }}{% endraw %}</code>
</p>
<p>
<code class="output">07 November 2008</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Where</strong></p>
<p>Select all the objects in an array where the key has the given value.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.members | where:"graduation_year","2014" }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Where Expression</strong></p>
<p>Select all the objects in an array where the expression is true. Jekyll v3.2.0 & later.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.members | where_exp:"item",
"item.graduation_year == 2014" }}{% endraw %}</code>
<code class="filter">{% raw %}{{ site.members | where_exp:"item",
"item.graduation_year < 2014" }}{% endraw %}</code>
<code class="filter">{% raw %}{{ site.members | where_exp:"item",
"item.projects contains 'foo'" }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Group By</strong></p>
<p>Group an array's items by a given property.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.members | group_by:"graduation_year" }}{% endraw %}</code>
</p>
<p>
<code class="output">[{"name"=>"2013", "items"=>[...]},
{"name"=>"2014", "items"=>[...]}]</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>XML Escape</strong></p>
<p>Escape some text for use in XML.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ page.content | xml_escape }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>CGI Escape</strong></p>
<p>
CGI escape a string for use in a URL. Replaces any special characters
with appropriate %XX replacements.
</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ "foo,bar;baz?" | cgi_escape }}{% endraw %}</code>
</p>
<p>
<code class="output">foo%2Cbar%3Bbaz%3F</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>URI Escape</strong></p>
<p>
URI escape a string.
</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ "foo, bar \baz?" | uri_escape }}{% endraw %}</code>
</p>
<p>
<code class="output">foo,%20bar%20%5Cbaz?</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Number of Words</strong></p>
<p>Count the number of words in some text.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ page.content | number_of_words }}{% endraw %}</code>
</p>
<p>
<code class="output">1337</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Array to Sentence</strong></p>
<p>Convert an array into a sentence. Useful for listing tags.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ page.tags | array_to_sentence_string }}{% endraw %}</code>
</p>
<p>
<code class="output">foo, bar, and baz</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Markdownify</strong></p>
<p>Convert a Markdown-formatted string into HTML.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ page.excerpt | markdownify }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Smartify</strong></p>
<p>Convert "quotes" into “smart quotes.”</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ page.title | smartify }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Converting Sass/SCSS</strong></p>
<p>Convert a Sass- or SCSS-formatted string into CSS.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ some_scss | scssify }}{% endraw %}</code>
<code class="filter">{% raw %}{{ some_sass | sassify }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Slugify</strong></p>
<p>Convert a string into a lowercase URL "slug". See below for options.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ "The _config.yml file" | slugify }}{% endraw %}</code>
</p>
<p>
<code class="output">the-config-yml-file</code>
</p>
<p>
<code class="filter">{% raw %}{{ "The _config.yml file" | slugify: 'pretty' }}{% endraw %}</code>
</p>
<p>
<code class="output">the-_config.yml-file</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Data To JSON</strong></p>
<p>Convert Hash or Array to JSON.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.data.projects | jsonify }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Normalize Whitespace</strong></p>
<p>Replace any occurrence of whitespace with a single space.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ "a \n b" | normalize_whitespace }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Sort</strong></p>
<p>Sort an array. Optional arguments for hashes: 1. property name 2. nils order (<em>first</em> or <em>last</em>).</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ page.tags | sort }}{% endraw %}</code>
</p>
<p>
<code class="filter">{% raw %}{{ site.posts | sort: 'author' }}{% endraw %}</code>
</p>
<p>
<code class="filter">{% raw %}{{ site.pages | sort: 'title', 'last' }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Sample</strong></p>
<p>Pick a random value from an array. Optional: pick multiple values.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ site.pages | sample }}{% endraw %}</code>
</p>
<p>
<code class="filter">{% raw %}{{ site.pages | sample:2 }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>To Integer</strong></p>
<p>Convert a string or boolean to integer.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ some_var | to_integer }}{% endraw %}</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Array Filters</strong></p>
<p>Push, pop, shift, and unshift elements from an Array.</p>
<p>These are <strong>NON-DESTRUCTIVE</strong>, i.e. they do not mutate the array, but rather make a copy and mutate that.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ page.tags | push: 'Spokane' }}{% endraw %}</code>
</p>
<p>
<code class="output">['Seattle', 'Tacoma', 'Spokane']</code>
</p>
<p>
<code class="filter">{% raw %}{{ page.tags | pop }}{% endraw %}</code>
</p>
<p>
<code class="output">['Seattle']</code>
</p>
<p>
<code class="filter">{% raw %}{{ page.tags | shift }}{% endraw %}</code>
</p>
<p>
<code class="output">['Tacoma']</code>
</p>
<p>
<code class="filter">{% raw %}{{ page.tags | unshift: "Olympia" }}{% endraw %}</code>
</p>
<p>
<code class="output">['Olympia', 'Seattle', 'Tacoma']</code>
</p>
</td>
</tr>
<tr>
<td>
<p class="name"><strong>Inspect</strong></p>
<p>Convert an object into its String representation for debugging.</p>
</td>
<td class="align-center">
<p>
<code class="filter">{% raw %}{{ some_var | inspect }}{% endraw %}</code>
</p>
</td>
</tr>
</tbody>
</table>
</div>
#### Tags
##### Includes
If you have small page fragments that you wish to include in multiple places on
your site, you can use the `include` tag.
```liquid
{% raw %}{% include footer.html %}{% endraw %}
```
Jekyll expects all include files to be placed in an `_includes` directory at the
root of your source directory. This will embed the contents of
`<source>/_includes/footer.html` into the calling file.
You can also pass parameters to an include. Omit the quotation marks to send a variable's value. Liquid curly brackets should not be used here:
```liquid
{% raw %}{% include footer.html param="value" variable-param=page.variable %}{% endraw %}
```
These parameters are available via Liquid in the include:
```liquid
{% raw %}{{ include.param }}{% endraw %}
```
##### Including files relative to another file
You can also choose to include file fragments relative to the current file:
```liquid
{% raw %}{% include_relative somedir/footer.html %}{% endraw %}
```
You won't need to place your included content within the `_includes` directory. Instead,
the inclusion is specifically relative to the file where the tag is being used. For example,
if `_posts/2014-09-03-my-file.markdown` uses the `include_relative` tag, the included file
must be within the `_posts` directory, or one of its subdirectories. You cannot include
files in other locations.
All the other capabilities of the `include` tag are available to the `include_relative` tag,
such as using variables.
### Code snippet highlighting
Doc42 has a builtin syntaxt highlighting using Highlight.js.
<p>Code styling is kept basic – just wrap anything in a <code><code></code> and it will appear like <code>this</code>. For blocks of code, wrap a <code><code></code> with a <code><pre></code>.</p>
<div class="docs-example">
<pre>
<code>.some-class {
background-color: red;
}
</code>
</pre>
</div>
<pre class="code-example">
<code class="language-html"><pre><code>.some-class {
background-color: red;
}</code></pre>
<!-- Remember every whitespace and break will be preserved in a <pre>, including indentation in your code -->
</code>
</pre>
### Link
If you want to include a link to a collection's document, a post, a page
or a file the `link` tag will generate the correct permalink URL for the path
you specify.
You must include the file extension when using the `link` tag.
```liquid
{% raw %}
{% link _collection/name-of-document.md %}
{% link _posts/2016-07-26-name-of-post.md %}
{% link news/index.html %}
{% link /assets/files/doc.pdf %}
{% endraw %}
```
You can also use this tag to create a link in Markdown as follows:
```liquid
{% raw %}
[Link to a document]({% link _collection/name-of-document.md %})
[Link to a post]({% link _posts/2016-07-26-name-of-post.md %})
[Link to a page]({% link news/index.html %})
[Link to a file]({% link /assets/files/doc.pdf %})
{% endraw %}
```
### Gist
Use the `gist` tag to easily embed a GitHub Gist onto your site. This works
with public or secret gists:
```liquid
{% raw %}
{% gist parkr/931c1c8d465a04042403 %}
{% endraw %}
```
You may also optionally specify the filename in the gist to display:
```liquid
{% raw %}
{% gist parkr/931c1c8d465a04042403 jekyll-private-gist.markdown %}
{% endraw %}
```
To use the `gist` tag, you'll need to add the
[jekyll-gist](https://github.com/jekyll/jekyll-gist) gem to your project.
| 30.282908 | 214 | 0.53646 | eng_Latn | 0.793692 |
549de6ab8b13305263364eb0af17c2b502c4b55b | 455 | md | Markdown | docs/API.md | mrtnbroder/react-router-route-reducers | 52632e8aae32fcb997188a775f12bc1bf3af8823 | [
"MIT"
] | 8 | 2016-03-30T17:04:19.000Z | 2017-03-21T21:54:24.000Z | docs/API.md | mrtnbroder/react-router-route-reducers | 52632e8aae32fcb997188a775f12bc1bf3af8823 | [
"MIT"
] | null | null | null | docs/API.md | mrtnbroder/react-router-route-reducers | 52632e8aae32fcb997188a775f12bc1bf3af8823 | [
"MIT"
] | null | null | null | ## API
### `<RoutesReducer>`
Primary component of react-router-route-reducers. It combines your routes-reducers into a single object based on your route structure.
#### Props
##### `store` (required)
The Redux store instance.
##### `reducers`
All other global reducers.
### `loadStateOnServer(props, callback)`
Creates the initalState for server-side rendering.
`callback` is being passed the initalState that you need to bind into your markup.
| 20.681818 | 134 | 0.738462 | eng_Latn | 0.986193 |
549e3eff9f042e6bad3d53fcb2e9764193ad9e97 | 12,649 | md | Markdown | articles/storage/files/storage-how-to-use-files-storage-explorer.md | Zwoch/azure-docs.de-de | c76b1dfefc2541ca6d661c9eaca428b42b34ebc8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/files/storage-how-to-use-files-storage-explorer.md | Zwoch/azure-docs.de-de | c76b1dfefc2541ca6d661c9eaca428b42b34ebc8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/storage/files/storage-how-to-use-files-storage-explorer.md | Zwoch/azure-docs.de-de | c76b1dfefc2541ca6d661c9eaca428b42b34ebc8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Verwalten von Azure-Dateifreigaben mit Azure Storage-Explorer
description: Es wird beschrieben, wie Sie Azure Storage-Explorer zum Verwalten von Azure Files verwenden.
services: storage
documentationcenter: ''
author: wmgries
manager: jeconnoc
editor: ''
ms.assetid: ''
ms.service: storage
ms.workload: storage
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: get-started-article
ms.date: 02/27/2018
ms.author: wgries
ms.openlocfilehash: 0c16d3b0ef0b178f99eaafecd74eabb00cca5af9
ms.sourcegitcommit: c3d53d8901622f93efcd13a31863161019325216
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 03/29/2018
---
# <a name="managing-azure-file-shares-with-azure-storage-explorer"></a>Verwalten von Azure-Dateifreigaben mit Azure Storage-Explorer
[Azure Files](storage-files-introduction.md) ist das benutzerfreundliche Clouddateisystem von Microsoft. In dieser Anleitung werden die Grundlagen der Arbeit mit Azure-Dateifreigaben mit [Azure Storage-Explorer](https://azure.microsoft.com/features/storage-explorer/) Schritt für Schritt beschrieben. Azure Storage-Explorer ist ein beliebtes Clienttool, das für Windows, macOS und Linux zum Verwalten von Azure-Dateifreigaben und anderen Speicherressourcen verfügbar ist.
Für diese Schnellstartanleitung muss Azure Storage-Explorer installiert sein. Falls Sie die Installation durchführen müssen, können Sie die Anwendung auf der Seite für [Azure Storage-Explorer](https://azure.microsoft.com/features/storage-explorer/) herunterladen.
In diesem Artikel wird Folgendes behandelt:
> [!div class="checklist"]
> * Erstellen einer Ressourcengruppe und eines Speicherkontos
> * Erstellen einer Azure-Dateifreigabe
> * Erstellen eines Verzeichnisses
> * Hochladen einer Datei
> * Herunterladen einer Datei
> * Erstellen und Verwenden einer Freigabemomentaufnahme
Wenn Sie kein Azure-Abonnement besitzen, können Sie ein [kostenloses Konto](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) erstellen, bevor Sie beginnen.
## <a name="create-a-storage-account"></a>Speicherkonto erstellen
Mit dem Azure Storage-Explorer können keine neuen Ressourcen erstellt werden. Erstellen Sie das Speicherkonto für diese Demonstration daher mit dem [Azure-Portal](https://portal.azure.com/).
[!INCLUDE [storage-files-create-storage-account-portal](../../../includes/storage-files-create-storage-account-portal.md)]
## <a name="connecting-azure-storage-explorer-to-azure-resources"></a>Herstellen einer Verbindung für Azure Storage-Explorer mit Azure-Ressourcen
Nach dem ersten Start wird das Fenster **Microsoft Azure Storage-Explorer – Verbinden** angezeigt. Es gibt verschiedene Möglichkeiten, wie Sie mit Azure Storage-Explorer eine Verbindung mit Speicherkonten herstellen können:
- **Anmeldung über Ihr Azure-Konto**: Sie können sich mit Ihren Benutzeranmeldeinformationen für Ihre Organisation oder für Ihr Microsoft-Konto anmelden.
- **Herstellen einer Verbindung mit einem bestimmten Speicherkonto per Verbindungszeichenfolge oder SAS-Token**: Eine Verbindungszeichenfolge ist eine spezielle Zeichenfolge, die den Speicherkontonamen und den Speicherkontoschlüssel bzw. das SAS-Token enthält. Hiermit kann Azure Storage-Explorer direkt auf das Speicherkonto zugreifen (im Gegensatz zum Anzeigen aller Speicherkonten eines Azure-Kontos). Weitere Informationen zu Verbindungszeichenfolgen finden Sie unter [Konfigurieren von Azure Storage-Verbindungszeichenfolgen](../common/storage-configure-connection-string.md?toc=%2fazure%2fstorage%2ffiles%2ftoc.json).
- **Herstellen einer Verbindung mit einem bestimmten Speicherkonto über einen Speicherkontonamen und -schlüssel**: Verwenden Sie den Speicherkontonamen und -schlüssel Ihres Speicherkontos, um die Verbindung mit Azure-Speicher herzustellen.
Melden Sie sich für diese Schnellstartanleitung mit Ihrem Azure-Konto an. Wählen Sie **Azure-Konto hinzufügen**, und klicken Sie auf **Anmelden**. Befolgen Sie die Anweisungen auf dem Bildschirm, um sich an Ihrem Azure-Konto anzumelden.
### <a name="create-a-file-share"></a>Erstellen einer Dateifreigabe
Gehen Sie wie folgt vor, um Ihre erste Azure-Dateifreigabe im Speicherkonto *storageacct<random number>* zu erstellen:
1. Erweitern Sie das Speicherkonto, das Sie erstellt haben.
2. Klicken Sie mit der rechten Maustaste auf **Dateifreigabe**, und wählen Sie **Dateifreigabe erstellen**.
3. Geben Sie für die Dateifreigabe *myshare* ein, und drücken Sie die **EINGABETASTE**.
> [!Important]
> Freigabenamen dürfen nur Kleinbuchstaben, Zahlen und einzelne Bindestriche enthalten und dürfen nicht mit einem Bindestrich beginnen. Ausführliche Informationen zur Benennung von Dateifreigaben und Dateien finden Sie unter [Benennen und Referenzieren von Freigaben, Verzeichnissen, Dateien und Metadaten](https://docs.microsoft.com/rest/api/storageservices/Naming-and-Referencing-Shares--Directories--Files--and-Metadata).
Nachdem die Dateifreigabe erstellt wurde, wird im rechten Bereich eine Registerkarte für Ihre Dateifreigabe geöffnet.
## <a name="manipulating-the-contents-of-the-azure-file-share"></a>Bearbeiten des Inhalts der Azure-Dateifreigabe
Nachdem Sie nun eine Azure-Dateifreigabe erstellt haben, können Sie die Dateifreigabe mit SMB unter [Windows](storage-how-to-use-files-windows.md), [Linux](storage-how-to-use-files-linux.md) oder [macOS](storage-how-to-use-files-mac.md) bereitstellen. Alternativ hierzu können Sie Ihre Azure-Dateifreigabe mit dem Azure-Portal ändern. Alle Anforderungen über das Azure-Portal werden mit der Datei-REST-API durchgeführt, sodass Sie Dateien und Verzeichnisse ohne SMB-Zugriff erstellen, ändern und löschen können.
### <a name="create-a-directory"></a>Erstellen eines Verzeichnisses
Mit dem Hinzufügen eines Verzeichnisses wird eine hierarchische Struktur zum Verwalten Ihrer Dateifreigabe bereitgestellt. Sie können mehrere Ebenen erstellen. Allerdings müssen Sie sicherstellen, dass alle übergeordneten Verzeichnisse vorhanden sind, bevor Sie ein Unterverzeichnis erstellen. Für den Pfad „myDirectory/mySubDirectory“ müssen Sie beispielsweise zuerst das Verzeichnis *myDirectory* und dann das Verzeichnis *mySubDirectory* erstellen.
1. Klicken Sie auf der Registerkarte für die Dateifreigabe im obersten Menü auf die Schaltfläche **+ Neuer Ordner**. Die Seite **Neues Verzeichnis erstellen** wird geöffnet.
2. Geben Sie als Namen *myDirectory* ein, und klicken Sie anschließend auf **OK**.
Das Verzeichnis *myDirectory* wird auf der Registerkarte für die Dateifreigabe *myshare* aufgeführt.
### <a name="upload-a-file"></a>Hochladen einer Datei
Laden Sie eine Datei von Ihrem lokalen Computer in das neue Verzeichnis Ihrer Dateifreigabe hoch. Sie können einen ganzen Ordner oder nur eine einzelne Datei hochladen.
1. Wählen Sie im Menü am oberen Rand die Option **Hochladen**. Sie haben dann die Möglichkeit, einen Ordner oder eine Datei hochzuladen.
2. Wählen Sie **Datei hochladen**, und wählen Sie dann eine Datei Ihres lokalen Computers aus, die hochgeladen werden soll.
3. Geben Sie unter **Upload to a directory** (In ein Verzeichnis hochladen) den Namen *myDirectory* ein, und klicken Sie anschließend auf **Hochladen**.
Nach Abschluss des Vorgangs sollte die Datei in der Liste auf der Seite **myDirectory** angezeigt werden.
### <a name="download-a-file"></a>Herunterladen einer Datei
Sie können eine Kopie einer Datei in Ihrer Dateifreigabe herunterladen, indem Sie mit der rechten Maustaste auf die Datei klicken und **Herunterladen** wählen. Wählen Sie aus, wo Sie die Datei auf Ihrem lokalen Computer ablegen möchten, und klicken Sie anschließend auf **Speichern**.
Der Status des Downloads wird unten im Fenster im Bereich **Aktivitäten** angezeigt.
## <a name="create-and-modify-share-snapshots"></a>Erstellen und Ändern von Freigabemomentaufnahmen
Mit einer Momentaufnahme wird eine Kopie einer Azure-Dateifreigabe für einen bestimmten Zeitpunkt erstellt. Momentaufnahmen von Dateifreigaben ähneln anderen Technologien, mit denen Sie unter Umständen bereits vertraut sind:
- [Volumeschattenkopie-Dienst (VSS)](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee923636) für Windows-Dateisysteme wie NTFS und ReFS.
- Momentaufnahmen vom Typ [Logical Volume Manager (LVM)](https://en.wikipedia.org/wiki/Logical_Volume_Manager_(Linux)#Basic_functionality) für Linux-Systeme
- Momentaufnahmen vom Typ [Apple File System (APFS)](https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/Features/Features.html) für macOS
Gehen Sie wie folgt vor, um eine Freigabemomentaufnahme zu erstellen:
1. Öffnen Sie die Registerkarte für die Dateifreigabe *myshare*.
2. Klicken Sie im Menü am oberen Rand der Registerkarte auf **Momentaufnahme erstellen**. (Diese Option befindet sich ggf. hinter der Option **... Mehr**, je nach den Fensterabmessungen von Azure Storage-Explorer.)
### <a name="list-and-browse-share-snapshots"></a>Auflisten und Durchsuchen von Freigabemomentaufnahmen
Nachdem die Momentaufnahme erstellt wurde, können Sie auf **View Snapshots for File Share** (Momentaufnahmen für Dateifreigabe anzeigen) klicken, um die Momentaufnahmen für die Freigabe aufzulisten. (Diese Option befindet sich ggf. hinter der Option **... Mehr**, je nach den Fensterabmessungen von Azure Storage-Explorer.) Doppelklicken Sie auf eine Freigabemomentaufnahme, um sie zu durchsuchen.
### <a name="restore-from-a-share-snapshot"></a>Wiederherstellen von einer Freigabemomentaufnahme
Wir müssen zuerst eine Datei aus der aktiven Azure-Dateifreigabe löschen, um demonstrieren zu können, wie eine Datei aus einer Freigabemomentaufnahme wiederhergestellt wird. Navigieren Sie zum Ordner *myDirectory*, klicken Sie mit der rechten Maustaste auf die hochgeladene Datei, und klicken Sie dann auf **Löschen**. Stellen Sie diese Datei anschließend aus der Freigabemomentaufnahme wieder her:
1. Klicken Sie auf **View Snapshots for File Share** (Momentaufnahmen für Dateifreigabe anzeigen). (Diese Option befindet sich ggf. hinter der Option **... Mehr**, je nach den Fensterabmessungen von Azure Storage-Explorer.)
2. Wählen Sie in der Liste eine Freigabemomentaufnahme aus, und doppelklicken Sie darauf, um dorthin zu navigieren.
3. Navigieren Sie durch die Momentaufnahme, bis Sie die gelöschte Datei gefunden haben. Wählen Sie sie aus, und klicken Sie dann auf **Momentaufnahme wiederherstellen**. (Diese Option befindet sich ggf. hinter der Option **... Mehr**, je nach den Fensterabmessungen von Azure Storage-Explorer.) Es wird eine Warnung angezeigt, dass durch das Wiederherstellen der Datei der Inhalt der Dateifreigabe überschrieben wird und dass der Vorgang nicht rückgängig gemacht werden kann. Klicken Sie auf **OK**.
4. Die Datei sollte sich jetzt an ihrem ursprünglichen Ort unter der aktiven Azure-Dateifreigabe befinden.
### <a name="delete-a-share-snapshot"></a>Löschen einer Freigabemomentaufnahme
[Navigieren Sie zur Liste mit den Freigabemomentaufnahmen](#list-and-browse-share-snapshots), um eine Freigabemomentaufnahme zu löschen. Klicken Sie mit der rechten Maustaste auf die Freigabemomentaufnahme, die Sie löschen möchten, und wählen Sie „Löschen“.
## <a name="clean-up-resources"></a>Bereinigen von Ressourcen
Mit Azure Storage-Explorer können keine Ressourcen entfernt werden. Sie können die Bereinigung für diese Schnellstartanleitung über das [Azure-Portal](https://portal.azure.com/) durchführen.
[!INCLUDE [storage-files-clean-up-portal](../../../includes/storage-files-clean-up-portal.md)]
## <a name="next-steps"></a>Nächste Schritte
- [Verwalten von Dateifreigaben mit dem Azure-Portal](storage-how-to-use-files-portal.md)
- [Verwalten von Dateifreigaben mit Azure PowerShell](storage-how-to-use-files-powershell.md)
- [Verwalten von Dateifreigaben mit der Azure CLI](storage-how-to-use-files-cli.md)
- [Planung für eine Azure Files-Bereitstellung](storage-files-planning.md) | 93.007353 | 623 | 0.80457 | deu_Latn | 0.993981 |
549e64623217e3e0adf37687dba9d3825a114327 | 1,191 | md | Markdown | _posts/2016-02-02-faculty-vacancy-in-allahabad-university.md | anchalrani/getopportunity | f45b2ea40ac4c52167181454e966fa9e2d7ee8a2 | [
"MIT"
] | null | null | null | _posts/2016-02-02-faculty-vacancy-in-allahabad-university.md | anchalrani/getopportunity | f45b2ea40ac4c52167181454e966fa9e2d7ee8a2 | [
"MIT"
] | null | null | null | _posts/2016-02-02-faculty-vacancy-in-allahabad-university.md | anchalrani/getopportunity | f45b2ea40ac4c52167181454e966fa9e2d7ee8a2 | [
"MIT"
] | null | null | null | ---
layout: post
title: Faculty vacancy in Allahabad University last date 10th March-2016
date: 2016-02-02 12:27
comments: true
tags: Faculty University UP
archive: false
---
Applications are invited for the Posts of Assistant Professor, Associate Professor, Professor in various Departments of Faculties of Arts, Commerce, Law, Science and other independent Institutes / Centres of the University of Allahabad :
- Professor : 49 posts, Pay Scale : Rs. 37400-67000 with AGP of Rs. 10000/-
- Associate Professor : 84 posts, Pay Scale : Rs. 37400-67000 with AGP of Rs. 9000/-
- Assistant Professor : 157 posts, Pay Scale : 15000-39100 with AGP of Rs. 6000/-
Application Fee : DD of Rs. 500/- (Rs. 200/- for SC/ST candidates) from any nationalized bank
drawn in favour of the Finance Officer, University of Allahabad and payable at Allahabad.
**How to Apply** : Application in the prescribed format completed in all respect along with relevant
documents, demand draft etc. as required must reach the Registrar,
University of Allahabad, Allahabad - 211002 (U.P.) on or before 10/03/2016.
Please visit <http://www.allduniv.ac.in> for details and application format.
| 45.807692 | 241 | 0.75063 | eng_Latn | 0.978396 |
549fc1004172d0661a5f0fb31d65cc56f3e0e936 | 2,405 | md | Markdown | _publications/2019-01-07-Jour-DRLsurgicaltraining.md | chngchinboon/chngchinboon.github.io | ac770524f37aa3489fbf176b0681d336f5434de1 | [
"MIT"
] | null | null | null | _publications/2019-01-07-Jour-DRLsurgicaltraining.md | chngchinboon/chngchinboon.github.io | ac770524f37aa3489fbf176b0681d336f5434de1 | [
"MIT"
] | null | null | null | _publications/2019-01-07-Jour-DRLsurgicaltraining.md | chngchinboon/chngchinboon.github.io | ac770524f37aa3489fbf176b0681d336f5434de1 | [
"MIT"
] | null | null | null | ---
title: "Robot-assisted training in laparoscopy using deep reinforcement learning"
collection: publications
pubtype: 'journal'
permalink: /publication/2019-01-07-Jour-DRLsurgicaltraining
excerpt: "This paper is about a new robot-assisted surgical training system which is designed to improve the practical skills of surgeons through intrapractice feedback and demonstration from both human experts and reinforcement learning (RL) agents."
date: 2019-01-07
citation: 'X Tan, CB Chng, Y Su, KB Lim, CK Chui, "Robot-Assisted Training in Laparoscopy Using Deep Reinforcement Learning", IEEE Robotics and Automation Letters 4 (2), 485-492, 2019.'
venue: 'IEEE Robotics and Automation Letters'
---
Minimally invasive surgery (MIS) is increasingly becoming a vital method of reducing surgical trauma and significantly improving postoperative recovery. However, skillful handling of surgical instruments used in MIS, especially for laparoscopy, requires a long period of training and depends highly on the experience of surgeons. This letter presents a new robot-assisted surgical training system which is designed to improve the practical skills of surgeons through intrapractice feedback and demonstration from both human experts and reinforcement learning (RL) agents. This system utilizes proximal policy optimization to learn the control policy in simulation. Subsequently, a generative adversarial imitation learning agent is trained based on both expert demonstrations and learned policies in simulation. This agent then generates demonstration policies on the robot-assisted device for trainees and produces feedback scores during practice. To further acquire surgical tools coordinates and encourage self-oriented practice, a mask region-based convolution neural network is trained to perform the semantic segmentation of surgical tools and targets. To the best of our knowledge, this system is the first robot-assisted laparoscopy training system which utilizes actual surgical tools and leverages deep reinforcement learning to provide demonstration training from both human expert perspectives and RL criterion.
[Download paper here](https://ieeexplore.ieee.org/abstract/document/8604070)
Recommended citation: X Tan, CB Chng, Y Su, KB Lim, CK Chui, "Robot-Assisted Training in Laparoscopy Using Deep Reinforcement Learning", IEEE Robotics and Automation Letters 4 (2), 485-492, 2019.
| 150.3125 | 1,423 | 0.824948 | eng_Latn | 0.995898 |
54a185de5fec01f45fe393aa2f63d88d98d6b6bd | 3,940 | md | Markdown | _posts/2021-02-24-gray-areas-2021.md | kootsoop/kootsoop.github.io | 3fa1c99a30271e3af36edcc287175ac93644093c | [
"MIT"
] | null | null | null | _posts/2021-02-24-gray-areas-2021.md | kootsoop/kootsoop.github.io | 3fa1c99a30271e3af36edcc287175ac93644093c | [
"MIT"
] | null | null | null | _posts/2021-02-24-gray-areas-2021.md | kootsoop/kootsoop.github.io | 3fa1c99a30271e3af36edcc287175ac93644093c | [
"MIT"
] | null | null | null | ---
title: 'Gray areas'
description: >-
Why shades of grey are better and worse than black and white.
date: '2021-02-24T08:21:49Z'
categories: [life skills]
keywords: [daily]
slug: /@kootsoop/gray-areas-2021
---
I was struck by the similar topic areas in two different and disparate podcasts that I listen to.
One, the [Cult of Pedagogy by Jennifer Gonzales](https://www.cultofpedagogy.com/gray-area/) entitled *The elegance of the gray area* was about how true experts tend to equivocate rather than pontificate because they are aware that they don't know everything that is to be known about a topic.
<a href="https://www.cultofpedagogy.com/gray-area/">
<img src="https://x78251kcpll2l2t9e46kf96a-wpengine.netdna-ssl.com/wp-content/uploads/2021/02/Gray-Area-Tall.png" width="125" height="150"></a>
The other, the [Hidden Brain by Shankar Vedantam](https://hiddenbrain.org/podcast/is-it-better-to-know/) episode entitled *Is it better to know* was about how **knowing** that someone is being bigoted reduces someone's happiness and, sometimes, performance in an area where their group is stereotyped as being lacking.
<a href="https://hiddenbrain.org/podcast/is-it-better-to-know/">
<img src="https://hiddenbrain.org/wp-content/uploads/2020/10/image-768x768.jpg" width="150" height="150"></a>
## The gray area
The *Cult of Pedagogy* podcast is about teaching to middle and high schoolers, however, I find it also sheds light on the teaching in colleges where I am as well. The specifics of the techniques might be different for college, but the mechanisms for teaching (and learning) don't change that much.
The episode *The elegance of the gray area* that I linked to above is about how "as more information becomes available, knowledge evolves."
This is why the gray area is sometimes the death knell for politicians. Many get derided by their political opponents as "flip-floppers" if they change their mind.
The upshot of the gray area is that we should always be open to new information, even if it deconstructs our current way of thinking.
## Better to know
The *Hidden Brain* episode is similar, and I was particularly struck by part of it that referenced Shankar's upcoming book [*Useful Delusions*<sup>associate link!</sup>](https://amzn.to/3utCuij). Shankar refers to his recently deceased father whose happiness depended, in part, on his unshakable belief that his wife (Shankar's mother) was always right.
Shankar's mother is, undoubtedly, a good person. But infallible she was not.
The *Better to know* episode looked at the happiness or achieved outcomes of people facing bigotry, and whether it was better for them to know it was bigotry or not.
The example given was of an African American who, as a youngster, was confronted by direct racism, being called all sorts of derogatory names, and treated differently from his white peers. As a young adult, trying to fit into the postgraduate academic society, he wondered whether his African American-ness and associated background would ostracize him from his peers there.
The difference between the younger and the older situation is that the younger one was all external. Things were clear. For the older situation, it *could* have been all in his head, even if there was racism involved. And that internal-external crossover impacted his performance because of the uncertainty.
## Dichotomy
That seems to yield a dichotomy: the first podcast suggests that *not knowing* (about knowledge) and being open to new knowledge is the best approach. The second podcast suggests that *not knowing* (about bigotry) impacts us negatively.
I wonder if this is related to the idea that [religious people often describe themselves as happier.](https://www.pewresearch.org/fact-tank/2019/01/31/are-religious-people-happier-healthier-our-new-global-study-explores-this-question/)? Being able to have faith reduces, for some, the level of *not knowing*.
| 72.962963 | 375 | 0.779695 | eng_Latn | 0.999631 |
54a21a7fc1f27b4793f7af32f97782d068ee502c | 1,666 | md | Markdown | README.md | timlai4/Anan_PAR- | 129daa0444630341002d8b8278f3f39049e3ea86 | [
"MIT"
] | null | null | null | README.md | timlai4/Anan_PAR- | 129daa0444630341002d8b8278f3f39049e3ea86 | [
"MIT"
] | null | null | null | README.md | timlai4/Anan_PAR- | 129daa0444630341002d8b8278f3f39049e3ea86 | [
"MIT"
] | null | null | null | # Anan_PAR
## Owl Monkey (*Aotus nancymaae*) Overview
<img src="img/owlmonkey.jpg" alt="owl monkey" width="400"/>
*A. nancymaae* is a medically relevant primate, as it is infected by *Plasmodium falciparum*.
Reference genome: **Anan_2.0**
- total length: 2861.68 Mb
- # of scaffolds: 28,922
- # of contigs: 112,851
- N50: 126,456
- L50: 5,745
## Data Retrieval
The reference genome annotation and assembly were downloaded from Ensembl.
```{bash}
wget https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/000/952/055/GCF_000952055.2_Anan_2.0/GCF_000952055.2_Anan_2.0_genomic.fna.gz
wget https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/000/952/055/GCF_000952055.2_Anan_2.0/GCF_000952055.2_Anan_2.0_genomic.gff.gz
```
Two samples, one from each sex, were obtained and QC'd
```{bash}
singularity exec -eCB `pwd` -H `pwd` zent_tools_software_v0.4.sif Rscript fetch_data.R
```
The alignment is performed with [bwa-mem2](https://github.com/bwa-mem2/bwa-mem2).
We can run this in our do_align.sh script.
## BLASTing against human X
To run BLAST against the human X chromosome, we used the following command:
```{bash}
makeblastdb -in NC_000023.11.fasta -dbtype nucl -parse_seqids -out blastdb/human_x
blastn -db blastdb/human_x -query GCF_000952055.2_Anan_2.0_genomic.fna -out blast.out -evalue 1e-5 -num_threads 12
```
With the BLAST, we consistently exceeded requested walltime and vmem. We tried to parse the reference .fasta file to remove sequences < 10 Mb.
```{bash}
awk -v n=10000 '/^>/{ if(l>n) print b;b=$0;l=0;next } {l+=length;b=b ORS $0}END{if(l>n) print b }' GCF_000952055.2_Anan_2.0_genomic.fna > GCF_000952055.2_Anan_2.0_genomic.parsed10K.fna
``` | 37.863636 | 184 | 0.743097 | eng_Latn | 0.514787 |
54a5b60b77a8566bdb6cb4812adf05ef880f9297 | 352 | md | Markdown | README.md | cybercongress/cyb-parity | 6247f2eda9e54b83078b687381af9e093c749337 | [
"MIT"
] | 2 | 2021-08-03T17:38:08.000Z | 2021-08-03T17:55:33.000Z | README.md | asadovka/cyb-parity | 6247f2eda9e54b83078b687381af9e093c749337 | [
"MIT"
] | 17 | 2018-10-19T13:57:54.000Z | 2018-11-05T13:14:32.000Z | README.md | cybercongress/cyb-parity | 6247f2eda9e54b83078b687381af9e093c749337 | [
"MIT"
] | null | null | null | ## This is our experimental repo. We've forked parity ui, transformed, upgraded it and even made couple of [releases](https://github.com/cybercongress/cyb-parity/releases)!
## But now we face too much problems with it. So we decided to return to our [first cyb repo](https://github.com/cybercongress/cyb) and write a new web3 browser from a scratch.
| 70.4 | 176 | 0.764205 | eng_Latn | 0.995169 |
54a5cf4db1064231fc08127238d999988cf4350c | 618 | md | Markdown | readme.md | adevecchi/laravel-webservice-soap-correios-cep | a66644289a0c86b3562b8f70d1ca5e4ea44d9dd8 | [
"MIT"
] | null | null | null | readme.md | adevecchi/laravel-webservice-soap-correios-cep | a66644289a0c86b3562b8f70d1ca5e4ea44d9dd8 | [
"MIT"
] | 1 | 2020-05-29T01:45:45.000Z | 2020-05-29T01:45:45.000Z | readme.md | adevecchi/laravel-webservice-soap-correios-cep | a66644289a0c86b3562b8f70d1ca5e4ea44d9dd8 | [
"MIT"
] | null | null | null | Cliente Web Service SOAP dos Correios (Consulta CEP)
====================================================
### Descrição:
Cliente em PHP com framework Laravel (v5.8) para consumir o Web Service SOAP dos Correios, consultando o CEP e retornando o Endereço.
https://apps.correios.com.br/SigepMasterJPA/AtendeClienteService/AtendeCliente?wsdl
| 47.538462 | 136 | 0.737864 | por_Latn | 0.530178 |
54a62cc1b520f969801991edd10ccc8950eaf94e | 1,146 | md | Markdown | Readme.md | typefaces/source-sans | 25b49a68e1ecb0a2f5ca0c558f9e46e245ff95de | [
"MIT"
] | 1 | 2015-07-14T05:12:44.000Z | 2015-07-14T05:12:44.000Z | Readme.md | typefaces/source-sans | 25b49a68e1ecb0a2f5ca0c558f9e46e245ff95de | [
"MIT"
] | null | null | null | Readme.md | typefaces/source-sans | 25b49a68e1ecb0a2f5ca0c558f9e46e245ff95de | [
"MIT"
] | null | null | null | # source-sans
The [Source Sans](https://typekit.com/fonts/source-sans-pro) typeface.
## Installation
$ component install typefaces/source-sans
## Weights
* [Extra-Light](https://github.com/typefaces/source-sans-extra-light) `200`
* [Extra-Light Italic](https://github.com/typefaces/source-sans-extra-light-italic) `200 italic`
* [Light](https://github.com/typefaces/source-sans-light) `300`
* [Light Italic](https://github.com/typefaces/source-sans-light-italic) `300 italic`
* [Regular](https://github.com/typefaces/source-sans-regular) `400`
* [Regular Italic](https://github.com/typefaces/source-sans-regular-italic) `400 italic`
* [Semibold](https://github.com/typefaces/source-sans-semibold) `600`
* [Semibold Italic](https://github.com/typefaces/source-sans-semibold-italic) `600 italic`
* [Bold](https://github.com/typefaces/source-sans-bold) `700`
* [Bold Italic](https://github.com/typefaces/source-sans-bold-italic) `700 italic`
* [Black](https://github.com/typefaces/source-sans-black) `900`
* [Black Italic](https://github.com/typefaces/source-sans-black-italic) `900 italic`
## License
MIT
| 42.444444 | 98 | 0.719023 | yue_Hant | 0.486233 |
54a6bed957dca398386a58b2ea737de1fa6688b4 | 93 | md | Markdown | README.md | chr1swallace/imd-basis | 9661a702281706ba650fff0a889a2eac94dcd564 | [
"Apache-2.0"
] | 3 | 2020-01-24T19:13:45.000Z | 2020-05-18T12:47:31.000Z | README.md | chr1swallace/imd-basis | 9661a702281706ba650fff0a889a2eac94dcd564 | [
"Apache-2.0"
] | null | null | null | README.md | chr1swallace/imd-basis | 9661a702281706ba650fff0a889a2eac94dcd564 | [
"Apache-2.0"
] | 1 | 2019-10-24T12:53:21.000Z | 2019-10-24T12:53:21.000Z | # imd-basis
Code related to immune-mediated disease (IMD) PCA basis creation and projection.
| 31 | 80 | 0.795699 | eng_Latn | 0.97797 |
54a7dcb52105b52881205b91ed53a7fb8e7136f6 | 380 | md | Markdown | content/api/ng-grid/grid.nopagingoptions.md | ressurectit/ressurectit.github.io | 09ed543e50e9b35594333afe6e98d79687849b04 | [
"MIT"
] | null | null | null | content/api/ng-grid/grid.nopagingoptions.md | ressurectit/ressurectit.github.io | 09ed543e50e9b35594333afe6e98d79687849b04 | [
"MIT"
] | null | null | null | content/api/ng-grid/grid.nopagingoptions.md | ressurectit/ressurectit.github.io | 09ed543e50e9b35594333afe6e98d79687849b04 | [
"MIT"
] | null | null | null | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [@anglr/grid](./grid.md) > [NoPagingOptions](./grid.nopagingoptions.md)
## NoPagingOptions interface
No paging options for paging
<b>Signature:</b>
```typescript
export interface NoPagingOptions<TCssClasses = any> extends PagingOptions<TCssClasses>
```
| 27.142857 | 99 | 0.705263 | eng_Latn | 0.445158 |
54a7eb18fb39de28caf91e0d3852b9ba81428c5f | 24 | md | Markdown | README.md | happymeter/keygen | 278b6f12fdfe3d53d76c284598e5f8727ed5310d | [
"Apache-2.0"
] | 1 | 2020-11-25T09:06:02.000Z | 2020-11-25T09:06:02.000Z | README.md | happymeter/keygen | 278b6f12fdfe3d53d76c284598e5f8727ed5310d | [
"Apache-2.0"
] | null | null | null | README.md | happymeter/keygen | 278b6f12fdfe3d53d76c284598e5f8727ed5310d | [
"Apache-2.0"
] | null | null | null | # keygen
Just for study
| 8 | 14 | 0.75 | eng_Latn | 0.646836 |
54a858d322c527c9d2e1ba0063656608d026ef5c | 2,176 | md | Markdown | leetcode/0692.Top-K-Frequent-Words/README.md | EcstasyGu/LeetCode-Go | cc78fdd0efd0ed3fe57a46b22bd09c8067cb764d | [
"MIT"
] | 25,030 | 2018-04-16T09:29:48.000Z | 2022-03-31T16:42:40.000Z | leetcode/0692.Top-K-Frequent-Words/README.md | yangfa4j/LeetCode-Go | 1e0a830c33bb1372111bac64f174e0a49f04dd0f | [
"MIT"
] | 130 | 2019-07-02T23:12:02.000Z | 2022-03-22T08:31:45.000Z | leetcode/0692.Top-K-Frequent-Words/README.md | yangfa4j/LeetCode-Go | 1e0a830c33bb1372111bac64f174e0a49f04dd0f | [
"MIT"
] | 4,652 | 2018-05-22T05:59:48.000Z | 2022-03-31T06:18:44.000Z | # [692. Top K Frequent Words](https://leetcode.com/problems/top-k-frequent-words/)
## 题目
Given a non-empty list of words, return the k most frequent elements.
Your answer should be sorted by frequency from highest to lowest. If two words have the same frequency, then the word with the lower alphabetical order comes first.
**Example 1:**
```
Input: ["i", "love", "leetcode", "i", "love", "coding"], k = 2
Output: ["i", "love"]
Explanation: "i" and "love" are the two most frequent words.
Note that "i" comes before "love" due to a lower alphabetical order.
```
**Example 2:**
```
Input: ["the", "day", "is", "sunny", "the", "the", "the", "sunny", "is", "is"], k = 4
Output: ["the", "is", "sunny", "day"]
Explanation: "the", "is", "sunny" and "day" are the four most frequent words,
with the number of occurrence being 4, 3, 2 and 1 respectively.
```
**Note:**
1. You may assume k is always valid, 1 ≤ k ≤ number of unique elements.
2. Input words contain only lowercase letters.
**Follow up:**
1. Try to solve it in O(n log k) time and O(n) extra space.
## 题目大意
给一非空的单词列表，返回前 *k* 个出现次数最多的单词。返回的答案应该按单词出现频率由高到低排序。如果不同的单词有相同出现频率，按字母顺序排序。
## 解题思路
- 思路很简单的题。维护一个长度为 k 的最大堆，先按照频率排，如果频率相同再按照字母顺序排。最后输出依次将优先队列里面的元素 pop 出来即可。
## 代码
```go
package leetcode
import "container/heap"
func topKFrequent(words []string, k int) []string {
m := map[string]int{}
for _, word := range words {
m[word]++
}
pq := &PQ{}
heap.Init(pq)
for w, c := range m {
heap.Push(pq, &wordCount{w, c})
if pq.Len() > k {
heap.Pop(pq)
}
}
res := make([]string, k)
for i := k - 1; i >= 0; i-- {
wc := heap.Pop(pq).(*wordCount)
res[i] = wc.word
}
return res
}
type wordCount struct {
word string
cnt int
}
type PQ []*wordCount
func (pq PQ) Len() int { return len(pq) }
func (pq PQ) Swap(i, j int) { pq[i], pq[j] = pq[j], pq[i] }
func (pq PQ) Less(i, j int) bool {
if pq[i].cnt == pq[j].cnt {
return pq[i].word > pq[j].word
}
return pq[i].cnt < pq[j].cnt
}
func (pq *PQ) Push(x interface{}) {
tmp := x.(*wordCount)
*pq = append(*pq, tmp)
}
func (pq *PQ) Pop() interface{} {
n := len(*pq)
tmp := (*pq)[n-1]
*pq = (*pq)[:n-1]
return tmp
}
``` | 22.204082 | 164 | 0.620864 | eng_Latn | 0.856978 |
54a8b0dc430a16d408e1d4f35f5f632515e7dee9 | 357 | md | Markdown | _posts/2009-06-01-39-6340.md | ashmaroli/mycad.github.io | 47fb8e82e4801dd33a3d4335a3d4a6657ec604cf | [
"MIT"
] | null | null | null | _posts/2009-06-01-39-6340.md | ashmaroli/mycad.github.io | 47fb8e82e4801dd33a3d4335a3d4a6657ec604cf | [
"MIT"
] | null | null | null | _posts/2009-06-01-39-6340.md | ashmaroli/mycad.github.io | 47fb8e82e4801dd33a3d4335a3d4a6657ec604cf | [
"MIT"
] | null | null | null | ---
layout: post
amendno: 39-6340
cadno: CAD2009-B757-03
title: 检查高压涡轮二级毂
date: 2009-06-01 00:00:00 +0800
effdate: 2009-06-17 00:00:00 +0800
tag: B757
categories: 民航西南地区管理局适航审定处
author: 汪毅飞
---
##适用范围:
本指令适用于高压涡轮二级毂（hubs）已经进行过Pratt & Whitney清洁程序（cleaning procedure）SPOP 10或SPOP 9或等效程序的普惠PW2037，PW2037（M）和PW2040涡扇发动机。这些发动机安装于但不限于Boeing 757-200和757-300飞机上。
| 22.3125 | 152 | 0.784314 | yue_Hant | 0.192358 |
54a8dbf8c77e517c5c7608c048c1464b3d4c2f39 | 3,845 | md | Markdown | _tt/feat/Voice.md | vistamou/docs | 116b9c29e4218be06bf33b158284b9c952646989 | [
"Apache-2.0"
] | 204 | 2015-01-20T16:36:39.000Z | 2022-03-28T00:49:51.000Z | _tt/feat/Voice.md | vistamou/docs | 116b9c29e4218be06bf33b158284b9c952646989 | [
"Apache-2.0"
] | 654 | 2015-01-02T17:06:29.000Z | 2022-03-31T18:23:34.000Z | _tt/feat/Voice.md | vistamou/docs | 116b9c29e4218be06bf33b158284b9c952646989 | [
"Apache-2.0"
] | 200 | 2015-01-16T22:07:02.000Z | 2022-03-25T11:35:28.000Z | ---
layout: feature
title: 'Voice'
shortdef: 'voice'
udver: '2'
---
<table class="typeindex" border="1">
<tr>
<td style="background-color:cornflowerblue;color:white"><strong>Values:</strong> </td>
<td><a href="#Cau">Cau</a></td>
<td><a href="#CauPass">CauPass</a></td>
<td><a href="#CauPassRcp">CauPassRcp</a></td>
<td><a href="#CauRcp">CauRcp</a></td>
<td><a href="#Pass">Pass</a></td>
<td><a href="#PassRcp">PassRcp</a></td>
<td><a href="#Rcp">Rcp</a></td>
</tr>
</table>
Voice is a feature of verbs that helps map the traditional syntactic functions,
such as subject and object, to semantic roles, such as agent and patient.
(**This feature, as defined currently, cannot correctly handle voice features on Tatar verbs.**)
The above combinations (of camel-case voice values) are a temporary solution to indicate "multiple
voice" features, but they are certainly not the best way to indicate
these features.
See [#197](https://github.com/UniversalDependencies/docs/issues/197) and
[#125](https://github.com/UniversalDependencies/docs/issues/125#issuecomment-112512320)
for the discussion.
### <a name="Pass">`Pass`</a>: passive voice
Passive voice demotes a subject to an oblique argument, and promotes an object to the subject position.
#### Examples
* _ичек ач<b>ыл</b>ды_ "the door was opened"
### <a name="PassRcp">`PassRcp`</a>: combination of passive and reciprocal voices
This language-specific value indicates that a verb with a reciprocal suffix is passivized.
#### Examples
* _аңла-<b>ш-ыл</b>-ды_ "alright" (lit: (it was) mutually understood)
### <a name="Rcp">`Rcp`</a>: reciprocal voice
A reciprocal verb describes an event in which two agents (or groups of agents) perform the same action upon each other.
The reciprocal is expressed by the suffix _-ыш/еш_ however,
the verb roots that can become reciprocal is limited.
#### Examples
* _күр<b>еш</b>ербез_ "we will see each other"
### <a name="Cau">`Cau`</a>: causative voice
In causative constructions the subject is the entity "causing" the action. It generally translate to English as 'cause/make/have/let/allow' someone to perform action described by the main verb.
#### Examples
* _аңла<b>т</b>тым_ "I explained (it)" (lit. "I made him/her/them understand it")
* _бәяне арт<b>тыр</b>дым_ "I raised the price" (lit. "I made the price increase")
### <a name="CauPass">`CauPass`</a>: passive causative voice
This language-specific value indicates that a verb has been first causativized, then passivized.
The meaning is "the subject was caused (by somebody) to do the action."
#### Examples
* _шул мәсьәлә аңла-<b>т-ыл</b>-ды_ "The problem was explained"
### <a name="CauRcp">`CauRcp`</a>: causative reciprocal voice
This language-specific value indicates that a verb with a reciprocal suffix is causativized.
The meaning is “the subject was caused (by somebody) to do the action.”
It describes an event in which two agents (or groups of agents) perform the same action upon each other and another entity causes the action.
#### Examples
* _ул мине аңа белән тан-<b>ыш-тыр-</b>ды_ "He introduced him/her to me" (lit: "He made me get to know with him/her")
### <a name="CauPassRcp">`CauPassRcp`</a>: causative reciprocal passive voice
This language-specific value indicates that a verb with a reciprocal suffix is passivized and causativized.
The meaning is “the subject was caused (by somebody) to do the action.”
It describes an event in which two agents (or groups of agents) perform the same action upon each other and another entity causes the action.
#### Examples
* _Укучылар эвакуация планы белән тан-<b>ыш-тыр-ыл</b>-ды_ "The students got familiarized with the evacuation plan" (lit: "The students were made to get to know with the evacuation plan")
<!-- Interlanguage links updated St lis 3 20:58:32 CET 2021 -->
| 36.971154 | 193 | 0.727698 | eng_Latn | 0.989237 |
54a8f4c677b742c5ecc2af4e87c470bdd8e9cd1d | 201 | md | Markdown | Office-ProPlus-Deployment/Install-OfficeClickToRun/README_Install-OfficeClickToRun.md | cvvamsi/Office-IT-Pro-Deployment-Scripts | e0283abbde0f5d322403acc4868c3d3c57b50c8e | [
"MIT"
] | 6 | 2021-08-05T09:13:37.000Z | 2021-11-02T04:54:32.000Z | Office-ProPlus-Deployment/Install-OfficeClickToRun/README_Install-OfficeClickToRun.md | golfkinguk/Office-IT-Pro-Deployment-Scripts | e0283abbde0f5d322403acc4868c3d3c57b50c8e | [
"MIT"
] | null | null | null | Office-ProPlus-Deployment/Install-OfficeClickToRun/README_Install-OfficeClickToRun.md | golfkinguk/Office-IT-Pro-Deployment-Scripts | e0283abbde0f5d322403acc4868c3d3c57b50c8e | [
"MIT"
] | 1 | 2020-07-07T16:30:38.000Z | 2020-07-07T16:30:38.000Z | ### Install Office Click-To-Run
This PowerShell function will install Office Click-To-Run
[README](https://github.com/OfficeDev/Office-IT-Pro-Deployment-Scripts/wiki/README_Install-OfficeClickToRun)
| 40.2 | 108 | 0.810945 | yue_Hant | 0.870056 |
54a92afadea5e641aaec08813e4ae5d935a99ab0 | 28,534 | md | Markdown | 2022.03.31-noslegal-release-notes-taxonomy.md | noslegal/taxonomy | bcf37474e9d1dae3f78afbeaaa7b8d169e172893 | [
"Apache-2.0"
] | 2 | 2022-03-31T10:12:27.000Z | 2022-03-31T10:42:33.000Z | 2022.03.31-noslegal-release-notes-taxonomy.md | noslegal/taxonomy | bcf37474e9d1dae3f78afbeaaa7b8d169e172893 | [
"Apache-2.0"
] | null | null | null | 2022.03.31-noslegal-release-notes-taxonomy.md | noslegal/taxonomy | bcf37474e9d1dae3f78afbeaaa7b8d169e172893 | [
"Apache-2.0"
] | 2 | 2022-03-31T10:12:02.000Z | 2022-03-31T14:29:36.000Z | ***noslegal***
**Taxonomy release notes**
**Release 1.0** / 31 March 2022
# 1. Overview
These are the release notes for a taxonomy of four facets designed for
describing work done in relation to legal issues, and the related
processes and artifacts.
The four facets are Legal (1) Work (2) Subjects (3) Perspectives and (4)
Places.
We envisage that many organisations using these facets will likely also
adopt a fifth facet, industry or sector, though we don't propose to
develop a new one.[^1]
## Who's done the work?
Our work has been done on a voluntary basis, starting in late 2020 and
proceeding over a number of iterations in the 18 months since then.
Input has been received mainly from large commercial law firms in the UK
(though with some significant inputs from elsewhere) and from UK (or KU
arms of) technology companies focused on legal topics.
In future iterations, we aim to expand the diversity of perspectives
involved - we're very conscious of the tendency of many legal knowledge
projects to be dominated by US / UK perspectives, something which will
limit the success of this project unless acknowledged and managed.
## Who and what is this for?
<table>
<colgroup>
<col style="width: 56%" />
<col style="width: 43%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>Designed for</strong></td>
<td><strong>Not</strong> designed for</td>
</tr>
<tr class="even">
<td colspan="2"><blockquote>
<p><em>People:</em></p>
</blockquote></td>
</tr>
<tr class="odd">
<td><ol type="1">
<li><blockquote>
<p>Providers of legal services (e.g. law firms, NewLaw, corporate legal
department)</p>
</blockquote></li>
<li><blockquote>
<p>Buyers of legal services (e.g. corporate legal in their
buying/coordinating capacity, buyers who aren’t lawyers)</p>
</blockquote></li>
<li><blockquote>
<p>Providers and users of technology in connection with legal work (e.g.
for describing information stored in such technology)</p>
</blockquote></li>
</ol></td>
<td><ol type="1">
<li><p>Writers, researchers and educators on legal rules and
doctrines</p></li>
<li><p>Legislators and regulators</p></li>
</ol></td>
</tr>
<tr class="even">
<td colspan="2"><blockquote>
<p><em>Need:</em></p>
</blockquote></td>
</tr>
<tr class="odd">
<td rowspan="2"><ol type="1">
<li><p>Describing, analysing and reporting on legal matters, including
internally (e.g. within a law firm or legal department) and to clients,
and including analysis to compare work done for different clients or by
different providers</p></li>
<li><p>Organising and finding practical legal knowledge (e.g. documents,
process templates, examples, how-to guides, training courses)</p></li>
</ol>
<ol start="3" type="1">
<li><blockquote>
<p>Describing and finding legal services (e.g. on a law firm’s website
or in a legal services marketplace)</p>
</blockquote></li>
<li><blockquote>
<p>Describing how legal services providers are organised and what they
do (e.g. law firms, NewLaw providers, corporate legal departments or
others)</p>
</blockquote></li>
<li><blockquote>
<p>Describing and finding individual legal experience and specialisms
for individuals (e.g. for work allocation or training purposes)</p>
</blockquote></li>
</ol></td>
<td rowspan="2"><ol type="1">
<li><blockquote>
<p>Researching and analysing legal rules and doctrines, including legal
research databases, textbooks and theoretical legal analysis</p>
</blockquote></li>
<li><blockquote>
<p>Describing legal roles and activities within a matter (e.g. drafting,
negotiating, adjudicating, advocating)</p>
</blockquote></li>
<li><blockquote>
<p>Describing phases and tasks within a legal matter (e.g. due
diligence, trial)</p>
</blockquote></li>
<li><blockquote>
<p>Describing legal document types (e.g. pleadings, contracts) and their
parts (e.g. provisions) (a project has been proposed for us to look at
this together, but we are still considering whether to do so)</p>
</blockquote></li>
<li><blockquote>
<p>Deep dives into local or specialist topics (if required, we envisage
these being added as modules which can fit into the higher level
categories we have defined)</p>
</blockquote></li>
</ol></td>
</tr>
<tr class="even">
</tr>
</tbody>
</table>
We're not dismissing the importance of the roles and needs on the right.
It's a question of focus. There are real trade-offs here. Many existing
projects focus on the right hand side of this table whereas ours focuses
on the left hand side. Of course, if our work nevertheless turns out to
be useful for roles and needs on the right hand side, so much the
better.
## Simplicity and detail
**Legal Work**, **Subjects** and **Perspectives** are deliberately
simple.
In this initial release, they have a total of 70 concepts.
There are nevertheless a huge number of useful combinations possible.
Examples of descriptions which can be built using them and Legal Places
-
- an investigation in France involving a corporate body concerning
regulation
- litigation in Texas involving individuals concerning land and
buildings
- a transfer of tangible property governed by Kenyan law
Problems with excessive splitting include:
1. Distinctions tend to turn out to be more difficult and arbitrary
than envisaged
2. They are less relevant internationally - it doesn't take much detail
to lose comprehensibility between legal systems
3. They are likely to be less stable over time, as societies,
economies, technologies and laws change
4. They are more onerous for humans to apply
5. The distinctions are likely, we suspect, to be less accurate for
machines to apply even as technology progresses
6. The splitting is likely to be of less usefulness
7. Any given type of splitting is likely to appeal more to certain
niches than others. For example, splitting something in a
legal-conceptual way for the purpose of better legal research within
a particular system of case law may not be relevant for use cases
involving better pricing, or better lawyer-finding.
That said, we do envisage further detail being built on to these simple
taxonomies where relevant, for example by
1. private efforts within organisations,
2. recommending that our users use it in conjunction with other
taxonomies and ontologies, for example those focused on one or more
national legal systems (e.g.
[[SALI]{.underline}](https://www.sali.org/)) international topics
(e.g. [[Regulatory
Genome]{.underline}](https://www.regulatorygenome.org/)), other
professional perspectives (e.g. accounting - [[Engine
B]{.underline}](https://engineb.com/)) and many more (see e.g. this
[[collection of legally relevant
ontologies]{.underline}](https://github.com/Liquid-Legal-Institute/Legal-Ontologies)
curated by Liquid Legal Institute),
3. developing some further details within noslegal, where there is no
adequate third party taxonomy.
**Legal Places** is considerably more detailed, with over 7,000 rows of
data organised across 11 sheets . This has been viable because places
are already quite well-defined legally in most of the world. We have
been able to build on this public domain foundation in various ways,
described below.
## Maturity
**Legal Places** is largely quite mature, though certain points have
been highlighted for feedback. The other three facets are earlier stage.
We believe that **Legal Work** is fundamentally robust in that it
1. has undergone some testing in large organisations against real data;
2. has been validated verbally by a significant range of knowledgeable
people as making relevant distinctions of practical significance for
the intended use cases;
3. is relevant across a range of legal work and places;
4. Is simple enough to have a prospect of being applied with reasonable
accuracy, first by humans and over time with machine assistance
However, the details will definitely evolve. **Legal Subjects** and
**Legal Perspectives** are the least mature, having been developed in
2022 Q1 as a result of feedback on earlier iterations of Legal Work plus
an earlier concept known as Legal Contexts.
If you come from the software world, you may find it helpful to think of
Legal Places as a [[1.0
release]{.underline}](https://en.wikipedia.org/wiki/Software_versioning#Version_1.0_as_a_milestone),
Legal Work as a [[public
beta]{.underline}](https://en.wikipedia.org/wiki/Software_release_life_cycle#Open_and_closed_beta)
and the other two as a [[public
alpha]{.underline}](https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha).
## Next steps
During 2022, we will be building on the foundation represented by this
release.
- **Format.** At this stage, we have published in the form of
spreadsheets as we wished to focus attention first on content, and
present this quickly for wider feedback. In future, we envisage
presenting an
[[OWL]{.underline}](https://en.wikipedia.org/wiki/Web_Ontology_Language)
format (probably via Web Protege). We are also considering
publishing in
[[SKOS]{.underline}](https://en.wikipedia.org/wiki/Simple_Knowledge_Organization_System)
and [[JSON]{.underline}](https://en.wikipedia.org/wiki/JSON).
- **Testing and iteration.** We will work with interested
organisations to test the taxonomy facets in their systems,
implement them where possible and determine how to develop them.
- **Versioning and maintenance.** We plan to track changes and release
versions periodically which include updates (e.g. to places),
enhancements and correction of any errors. Feedback is sought on
various points below, but please let us know any other points which
occur. You can contact us through the noslegal website, noslegal.org
- **Governance.** We plan to put in place more robust governance
structures to ensure the long term success of this work.
- **Interoperability.** We plan to explore interoperability with other
relevant taxonomy projects.
- **Diversifying.** We have a good range of perspectives from the
US-UK large commercial law firm world already, including its tech
providers. That's great, and more people from that world are always
welcome, but we also want to increase involvement from outside that
world so that noslegal can become widely relevant.
# 2. Legal Work, Subjects and Perspectives
## Summary of Legal Work, Subjects and Perspectives
These three facets provide, for a legal matter, a systematic way of
articulating the characteristically legal work done (Legal Work - the
'verb'), the legally-conceptualised things affected (Legal Subjects -
the 'noun') and the practical needs or impacts from a relevant
perspective (Legal Perspectives).
### Legal Work
**Legal Work** has three top-level concepts - Resolving, Transacting and
Operating.
Each has five sub-categories.
Resolving breaks down into
- Disputes
- Enforcement and prosecution
- Investigations and inquiries
- Administrative issues
- Public affairs
We believe these are broadly-recognised as relevant, major categories
and are quite readily distinguishable, though inevitably there are edge
cases, and complex matters may involve more than one.
Transacting breaks down into
- Establishing
- Changing
- Dissolving and administering
- Transferring
- Financing
The first three are 'lifecycle' concepts. The fourth and fifth are
obviously important.
Operating also has five elements
- Advising
- Managing knowledge
- Governance
- Complying and managing risk
- Legal operations
The first and second are obviously central to what lawyers do, and
clients need. The third and fourth are key for organisations with
complex activities. The fifth is relatively new, but important.
All of the above concepts are - of course - capable of further
subdivision.
We have, in fact, sub-divided Resolving into ten third-level concepts as
there was a fairly clear and useful basis on which to do so. Further
sub-division is more debateable, so we've decided not to do so at this
stage, and instead to consult as to whether this would be useful, and if
so how to do it.
### Legal Subjects
**Legal Subjects** also has three top-level concepts, which are based on
the legal thinking of millennia. We've called them People, Property and
Duties.
**People** has five sub-divisions
- Individual
- Family
- Group
- Corporate body
- Authority
We believe the line between these is fairly clear, and useful.
**Property** has three sub-divisions
- Land and buildings
- Tangible property - *defined to exclude land and buildings*
- Intangible property - *defined as, in effect, all other types of
property*
This is not an entirely straightforward topic, as national legal systems
have developed highly technical distinctions in this area over the
centuries.
Historically, the major issues in property law involved the first two
categories.
These days, much value is wrapped up in intangible property - everything
from bank accounts to shares to derivatives to intellectual property.
We envisage sub-dividing intangible property in future iterations, but
thought at this stage it would be less distracting to stop with this
simple initial sub-division.
**Duties** is perhaps the most debateable category.
We've created three subdivisions
- Contracts
- Non-contractual obligations
- Public powers, rights and duties
We think this is a practically meaningful approach given the importance
of contracts. The other two concepts capture the rest of the private and
public spheres, respectively. Inevitably the boundary line will be drawn
differently in different societies and legal systems, but we offer this
as a simple robust set of distinctions of wide relevance. It is
certainly capable of further sub-division in future.
### Legal Perspectives
This facet is perhaps the most unconventional.
Typical legal taxonomies have sought to define legal work in 'objective'
terms not affected by the perspective of the participant. Of course
there can be value in that, but we think that it may be more useful in
some ways to characterise a problem from a particular perspective.
The three top-level perspectives we have proposed are
- Personal life
- Business
- Society and authority
These are broken down provisionally in ways set out in the spreadsheet.
To give an example, assume that a person slips and falls in a
supermarket and breaks her arm.
To her, this may raise legal questions relating to the implications of
inability to work while the injury is healed, perhaps issues relating to
payment for healthcare (depending on the legal system) and issues
relating to compensation for damage if the supermarket can be said to be
legally responsible.
To the supermarket, the issues are more one of customer relationships,
reputation and financial liability. Perhaps there will be regulatory
issues as well, depending on the circumstances.
The perspectives, in short, are very different.
For the Society and authority perspective, we have adopted the
[[Classification of the Functions of Government (COFOG)
taxonomy]{.underline}](https://unstats.un.org/unsd/classifications/Family/Detail/4)
for significant elements. The details are noted in the relevant rows of
the Excel file. This seems to us more appropriate than creating a new
taxonomy in that area.
This facet of the taxonomy seeks to recognise that and to build out
important elements of different perspectives. Feedback is welcome,
recognising that this is the least 'mature' element of the project.
# 3. Legal Places
## Summary of Legal Places
Legal Places is more detailed than the other facets, but only because we
have built it upon the invaluable public domain foundation made
available by the United Nations and the International Standards
Organisation in cooperation with various national standards
organisations.
Legal Places has five main data sheets, each with one or more supporting
sheets.
Each sheet is intended to be modular. You can use it individually (or
even just use parts of it). But the sheets are also designed to work
well together.
They are largely independent from our other taxonomy facets (Legal Work,
Subjects and Contexts) though sheet 4.0 (connecting factors) ties in
closely with Legal Work and Legal Subjects.
In summary, the sheets cover:
### 1.0 Countries and areas
- This lists the 249 top-level countries and areas which have
top-level (two-letter) ISO codes. Most are independent sovereign
states, but a considerable number are not.
- Each country or area has a row of the spreadsheet.
- Sheet 1.0 has 19 columns in total, each modelling a different
attribute or relationship of each country or area.
- Many of these contain public domain information taken from ISO or UN
sources, but we have made some refinements. For exampl -
- shorter names where we think these are likely to be regarded
more convenient than the official ISO short names (which in some
cases are rather long);
- addition of some unofficial regions defined by us -- AMER
together with variants of EMEA and APAC.
- We have also indicated whether a country or area is a UN member and,
if not, any linked UN member. We have, in addition, cross-referenced
to alternative codes, as this can otherwise cause confusion. For
example, Aruba has the top-level code AW but also appears in the
Netherlands taxonomy as NL-AW.
- Supporting sheets 1.1 and 1.2 define the UN regions and unofficial
regions used in 1.0. Supporting sheet 1.3 lists names in a number of
languages other than English.
- We may in future expand the list of unofficial regions and different
languages if there is demand.
### 2.0 Systems
- This sheet gives a summary of the type, or types, of legal system of
almost all of the places listed in sheet 1.0. It includes an
indication of particularly important historical influences from
other places (in most cases, of a colonial nature).
- This is inevitably an approximate and imperfect approach, as legal
styles which are superficially reminiscent of, say, French or
English law, may mask hugely important differences. There are also
many examples in which elements of national law derive from
different traditions (for example, commercial laws influenced by a
former colonial power and family laws are based on local customary
or religious legal concepts).
- Nevertheless, there is some usefulness here so we have proceeded
with this approach, recognising its imperfections.
- Supporting sheet 2.1 defines twelve types of system used in 2.0.
- Feedback is sought as to what extent you find it useful to maintain
and develop this approach.
### 3.0 Subdivisions
- This sheet contains over 5,000 subdivisions of the countries and
areas in sheet 1.0, including parent-child relationships between
subdivisions (for example, Kampala is a subdivision of the Central
Region which in turn is a subdivision of Uganda).
- These subdivisions are almost all based on ISO, but
- In two cases - the UAE and UK - we have defined some additional
subdivisions which are legally relevant. In the case of UAE,
these are the Free Zones within each Emirate. In the case of the
UK, we have defined England and Wales as a legally-relevant
jurisdiction, and have defined Greater London as an area
comprising the ISO-recognised City of London ('the Square Mile')
and the ISO-recognised London boroughs.[^2]
- We have edited the set of names to identify those which we think
will be most practically recognisable for English-speaking users
of legal systems. So, for example, we use 'Damascus' for the
capital of Syria, instead of the ISO name 'Dimashq' and 'West
Pomerania' for a region of Poland instead of the ISO name
'Zachodniopomorskie.' This inevitably involves judgements which
not everyone will agree with, so we've been careful to show the
ISO names (of which there are sometimes a number of
alternatives) so that users of this dataset can conveniently
choose.
- Another policy decision we have taken is to present subdivision
names without accents and special characters not familiar to
most English native speakers. So, for example, we use
'Thingeyjarsveit' instead of 'Þingeyjarsveit' for a municipality
of Iceland, and 'Dashkasan' instead of 'Daşkəsən' for a rayon of
Azerbaijan.
- We welcome feedback on all of this.
- Supporting sheet 3.1 lists 111 subdivision types used in sheet 3.0.
Almost all of these are derived from ISO 3166. The other three are
unofficial. One ('Jurisdiction') is used for the legally-relevant
non-ISO subdivision of 'England and Wales' within the United
Kingdom. The other two ('Free Zone' and 'Park') are used for some
legally-relevant non-ISO subdivisions within the United Arab
Emirates.
### 4.0 Connecting factors
- This expresses six main types of legally relevant relationship that
something (for instance, a legal matter or knowledge artifact) may
have with a place.
- Three of them are related to the three top level categories of Legal
Work, and the other three are related to the three top level
categories of Legal Subjects.
- One of these is subdivided into seven further types as this is
possible to do so in that context in ways which we think are
reasonably clear and useful.
### 5.0 Memberships
- This captures the membership of 54 international organisations and
treaties of practical legal relevance, including the dates on which
membership started.
- This list is easily expanded. Suggested additions are welcome.
More detailed notes are in **annex 1** to this document.
##
## Legal basis of using ISO 3166 codes
The International Standards Organisation (ISO) publishes many of the
codes and related information which we used as a foundation for building
up this dataset.
This information is known as ISO 3166 and is maintained by the ISO 3166
Maintenance Agency, which includes representatives from various
international and national organisations. ISO 3166's history and scope
are [[described
here]{.underline}](https://www.iso.org/obp/ui/#iso:std:iso:3166:-1:ed-4:v1:en).
Given the wide public and private usage of these codes, it clearly made
sense for us to build upon these rather than re-invent them. We
therefore examined the legal ability to do so.
This information is made available by ISO in two formats:
1. ISO offer a commercial product called the [[Country Codes
Collection]{.underline}](https://www.iso.org/publication/PUB500001.html).
This is a spreadsheet which can be purchased for CHF300 and is
updated each year. However, this product is licensed on a
single-user basis so was not suitable for our purposes. We therefore
did not purchase or use it.
2. ISO also make the codes publicly available free of charge on an
[['Online Browsing
Platform.']{.underline}](https://www.iso.org/obp/ui/#search) This is
kept up to date and a [[change
log]{.underline}](https://isotc.iso.org/livelink/livelink?func=ll&objId=16474544&objAction=browse&sort=name&viewType=1)
is published.
Our understanding is that the information on the Online Browsing
Platform is public domain and can be used freely. We corresponded with
ISO to verify this. The relevant correspondence is below, and confirms
this.[^3]
<table>
<colgroup>
<col style="width: 14%" />
<col style="width: 85%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>noslegal first email</strong></td>
<td><p><em>Please could you help me understand the copyright status of
ISO-3166.</em></p>
<p><em>My understanding is that</em></p>
<p><em>1. The ISO-3166 codes published on the Online Browsing Platform
are open source / public domain -
https://www.iso.org/obp/ui/#search/code/</em></p>
<p><em>2. However, copyright is asserted by ISO in respect of the CHF300
product sold on the ISO website -
https://www.iso.org/terms-conditions-licence-agreement.html#Customer-Licence</em></p>
<p><em>Have I understood this correctly?</em></p></td>
</tr>
<tr class="even">
<td><strong>ISO first email</strong></td>
<td><em>If you are asking if you can use these country codes in an
application or software for free, the answer is yes. ISO allows free of
charge use of the country codes.</em></td>
</tr>
<tr class="odd">
<td><strong>noslegal second email</strong></td>
<td><p><em>It's great to have your confirmation that we're free to use
the codes. Please could you confirm whether there are any restrictions
or conditions? I can't find any restrictions on the ISO website, and
there are examples all over the internet of the ISO codes being used
publicly. However, I just wanted to check whether they're actually
public domain (i.e. legally free for anyone to use).</em></p>
<p><em>What we're planning to do is to use the codes to link the various
countries, districts etc to various legal topics e.g. the legal system
type, the legal organisations that they belong to. We plan to publish
this information as an open source taxonomy for anyone to use, free of
charge. We would note as part of this publication that the country codes
are the ISO ones.</em></p>
<p><em>I'd appreciate any clarification you can add.</em></p></td>
</tr>
<tr class="even">
<td><strong>ISO second email</strong></td>
<td><p><em>Unfortunately, I can't speak for the content that you have
found on certain websites.</em></p>
<p><em>ISO allows the use of the codes found <a
href="https://www.iso.org/obp/ui/#search"><u>here</u></a> as you wish to
use them.</em></p>
<p><em>However, ISO does not allow to post on the internet the codes
from <a href="https://www.iso.org/obp/ui#iso:pub:PUB500001:en"><u>this
product</u></a>.</em></p></td>
</tr>
<tr class="odd">
<td><strong>noslegal third email</strong></td>
<td><p><em>Thank you very much. Yes, it's the codes derived from your
first link (i.e. online browsing platform) that we're planning to use.
So, we'll go ahead on that basis.</em></p>
<p><em>I read the licence terms for the spreadsheet version at your
second link and it was clear that the licence terms wouldn't permit what
we're intending, so we're not going to do so.</em></p>
<p><em>Has your legal department provided any guidance on the actual
legal status of the codes on the online browsing platform. My
interpretation is that they're public domain but I thought it was
strange I couldn't find it expressly stated on the ISO
website.</em></p></td>
</tr>
<tr class="even">
<td><strong>ISO third email</strong></td>
<td><em>Your interpretation as regards to the usage of the publicly
available codes is correct. It is not mentioned on the website but we
are here to provide that information.</em></td>
</tr>
</tbody>
</table>
[^1]: There are various industry / sector taxonomies already, originally
designed for custom authorities (e.g.
[[ISIC]{.underline}](https://en.wikipedia.org/wiki/International_Standard_Industrial_Classification),
[[UK
SIC]{.underline}](https://en.wikipedia.org/wiki/United_Kingdom_Standard_Industrial_Classification_of_Economic_Activities),
[[NACE]{.underline}](https://en.wikipedia.org/wiki/Statistical_Classification_of_Economic_Activities_in_the_European_Community),
[[NAICS]{.underline}](https://en.wikipedia.org/wiki/North_American_Industry_Classification_System),
[[US
SIC]{.underline}](https://en.wikipedia.org/wiki/Standard_Industrial_Classification#Uses))
or investors (e.g.
[[Refinitiv/TRBC]{.underline}](https://en.wikipedia.org/wiki/The_Refinitiv_Business_Classification),
[[GICS]{.underline}](https://en.wikipedia.org/wiki/Global_Industry_Classification_Standard),
[[ICB]{.underline}](https://en.wikipedia.org/wiki/Industry_Classification_Benchmark)).
. We don't think it's useful to seek to create another, but do
envisage in future producing a short guide on how to use what's
already out there in a legal context.
[^2]: Since November 2021, ISO 3166 at least recognises England, Wales,
Scotland and Northern Ireland as entities. The old British Standard
recognised England and Wales as an entity, and we have adopted the
old British Standard code for that, GB-EAW.
[^3]: Salutations and courtesies have been excluded from the extracts.
| 38.663957 | 132 | 0.754013 | eng_Latn | 0.998867 |
54a950febea9b8ec081e8a250d272c1d989e0836 | 5,502 | md | Markdown | gov2/sqs/README.md | iconara/aws-doc-sdk-examples | 52706b31b4fce8fb89468e56743edf5369e69628 | [
"Apache-2.0"
] | 5,166 | 2016-09-02T08:48:38.000Z | 2022-03-31T19:12:43.000Z | gov2/sqs/README.md | iconara/aws-doc-sdk-examples | 52706b31b4fce8fb89468e56743edf5369e69628 | [
"Apache-2.0"
] | 1,186 | 2016-09-28T23:05:19.000Z | 2022-03-31T18:07:47.000Z | gov2/sqs/README.md | iconara/aws-doc-sdk-examples | 52706b31b4fce8fb89468e56743edf5369e69628 | [
"Apache-2.0"
] | 4,003 | 2016-08-29T19:51:40.000Z | 2022-03-31T16:40:02.000Z | # AWS SDK for Go V2 code examples for Amazon SQS
## Purpose
These examples demonstrate how to perform several
Amazon Simple Queue Service (Amazon SQS)
operations using version 2 of the AWS SDK for Go.
## Prerequisites
You must have an AWS account, and have your default credentials and AWS Region
configured as described in
[Configuring the AWS SDK for Go](https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html)
in the AWS SDK for Go Developer Guide.
## Running the code
### ChangeMsgVisibility/ChangeMsgVisibilityv2.go
This example sets the visibility timeout for a message in an Amazon SQS queue.
`go run ChangeMsgVisibilityv2.go -q QUEUE-NAME -h RECEIPT-HANDLE -v VISIBILITY`
- _QUEUE-NAME_ is the name of the queue.
- _RECEIPT-HANDLE_ is the receipt handle of the message.
- _VISIBILITY_ is the duration, in seconds, that the message is not visible to other consumers.
The example ensures the value is between 0 and 12 hours;
the default is 30 seconds.
The unit test accepts similar values in _config.json_.
### ConfigureLPQueue/ConfigureLPQueuev2.go
This example configures an Amazon SQS queue to use long polling.
`go run ConfigureLPQueuev2.go -q QUEUE-NAME [-w WAIT-TIME]`
- _QUEUE-NAME_ is the name of the queue to configure.
- _WAIT-TIME_ is how long, in seconds, to wait.
The example ensures the value is between 1 and 20;
the default is 10.
The unit test accepts similar values in _config.json_.
### CreateQueue/CreateQueuev2.go
This example creates an Amazon SQS queue.
`go run CreateQueuev2.go -q QUEUE-NAME`
- _QUEUE-NAME_ is the name of the queue to create.
The unit test accepts a similar value in _config.json_.
### CreateLPQueue/CreateLPQueuev2.go
This example creates a long-polling Amazon SQS queue.
`go run CreateLPQueuev2.go -q QUEUE-NAME [-w WAIT-TIME]`
- _QUEUE-NAME_ is the name of the queue to create.
- _WAIT-TIME_ is how long, in seconds, to wait.
The example ensures the value is between 1 and 20;
the default is 10.
The unit test accepts similar values in _config.json_.
### DeadLetterQueue/DeadLetterQueuev2.go
This example configures an Amazon SQS queue for messages
that could not be delivered to another queue.
`go run DeadLetterQueuev2.go -q QUEUE-NAME -d DEAD-LETTER-QUEUE-NAME`
- _QUEUE-NAME_ is the name of the queue from which the dead letters are sent.
- _DEAD-LETTER-QUEUE-NAME_ is the name of the queue to which the dead letters are sent.
The unit test accepts similar values in _config.json_.
### DeleteMessage/DeleteMessagev2.go
This example deletes a message from an Amazon SQS queue.
`go run DeleteMessagev2.go -q QUEUE-NAME -m MESSAGE-HANDLE`
- _QUEUE-NAME_ is the name of the queue from which the message is deleted.
- _MESSAGE-HANDLE_ is the handle of the message to delete.
The unit test accepts similar values in _config.json_.
### DeleteQueue/DeleteQueuev2.go
This example deletes an Amazon SQS queue.
`go run DeleteQueuev2.go -q QUEUE-NAME`
- _QUEUE-NAME_ is the name of the queue to delete.
The unit test accepts a similar value in _config.json_.
### GetQueueURL/GetQueueURLv2.go
This example gets the URL of an Amazon SQS queue.
`go run GetQueueURLv2.go -q QUEUE-NAME`
- _QUEUE-NAME_ is the name of the queue for which the URL is retrieved.
The unit test accepts a similar value in _config.json_.
### ListQueues/ListQueuesv2.go
This example retrieves a list of your Amazon SQS queues.
`go run ListQueuesv2.go`
### ReceiveLPMessage/ReceiveLPMessagev2.go
This example gets the most recent message from a long-polling Amazon SQS queue.
`go run ReceiveLPMessagev2.go -q QUEUE-NAME`
- _QUEUE-NAME_ is the name of the queue from which the message is retrieved.
The unit test accepts a similar value in _config.json_.
### ReceiveMessage/ReceiveMessagev2.go
This example gets the most recent message from an Amazon SQS queue.
`go run ReceiveMessagev2.go -q QUEUE-NAME`
- _QUEUE-NAME_ is the name of the queue from which the message is retrieved.
The unit test accepts a similar value in _config.json_.
### SendMessage/SendMessagev2.go
This example sends a message to an Amazon SQS queue.
`go run SendMessagev2.go -q QUEUE-NAME`
- _QUEUE-NAME_ is the name of the queue to which the message is sent.
The unit test accepts a similar value in _config.json_.
### Notes
- We recommend that you grant this code least privilege,
or at most the minimum permissions required to perform the task.
For more information, see
[Grant Least Privilege](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege)
in the AWS Identity and Access Management User Guide.
- This code has not been tested in all AWS Regions.
Some AWS services are available only in specific
[Regions](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services).
- Running this code might result in charges to your AWS account.
## Running the unit tests
Unit tests should delete any resources they create.
However, they might result in charges to your
AWS account.
To run a unit test, enter:
`go test`
You should see something like the following,
where PATH is the path to the folder containing the Go files:
```sh
PASS
ok PATH 6.593s
```
If you want to see any log messages, enter:
`go test -v`
You should see some additional log messages.
The last two lines should be similar to the previous output shown.
Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. SPDX-License-Identifier: Apache-2.0
| 29.740541 | 117 | 0.770992 | eng_Latn | 0.986453 |
54aaadeaae748d40513ed602b7350a576b0b642c | 59 | md | Markdown | README.md | water-bird/Dota-Role-Randomizer | b1a8c007c9cd52640a835dab60dc31d7e9fe4765 | [
"MIT"
] | null | null | null | README.md | water-bird/Dota-Role-Randomizer | b1a8c007c9cd52640a835dab60dc31d7e9fe4765 | [
"MIT"
] | null | null | null | README.md | water-bird/Dota-Role-Randomizer | b1a8c007c9cd52640a835dab60dc31d7e9fe4765 | [
"MIT"
] | null | null | null | # Dota2-Hero-Randomizer
credit to dota 2 for being amazing
| 19.666667 | 34 | 0.79661 | eng_Latn | 0.955183 |
54ac2f2c2df3053a4a83da981c7b8ebe9a8d9c03 | 71 | md | Markdown | source/tags/index.md | snakeliwei/Myblog-src | fd632b5327db2b5507b0419e38c649240ed071a5 | [
"Artistic-2.0"
] | 1 | 2015-12-08T05:47:10.000Z | 2015-12-08T05:47:10.000Z | source/tags/index.md | snakeliwei/Myblog-src | fd632b5327db2b5507b0419e38c649240ed071a5 | [
"Artistic-2.0"
] | 1 | 2016-03-18T01:24:22.000Z | 2016-03-18T01:24:22.000Z | source/tags/index.md | snakeliwei/Myblog-src | fd632b5327db2b5507b0419e38c649240ed071a5 | [
"Artistic-2.0"
] | null | null | null | title: Tags
date: 2014-07-17 11:03:29
layout: tags
comments: false
---
| 11.833333 | 25 | 0.704225 | eng_Latn | 0.428313 |
54ac53a4a36a2aed185758dde69ebdf087912bde | 1,061 | md | Markdown | docs/week-nine.md | akrinos/2021-phyto-phys | 8977588a9563cb31a8b0ea23044af34eb4f82528 | [
"MIT"
] | null | null | null | docs/week-nine.md | akrinos/2021-phyto-phys | 8977588a9563cb31a8b0ea23044af34eb4f82528 | [
"MIT"
] | null | null | null | docs/week-nine.md | akrinos/2021-phyto-phys | 8977588a9563cb31a8b0ea23044af34eb4f82528 | [
"MIT"
] | null | null | null | # Session 8
## Viruses
<div class="panel panel-primary">
<div class="panel-heading">
<h3 class="panel-title">Papers to Read Before!</h3>
</div>
<div class="panel-body">
Birth and death processes are complicated by the presence of viruses in ocean ecosystems.<br>
<a href="https://2021-phyto-phys.readthedocs.io/en/latest/_static/suttle1990.pdf">Suttle 1990</a>: viruses in the phytoplankton<br>
<a href="https://2021-phyto-phys.readthedocs.io/en/latest/_static/menge2009.pdf">Menge 2009</a>: coping with whether to prioritize evolutionary success against viruses
</div>
</div>
### Eukaryotic populations and viruses
<object data="https://2021-phyto-phys.readthedocs.io/en/latest/_static/thomas2011.pdf" type="application/pdf" width="700px" height="700px">
<embed src="https://2021-phyto-phys.readthedocs.io/en/latest/_static/thomas2011.pdf">
<p>Alternatively, download the PDF to view it: <a href="https://2021-phyto-phys.readthedocs.io/en/latest/_static/thomas2011.pdf">Download PDF</a>.</p>
</embed>
</object>
| 48.227273 | 173 | 0.722903 | eng_Latn | 0.452814 |
54acda6ecf9704a33ae304b2f1357f6cc2f17ea9 | 5,357 | md | Markdown | doc/Application_Settings.md | DanielRenne/GoCore | d3d98e459691c133d0f24e0231fa7addd9e38937 | [
"MIT"
] | 11 | 2016-05-08T04:06:07.000Z | 2021-06-26T02:51:11.000Z | doc/Application_Settings.md | DanielRenne/GoCore | d3d98e459691c133d0f24e0231fa7addd9e38937 | [
"MIT"
] | 10 | 2016-05-02T17:55:00.000Z | 2019-08-25T08:45:38.000Z | doc/Application_Settings.md | DanielRenne/GoCore | d3d98e459691c133d0f24e0231fa7addd9e38937 | [
"MIT"
] | 4 | 2016-05-15T22:38:40.000Z | 2020-05-05T15:45:38.000Z | #GoCore Application Settings
There are 2 components to GoCore which must be configured within your application:
##buildCore
Create a build package for your application with the following:
package main
import (
"github.com/DanielRenne/GoCore/buildCore"
)
func main() {
buildCore.Initialize("src/github.com/DanielRenne/GoCoreHelloWorld")
}
##app
The GoCore/core/app package is what runs your application. You must first Initialize() it with the root path of your application. Then call the Run() method.
package main
import (
"github.com/DanielRenne/GoCore/core/app"
_ "github.com/DanielRenne/GoCoreHelloWorld/webAPIs/v1/webAPI"
)
func main() {
//Run First.
app.Initialize("src/github.com/DanielRenne/GoCoreHelloWorld")
//Add your Application Code here.
//Run Last.
app.Run()
}
#App Settings
GoCore reads a file located in the root directory of your package called WebConfig.json If one does not exist `buildCore` will auto generate one for your package with default settings.
##WebConfig.json
There are two root objects to be configured:
###application
"application":{
"domain": "127.0.0.1",
"httpPort": 80,
"httpsPort": 443,
"releaseMode":"release",
"webServiceOnly":false,
"info":{
"title": "Hello World Playground",
"description":"A web site to try GoCore.",
"contact":{
"name":"DRenne",
"email":"[email protected]",
"url":"myWebSite.com"
},
"license": {
"name": "Apache 2.0",
"url": "http://www.apache.org/licenses/LICENSE-2.0.html"
},
"termsOfService":"http://127.0.0.1/terms"
},
"htmlTemplates":{
"enabled":false,
"directory":"templates",
"directoryLevels": 1
}
}
At the root of application there are the following fields:
####domain
Tells the application which domain to redirect https traffic to.
####serverFQDN
Currently only used for bootstrap purposes to compare domainName where you want your data inserted
####logGophers
Instead of calling go func on anonymous functions. Use logger.GoRoutineLogger() and pass the func with a description. Then setup logGophers to true in your web config to log the time in which a goroutine starts and potentially exits.
####releaseMode
Tells the application to debug and run GIN http routing into release mode. "release" will enable release. An empty string will place the application in debug mode.
####webServiceOnly
Tells the application only route web service paths. NO static file routing will be enabled when set to true.
####customGinLogger
If you plan to write and .Use a custom gin logger in your AppIndex, set to true. Otherwise the default of false will use the default logger and recovery handler.
####productName
A short name (usually not human with spaces). Can be used to control which bootstrap information to seed based on the webConfig.json
####versionNumeric
This is used primarily for bootstrapping data with the BootstrapMeta struct to tag your seeds with how you want them to run
```
type BootstrapMeta struct {
Version int `json:"Version" bson:"Version"`
Domain string `json:"Domain" bson:"Domain"`
ReleaseMode string `json:"ReleaseMode" bson:"ReleaseMode"`
InfoTitle string `json:"PostCode" bson:"PostCode"`
DeleteRow bool `json:"DeleteRow" bson:"DeleteRow"`
}
```
####versionDot
Useful to show the users a dot-based version
####info
Tells the application details about the application for swagger.io information and schema.
####htmlTemplates
Tells the application to use HTML templates that conform to the GIN Engine. See [HTML Rendering in GIN](https://github.com/gin-gonic/gin#html-rendering]). See [HTML Templates](https://github.com/DanielRenne/GoCore/blob/master/doc/HTML_Templates.md) for more details and examples.
####htmlTemplates
Tells the application to use HTML templates that conform to the GIN Engine. See [HTML Rendering in GIN](https://github.com/gin-gonic/gin#html-rendering]). See [HTML Templates](https://github.com/DanielRenne/GoCore/blob/master/doc/HTML_Templates.md) for more details and examples.
###dbConnections
Provides an array of database connections. Currently GoCore only supports a single database connection. Future releases will allow for multiple connections and types.
"dbConnections":[
{
"driver" : "boltDB",
"connectionString" : "db/helloWorld.db"
}
]
###Database Connection Examples
###Bolt DB
A NOSQL GOLang native database that runs within your application
{
"driver" : "boltDB",
"connectionString" : "db/helloWorld.db"
}
###Mongo DB
A NOSQL database that runs outside your application
{
"driver" : "mongoDB",
"connectionString" : "mongodb://myuser:mypass@localhost:40001,otherhost:40001/mydb"
}
###SQLite3
A SQL Database instance running within your application
{
"driver" : "sqlite3",
"connectionString" : "db/helloWorld.db"
}
###MYSQL
A SQL Database instance running external to your application
{
"driver" : "mysql",
"connectionString" : " myUsername:myPassword@/HelloWorld"
}
###MS SQL Server
A SQL Database instance running external to your application
{
"driver" : "mssql",
"connectionString" : "server=myServerAddress;Database=HelloWorld;user id=myUsername;Password=myPassword;Connection Timeout=3000;"
}
| 27.331633 | 281 | 0.723166 | eng_Latn | 0.873563 |
54ad537da5f70dcc6e3380f0b6d4c77022de2a71 | 1,335 | md | Markdown | _talks/2022-03-30-tecnosocial.md | ihupont/ihupont.github.io | 1e1338a4bdfeaba8b7c2451457eb1ae984cb2f0b | [
"MIT"
] | null | null | null | _talks/2022-03-30-tecnosocial.md | ihupont/ihupont.github.io | 1e1338a4bdfeaba8b7c2451457eb1ae984cb2f0b | [
"MIT"
] | null | null | null | _talks/2022-03-30-tecnosocial.md | ihupont/ihupont.github.io | 1e1338a4bdfeaba8b7c2451457eb1ae984cb2f0b | [
"MIT"
] | null | null | null | ---
title: "Keynote speech at TECNOSOCIAL 2022"
collection: talks
type: "Talk"
permalink: /talks/2022-03-30-tecnosocial
venue: "University of Malaga"
date: 2022-03-30
location: "Malaga, Spain"
---
I was invited to give the closing keynote at [TECNOSOCIAL 2022](https://www.uma.es/fest/info/132684/tecnosocial-2022/).
Tecnosocial 2022 is a project promoted by the Department of Equality, Social Policies and Work-Life Balance of the Andalusian Regional Government, the Malaga Provincial Council and Malaga City Council. It is one of the actions included in the first Research and Innovation Plan for Social Services in Andalusia and aims to be a forum for analysis, dissemination, research and technological innovation in Social Services. The 2022 event brought together leading academics, scientists, industry professionals, third sector organisations, government authorities and national and international companies. The topics discussed have a great impact with an economic and social added value for the whole sector.
I presented [HUMAINT](https://ec.europa.eu/jrc/communities/en/community/humaint)'s research on trustworthy human-centred AI in a keynote speech entitled <i>AI and its impact on people from a European perspective: the example of facial analysis applications</i>.
<br> <br/><img src='/images/TECNOSOCIAL.jpg'>"
| 74.166667 | 704 | 0.799251 | eng_Latn | 0.98624 |
54ad84f3961f0f0aa8ed1b1984ffd7d1e2beb2b8 | 5,703 | md | Markdown | _posts/2020-09-27-the-making-of-valorant-throws.md | MYOOOTT/myooot.github.io | 0aeb9e24d78f786bb2745df9a15debf0883439a5 | [
"MIT"
] | null | null | null | _posts/2020-09-27-the-making-of-valorant-throws.md | MYOOOTT/myooot.github.io | 0aeb9e24d78f786bb2745df9a15debf0883439a5 | [
"MIT"
] | 3 | 2021-03-27T23:21:18.000Z | 2022-02-26T06:58:21.000Z | _posts/2020-09-27-the-making-of-valorant-throws.md | MYOOOTT/myooot.github.io | 0aeb9e24d78f786bb2745df9a15debf0883439a5 | [
"MIT"
] | null | null | null | ---
layout: post
title: "The making of Valorant Throws"
date: 2020-09-27
---
This will give an insight into how I came to solve a problem I was having as of late.
[Click here to go to the website!](https://valorant-throws.herokuapp.com/)
# The Problem
[Valorant](playvalorant.com) came out and I was absolutely obsessed with it. It's a 5v5 tactical shooter similar to Counter-Strike: Global Offensive (or CS:GO for short).
Valorant, like CS:GO, has the capacity to throw grenades across the map to set up strategies and gain an advantage by blocking vision or damaging enemies. The major difference was that in Valorant, each character (otherwise called agents) each had their own unique abilities - everyone in CS:GO had access to the same types of grenades.
However, for Valorant there wasn't a good place to find tutorials on how to do these setups - the main ways were to browse through Reddit or watch Youtube videos. This would lead to a ton of bookmarks and no one really likes that.
So I wanted to create a website that allowed for community input and would be a center for learning these setups or being a reference.
Specifically, here's what I wanted out of the website:
- as I emphasized before, allow users to submit their own lineups
- use gif / videos to portray how to do these, instead of using static images
- filtering by agent / map / ability
# Solution
I really liked the card-based look such as in <csgonades.com>, so I took a lot of inspiration from them.
Also, a couple of friends of mine suggested to take a look at the [Blitz](blitz.gg) app. They also use a card layout, but I really didn't like the way their lineups were titled or how the information was portrayed.
I'm Not Really Sure How People Can Read Posts Like This.
## Tech Stack
First thing that came to my mind on what to use to implement this was Flask or Django. I had used Flask briefly before in a hackathon and it seemed pretty simple to use. I wanted to stick with Python because I was entering a new area of programming and I wanted to start quickly on this project.
From looking online on comparisons on which to use, Django was touted as the framework to use in my situation since it generally "held your hand" more by providing a multitude of features such as:
- built-in Object Relation Mapping (ORM) and provided support for databases out of the box; I knew that I would have to be storing data somewhere and this wouldn't be just a single page app
- forms -> I had no idea how to make forms, I figured Django's class-based views would help me out here
This isn't a comprehensive list of the pros of Django at all, but this is what caught my eye. Mainly, the built-in ORM was the biggest feature that appealed to me. At the time, I didn't want to have to worry about how to deal with the database other than configuring it.
As for the front-end, it was pretty simple. I didn't really think I would have the need for a dynamic page, so just HTML and CSS would do the trick. Later, I would end up using Javascript for some very small "dynamicness" on a page, but that's about it.
In terms of how I was going to portray the gif / video of the lineup, I saw on [csgonades](csgonades.com) that it uses gfycat to display gifs. A quick google search for "gfycat iframe" gave me the [documentation](https://developers.gfycat.com/iframe/). Looking closer into the process of uploading a gif, gfycat allows you to add subtitles to video and has a very basic editor. I found this useful in providing more context/information when trying to demonstrate a lineup.
# Learning from this project
This is mainly for myself and to articulate what I have learned.
## Hidden inputs on forms
I had a problem with trying to save previous query parameters on a filter. I was using query parameters to filter through the different lineups, however at that moment I could only have one filter applied at a time.
I learned by using hidden fields, you could pre-populate those fields with your previous query parameters. In doing so, when you submit the "form" to filter out the lineups, it would save those hidden fields along with the additional filters applied.
## MVT structure, extended to MVC structure
On this, it's more just like working with these structures and knowing where to look if I wanted something done.
Normally in MVC (Model-View-Controller), the request to see the details of a object is created through the controller. The controller receives input and passes it to the model. The controller has the logic to retrieve the details of the object. The model manages and returns the data. Then, the object details are rendered in the view.
In Django however, it handles the logic in retrieving the object details where normally in MVC you would have to write it on your own.
## Relationships in Databases
Stuff like foreign keys, what fields are in a model, etc.
# Future Plans
At this point, the project hasn't really gotten a lot of traction in the Valorant community. Have lost a bit of motivation to keep making features for this when no one really uses it and lately I haven't been playing Valorant as much nor as competitively.
But if I were to be working on this again I would add:
- an interactive map like with [blitz](https://blitz.gg/valorant/maps/ascent)
- a system to personally review and accept/reject lineups people post, instead of automatically letting people post their lineups (which may lead to redundancies or loss of quality in lineups)
All in all, it was a great project to keep myself occupied in with the beginning of lockdown. | 74.064935 | 472 | 0.778362 | eng_Latn | 0.999873 |
54aebaa2ed21ccb350199c3872c9e0e63bc0680e | 874 | md | Markdown | content/momentum/web-ref/console_commands.message_fail.md | ahdvnd/developers.sparkpost.com | ff60f1f534d1bcf3b7bc85a6db58be2cf22978c3 | [
"MIT"
] | null | null | null | content/momentum/web-ref/console_commands.message_fail.md | ahdvnd/developers.sparkpost.com | ff60f1f534d1bcf3b7bc85a6db58be2cf22978c3 | [
"MIT"
] | null | null | null | content/momentum/web-ref/console_commands.message_fail.md | ahdvnd/developers.sparkpost.com | ff60f1f534d1bcf3b7bc85a6db58be2cf22978c3 | [
"MIT"
] | null | null | null | | | | |
| --- | --- | --- |
| [Prev](console_commands.message_details) | 12.2. System Console Commands | [Next](console_commands.message_fail_quiet.php) |
<a name="console_commands.message_fail"></a>
## Name
message fail — fail a message
## Synopsis
`message fail` { *`message_id`* }
<a name="idp16134640"></a>
## Description
This command takes a single argument in the form of a message id and will permanently fail the delivery of the message with the error: "554 manually failed."
<a name="idp16136400"></a>
## See Also
[message fail quiet](console_commands.message_fail_quiet "message fail quiet")
| | | |
| --- | --- | --- |
| [Prev](console_commands.message_details) | [Up](console.commands.non-module.php) | [Next](console_commands.message_fail_quiet.php) |
| message details | [Table of Contents](index) | message fail quiet |
| 31.214286 | 157 | 0.673913 | eng_Latn | 0.72017 |
54aed8e225e9fa4cc0d972cf02b8c02a5ea5af04 | 6,142 | md | Markdown | src/pages/products/hobbyist.md | maxmurdoch/flock | 98e6f1391beaa4469d1109c6607d90b719fdf650 | [
"MIT"
] | null | null | null | src/pages/products/hobbyist.md | maxmurdoch/flock | 98e6f1391beaa4469d1109c6607d90b719fdf650 | [
"MIT"
] | 1 | 2018-07-26T08:47:45.000Z | 2018-07-26T08:47:45.000Z | src/pages/products/hobbyist.md | maxmurdoch/flock | 98e6f1391beaa4469d1109c6607d90b719fdf650 | [
"MIT"
] | 2 | 2018-07-23T16:34:29.000Z | 2018-07-29T10:57:31.000Z | ---
title: Recreational
templateKey: product
hero:
backgroundImage: ../../images/uploads/hobbyist-header.jpg
button:
text: Download
to: /download
description: |-
* On-demand insurance from £2.95
* Short-term cover from 1-8 hours
* Public Liability insurance (£250,000)
* Real-time risk assessment
header: 'Pay-as-you-fly drone insurance for recreational pilots '
why:
description: >-
Enjoy your favourite hobby without worrying about insurance. Get covered
on-demand for the price of a coffee.
list:
- text: >-
Flock's pricing is risk-dependent, so the safer you fly, the less you
pay. Simple!
title: Fairer pricing
- text: >-
Insure your drone flight for as little as an hour, or up to a day. You
decide.
title: 'Short-term cover '
- text: >-
Get covered on the spot or plan a flight up to 10 days in advance. It
only takes 60 seconds.
title: SIMPLE INSURANCE
title: Why do recreational pilots fly with Flock?
flightSchool:
list:
- image: ../../images/uploads/uav-trade-craft.png
to: 'https://uavtradecraft.com/'
- image: ../../images/uploads/uav-hummingbird.png
to: 'https://www.hummingbird-uav.co.uk/'
- image: ../../images/uploads/flyby-technology-logo.png
to: 'https://www.flybydronetraining.co.uk/'
- image: ../../images/uploads/the-aerial-academy.png
to: 'https://dronetraining.co.uk/'
- image: ../../images/uploads/uav-academy.png
to: 'http://uavacademy.co.uk/'
- image: ../../images/uploads/aerial-motion-pictures.png
to: 'https://www.aerialmotionpictures.co.uk/'
- image: ../../images/uploads/3iC.png
to: 'https://3ic.co.uk/'
- image: ../../images/uploads/drone-partners.png
to: 'https://dronepartners.co.uk/'
show: false
title: Flock is proud to work with the leading flight schools in the UK
coverNote:
bodyText: >-
You no longer need to commit to an annual insurance policy in order to get
your proof of insurance for your PfCO renewal.
image: ../../images/uploads/cover-note.svg
isShowing: false
link:
text: Learn how to get your cover note within our app →
to: /download
smallText: >-
Flock’s Cover Note is accepted by the CAA as proof of EC785/2004 compliant
insurance, and you can get yours instantly without having to pay a penny.
title: Applying for your PfCO?
doINeedInsurance:
bigText: >-
Whilst it's not against the law in the UK to fly without insurance, a flying
robot with spinning propellers has the potential to cause some serious
damage.
Flock's Public Liability insurance starts from just £2.95, and gives you
peace of mind from the second you take off.
smallText: ''
title: |-
I fly my drone for fun,
do I need insurance?
how:
description: >-
Insuring your drone flight has never been simpler. All it takes is a matter
of taps on your mobile phone.
list:
- image: ../../images/uploads/screens/flight-details-screen.png
text: >-
Choose your flight area, and the date and time you want to fly. Receive
a real-time quote instantly.
title: 1. Enter your flight details
- image: ../../images/uploads/screens/customise-policy-home-screen.png
text: >-
Select how long you want to be insured for. With options from 1-8 hours,
get covered only for the hours you fly.
title: 2. Customise your policy
- image: ../../images/uploads/screens/get-flying-screen.png
text: >-
Pay and you're good to go! Your policy documents are instantly emailed
to you.
title: 3. Get flying
title: 'How Flock Cover works '
risk:
description: >-
With Flock Cover you get much more than just an insurance policy. The app
analyses real-time data in your Flight Area to instantly identify the
important risks before you take-off.
list:
- icon: ../../images/uploads/icons-house.svg
text: Flock Cover analyses building data to inform you of nearby schools hospitals and prisons.
title: Inhabited spaces
- icon: ../../images/uploads/icons-circle.svg
text: The app identifies high-risk areas such as power plants military bases and busy roads.
title: Ground hazards
- icon: ../../images/uploads/icons-plane.svg
text: Be alerted to surrounding airports and heliports and keep up to date with the latest NOTAMS.
title: Restricted airspace
- icon: ../../images/uploads/icons-cloud.svg
text: Receive hyper-local weather information such as wind speed temperature and probability of rainfall.
title: Hyperlocal weather
title: Know your risks before you fly
testimonial:
- author: 'David Dennison, Parrot Mambo FPV pilot'
image: /images/uploads/testimonial/[email protected]
quote: >-
“With all the current drone laws in the UK, having Flock is an added peace
of mind. Another bonus is that Flock will insure non professional drone
pilots. This is a brilliant app!”
- author: Ron Swanson
image: /images/uploads/testimonial/[email protected]
quote: >-
I hate drones. But I have one. And I insure my property because I'm a
responsible adult. Flock are the best drone insurers. I use Flock.
otherProducts:
description: >-
Chances are we can provide coverage tailored specifically to you. Select
below to learn more.
products:
- icon: /images/uploads/commercial-pilot.svg
link: /products/commercial
text: >-
Flock’s EC785/2004 compliant policies offer flexible hull and liability
insurance from just £4.95 a day.
title: Commercial pilot
- icon: /images/uploads/trainee-pilot.svg
link: /products/trainee
text: >-
From flight assessment insurance, to providing proof-of-insurance in
your PfCO application, Flock’s got you covered.
title: Trainee pilot
title: What kind of pilot are you?
siteMetadataOverride:
description: drone insurance
keywords:
- drones
- insurance
- on-demand
- Flock
- commercial drone insurance
title: Hobbyist
---
| 38.3875 | 111 | 0.679909 | eng_Latn | 0.98159 |
54aefc2821f60d0bfc6e34eaea1b843e99a219db | 1,360 | md | Markdown | doc/RELEASE-WORKFLOW.md | sketch7/ssv-ng2-core | 4eac1d4ca268f6aa4828dcd1ae9f6c57cd41ae6a | [
"MIT"
] | null | null | null | doc/RELEASE-WORKFLOW.md | sketch7/ssv-ng2-core | 4eac1d4ca268f6aa4828dcd1ae9f6c57cd41ae6a | [
"MIT"
] | null | null | null | doc/RELEASE-WORKFLOW.md | sketch7/ssv-ng2-core | 4eac1d4ca268f6aa4828dcd1ae9f6c57cd41ae6a | [
"MIT"
] | null | null | null | # Release workflow
In order to release follow the following procedure.
## Machine Setup
In order for this to work first need to setup github through cmd
### Auth to GitHub
Authenticate to github via username/password or SSH.
#### Username/Password Auth
- run `git config --global credential.helper wincred`
- this will persist the credentials (for windows)
- Trigger push command e.g.
```
git push origin develop
```
- Auth to github by providing username and password/token
# Create new Release
## New RC Release
RC release process
- Checkout `develop` branch (or release branch)
- Run `gulp publish`
## New Stable Release
Stable release process
- Checkout `master`
- Run `gulp publish --rel --bump major|minor|patch (default: patch)`
- Merge `master => develop`
# Gulp Release Commands
Commands in order to help release easier.
### Publish for RC
Quick publish an "RC", this will prepare release and commit.
```
gulp publish
```
### Publish Rel
Quick publish a stable release, this will prepare release and commit.
```
gulp publish --rel --bump major|minor|patch|prerelease (default: patch)
```
### Prepare-Release
Create a new build, test, bump version and generate changelog.
```
gulp prepare-release --bump major|minor|patch|prerelease (default: patch)
```
### Perform-Release
Commit, push and create tag.
```
gulp perform-release
``` | 22.666667 | 73 | 0.733088 | eng_Latn | 0.989148 |
54af273c272989a60f13295f710350e15b776e3c | 13 | md | Markdown | README.md | Felipe-Baz/Memories | 0d2ad79c4f5fd88047aa1d12f0861130e9dedeb4 | [
"MIT"
] | null | null | null | README.md | Felipe-Baz/Memories | 0d2ad79c4f5fd88047aa1d12f0861130e9dedeb4 | [
"MIT"
] | null | null | null | README.md | Felipe-Baz/Memories | 0d2ad79c4f5fd88047aa1d12f0861130e9dedeb4 | [
"MIT"
] | null | null | null | # Memories
| 4.333333 | 10 | 0.615385 | eng_Latn | 0.642989 |
54af43da953229e9dfe3fe99213f7a3c6eec87e2 | 14,248 | md | Markdown | C#/C# DB/DataBases Basics/09. EXAMS/20 Oct 2019/README.md | AntoniyaIvanova/SoftUni | 0219c55ca8514e16c3d927b926f3e7c9c4b9d8cd | [
"MIT"
] | null | null | null | C#/C# DB/DataBases Basics/09. EXAMS/20 Oct 2019/README.md | AntoniyaIvanova/SoftUni | 0219c55ca8514e16c3d927b926f3e7c9c4b9d8cd | [
"MIT"
] | null | null | null | C#/C# DB/DataBases Basics/09. EXAMS/20 Oct 2019/README.md | AntoniyaIvanova/SoftUni | 0219c55ca8514e16c3d927b926f3e7c9c4b9d8cd | [
"MIT"
] | null | null | null | # Database Basics MS SQL Exam – 20 Oct 2019
Exam problems for the [“Database Basics MSSQL Server” course @
SoftUni](https://softuni.bg/opencourses/ms-sql)" Submit your solutions
in the SoftUni judge system at Software University.
# Service
The city mayor, came up with the idea to create an online platform where
all the citizens can **report about different problems** and a special
organization will work to resolve all the incoming reports. This
organization has a few **departments each of which is responsible for a
set of problem's categories** in which **users can submit a report**. In
each department there are employees who get assigned to a report. Of
course, this huge platform needs a reliable database to store and
process the information and the mayor has asked for the best specialist
in this area. That’s why you got chosen\! Congratulations and good
luck\!
# Section 1. DDL (**30 pts)**
You have been given the E/R Diagram of the Report Service:
Create a database called **Service**. You need to create **6 tables**:
- **Users** - contains information about the people who submist
reports
- **Reports** - contains information about the problems
- **Employees** - contains information about the employees
- **Departments** - contains information about the departments
- **Categories** - contains information about categories in reports.
- **Status** - contains information about the possible
Users
| **Column Name** | **Data Type** | **Constraints** |
| --------------- | --------------------------------------- | -------------------------------------------------------- |
| Id | Integer from **0** **to 2,147,483,647** | **Unique** table identificator, **Identity.** |
| Username | String up to **30 symbols** | **Unique** for each user, **NULL** is **NOT** permitted. |
| Password | String up to **50 symbols** | **NULL** is **NOT** permitted. |
| Name | String up to **50 symbols** | **NULL** is permitted. |
| Birthdate | Date **with time** | **NULL** is permitted. |
| Age | Integer from **0 to 2,147,483,647** | In range between **14** and **110 (inclusive).** |
| Email | String up to **50 symbols** | **NULL** is **NOT** permitted. |
Departments
| **Column Name** | **Data Type** | **Constraints** |
| --------------- | ----------------------------------- | --------------------------------------------- |
| Id | Integer from **0 to 2,147,483,647** | **Unique** table identificator, **Identity.** |
| Name | String up to 50 symbols | **NULL** is **NOT** permitted. |
Employees
| **Column Name** | **Data Type** | **Constraints** |
| --------------- | ----------------------------------- | ------------------------------------------------ |
| Id | Integer from **0 to 2,147,483,647** | **Unique** table identificator, **Identity.** |
| FirstName | String up to **25 symbols** | **NULL** is permitted. |
| LastName | String up to **25 symbols** | **NULL** is permitted. |
| Birthdate | Date **with time** | **NULL** is permitted. |
| Age | Integer from **0 to 2,147,483,647** | In range between **18** and **110 (inclusive).** |
| DepartmentId | Integer from **0 to 2,147,483,647** | Relationship with table **departments**. |
Categories
| **Column Name** | **Data Type** | **Constraints** |
| --------------- | ----------------------------------- | ------------------------------------------------------------------------ |
| Id | Integer from **0 to 2,147,483,647** | **Unique** table identificator, **Identity.** |
| Name | String up to **50 symbols** | **NULL** is **NOT** permitted. |
| DepartmentId | Integer from **0 to 2,147,483,647** | Relationship with table **departments**. **NULL** is **NOT** permitted . |
Status
| **Column Name** | **Data Type** | **Constraints** |
| --------------- | ----------------------------------- | --------------------------------------------- |
| Id | Integer from **0 to 2,147,483,647** | **Unique** table identificator, **Identity.** |
| Label | String up to **30 symbols** | **NULL** is **NOT** permitted. |
Reports
| **Column Name** | **Data Type** | **Constraints** |
| --------------- | ----------------------------------- | ---------------------------------------------------------------------- |
| Id | Integer from **0 to 2,147,483,647** | **Unique** table identificator, **Identity.** |
| CategoryId | Integer from **0 to 2,147,483,647** | Relationship with table **categories**. **NULL** is **NOT** permitted. |
| StatusId | Integer from **0 to 2,147,483,647** | Relationship with table **status**. **NULL** is **NOT** permitted. |
| OpenDate | Date **with time** | **NULL** is **NOT** permitted. |
| CloseDate | Date **with time** | **NULL** is permitted. |
| Description | String up to **200 symbols** | **NULL** is **NOT** permitted. |
| UserId | Integer from **0 to 2,147,483,647** | Relationship with table **users**. **NULL** is **NOT** permitted. |
| EmployeeId | Integer from **0 to 2,147,483,647** | Relationship with table **employees**. |
## Table design
Submit all of your **create statements** to Judge.
# Section 2. DML (**10 pts)**
**<span class="underline">Before you start you have to import
"DataSet-Service.sql". If you have created the structure correctly the
data should be successfully inserted.</span>**
In this section, you have to do some data manipulations:
## Insert
Let's **insert** some sample data into the database. Write a query to
add the following records into the corresponding tables. All Id's should
be auto-generated.
**Employees**
| **FirstName** | **LastName** | **Birthdate** | **DepartmentId** |
| ------------- | ------------ | ------------- | ---------------- |
| Marlo | O'Malley | 1958-9-21 | 1 |
| Niki | Stanaghan | 1969-11-26 | 4 |
| Ayrton | Senna | 1960-03-21 | 9 |
| Ronnie | Peterson | 1944-02-14 | 9 |
| Giovanna | Amati | 1959-07-20 | 5 |
**Reports**
| **CategoryId** | **StatusId** | **OpenDate** | **CloseDate** | **Description** | **UserId** | **EmployeeId** |
| -------------- | ------------ | ------------ | ------------- | ----------------------------- | ---------- | -------------- |
| 1 | 1 | 2017-04-13 | | Stuck Road on Str.133 | 6 | 2 |
| 6 | 3 | 2015-09-05 | 2015-12-06 | Charity trail running | 3 | 5 |
| 14 | 2 | 2015-09-07 | | Falling bricks on Str.58 | 5 | 2 |
| 4 | 3 | 2017-07-03 | 2017-07-06 | Cut off streetlight on Str.11 | 1 | 1 |
## Update
Update the CloseDate with the current date of all reports, which don't
have CloseDate.
## Delete
Delete **all reports** who have a **Status** **4**.
# Section 3. Querying (**40 pts)**
**<span class="underline">You need to start with a fresh dataset, so
recreate your DB and import the sample data again
(DataSet-Service.sql).</span>**
## Unassigned Reports
Find all **reports** that **don't** have an **assigned employee**.
**Order** the results by **OpenDate** in **ascending** order, then by
**description ascending**. **OpenDate** must be in format -
**'dd-MM-yyyy'**
### Example:
| **Description** | **OpenDate** |
| ------------------------- | ------------ |
| Art exhibition on July 24 | 17-12-2014 |
| Stuck Road on Str.133 | 20-06-2015 |
| Burned facade on Str.560 | 26-08-2015 |
## Reports & Categories
Select all **descriptions** from reports, which have **category**. Order
them by description (**ascending**) then by category name
(**ascending**).
### Example:
| **Description** | **CategoryName** |
| ----------------------------- | ---------------- |
| 162 kg plastic for recycling. | Green Areas |
| 246 kg plastic for recycling. | Snow Removal |
| 366 kg plastic for recycling. | Recycling |
## Most Reported Category
Select the **top 5 most reported categories** and **order** them **by**
the number of **reports** **per category** in **descending** order and
then **alphabetically** by **name**.
### Example:
| **CategoryName** | **ReportsNumber** |
| ---------------- | ----------------- |
| Recycling | 8 |
| Snow Removal | 5 |
| Streetlight | 4 |
## Birthday Report
Select the user's **username** and **category name** in all **reports**
in which **users** have submitted a report **on their birthday**.
**Order** them by **username** (**ascending**) and then by **category
name** (**ascending**).
### Example:
| **Username** | **CategoryName** |
| ------------- | ---------------- |
| 5omarkwelleyc | Snow Removal |
| dpennid | Dangerous Trees |
| llankham6 | Homeless Elders |
## Users per Employee
Select **all** **employees** and show how many **unique** users each of
them has served to.
Order by **users count** (**descending**) and then by **full** **name**
(**ascending**).
### Example:
| | |
| -------------- | -------------- |
| **FullName** | **UsersCount** |
| Bron Ledur | 3 |
| Adelind Benns | 2 |
| Dick Wentworth | 2 |
| … | … |
## Full Info
Select **all info** for reports along with employee **first name** and
**last name** (**concataned with space**), **department name**,
**category name**, **report description**, **open date**, **status
label** and **name of the user**. Order them by first name
(**descending**), last name (**descending**), department
(**ascending**), category (**ascending**), description (**ascending**),
open date (**ascending**), status (**ascending**) and user
(**ascending**).
Date should be in format - **dd.MM.yyyy**
If there are empty records, replace them with '**None**'.
### Example:
| | | | | | | |
| ----------------- | ---------------- | ---------------- | -------------------------------------------------- | ------------ | ----------- | ----------------- |
| **Employee** | **Department** | **Category** | **Description** | **OpenDate** | **Status** | **User** |
| Niki Stranaghan | Event Management | Sports Events | Sky Run competition on September 8 | 08.06.2015 | Completed | Emlynn Alliberton |
| Marlo O'Malley | Infrastructure | Streetlight | Fallen streetlight columns on Str.14 | 12.09.2017 | Blocked | Erhart Alpine |
| Leonardo Shopcott | Animals Care | Animal in Danger | Parked car on green area on the sidewalk of Str.74 | 10.11.2016 | In Progress | Jocko Greggor |
| … | …. | … | … | … | … | … |
# Section 4. Programmability (**20 pts)**
## Hours to Complete
Create a **user defined function** with the name
**udf\_HoursToComplete(@StartDate** **DATETIME, @EndDate** **DATETIME)**
that receives a start date and end date and must returns the total hours
which has been taken for this task. If start date is null or end is null
return 0.
### Example usage:
<table>
<tbody>
<tr class="odd">
<td><strong>Query</strong></td>
</tr>
<tr class="even">
<td><p>SELECT dbo.udf_HoursToComplete(OpenDate, CloseDate) AS TotalHours</p>
<p>FROM Reports</p></td>
</tr>
<tr class="odd">
<td>TotalHours</td>
</tr>
<tr class="even">
<td>0</td>
</tr>
<tr class="odd">
<td>120</td>
</tr>
<tr class="even">
<td>0</td>
</tr>
</tbody>
</table>
## Assign Employee
Create a **stored procedure** with the name
**usp\_AssignEmployeeToReport(@EmployeeId INT, @ReportId INT)** that
receives an **employee's Id** and a **report's Id** and assigns the
employee to the report **only if** the department of the employee and
the department of the report's category are the same. Otherwise throw an
**exception** with message: "Employee doesn't belong to the appropriate
department\!".
### Example usage:
| |
| ------------------------------------------------------- |
| **Query** |
| EXEC usp\_AssignEmployeeToReport 30, 1 |
| **Response** |
| Employee doesn't belong to the appropriate department\! |
| **Query** |
| EXEC usp\_AssignEmployeeToReport 17, 2 |
| **Response** |
| (1 row affected) |
#
| 45.666667 | 161 | 0.473891 | eng_Latn | 0.890069 |
54af5c80fee261a5dbfb87252c82810a895079a0 | 1,483 | md | Markdown | _posts/2019-03-17-Download-para-set-ref-no-3-laminated-cover.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2019-03-17-Download-para-set-ref-no-3-laminated-cover.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2019-03-17-Download-para-set-ref-no-3-laminated-cover.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Para set ref no 3 laminated cover book
He has no guardian but himself, and that makes you angry. "I have come," he said. Humanity doesn't belong here. "Well, a charcoal burner from Firn. ' Para set ref no 3 laminated cover end, cows. He returned through Yugor advantage of the ear-drums of the travellers. colored sheets of sailboats. ' insects in a land which is exposed to a winter cold below the of level terraces rising one above the other, reached Stockholm on the 23rd November and St, but I'd rather you didn't disturb him until tomorrow. should darken the hair. It takes about para set ref no 3 laminated cover an boor; so we couldn't get out hi time to meet you? There was some mystery or shame connected with Ard. Notwithstanding the exceedingly severe cold a woman here the father, Agnes realized that this was not a prayer for the soul of a my existence. It was traveling, But when Hinda came out of the door. " She almost left? series of convenient rides had taken them. Neither of them was aware that their personal drama, she'll need to speak to me directly. The sparkweed, Junior had nothing to gain by talking to him, talking about someone else. Then he likely, though, who appear to have at that time frequently visited North life should not suffer any harm from the complete darkness. child with anyone, with caretaker and the dog, Junior gathered an electric razor and toiletries. Ron Hubbard. | 164.777778 | 1,376 | 0.781524 | eng_Latn | 0.99992 |
54af7beb3408552a6708dca8f59c9b1d258a92d0 | 1,752 | md | Markdown | _posts/2018-09-01-travel-moving-to-cern.md | ExcitedPositron/excitedpositron.github.io | e97597d50416ff1e87916496ca00986fdde17030 | [
"MIT"
] | null | null | null | _posts/2018-09-01-travel-moving-to-cern.md | ExcitedPositron/excitedpositron.github.io | e97597d50416ff1e87916496ca00986fdde17030 | [
"MIT"
] | null | null | null | _posts/2018-09-01-travel-moving-to-cern.md | ExcitedPositron/excitedpositron.github.io | e97597d50416ff1e87916496ca00986fdde17030 | [
"MIT"
] | null | null | null | ---
layout: post
title: "CERN - moving in longterm"
date: 2018-09-01
excerpt: "The big move to CERN."
life: true
comments: true
feature: /assets/img/posts/cern2.jpg
---
Moving to CERN didn't seem like a big deal to me in the first instant. It is just living in a new country and I have done that many times over the past few years, so it shouldn't be so hard, right? Well I am here for over a month now and few of my plants haven't yet recovered from the move. One of them died already.
CERN is a great place to be and I love it here! However some things are so different I have to note them here. Lets start with the bad things, not that I like to complain, but it has to be said. First of all, stores are closed on Sunday! Like groceries and all. I have been taking it for granted to go buy food on my day off. No, not ok to do so anymore.
Also, things are expensive here. Going out for dinner is a thing for the rich and shopping is narrowed to necessities. Living on the boarder with Switzerland influences the price of living.
Now the good things, the landscapes here are amazing. I can see the Alps and the Jura mountains from work or while spending an evening by the Lake Geneva and it makes me enjoy my life here so much. The nature is really beautiful around here. It also generates infinite possibilities for hiking during weekends.
<figure>
<a href="/assets/img/posts/cern1.JPG"><img src="/assets/img/posts/cern1.JPG"></a>
<figcaption>On top of Le Mol with views of Mont Blanc.</figcaption>
</figure>
Well I started my life on the French/Swiss border working at the largest particle physics lab in the world and I am so happy I got this opportunity through my PhD. Thanks for reading!
{% include subscribe.html %}
| 62.571429 | 354 | 0.753995 | eng_Latn | 0.999827 |
54afbc339fbe1843621ed2ad6a8d0b40a5400633 | 8,182 | md | Markdown | README.md | mredig/conference-contacts-ios | e53429af5438dd6ec8d45be1b779438941bcb953 | [
"MIT"
] | null | null | null | README.md | mredig/conference-contacts-ios | e53429af5438dd6ec8d45be1b779438941bcb953 | [
"MIT"
] | null | null | null | README.md | mredig/conference-contacts-ios | e53429af5438dd6ec8d45be1b779438941bcb953 | [
"MIT"
] | null | null | null |
<img src="Screenshots/swaaplogoblue.svg" width="400">
## 9 Contributors
| [Marlon Raskin][MarlonLink] | [Michael Redig][MichaelLink] | [Jonathan Picazzo][JonathanLink] | [Bobby Hall][BobbyLink] | [Tyler Quinn][QuinnLink] | [Emily Arias][EmilyLink] | [Jarvise Billups][JarviseLink] | [Tyler Nishida][TylerLink] | [Zachary Peasley][ZackLink] |
| :-----------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: | :-----------------------------------------------------------------------------------------------------------: |
| [<img src="https://ca.slack-edge.com/T4JUEB3ME-UHUR873EV-d88881406d1d-512" width = "200" />][MarlonLink] | [<img src="https://ca.slack-edge.com/T4JUEB3ME-UHF67A9T9-a3fb05aba2cd-512" width = "200" />][MichaelLink] | [<img src="https://avatars0.githubusercontent.com/u/8473052?s=400&v=4" width = "200" />][JonathanLink] | [<img src="https://avatars1.githubusercontent.com/u/29504858?s=400&v=4" width = "200" />][BobbyLink] | [<img src="https://avatars3.githubusercontent.com/u/52711778?s=400&v=4" width = "200" />][QuinnLink] | [<img src="https://ca.slack-edge.com/T4JUEB3ME-UGVBY5QK0-0322eb799fbf-512" width = "200" />][EmilyLink] | [<img src="https://ca.slack-edge.com/T4JUEB3ME-UHV013MQF-3a9d77644b52-512" width = "200" />][JarviseLink] | [<img src="https://avatars3.githubusercontent.com/u/49229588?s=400&v=4" width = "200" />][TylerLink] | [<img src="https://ca.slack-edge.com/T4JUEB3ME-UJG8RLWKG-3766d295008c-512" width = "200" />][ZackLink] |
| [<img src="https://github.com/favicon.ico" width="15"> ][MarlonLink] | [<img src="https://github.com/favicon.ico" width="15"> ][MichaelLink] | [<img src="https://github.com/favicon.ico" width="15"> ][JonathanLink] | [<img src="https://github.com/favicon.ico" width="15"> ][BobbyLink] | [<img src="https://github.com/favicon.ico" width="15"> ][QuinnLink] | [<img src="https://github.com/favicon.ico" width="15"> ][EmilyLink] | [<img src="https://github.com/favicon.ico" width="15"> ][JarviseLink] | [<img src="https://github.com/favicon.ico" width="15"> ][TylerLink] | [<img src="https://github.com/favicon.ico" width="15"> ][ZackLink] |
[![Swift Version][swift-image]][swift-url] [![License][license-image]][license-url] [](https://github.com/Carthage/Carthage)
## Project Overview
* You can find the deployed project at [Swaap on TestFlight](https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/app/1489988902/testflight?section=build&subsection=testers&id=58839d93-df6a-4175-9163-018050500150).
* [Trello Board](https://trello.com/b/Jh8cS46t/conference-contacts)
* [Product Canvas](https://www.notion.so/Release-1-0-Auth-User-Profile-7abf0ffafe804fc88e9af40ed335f17b)
* [UX Design files](https://www.figma.com/file/CkvwWMzxcI4lI4udHm8QiH/Labs18_Conference-Contacts%2C-Emily%2CTylerr?node-id=211%3A5)
Swaap is an app to help professional people make great contacts at events such as conferences, conventions, or trade shows. A lot of times it can be difficult to keep track of the people you've added to your network. Swaap makes it super easy to swap contact information with others and keep in touch. Easy QR code reader or NFC will automatically redirect you to that person's profile page where you are shown many different ways to connect with that person. Their profile will even let you know what the best way to get in touch with them.
<img src="Screenshots/girlLightFrontOfCard.png" width="400"> <img src="Screenshots/guyDarkFronOfCard.png" width="400">
<img src="Screenshots/girlLightBackOfCard.png" width="400"> <img src="Screenshots/guyDarkBackOfcard.png" width="400">
### Features
- Connect to other users easily via NFC or QR code/reader
- Easily keep tabs on how well you are keeping in touch with your professional contacts
- Keep track of how you met your contacts and notes about them or how you met
- swaap acts as a hub for all the ways you can be contacted by the people in your network
### Authentication API - Auth0
Auth0 provides a universal authentication & authorization platform for web, mobile and legacy applications.
Using Auth0, developers can connect any application written in any language or stack, and define the external identity providers, as well as integrations, that they want to use.
### Cloudinary API
Securely upload & store as many images and videos as needed, at any scale, from any source. Use a powerful API for fast upload directly from users’ browsers or mobile apps. Rest easy with auto-backups, historical revisions, and flexible storage options.
## Requirements
- iOS 13.0+
- Xcode 11.0
- Carthage
## Contribution
Please go [here](Contributing.md)
## Documentation
See [Backend Documentation](https://github.com/Lambda-School-Labs/conference-contacts-be/blob/staging/schema.md) for details on the backend of our project.
See [Frontend Here](https://github.com/Lambda-School-Labs/conference-contacts-fe)
<!-- Names + GitHub -->
[MarlonLink]: https://github.com/marlonjames71
[MichaelLink]: https://github.com/mredig
[JonathanLink]: https://github.com/macjabeth
[BobbyLink]: https://github.com/bobbyhalljr
[QuinnLink]: https://github.com/Bangstry
[EmilyLink]: https://github.com/Ehuntwork
[JarviseLink]: https://github.com/Fullmetal235
[TylerLink]: https://github.com/tylernishida
[ZackLink]: https://github.com/zpallday
<!-- Photos -->
[MarPhoto]: <img src="https://ca.slack-edge.com/T4JUEB3ME-UHUR873EV-d88881406d1d-512" width = "200" />
[MarlonPhoto]: https://ca.slack-edge.com/T4JUEB3ME-UHUR873EV-d88881406d1d-512
[MichaelPhoto]: https://ca.slack-edge.com/T4JUEB3ME-UHF67A9T9-a3fb05aba2cd-512
[JonathanPhoto]: https://avatars0.githubusercontent.com/u/8473052?s=400&v=4
[BobbyPhoto]: https://avatars1.githubusercontent.com/u/29504858?s=400&v=4
[QuinnPhoto]: https://avatars3.githubusercontent.com/u/52711778?s=400&v=4
[EmilyPhoto]: https://ca.slack-edge.com/T4JUEB3ME-UGVBY5QK0-0322eb799fbf-512
[JarvisePhoto]: https://ca.slack-edge.com/T4JUEB3ME-UHV013MQF-3a9d77644b52-512
[TylerPhoto]: https://avatars3.githubusercontent.com/u/49229588?s=400&v=4
[ZackPhoto]: https://ca.slack-edge.com/T4JUEB3ME-UJG8RLWKG-3766d295008c-512
<!-- Badges -->
[swift-image]: https://img.shields.io/badge/swift-5.1-orange.svg
[swift-url]: https://swift.org/
[license-image]: https://img.shields.io/badge/License-MIT-blue.svg
[license-url]: LICENSE
| 88.934783 | 1,009 | 0.567221 | yue_Hant | 0.551014 |
54b0236908c94abef5a5ea1d6a5c5795ead36e56 | 1,405 | md | Markdown | content/posts/release-3-2-0/README.md | dkapanidis/www.kubernetic.com | d04eb12decd6b5b4bc1b21d3f6f021d2b0b6b243 | [
"MIT"
] | null | null | null | content/posts/release-3-2-0/README.md | dkapanidis/www.kubernetic.com | d04eb12decd6b5b4bc1b21d3f6f021d2b0b6b243 | [
"MIT"
] | null | null | null | content/posts/release-3-2-0/README.md | dkapanidis/www.kubernetic.com | d04eb12decd6b5b4bc1b21d3f6f021d2b0b6b243 | [
"MIT"
] | null | null | null | ---
title: 'Kubernetic v3.2.0 Released'
excerpt: 'Release v3.2.0 is out with bug fixes and maintaince tasks.'
date: '2022-02-01'
---
Release v3.2.0 is out with bug fixes and maintaince tasks. You can check the complete list of changes on the [changelog](https://docs.kubernetic.com/changelog.html).
## Fix breaking changes introduced on Control Plane 1.20+
Kubernetes control plane deprecated use of `metadata.selfLink` field [here](https://github.com/kubernetes/kubernetes/pull/80978) in individual and list objects. The selfLink field was used in Kubernetic as a reference to track changes on UI, which had the effect of disappearing resources when listed.
This is now fixed by using the `metadata.uid` field instead to track changes.
## Change Font Size
Depending on your display resolution the default font size may not be the optimal for your setup. Now there is an option to zoom in/out to better customize your app.
## Linux version Self Updates
Mac version always had the option to self update the version, but in Linux there was an issue that made a popup display the following error `Error Updating: There seems to be some connectivity issue.`.
This is now fixed by updating the electron builder responsible for the packaging of Linux app. The app is now been distributed using `AppImage` format instead of `tar.gz` which is more widely used.
| 54.038462 | 301 | 0.776512 | eng_Latn | 0.998823 |
54b08f7c059bc85ffbcb52b8fb2122ccbf8a70f1 | 416 | md | Markdown | sources/api/sundog/README.md | zxb789/bottlerocket | b785d20538a9349487d96beca4e6de53eec5fca7 | [
"Apache-2.0",
"MIT"
] | 6,422 | 2020-03-10T19:06:18.000Z | 2022-03-31T18:47:38.000Z | sources/api/sundog/README.md | zxb789/bottlerocket | b785d20538a9349487d96beca4e6de53eec5fca7 | [
"Apache-2.0",
"MIT"
] | 851 | 2020-03-11T01:51:00.000Z | 2022-03-31T23:26:56.000Z | sources/api/sundog/README.md | zxb789/bottlerocket | b785d20538a9349487d96beca4e6de53eec5fca7 | [
"Apache-2.0",
"MIT"
] | 350 | 2020-03-10T18:54:33.000Z | 2022-03-30T18:21:23.000Z | # sundog
Current version: 0.1.0
## Introduction
sundog is a small program to handle settings that must be generated at OS runtime.
It requests settings generators from the API and runs them.
The output is collected and sent to a known Bottlerocket API server endpoint.
## Colophon
This text was generated using [cargo-readme](https://crates.io/crates/cargo-readme), and includes the rustdoc from `src/main.rs`. | 29.714286 | 129 | 0.776442 | eng_Latn | 0.998278 |
54b20deb0276da026bd74a2cf698e497a69ad636 | 9,104 | md | Markdown | source/includes/_colour.md | benh-gds/gov-docs-test | 384b414069cb7fa445273b94a953a5a8ffb8faa5 | [
"Apache-2.0"
] | 1 | 2016-11-01T11:09:39.000Z | 2016-11-01T11:09:39.000Z | source/includes/_colour.md | benh-gds/gov-docs-test | 384b414069cb7fa445273b94a953a5a8ffb8faa5 | [
"Apache-2.0"
] | null | null | null | source/includes/_colour.md | benh-gds/gov-docs-test | 384b414069cb7fa445273b94a953a5a8ffb8faa5 | [
"Apache-2.0"
] | 3 | 2016-10-14T11:53:26.000Z | 2021-04-10T20:00:18.000Z | # Colour
Always use the GOV.UK colour palette.
## Colour contrast
The colour contrast ratio for text and interactive elements should be at least 4.5:1 [as recommended by the W3C](http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html). Test your service to meet this standard.
## SASS variables
Use Sass variables in case colour values need to be updated – find these in the GOV.UK frontend toolkit [colours.scss]( https://github.com/alphagov/govuk_frontend_toolkit/blob/master/stylesheets/_colours.scss) file.
<div class="sizer">
<div class="example">
<div class="swatch-wrapper">
<h4 class="heading-small">Text</h4>
<div class="swatch swatch-text-colour"></div>
<ul>
<li><b>#0B0C0C</b></li>
<li>$text-colour</li>
</ul>
<div class="swatch swatch-text-secondary"></div>
<ul>
<li><b>#6F777B</b></li>
<li>$secondary-text-colour</li>
</ul>
<div class="swatch swatch-page-colour"></div>
<ul>
<li><b>#FFFFFF</b></li>
<li>$page-colour</li>
</ul>
</div>
<div class="swatch-wrapper">
<h4 class="heading-small">Links</h4>
<div class="swatch swatch-link-colour"></div>
<ul>
<li><b>#005ea5</b></li>
<li>$link-colour</li>
</ul>
<div class="swatch swatch-link-colour-hover"></div>
<ul>
<li><b>#2b8cc4</b></li>
<li>$link-hover-colour</li>
</ul>
<div class="swatch swatch-link-colour-visited"></div>
<ul>
<li><b>#4c2c92</b></li>
<li>$link-visited-colour</li>
</ul>
</div>
<div class="swatch-wrapper">
<h4 class="heading-small">Backgrounds</h4>
<div class="swatch swatch-border-colour"></div>
<ul>
<li><b>#BFC1C3</b></li>
<li>$border-colour</li>
</ul>
<div class="swatch swatch-panel-colour"></div>
<ul>
<li><b>#DEE0E2</b></li>
<li>$panel-colour</li>
</ul>
<div class="swatch swatch-highlight-colour"></div>
<ul>
<li><b>#F8F8F8</b></li>
<li>$highlight-colour</li>
</ul>
</div>
<div class="swatch-wrapper">
<h4 class="heading-small">Buttons</h4>
<div class="swatch swatch-button-colour"></div>
<ul>
<li><b>#00823B</b></li>
<li>$button-colour</li>
</ul>
<div class="swatch swatch-green"></div>
<ul>
<li><b>#006435</b></li>
<li>$green (hover colour)</li>
</ul>
</div>
<div class="swatch-wrapper">
<h4 class="heading-small">Focus</h4>
<div class="swatch swatch-yellow"></div>
<ul>
<li><b>#FFBF47</b></li>
<li>$focus-colour</li>
</ul>
</div>
</div>
</div>
## Status colours
<div class="sizer">
<div class="example">
<div class="swatch-wrapper">
<div class="swatch swatch-alpha"></div>
<ul>
<li><b>#d53880</b></li>
<li>$alpha-colour</li>
</ul>
</div>
<div class="swatch-wrapper">
<div class="swatch swatch-beta"></div>
<ul>
<li><b>#f47738</b></li>
<li>$beta-colour</li>
</ul>
</div>
<div class="swatch-wrapper">
<div class="swatch swatch-discovery"></div>
<ul>
<li><b>#912b88</b></li>
<li>$discovery-colour</li>
</ul>
</div>
<div class="swatch-wrapper">
<div class="swatch swatch-live"></div>
<ul>
<li><b>#85994b</b></li>
<li>$live-colour</li>
</ul>
</div>
<div class="swatch-wrapper">
<div class="swatch swatch-error"></div>
<ul>
<li><b>#B10E1E</b></li>
<li>$error-colour</li>
</ul>
</div>
</div>
</div>
## Greyscale palette
<div class="sizer">
<div class="example">
<div class="swatch-wrapper">
<div class="swatch swatch-black"></div>
<ul>
<li><b>#0B0C0C</b></li>
<li>$black</li>
</ul>
</div>
<div class="swatch-wrapper">
<div class="swatch swatch-grey-1"></div>
<ul>
<li><b>#6F777B</b></li>
<li>$grey-1</li>
</ul>
</div>
<div class="swatch-wrapper">
<div class="swatch swatch-grey-2"></div>
<ul>
<li><b>#BFC1C3</b></li>
<li>$grey-2</li>
</ul>
</div>
<div class="swatch-wrapper">
<div class="swatch swatch-grey-3"></div>
<ul>
<li><b>#DEE0E2</b></li>
<li>$grey-3</li>
</ul>
</div>
<div class="swatch-wrapper">
<div class="swatch swatch-grey-4"></div>
<ul>
<li><b>#F8F8F8</b></li>
<li>$grey-4</li>
</ul>
</div>
</div>
</div>
## Extended palette
<div class="sizer">
<ul class="list list-bullet text">
<li>used for graphs and supporting material</li>
<li>for tints of the extended palette use 50% or 25%</li>
<li>for departmental colours
– find these in the GOV.UK frontend toolkit <a href="https://github.com/alphagov/govuk_frontend_toolkit/blob/master/stylesheets/colours/_organisation.scss" rel="external">organisation.scss file</a></li>
</ul>
</div>
<div class="sizer">
<div class="example">
<div class="swatch-wrapper">
<h4 class="heading-small">Purple</h4>
<div class="swatch swatch-purple"></div>
<ul>
<li><b>#2e358b</b></li>
<li>$purple</li>
</ul>
<h4 class="heading-small">Mauve</h4>
<div class="swatch swatch-mauve"></div>
<ul>
<li><b>#6f72af</b></li>
<li>$mauve</li>
</ul>
<h4 class="heading-small">Fuschia</h4>
<div class="swatch swatch-fuschia"></div>
<ul>
<li><b>#912b88</b></li>
<li>$fuschia</li>
</ul>
</div>
<div class="swatch-wrapper">
<h4 class="heading-small">Pink</h4>
<div class="swatch swatch-pink"></div>
<ul>
<li><b>#d53880</b></li>
<li>$pink</li>
</ul>
<h4 class="heading-small">Baby pink</h4>
<div class="swatch swatch-baby-pink"></div>
<ul>
<li><b>#f499be</b></li>
<li>$baby-pink</li>
</ul>
<h4 class="heading-small">Red</h4>
<div class="swatch swatch-red"></div>
<ul>
<li><b>#b10e1e</b></li>
<li>$red</li>
</ul>
</div>
<div class="swatch-wrapper">
<h4 class="heading-small">Mellow red</h4>
<div class="swatch swatch-mellow-red"></div>
<ul>
<li><b>#df3034</b></li>
<li>$mellow-red</li>
</ul>
<h4 class="heading-small">Orange</h4>
<div class="swatch swatch-orange"></div>
<ul>
<li><b>#f47738</b></li>
<li>$orange</li>
</ul>
<h4 class="heading-small">Brown</h4>
<div class="swatch swatch-brown"></div>
<ul>
<li><b>#b58840</b></li>
<li>$brown</li>
</ul>
</div>
<div class="swatch-wrapper">
<h4 class="heading-small">Yellow</h4>
<div class="swatch swatch-yellow"></div>
<ul>
<li><b>#ffbf47</b></li>
<li>$yellow</li>
</ul>
<h4 class="heading-small">Green</h4>
<div class="swatch swatch-green"></div>
<ul>
<li><b>#006435</b></li>
<li>$green</li>
</ul>
<h4 class="heading-small">Grass green</h4>
<div class="swatch swatch-grass-green"></div>
<ul>
<li><b>#85994b</b></li>
<li>$grass-green</li>
</ul>
</div>
<div class="swatch-wrapper">
<h4 class="heading-small">Turquoise</h4>
<div class="swatch swatch-turquoise"></div>
<ul>
<li><b>#28a197</b></li>
<li>$turquoise</li>
</ul>
<h4 class="heading-small">Light blue</h4>
<div class="swatch swatch-light-blue"></div>
<ul>
<li><b>#2b8cc4</b></li>
<li>$light-blue</li>
</ul>
<h4 class="heading-small">GOV.UK blue</h4>
<div class="swatch swatch-govuk-blue"></div>
<ul>
<li><b>#005ea5</b></li>
<li>$govuk-blue</li>
</ul>
</div>
</div>
</div>
[Discuss colour on the design patterns Hackpad](https://designpatterns.hackpad.com/Colour-PDuGV42pJqx)
## Examples
### Transaction end page
<div class="sizer">
<div class="example">
<div class="grid-row">
<div class="column-two-thirds">
<p class="heading-xlarge">
Example service name
</p>
<div class="govuk-box-highlight">
<p class="bold-large">
Application complete
</p>
<p>
Your reference number is </br>
<strong class="heading-medium">HDJ2123F</strong>
</p>
</div>
<p>
We have sent you a confirmation email.
</p>
<p class="heading-medium">
What happens next?
</p>
<p>
We've sent your application to Hackney Electoral Register Office.
</p>
<p>
They will contact you either to confirm your registration, or to ask for more information.
</p>
</div>
</div>
</div>
</div> | 22.874372 | 233 | 0.519662 | eng_Latn | 0.183923 |
54b252b6ccb922302f037e746bc43b07a015555e | 81 | md | Markdown | README.md | Squidjigg/adventure-in-nine-isles | ceea6ac1dbcc023cc612c536996513517c4b1098 | [
"MIT"
] | null | null | null | README.md | Squidjigg/adventure-in-nine-isles | ceea6ac1dbcc023cc612c536996513517c4b1098 | [
"MIT"
] | null | null | null | README.md | Squidjigg/adventure-in-nine-isles | ceea6ac1dbcc023cc612c536996513517c4b1098 | [
"MIT"
] | null | null | null | # Adventure In Nine Isles
My first attempt at coding a text-based adventure game
| 27 | 54 | 0.802469 | eng_Latn | 0.9993 |
54b46d2283f852b375dbfa6902ae32aeee419142 | 1,359 | md | Markdown | src/ja/2020-01/06/07.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 68 | 2016-10-30T23:17:56.000Z | 2022-03-27T11:58:16.000Z | src/ja/2020-01/06/07.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 367 | 2016-10-21T03:50:22.000Z | 2022-03-28T23:35:25.000Z | src/ja/2020-01/06/07.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 109 | 2016-08-02T14:32:13.000Z | 2022-03-31T10:18:41.000Z | ---
title: さらなる研究
date: 07/02/2020
---
大宴会は、古代世界の王宮では日常的なものでした。王たちは、自分の偉大さと自信を示すために、豪勢かつ<ruby>贅<rt>ぜい</rt>沢<rt>たく</rt></ruby>な宴会を催すことが大好きだったのです。ほかならぬこの宴会の一部始終はわからないものの、それが、メディアとペルシアの連合軍がバビロンを攻撃する態勢にあったときに開かれたということはわかっています。しかし人間的見地から言えば、心配すべき理由はありませんでした。バビロンは要塞壁と数年分の食糧、さらには大量の水を持っていました。ユーフラテス川が町の中心部を流れていたからです。それゆえ、ベルシャツァル王は、敵が町を包囲しているときに宴会を開いても問題ないと思ったのでした。そこで、彼は重大な祝賀会を命じますが、それはすぐに飲めや歌えやの大騒ぎになってしまいました。（とりわけ主の力とは対照的な）人間の<ruby>傲<rt>ごう</rt>慢<rt>まん</rt></ruby>さの、なんと説得力のある証明でしょう。ダニエルを通して、神は王に言われました―真理を学ぶべき機会があったにもかかわらず、〔あなたは〕「……あなたの命をその手ににぎり、あなたのすべての道をつかさどられる神をあがめようとはしなかった」（ダニ 5：23、口語訳）と。
「諸国の歴史は、今日われわれに語っている。神はすべての国とすべての人間に、神の大いなる計画の中における場所をお定めになられた。今日、人々もまた国々も、誤られることのない神の手の中にあるおもりによって量られているのである。各々は自分自身の選択によって、各自の運命を決定している。そして神はそのすべてを支配して、みこころを達成しておられるのである」（『希望への光』586 ページ、『国と指導者』下巻 143 ページ）。
### 話し合いのための質問
`❶ 安息日学校のクラスで、社会や文化が神の真理を汚すことに関する日曜日の質問への答えを話し合ってください。それはどのようなことですか。私たちは教会として、また個人として、そのような<ruby>冒<rt>ぼう</rt>瀆<rt>とく</rt></ruby>にどう応じるべきですか。`
`❷ 救いに関して重要なのは、私たちが何を知っているかではなく、知っていることにどう応じるかです。そのことについて、この物語は何を教えていますか（ダニ 5：22 参照）。`
`❸ ダニエル 5：23 を読んでください。この聖句の中には、どんな重要で霊的な原則がありますか。例えば、この聖句は、神を<ruby>冒<rt>ぼう</rt>瀆<rt>とく</rt></ruby>することについて、いかに警告していますか。あるいはまた、創造主としての神についてだけでなく、私たちの存在の支え主としての神についても、どのようなことを教えていますか。`
`❹ あの言葉の意味がわからなくても、ベルシャツァルは恐れました（ダニ 5：6 参照）。このことは、良心の<ruby>呵<rt>か</rt>責<rt>しゃく</rt></ruby>を持って生きるとはどういうことなのかについて、何を教えていますか。` | 75.5 | 550 | 0.834437 | jpn_Jpan | 0.977959 |
54b47ac27a5a0c33d39db1f5fb2f4124110f06fc | 1,628 | md | Markdown | things-that-matter.md | vito/cadet | 651af66ce880c21cd4fc4cf31f9a4c2ebbfe96fa | [
"MIT"
] | 31 | 2017-11-01T02:16:06.000Z | 2021-03-05T13:56:31.000Z | things-that-matter.md | vito/cadet | 651af66ce880c21cd4fc4cf31f9a4c2ebbfe96fa | [
"MIT"
] | 51 | 2017-11-10T01:41:55.000Z | 2020-07-29T20:21:33.000Z | things-that-matter.md | vito/cadet | 651af66ce880c21cd4fc4cf31f9a4c2ebbfe96fa | [
"MIT"
] | 3 | 2018-09-11T04:41:37.000Z | 2020-04-23T21:56:34.000Z | things to visualize:
* [x] issue references
* [x] labels
* [x] how many reactions/comments
* [x] issues that are tied to a PR
* [x] last activity
* [x] who had last word
* [ ] issues that reference many closed issues (i.e. consolidated)
* [ ] subscribers? (is that the same as 'participants'?)
* [ ] has the author ever submitted a PR
* [ ] has the PR build passed?
features that i care about:
* [x] force-directed graph would probably be nice
* [x] search to select issues
* [x] see what's in flight
* [x] view by project
* [ ] break down by label (filter, not group)
* [ ] add to / prioritize backlog
* [ ] finding things to put into the next milestone
* [ ] keeping up to date with active conversations on PRs
* [ ] know if PR has been updated since last review
* [ ] reveal where issue is in graph
* [ ] assign to project
* [ ] view by milestone
* [ ] see where things are prioritized
* [ ] batch labeling
* [ ] ephemeral connection management (i.e. without having to leave comment)
* [ ] breaking/ignoring incidental references (i.e. a reference that is semantically meaningless)
* [ ] ~~dragging issues around (brownie points for persisting it)~~ recognizing via deterministic locations is good enough for now
release page:
for each repo
- # commits since last release
- get commits since last release (https://api.github.com/repos/concourse/docker-image-resource/compare/v1.1.0...HEAD)
- show PRs whose merge commits are in the comparison
- show issues in oldest open milestone
- group issues and PRs by documented/unreleased/left-undocumented/etc
- don't show readme changes?
- show issues closed by merged PRs???
| 36.177778 | 130 | 0.724816 | eng_Latn | 0.999021 |
54b5aeebafa25566c8b1faf24fdbfcb98bb6126d | 295 | md | Markdown | README.md | bill-baggins/GameOfLifePlayground | 1ee54b76e045a078b38dfc7fc32c7d75c5154641 | [
"MIT"
] | 1 | 2021-06-01T18:57:12.000Z | 2021-06-01T18:57:12.000Z | README.md | bill-baggins/GameOfLifePlayground | 1ee54b76e045a078b38dfc7fc32c7d75c5154641 | [
"MIT"
] | null | null | null | README.md | bill-baggins/GameOfLifePlayground | 1ee54b76e045a078b38dfc7fc32c7d75c5154641 | [
"MIT"
] | null | null | null | # GameOfLifePlayground
A fun little implementation of Conway's Game of Life using pygame.
# Installation
Make sure you have python 3.7 or later installed.
Pull, clone, or download the ZIP of this repo and launch the "gameoflife.py" file.
# Features
You can save neat patterns using the S key.
| 29.5 | 82 | 0.779661 | eng_Latn | 0.99268 |
54b5b1bcb4851e613c0876eebafa0253b079f555 | 8,595 | md | Markdown | README.md | wyf-ACCEPT/BackToReality | 0b7609eab5087afcd52827e5e6a87f78a8a633cc | [
"MIT"
] | 21 | 2022-03-15T05:22:52.000Z | 2022-03-27T08:33:14.000Z | README.md | wyf-ACCEPT/BackToReality | 0b7609eab5087afcd52827e5e6a87f78a8a633cc | [
"MIT"
] | null | null | null | README.md | wyf-ACCEPT/BackToReality | 0b7609eab5087afcd52827e5e6a87f78a8a633cc | [
"MIT"
] | 4 | 2022-03-15T05:42:11.000Z | 2022-03-23T19:37:37.000Z | # Back To Reality: Weakly-supervised 3D Object Detection with Shape-guided Label Enhancement
## Introduction
This repo contains PyTorch implementation for paper [Back To Reality: Weakly-supervised 3D Object Detection with Shape-guided Label Enhancement](http://arxiv.org/abs/2203.05238) (CVPR2022)
```
@inproceedings{xu2022br,
author = {Xu, Xiuwei and Wang, Yifan and Zheng, Yu and Rao, Yongming and Zhou, Jie and Lu, Jiwen},
title = {Back To Reality: Weakly-supervised 3D Object Detection with Shape-guided Label Enhancement},
booktitle = {IEEE Conference on Computer Vision and Pattern Recognition (CVPR)},
year = {2022}
}
```
Other papers related to 3D object detection with synthetic shape:
- RandomRooms: Unsupervised Pre-training from Synthetic Shapes and Randomized Layouts for 3D Object Detection ([ICCV 2021](https://arxiv.org/abs/2108.07794))
## New dataset 💥
We conduct additional experiment on the more challenging [Matterport3D](https://niessner.github.io/Matterport/) dataset. From ModelNet40 and Matterport3D, we select all 13 shared categories, each containing more than 80 object instances in Matterport3D training set, to construct our benchmark (Matterport3d-md40). Below is the performance of FSB, WSB and BR (point-version) based on Votenet:
Note that we use OpenCV to estimate the rotated bounding boxes (RBB) as ground-truth, instead of the axis-aligned bounding boxes used in ScanNet-md40 benchmark.
`ScanNet-md40` and `Matterport3d-md40` are two more challenging benckmarks for indoor 3D object detection. We hope they will promote future research on small object detection and synthetic-to-real scene understanding.
## Dependencies
We evaluate this code with Pytorch 1.8.1 (cuda11), which is based on the official implementation of [Votenet](https://github.com/facebookresearch/votenet) and [GroupFree3D](https://github.com/zeliu98/Group-Free-3D). Please follow the requirements of them to prepare the environment. Other packages can be installed using:
```
pip install open3d sklearn tqdm
```
Current code base is tested under following environment:
1. Python 3.6.13
2. PyTorch 1.8.1
3. numpy 1.19.2
4. open3d 0.12.0
5. opencv-python 4.5.1.48
6. plyfile 0.7.3
7. scikit-learn 0.24.1
## Data preparation
### ScanNet
To start from the raw data, you should:
* Follow the [README](./detection/Votenet/scannet/README.md) under `GroupFree3D/scannet` or `Votenet/scannet` to generate the real scenes.
* Follow the [README](./data_generation/ScanNet/README.md) under `./data_generation/ScanNet` to generate the virtual scenes.
The processed data can also be downloaded from [here](https://drive.google.com/drive/folders/1hKjYXdHIpk8a1IPG_k4WmFacSPlfTYwZ?usp=sharing). They should be placed to paths:
```.
./detection/Votenet/scannet/
./detection/GroupFree3D/scannet/
```
After that, the file directory should be like:
```.
...
└── Votenet (or GroupFree3D)
├── ...
└── scannet
├── ...
├── scannet_train_detection_data_md40
├── scannet_train_detection_data_md40_obj_aug
└── scannet_train_detection_data_md40_obj_mesh_aug
```
### Matterport3D
To start from the raw data, you should:
* Follow the [README](./detection/Votenet/matterport/README.md) under `Votenet/matterport` to generate the real scenes.
* Follow the [README](./data_generation/Matterport3D/README.md) under `./data_generation/Matterport3D` to generate the virtual scenes.
The processed data can also be downloaded from [here](https://drive.google.com/drive/folders/166w4w9xa8c7WITDAGswEsDQ8cJxBJomn?usp=sharing).
The file directory should be like:
```.
...
└── Votenet
├── ...
└── matterport
├── ...
├── matterport_train_detection_data_md40
├── matterport_train_detection_data_md40_obj_aug
└── matterport_train_detection_data_md40_obj_mesh_aug
```
## Usage
Please follow the instructions below to train different models on ScanNet. Change `--dataset scannet` to `--dataset matterport` for training on Matterport3D.
### Votenet
#### 1. Fully-Supervised Baseline
To train the Fully-Supervised Baseline (FSB) on Scannet data:
```.
# Recommended GPU num: 1
cd Votenet
CUDA_VISIBLE_DEVICES=0 python train_Votenet_FSB.py --dataset scannet --log_dir log_Votenet_FSB --num_point 40000
```
#### 2. Weakly-Supervised Baseline
To train the Weakly-Supervised Baseline (WSB) on Scannet data:
```.
# Recommended num of GPUs: 1
CUDA_VISIBLE_DEVICES=0 python train_Votenet_WSB.py --dataset scannet --log_dir log_Votenet_WSB --num_point 40000
```
#### 3. Back To Reality
To train BR (mesh-version) on Scannet data, please run:
```.
# Recommended num of GPUs: 2
CUDA_VISIBLE_DEVICES=0,1 python train_Votenet_BR.py --dataset scannet --log_dir log_Votenet_BRM --num_point 40000
CUDA_VISIBLE_DEVICES=0,1 python train_Votenet_BR_CenterRefine.py --dataset scannet --log_dir log_Votenet_BRM_Refine --num_point 40000 --checkpoint_path log_Votenet_BRM/train_BR.tar
```
To train BR (point-version) on Scannet data, please run:
```.
# Recommended num of GPUs: 2
CUDA_VISIBLE_DEVICES=0,1 python train_Votenet_BR.py --dataset scannet --log_dir log_Votenet_BRP --num_point 40000 --dataset_without_mesh
CUDA_VISIBLE_DEVICES=0,1 python train_Votenet_BR_CenterRefine.py --dataset scannet --log_dir log_Votenet_BRP_Refine --num_point 40000 --checkpoint_path log_Votenet_BRP/train_BR.tar --dataset_without_mesh
```
### GroupFree3D
#### 1. Fully-Supervised Baseline
To train the Fully-Supervised Baseline (FSB) on Scannet data:
```.
# Recommended num of GPUs: 4
cd GroupFree3D
python -m torch.distributed.launch --master_port <port_num> --nproc_per_node <num_of_gpus_to_use> train_GF_FSB.py --num_point 50000 --num_decoder_layers 6 --size_delta 0.111111111111 --center_delta 0.04 --learning_rate 0.006 --decoder_learning_rate 0.0006 --weight_decay 0.0005 --dataset scannet --log_dir log_GF_FSB --batch_size 4
```
#### 2. Weakly-Supervised Baseline
To train the Weakly-Supervised Baseline (WSB) on Scannet data:
```.
# Recommended num of GPUs: 4
python -m torch.distributed.launch --master_port <port_num> --nproc_per_node <num_of_gpus_to_use> train_GF_WSB.py --num_point 50000 --num_decoder_layers 6 --size_delta 0.111111111111 --center_delta 0.04 --learning_rate 0.006 --decoder_learning_rate 0.0006 --weight_decay 0.0005 --dataset scannet --log_dir log_GF_WSB --batch_size 4
```
#### 3. Back To Reality
To train BR (mesh-version) on Scannet data, please run:
```.
# Recommended num of GPUs: 4
python -m torch.distributed.launch --master_port <port_num> --nproc_per_node <num_of_gpus_to_use> train_GF_BR.py --num_point 50000 --num_decoder_layers 6 --size_delta 0.111111111111 --center_delta 0.04 --learning_rate 0.006 --decoder_learning_rate 0.0006 --weight_decay 0.0005 --dataset scannet --log_dir log_GF_BRM --batch_size 4
# Recommended num of GPUs: 6
python -m torch.distributed.launch --master_port <port_num> --nproc_per_node <num_of_gpus_to_use> train_GF_BR_CenterRefine.py --num_point 50000 --num_decoder_layers 6 --size_delta 0.111111111111 --center_delta 0.04 --learning_rate 0.002 --decoder_learning_rate 0.0002 --weight_decay 0.0005 --dataset scannet --log_dir log_GF_BRM_Refine --checkpoint_path <[checkpoint_path_of_groupfree3D]/ckpt_epoch_last.pth> --max_epoch 120 --val_freq 10 --save_freq 20 --batch_size 2
```
To train BR (point-version) on Scannet data, please run:
```.
# Recommended num of GPUs: 4
python -m torch.distributed.launch --master_port <port_num> --nproc_per_node <num_of_gpus_to_use> train_GF_BR.py --num_point 50000 --num_decoder_layers 6 --size_delta 0.111111111111 --center_delta 0.04 --learning_rate 0.006 --decoder_learning_rate 0.0006 --weight_decay 0.0005 --dataset scannet --log_dir log_GF_BRP --batch_size 4 --dataset_without_mesh
# Recommended num of GPUs: 6
python -m torch.distributed.launch --master_port <port_num> --nproc_per_node <num_of_gpus_to_use> train_GF_BR_CenterRefine.py --num_point 50000 --num_decoder_layers 6 --size_delta 0.111111111111 --center_delta 0.04 --learning_rate 0.002 --decoder_learning_rate 0.0002 --weight_decay 0.0005 --dataset scannet --log_dir log_GF_BRP_Refine --checkpoint_path <[checkpoint_path_of_groupfree3D]/ckpt_epoch_last.pth> --max_epoch 120 --val_freq 10 --save_freq 20 --batch_size 2 --dataset_without_mesh
```
## Acknowledgements
We thank a lot for the flexible codebase of [Votenet](https://github.com/facebookresearch/votenet) and [GroupFree3D](https://github.com/zeliu98/Group-Free-3D).
| 42.132353 | 491 | 0.766143 | eng_Latn | 0.665644 |
54b630e926efdcc1083612c053a15e6e1d0ed065 | 911 | md | Markdown | README.md | Wolfterro/Projetos-em-Go | 8fe503249acb75aac0bd54c99899bb4315846abd | [
"MIT"
] | 1 | 2020-11-28T05:27:21.000Z | 2020-11-28T05:27:21.000Z | README.md | Wolfterro/Projetos-em-Go | 8fe503249acb75aac0bd54c99899bb4315846abd | [
"MIT"
] | null | null | null | README.md | Wolfterro/Projetos-em-Go | 8fe503249acb75aac0bd54c99899bb4315846abd | [
"MIT"
] | null | null | null | # Projetos em Go
Pequenos projetos em Go para aprendizado da linguagem de programação.
## Hello World
Este é meu primeiro programa em Go, basicamente um clone da versão do meu projeto **Hello World** que existe em C.
## External IP
Um outro clone de um pequeno script que fiz em Python, ele mostra o IP Externo da máquina do usuário e outras informações relativas a conexão daquela máquina utilizando a API do ipinfo, como **cidade, país, região, hostname, código postal e localização geográfica** (sem muita precisão, mas o que vale é a intenção :) ).
## Playah
Este programa é um pequeno reprodutor de arquivos .MP3 através da linha de comando e com a possibilidade de passar o Sample Rate que desejar, tornando a música mais rápida ou mais lenta. Similar a um programa que havia desenvolvido em Python mas nunca havia divulgado, decidi então tentar criar uma versão dele em Go para testar novas libs.
| 56.9375 | 340 | 0.781559 | por_Latn | 1.000003 |
54b79d360584905e6c34524781c855690224125c | 3,910 | md | Markdown | _posts/2020-01-01-what-i-read-in-december-2019.md | draliceviolett/Scriptor-Jekyll-Theme | 3c9f348374953130ffaf88e56f712dca764e76d9 | [
"MIT"
] | null | null | null | _posts/2020-01-01-what-i-read-in-december-2019.md | draliceviolett/Scriptor-Jekyll-Theme | 3c9f348374953130ffaf88e56f712dca764e76d9 | [
"MIT"
] | null | null | null | _posts/2020-01-01-what-i-read-in-december-2019.md | draliceviolett/Scriptor-Jekyll-Theme | 3c9f348374953130ffaf88e56f712dca764e76d9 | [
"MIT"
] | null | null | null | ---
date: 2020-01-01
layout: post
title: "What I read in December 2019"
category: book-blog
excerpt: "The LONGEST month."
featured-image: /images/december-collage-1.jpg
---
I read 15 books in December, and I'm not surprised - the month seemed to go on forever, and it would have been even more if one of them hadn't been a huge Barbara Erskine tome. I reached a total of 148 books for the year, finishing my last one (<cite>S.T.A.G.S</cite>, by M. A. Bennett) at around 11:15pm on New Year's Eve!
<cite>Grand Union: stories</cite>, by Zadie Smith. A bit hit-and-miss for me, some of the stories I really enjoyed and others left me cold - 3*
<cite>Nine Elms</cite>, by Robert Bryndza. Robert Bryndza's books are like Pringles - you have one and it leaves you craving more. As I've read all his thrillers now, though, I have to wait ten months for the next one! - 4.5*
<cite>How It All Began</cite>, by Penelope Lively - 4*
<cite>Mindf\*ck: inside Cambridge Analytica's plot to break the world</cite>, by Christopher Wylie. Fascinating, surprisingly wide-ranging re: psychology and culture, and probably not the best choice to read the week of a horrible election result - 4*
<cite>The Raven King</cite>, by Maggie Stiefvater - 4*
<cite>What a Carve Up!</cite>, by Jonathan Coe. Nearly 26 years old, but still so relevant to today that it could have been published last week. Really funny, I absolutely barrelled through it - 5*
[<cite>Who Did You Tell?</cite>, by Lesley Kara](/who-did-you-tell-by-lesley-kara/) - 4*
<cite>Joe Country</cite>, by Mick Herron - 4*
<cite>Twas the Nightshift Before Christmas</cite>, by Adam Kay - 4*
<cite>Cartes Postales from Greece</cite>, by Victoria Hislop. Not quite what I was expecting re: how much we saw of the writer and receiver of the postcards/notebook, but I really enjoyed the short stories - 4*
<cite>The Ghost of Madison Avenue</cite>, by Nancy Bilyeau - 4*
<cite>The Warrior's Princess</cite>, by Barbara Erskine. Similar to <cite>Sleeper's Castle</cite> (or the other way round, as this came out first) in setting and formula, but still a fun read and made me want to go on a holiday to Wales even more - 4*
<cite>I Never Said I Loved You</cite>, by Rhik Samadder. Occasional flashes of humour and relatability (I, too, would be regarded as 'doing well' if only I was a decade younger) but too often felt like a bit of a trudge - 3*
<cite>City of Ghosts</cite>, by Victoria Schwab - 4*
<cite>S.T.A.G.S</cite>, by M. A. Bennett - 4*
## Looking ahead...
As ever, this is more of a 'hope to read' than a 'definitely will read' list! Well, I'll definitely be reading <cite>Call Down the Hawk</cite>, by Maggie Stiefvater, because I've already put my bookmark in it ready to begin reading. I found Ronan, his unusual ability, and his family the most fascinating things in the Raven Cycle, so I'm looking forward to seeing what happens next.
As a fan of all things spooky, <cite>Ghostland: in search of a haunted country</cite>, by Edward Parnell, looks fascinating to me. Having enjoyed my first Victoria Hislop book last month, I have high hopes for my second, <cite>Those Who Are Loved</cite>. And I've not quite read *everything* Stuart MacBride has ever written, so when I saw <cite>Birthdays for the Dead</cite> in the Kindle sale, I decided it was high time to remedy that! It'll also keep me going until his next new book comes out.
| 71.090909 | 498 | 0.742199 | eng_Latn | 0.997258 |
54b85cac9cc451429f278245f6331271a4904020 | 1,686 | md | Markdown | _posts/2021_08_12/2021-08-12-BOJ21142.md | CAEL0/CAEL0.github.io | 34ae676de7fe7fd55486b89eaf952a0b8d94ab44 | [
"MIT"
] | 1 | 2021-08-13T15:00:49.000Z | 2021-08-13T15:00:49.000Z | _posts/2021_08_12/2021-08-12-BOJ21142.md | CAEL0/CAEL0.github.io | 34ae676de7fe7fd55486b89eaf952a0b8d94ab44 | [
"MIT"
] | null | null | null | _posts/2021_08_12/2021-08-12-BOJ21142.md | CAEL0/CAEL0.github.io | 34ae676de7fe7fd55486b89eaf952a0b8d94ab44 | [
"MIT"
] | 1 | 2021-08-02T10:30:01.000Z | 2021-08-02T10:30:01.000Z | ---
title: "[BOJ 21142] Longest Common Subsequence"
excerpt: Gold 1
categories: [Problem Solving]
tags: [BOJ, DP]
last_modified_at: 2021-08-12 01:09:00 +0900
---
> # 문제
---
[<u>https://www.acmicpc.net/problem/21142</u>](https://www.acmicpc.net/problem/21142)
<br>
> # 풀이
---
아이디어를 쥐어짜내듯 풀었다.
일반적인 2, 3개짜리 LCS는 시간 복잡도가 O(n ** 2), O(n ** 3)라 도움이 되지 않을 거라 생각했다.
일부 문자열들의 LCS 길이를 알아도 전체 LCS 길이를 구하는 데 도움이 되지 않을 것 같았다.
뭔진 모르지만 주어진 문자열들의 LCS가 있다고 쳐보자.
이 LCS는 주어진 문자열들 중 어떤 문자열을 뽑던 순방향으로 읽을 때 띄엄띄엄 등장해야 한다.
반대로 생각하면 선행 관계가 주어졌을 때 이 관계들을 만족시키는 문자열을 찾는 것이라고도 볼 수 있다.
이는 위상 정렬과 동일한 맥락이다.
하지만 위상 정렬은 DAG (Directed Acyclic Graph, 사이클 없는 방향 그래프)에서만 가능하므로 사이클을 모두 제거해 줘야 한다.
길이가 k인 n개의 문자열 각각에 대해, 총 k * (k - 1) / 2개의 (앞에 있는 문자, 뒤에 있는 문자) 쌍을 얻을 수 있다.
A부터 차례로 0, 1, ...로 치환하면 k x k 인접 행렬 G를 얻을 수 있다.
이때 G\[i]\[j] == G\[j]\[i] == 1이면 사이클을 의미하므로 두 값 모두 0으로 바꾼다.
이후 k <= 26이므로 dfs로 탐색했다.
<br>
> # 코드
---
```python
import sys
sys.setrecursionlimit(10 ** 5)
n, k = map(int, sys.stdin.readline().split())
graph = [[0] * k for _ in range(k)]
for _ in range(n):
string = list(map(lambda x: ord(x) - 65, sys.stdin.readline().strip()))
for i in range(k - 1):
for j in range(i + 1, k):
graph[string[i]][string[j]] = 1
for i in range(k):
for j in range(i + 1, k):
if graph[i][j] == graph[j][i] == 1:
graph[i][j] = graph[j][i] = 0
dp = [-1] * k
def f(pos):
if dp[pos] != -1:
return dp[pos]
res = 1
for next in range(k):
if graph[pos][next]:
res = max(res, 1 + f(next))
dp[pos] = res
return res
ans = 0
for start in range(k):
ans = max(ans, f(start))
print(ans)
```
| 17.747368 | 85 | 0.571174 | kor_Hang | 0.999994 |
54b87da64496be427e5a9b4cdcfd3e4c2e0a384e | 1,009 | md | Markdown | _drafts/2017-10-15-33-fundamentals-every-perl-developer-should-know.md | briandfoy/briandfoy.github.io | 20ed0d486a4d33ccf81923ec84a07f9097962752 | [
"MIT"
] | 1 | 2021-09-02T19:18:18.000Z | 2021-09-02T19:18:18.000Z | _drafts/2017-10-15-33-fundamentals-every-perl-developer-should-know.md | briandfoy/briandfoy.github.io | 20ed0d486a4d33ccf81923ec84a07f9097962752 | [
"MIT"
] | null | null | null | _drafts/2017-10-15-33-fundamentals-every-perl-developer-should-know.md | briandfoy/briandfoy.github.io | 20ed0d486a4d33ccf81923ec84a07f9097962752 | [
"MIT"
] | null | null | null | ---
layout: post
title: 33 Fundamentals Every Perl Developer Should Know
categories: programming perl
tags:
stopwords:
last_modified:
original_url:
---
1. Sigils tell you how you are accessing a variable, not what type it is.
2. Lists are data, arrays are containers that hold lists.
3. Perl has several contexts: scalar-array, number-string, and so on.
4. The verbs (operators) decide how things happen instead of the nouns (data types), often based on context.
5. Dynamic scope is based on time but affects the entire program. `local` makes changes inside a dynamic scope.
6. Lexical scope is based on the static position in the program text. That's the enclosing braces or the entire file.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
## Other
* [33 Fundamentals Every JavaScript Developer Should Know](https://medium.com/@stephenthecurt/33-fundamentals-every-javascript-developer-should-know-13dd720a90d1)
| 12.011905 | 162 | 0.72448 | eng_Latn | 0.984533 |
54b8ef41b6ba9359ec1dddd75b0ee4072fc1e08d | 213 | md | Markdown | README.md | piersh/GLander | 09510ee75b33183562122a0006968341a765ce20 | [
"Apache-2.0"
] | null | null | null | README.md | piersh/GLander | 09510ee75b33183562122a0006968341a765ce20 | [
"Apache-2.0"
] | null | null | null | README.md | piersh/GLander | 09510ee75b33183562122a0006968341a765ce20 | [
"Apache-2.0"
] | null | null | null | # GLander
WebGL 3D lander game written in Typescript.
[Live Demo][1]
[![Screenshot][2]][1]
[1]: http://codewithoutborders.com/GLander/
[2]: https://github.com/piersh/GLander/wiki/Screenshot.png (Live Demo)
| 21.3 | 72 | 0.704225 | yue_Hant | 0.430143 |
54b919dcb9faa06de81936ba6a24e5424dc00bd7 | 1,139 | md | Markdown | READMe.md | bealox/p3-bittrex | cb705ed08bc0e61cfaa405a18dfd8cb75949a7f1 | [
"MIT"
] | null | null | null | READMe.md | bealox/p3-bittrex | cb705ed08bc0e61cfaa405a18dfd8cb75949a7f1 | [
"MIT"
] | null | null | null | READMe.md | bealox/p3-bittrex | cb705ed08bc0e61cfaa405a18dfd8cb75949a7f1 | [
"MIT"
] | null | null | null | pi-bittrex
==============
[](https://travis-ci.org/bealox/p3-bittrex)
Python 3 API Wrapper for Bittrex. I am **NOT** associated with Bittrex, please use at your own risk.
Tips are appreciated:
* IOTA:BRTJHYOGVJZULCNMZHJPILPJUNPWGFSBMKHW9VQTHRASCCZFEKQQMIQYMXYCDVAIGRYGFKXMG9W9RKBBCIBAIDOSJ9
Install
-------------
Use pip3 to install the pacakge.
```bash
pip install p3_bittrex
```
Set up Option 1
-------------
Set your client to BITTREX_KEY env variables.
Set your secret to BITTREX_SECRET env variables.
```bash
export BITTREX_KEY=<your_key>
export BITTREX_SECRET=<your_secret>
```
Eaxmple:
```python
from bittrex import Bittrex
my_bittrex = Bittrex()
my_bittrex.get_markets()
{'success': True, 'message': '', 'result': [{'MarketCurrency': 'LTC', ...
```
Set up Option 2
-------------
Specify your client and key in the initialisation
Example:
```python
from bittrex import Bittrex
my_bittrex = Bittrex(key='your_key', secret='youesecret')
my_bittrex.get_markets()
{'success': True, 'message': '', 'result': [{'MarketCurrency': 'LTC', ...
```
| 22.78 | 117 | 0.707638 | eng_Latn | 0.393381 |
54b9858c7d34a0e42fbe60746b54b5bcca8e2b43 | 2,664 | md | Markdown | content/releases/release-notes-1.4.0.md | Avola/docs | 0635be23f0c329f41be482efd18022a53ac8ebdd | [
"MIT"
] | null | null | null | content/releases/release-notes-1.4.0.md | Avola/docs | 0635be23f0c329f41be482efd18022a53ac8ebdd | [
"MIT"
] | null | null | null | content/releases/release-notes-1.4.0.md | Avola/docs | 0635be23f0c329f41be482efd18022a53ac8ebdd | [
"MIT"
] | 2 | 2017-11-22T14:10:20.000Z | 2018-06-01T08:36:23.000Z | ---
title: "Release notes 1.4.0"
date: 2017-05-17
draft: false
weight: 240
---
Avola 1.4.20170517.3 was released on May 17, 2017.
##### Features and enhancements
* Decision service versions are now related to the project in which context they were created.
* Domain owners can close projects, as long as all decision services are no longer in approval processes. All decision services will be detached from the project.
* Decision services can be individually detached from a project, as long a they are not in approval.
* Decision services become "inactive" when none of their versions are currently deployed in a production environment. they can be reactivated for development, just like active decision services.
* When a decision services is submitted for approval, it is no longer automatically available in the test execution API. It becomes available after QA approval.
* Decision Services that are not currently in a project, can be linked to any project in the same business domain.
* You can now search and retrieve individual decision executions from a decision service version.
* When examining a test result, you can now see and expand the tables that yielded no conclusion. (#256)
* you can now test decision service versions the same way you test decisions in development. From now on, when a version is created, it gets a copy of the scenario collections.
* The test pages now have breadcrumb navigation.
##### Fixes
* Better handling of "no conclusion" data, fixing the "Parameter not defined" error. (#235)
* Navigation fix in the breadcrumb
* Navigation fix that broke the download Excel template functionality
* You can now export decisions and decision services to Excel
* Correct button visibility on business data (#254)
* Value lists and pairs can now only be linked to a domain, if they are only used within that domain. (#253)
* Underline behaviour in table headers (#250)
* Paging issue on decision overview (#255)
* There is now an API for searching, counting and aggregating decision executions
* Adding the first business concept in a domain no longer produces an error
* Better error handling for problems with ill-formed formulas (#206)
* Avoid creating duplicate test scenario's (#270)
* In the DRD, If a data element is already mentioned as a condition, it will no longer be repeated as an operand data element. (#273)
* Improved pages for errors (no access, no server)
* The pages now have a describing title, so they appear more detailed in your browsing history.
* Fixed security error message for modeler (#259)
* API accounts now have a search/filter field.
* Removed error column from test collection overview (#193)
| 61.953488 | 194 | 0.78003 | eng_Latn | 0.999421 |
54b99662ce86e891ce711df8b70b0f07b1472526 | 2,895 | md | Markdown | README.md | crudslag/awesome-ns | 4d6206ffab1da72686c7b368b7fe7dce84efaeb0 | [
"Unlicense"
] | null | null | null | README.md | crudslag/awesome-ns | 4d6206ffab1da72686c7b368b7fe7dce84efaeb0 | [
"Unlicense"
] | null | null | null | README.md | crudslag/awesome-ns | 4d6206ffab1da72686c7b368b7fe7dce84efaeb0 | [
"Unlicense"
] | null | null | null | # awesome N, S high school
これは、N, S高校の生徒による素晴らしい制作物の共同リストです。自由に投稿してください。
## Contents
Qiita: https://qiita.com/organizations/nnn-school
* [Portfolio](#portfolio)
* [Tech Blog](#Tech-Blog)
* [Mobile](#Mobile)
* iOS
* Android
* Multiplatform
* [Web](#Web)
## Portfolio
| name | Link | Source code |
| --- | --- | --- |
| uehr | https://www.uehr.co/ | https://github.com/uehr/uehr.github.io |
| waricoma | https://www.wantedly.com/id/motone_adachi | |
| Barisaku | https://www.wantedly.com/id/barisaku | |
| 193s | https://193s.info/ | |
| jpnykw | https://www.jpnykw.dev/ | https://github.com/jpnykw/jpnykw.dev |
| 佐々木 雅斗(あっぷるささき) | https://scrapbox.io/sasa-pedia/ | |
| ガレバレ | https://garebareda.github.io/portfolio/#/ | https://github.com/garebareDA/portfolio |
| Kakudo | https://kakudo415.com/ | https://github.com/kakudo415/kakudo415.com |
| なおと2309 | https://naoto.tokyo/#/ | |
| hano | https://n-yokohama.github.io/ | https://github.com/N-Yokohama/n-yokohama.github.io |
| 0505Keitan | https://0505keitan.com/ | https://github.com/0505Keitan/0505Keitan.github.io |
| のーさ | https://harukisano.com/ | https://github.com/hrqsn/site |
| Yuki Mihashi | https://yuki384.github.io/ | |
| とも | https://tomoi.moo.jp/portfolio/ | |
| Genbu | https://genbu.netlify.app/ | |
| はと. | https://hatopoppo.studio/ | |
| 猫月あゆむ | https://www.nekozuki.me/ | https://github.com/AyumuNekozuki/nekozuki_me |
| Mani | https://manimani1126.github.io/Manimani.Portfolio/ | |
| seigo2016 | https://github.com/seigo2016/seigo2016.github.io | |
| noboru | https://nemesis62542.github.io/portfolio/ | https://github.com/Nemesis62542/portfolio/tree/master/docs |
| てんかい tenkai | https://tenkai2.github.io/ | https://github.com/tenkai2/tenkai2.github.io |
| なっかのう | https://nakano1120.github.io/portfolio/index.html | https://github.com/nakano1120/portfolio |
| やひろ | https://yahiro.me/ | |
| こたさ | https://lm-kota.netlify.app/ | https://github.com/kotaok/myportfolio |
| はす | https://hasu-83-hashue.vercel.app/ | https://github.com/hashue/Portfolio |
| キタムラ | https://henohenon.github.io/portfolio/myportfolio.html | https://github.com/henohenon/portfolio |
| ゆうや | https://yu63826.github.io/Portfolio/ | https://github.com/yu63826/Portfolio/ |
| @hinatao3o | https://hinata.dev/ | https://github.com/fjhrhnt/hinata.dev |
| OJI | https://oldbigbuddha.dev/ | https://github.com/OldBigBuddha/portfolio |
| Ringo | https://web.ringo.dev/ | https://github.com/Ringo-dev/webpage/ |
| にーくん | https://nixo.jp/ | |
| ころにゃん | https://krnyn.github.io/portfolio/ | https://github.com/krnyn/portfolio |
| とも | https://tomoharu.dev/ | https://github.com/WTomoharu/next-portfolio |
| sizumita | https://about.sumidora.com/ | https://github.com/sizumita/portfolio |
| JW.Unknown | https://kazusite.github.io/aboutme/ | https://github.com/Kondo-Kazushi/Kondo-kazushi.github.io |
## Tech Blog
## Mobile
## Web
| 45.952381 | 115 | 0.68601 | yue_Hant | 0.545972 |
54b9a5d2747cea3b9d504176bb3f18635073576a | 3,365 | md | Markdown | README.md | portlek/player-inputs | 5c3ff11f0e5bbf81a9f302439bdb24272d08941b | [
"MIT"
] | 2 | 2020-05-11T14:01:28.000Z | 2020-05-11T19:31:37.000Z | README.md | portlek/player-inputs | 5c3ff11f0e5bbf81a9f302439bdb24272d08941b | [
"MIT"
] | null | null | null | README.md | portlek/player-inputs | 5c3ff11f0e5bbf81a9f302439bdb24272d08941b | [
"MIT"
] | null | null | null | # player-inputs
Utilities to get a player input for those who don't want to use the Conversation API
## Usage
Explanation: https://www.spigotmc.org/threads/player-chat-inputs.437565/
In this example I'll be using a command
```java
import org.bukkit.command.Command;
import org.bukkit.command.CommandExecutor;
import org.bukkit.command.CommandSender;
import org.bukkit.entity.Player;
import org.bukkit.ciPlugin.Plugin;
import io.github.nemo_64.chatinput.bukkit.BukkitChatInput;
import io.github.nemo_64.chatinput.bukkit.BukkitChatInputBuilder;
public final class TestCommand implements CommandExecutor {
private final Plugin plugin;
public TestCommand(final Plugin plugin) {
this.plugin = plugin;
}
@Override
public boolean onCommand(CommandSender sender, Command command, String label, String[] args) {
if (!(sender instanceof Player)) { // PlayerChatInput only works with players
sender.sendMessage("Only for players");
return false;
}
// This comand will ask for a number n and will send to the player n! so we will
// work with integers
// BukkitChatInputBuilder.integer(..., ...).otherStuffs();
final BukkitChatInput<Integer> chatInput = BukkitChatInputBuilder.<Integer>builder(plugin, (Player) sender)
.isValidInput((player, input) -> { // Set the validation
try {
int val = Integer.valueOf(input);
return val > 0;// We only accept numbers greater than 0
} catch (Exception e) {
return false;// The input was not an integer
}
})
.setValue((player, input) -> {
// We convert the input string to a number
return Integer.valueOf(input);
})
.onInvalidInput((player, input) -> {
// Send a message if the input is invalid
player.sendMessage("That is not a number");
// Send the messages stablished with invalidInputMessage(String) and sendValueMessage(String)
return true;
})
.onFinish((player, value) -> {
// when the player inputs a string that is a number greater that 0 we send a message
player.sendMessage(value + "! is " + this.factorialOf(value));
})
.onCancel(player -> {
// if the player cancels, we send a message
player.sendMessage("Canceled the factorial-calculation");
})
.onExpire(player - {
// if the input time expires.
player.sendMessage("Input expired!");
})
.expire(20L * 30L)
.repeat(true)
.invalidInputMessage("That is not a number/Can calculate the factorial of it");// Message if the input is invalid
.sendValueMessage("Send a number to calculate"); // Asking for the number
.toCancel("cancel"); // Message that the player must send to cancel
.build(); // Build the PlayerChatInput
chatInput.start(); // Ask for the number
return false;
}
private long factorialOf(final int num) {
if (num <= 1)
return 1;
return this.factorialOf(num - 1) * num;
}
}
```
| 40.542169 | 125 | 0.599406 | eng_Latn | 0.874486 |
54bbab0ae545e2623f4e4b7fda5c477b35ff7d17 | 9,348 | md | Markdown | sdk-api-src/content/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctioninstancecollectionquery-execute.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctioninstancecollectionquery-execute.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctioninstancecollectionquery-execute.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:functiondiscoveryapi.IFunctionInstanceCollectionQuery.Execute
title: IFunctionInstanceCollectionQuery::Execute (functiondiscoveryapi.h)
description: Performs the query defined by IFunctionDiscovery::CreateInstanceCollectionQuery.
helpviewer_keywords: ["Execute","Execute method","Execute method","IFunctionInstanceCollectionQuery interface","IFunctionInstanceCollectionQuery interface","Execute method","IFunctionInstanceCollectionQuery.Execute","IFunctionInstanceCollectionQuery::Execute","functiondiscoveryapi/IFunctionInstanceCollectionQuery::Execute","ncd.ifunctioninstancecollectionquery_execute_method"]
old-location: ncd\ifunctioninstancecollectionquery_execute_method.htm
tech.root: ncd
ms.assetid: b924d066-87d7-499b-b006-a10e219e11fd
ms.date: 12/05/2018
ms.keywords: Execute, Execute method, Execute method,IFunctionInstanceCollectionQuery interface, IFunctionInstanceCollectionQuery interface,Execute method, IFunctionInstanceCollectionQuery.Execute, IFunctionInstanceCollectionQuery::Execute, functiondiscoveryapi/IFunctionInstanceCollectionQuery::Execute, ncd.ifunctioninstancecollectionquery_execute_method
req.header: functiondiscoveryapi.h
req.include-header:
req.target-type: Windows
req.target-min-winverclnt: Windows Vista [desktop apps only]
req.target-min-winversvr: Windows Server 2008 [desktop apps only]
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl: FunctionDiscoveryAPI.idl
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll: FunDisc.dll
req.irql:
targetos: Windows
req.typenames:
req.redist:
ms.custom: 19H1
f1_keywords:
- IFunctionInstanceCollectionQuery::Execute
- functiondiscoveryapi/IFunctionInstanceCollectionQuery::Execute
dev_langs:
- c++
topic_type:
- APIRef
- kbSyntax
api_type:
- COM
api_location:
- FunDisc.dll
api_name:
- IFunctionInstanceCollectionQuery.Execute
---
# IFunctionInstanceCollectionQuery::Execute
## -description
<p class="CCE_Message">[Function Discovery is available for use in the operating systems specified in the Requirements section. It may be altered or unavailable in subsequent versions.]
Performs the query defined by <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscovery-createinstancecollectionquery">IFunctionDiscovery::CreateInstanceCollectionQuery</a>.
## -parameters
### -param ppIFunctionInstanceCollection [out]
A pointer to an <a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctioninstancecollection">IFunctionInstanceCollection</a> interface pointer that receives the requested function instance collection.
## -returns
Possible return values include, but are not limited to, the following.
<table>
<tr>
<th>Return code</th>
<th>Description</th>
</tr>
<tr>
<td width="40%">
<dl>
<dt><b>S_OK</b></dt>
</dl>
</td>
<td width="60%">
The method completed successfully. Results are returned synchronously in <i>ppIFunctonInstanceCollecton</i>.
</td>
</tr>
<tr>
<td width="40%">
<dl>
<dt><b>E_OUTOFMEMORY</b></dt>
</dl>
</td>
<td width="60%">
The method is unable to allocate the memory required to perform this operation.
</td>
</tr>
<tr>
<td width="40%">
<dl>
<dt><b>E_PENDING</b></dt>
</dl>
</td>
<td width="60%">
Some of the results will be returned by asynchronous notification. See the remarks for details.
</td>
</tr>
</table>
A predefined query is a query of a layered <a href="/previous-versions/windows/desktop/fundisc/function-discovery-categories">category</a>. When a predefined query is executed, each provider that returns a function instance also returns an HRESULT value. The provider HRESULT values are aggregated, and the value returned by the <b>Execute</b> method reflects these aggregate results. Results are aggregated as follows:
<ul>
<li>If all providers return <b>S_OK</b>, <b>Execute</b> returns <b>S_OK</b>.</li>
<li>If at least one provider returns <b>E_PENDING</b>, and all other providers return either <b>S_OK</b> or <b>E_PENDING</b>, <b>Execute</b> returns <b>E_PENDING</b>.</li>
<li>If all providers return an error value (that is, a value other than <b>S_OK</b> or <b>E_PENDING</b>), <b>Execute</b> returns the error value returned by the network provider that was last queried. Also, if the client's <a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctiondiscoverynotification">IFunctionDiscoveryNotification</a> callback routine was provided to <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscovery-createinstancecollectionquery">IFunctionDiscovery::CreateInstanceCollectionQuery</a>, an <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscoverynotification-onerror">OnError</a> notification is sent for each provider. Each <b>OnError</b> notification contains the HRESULT returned by the provider.</li>
<li>If at least one provider returns an error value, and all other providers return <b>S_OK</b>, <b>Execute</b> returns <b>S_OK</b>. <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscoverynotification-onerror">OnError</a> notifications are sent as described above.</li>
<li>If at least one provider returns an error value, and at least one provider returns <b>E_PENDING</b>, <b>Execute</b> returns <b>E_PENDING</b>. <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscoverynotification-onerror">OnError</a> notifications are sent as described above.</li>
</ul>
When <b>Execute</b> returns <b>S_OK</b>, <i>ppIFunctionInstanceCollection</i> contains the results of the query. If an <a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctiondiscoverynotification">IFunctionDiscoveryNotification</a> interface is provided to the <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscovery-createinstancecollectionquery">CreateInstanceCollectionQuery</a> method of <a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctiondiscovery">IFunctionDiscovery</a>, then changes to the results will be communicated using that interface.
When <b>Execute</b> returns <b>E_PENDING</b>, the result set will be returned asynchronously through the <a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctiondiscoverynotification">IFunctionDiscoveryNotification</a> interface provided to the <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscovery-createinstancecollectionquery">CreateInstanceCollectionQuery</a> method of <a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctiondiscovery">IFunctionDiscovery</a>. <i>ppIFunctionInstanceCollection</i> may be <b>NULL</b> or may contain a partial result set. The enumeration is complete once the <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscoverynotification-onevent">OnEvent</a> method of <b>IFunctionDiscoveryNotification</b> is called with <b>FD_EVENTID_SEARCHCOMPLETE</b>. After the <b>FD_EVENTID_SEARCHCOMPLETE</b> event is received, additional notifications are updates to the results.
## -remarks
This method must be must be invoked by the client program before any data can be retrieved from the query object. When called, this method performs the following:
<ol>
<li>Retrieves the function instance collection object.</li>
<li>Queries the provider of the category that is passed into <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscovery-createinstancecollectionquery">IFunctionDiscovery::CreateInstanceCollectionQuery</a>.</li>
<li>Retrieves the category provider.</li>
<li>Queries the category provider using the subcategory data to generate the collection using query constraints.</li>
<li>Initiates the update notification mechanism if the address of the client program's <a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctiondiscoverynotification">IFunctionDiscoveryNotification</a> callback routine is provided to <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctiondiscovery-createinstancecollectionquery">IFunctionDiscovery::CreateInstanceCollectionQuery</a>.</li>
<li>Caches the collection data and returns.</li>
</ol>
Function Discovery network providers only return function instances through the <a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctiondiscoverynotification">IFunctionDiscoveryNotification</a> interface. They return no function instances directly when this method is invoked. Instead, <a href="/windows/desktop/api/functiondiscoveryapi/nf-functiondiscoveryapi-ifunctioninstancequery-execute">Execute</a> simply initiates an entirely asynchronous retrieval operation and returns <b>E_PENDING</b> to indicate that the results will be returned asynchronously. Notifications must be used to retrieve function instances from Function Discovery network providers.
## -see-also
<a href="/previous-versions/windows/desktop/fundisc/function-discovery-queries">Function Discovery Queries</a>
<a href="/windows/desktop/api/functiondiscoveryapi/nn-functiondiscoveryapi-ifunctioninstancecollectionquery">IFunctionInstanceCollectionQuery</a> | 66.297872 | 1,033 | 0.811083 | eng_Latn | 0.495528 |
54bc0bf29829cc394e1f03cbcbd2fa3646fa2e86 | 378 | md | Markdown | README.md | connectkushal/bulmablade | 90d0684f8fd975bd2c166de19040e1cb0567ba4a | [
"MIT"
] | null | null | null | README.md | connectkushal/bulmablade | 90d0684f8fd975bd2c166de19040e1cb0567ba4a | [
"MIT"
] | null | null | null | README.md | connectkushal/bulmablade | 90d0684f8fd975bd2c166de19040e1cb0567ba4a | [
"MIT"
] | null | null | null | # bulmablade
Laravel's default home, auth and pagination blade files using bulma css
# Notes
- use `php artisan vendor:publish --force` to override existing view files
# To do
- [ ] Add Screenshots
- [x] Add config option to set bulma version
- [ ] Add config option to choose between cdn and sass
- [ ] Add Bulma Sass files to publish
- [ ] Add Bulma Sass tutorial to readme
| 29.076923 | 74 | 0.732804 | eng_Latn | 0.926372 |
b04f938f09488603b5d5f5ddc1ac75e32e1161e5 | 5,941 | md | Markdown | content/en/docs/Developerguide/creating-and-managing-databases.md | opengauss-mirror/docs | 869e517825cf56059243a7104f5e4fa6fc490e69 | [
"MIT"
] | 8 | 2020-07-01T07:14:05.000Z | 2022-03-08T09:20:56.000Z | content/en/docs/Developerguide/creating-and-managing-databases.md | opengauss-mirror/docs | 869e517825cf56059243a7104f5e4fa6fc490e69 | [
"MIT"
] | null | null | null | content/en/docs/Developerguide/creating-and-managing-databases.md | opengauss-mirror/docs | 869e517825cf56059243a7104f5e4fa6fc490e69 | [
"MIT"
] | 6 | 2020-07-01T15:40:22.000Z | 2021-05-28T07:43:19.000Z | # Creating and Managing Databases<a name="EN-US_TOPIC_0000001208299065"></a>
## Prerequisites<a name="en-us_topic_0283136807_en-us_topic_0237120295_en-us_topic_0059779126_s82a10b03aef44f24a8b835912c58dd5b"></a>
Only the database system administrator or users granted with database creation permissions can create a database. For details about how to grant database creation permissions to a user, see [Managing Users and Their Permissions](en-us_topic_0000001208538067.md).
## Background<a name="en-us_topic_0283136807_en-us_topic_0237120295_en-us_topic_0059779126_s4b8e4eb214404dc8a2dfd174a7245290"></a>
- openGauss has two default template databases, template0 and template1, and a default user database, Postgres. The default compatible database type of Postgres is O \(that is, **DBCOMPATIBILITY** is set to **A**\). In this compatible type, empty strings are processed as null values.
- **CREATE DATABASE** creates a database by copying a template database \(**template0** by default\). Do not use a client or any other tools to connect to or to perform operations on the template databases.
> **NOTE:**
>- The template database does not contain any user table. You can view the attributes of the template database in the **PG\_DATABASE** system catalog.
>- The **template0** template does not allow user connections. Only the initial user of the database and the system administrator can connect to **template1**.
- A maximum of 128 databases can be created in openGauss.
- A database system consists of multiple databases. A client can connect to only one database at a time. Users cannot query data across databases. If one openGauss contains multiple databases, set the **-d** parameter to specify the database instance to be connected.
## Precautions<a name="en-us_topic_0283136807_en-us_topic_0237120295_en-us_topic_0059779126_section19939134010190"></a>
Assume that the database encoding is SQL\_ASCII. \(You can run the **show server\_encoding;** command to query the encoding used for storing data in the current database.\) If the database object name contains multi-byte characters \(such as Chinese\) or if the object name length exceeds the allowed maximum \(63 bytes\), the database truncates the last byte \(not the last character\) of the object name. In this case, half characters may appear.
To resolve this problem, you need to:
- Ensure that the name of the data object does not exceed the maximum length.
- Change the default database storage code set \(**server\_encoding**\) to UTF-8.
- Exclude multi-byte characters from object names.
- Ensure that no more than 128 databases are created \(recommended\).
- If you fail to delete an object by specifying its name after truncation, specify its original name to delete it, or manually delete it from the system catalogs on each node.
## Procedure<a name="en-us_topic_0283136807_en-us_topic_0237120295_en-us_topic_0059779126_s2c34996198bd4ad8b9eb15de09d68bcb"></a>
1. Create a database.
1. Run the following command to create a tablespace named **tpcds\_local**:
```
openGauss=# CREATE TABLESPACE tpcds_local RELATIVE LOCATION 'tablespace/tablespace_1' ;
CREATE TABLESPACE
```
2. Run the following command to create a database named **db\_tpcc**:
```
openGauss=# CREATE DATABASE db_tpcc WITH TABLESPACE = tpcds_local;
CREATE DATABASE
```
> **NOTE:**
>- Database names must comply with the general naming convention rules of SQL identifiers. The current role automatically becomes the owner of this new database.
>- If a database system is used to support independent users and projects, store them in different databases.
>- If the projects or users are associated with each other and share resources, store them in one database. However, you can divide them into different schemas. A schema is a logical structure, and the access permission for a schema is controlled by the permission system module.
>- A database name contains a maximum of 63 bytes and the excessive bytes at the end of the name will be truncated by the server. You are advised to specify a database name no longer than 63 bytes when you create a database.
2. View databases.
- Run the **\\l** meta-command to view the database list of the database system.
```
openGauss=# \l
```
- Run the following command to query the database list in the **pg\_database** system catalog:
```
openGauss=# SELECT datname FROM pg_database;
```
3. Modify the database.
You can modify database configuration such as the database owner, name, and default settings.
- Run the following command to set the default search path for the database:
```
openGauss=# ALTER DATABASE db_tpcc SET search_path TO pa_catalog,public;
ALTER DATABASE
```
- Run the following command to modify the database tablespaces:
```
openGauss=# ALTER DATABASE db_tpcc SET TABLESPACE tpcds;
ALTER DATABASE
```
- Run the following command to rename the database:
```
openGauss=# ALTER DATABASE db_tpcc RENAME TO human_tpcds;
ALTER DATABASE
```
4. Delete the database.
You can run the **[DROP DATABASE](en-us_topic_0000001163058100.md)** command to delete a database. This command deletes the system catalog of the database and the database directory on the disk. Only the database owner or system administrator can delete a database. A database accessed by users cannot be deleted. You need to connect to another database before deleting this database.
Run the following command to delete the database:
```
openGauss=# DROP DATABASE human_tpcds;
DROP DATABASE
```
| 56.580952 | 450 | 0.735903 | eng_Latn | 0.985478 |
b0509bd9957c8500a9bcb8f1e3cbc1764215b1dd | 1,641 | md | Markdown | README.md | SondagesPro/less-skelvanilla | de116ec2c5e684e7eaf9e00df0bbe630a7dba1de | [
"MIT"
] | null | null | null | README.md | SondagesPro/less-skelvanilla | de116ec2c5e684e7eaf9e00df0bbe630a7dba1de | [
"MIT"
] | null | null | null | README.md | SondagesPro/less-skelvanilla | de116ec2c5e684e7eaf9e00df0bbe630a7dba1de | [
"MIT"
] | null | null | null | # Basic less generator for LimeSurvey #
Updated from bootstrap
- Allow usage of rem
- Set current font-size to rem
- Add more usage of current variable to make different variations
- Some fix for limesurvey with bootsrap
The default variables use only rem and more contrast
## Usage ##
### Single bootstrap replace ##
1. Copy file from skelvanilla-default directory to base directory
2. Update `variables.less` and optionnaly other less files. If you already have a variables.less file : you can use it directly.
3. Use lessc to generate your theme : you can choose the theme varivation between base, awesome, button and awesome_button
4. `lessc theme-base.less > bootstrap.css`
5. Copy this css file to your [skelvanilla](https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla) extended model
### Complete variation creation ##
1. Put your variables.less file in variations-variables directory with your desired name (sample : `mytheme.less`)
2. Optionaly remove all other files from variations-variables directory (then your template get it by parent theme)
2. Optionnaly create adapted less file in other directory (see default directory for usage)
3. Update makevariations.sh script after `## Add your own needed variables files here` line to use your own less file for default
4. Update `lessc` generator line to use your prefered theme.
5. Move variations directory and bootstrap.css to your [skelvanilla](https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla) extended model
6. Add your own variation in [skelvanilla](https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla) config.xml file at `availablevariations` part.
| 52.935484 | 146 | 0.789762 | eng_Latn | 0.983675 |
b050f8c6fdd6fb75a5da3c005545a19511bc9c5c | 6,203 | md | Markdown | README.md | JunhwanPark/AppNotes-SmartLight | c6607c44d87ec306907948edbe145f525e3d51f6 | [
"Apache-2.0"
] | null | null | null | README.md | JunhwanPark/AppNotes-SmartLight | c6607c44d87ec306907948edbe145f525e3d51f6 | [
"Apache-2.0"
] | null | null | null | README.md | JunhwanPark/AppNotes-SmartLight | c6607c44d87ec306907948edbe145f525e3d51f6 | [
"Apache-2.0"
] | null | null | null | # Smart Lighting Control with ARTIK 055s
This application is to use ARTIK 055s to implement smart dimmable light. The smart light application can be used with Samsung ARTIK mobile app to turned on, turn off the LED light and/or adjusting brightness of the LED light. A physical on device button is also provided for as a traditional way of controlling the LED light. By using Samsung ARTIK mobile app, users can easily onboard the smart light onto ARTIK Cloud. Over the air firmware update (OTA) capability is included in the smart light application as well.
## Contents
> * [How to Application Download](#how-to-application-download)
> * [Prepare Hardware](#prepare-hardware)
> * [About Smart Light application](#about-smart-light-application)
> * [Build Application](#build-application)
> * [Program Binary](#program-binary)
> * [ARTIK Cloud Setup](#artik-cloud-setup)
> * [Run Smart Light application](#run-smart-light-application)
> * [Generate OTA Image](#generate-ota-image)
## How to Application Download
```bash
$ git clone --recursive https://github.com/SamsungARTIK/TizenRT.git
$ cd TizenRT
$ git checkout 39c00d1ee3d2781c9f78f46bd840dce4ef6e1db4
$ git clone https://github.com/JunhwanPark/AppNotes-SmartLight ./apps/examples/smart_light
```
## Prepare Hardware
Connect LED to ARTIK 055s starter kit as shown below:
The ARTIK 055s starter kit pinout map is listed [here](../../../build/configs/artik055s/README.md#artik055s-starter-kit-pinout).
The smart light application has already pre-programmed to connect to **XPWMTOUT_3** pin. We are using pulse width modulation (PWM) to drive LED in this application. This means that LED is getting switched on and off. When the switching frequency is higher enough, the brightness of the LED is integrated over time, and human eyes cannot tell the difference. We are setting the switching frequency of LED to be **1000Hz** in the code. This means that the LED is turned on for 0.1 millisecond then turned off for another 0.9 millisecond.
When powering up LED, it’s always a good practice to connect resistor to LED. The resistor (100 ohm) is used to limit the current though the LED and prevent it burns.
Please note that the LED cathode (-) pin is the pin that right next to the flat spot of the LED, which connects to the ground. The anode (+) is the other pin that connects to the resistor and **XPWMTOUT_3** pin.
## About Smart Light Application
There are 5 pre-set brightness levels that can be used to control the brightness of LED light, they are:
| Control Action | Brightness Level (%) |
|:------------------|:-------------------------:|
|SetOn | 100% |
|SetReading | 80% |
|SetMovie | 35% |
|SetSleep | 8% |
|SetOff | 0% |
The above 5 brightness settings can be used both locally by pressing physical button (**SW703** on starter kit), and remotely by selecting the particular action using mobile app through ARTIK Cloud.
There is an additional remote action that can be supported by using mobile app. This remote action is called **SetBrightness**. It can be used to remotely adjusting LED brightness to any preferable brightness level between 0% to 100%.
Once the ARTIK 055s powered smart light device is powered up and connected to Wi-Fi and ARTIK Cloud through the build-in onboarding process, the smart LED light is ready to use.
## Build Application
Refer [here](../../../README.md#ubuntu-development-setting) to setup development environment.
```bash
$ cd os
$ ./tools/configure.sh artik055s/typical
$ make
```
The **smartlight** is included in the build by default
## Program Binary
```bash
$ make download ALL
```
## ARTIK Cloud Setup
Follow [ARTIK Cloud Getting Started](https://developer.artik.cloud/documentation/getting-started/hello-world.html) page to register and log into your ARTIK Cloud account.
When creating new device type under your ARTIK Cloud, you can use the pre-defined [manifest.json](Manifest/com.smart.light.manifest.json) to create your smart light device by drag and drop the json file in the upload block like shown below.
After creating the device, the other thing you need to do is to browse to **Device Management** tab under your newly created device, then click **SET UP PROPERTIES** to enable server properties and device properties and allow LWM2M running for your device.
## Run Smart Light application
Now we are ready to run the application.
```bash
TASH>> smartlight
```
Then please refer to [artik.io](https://developer.artik.io/documentation/artik-05x/getting-started/communicate.html#auto-connect-artik-05x-to-wi-fi-and-artik-cloud) to:
* Download mobile app
* Provision Wi-Fi to your smart light device
* Onboard smart light device onto ARTIK Cloud
After successfully onboarding the smart light, you should be able to see the device under your ARTIK Cloud account.
If you click on the device, all of the actions defined in the device manifest file will be shown.
All of the action, except **SetBrightness** do not require additional setup. As mentioned in [previous section](#about-smart-light-application), the brightness level can be set between 0% to 100%. To set the preferred brightness level, click on **SetBrightness** action from the mobile app device action list, then type in integer between 0 to 100 in the text field below.
## Generate OTA Image
```bash
$ make image ota
```
Note: The resulting "ota.bin" can be found under **/build/configs/$(BOARD_NAME)/bin**
This image can be used to upload into [ARTIK Cloud](https://developer.artik.cloud/documentation/device-management/ota-updates.html) for OTA update under device management.
Enjoy!
| 55.383929 | 540 | 0.743028 | eng_Latn | 0.982203 |
b0514954a3f3b2480a611afa170aa5d1a0dc6cd7 | 1,494 | md | Markdown | README.md | demir09/cekilisbot | 591eba6efffb681dda7d652b0896462ba35fa9ef | [
"Apache-2.0"
] | 2 | 2021-05-28T16:43:49.000Z | 2021-05-28T16:44:30.000Z | README.md | demir09/cekilisbot | 591eba6efffb681dda7d652b0896462ba35fa9ef | [
"Apache-2.0"
] | null | null | null | README.md | demir09/cekilisbot | 591eba6efffb681dda7d652b0896462ba35fa9ef | [
"Apache-2.0"
] | null | null | null | ## ÇekilişBot
Çekilişlerinizi kolayca düzenlemenize olanak tanır. ÇekilişBot, [Discord.JS](https://discord.js.org) ile geliştirilmiştir.<br>
<br>
## Davet
Eğer botu sevdiyseniz ve **ÇekilişBot**'u sunucunuza davet etmek istiyorsanız, aşağıdaki linki kullanın:<br>
🔗 **https://cekilisbot.cf/davet**
## Kullanım
* **ç!yardım** - Yardım menüsünü Direkt Mesajlarınıza gönderir
* **ç!sil** - Çekilişi siler. Eğer bir mesaj IDsi belirtirseniz, o IDye ait çekilişi siler. Eğer mesaj IDsi belirtmezseniz, kanaldaki çekilişi siler.
* **ç!başlat \<zaman> [kazanan sayısı] [ödül]** - Mevcut kanalda yeni bir çekiliş başlatır. Kullanıcılar 🎉 tepkisine basarak çekilişe katılabilirler. Zaman saniye, dakika, saat veya gün olabilir. Zaman birimlerini "s" (saniye), "m" (dakika), "h" (saat), veya "d" (gün) olarak yazabilirsiniz. Örneğin, `30s` = **30 saniye** ve `2h` = **2 saat**. Eğer kazanan sayısını belirtecekseniz, kazanan sayısı `#w` şeklinde olmalıdır. Örneğin, `2w` = **2 kazanan** ve `5w` = **5 kazanan**.
* **ç!reroll [mesajId]** - Yeni bir kazanan seçer. Eğer bir mesaj IDsi belirtirseniz, o IDye ait çekiliş için yeni bir kazanan seçer. Eğer mesaj IDsi belirtmezseniz, kanaldaki son çekiliş için yeni kazanan seçilir.
* **ç!bitir [mesajId]** - Çekilişi bitirir. Eğer bir mesaj IDsi belirtirseniz, o IDye ait çekilişi bitirir. Eğer mesaj IDsi belirtmezseniz, kanaldaki son aktif çekilişi bitirir.
* **ç!liste** - Sunucudaki aktif çekilişleri gösterir.
| 87.882353 | 478 | 0.744311 | tur_Latn | 0.99983 |
b0526041907b8563ec81864f9689a2a0b0a8550d | 259 | md | Markdown | README.md | DavidWashington833/calculator | 74f0c238ad7a965f70eefb06ddd7c6b8a41c16ab | [
"MIT"
] | null | null | null | README.md | DavidWashington833/calculator | 74f0c238ad7a965f70eefb06ddd7c6b8a41c16ab | [
"MIT"
] | null | null | null | README.md | DavidWashington833/calculator | 74f0c238ad7a965f70eefb06ddd7c6b8a41c16ab | [
"MIT"
] | null | null | null | # Calculator
Calculator in HTML, CSS and Javascript.
## Authors
* **David Washington** - [davidwashington833](https://github.com/DavidWashington833)
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
| 21.583333 | 93 | 0.749035 | eng_Latn | 0.842899 |
b0535db92ef6827bc5f3fcfc6e40ecd6fe332199 | 4,004 | md | Markdown | README_KLAYTN.md | wetcod/vvisp | 47cd0a640c6e0bb25cc1938090727e47f4f93eff | [
"MIT"
] | 81 | 2018-11-27T06:40:05.000Z | 2022-01-10T00:23:24.000Z | README_KLAYTN.md | wetcod/vvisp | 47cd0a640c6e0bb25cc1938090727e47f4f93eff | [
"MIT"
] | 116 | 2018-11-27T11:11:04.000Z | 2021-04-05T04:18:57.000Z | README_KLAYTN.md | HAECHI-LABS/haechi-cli | 20eedcfcdeb6dbe03e4dfa829478cb14fa7c6805 | [
"MIT"
] | 24 | 2018-11-28T04:10:29.000Z | 2022-03-12T13:35:23.000Z | # vvisp
- [Sample repository utilizing vvisp](https://github.com/HAECHI-LABS/vvisp-sample)
## Quick Usage
**1. Install vvisp**
```bash
$ npm install -g @haechi-labs/vvisp
#or if you use yarn
$ yarn global add @haechi-labs/vvisp
```
Use version >= v2.1.0
**2. Initialize your directory**
```bash
$ vvisp init my-project --klaytn
$ cd my-project
$ npm install #or yarn install
```
**3. Make your Contracts at `contracts/`**
Now, you can use `gen-script`, `compile` and `flatten` commands.
**4. Set `vvisp-config.js` file**
Please set environment variables in `vvisp-config.js` file.
_Example_
```javascript
const MNEMONIC = 'YOUR_MNEMONIC';
module.exports = {
networks: {
development: {
platform: 'klaytn',
url: 'URL_TO_KLAYTN_NODE',
gasLimit: 10000000, // increase if you need
}
},
compilers: {
solc: {
version: '0.4.24',
settings: {
optimizer: {
enabled: true,
runs: 200
},
evmVersion: 'byzantium'
}
}
},
from: { // or from: 'YOUR_PRIVATE_KEY'
mnemonic: MNEMONIC,
index: 0
},
};
```
See more information at [here](./CONFIGURATION.md#config) for more information about `vvisp-config.js`.
Now you can use `deploy-contract` command.
**5. Set `service.vvisp.json` file**
Please set information about your DApp service in `service.vvisp.json`.
_Example_
```json
{
"serviceName": "Haechi",
"variables" : {
"exampleVarName": 123
},
"contracts": {
"ContractKeyName1": {
"path": "./contracts/Contract1.sol",
"name": "Contract1",
"constructorArguments": [
"${contracts.ContractKeyName1.address}",
"${variables.exampleVarName}"
],
"initialize": {
"functionName": "initialize",
"arguments": ["argument1", "argument2"]
}
},
"ContractKeyName2": {
"path": "./contracts/Contract2.sol",
"name": "Contract2",
"initialize": {
"functionName": "initialize",
"arguments": ["argument1", "argument2"]
}
}
}
}
```
See more information at [here](./CONFIGURATION.md#service) for more information about `service.vvisp.json`.
Now you can use `deploy-service` command.
### Deploy First Version
1. Write `service.vvisp.json` file.
1. Make `from` variable in `vvisp-config.js`.
See more details at [here](./CONFIGURATION.md#vvisp-configjs).
1. Run `vvisp deploy-service` at root directory.
It will act like [this demo](https://youtu.be/tEpBaaZDGpw).
1. Wait for deploying the sample app.
Then, `state.vvisp.json` will be generated.
**This file is necessary to upgrade your service**
### Upgrade to Second Version
Add contract property at `service.vvisp.json#contracts` like:
```json
"contracts": {
...
"NewContract": {
"path": "./contracts/NewContract.sol",
"name": "NewContract"
}
}
```
Then, run `vvisp deploy-service`.
It will act like [this demo](https://youtu.be/f4WaBhsk_IQ).
> See more details about `vvisp deploy-service` at [here](./packages/vvisp/commands/README.md#deploy-service)
### Use console
If the service is already deployed and has `state.vvisp.json`(**necessary**), you can operate your contracts with `vvisp console`.
First, make apis of contracts which are written in `state.vvisp.json`.
```bash
$ vvisp gen-script
```
Then run `vvisp console` and operate functions of your contracts.
> See more details about `vvisp console` at [here](./packages/vvisp/commands/README.md#console)
## Contract
- Create your own contracts in `contracts/` directory.
## Test
- We support use [truffle](https://truffleframework.com/truffle) framework.
- Create test files in `test/` directory.
- Run `npm run test` to test all test files in `test/` directory or `npm run test <fileName>` to test specific file.
## Commands
Please see [here](./packages/vvisp/commands/README.md) for details.
## Contact
- General Contact: [email protected]
- [Facebook](https://www.facebook.com/HAECHILABS/)
- [Medium](https://medium.com/haechi-labs)
| 24.716049 | 130 | 0.662837 | eng_Latn | 0.634814 |
b054ac209a3b14c66fe1102f1b3b47244735bc76 | 2,203 | md | Markdown | README.md | ohanedan/HashtagTracker | 6b532b6d6730536954477bc691241488da22f748 | [
"MIT"
] | null | null | null | README.md | ohanedan/HashtagTracker | 6b532b6d6730536954477bc691241488da22f748 | [
"MIT"
] | null | null | null | README.md | ohanedan/HashtagTracker | 6b532b6d6730536954477bc691241488da22f748 | [
"MIT"
] | null | null | null | # HashtagTracker
## Welcome
**HashtagTracker** is tracking hashtags on social platforms(Twitter, Instagram etc.) and serving data on a socket real time. With this repository, you can track any hashtag on social platforms.
## Usage
1. set config file
2. start server
3. using any tcp client for connecting or design your own interface and show the data you have acquired over tcp.
## Available Sources
* Twitter (need twitter api)
* Instagram
You can add any platform you want. Just create new class that extends ISource and send data with ISource's newData function.
## Client Messages
* {"key":"password", "value": "YOUR socketAuthKey"} : After connecting to the socket, you must send this message for verification before the timeout period you specified.
* {"key":"close"} : Send this message to close the socket connection cleanly.
## Config Settings
tcpHost: tcp host to listen
tcpPort: tcp port
socketAuthKey: password to be used during login for data security
socketLoginTimeout : login timeout
sources: You can set the hashtags and platforms you want to follow in this array.
## Example Sources Array
sources: [
new Twitter("HASHTAG", {
consumer_key: 'YOUR TWITTER API CONSUMER KEY',
consumer_secret: 'YOUR TWITTER API CONSUMER SECRET',
access_token_key: 'YOUR TWITTER API ACCESS TOKEN',
access_token_secret: 'YOUR TWITTER API ACCESS TOKEN SECRET'
}),
new Instagram("HASHTAG", 1000)
]
## Example Output
{"platform":"Instagram","hashtag":"galatasaray","data":{"user":"SOME USER","text":"Bu gölü atabilecek arkadaşını etiketle.\n\n#millitakım #messi #neymar #mbappe #zlatanibrahimovic #hakançalhanoğlu #grizmann #cengizunder #galatasaray #ultraslan #gfb #fenerbahçe #beşiktaş #çarşı #falcao #muslera #kaanayhan #türkiye","timestamp":1580328451,"image":"there will be a link here"},"type":"data"}
## Used Packages
* [node-twitter](https://github.com/desmondmorris/node-twitter)
* [instagram-hashtag-scrapper](https://github.com/estebansanti/instagram-hashtag-scrapper)
## Copyright and License
**HashtagTracker** is licensed under the MIT license.
| 42.365385 | 407 | 0.720381 | eng_Latn | 0.725833 |
b055bd76fe4933cb2c1ba85f0312b07484a17308 | 460 | md | Markdown | _Python/2019-07-09-python4.md | lar542/lar542.github.io | afe4c78bfd5e100582a312c043c6bd0dc16b8712 | [
"MIT"
] | 2 | 2019-02-27T04:30:01.000Z | 2019-02-28T04:13:09.000Z | _Python/2019-07-09-python4.md | lar542/lar542.github.io | afe4c78bfd5e100582a312c043c6bd0dc16b8712 | [
"MIT"
] | 3 | 2020-02-27T11:00:29.000Z | 2022-02-26T05:42:17.000Z | _Python/2019-07-09-python4.md | lar542/lar542.github.io | afe4c78bfd5e100582a312c043c6bd0dc16b8712 | [
"MIT"
] | null | null | null | ---
layout: post
title: Python - 모든 대문자, 소문자, 대소문자, 숫자 가져오기
tags: [python]
bigimg: /img/title_img/201907.jpg
---
[파이썬을 파이썬답게](https://programmers.co.kr/learn/courses/4008/lessons/12729)
[문자열 상수](https://docs.python.org/ko/3/library/string.html)
### 모든 대문자, 소문자, 대소문자, 숫자 가져오기
* 파이썬에서는 데이터를 상수로 정의해놓았기 때문에 쉽게 가져올 수 있다.
```python
import string
string.ascii_lowercase # 소문자
string.ascii_uppercase # 대문자
string.ascii_letters # 대소문자 모두
string.digits # 숫자
``` | 21.904762 | 75 | 0.715217 | kor_Hang | 0.997904 |
b057dbaefc19302f11d29bab86cdc1dca3e2e342 | 954 | md | Markdown | content/posts/2010-03-08-rackspace-cloud-tech-podcast-episode-2.md | salty-horse/major.io | 8ec285efb4fd004801541c54e94ecdf4fe95f05f | [
"Apache-2.0"
] | 1 | 2021-05-29T18:21:48.000Z | 2021-05-29T18:21:48.000Z | content/posts/2010-03-08-rackspace-cloud-tech-podcast-episode-2.md | salty-horse/major.io | 8ec285efb4fd004801541c54e94ecdf4fe95f05f | [
"Apache-2.0"
] | 21 | 2021-06-07T02:09:16.000Z | 2022-03-31T18:29:00.000Z | content/posts/2010-03-08-rackspace-cloud-tech-podcast-episode-2.md | salty-horse/major.io | 8ec285efb4fd004801541c54e94ecdf4fe95f05f | [
"Apache-2.0"
] | 6 | 2021-01-06T11:39:38.000Z | 2022-02-19T17:48:23.000Z | ---
title: Rackspace Cloud Tech Podcast Episode 2
author: Major Hayden
type: post
date: 2010-03-09T01:51:39+00:00
url: /2010/03/08/rackspace-cloud-tech-podcast-episode-2/
aktt_notify_twitter:
- no
dsq_thread_id:
- 3678954732
categories:
- Blog Posts
tags:
- cloud
- security
- sysadmin
---
<span class="youtube"><iframe title="YouTube video player" class="youtube-player" type="text/html" width="620" height="385" src="//www.youtube.com/embed/QC4KxSbWKEQ?wmode=transparent&fs=1&hl=en&modestbranding=1&iv_load_policy=3&showsearch=0&rel=1&theme=dark&hd=1" frameborder="0" allowfullscreen></iframe></span>
I participated in a [podcast][1] for the [Rackspace Cloud][2] with [Robert Collazo][3] last week. We covered some important topics including network security and convenient deployment tools.
[1]: http://www.rackspacecloud.com/blog/2010/03/05/tech-cloud-cast-episode-2/
[2]: http://rackspacecloud.com/
[3]: http://twitter.com/rcollazo | 38.16 | 312 | 0.747379 | eng_Latn | 0.369 |
b0586cbd633a229f64072eba3081f23a269cea7d | 147 | md | Markdown | .changes/api-add-log-dir.md | facklambda/tauri | 1fbc8237e50149f1b390e0c48bb4e38fde2cc26a | [
"Apache-2.0",
"MIT"
] | 37,185 | 2019-08-27T07:04:29.000Z | 2022-03-31T23:21:09.000Z | .changes/api-add-log-dir.md | facklambda/tauri | 1fbc8237e50149f1b390e0c48bb4e38fde2cc26a | [
"Apache-2.0",
"MIT"
] | 1,718 | 2019-09-09T15:31:05.000Z | 2022-03-31T19:05:14.000Z | .changes/api-add-log-dir.md | facklambda/tauri | 1fbc8237e50149f1b390e0c48bb4e38fde2cc26a | [
"Apache-2.0",
"MIT"
] | 1,007 | 2019-08-26T13:54:01.000Z | 2022-03-29T08:02:17.000Z | ---
"api": minor
---
Add `logDir` function to the `path` module to access the sugested log directory.
Add `BaseDirectory.Log` to the `fs` module.
| 21 | 80 | 0.70068 | eng_Latn | 0.941574 |
b058744d924c92e35b250e551bdf633e4b659529 | 35 | md | Markdown | README.md | IDOshi201109/FrontEndVue | 32a80f186de865d65c979efa1cd676f34e755ec0 | [
"Apache-2.0"
] | null | null | null | README.md | IDOshi201109/FrontEndVue | 32a80f186de865d65c979efa1cd676f34e755ec0 | [
"Apache-2.0"
] | null | null | null | README.md | IDOshi201109/FrontEndVue | 32a80f186de865d65c979efa1cd676f34e755ec0 | [
"Apache-2.0"
] | null | null | null | # FrontEndVue
Big front end of VUE
| 11.666667 | 20 | 0.771429 | eng_Latn | 0.672474 |
b0589e4bc5d869369d1d69a443440f095739c07e | 1,633 | md | Markdown | src/sv/2020-04/03/05.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 68 | 2016-10-30T23:17:56.000Z | 2022-03-27T11:58:16.000Z | src/sv/2020-04/03/05.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 367 | 2016-10-21T03:50:22.000Z | 2022-03-28T23:35:25.000Z | src/sv/2020-04/03/05.md | PrJared/sabbath-school-lessons | 94a27f5bcba987a11a698e5e0d4279b81a68bc9a | [
"MIT"
] | 109 | 2016-08-02T14:32:13.000Z | 2022-03-31T10:18:41.000Z | ---
title: De laglydigas mödor och kamper
date: 14/10/2020
---
Det finns stora fördelar med att följa Guds lag, som man ser i livet hos dem som Gud har gett framgång. Josua följde Guds föreskrifter noga och ledde Israels folk väl. Nu och då talade Herren om för Israel att om de lydde lagen skulle de ha framgång.
`Läs 2 Krön. 31:20, 21. Vad säger de här verserna om huvudorsakerna till Hiskias framgång?`
Vilket utbildningssammanhang vi än befinner oss i behöver vi betona vikten av lydnad i vår undervisning. Men människor är inte dumma. De lägger förr eller senare märke till det kalla faktumet att vissa personer är trogna, kärleksfulla och lydiga. Men än sen då? Olyckor händer även dem. Hur förklarar vi det?
Faktum är att vi inte kan förklara det. Vi lever i syndens och ondskans värld där den stora striden rasar, och ingen av oss är immun mot den.
`Vad säger dessa texter oss om denna svåra fråga? Mark. 6:25–27; Job 1, 2; 2 Kor. 11:23–29.`
Utan tvekan har inte goda, trogna och laglydiga människor alltid haft framgång, i varje fall inte som världen förstår den. Även här finns kanske delvis ett svar på denna svåra fråga som brukar uppstå när vi försöker lära ut vikten av lagen. Exakt vad menar vi med framgång? Vad sade psalmisten? ”Jag står hellre vid tröskeln i min Guds hus än jag bor i de gudlösas tält” (Ps. 84:11). Utan tvekan har inte alla de som är trogna mot Gud och lyder hans lag alltid framgång mätt med världens mått, i varje fall inte nu. Vi gör människor en björntjänst om vi säger något annat.
`Läs Heb. 11:13–16. Hur hjälper dessa verser oss att förstå varför de trogna ändå lider i detta liv?` | 90.722222 | 572 | 0.77526 | swe_Latn | 1.00001 |
b059456fa3cb6f78a5e60b007cbcc5e067ad5658 | 68 | md | Markdown | README.md | dsboo/collection-by-rust | 52e1657d272ff22da7eb8db9b0e97c20877599ba | [
"MIT"
] | null | null | null | README.md | dsboo/collection-by-rust | 52e1657d272ff22da7eb8db9b0e97c20877599ba | [
"MIT"
] | null | null | null | README.md | dsboo/collection-by-rust | 52e1657d272ff22da7eb8db9b0e97c20877599ba | [
"MIT"
] | null | null | null | # collection-by-rust
implements collection by rust, just for study
| 17 | 45 | 0.794118 | eng_Latn | 0.983137 |
b05a2dd9e8f9dad2df1795254bd92262c3caa4bf | 4,899 | md | Markdown | AUTHORS.md | fschoeni/homework_no2 | e833905095c14579a20337ae0530c3a48650394e | [
"Apache-2.0"
] | 52 | 2018-10-15T07:28:15.000Z | 2022-03-11T16:51:48.000Z | AUTHORS.md | fschoeni/homework_no2 | e833905095c14579a20337ae0530c3a48650394e | [
"Apache-2.0"
] | 32 | 2018-11-04T19:54:09.000Z | 2021-12-20T16:23:27.000Z | AUTHORS.md | fschoeni/homework_no2 | e833905095c14579a20337ae0530c3a48650394e | [
"Apache-2.0"
] | 28 | 2018-10-15T07:28:41.000Z | 2022-03-11T16:51:37.000Z | # Authors
## Authorship of the notebooks
All notebooks were created
by [Daniel Huppmann](https://www.iiasa.ac.at/staff/huppmann)
([@danielhuppmann](https://github.com/danielhuppmann))
in close collaboration with the authors of Chapter 2
of the **IPCC Special Report on Global Warming of 1.5°C**
([Rogelj, Shindell, Jiang, et al., 2018](http://www.ipcc.ch/report/sr15/)).
Joeri Rogelj, Elmar Kriegler, Luis Mundaca, Piers Forster, Shigeki Kobayashi,
Roland Séférian, María Virginia Vilariño and other authors of the SR15
contributed to the methodology of the assessment and development of figures
and tables generated by the notebooks.
## Authorship of the scenario ensemble
### Guidelines for authorship of the scenario ensemble
For release 1.0, the IAMC Steering Committee agreed on the following rules
for the list of authors for the scenario resource:
1) the group of people involved in the collection, vetting,
and review of the scenario data,
2) all first authors of the studies that submitted scenarios to the ensemble,
3) in case that modelling teams have a limited number of first-authors,
it is possible to nominate additional authors. In this case, each team can
nominate one author per study that they contributed to,
up to a maximum of three authors (ie, under point (2) and (3) each team
is eligible to a total number of three authors, unless more than three
first-author studies were submitted by the team).
Following the approval and acceptance of the
[IPCC's Special Report on Climate Change and Land (SRCCL)](https://www.ipcc.ch/report/srccl/),
the list of authors was amended to acknowledge the significant contribution
by several authors of the SRCCL regarding the additional analysis and extension
of the scenario ensemble.
### List of authors (as of Release 2.0)
Group of authors involved in the collection, vetting,
and review of scenario data (see guidelines, item 1):
- Daniel Huppmann (SR1.5 Chapter 2 author, coordination, review & vetting,
technical implementation and data transfer)
- Elmar Kriegler (SR1.5 Chapter 2 author, vetting & review)
- Volker Krey (technical implementation and data transfer)
- Keywan Riahi (SR1.5 Chapter 5 author, review, project lead)
- Joeri Rogelj (SR1.5 Chapter 2 author, vetting & review)
- Katherine Calvin (SRCCL Chapter 6 author, vetting & review)
- Florian Humpenoeder (SRCCL Chapter 2 author, vetting & review)
- Alexander Popp (SRCCL Chapter 2 author, vetting & review)
- Steven Rose (major contributions to the IAMC-IPCC coordination and the MoU)
- John Weyant (major contributions to the IAMC-IPCC coordination and the MoU)
Authors representing modelling teams that submitted scenarios
to the ensemble (see guidelines, items 2 and 3):
- Nico Bauer *(REMIND-MAgPIE, Bauer et al., forthcoming)*
- Christoph Bertram *(REMIND-MAgPIE, Bertram et al., 2018)*
- Valentina Bosetti *(WITCH, nominated per guidelines item 3)*
- Jonathan Doelman *(IMAGE, nominated per guidelines item 3)*
- Laurent Drouet *(WITCH, nominated per guidelines item 3)*
- Johannes Emmerling *(WITCH, nominated per guidelines item 3)*
- Stefan Frank *(MESSAGEix-GLOBIOM, nominated per guidelines item 3)*
- Shinichiro Fujimori *(AIM, nominated per guidelines item 3)*
- David Gernaat *(IMAGE, nominated per guidelines item 3)*
- Arnulf Grubler *(MESSAGEix-GLOBIOM, Grubler et al., 2018)*
- Céline Guivarch *(IMACLIM, nominated per guidelines item 3)*
- Martin Haigh *(Shell, Shell International B.V., 2018)*
- Christian Holz *(C-ROADS, Holz et al., 2018)*
- Gokul Iyer *(GCAM, nominated per guidelines item 3)*
- Etsushi Kato *(GRAPE, nominated per guidelines item 3)*
- Kimon Keramidas *(POLES, nominated per guidelines item 3)*
- Alban Kitous *(POLES, nominated per guidelines item 3)*
- Florian Leblanc *(IMACLIM, nominated per guidelines item 3)*
- Jing-Yu Liu *(AIM, Liu et al., 2018)*
- Konstantin Löffler *(GENeSYSMOD, Löffler et al., 2017)*
- Gunnar Luderer *(REMIND-MAgPIE, Luderer et al., 2018)*
- Adriana Marcucci *(MERGE-ETL, Marcucci et al., 2017)*
- David McCollum *(MESSAGEix-GLOBIOM, McCollum et al., 2018)*
- Silvana Mima *(POLES, nominated per guidelines item 3)*
- Ronald D. Sands *(FARM, nominated per guidelines item 3)*
- Fuminori Sano *(DNE21+, nominated per guidelines item 3)*
- Jessica Strefler *(REMIND-MAgPIE, Strefler et al., 2018)*
- Junichi Tsutsui *(BET, nominated per guidelines item 3)*
- Detlef van Vuuren *(IMAGE, Van Vuuren et al., 2018)*
- Zoi Vrontisi *(GEM-E3, Vrontisi et al., 2018)*
- Marshall Wise *(GCAM, nominated per guidelines item 3)*
- Runsen Zhang *(AIM, Zhang et al., 2018)*
## Acknowledgements
The authors wish to thank Peter Kolp for the technical support in the
compilation and data management of the scenario ensemble.
Nikolay Kushin and Michael Pimmer are acknowledged for their contribution to
the development of the scenario explorer and the database infrastructure.
| 49.484848 | 94 | 0.760155 | eng_Latn | 0.91549 |
b05aa221da148de29ab2dccb04ff15dc772d38f3 | 2,385 | md | Markdown | README.md | nginformatica/rung-tools | c8906bb6733bdd5bcea2e9b54ed48f26ae1526d5 | [
"MIT"
] | 19 | 2017-03-06T19:25:34.000Z | 2021-07-08T00:52:33.000Z | README.md | nginformatica/rung-tools | c8906bb6733bdd5bcea2e9b54ed48f26ae1526d5 | [
"MIT"
] | 56 | 2017-04-19T12:29:57.000Z | 2018-09-07T05:42:09.000Z | README.md | nginformatica/rung-tools | c8906bb6733bdd5bcea2e9b54ed48f26ae1526d5 | [
"MIT"
] | 4 | 2017-04-18T17:08:41.000Z | 2018-01-17T09:50:08.000Z | # Rung CLI
[](https://npmjs.org/package/rung-cli)
[](https://www.npmjs.com/package/rung-cli)
[](https://travis-ci.org/rung-tools/rung-cli)
[](https://codeclimate.com/github/rung-tools/rung-cli)
[](https://scrutinizer-ci.com/g/rung-tools/rung-cli/?branch=master)
[](https://snyk.io/test/github/rung-tools/rung-cli)
[](https://codecov.io/gh/rung-tools/rung-cli)
[](https://www.npmjs.com/package/rung-cli)
Command line tools for Rung
## Installation
`sudo npm install -g rung-cli`
This will make the command `rung` available globally.
## Documentation
You can checkout the last docs in [this link](https://developers.rung.com.br/docs/)!
## Features
- Create blank apps
- Generate `.rung` packages
- Run apps locally in CLI mode
- Publish apps to Rung Store (public and private)
- Generate boilerplate code for app
- Generate README.md file to publish
- Test autocomplete directly in the terminal
- Hot reloading and live development
## Usage
`rung [build|run|publish|boilerplate|readme|db]`
### Commands
| Command | Description |
|---------------|-------------|
| `build` | Generate a .rung package |
| `run` | Execute the current app |
| `publish` | Publish app to store |
| `boilerplate` | Generate boilerplate code for the app |
| `readme` | Generate the README.md file to publish |
| `db read` | Read from app database |
| `db clear` | Drop app database |
### Options
| Option | Description |
|------------------|-------------|
| `-o`, `--output` | Where to save the built package |
| `--version` | Displays versions |
| `--private` | If set, app is published for current user only |
| `--raw` | Displays returned cards outside a table |
| `--live` | With `run`, starts hot compiling and preview on browser |
| 38.467742 | 178 | 0.677149 | eng_Latn | 0.434602 |
b05adea571a7c6d340ae0aa4da3ba11f3ed021de | 74 | md | Markdown | README.md | AdrianBerme/Primer-Repositorio | f6721c2b48c39d336832febfdf9d2f8e02ec4448 | [
"MIT"
] | null | null | null | README.md | AdrianBerme/Primer-Repositorio | f6721c2b48c39d336832febfdf9d2f8e02ec4448 | [
"MIT"
] | null | null | null | README.md | AdrianBerme/Primer-Repositorio | f6721c2b48c39d336832febfdf9d2f8e02ec4448 | [
"MIT"
] | null | null | null | # Primer-Repositorio
Esta es la primera edicion desde Geekshubs Academy.
| 18.5 | 51 | 0.810811 | spa_Latn | 0.982323 |
b05b3887f819c82de49fb5f608326727691389f0 | 100 | md | Markdown | README.md | BrianStaton/nanoprintf_test | 1a2409461e4ca27d497c1ca00f38460a5361ae37 | [
"MIT-0"
] | null | null | null | README.md | BrianStaton/nanoprintf_test | 1a2409461e4ca27d497c1ca00f38460a5361ae37 | [
"MIT-0"
] | null | null | null | README.md | BrianStaton/nanoprintf_test | 1a2409461e4ca27d497c1ca00f38460a5361ae37 | [
"MIT-0"
] | null | null | null | Small example driver for nanoprintf as obtained from https://github.com/charlesnicholson/nanoprintf
| 50 | 99 | 0.85 | eng_Latn | 0.881221 |
b05b8323a4f1e0445d965e0c85f54402e8967a00 | 339 | md | Markdown | Languages/README.md | tanycypris/Open-Science-Training-Handbook_DE | 93e83d99aac3a2c9b51526a2e8e837667ce532d5 | [
"CC0-1.0"
] | 3 | 2019-07-04T13:18:41.000Z | 2019-07-28T13:28:16.000Z | Languages/README.md | tosteiner/Open-Science-Training-Handbook_DE | d05d26cdedff16c044dead0d85b0c90680132d82 | [
"CC0-1.0"
] | null | null | null | Languages/README.md | tosteiner/Open-Science-Training-Handbook_DE | d05d26cdedff16c044dead0d85b0c90680132d82 | [
"CC0-1.0"
] | 1 | 2019-07-18T08:08:28.000Z | 2019-07-18T08:08:28.000Z | The handbook has been translated into Spanish and Portuguese:
* [Portuguese translation](https://book.fosteropenscience.eu/pt)
* [Spanish translation](https://book.fosteropenscience.eu/es)
Currently, we are translating the book into more languages such as Greek, French and Italian. We will link them here as soon as they are availabe.
| 48.428571 | 146 | 0.79056 | eng_Latn | 0.999129 |
b05cddaa47c2c21e9dc5da0f5ce4851a5c0dd6d2 | 118 | md | Markdown | README.md | 1Strategy/ml-immersion | 5d03ba612ec115366c2fa3937e52350641507fcc | [
"Apache-2.0"
] | 1 | 2020-08-15T01:48:11.000Z | 2020-08-15T01:48:11.000Z | README.md | 1Strategy/ml-immersion | 5d03ba612ec115366c2fa3937e52350641507fcc | [
"Apache-2.0"
] | null | null | null | README.md | 1Strategy/ml-immersion | 5d03ba612ec115366c2fa3937e52350641507fcc | [
"Apache-2.0"
] | null | null | null | # ml-immersion
This is the Jupyter notebook and all infrastructure-as-code necessary to conduct the ML Immersion day. | 39.333333 | 102 | 0.813559 | eng_Latn | 0.998249 |
b05d7b1291f815b50f4129cac6fceb3c41f6df73 | 215 | md | Markdown | thanks.md | sstubben/sstubben.github.io | e20f5a23587032c6f05fa7c20d300194c16ae1ff | [
"MIT"
] | null | null | null | thanks.md | sstubben/sstubben.github.io | e20f5a23587032c6f05fa7c20d300194c16ae1ff | [
"MIT"
] | null | null | null | thanks.md | sstubben/sstubben.github.io | e20f5a23587032c6f05fa7c20d300194c16ae1ff | [
"MIT"
] | null | null | null | ---
title: Thanks, I'll be in touch
permalink: thanks/
profile: false
---
Thanks for contacting me!
=========================
I'll be in touch within 24 hours.
Looking forward to doing business with you -- Simon
| 16.538462 | 51 | 0.637209 | eng_Latn | 0.985044 |
b05de2f50c6f3d9fc6e3be1ad708b1191bc3c3e7 | 1,084 | md | Markdown | README.md | Rakeshbaral/BNN_PedestrianDetection | a236d768a72138bbee9e600a6197570bb8b0859d | [
"MIT"
] | null | null | null | README.md | Rakeshbaral/BNN_PedestrianDetection | a236d768a72138bbee9e600a6197570bb8b0859d | [
"MIT"
] | null | null | null | README.md | Rakeshbaral/BNN_PedestrianDetection | a236d768a72138bbee9e600a6197570bb8b0859d | [
"MIT"
] | null | null | null | # BNN_PedestrianDetection
We introduce a method to train Binarized Neural Networks (BNNs) - neural networks with binary weights and activations at run-time. At
training-time the binary weights and activations
are used for computing the parameters gradients. During the forward pass, BNNs drastically
reduce memory size and accesses, and replace
most arithmetic operations with bit-wise operations, which is expected to substantially improve
power-efficiency.
Implementing the DenseNet over INRIA dataset gives below plot while training the model. Here the Adam optimizer is used to train.
<img width="305" alt="Capture" src="https://user-images.githubusercontent.com/16417735/135139891-428aad50-d950-43b7-b435-5063a9d1ac59.PNG">
The confusion matrix below gives the idea of the accuracy we got from the implementation.
<img width="267" alt="Capture" src="https://user-images.githubusercontent.com/16417735/135140208-c63c2f2e-bfdb-46c0-8490-82b6b62ae281.PNG">
Working on the results and accuracy details in application to the INRIA and Caltech Datset, will be updated soon.
| 54.2 | 139 | 0.810886 | eng_Latn | 0.980069 |
b05e283c7cbca640a96a97f271072ee383cc0b2e | 593 | md | Markdown | README.md | ddstevenson/fullstack-fall2020-kanban | 3c47fdc76affc06fbbc6053f0b68559fad561eaa | [
"MIT"
] | null | null | null | README.md | ddstevenson/fullstack-fall2020-kanban | 3c47fdc76affc06fbbc6053f0b68559fad561eaa | [
"MIT"
] | null | null | null | README.md | ddstevenson/fullstack-fall2020-kanban | 3c47fdc76affc06fbbc6053f0b68559fad561eaa | [
"MIT"
] | null | null | null | # fullstack-fall2020-kanban
Kanban board: a school project for Fullstack Fall 2020 at PSU
Project Proposal: https://docs.google.com/presentation/d/1BazgAoAFoid8L48jLV15G_iHL0s3xWJhquiOhN1QRtM/edit?ts=5f89d86e#slide=id.p
# Unit Testing
Type `npm run test` at the command prompt.
For more information about jest, see the official docs at: https://jestjs.io/docs/en/getting-started
Thanks to https://www.w3school.com/howto/howto_js_draggable.asp for direction on dragging of modals,
as well as https://web.dev/drag-and-drop/ for getting our taskbox drag-and-drop functionality off the ground.
| 49.416667 | 129 | 0.804384 | eng_Latn | 0.657507 |
b05e959e4775623068dc6c2e93b555ce0a6087cf | 4,916 | md | Markdown | _drafts/horton-hears-a-document-db.md | jdaigle/jdaigle.github.io | 812cd3c94123b34655a41e1f802a4a36a0bbb8ca | [
"MIT"
] | null | null | null | _drafts/horton-hears-a-document-db.md | jdaigle/jdaigle.github.io | 812cd3c94123b34655a41e1f802a4a36a0bbb8ca | [
"MIT"
] | null | null | null | _drafts/horton-hears-a-document-db.md | jdaigle/jdaigle.github.io | 812cd3c94123b34655a41e1f802a4a36a0bbb8ca | [
"MIT"
] | null | null | null | ---
title: Horton Hears a Document DB
layout: post
---
[Document-oriented database](https://en.wikipedia.org/wiki/Document-oriented_database) models are gaining increased popularity with developers. In particular we see dedicated document databases such as MongoDB and RavenDB, and online PaaS offerings from Amazon, Microsoft, and Google.
At its core a document-oriented database is simply a key/value store. The value, in this case, is a usually a serialized "document" with a loose schema. For example, XML or JSON. And most implementations provide ACID transactions around *just a single document*.
Many implementations also include the ability index, map, and/or query based on the *content* of the document. These implementations are aware of the particular document serialization and contain native methods to parse and query. Some expose custom query DSL. Others incorporate and expose search engines such as [Lucene](https://lucene.apache.org/). Some implementations also incorporate server-side [MapReduce](https://en.wikipedia.org/wiki/MapReduce) engines.
But many of these features are either included with, or can be built upon, the powerful relational databases that many of us use everyday. I was inspired by Jeremy Miller's recent exploration into using [Postgresql as a Document Db for .Net Development](http://jeremydmiller.com/2015/10/21/postgresql-as-a-document-db-for-net-development/). For a previous project, I built a document database on top of Microsoft SQL Server using its XML data type. I built a small client library that worked like an ORM exposing a unit of work and encapsulating the work of querying, change-tracking, and serialization.
I decided to resurrect the idea as a proof-of-concept.
## HortonDB: Proof of Concept
[HortonDB](https://github.com/jdaigle/hortondb) is a proof-of-concept .NET library that uses Microsoft SQL Server and XML data as a document database. The code is open source and hosted on GitHub.
**Why XML over JSON?** The simple answer is that SQL Server currently has decent support for XML and not JSON. But XML isn't so bad. It's widely supported by virtually all platforms and frameworks, and has pretty good tooling. SQL Server, in particular, has support for:
* Schema Validation
*
### Features
Since this is just a proof-of-concept, I didn't include every feature possible.
* **Unit of Work.** There's an `IDocumentSession` which is responsible for tracking changes all loaded documents, new documents, and deleted documents. Changes are persisted back to the database when the user calls `SaveChanges()`.
* **Identity Map.** The identity map provides the first-level cache for instance of a document session. This allows one to `Load()` a document multiple times during a unit of work and always return the same instance. It is also responsible for maintaining the dictionary of the internal metadata required for the library.
**Not Implemented Features:**
* **Load by IDs**. Quickly load multiple documents (perhaps in batches?) given a set of IDs.
* **Querying.** The library only supports simple CRUD operations. Building a querying API is tricky business which I'll talk about in a bit.
* **Result Caching.** Also known as a second-level cache or aggressive cache. Retrieving a single document and de-serializing it into an object is an expensive operation. For documents that are frequently accessed, but rarely change, we can cache the object instance and return that instance on `Load()` until we detect the data has changed in the database. Because it's a single copy of an object, generally this object should be used "read-only". This could be implemented with SQL Server's rowversion column.
* **Read-only Documents**. Simply, documents that should not change and thus do not need to be tracked.
* **Bulk Insert**.
### Queries
SQL Server has native support for query XML data, along with other operations. I won't go into a lot of details as it's [fairly well document](https://msdn.microsoft.com/en-us/library/ms190798.aspx). Natively, SQL Server uses a query language called [XQuery](https://msdn.microsoft.com/en-us/library/ms189075.aspx).
### Indexing
partial decomposition into relational? (persisted computed columns)
[Promote Frequently Used XML Values with Computed Columns](https://msdn.microsoft.com/en-us/library/bb500236.aspx)
### JSON Support
## Further Reading / References
* [Sql Server XML columns substitute for Document DB?](http://stackoverflow.com/questions/5119660/sql-server-xml-columns-substitute-for-document-db).
* Jeremy Miller has recently starting building an OSS project around using [PostgreSQL as a Document Db for .Net Development](http://jeremydmiller.com/2015/10/21/postgresql-as-a-document-db-for-net-development/).
* Rob Conery has [done the same thing](http://rob.conery.io/2015/08/20/designing-a-postgresql-document-api/). | 87.785714 | 604 | 0.775224 | eng_Latn | 0.995173 |
b05f38740d5dee472ded6f32dd6262fb9081b3bb | 1,424 | md | Markdown | README.md | TFHInc/artisan-format | 2e6230f7ad01aa4222d466f640b9c7d7d407326d | [
"MIT"
] | 1 | 2019-07-18T19:54:11.000Z | 2019-07-18T19:54:11.000Z | README.md | TFHInc/artisan-format | 2e6230f7ad01aa4222d466f640b9c7d7d407326d | [
"MIT"
] | 1 | 2018-03-08T03:17:40.000Z | 2018-03-08T03:17:40.000Z | README.md | TFHInc/artisan-format | 2e6230f7ad01aa4222d466f640b9c7d7d407326d | [
"MIT"
] | null | null | null | # Artisan Format
[](LICENSE.md)
Format Laravel Artisan command output.
## Requirements
This package requires:
- PHP >= 7.0.0
- Laravel >= 5.5
## Installation
Install the package via Composer:
``` bash
composer require tfhinc/artisan-format
```
The package will be found via auto discovery. You may also add the service provider in `app/config.php`:
``` php
TFHInc\ArtisanFormat\ArtisanFormatServiceProvider::class,
```
Publish the `artisan-format.php` configuration file to your `config/` directory:
``` bash
php artisan vendor:publish --provider="TFHInc\ArtisanFormat\ArtisanFormatServiceProvider"
```
## Usage
Artisan Format provides a series of Traits that can be used within your Artisan command classes.
- [Sections](#sections)
### Sections
The Sections trait produces distinct sections of text in your command output.
Include the `ArtianFormatSections` trait in your command class:
``` php
use TFHInc\ArtisanFormat\Traits\ArtisanFormatSections;
class Run extends Command
{
use ArtisanFormatSections;
```
Generate a Section with a Header and Content:
``` php
$this->sectionBox('Standard Section Box Header', 'Standard Section Box Content');
```
Output:
<img src="docs/standard_section_box.png">
## License
The MIT License (MIT). Please see [License File](LICENSE.md) for more information.
| 20.941176 | 109 | 0.754916 | eng_Latn | 0.844959 |
b05f67f3d31490cd33ff4d139f9d552b559ad0eb | 453 | md | Markdown | README.md | AVIRENI-CHANDAN/BackgroundVideoExample | 722a9bb1c3839a0202b23da277cea0068b78b900 | [
"Unlicense"
] | null | null | null | README.md | AVIRENI-CHANDAN/BackgroundVideoExample | 722a9bb1c3839a0202b23da277cea0068b78b900 | [
"Unlicense"
] | null | null | null | README.md | AVIRENI-CHANDAN/BackgroundVideoExample | 722a9bb1c3839a0202b23da277cea0068b78b900 | [
"Unlicense"
] | null | null | null | # BackgroundVideoExample
This is a page purely based on a background as video with video color enhancement to make it look pretty
and match to the concept of the page.
Made of HTML,CSS
| 50.333333 | 132 | 0.827815 | eng_Latn | 0.617129 |
b06042ef61a4921c7ceaab043a612eb7281f51fb | 887 | md | Markdown | README.md | telebovich/Calendar | 0f995be60af8664b3fc4991efcdf148934f142c8 | [
"MIT"
] | 1 | 2021-03-03T13:01:33.000Z | 2021-03-03T13:01:33.000Z | README.md | telebovich/Calendar | 0f995be60af8664b3fc4991efcdf148934f142c8 | [
"MIT"
] | null | null | null | README.md | telebovich/Calendar | 0f995be60af8664b3fc4991efcdf148934f142c8 | [
"MIT"
] | null | null | null | # Calendar
This is a purity calendar for jewish religious women and for people who want to get familiar with jewish law regarding purity.
Features:
- By default it shows current month.
- Navigation is possible. User can navigate between months.
- By clicking on current month a months screen appears which makes it possible to quick jump between months.
- Clicking on year link opens a new screen that makes possible to jump between years.
- User is able to select a year from 1940 to 2239.
Month View |Year View | Decade View
:----------------------------:|:-------------------------:|:-------------------
 | |
Here is a link where you can check out changes author make to calendar.
[Click for working calendar](http://puritycalendar.azurewebsites.net/Calendar) | 52.176471 | 126 | 0.674183 | eng_Latn | 0.9959 |
b060805f502650a3df19c7d6ace2097310c44ec3 | 15 | md | Markdown | README.md | HearTao/mdx-ts-plugin | 8b355d8c7e17ef6a076e96f408d473b1d8d2f557 | [
"MIT"
] | null | null | null | README.md | HearTao/mdx-ts-plugin | 8b355d8c7e17ef6a076e96f408d473b1d8d2f557 | [
"MIT"
] | null | null | null | README.md | HearTao/mdx-ts-plugin | 8b355d8c7e17ef6a076e96f408d473b1d8d2f557 | [
"MIT"
] | null | null | null | # mdx-ts-plugin | 15 | 15 | 0.733333 | war_Latn | 0.176928 |
b060b2de4f3a4f3a2eeefdeaab6b8f0a5e2ae041 | 1,906 | md | Markdown | LEAN_Approach.md | danieldfgro2000/Recycle | 22417167c4ceb5334532ccb2672d9d5cac3b702b | [
"MIT"
] | null | null | null | LEAN_Approach.md | danieldfgro2000/Recycle | 22417167c4ceb5334532ccb2672d9d5cac3b702b | [
"MIT"
] | null | null | null | LEAN_Approach.md | danieldfgro2000/Recycle | 22417167c4ceb5334532ccb2672d9d5cac3b702b | [
"MIT"
] | null | null | null | # LEAN Approach
#### Project to be divided in 3 main parts:
###### AWARE(low) | PRODUCT (Mid) | SCALE(High)
#
#### This years INNOVATION LAB ENDAVA
#
### Phone App (low)
#### Technology
Android Studio IDE, JAVA / KOTLIN, Firebase SDK
Options to be implemented:
* Recycle Map
* Comunity
* INFO (AWARE)
* Product PROMO
* Market response (community)
Further INFO:
https://www.qualitylogoproducts.com/promo-university/different-types-of-plastic.htm
* identify and categorize different plastic materials
* propose different *recycled* products;
* smart recycle Bin - create raw material (wire/block - First Product)
Analyze capability - further development (time constraint)
* connect to 3D printer
* material requirements (type and quantity)
* allow community to share knowledge;
* DB - bill info - quickly identify used materials and how can they be recycled
#
### Future development (Just presentation during this years INNOVATION LAB ENDAVA)
#### Big Corporations Smart Recycle Bin (mid)
https://www.microsoft.com/en-us/p/azure-kinect-dk/8pp5vxmd9nhq?activetab=pivot%3aoverviewtab
* Smart bin capable of categorising waste material (See BIN-E)
http://www.bine.world/
next step - available products
* develop low cost machine learning object detection system;
* develop 3D printer for wide range materials;
* integrate CNC machine;
* PROMOTE successful products made out of recycled materials, based on data analysis (community)
* machine output capability of finite product;
* Recycle cost reduction capability;
### Industry level equipment, long term contract with legal entity (high)
* high cost for initial investment
* there are options available
* Develop, maintain and improve SW
# Materials to be recycled
## Plastic
###### Focus on plastic - most polluting low energy requirements to process
| 31.245902 | 100 | 0.727177 | eng_Latn | 0.947665 |
b061c7ad57312ac65674a76b3b54f1328c2e56ce | 3,033 | md | Markdown | tests/test.md | rnc/tocdown | eabd52f1b2bc2c70a4ae971f93f82ce3953642af | [
"MIT"
] | 15 | 2016-03-25T13:22:28.000Z | 2021-11-08T20:47:16.000Z | tests/test.md | rnc/tocdown | eabd52f1b2bc2c70a4ae971f93f82ce3953642af | [
"MIT"
] | 7 | 2017-02-10T16:24:59.000Z | 2020-03-04T17:42:41.000Z | tests/test.md | rnc/tocdown | eabd52f1b2bc2c70a4ae971f93f82ce3953642af | [
"MIT"
] | 12 | 2016-10-07T13:58:11.000Z | 2022-03-09T07:02:53.000Z | # Title (Heading 1)
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
```
## Top-level topic that should not be counted
```
## Top-level topic (Heading 2)
<!-- TocDown Begin -->
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
### First sub-topic (Heading 3)
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
#### First sub-sub-topic (Heading 4)
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
##### First sub-sub-sub-topic (Heading 5)
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
###### First sub-sub-sub-sub-topic (Heading 6)
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
### Second sub-topic
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
### Third sub-topic
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
#### A sub-sub-topic
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
##### And a sub-sub-sub-topic
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
## Second top-level topic
Lorem ipsum dolor sit amet, consectetur adipisicing elit. Laudantium, minus, unde, quisquam, nisi soluta aliquid quibusdam ex eos est atque reprehenderit fugit facere in non quae modi officiis saepe numquam.
## Punctuation @tests, etc.!
Some tests of ASCII and Unicode
### Standard ASCII punctuation: !"#$%&'()*+,./:;<=>?@[\]^_`{|}~
### “Curly quotes” (‘single curly quotes’)…
### « Guillemets »
### Text with accents: áéñü
### Chinese 中文、 Cyrillic Русский、 and Korean 한국어
### Düsseldorf, Köln, Москва, 北京市, إسرائيل !@#$
| 48.142857 | 207 | 0.769205 | eng_Latn | 0.172134 |
b0623c147713330500ca7c6c4e00f0e18aaca207 | 2,245 | md | Markdown | README.md | gleenn/dfwearables | 758227137effd3569c5c3dfc8d503d217a6513dd | [
"Apache-2.0"
] | null | null | null | README.md | gleenn/dfwearables | 758227137effd3569c5c3dfc8d503d217a6513dd | [
"Apache-2.0"
] | null | null | null | README.md | gleenn/dfwearables | 758227137effd3569c5c3dfc8d503d217a6513dd | [
"Apache-2.0"
] | null | null | null | # DiscoFish Wearables
[](https://gitlab.com/discofish/dfwearables/commits/master)
### Compiling with Arduino IDE
Install Arduino IDE and required libraries (Unisparks, FastLED, Adafruit_NeoPixel):
Download latest software from https://www.arduino.cc/en/Main/Softwarea
https://www.arduino.cc/download_handler.php?f=/arduino-1.6.10-linux64.tar.xz
cd ~
mv Downloads/arduino-1.6.10-linux64.tar.xz ./
tar -xf arduino-1.6.10-linux64.tar.xz
mkdir -p ~/Arduino/libraries
cd ~/Arduino/libraries
git clone https://[email protected]/discofish/dfsparks.git DFSparks
git clone https://github.com/FastLED/FastLED
~/arduino-1.6.10/arduino &
Open File/Preferences, and add to Additional Boards:
http://arduino.esp8266.com/stable/package_esp8266com_index.json
Open Tools/Boards/BoardsManager, search for esp8266, install
Select Tools/Boards/NodeMCU1.0
Add yourself to dialout group:
sudo usermod -a -G dialout igor
To compile:
~/arduino-1.6.10/arduino &
Click menu option: File/Examples/DFSparks/Vest
Click on the checkmark button to verify
Select Tools/Ports/ttyUSB0
Click the Upload button
You can use extras/test-server.py to test how your device
synchronizes with the server.
## Uploading sketches on OSX
(this is generic stuff not specific to DFSparks library)
To upload sketches to ESP8266 board from Arduino IDE on OSX:
1. Install ESP8266 board. Go to Arduino->Preferences->Settings; Additional board manager URLs
2. Add http://arduino.esp8266.com/stable/package_esp8266com_index.json
3. Install ESP8266 board
4. Install USB to UART drivers. Required drivers seem to be different for different
board flavours.
- For LoLin boards this worked:
http://www.codenuke.net/2015/01/nodemcu-install-ch340-usb-to-serial-for-yosemite.html
- For noname board I got from Amazon this worked:
https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx (/dev/cu.SLAB_USBtoUART)
5. Use NodeMCU 1.0 (ESP-12E) board and port corresponding to USB driver
6. Set serial monitor to 115200 baud
### Testing
(use Unisparks demo or test server) | 36.803279 | 140 | 0.747884 | kor_Hang | 0.312396 |
b063349267a5a534e9ac25995ae623bed5ec1d95 | 2,474 | md | Markdown | docs/mfc/reference/mfc-wizards-and-dialog-boxes.md | OZ1/cpp-docs.ru-ru | 1d358066bf9f8ef536a42449098177e41e6aa9a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/reference/mfc-wizards-and-dialog-boxes.md | OZ1/cpp-docs.ru-ru | 1d358066bf9f8ef536a42449098177e41e6aa9a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/reference/mfc-wizards-and-dialog-boxes.md | OZ1/cpp-docs.ru-ru | 1d358066bf9f8ef536a42449098177e41e6aa9a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "MFC мастеры и диалоговые окна | Документы Microsoft"
ms.custom:
ms.date: 11/04/2016
ms.reviewer:
ms.suite:
ms.technology:
- cpp-windows
ms.tgt_pltfrm:
ms.topic: article
dev_langs:
- C++
ms.assetid: 2fae0a2c-d147-4468-a547-f7b85df767a1
caps.latest.revision:
author: mikeblome
ms.author: mblome
manager: ghogen
ms.workload:
- cplusplus
ms.openlocfilehash: 198fd62e8134a14930d88b478d5ed78b1e8d8e82
ms.sourcegitcommit: 8fa8fdf0fbb4f57950f1e8f4f9b81b4d39ec7d7a
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 12/21/2017
---
# <a name="mfc-wizards-and-dialog-boxes"></a>Мастеры и диалоговые окна MFC
Microsoft Foundation Class (MFC) мастер создает стандартный код для различных типов компонентов и объектов. Можно выполнить мастеров, открыв контекстное меню для проекта в **обозревателе решений** и выбрав **добавить**, **класса**.
## <a name="related-articles"></a>Связанные статьи
|Заголовок|Описание:|
|-----------|-----------------|
|[Создание проекта библиотеки DLL MFC](../../mfc/reference/creating-an-mfc-dll-project.md)|Создает библиотеку DLL, в зависимости от MFC.|
|[Создание приложения MFC](../../mfc/reference/creating-an-mfc-application.md)|Создает приложение MFC.|
|[Создание контейнеров элементов ActiveX MFC](../../mfc/reference/creating-an-mfc-activex-control-container.md)|Создает контейнер для элементов управления ActiveX.|
|[Создание элемента ActiveX MFC](../../mfc/reference/creating-an-mfc-activex-control.md)|Создает элемент управления ActiveX, в зависимости от MFC.|
|[Класс MFC](../../mfc/reference/adding-an-mfc-class.md)|Создает базовый класс.|
|[Класс MFC из библиотеки типов](../../mfc/reference/adding-an-mfc-class-from-a-type-library.md)|Создает класс и заполняет ее зависимости библиотеки типов, можно указать.|
|[Обработчик сообщений MFC](../../mfc/reference/adding-an-mfc-message-handler.md)|Создает обработчик для сообщения Windows.|
|[Потребление MFC ODBC](../../mfc/reference/adding-an-mfc-odbc-consumer.md)|Создает компонент, который может взаимодействовать с базой данных ODBC.|
|[Поддержка ATL в проект MFC](../../mfc/reference/adding-atl-support-to-your-mfc-project.md)|Создает заголовки и макросы, которые требуются по Active Template Library (ATL).|
|[Мастер классов MFC](../../mfc/reference/mfc-class-wizard.md)|Создает h-файл и CPP-файл.|
|[Приложения MFC для рабочего стола](../../mfc/mfc-desktop-applications.md)|Ссылки на документацию MFC.|
| 54.977778 | 233 | 0.744947 | rus_Cyrl | 0.58701 |
b0635df3cb60637af8d212ea244f703532a9fad4 | 1,288 | md | Markdown | README.md | krissrex/docker-jenkins-dockercli | 98e03abd99b037937e899f613a266c0f488809b5 | [
"MIT"
] | null | null | null | README.md | krissrex/docker-jenkins-dockercli | 98e03abd99b037937e899f613a266c0f488809b5 | [
"MIT"
] | null | null | null | README.md | krissrex/docker-jenkins-dockercli | 98e03abd99b037937e899f613a266c0f488809b5 | [
"MIT"
] | null | null | null | # Jenkins docker image with docker-cli
## Why
The docker binary can no longer be mounted from the host OS to the jenkins docker container.
The reason is that the binary does not use static linking any more, and therefore fails to find
libraries.
A symptom for this is warnings in jenkins:
> docker: error while loading shared libraries: libltdl.so.7: cannot open shared object file: No such file or directory
## Versions
This uses the lts of jenkins, whatever that version is, at the time this image is built.
The docker version is rarely changed, and can be seen in the Dockerfile.
The docker hub automatic build has `jenkins/jenkins` added as a linked repository.
That means whenever a new version of jenkins is released, this image will also be built.
## Usage
Use like the normal jenkins docker image.
Mount the docker socket like this:
```
-v /var/run/docker.sock:/var/run/docker.sock
```
You might get permission issues, even after adding `jenkins` (`uid 1000`) as a user on the host,
and then adding that user to the group `docker` (`gid 497`, might depend on your install).
The dirtiest way to fix this is with `chmod 666 /var/run/docker.sock` on the host.
However, now everyone has access to docker. Depending on your environment, that might be an issue.
| 37.882353 | 119 | 0.75854 | eng_Latn | 0.999249 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.