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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
578ac6af9fce9845e59759f959d9b6e78af0462a | 14,906 | md | Markdown | .VSCodeCounter/2022-04-14_22-58-20/details.md | snow2512/snowBlogProject | 9827f8f3c27dac90e1618953b274e286313f5a44 | [
"MIT"
] | 1 | 2022-03-12T12:51:06.000Z | 2022-03-12T12:51:06.000Z | .VSCodeCounter/2022-04-14_22-58-20/details.md | snow2512/snowBlogProject | 9827f8f3c27dac90e1618953b274e286313f5a44 | [
"MIT"
] | null | null | null | .VSCodeCounter/2022-04-14_22-58-20/details.md | snow2512/snowBlogProject | 9827f8f3c27dac90e1618953b274e286313f5a44 | [
"MIT"
] | null | null | null | # Details
Date : 2022-04-14 22:58:20
Directory /Users/will/projects/blog
Total : 133 files, 16021 codes, 125 comments, 735 blanks, all 16881 lines
[Summary](results.md) / Details / [Diff Summary](diff.md) / [Diff Details](diff-details.md)
## Files
| filename | language | code | comment | blank | total |
| :--- | :--- | ---: | ---: | ---: | ---: |
| [README.md](/README.md) | Markdown | 4 | 0 | 3 | 7 |
| [client/Editor/Editor.js](/client/Editor/Editor.js) | JavaScript | 5 | 0 | 1 | 6 |
| [client/components/RootContainer.jsx](/client/components/RootContainer.jsx) | JavaScript React | 15 | 0 | 1 | 16 |
| [client/components/admin/Admin.css](/client/components/admin/Admin.css) | CSS | 38 | 0 | 7 | 45 |
| [client/components/admin/Admin.jsx](/client/components/admin/Admin.jsx) | JavaScript React | 64 | 0 | 13 | 77 |
| [client/components/admin/article/Article.css](/client/components/admin/article/Article.css) | CSS | 24 | 0 | 4 | 28 |
| [client/components/admin/article/Article.jsx](/client/components/admin/article/Article.jsx) | JavaScript React | 249 | 0 | 12 | 261 |
| [client/components/admin/article/articleEditor/ArticleEditor.css](/client/components/admin/article/articleEditor/ArticleEditor.css) | CSS | 38 | 0 | 6 | 44 |
| [client/components/admin/article/articleEditor/ArticleEditor.jsx](/client/components/admin/article/articleEditor/ArticleEditor.jsx) | JavaScript React | 137 | 6 | 7 | 150 |
| [client/components/admin/dashboard/Dashboard.css](/client/components/admin/dashboard/Dashboard.css) | CSS | 0 | 0 | 1 | 1 |
| [client/components/admin/dashboard/Dashboard.jsx](/client/components/admin/dashboard/Dashboard.jsx) | JavaScript React | 10 | 0 | 1 | 11 |
| [client/components/admin/homePages/contentPage/ContentPage.css](/client/components/admin/homePages/contentPage/ContentPage.css) | CSS | 24 | 0 | 2 | 26 |
| [client/components/admin/homePages/contentPage/ContentPage.jsx](/client/components/admin/homePages/contentPage/ContentPage.jsx) | JavaScript React | 116 | 0 | 10 | 126 |
| [client/components/admin/homePages/contentPageDetail/ContentPageDetail.css](/client/components/admin/homePages/contentPageDetail/ContentPageDetail.css) | CSS | 48 | 0 | 9 | 57 |
| [client/components/admin/homePages/contentPageDetail/ContentPageDetail.jsx](/client/components/admin/homePages/contentPageDetail/ContentPageDetail.jsx) | JavaScript React | 319 | 0 | 20 | 339 |
| [client/components/admin/homePages/footerPage/FooterPage.css](/client/components/admin/homePages/footerPage/FooterPage.css) | CSS | 57 | 0 | 9 | 66 |
| [client/components/admin/homePages/footerPage/FooterPage.jsx](/client/components/admin/homePages/footerPage/FooterPage.jsx) | JavaScript React | 229 | 0 | 16 | 245 |
| [client/components/admin/homePages/indexPage/IndexPage.css](/client/components/admin/homePages/indexPage/IndexPage.css) | CSS | 48 | 0 | 9 | 57 |
| [client/components/admin/homePages/indexPage/IndexPage.jsx](/client/components/admin/homePages/indexPage/IndexPage.jsx) | JavaScript React | 291 | 0 | 15 | 306 |
| [client/components/admin/login/Login.css](/client/components/admin/login/Login.css) | CSS | 73 | 0 | 9 | 82 |
| [client/components/admin/login/Login.jsx](/client/components/admin/login/Login.jsx) | JavaScript React | 72 | 0 | 10 | 82 |
| [client/components/admin/message/Message.css](/client/components/admin/message/Message.css) | CSS | 0 | 0 | 1 | 1 |
| [client/components/admin/message/Message.jsx](/client/components/admin/message/Message.jsx) | JavaScript React | 14 | 0 | 1 | 15 |
| [client/components/admin/sideBar/SideBar.jsx](/client/components/admin/sideBar/SideBar.jsx) | JavaScript React | 66 | 0 | 8 | 74 |
| [client/components/app/App.css](/client/components/app/App.css) | CSS | 24 | 1 | 5 | 30 |
| [client/components/app/App.jsx](/client/components/app/App.jsx) | JavaScript React | 28 | 0 | 4 | 32 |
| [client/components/articleList/ArticleList.css](/client/components/articleList/ArticleList.css) | CSS | 29 | 2 | 4 | 35 |
| [client/components/articleList/ArticleList.jsx](/client/components/articleList/ArticleList.jsx) | JavaScript React | 135 | 0 | 10 | 145 |
| [client/components/articleList/articleCard/ArticleCard.css](/client/components/articleList/articleCard/ArticleCard.css) | CSS | 67 | 0 | 8 | 75 |
| [client/components/articleList/articleCard/ArticleCard.jsx](/client/components/articleList/articleCard/ArticleCard.jsx) | JavaScript React | 33 | 0 | 2 | 35 |
| [client/components/articleList/sideBar/SideBar.css](/client/components/articleList/sideBar/SideBar.css) | CSS | 48 | 0 | 10 | 58 |
| [client/components/articleList/sideBar/SideBar.jsx](/client/components/articleList/sideBar/SideBar.jsx) | JavaScript React | 83 | 0 | 5 | 88 |
| [client/components/articlePage/ArticlePage.css](/client/components/articlePage/ArticlePage.css) | CSS | 20 | 0 | 5 | 25 |
| [client/components/articlePage/ArticlePage.jsx](/client/components/articlePage/ArticlePage.jsx) | JavaScript React | 63 | 1 | 8 | 72 |
| [client/components/blackBoard/BlackBoard.jsx](/client/components/blackBoard/BlackBoard.jsx) | JavaScript React | 13 | 0 | 1 | 14 |
| [client/components/comment/Comment.css](/client/components/comment/Comment.css) | CSS | 43 | 0 | 3 | 46 |
| [client/components/comment/Comment.jsx](/client/components/comment/Comment.jsx) | JavaScript React | 42 | 3 | 9 | 54 |
| [client/components/comment/commentList/CommentItem.css](/client/components/comment/commentList/CommentItem.css) | CSS | 32 | 0 | 0 | 32 |
| [client/components/comment/commentList/CommentItem.jsx](/client/components/comment/commentList/CommentItem.jsx) | JavaScript React | 52 | 3 | 6 | 61 |
| [client/components/comment/commentSubmit/CommentSubmit.css](/client/components/comment/commentSubmit/CommentSubmit.css) | CSS | 0 | 0 | 1 | 1 |
| [client/components/comment/commentSubmit/CommentSubmit.jsx](/client/components/comment/commentSubmit/CommentSubmit.jsx) | JavaScript React | 145 | 4 | 10 | 159 |
| [client/components/homepage/HomePage.css](/client/components/homepage/HomePage.css) | CSS | 10 | 0 | 5 | 15 |
| [client/components/homepage/HomePage.jsx](/client/components/homepage/HomePage.jsx) | JavaScript React | 76 | 0 | 9 | 85 |
| [client/components/homepage/contentPage/ContentPage.css](/client/components/homepage/contentPage/ContentPage.css) | CSS | 39 | 4 | 3 | 46 |
| [client/components/homepage/contentPage/ContentPage.jsx](/client/components/homepage/contentPage/ContentPage.jsx) | JavaScript React | 54 | 0 | 5 | 59 |
| [client/components/homepage/footerPage/FooterPage.css](/client/components/homepage/footerPage/FooterPage.css) | CSS | 74 | 3 | 6 | 83 |
| [client/components/homepage/footerPage/FooterPage.jsx](/client/components/homepage/footerPage/FooterPage.jsx) | JavaScript React | 101 | 4 | 13 | 118 |
| [client/components/homepage/indexPage/IndexPage.css](/client/components/homepage/indexPage/IndexPage.css) | CSS | 39 | 4 | 3 | 46 |
| [client/components/homepage/indexPage/IndexPage.jsx](/client/components/homepage/indexPage/IndexPage.jsx) | JavaScript React | 54 | 0 | 5 | 59 |
| [client/components/navbar/Navbar.css](/client/components/navbar/Navbar.css) | CSS | 26 | 0 | 2 | 28 |
| [client/components/navbar/Navbar.jsx](/client/components/navbar/Navbar.jsx) | JavaScript React | 75 | 0 | 5 | 80 |
| [client/components/navbar/item/Item.css](/client/components/navbar/item/Item.css) | CSS | 15 | 0 | 2 | 17 |
| [client/components/navbar/item/Item.jsx](/client/components/navbar/item/Item.jsx) | JavaScript React | 15 | 0 | 1 | 16 |
| [client/global.css](/client/global.css) | CSS | 45 | 0 | 8 | 53 |
| [client/global.js](/client/global.js) | JavaScript | 15 | 2 | 3 | 20 |
| [client/herald/herald.js](/client/herald/herald.js) | JavaScript | 51 | 0 | 5 | 56 |
| [client/index.jsx](/client/index.jsx) | JavaScript React | 21 | 6 | 2 | 29 |
| [client/router/Guard.jsx](/client/router/Guard.jsx) | JavaScript React | 22 | 0 | 4 | 26 |
| [client/router/interceptor.js](/client/router/interceptor.js) | JavaScript | 7 | 0 | 2 | 9 |
| [client/router/loader.js](/client/router/loader.js) | JavaScript | 17 | 0 | 2 | 19 |
| [client/router/redirector.js](/client/router/redirector.js) | JavaScript | 4 | 1 | 1 | 6 |
| [client/router/routes.js](/client/router/routes.js) | JavaScript | 150 | 5 | 8 | 163 |
| [client/store/adminLogin/adminLogin.js](/client/store/adminLogin/adminLogin.js) | JavaScript | 32 | 0 | 3 | 35 |
| [client/store/index.js](/client/store/index.js) | JavaScript | 24 | 0 | 7 | 31 |
| [client/store/sideBar/sideBar.js](/client/store/sideBar/sideBar.js) | JavaScript | 21 | 0 | 3 | 24 |
| [client/store/window/windowReducer.js](/client/store/window/windowReducer.js) | JavaScript | 14 | 0 | 3 | 17 |
| [client/template/index.html](/client/template/index.html) | HTML | 12 | 0 | 0 | 12 |
| [client/util/fontSize2className.js](/client/util/fontSize2className.js) | JavaScript | 10 | 3 | 1 | 14 |
| [client/util/string2color.js](/client/util/string2color.js) | JavaScript | 10 | 0 | 1 | 11 |
| [client/util/typeCheck.js](/client/util/typeCheck.js) | JavaScript | 10 | 0 | 1 | 11 |
| [comtomFile/quill.snow.css](/comtomFile/quill.snow.css) | CSS | 937 | 6 | 1 | 944 |
| [config/config.js](/config/config.js) | JavaScript | 27 | 0 | 1 | 28 |
| [docs/D00-设计.md](/docs/D00-%E8%AE%BE%E8%AE%A1.md) | Markdown | 273 | 0 | 85 | 358 |
| [docs/D01-框架搭建.md](/docs/D01-%E6%A1%86%E6%9E%B6%E6%90%AD%E5%BB%BA.md) | Markdown | 3 | 0 | 1 | 4 |
| [docs/D02-封装React路由.md](/docs/D02-%E5%B0%81%E8%A3%85React%E8%B7%AF%E7%94%B1.md) | Markdown | 50 | 0 | 23 | 73 |
| [docs/D03-数据表设计.md](/docs/D03-%E6%95%B0%E6%8D%AE%E8%A1%A8%E8%AE%BE%E8%AE%A1.md) | Markdown | 19 | 0 | 6 | 25 |
| [docs/L01-React-router.md](/docs/L01-React-router.md) | Markdown | 10 | 0 | 10 | 20 |
| [docs/L02-CSS.md](/docs/L02-CSS.md) | Markdown | 172 | 0 | 66 | 238 |
| [docs/L03-Mongo.md](/docs/L03-Mongo.md) | Markdown | 24 | 0 | 13 | 37 |
| [docs/L04-webpack.md](/docs/L04-webpack.md) | Markdown | 42 | 0 | 19 | 61 |
| [docs/PIT-踩坑记录.md](/docs/PIT-%E8%B8%A9%E5%9D%91%E8%AE%B0%E5%BD%95.md) | Markdown | 49 | 0 | 13 | 62 |
| [docs/X01-奇思妙想.md](/docs/X01-%E5%A5%87%E6%80%9D%E5%A6%99%E6%83%B3.md) | Markdown | 13 | 0 | 3 | 16 |
| [graph/AdminAccess.drawio](/graph/AdminAccess.drawio) | Draw.io | 117 | 0 | 0 | 117 |
| [graph/AdminModule.drawio](/graph/AdminModule.drawio) | Draw.io | 70 | 0 | 0 | 70 |
| [graph/BSarch.drawio](/graph/BSarch.drawio) | Draw.io | 63 | 0 | 0 | 63 |
| [graph/ERDigram.drawio](/graph/ERDigram.drawio) | Draw.io | 297 | 0 | 0 | 297 |
| [graph/SystemModule.drawio](/graph/SystemModule.drawio) | Draw.io | 71 | 0 | 0 | 71 |
| [graph/sysyemUseCase.drawio](/graph/sysyemUseCase.drawio) | Draw.io | 144 | 0 | 0 | 144 |
| [index.js](/index.js) | JavaScript | 1 | 0 | 4 | 5 |
| [jsconfig.json](/jsconfig.json) | JSON with Comments | 8 | 6 | 0 | 14 |
| [nodemon.json](/nodemon.json) | JSON | 2 | 1 | 0 | 3 |
| [package-lock.json](/package-lock.json) | JSON | 8,858 | 0 | 1 | 8,859 |
| [package.json](/package.json) | JSON | 75 | 0 | 1 | 76 |
| [scripts/dbSetup.js](/scripts/dbSetup.js) | JavaScript | 42 | 3 | 4 | 49 |
| [scripts/launchApiServer.js](/scripts/launchApiServer.js) | JavaScript | 24 | 11 | 6 | 41 |
| [scripts/launchStaticServer.js](/scripts/launchStaticServer.js) | JavaScript | 41 | 8 | 6 | 55 |
| [scripts/snowBlog.js](/scripts/snowBlog.js) | JavaScript | 2 | 0 | 0 | 2 |
| [server/api/Login.js](/server/api/Login.js) | JavaScript | 52 | 0 | 5 | 57 |
| [server/api/admin/Admin.js](/server/api/admin/Admin.js) | JavaScript | 9 | 0 | 2 | 11 |
| [server/api/admin/Article.js](/server/api/admin/Article.js) | JavaScript | 56 | 1 | 7 | 64 |
| [server/api/admin/ArticleEdit.js](/server/api/admin/ArticleEdit.js) | JavaScript | 21 | 0 | 5 | 26 |
| [server/api/admin/Asset.js](/server/api/admin/Asset.js) | JavaScript | 57 | 0 | 3 | 60 |
| [server/api/admin/Comment.js](/server/api/admin/Comment.js) | JavaScript | 9 | 0 | 3 | 12 |
| [server/api/admin/PageDetail.js](/server/api/admin/PageDetail.js) | JavaScript | 68 | 7 | 13 | 88 |
| [server/api/admin/TextLink.js](/server/api/admin/TextLink.js) | JavaScript | 26 | 0 | 3 | 29 |
| [server/api/open/AllPage.js](/server/api/open/AllPage.js) | JavaScript | 22 | 0 | 2 | 24 |
| [server/api/open/Article.js](/server/api/open/Article.js) | JavaScript | 26 | 0 | 3 | 29 |
| [server/api/open/ArticleContent.js](/server/api/open/ArticleContent.js) | JavaScript | 15 | 0 | 3 | 18 |
| [server/api/open/Comment.js](/server/api/open/Comment.js) | JavaScript | 15 | 0 | 5 | 20 |
| [server/api/open/Open.js](/server/api/open/Open.js) | JavaScript | 9 | 0 | 2 | 11 |
| [server/api/open/PageDetail.js](/server/api/open/PageDetail.js) | JavaScript | 28 | 0 | 3 | 31 |
| [server/api/open/Tags.js](/server/api/open/Tags.js) | JavaScript | 14 | 0 | 3 | 17 |
| [server/mongo/model/AdminModel.js](/server/mongo/model/AdminModel.js) | JavaScript | 3 | 0 | 1 | 4 |
| [server/mongo/model/ArticleModel.js](/server/mongo/model/ArticleModel.js) | JavaScript | 3 | 0 | 1 | 4 |
| [server/mongo/model/CommentModel.js](/server/mongo/model/CommentModel.js) | JavaScript | 3 | 0 | 1 | 4 |
| [server/mongo/model/CommentatorModel.js](/server/mongo/model/CommentatorModel.js) | JavaScript | 3 | 0 | 1 | 4 |
| [server/mongo/model/IconLinkModel.js](/server/mongo/model/IconLinkModel.js) | JavaScript | 0 | 0 | 1 | 1 |
| [server/mongo/model/PageModel.js](/server/mongo/model/PageModel.js) | JavaScript | 3 | 0 | 1 | 4 |
| [server/mongo/model/TextLinkModel.js](/server/mongo/model/TextLinkModel.js) | JavaScript | 3 | 0 | 1 | 4 |
| [server/mongo/mongo.js](/server/mongo/mongo.js) | JavaScript | 11 | 0 | 5 | 16 |
| [server/mongo/schema/AdminSchema.js](/server/mongo/schema/AdminSchema.js) | JavaScript | 7 | 0 | 1 | 8 |
| [server/mongo/schema/ArticleSchema.js](/server/mongo/schema/ArticleSchema.js) | JavaScript | 12 | 0 | 1 | 13 |
| [server/mongo/schema/CommentSchema.js](/server/mongo/schema/CommentSchema.js) | JavaScript | 25 | 0 | 2 | 27 |
| [server/mongo/schema/CommentatorSchema.js](/server/mongo/schema/CommentatorSchema.js) | JavaScript | 15 | 0 | 1 | 16 |
| [server/mongo/schema/IconLinkSchema.js](/server/mongo/schema/IconLinkSchema.js) | JavaScript | 0 | 0 | 1 | 1 |
| [server/mongo/schema/PageSchema.js](/server/mongo/schema/PageSchema.js) | JavaScript | 20 | 0 | 1 | 21 |
| [server/mongo/schema/TextLinkSchema.js](/server/mongo/schema/TextLinkSchema.js) | JavaScript | 23 | 6 | 1 | 30 |
| [server/response/response.js](/server/response/response.js) | JavaScript | 11 | 8 | 0 | 19 |
| [server/servers.js](/server/servers.js) | JavaScript | 33 | 3 | 4 | 40 |
| [server/utils/interceptor.js](/server/utils/interceptor.js) | JavaScript | 34 | 0 | 1 | 35 |
| [webpack.common.js](/webpack.common.js) | JavaScript | 87 | 9 | 2 | 98 |
| [webpack.dev.js](/webpack.dev.js) | JavaScript | 18 | 3 | 3 | 24 |
| [webpack.prod.js](/webpack.prod.js) | JavaScript | 5 | 1 | 1 | 7 |
[Summary](results.md) / Details / [Diff Summary](diff.md) / [Diff Details](diff-details.md) | 100.716216 | 195 | 0.691869 | yue_Hant | 0.22572 |
578bac953dce617cf85e8b1c675298c33f3040d2 | 1,639 | md | Markdown | _posts/2020-06-08-useful-intellij-plugins.md | bit-jkraushaar/bit-jkraushaar.github.io | 70d96a033b11c278d3ef5cfb2c0218836aa6134d | [
"Unlicense",
"MIT"
] | null | null | null | _posts/2020-06-08-useful-intellij-plugins.md | bit-jkraushaar/bit-jkraushaar.github.io | 70d96a033b11c278d3ef5cfb2c0218836aa6134d | [
"Unlicense",
"MIT"
] | null | null | null | _posts/2020-06-08-useful-intellij-plugins.md | bit-jkraushaar/bit-jkraushaar.github.io | 70d96a033b11c278d3ef5cfb2c0218836aa6134d | [
"Unlicense",
"MIT"
] | null | null | null | ---
layout: post
title: "Nützliche IntelliJ Plugins"
---
In diesem Artikel liste ich IntelliJ Plugins auf, die ich in der Vergangenheit eingesetzt habe und die sich bewährt haben.
# Versionsverwaltung
* [.ignore](https://plugins.jetbrains.com/plugin/7495--ignore): Unterstützung für ignorierte Dateien in verschiedenen Frameworks und Tools
* [Git Flow Integration](https://plugins.jetbrains.com/plugin/7315-git-flow-integration): Unterstützung des Git Flows direkt aus IntelliJ heraus
* [GitToolBox](https://plugins.jetbrains.com/plugin/7499-gittoolbox): Erweiterung der Git Funktionalität, z.B. Inline Blame
# Dokumentation
* [AsciiDoc](https://plugins.jetbrains.com/plugin/7391-asciidoc): Unterstützung von AsciiDoc-Dateien
* [PlantUML integration](https://plugins.jetbrains.com/plugin/7017-plantuml-integration): Integration für PlantUML
# Editor
* [HexView](https://plugins.jetbrains.com/plugin/10-hexview): Hex-Darstellung beliebiger Dateien
* [Ideolog](https://plugins.jetbrains.com/plugin/9746-ideolog): Erweiterte Funktionalität für Logs
* [Save Actions](https://plugins.jetbrains.com/plugin/7642-save-actions): Aktionen nach dem Speichern ausführen
# Anbindung von Tools und Frameworks
* [Karma](https://plugins.jetbrains.com/plugin/7287-karma): Integration für Karma
* [Kotlin](https://plugins.jetbrains.com/plugin/6954-kotlin): Integration für Kotlin
* [Lombok](https://plugins.jetbrains.com/plugin/6317-lombok): Integration für Lombok
* [Swagger](https://plugins.jetbrains.com/plugin/8347-swagger): Integration für Swagger
* [SonarLint](https://plugins.jetbrains.com/plugin/7973-sonarlint): Integration für SonarQube
| 51.21875 | 144 | 0.788896 | deu_Latn | 0.553627 |
578eb9858388553ef4f17df1a228cf20d89c014d | 387 | md | Markdown | bug-tracking/youtrack/README.md | alexanderfefelov/docker-backpack | 33aa9b41451fa54e4573c1fc0557a3b1f8fd37fa | [
"MIT"
] | 13 | 2020-10-23T13:10:49.000Z | 2021-12-07T17:43:39.000Z | bug-tracking/youtrack/README.md | alexanderfefelov/docker-backpack | 33aa9b41451fa54e4573c1fc0557a3b1f8fd37fa | [
"MIT"
] | 101 | 2020-08-09T07:01:23.000Z | 2021-06-11T11:59:29.000Z | bug-tracking/youtrack/README.md | alexanderfefelov/docker-backpack | 33aa9b41451fa54e4573c1fc0557a3b1f8fd37fa | [
"MIT"
] | 6 | 2020-08-11T09:59:39.000Z | 2021-11-04T15:45:02.000Z | # backpack-youtrack
Hostname `youtrack.backpack.test`
## Services
| Port | Service | Credentials
| ---: | :------ | :----------
| [8094](http://youtrack.backpack.test:8094) | HTTP [API](https://www.jetbrains.com/help/youtrack/standalone/youtrack-rest-api-reference.html) and management console | `admin_mahcaewaeth0` / `geeh2io1oquu`
| 32.25 | 205 | 0.687339 | kor_Hang | 0.180042 |
578f67576e53fa427f9514450a4545da8dcaa676 | 767 | md | Markdown | profiles/cristina-iancu.md | caltechlibrary/cell-atlas | c3c70bb121b75f44f60ffba1a94cb964035c7f2e | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 1 | 2020-11-07T00:13:48.000Z | 2020-11-07T00:13:48.000Z | profiles/cristina-iancu.md | caltechlibrary/cell-atlas | c3c70bb121b75f44f60ffba1a94cb964035c7f2e | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 48 | 2020-10-30T17:55:49.000Z | 2022-03-26T00:08:18.000Z | profiles/cristina-iancu.md | caltechlibrary/cell-atlas | c3c70bb121b75f44f60ffba1a94cb964035c7f2e | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 3 | 2020-10-08T16:47:30.000Z | 2021-01-11T20:47:07.000Z | ---
title: Cristina Iancu
img:
---
Cristina V. Iancu received her B.S. in Biophysics from the Faculty of Physics of the University of Bucharest, Romania, and her Ph.D. in Biochemistry from Iowa State University, Ames, IA, U.S. Her graduate work in the protein crystallography group of Dr. Richard B. Honzatko involved structural and functional studies of key enzymes in gluconeogenesis and de novo nucleotide synthesis. She joined the cryo-EM lab of Dr. Grant J. Jensen as his first postdoc, where she worked on cryo-ET method development projects and cryo-ET structure determination of protein complexes, isolated carboxysomes, and carboxysome-producing bacteria. Currently, she works on drug discovery targeting carbohydrate transporters with Dr. Jun-yong Choe.
| 95.875 | 728 | 0.801825 | eng_Latn | 0.994261 |
57905b78c09952d748cded3056cd6940f3aa22a1 | 2,276 | md | Markdown | services/blockchain/nl/pt/BR/knownissues.md | Ranjanasingh9/docs | 45286f485cd18ff628e697ddc5091f396bfdc46b | [
"Apache-2.0"
] | null | null | null | services/blockchain/nl/pt/BR/knownissues.md | Ranjanasingh9/docs | 45286f485cd18ff628e697ddc5091f396bfdc46b | [
"Apache-2.0"
] | null | null | null | services/blockchain/nl/pt/BR/knownissues.md | Ranjanasingh9/docs | 45286f485cd18ff628e697ddc5091f396bfdc46b | [
"Apache-2.0"
] | 1 | 2020-09-24T04:33:34.000Z | 2020-09-24T04:33:34.000Z | ---
copyright:
years: 2017
lastupdated: "2017-03-07"
---
{:new_window: target="_blank"}
{:shortdesc: .shortdesc}
{:codeblock: .codeblock}
{:screen: .screen}
{:pre: .pre}
# Problemas conhecidos do HSBN
{: #etn_overview}
Os problemas do plano HSBN a seguir foram relatados:
1. Ao usar o High Security Business Network, que utiliza o Hyperledger Fabric v0.6.1, reconfigurar a rede periodicamente durante uma fase de desenvolvimento será sugerido se houver mais do que aproximadamente cinquenta implementações de chaincode. Redefinir a rede remove o chaincode implementado e os dados que foram coletados. Isso fornece uma chance de remover o chaincode mais antigo que foi substituído por melhorias feitas durante uma fase de desenvolvimento iterativo. Se você estiver em uma fase pós-desenvolvimento, o número de implementações de chaincode deverá ser monitorado para deixar capacidade para o chaincode mais importante.
2. Erros esporádicos "503 Serviço Indisponível" e "502 Gateway Inválido" recebidos ao executar uma consulta de status da rede e dos peers.
3. Potencial para mensagens "Server.Serve falhou ao concluir o handshake de segurança" nos logs para vp1. Esse é um erro não fatal e não relacionado à operação de rede.
4. As **Credenciais de Serviço** podem não se autopreencher; nesse caso, gere as credenciais da seguinte maneira:
a) A partir do seu Painel de Serviço, clique na guia **Credenciais de Serviço**:
b) Na guia **Credenciais de Serviço**, clique no botão para **Nova Credencial**:
c) Uma nova janela intitulada **Incluir Nova Credencial** é exibida; clique no botão **Incluir** na parte inferior desta janela:
d) Agora sua tela deve ser semelhante ao exemplo a seguir. Clicar em **Visualizar Credenciais** revelará uma carga útil JSON que contém as Credenciais de Serviço para sua instância HSBN.
## Como Obter Ajuda
Para suporte e ajuda com a sua rede do IBM Blockchain on Bluemix, veja [Obtendo suporte](ibmblockchain_support.html).
| 48.425532 | 646 | 0.775483 | por_Latn | 0.999369 |
5790cca847e06a22125ced6530eeb8c5f43277aa | 1,456 | md | Markdown | Resources/Logo/README.md | twistedflick/Yuka | c1601a7314ccbdb1de2f4b7c69f4e2eb3f749b35 | [
"Apache-2.0"
] | null | null | null | Resources/Logo/README.md | twistedflick/Yuka | c1601a7314ccbdb1de2f4b7c69f4e2eb3f749b35 | [
"Apache-2.0"
] | null | null | null | Resources/Logo/README.md | twistedflick/Yuka | c1601a7314ccbdb1de2f4b7c69f4e2eb3f749b35 | [
"Apache-2.0"
] | null | null | null | # Yuka Logo
## Copyright & Licence
Copyright © 2018 Mo McRoberts.
The Yuka Logo, and related assets in this directory, are **not** released under the same licensing
terms as the software.
### You may
* Redistribute unmodified versions of the assets in this directory when redistributing Yuka.
* Include unmodified versions of the assets in a project which incorporates Yuka.
* Incorporate these assets into your software and/or documentation project as a means of giving credit to Yuka.
* Submit _Pull Requests_ containing modified versions of these assets for onward distribution as part of this directory according these terms. If your PR is accepted, your work will of course be credited appropriately.
### You may not
* Distribute materially modified versions of these assets.
* Make use of the assets in such a way that conveys the impression that:—
* (a) your project is endorsed by the Yuka authors;
* (b) your project is the official Yuka distribution;
* (c) your project makes use of Yuka when it does not.
### Additional guidance
* Conversion between file formats (for example, converting an SVG-format asset to PostScript) is not considered to be "modification" provided the visual properties of the asset are preserved.
* This document is not legal advice.
* This document is not a copyright waiver. Except by adhering to these terms (and statutory provisions in law) you do **not** have permission to redistribute these assets.
| 48.533333 | 218 | 0.779533 | eng_Latn | 0.999789 |
579308cb24bd5929c232d5afde820580254359af | 1,776 | md | Markdown | docs/QC.md | RENCI/fuse-immcellfie-api | f56b6794199edc7c862697b545a4b82e842e6a44 | [
"MIT"
] | null | null | null | docs/QC.md | RENCI/fuse-immcellfie-api | f56b6794199edc7c862697b545a4b82e842e6a44 | [
"MIT"
] | 3 | 2021-03-12T05:44:30.000Z | 2021-05-03T14:57:06.000Z | docs/QC.md | RENCI/fuse-immcellfie-api | f56b6794199edc7c862697b545a4b82e842e6a44 | [
"MIT"
] | null | null | null | # ImmCellFIE Project Quality Control (QC) plan
## Overview
For quality control, we use a combination of peer-reviewed acceptance testing for manual systems and automated regression testing for containerized appliances and dashboard.
We use [pytest](https://docs.pytest.org/en/stable/) and [dockerhub](https://hub.docker.com) auto builds for automated testing, and failed tests are flagged directly on the
github repositories using [shields.io](https://shields.io/category/build) to generate dockerhub build status badges.
## Automated Regression Testing
Each docker-containerized appliance comprizing this framework is added as a submodule to this repo. Each submodule has unit tests installed under `<main>/tests`.
The bash script, `<main>/tests/test.sh` can be used to kick-off the tests. Tests are run automatically by dockerhub through pytest which picks up tests named `def test_<some test` in a file called `<main>/tests/test_<some-file>.py`. The `test.sh` shell script sets all the variables found in `<main>/.env` and kicks off the docker container builds using docker-compose.
Subsequently, pytest will look for any files matching the following regular expression: `<main>/tests/test_*.py`. Within those files, pytest will run and report the
results of any tests matching the regular expression: `def test_*():`.
## System Testing
Currently we manually system test via peer review. Upon completion of each milestone, the accountable developer presents a demo of the implemented functionality to a
pre-assigned acceptance tester (AT). The milestone can be marked as complete only after the demo has met the AT's approval. AT's and approvals are tracked alongside
the [project plan](https://drive.google.com/file/d/1H5ocHVMpFI9Ju3CdT_NVYG4yHXoR-jz9/view).
| 84.571429 | 370 | 0.789977 | eng_Latn | 0.994277 |
57946c5fda043d5d212fcaa735a93cb543d78ae2 | 4,587 | md | Markdown | meetings/2020-09-09-ODPi-TSC-Meeting-Notes.md | mandy-chessell/tsc | 7cddd8285a5f3c376745b28c38698203a5497d96 | [
"CC-BY-4.0"
] | 6 | 2019-04-11T15:50:45.000Z | 2021-02-02T15:00:04.000Z | meetings/2020-09-09-ODPi-TSC-Meeting-Notes.md | mandy-chessell/tsc | 7cddd8285a5f3c376745b28c38698203a5497d96 | [
"CC-BY-4.0"
] | 1 | 2020-04-07T15:26:37.000Z | 2020-04-08T13:32:58.000Z | meetings/2020-09-09-ODPi-TSC-Meeting-Notes.md | mandy-chessell/tsc | 7cddd8285a5f3c376745b28c38698203a5497d96 | [
"CC-BY-4.0"
] | 5 | 2019-05-03T14:29:35.000Z | 2020-01-15T16:35:43.000Z | # Roll call:
## Attending
* Mandy Chessell
* Cupid Chan
* Maryna Strelchuk
* Andre de Waal
## Regrets
* John Mertic
* Arun Nair
## Non-voting observers
# Agenda:
* Project updates
* OpenDS4All - Andre
* Second adopter - Oklahoma State University - 150 students
* Other adopters in pipeline
* Seeking content for 2 open source AI open source projects around explainable AI
* License file scan - making small changes to a couple of files to clean up report
* Looking to create a dojo - may be for next month
* ODPi BI & AI - Cupid
The options below will be voted on in next Friday's call
* Option 1: Bridge API: Build library (npm/Python/Java/Go…etc). On one hand it spawns a child process (in Python or other chosen language) calling AI frameworks (e.g. TensorFlow and PyTorch) to train or run a model, on the other hand, it exposes an API to allow frontend (e.g. Angular or React) to get immediate update of an result.
* Option 2: Human-centered AI: The idea is when the industry talked about AI in the past few years, we focus a lot on Machine Learning. However, just like in traditional schooling system, Learning is only half of the equation - the other half is TEACHING. And we are missing Machine TEACHING which is where the Human-centered portion comes in. Guess who has a long history to enable human interacting with data. That’s BI!!!! It also aligns with what I shared with the team earlier about AI + BI = CI, by combining the Speed of a machine can offered in AI and the Direction intuited by Human, we can achieve the ultimate Cognitive Intelligence. So, our bridge can focus on to building up a framework to enable Human-Centered AI
* Option 3: The bridge for AI/BI will provide a mechanism to handle administration, training and return results and be able to return explanations. It should allow BI users to pass data or pointers to the data if it exists in the cloud and provide a manner in which cognitive information regarding data sensitivity can be maintained and report data drift as it starts occurring.
* Option 4: With the rapid development of data science and data platforms, user communities from all over the world have an opportunity to bridge previously opaque and massive data workloads into one data library for further analysis/consumption.
* Option 5: Further, BI tools can now be used to promote greater transparency and new insight within even more communities than ever before
* Option 6: The Bridge for AI/BI (data shared for use by both) is a platform-agnostic (doesn’t matter whether it’s on premise, in the cloud, or virtual) and tool-agnostic (doesn’t matter whether it is MicroStrategy, Power BI, Qlik, SAS, or Tableau) exchange (API, connector, etc) that allows for AI technologies to inter-operate with BI technologies likely using data as the medium for the exchange.
* Option 7: It defines how a BI system interfaces with an AI system, and delegates "what" to expose to the BI system, however includes specific components relevant to BI (e.g. triggers for db refresh or providing metadata about the sensitivity/security of input variables). The definition includes training, inference (predict), and model definition endpoints.
* Option 8: this bridge presents an automatic gateway for generating new BI insights based on a black box but regulated AI framework.
* ODPi Egeria - Mandy and Maryna
* Release 2.2 branched - but still have issues in containers
* Team working on the definition of a project level TSC:
* [Link to proposal](https://github.com/odpi/data-governance/wiki/ODPi-Egeria-Weekly-Meeting-10th-September-2020)
* *All about graphs* webinar went well
* [Link to replay](https://www.youtube.com/watch?v=dgeOAJF6jq8&t=4s)
* AOB
* Additional integration suggestions: Apache Druid - still to look at
* Also from Arun ...
----
Evaluate Possibility of Using Spacy for Entity Recognition for MetaData - in Egeria .
I wanted to discuss/brainstorm with you(experts) on the possibility of using Named Entity recognition using spacy, in Egeria
Do you think a Natural Language processing tool that identifies various Entity will help us in building better meta data.
Following in a link on how NLP SPACY is used for better Meta Data recognition.
Named entity recognition using spacy
https://towardsdatascience.com/named-entity-recognition-with-nltk-and-spacy-8c4a7d88e7da
Have a good day.
Regards,
Arunkumar Nair
----
| 57.3375 | 731 | 0.747765 | eng_Latn | 0.996445 |
5795c1a262d49655fdec5c6ad61e52f16b61d55d | 1,344 | md | Markdown | CONTRIBUTING.md | djdaniels90/docker-speedtest-ui | 93b60d9c9dc735dac4441f017e2ab1ca37ab514e | [
"MIT"
] | null | null | null | CONTRIBUTING.md | djdaniels90/docker-speedtest-ui | 93b60d9c9dc735dac4441f017e2ab1ca37ab514e | [
"MIT"
] | null | null | null | CONTRIBUTING.md | djdaniels90/docker-speedtest-ui | 93b60d9c9dc735dac4441f017e2ab1ca37ab514e | [
"MIT"
] | null | null | null | # TODO
TODO: change this file to explain a bit about commitzen, and the release procedure as well as the style, linting rules we use and flow configuration etc.
[](https://conventionalcommits.org)
## Contributing to Panda4000
TODO: change this file to explain a bit about commitzen, and the release procedure as well as the style, linting rules we use and flow configuration etc.
# Git and Commits
We use commitizen to enforce a standard commit message format
[](https://conventionalcommits.org)
# Releases
### Documentation
We need your help with improving documentation to the project. This might be the easiest way for
you to contribute, because you don't even need to clone the repo but can edit or create new `.md`
files right from GitHub website as described.
#### Style Guide
Our linter will catch most styling issues that may exist in your code. You can check the status
of your code styling by simply running: `npm lint`
However, there are still some styles that the linter cannot pick up. If you are unsure about
something, looking at [Airbnb's Style Guide](https://github.com/airbnb/javascript) will guide you
in the right direction.
| 40.727273 | 153 | 0.779762 | eng_Latn | 0.995675 |
579696146d373c8dfade13aea15e5f99ffdc6387 | 326 | md | Markdown | README.md | luminarious/jsonld-examples | 215c003f73b2362384136b8374cd9fec71886587 | [
"MIT"
] | 3 | 2017-12-20T09:32:00.000Z | 2021-02-19T02:01:10.000Z | README.md | luminarious/jsonld-examples | 215c003f73b2362384136b8374cd9fec71886587 | [
"MIT"
] | null | null | null | README.md | luminarious/jsonld-examples | 215c003f73b2362384136b8374cd9fec71886587 | [
"MIT"
] | null | null | null | # JSON-LD
Structured data, Google likes it a lot.
* https://developers.google.com/search/docs/guides/intro-structured-data
* https://search.google.com/structured-data/testing-tool
* http://schema.org/
## In HTML
```html
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": ...,
}
</script>
``` | 18.111111 | 72 | 0.677914 | yue_Hant | 0.455072 |
5796e08e29e7fae3aaee14aed2ec4f5160e2e34b | 3,246 | md | Markdown | README.md | DontGetBoard/DGB_App | a29b7e72caa8da9d7f2a691e96a7d268ff3abeba | [
"MIT"
] | null | null | null | README.md | DontGetBoard/DGB_App | a29b7e72caa8da9d7f2a691e96a7d268ff3abeba | [
"MIT"
] | null | null | null | README.md | DontGetBoard/DGB_App | a29b7e72caa8da9d7f2a691e96a7d268ff3abeba | [
"MIT"
] | null | null | null |
____ __ __
/\ _ \ /\ \__ /\ \__
\ \ \/\ \ ___ ___\ \ _\ __ __\ \ _\
\ \ \ \ \ / __ \ / _ \ \ \/ / _ \ / __ \ \ \/
\ \ \_\ \/\ \ \ \/\ \/\ \ \ \_ /\ \ \ \/\ __/\ \ \_
\ \____/\ \____/\ \_\ \_\ \__\ \ \____ \ \____\\ \__\
\/___/ \/___/ \/_/\/_/\/__/ \/____\ \/____/ \/__/
/\____/
\____/
__ __
/\ \ /\ \
\ \ \____ ___ __ _ __ \_\ \
\ \ __ \ / __ \ / __ \ /\ __\/ _ \
\ \ \ \ \/\ \ \ \/\ \ \ \_\ \ \//\ \ \ \
\ \____/\ \____/\ \__/ \_\\ \_\\ \_____\
\/___/ \/___/ \/__/\/_/ \/_/ \/_____/
[](https://www.codacy.com/public/sat/DGB_App) [](https://david-dm.org/DontGetBoard/DGB_App)
Requirements
------------
You must have `npm` and `mongod` to run this application.
Environments Variables
----------------------
| Variable | Usage |
|---------|------|
| DGB_APP_NEW_RELIC_KEY | New Relic Api Key |
| DGB_MAILGUN_API_KEY | MailGun API Key |
| DGB_MAILGUN_DOMAIN | MailGun API Domain |
| DGB_PASSPORT_SECRET | Secret Passphrase to generate Hashes |
| DGB_MAILCHIMP_API_KEY | MailChimp API Key |
| DGB_MAILCHIMP_LIST_ID | MailChimp List ID |
Installation
------------
Setup the application with:
npm install
Run MangoDB to host the database:
mangod
Launch the application:
npm start
then browse to `http://localhost:3000`
Routes
------
GET /
GET /login
POST /login
GET /signup
POST /signup
GET /logout (must be auth)
Dependencies
------------
"dependencies": {
"bcrypt-nodejs": "latest",
"body-parser": "~1.8.1",
"connect-flash": "~0.1.1",
"cookie-parser": "~1.3.3",
"debug": "~2.0.0",
"ejs": "~0.8.5",
"express": "~4.9.0",
"express-session": "~1.0.0",
"mailgun-js": "^0.6.7",
"mongoose": "^3.8.19",
"morgan": "~1.3.0",
"newrelic": "^1.14.2",
"nodejs-gravatar": "^1.0.2",
"passport": "~0.1.17",
"passport-local": "~0.1.6",
"serve-favicon": "~2.1.3"
}
Thanks To
---------
Icons:
- players.svg => [Daniel Bruce](http://www.flaticon.com/free-icon/user-group_3671)
- clock.svg => [Daniel Bruce](http://www.flaticon.com/free-icon/back-in-time_3712)
Plugins:
- [Animate.css](http://daneden.github.io/animate.css/)
- [AngularJS](https://angularjs.org/)
- [Equalize.js](http://tsvensen.github.io/equalize.js/)
- [Foundation](http://foundation.zurb.com/)
| 30.622642 | 244 | 0.418053 | yue_Hant | 0.430322 |
5798831c6cab551541a7c0d0c8bf773625ff1a70 | 133 | md | Markdown | TODO.md | yanhaijing/templatejs-atom | eff0a5c4eadeeea48cb30ae010bea336a741dc13 | [
"MIT"
] | 1 | 2020-08-18T03:56:55.000Z | 2020-08-18T03:56:55.000Z | TODO.md | yanhaijing/templatejs-atom | eff0a5c4eadeeea48cb30ae010bea336a741dc13 | [
"MIT"
] | 1 | 2021-03-17T05:23:53.000Z | 2021-03-17T06:14:41.000Z | TODO.md | yanhaijing/templatejs-atom | eff0a5c4eadeeea48cb30ae010bea336a741dc13 | [
"MIT"
] | null | null | null | # 计划列表
这里列出会在未来添加的新功能，和已经完成的功能
## 已完成
## 未完成
- [ ] 支持`<% %>`中的js语法
- [ ] 支持分隔符自定义，目前仅支持`<% %>`和`<# #>`
- [ ] 合并进template.js的mono仓库
| 13.3 | 35 | 0.556391 | yue_Hant | 0.746047 |
579c20adcd7ad81f188eb89f29a161dd827db4e5 | 53 | md | Markdown | README.md | nanlovescan/nansheng.github.io | 7adddf2037b7254a5684fa7b82d2d11788f6a9ff | [
"MIT"
] | null | null | null | README.md | nanlovescan/nansheng.github.io | 7adddf2037b7254a5684fa7b82d2d11788f6a9ff | [
"MIT"
] | null | null | null | README.md | nanlovescan/nansheng.github.io | 7adddf2037b7254a5684fa7b82d2d11788f6a9ff | [
"MIT"
] | 1 | 2021-07-22T05:46:19.000Z | 2021-07-22T05:46:19.000Z | [Nan Sheng's Webpage](https://nanlovescan.github.io)
| 26.5 | 52 | 0.754717 | kor_Hang | 0.252489 |
579d683ed43305a45b907cbc0d3f644d907759ba | 91 | md | Markdown | README.md | sjk0709/Shrinkage2D | e9c8eec1050ffa836b82a53e48309ad8435a380c | [
"MIT"
] | null | null | null | README.md | sjk0709/Shrinkage2D | e9c8eec1050ffa836b82a53e48309ad8435a380c | [
"MIT"
] | null | null | null | README.md | sjk0709/Shrinkage2D | e9c8eec1050ffa836b82a53e48309ad8435a380c | [
"MIT"
] | null | null | null | # Shrinkage2D
We study on a fast shrinkage prediction simulation by the deep learning.
| 13 | 72 | 0.78022 | eng_Latn | 0.987944 |
579f39075dda7a05c02e25aeb00d537c7053dfaf | 2,026 | md | Markdown | mdop/agpm/user-interface-advanced-group-policy-management.md | MicrosoftDocs/mdop-docs-pr.pt-br | 2d38ae9d6390d84fbff1002a9e2397406a57b481 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-20T21:13:51.000Z | 2021-04-20T21:13:51.000Z | mdop/agpm/user-interface-advanced-group-policy-management.md | MicrosoftDocs/mdop-docs-pr.pt-br | 2d38ae9d6390d84fbff1002a9e2397406a57b481 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-07-08T05:41:31.000Z | 2020-07-08T15:40:05.000Z | mdop/agpm/user-interface-advanced-group-policy-management.md | MicrosoftDocs/mdop-docs-pr.pt-br | 2d38ae9d6390d84fbff1002a9e2397406a57b481 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-04T12:32:41.000Z | 2021-11-04T12:32:41.000Z | ---
title: Interface do usuário avançada gerenciamento de política de grupo
description: Interface do usuário avançada gerenciamento de política de grupo
author: dansimp
ms.assetid: 73324c99-adca-46dc-b516-ef78b7235f59
ms.reviewer: ''
manager: dansimp
ms.author: dansimp
ms.pagetype: mdop
ms.mktglfcycl: manage
ms.sitesec: library
ms.prod: w10
ms.date: 06/16/2016
ms.openlocfilehash: 1a4bc7d95ce69a296bf88704337faa82dde2de7d
ms.sourcegitcommit: 354664bc527d93f80687cd2eba70d1eea024c7c3
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 06/26/2020
ms.locfileid: "10797276"
---
# Interface do usuário: Gerenciamento Avançado de Política de Grupo
O gerenciamento avançado de política de grupo (AGPM) adiciona um nó de **controle de alterações** a cada domínio exibido no GPMC (console de gerenciamento de **política de grupo** ). Em um ambiente em que vários domínios são gerenciados com o GPMC, cada domínio é listado no nó **domínios** na árvore do console. Cada domínio tem um nó de **controle de alterações** abaixo dele, e há um arquivo de objetos de política de grupo (GPOs) por domínio.
No painel de detalhes há três guias principais, fornecendo acesso a configurações no nível do GPO e configurações e comandos no nível do domínio para AGPM.
- [Guia conteúdo](contents-tab.md): configurações e comandos do GPO e delegação em nível de GPO
- [Guia de delegação de domínio](domain-delegation-tab.md): configurações de notificação por email do AGPM e delegação em nível de domínio
- [Guia do servidor do AGPM](agpm-server-tab.md): configurações da conexão de arquivo morto em nível de domínio
Outros aprimoramentos e configurações:
- [Configurações de modelo administrativo](administrative-template-settings.md): configuração central de log e rastreamento, locais de arquivamento e visibilidade de recursos
- [Outros aprimoramentos no GPMC: o](other-enhancements-to-the-gpmc.md)AGPM adiciona uma guia **histórico** e uma guia **extensões** para cada GPO e link de política de grupo
| 42.208333 | 446 | 0.788746 | por_Latn | 0.999205 |
579f785b254f0b1aa03bfef1322b5a218c15c7b5 | 181 | md | Markdown | data/meena.md | garfix/nligems | d396ccb4964bea694d061ba7819b014e6d8ffdad | [
"MIT"
] | 1 | 2019-12-16T01:18:40.000Z | 2019-12-16T01:18:40.000Z | data/meena.md | garfix/nligems | d396ccb4964bea694d061ba7819b014e6d8ffdad | [
"MIT"
] | null | null | null | data/meena.md | garfix/nligems | d396ccb4964bea694d061ba7819b014e6d8ffdad | [
"MIT"
] | null | null | null | Neural-net based chatbot by Google AI.
At its heart lies the Evolved Transformer seq2seq architecture.
https://ai.googleblog.com/2020/01/towards-conversational-agent-that-can.html | 36.2 | 76 | 0.81768 | kor_Hang | 0.481774 |
57a0cd8671dc8fe0bf0459e39238ccbcc26e5069 | 2,099 | md | Markdown | content/docs/microelectronics/section6/index.md | Marukohe/doks | 4ccbf9b6e6c7a09933fd6158dc57ebd22402a98e | [
"MIT"
] | null | null | null | content/docs/microelectronics/section6/index.md | Marukohe/doks | 4ccbf9b6e6c7a09933fd6158dc57ebd22402a98e | [
"MIT"
] | 33 | 2021-07-30T23:15:56.000Z | 2022-01-24T23:20:08.000Z | content/docs/microelectronics/section6/index.md | Marukohe/doks | 4ccbf9b6e6c7a09933fd6158dc57ebd22402a98e | [
"MIT"
] | null | null | null | ---
title: "放大电路模型"
description: ""
lead: ""
date: 2021-04-09T23:56:31+08:00
lastmod: 2021-04-09T23:56:31+08:00
draft: false
images: []
menu:
docs:
parent: "microelectronics"
weight: 20
toc: true
---
## 307.放大电路模型
### 信号
+ **信号**：信息的载体——温度、压力、速度、声音、亮度。。。
+ 电信号：用电量来描述信息的变化
### 模拟信号和数字信号
+ 模拟信号：在时间和幅值上都是连续的信号
+ 数字信号：在时间和幅值上都是离散的信号
+ 按时间和幅值的连续性和离散性分类：
+ 时间连续、数值连续——模拟信号
+ 时间离散、数值连续——例如AD转换信号
+ 时间连续、数值离散——例如DA转换信号
+ 时间离散、数值离散——数字信号
### 放大电路
+ 放大电路是模拟电路中最基本的单元电路
### 放大电路的符号及模拟信号放大
{{< img src="放大电路.png" alt="Rectangle" class="border-0" >}}
### 放大电路模型
{{< img src="放大电路模型.png" alt="Rectangle" class="border-0" >}}
## 308.运算放大器
### 集成电路运算放大器
+ 集成电路运算放大器的功能：
+ 信号放大
+ 信号运算
+ 信号的处理
+ 波形的产生和变换
+ 集成电路运算放大器的分类：
+ 通用运放和专用运放
+ 单运放、双运放、四运放
+ 集成电路运算放大器的内部组成单元
输入级差分放大$\rightarrow$中间级电压放大$\rightarrow$输出级功率放大
+ **放大**：在输入信号控制下，放大电路将供电电源能量转换成为输出信号能量
+ 运算放大器的电压传输特性
{{< img src="集成运算放大器.png" alt="Rectangle" class="border-0" >}}
设$v_p>v_N$
1. 线性区：
$$V_-<A_{vo}(v_p-v_N)<V_+$$
$$v_o=A_{vo}(v_p-v_N)$$
2. 饱和区：
$$A_{vo}(v_p-v_N)\geq V_+$$
$$v_o=+V_{om}=V_+$$
$$A_{vo}(v_p-v_N)\leq V_-$$
$$v_o=-V_{om}=V_-$$
### 理想运算放大器
+ 特点：
+ 开环差模电压增益：$A_{vo}=\infty$
+ 差模输入电阻：$R_{id}=\infty$
+ 输出电阻：$r_o=0$
+ 理想运算的电路模型
{{< img src="理想运算放大器.png" alt="Rectangle" class="border-0" >}}
### 反馈的基本概念
+ 将系统的输出返回到输入端并以某种方式改变输入，进而影响系统功能的过程，即将输出量通过恰当的检测装置返回到输入端并与输入量进行比较的过程。
+ 反馈通路----信号反向传输的渠道
+ 开环----无反馈回路；闭环----有反馈回路
### 电路中的反馈形式（概念，不用分析）
+ 正反馈与负反馈
+ 正反馈：输入量不变时，引入反馈后输出量变大了
+ 负反馈：输入量不变时，引入反馈后输出量变小了
+ 另一角度（同样输出情况下）
+ 正反馈：引入反馈后，净输入量变小了
+ 负反馈：引入反馈后，净输入量变大了
+ 判别方法：瞬时极性发。即在电路中，从输入端开始，沿着信号流向，标出某一时刻有关节点电压变化的斜率（正斜率或负斜率，用"+"、"-"号表示）
### 同相放大电路的反馈过程
+ 负反馈作用：利用输出电压$V_o$通过反馈元件（反馈网络）对放大电路起自动调整作用，从而牵制了$V_o$的变化，最后达到输出稳定平衡。
### 反馈的电压增益
+ 闭环电压增益$A_v$：只取决于运放外部电路的元件值，即取决于$R_1,R_2$，而与运放本身的$A_{vo},r_i,r_o$无关。
+ 深度负反馈
$$
(1+A_{vo}F_v)\gg 1\newline
F_v=\frac{v_f}{v_0}
$$
### 虚短和虚断（重要）
1. 虚短：在深度负反馈作用下，$v_N$自动跟踪$v_p$，净输入电压$(v_p-v_N)\rightarrow 0$，即$P$端与$N$端相当于短路。
2. 虚断：由于$(v_p\approx v_N)$，而运放的输入电阻阻值又很高，因此流经两输入端之间的电流$i_p=i_N\approx 0$
| 18.412281 | 77 | 0.646498 | yue_Hant | 0.406218 |
57a28507a05524ff2ae5e87437331e6e29a10e80 | 1,867 | md | Markdown | _pages/about.md | propan2one/propan2one.github.io | 30a9622c85abd883ce9b384cc32ac23d5e1863c7 | [
"MIT"
] | null | null | null | _pages/about.md | propan2one/propan2one.github.io | 30a9622c85abd883ce9b384cc32ac23d5e1863c7 | [
"MIT"
] | 4 | 2018-07-04T09:42:01.000Z | 2018-07-04T09:50:15.000Z | _pages/about.md | propan2one/propan2one.github.io | 30a9622c85abd883ce9b384cc32ac23d5e1863c7 | [
"MIT"
] | null | null | null | ---
layout: single
permalink: /about/
title: About
author_profile: true
header:
overlay_image: /assets/images/thinking-bioinformatics-tools.jpg
date: March 30, 2020
excerpt: "Coding is the worst of all drugs: those who do it die, those who miss it also die.."
---
<figure style="width: 50%" class="align-right">
<img src="{{ site.url }}{{ site.baseurl }}/assets/images/Sequencing_minion.jpg" alt="">
</figure>
I am currently an PhD Student fellow in the Host-Pathogen-Environment Interactions ([IHPE](http://ihpe.univ-perp.fr/en/)) research group at the University of Montpellier ([UM](https://www.umontpellier.fr/university-of-montpellier)). `JDLab` is my personal blog to keep track of my projects and share some of my analysis on some subject of interest.
{: .text-justify}
I was born and grew up in France, I had the opportunity to study a lot of fields when I studied in Paris. I started with biochemistry where I found a passion for organ chemistry, then I realized that a ribosome is more efficient than a chemist. I then turned to biology and particularly virology and immunology. During my last year I followed courses at the Pasteur Institute where I discovered the possibility offered by bioinformatics. Here I am now in the last year of my bioinformatics thesis. My main interest is to assess the viral genetic diversity of an herpesvirus, OsHV-1, during Pacific Oyster mortality syndrome.
{: .text-justify}
In my free time (Although this concept is relataif when we do a PhD), I enjoy writing code for myself to satisfy my own intellectual curiosity as well as to develop valuable IT skills through project learning, go skating, jogging, painting, and of course, hang out with my friends.
{: .text-justify}
I hope that you will find information which will help through the various articles of blogs which I will publish.
{: .text-justify}
| 66.678571 | 625 | 0.77022 | eng_Latn | 0.99847 |
57a3cb0cc58b3a3d4a8a5d08dabcd9a9cef6a8df | 1,075 | md | Markdown | doc/test-framework-choice.md | jar398/tryphy | 8dc0c713d3bd44126c3664e930625d641298b849 | [
"BSD-2-Clause"
] | null | null | null | doc/test-framework-choice.md | jar398/tryphy | 8dc0c713d3bd44126c3664e930625d641298b849 | [
"BSD-2-Clause"
] | 1 | 2018-08-27T19:19:22.000Z | 2018-08-28T14:41:08.000Z | doc/test-framework-choice.md | jar398/tryphy | 8dc0c713d3bd44126c3664e930625d641298b849 | [
"BSD-2-Clause"
] | null | null | null | Choice of test framework
========================
* [Web site about python testing frameworks](http://pythontesting.net/start-here/)
* [Good Python testing overview from 2009](https://www.ibm.com/developerworks/aix/library/au-python_test/index.html/)
* [Unit test example from Open Tree](https://github.com/OpenTreeOfLife/phylesystem-api/blob/master/modules/test_gitdata.py)
* Mark Holder (peyotl, otcetera, etc.) likes nose, but nose and nose2 seem to be abandonware.
* Duke Leto used unittest for phylesystem back in December 2013
* pytest requires an install step. Might make the test files more succinct.
Has things we don't need.
* unittest is sort of clunky but is built into the python distribution.
No install step is required and there is no shell command.
* Open Tree has [web API testing code that we can use](https://github.com/OpenTreeOfLife/germinator/tree/master/ws-tests). The framework is nonstandard but we don't have to use it.
Strategy: unittest + open tree utilities; upgrade later from unittest
to pytest if unittest ends up being inadequate.
| 56.578947 | 181 | 0.76186 | eng_Latn | 0.935893 |
57a531b11487aeaae4d731033f5cc27b4766ba15 | 3,530 | md | Markdown | week1/unit5.md | gauravkarkara/openSAP-RAP-Course-Artifacts | 2ec815424a49d0882dba843ecf6aecc4f7d4f383 | [
"Apache-2.0"
] | 257 | 2020-10-19T10:23:57.000Z | 2022-03-29T12:36:17.000Z | week1/unit5.md | gauravkarkara/openSAP-RAP-Course-Artifacts | 2ec815424a49d0882dba843ecf6aecc4f7d4f383 | [
"Apache-2.0"
] | 28 | 2020-10-30T19:00:02.000Z | 2021-12-19T17:14:48.000Z | week1/unit5.md | gauravkarkara/openSAP-RAP-Course-Artifacts | 2ec815424a49d0882dba843ecf6aecc4f7d4f383 | [
"Apache-2.0"
] | 161 | 2020-10-19T10:32:27.000Z | 2022-03-30T14:50:41.000Z | # HANDS-ON EXERCISE FOR WEEK 1 UNIT 5: PREPARING YOUR ABAP DEVELOPMENT ENVIRONMENT
## Introduction
The development environment used for this course consists of the SAP Cloud Platform ABAP Environment and ABAP Development Tools for Eclipse.
You can watch [unit 5 of week 1: Preparing Your ABAP Development Environment](https://open.sap.com/courses/cp13/items/6RRUwtY9ABBVBoywenimzq) on the openSAP.com platform.
In this hands-on exercise, you will set up your ABAP development environment for the development of applications with the ABAP RESTful Application Programming Model (RAP) on the SAP Cloud Platform ABAP Environment.
Follow the instructions below.
## Step 1. Install the ABAP Development Tools (ADT)
To install ADT, check out the prerequisites and follow the procedure provided on the _ABAP Development Tools_ site:
https://tools.hana.ondemand.com/#abap
## Step 2. Onboard to the SAP Cloud Platform ABAP Environment Trial
To onboard to the trial ABAP environment, check out the prerequisites and follow the instructions described in the tutorial:
https://developers.sap.com/tutorials/abap-environment-trial-onboarding.html
The tutorial also describes how to create an ABAP cloud project in ADT to connect to your SAP Cloud Platform ABAP Environment Trial account.
> **Please note**
> A faster onboarding process (using _Boosters_) is described in the tutorial. The _Boosters_-based process is different and faster than the one shown in the course video.
## Step 3. [Optional] Download the Service Key in the SAP Cloud Platform Trial Cockpit
In case you have already onboarded to the SAP Cloud Platform ABAP environment trial (_Step 2_) and would like to access your _Service Key_ in the SAP Cloud Platform trial cockpit, please follow the instructions provided below.
>**Please note**
>The _service key_ is needed for the creation of an _ABAP Cloud Project_ in the ABAP Development Tools (ADT).
1. In your web browser, open the [SAP Cloud Platform trial cockpit](https://cockpit.hanatrial.ondemand.com).
2. Navigate to your trial global account by clicking on **Enter Your Trial Account**.
3. Navigate to your **trial** subaccount.
4. In the **Spaces** area, go to the **dev** space and navigate to the **Service Instances** as shown on the screenshot.
5. Now, go to the instance **default_abap-trial** and click on the arrow (>) on the right-hand side as shown on the screenshot to open a side panel with further instance details.
6. In the side panel, go to the **Service Keys** area and download your service key.
**In case no service key is available**, then create a new one as shown on the screenshot and download it.
## Summary
You have completed the exercise!
In this unit, you have learned
- About setting up your development environment
- How to install ABAP Development Tools (ADT) in Eclipse
- How to get access to the SAP Cloud Platform ABAP envrionment trial
- How to connect to the trial ABAP system
- How to find and download the Service Key in the SAP Cloud Platform trial cockpit
## Next Exercise
[Week 1 Unit 6: Creating Your First ABAP Cloud Console App](unit6.md)
| 49.027778 | 229 | 0.754958 | eng_Latn | 0.962818 |
57a5754997d7b21cdfa705b5fd63daa60154e46c | 3,992 | md | Markdown | hugo-source/content/output/sahakAra nagar, bengaLUru/MULTI_NEW_MOON_SIDEREAL_MONTH_ADHIKA__CHITRA_AT_180/gregorian/2000s/2020s/2021_monthly/2021-10/2021-10-17.md | Prabhakaran-cbe/jyotisha | 689327c5944c6cc84b7e58af4deae2a4ebe94d7b | [
"MIT"
] | 40 | 2017-10-01T04:22:35.000Z | 2020-11-30T03:47:57.000Z | hugo-source/content/output/sahakAra nagar, bengaLUru/MULTI_NEW_MOON_SIDEREAL_MONTH_ADHIKA__CHITRA_AT_180/gregorian/2000s/2020s/2021_monthly/2021-10/2021-10-17.md | Prabhakaran-cbe/jyotisha | 689327c5944c6cc84b7e58af4deae2a4ebe94d7b | [
"MIT"
] | 71 | 2017-08-27T13:54:06.000Z | 2020-12-11T01:16:47.000Z | hugo-source/content/output/sahakAra nagar, bengaLUru/MULTI_NEW_MOON_SIDEREAL_MONTH_ADHIKA__CHITRA_AT_180/gregorian/2000s/2020s/2021_monthly/2021-10/2021-10-17.md | Prabhakaran-cbe/jyotisha | 689327c5944c6cc84b7e58af4deae2a4ebe94d7b | [
"MIT"
] | 23 | 2017-08-27T11:54:41.000Z | 2020-11-14T19:41:58.000Z | +++
title = "2021-10-17"
+++
## आश्वयुजः-07-12,कुम्भः-शतभिषक्🌛🌌◢◣तुला-चित्रा-07-01🌌🌞◢◣इषः-07-25🪐🌞भानुः
- Indian civil date: 1943-07-25, Islamic: 1443-03-10 Rabīʿ alʾ Awwal/Ūlā
- संवत्सरः - प्लवः
- वर्षसङ्ख्या 🌛- शकाब्दः 1943, विक्रमाब्दः 2078, कलियुगे 5122
___________________
- 🪐🌞**ऋतुमानम्** — शरदृतुः दक्षिणायनम्
- 🌌🌞**सौरमानम्** — शरदृतुः दक्षिणायनम्
- 🌛**चान्द्रमानम्** — शरदृतुः आश्वयुजः
___________________
## खचक्रस्थितिः
- |🌞-🌛|**तिथिः** — शुक्ल-द्वादशी►17:39; शुक्ल-त्रयोदशी►
- 🌌🌛**नक्षत्रम्** — शतभिषक्►09:50; पूर्वप्रोष्ठपदा► (मीनः)
- 🌌🌞**सौर-नक्षत्रम्** — चित्रा►
___________________
- 🌛+🌞**योगः** — वृद्धिः►21:34; ध्रुवः►
- २|🌛-🌞|**करणम्** — बालवः►17:39; कौलवः►29:50*; तैतिलः►
- 🌌🌛- **चन्द्राष्टम-राशिः**—सिंहः
___________________
- 🌞-🪐 **मूढग्रहाः** - मङ्गलः (2.92° → 3.25°)
- 🌞-🪐 **अमूढग्रहाः** - शनैश्चरः (-103.04° → -102.06°), गुरुः (-118.46° → -117.47°), शुक्रः (-46.46° → -46.53°), बुधः (13.50° → 14.70°)
___________________
## दिनमान-कालविभागाः
- 🌅**सूर्योदयः**—06:13-12:04🌞️-17:56🌇
- 🌛**चन्द्रोदयः**—15:53; **चन्द्रास्तमयः**—04:08(+1)
___________________
- 🌞⚝भट्टभास्कर-मते वीर्यवन्तः— **प्रातः**—06:13-07:41; **साङ्गवः**—09:09-10:37; **मध्याह्नः**—12:04-13:32; **अपराह्णः**—15:00-16:28; **सायाह्नः**—17:56-19:28
- 🌞⚝सायण-मते वीर्यवन्तः— **प्रातः-मु॰1**—06:13-07:00; **प्रातः-मु॰2**—07:00-07:47; **साङ्गवः-मु॰2**—09:21-10:07; **पूर्वाह्णः-मु॰2**—11:41-12:28; **अपराह्णः-मु॰2**—14:02-14:48; **सायाह्नः-मु॰2**—16:22-17:09; **सायाह्नः-मु॰3**—17:09-17:56
- 🌞कालान्तरम्— **ब्राह्मं मुहूर्तम्**—04:35-05:24; **मध्यरात्रिः**—22:51-01:18
___________________
- **राहुकालः**—16:28-17:56; **यमघण्टः**—12:04-13:32; **गुलिककालः**—15:00-16:28
___________________
- **शूलम्**—प्रतीची दिक् (►10:54); **परिहारः**–गुडम्
___________________
## उत्सवाः
- आकाशदीप-आरम्भः, तुला-कावेरी-स्नान-आरम्भः, तुला-सङ्क्रमण-पुण्यकालः, द्विदल-व्रत-आरम्भः
### आकाशदीप-आरम्भः
Observed on day 1 of Tulā (sidereal solar) month (Sūryodayaḥ/puurvaviddha). Offer Akasha Dipam for this entire month, in the evening, on a high place (pillar?). Light lamps using gingelly oil with eight wicks.
तुलायां तिलतैलेन सायङ्काले समागते।
आकाशदीपं यो दद्यान्मासमेकं हरिं प्रति।
महतीं श्रियमाप्नोति रूप-सौभाग्य-सम्पदम्॥
दामोदराय नभसि तुलायां लोलया सह।
प्रदीपं ते प्रयच्छामि नमोऽनन्ताय वेधसे॥
#### Details
- References
- Nirnaya Sindhu 146
- [Edit config file](https://github.com/jyotisham/adyatithi/blob/master/general/sidereal_solar_month/day/07/01/AkAzadIpa-ArambhaH.toml)
- Tags: LessCommonFestivals
### द्विदल-व्रत-आरम्भः
Observed on Śukla-Dvādaśī tithi of Āśvayujaḥ (lunar) month (Sūryodayaḥ/puurvaviddha).
अनिरुद्ध सुरैर्वन्द्य द्विदलव्रतमुत्तमम्।
करोम्यहमिषेमासे निर्विघ्नं कुरु मे प्रभो॥
#### Details
- [Edit config file](https://github.com/jyotisham/adyatithi/blob/master/general/lunar_month/tithi/07/12/dvidala-vrata-ArambhaH.toml)
- Tags: VratamStart SpecialPeriodStart CommonFestivals
### तुला-कावेरी-स्नान-आरम्भः
Observed on day 1 of Tulā (sidereal solar) month (Sūryodayaḥ/puurvaviddha). Perform snānam in Kaveri during this month.
षट्षष्टिकोटितीर्थानि द्विसप्तभुवनेषु च।
केशवस्याऽऽज्ञया यान्ति तुलामासे मरुद्वृधम्॥
#### Details
- [Edit config file](https://github.com/jyotisham/adyatithi/blob/master/devatA/nadI/sidereal_solar_month/day/07/01/tulA-kAvErI-snAna-ArambhaH.toml)
- Tags:
### तुला-सङ्क्रमण-पुण्यकालः
- 08:40→16:40
Tulā-Saṅkramaṇa Punyakala. Perform danam of rice/wheat/grains and cow ghee/curd etc.
तुलाप्रवेशे धान्यानां गोरसानामपीष्टदम्"
सङ्क्रान्तिस्नानाकरणे प्रत्यवायमाह शातातपः—
सूर्यसङ्क्रमणे पुण्ये न स्नायाद्यदि मानवः।
सप्तजन्मसु रोगी स्याद् दुःखभागी च जायते॥
सङ्क्रान्त्यां यानि दत्तानि हव्यकव्यानि मानवैः।
तानि तस्य ददात्यर्कः सप्तजन्मसु निश्चितम्॥
(स्मृतिमुक्ताफले आह्निक-काण्डे-पूर्वभागः)
#### Details
- [Edit config file](https://github.com/jyotisham/adyatithi/blob/master/time_focus/sankrAnti/description_only/tulA-saGkramaNa-puNyakAlaH.toml)
- Tags: SunSankranti CommonFestivals
| 35.642857 | 239 | 0.581413 | san_Deva | 0.250776 |
57a58f391aa76caeddbd82b95c3f7aeab1beb60a | 28 | md | Markdown | README.md | ethersummary/ethersummary.github.io | 0cdfc6f07560d4dbc3a3448bae62db5002b55d75 | [
"MIT"
] | null | null | null | README.md | ethersummary/ethersummary.github.io | 0cdfc6f07560d4dbc3a3448bae62db5002b55d75 | [
"MIT"
] | null | null | null | README.md | ethersummary/ethersummary.github.io | 0cdfc6f07560d4dbc3a3448bae62db5002b55d75 | [
"MIT"
] | null | null | null | "# ethersummary.github.io"
| 14 | 27 | 0.714286 | war_Latn | 0.129666 |
57a7a5b2dfdf42cf6fd660a76068f2d287abe6b3 | 21 | md | Markdown | README.md | mew1033/coolness | f806a69ed18147f018b9e642f80f5400e8dab163 | [
"MIT"
] | null | null | null | README.md | mew1033/coolness | f806a69ed18147f018b9e642f80f5400e8dab163 | [
"MIT"
] | null | null | null | README.md | mew1033/coolness | f806a69ed18147f018b9e642f80f5400e8dab163 | [
"MIT"
] | null | null | null | CCDC
====
CCDC Repo
| 4.2 | 9 | 0.571429 | kor_Hang | 0.996419 |
57a89a1462f1d53ec5d4d50b0a392d69d0d8c335 | 1,709 | md | Markdown | _posts/2018-12-21-algorithmPython-Q1-maze.md | namekun/minimal-mistakes | 16b44c833d3988d98239a22de865f667d7f230fa | [
"MIT"
] | 1 | 2018-06-19T04:07:46.000Z | 2018-06-19T04:07:46.000Z | _posts/2018-12-21-algorithmPython-Q1-maze.md | namekun/namekun.github.io | 16b44c833d3988d98239a22de865f667d7f230fa | [
"MIT"
] | null | null | null | _posts/2018-12-21-algorithmPython-Q1-maze.md | namekun/namekun.github.io | 16b44c833d3988d98239a22de865f667d7f230fa | [
"MIT"
] | null | null | null | ---
title: "모두의 알고리즘 with python - 알고리즘 문제풀이 1 - MAZE!"
tags:
- python
- algorithm
- 모두의알고리즘
comments: true
---
# 미로찾기 알고리즘
다음 그림과 같이 미로의 형태와 출발점 도착점이 주어졌을 때, 출발점에서 도착점까지 가기 위한 최단 경로를 찾는 알고리즘을 만들어보세요~
## 1. 문제 분석과 모델링
| **a** | **b** | **c** | **d** |
| ----- | ----- | ----- | ----- |
| **e** | **f** | **g** | **h** |
| **i** | **j** | **k** | **l** |
| **m** | **n** | **o** | **p** |
이렇게 생긴 미로가 있다. 벽은 a, e, i 와 b, f, j 사이에 하나, c, d와 g, h 사이에 벽 하나, n과 o 사이에 하나, g와 k 사이에 하나, k, o와 I, p사이에 하나가 있다.
이러한 미로를 그래프로 생각하고 딕셔너리 형식으로 나타낸다면 다음과 같다.
```python
maze = {
'a' : ['e'],
'b' : ['c', 'f'],
'c' : ['b', 'd'],
'd' : ['c'],
'e' : ['a', 'i'],
'f' : ['b', 'g', 'j'],
'g' : ['f', 'h'],
'h' : ['g', 'l'],
'i' : ['e', 'm'],
'j' : ['f', 'k', 'n'],
'k' : ['j', 'o'],
'l' : ['h', 'p'],
'm' : ['i', 'n'],
'n' : ['m', 'j'],
'o' : ['k'],
'p' : ['l']
}
```
이제 이 미로를 빠져나갈 코드를 작성해보자.
```python
# 이 문제는 탐색 문제이다.
# 출발점에서 도착점까지 미로를 헤쳐나가면된다.
# 도착점에 도달하면 끝낸다.
# 끝낼 수 없는 미로라면 ? 를 출력한다.
def mazeOut(g, start, end):
queue = [] # 앞으로 이동해야할 이동경로를 큐에 저장한다.
visited = set() # 방문했던 꼭짓점들을 기록한다.
# 시작점 추가
queue.append(start)
visited.add(start)
while queue:
x = queue.pop(0) # 큐에 저장된 가장 첫번째 데이터를 꺼낸다.
v = x[-1] # 이동경로의 마지막 문자는 우리가 처리해야할 문자이다.
if v == end: # 만약 우리가 마지막으로 꺼낸 문자가 도착점과 같다면?
return x
for i in g[v]: # 처리해야할 문자와 연결된 그래프 중에서
if i not in visited: # 아직 방문하지 않은 꼭짓점이 있다면
queue.append(x + i) # 큐에 있던 이동경로에 더해주고,
visited.add(i) # 방문했다는 것을 체크해줍니다.
return "?" # 도착점이 없는 미로라면 ? 를 리턴해줍니다.
print(mazeOut(maze, 'a', 'p'))
```
| 21.3625 | 112 | 0.433002 | kor_Hang | 1.000008 |
57a8b45b130d6ab6d550cea4e45122cc9cd0ed16 | 64 | md | Markdown | README.md | DianaCarolina3/Course-Definitive-HTML | b4aeafd5588d0c45de9cba67e367d41f56df3ac6 | [
"MIT"
] | null | null | null | README.md | DianaCarolina3/Course-Definitive-HTML | b4aeafd5588d0c45de9cba67e367d41f56df3ac6 | [
"MIT"
] | null | null | null | README.md | DianaCarolina3/Course-Definitive-HTML | b4aeafd5588d0c45de9cba67e367d41f56df3ac6 | [
"MIT"
] | null | null | null | # Definitive-Course-CSS-and-HTML
Definitive course css and html
| 21.333333 | 32 | 0.8125 | kor_Hang | 0.795456 |
57a8b822f27ca035ce2c13876ec87f464a5c3300 | 291 | md | Markdown | README.md | jnycz/d7_sk | 4d7c66a84ba736e505c5b34abee2d9cdf8e55454 | [
"MIT"
] | null | null | null | README.md | jnycz/d7_sk | 4d7c66a84ba736e505c5b34abee2d9cdf8e55454 | [
"MIT"
] | null | null | null | README.md | jnycz/d7_sk | 4d7c66a84ba736e505c5b34abee2d9cdf8e55454 | [
"MIT"
] | null | null | null | Drupal 7 Starter Kit
====================
Purpose
-------
This project was created as a Drupal 7 starter kit that leverages Drush. Modules and Themes are automatically pulled in based on what I find useful and timesaving.
Thanks to ghanbak for providing the template for this make file. | 29.1 | 164 | 0.725086 | eng_Latn | 0.999618 |
57a8d672f0bc73777c4f49a6040b2f399a180111 | 91 | md | Markdown | 차해운/FishBerry_홈페이지_테스트제작/README.md | Fishberry/RemoteFishbowl | a8b0d987efc6be135358029f5b45f2d3425d92f1 | [
"MIT"
] | 6 | 2019-01-03T05:47:34.000Z | 2020-11-21T00:57:06.000Z | 차해운/FishBerry_홈페이지_테스트제작/README.md | Fishberry/RemoteFishbowl | a8b0d987efc6be135358029f5b45f2d3425d92f1 | [
"MIT"
] | null | null | null | 차해운/FishBerry_홈페이지_테스트제작/README.md | Fishberry/RemoteFishbowl | a8b0d987efc6be135358029f5b45f2d3425d92f1 | [
"MIT"
] | 1 | 2019-01-06T09:40:35.000Z | 2019-01-06T09:40:35.000Z | # FishBerry Node.js 웹 사이트
파일을 내려받은 후 모듈설치를 위해 폴더 내에 콘솔을 위치시킨 후 npm i 명령어로 모듈을 다운받아 주세요.
| 22.75 | 63 | 0.703297 | kor_Hang | 1.00001 |
57aa3d80e959f9c3a1ff2cf9ef97963bfb81f1b2 | 246 | md | Markdown | Wiki/k8s.md | shafr/LinuxTips | bba38c55e291779e58e15f39302f3df3ec2eeb7d | [
"Apache-2.0"
] | 1 | 2016-11-06T12:51:59.000Z | 2016-11-06T12:51:59.000Z | Wiki/k8s.md | shafr/LinuxTips | bba38c55e291779e58e15f39302f3df3ec2eeb7d | [
"Apache-2.0"
] | null | null | null | Wiki/k8s.md | shafr/LinuxTips | bba38c55e291779e58e15f39302f3df3ec2eeb7d | [
"Apache-2.0"
] | null | null | null | Copy secrets between namespaces:
```
kubectl get secret secret1 --namespace=test -o yaml | sed 's/namespace: test/namespace: test1/g' | kubectl create -f -
```
Change context:
```
kubectl config set-context --current --namespace=ggckad-s2
```
| 24.6 | 120 | 0.711382 | eng_Latn | 0.609076 |
57aadee4cbdd36d7ca46e21a268a10705353df07 | 138 | md | Markdown | README.md | topher6345/pitchFollowerSynth | df741945438fc62feeac95eeabda73390013d773 | [
"MIT"
] | 1 | 2020-01-08T14:37:10.000Z | 2020-01-08T14:37:10.000Z | README.md | topher6345/pitchFollowerSynth | df741945438fc62feeac95eeabda73390013d773 | [
"MIT"
] | null | null | null | README.md | topher6345/pitchFollowerSynth | df741945438fc62feeac95eeabda73390013d773 | [
"MIT"
] | null | null | null | Pitch Follower Synth
====================
Quick Start
`bin/setup`
`bin/ds` to run distortionSynth
`bin/pf` to run pitchFollowerSynth
| 11.5 | 34 | 0.644928 | eng_Latn | 0.548862 |
57ac70b7e76de625169bfd23bbcee2d677960599 | 309 | md | Markdown | _documentation/developer/bzfs_api_functions/bz_getWorldCacheData.md | kilitary/bzflag.org | 20de1084a7901be21836d4f94afded5185a1e895 | [
"MIT"
] | 4 | 2019-01-12T06:51:11.000Z | 2020-01-31T06:07:27.000Z | _documentation/developer/bzfs_api_functions/bz_getWorldCacheData.md | kilitary/bzflag.org | 20de1084a7901be21836d4f94afded5185a1e895 | [
"MIT"
] | 32 | 2018-03-16T00:47:36.000Z | 2022-03-17T22:30:59.000Z | _documentation/developer/bzfs_api_functions/bz_getWorldCacheData.md | kilitary/bzflag.org | 20de1084a7901be21836d4f94afded5185a1e895 | [
"MIT"
] | 11 | 2017-02-08T15:08:31.000Z | 2021-05-26T16:07:29.000Z | ---
since: 2.4.0
category: Server Management
signatures:
- - dataType: unsigned char*
name: data
description: ~
default: ~
returns:
dataType: unsigned int
description: ~
---
This function needs a description. Please feel free to contribute a description to this function.
| 20.6 | 97 | 0.666667 | eng_Latn | 0.968976 |
57ad2203971b7b3b7eeba1cd655ed45ff31ea3bc | 1,767 | markdown | Markdown | _posts/2015/2015-10-22-java-batch.markdown | JUG-Ostfalen/JUG-Ostfalen.github.io | 43a7f14853189edd6eaf2410d48368117ae75e1e | [
"Apache-2.0"
] | 2 | 2015-01-19T19:53:30.000Z | 2015-04-14T15:13:50.000Z | _posts/2015/2015-10-22-java-batch.markdown | JUG-Ostfalen/JUG-Ostfalen.github.io | 43a7f14853189edd6eaf2410d48368117ae75e1e | [
"Apache-2.0"
] | 39 | 2015-01-07T09:40:07.000Z | 2019-07-29T12:01:21.000Z | _posts/2015/2015-10-22-java-batch.markdown | JUG-Ostfalen/JUG-Ostfalen.github.io | 43a7f14853189edd6eaf2410d48368117ae75e1e | [
"Apache-2.0"
] | 10 | 2015-10-20T10:49:22.000Z | 2019-07-29T10:40:40.000Z | ---
layout: post
title: "Java Batch: Massendatenverarbeitung nach JSR 352"
date: 2015-10-22 19:00
location: lineas
speaker: Dirk Weil
categories: event
organizer: JUG
author: jens
---
<img src="/assets/articles/2015/dirk-weil.png" class="speaker" />
Die Java-EE-Welt hat sich bislang um das Thema Batchverarbeitung gedrückt, was zur Entwicklung von
Batch-Frameworks wie Spring Batch geführt hat. Die Hintergrund-Verarbeitung von (i. d. R.)
Massendaten ist aber ein wichtiger Bestandteil vieler Enterprise-Anwendungen, dem der Einzug von
„Batch Applications for the Java Platform“ (JSR 352) in den Standard Java EE 7 nun Rechnung trägt.
Dirk Weil stellt in seinem Vortrag die Grundzüge der
Offline-Verarbeitung mit Jobs, Steps, Chunks etc. dar und demonstriert einige Beispiele auf dem
Java-EE-7-Server WildFly 8.
[Dirk Weil](https://www.xing.com/profile/Dirk_Weil2)
ist seit 1998 als Berater im Bereich Java tätig. Als Geschäftsführer
der GEDOPLAN GmbH in Bielefeld ist er für die Konzeption und Realisierung von
Informationssystemen auf Basis von Java EE verantwortlich. Seine langjährige
Erfahrung in der Entwicklung anspruchsvoller Unternehmenslösungen machen ihn
zu einem kompetenten Ansprechpartner und anerkannten Experten auf dem Gebiet
Java EE. Er ist Fachbuch-Autor, schreibt Artikel für Fachmagazine, hält Vorträge
und leitet Seminare und Workshops zu diversen Themen, Tools und Servern rund
um Java EE.
Dies ist schon der dritte Vortrag den Dirk Weil bei der JUG-Ostfalen hält und
das hat sehr gute Gründe
Zur Anmeldung:
**[Xing](https://www.xing.com/events/java-batch-massendatenverarbeitung-jsr-352-1602119)**
**[Eventbrite](https://www.eventbrite.de/e/java-batch-massendatenverarbeitung-nach-jsr-352-tickets-18705698247)** | 46.5 | 113 | 0.793435 | deu_Latn | 0.984605 |
57ad303365196b0a01c4ea2ac5a29876750eea94 | 236 | md | Markdown | README.md | mmbharadwaj/ec2creator | 41c9a14f92c8e476aee43ed3e77ad8da9f167ece | [
"MIT"
] | 2 | 2019-07-28T23:59:45.000Z | 2021-01-04T16:42:41.000Z | README.md | mmbharadwaj/ec2creator | 41c9a14f92c8e476aee43ed3e77ad8da9f167ece | [
"MIT"
] | null | null | null | README.md | mmbharadwaj/ec2creator | 41c9a14f92c8e476aee43ed3e77ad8da9f167ece | [
"MIT"
] | 6 | 2018-08-21T04:26:54.000Z | 2022-02-11T16:19:02.000Z | # Intro
This shell script is for creating multiple EC2 instances with just 1 execution of the script.
For more detailed explanation and demo video, please visit https://paulcodr.co/2017/use-shell-script-awscli-to-create-multiple-ec2/
| 39.333333 | 131 | 0.800847 | eng_Latn | 0.98245 |
57aeafc878239669e6252149f695cfba8d3dab08 | 1,196 | md | Markdown | vault/lexicon/G24230.md | mandolyte/uw-obsidian | 39e987c4cdc49d2a68e3af6b4e3fc84d1cda916d | [
"MIT"
] | null | null | null | vault/lexicon/G24230.md | mandolyte/uw-obsidian | 39e987c4cdc49d2a68e3af6b4e3fc84d1cda916d | [
"MIT"
] | null | null | null | vault/lexicon/G24230.md | mandolyte/uw-obsidian | 39e987c4cdc49d2a68e3af6b4e3fc84d1cda916d | [
"MIT"
] | null | null | null | # Ἰεχονίας, ου, ὁ.
<!-- Status: S3=Needs2ndReview -->
<!-- Lexica used for edits: BDAG, LN, FFM, A-S -->
## Word data
* Strongs: G24230.
* Alternate spellings:
* Principle Parts:
* Part of speech:
[Proper Noun](http://ugg.readthedocs.io/en/latest/proper_noun.html).
* Instances in the New Testament: 2.
* All Scriptures cited: Yes.
## Etymology:
* LXX/Hebrew glosses:
;Hebrew [יְהוֹיָכִין](//en-uhal/H3078): Jehoiakin.
* Time Period/Ancient Authors:
* Related words:
* Antonyms for all senses:
* Synonyms for all senses:
## Senses:
### Sense 1.0:
#### Definition:
The name of a king of Judah in the Old Testament
#### Glosses:
Jechoniah
#### Explanation:
#### Citations:
; [Ἰωσίας](../G25020/01.md) [δὲ](../G11610/01.md) [ἐγέννησεν](../G10800/01.md) [τὸν](../G35880/01.md) [Ἰεχονίαν](../G24230/01.md) [καὶ](../G25320/01.md) [τοὺς](../G35880/01.md) [ἀδελφοὺς](../G00800/01.md) [αὐτοῦ](../G08460/01.md) [ἐπὶ](../G19090/01.md) [τῆς](../G35880/01.md) [μετοικεσίας](../G33500/01.md) [Βαβυλῶνος](../G08970/01.md)
; " Josiah became the father of Jechoniah and his brothers at the time of the deportation to Babylon." (ULT):
[Matt 1:11](mat 1:11), [12](mat 1:12).
| 21.745455 | 335 | 0.641304 | eng_Latn | 0.280308 |
57af5930434ee239443fdb9413925517557dc11d | 1,339 | md | Markdown | README.md | boomin614/Mecab2 | e168697e58e189a63c2f74fdcd80700842c75242 | [
"MIT"
] | 3 | 2018-01-19T07:37:09.000Z | 2019-07-07T01:56:11.000Z | README.md | boomin614/Mecab2 | e168697e58e189a63c2f74fdcd80700842c75242 | [
"MIT"
] | null | null | null | README.md | boomin614/Mecab2 | e168697e58e189a63c2f74fdcd80700842c75242 | [
"MIT"
] | 5 | 2018-01-28T01:14:34.000Z | 2020-12-05T04:12:23.000Z | # What is this?
日本語解析ライブラリ[MeCab](http://taku910.github.io/mecab/)を使う際の、前処理を行うためのpython用ライブラリOcabです。
Mecabを雌株と見たてて、雄株ことOcabと命名。
使い方の詳細は、[こちらを参照](http://boomin.yokohama/archives/634)してください。
# How to use
## As a single program
単体で使うときは、以下のように使います。
```bash
$ python Ocab.py 南アルプスの天然水-Ｓｐａｒｋｉｎｇ*Ｌｅｍｏｎ+レモン一絞り
input : 南アルプスの天然水-Ｓｐａｒｋｉｎｇ*Ｌｅｍｏｎ+レモン一絞り
normalized: 南アルプスの天然水-Sparking*Lemon+レモン一絞り
wakati : 南アルプスの天然水 Sparking Lemon レモン 一 絞る
rmv st wds: 南アルプスの天然水 Sparking Lemon レモン 絞る
```
## As like Library in Python code
ライブラリとして使うときは、こんな感じです。
```python
$ python
from Ocab import Ocab, Regexp
c = Regexp()
text1 = c.normalize("南アルプスの天然水-Ｓｐａｒｋｉｎｇ*Ｌｅｍｏｎ+レモン一絞り")
print(text1) # 南アルプスの天然水-Sparking*Lemon+レモン一絞り
m = Ocab(target=["名詞","動詞","形容詞","副詞"])
text2 = m.wakati(text1)
print(text2) # 南アルプスの天然水 Sparking Lemon レモン 一 絞る
text3 = m.removeStoplist(text2, [])
print(text3) # 南アルプスの天然水 Sparking Lemon レモン 絞る
```
`m = Ocab(target=["名詞","動詞","形容詞","副詞"])`の部分でもっといろいろ指定できたりしますが、
そこはコード読んでください。
# License
This program is applied MIT License.
# Reference
1. [解析前に行うことが望ましい文字列の正規化処理](https://github.com/neologd/mecab-ipadic-neologd/wiki/Regexp.ja)
1. [MeCabとPythonで品詞を選びつつ分かち書きをしたよ](https://foolean.net/p/576)
1. [日本語のストップワードのリスト](http://svn.sourceforge.jp/svnroot/slothlib/CSharp/Version1/SlothLib/NLP/Filter/StopWord/word/Japanese.txt)
| 30.431818 | 127 | 0.756535 | yue_Hant | 0.665022 |
57b05e779849e0f3ee277f497e6e2921decd2015 | 76 | md | Markdown | README.md | motemen/ansi-sgr-parser | 3f82be789d7393afa13f257f3f88a1f015c28566 | [
"MIT"
] | 1 | 2015-05-15T02:23:57.000Z | 2015-05-15T02:23:57.000Z | README.md | motemen/ansi-sgr-parser | 3f82be789d7393afa13f257f3f88a1f015c28566 | [
"MIT"
] | null | null | null | README.md | motemen/ansi-sgr-parser | 3f82be789d7393afa13f257f3f88a1f015c28566 | [
"MIT"
] | null | null | null | ansi-sgr-parser
===============
Parse ANSI text attribute escape sequences
| 15.2 | 42 | 0.657895 | oci_Latn | 0.512051 |
57b1495dcfd1c5d3c0c184564f2911f1d25e21d6 | 667 | md | Markdown | docs/assembler/masm/dot-586p.md | Erikarts/cpp-docs.es-es | 9fef104c507e48ec178a316218e1e581753a277c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/assembler/masm/dot-586p.md | Erikarts/cpp-docs.es-es | 9fef104c507e48ec178a316218e1e581753a277c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/assembler/masm/dot-586p.md | Erikarts/cpp-docs.es-es | 9fef104c507e48ec178a316218e1e581753a277c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: .586P
ms.date: 08/30/2018
f1_keywords:
- .586P
helpviewer_keywords:
- .586P directive
ms.assetid: 90da2a7d-66f4-4073-b1a9-874de6e8f05d
ms.openlocfilehash: 328610e93ec22f0dd93786ab8fd0028bf8eba938
ms.sourcegitcommit: 6052185696adca270bc9bdbec45a626dd89cdcdd
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 10/31/2018
ms.locfileid: "50495550"
---
# <a name="586p"></a>.586P
Permite que el ensamblado de todas las instrucciones para el procesador Pentium (incluido con privilegios).
## <a name="syntax"></a>Sintaxis
> .586P
## <a name="see-also"></a>Vea también
[Referencia de directivas](../../assembler/masm/directives-reference.md)<br/> | 25.653846 | 107 | 0.767616 | spa_Latn | 0.305987 |
57b24d2c657a8c4bd216214b95f545e07f36891c | 827 | md | Markdown | _publications/2012-06-01-The-Halo-Masses-and-Galaxy-Environments-of-Hyperluminous-QSOs-at-z-raisebox-05extextasciitilde-27-in-the-Keck-Baryonic-Structure-Survey.md | ryantrainor/ryantrainor.github.io | 5dbe55e69ecbad606e92253fd3b146589b79c852 | [
"MIT"
] | null | null | null | _publications/2012-06-01-The-Halo-Masses-and-Galaxy-Environments-of-Hyperluminous-QSOs-at-z-raisebox-05extextasciitilde-27-in-the-Keck-Baryonic-Structure-Survey.md | ryantrainor/ryantrainor.github.io | 5dbe55e69ecbad606e92253fd3b146589b79c852 | [
"MIT"
] | null | null | null | _publications/2012-06-01-The-Halo-Masses-and-Galaxy-Environments-of-Hyperluminous-QSOs-at-z-raisebox-05extextasciitilde-27-in-the-Keck-Baryonic-Structure-Survey.md | ryantrainor/ryantrainor.github.io | 5dbe55e69ecbad606e92253fd3b146589b79c852 | [
"MIT"
] | null | null | null | ---
title: "The Halo Masses and Galaxy Environments of Hyperluminous QSOs at z raisebox-0.5extextasciitilde= 2.7 in the Keck Baryonic Structure Survey"
collection: publications
permalink: /publication/2012-06-01-The-Halo-Masses-and-Galaxy-Environments-of-Hyperluminous-QSOs-at-z-raisebox-05extextasciitilde-27-in-the-Keck-Baryonic-Structure-Survey
date: 2012-06-01
venue: 'apj'
citation: ' Ryan {Trainor}, Charles {Steidel}, "The Halo Masses and Galaxy Environments of Hyperluminous QSOs at z raisebox-0.5extextasciitilde= 2.7 in the Keck Baryonic Structure Survey." apj, 2012.'
---
Use [Google Scholar](https://scholar.google.com/scholar?q=The+Halo+Masses+and+Galaxy+Environments+of+Hyperluminous+QSOs+at+z+raisebox+0.5extextasciitilde=+2.7+in+the+Keck+Baryonic+Structure+Survey){:target="_blank"} for full citation | 91.888889 | 233 | 0.796856 | yue_Hant | 0.289546 |
57b2f4b74f2856512ed7819740045786494af044 | 547 | md | Markdown | posts/crisis-in-kyrgyzstan.md | arpith/blog | 5244ea5803aa2faf80ef2354de8ea2ef856235e6 | [
"MIT"
] | null | null | null | posts/crisis-in-kyrgyzstan.md | arpith/blog | 5244ea5803aa2faf80ef2354de8ea2ef856235e6 | [
"MIT"
] | null | null | null | posts/crisis-in-kyrgyzstan.md | arpith/blog | 5244ea5803aa2faf80ef2354de8ea2ef856235e6 | [
"MIT"
] | null | null | null | ---
layout: post
date: 2010-04-07 18:25:39 GMT
title: "Crisis in Kyrgyzstan"
---
# [Crisis in Kyrgyzstan](http://www.boston.com/bigpicture/2010/04/crisis_in_kyrgyzstan.html)
> As riot police fired on opposition members and protesters fought with stones and captured weapons, estimates of casualties have varied widely, with reports ranging from 12 killed to over 100 killed. Opposition leaders appear to have taken over some of the national television channels, and President Kurmanbek Bakiyev appears to have fled the capital, Bishkek overnight. | 68.375 | 372 | 0.798903 | eng_Latn | 0.996322 |
57b30db24183049303e7ce9e2b4cfc1964c7d049 | 36 | md | Markdown | demos/demo2/README.md | tw00/grapql-demos | 043bd1d38aff39c0cfb90f0b9b4d330cd5f09952 | [
"MIT"
] | null | null | null | demos/demo2/README.md | tw00/grapql-demos | 043bd1d38aff39c0cfb90f0b9b4d330cd5f09952 | [
"MIT"
] | null | null | null | demos/demo2/README.md | tw00/grapql-demos | 043bd1d38aff39c0cfb90f0b9b4d330cd5f09952 | [
"MIT"
] | null | null | null | This demo shows how resolvers work.
| 18 | 35 | 0.805556 | eng_Latn | 0.999794 |
57b324cc0bbf958eaf0b6da6b472d6389bc1d4b1 | 981 | md | Markdown | README.md | MindyPHP/Template | 4f46f8153e3428e53ae00387ddaf51f3634d65f4 | [
"MIT"
] | 1 | 2018-01-14T15:57:40.000Z | 2018-01-14T15:57:40.000Z | README.md | MindyPHP/Template | 4f46f8153e3428e53ae00387ddaf51f3634d65f4 | [
"MIT"
] | null | null | null | README.md | MindyPHP/Template | 4f46f8153e3428e53ae00387ddaf51f3634d65f4 | [
"MIT"
] | null | null | null | # Template Component
[](https://travis-ci.org/MindyPHP/Template)
[](https://codecov.io/gh/MindyPHP/Template)
[](https://packagist.org/packages/mindy/template)
[](https://packagist.org/packages/mindy/template)
The Template Component
Resources
---------
* [Documentation](https://mindy-cms.com/doc/current/components/template/index.html)
* [Contributing](https://mindy-cms.com/doc/current/contributing/index.html)
* [Report issues](https://github.com/MindyPHP/mindy/issues) and
[send Pull Requests](https://github.com/MindyPHP/mindy/pulls)
in the [main Mindy repository](https://github.com/MindyPHP/mindy)
| 49.05 | 125 | 0.749235 | yue_Hant | 0.637933 |
57b3d4ffb5415b770bedd6cd0f43676047e447c7 | 5,443 | md | Markdown | TIPs/tip-001.md | TP-Lab/TIPs | b4dad2696edd969252468594efa3b6551e1f29c4 | [
"Apache-2.0"
] | 3 | 2021-11-08T14:36:18.000Z | 2021-11-19T09:22:20.000Z | TIPs/tip-001.md | TP-Lab/TIPs | b4dad2696edd969252468594efa3b6551e1f29c4 | [
"Apache-2.0"
] | 1 | 2021-12-25T12:13:16.000Z | 2022-01-14T04:14:44.000Z | TIPs/tip-001.md | TP-Lab/TIPs | b4dad2696edd969252468594efa3b6551e1f29c4 | [
"Apache-2.0"
] | null | null | null | ---
tip: 001
title: Add DApps to TokenPocket
status: done
created: 2021.11.08
---
## Language
- en [English](tip-001.md)
- zh_CN [中文](tip-001.zh_CN.md)
## <a name='summary'></a>Overview
TIP-001 is a proposal of adding DApp to TokenPocket. Developers could use this proposal to add Dapp to TokenPocket easily and quickly.
A single DApp can be added to the wallet, or multiple DApps can be added to the wallet in batches.
## <a name='usage'></a>How to add a single DApp to the wallet
First you have to build data of DApp Json, and then add DApp to TokenPocket through Deeklink, tp-js-sdk or QR Code
DApp Json structure as following：（detailed introduction below）
```
{
"title": "Etherscan",
"url": "https://etherscan.io/",
"icon_url": "https://etherscan.io/images/logo-ether.png?v=0.0.2",
"protocol": "TIP-001",
"protocol_version": "1.0",
"chain_list": [{
"network": "ethereum",
"chain_id": "1"
}],
"desc": "Etherscan is a Block Explorer and Analytics Platform for Ethereum, a decentralized smart contracts platform",
"full_screen": 0,
"hori_vert": 0,
"title_color": "0xffffff",
"navi_color": "0x2890fe"
}
```
## <a name='add'></a>How to add DApp to TokenPocket
#### Method 1：Deeplink
1.Build URL**tpdiscover://add?params=..**, params' value is DApp Json. Note: you need to decode json subject, below is result：
```
tpdiscover://add?params=%7B%22title%22%3A%20%22Etherscan%22%2C%22url%22%3A%20%22https%3A%2F%2Fetherscan.io%2F%22%2C%22icon_url%22%3A%20%22https%3A%2F%2Fetherscan.io%2Fimages%2Flogo-ether.png%3Fv%3D0.0.2%22%2C%22protocol%22%3A%20%22TIP-001%22%2C%22protocol_version%22%3A%20%221.0%22%2C%22chain_list%22%3A%5B%5D%2C%22desc%22%3A%20%22Etherscan%20is%20a%20Block%20Explorer%20and%20Analytics%20Platform%20for%20Ethereum%2C%20a%20decentralized%20smart%20contracts%20platform%22%2C%22full_screen%22%3A%200%2C%22hori_vert%22%3A%200%2C%22title_color%22%3A%20%220xffffff%22%2C%22navi_color%22%3A%20%220x2890fe%22%7D
```
2.Use on the web
```
<a href="tpdiscover://add?params=...">Add DApp to TokenPocket</a>
```
#### Method 2：tp-js-sdk
After built data of DApp Json, call tp-js-sdk's function: addDAppToDiscover**
#### Method 3：QR Code
After built data of DApp Json, generated the QR code, click the up right conner to scan on TokenPocket.
## <a name='dapp'></a>About DApp JSON
DApp JSON structure as follow:
- `title`: `String`
- `url`: `String`
- `icon_url`: `String`
- `protocol`: `String`
- `protocol_version`: `String`
- `chain_list`: `Array`
- `desc`: `String`
- `full_screen`: `Integer`
- `hori_vert`: `Integer`
- `title_color`: `String`
- `navi_color`: `String`
among them**title**，**url** and **icon_url** are required option to fill，when using QR code，**protocol** is also required option to fill，and other options are optional to fill
chain_list structure as follow：
- `chain_list`: `Array`
- `network` : `Stirng`
- `chain_id` : `String`
- `ss58` : `String`
Introductions of each field：
- title: DApp's title(name)
- url: DApp's URL
- icon_url: DApp logo's URL
- protocol: TIP，such as TIP-001
- protocol_version: version number of protocol. If protocol upgrade from 1.0 to 2.0, it requied ungrade accordingly.
- chain_list: point out which chain is available for the DApp, such as DApp support Ethereum, Binance Smart Chain, HECO; When it is empty, then no limitation, which means support all chains
- desc: DApp's describe text
- full_screen: Full screen or not，1 means full screen，0 means not full screen
- hori_vert: Landscape or not，0 means portrait screen, 1 means landscape mode
- title_color: when DApp under not full screen mode, will display navigation bar, it used to appoint the font color of navigation bar (when under full screen mode, then this field is invalid)
- navi_color: when DApp under not full screen mode, will display navigation bar, it used to appoint the background color of navigation bar (when under full screen mode, then this field is invalid)
#### How to use chain_list
**chain_list** is used to point out which chain is available for the DApp, such as DApp support Ethereum, Binance Smart Chain, HECO; When it is empty, then no limitation, which means support all chains
1.Appoint EVM Chain. When need to appoint DApp is support Ethereum, Binance Smart Chain, HECO, the field as follow
```
[{
"network": "ethereum",
"chain_id": "1"
},
{
"network": "ethereum",
"chain_id": "56"
},
{
"network": "ethereum",
"chain_id": "128"
}
]
```
differentiate throughchain_id，it apply to all EVM chain
2.Appoint network like Tron, Solana, ect. Differentiate chain through the symbol of native token
```
[{
"network": "SOL"
}, {
"network": "TRX"
}]
```
3.Appoint Polkadot series chain. Differentiate chain throughss58
```
[{
"network": "polkadot",
"ss58": "0"
}, {
"network": "polkadot",
"ss58": "2"
}, {
"network": "polkadot",
"ss58": "27"
}]
```
## <a name='dapps'></a>How to add DApps to the wallet in batches
1.Build DApp List data as follows
```
{
"protocol": "TIP-001",
"name": "NFT List",
"logo_uri": "https:https://raw.githubusercontent.com/compound-finance/token-list/master/assets/compound-interface.svg",
"timestamp": "2021-05-27T20:37:00.000+00:00",
"version": 1,
"dapp_list": []
}
```
Put DApps data to **dapp_list**.
2.Upload and save the Json data as a url link, such as [Example](https://gz.bcebos.com/v1/tokenpocket-test/clement/dapplist.json)
3.Find **Add DApp List** on the wallet, copy and paste the link.
| 33.392638 | 605 | 0.713761 | eng_Latn | 0.901758 |
57b5890e6f95a0cd5d1983f727ca319114b18c02 | 332 | md | Markdown | automation/e2e/README.md | nitpum/webring | 082e31e00a6501819bc0775442eb4a525131151e | [
"MIT"
] | 115 | 2021-01-16T20:41:42.000Z | 2022-03-16T06:13:52.000Z | automation/e2e/README.md | nitpum/webring | 082e31e00a6501819bc0775442eb4a525131151e | [
"MIT"
] | 83 | 2021-01-17T08:44:40.000Z | 2022-03-20T07:07:03.000Z | automation/e2e/README.md | nitpum/webring | 082e31e00a6501819bc0775442eb4a525131151e | [
"MIT"
] | 95 | 2021-01-17T08:23:16.000Z | 2022-03-08T10:49:25.000Z | # webring e2e
E2E tests based on Cypress.
## Run with Docker
(Note: Invoke this command in repo root.)
```
docker-compose -f docker-compose.e2e.yml up
```
Then, open <http://localhost:6080> to control Cypress Test Runner.
## Development
Run `yarn` inside `automation/e2e` first so that type definitions are properly fetched.
| 18.444444 | 87 | 0.731928 | eng_Latn | 0.871642 |
57b5b91275bfec7ec0a1e59195130982a75c5ba4 | 3,890 | md | Markdown | README_Swift.md | djroser/EBBannerView | 5214a65461788898f3b6ea2d5b177116d1753227 | [
"MIT"
] | 722 | 2017-11-01T01:16:40.000Z | 2022-03-28T06:12:49.000Z | README_Swift.md | djroser/EBBannerView | 5214a65461788898f3b6ea2d5b177116d1753227 | [
"MIT"
] | 47 | 2017-11-03T03:33:00.000Z | 2021-12-07T08:25:43.000Z | README_Swift.md | djroser/EBBannerView | 5214a65461788898f3b6ea2d5b177116d1753227 | [
"MIT"
] | 121 | 2017-11-01T06:17:06.000Z | 2022-01-04T07:36:55.000Z | 查看中文文档 [中文 Swift README.md](README_CHS_Swift.md)
Email：[email protected]
微信：pikacode
# EBBannerView
Only one line to show:
- a banner the same style as iOS Push Notifications (auto show iOS 9~13 styles up to system version)
- auto play a sound or vibrate when the banner is showing
- support swipe down gesture for a long text
And more：
- custom banner's icon/title/date/content/animation_time_interval
- custom the sound (use system sound or play a sound file)
- autosize portrait/landscape frame
- show a custom view with different frame in portrait/landscape
- custom view has different animation mode, appear from top/left/right/left/center
- NSNotification with click event and pass a value
## Screenshot
### System style:
### Custom style:
## Installation
### pod
```python
use_frameworks!
target 'YourTargetName' do
pod 'EBBannerViewSwift', '1.1.3'
end
```
### Demo
[Swift Demo](SwiftDemo)
## Usage
### System style
---
```swift
import EBBannerViewSwift
```
2 ways to use:
#### 1.Fast way to show a iOS style banner with one line
up to system version，will show iOS 9~13 style，auto show app icon/name.
```swift
EBSystemBanner.show("something")
```
#### 2.Customize any property of the banner
```swift
//1.create a banner, custom all values
let banner = EBSystemBanner()
.style(.iOS13)
.icon(UIImage(named: "icon"))
.appName("Somebook")
.title("title")
.content("some content")
.date("now")
.vibrateOnMute(true)
.object(anyObj) // let anyObj: Any?
.sound(.name("sing.mp3"))
.onClick { (b) in
print(b.title!)
print(b.object!)
}
//2.show
banner.show()
```
##### Parameters:
(if not set will use default values)
- `style`：the iOS style, default is `UIDevice.currentDevice.systemVersion.intValue`, type enum : NSInteger {9/10/11}
- `icon`：the icon, default is app icon, type UIImage
- `title`：the title, default is app name, type NSString
- `date`：the date, default is localized string @"现在" = @"now", type NSString
- `content`：the content, type NSString
- `showDuration`：the animation time(show the banner), type NSTimeInterval, default is 0.3
- `hideDuration`：the animation time(hide the banner), type NSTimeInterval, default is 0.5
- `stayDuration`：how long the banner will stay before hide, type NSTimeInterval, default is 4.0
- `spreadStayDuration`：how long a long text banner will stay before hide when it is expanded, default is 4.0. U can set it a large value, then the banner will not hide, until customer click it or call 'hide'
- `object`：you can set it when create, then get it when clicked by adding an observer (see below), default is `content`，type id
- `soundID`：the sound will play when the banner is showing (when the mute is turn on iPhone will vibrate), type UInt32
- it's iOS system sound id, default push notification sound "Tritone" is 1312
- More sound id to see here [iOS Predefined sounds](http://iphonedevwiki.net/index.php/AudioServices#) or here [AudioServices sounds](http://www.cocoachina.com/bbs/read.php?tid=134344)
- You can download all the system sounds [UISounds.zip](/UISounds.zip) , listen and choose one which you perfer, then check out it's `id` with the form above
- `soundName`：play a cusome sound file, type NSString
- drag the file to Xcode proj
- pass the file name and extension，e.g. `banner.soundName = @"sound.mp3"`
- `showDetailOrHideWhenClickLongText`： when click a long text banner, expand it for all height or hide it, YES = expand/NO = hide, default is YES
#### Look for more details please:
- download the demo
- view the comment in source code
- compare with objc readme | 26.827586 | 207 | 0.682262 | eng_Latn | 0.934398 |
57b73da73c65439ca0ead74b98b0f41576865a0e | 2,534 | md | Markdown | README.md | kulanah/3dscene-creator | 1248a9d56b0f1b061edf7bf6b1d6910078dbb5a8 | [
"MIT"
] | null | null | null | README.md | kulanah/3dscene-creator | 1248a9d56b0f1b061edf7bf6b1d6910078dbb5a8 | [
"MIT"
] | 25 | 2018-07-18T17:34:41.000Z | 2018-11-21T18:22:57.000Z | README.md | kulanah/3dscene-creator | 1248a9d56b0f1b061edf7bf6b1d6910078dbb5a8 | [
"MIT"
] | null | null | null | # 3d Scene Creator
3d Scene creator is just that, a 3d scene creator. It allows you to place 3d objects arbitraily in a scene, then move them about or edit their various paramters.
## Getting Started
To get started running the program download the directory however you choose to do that. Navigate to the directory with a command line program of some kind. Then run the following two commands `npm install` and then `npm start`. This will open an instance of your browser to localhost:3000, which you can always navigate back to if you lose your instance.
### Prerequisites
NPM is all that's required. It will handle all prereqs.
## Issue Templates
### Enhancements/Feature requests
1. Summary
* As [the actor], I want [the something], so that I can [the goal].
* The actor — the person using the feature.
* The something — what the user needs the feature for.
* The goal — why the user needs it.
2. Acceptance Criteria
* This should detail what success for the ticket looks like. Each of these sentences should start with "It's done when..."
3. Other Details
* This could be links to assets that need to be added, further documentation for the request, mockups of how it should look, or anything else useful to the request.
### Bug Reports
1. Summary
* Give a summary of what should happen, "instead of", then a summary of what actually happens.
2. Scenario
* Give a numbered list of the steps to recreate the bug in question. List any required states or else. This should give you 100% of steps to reproduce the bug.
3. Expected Result
* Detail the expected resutls, complete with any state changes or navigations required.
4. Actual Result
* What happens when you trigger the bug. Only list the deviations from the expected result above.
5. Extra Information
* If there are any error codes include thoses here.
* Screenshots of the bug in question are also very helpful to understand what is actually going on.
* If there are related bugs, or if you can pinpoint what new code introduced the bug pointing that out here is helpful.
## Built With
* [React](https://reactjs.org/) - The web framework used
* [Redux](https://redux.js.org/) - The state management tool
* [three.js](https://threejs.org/) - The rendering tool for the 3d scene
## Authors
* **Devon Butler** - *Design and code* - [Kulanah](https://github.com/Kulanah)
## License
This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details | 41.540984 | 358 | 0.733623 | eng_Latn | 0.999583 |
57ba010d976aa72d8ee5dfaf752b57c3a298f261 | 18,573 | md | Markdown | articles/active-directory/saas-apps/sap-hana-cloud-platform-identity-authentication-tutorial.md | changeworld/azure-docs.pl-pl | f97283ce868106fdb5236557ef827e56b43d803e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/saas-apps/sap-hana-cloud-platform-identity-authentication-tutorial.md | changeworld/azure-docs.pl-pl | f97283ce868106fdb5236557ef827e56b43d803e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/saas-apps/sap-hana-cloud-platform-identity-authentication-tutorial.md | changeworld/azure-docs.pl-pl | f97283ce868106fdb5236557ef827e56b43d803e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Samouczek: Integracja usługi Azure Active Directory z uwierzytelnianiem tożsamości platformy SAP Cloud Platform | Dokumenty firmy Microsoft'
description: Dowiedz się, jak skonfigurować logowanie jednokrotne między usługami Azure Active Directory i SAP Cloud Platform Identity Authentication.
services: active-directory
documentationCenter: na
author: jeevansd
manager: mtillman
ms.reviewer: barbkess
ms.assetid: 1c1320d1-7ba4-4b5f-926f-4996b44d9b5e
ms.service: active-directory
ms.subservice: saas-app-tutorial
ms.workload: identity
ms.tgt_pltfrm: na
ms.topic: tutorial
ms.date: 01/16/2020
ms.author: jeedes
ms.collection: M365-identity-device-management
ms.openlocfilehash: 95be73bd125c124409585a478fa9707e7b6a2ac2
ms.sourcegitcommit: 0947111b263015136bca0e6ec5a8c570b3f700ff
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 03/24/2020
ms.locfileid: "76289071"
---
# <a name="tutorial-azure-active-directory-single-sign-on-sso-integration-with-sap-cloud-platform-identity-authentication"></a>Samouczek: Integracja rejestracji jednokrotnej usługi Azure Active Directory (SSO) z uwierzytelnianiem tożsamości platformy SAP cloud
W tym samouczku dowiesz się, jak zintegrować uwierzytelnianie tożsamości platformy SAP Cloud Platform z usługą Azure Active Directory (Azure AD). Po zintegrowaniu uwierzytelniania tożsamości platformy SAP Cloud Platform z usługą Azure AD można:
* Kontrola w usłudze Azure AD, która ma dostęp do uwierzytelniania tożsamości platformy SAP Cloud Platform.
* Włącz użytkownikom automatyczne logowanie do uwierzytelniania tożsamości platformy SAP Cloud Platform za pomocą ich kont usługi Azure AD.
* Zarządzaj kontami w jednej centralnej lokalizacji — witrynie Azure Portal.
Aby dowiedzieć się więcej o integracji aplikacji SaaS z usługą Azure AD, zobacz [Co to jest dostęp do aplikacji i logowanie jednokrotne za pomocą usługi Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis).
## <a name="prerequisites"></a>Wymagania wstępne
Aby rozpocząć, potrzebujesz następujących elementów:
* Subskrypcja usługi Azure AD. Jeśli nie masz subskrypcji, możesz uzyskać [bezpłatne konto.](https://azure.microsoft.com/free/)
* Subskrypcja z włączoną funkcją rejestracji jednokrotnej (SSO) usługi SAP Cloud Platform Identity Authentication.
## <a name="scenario-description"></a>Opis scenariusza
W tym samouczku skonfigurujesz i przetestujesz logowanie jednokrotne usługi Azure AD w środowisku testowym.
* Usługa SAP Cloud Platform Identity Authentication obsługuje logowanie jednokrotne zainicjowane przez **dostawcę usługi** oraz **dostawcę tożsamości**
* Po skonfigurowaniu uwierzytelniania tożsamości platformy SAP Cloud Platform można wymusić kontrole sesji, które chronią eksfiltrację i infiltrację poufnych danych organizacji w czasie rzeczywistym. Formanty sesji rozciągają się od dostępu warunkowego. [Dowiedz się, jak wymusić kontrolę nad sesją za pomocą programu Microsoft Cloud App Security](https://docs.microsoft.com/cloud-app-security/proxy-deployment-aad)
Zanim zagłębisz się w szczegóły techniczne, konieczne jest zrozumienie koncepcji, które zostaną omówione. Usługi SAP Cloud Platform Identity Authentication oraz Active Directory Federation Services umożliwiają wdrożenie logowania jednokrotnego we wszystkich aplikacjach i usługach chronionych przez usługę Azure AD (jako dostawcę tożsamości) z aplikacjami i usługami SAP chronionymi przez usługę SAP Cloud Platform Identity Authentication.
Obecnie usługa SAP Cloud Platform Identity Authentication pełni funkcję dodatkowego dostawcy tożsamości w aplikacjach SAP. Usługa Azure Active Directory z kolei pełni funkcję głównego dostawcy tożsamości w tej konfiguracji.
Na poniższym diagramie przedstawiono tę relację:
W tej konfiguracji dzierżawa usługi SAP Cloud Platform Identity Authentication jest konfigurowana jako zaufana aplikacja w usłudze Azure Active Directory.
Wszystkie usługi i aplikacje SAP, które chcesz zabezpieczyć w ten sposób, są następnie konfigurowane w konsoli zarządzania usługą SAP Cloud Platform Identity Authentication.
Autoryzacja dostępu do aplikacji i usług SAP musi mieć miejsce w usłudze SAP Cloud Platform Identity Authentication, a nie w usłudze Azure Active Directory.
Dzięki skonfigurowaniu usługi SAP Cloud Platform Identity Authentication jako aplikacji w witrynie Azure Active Directory Marketplace nie musisz konfigurować pojedynczych oświadczeń lub asercji SAML.
> [!NOTE]
> Obecnie tylko logowanie jednokrotne przez Internet zostało przetestowane przez obie strony. Przepływy, które są niezbędne do nawiązania komunikacji pomiędzy aplikacją a interfejsem API lub pomiędzy interfejsami API, powinny działać, ale nie zostały jeszcze przetestowane. Zostaną przetestowane później.
## <a name="adding-sap-cloud-platform-identity-authentication-from-the-gallery"></a>Dodawanie usługi SAP Cloud Platform Identity Authentication z galerii
Aby skonfigurować integrację usługi SAP Cloud Platform Identity Authentication z usługą Azure AD, należy dodać aplikację SAP Cloud Platform Identity Authentication z galerii do listy zarządzanych aplikacji SaaS.
1. Zaloguj się do [witryny Azure portal](https://portal.azure.com) przy użyciu konta służbowego lub konta firmy Microsoft.
1. W lewym okienku nawigacji wybierz usługę **Azure Active Directory.**
1. Przejdź do **aplikacji korporacyjnych,** a następnie wybierz pozycję **Wszystkie aplikacje**.
1. Aby dodać nową aplikację, wybierz pozycję **Nowa aplikacja**.
1. W sekcji **Dodaj z galerii** wpisz w polu wyszukiwania **uwierzytelnianie tożsamości platformy SAP Cloud.**
1. Wybierz **sap cloud platform uwierzytelniania tożsamości** z panelu wyników, a następnie dodać aplikację. Poczekaj kilka sekund, gdy aplikacja zostanie dodana do dzierżawy.
## <a name="configure-and-test-azure-ad-single-sign-on-for-sap-cloud-platform-identity-authentication"></a>Konfigurowanie i testowanie logowania jednokrotnego usługi Azure AD dla uwierzytelniania tożsamości platformy SAP Cloud
Konfigurowanie i testowanie usługi Azure AD SSO za pomocą uwierzytelniania tożsamości platformy SAP Cloud platform przy użyciu użytkownika testowego o nazwie **B.Simon**. Aby funkcja SSO działała, należy ustanowić relację łącza między użytkownikiem usługi Azure AD a powiązanym użytkownikiem w uwierzytelnianiu tożsamości platformy SAP Cloud Platform.
Aby skonfigurować i przetestować usługę Azure AD SSO za pomocą uwierzytelniania tożsamości platformy SAP Cloud, wykonaj następujące bloki konstrukcyjne:
1. **[Skonfiguruj samouszeńcę usługi Azure AD](#configure-azure-ad-sso)** — aby umożliwić użytkownikom korzystanie z tej funkcji.
* **[Utwórz użytkownika testowego usługi Azure AD](#create-an-azure-ad-test-user)** — aby przetestować logowanie jednokrotne usługi Azure AD za pomocą usługi B.Simon.
* **[Przypisz użytkownika testowego usługi Azure AD](#assign-the-azure-ad-test-user)** — aby umożliwić B.Simon używać logowania jednokrotnego usługi Azure AD.
1. **[Skonfiguruj logowanie jednokrotne uwierzytelnianie tożsamości platformy SAP Cloud Platform](#configure-sap-cloud-platform-identity-authentication-sso)** — aby skonfigurować ustawienia logowania jednokrotnego po stronie aplikacji.
* **[Utwórz użytkownika testowego uwierzytelniania tożsamości platformy SAP Cloud Platform](#create-sap-cloud-platform-identity-authentication-test-user)** — aby mieć odpowiednik B.Simon w uwierzytelnianiu tożsamości platformy sap cloud, który jest połączony z reprezentacją użytkownika usługi Azure AD.
1. **[Test SSO](#test-sso)** - aby sprawdzić, czy konfiguracja działa.
## <a name="configure-azure-ad-sso"></a>Konfigurowanie rejestracji jednokrotnej w usłudze Azure AD
Wykonaj następujące kroki, aby włączyć usługę Azure AD SSO w witrynie Azure portal.
1. W [witrynie Azure portal](https://portal.azure.com/)— na stronie integracji aplikacji **uwierzytelniania tożsamości platformy SAP Cloud,** znajdź sekcję **Zarządzaj** i wybierz **opcję logowanie jednokrotne**.
1. Na stronie **Wybierz metodę logowania jednokrotnego** wybierz pozycję **SAML**.
1. Na stronie **Konfigurowanie logowania jednokrotnego za pomocą saml** kliknij ikonę edycji/pióra dla **podstawowej konfiguracji SAML,** aby edytować ustawienia.
4. W sekcji **Podstawowa konfiguracja SAML,** jeśli chcesz skonfigurować w trybie inicjowanym **przez IDP,** wykonaj następujące czynności:
a. W polu tekstowym **Identyfikator** wpisz adres URL przy użyciu następującego wzorca:`<IAS-tenant-id>.accounts.ondemand.com`
b. W polu tekstowym **Adres URL odpowiedzi** wpisz adres URL, korzystając z następującego wzorca: `https://<IAS-tenant-id>.accounts.ondemand.com/saml2/idp/acs/<IAS-tenant-id>.accounts.ondemand.com`
> [!NOTE]
> Te wartości nie są prawdziwe. Zastąp te wartości rzeczywistymi wartościami identyfikatora i adresu URL odpowiedzi. Skontaktuj się z [zespołem obsługi klienta usługi SAP Cloud Platform Identity Authentication](https://cloudplatform.sap.com/capabilities/security/trustcenter.html), aby uzyskać te wartości. Jeśli nie rozumiesz wartości identyfikatora, zapoznaj się z tematem [Tenant SAML 2.0 configuration (Konfiguracja formatu SAML 2.0 dzierżawy)](https://help.hana.ondemand.com/cloud_identity/frameset.htm?e81a19b0067f4646982d7200a8dab3ca.html) w dokumentacji usługi SAP Cloud Platform Identity Authentication.
5. Kliknij **pozycję Ustaw dodatkowe adresy URL** i wykonaj następujący krok, jeśli chcesz skonfigurować aplikację w trybie inicjowanym przez sp: **SP**
W polu tekstowym **Adres URL logowania** wpisz adres URL, korzystając z następującego wzorca: `{YOUR BUSINESS APPLICATION URL}`
> [!NOTE]
> Ta wartość nie jest prawdziwa. Zastąp tę wartość rzeczywistym adresem URL logowania. Użyj konkretnego adresu URL logowania aplikacji biznesowej. Skontaktuj się z [zespołem obsługi klienta usługi SAP Cloud Platform Identity Authentication](https://cloudplatform.sap.com/capabilities/security/trustcenter.html), jeśli masz jakiekolwiek wątpliwości.
1. Aplikacja SAP Cloud Platform Identity Authentication oczekuje potwierdzeń SAML w określonym formacie, który wymaga dodania mapowań atrybutów niestandardowych do konfiguracji atrybutów tokenu SAML. Poniższy zrzut ekranu przedstawia listę atrybutów domyślnych.
1. Oprócz powyższej aplikacji SAP Cloud Platform Identity Authentication oczekuje kilku więcej atrybutów, które mają być przekazywane z powrotem w odpowiedzi SAML, które są pokazane poniżej. Te atrybuty są również wstępnie wypełnione, ale można je przejrzeć zgodnie z wymaganiami.
| Nazwa | Atrybut źródłowy|
| ---------------| --------------- |
| firstName | user.givenname |
8. Na stronie **Konfigurowanie logowania jednokrotnego za pomocą protokołu SAML** w sekcji **Certyfikat podpisywania SAML** kliknij link **Pobierz**, aby pobrać **kod XML metadanych** z podanych opcji zgodnie z wymaganiami i zapisać go na komputerze.
9. W sekcji **Konfigurowanie usługi SAP Cloud Platform Identity Authentication** skopiuj odpowiednie adresy URL zgodnie z wymaganiami.
a. Adres URL logowania
b. Identyfikator usługi Azure AD
d. Adres URL wylogowywania
### <a name="create-an-azure-ad-test-user"></a>Tworzenie użytkownika testowego usługi Azure AD
W tej sekcji utworzysz użytkownika testowego w witrynie Azure portal o nazwie B.Simon.
1. Z lewego okienka w witrynie Azure portal wybierz pozycję **Azure Active Directory**, wybierz pozycję **Użytkownicy**, a następnie wybierz pozycję **Wszyscy użytkownicy**.
1. Wybierz **pozycję Nowy użytkownik** u góry ekranu.
1. We właściwościach **Użytkownika** wykonaj następujące kroki:
1. W polu **Nazwa** wprowadź wartość `B.Simon`.
1. W polu **Nazwa użytkownika** [email protected]ź pole . Na przykład `[email protected]`.
1. Zaznacz pole wyboru **Pokaż hasło** i zanotuj wartość wyświetlaną w polu **Hasło**.
1. Kliknij przycisk **Utwórz**.
### <a name="assign-the-azure-ad-test-user"></a>Przypisywanie użytkownika testowego usługi Azure AD
W tej sekcji włączysz B.Simon do korzystania z logowania jednokrotnego platformy Azure, przyznając dostęp do uwierzytelniania tożsamości platformy sap cloud.
1. W portalu Azure wybierz pozycję **Aplikacje dla przedsiębiorstw**, a następnie wybierz pozycję **Wszystkie aplikacje**.
1. Na liście aplikacji wybierz pozycję **SAP Cloud Platform Identity Authentication**.
1. Na stronie przegląd aplikacji znajdź sekcję **Zarządzaj** i wybierz pozycję **Użytkownicy i grupy**.
1. Wybierz **pozycję Dodaj użytkownika**, a następnie wybierz pozycję **Użytkownicy i grupy** w oknie dialogowym Dodawanie **przydziału.**
1. W oknie dialogowym **Użytkownicy i grupy** wybierz pozycję **B.Simon** z listy Użytkownicy, a następnie kliknij przycisk **Wybierz** u dołu ekranu.
1. Jeśli oczekujesz dowolnej wartości roli w asercji SAML, w oknie dialogowym **Wybierz rolę** wybierz odpowiednią rolę dla użytkownika z listy, a następnie kliknij przycisk **Wybierz** u dołu ekranu.
1. W oknie dialogowym **Dodawanie przydziału** kliknij przycisk **Przypisz.**
## <a name="configure-sap-cloud-platform-identity-authentication-sso"></a>Konfigurowanie sytuowanego uwierzytelnienia tożsamości platformy SAP cloud
1. Aby umożliwić aplikacji skonfigurowanie logowania jednokrotnego, przejdź do konsoli administracyjnej usługi SAP Cloud Platform Identity Authentication. Adres URL odpowiada następującemu wzorcowi: `https://<tenant-id>.accounts.ondemand.com/admin`. Następnie zapoznaj się z tematem [Integration with Microsoft Azure AD (Integracja z usługą Microsoft Azure AD)](https://help.hana.ondemand.com/cloud_identity/frameset.htm?626b17331b4d4014b8790d3aea70b240.html) w dokumentacji usługi SAP Cloud Platform Identity Authentication.
2. W witrynie Azure Portal wybierz przycisk **Zapisz**.
3. Wykonuj dalsze czynności tylko, jeśli chcesz dodać i włączyć logowanie jednokrotne dla kolejnej aplikacji SAP. Powtórz kroki opisane w sekcji **Dodawanie usługi SAP Cloud Platform Identity Authentication z galerii**.
4. W witrynie Azure Portal na stronie integracji aplikacji **SAP Cloud Platform Identity Authentication**, wybierz pozycję **Połączone logowanie**.
5. Zapisz konfigurację.
> [!NOTE]
> Nowa aplikacja wykorzystuje konfigurację pojedynczego logowania poprzedniej aplikacji SAP. Upewnij się, że korzystasz z tych samych firmowych dostawców tożsamości w konsoli administracyjnej usługi SAP Cloud Platform Identity Authentication.
### <a name="create-sap-cloud-platform-identity-authentication-test-user"></a>Tworzenie użytkownika testowego usługi SAP Cloud Platform Identity Authentication
Nie musisz tworzyć użytkownika w usłudze SAP Cloud Platform Identity Authentication. Użytkownicy, którzy są w magazynie użytkowników usługi Azure AD, mogą korzystać z funkcji logowania jednokrotnego.
Usługa SAP Cloud Platform Identity Authentication obsługuje opcję federacji tożsamości. Ta opcja umożliwia aplikacji sprawdzenie, czy użytkownicy, którzy są uwierzytelniani przez firmowego dostawcę tożsamości, istnieją w magazynie użytkowników usługi SAP Cloud Platform Identity Authentication.
Opcja federacji tożsamości jest domyślnie wyłączona. Jeśli opcja federacji tożsamości jest włączona, tylko użytkownicy, którzy są zaimportowani w usłudze SAP Cloud Platform Identity Authentication, mogą uzyskać dostęp do aplikacji.
Abu uzyskać więcej informacji na temat włączania lub wyłączania funkcji federacji tożsamości w usłudze SAP Cloud Platform Identity Authentication, zobacz „Enable Identity Federation with SAP Cloud Platform Identity Authentication” („Włączanie funkcji federacji tożsamości w usłudze SAP Cloud Platform Identity Authentication”) w temacie [Configure Identity Federation with the User Store of SAP Cloud Platform Identity Authentication (Konfigurowanie funkcji federacji tożsamości z magazynem użytkowników w usłudze SAP Cloud Platform Identity Authentication)](https://help.hana.ondemand.com/cloud_identity/frameset.htm?c029bbbaefbf4350af15115396ba14e2.html).
## <a name="test-sso"></a>Test SSO
W tej sekcji przetestujesz konfigurację logowania jednokrotnego usługi Azure AD przy użyciu panelu dostępu.
Po kliknięciu kafelka SAP Cloud Platform Identity Authentication w panelu dostępu powinno nastąpić automatyczne zalogowanie do usługi SAP Cloud Platform Identity Authentication, dla której skonfigurowano logowanie jednokrotne. Aby uzyskać więcej informacji na temat Panelu dostępu, zobacz [Wprowadzenie do Panelu dostępu](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
## <a name="additional-resources"></a>Zasoby dodatkowe
- [Lista samouczków dotyczących integrowania aplikacji SaaS z usługą Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
- [Co to jest dostęp do aplikacji i logowanie jednokrotne z usługą Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/active-directory-appssoaccess-whatis)
- [Co to jest dostęp warunkowy w usłudze Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
- [Wypróbuj uwierzytelnianie tożsamości platformy SAP cloud w usłudze Azure AD](https://aad.portal.azure.com/)
- [Co to jest kontrola sesji w usłudze Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)
- [Jak chronić uwierzytelnianie tożsamości platformy SAP Cloud Platform za pomocą zaawansowanej widoczności i kontroli](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)
| 83.286996 | 657 | 0.811985 | pol_Latn | 0.999786 |
57ba1e7cb6aea6e2600afa99f325804b22372679 | 198 | md | Markdown | source/_assessments/21414.md | salihzeki12000/Website | 733c8f7ea86f6ee4967cbbbb83cfc10d12cf7c12 | [
"MIT"
] | null | null | null | source/_assessments/21414.md | salihzeki12000/Website | 733c8f7ea86f6ee4967cbbbb83cfc10d12cf7c12 | [
"MIT"
] | 10 | 2019-08-13T10:55:15.000Z | 2022-02-26T10:21:10.000Z | source/_assessments/21414.md | wing5wong/artisan-whs-static | cb36480c54adcb5cbe1fd25c1a741bb525112a72 | [
"MIT"
] | 1 | 2020-10-30T12:55:04.000Z | 2020-10-30T12:55:04.000Z | ---
title: '21414'
categories:
- SPX3
description: Plan and run a recreation activity
pdf: 'https://www.nzqa.govt.nz/nqfdocs/units/pdf/21414.pdf'
level: '3'
credits: '4'
assessment: Internal
---
| 16.5 | 59 | 0.707071 | yue_Hant | 0.234838 |
57ba74ee08db32da0c8dce5cbe781358ffe8dce6 | 1,799 | md | Markdown | AlchemyInsights/auditing-results-are-blank.md | isabella232/OfficeDocs-AlchemyInsights-pr.es-ES | ac116fbd9d1c1d91f8560a05b3bd9bf7ac60d13b | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T19:06:13.000Z | 2020-09-30T12:26:20.000Z | AlchemyInsights/auditing-results-are-blank.md | isabella232/OfficeDocs-AlchemyInsights-pr.es-ES | ac116fbd9d1c1d91f8560a05b3bd9bf7ac60d13b | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:58:54.000Z | 2022-02-09T06:59:11.000Z | AlchemyInsights/auditing-results-are-blank.md | isabella232/OfficeDocs-AlchemyInsights-pr.es-ES | ac116fbd9d1c1d91f8560a05b3bd9bf7ac60d13b | [
"CC-BY-4.0",
"MIT"
] | 4 | 2019-10-11T18:38:49.000Z | 2020-12-05T17:24:01.000Z | ---
title: Los resultados de auditoría están en blanco
ms.author: pebaum
author: bentoncity
manager: scotv
ms.date: 04/21/2020
ms.audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.collection: Adm_O365
ms.custom: ''
ms.assetid: 1437061a-a602-4853-b5fb-3cea7fd735ce
ms.openlocfilehash: d63158872c817ea6b856378367acc6f41f41e055
ms.sourcegitcommit: ab75f66355116e995b3cb5505465b31989339e28
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 08/13/2021
ms.locfileid: "58313859"
---
# <a name="auditing-results-are-blank"></a>Los resultados de auditoría están en blanco
**Informes de auditoría de sitios clásicos**
Para ver un informe de auditoría de una SharePoint de sitios, debe ser administrador de la colección de sitios. Para agregarse como administrador, vea [Manage site admins](https://docs.microsoft.com/sharepoint/manage-site-collection-administrators). Para obtener información sobre cómo trabajar con el registro de auditoría, consulta [Ver informes de registro de auditoría.](https://support.microsoft.com/office/view-audit-log-reports-b37c5869-1b47-4a82-a30d-ea20070fe527)
**Buscar en el registro de auditoría**
Debe ser un administrador global para trabajar con el registro de auditoría en el Centro de cumplimiento de Microsoft 365 en o en el <https://compliance.microsoft.com/auditlogsearch> portal Microsoft 365 Defender en <https://security.microsoft.com/auditlogsearch> . Antes de empezar, active el registro de auditoría. A continuación, puede ejecutar una búsqueda de registro de auditoría.
[Obtenga información sobre cómo buscar en el registro de auditoría](https://docs.microsoft.com/microsoft-365/compliance/search-the-audit-log-in-security-and-compliance#search-the-audit-log).
| 54.515152 | 472 | 0.808227 | spa_Latn | 0.840885 |
57bbf8fe661000a152ead9a195355745451eb93d | 77 | md | Markdown | README.md | Hacker719/SummerProgrammingWebsite | 88cedff0d054ec1394ef35e85cdcab6df1217f09 | [
"MIT"
] | 1 | 2020-12-30T09:48:23.000Z | 2020-12-30T09:48:23.000Z | README.md | neelr/DVPC | 88cedff0d054ec1394ef35e85cdcab6df1217f09 | [
"MIT"
] | null | null | null | README.md | neelr/DVPC | 88cedff0d054ec1394ef35e85cdcab6df1217f09 | [
"MIT"
] | null | null | null | # DVPC
A quick static website for a summer camp
## visit at https://dvpc.tk
| 15.4 | 40 | 0.714286 | eng_Latn | 0.493868 |
57bc13f81e11cb211f0e9d137226c6f35bf6daba | 795 | md | Markdown | src/iOS/Xamarin.iOS/Samples/Symbology/RenderUniqueValues/readme.md | jf990/arcgis-runtime-samples-dotnet | 15ec602fc64b09d1f63f5ac4ae4feeec59097334 | [
"Apache-2.0"
] | 2 | 2020-04-25T18:41:47.000Z | 2021-03-22T19:08:25.000Z | src/iOS/Xamarin.iOS/Samples/Symbology/RenderUniqueValues/readme.md | jf990/arcgis-runtime-samples-dotnet | 15ec602fc64b09d1f63f5ac4ae4feeec59097334 | [
"Apache-2.0"
] | null | null | null | src/iOS/Xamarin.iOS/Samples/Symbology/RenderUniqueValues/readme.md | jf990/arcgis-runtime-samples-dotnet | 15ec602fc64b09d1f63f5ac4ae4feeec59097334 | [
"Apache-2.0"
] | null | null | null | # Unique value renderer
Render features in a layer using a distinct symbol for each unique attribute value.
## How to use the sample
The map with the symbolized feature layer will be shown automatically when the sample loads.
## How it works
1. In this case, the field is subregions of the USA. While multiple fields can be used, this sample only uses one.
## Relevant API
* FeatureLayer
* ServiceFeatureTable
* SimpleFillSymbol
* SimpleLineSymbol
* UniqueValue
* UniqueValueRenderer
## About the data
The map shows U.S. states symbolized by subregion. Symbols are defined for *Pacific*, *Mountain*, and *West South Central* states. All other features are symbolized with the default symbol.
## Tags
Symbology, UniqueValueRenderer, draw, symbol
| 25.645161 | 189 | 0.777358 | eng_Latn | 0.99404 |
57bc3a7ceb76095e6b734ca2e7896429929b8d4d | 48 | md | Markdown | README.md | llllys/OV | 388aa2ab32123a869f4a110bebdfabc6b4c90c0c | [
"MIT"
] | null | null | null | README.md | llllys/OV | 388aa2ab32123a869f4a110bebdfabc6b4c90c0c | [
"MIT"
] | null | null | null | README.md | llllys/OV | 388aa2ab32123a869f4a110bebdfabc6b4c90c0c | [
"MIT"
] | null | null | null | # OV
online verification for Autonomous vehicle
| 16 | 42 | 0.833333 | eng_Latn | 0.96274 |
57bc86c60f521f28c7c59cd2f7003b63659fe260 | 1,253 | md | Markdown | _temp/2022-01-25-basicElement.md | 91ssalbap/91ssalbap.github.io | 4ff58e9e16ad0d7655729a385a141120f0be6348 | [
"MIT"
] | null | null | null | _temp/2022-01-25-basicElement.md | 91ssalbap/91ssalbap.github.io | 4ff58e9e16ad0d7655729a385a141120f0be6348 | [
"MIT"
] | null | null | null | _temp/2022-01-25-basicElement.md | 91ssalbap/91ssalbap.github.io | 4ff58e9e16ad0d7655729a385a141120f0be6348 | [
"MIT"
] | null | null | null | ---
layout: single
title: HTML - 필수 엘리먼트
categories: tech.frontend
tags: html
---
## 필수 엘리먼트
### 들어가기 전에 '< !DOCTYPE html >'
- DTD(Document Type Definition)은 문서 형식을 정의하는 것을 말합니다. 컴퓨터 용어로 SGML 계열의 마크업 언어에서 사용합니다.
- '< !DOCTYPE html >'은 해당 문서가 html이라고 브라우저에 알려주는 DTD입니다. '< !DOCTYPE html >'은 html5 형식을 정의하는 방법입니다. 각 문서 형식마다 다른 방식을 가지고 있습니다.
### 필수 엘리먼트
```html
<!DOCTYPE html>
<html>
<head>
<title>title</title>
</head>
<body>
...
</body>
</html>
```
- 위의 예시는 이전 포스트에서 기본 엘리먼트의 예시로 들었던 것과 같습니다. 위에 선언된 엘리먼트들은 모든 html 문서들이 꼭 포함해야 하는 엘리먼트들 입니다.
### html 엘리먼트
- '< html >' 태그로 선언되는 html 엘리먼트는 html 문서의 root element를 정의합니다.
- html엘리먼트는 DOCTYPE 선언을 제외한 모든 엘리먼트를 포함하는 최상위의 엘리먼트 입니다. DOCTYPE과 함께 브라우저가 해당 문서가 html 문서임을 알 수 있도록 합니다.
- 'xmlns' 속성을 가집니다. 'xmlns'는 해당 문서를 위한 XML 네임스페이스를 명시하며 선언하지 않으면 기본 값으로 'http://www.w3.org/1999/xhtml'을 가집니다.
### head 엘리먼트
- '< head >' 태그로 선언되는 head 엘리먼트는 해당 문서에 대한 메타데이터들을 포함하기 위한 엘리먼트입니다.
- 여기에서 메타데이터는 해당 html 문서에 대한 포괄적인 정보를 의미합니다. 브라우저가 문서를 구성할 때 참조하기 위해 사용하며 웹브라우저에 직접적으로 표현되지는 않습니다.
- title, style, meta, link, script, base 등의 엘리먼트들이 내부에 선언됩니다.
### title 엘리먼트
### body 엘리먼트
- '< body >' 태그로 선언되는 body 엘리먼트는 해당 html 문서의 내용들을 포함하기위한 엘리먼트입니다. 하나의 html 문서에 하나의 body 엘리먼트만 존재할 수 있습니다. | 30.560976 | 126 | 0.667199 | kor_Hang | 1.00001 |
c047037fbd13e040cdf561a46aba4a7e2fa15649 | 6,724 | md | Markdown | _posts/mountaineering/2021-06-02-yam-week9.md | gpiks/gpiks.github.io | 76fa717e9e94faae445ee1b94271f2163f6e6561 | [
"MIT"
] | null | null | null | _posts/mountaineering/2021-06-02-yam-week9.md | gpiks/gpiks.github.io | 76fa717e9e94faae445ee1b94271f2163f6e6561 | [
"MIT"
] | 1 | 2020-03-13T13:21:32.000Z | 2020-03-13T13:21:32.000Z | _posts/mountaineering/2021-06-02-yam-week9.md | gpiks/gpiks.github.io | 76fa717e9e94faae445ee1b94271f2163f6e6561 | [
"MIT"
] | null | null | null | ---
layout: post
title: "Mountain Expedtion!"
date: 2021-06-02
categories: mountaineering
---
Hello friends!
It's been a hectic few weeks with planning our final mountain expedition and wrapping up the course and figuring what I am up to next! This letter is also long overdue and the procrastination has been a function of the finality of this newsletter, marking an end to this adventure.
But I am feeling both happy and thankful to have completed the course, met some amazing guides and made some lifelong friends. At the same time I feel a sense of loss - our crew will probably never be together again and very quickly the good times that we had over the last few months have become memories to cherish. However, this is not goodbye - we will be climbing again in the future. In some sense this is just the beginning.
Our mountain exped planning was off to a pretty rocky start with a lot of uncertainty since the weather was not extremely cooperative with us. After months of coddling us, the weather gods finally relented and the forecast showed some poor weather for most of the trip. We also had some people (me included) who did not want to ski which meant that we had to think outside the box. The course itself had a little budget left over which was going to be returned but instead we added an extra guide to our trip so that we could do some more climbing and alpine travel.
We went back to the Honeymoon Lake campground near Jasper. This was the same campground we used for our previous alpine trip. It is quite the luxurious campground compared to our other trips.
Back at scenic Honeymoon Lake campground
On our way to Honeymoon on the first day, we stopped at a climbing crag called little Russia that allowed us to squeeze in a little more climbing into the trip. It is a great climbing location which is under active development! Sadly no pictures of the place :(
After we arrived at Honeymoon, we had to start planning for the next day. Everyone was attempting to climb Mt Athabasca (3,491m or 11,450 ft) via different routes. I was with the group that would ascend via the AA (Andromeda & Athabasca) col route. It is a relatively non technical route requiring no actual rock or ice climbing, but requires us to navigate glaciers and climb steep snow slopes - still quite challenging. The other groups were using the extra guides that day to attempt the peak via more technical routes.
The AA Col route to the summit - the route our group took.
Grant, our lead guide, opened our planning meeting with our leaving camp time - he said we should be out of camp by 2.30. But then he paused and said he made a mistake and we all assumed he meant something later but no! Our goal was to be out of camp at 1.30 am which meant a wake up time of 12.30 am…
Pitch black, eating breakfast and drinking coffee at 1 am
Well we woke up at 12.30 and ate ‘breakfast’ in pitch darkness which felt weird for sure but we were soon on our way. The rain and snow started coming down shortly after cooling the already subzero morning further. We started our journey up the trail and onto the glacier in constant rain which eventually became tiny hail particles. The wind was absolutely howling as well and we had to make sure that most if not all the skin was covered because the wind would blast the hail pellets onto your face and hands and it felt like we were being sand papered with a vengeance. It was quite an epic journey getting through the col and the summit ridge where at moments I thought we would need to turn back but, I am glad that Grant kept asking us to push forward. It took us about 7, mostly painful, hours to the summit where there was no view because of the wind, snow and clouds. After spending maybe 3 minutes on the summit we quickly started descending. As we were descending the weather showed some signs of clearing up and by the time we got back to the car 5 hours later, the weather had significantly improved (no rain but still windy) and when we got back to camp it had cleared up to a fantastic blue bird sky day so we got to enjoy the fruits of our labor in comfort and warmth!
Our next day was ice climbing! Our plan was to visit Two O’Clock falls which has frozen substantially larger than usual this year and stayed in condition to climb much longer than it usually does. This meant that we had a chance to lead on ice for the first time! We had a relatively leisurely wake up time (4 am) to get to the falls early and climb it before the sun came out and made the climbing more challenging because of the melt. It was a type 1 fun kind of day and I thoroughly enjoyed the climbing!
Rare picture of me climbing, taken by our guide Shaun - I got my first ice climbing lead in on some WI3 ice. It was exhilarating!
It was pretty wild how the ice stayed in condition till the end of May
The last day was dedicated to some cruisy rock climbing - an easy 5.7 climb up a slabby route called Free Diver in Jasper. Slabby generally means that the route has not many places to hold with your hands and you need to trust little scoops in the rock with your feet to push up. It can feel quite unnerving at times but once you get the hang of it, it can be fairly easy to run up such routes. I had a blast and got the climbing systems dialed by the end of it!
Medicine lake from up high - this picture was taken from nearly the top of the 11 pitches (around 250m) of climbing on a beautiful day.
Long way down: objects in the picture are further than they appear! Ben and Shaun (guide) getting ready to climb after I just led a pitch of climbing.
We spent half of the last day at Lake Louise doing some easy trad climbing before heading back to Canmore to wrap up. I also saw my first grizzly bear!
Luckily we were all in the van!
An expedition worthy of wrapping up an epic 3 months! It has been quite the wild ride. There have been plenty of challenging moments which ended up being the most valuable learning opportunities. I will miss being part of this course but I am really excited to apply all the skills going forward.
I hope you all enjoyed reading and following along! Thanks for the support and I hope to see everyone soon!
Cheers,
— G
| 61.127273 | 1,284 | 0.77558 | eng_Latn | 0.999949 |
c04896af55c76b9dc57a7477c37bbcf24361f4ed | 19,540 | md | Markdown | Samples/image-sequencer/Details.md | UNIVERSAL-IT-SYSTEMS/Lumia-imaging-sdk | d8046c73f2c6988204a96405b96582cf837bb9a6 | [
"MIT"
] | 64 | 2015-09-21T09:54:53.000Z | 2018-11-04T04:32:11.000Z | Samples/image-sequencer/Details.md | LanceMcCarthy/Lumia-imaging-sdk | d8046c73f2c6988204a96405b96582cf837bb9a6 | [
"MIT"
] | 20 | 2015-09-23T05:07:04.000Z | 2019-05-05T18:34:34.000Z | Samples/image-sequencer/Details.md | LanceMcCarthy/Lumia-imaging-sdk | d8046c73f2c6988204a96405b96582cf837bb9a6 | [
"MIT"
] | 33 | 2015-09-29T21:30:17.000Z | 2018-09-24T22:34:27.000Z | ## Architecture overview
The application consists of six views:
- Most of the application functionality is in the **SequencePreviewPage** class. It displays the animation preview and also handles the image stabilization using the Lumia Imaging SDK **ImageAligner**. To export the previewed animation to the GIF file, it utilizes GifExporter, which in turn uses **GifEncoder** from the Lumia Imaging SDK.
- **SequencesPage** is the opening view of the application in which example image sequences and saved GIF files are displayed.
- **GifPage** displays a saved GIF animation.
- **AboutPage** contains the application description and version info and is available in the menu of each view.
- **SequenceCapturePage** and **VideoPreviewPage** both implement the sequence capture functionality. **SequenceCapturePage** uses the **LowLagPhotoSequenceCapture** of the WinRT MediaCapture API, while **VideoPreviewCapturePage** is a fallback solution for devices where sequence capture is not supported by the camera hardware. It implements the sequence capture by capturing video preview images in short intervals.
## Preview page
**Initialization and image stabilization**
The animation preview is implemented in the **SequencePreviewPage** class. When the **SequencePreviewPage OnNavigatedTo** method gets called, it receives a list of image StorageFiles as a parameter. In the case of the example sequence, an identifier is received. The ID is a file name suffix for the image resource files stored in the project Assets/Sequences directory. The file name syntax is sequence.[id].[sequence index].jpg. A list of StorageFileImageSources is then created out of the provided files so they can be used by the Lumia Imaging SDK APIs.
The list of StorageFileImageSources gets passed to the **PrepareImageSequence** method. The **PrepareImageSequence** method prepares the image sequence playback by creating an aligned copy of the image sequence by using the Image Aligner API. The application can then display either unaligned or aligned bitmaps in real time by rendering images from either the list of unaligned image providers, or the list of aligned image providers.
C#
```
public async Task PrepareImageSequence(List<IImageProvider> imageProviders)
{
_unalignedImageProviders = imageProviders;
_onScreenImageProviders = _unalignedImageProviders;
// ...
using (ImageAligner imageAligner = new ImageAligner())
{
imageAligner.Sources = _unalignedImageProviders;
imageAligner.ReferenceSource = _unalignedImageProviders[0];
try
{
_alignedImageProviders = await imageAligner.AlignAsync();
// ...
}
catch (Exception e)
{
// If align fails, fail silently but don't enable the align button on UI.
}
};
}
```
### Animation
**DispatcherTimer** is used for timing the animation. The timer is created in the **SequencePreviewPage** constructor and is controlled in **Play** and **Stop** methods. When the timer is running, it calls the **AnimationTimer\_Tick** method at 100 millisecond intervals. The **AnimationTimer\_Tick** method calls the **Render** method to render the current frame and advances the index of the displayed frame, wrapping it when necessary.
C#
```
private void AnimationTimer_Tick(object sender, EventArgs eventArgs)
{
Render(_animationIndex);
if (_animationIndex == (_onScreenImageProviders.Count() - 1))
{
_animationIndex = 0;
}
else
{
_animationIndex++;
}
}
```
In the **Render** method, the **IImageProvider** is rendered to the on-screen bitmap.
C#
```
private void Render(IReadOnlyList<IImageProvider> imageProviders, int animationIndex, bool renderBackground = false)
{
if (_renderTask == null || _renderTask.IsCompleted)
{
_renderTask = DoRender(imageProviders, animationIndex, renderBackground);
}
}
private async Task DoRender(IReadOnlyList<IImageProvider> imageProviders, int animationIndex, bool renderBackground = false)
{
if (_onScreenImageProviders[animationIndex] != null)
{
int imageWidth = imageProviders == _unalignedImageProviders ? _unalignedImageWidth : _alignedImageWidth;
int imageHeight = imageProviders == _unalignedImageProviders ? _unalignedImageHeight : _alignedImageHeight;
if (_foregroundBitmap == null || _foregroundBitmap.PixelWidth != imageWidth || _foregroundBitmap.PixelHeight != imageHeight)
_foregroundBitmap = new WriteableBitmap(imageWidth, imageHeight);
using (WriteableBitmapRenderer writeableBitmapRenderer = new WriteableBitmapRenderer(imageProviders[animationIndex], _foregroundBitmap))
{
_foregroundBitmap = await writeableBitmapRenderer.RenderAsync();
}
if (renderBackground)
{
if (_backgroundBitmap == null || _backgroundBitmap.PixelWidth != imageWidth || _backgroundBitmap.PixelHeight != imageHeight)
_backgroundBitmap = new WriteableBitmap(imageWidth, imageHeight);
using (WriteableBitmapRenderer writeableBitmapRenderer = new WriteableBitmapRenderer(imageProviders[0], _backgroundBitmap))
{
_backgroundBitmap = await writeableBitmapRenderer.RenderAsync();
}
}
await CoreApplication.MainView.CoreWindow.Dispatcher.RunAsync(CoreDispatcherPriority.Normal,
() =>
{
_foregroundBitmap.Invalidate();
ImageElement.Source = _foregroundBitmap;
if (renderBackground)
{
_backgroundBitmap.Invalidate();
ImageElementBackground.Source = _backgroundBitmap;
}
});
}
}
```
### Setting the animation boundaries
The animated area selection works by having the animation in two layers: background and foreground. In the preview page, this works by having two overlapping Image elements, **ImageElementBackground** and **ImageElement**. **ImageElementBackground** displays the first frame of the sequence. **ImageElement** displays the current frame, cropped to the selected area by using the Clip property of **ImageElement**. During animation playback, only **ImageElement** is refreshed.
The user can adjust the cropped area by dragging the canvas. The drag events are handled in the **ImageElement\_ManipulationDelta** method. The animated area is indicated by drawing a white rectangle on top of the image elements.
## Exporting animated GIF files
When user taps the save icon, the previewed animation is exported as an animated GIF file. The GIF export happens in the **GifExporter** class. It takes a list of IImageProviders as parameter, as well as an optional Rect representing the animated area.
The file is saved to the Pictures library. This requires the Pictures library capability to be set in the package manifest. The saved files are available for viewing and sharing in the Photos app, though the Photos image viewer does not play back the animation. The saved files are also accessible through the device file system. Note that you cannot use the MediaLibrary API to store the GIF files to the camera roll because it converts the GIF files to still JPEG images.
C#
```
public static async Task Export(IReadOnlyList<IImageProvider> images, Rect? animatedArea)
{
// The list of aligned images may contain Null items if some images couldn't be aligned.
List<IImageProvider> sanitizedImages = new List<IImageProvider>();
foreach (IImageProvider image in images) {
if (image != null) {
sanitizedImages.Add(image);
}
}
ImageProviderInfo info = await sanitizedImages[0].GetInfoAsync();
int w = (int)info.ImageSize.Width;
int h = (int)info.ImageSize.Height;
IReadOnlyList<IImageProvider> gifRendererSources;
if (animatedArea.HasValue)
{
// Ensure the animated area dimensions are smaller than the image dimensions.
double rectW = animatedArea.Value.Width;
double rectH = animatedArea.Value.Height;
if ((animatedArea.Value.Width + animatedArea.Value.Left) >= w)
{
rectW = w - animatedArea.Value.Left - 1;
}
if ((animatedArea.Value.Top + animatedArea.Value.Height) >= h)
{
rectH = h - animatedArea.Value.Top - 1;
}
Rect rect = new Rect(animatedArea.Value.Left, animatedArea.Value.Top, rectW, rectH);
gifRendererSources = CreateFramedAnimation(sanitizedImages, rect, w, h);
}
else {
gifRendererSources = sanitizedImages;
}
using (GifRenderer gifRenderer = new GifRenderer())
{
gifRenderer.Duration = 100;
gifRenderer.NumberOfAnimationLoops = 10000;
gifRenderer.Sources = gifRendererSources;
var buffer = await gifRenderer.RenderAsync();
var filename = "Sequence" + (await GetFileNameRunningNumber()) + ".gif";
var storageFile = await KnownFolders.SavedPictures.CreateFileAsync(filename, CreationCollisionOption.ReplaceExisting);
using (var stream = await storageFile.OpenAsync(FileAccessMode.ReadWrite))
{
await stream.WriteAsync(buffer);
}
}
}
```
If the animated area is defined, **GifExporter** creates a new list of IImageProviders that contain images in which only the animated area changes. This is implemented by using **CropFilter** to crop the animated area, and then using **BlendFilter** to blend it on top of the static background.
C#
```
private static IReadOnlyList<IImageProvider> CreateFramedAnimation(IReadOnlyList<IImageProvider> images, Rect animationBounds, int w, int h)
{
List<IImageProvider> framedAnimation = new List<IImageProvider>();
foreach (IImageProvider frame in images)
{
FilterEffect cropFilterEffect = new FilterEffect(frame);
cropFilterEffect.Filters = new List<IFilter>() { new CropFilter(animationBounds) };
FilterEffect blendFilterEffect = new FilterEffect(images[0]);
BlendFilter blendFilter = new BlendFilter();
blendFilter.ForegroundSource = cropFilterEffect;
blendFilter.Level = 1.0;
blendFilter.BlendFunction = BlendFunction.Normal;
blendFilter.TargetArea = new Rect(
animationBounds.Left / w,
animationBounds.Top / h,
animationBounds.Width / w,
animationBounds.Height / h
);
blendFilterEffect.Filters = new List<IFilter>() { blendFilter };
framedAnimation.Add(blendFilterEffect);
}
return framedAnimation;
}
```
## Capturing image sequences
### Initialization
Sequence capture is implemented in the **SequenceCapturePage** class. A **MediaCapture** object for controlling the phone back camera is initialized in the **InitializeMediaCapture** method, called in the **OnNavigatedTo** method of the page.
C#
```
// ...
_mediaCapture = new MediaCapture();
var devices = await DeviceInformation.FindAllAsync(DeviceClass.VideoCapture);
var backCamera = devices.FirstOrDefault(x => x.EnclosureLocation != null && x.EnclosureLocation.Panel == Windows.Devices.Enumeration.Panel.Back);
await _mediaCapture.InitializeAsync(new MediaCaptureInitializationSettings
{
StreamingCaptureMode = StreamingCaptureMode.Video,
PhotoCaptureSource = PhotoCaptureSource.Auto,
AudioDeviceId = string.Empty,
VideoDeviceId = backCamera.Id
});
// ...
```
The **SequenceCapturePage** XAML tree contains a **CaptureElement** that is used to display the camera viewfinder image, so you must set the previously initialized **MediaCapture** object as the source of **CaptureElement**, and start the preview:
C#
```
// ...
captureElement.Source = _mediaCapture;
await _mediaCapture.StartPreviewAsync();
// ...
```
The **MediaCapture.PrepareLowLagPhotoSequenceCaptureAsync** method is then used to initialize the photo sequence capture. It returns a **LowLagPhotoSequenceCapture** object, which can be used to control the sequence capture.
C#
```
// ...
var format = ImageEncodingProperties.CreateJpeg();
format.Width = 640;
format.Height = 480;
_variablePhotoSequenceCapture = await _mediaCapture.PrepareLowLagPhotoSequenceCaptureAsync(format);
// ...
```
A handler is added for the PhotoCaptured event that is triggered on each captured image. Whenever a shot is taken, it's saved to a temporary folder to be used later. In Image Sequencer, the number of captured images is limited to 20 due to memory usage concerns on low-end devices.
C#
```
// ...
_variablePhotoSequenceCapture.PhotoCaptured += OnPhotoCaptured;
// ...
public void OnPhotoCaptured(LowLagPhotoSequenceCapture s, PhotoCapturedEventArgs e)
{
if (_fileIndex < AMOUNT_OF_FRAMES_IN_SEQUENCE)
{
if (_saveTask == null)
{
_saveTask = Save(e.Frame, _fileIndex++);
}
else
{
_saveTask = _saveTask.ContinueWith(t => Save(e.Frame, _fileIndex++));
}
}
else
{
StopSequenceCapture();
}
}
private async Task Save(IRandomAccessStream frame, int i) {
var filename = "ImageSequencer." + i + ".jpg";
var folder = Windows.Storage.ApplicationData.Current.TemporaryFolder;
var storageFile = await folder.CreateFileAsync(filename, CreationCollisionOption.ReplaceExisting);
var stream = await storageFile.OpenAsync(FileAccessMode.ReadWrite);
await RandomAccessStream.CopyAndCloseAsync(frame, stream);
_files.Add(storageFile);
}
```
The photo sequence capture can be started and stopped using the **StartAsync** and **StopAsync** methods of **LowLagPhotoSequenceCapture**. Use **FinishAsync** to release the resources used by the photo sequence operation. These methods are used in the event handlers of the hardware camera button and the on-screen capture button.
### Using video preview images for capturing image sequences
Not all devices support photo sequence capture. You can use the **MediaCapture.VideoDeviceController.LowLagPhotoSequence.Supported** property to verify whether sequence capture is supported by the device running your application. For unsupported devices, you can implement a fall-back by using video preview to capture sequences of images. This can be done easily using **CameraPreviewImageSource** in the Lumia Imaging SDK.
The **CameraPreviewImageSource** is initialized similarly to the **LowLagPhotoSequenceCapture**:
C#
```
public async void InitializeAsync()
{
// Create a camera preview image source (from Imaging SDK).
_cameraPreviewImageSource = new CameraPreviewImageSource();
await _cameraPreviewImageSource.InitializeAsync(string.Empty);
var properties = await _cameraPreviewImageSource.StartPreviewAsync();
// Create a preview bitmap with the correct aspect ratio.
var width = 640.0;
var height = (width / properties.Width) * properties.Height;
_writeableBitmap = new WriteableBitmap((int)width, (int)height);
captureElement.Source = _writeableBitmap;
_writeableBitmapRenderer = new WriteableBitmapRenderer();
_jpegRenderer = new JpegRenderer();
// Attach preview frame delegate.
_cameraPreviewImageSource.PreviewFrameAvailable += OnPreviewFrameAvailable;
}
```
Instead of using **CaptureElement** to display the viewfinder, a regular image control is used to display the images provided by the **CameraPreviewImageSource**. If sequence capture is ongoing, the image is saved to JPG file using the Lumia Imaging SDK **JpegRenderer**.
C#
```
private void OnPreviewFrameAvailable(IImageSize args)
{
_renderTask = Render();
}
private async Task Render()
{
if (!_rendering && !_stop)
{
_rendering = true;
// Render the camera preview frame to the screen.
_writeableBitmapRenderer.Source = _cameraPreviewImageSource;
_writeableBitmapRenderer.WriteableBitmap = _writeableBitmap;
await _writeableBitmapRenderer.RenderAsync();
await Windows.ApplicationModel.Core.CoreApplication.MainView.CoreWindow.Dispatcher.RunAsync(
CoreDispatcherPriority.High, () =>
{
_writeableBitmap.Invalidate();
});
// Write the camera preview frame to a file if capturing.
if (_capturing)
{
if (_sequenceIndex < 20)
{
_jpegRenderer.Source = _cameraPreviewImageSource;
IBuffer jpg = await _jpegRenderer.RenderAsync();
await Save(jpg, _sequenceIndex++);
}
else
{
StartStopCapture();
}
}
_rendering = false;
}
if (_stop)
{
_capturing = false;
_cameraPreviewImageSource.Dispose();
_writeableBitmapRenderer.Dispose();
_jpegRenderer.Dispose();
}
}
```
## Viewing animated GIF files
No standard XAML control exists for displaying animated GIFs, so you have to to decode the GIF frames manually by using BitmapDecoder. This is done in the **GifPage** class.
**BitmapDecoder** provides us access to the animation frames in a GIF file. The GIFs generated by the Lumia Imaging SDK uses partial GIF encoding, meaning that the animation frames contain only pixels different from the corresponding pixels in the first frame. Hence, in addition to decoding the frames, you must overlay each frame on top of the first frame to complete the image. This is done by examining the RGBA values of the pixels. If the value of the alpha channel is zero, you must replace the pixel using the corresponding pixel in the first frame.
**Note**: The overlay procedure is not needed for animated GIFs not using partial encoding.
C#
```
private async Task LoadImage(String filename)
{
var storageFile = await KnownFolders.SavedPictures.GetFileAsync(filename);
using (var res = await storageFile.OpenAsync(FileAccessMode.Read))
{
var bitmapDecoder = await BitmapDecoder.CreateAsync(BitmapDecoder.GifDecoderId, res);
byte[] firstFrame = null;
for (uint frameIndex = 0; frameIndex < bitmapDecoder.FrameCount; frameIndex++)
{
var frame = await bitmapDecoder.GetFrameAsync(frameIndex);
var writeableBitmap = new WriteableBitmap((int)bitmapDecoder.OrientedPixelWidth, (int)bitmapDecoder.OrientedPixelHeight);
var pixelData = await frame.GetPixelDataAsync(
BitmapPixelFormat.Bgra8,
BitmapAlphaMode.Straight,
new BitmapTransform(),
ExifOrientationMode.RespectExifOrientation,
ColorManagementMode.DoNotColorManage);
var bytes = pixelData.DetachPixelData();
if (firstFrame == null)
{
firstFrame = bytes;
}
else
{
// Blend the frame on top of the first frame.
for (uint i = 0; i < bytes.Count(); i += 4)
{
int alpha = bytes[i + 3];
if (alpha == 0 && firstFrame != null)
{
Array.Copy(firstFrame, i, bytes, i, 4);
}
}
}
using (var stream = writeableBitmap.PixelBuffer.AsStream())
{
stream.Write(bytes, 0, bytes.Length);
}
_frames.Add(writeableBitmap);
}
}
StartAnimation();
}
```
| 44.108352 | 557 | 0.703941 | eng_Latn | 0.772623 |
c0495fae5ed77344e191b7711e00020b4c04c55f | 1,552 | md | Markdown | results/crinacle/harman_in-ear_2019v2/Custom Art Pro330v2/README.md | vinzmc/AutoEq | 4b42aa25e5f4933528be44e7356afe1fde75a3af | [
"MIT"
] | 6,741 | 2018-07-27T10:54:04.000Z | 2022-03-31T20:22:57.000Z | results/crinacle/harman_in-ear_2019v2/Custom Art Pro330v2/README.md | davidvandamage/AutoEq | e6b1648ea09ae3eade14f92c6f9d5afd87e400ac | [
"MIT"
] | 428 | 2018-08-08T17:12:40.000Z | 2022-03-31T05:53:36.000Z | results/crinacle/harman_in-ear_2019v2/Custom Art Pro330v2/README.md | davidvandamage/AutoEq | e6b1648ea09ae3eade14f92c6f9d5afd87e400ac | [
"MIT"
] | 1,767 | 2018-07-27T16:50:12.000Z | 2022-03-31T19:26:39.000Z | # Custom Art Pro330v2
See [usage instructions](https://github.com/jaakkopasanen/AutoEq#usage) for more options and info.
### Parametric EQs
In case of using parametric equalizer, apply preamp of **-6.4dB** and build filters manually
with these parameters. The first 5 filters can be used independently.
When using independent subset of filters, apply preamp of **-6.4 dB**.
| Type | Fc | Q | Gain |
|:--------|:---------|:-----|:--------|
| Peaking | 16 Hz | 0.48 | 3.5 dB |
| Peaking | 314 Hz | 0.39 | -6.7 dB |
| Peaking | 1696 Hz | 0.33 | 3.9 dB |
| Peaking | 8212 Hz | 0.58 | 3.7 dB |
| Peaking | 19109 Hz | 0.25 | 5.8 dB |
| Peaking | 1266 Hz | 1.97 | 1.1 dB |
| Peaking | 1736 Hz | 3.69 | -4.8 dB |
| Peaking | 2460 Hz | 1.78 | 3.1 dB |
| Peaking | 3439 Hz | 2.89 | -0.6 dB |
| Peaking | 3471 Hz | 3.53 | -1.9 dB |
### Fixed Band EQs
In case of using fixed band (also called graphic) equalizer, apply preamp of **-9.2dB**
(if available) and set gains manually with these parameters.
| Type | Fc | Q | Gain |
|:--------|:---------|:-----|:--------|
| Peaking | 31 Hz | 1.41 | 2.9 dB |
| Peaking | 62 Hz | 1.41 | -0.5 dB |
| Peaking | 125 Hz | 1.41 | -2.8 dB |
| Peaking | 250 Hz | 1.41 | -5.1 dB |
| Peaking | 500 Hz | 1.41 | -4.1 dB |
| Peaking | 1000 Hz | 1.41 | 1.6 dB |
| Peaking | 2000 Hz | 1.41 | 2.7 dB |
| Peaking | 4000 Hz | 1.41 | 3.4 dB |
| Peaking | 8000 Hz | 1.41 | 6.4 dB |
| Peaking | 16000 Hz | 1.41 | 8.6 dB |
### Graphs
 | 38.8 | 98 | 0.554124 | eng_Latn | 0.748498 |
c0497529e40931cd0715c9ec31e5022aeea97d3a | 6,237 | md | Markdown | msteams-platform/tabs/quickstarts/create-personal-tab-node-yeoman.md | isabella232/msteams-docs.pt-BR | de4d2abe7ca8135fb75cfb65c664978ba825da70 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | msteams-platform/tabs/quickstarts/create-personal-tab-node-yeoman.md | isabella232/msteams-docs.pt-BR | de4d2abe7ca8135fb75cfb65c664978ba825da70 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-02-23T19:28:18.000Z | 2021-02-23T19:28:18.000Z | msteams-platform/tabs/quickstarts/create-personal-tab-node-yeoman.md | isabella232/msteams-docs.pt-BR | de4d2abe7ca8135fb75cfb65c664978ba825da70 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Início rápido: criar uma guia pessoal personalizada com Node.js e o gerador Yeoman para o Microsoft Teams'
author: laujan
description: Um guia de início rápido para criar uma guia pessoal com o gerador Yeoman para o Microsoft Teams.
ms.topic: quickstart
ms.author: lajanuar
ms.openlocfilehash: e39878d117b0b1b1f8c0e2450021d9238f5b7877
ms.sourcegitcommit: e8dfcb167274e996395b77d65999991a18f2051a
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 09/15/2020
ms.locfileid: "47818882"
---
# <a name="quickstart-create-a-custom-personal-tab-with-nodejs-and-the-yeoman-generator-for-microsoft-teams"></a>Início rápido: criar uma guia pessoal personalizada com Node.js e o gerador Yeoman para o Microsoft Teams
>[!NOTE]
>Este QuickStart segue as etapas descritas no [Build Your First Microsoft Teams app](https://github.com/OfficeDev/generator-teams/wiki/Build-Your-First-Microsoft-Teams-App) wiki encontrado no repositório do GitHub do Microsoft OfficeDev.
Neste QuickStart, veremos como criar uma guia pessoal personalizada usando o [gerador Yeoman do teams](https://github.com/OfficeDev/generator-teams/wiki/Build-Your-First-Microsoft-Teams-App). Também carregaremos o aplicativo para a equipe.
[!INCLUDE [node-js-yeoman-prereq](~/includes/tabs/node-js-yeoman-prereq.md)]
**Você deseja criar uma guia configurável ou estática?**
Use as teclas de seta para selecionar a guia estático.
>[!IMPORTANT]
>O componente de caminho *yourDefaultTabNameTab*, referenciado neste QuickStart, é o valor que você inseriu no gerador para o *nome de guia padrão* mais a *guia*Word.
>
>Por exemplo: DefaultTabName: *MyTab* => */MyTabTab/*
## <a name="create-your-personal-tab"></a>Criar sua guia pessoal
Para adicionar uma guia pessoal a este aplicativo, você criará uma página de conteúdo e atualizará os arquivos existentes:
- No editor de códigos, crie um novo arquivo HTML, **personal.html** e adicione a marcação a seguir:
```html
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>
<!-- Todo: add your a title here -->
</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<!-- inject:css -->
<!-- endinject -->
</head>
<body>
<h1>Personal Tab</h1>
<p><img src="/assets/icon.png"></p>
<p>This is your personal tab!</p>
</body>
</html>
```
- Salve **personal.html** na pasta **da Web** do seu aplicativo:
```bash
./src/app/web/<yourDefaultTabNameTab>/personal.html
```
- Abra o **manifest.jsno** editor de código:
```bash
./src/manifest/manifest.json/
```
Adicione o seguinte à matriz vazia `staticTabs` ( `staticTabs":[]` ) e adicione o seguinte objeto JSON:
```json
{
"entityId": "personalTab",
"name": "Personal Tab ",
"contentUrl": "https://{{HOSTNAME}}/<yourDefaultTabNameTab>/personal.html",
"websiteUrl": "https://{{HOSTNAME}}",
"scopes": ["personal"]
}
```
Lembre-se de atualizar o componente de caminho **"contentURL"** **yourDefaultTabNameTab** com seu nome de guia real.
- Salve o **manifest.jsatualizado em**.
- A página de conteúdo deve ser fornecida em um IFrame. Abra **Tab. TS** no editor de código:
```bash
./src/app/<yourDefaultTabNameTab>/<yourDefaultTabNameTab>.ts
```
- Adicione o seguinte à lista de decoradores de IFrame:
```typescript
@PreventIframe("/<yourDefaultAppName>TabNameTab>/personal.html")
```
- Certifique-se de salvar o arquivo **Tab atualizado. TS** . O código da guia está completo.
## <a name="build-and-run-your-application"></a>Criar e executar o aplicativo
Abra um prompt de comando no diretório do projeto para concluir as próximas tarefas.
[!INCLUDE [node-js-yeoman-gulp-tasks](~/includes/tabs/node-js-yeoman-gulp-tasks.md)]
Para exibir sua guia pessoal, vá para `http://localhost:3007/<yourDefaultAppNameTab>/personal.html`
>
## <a name="establish-a-secure-tunnel-to-your-tab"></a>Estabelecer um túnel seguro para sua guia
O Microsoft Teams é um produto totalmente baseado em nuvem e exige que o conteúdo da guia esteja disponível na nuvem usando pontos de extremidade HTTPS. O Microsoft Teams não permite hospedagem local, portanto, você precisa publicar sua guia em uma URL pública ou usar um proxy que exporá sua porta local para uma URL voltada para a Internet.
Para testar sua extensão de guia, você usará o [ngrok](https://ngrok.com/docs), que é integrado a esse aplicativo. O Ngrok é uma ferramenta de software de proxy reverso que criará um túnel para os pontos de extremidade HTTPS publicamente disponíveis do servidor Web em execução localmente. Os pontos de extremidade da Web do seu servidor estarão disponíveis durante a sessão atual em sua máquina local. Quando o computador é desligado ou vai para a suspensão, o serviço não estará mais disponível.
No prompt de comando, saia do localhost e digite o seguinte:
```bash
gulp ngrok-serve
```
> [!IMPORTANT]
> Depois que a guia tiver sido carregada no Microsoft Teams, via *ngrok*e salva com êxito, você poderá exibi-la no Teams até que a sessão de túnel seja encerrada.
## <a name="upload-your-application-to-teams"></a>Carregar seu aplicativo para o Microsoft Teams
- Abra o cliente do Microsoft Teams. Se você usar a [versão baseada na Web](https://teams.microsoft.com) , poderá inspecionar seu código de front-end usando as [ferramentas de desenvolvedor](~/tabs/how-to/developer-tools.md)do navegador.
- No painel *YourTeams* à esquerda, selecione o `...` menu ao lado da equipe que você está usando para testar sua guia e escolha **Gerenciar equipe**.
- No painel principal, selecione **aplicativos** na barra de guias e escolha **carregar um aplicativo personalizado** localizado no canto inferior direito da página.
- Abra o diretório do projeto, navegue até a pasta **./Package** , selecione a pasta zip, clique com o botão direito do mouse e escolha **abrir**. Sua guia será carregada no Microsoft Teams.
## <a name="view-your-personal-tabs"></a>Exibir suas guias pessoais
Na barra de navegação localizada na extrema esquerda do cliente Teams, selecione o `...` menu e escolha seu aplicativo na lista.
| 45.860294 | 497 | 0.740901 | por_Latn | 0.993862 |
c049f0a2dcdb3d31f9bd597c9a31c1695385b5fb | 689 | md | Markdown | _patents/2017-09-15-patent-008.md | JianshanZhou/jianshanzhou.github.io | 3e97ecc1c0150dd44f0db4a0252f6058e47fa7d8 | [
"MIT"
] | null | null | null | _patents/2017-09-15-patent-008.md | JianshanZhou/jianshanzhou.github.io | 3e97ecc1c0150dd44f0db4a0252f6058e47fa7d8 | [
"MIT"
] | null | null | null | _patents/2017-09-15-patent-008.md | JianshanZhou/jianshanzhou.github.io | 3e97ecc1c0150dd44f0db4a0252f6058e47fa7d8 | [
"MIT"
] | null | null | null | ---
title: "一种基于小波分析和半监督学习的车联网油耗数据质量评估方法"
collection: patents
permalink: /patents/2017-09-15-patent-008
excerpt: 'Authors: 田大新 朱宇凯 王云鹏 李玉洲 刘超 郑坤贤 <b>周建山</b> 康璐 刘文豪'
date: 2017-09-15
venue: 'CN107169532A'
paperurl: 'http://www.wanfangdata.com.cn/details/detail.do?_type=patent&id=CN201710447844.4'
citation: '田大新, 朱宇凯, 王云鹏, 李玉洲, 刘超, 郑坤贤, <b>周建山</b>, 康璐, 刘文豪. (2017). 一种基于小波分析和半监督学习的车联网油耗数据质量评估方法. CN107169532A.'
---
**摘要**: 本发明公开了一种基于小波分析和半监督学习的车联网油耗数据质量评估方法，包括以下步骤：步骤一：对数据进行预处理；步骤二：小波分析；步骤三：随机选取样本，由人工经验初步标注类别标签；步骤四：基于支持向量机的多分类器学习；步骤五：加入无标签的数据样本XUL，利用局部搜索策略进行半监督学习，更新分类器。本发明利用了小波分解的信号特点来构建油耗数据的属性特征，具有针对性且能有效地提高分类准确性和结论的可靠性。本发明多层小波分解得到的近似成分可以作为对数据有效的压缩过滤，细节成分能用于异常状况分析，为数据质量的类别划分提供可信的依据。
| 53 | 272 | 0.801161 | yue_Hant | 0.632602 |
c04a46ca5f78d66f13df2885e8c78402166a93b7 | 569 | md | Markdown | sections/5-12-cdv.md | caltechlibrary/cell-atlas | c3c70bb121b75f44f60ffba1a94cb964035c7f2e | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 1 | 2020-11-07T00:13:48.000Z | 2020-11-07T00:13:48.000Z | sections/5-12-cdv.md | caltechlibrary/cell-atlas | c3c70bb121b75f44f60ffba1a94cb964035c7f2e | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 48 | 2020-10-30T17:55:49.000Z | 2022-03-26T00:08:18.000Z | sections/5-12-cdv.md | caltechlibrary/cell-atlas | c3c70bb121b75f44f60ffba1a94cb964035c7f2e | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 3 | 2020-10-08T16:47:30.000Z | 2021-01-11T20:47:07.000Z | ---
title: Cdv
doi: 10.22002/D1.1518
videoTitle: Sulfolobus acidocaldarius
video: 5_12_Sacidocaldarius.mp4
videoAlt: 5_12.png
collector: Shrawan Mageswaran
subsections: []
---
The Cdv filaments then pull the membrane inward, constricting the cell, as you can see in this *Sulfolobus acidocaldarius* at a later stage of division. Again, the exact mechanism is unknown.
The majority of bacterial and archaeal cells divide by one of these two mechanisms–FtsZ or Cdv–but not all do. Some species have neither FtsZ nor Cdv, and we are still figuring out how they divide.
| 37.933333 | 197 | 0.790861 | eng_Latn | 0.997639 |
c04d065aea612fd603c8cebe1a2e78f565596221 | 119 | md | Markdown | README.md | EchtkPvL/twitch-chat | 176a16d836b9bb08963b7a461b8d7075741f4369 | [
"MIT"
] | null | null | null | README.md | EchtkPvL/twitch-chat | 176a16d836b9bb08963b7a461b8d7075741f4369 | [
"MIT"
] | null | null | null | README.md | EchtkPvL/twitch-chat | 176a16d836b9bb08963b7a461b8d7075741f4369 | [
"MIT"
] | null | null | null | # twitch-chat
## Copyright
Note that this repository is distributed under the MIT License. See `LICENSE` for details.
| 23.8 | 90 | 0.773109 | eng_Latn | 0.995949 |
c04e5ca0748c9f55a51bd62292d50fd8418bb08c | 866 | md | Markdown | documentation/reports/viikko4.md | Jhoneagle/RouteSolver | 05af7bca3c5bc47633de7cec4520e69cb1d8c406 | [
"Apache-2.0"
] | null | null | null | documentation/reports/viikko4.md | Jhoneagle/RouteSolver | 05af7bca3c5bc47633de7cec4520e69cb1d8c406 | [
"Apache-2.0"
] | 1 | 2018-08-23T20:10:11.000Z | 2018-12-10T09:32:42.000Z | documentation/reports/viikko4.md | Jhoneagle/RouteSolver | 05af7bca3c5bc47633de7cec4520e69cb1d8c406 | [
"Apache-2.0"
] | null | null | null | # Viikkoraportti 4
Projekti on edennyt pitkälle. Reitinhaku algoritmi pystyy nyt liikkumaan diagonaalisesti ja laskea etäisyys arviot tarkemmin. A* on kirjoitettu paremmaksi ja sen ohelle on luotu JPS reitinhaku algoritmi, joka on toimiva yksittäisiä erityistapauksia lukuunottamatta.
Dokumentatio on myös edennyt. Käyttö-ohjeet on kirjoitettu ja seuraavaksi alkaa testaus- ja toteutusdokumenttien teko. Seuraavaksi myös viimeistellään omien tietorakenteiden teko ja tarkoitus olisi yrittää vielä hioa JPS:n toimivuutta tietyissä erityistapauksissa.
Yksilötestaus junitilla on pääasiallisesti toteutettu myös ja empiiriselle suorituskyky testaukselle on luotu välineet käyttöliittymän yhteyteen. Tulokset ja vertailut vain pitää viellä saada aikaiseksi.
Paljon kyllä tuli kyllä opittua jump point seachistä lisää.
Tällä viikolla meni n. 28,5h työn tekoon.
| 66.615385 | 266 | 0.84642 | fin_Latn | 1.000009 |
c04f0cc96f3bbb9c5fbdc05cc318bccf87254785 | 1,529 | md | Markdown | results/innerfidelity/sbaf-serious/Philips SME3580/README.md | mmshivesh/AutoEq | 43414bfd71ac5c5ce5b5ae0e8d3ce7a11af2d5bf | [
"MIT"
] | 1 | 2020-07-26T09:34:56.000Z | 2020-07-26T09:34:56.000Z | results/innerfidelity/sbaf-serious/Philips SME3580/README.md | TheDarkMikeRises/AutoEq | ab0fcf2fe072665f8af1d253c14226621fadecec | [
"MIT"
] | null | null | null | results/innerfidelity/sbaf-serious/Philips SME3580/README.md | TheDarkMikeRises/AutoEq | ab0fcf2fe072665f8af1d253c14226621fadecec | [
"MIT"
] | null | null | null | # Philips SME3580
See [usage instructions](https://github.com/jaakkopasanen/AutoEq#usage) for more options and info.
### Parametric EQs
In case of using parametric equalizer, apply preamp of **-4.4dB** and build filters manually
with these parameters. The first 5 filters can be used independently.
When using independent subset of filters, apply preamp of **-4.4dB**.
| Type | Fc | Q | Gain |
|:--------|:--------|:-----|:--------|
| Peaking | 21 Hz | 0.44 | -9.2 dB |
| Peaking | 115 Hz | 0.54 | -3.3 dB |
| Peaking | 703 Hz | 0.8 | 4.2 dB |
| Peaking | 2209 Hz | 2.5 | -5.7 dB |
| Peaking | 5145 Hz | 7.03 | -5.0 dB |
| Peaking | 2692 Hz | 6.13 | -2.6 dB |
| Peaking | 3586 Hz | 2.64 | 5.2 dB |
| Peaking | 4426 Hz | 1.05 | -1.5 dB |
| Peaking | 5212 Hz | 1.38 | -1.0 dB |
| Peaking | 6753 Hz | 4.35 | 4.1 dB |
### Fixed Band EQs
In case of using fixed band (also called graphic) equalizer, apply preamp of **-4.3dB**
(if available) and set gains manually with these parameters.
| Type | Fc | Q | Gain |
|:--------|:---------|:-----|:--------|
| Peaking | 31 Hz | 1.41 | -9.6 dB |
| Peaking | 62 Hz | 1.41 | -3.9 dB |
| Peaking | 125 Hz | 1.41 | -3.6 dB |
| Peaking | 250 Hz | 1.41 | -1.1 dB |
| Peaking | 500 Hz | 1.41 | 2.7 dB |
| Peaking | 1000 Hz | 1.41 | 4.1 dB |
| Peaking | 2000 Hz | 1.41 | -4.8 dB |
| Peaking | 4000 Hz | 1.41 | 0.4 dB |
| Peaking | 8000 Hz | 1.41 | 0.2 dB |
| Peaking | 16000 Hz | 1.41 | -0.0 dB |
### Graphs
 | 38.225 | 98 | 0.554611 | eng_Latn | 0.781858 |
c05032f531ff4263e712bbe004e71591bac4ff1b | 413 | md | Markdown | devices/esp_eye.md | chagen24/iot-curriculum | 32c4cfe6a24d63e10d2f3f8ca5bcd32d6d84652d | [
"CC-BY-4.0",
"MIT"
] | 126 | 2020-07-15T02:46:53.000Z | 2022-03-20T06:11:47.000Z | devices/esp_eye.md | toolboc/iot-curriculum | ca7e6a62f8d5367708b9b397bb8a3f87e7562f50 | [
"CC-BY-4.0",
"MIT"
] | 33 | 2020-08-31T21:59:16.000Z | 2021-06-27T15:42:59.000Z | devices/esp_eye.md | toolboc/iot-curriculum | ca7e6a62f8d5367708b9b397bb8a3f87e7562f50 | [
"CC-BY-4.0",
"MIT"
] | 48 | 2020-07-14T19:13:06.000Z | 2022-03-01T08:55:49.000Z | # ESP-EYE
The [ESP-EYE from Espressif](https://www.espressif.com/en/products/devkits/esp-eye/overview) is a development board for image recognition and audio processing, which can be used in various AI powered IoT applications.
## ESP-EYE Resources
* [ESP32 + Azure Custom Vision](https://www.hackster.io/andri/esp32-azure-custom-vision-83d9c1) - a hands-on project to use the ESP-EYE with Azure Custom Vision
| 51.625 | 217 | 0.774818 | eng_Latn | 0.752462 |
c05051f87d3fe492caf0f1eb3b8224a45f25ed40 | 299 | md | Markdown | Game18/README.md | EOE0102/Games | 34eb0bfd48136f14834a569cbcf296012e7fc424 | [
"MIT"
] | 19 | 2019-12-31T07:12:44.000Z | 2022-03-27T15:12:49.000Z | Game18/README.md | SoulUi/Games | 95d5ac37c1104c896d64828eef76997d7deb8e15 | [
"MIT"
] | 4 | 2021-03-17T07:44:43.000Z | 2022-03-31T08:38:20.000Z | Game18/README.md | SoulUi/Games | 95d5ac37c1104c896d64828eef76997d7deb8e15 | [
"MIT"
] | 8 | 2020-05-22T00:15:48.000Z | 2022-02-07T10:36:13.000Z | # Introduction
https://mp.weixin.qq.com/s/9tNVTA06dFthdugNs3TePA
# Environment(Tested)
- Windows10
- Python3.5+(have installed necessary dependencies)
# Usage
- pip install -r requirements.txt
- python Game18.py
# Packages
- os
- sys
- random
- pygame
# Game Display
 | 15.736842 | 51 | 0.745819 | kor_Hang | 0.446247 |
c0507738b94c43cd9976e5726a826bc0d67e30bd | 1,045 | md | Markdown | interface-elements-for-desktop/articles/spreadsheet/pictures-and-hyperlinks/move-rotate-and-resize-a-picture.md | VeraGorbyliova/dotnet-eud | c9437f1eb0966cc0bc0d7ff8e275f41307d67aad | [
"RSA-MD"
] | 55 | 2017-07-06T14:02:11.000Z | 2022-01-13T13:46:18.000Z | interface-elements-for-desktop/articles/spreadsheet/pictures-and-hyperlinks/move-rotate-and-resize-a-picture.md | VeraGorbyliova/dotnet-eud | c9437f1eb0966cc0bc0d7ff8e275f41307d67aad | [
"RSA-MD"
] | 8 | 2017-08-25T11:39:35.000Z | 2021-12-03T11:53:02.000Z | interface-elements-for-desktop/articles/spreadsheet/pictures-and-hyperlinks/move-rotate-and-resize-a-picture.md | VeraGorbyliova/dotnet-eud | c9437f1eb0966cc0bc0d7ff8e275f41307d67aad | [
"RSA-MD"
] | 73 | 2017-07-12T06:28:37.000Z | 2022-02-07T06:10:22.000Z | ---
title: Move, Rotate and Resize a Picture
author: Natalya Senichkina
legacyId: 15756
---
# Move, Rotate and Resize a Picture
## Move a Picture
1. Click the picture you wish to move.
2. Drag the picture to a new location.
## Rotate a Picture
1. Click the picture you wish to rotate.
2. Click the _rotation handle_ (the round arrow that appears over the selected picture) and drag it in the direction in which you wish to rotate the object.
3. To rotate a picture in 15-degree increments, drag the rotation handle while holding down the **SHIFT** key.
## Resize a Picture
1. Click the picture to be resized.
2. Drag the _sizing handle_ away from the center (or towards the center) of the picture, and release it once the desired size is reached.
When you change the width of the object by dragging a _corner sizing handle_, the object's height will automatically be changed to maintain the aspect ratio of the object, and vice-versa. | 43.541667 | 187 | 0.75311 | eng_Latn | 0.9959 |
c050bc089b67e4861094f0597802442241dcc300 | 5,084 | md | Markdown | src/fr/2021-02/13/01.md | Pmarva/sabbath-school-lessons | 0e1564557be444c2fee51ddfd6f74a14fd1c45fa | [
"MIT"
] | 68 | 2016-10-30T23:17:56.000Z | 2022-03-27T11:58:16.000Z | src/fr/2021-02/13/01.md | Pmarva/sabbath-school-lessons | 0e1564557be444c2fee51ddfd6f74a14fd1c45fa | [
"MIT"
] | 367 | 2016-10-21T03:50:22.000Z | 2022-03-28T23:35:25.000Z | src/fr/2021-02/13/01.md | Pmarva/sabbath-school-lessons | 0e1564557be444c2fee51ddfd6f74a14fd1c45fa | [
"MIT"
] | 109 | 2016-08-02T14:32:13.000Z | 2022-03-31T10:18:41.000Z | ---
title: 'La vie de la nouvelle alliance'
date: 19/06/2021
---
Sabbat Après-Midi
### Lecture de la semaine
1 Jean 1:4; Jean 5:24; Rom. 3:24, 25; 2 Cor. 5:21; 1 Jean 4:16; Apo 2:11; Apo. 20:6, 14; Apo 21:8.
> <p>Verset à mémoriser</p>
> « Moi, Je suis venu afin que les brebis aient la vie, et qu’elles soient dans l’abondance » (Jean 10:10).
Ce trimestre a été consacré à une étude sur l’alliance, qui est (pour la réduire à sa forme la plus simple et la plus pure), Dieu disant: voici comment Je vous sauverai du péché, point final. Bien que le résultat, la grande finalité de la promesse de l’alliance, soit, bien sûr, la vie éternelle dans un monde nouveau, nous n’avons pas à attendre cela pour jouir des bénédictions de l’alliance aujourd’hui. Le Seigneur se soucie de nos vies maintenant; Il veut ce qu’il y a de mieux pour nous maintenant. L’alliance n’est pas une affaire où vous faites ceci et cela, et puis, très loin, vous obtenez votre récompense. Les récompenses, les dons, ce sont des bénédictions dont ceux qui, par la foi, entrent dans la relation d’alliance peuvent jouir ici et maintenant.
La leçon de cette semaine, la dernière de notre série sur l’alliance, examine quelques bénédictions immédiates, des promesses qui viennent de la grâce de Dieu versées dans nos cœurs, parce que, l’ayant entendu frapper, nous avons ouvert la porte. Bien sûr, il y a plus de bénédictions que ce que nous pouvons évoquer cette semaine. Mais ce n’est qu’un début, un début de quelque chose qui, en fait, ne finira jamais.
Aperçu de la semaine: Pourquoi devrions-nous ressentir de la joie? Sur quelle base pouvons-nous réclamer cette promesse? Qu’est-ce qui dans l’alliance, devrait nous libérer du fardeau de la culpabilité? Que signifie avoir un cœur nouveau?
_* Étudiez cette leçon pour le sabbat 26 Juin._
### Citations d’Ellen White en complément à l’étude de la Bible par l’École du Sabbat
La communion avec Dieu est une expérience personnelle. Le cœur, sous la direction du Saint-Esprit, brûlera de l’amour de Dieu. On se sent comme des enfants pleins de confiance. Christ ne cherche pas les personnes qui ont des mérites. Oh si chacun venait à Lui, et Le laissait agir, Il le prendrait tel qu’il est ! Le Seigneur désire seulement que chacun Le reçoive et apprenne à porter Son joug, et Ses fardeaux, afin que le ciel puisse observer qu’il est collaborateur avec Dieu. Pourquoi chacun de nous qui avons besoin d’aide et de repos ne venons pas à Celui qui porte les fardeaux afin qu’il puisse avoir lumière et vie ?
(Briller) était l’état naturel du Christ. Son œuvre même consistait à illuminer ceux qui l’entouraient... La lumière signifie révélation. Et la lumière doit briller au milieu des ténèbres morales. Le Christ est tout pour ceux qui Le reçoivent. Il est leur réconfort, leur sauvegarde, leur santé. Hors de Christ il n’y a pas de lumière. Le moindre nuage entre l’âme et Jésus n’a pas de raison d’être. Son cœur plein d’amour ne désire qu’une chose : combler l’âme des rayons lumineux de Sa justice. _Lift Him Up, p. 221._
Quelle richesse exprimée par ces mots : « Je suis la lumière du monde » (Jean 8.12). « Je suis le pain de vie » (Jean 6.35). « Je suis le chemin, la vérité, et la vie » (Jean 14.6). « Je suis le bon berger » (Jean10.14). « Moi, je suis venu afin que les brebis aient la vie, et qu’elles soient dans l’abondance » (Jean 10.10). Voilà le genre de vie que nous devons avoir, et nous devons l’avoir avec abondance. Dieu soufflera cette vie dans l’âme de tous ceux qui meurent à eux-mêmes et vivent pour Christ. Mais un total renoncement à soi-même est exigé. À moins que cela ne prenne place, nous portons avec nous le mal qui détruit notre bonheur. Mais quand l’ego est crucifié, le Christ vit en nous (voir Galates 2.20), et la puissance de l’esprit soutient nos efforts.
Nous devons, chaque jour, nous consacrer au service de Dieu et aller à Lui avec foi. Nous avons besoin de nous humilier devant Dieu. C’est la première chose à faire. Il faut soigneusement développer son sens critique envers soi-même, et chercher ce qui empêche l’Esprit de Dieu d’avoir accès à notre cœur. Car nous devons recevoir le Saint Esprit. Alors nous pourrons être revêtus de la puissance qui nous permettra d’être victorieux avec Dieu. _Our High Calling, p. 21._
Le ciel tout entier s’intéresse au bonheur de l’homme. Notre Père céleste ne prive de la joie aucune de ses créatures... Il veut non seulement les purifier du péché et leur accorder la rédemption par son sang, mais encore répondre aux soupirs de tous ceux qui consentent à se charger de son joug et à porter son fardeau. Il cherche à communiquer la paix et la sérénité à tous ceux qui viennent à lui (voir Matthieu 11.28) pour recevoir le pain de vie (voir Jean 6.48-58). Il attend de nous l’accomplissement de devoirs qui nous conduiront à une félicité supérieure, à laquelle le rebelle ne pourra jamais atteindre. La vie réelle et joyeuse de l’âme, c’est de posséder Jésus-Christ, l’espérance de la gloire (voir Colossiens1.27). _Steps toChrist, p. 46 ; Le MeilleurChemin, p. 44._ | 158.875 | 782 | 0.768686 | fra_Latn | 0.99505 |
c050f046521fdee398c39c5ce8eaca4d50ac497b | 4,359 | md | Markdown | _posts/2018-08-19-Safe-partial-initialization-in-Rust.md | scottjmaddox/scottjmaddox.github.io | 8a21ae6942c7c08f35202a3dad3135f866020e0a | [
"MIT"
] | null | null | null | _posts/2018-08-19-Safe-partial-initialization-in-Rust.md | scottjmaddox/scottjmaddox.github.io | 8a21ae6942c7c08f35202a3dad3135f866020e0a | [
"MIT"
] | null | null | null | _posts/2018-08-19-Safe-partial-initialization-in-Rust.md | scottjmaddox/scottjmaddox.github.io | 8a21ae6942c7c08f35202a3dad3135f866020e0a | [
"MIT"
] | null | null | null | ---
published: true
layout: post
---
Say we have a struct, `Foo`, with multiple fields that we would like to partially initialize without resorting to using `unsafe`. We could write a procedural macro called `PartialInit`, for example, which would be invoked using `derive`:
```rust
#[derive(PartialInit)]
struct Foo {
a: Box<bool>,
b: Box<u32>,
}
```
And which would expand into something like the following:
```rust
impl PartialInit for Foo {
type Uninit = PartialInitFoo<Uninit<Box<bool>>, Uninit<Box<u32>>>;
#[inline]
fn partial_init() -> Self::Uninit {
PartialInitFoo {
a: Uninit::new(),
b: Uninit::new(),
}
}
}
struct PartialInitFoo<A, B> {
a: A,
b: B,
}
impl<A, B> PartialInitFoo<Uninit<A>, B> {
#[inline]
fn init_a(self, a: A) -> PartialInitFoo<A, B> {
PartialInitFoo { a, b: self.b }
}
}
impl<A, B> PartialInitFoo<A, Uninit<B>> {
#[inline]
fn init_b(self, b: B) -> PartialInitFoo<A, B> {
PartialInitFoo { a: self.a, b }
}
}
impl PartialInitFoo<Box<bool>, Box<u32>> {
#[inline]
fn finalize(self) -> Foo {
Foo {
a: self.a,
b: self.b,
}
}
}
```
Where `Uninit` and `PartialInit` are defined as follows:
```rust
union Uninit<T> {
init: T,
uninit: (),
}
impl<T> Uninit<T> {
#[inline]
fn new() -> Self {
Self { uninit: () }
}
}
trait PartialInit {
type Uninit;
fn partial_init() -> Self::Uninit;
}
```
Note 1: Currently, due to limitations around unions in stable Rust, `Uninit` can only be defined this way in unstable Rust.
An alternative stable-friendly definition is possible using `core::mem::ManuallyDrop` and `core::mem::uninitialized`, though.
Note 2: the amount of generated source code grows linearly with the
number of fields, which is as good as we can expect.
Here's some example usage code:
```rust
let partial_foo = Foo::partial_init().init_a(Box::new(false));
// Feel free to do something that might panic, here.
// `partial_foo` has type `PartialInitFoo<Box<bool>, Uninit<Box<u32>>>`,
// which will properly drop `a: Box<bool>` on panic.
// In contrast, since `b: Uninit<Box<u32>>` is wrapped in `Uninit`,
// it will not be dropped, thus avoiding a potential security
// vulnerability.
let foo = partial_foo.init_b(Box::new(42)).finalize();
// `foo` is now a fully initialized `Foo`.
```
This looks promising! Using a little bit of boilerplate (that can be automated with
a procedural macro), we can provide a safe
interface to the bug-prone problem of partial initialization! But there's a catch...
[Unfortunately, LLVM is not able to optimize away all of the copying associated
with this approach to partial initialization](https://play.rust-lang.org/?gist=e4b00689bc21274119a7ad9a6e6beea3&version=nightly&mode=release).
So for performance-critical code, this isn't a very good solution.
Furthermore, one major reason for using partial initialization is to initialize structs
that are too large to fit on the stack, where idiomatic Rust initialization (`fn new() -> Self { ... }`)
would overflow the stack. However, since this approach to partial initialization
requires copying the entire struct onto the stack (multiple times), it will not
work for very large structs.
So while this pattern can be used today (either manually or through a procedural macro),
it is far from perfect. _But there's an opportunity here._ Rust could take memory safety to the next
level by providing first-class support for partial initialization with type-level safety
guarantees. By bringing support into the compiler and core library, the door opens to
guaranteeing copy elision (in debug *and* release builds),
enabling any and all use cases of partial initialization of structs and enums!
## Postscript
Once const generics are
available, this approach could potentially be extended to cover partial initialization of arrays,
making it possible to implement data structures like
[`ArrayVec`](https://docs.rs/arrayvec/latest/arrayvec/struct.ArrayVec.html)
with little-to-no `unsafe` code, making Rust even more appealing for security-critical applications.
## Comments
If you have any comments or questions, please [join the Reddit discussion!](https://www.reddit.com/r/rust/comments/98nmge/safe_partial_initialization_in_rust/)
| 32.529851 | 237 | 0.707272 | eng_Latn | 0.990485 |
c05125691fa4d554ecf492d777b4853c2ef2941b | 55 | md | Markdown | src/DDRTree/README.md | liluacrobat/MicroDynamics | d5d39a7ce86162cace7e13fd64826d57757cad0c | [
"MIT"
] | null | null | null | src/DDRTree/README.md | liluacrobat/MicroDynamics | d5d39a7ce86162cace7e13fd64826d57757cad0c | [
"MIT"
] | null | null | null | src/DDRTree/README.md | liluacrobat/MicroDynamics | d5d39a7ce86162cace7e13fd64826d57757cad0c | [
"MIT"
] | null | null | null |
DDRTree algorithm to learn a principal tree from data
| 18.333333 | 53 | 0.818182 | eng_Latn | 0.991587 |
c0513028aef7f03d00ce91a721ab08dccc5b85c0 | 2,433 | md | Markdown | docs/operator-guide/gitlab-integration.md | epam/edp-install | 2084b338b645ff673d03a51f43d7f093ca2c9792 | [
"Apache-2.0"
] | 16 | 2021-03-15T18:36:58.000Z | 2022-03-28T10:03:58.000Z | docs/operator-guide/gitlab-integration.md | epam/edp-install | 2084b338b645ff673d03a51f43d7f093ca2c9792 | [
"Apache-2.0"
] | null | null | null | docs/operator-guide/gitlab-integration.md | epam/edp-install | 2084b338b645ff673d03a51f43d7f093ca2c9792 | [
"Apache-2.0"
] | 5 | 2021-06-16T13:45:57.000Z | 2022-01-12T11:03:16.000Z | # GitLab Integration
Discover the steps below to apply the GitLab integration correctly:
!!! note
Before applying the GitLab integration, make sure to enable VCS Import strategy. For details, please refer to the [Enable VCS Import Strategy](import-strategy.md) section.
1. Create access token in **Gitlab**:
* Log in to **GitLab**;
* In the top-right corner, click your avatar and select **Settings**;
* On the **User Settings** menu, select **Access Tokens**;
* Choose a name and an optional expiry date for the token;
* In the Scopes block, select the *api* scope for the token;
* Click the **Create personal access token** button.
!!! note
Make sure to save the access token as there won`t be the ability to access it once again.
2. Install **GitLab plugin** (if not installed) by navigating to *Manage Jenkins* and switching to plugin manager, select the **GitLab Plugin** check box:
3. Create Jenkins Credential ID by navigating to *Jenkins -> Credentials -> System -> Global Credentials -> Add Credentials*:
* Select GitLab API token;
* Select Global scope;
* API token - the **Access Token** that was created earlier;
* ID - the **gitlab-access-token** ID;
* Description - the description of the current Credential ID;
4. Configure **Gitlab plugin** by navigating to *Manage Jenkins -> Configure System* and fill in the **GitLab plugin** settings:
* Connection name - gitlab;
* Gitlab host URL - a host URL to GitLab;
* Credentials - credentials with **Access Token** to GitLab (**gitlab-access-token**);
5. Create a new **Job Provision** by following the [instruction](manage-jenkins-ci-job-provision.md#gitlab-gitlab).
!!! warning
Using the GitLab integration, a webhook is automatically created. After the removal of the application, the webhook stops working but not deleted. If necessary, it must be deleted manually.
### Related Articles
* [Adjust Jira Integration](jira-integration.md)
* [Enable VCS Import Strategy](import-strategy.md)
* [Manage Jenkins CI Pipeline Job Provision](manage-jenkins-ci-job-provision.md)
| 44.236364 | 195 | 0.730374 | eng_Latn | 0.886521 |
c051e15919c04ef836afebbfac477f29ae66d9b7 | 3,807 | md | Markdown | _episodes/01-why-work-in-teams.md | esciencecenter-digital-skills/teamwork-for-research-software | 5391ba7dd6e39da0e1c5c8563d7d395efbc3cca8 | [
"CC-BY-4.0"
] | null | null | null | _episodes/01-why-work-in-teams.md | esciencecenter-digital-skills/teamwork-for-research-software | 5391ba7dd6e39da0e1c5c8563d7d395efbc3cca8 | [
"CC-BY-4.0"
] | 21 | 2021-11-08T12:56:47.000Z | 2021-11-11T08:29:34.000Z | _episodes/01-why-work-in-teams.md | NLeSC/teamwork-for-research-software-development | 5391ba7dd6e39da0e1c5c8563d7d395efbc3cca8 | [
"CC-BY-4.0"
] | null | null | null | ---
title: "Why work in teams?"
teaching: 10
exercises: 20
questions:
- "What are the benefits of working in a team?"
- "What are downsides of working in a team?"
objectives:
- "Explain the benefits and downsides of working in a team"
keypoints:
- "If done well, working in a team is fun and productive"
---
## Introduction
In this episode we will learn about teams and discuss why you should want to
work in a team in the first place. To define a team, it is useful to look at
teams in a continuum and think about the difference between a team and just any
group of people:
- Any gathering of people: they might not even know or see each other, nor
necessarily share common interests.
- Groups: they are aware of each other and may interact, more than a
simple gathering of people.
- Working group: a group with at least some common goals.
- Team: a group of people who act together to achieve common goals. Often,
a group of individuals first form a working group. Then, they become a team.
As opposed to working groups, teams have collective responsibility, leadership, and achievements. Read more about differences between working groups and teams
[here](https://ec.europa.eu/eusa/ebooks/wit-en/book.html#chapter02).
> ## Discussion
>
> Do you work in a working group or a team?
{: .discussion}
> ## Scrum team
>
> You might have heard of a _Scrum team_ that includes people with different
roles. We will learn about it in the episode [Introduction to
Scrum](./03-scrum-intro.md).
{: .callout}
## Why work in teams
> ## Discussion
>
> - What do you think are benefits of working in a team?
> - What do you think are downsides of working in a team?
>
> > ## Solution
> >
> > ### Benefits
> >
> > - Boost creativity and idea generation
> > - Learn from each other
> > - Share the workload of hard complex tasks
> > - Make use of complementary strengths of employees
> > - Better decision making
> > - A review process (where co-workers review each others work) often works better in a team because team members are familiar with the shared work. This increases the quality of the work.
> > - Humans are highly social animals and in general thrive by regular interaction with others, increasing motivation and productivity
> > - Increase the bus factor (i.e. when someone falls under a bus, the team can take over)
> > - Projects do not go on hold when a single employee is away, the team is able to pick up the work
> > - Shared responsibility and ownership
> > - Have multiple perspectives on performance from different team members.
> >
> > ### Downsides
> >
> > - Overhead of team meetings, communication and management
> > - More likely to get into conflicts with colleagues
> > - Possibility for too much peer pressure or feeling of being overlooked
> > - Not everything is under your control, so sometimes you have to work on things you do not like or that are initiated by someone else
> > - Teams can form isolated silos within an organisations
> > - Harder to measure contribution of individual to team outputs (think about publishing papers)
> > - You need a set of soft skills to work together successfully, potentially disadvantaging people that have more difficulty to develop these skills
> > - Leadership issues: leading a team is a difficult skill, which, if practiced badly, can have negative influence on the team members' work environment
> > - Differences in number of working hours or work pace can be magnified, which can lead to frustrations
> {: .solution}
{: .challenge}
There are many benefits of working in teams, but there are clearly also some downsides.
The key is to work together in such a way that the advantages outweigh the disadvantages.
An Agile way of working can help with this!
{% include links.md %}
| 44.267442 | 190 | 0.749672 | eng_Latn | 0.999935 |
c052f3ab4ab35c083a05964afed9c8e769cb9724 | 435 | md | Markdown | chapter4/README.md | VLDB-Study/transaction-processing-study | e3ae386629433259ec66fdf46548598872fe17bc | [
"MIT"
] | 4 | 2021-06-29T19:45:43.000Z | 2022-02-07T12:46:38.000Z | chapter4/README.md | VLDB-Study/transaction-processing-study | e3ae386629433259ec66fdf46548598872fe17bc | [
"MIT"
] | null | null | null | chapter4/README.md | VLDB-Study/transaction-processing-study | e3ae386629433259ec66fdf46548598872fe17bc | [
"MIT"
] | 2 | 2021-07-05T06:12:22.000Z | 2022-01-30T19:49:49.000Z | # Chapter 4: Transaction Models
## Main Presentation
- Presenter: 박종혁
- [Slides](slides/ch4-transaction-models.pdf)
## Short Presentation
- Presenter 1: 안미진
- How to Handle Distributed Transactions in MSA
- [Slides](slides/ch4-distributed-transactions-in-msa.pdf)
- Presenter 2: 이종백
- Emerging Hardware Trends in Large-Scale Transaction Processing
- [Slides](slides/ch4-emerging-hardware-trends-and-tx-processing.pdf) | 27.1875 | 71 | 0.749425 | yue_Hant | 0.296009 |
c053ba0e7116b1981502589c0ec33dc51b6a2747 | 6,023 | md | Markdown | cluster-deployment/minikube.md | PythonMove/k8s-notes | 1cfc092255ab7c7657acf1d4033fc39455ac9c77 | [
"MIT"
] | null | null | null | cluster-deployment/minikube.md | PythonMove/k8s-notes | 1cfc092255ab7c7657acf1d4033fc39455ac9c77 | [
"MIT"
] | null | null | null | cluster-deployment/minikube.md | PythonMove/k8s-notes | 1cfc092255ab7c7657acf1d4033fc39455ac9c77 | [
"MIT"
] | null | null | null | Follow this guide **ONLY** if you have the Minikube already installed. If you wish
to install the Minikube, follow [Minikube install guide](../install-guides/minikube.md).
---
## Useful Minikube deployment options
> **NOTE:** To see all the options, use **minikube start -h**.
You can specify number of nodes (virtual machines) Minikube will create when deploying cluster. This option does not work with driver=None.
```
--nodes=1
```
Number of vCPUs to use for Minikube virtual machines.
```
--cpus=4
```
Disk size to allocate for Minikube virtual machines.
```
--disk-size=64g
```
RAM size to allocate for Minikube virtual machines.
```
--memory=10g
```
Driver you want to use for Minikube. Via this you can specify whether you want to deploy cluster using
virtual machines, baremetal or in containers. KVM2 is driver for virtual machines.
```
--driver=kvm2
```
If you use KVM2 driver for Minikube, you can specify on which KVM network you want to deploy. Note that
specified KVM network has to be created beforehand. Minikube will **NOT** create the network for you.
```
--kvm-network=gitlabnet
```
This setting is used to freeze the cluster deploy on certain kubernetes version. Otherwise, newest available version would be used.
```
--kubernetes-version=1.19.9
```
Specify what container runtime to use in kubernetes cluster. Docker is the most comfortable solution. For other options, see "minikube config defaults -h"
```
--container-runtime=docker
```
Specify what CNI solution to use for Kubernetes cluster. Calico is used for performance. Other, more lightweight option is flannel.
```
--cni=calico
```
Just to demonstrate you can specify the dns domain name in Kubernetes cluster.
```
--dns-domain=k8s.local
```
Timeout for the cluster to boot up. Default is 6m0s which is too long for modern powerful hardware. You can save up some time by lowering the timeout.
```
--wait-timeout=5m0s
```
This is can be used to validate minikube run command.
```
--dry-run=true
```
## Minikube useful addons
To see list of all available addons:
```
minikube addons list
```
Enabling kubernetes helm-tiller.
```
minikube addons enable helm-tiller
```
Enabling kubernetes ingress.
```
minikube addons enable ingress
```
Enabling kubernetes podSecurityPolicy objects.
```
minikube addons enable pod-security-policy
```
Enabling kubernetes dashboard.
```
minikube addons enable dashboard
```
Enabling metrics-server.
```
minikube addons enable metrics-server
```
## Default HW deploy values
If you don't specify driver, Minikube will start the cluster using either KVM or Docker, since they are preferred. If none of that is installed, it will try to deploy using other drivers or will fail completely. It is recommended to explicitly specify the driver.
Minikube can be told what HW requirements to place on VMs, if KVM or Virtualbox is used as driver. default values are:
* --cpus=2
* --disk-size=20000mb
* --memory=2g
# Deploying the VM to other disk
If you want to deploy minikube VM instance on different hard drive than that of where your system is installed, set environment variable MINIKUBE_HOME to path which is on different hard drive.
```
export MINIKUBE_HOME=<path-mounted-on-different-hard-drive>
```
## Start single-node Minikube cluster with default values
```
minikube start --driver=kvm2
```
## Start multi-node Minikube cluster with custom values
Following command will create Minikube cluster, using KVM driver. Minikube will create 2 VMs. Both VMs will have allocated 4vCPUs, 8GB RAM and by default, 20GB of disk space.
```
minikube start --driver=kvm2 --nodes=2 --cpus=4 --memory=8g
```
## Verify the deployment
Check Kubernets components status. You should get following values:
```
daniel@pop-os:~$ minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
timeToStop: Nonexistent
```
Check kube-system pods. You should see all in "Running" status.
```
daniel@pop-os:~$ minikube kubectl -- get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-74ff55c5b-6h954 1/1 Running 0 7m48s
kube-system etcd-minikube 1/1 Running 0 7m56s
kube-system kube-apiserver-minikube 1/1 Running 0 7m56s
kube-system kube-controller-manager-minikube 1/1 Running 0 7m56s
kube-system kube-proxy-zkn7z 1/1 Running 0 7m48s
kube-system kube-scheduler-minikube 1/1 Running 0 7m56s
kube-system storage-provisioner 1/1 Running 1 8m2s
```
If there are some components or pods failing, try to use steps in *troubleshooting*.
## Connecting system-installed Kubectl to Minikube
If you wish to connect to Minikube cluster with system-installed kubectl, you have to use kubectl with sudo. When using with sudo, system-installed kubectl will be able to see the cluster.
## Troubleshooting
If you get some error during *minikube start*, you will usually get self-explanatory error message. You can google it and most likely find an answer on github or stack-overflow. If you cannot find a solution, you can always try one of the ways to reset minikube bellow:
If you encounter an error that breaks the Minikube, you can clean the changes and start again:
```
minikube stop
minikube delete
minikube start ...
```
If you want to stop/delete VM and it is stuck, you can always try to stop/delete the VM using the driver directly. For example, if you run VMs using Virtualbox, you can fire up Virtualbox GUI and manually stop/delete the VM.
If steps above did not help, you can hard delete Minikube files:
```
rm -rf ~/.minikube
```
> **NOTE:** Be aware that by deleting *~/.minikube*, you are deleting all ISO files and images that are required to run Minikube cluster. Your next *minikube start* command will have to re-download all these files, which is about 0.75GB of data.
| 34.614943 | 269 | 0.731031 | eng_Latn | 0.991677 |
c054badb25ed88a7c5b9122b50535280485149d3 | 2,531 | md | Markdown | README.md | ansuleymanova/comment_tree | ae6b222b7380501896fa1de8127afd00a4f33d10 | [
"MIT"
] | null | null | null | README.md | ansuleymanova/comment_tree | ae6b222b7380501896fa1de8127afd00a4f33d10 | [
"MIT"
] | null | null | null | README.md | ansuleymanova/comment_tree | ae6b222b7380501896fa1de8127afd00a4f33d10 | [
"MIT"
] | null | null | null | # comment_tree
## Description
Comment tree is a simple REST API app to implement a blogging function: users can post an article, and other users can comment the articles or leave a comment on other people's comment. API response for a comment contains ID of a parent comment (```Null``` if its zero-level comment) and nesting level (depth of the comment, 0 if the comment is left directly in response to an article). These fields allow one to recreate the comment tree structure, which is organized as a linked list.
Powered by nginx, Django, PostgreSQL.
## Settings
Default query for an article's comments includes only comments up to 3rd nesting level. Deeper comments can be called additionally by corresponding endpoint.
## Endpoints
Endpoints are created by REST DefaultRouter. API is versioned, api root is ```api/v1/```. Please note: CORS headers need to be configured additionally!
```hhtp://127.0.0.1/api/v1/articles``` returns paginated list of articles.
```hhtp://127.0.0.1/api/v1/articles/<article-id>``` returns specific article by id.
```hhtp://127.0.0.1/api/v1/articles/<article-id>/comments``` returns paginated article's comments UP TO third nesting level.
```hhtp://127.0.0.1/api/v1/articles/<article-id>/comments/<article-id>``` returns specific comment by id.
```hhtp://127.0.0.1/api/v1/articles/<article-id>/comments/<article-id>/child-comments``` returns comments of depth 4 and deeper for a specefic comment.
## Permissions
Default permission is rest_framework.permissions.IsAdminUser. Articles and Comments viewsets are rest_framework.permissions.IsAuthenticatedOrReadOnly.
## Setup
Clone project to your machine. Create .env file with database access specifications (DB_NAME, POSTGRES_USER, POSTGRES_PASSWORD, DB_HOST, DB_PORT) and SECRET_KEY (can be generated here: https://djecrety.ir)
From root direcrory of the project run:
```
docker-compose up -d --build
```
I prefer running migrations manually, to do that run following:
```
docker-compose exec web python manage.py makemigrations articles comments
docker-compose exec web python manage.py migrate
docker-compose exec web python manage.py collectstatic
```
To create superuser run:
```
docker-compose exec web python manage.py createseperuser
```
Apply initial data:
```
docker-compose exec web python manage.py loaddata fixtures.json
```
All is set! Now you can check the results at http://127.0.0.1/api/v1
## API Specs
After the setup API specifications can be found at http://127.0.0.1/swagger or http://127.0.0.1/redoc
| 39.546875 | 486 | 0.766891 | eng_Latn | 0.976895 |
c05518eaf3a9d26f90fa1cac23d410556e43c3f7 | 2,677 | md | Markdown | Documentation/SCRUM Documentation/Sprint 3.md | PRocha0503/Construcci-n-de-software | e9cb31ff61a37fd73dc59bc20540c45c3040d091 | [
"MIT"
] | null | null | null | Documentation/SCRUM Documentation/Sprint 3.md | PRocha0503/Construcci-n-de-software | e9cb31ff61a37fd73dc59bc20540c45c3040d091 | [
"MIT"
] | null | null | null | Documentation/SCRUM Documentation/Sprint 3.md | PRocha0503/Construcci-n-de-software | e9cb31ff61a37fd73dc59bc20540c45c3040d091 | [
"MIT"
] | null | null | null | # Sprint 3
SCRUM MASTER: Pablo Rocha
## Sprint Planning
### What tasks will we do this sprint?
- Create an api with Node Js.
- Connect the database to the API.
- Create endpoints to be able to add game information to the database.
- Create endpoints to be able to obtain information from the database.
- Create a simple web page.
- Generate sounds for the game
## Daily SCRUM
### Day #1
April 18, 2022
### What tasks will we do today?
Miguel Arriaga: code documentation and readability
Pablo Rocha: Created API
Luis Karam: Start game soundtrack composing
### Did I accomplish what I proposed yesterday
This was the first day of the sprint
### Day #2
April 19, 2022
### What tasks will we do today?
Miguel Arriaga: API routes for levels
Pablo Rocha: Game endpoints
Luis Karam: Fix scrolling bar and drum sounds in-game
### Did I accomplish what I proposed yesterday
Miguel Arriaga: ✅
Pablo Rocha: ✅
Luis Karam: ✅
### Day #3
April 20, 2022
### What tasks will we do today?
Miguel Arriaga: Start simple webpage
Pablo Rocha: Fix endpoints
Luis Karam: Create drum sprites and animations
### Did I accomplish what I proposed yesterday
Miguel Arriaga: ✅
Pablo Rocha: ✅
Luis Karam: ✅
### Day #4
April 21, 2022
### What tasks will we do today?
Miguel Arriaga: Finish delete endpoints
Pablo Rocha: Make better front end
Luis Karam: Create drum sprites and animations
### Did I accomplish what I proposed yesterday
Miguel Arriaga: ✅
Pablo Rocha: ✅
Luis Karam: ✅
### Day #5
April 22, 2022
### What tasks will we do today?
Miguel Arriaga: Learn about making api calls from unity
Pablo Rocha: Check that all api work
Luis Karam: produce game over soundtrack
### Did I accomplish what I proposed yesterday
Miguel Arriaga: ✅
Pablo Rocha: ✅
Luis Karam: ✅
## Sprint review
### What did the client like?
- That the prototype is working.
- Assets, art, music.
### What did the client dislike?
- Assets are too small and visibility is not clear.
### What tasks need to be be added to the backlog?
- Make assets bigger or improve game visibility somehow.
## Sprint Retrospective
### How many requirements where completed?
- 6
### What did we do right?
- Completed api and admin view
### What can we improve?
- Animation of the drums.
### What tasks need to be repeated?
- NONE
### Did we accomplish our goals?
- YES
### How long did it took?
This sprint took about 126 hours to complete, with the foundation for the game now complete, there was more time to focus on the development of the api to comunicate the database with the game, there was also a lot of for in aesthetic aspects such as visuals and audio. | 17.496732 | 269 | 0.723198 | eng_Latn | 0.996933 |
c0554fd9db5e5de170afdfcea2119bab36b7104c | 55 | md | Markdown | README.md | samuelkll/Web-2-repository | a4bebf67c966d47d36bc1587c37c73b953c1781a | [
"MIT"
] | null | null | null | README.md | samuelkll/Web-2-repository | a4bebf67c966d47d36bc1587c37c73b953c1781a | [
"MIT"
] | null | null | null | README.md | samuelkll/Web-2-repository | a4bebf67c966d47d36bc1587c37c73b953c1781a | [
"MIT"
] | null | null | null | # Web-2-repository
criado por erros no 1° repositório
| 18.333333 | 35 | 0.763636 | por_Latn | 0.997602 |
c0580110cab45ed01c3a5c95f64fe402fab78ccf | 3,568 | md | Markdown | articles/service-fabric/service-fabric-create-your-first-linux-application-with-java.md | lettucebo/azure-content-zhtw | f9aa6105a8900d47dbf27a51fd993c44a9af5b63 | [
"CC-BY-3.0"
] | null | null | null | articles/service-fabric/service-fabric-create-your-first-linux-application-with-java.md | lettucebo/azure-content-zhtw | f9aa6105a8900d47dbf27a51fd993c44a9af5b63 | [
"CC-BY-3.0"
] | null | null | null | articles/service-fabric/service-fabric-create-your-first-linux-application-with-java.md | lettucebo/azure-content-zhtw | f9aa6105a8900d47dbf27a51fd993c44a9af5b63 | [
"CC-BY-3.0"
] | null | null | null | <properties
pageTitle="使用 Java 在 Linux 上建立第一個 Service Fabric 應用程式 | Microsoft Azure"
description="使用 Java 建立和部署 Service Fabric 應用程式"
services="service-fabric"
documentationCenter="java"
authors="seanmck"
manager="timlt"
editor=""/>
<tags
ms.service="service-fabric"
ms.devlang="java"
ms.topic="hero-article"
ms.tgt_pltfrm="NA"
ms.workload="NA"
ms.date="09/28/2016"
ms.author="seanmck"/>
# 建立第一個 Azure Service Fabric 應用程式
> [AZURE.SELECTOR]
- [C Sharp](service-fabric-create-your-first-application-in-visual-studio.md)
- [Java](service-fabric-create-your-first-linux-application-with-java.md)
Service Fabric 提供了在 Linux 上建置服務的 .NET Core 和 Java SDK。在本教學課程中，我們將探討如何建立適用於 Linux 的應用程式以及使用 Java 建置服務。
## 必要條件
開始之前，請確定您已[設定 Linux 開發環境](service-fabric-get-started-linux.md)。如果您使用 Mac OS X，您可以[使用 Vagrant 在虛擬機器中設定 Linux 一整體環境](service-fabric-get-started-mac.md)。
## 建立應用程式
Service Fabric 應用程式可以包含一或多個服務，而每個服務在提供應用程式的功能時都有特定角色。適用於 Linux 的 Service Fabric SDK 包含 [Yeoman](http://yeoman.io/) 產生器，可讓您輕鬆建立第一個服務且稍後新增更多服務。讓我們使用 Yeoman 來建立具有單一服務的新應用程式。
1. 在終端機中，輸入 **yo azuresfjava**。
2. 為您的應用程式命名。
3. 選擇第一個服務的類型並加以命名。基於本教學課程的用途，我們將選擇 Reliable Actor 服務。
![適用於 Java 的 Service Fabric Yeoman 產生器][sf-yeoman]
>[AZURE.NOTE] 如需選項的詳細資訊，請參閱 [Service Fabric 程式設計模型概觀](service-fabric-choose-framework.md)。
## 建置應用程式
Service Fabric Yeoman 範本包含 [Gradle](https://gradle.org/) 的建置指令碼，可用來從終端機建置應用程式。
```bash
gradle
```
## 部署應用程式
建置應用程式後，可以使用 Azure CLI 將它部署到本機叢集。
1. 連接到本機 Service Fabric 叢集。
```bash
azuresfcli servicefabric cluster connect
```
2. 使用範本中所提供的安裝指令碼，將應用程式套件複製到叢集的映像存放區、註冊應用程式類型，以及建立應用程式的執行個體。
```bash
cd myapp
./install.sh
```
3. 開啟瀏覽器並瀏覽至位於 http://localhost:19080/Explorer 的 Service Fabric Explorer (如果在 Mac OS X 上使用 Vagrant，請以 VM 的私人 IP 取代 localhost)。
4. 展開 [應用程式] 節點，請注意，您的應用程式類型現在有一個項目，而另一個則是該類型的第一個執行個體。
## 啟動測試用戶端並執行容錯移轉
動作項目專案沒有任何屬於自己的項目。它們需要其他服務或用戶端傳送訊息給它們。動作項目範本包含簡單的測試指令碼，您可以用來與動作項目服務互動。
1. 使用監看式公用程式執行指令碼，以查看動作項目服務的輸出。
```bash
cd myactorsvcTestClient
watch -n 1 ./testclient.sh
```
2. 在 Service Fabric Explorer 中，找出裝載動作項目服務主要複本的節點。在以下的螢幕擷取畫面中是節點 3。
![在 Service Fabric Explorer 中尋找主要複本][sfx-primary]
3. 按一下您在上一個步驟中找到的節點，然後從 [動作] 功能表選取 [停用 (重新啟動)]。這會重新啟動本機叢集中五個節點的其中一個，並強制容錯移轉至在另一個節點上執行的其中一個次要複本。當您這麼做時，請留意測試用戶端的輸出，並注意儘管是容錯移轉，計數器仍會繼續增加。
## 使用 Eclipse Neon 外掛程式建置和部署應用程式
如果您已安裝適用於 Eclipse Neon 的 Service Fabric 外掛程式，您可以使用它來建立、建置和部署使用 Java 建置的 Service Fabric 應用程式。
### 建立應用程式
Service Fabric 外掛程式可透過 Eclipse 擴充功能取得。
1. 在 Eclipse 中，選擇 [檔案] > [其他] > [Service Fabric]。您會看到一組選項，包括 [動作項目] 和 [容器]。
![Eclipse 中的 Service Fabric 範本][sf-eclipse-templates]
2. 在此情況下，選擇 [無狀態服務]。
3. 系統會要求您確認使用的 Service Fabric 層面，以最佳化搭配 Service Fabric 專案使用的 Eclipse。選擇 [是]。
### 部署應用程式
Service Fabric 範本包含一組用來建置和部署應用程式的 Gradle 工作，您可以透過 Eclipse 觸發這些工作。
1. 選擇 [執行] > [執行組態]。
2. 展開 [Gradle 專案] 並選擇 [ServiceFabricDeployer]。
3. 按一下 **[執行]**。
幾分鐘內即可建置和部署您的應用程式。您可以從 Service Fabric Explorer 監視其狀態。
## 後續步驟
- [深入了解 Reliable Actors](service-fabric-reliable-actors-introduction.md)
<!-- Images -->
[sf-yeoman]: ./media/service-fabric-create-your-first-linux-application-with-java/sf-yeoman.png
[sfx-primary]: ./media/service-fabric-create-your-first-linux-application-with-java/sfx-primary.png
[sf-eclipse-templates]: ./media/service-fabric-create-your-first-linux-application-with-java/sf-eclipse-templates.png
<!---HONumber=AcomDC_0928_2016--> | 27.658915 | 171 | 0.717769 | yue_Hant | 0.973894 |
c05826f638c57edba6b61ad206daff40e62ada3a | 6,176 | md | Markdown | output/jira-contributions.md | elek/ozone-stat | 706fda79e0e48f7ed7e0515c711d07b6b4b86c16 | [
"Apache-2.0"
] | null | null | null | output/jira-contributions.md | elek/ozone-stat | 706fda79e0e48f7ed7e0515c711d07b6b4b86c16 | [
"Apache-2.0"
] | null | null | null | output/jira-contributions.md | elek/ozone-stat | 706fda79e0e48f7ed7e0515c711d07b6b4b86c16 | [
"Apache-2.0"
] | null | null | null | <div>
<table border="1" class="dataframe">
<thead>
<tr style="text-align: right;">
<th></th>
<th>contributions</th>
</tr>
<tr>
<th>author</th>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<th>hadoopqa</th>
<td>3115</td>
</tr>
<tr>
<th>hudson</th>
<td>2464</td>
</tr>
<tr>
<th>anu</th>
<td>1837</td>
</tr>
<tr>
<th>genericqa</th>
<td>1130</td>
</tr>
<tr>
<th>xyao</th>
<td>894</td>
</tr>
<tr>
<th>elek</th>
<td>754</td>
</tr>
<tr>
<th>arpitagarwal</th>
<td>643</td>
</tr>
<tr>
<th>ppogde</th>
<td>628</td>
</tr>
<tr>
<th>nandakumar131</th>
<td>585</td>
</tr>
<tr>
<th>msingh</th>
<td>559</td>
</tr>
</tbody>
</table>
</div>
## Contributors per participations in JIRA which are not created by self (commenting/helping JIRA)
<div>
<table border="1" class="dataframe">
<thead>
<tr style="text-align: right;">
<th></th>
<th>identifier</th>
</tr>
<tr>
<th>author</th>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<th>hudson</th>
<td>1904</td>
</tr>
<tr>
<th>hadoopqa</th>
<td>1127</td>
</tr>
<tr>
<th>anu</th>
<td>899</td>
</tr>
<tr>
<th>ppogde</th>
<td>623</td>
</tr>
<tr>
<th>xyao</th>
<td>484</td>
</tr>
<tr>
<th>arpitagarwal</th>
<td>411</td>
</tr>
<tr>
<th>elek</th>
<td>368</td>
</tr>
<tr>
<th>genericqa</th>
<td>356</td>
</tr>
<tr>
<th>msingh</th>
<td>306</td>
</tr>
<tr>
<th>nandakumar131</th>
<td>303</td>
</tr>
<tr>
<th>bharatviswa</th>
<td>247</td>
</tr>
<tr>
<th>shashikant</th>
<td>155</td>
</tr>
<tr>
<th>ajayydv</th>
<td>135</td>
</tr>
<tr>
<th>linyiqun</th>
<td>135</td>
</tr>
<tr>
<th>dineshchitlangia</th>
<td>123</td>
</tr>
<tr>
<th>adoroszlai</th>
<td>112</td>
</tr>
<tr>
<th>jnp</th>
<td>106</td>
</tr>
<tr>
<th>cheersyang</th>
<td>99</td>
</tr>
<tr>
<th>vagarychen</th>
<td>92</td>
</tr>
<tr>
<th>avijayan</th>
<td>87</td>
</tr>
</tbody>
</table>
</div>
## Contributors per participations in any issue
<div>
<table border="1" class="dataframe">
<thead>
<tr style="text-align: right;">
<th></th>
<th>identifier</th>
</tr>
<tr>
<th>author</th>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<th>hudson</th>
<td>1904</td>
</tr>
<tr>
<th>anu</th>
<td>1134</td>
</tr>
<tr>
<th>hadoopqa</th>
<td>1127</td>
</tr>
<tr>
<th>elek</th>
<td>1019</td>
</tr>
<tr>
<th>xyao</th>
<td>729</td>
</tr>
<tr>
<th>ppogde</th>
<td>685</td>
</tr>
<tr>
<th>msingh</th>
<td>646</td>
</tr>
<tr>
<th>bharatviswa</th>
<td>645</td>
</tr>
<tr>
<th>nandakumar131</th>
<td>592</td>
</tr>
<tr>
<th>adoroszlai</th>
<td>541</td>
</tr>
<tr>
<th>arpitagarwal</th>
<td>531</td>
</tr>
<tr>
<th>shashikant</th>
<td>413</td>
</tr>
<tr>
<th>genericqa</th>
<td>356</td>
</tr>
<tr>
<th>avijayan</th>
<td>251</td>
</tr>
<tr>
<th>dineshchitlangia</th>
<td>250</td>
</tr>
<tr>
<th>ajayydv</th>
<td>250</td>
</tr>
<tr>
<th>ljain</th>
<td>218</td>
</tr>
<tr>
<th>hanishakoneru</th>
<td>212</td>
</tr>
<tr>
<th>linyiqun</th>
<td>196</td>
</tr>
<tr>
<th>cheersyang</th>
<td>180</td>
</tr>
</tbody>
</table>
</div>
# Bus factor (number of contributors responsible for the 50% of the issue creations) from last half year
## Contributors until the half of the all contributions
<div>
<table border="1" class="dataframe">
<thead>
<tr style="text-align: right;">
<th></th>
<th>author</th>
<th>identifier</th>
<th>cs</th>
<th>ratio</th>
</tr>
</thead>
<tbody>
<tr>
<th>0</th>
<td>elek</td>
<td>85</td>
<td>85</td>
<td>11.470985</td>
</tr>
<tr>
<th>1</th>
<td>adoroszlai</td>
<td>80</td>
<td>165</td>
<td>10.796221</td>
</tr>
<tr>
<th>2</th>
<td>bharatviswa</td>
<td>41</td>
<td>206</td>
<td>5.533063</td>
</tr>
<tr>
<th>3</th>
<td>rakeshr</td>
<td>39</td>
<td>245</td>
<td>5.263158</td>
</tr>
<tr>
<th>4</th>
<td>glengeng</td>
<td>39</td>
<td>284</td>
<td>5.263158</td>
</tr>
<tr>
<th>5</th>
<td>shashikant</td>
<td>36</td>
<td>320</td>
<td>4.858300</td>
</tr>
<tr>
<th>6</th>
<td>avijayan</td>
<td>31</td>
<td>351</td>
<td>4.183536</td>
</tr>
</tbody>
</table>
</div>
## Pony number (bus factor)
8
## Dev power (All the contributions in the ration of the top contributor)
8.717647058823529
## People with created JIRAs > commented JIRA
## Same graph with focusing to the last 6 month
Only contributors with both created pr and helped pr visible
# Number of individual contributors per month
Number of different Jira users who either created ssue or commented Issue
Text(0.5, 1.0, 'Number of induvidual contributors per month')
# JIRA activity heatmap
| 15.100244 | 104 | 0.459035 | eng_Latn | 0.37179 |
c0589c60c1a0887b42ae4e9dbbb8c4068d801b61 | 81 | md | Markdown | README.md | Unviray/Bin2Dec | 9e54679499b4ffa1ac1ddb615123ffeecc4093f0 | [
"MIT"
] | null | null | null | README.md | Unviray/Bin2Dec | 9e54679499b4ffa1ac1ddb615123ffeecc4093f0 | [
"MIT"
] | null | null | null | README.md | Unviray/Bin2Dec | 9e54679499b4ffa1ac1ddb615123ffeecc4093f0 | [
"MIT"
] | null | null | null |
# Bin2Dec
Convert binary into decimal
| 16.2 | 41 | 0.740741 | kor_Hang | 0.40511 |
c058a75f62e56af81b27eb2a2d81a99392612ff0 | 666 | md | Markdown | README.md | twitter/autolog-clustering | 697c618c04fbaea5b1df1c0e310adb4e75cb2fe8 | [
"Apache-2.0",
"MIT"
] | null | null | null | README.md | twitter/autolog-clustering | 697c618c04fbaea5b1df1c0e310adb4e75cb2fe8 | [
"Apache-2.0",
"MIT"
] | null | null | null | README.md | twitter/autolog-clustering | 697c618c04fbaea5b1df1c0e310adb4e75cb2fe8 | [
"Apache-2.0",
"MIT"
] | 1 | 2021-06-03T23:20:10.000Z | 2021-06-03T23:20:10.000Z | # thrift-examples
## Generate
```bash
thrift -out pygen/ --gen py example.thrift
thrift -out jsgen/ --gen js:node example.thrift
```
### Requirements
* Python: `$ pip install thrift`,
* Node.js: `$ npm install thrift`,
* Code generator: [Apache Thrift](https://thrift.apache.org/) (requires only for development).
### Run
* Server: `$ python ./server.py`,
* Python client: `$ ./client.py` or `$ python client.py`,
* Node.js client: `$ ./client.js` or `$ node client.js`.
### Output
```bash
$ python server.py
Starting python server...
Hello from Python!
Hello from JavaScript!
```
```bash
$ python client.py
\\ output
```
```bash
$ node client.js
\\ output
```
| 19.028571 | 94 | 0.657658 | eng_Latn | 0.62061 |
c0598d2566d63dbebe801e892e1ba33ad3bd5979 | 272 | md | Markdown | lintr/closed_curly_linter.md | r3yn0ld4/docs-for-code-review-tools | a1590fce3b30891679373ec284787b227b21df05 | [
"MIT"
] | 4 | 2019-07-17T18:16:06.000Z | 2021-03-28T23:53:10.000Z | lintr/closed_curly_linter.md | r3yn0ld4/docs-for-code-review-tools | a1590fce3b30891679373ec284787b227b21df05 | [
"MIT"
] | null | null | null | lintr/closed_curly_linter.md | r3yn0ld4/docs-for-code-review-tools | a1590fce3b30891679373ec284787b227b21df05 | [
"MIT"
] | 5 | 2018-09-29T17:02:14.000Z | 2021-12-26T16:53:04.000Z | Pattern: Closed curly brace on same line
Issue: -
## Description
Checks that closed curly braces are always on their own line unless they are followed by an `else`.
## Further Reading
* [lintr - Available linters](https://github.com/jimhester/lintr#available-linters) | 24.727273 | 99 | 0.761029 | eng_Latn | 0.99681 |
c05a81757aa722a5209450e39ad42bfdd5b8bca4 | 417 | md | Markdown | README.md | rgies/dsp | 6b6b69567a59e32bd8e8f05ee23076fc05daba76 | [
"MIT"
] | null | null | null | README.md | rgies/dsp | 6b6b69567a59e32bd8e8f05ee23076fc05daba76 | [
"MIT"
] | null | null | null | README.md | rgies/dsp | 6b6b69567a59e32bd8e8f05ee23076fc05daba76 | [
"MIT"
] | null | null | null | Digital Story Processing
===============================
Framework to help agile project to work with digital story cards.
Install
========
Download and install Composer from http://getcomposer.org.
Then start the command line and type in the following command to install this package.
> php composer.phar create-project -s dev rgies/dsp
Update
========
Update with composer:
> php composer.phar update
test | 18.130435 | 86 | 0.697842 | eng_Latn | 0.944739 |
c05c02a9b8d618e80355f2cfcd827e479686732f | 1,025 | md | Markdown | _posts/2019-03-16-tonakyuuBD1.md | noaione/noaione.github.io | 02db8eca1d43c7bcf7772805c2108f811c1ef2ae | [
"MIT"
] | null | null | null | _posts/2019-03-16-tonakyuuBD1.md | noaione/noaione.github.io | 02db8eca1d43c7bcf7772805c2108f811c1ef2ae | [
"MIT"
] | 1 | 2019-03-04T06:14:47.000Z | 2019-03-04T06:14:47.000Z | _posts/2019-03-16-tonakyuuBD1.md | noaione/noaione.github.io | 02db8eca1d43c7bcf7772805c2108f811c1ef2ae | [
"MIT"
] | null | null | null | ---
layout: releasepost
title: "Tonari no Kyuuketsuki-san - Vol 1 (BD)"
image: "https://puu.sh/D0HHh/6e38812506.png"
site_name: "Release"
lang: "id_ID"
tags: ["tonakyuu", 'bd', "serial"]
date: 2019-03-16
comments: true
staff_list:
-
work: "TL"
name: "Ponimu"
-
work: "TS, Timing, Edit, Encode, dan QC"
name: "N4O"
-
work: "BD Source"
name: "paihctom@U2"
vainfo:
-
head: "Video"
body: "BD | x264 1280x720 Hi444PP CRF15.25"
-
head: "Audio"
body: "BD | qAAC 2.0 TVBR100"
-
head: "Subs"
body: "Ponimu Edited (TSed, Restyled, Retimed)"
urls:
-
id: "bdvol1"
link: "https://www.perpusindo.info/berkas/OuYFHtp4"
text: "Episode 01-03 (Vol 1)"
-
id: "bonus"
link: "https://drive.google.com/drive/folders/18qYWg8sEE5vq_gIdzJKLQPM30MISSuHb?usp=sharing"
text: "Bonus CD (FLAC)"
---
Kapan punya tetangga kayak gini
BELUM MATI!<br>
Ada Bonus CD bagi yang mau<br>
Tolong kasitau kesalahan di Discord atau comment biar cepet di v2 pas batch :wink: | 23.295455 | 96 | 0.639024 | yue_Hant | 0.353014 |
c05c71337f8474a2f2bfc52a4ea62b644b6872d2 | 108 | md | Markdown | _posts/0000-01-02-cchalifoux.md | cchalifoux/github-slideshow | abf8f9090bcaca0de4f08b946108cbb5627d3664 | [
"MIT"
] | null | null | null | _posts/0000-01-02-cchalifoux.md | cchalifoux/github-slideshow | abf8f9090bcaca0de4f08b946108cbb5627d3664 | [
"MIT"
] | 2 | 2018-08-18T03:26:23.000Z | 2018-08-18T03:57:20.000Z | _posts/0000-01-02-cchalifoux.md | cchalifoux/github-slideshow | abf8f9090bcaca0de4f08b946108cbb5627d3664 | [
"MIT"
] | null | null | null | ---
layout: slide
title: "Welcome to our second slide!"
---
Simone is home
Use the left arrow to go back!
| 15.428571 | 37 | 0.685185 | eng_Latn | 0.999302 |
c05d1896140722ee35c1930470415818dde2788d | 5,571 | md | Markdown | CHANGELOG.md | jamzo/see | d2badb58951e03778ff318a72ac8fbeedd444769 | [
"BSD-3-Clause"
] | null | null | null | CHANGELOG.md | jamzo/see | d2badb58951e03778ff318a72ac8fbeedd444769 | [
"BSD-3-Clause"
] | null | null | null | CHANGELOG.md | jamzo/see | d2badb58951e03778ff318a72ac8fbeedd444769 | [
"BSD-3-Clause"
] | null | null | null | Change Log
==========
All notable changes to this project will be documented in this file.
This project adheres to [Semantic Versioning][semver] as of v1.1.0.
## [v1.1.1][] / 2015-04-17
### Fixed
* Broken on Windows due to a dependency on the fcntl module.
_(Spotted by Christopher Toth.)_
## [v1.1.0][] / 2015-03-27
### Added
* Output is adjusted to fit the terminal width.
* Print '?' after any attributes that raised an exception.
_(Contributed by Andrei Fokau.)_
### Fixed
* Unhandled exceptions when reading attributes.
_(Patch contributed by Andrei Fokau.)_
## [v1.0.1][] / 2010-10-17
### Changed
* Changed the license from GPL to BSD.
## [v1.0][] / 2010-07-31
### Added
* Justified columns.
_(Contributed by Steve Losh.)_
### Changed
* Output is indented to line up with the prompt. For example, if the prompt
string is "<code>> </code>", the output will be indented by two
spaces. _(Contributed by Liam Cooke with a bug fix from Adam Lloyd.)_
### Fixed
* Exception raised when `see()` has nothing to display.
## [v0.5.4][] / 2009-07-23
### Fixed
* Calling `see()` first with no arguments would return nothing.
## [v0.5.3][] / 2009-04-12
### Added
* Running `see.py` as a script will show documentation, equivalent
to `help(see)`.
* If you want to be lazy, you can '`from see import *`', and only `see()`
will be imported.
### Changed
* Results are spaced out more, and line up with the default interpreter prompt.
For example:
>>> see(int, pattern='h*')
hash() help() hex()
* Unary operator symbols changed from `+@` and `-@` to `+obj` and `-obj`
respectively.
* Revised code documentation and examples.
* New project homepage: http://inky.github.com/see/
### Fixed
* `see()` output could be modified, but would still print the original
results. The output list now acts like a tuple.
## [v0.5.2][] / 2009-03-16
### Added
* Calling `see()` without arguments shows local variables.
_(Contributed by Charlie Nolan.)_
## [v0.5.1][] / 2009-03-13
### Changed
* Filename pattern matching is now the default. For example:
> see('', '.is*')
.isalnum() .isalpha() .isdigit() .islower() .isspace()
.istitle() .isupper()
Regular expression matching can still be done, using the `r` argument.
### Fixed
* Python 3.0: After the first `see()` call, subsequent calls would give no
output for some objects.
* Python 3.0: Regular expression and filename pattern matching would also
result in nothing being output.
## [v0.5][] / 2009-03-07
### Added
* Now returns a list-like object, for iterating through the results, while
still showing the human-readable output when run interactively.
_(Contributed by Bob Farrell.)_
* Optional `regex` and `fn` arguments, for regular expression and filename
pattern matching, respectively.
_(Contributed by Ed Page.)_
## [v0.4.1][] / 2009-02-23
### Added
* New attributes: `str()` and `repr()`.
_(`str()` contributed by Guff.)_
## [v0.4][] / 2009-02-19
### Added
* For Python 3.0, new attributes are included, and deprecated attributes
are no longer shown.
_(Contributed by Gabriel Genellina.)_
* Instructions added for using this with iPython.
_(Contributed by Baishampayan Ghose.)_
### Changed
* (Pseudo-)static variables moved outside the `see()` function.
This may or may not be more efficient.
* If the object has a docstring set, 'help()' is shown in the list
instead of '?'.
_(Suggested by Eduardo de Oliveira Padoan.)_
### Fixed
* AttributeError with Django class attributes fixed.
_(Contributed by Jeremy Dunck.)_
* The correct symbols are now shown for objects implementing
`__divmod__`, `__floordiv__` and `__cmp__`.
_(Contributed by Gabriel Genellina.)_
## [v0.3.1][] / 2009-02-18
### Added
* Symbols for binary arithmetic operations using reflected
(swapped) operands.
* 'with' and 'reversed()' symbols.
## [v0.3][] / 2009-02-18
### Added
* Rudimentary Python 3.0 support.
_(Suggestions by CommodoreGuff.)_
* Created a _setup.py_ installation script.
### Fixed
* Outdated documentation link in the _README_ file.
_(Spotted by Ian Gowen.)_
## v0.2 / 2009-02-17
### Added
* Added '.\*' symbol for the `__getattr__` attribute.
* `help()` documentation added.
### Changed
* Special attribute symbols reordered.
* Unary addition and subtraction changed to `+@` and `-@` respectively.
## v0.1 / 2009-02-16
* Original release.
[unreleased]: https://github.com/inky/see/compare/v1.1.1...develop
[v1.1.1]: https://github.com/inky/see/compare/v1.1.0...v1.1.1
[v1.1.0]: https://github.com/inky/see/compare/v1.0.1...v1.1.0
[v1.0.1]: https://github.com/inky/see/compare/v1.0-fixed...v1.0.1
[v1.0]: https://github.com/inky/see/compare/v0.5.4...v1.0-fixed
[v0.5.4]: https://github.com/inky/see/compare/v0.5.3...v0.5.4
[v0.5.3]: https://github.com/inky/see/compare/v0.5.2...v0.5.3
[v0.5.2]: https://github.com/inky/see/compare/v0.5.1...v0.5.2
[v0.5.1]: https://github.com/inky/see/compare/v0.5...v0.5.1
[v0.5]: https://github.com/inky/see/compare/v0.4.1...v0.5
[v0.4.1]: https://github.com/inky/see/compare/v0.4...v0.4.1
[v0.4]: https://github.com/inky/see/compare/v0.3.1...v0.4
[v0.3.1]: https://github.com/inky/see/compare/v0.3...v0.3.1
[v0.3]: https://github.com/inky/see/compare/v0.2...v0.3
[semver]: http://semver.org/
[keepachangelog]: http://keepachangelog.com/
| 23.706383 | 81 | 0.656076 | eng_Latn | 0.946197 |
c05d87055ed88965c0a50541c28ccd4414ee3974 | 2,050 | md | Markdown | IAMRole/Readme.md | erankitcs/AWS_SSM_HandsOn | 934b6bb1dde7355a7ee27eb28e68f71cd5ff876e | [
"MIT"
] | null | null | null | IAMRole/Readme.md | erankitcs/AWS_SSM_HandsOn | 934b6bb1dde7355a7ee27eb28e68f71cd5ff876e | [
"MIT"
] | null | null | null | IAMRole/Readme.md | erankitcs/AWS_SSM_HandsOn | 934b6bb1dde7355a7ee27eb28e68f71cd5ff876e | [
"MIT"
] | null | null | null | ### Creating an IAM Role and Configuring an EC2 Instance for AWS Systems Manager
1. Get the ARN of SSM Policy for IAM Role `AmazonEC2RoleforSSM`
aws iam list-policies --scope AWS --query "Policies[?PolicyName == 'AmazonEC2RoleforSSM']"
2. Create the role and attach the trust policy JSON file
aws iam create-role --role-name MyEC2SSMRole --assume-role-policy-document file://EC2Trust.json
3. Assign policy from previous step to the newly created role
aws iam attach-role-policy --role-name MyEC2SSMRole --policy-arn <SSM-POLICY-ARN>
4. Create instance profile for EC2 instance
aws iam create-instance-profile --instance-profile-name MyEC2InstanceProfile
5. Add the role created in second task to the instance profile created above:
aws iam add-role-to-instance-profile --instance-profile-name MyEC2InstanceProfile --role-name MyEC2SSMRole
6. Get subnet ID
aws ec2 describe-subnets --query "Subnets[?Tags[?Value == 'SubnetA'] ].SubnetId | [0]"
7. Get security group ID
aws ec2 describe-security-groups --filters Name=group-name,Values=SG --query "SecurityGroups[?GroupName == 'SG'].GroupId | [0]"
8. Get AMI ID (with SSM installed)
aws ec2 describe-images --filters "Name=architecture,Values=x86_64" "Name=description,Values=*Amazon Linux 2 AMI 2.0.2019*gp2" "Name=owner-id,Values=137112412989" "Name=image-type,Values=machine" --query "sort_by(Images, &CreationDate)[::-1].ImageId | [0]"
9. Create an EC2 Instance Using Subnet, Security Group, and AMI ID
aws ec2 run-instances --associate-public-ip-address --security-group-ids <SECURITY-GROUP-ID> --iam-instance-profile Arn=<INSTANCE-PROFILE-ARN> --instance-type t2.micro --image-id <AMI-ID> --subnet-id <SUBNET-ID> --tag-specifications "ResourceType=instance,Tags=[{Key=Name,Value=MyEC2}]"
10. Verify instance
aws ec2 describe-instances --filters Name=tag:Name,Values=MyEC2 --query "Reservations[].Instances[].InstanceId"
11. Verify from SSM
aws ssm describe-instance-information --query "InstanceInformationList[?InstanceId == '<INSTANCE-ID>']" | 82 | 290 | 0.75122 | yue_Hant | 0.456971 |
c05dbb9c210f21635f8887a4905168816f252491 | 31 | md | Markdown | README.md | meziantou/CsharpProjectTemplate | 777a9117e1e90ba5fe59199c9f928305e2ba8c25 | [
"MIT"
] | 7 | 2021-02-11T14:42:57.000Z | 2022-03-30T16:52:18.000Z | README.md | meziantou/CsharpProjectTemplate | 777a9117e1e90ba5fe59199c9f928305e2ba8c25 | [
"MIT"
] | 52 | 2020-12-01T07:10:31.000Z | 2022-03-28T00:05:31.000Z | README.md | meziantou/CsharpProjectTemplate | 777a9117e1e90ba5fe59199c9f928305e2ba8c25 | [
"MIT"
] | 6 | 2020-11-28T13:11:32.000Z | 2022-03-10T20:14:01.000Z | # Project
project description
| 7.75 | 19 | 0.806452 | eng_Latn | 0.985935 |
c05f59bcfb1368d79ae084179d4d8311f4e8c943 | 13,304 | md | Markdown | 20131230-kittys_dresses_2013.md | ohtake/blog-ameba | a81987189f8d3fa0893238299de51282511a83a2 | [
"CC-BY-4.0"
] | 1 | 2019-02-04T15:04:19.000Z | 2019-02-04T15:04:19.000Z | 20131230-kittys_dresses_2013.md | ohtake/blog-ameba | a81987189f8d3fa0893238299de51282511a83a2 | [
"CC-BY-4.0"
] | 2 | 2020-08-25T16:25:58.000Z | 2021-05-09T09:44:31.000Z | 20131230-kittys_dresses_2013.md | ohtake/blog-ameba | a81987189f8d3fa0893238299de51282511a83a2 | [
"CC-BY-4.0"
] | null | null | null | # キティ衣装2013
2013年にお会いできたキティの衣装の一覧を作っておこう。なるべく全身が写っているものから1枚ずつ選んで。たったの一年だけでこれだけの衣装を着たキティに会えたし、大阪や大分やその他の場所でもまた別の衣装があるはずなので、いったいどれだけ衣装をお持ちのことなのだろう。
## ピューロランドのショー・アトラクション
### Believe
光っている状態と光っていない状態は別扱いでいいのかな。
[](http://www.flickr.com/photos/ohtake_tomohiro/9286149912/)
[](http://www.flickr.com/photos/ohtake_tomohiro/10249355304/)
<!-- markdownlint-disable MD026 -->
### ARIGATO EVERYONE!
<!-- markdownlint-restore -->
40th のは 40th オープニングセレモニー、1000人ハグの先着100人、晩餐会でも使用。
[](http://www.flickr.com/photos/ohtake_tomohiro/10902416776/)
[](http://www.flickr.com/photos/ohtake_tomohiro/11529767796/)
### オズの魔法の国
普段着のはキャラクター大賞グリーティングでも使用。
[](https://picasaweb.google.com/lh/photo/toLc9rbQd6Tv-Pa8mTaPt9MTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](https://picasaweb.google.com/lh/photo/-yE7zHAYXfkytpFS3A75OdMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](https://picasaweb.google.com/lh/photo/_-mt0jqh4Dkz-i9xn53vLNMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
### 不思議の国のハローキティ
[](http://www.flickr.com/photos/ohtake_tomohiro/9054261550/)
[](http://www.flickr.com/photos/ohtake_tomohiro/8991669805/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9656300946/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9775216493/)
### どきどき! マジカル☆マーチ
[](http://www.flickr.com/photos/ohtake_tomohiro/10776773186/)
### パワー・ザ・キティ
8月のくまモン夏期講習と、西武園ゆうえんちの9月『ハッピースマイルセレブレーション』でも使用。
イチゴマンはキティの扱いにしていいのか悩むが、数を増やすためにも入れてしまおう。イチゴマンはキャラクター大賞期間の14時グリでも何回か登場。無料開放日にも登場していたらしい。
[](http://www.flickr.com/photos/ohtake_tomohiro/8991764793/)
[](https://picasaweb.google.com/lh/photo/y-l8PZz_5TJPfahMe9q8-dMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
### PURO★アイドル★コレクション
KITTY5 のは晩餐会でも使用。
[](https://picasaweb.google.com/lh/photo/EQrODMpKzTvHC6zQ2xXJftMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](https://picasaweb.google.com/lh/photo/plZkpqfY9GmxR6h-vykdE9MTjNZETYmyPJy0liipFm0?feat=embedwebsite)
### Join!☆Kitty
[](http://www.flickr.com/photos/ohtake_tomohiro/9286109572/)
### キティズハウス
サンリオタウンリニューアル中のリトルガーデンでも同様。白地に赤リボンのは、7月27日のゆめみっちのスペシャルステージと、8月のくまモン夏期講習でも使用。12月のお祓いでも着ていたらしい。
[](https://picasaweb.google.com/lh/photo/8QDf7ChAhXlcyIKBqRniZNMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](https://picasaweb.google.com/lh/photo/VwFz6fXwxw_UeZrLi12WGNMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](https://picasaweb.google.com/lh/photo/0PFa4BsUBZFjugZvBmr8QNMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
### レディキティハウス
[](http://www.flickr.com/photos/ohtake_tomohiro/9329266957/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9444139092/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9544039147/)
## ピューロランドのグリーティング
### 通常もの
たいていは ONE で、ごくまれにフローレンス。アリスのタイムエプロンはショーで使っているものとは別物。チャーミーがついているだけでなく、腰後ろリボンの模様も異なる。ティーパーティもグリーティング用のものであった。
[](http://www.flickr.com/photos/ohtake_tomohiro/8826145024/)
[](https://picasaweb.google.com/lh/photo/PhVzKqKfKHZHwO566xaYqNMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](https://picasaweb.google.com/lh/photo/Jv33BfYcpxTPIRZJZwYscdMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
### 正月
ピンクのは餅つきイベントや豆まきパーティでも使用。年末にはリトルガーデンや写真のミニプラントでも使用。
赤の晴れ着では今年はショールを付けないのかな。
[](https://picasaweb.google.com/lh/photo/rmGwNeWahAtKNiGKRUkkONMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](http://www.flickr.com/photos/ohtake_tomohiro/11613512694/)
### お盆
3枚目の白い着物は落合夏祭盆踊り大会でも使用。
[](http://www.flickr.com/photos/ohtake_tomohiro/9382750550/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9286105178/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9582808717/)
### ハロウィン
パンプキンは9月上旬の SANRIO EXPO で一足先に使用。3種類ともハロウィンマーチングパレードやリトルガーデンでも使用。
[](http://www.flickr.com/photos/ohtake_tomohiro/10113679845/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9949424505/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9741887827/)
### クリスマス
リトルガーデンおよび写真のミニプラントではクリスマスをすっ飛ばして正月になっていて、普段のグリーティングでも普段着のままだったので、今年のクリスマスは中止です。
## ピューロランドその他
### ちょるる
バラの衣装は3月末の多摩センタースプリングフェスタや11月の西武園ゆうえんち『ハローキティのバースデーセレモニー』や11月のハローキティストリート・しまじろう広場の誕生パレードでも使用。
[](https://picasaweb.google.com/lh/photo/o0ovmSrq8LFGRcoH4uPtA9MTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](http://www.flickr.com/photos/ohtake_tomohiro/8779716987/)
### アリスのティーパーティ
グリーティング用のアリス、オズのフィナーレ、神田うのによる[UNO KITTY ドレス](http://ameblo.jp/unokanda/entry-11419848940.html)。オズの衣装は冠や背中の羽がないので別扱いで。
[](https://picasaweb.google.com/lh/photo/PpPSSMC33k6uKnCmZ0fDfdMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](https://picasaweb.google.com/lh/photo/TXouq-8ZCSbT4Yb-mDHdpNMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
### キャラクター大賞
キャラクター大賞以外では、燕尾服を6月27日のパルテノン多摩グリーティングや12月30日の年末サンリオキャラクター歌自慢で使用。
[](http://www.flickr.com/photos/ohtake_tomohiro/9067235198/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9332074182/)
### 晩餐会
全部で4衣装あり、以下の2衣装以外では『ありがとうマイフレンズ』 (KITTY5 と同じ) と 40th があった。オーバーオールは12月上旬の平日に通常グリやふわふわランドで着てきたと聞いた。
[](http://www.flickr.com/photos/ohtake_tomohiro/10836893815/)
[](http://www.flickr.com/photos/ohtake_tomohiro/10836880765/)
### クリスマススペシャルパーティ
クリスマスイルミナント、燕尾服、ロマンティックセレナーデ、Believe in Christmas の4着。燕尾服は胸のリボンが通常版とは変更になっているので別扱いで。
[](http://www.flickr.com/photos/ohtake_tomohiro/11486544915/)
[](http://www.flickr.com/photos/ohtake_tomohiro/11486537885/)
[](http://www.flickr.com/photos/ohtake_tomohiro/11486648763/)
[](http://www.flickr.com/photos/ohtake_tomohiro/11486523755/)
## 普段の出張先
### 西武園ゆうえんち
9月『プリンセスアカデミー』
[](http://www.flickr.com/photos/ohtake_tomohiro/9996491643/)
10月『ハッピースマイルセレブレーション』
[](http://www.flickr.com/photos/ohtake_tomohiro/10114607714/)
11月『ハッピースマイルセレブレーション』
[](http://www.flickr.com/photos/ohtake_tomohiro/10644113985/)
12月『ハローキティのハッピークリスマス』と12月『ハローキティのクリスマス大行進!』
[](http://www.flickr.com/photos/ohtake_tomohiro/11152926336/)
12月『ハッピースマイルセレブレーション』
[](http://www.flickr.com/photos/ohtake_tomohiro/11152934336/)
### Kawaii Paradise
クリスマス時期だったためケープが追加されているが、通常はケープなし。
[](http://www.flickr.com/photos/ohtake_tomohiro/11026276214/)
### CLUB KT SHIBUYA
[](http://www.flickr.com/photos/ohtake_tomohiro/11026346226/)
## 外部公演
### みんなでスマイル
[](https://picasaweb.google.com/lh/photo/sWHvcGs0GMEr1xzdSihHg9MTjNZETYmyPJy0liipFm0?feat=embedwebsite)
### ハッピーキャラバン (旧)
[](https://picasaweb.google.com/lh/photo/vOte4gCeq92JvkjCVT06LNMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
[](https://picasaweb.google.com/lh/photo/XTneiWGB4usTSJZzS7IMENMTjNZETYmyPJy0liipFm0?feat=embedwebsite)
### ハッピーキャラバン (新)
[](http://www.flickr.com/photos/ohtake_tomohiro/10625208894/)
### OLキティ
[](http://www.flickr.com/photos/ohtake_tomohiro/9690589088/)
### ハッピーフレンドクリスマス
[](http://www.flickr.com/photos/ohtake_tomohiro/11494229915/)
### クリスマスレビューショー
9月の大崎では3着目が3枚目のサンタ衣装の替わりに4枚目の水色であった。4枚目の水色は多摩センターイルミネーションのスペシャルパレードでも着ていたらしい。
[](http://www.flickr.com/photos/ohtake_tomohiro/11009201923/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9687347403/)
[](http://www.flickr.com/photos/ohtake_tomohiro/11009211033/)
[](http://www.flickr.com/photos/ohtake_tomohiro/9690585032/)
## 総数
ちょっと多めに数えてはいるものの、自分がお見かけした衣装数だけで63着もあり週替わりでも収まりきらない。多摩近辺でも逃していることを把握しているだけでも何着かあるし、日本各地ましてや海外も含めればもっとたくさんの衣装がある。さすが世界のアイドル。
これだけ衣装数があるとそれぞれに名前がないと扱いが大変。冊子形式で衣装資料集でも出してほしいくらい。多数の衣装があるだけでなく、メインの服に合わせてリボンと靴も異なるデザインになっているのでかなり奥が深い。カルタの取り札にリボンだけが印刷されていて、読み札には全身写真と衣装名や使われた場面などが書かれていたら熱いな。誰が買うのか知らんけど自分はほしい。
リボンや靴だけでなくドロワーズも異なるデザインになっているようだ。長いスカートの場合でもメインの服に合わせたドロワーズになっていて、キティのおしゃれ具合に驚かされたり。ただ、スカートがめくれ上がる場面ばかりを狙ったりしているわけではないので、自分の手元にはそろってはいない。ドロワーズの一覧は誰かに任せた。
| 51.169231 | 252 | 0.817198 | yue_Hant | 0.528821 |
c05fec0f731b2362a40c4c63cf98c94e4bccecfa | 160 | md | Markdown | docs/_Footer.md | r-franke/brim | 41cf3e47495f6b258baecc8fc9c8cc5bc2c6bfa6 | [
"BSD-3-Clause"
] | null | null | null | docs/_Footer.md | r-franke/brim | 41cf3e47495f6b258baecc8fc9c8cc5bc2c6bfa6 | [
"BSD-3-Clause"
] | null | null | null | docs/_Footer.md | r-franke/brim | 41cf3e47495f6b258baecc8fc9c8cc5bc2c6bfa6 | [
"BSD-3-Clause"
] | null | null | null | Join our [Public Slack](https://join.slack.com/t/brimsec/shared_invite/zt-cy34xoxg-hZiTKUT~1KdGjlaBIuUUdg) workspace for announcements, Q&A, and to trade tips!
| 80 | 159 | 0.8 | eng_Latn | 0.428622 |
c0606640ee4526ef6431d4c560026744eafecf22 | 18 | md | Markdown | README.md | hayetadam/user-typescript | 13a259ae2fd9a322cc879849721e0f79bfe64c0c | [
"MIT"
] | null | null | null | README.md | hayetadam/user-typescript | 13a259ae2fd9a322cc879849721e0f79bfe64c0c | [
"MIT"
] | null | null | null | README.md | hayetadam/user-typescript | 13a259ae2fd9a322cc879849721e0f79bfe64c0c | [
"MIT"
] | null | null | null | # user-typescript
| 9 | 17 | 0.777778 | eng_Latn | 0.753057 |
c0609a5ad4fb6e2c1a2e8a81442069bf0c8aa228 | 1,246 | md | Markdown | utility-libraries/README.md | johanseaxis/acap-native-sdk-examples | 6cd00b807ee5ae36c24b89cf64befb5f190d37e9 | [
"Apache-2.0"
] | 41 | 2020-08-24T12:29:42.000Z | 2022-03-26T17:13:52.000Z | utility-libraries/README.md | johanseaxis/acap-native-sdk-examples | 6cd00b807ee5ae36c24b89cf64befb5f190d37e9 | [
"Apache-2.0"
] | 70 | 2020-09-16T12:32:17.000Z | 2022-02-22T13:40:36.000Z | utility-libraries/README.md | johanseaxis/acap-native-sdk-examples | 6cd00b807ee5ae36c24b89cf64befb5f190d37e9 | [
"Apache-2.0"
] | 13 | 2020-09-16T10:22:02.000Z | 2022-02-13T19:15:28.000Z | *Copyright (C) 2021, Axis Communications AB, Lund, Sweden. All Rights Reserved.*
# ACAP applications interacting with external libraries
This README file lists examples of how to build and use libraries in an application
## Getting started
Below is the structure of the files and folders on the top level:
```bash
utility-libraries
├── curl_example
├── custom_lib_example
└── README.md
```
* **curl_example** - Folder containing files for building ACAP application "curl_example".
* **custom_lib_example** - Folder containing files for building ACAP application "custom_lib_example".
* **README.md** - Step by step instructions on how to use the examples.
### Example applications
Each example has as a README file in its directory which shows overview, example directory structure and step-by-step instructions on how to run applications on the device.
Below is the list of examples available in the repository.
* [Curl Example](./curl_example/README.md)
* The example shows how to build curl as a library and make use of it in an application.
* [Custom lib Example](./custom_lib_example/README.md)
* The example shows how to build custom library and make use of it in an application.
## License
**[Apache License 2.0](../LICENSE)**
| 40.193548 | 172 | 0.764848 | eng_Latn | 0.996782 |
c062727bd794363d63ff62765f705844fee29de3 | 11,446 | md | Markdown | content/ps/BOJ/12100.md | nowwater/algoblog | 1fdb92c3a35e1242b05460cf96294580f2accda4 | [
"MIT"
] | 4 | 2021-03-08T08:43:44.000Z | 2021-05-14T13:35:32.000Z | content/ps/BOJ/12100.md | nowwater/algoblog | 1fdb92c3a35e1242b05460cf96294580f2accda4 | [
"MIT"
] | null | null | null | content/ps/BOJ/12100.md | nowwater/algoblog | 1fdb92c3a35e1242b05460cf96294580f2accda4 | [
"MIT"
] | 1 | 2021-10-06T04:05:02.000Z | 2021-10-06T04:05:02.000Z | ---
title: '12100. 2048(easy)'
metaTitle: '만렙 개발자 키우기'
metaDescription: '알고리즘 문제를 풀고 정리한 곳입니다.'
tags: ['구현', '브루트포스', '시뮬레이션']
date: '2021-01-17'
---
# 문제
- [12100. 2048(easy)](https://www.acmicpc.net/problem/12100)
## 코드
<details><summary> 코드 보기 </summary>
```java
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.util.*;
class Pair{
int x, y;
public Pair(int x, int y){
this.x = x;
this.y = y;
}
}
class Snap{
int snapshot[][];
public Snap(int n){
this.snapshot = new int[n][n];
}
public Snap(int[][] snapshot) {
this.snapshot = snapshot;
}
}
public class Q12100 {
static int n, board[][], max = 0, dx[] = {-1, 0, 1, 0}, dy[] = {0, 1, 0, -1};
static Snap start;
public static void main(String[] args) throws IOException {
init();
solution();
}
static void init() throws IOException {
BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
StringTokenizer st;
n = Integer.parseInt(br.readLine());
board = new int[n][n];
for (int i = 0; i < n; i++) {
st = new StringTokenizer(br.readLine());
for (int j = 0; j < n; j++)
board[i][j] = Integer.parseInt(st.nextToken());
}
start = new Snap(board);
}
static void solution() {
Queue<Snap> q = new LinkedList<>();
q.add(start);
int size, round = 0;
while(!q.isEmpty()){
if(round >= 5) break;
size = q.size();
for (int i = 0; i < size; i++) {
Snap now = q.poll();
for (int j = 0; j < 4; j++) {
Snap temp = new Snap(n);
copyArr(temp.snapshot, now.snapshot);
move(temp.snapshot, j);
updateMax(temp.snapshot);
q.add(temp);
}
}
round += 1;
}
System.out.println(max);
}
static void move(int snapshot[][], int dir) {
boolean merge[][] = new boolean[n][n];
for (int i = 0; i < n; i++)
Arrays.fill(merge[i], false);
if(dir == 0){ // up
for (int i = 0; i < n; i++) {
for (int j = 0; j < n; j++) {
if(snapshot[i][j] == 0) continue;
int x = i, y = j;
while(true){
int nx = x + dx[dir], ny = y + dy[dir];
if(!isBorder(nx, ny)) break;
if(snapshot[nx][ny] == 0)
{
snapshot[nx][ny] = snapshot[x][y];
snapshot[x][y] = 0;
}
else
{
if(snapshot[nx][ny] == snapshot[x][y] && !merge[nx][ny]) {
snapshot[nx][ny] = 2 * snapshot[x][y];
snapshot[x][y] = 0;
merge[nx][ny] = true;
}
break;
}
x = nx; y = ny;
}
}
}
} else if(dir == 1){ // right
for (int i = 0; i < n; i++) { // row
for (int j = n - 1; j >= 0; j--) { // col
if(snapshot[i][j] == 0) continue;
int x = i, y = j;
while(isBorder(x, y)){
int nx = x + dx[dir], ny = y + dy[dir];
if(!isBorder(nx, ny)) break;
if(snapshot[nx][ny] == 0)
{
snapshot[nx][ny] = snapshot[x][y];
snapshot[x][y] = 0;
}
else
{
if(snapshot[nx][ny] == snapshot[x][y] && !merge[nx][ny]) {
snapshot[nx][ny] = 2 * snapshot[x][y];
snapshot[x][y] = 0;
merge[nx][ny] = true;
}
break;
}
x = nx; y = ny;
}
}
}
} else if(dir == 2){ // down
for (int i = n - 1; i >= 0; i--) {
for (int j = 0; j < n; j++) {
if(snapshot[i][j] == 0) continue;
int x = i, y = j;
while(isBorder(x, y)){
int nx = x + dx[dir], ny = y + dy[dir];
if(!isBorder(nx, ny)) break;
if(snapshot[nx][ny] == 0)
{
snapshot[nx][ny] = snapshot[x][y];
snapshot[x][y] = 0;
}
else
{
if(snapshot[nx][ny] == snapshot[x][y] && !merge[nx][ny]) {
snapshot[nx][ny] = 2 * snapshot[x][y];
snapshot[x][y] = 0;
merge[nx][ny] = true;
}
break;
}
x = nx; y = ny;
}
}
}
} else { // left
for (int i = 0; i < n; i++) {
for (int j = 0; j < n; j++) {
if(snapshot[i][j] == 0) continue;
int x = i, y = j;
while(isBorder(x, y)){
int nx = x + dx[dir], ny = y + dy[dir];
if(!isBorder(nx, ny)) break;
if(snapshot[nx][ny] == 0)
{
snapshot[nx][ny] = snapshot[x][y];
snapshot[x][y] = 0;
}
else
{
if(snapshot[nx][ny] == snapshot[x][y] && !merge[nx][ny]) {
snapshot[nx][ny] = 2 * snapshot[x][y];
snapshot[x][y] = 0;
merge[nx][ny] = true;
}
break;
}
x = nx; y = ny;
}
}
}
}
}
private static boolean isBorder(int x, int y) {
return (x >= 0 && x < n && y >= 0 && y < n);
}
static void copyArr(int[][] snap, int[][] snapshot) {
for (int i = 0; i < n; i++) {
for (int j = 0; j < n; j++) {
snap[i][j] = snapshot[i][j];
}
}
}
static void updateMax(int[][] snap) {
for (int i = 0; i < n; i++)
for (int j = 0; j < n; j++)
if(snap[i][j] > max) max = snap[i][j];
}
}
/*
Queue 를 이용해 푸는 방법
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.util.LinkedList;
import java.util.Queue;
import java.util.StringTokenizer;
public class Main {
public static void main(String[] args) throws IOException {
BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
int N = Integer.parseInt(br.readLine());
int[][] arr = new int[N][N];
for(int i = 0; i < N; i++) {
StringTokenizer st = new StringTokenizer(br.readLine());
int count = st.countTokens();
for(int j = 0; j < count; j++)
arr[i][j] = Integer.parseInt(st.nextToken());
}
System.out.println(dfs(arr, 0));
br.close();
}
public static int dfs(int[][] arr, int depth) {
if(depth == 5) {
return maxNum(arr);
}
int[][] temp = copy(arr);
int[] maxArr = new int[4];
left(temp);
maxArr[0] = dfs(temp, depth + 1);
temp = copy(arr);
right(temp);
maxArr[1] = dfs(temp, depth + 1);
temp = copy(arr);
up(temp);
maxArr[2] = dfs(temp, depth + 1);
temp = copy(arr);
down(temp);
maxArr[3] = dfs(temp, depth + 1);
int max = Integer.MIN_VALUE;
for(int i = 0; i < maxArr.length; i++) {
if(maxArr[i] > max)
max = maxArr[i];
}
return max;
}
public static int[][] copy(int[][] arr) {
int[][] copy = new int[arr.length][arr.length];
for(int i = 0; i < arr.length; i++) {
for(int j = 0; j < arr[i].length; j++) {
copy[i][j] = arr[i][j];
}
}
return copy;
}
public static int maxNum(int[][] arr) {
int max = Integer.MIN_VALUE;
for(int i = 0; i < arr.length; i++) {
for(int j = 0; j < arr[i].length; j++) {
if(arr[i][j] > max)
max = arr[i][j];
}
}
return max;
}
public static void left(int[][] arr) {
for(int i = 0; i < arr.length; i++) {
Queue<Integer> q = new LinkedList<>();
for(int j = 0; j < arr[i].length; j++) {
if(arr[i][j] != 0) {
q.add(arr[i][j]);
arr[i][j] = 0;
}
}
int index = 0;
while(!q.isEmpty()) {
int value = q.poll();
if(!q.isEmpty() && value == q.peek()) {
value += q.poll();
arr[i][index++] = value;
} else {
arr[i][index++] = value;
}
}
}
}
public static void right(int[][] arr) {
for(int i = 0; i < arr.length; i++) {
Queue<Integer> q = new LinkedList<>();
for(int j = arr.length - 1; j > -1; j--) {
if(arr[i][j] != 0) {
q.add(arr[i][j]);
arr[i][j] = 0;
}
}
int index = arr.length - 1;
while(!q.isEmpty()) {
int value = q.poll();
if(!q.isEmpty() && value == q.peek()) {
value += q.poll();
arr[i][index--] = value;
} else {
arr[i][index--] = value;
}
}
}
}
public static void up(int[][] arr) {
for(int i = 0; i < arr.length; i++) {
Queue<Integer> q = new LinkedList<>();
for(int j = 0; j < arr[i].length; j++) {
if(arr[j][i] != 0) {
q.add(arr[j][i]);
arr[j][i] = 0;
}
}
int index = 0;
while(!q.isEmpty()) {
int value = q.poll();
if(!q.isEmpty() && value == q.peek()) {
value += q.poll();
arr[index++][i] = value;
} else {
arr[index++][i] = value;
}
}
}
}
public static void down(int[][] arr) {
for(int i = 0; i < arr.length; i++) {
Queue<Integer> q = new LinkedList<>();
for(int j = arr.length - 1; j > -1; j--) {
if(arr[j][i] != 0) {
q.add(arr[j][i]);
arr[j][i] = 0;
}
}
int index = arr.length - 1;
while(!q.isEmpty()) {
int value = q.poll();
if(!q.isEmpty() && value == q.peek()) {
value += q.poll();
arr[index--][i] = value;
} else {
arr[index--][i] = value;
}
}
}
}
}
*/
```
</details>
## ⭐️느낀점⭐️
> 여태 풀어본 구현중에 손꼽아 어려운 문제였다. 이전에 풀었던 구슬 탈출과 비슷하게 풀어보려고 했지만 더 복잡했다.. 이틀동안 메달려서 푼 문제 <br/>
> 자바는 왜 기본 자료형 외에는 전부 값이 복사되는 것인가................... <br/>
> 조금 반복적인 코드가 존재하더라도, 확실하게 메서드를 용도에 따라 구분해서 작성하는 방법도 고려해야겠다.
## 풀이 📣
<hr/>
1️⃣ 상.하.좌.우 방향으로 현재 상태에서 모두 이동시킨다. 이 때, 각 방향에 있어 먼저 가장자리에 도착하는 칸부터 동작을 수행한다. <br/>
2️⃣ 같은 숫자를 만나게 되면 해당 칸에서 이미 합쳐진 숫자가 없을 경우에 \*2 를 수행한다. <br/>
3️⃣ 위의 과정을 5번 반복해서 만들 수 있는 가장 높은 숫자를 출력한다. <br/>
<hr/>
## 실수 😅
- 자바의 값 복사가 C++과는 매우 다르다.. Snap temp를 어디서 선언해주냐에 따라서 값이 이상하게 복사되서 계속 헤맸다.
- 나름 코드의 간결성을 위해서 하드코딩말고 dir에 따라서 연산하는 부분을 하나의 메서드로 짜려다가 굉장히 복잡해졌다. 이런 BFS 문제에서는 그냥 상하좌우를 각 메서드로 나눠서 짜야겠다.
| 26.680653 | 106 | 0.402848 | kor_Hang | 0.701527 |
c063672e86713754205ed232623c8a45a325a1f8 | 3,335 | md | Markdown | content/publication/cancer_chapt/index.md | mattmctaggart/academic-kickstart | df507fbf3a28726347211bff2bddf453aaef4c1c | [
"MIT"
] | null | null | null | content/publication/cancer_chapt/index.md | mattmctaggart/academic-kickstart | df507fbf3a28726347211bff2bddf453aaef4c1c | [
"MIT"
] | null | null | null | content/publication/cancer_chapt/index.md | mattmctaggart/academic-kickstart | df507fbf3a28726347211bff2bddf453aaef4c1c | [
"MIT"
] | null | null | null | ---
# Documentation: https://sourcethemes.com/academic/docs/managing-content/
title: Nanomedicine and Drug Delivery Systems in Overcoming Resistance to Targeted Therapy
authors: [admin]
date: 2019-08-20
doi: "10.1007/978-3-030-21477-7_10"
# Schedule page publish date (NOT publication's date).
publishDate: 2019-26-10
# Publication type.
# Legend: 0 = Uncategorized; 1 = Conference paper; 2 = Journal article;
# 3 = Preprint / Working Paper; 4 = Report; 5 = Book; 6 = Book section;
# 7 = Thesis; 8 = Patent
publication_types: ["6"]
# Publication name and optional abbreviated publication name.
publication: "Current Applications for Overcoming Resistance to Targeted Therapies. Resistance to Targeted Anti-Cancer Therapeutics"
publication_short: ""
abstract: The first nanomedicine was approved for clinical use over 20 years ago. In the intervening time, our ability to engineer materials at the nanoscale has advanced immensely, yet a revolution in targeted drug delivery remains elusive. Nowhere is this more keenly felt than in the treatment of multi-drug resistant cancers, where nanotechnology’s fine control over drug release rate, location, and sequence promises a suite of tools for the effective long-term management of disease. This chapter provides a survey of the current knowledge and trajectory of nanomaterial drug delivery systems for avoiding or overcoming multiple drug resistance in cancer treatment. Existing nanocarriers in development incorporate a variety of materials and properties designed to transit through the circulatory system, concentrate at tumor sites, selectively bind to cancerous cells, and release their drug payloads. However, a greater understanding of the biological barriers to achieving each of those steps is still needed for drug delivery systems to successfully translate into clinical treatment. Greater attention on the interactions between specific delivery systems and their specific target cells in vivo might be achieved through a ‘disease-first’ design strategy and closer integration of materials and physiology during training.
# Summary. An optional shortened abstract.
summary: ""
tags: []
categories: []
featured: true
# Custom links (optional).
# Uncomment and edit lines below to show custom links.
# links:
# - name: Follow
# url: https://twitter.com
# icon_pack: fab
# icon: twitter
url_pdf:
url_code:
url_dataset:
url_poster:
url_project:
url_slides:
url_source: https://link.springer.com/chapter/10.1007/978-3-030-21477-7_10
url_video:
# Featured image
# To use, add an image named `featured.jpg/png` to your page's folder.
# Focal points: Smart, Center, TopLeft, Top, TopRight, Left, Right, BottomLeft, Bottom, BottomRight.
image:
caption: ""
focal_point: ""
preview_only: false
# Associated Projects (optional).
# Associate this publication with one or more of your projects.
# Simply enter your project's folder or file name without extension.
# E.g. `internal-project` references `content/project/internal-project/index.md`.
# Otherwise, set `projects: []`.
projects: []
# Slides (optional).
# Associate this publication with Markdown slides.
# Simply enter your slide deck's filename without extension.
# E.g. `slides: "example"` references `content/slides/example/index.md`.
# Otherwise, set `slides: ""`.
slides: ""
---
| 47.642857 | 1,334 | 0.776012 | eng_Latn | 0.978093 |
c063b28495e95bf1be70a4bf023f3b434a4e9028 | 1,163 | md | Markdown | docs/cli/commands/tanzu_secret_registry_list.md | benjaminapetersen/tanzu-framework | fbabd54a42868572dee518178c64dcb80fc02cd2 | [
"Apache-2.0"
] | 92 | 2021-10-04T07:46:46.000Z | 2022-03-24T22:13:14.000Z | docs/cli/commands/tanzu_secret_registry_list.md | benjaminapetersen/tanzu-framework | fbabd54a42868572dee518178c64dcb80fc02cd2 | [
"Apache-2.0"
] | 1,061 | 2021-10-04T09:35:11.000Z | 2022-03-31T21:34:35.000Z | docs/cli/commands/tanzu_secret_registry_list.md | benjaminapetersen/tanzu-framework | fbabd54a42868572dee518178c64dcb80fc02cd2 | [
"Apache-2.0"
] | 110 | 2021-10-04T07:22:29.000Z | 2022-03-23T20:18:07.000Z | ## tanzu secret registry list
Lists all v1/Secret of type kubernetes.io/dockerconfigjson and checks for the associated SecretExport with the same name
```
tanzu secret registry list [flags]
```
### Examples
```
# List registry secrets across all namespaces
tanzu registry secret list -A
# List registry secrets from specified namespace
tanzu registry secret list -n test-ns
# List registry secrets in json output format
tanzu registry secret list -n test-ns -o json
```
### Options
```
-A, --all-namespaces If present, list registry secrets across all namespaces, optional
-h, --help help for list
-o, --output string Output format (yaml|json|table), optional
```
### Options inherited from parent commands
```
--kubeconfig string The path to the kubeconfig file, optional
-n, --namespace string Target namespace for the registry secret, optional (default "default")
--verbose int32 Number for the log level verbosity(0-9)
```
### SEE ALSO
* [tanzu secret registry](tanzu_secret_registry.md) - Registry secret operations
###### Auto generated by spf13/cobra on 5-Nov-2021
| 26.431818 | 120 | 0.698194 | eng_Latn | 0.87967 |
c064b9a907bcc75cdd602e07d337d89083409cac | 966 | md | Markdown | content/publication/tebo-2019nc/index.md | agtebo/academic-kickstart | 3c8102694c28da94e5286c6f7c600c58701e88e1 | [
"MIT"
] | null | null | null | content/publication/tebo-2019nc/index.md | agtebo/academic-kickstart | 3c8102694c28da94e5286c6f7c600c58701e88e1 | [
"MIT"
] | null | null | null | content/publication/tebo-2019nc/index.md | agtebo/academic-kickstart | 3c8102694c28da94e5286c6f7c600c58701e88e1 | [
"MIT"
] | null | null | null | +++
title = "A split fluorescent reporter with rapid and reversible complementation"
date = 2019-06-27
authors = ["**Alison G Tebo**", "Arnaud Gautier"]
publication_types = ["2"]
abstract = "Interactions between proteins play an essential role in metabolic and signaling pathways, cellular processes and organismal systems. We report the development of splitFAST, a fluorescence complementation system for the visualization of transient protein-protein interactions in living cells. Engineered from the fluorogenic reporter FAST (Fluorescence-Activating and absorption-Shifting Tag), which specifically and reversibly binds fluorogenic hydroxybenzylidene rhodanine (HBR) analogs, splitFAST displays rapid and reversible complementation, allowing the real-time visualization of both the formation and the dissociation of a protein assembly."
featured = false
publication = "*Nature Communications*"
url_pdf = "https://www.nature.com/articles/s41467-019-10855-0"
+++
| 80.5 | 661 | 0.809524 | eng_Latn | 0.979522 |
c064eb8e433bc0166c94931cc87bdf2dba96bbe7 | 118 | md | Markdown | README.md | jaymickey/blog | 175154405264729806402cd9d399475d04aada23 | [
"MIT"
] | 2 | 2021-06-02T03:31:27.000Z | 2022-01-24T14:24:55.000Z | README.md | jaymickey/blog | 175154405264729806402cd9d399475d04aada23 | [
"MIT"
] | null | null | null | README.md | jaymickey/blog | 175154405264729806402cd9d399475d04aada23 | [
"MIT"
] | 4 | 2019-11-11T08:24:04.000Z | 2021-05-28T00:55:54.000Z | # Personal Website
## <https://mickey.dev>
This repo holds my personal website build with [Hugo](httpa://gohugo.io). | 23.6 | 73 | 0.720339 | eng_Latn | 0.433508 |
c065cfd1838c23066376cb7510e54d1bca200318 | 4,273 | md | Markdown | README.md | bradsheppard/crypto-sma | eb3d67b7048aff7cc82c1cce0f96690ecfefac77 | [
"MIT"
] | 4 | 2018-03-22T14:20:00.000Z | 2019-10-21T10:19:42.000Z | README.md | bradsheppard/crypto-sma | eb3d67b7048aff7cc82c1cce0f96690ecfefac77 | [
"MIT"
] | null | null | null | README.md | bradsheppard/crypto-sma | eb3d67b7048aff7cc82c1cce0f96690ecfefac77 | [
"MIT"
] | null | null | null | crypto-sma
=============
[![npm][npm-image]][npm-url]
[![travis][travis-image]][travis-url]
[npm-image]: https://badge.fury.io/js/crypto-sma.svg
[npm-url]: https://www.npmjs.com/package/crypto-sma
[travis-image]: https://travis-ci.org/bradsheppard/crypto-sma.svg?branch=master
[travis-url]: https://travis-ci.org/bradsheppard/crypto-sma
Install
-------
npm install --save crypto-sma
Usage
-----
crypto-sma is a node module for calculating the SMA (Simple Moving Average) and Bollinger Bands of a crypto currency over
a specified number of days. This node module module uses async function, and as such, requires a version of Node.js supporting this.
### Methods
### `currentPrice()`
Gets the price of the crypto currency in the specified currency.
`currentPrice(coin, currency)`
- `coin` (String) Represents the symbol of the coin.
- `currency` (String) Represents the currency to use for returning the price.
- `Returns` (Number) The price.
```js
var cryptoSMA = require('crypto-sma');
// Usage:
getBitcoinPrice = async () => {
var price = await cryptoSMA.currentPrice('BTC', 'CAD');
console.log(price);
};
getBitcoinPrice();
```
### `movingAverage()`
Calculates the specified SMA (Simple Moving Average) of a crypto currency.
`movingAverage(coin, currency, options)`
- `coin` (String) Represents the symbol of the coin.
- `currency` (String) Represents the currency to use for returning the moving average.
- `options` (Object)
- `days` (Number) The number of days to use when calculating the moving average.
- `offset` (Number) By default the offset used will be zero, meaning the days used to calculate
the moving average will be up to the current day. If offset is used, the days will instead be up to the current
day minus the offset.
- `Returns` (Number) The moving average.
```js
var cryptoSMA = require('crypto-sma');
// Usage:
getMovingAverage = async () => {
var price = await cryptoSMA.movingAverage('BTC', 'CAD', { days: 5, offset: 2 });
console.log(price);
};
getMovingAverage();
```
### `upperBollingerBand()`
Calculates the upper Bollinger Band of the crypto currency based on the given number of days, offset and k value.
(movingAverage + k * standardDeviation).
`upperBollingerBand(coin, currency, options)`
- `coin` (String) Represents the symbol of the coin.
- `currency` (String) Represents the currency to use for returning the moving average.
- `options` (Object)
- `days` (Number) The number of days to use when calculating the moving average.
- `offset` (Number) By default the offset used will be zero, meaning the days used to calculate
the moving average will be up to the current day. If offset is used, the days will instead be up to the current
day minus the offset.
- `k` (Number) The k value used for the Bollinger band calculation.
- `Returns` (Number) The upper Bollinger Band.
```js
var cryptoSMA = require('crypto-sma');
// Usage:
var getUpperBollingerBand = async () => {
var result = await cryptoSMA.upperBollingerBand('BTC', 'CAD', { days: 4, offset: 2, k: 2});
console.log(result);
};
getUpperBollingerBand();
```
### `lowerBollingerBand()`
Calculates the lower Bollinger Band of the crypto currency based on the given number of days, offset and k value.
(movingAverage - k * standardDeviation).
`lowerBollingerBand(coin, currency, options)`
- `coin` (String) Represents the symbol of the coin.
- `currency` (String) Represents the currency to use for returning the moving average.
- `options` (Object)
- `days` (Number) The number of days to use when calculating the moving average.
- `offset` (Number) By default the offset used will be zero, meaning the days used to calculate
the moving average will be up to the current day. If offset is used, the days will instead be up to the current
day minus the offset.
- `k` (Number) The k value used for the Bollinger band calculation.
- `Returns` (Number) The lower Bollinger Band.
```js
var cryptoSMA = require('crypto-sma');
// Usage:
var getLowerBollingerBand = async () => {
var result = await cryptoSMA.lowerBollingerBand('BTC', 'CAD', { days: 4, offset: 2, k: 2});
console.log(result);
};
getLowerBollingerBand();
```
## License
[MIT](LICENSE.md)
| 31.651852 | 132 | 0.709104 | eng_Latn | 0.968203 |
c0666a504dd5cf1b8a5cfd0ef7f11d8f5219ae9f | 32 | md | Markdown | README.md | BrunoAchon/Node.Vue.MontyHall | 76ea8af012c6df98f13d58ac56ce33748d261c71 | [
"MIT"
] | null | null | null | README.md | BrunoAchon/Node.Vue.MontyHall | 76ea8af012c6df98f13d58ac56ce33748d261c71 | [
"MIT"
] | null | null | null | README.md | BrunoAchon/Node.Vue.MontyHall | 76ea8af012c6df98f13d58ac56ce33748d261c71 | [
"MIT"
] | null | null | null | # Node.Vue.MontyHall
Node + Vue
| 10.666667 | 20 | 0.71875 | yue_Hant | 0.697658 |
c06791194f4a1af3485b5298e327c8aa4246e808 | 4,234 | markdown | Markdown | _posts/2016-05-27-my_beginning_interest_with_coding.markdown | mekowalski/mekowalski.github.io | 8b792edc36283a61633f587d240757e7a6c85db6 | [
"MIT"
] | null | null | null | _posts/2016-05-27-my_beginning_interest_with_coding.markdown | mekowalski/mekowalski.github.io | 8b792edc36283a61633f587d240757e7a6c85db6 | [
"MIT"
] | null | null | null | _posts/2016-05-27-my_beginning_interest_with_coding.markdown | mekowalski/mekowalski.github.io | 8b792edc36283a61633f587d240757e7a6c85db6 | [
"MIT"
] | null | null | null | ---
layout: post
title: "My Beginning Interest with Coding"
date: 2016-05-27 15:56:23 -0400
---
I began looking into becoming a programmer for two reasons: Karlie Kloss and where I live.
I was going through a moment where nothing was changing. This was neither good nor bad it was just unproductive and boring. I managed a women's clothing boutique and I loved what I did there. I was creative with selecting clothes and accessories to bring in. I was creative with how to display the store to keep customers interested. I was creative on window displays, especially when there was a holiday or town event going on. This all helped me express my creativity in a fun environment. I also had a great social setting that being relating with customers, helping them find the perfect heels to go with their outfit and helping them explore options they had yet to consider. While this was all good, I had reach my highest potential of management at the boutique. This is where I stopped growing as an indivual and as a professional.
At the boutique we displayed many different magazines for customers to browse. One of which was a Glamour magazine with Karlie Kloss on the cover. Being immersed in fashion, I knew who she was: a model the world knew but that's all I knew. I picked up the magazine mainly to look at photographed editorials and maybe read an article or two, then I came across Karlie's interview with Glamour. She touched on many topics but what struck me was her enthusiasm with coding. I was kind of surprised and even more interested with her at this point. But what she spoke of, empowering young women with coding, made me think of how I can contribute into a community and also help others grow. This kindled a new idea for me, an idea that I had been looking for while stagnant at my position. While at work, during slow moments, I would browse online fashion streams and one was Elle magazine. I, again, came across Karlie, coding and a new venture. The venture of coding fully at your own pace with a young, successful school, FlatIron School. That's when my kindling became a small ignite for new adventures.
I am always up for new adventures. They help you grow, take to places, let you breathe in new perspectives. I have this mindset because of where I live.
I reside in the mountains in Southwest Colorado. I have been inspired and fortunate to live in a gorgeous area where you are surrounded by beauty. With this beauty comes many adventures, seasons and challenges. I wanted to dive into programming to better myself, challenge my intellectual strengths to be a better individual and worker. I have been fortunate to live in a place while working one job. But because of working one job, I have also reached my highest potential where I am unable to grow myself. Therefore I began seeking coding because, as I have already encountered, it has been a new adventure. A great challenge, I am so excited when I learn something new. I share it with those around me and they can see my excitement on learning an entirely new language that is already developing my life for the better. I want to become a programmer to seek new adventures, meet new faces and offer my personal insights to those I meet. This has been a new interest that has revived my passion for life, I cannot quit thinking about it and I want to be fully immersed in it. I mean how else do you learn a foreign tongue if you're not fully in the culture? I'm ready to dig into a new culture.
### HAPPY CODING, malind
| 162.846154 | 1,209 | 0.771375 | eng_Latn | 0.999396 |
c067c20081f4a56134e5cf05607097213f96a407 | 2,151 | md | Markdown | docs/framework/unmanaged-api/metadata/imetadataimport2-getmethodspecprops-method.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/metadata/imetadataimport2-getmethodspecprops-method.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/unmanaged-api/metadata/imetadataimport2-getmethodspecprops-method.md | cihanyakar/docs.tr-tr | 03b6c8998a997585f61b8be289df105261125239 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: IMetaDataImport2::GetMethodSpecProps Metodu
ms.date: 03/30/2017
api_name:
- IMetaDataImport2.GetMethodSpecProps
api_location:
- mscoree.dll
api_type:
- COM
f1_keywords:
- IMetaDataImport2::GetMethodSpecProps
helpviewer_keywords:
- GetMethodSpecProps method [.NET Framework metadata]
- IMetaDataImport2::GetMethodSpecProps method [.NET Framework metadata]
ms.assetid: 9544b711-e669-4eaf-8630-ee862e5e4489
topic_type:
- apiref
author: mairaw
ms.author: mairaw
ms.openlocfilehash: 3249ad76c428752c91540e135bc978d3fe835de1
ms.sourcegitcommit: 3d5d33f384eeba41b2dff79d096f47ccc8d8f03d
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 05/04/2018
ms.locfileid: "33448139"
---
# <a name="imetadataimport2getmethodspecprops-method"></a>IMetaDataImport2::GetMethodSpecProps Metodu
Belirtilen MethodSpec tarafından başvurulan meta veri imzası belirtecini alır.
## <a name="syntax"></a>Sözdizimi
```
HRESULT GetMethodSpecProps (
[in] mdMethodSpec mi,
[out] mdToken *tkParent,
[out] PCCOR_SIGNATURE *ppvSigBlob,
[out] ULONG *pcbSigBlob
);
```
#### <a name="parameters"></a>Parametreler
`mi`
[in] Örnek oluşturma yönteminin temsil eden bir MethodSpec belirteci.
`tkParent`
[out] Yöntem tanımını temsil eden MethodDef veya MethodRef belirteci için bir işaretçi.
`ppvSigBlob`
[out] Yönteminin ikili meta verileri imza için bir işaretçi.
`pcbSigBlob`
[out] Bayt olarak boyutu, `ppvSigBlob`.
## <a name="requirements"></a>Gereksinimler
**Platformlar:** bkz [sistem gereksinimleri](../../../../docs/framework/get-started/system-requirements.md).
**Başlık:** Cor.h
**Kitaplığı:** MsCorEE.dll kaynak olarak kullanılır
**.NET framework sürümleri:** [!INCLUDE[net_current_v20plus](../../../../includes/net-current-v20plus-md.md)]
## <a name="see-also"></a>Ayrıca Bkz.
[IMetaDataImport2 Arabirimi](../../../../docs/framework/unmanaged-api/metadata/imetadataimport2-interface.md)
[IMetaDataImport Arabirimi](../../../../docs/framework/unmanaged-api/metadata/imetadataimport-interface.md)
| 32.590909 | 112 | 0.720595 | tur_Latn | 0.415412 |
c067c47e540ecf73b9bc872f8ea24e0abdea1a67 | 39,956 | md | Markdown | security-updates/SecurityBulletins/2014/ms14-039.md | eltociear/security-updates.ko-kr | 3cc53b06134d150c4db82c9ea2605be13e4659ff | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T20:16:19.000Z | 2020-05-19T20:16:19.000Z | security-updates/SecurityBulletins/2014/ms14-039.md | eltociear/security-updates.ko-kr | 3cc53b06134d150c4db82c9ea2605be13e4659ff | [
"CC-BY-4.0",
"MIT"
] | 232 | 2017-12-12T16:03:13.000Z | 2020-03-20T16:31:01.000Z | security-updates/SecurityBulletins/2014/ms14-039.md | eltociear/security-updates.ko-kr | 3cc53b06134d150c4db82c9ea2605be13e4659ff | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-12-06T22:49:08.000Z | 2021-11-15T11:06:35.000Z | ---
TOCTitle: 'MS14-039'
Title: 'Microsoft 보안 공지 MS14-039 - 중요'
ms:assetid: 'ms14-039'
ms:contentKeyID: 62554734
ms:mtpsurl: 'https://technet.microsoft.com/ko-KR/library/ms14-039(v=Security.10)'
---
Microsoft 보안 공지 MS14-039 - 중요
===================================
화상 키보드의 취약점으로 인한 권한 상승 문제점(2975685)
-------------------------------------------------------
게시된 날짜: 2014년 7월 9일 | 업데이트 날짜: 2014년 7월 17일
**버전:** 1.1
일반 정보
---------
### 요약
이 보안 업데이트는 비공개적으로 보고된 Microsoft Windows의 취약점을 해결합니다. 이 취약점으로 인해 공격자가 낮은 무결성 프로세스에서 취약점을 악용해 화상 키보드(OSK)를 실행하고 대상 시스템에 특수하게 조작된 프로그램을 업로드할 경우 권한 상승이 허용될 수 있습니다.
이 보안 업데이트의 심각도는 Windows Server 2003을 제외한 지원 대상인 모든 Windows 릴리스에 대해 중요입니다. 자세한 내용은 **영향을 받는 소프트웨어 및 영향을 받지 않는 소프트웨어** 섹션을 참조하십시오.
이 보안 업데이트는 일부 프로그램이 무결성 수준이 다른 프로그램과 통신하는 방식을 수정하여 취약점을 해결합니다. 취약점에 대한 자세한 내용은 이 공지의 특정 취약점에 대한 **자주 제기되는 질문 사항(FAQ)** 하위 섹션을 참조하십시오.
**권장 사항.** 대부분의 고객은 자동 업데이트를 사용하고 있기 때문에 따로 조치를 취할 필요가 없습니다. 이 보안 업데이트가 자동으로 다운로드되고 설치됩니다. 자동 업데이트의 특정 구성 옵션에 대한 자세한 내용은 [Microsoft 기술 자료 문서 294871](https://support.microsoft.com/kb/294871)을 참조하십시오. 자동 업데이트를 사용하고 있지 않은 고객은 [자동 업데이트 설정 또는 해제](https://go.microsoft.com/fwlink/?linkid=398470)(영문)의 단계를 사용하여 자동 업데이트를 사용할 수 있습니다.
엔터프라이즈 설치의 경우 또는 이 보안 업데이트를 수동으로 설치하려는 관리자 및 최종 사용자의 경우(자동 업데이트를 사용하고 있지 않은 고객 포함) 고객이 업데이트 관리 소프트웨어를 사용하거나 [Microsoft 업데이트](https://go.microsoft.com/fwlink/?linkid=40747) 서비스를 통해 업데이트를 확인하여 가능한 빨리 업데이트를 적용하는 것이 좋습니다. 이 공지의 **영향을 받는 소프트웨어** 표에 있는 다운로드 링크를 통해서도 업데이트할 수 있습니다.
자세한 지침은 이 공지의 **검색, 배포 도구 및 지침** 섹션을 참조하십시오.
### 기술 자료 문서
- **기술 자료 문서**: [**2975685**](https://support.microsoft.com/kb/2975685)
- **파일 정보**: 예
- **SHA1/SHA2 해시**: 예
- **알려진 문제점**: 예
영향을 받는 소프트웨어 및 영향을 받지 않는 소프트웨어
-----------------------------------------------------
<span id="sectionToggle0"></span>
다음 소프트웨어는 테스트를 거쳐 영향을 받는 버전 또는 에디션이 확인되었습니다. 다른 버전은 지원 기간이 끝났거나 영향을 받지 않습니다. 사용 중인 소프트웨어 버전에 대한 지원 기간을 확인하려면 [Microsoft 지원 기간 정책 웹 사이트](https://go.microsoft.com/fwlink/?linkid=21742)를 참조하십시오.
**영향을 받는 소프트웨어**
<p> </p>
<table style="border:1px solid black;">
<tr>
<td style="border:1px solid black;">
**운영 체제**
</td>
<td style="border:1px solid black;">
**최대 보안 영향**
</td>
<td style="border:1px solid black;">
**전체 심각도**
</td>
<td style="border:1px solid black;">
**대체된 업데이트**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="4">
**Windows Vista**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Vista 서비스 팩 2](https://www.microsoft.com/download/details.aspx?familyid=ff87fab9-2ef3-4d16-bcd7-a1f20ddf10a6&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Vista x64 Edition 서비스 팩 2](https://www.microsoft.com/download/details.aspx?familyid=c5cbea19-e0af-466f-99a4-bd1a84675e13&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="4">
**Windows Server 2008**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2008(32비트 시스템용) 서비스 팩 2](https://www.microsoft.com/download/details.aspx?familyid=4cba798f-7f47-4faf-871b-12938b1ae975&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2008(x64 기반 시스템용) 서비스 팩 2](https://www.microsoft.com/download/details.aspx?familyid=8b4fbdd0-3bf7-43fe-aa5c-6e7dd3caa8cd&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2008(Itanium 기반 시스템용) 서비스 팩 2](https://www.microsoft.com/download/details.aspx?familyid=be1640bf-6193-422d-bcb8-8b7e7ae900f6)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="4">
**Windows 7**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows 7(32비트 시스템용) 서비스 팩 1](https://www.microsoft.com/download/details.aspx?familyid=983472e1-86c5-4dcf-9ee2-0806d0be0e02&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows 7(x64 기반 시스템용) 서비스 팩 1](https://www.microsoft.com/download/details.aspx?familyid=28171ee6-6ba1-4f7c-a486-de4658e7ee1c&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="4">
**Windows Server 2008 R2**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2008 R2(x64 기반 시스템용) 서비스 팩 1](https://www.microsoft.com/download/details.aspx?familyid=e3bf1294-a462-43cf-8d86-778f4b529a84&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2008 R2(Itanium 기반 시스템용) 서비스 팩 1](https://www.microsoft.com/download/details.aspx?familyid=7245d363-1667-4262-a7c2-155759450968)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="4">
**Windows 8 및 Windows 8.1**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows 8(32비트 시스템용)](https://www.microsoft.com/download/details.aspx?familyid=0f93b9f1-4c03-4a44-ac1d-37e5c3eaf7dd&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows 8(x64 기반 시스템용)](https://www.microsoft.com/download/details.aspx?familyid=75176c26-ce4c-4002-8c02-6ffd74246b7d&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows 8.1(32비트 시스템용)](https://www.microsoft.com/download/details.aspx?familyid=741029de-77ee-4be7-ab89-098029ca7118&displaylang=ko)<sup>[1]</sup>
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 8.1(32비트 시스템용)<sup>[2]</sup>
(2973906)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows 8.1(x64 기반 시스템용)](https://www.microsoft.com/download/details.aspx?familyid=95295162-2f5b-46f6-a07e-c696c6e987ab&displaylang=ko)<sup>[1]</sup>
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 8.1(x64 기반 시스템용)<sup>[2]</sup>
(2973906)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="4">
**Windows Server 2012 및 Windows Server 2012 R2**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2012](https://www.microsoft.com/download/details.aspx?familyid=c8d92461-cfab-4a80-ab3a-19dfbdaa11e6&displaylang=ko)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2012 R2](https://www.microsoft.com/download/details.aspx?familyid=089c739c-b1da-4605-b6d1-e3064123c18e&displaylang=ko)<sup>[1]</sup>
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2012 R2<sup>[2]</sup>
(2973906)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="4">
**Windows RT 및 Windows RT 8.1**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows RT<sup>[3]</sup>
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows RT 8.1<sup>[3]</sup>
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="4">
**Server Core 설치 옵션**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2008(32비트 시스템용) 서비스 팩 2](https://www.microsoft.com/download/details.aspx?familyid=4cba798f-7f47-4faf-871b-12938b1ae975&displaylang=ko)(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2008(x64 기반 시스템용) 서비스 팩 2](https://www.microsoft.com/download/details.aspx?familyid=8b4fbdd0-3bf7-43fe-aa5c-6e7dd3caa8cd&displaylang=ko)(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2008 R2(x64 기반 시스템용) 서비스 팩 1](https://www.microsoft.com/download/details.aspx?familyid=e3bf1294-a462-43cf-8d86-778f4b529a84&displaylang=ko)(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2012](https://www.microsoft.com/download/details.aspx?familyid=c8d92461-cfab-4a80-ab3a-19dfbdaa11e6&displaylang=ko)(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Windows Server 2012 R2](https://www.microsoft.com/download/details.aspx?familyid=089c739c-b1da-4605-b6d1-e3064123c18e&displaylang=ko)(Server Core 설치)<sup>[1]</sup>
(2973201)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2012 R2(Server Core 설치)<sup>[2]</sup>
(2973906)
</td>
<td style="border:1px solid black;">
권한 상승
</td>
<td style="border:1px solid black;">
중요
</td>
<td style="border:1px solid black;">
[MS14-015](https://go.microsoft.com/fwlink/?linkid=392067)의 2930275
</td>
</tr>
</table>
<sup>[1]</sup>이 업데이트는 2919355 업데이트가 설치된 시스템에 제공됩니다. 자세한 내용은 **업데이트 FAQ**를 참조하십시오.
<sup>[2]</sup>이 업데이트는 2919355 업데이트가 설치되지 않은 시스템에 제공됩니다. 이 업데이트는 Microsoft 다운로드 센터를 통해 다운로드할 수 없습니다. 자세한 내용은 **업데이트 FAQ**를 참조하십시오.
<sup>[3]</sup>이 업데이트는 [Windows Update](https://go.microsoft.com/fwlink/?linkid=21130)를 통해 제공됩니다.
**영향을 받지 않는 소프트웨어**
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="100%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>운영 체제</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Windows Server 2003 서비스 팩 2</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Windows Server 2003 x64 Edition 서비스 팩 2</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Windows Server 2003 SP2(Itanium 기반 시스템용)</td>
</tr>
</tbody>
</table>
업데이트 FAQ
------------
<span id="sectionToggle1"></span>
**Windows 8.1 및 Windows Server 2012 R2에 대한 여러 업데이트가 나열되어 있습니다. 업데이트를 모두 설치해야 합니까?**
아니요. 시스템의 업데이트 수신 방법 구성에 따라 Windows 8.1 또는 Windows Server 2012 R2에 대한 업데이트 중 1개만 적용될 수 있습니다.
Windows 8.1 또는 Windows Server 2012 R2를 실행하는 시스템:
2973201 업데이트는 2919355(Windows 8.1 업데이트) 업데이트가 이미 설치된 시스템에 제공됩니다.
2973906 업데이트는 2919355 업데이트가 설치되지 않은 시스템에 제공됩니다. 2973906 업데이트는 Windows Server Update Services(WSUS), Windows Intune 또는 System Center Configuration Manager를 사용하여 업데이트를 관리하는 고객만 사용할 수 있습니다.
**Windows 8.1, Windows Server 2012 R2 및 Windows RT 8.1의 경우 2973201 업데이트의 전제 조건이 있습니까?**
예. Windows 8.1, Windows Server 2012 R2 또는 Windows RT 8.1을 실행하는 고객은 2973201 업데이트를 설치하기 전에 먼저 2014년 4월에 발표된 2919355(Windows 8.1 업데이트) 업데이트를 설치해야 합니다. 이 필수 업데이트에 대한 자세한 내용은 [Microsoft 기술 자료 문서 2919355](https://support.microsoft.com/kb/2919355)를 참조하십시오.
**이 업데이트에 기능에 대한 보안 관련 변경 사항이 포함되어 있습니까?**
예. 이 업데이트는 개발자가 하위 수준 키보드 및 마우스 입력 후크를 작성할 때 사용하는 구조에 새로운 보안 관련 플래그를 추가합니다. 기능 변경에 대한 자세한 내용은 [KBDLLHOOKSTRUCT 구조](https://msdn.microsoft.com/ko-kr/library/windows/desktop/ms644967(v=vs.85).aspx)(영문) 및 [MSLLHOOKSTRUCT 구조](https://msdn.microsoft.com/ko-kr/library/windows/desktop/ms644970(v=vs.85).aspx)(영문)를 참조하십시오.
**이 보안 공지에서 설명하는 소프트웨어의 이전 버전을 사용하고 있습니다. 어떻게 해야 합니까?**
이 공지에 나열된 영향을 받는 소프트웨어는 테스트를 거쳐 해당 릴리스가 영향을 받는지 확인되었습니다. 다른 버전은 지원 기간이 끝났습니다. 제품 지원 기간에 대한 자세한 내용은 [Microsoft 지원 기간 정책](https://go.microsoft.com/fwlink/?linkid=21742) 웹 사이트를 참조하십시오.
이전 버전의 소프트웨어를 사용 중인 고객은 이후의 취약점에 노출되지 않도록 지원되는 버전으로 마이그레이션을 우선적으로 고려하십시오. 사용 중인 소프트웨어 버전에 대한 지원 기간을 확인하려면 [지원 기간 제품 선택](https://go.microsoft.com/fwlink/?linkid=169555)을 참조하십시오. 이러한 소프트웨어 버전의 서비스 팩에 대한 자세한 내용은 [서비스 팩 지원 기간 정책](https://go.microsoft.com/fwlink/?linkid=89213)을 참조하십시오.
이전 버전의 소프트웨어에 대한 사용자 지정 지원이 필요한 고객은 자신의 Microsoft 계정 관리 팀 담당자나 TAM(기술 계정 관리자) 또는 해당 Microsoft 파트너 담당자에게 사용자 지정 지원 옵션에 대해 문의하십시오. Alliance, Premier 또는 Authorized Contract가 없는 고객은 해당 지역의 Microsoft 판매처에 문의하십시오. 연락처 정보는 [Microsoft 정보](https://go.microsoft.com/fwlink/?linkid=33329) 웹 사이트를 방문하여 Contact Information 목록에서 국가를 선택한 다음 **Go**를 클릭하면 나타나는 전화 번호 목록을 참조하십시오. 전화를 할 경우에는 해당 지역의 프리미어 지원 영업 담당자와 상담을 요청하십시오. 자세한 내용은 [Microsoft 지원 기간 정책 FAQ](https://go.microsoft.com/fwlink/?linkid=169557)를 참조하십시오.
심각도 및 취약점
----------------
<span id="sectionToggle2"></span>
다음의 심각도는 취약점의 잠재적인 최대 영향을 가정합니다. 이 보안 공지 발표 후 30일 이내의 심각도 및 보안 영향과 관련된 취약점 악용 가능성에 대해서는 [7월 공지 요약](https://technet.microsoft.com/library/security/ms14-jul)의 악용 가능성 인덱스를 참조하십시오. 자세한 내용은 [Microsoft 악용 가능성 인덱스](https://technet.microsoft.com/security/cc998259)를 참조하십시오.
<p> </p>
<table style="border:1px solid black;">
<tr>
<td style="border:1px solid black;" colspan="3">
**영향을 받는 소프트웨어별 취약점 심각도 및 최대 심각도 영향**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**영향을 받는 소프트웨어**
</td>
<td style="border:1px solid black;">
**화상 키보드 권한 상승 취약점(CVE-2014-2781)**
</td>
<td style="border:1px solid black;">
**전체 심각도**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows Vista**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Vista 서비스 팩 2
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Vista x64 Edition 서비스 팩 2
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows Server 2008**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008(32비트 시스템용) 서비스 팩 2
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008(x64 기반 시스템용) 서비스 팩 2
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008(Itanium 기반 시스템용) 서비스 팩 2
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows 7**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 7(32비트 시스템용) 서비스 팩 1
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 7(x64 기반 시스템용) 서비스 팩 1
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows Server 2008 R2**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 R2(x64 기반 시스템용) 서비스 팩 1
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 R2(Itanium 기반 시스템용) 서비스 팩 1
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows 8 및 Windows 8.1**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 8(32비트 시스템용)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 8(x64 기반 시스템용)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 8.1(32비트 시스템용)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 8.1(32비트 시스템용)
(2973906)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 8.1(x64 기반 시스템용)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows 8.1(x64 기반 시스템용)
(2973906)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows Server 2012 및 Windows Server 2012 R2**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2012
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2012 R2
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2012 R2
(2973906)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Windows RT 및 Windows RT 8.1**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows RT
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows RT 8.1
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;" colspan="3">
**Server Core 설치 옵션**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008(32비트 시스템용) 서비스 팩 2(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008(x64 기반 시스템용) 서비스 팩 2(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2008 R2(x64 기반 시스템용) 서비스 팩 1(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2012(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2012 R2(Server Core 설치)
(2973201)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Windows Server 2012 R2(Server Core 설치)
(2973906)
</td>
<td style="border:1px solid black;">
**중요**
권한 상승
</td>
<td style="border:1px solid black;">
**중요**
</td>
</tr>
</table>
화상 키보드 권한 상승 취약점(CVE-2014-2781)
-------------------------------------------
<span id="sectionToggle3"></span>
화상 키보드에 로컬 권한 상승이 허용될 수 있는 취약점이 존재합니다.
이 취약점을 CVE(Common Vulnerabilities and Exposures) 목록의 표준 항목으로 보려면 [CVE-2014-2781](https://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2014-2781)(영문)을 참조하십시오.
### 완화 요소
이 취약점에 대해 확인된 완화 요소가 없습니다.
### 대안
이 취약점에 대한 대안을 확인하지 못했습니다.
### FAQ
**이 취약점을 악용하면 어느 작업까지 가능합니까?**
이 취약점은 로컬 권한 상승 취약점입니다.
**취약점의 원인은 무엇입니까?**
이 취약점은 낮은 무결성 프로세스 컨텍스트에서 화상 키보드를 실행할 경우 발생합니다.
**화상 키보드(OSK)란 무엇입니까?**
화상 키보드(OSK)는 사용자가 PC에서 물리적인 외부 키보드 없이도 텍스트를 입력할 수 있도록 해주는 Microsoft Windows의 액세스 편의를 위한 도구입니다. OSK에는 터치 스크린, 마우스 또는 기타 포인팅 장치로 액세스할 수 있는 모든 표준 키가 포함된 비주얼 키보드가 표시됩니다.
**공격자는 취약점을 악용하여 무엇을 할 수 있습니까?**
이 취약점 악용에 성공한 공격자는 현재 사용자와 같은 무결성 수준에서 임의 프로그램을 실행할 수 있습니다.
**공격자는 이러한 취약점을 어떻게 악용합니까?**
이 취약점을 악용하려면 공격자는 우선 낮은 무결성 프로세스의 취약점을 이용해 화상 키보드를 실행한 후 대상 시스템에 특수하게 조작된 프로그램을 업로드해야 합니다.
**취약점으로 인해 주로 공격 받을 위험이 있는 시스템은 무엇입니까?**
워크스테이션과 터미널 서버가 주로 위험합니다. 관리자가 사용자가 서버에 로그온하여 프로그램을 실행할 수 있도록 허용할 경우, 서버가 더 위험할 수 있습니다. 가장 좋은 방법은 이러한 기능을 허용하지 않는 것입니다.
**업데이트는 어떤 기능을 수행합니까?**
이 업데이트는 일부 프로그램이 무결성 수준이 다른 프로그램과 통신하는 방식을 수정하여 취약점을 해결합니다. 이 업데이트를 통해 구현된 기능 변경에 대한 자세한 내용은 [KBDLLHOOKSTRUCT 구조](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644967(v=vs.85).aspx) 및 [MSLLHOOKSTRUCT 구조](https://msdn.microsoft.com/en-us/library/windows/desktop/ms644970(v=vs.85).aspx)를 참조하십시오.
**이 보안 공지를 게시했을 때 이 취약점이 공개되어 있었습니까?**
아니요. Microsoft는 조정된 취약점 공개를 통해 이 취약점 관련 정보를 입수하였습니다.
**이 보안 공지를 게시했을 때 Microsoft는 이 취약점이 악용되었다는 보고를 받았습니까?**
아니요. Microsoft는 이 보안 공지를 처음에 게시했을 때 이 취약점이 고객을 공격하는 데 공개적으로 사용되었다는 정보를 확인하지 못했습니다.
검색, 배포 도구 및 지침
-----------------------
<span id="sectionToggle4"></span>
관리자가 보안 업데이트를 배포하는 데 도움이 되는 다양한 리소스가 존재합니다.
- 관리자는 MBSA(Microsoft Baseline Security Analyzer)를 사용하여 로컬 및 원격 시스템에서 누락된 보안 업데이트 및 일반적인 보안 구성 오류를 검색할 수 있습니다.
- WSUS(Windows Server Update Services), SMS(Systems Management Server), System Center Configuration Manager는 관리자가 보안 업데이트를 배포하는 데 도움이 됩니다.
- ACT(Application Compatibility Toolkit)에 포함되어 있는 UCE(Update Compatibility Evaluator) 구성 요소를 사용하면 설치된 응용 프로그램에 대한 Windows 업데이트 테스트 및 유효성 검사가 간소화됩니다.
여기에 나온 도구 및 사용 가능한 기타 도구에 대한 자세한 내용은 [보안 도구](https://technet.microsoft.com/security/cc297183)를 참조하십시오.
보안 업데이트 배포
------------------
<span id="sectionToggle5"></span>
### Windows Vista(모든 버전)
**참조 표**
다음 표에는 이 소프트웨어에 대한 보안 업데이트 정보가 포함되어 있습니다.
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>보안 업데이트 파일 이름</strong></td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Vista 32비트 에디션:<br />
<strong>Windows6.0-KB2973201-x86.msu</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Vista x64 에디션:<br />
<strong>Windows6.0-KB2973201-x64.msu</strong></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>설치 스위치</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/934307">Microsoft 기술 자료 문서 934307</a> 참조</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>다시 시작 요구 사항</strong></td>
<td style="border:1px solid black;">예, 이 보안 업데이트를 적용한 후에는 컴퓨터를 다시 시작해야 합니다.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>제거 정보</strong></td>
<td style="border:1px solid black;">WUSA.exe는 업데이트 제거를 지원하지 않습니다. WUSA에서 설치한 업데이트를 설치 제거하려면 <strong>제어판</strong>, <strong>보안</strong>을 차례로 클릭하십시오. Windows 업데이트에서 <strong>설치된 업데이트 보기</strong>를 클릭하고 업데이트 목록에서 선택합니다.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>파일 정보</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/2973201">Microsoft 기술 자료 문서 2973201</a> 참조</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>레지스트리 키 확인</strong></td>
<td style="border:1px solid black;"><strong>참고:</strong> 이 업데이트가 있는지 확인하는 레지스트리 키는 없습니다.</td>
</tr>
</tbody>
</table>
### Windows Server 2008(모든 에디션)
**참조 표**
다음 표에는 이 소프트웨어에 대한 보안 업데이트 정보가 포함되어 있습니다.
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>보안 업데이트 파일 이름</strong></td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Server 2008 32비트 에디션:<br />
<strong>Windows6.0-KB2973201-x86.msu</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Server 2008 x64 기반 에디션:<br />
<strong>Windows6.0-KB2973201-x64.msu</strong></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Server 2008 Itanium 기반 에디션:<br />
<strong>Windows6.0-KB2973201-ia64.msu</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>설치 스위치</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/934307">Microsoft 기술 자료 문서 934307</a> 참조</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>다시 시작 요구 사항</strong></td>
<td style="border:1px solid black;">예, 이 보안 업데이트를 적용한 후에는 컴퓨터를 다시 시작해야 합니다.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>제거 정보</strong></td>
<td style="border:1px solid black;">WUSA.exe는 업데이트 제거를 지원하지 않습니다. WUSA에서 설치한 업데이트를 설치 제거하려면 <strong>제어판</strong>, <strong>보안</strong>을 차례로 클릭하십시오. Windows 업데이트에서 <strong>설치된 업데이트 보기</strong>를 클릭하고 업데이트 목록에서 선택합니다.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>파일 정보</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/2973201">Microsoft 기술 자료 문서 2973201</a> 참조</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>레지스트리 키 확인</strong></td>
<td style="border:1px solid black;"><strong>참고:</strong> 이 업데이트가 있는지 확인하는 레지스트리 키는 없습니다.</td>
</tr>
</tbody>
</table>
### Windows 7(모든 에디션)
**참조 표**
다음 표에는 이 소프트웨어에 대한 보안 업데이트 정보가 포함되어 있습니다.
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>보안 업데이트 파일 이름</strong></td>
<td style="border:1px solid black;">지원 대상인 모든 Windows 7 32비트 에디션:<br />
<strong>Windows6.1-KB2973201-x86.msu</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows 7 x64 기반 에디션:<br />
<strong>Windows6.1-KB2973201-x64.msu</strong></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>설치 스위치</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/934307">Microsoft 기술 자료 문서 934307</a> 참조</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>다시 시작 요구 사항</strong></td>
<td style="border:1px solid black;">예, 이 보안 업데이트를 적용한 후에는 컴퓨터를 다시 시작해야 합니다.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>제거 정보</strong></td>
<td style="border:1px solid black;">WUSA에서 설치한 업데이트를 설치 제거하려면 /Uninstall 설치 스위치를 사용하거나 <strong>제어판</strong>, <strong>시스템 및 보안</strong>을 차례로 클릭한 후 Windows 업데이트에서 <strong>설치된 업데이트 보기</strong>를 클릭하고 업데이트 목록에서 선택합니다.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>파일 정보</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/2973201">Microsoft 기술 자료 문서 2973201</a> 참조</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>레지스트리 키 확인</strong></td>
<td style="border:1px solid black;"><strong>참고:</strong> 이 업데이트가 있는지 확인하는 레지스트리 키는 없습니다.</td>
</tr>
</tbody>
</table>
### Windows Server 2008 R2(모든 에디션)
**참조 표**
다음 표에는 이 소프트웨어에 대한 보안 업데이트 정보가 포함되어 있습니다.
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>보안 업데이트 파일 이름</strong></td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Server 2008 R2 x64 기반 에디션:<br />
<strong>Windows6.1-KB2973201-x64.msu</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Server 2008 R2 Itanium 기반 에디션:<br />
<strong>Windows6.1-KB2973201-ia64.msu</strong></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>설치 스위치</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/934307">Microsoft 기술 자료 문서 934307</a> 참조</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>다시 시작 요구 사항</strong></td>
<td style="border:1px solid black;">예, 이 보안 업데이트를 적용한 후에는 컴퓨터를 다시 시작해야 합니다.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>제거 정보</strong></td>
<td style="border:1px solid black;">WUSA에서 설치한 업데이트를 설치 제거하려면 /Uninstall 설치 스위치를 사용하거나 <strong>제어판</strong>, <strong>시스템 및 보안</strong>을 차례로 클릭한 후 Windows 업데이트에서 <strong>설치된 업데이트 보기</strong>를 클릭하고 업데이트 목록에서 선택합니다.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>파일 정보</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/2973201">Microsoft 기술 자료 문서 2973201</a> 참조</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>레지스트리 키 확인</strong></td>
<td style="border:1px solid black;"><strong>참고:</strong> 이 업데이트가 있는지 확인하는 레지스트리 키는 없습니다.</td>
</tr>
</tbody>
</table>
### Windows 8 및 Windows 8.1(모든 에디션)
**참조 표**
다음 표에는 이 소프트웨어에 대한 보안 업데이트 정보가 포함되어 있습니다.
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>보안 업데이트 파일 이름</strong></td>
<td style="border:1px solid black;">지원 대상인 모든 Windows 8 32비트 에디션:<br />
<strong>Windows8-RT-KB2973201-x86.msu</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows 8 x64 기반 에디션:<br />
<strong>Windows8-RT-KB2973201-x64.msu</strong></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows 8.1 32비트 에디션:<br />
<strong>Windows8.1-KB2973201-x86.msu</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows 8.1 x64 기반 에디션:<br />
<strong>Windows8.1-KB2973201-x64.msu</strong></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>설치 스위치</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/934307">Microsoft 기술 자료 문서 934307</a> 참조</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>다시 시작 요구 사항</strong></td>
<td style="border:1px solid black;">예, 이 보안 업데이트를 적용한 후에는 컴퓨터를 다시 시작해야 합니다.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>제거 정보</strong></td>
<td style="border:1px solid black;">WUSA에서 설치한 업데이트를 설치 제거하려면 /Uninstall 설치 스위치를 사용하거나 <strong>제어판</strong>, <strong>시스템 및 보안</strong>, <strong>Windows 업데이트</strong>를 차례로 클릭한 후 참고 항목 아래의 <strong>설치된 업데이트</strong>를 클릭하고 업데이트 목록에서 선택합니다.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>파일 정보</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/2973201">Microsoft 기술 자료 문서 2973201</a> 참조</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>레지스트리 키 확인</strong></td>
<td style="border:1px solid black;"><strong>참고:</strong> 이 업데이트가 있는지 확인하는 레지스트리 키는 없습니다.</td>
</tr>
</tbody>
</table>
### Windows Server 2012 및 Windows Server 2012 R2(모든 에디션)
**참조 표**
다음 표에는 이 소프트웨어에 대한 보안 업데이트 정보가 포함되어 있습니다.
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>보안 업데이트 파일 이름</strong></td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Server 2012 에디션:<br />
<strong>Windows8-RT-KB2973201-x64.msu</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><br />
</td>
<td style="border:1px solid black;">지원 대상인 모든 Windows Server 2012 R2 에디션:<br />
<strong>Windows8.1-KB2973201-x64.msu</strong></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>설치 스위치</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/934307">Microsoft 기술 자료 문서 934307</a> 참조</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>다시 시작 요구 사항</strong></td>
<td style="border:1px solid black;">예, 이 보안 업데이트를 적용한 후에는 컴퓨터를 다시 시작해야 합니다.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>제거 정보</strong></td>
<td style="border:1px solid black;">WUSA에서 설치한 업데이트를 설치 제거하려면 /Uninstall 설치 스위치를 사용하거나 <strong>제어판</strong>, <strong>시스템 및 보안</strong>, <strong>Windows 업데이트</strong>를 차례로 클릭한 후 참고 항목 아래의 <strong>설치된 업데이트</strong>를 클릭하고 업데이트 목록에서 선택합니다.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>파일 정보</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/2973201">Microsoft 기술 자료 문서 2973201</a> 참조</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>레지스트리 키 확인</strong></td>
<td style="border:1px solid black;"><strong>참고:</strong> 이 업데이트가 있는지 확인하는 레지스트리 키는 없습니다.</td>
</tr>
</tbody>
</table>
### Windows RT 및 Windows RT 8.1(모든 에디션)
**참조 표**
다음 표에는 이 소프트웨어에 대한 보안 업데이트 정보가 포함되어 있습니다.
<p> </p>
<table style="border:1px solid black;">
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>배포</strong></td>
<td style="border:1px solid black;">이러한 업데이트는 <a href="https://go.microsoft.com/fwlink/?linkid=21130">Windows Update</a>를 통해서만 제공됩니다.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>다시 시작 요구 사항</strong></td>
<td style="border:1px solid black;">예, 이 보안 업데이트를 적용한 후에는 컴퓨터를 다시 시작해야 합니다.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>제거 정보</strong></td>
<td style="border:1px solid black;"><strong>제어판</strong>, <strong>시스템 및 보안</strong>, <strong>Windows Update</strong>를 차례로 클릭한 후 참고 항목 아래의 <strong>설치된 업데이트</strong>를 클릭하고 업데이트 목록에서 선택합니다.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>파일 정보</strong></td>
<td style="border:1px solid black;"><a href="https://support.microsoft.com/kb/2973201">Microsoft 기술 자료 문서 2973201</a> 참조</td>
</tr>
</tbody>
</table>
감사의 말
---------
<span id="sectionToggle6"></span>
고객 보호를 위해 협력해 주신 다음 분들께 [감사](https://go.microsoft.com/fwlink/?linkid=21127)드립니다.
- 화상 키보드의 권한 상승 취약점(CVE-2014-2781)을 [HP](https://www.hpenterprisesecurity.com/products)(영문)의 [Zero Day Initiative](https://www.zerodayinitiative.com/)(영문)와 협력하여 보고해 주신 익명 연구자
기타 정보
---------
<span id="sectionToggle7"></span>
### MAPP(Microsoft Active Protections Program)
고객에 대한 보안을 강화하기 위해 Microsoft는 월별 보안 업데이트를 배포하기 전에 주요 보안 소프트웨어 제공업체에 취약점 정보를 제공합니다. 보안 소프트웨어 제공업체는 이 취약점 정보를 사용하여 안티바이러스, 네트워크 기반 침입 탐지 시스템 또는 호스트 기반 침임 방지 시스템 등 자사의 보안 소프트웨어나 장치를 통해 업데이트된 보호 기능을 고객에게 제공할 수 있습니다. 보안 소프트웨어 제공업체가 활성 보호 기능을 제공하는지 확인하려면 [Microsoft MAPP(Active Protections Program) 파트너](https://go.microsoft.com/fwlink/?linkid=215201)에 나열된 프로그램 파트너가 제공하는 활성 보호 기능 웹 사이트를 참조하십시오.
### 지원
**이 보안 업데이트에 대한 도움말 및 지원을 얻는 방법**
- 업데이트 설치 도움말: [Microsoft 업데이트에 대한 지원](https://support.microsoft.com/ph/6527)
- IT 전문가를 위한 보안 솔루션: [TechNet 보안 문제 해결 및 지원](https://technet.microsoft.com/security/bb980617.aspx)
- Windows를 실행하는 컴퓨터를 바이러스와 맬웨어로부터 보호: [바이러스 및 보안 솔루션 센터](https://support.microsoft.com/contactus/cu_sc_virsec_master)
- 국가별 현지 지원: [국가별 지원](https://support.microsoft.com/common/international.aspx)
### 부인
Microsoft 기술 자료에서 제공되는 정보는 어떠한 보증도 없이 "있는 그대로" 제공됩니다. Microsoft는 상품성 및 특정 목적에의 적합성에 대한 보증을 포함하여 명시적이거나 묵시적인 어떤 보증도 하지 않습니다. Microsoft Corporation 또는 그 공급자는 모든 직접적, 간접적, 부수적, 파생적 손해 또는 영업 이익 손실 또는 특수한 손실에 대하여 어떠한 경우에도 책임을 지지 않으며, 이는 Microsoft Corporation과 그 공급자가 그와 같은 손해의 가능성을 사전에 알고 있던 경우에도 마찬가지입니다. 일부 지역에서는 파생적 또는 부수적 손해에 대한 책임의 배제 또는 제한을 허용하지 않으므로 위 제한은 귀하에게 적용되지 않을 수도 있습니다.
### 개정 내역
- V1.0(2014년 7월 9일): 공지가 게시되었습니다.
- V1.1(2014년 7월 17일): **기술 자료 문서**의 알려진 문제점 항목이 "없음"에서 "예"로 업데이트되었습니다.
*2014년 7월 16일 11:13Z-07:00에 페이지가 생성되었습니다.*
| 25.035088 | 497 | 0.674092 | kor_Hang | 0.998201 |
c067c566dfa6fec109b402ae10ddf04ae2d8eb9a | 8,027 | md | Markdown | docs/standard/library-guidance/breaking-changes.md | dhernandezb/docs.es-es | cf1637e989876a55eb3c57002818d3982591baf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/library-guidance/breaking-changes.md | dhernandezb/docs.es-es | cf1637e989876a55eb3c57002818d3982591baf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/library-guidance/breaking-changes.md | dhernandezb/docs.es-es | cf1637e989876a55eb3c57002818d3982591baf1 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Cambios importantes y las bibliotecas de .NET
description: Prácticas recomendadas para explorar los cambios importantes al crear bibliotecas de. NET.
author: jamesnk
ms.author: mairaw
ms.date: 10/02/2018
ms.openlocfilehash: 83c01fdad7d836877bf692b87eeb0230219ded36
ms.sourcegitcommit: fd8d4587cc26e53f0e27e230d6e27d828ef4306b
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 10/16/2018
ms.locfileid: "49370340"
---
# <a name="breaking-changes"></a>Cambios importantes
Es importante para una biblioteca de .NET buscar un equilibrio entre la estabilidad para los usuarios existentes y la innovación para el futuro. Obtenga información sobre los creadores de bibliotecas hacia la refactorización y replanteamiento de código hasta que es perfecto, pero importantes de los usuarios existentes tiene un impacto negativo, especialmente para bibliotecas de bajo nivel.
## <a name="project-types-and-breaking-changes"></a>Tipos de proyecto y los cambios recientes
Uso de una biblioteca de la Comunidad de .NET cambia el efecto de los principales cambios en los usuarios finales.
* **Baja y bibliotecas de nivel intermedio** al igual que un analizador serializador, HTML, asignador relacional de objetos de base de datos o marco web son las más afectadas por cambios importantes.
Los paquetes de bloques de creación se usan por el usuario final a los desarrolladores crear aplicaciones y otras bibliotecas como dependencias de NuGet. Por ejemplo, está creando una aplicación y está usando a un cliente de código abierto para llamar a un servicio web. Una actualización de última hora a una dependencia que usa el cliente no es algo que puede corregir. Es el cliente de código abierto que deba cambiarse y no tiene ningún control sobre él. Tendrá que buscar las versiones compatibles de las bibliotecas o enviar una corrección a la biblioteca de cliente y espere a que una nueva versión. La peor situación posible es si desea utilizar dos bibliotecas que dependan de las versiones incompatibles de una biblioteca de terceros.
* **Bibliotecas de alto nivel** como un conjunto de aplicaciones de interfaz de usuario, los controles son menos sensibles a cambios importantes.
Bibliotecas de alto nivel se hace referencia directamente en una aplicación de usuario final. Si se producen cambios importantes, el desarrollador puede elegir actualizar a la versión más reciente, o puede modificar su aplicación para que funcione con el cambio.
**HACER ✔️** piense en cómo se utilizará la biblioteca. ¿Qué efectos tendrá los cambios importantes en las aplicaciones y bibliotecas que lo usan?
**HACER ✔️** minimizar los cambios importantes al desarrollar una biblioteca de bajo nivel.
**Considere la posibilidad de ✔️** publicación principal reescritura de una biblioteca como un nuevo paquete de NuGet.
## <a name="types-of-breaking-changes"></a>Tipos de cambios importantes
Cambios importantes se dividen en categorías diferentes y no son igualmente impactantes.
### <a name="source-breaking-change"></a>Cambio de origen
Un origen de cambio no afecta a la ejecución del programa, pero provocará errores de compilación la próxima vez que se vuelve a compilar la aplicación. Por ejemplo, una nueva sobrecarga puede crear ambigüedad en las llamadas de método que anteriormente se encontraban ambiguas o un parámetro cuyo nombre ha cambiado interrumpirá los llamadores que utilizan parámetros con nombre.
```csharp
public class Task
{
// Adding a type called Task could conflict with System.Threading.Tasks.Task at compilation
}
```
Como un origen de cambio importante solo es perjudicial cuando los desarrolladores compilar sus aplicaciones, es el menos disruptivo cambio importante. Los desarrolladores pueden corregir fácilmente su propio código fuente roto.
### <a name="behavior-breaking-change"></a>Cambio de comportamiento
Los cambios de comportamiento son el tipo más común de cambio importante: casi cualquier cambio de comportamiento podría afectar a alguien. Cambia a la biblioteca, como las firmas de método, las excepciones que produce o de entrada o salida formatos de datos, podrían todos afectar negativamente a los consumidores de la biblioteca. Si los usuarios se basaban en el comportamiento previamente dañado, incluso una corrección de errores puede calificar como un cambio importante.
Incorporar características y mejorar los comportamientos incorrectos son algo bueno, pero sin la atención, puede resultar muy difícil para los usuarios existentes que se va a actualizar. Es un enfoque para ayudar a los desarrolladores a lidiar con los últimos cambios de comportamiento ocultarlas detrás de la configuración. La configuración permite a los desarrolladores actualizar a la versión más reciente de la biblioteca mientras al mismo tiempo si elige participar o dejar de participar en cambios importantes. Esta estrategia permite a los desarrolladores a mantenerse al día al permitir que su código usado adaptarse con el tiempo.
Por ejemplo, ASP.NET Core MVC tiene el concepto de un [versión compatibilidad](/aspnet/core/mvc/compatibility-version) que modifica las características habilitadas y deshabilitadas en `MvcOptions`.
**Considere la posibilidad de ✔️** excluyendo las nuevas características de forma predeterminada, si afectan a los usuarios existentes y permiten que los desarrolladores a participar en la característica con una configuración.
### <a name="binary-breaking-change"></a>Cambio importante binario
Se produce un cambio de archivo binario cuando cambie la API pública de la biblioteca, por lo que los ensamblados compilados con versiones anteriores de la biblioteca ya no sean pueden llamar a la API. Por ejemplo, cambiar la firma de un método mediante la adición de un nuevo parámetro hará que los ensamblados compilados con la versión anterior de la biblioteca producir un <xref:System.MissingMethodException>.
Un cambio de archivo binario también puede interrumpir un **todo el ensamblado**. Cambiar el nombre de un ensamblado con `AssemblyName` cambiará la identidad del ensamblado, así como agregar, quitar o cambiar la clave de nomenclatura segura del ensamblado. Un cambio de identidad de un ensamblado interrumpirá en todo el código compilado que lo usa.
**❌ NO** cambiar un nombre de ensamblado.
**NO ❌** agregar, quitar o cambiar la clave de nomenclatura segura.
**Considere la posibilidad de ✔️** mediante clases base abstractas en lugar de interfaces.
> Agrega algo a una interfaz hará que los tipos existentes que implementan un error. Una clase base abstracta permite agregar una implementación virtual predeterminada.
**Considere la posibilidad de ✔️** colocar el <xref:System.ObsoleteAttribute> en tipos y miembros que se va a quitar. El atributo debe tener instrucciones para actualizar el código para dejar de usar la API obsoleta.
> Código que llama a tipos y métodos con el <xref:System.ObsoleteAttribute> generará una advertencia de compilación con el mensaje proporcionado para el atributo. Las personas de dar advertencias que use el tiempo de superficie de API obsoleto para migrar de modo que cuando se quita la API obsoleta, la mayoría ya no está usando.
```csharp
public class Document
{
[Obsolete("LoadDocument(string) is obsolete. Use LoadDocument(Uri) instead.")]
public static Document LoadDocument(string uri)
{
return LoadDocument(new Uri(uri));
}
public static Document LoadDocument(Uri uri)
{
// Load the document
}
}
```
## <a name="see-also"></a>Vea también
* [Consideraciones sobre la versión y actualización para los desarrolladores de C#](../../csharp/whats-new/version-update-considerations.md)
* [Una guía definitiva para cambios importantes de la API de .NET](https://stackoverflow.com/questions/1456785/a-definitive-guide-to-api-breaking-changes-in-net)
* [Reglas de cambio de salto de CoreFX](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/breaking-change-rules.md)
>[!div class="step-by-step"]
[Anterior](./versioning.md)
| 76.447619 | 746 | 0.801171 | spa_Latn | 0.994212 |
c06803017f805bfc40dc7749a547dca0e40d19a7 | 5,528 | md | Markdown | collections/_concerts/220625_kim.md | chmaynard/Sources2 | bcddf1097bb1063d63ccf90b3eb6cc7bdd42d546 | [
"MIT"
] | null | null | null | collections/_concerts/220625_kim.md | chmaynard/Sources2 | bcddf1097bb1063d63ccf90b3eb6cc7bdd42d546 | [
"MIT"
] | null | null | null | collections/_concerts/220625_kim.md | chmaynard/Sources2 | bcddf1097bb1063d63ccf90b3eb6cc7bdd42d546 | [
"MIT"
] | null | null | null | ---
date: 2022-06-25
time: 7:30 pm
title: An Evening with Stephen Kim
artists: Stephen Kim, violin ∙ Andrew Hsu, piano
banner: prairie.jpg
capacity: 30
---
<br/>
{% assign poster = "/assets/images/concerts/stephen-kim.png" %}
{% assign caption = "2019 Queen Elisabeth Competition, Brussels" %}
<div align="center" style="padding-top: 2.0em; padding-bottom: 1.0em;" >
<figure>
<video controls width=720 height=405 preload=auto poster="{{ poster }}" style="background-color:black;" >
<source src="https://corememorymusic.s3.us-west-001.backblazeb2.com/stephen-kim.mp4" type="video/mp4">
Your browser does not support the video tag.
</video>
<figcaption style="font-style: italic; text-align: center; padding: 0.5em;">
{{ caption }}
</figcaption>
</figure>
</div>
<br/>
Join us on {{ page.date | date: "%A, %B %e" }} at {{ page.time }}
for a performance by violinist Stephen Kim and composer/pianist Andrew Hsu.
<br>
* TOC
{:toc}
## Program
{% include cmm/program.html %}
## About the Artists
### Stephen Kim
{% include cmm/figure-image.html name="stephen-kim.jpg" align="left" %}
Combining a distinctive ability of “holding an audience spellbound” with his expressive
qualities as “a fire-breathing, passionate communicator” (Indiana Tribune-Star; Aspen
Times), violinist Stephen Kim is continually praised for his originality and honest
performances.
Presented in venues across North America, Europe, and Asia, Stephen has appeared as a
soloist with the Orchestre Philharmonique Royal de Liège, Brussels Philharmonic, Belgian
National Orchestra, Orchestre Royal de Chambre de Wallonie, l’Orchestra del Teatro Carlo
Felice, Sendai Philharmonic Orchestra, Bucheon Philharmonic Orchestra, Suwon Philharmonic
Orchestra, Curtis Chamber Orchestra, Juilliard Orchestra, Carmel Symphony Orchestra, Terre
Haute Symphony Orchestra, Austin Symphony Orchestra, and the Aspen Music Festival’s AACA and
Philharmonic orchestras, among others.
In recent seasons, Stephen performed Brahms' Violin Concerto seven times with two orchestras
during a two-week tour in Belgium, as well as six performances of Mozart's Violin Concerto
No. 5 during a two-month tour across the United States with the Curtis Chamber Orchestra. He
embarked on multiple concert tours in Korea, Japan, Shanghai, Hong Kong, Macao, and Belgium,
in addition to performing recitals at the Verbier Festival Academy, Stradivari Society
recital series, and Kingston Chamber Music Festival.
Stephen holds a Bachelor of Music from the Curtis Institute of Music, where he studied with
Shmuel Ashkenasi, Joseph Silverstein, and Aaron Rosand. At Curtis, Stephen was the recipient
of the Joan and Irwin Jacobs Fellowship, and he was awarded the Curtis/Milka Violin Artist
Prize. Stephen also received a Master of Music from the Juilliard School, where he studied
with Hyo Kang. Stephen's studies at Juilliard were also fully funded as the recipient of the
Irene Diamond Fellowship, along with the Syril H. and Walter A. Frank Scholarship and the
Mary L. Bianco Scholarship. Stephen is currently pursuing Professional Studies at the
Kronberg Academy with Antje Weithaas. These studies are funded by the Dr. Rolf M. Schwiete
Stiftung.
Stephen plays the 1725 “ex-Moller” Guarnerius del Gesù, on generous loan from the Samsung
Foundation of Culture of Korea and the Stradivari Society of Chicago.
### Andrew Hsu
{% include cmm/figure-image.html name="andrew-hsu.jpg" align="left" %}
Andrew Hsu (徐鴻) is a Chinese-American composer and pianist based in New York City. The
range and versatility of his musical pursuits range from the classical canon to modern
masterworks and contemporary experimentalism. His music probes the imagination, searching
for a distinct sense of colour and timelessness within a delicate sonic palette.
Hsu’s compositions have earned international acclaim from performances across Europe and the
USA—notably Alice Tully Hall, Carnegie Hall, Die Glocke, and Konzerthaus Berlin—and
partnerships with some of today’s leading musical artists and ensembles—including the Battle
Creek, Juilliard, and Minnesota Orchestras, the Miró and Zorá Quartets, Network for New
Music, Lyon-Sasaki Duo, Sasha Cooke, Lucy Fitz Gibbon, Daniel Hsu, Sarah Shafer, Katherine
Siochi, Steven Tenenbom, and Angelo Xiang Yu.
As a performer, Hsu has been associated with the Battle Creek, Castro Valley, Lansing,
Louisville, and Oakland Symphony Orchestras; ensembles Cantata Profana, Metropolis, New
Fromm Players, New Juilliard, and Sejong Soloists; and Aspen Music Festival, Caramoor,
Chamber Music Northwest, Concert Artists Guild, Conservatoire américain de Fontainebleau,
Curtis on Tour, Foundation for Chinese Performing Arts, Gilmore Keyboard Festival and Rising
Star Series, King’s Lynn Festival, Marlboro Music, Ravinia, Tanglewood, and WQXR. Hsu’s list
of honours include a Charles Ives Scholarship from the American Academy of Arts and Letters,
ASCAP Morton Gould Award, Aspen Music Festival’s Hermitage Prize, BMI William Schuman Prize,
and Gilmore Young Artist Award.
Hsu is a graduate of the Curtis Institute and Juilliard, where he completed his DMA; as a
student, he held the Kovner, Rising Star Annual, and C. V. Starr Doctoral Fellowships. His
teachers included pianists Gary Graffman and Eleanor Sokoloff, and composers Samuel Adler,
Richard Danielpour, David Serkin Ludwig, Matthias Pintscher and Steven Stucky. He is married
to concert violinist Rose Hsien.
## About the Concert
{% include cmm/about-the-concert.html %}
| 47.247863 | 108 | 0.785999 | eng_Latn | 0.982566 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.