BramVanroy/stack_md_lid · Datasets at Hugging Face

b58781c16e289ae2df21c8c486083d8fb4095cc5

1,607

md

Markdown

fmcapi/api_objects/README.md

realvitya/fmcapi

38fb9a8da2d9ebbadf4ed4cb559244646b3bf3be

[ "BSD-3-Clause" ]

57

2017-06-13T17:06:20.000Z

2021-07-27T08:53:25.000Z

fmcapi/api_objects/README.md

realvitya/fmcapi

38fb9a8da2d9ebbadf4ed4cb559244646b3bf3be

[ "BSD-3-Clause" ]

66

2017-11-09T16:02:45.000Z

2021-08-04T20:52:41.000Z

fmcapi/api_objects/README.md

realvitya/fmcapi

38fb9a8da2d9ebbadf4ed4cb559244646b3bf3be

[ "BSD-3-Clause" ]

56

2017-06-08T07:53:12.000Z

2021-07-30T13:26:47.000Z

#First, thank you for taking a look around the code! If you find something wrong, and you don't want to fix it, please open an issue on github: https://github.com/daxm/fmcapi/issues. ##If you desire to write some code then please note these items: * Use the Cisco Quick Start Guide for FMC API to know where each API class should be stored. As you can see there are several sub-package directories in the api_objects package. Place your new Class file there. * Please name the Python file and the Class you create to match the associated API method from the Quick Start Guide. This will help users know what is what. * 99% of the time your Class should inherit from APIClassTemplate to get all the additional Class methods. No need for you to re-write that code! * In both the api_objects' dunder init and the sub-package's dunder init please import your specific Class and add it to the dunder all variable. * Lastly, please create a "unit-test" for your new Class' features. These unit-tests are referenced from the TestingUserScript.py file. ##Misc Notes about adding code: * You may not agree with me on this logic but I feel we need to control what is submitted to format_data() and/or parse_kwargs() class methods. It's been my experience that the FMC is VERY touchy about what is in the JSON payload so we might as well accept that we need to manage what is sent. So, you'll see that each API class has VALID_JSON_DATA and VALID_FOR_KWARGS variables. These are lists of variable names we will allow. Be sure to create/update these variables as you create/modify the Class(es).

66.958333

120

0.774113

eng_Latn

0.999696

b58786feda28c31a9a02a60e1a41997cef96aadb

500

md

Markdown

_posts/results/2015-01-03-results.md

bvilnis/goulburnspeedway

bad1c5bbc129a99d3302a6006001fd4b9992e84b

[ "MIT" ]

null

_posts/results/2015-01-03-results.md

bvilnis/goulburnspeedway

bad1c5bbc129a99d3302a6006001fd4b9992e84b

[ "MIT" ]

2

2017-08-25T23:50:40.000Z

2017-08-26T00:00:57.000Z

_posts/results/2015-01-03-results.md

bvilnis/goulburnspeedway

bad1c5bbc129a99d3302a6006001fd4b9992e84b

[ "MIT" ]

null

--- layout: post title: "Results" categories: results --- | Event | 1st | 2nd | 3rd | | ------------- |------------- | ----- | ------- | | Stock Rods | Peter Croker | Mitch Brown | Dean Alessi | | Mod Lites | Rob Swain | Bruce Adams | Kenny Brooks | | GPs | Scott Moir | Trevor Perry | Cory Tatarko | | Juniors | Steven King | Sean Rooney | Tim Vilnis | | Fender Benders | Chrif Chaffy | David Browne | Tony Irwin | | F500's | Daniel Broadbent | Nathan Pryor | Paul Gray |

33.333333

61

0.566

eng_Latn

0.258369

b588c80cba73530e777697e6c84c64ae7f09760e

58

md

Markdown

README.md

rorydunn/insurance-marketing

4c42e5273d3cf670b371a4bed8a3bc4828831029

[ "MIT" ]

1

2019-07-30T17:12:10.000Z

README.md

rorydunn/insurance-marketing

4c42e5273d3cf670b371a4bed8a3bc4828831029

[ "MIT" ]

null

README.md

rorydunn/insurance-marketing

4c42e5273d3cf670b371a4bed8a3bc4828831029

[ "MIT" ]

null

# [Saleslight Marketing Site](https://www.saleslight.io)

19.333333

56

0.741379

ind_Latn

0.162066

b588f9e6a574fc9a6a8a3f3923746db2a9da7458

3,732

md

Markdown

math/README.md

asukakenji/go-benchmarks

2f611ba1f88366c36b3347f1ac5014fd8a9103ce

[ "MIT" ]

null

math/README.md

asukakenji/go-benchmarks

2f611ba1f88366c36b3347f1ac5014fd8a9103ce

[ "MIT" ]

null

math/README.md

asukakenji/go-benchmarks

2f611ba1f88366c36b3347f1ac5014fd8a9103ce

[ "MIT" ]

null

# Math ## BitCount ### 32-bit The most efficient implementations for 32-bit are: `BitCountUint32Pop1Alt`: ```go func BitCountUint32Pop1Alt(x uint32) uint { x = x - ((x >> 1) & 0x55555555) x = (x & 0x33333333) + ((x >> 2) & 0x33333333) x = (x + (x >> 4)) & 0x0f0f0f0f return uint((x * 0x01010101) >> 24) } ``` `BitCountUint32Pop3`: ```go func BitCountUint32Pop3(x uint32) uint { n := (x >> 1) & 0x77777777 // Count bits in x = x - n // each 4-bit n = (n >> 1) & 0x77777777 // field. x = x - n n = (n >> 1) & 0x77777777 x = x - n x = (x + (x >> 4)) & 0x0f0f0f0f // Get byte sums. x = x * 0x01010101 // Add the bytes. return uint(x >> 24) } ``` `BitCountUint32Pop6`: ```go var byteToBitCountTable = [...]uint{ 0, 1, 1, 2, 1, 2, 2, 3, 1, 2, 2, 3, 2, 3, 3, 4, 1, 2, 2, 3, 2, 3, 3, 4, 2, 3, 3, 4, 3, 4, 4, 5, 1, 2, 2, 3, 2, 3, 3, 4, 2, 3, 3, 4, 3, 4, 4, 5, 2, 3, 3, 4, 3, 4, 4, 5, 3, 4, 4, 5, 4, 5, 5, 6, 1, 2, 2, 3, 2, 3, 3, 4, 2, 3, 3, 4, 3, 4, 4, 5, 2, 3, 3, 4, 3, 4, 4, 5, 3, 4, 4, 5, 4, 5, 5, 6, 2, 3, 3, 4, 3, 4, 4, 5, 3, 4, 4, 5, 4, 5, 5, 6, 3, 4, 4, 5, 4, 5, 5, 6, 4, 5, 5, 6, 5, 6, 6, 7, 1, 2, 2, 3, 2, 3, 3, 4, 2, 3, 3, 4, 3, 4, 4, 5, 2, 3, 3, 4, 3, 4, 4, 5, 3, 4, 4, 5, 4, 5, 5, 6, 2, 3, 3, 4, 3, 4, 4, 5, 3, 4, 4, 5, 4, 5, 5, 6, 3, 4, 4, 5, 4, 5, 5, 6, 4, 5, 5, 6, 5, 6, 6, 7, 2, 3, 3, 4, 3, 4, 4, 5, 3, 4, 4, 5, 4, 5, 5, 6, 3, 4, 4, 5, 4, 5, 5, 6, 4, 5, 5, 6, 5, 6, 6, 7, 3, 4, 4, 5, 4, 5, 5, 6, 4, 5, 5, 6, 5, 6, 6, 7, 4, 5, 5, 6, 5, 6, 6, 7, 5, 6, 6, 7, 6, 7, 7, 8, } func BitCountUint32Pop6(x uint32) uint { return byteToBitCountTable[x&0xff] + byteToBitCountTable[(x>>8)&0xff] + byteToBitCountTable[(x>>16)&0xff] + byteToBitCountTable[(x>>24)] } ``` The implementations `BitCountUint32Pop1Alt` and `BitCountUint32Pop6` are more widely used. They are easier than `BitCountUint32Pop3` to understand. As a result, they are used as the [optimized implementation](https://github.com/gcc-mirror/gcc/blob/master/libgcc/libgcc2.c#L847-L850) and [fallback implementation](https://github.com/gcc-mirror/gcc/blob/master/libgcc/libgcc2.c#L852-L857) of GCC's `__builtin_popcount` respectively. In benchmarks, these 3 implementations score almost the same most of the time. `BitCountUint32Pop1Alt` is usually the best among them when there is a difference. ### 64-bit Here are the 64-bit implementations: `BitCountUint64Pop1Alt`: ```go func BitCountUint64Pop1Alt(x uint64) uint { x = x - ((x >> 1) & 0x5555555555555555) x = (x & 0x3333333333333333) + ((x >> 2) & 0x3333333333333333) x = (x + (x >> 4)) & 0x0f0f0f0f0f0f0f0f return uint((x * 0x0101010101010101) >> 56) } ``` `BitCountUint64Pop3`: ```go func BitCountUint64Pop3(x uint64) uint { n := (x >> 1) & 0x7777777777777777 // Count bits in x = x - n // each 4-bit n = (n >> 1) & 0x7777777777777777 // field. x = x - n n = (n >> 1) & 0x7777777777777777 x = x - n x = (x + (x >> 4)) & 0x0f0f0f0f0f0f0f0f // Get byte sums. x = x * 0x0101010101010101 // Add the bytes. return uint(x >> 56) } ``` `BitCountUint64Pop6`: ```go // byteToBitCountTable is the same as that in the 32-bit implementation above. func BitCountUint64Pop6(x uint64) uint { return byteToBitCountTable[x&0xff] + byteToBitCountTable[(x>>8)&0xff] + byteToBitCountTable[(x>>16)&0xff] + byteToBitCountTable[(x>>24)&0xff] + byteToBitCountTable[(x>>32)&0xff] + byteToBitCountTable[(x>>40)&0xff] + byteToBitCountTable[(x>>48)&0xff] + byteToBitCountTable[(x>>56)] } ``` For 64-bit, the best implementations are `BitCountUint64Pop1Alt` and `BitCountUint64Pop3`. The table-based implementation `BitCountUint64Pop6` is significantly slower than its 32-bit counterpart.

31.1

592

0.594855

krc_Cyrl

0.582141

b5895329bf7c156c2a563a71a2dde374fa3713b3

243

md

Markdown

CHANGELOG.md

seegno/karma-should

fb1127bc11169e445ca2dac7bf6f5af553fef36b

[ "MIT" ]

5

2015-03-13T15:41:32.000Z

2016-01-07T16:41:21.000Z

CHANGELOG.md

ruimarinho/karma-should

fb1127bc11169e445ca2dac7bf6f5af553fef36b

[ "MIT" ]

2

2015-07-23T12:19:43.000Z

2015-10-28T17:40:54.000Z

CHANGELOG.md

ruimarinho/karma-should

fb1127bc11169e445ca2dac7bf6f5af553fef36b

[ "MIT" ]

1

2015-07-22T23:43:04.000Z

# Change Log ## [1.0.0](https://github.com/seegno/karma-should/tree/1.0.0) (2015-07-24) **Merged pull requests:** - Add support for should@7 [\#2](https://github.com/seegno/karma-should/pull/2) ([ruimarinho](https://github.com/ruimarinho))

30.375

125

0.687243

eng_Latn

0.175404

b589c4747526da01004af531b4e3139e1627dc25

566

md

Markdown

README.md

SurajReddyThummala/Weather-App

98afe351d7b90c572d07db8384336716eb9d46bd

[ "MIT" ]

null

README.md

SurajReddyThummala/Weather-App

98afe351d7b90c572d07db8384336716eb9d46bd

[ "MIT" ]

null

README.md

SurajReddyThummala/Weather-App

98afe351d7b90c572d07db8384336716eb9d46bd

[ "MIT" ]

null

React-Redux Weather Web App This web app is used to display acccurate weather information based on user's input for five days This app uses OpenWeatherApi to retrieve the weather information for 5 days This app uses axios for asynchronous network calls Redux promise is used as a middleware to promise the network request. SET-UP: git clone https://github.com/SurajReddyThummala/Weather-App.git npm install npm start visit localhost:8080 on browser Live Website - https://oj6jko6y6q.codesandbox.io/ This project is a part of Udemy Stephen Grider Course.

22.64

97

0.800353

eng_Latn

0.960112

b58a264494b388c53e71ff12e4d13f0082a0515b

1,531

md

Markdown

README.md

maczniak/practical-erlang-programming

04a84169359e3569beca13fec3cc72f555c68579

[ "CC0-1.0" ]

null

README.md

maczniak/practical-erlang-programming

04a84169359e3569beca13fec3cc72f555c68579

[ "CC0-1.0" ]

null

README.md

maczniak/practical-erlang-programming

04a84169359e3569beca13fec3cc72f555c68579

[ "CC0-1.0" ]

null

# practical-erlang-programming ## Development * IDE * build system * documentation * testing * logging * debugger * profiler * coverage * benchmark * rumtime tracer, inspector * reflection * code parser, formatter * parser generator ## Runtime System * os, POSIX, signal, subprocess * io (readline) * getopt * scheduler (cron) * terminal handling * garbage collection ## File * path, stat, filename matching, tmpfile * file operations * mmap ## Data Types * datetime * popular data structures and algorithms * pretty print ## Text * string, unicode * charset conversion * regular expression * template engine ## Encoding * serialization * base64 ## File Format * plain text (YAML, INI, CSV) * HTML (Beautiful Soup) * XML * JSON * mimetype, mbox ## Numeric Computation * math * random (UUID) * statistics ## Compression ## Cryptography * hash functions * encryption, decryption ## Network * socket, TLS * resolver * web server * HTTP (cookie) and popular Internet protocol client libraries (SSH, telnet, FTP, SMTP) ## Messaging System * XMPP * AMQP * MQTT ## OTP ## Distributed System * distributed data types and algorithms (consistent hash, CRDT, bloom, Paxos, raft) * job queue * map reduce framework (Hadoop client) * Riak core ## Database * Ets, Dets, Mnesia * dbm, sqlite * RDBMS clients (ODBC, ORM) * NoSQL clients ## GUI * window system toolkit * multimedia ## Localization * locale (calendar) * gettext ## Interface * foreign function library (NIF) * Erl_Interface * cloud providers (AWS)

13.08547

87

0.713912

eng_Latn

0.571153

b58ba7ba92c02d803cb45cfaa00453940f50a03b

4,922

md

Markdown

content/docs/start_canvas.md

slu-soc1120/slu-soc1120.github.io

10d7e4cd549583e2990cd831515129b2deb247cc

[ "CC-BY-4.0" ]

null

content/docs/start_canvas.md

slu-soc1120/slu-soc1120.github.io

10d7e4cd549583e2990cd831515129b2deb247cc

[ "CC-BY-4.0" ]

null

content/docs/start_canvas.md

slu-soc1120/slu-soc1120.github.io

10d7e4cd549583e2990cd831515129b2deb247cc

[ "CC-BY-4.0" ]

null

+++ title = "Tips for Using Canvas" date = 2020-08-11T00:00:00 lastmod = 2021-01-25T00:00:00 draft = false # Is this a draft? true/false toc = true # Show table of contents? true/false type = "docs" # Do not modify. # Add menu entry to sidebar. linktitle = "Using Canvas" [menu.docs] parent = "Getting Started" weight = 4 +++ ## What is Canvas? **Canvas** is what we call a "learning management system." It provides a platform for online teaching, and we use it for face-to-face courses as well. <br> ## How Do I Use Canvas? Go to <a href = "http://canvas.slu.edu" target = "_blank">the SLU Canvas login page</a>. You may be prompted to use your username, password, and multi-factor authentication credentials when you login. On the landing page, look for TBD. <br> ## Getting Around Canvas TBD <br> ## Netiquette Considerations Netiquette is a set of cultural norms (we'll discuss these this semester!) for interacting with classmates online. Different professors might have slightly different ideas about what is appropriate, so don't assume that everything below applies to all classes. These are adapted from <a href="https://tilt.colostate.edu/TipsAndGuides/Tip/128" target="_blank">Colorado State's guide to online discussions</a> and also include some of SLU's best practices. {{% alert warning %}} Not all of these apply to how we'll be using Canvas for this course, but they're solid best practices to follow and so I like to share them anyway! {{% /alert %}} 1. **Report Glitches**: Like all software, sometimes Canvas doesn't work right. If for any reason you experience difficulty participating, please call, email, or otherwise inform me of the issue. Chances are others are having the same problem. 2. **Help Others**: You may have more experience with online discussion forums than the person next to you. Give them a hand. Show them it’s not so hard. They’re really going to appreciate it! 3. **Be Patient**: Read everything in the discussion thread before replying. This will help you avoid repeating something someone else has already contributed. Acknowledge the points made with which you agree and suggest alternatives for those with which you don’t. 4. **Be Brief**: You want to be clear—and to articulate your point—without being preachy or pompous. Be direct. Stay on point. Don’t lose yourself, or your readers, in overly wordy sentences or paragraphs. 5. **Write Well**: Feel free to be a bit less formal than you would in a paper (contractions are fine), but make sure your work is easy to read. This means correct spelling, grammatical construction and sentence structure are expected. 6. **Cite Your Sources**: Another big must! If your contribution to the conversation includes the intellectual property (authored material) of others, e.g., books, newspaper, magazine, or journal articles—online or in print—they must be given proper attribution. Use hyperlinks to reference anything online. 7. **Emojis**: I differ from many of my colleagues here. Use them if you want! 8. **Respect Diversity**: Respect and be attentive to the diversity of your classmates and instructor. Before communicating, consider your message in the context of the class’ diversity in race, ethnicity, religion, disabilities, gender, sexual orientation, age, social class, marital status, geography, etc. Consider the diversity you can see or know – as well as that you cannot. 9. **Remember We Can't See You**: Be cautious when using humor or sarcasm; without the context of facial expressions or other body language, your tone or intent could be missed or misunderstood by others. 10. **Respect Others' Time**: Respect others’ time and life circumstances, which often don’t allow for an immediate response to a question or comment. 11. **No Yelling**: Step carefully. Beware the electronic footprint you leave behind. Using bold upper-case letters is bad form, like stomping around and yelling at somebody 12. **No Flaming**: Criticism must be constructive, well-meaning, and well-articulated. Please, no tantrums. Rants directed at any other contributor are simply unacceptable and will not be tolerated. The same goes for profanity. The academic environment expects higher-order language. 13. **Remember, You Can't Un-Ring the Bell**: Language is your only tool in an online environment. Be mindful. How others perceive you will be largely—as always—up to you. Once you've hit the send button, you've rung the bell. 14. **Review and Revise**: Review your written posts and responses to ensure that you’ve conveyed exactly what you intended. This is an excellent opportunity to practice your proofreading, revision, and rewriting skills—valuable assets in the professional world for which you are now preparing. I try read my posts out loud. This helps me ensure that grammar and sentence structure are correct, your tone is appropriate, and my post is clear.

91.148148

455

0.766355

eng_Latn

0.999048

b58ccdca2a1be88e8f9d946da34cff72fb06961b

1,403

md

Markdown

2020/12/05/2020-12-05 14:20.md

zhzhzhy/WeiBoHot_history

32ce4800e63f26384abb17d43e308452c537c902

[ "MIT" ]

3

2020-07-14T14:54:15.000Z

2020-08-21T06:48:24.000Z

2020/12/05/2020-12-05 14:20.md

zhzhzhy/WeiBoHot_history

32ce4800e63f26384abb17d43e308452c537c902

[ "MIT" ]

null

2020/12/05/2020-12-05 14:20.md

zhzhzhy/WeiBoHot_history

32ce4800e63f26384abb17d43e308452c537c902

[ "MIT" ]

null

2020年12月05日14时数据 Status: 200 1.焉栩嘉微博热度:2454146 2.拜登称希望特朗普来参加就职典礼微博热度:2046367 3.人民保险燃情冬奥微博热度:2045881 4.杨幂客串华晨宇站姐微博热度:2030159 5.王一博挖藕微博热度:1369217 6.能说会道的姐姐要成团微博热度:1195501 7.警察注视女生溺亡被停职微博热度:1167221 8.苹果承认部分iPhone11存在触摸问题微博热度:762746 9.美国医生在地下停车场病房拍下工作照微博热度:732337 10.美国将对更多中国公民实施签证限制微博热度:714061 11.哈尔滨发现一份冷冻食品阳性微博热度:687544 12.心疼龙丹妮微博热度:685781 13.GQ回应刘昊然的奖杯缺了个角微博热度:681710 14.倪妮好绝微博热度:678111 15.挪威央行副行长被辞职微博热度:676762 16.从结婚开始恋爱大结局微博热度:673188 17.马思唯易梦玲恋情微博热度:670762 18.诺言参加创造营微博热度:667959 19.热依扎产女微博热度:664560 20.亚洲最大生物物种诺亚方舟微博热度:633600 21.养了两年的暹罗微博热度:628521 22.余文乐二胎得女微博热度:625310 23.R1SE 微博热度:605630 24.韩美娟确认参加创4 微博热度:511853 25.郴州北湖区原团委书记强奸罪被判3年微博热度:441184 26.小盒鱼会喵喵叫吗微博热度:424494 27.爵迹微博热度:419235 28.斗罗大陆微博热度:408238 29.苹果被曝无需接触便可被盗一切信息微博热度:408098 30.二建微博热度:408083 31.杨幂没走GQ台阶微博热度:408071 32.丁真直播微博热度:355776 33.浦东医院结束闭环管理微博热度:322330 34.凌睿求婚鹿方宁微博热度:297170 35.重庆永川煤矿事故已致18人遇难微博热度:291346 36.赤狐书生评分微博热度:287549 37.天官赐福微博热度:279276 38.蔡徐坤刘昊然互相谦让微博热度:235949 39.张若昀腰围62 微博热度:209290 40.美术老师雪地中扫出巨幅雪竹图微博热度:207373 41.唐三小舞重逢微博热度:206875 42.2020年度十大BGM 微博热度:198670 43.刘昊然拿到的奖杯微博热度:197986 44.郭采洁羽毛飞舞靠浦江的风微博热度:195871 45.费启鸣找杨幂合影成功微博热度:190615 46.雅思微博热度:173576 47.西双版纳勐海将有火箭残骸陨落微博热度:169598 48.中国首次成为英国最大的进口来源国微博热度:160170 49.咸阳悬赏50万的涉黑在逃夫妻落网微博热度:110581 50.新疆完成对楼兰古城重要遗址抢险加固微博热度:89195

6.877451

22

0.781896

yue_Hant

0.355469

b58cd2f9dfa72b78067c2e6c36ff47fea82b9902

159

md

Markdown

README.md

jmarin/scale-geocode

942570f70329ddca49c74f54541af7139f192c84

[ "Apache-2.0" ]

null

README.md

jmarin/scale-geocode

942570f70329ddca49c74f54541af7139f192c84

[ "Apache-2.0" ]

null

README.md

jmarin/scale-geocode

942570f70329ddca49c74f54541af7139f192c84

[ "Apache-2.0" ]

null

scale-geocode ============= Geocoding at scale *Deprecated* : this project has been superseded by the work being done at https://github.com/cfpb/grasshopper

22.714286

109

0.72327

eng_Latn

0.995084

b58ce5b09491e16883fafc33592e9b9417cac6c7

113

md

Markdown

appendix.md

hamaier/mdEditor-doc

f5db650fbd605546590b11e6b07e5c4345be0d55

[ "CC0-1.0" ]

1

2017-05-17T15:44:10.000Z

appendix.md

hamaier/mdEditor-doc

f5db650fbd605546590b11e6b07e5c4345be0d55

[ "CC0-1.0" ]

16

2018-09-04T21:35:42.000Z

2021-08-24T19:25:23.000Z

appendix.md

hamaier/mdEditor-doc

f5db650fbd605546590b11e6b07e5c4345be0d55

[ "CC0-1.0" ]

7

2017-05-17T15:46:24.000Z

2021-05-11T00:58:19.000Z

# Appendix --- 1. [mdToolkit](appendix/mdToolkit.md) 2. [Documentation Guide](appendix/documentation-guide.md)

16.142857

57

0.743363

kor_Hang

0.269083

b58e597bad0a83d8555a4a6fe8c112710ca4666d

421

md

Markdown

data/content/fate-grand-order/ce/treasure-chocolate/attr.en.md

tmdict/tmdict

c2f8ddb7885a91d01343de4ea7b66fea78351d94

[ "MIT" ]

3

2022-02-25T11:13:45.000Z

2022-02-28T11:55:41.000Z

data/content/fate-grand-order/ce/treasure-chocolate/attr.en.md

slsdo/tmdict

c2f8ddb7885a91d01343de4ea7b66fea78351d94

[ "MIT" ]

null

data/content/fate-grand-order/ce/treasure-chocolate/attr.en.md

slsdo/tmdict

c2f8ddb7885a91d01343de4ea7b66fea78351d94

[ "MIT" ]

2

2022-02-25T09:59:50.000Z

2022-02-28T11:55:09.000Z

--- parent: attribute.ce source: fate-grand-order id: treasure-chocolate language: en weight: 0 --- Valentine’s chocolate from Anne Bonny & Mary Read. What? I’m supposed to write a message? S-Sure thing. Uh… Master, I’ve tasted this numerous times, so I think it should be safe. I’d be happy if you ate it all. Also, thanks for everything. Someday, I’d like to, um, go on a cruise with you and Anne. What do you think?

23.388889

70

0.733967

eng_Latn

0.9943

b58f774aa1069c0a941bb33b9ab99067a4cfe2ba

218

md

Markdown

_watches/M20200530_033838_TLP_4.md

Meteoros-Floripa/meteoros.floripa.br

7d296fb8d630a4e5fec9ab1a3fb6050420fc0dad

[ "MIT" ]

5

2020-05-19T17:04:49.000Z

2021-03-30T03:09:14.000Z

_watches/M20200530_033838_TLP_4.md

Meteoros-Floripa/site

764cf471d85a6b498873610e4f3b30efd1fd9fae

[ "MIT" ]

null

_watches/M20200530_033838_TLP_4.md

Meteoros-Floripa/site

764cf471d85a6b498873610e4f3b30efd1fd9fae

[ "MIT" ]

2

2020-05-19T17:06:27.000Z

2020-09-04T00:00:43.000Z

--- layout: watch title: TLP4 - 30/05/2020 - M20200530_033838_TLP_4T.jpg date: 2020-05-30 03:38:38 permalink: /2020/05/30/watch/M20200530_033838_TLP_4 capture: TLP4/2020/202005/20200529/M20200530_033838_TLP_4T.jpg ---

27.25

62

0.784404

fra_Latn

0.048243

b590015c2ad098cdbb5c86f3dcffc78159bba0e8

457

md

Markdown

content/slides/Introduction/Building.md

tbranyen/devoxx-2013

e6852a067b162b659027e08c88f808dfa8f68766

[ "MIT" ]

1

2015-11-05T11:13:05.000Z

content/slides/Introduction/Building.md

tbranyen/devoxx-2013

e6852a067b162b659027e08c88f808dfa8f68766

[ "MIT" ]

null

content/slides/Introduction/Building.md

tbranyen/devoxx-2013

e6852a067b162b659027e08c88f808dfa8f68766

[ "MIT" ]

null

How to Build Web Applications ============================= <script type="speaker-notes"> ~ 25 seconds. - One hour to teach you everything I know. - Discuss techniques for building modern web applications. - Show simple ways of developing, as the best way is usually simple. - No live coding, I will show high level and then dig into the actual source. </script> <style scoped> @host { background-color: #28723A; color: #C4C182; } </style>

21.761905

77

0.671772

eng_Latn

0.987686

b5900edeb32682fa31d180f84c24ab07bf27eff2

1,148

md

Markdown

README.md

austonpramodh/maha_portfolio

b94332ae4f97aafaf3ec003dbad99a7f76755c66

[ "MIT" ]

null

README.md

austonpramodh/maha_portfolio

b94332ae4f97aafaf3ec003dbad99a7f76755c66

[ "MIT" ]

4

2020-02-09T14:52:28.000Z

2020-03-10T06:03:37.000Z

README.md

austonpramodh/maha_portfolio

b94332ae4f97aafaf3ec003dbad99a7f76755c66

[ "MIT" ]

null

Kick off your portfolio with this awesome project. This project has been u=built using [Prismic.io](https://prismic.io) CMS. ### This project is built using [Gatsby default starter ](https://github.com/gatsbyjs/gatsby-starter-default) boilerplate. ## 🚀 Quick start 1. **Clone this repository** Use the git CLI to clone this repository. ```shell git clone https://github.com/austonpramodh/portfolio-website ``` 1. **Create a Custom Content type on Prismic.io HomePage** Use [this](./src/Schemas/homepage.json) to copy the content type to the created custom content type on prismic cms. 1. **Create new Content and add the content** 1. **Install all the dependencies** ```shell npm install ``` 1. **Link the repository name** Copy `.env.example` file with name `.env` Add the Prismic CMS access token and Repository name. 1. **use the following command to build the project** ```shell npm run build ``` ## 💫 Deploy [![Deploy to Netlify](https://www.netlify.com/img/deploy/button.svg)](https://app.netlify.com/start/deploy?repository=https://github.com/austonpramodh/portfolio-website)

26.090909

169

0.705575

eng_Latn

0.857629

b590433e3b952fe482daeb6dacb9a92aff2da238

79

md

Markdown

README.md

GoldenbergDaniel/RustyTag

ce86e77f17509476b245d9659c85f188b594f0db

[ "MIT" ]

null

README.md

GoldenbergDaniel/RustyTag

ce86e77f17509476b245d9659c85f188b594f0db

[ "MIT" ]

null

README.md

GoldenbergDaniel/RustyTag

ce86e77f17509476b245d9659c85f188b594f0db

[ "MIT" ]

null

# RustyTag A circle tag game made with Rust and raylib. My first Rust projects

26.333333

67

0.78481

eng_Latn

0.996829

b5911dea43e147a56d42389c35a35faba121c873

726

md

Markdown

README.md

DoraemonYu/JS-PageVisibilityEvent

e5e3ccf6c293b8c32e12d990f55612d744efc410

[ "MIT" ]

null

README.md

DoraemonYu/JS-PageVisibilityEvent

e5e3ccf6c293b8c32e12d990f55612d744efc410

[ "MIT" ]

null

README.md

DoraemonYu/JS-PageVisibilityEvent

e5e3ccf6c293b8c32e12d990f55612d744efc410

[ "MIT" ]

null

# JS-PageVisibilityEvent provide the event deal with page **hidden/deactive** or **visible/active**, written by PURE JS, Cross-browser Support. # Current browser support - Chrome 13+ - Internet Explorer 10+ - Firefox 10+ - Opera 12.10+ # Example ``` var pv = new PageVisibilityEvent(); //New a Instance pv.SetCallback(visibilityChange); //To Set (or Rest) a Callback pv.Disable(); //To Disable pv.Enable(); //To Re-Enable pv.GetIsAtivceNow(); //Return current status function visibilityChange(isActive){ //isActive equal TRUE means active; //isActive equal FALSE means deactive; } ``` # licenses MIT licenses :)

25.034483

118

0.62259

eng_Latn

0.595366

b5911fed61effd0a79822d4978451447993efc0a

315

md

Markdown

_posts/2021-07-09-Filled-20210709061531428002.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

[ "Apache-2.0" ]

null

_posts/2021-07-09-Filled-20210709061531428002.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

[ "Apache-2.0" ]

null

_posts/2021-07-09-Filled-20210709061531428002.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

[ "Apache-2.0" ]

null

--- title: "(F)illed" metadate: "hide" categories: [ Pussy ] image: "https://preview.redd.it/lg18jg3582a71.jpg?auto=webp&s=f7ed60c5d1525c0a9eca6af75aa2906d978872bc" thumb: "https://preview.redd.it/lg18jg3582a71.jpg?width=1080&crop=smart&auto=webp&s=3b64e7f9943c847431a15813e7f8024a43602b2c" visit: "" --- (F)illed

31.5

125

0.771429

yue_Hant

0.089106

b59158bfbcbc4773d41a53d44f7cf5dfd1f38c0b

213

md

Markdown

README.md

bitfede/learning-polymer

c55a3015b70e3579f0865cadec10ced45e834e0e

[ "MIT" ]

null

README.md

bitfede/learning-polymer

c55a3015b70e3579f0865cadec10ced45e834e0e

[ "MIT" ]

null

README.md

bitfede/learning-polymer

c55a3015b70e3579f0865cadec10ced45e834e0e

[ "MIT" ]

null

#Hello! This is just a simple project that I'm doing to learn the Polymer Framework. I'm following the LevelUp tutorial on youtube at: https://www.youtube.com/playlist?list=PLLnpHn493BHGhoGAb2PRKzv4Zw3QoatK- :)

30.428571

122

0.793427

eng_Latn

0.920498

b59336c0b3bba9aad428ae2d860f538fc71dc2f4

5,331

md

Markdown

data/blog/2007/138-Start-Writing-Embeddable-Applications.md

Lohn/mwop.net

da7422d0c68b0b5b14e40b4fb59628203408cb2e

[ "BSD-2-Clause" ]

56

2015-07-26T07:21:37.000Z

2021-06-28T16:55:12.000Z

data/blog/2007/138-Start-Writing-Embeddable-Applications.md

weierophinney/mwop.net

de84c05c74e79eb923eb081a0fb0330a051ea9b1

[ "BSD-2-Clause" ]

15

2015-07-26T07:51:04.000Z

2022-01-21T15:21:05.000Z

data/blog/2007/138-Start-Writing-Embeddable-Applications.md

Lohn/mwop.net

da7422d0c68b0b5b14e40b4fb59628203408cb2e

[ "BSD-2-Clause" ]

29

2015-04-20T21:17:56.000Z

2021-11-29T22:40:25.000Z

--- id: 138-Start-Writing-Embeddable-Applications author: matthew title: 'Start Writing Embeddable Applications' draft: false public: true created: '2007-05-07T00:00:40-04:00' updated: '2007-05-08T20:16:18-04:00' tags: - php --- [Clay Loveless](http://killersoft.com/randomstrings/) wrote last year an article entitled [Stop Writing Loner Applications](http://killersoft.com/randomstrings/2006/06/14/stop-writing-loner-applications/) in which he ranted about all the monolithic applications that act like they're the only kid on the block when it comes to user authentication. Basically, if you want to create a site that utilizes several third-party, off-the-shelf PHP apps (say, a forum, a blog, and a wiki), getting a shared authentication to work between them can be more than a little painful. I've hit a similar problem repeatedly the past couple months: most of these apps simply are not embeddable, at least not without modifying the source. "Why embed?" you ask. Simple: if I'm creating a site that has one or two of these applications, but also my (or my company's) own custom functionality, I may want to ensure that certain elements are present on all pages, or that I can control some of the content in all pages: a unified header and footer, ability to inject statistic tracking javascript, etc. The predominant attitudes are either, "Don't embed our app, embed your app in ours," or "Just modify the templates." Neither of these solutions is acceptable.  Why not? In the first case, it's *my* site. If I'm mixing and matching several such applications, which ones should I embed, and which should be the master? Honestly, the applications *I'm* writing for the site are the master application; the third party solutions should be embedded in *my* website. In the second case, I may have my own header and footer, and tools for automating what tracking scripts are embedded when — in other words, I'm running my own display logic, possibly with my own tools. Embedding these tools into another apps templates is at times difficult (if the application is simply using PHP, the difficulty may be mainly finding what code to alter), at times impossible (if the application uses a templating engine vastly different than what I'm using, or one that does not allow arbitrary PHP). Why should I have to write an interface to my code for each application? Truthfully, it simply makes sense to use a Two Step View in most cases, having the application generate content that is then injected into a sitewide template I control. I've tried in a number of cases to write wrappers so I can grab content from these third party apps, typically using output buffering to capture the output so I can inject it into my own views. So far, my experience has been universally dismal. Most of the secure, robust apps out there (I'm not going to name names) *still* use procedural methods for at the very least the main script, usually index.php. This includes slurping in configuration from other files… all of which happens in the global namespace. What's the problem? Most wrappers I write are by necessity class methods or functions, or run from within one, meaning the global namespace is no longer in effect. The end result is that I have to greatly alter the code to get things to work — in one case, my colleague and I ended up changing all `$_GLOBALS` references to `$_SESSION` simply to get things to work. Hackish, but it got the job done. However, it also means it will be a nightmare to upgrade until we can script it. If you're writing a standalone PHP application, maybe the next great forum software, or blog software, or wiki, or what have you, please design it in such a way that it is easily embeddable: - When using configuration files, use a configuration component that doesn't require use of the global namespace (PEAR's `Config`, Solar's `Solar_Config`, and Zend Framework's `Zend_Config` come to mind); when coupled with a registry or implemented as a static class property (in PHP5), you can have access to the configuration from anywhere in your application. - Have your bootstrap script call on class methods or functions to do their work. Don't do any decisioning in the global namespace. - Better yet, use an MVC pattern in your apps, and have your bootstrap simply dispatch the controller. This can easily be duplicated in somebody else's code, or simply directly included. - Make sure your templates are easily modified to allow developers to strip out header, footer, and menu elements. - Create an API to allow retrieving necessary javascript and CSS so that it can later be injected into another system's templates. - Don't use `$_GLOBALS` ever. It seems like an easy way to keep variables accessible across classes and functions, but with PHP 5's static properties, or judicious usage of singleton's in PHP 4, there are other ways to accomplish the same effect with fewer side effects. If you're responsible for maintaining an existing project, please start fixing your application today so it can be embedded. Believe it or not, it may actually *increase* adoption of your project, as more people will be able to use it within their existing sites. At the very least, you'll stop me from ranting, and reduce the amount I spend on acetaminophen.

56.115789

131

0.78203

eng_Latn

0.999815

b593f5916f93f972cef02571a9e9ff859ad889bd

2,327

md

Markdown

apps/website/src/data/pakt/unternehmen-und-stiftungen/frimo-group-gmb-h.md

mint-vernetzt/mint-vernetzt

66b858856127a65184397660b79b0c6684be7d30

[ "MIT" ]

7

2021-08-03T08:07:58.000Z

2022-01-24T17:07:37.000Z

apps/website/src/data/pakt/unternehmen-und-stiftungen/frimo-group-gmb-h.md

mint-vernetzt/mint-vernetzt

66b858856127a65184397660b79b0c6684be7d30

[ "MIT" ]

199

2021-08-25T08:57:10.000Z

2022-03-16T09:35:35.000Z

apps/website/src/data/pakt/unternehmen-und-stiftungen/frimo-group-gmb-h.md

mint-vernetzt/mint-vernetzt

66b858856127a65184397660b79b0c6684be7d30

[ "MIT" ]

3

2021-10-14T18:04:47.000Z

2022-02-02T11:09:25.000Z

--- name: "FRIMO Group GmbH" slug: "unternehmen-und-stiftungen/frimo-group-gmb-h" logo: "../logos/Frimo-1.png" category: "Unternehmen und Stiftungen" citeAuthor: "" citeAuthorFunction: "" citeQuote: "" --- Die FRIMO Unternehmensgruppe stellt Systemlösungen zur Fertigung hochwertiger Kunststoffkomponenten her. Seit mehr als fünf Jahrzehnten ist maßgeschneiderte Werkzeug- und Anlagentechnik bei der FRIMO Kundschaft weltweit im Einsatz. Vom klassischen Werkzeug- und Anlagenlieferanten hat sich das Unternehmen zu einem globalen Technologiepartner entwickelt. Heute gehören internationale Standorte in Europa, Amerika und Asien mit insgesamt 1.500 Mitarbeiterinnen und Mitarbeitern sowie zahlreiche internationale Vertretungen zum FRIMO Netzwerk. Die Unternehmensgruppe mit ihrem Hauptsitz in Lotte bei Osnabrück erwirtschaftete 2018 einen Jahresumsatz von über 200 Mio. Euro. #### Aktivitäten im MINT-Bereich: FRIMO nimmt deutschlandweit am [Girls'Day](https://www.girls-day.de/) teil und bietet Mädchen die Möglichkeit, in handwerkliche und technische Berufe hineinzuschnuppern. Die Mädchen können den Betrieb besichtigen, werden von den Auszubildenden an das Thema PUR-Schäumen herangeführt und dürfen selbst Pilze schäumen. Auch das Thema Konstruktion steht im Vordergrund, so dürfen die Mädchen mit Hilfe einer CAD-Simulation ein „Laserschwert“ führen und so die CAD-Konstruktionsprogramme besser kennenlernen. Ebenso beteiligt sich FRIMO seit 2018 an dem [Niedersachsen Technikum](https://www.niedersachsen-technikum.de/), einer Initiative für Frauen in MINT Berufen. Eine Technikantin entwickelt aktuell gemeinsam mit FRIMO-Konstrukteuren ein eigenes Projekt und schnuppert in den Alltag einer Konstrukteurin hinein. Im Vorhinein durfte die Technikantin gemeinsam mit den neuen Auszubildenden grundständiges Wissen der technischen Ausbildungsberufe kennenlernen, bspw. eigenständiges Fräsen oder Feilen. Praktika und Unternehmensbesuche kooperierender Schulen bieten Mädchen und Jungen die Möglichkeit, hinter die Kulissen des Werkes zu schauen und die Ausbildungsberufe der verschiedenen Standorte kennenzulernen. FRIMO besucht auch Schulen und stellt gemeinsam mit den Schüler/innen Versuche zum Thema PU-Schaum oder Biegeübungen mit Draht an. [www.frimo.com/karriere](https://www.frimo.com/de/karriere.html)

89.5

504

0.831972

deu_Latn

0.99831

b594aa41120e595e64660622a3a55d4e19c2df0c

3,154

md

Markdown

docs/quick-start-guides/SGX Infrastructure/1Introduction.md

intel-secl/docs

be3563b66d2e1b8e47fcbb67e2dc4d810bfb59d8

[ "Intel", "BSD-3-Clause" ]

6

2021-03-01T18:53:29.000Z

2021-12-25T04:53:08.000Z

docs/quick-start-guides/SGX Infrastructure/1Introduction.md

intel-secl/docs

be3563b66d2e1b8e47fcbb67e2dc4d810bfb59d8

[ "Intel", "BSD-3-Clause" ]

1

2021-11-10T09:34:43.000Z

2021-11-15T00:54:01.000Z

docs/quick-start-guides/SGX Infrastructure/1Introduction.md

intel-secl/docs

be3563b66d2e1b8e47fcbb67e2dc4d810bfb59d8

[ "Intel", "BSD-3-Clause" ]

16

2020-11-05T16:27:46.000Z

2022-03-22T14:26:49.000Z

# Introduction [Intel® SecL-DC libraries](https://github.com/intel-secl/docs/-/blob/v4.1/develop/product-guides/Secure%20Key%20Caching.md#sgx-attestation-infrastructure-and-skc-components) support SGX attestation as a base use case. For a detailed description of SGX Attestation, please refer to [SGX ECDSA Attestation](https://github.com/intel-secl/docs/-/blob/v4.1/product-guides/SGX%20Infrastructure.md#sgx-ecdsa-attestation) Intel® SecL-DC libraries also support following usecases which build upon the SGX Attestation usecase * Secure Key Caching * SGX Orchestration Support for Kubernetes and Openstack ## Glossary | CMS | Certificate Management Service | Responsible for Providing TLS Certificates for other components | |------------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| | AAS | Authentication and Authorization Service | Authenticates Service User and Authorizes User against set of predefined roles | | Agent | SGX Agent | Performs SGX Feature Discovery and Extracts SGX Platform Data from a SGX Compute Node | | IHUB | integration Hub | Service to populate SGX Platform Discovery and Enablement Data to Cloud Orchestrator Services like Kubernetes and Openstack | | KBS | Key Broker Service | Broker Service which integrates with backend key management solution for accessing secrets over KMIP Interface | | SCS | SGX Caching Service | Responsible for Providing PCK Certifcates and other SGX Platform Collaterals | | SQVS | SGX Quote Verification Service | Responsible fo Verifying SGX ECDSA Quote | | SKC Client | SKC Library | A Client Library which connects to Key Broker Service to get the Secrets over secure channel and stores secret in a SGX Enclave | | SHVS | SGX Host Verification Service | Aggregates SGX Platform Discovery and Enablement Data for all the SGX Compute Nodes in a cluster | ## Intel® SecL-DC libraries Services Deployment Matrix for All Supported Usecases | Usecases | CMS | AAS | SGX Agent | SCS | SQVS | SKC Library | KBS | SHVS | IHUB | |-----------------------------------|-----|-----|-----------|-----|------|-------------|-----|------|------| | SGX Attestation | ✔ | ✔ | ✔ | ✔ | ✔ | | | | | | Secure Key Caching | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | | | | Orchestration Support | ✔ | ✔ | ✔ | ✔ | | | | ✔ | ✔ |

105.133333

413

0.500317

eng_Latn

0.799475

b595060a8a01c39166270e7168b9345ec3710fd3

836

md

Markdown

documentation/wiki/FAQ.md

amosproj/amos-ss2020-metadata-hub

f8434b27b306332c117a8dd20a8a55a3104d0f89

[ "MIT" ]

9

2020-04-23T14:22:48.000Z

2022-02-25T21:35:05.000Z

documentation/wiki/FAQ.md

amosproj/amos-ss2020-metadata-hub

f8434b27b306332c117a8dd20a8a55a3104d0f89

[ "MIT" ]

42

2020-04-24T17:59:33.000Z

2022-02-16T01:09:23.000Z

documentation/wiki/FAQ.md

amosproj/amos-ss2020-metadata-hub

f8434b27b306332c117a8dd20a8a55a3104d0f89

[ "MIT" ]

2

2020-08-17T11:19:44.000Z

2021-04-30T08:32:05.000Z

### I have problems with docker permissions using Linux. It is most likely your user does not belong to the ``docker`` group. Please have a look at these [instructions](https://docs.docker.com/engine/install/linux-postinstall/). ### I have problems with a running container and want to inspect them. You can start a shell session in your running container: ```bash docker exec -it {container-id} /bin/bash ``` This will start a *bash* session inside the container with the ID ``container-id``. Furthermore, you can inspect the log files at ``/metadatahub/server.log`` and ``/metadatahub/crawler.log``. ### I have problems with scheduled exeuctions and time intervals The docker image uses UTC time instead of the local time on your system. All time values, such as the start of a TreeWalk exeuction, should be given in UTC time.

36.347826

132

0.757177

eng_Latn

0.997808

b595a084bcf42fd004cc04e0f19a24ed193edcdd

648

md

Markdown

content/bulgaria3f.md

hidienet/Hugo

5e7f211db507e2298e2f9694416f0129211e1782

[ "Apache-2.0" ]

null

content/bulgaria3f.md

hidienet/Hugo

5e7f211db507e2298e2f9694416f0129211e1782

[ "Apache-2.0" ]

null

content/bulgaria3f.md

hidienet/Hugo

5e7f211db507e2298e2f9694416f0129211e1782

[ "Apache-2.0" ]

1

2020-11-24T12:08:27.000Z

--- title: '[保加利亞醉遊記] Day3：在攤檔市場買的大大個粉紅番茄' date: 2014-05-16T14:00:00.000+08:00 draft: false aliases: [ "/2014/05/day3.html" ] tags : [travel-保加利亞] --- 在[balkan bites](https://hidie.net/bulgaria2f/)時真的有特別留心聽講（因為都是關於食的吧～）就說過「在攤檔」買「粉紅番茄」 ![](/images/bulgaria3f1.jpg) 除了番茄，這樣的色彩也太繽紛了 ![](/images/bulgaria3f2.jpg) 找到了找到了真的比平時的大紅番茄顏色淡很多 ![](/images/bulgaria3f3.jpg) 買了兩個大大的返apartment 跟我的整隻手差不多一樣大（吼）超～清～甜～ juicy juicy ![](/images/bulgaria3f4.jpg) 還買了有柄的士多啤梨不像日本韓國種那樣只有濃濃的甜是似小時候清新的酸裡帶甜好懷念呢，這才是新鮮無添加的水果喔！ \----------------------------------------------- 延伸閱讀：[保加利亞醉遊記（14D16N）](https://hidie.net/bulgaria14d16n/)

17.052632

58

0.649691

yue_Hant

0.247356

b597d730803e35de8191a1ffc72987a90598118e

586

markdown

Markdown

_sentieri/2019-10-13-Da_Bertone_a_Monte_Alfeo.markdown

andou/pick-a-trek

4a7845d96472e5bd2242ab8dcb948f619afda8c3

[ "MIT" ]

1

2021-03-14T13:31:30.000Z

_sentieri/2019-10-13-Da_Bertone_a_Monte_Alfeo.markdown

andou/pick-a-trek

4a7845d96472e5bd2242ab8dcb948f619afda8c3

[ "MIT" ]

32

2021-03-06T11:13:10.000Z

2021-04-01T06:58:03.000Z

_sentieri/2019-10-13-Da_Bertone_a_Monte_Alfeo.markdown

andou/pick-a-trek

4a7845d96472e5bd2242ab8dcb948f619afda8c3

[ "MIT" ]

null

--- layout: sentiero longitude : 9.267293 latitude : 44.6226823 title: "Da Bertone a Monte Alfeo" date: 2019-10-13 09:05:00 +0100 track: /assets/tracks/2019-10-13-Da_Bertone_a_Monte_Alfeo.gpx track_color: green categories: - Italia - Appennino Ligure tags: - Tranquillo - Andata e ritorno - Panorami - Natura - Appennino - Facile difficulty: 1 distance: 5.974 duration: 2:32:55 min_elev: 1061 max_elev: 1643 loss_elev: -568 gain_elev: 577 --- Un altro bel sentiero in appennino, in parte nel bosco e in parte in cresta dove (nebbia permettendo...) si gode di una splendida vista.

20.206897

136

0.750853

ita_Latn

0.802555

b59973d9e9de17a67356b95662b967a0d2d2d672

1,404

md

Markdown

README.md

kenhys/fluent-plugin-hipchat

1b532553c7fbcd7b9515f66e63e088aa8d3a6949

[ "Apache-1.1" ]

9

2015-01-02T04:29:12.000Z

2015-10-28T23:44:12.000Z

README.md

kenhys/fluent-plugin-hipchat

1b532553c7fbcd7b9515f66e63e088aa8d3a6949

[ "Apache-1.1" ]

5

2015-08-19T03:18:36.000Z

2017-04-18T08:30:01.000Z

README.md

kenhys/fluent-plugin-hipchat

1b532553c7fbcd7b9515f66e63e088aa8d3a6949

[ "Apache-1.1" ]

6

2015-03-09T05:37:51.000Z

2017-03-30T09:34:44.000Z

# Fluent event to hipchat plugin. [![Build Status](https://travis-ci.org/fluent-plugins-nursery/fluent-plugin-hipchat.svg?branch=master)](https://travis-ci.org/fluent-plugins-nursery/fluent-plugin-hipchat) # Requirements | fluent-plugin-hipchat | fluentd | ruby | |-----------------------|------------|--------| | >= 0.3.0 | >= v0.14.0 | >= 2.1 | | < 0.3.0 | >= v0.12.0 | >= 1.9 | # Installation $ fluent-gem install fluent-plugin-hipchat # Usage <match hipchat> @type hipchat api_token XXX default_room my_room default_from fluentd default_color yellow default_notify 0 default_format html default_timeout 3 # HipChat API Request Timeout Seconds (default 3) key_name message # proxy settings # http_proxy_host localhost # http_proxy_port 8080 # http_proxy_user username # http_proxy_pass password </match> fluent_logger.post('hipchat', { :from => 'alice', :message => 'Hello<br>World!', :color => 'red', :room => 'my_room', :notify => 1, :format => 'text', }) # set topic fluent_logger.post('hipchat', { :from => 'alice', :topic => 'new topic', :room => 'my_room', }) # Copyright Copyright (c) 2012- Yuichi Tateno # License Apache License, Version 2.0

23.4

171

0.566239

kor_Hang

0.224376

b599a435c390974e615b007ceed61ecaffb474e4

102

md

Markdown

README.md

p1yu5h0/dictionary

b4d360eb16d5a7aa2093eb2c6be58585f85b1000

[ "MIT" ]

null

README.md

p1yu5h0/dictionary

b4d360eb16d5a7aa2093eb2c6be58585f85b1000

[ "MIT" ]

1

2021-10-09T04:22:29.000Z

README.md

p1yu5h0/dictionary

b4d360eb16d5a7aa2093eb2c6be58585f85b1000

[ "MIT" ]

null

Made a small Dictionary Project !! <br> Site can be found at:- https://p1yu5h-dictionary.netlify.app/

20.4

38

0.745098

eng_Latn

0.779327

b59a63fc52a29cee54ba3af0cd7afd4cf0eec027

3,783

md

Markdown

_posts/2021-10-10-Web开发入门.md

lixiaogang03/lixiaogang03.github.io

362f7a5d3d940ef1018487f4e74cc991f2575845

[ "MIT" ]

1

2019-08-06T09:49:48.000Z

_posts/2021-10-10-Web开发入门.md

lixiaogang03/lixiaogang03.github.io

362f7a5d3d940ef1018487f4e74cc991f2575845

[ "MIT" ]

218

2021-09-30T06:09:01.000Z

2022-03-31T06:25:33.000Z

_posts/2021-10-10-Web开发入门.md

lixiaogang03/lixiaogang03.github.io

362f7a5d3d940ef1018487f4e74cc991f2575845

[ "MIT" ]

null

--- layout: post title: Web开发入门 subtitle: Getting started with web front-end and back-end development date: 2021-10-10 author: LXG header-img: img/post-bg-rwd.jpg catalog: true tags: - web --- [Web 入门](https://developer.mozilla.org/zh-CN/docs/Learn/Getting_started_with_the_web) [服务器端编程](https://developer.mozilla.org/zh-CN/docs/Learn/Server-side/First_steps/Introduction) [JavaScript Demo](https://github.com/YUUXIAO/webProject) ## Web前端知识准备 * HTML * CSS * JavaScript ![web_front](/images/web/web_front.png) ### HTML 超文本标记语言 (英语：Hypertext Markup Language，简称：HTML ) 是一种用来结构化 Web 网页及其内容的标记语言。网页内容可以是：一组段落、一个重点信息列表、也可以含有图片和数据表。 HTML 不是一门编程语言，而是一种用于定义内容结构的标记语言。HTML 由一系列的元素（elements）组成，这些元素可以用来包围不同部分的内容，使其以某种方式呈现或者工作。 ![web_html](/images/web/web_html.png) **HTML5** HTML5已经远远超越了标记语言的范畴，它的设计目的是在移动设备上支持多媒体，和HTML比起来，深度和广度上都做了进一步提升。 ### CSS CSS （Cascading Style Sheets，层叠样式表）是用来控制网页在浏览器中的显示外观的声明式语言。浏览器会根据 CSS 的样式定义将其选定的元素显示为恰当的形式。一条 CSS 的样式定义包括属性和属性值，它们共同决定网页的外观。和 HTML 类似，CSS 也不是真正的编程语言，甚至不是标记语言。它是一门样式表语言，这也就是说人们可以用它来选择性地为 HTML 元素添加样式。 ![css-declaration](/images/web/css-declaration.png) ![css_rendering](/images/css_rendering.svg) ### JavaScript JavaScript 编程语言允许你在 Web 页面上实现复杂的功能。如果你看到一个网页不仅仅显示静态的信息，而是显示依时间更新的内容，或者交互式地图，或者 2D/3D 动画图像，或者滚动的视频播放器，等等——你基本可以确定，这需要 JavaScript 的参与。 ![web_execution](/images/web/web_execution.png) 在 HTML 和 CSS 集合组装成一个网页后，浏览器的 JavaScript 引擎将执行 JavaScript 代码。这保证了当 JavaScript 开始运行之前，网页的结构和样式已经就位。 ### 服务器端代码 vs 客户端代码服务器端（server-side）和客户端（client-side）代码。客户端代码是在用户的电脑上运行的代码，在浏览一个网页时，它的客户端代码就会被下载，然后由浏览器来运行并展示。这就是客户端 JavaScript。而服务器端代码在服务器上运行，接着运行结果才由浏览器下载并展示出来。流行的服务器端 web 语言包括：PHP、Python、Ruby、ASP.NET 以及...... JavaScript！JavaScript 也可用作服务器端语言，比如现在流行的 Node.js 环境 ## 前端框架现代JavaScript框架的到来加快了打造高度动态化和交互性强的应用程序的速度. 框架就是提供该如何构建应用程序的意见的库。这些意见能使应用具有可预测性和同质性。可预测性让软件能在扩展到很大规模的同时仍保持可维护性。可预测性和可维护性对于一个软件的长久健康运行是十分重要的。 ### Bootstrap Bootstrap 是最受欢迎的 HTML、CSS 和 JS 框架，用于开发响应式布局、移动设备优先的 WEB 项目。 [Bootstrap](https://v3.bootcss.com/) ### React React是 Facebook 开发的框架，用于构建页面、javascript库。主要功能是对DOM操作，声明式设计，更快的开发出web应用系统。 [React](https://react.docschina.org/) ## Angular Angualr 是一款来自谷歌的开源的 web 前端框架，诞生于 2009 年，由 Misko Hevery 等人创建，后为 Google 所收购。是一款优秀的前端 JS 框架，已经被用于 Google 的多款产品当中。 [Angular](https://angular.cn/) ### Vue 渐进式 JavaScript 框架 [Vue](https://v3.cn.vuejs.org/) ## 服务器端编程网络浏览器通过超文本传输协议 (HTTP)来和网络服务器进行通信。当你在网页上点击一个链接，或提交一个表单，再或进行一次搜索时，一个HTTP请求就从你的浏览器发送到了目标服务器。相应一个请求的成功回应包含被请求的资源（比如一个新的HTML页面，或者图片等），然后这些会被展示在客户端的网络浏览器上。 ### 静态网站静态网站是指无论何时当一个特定资源被请求的时候都返回相同的被硬编码的内容 ![static_web_arch](/images/web/static_web_arch.png) ### 动态网站动态网站是指，一些响应内容只有在被需要的时候才会生发的网站。在一个动态网站上，页面通常是通过将数据库的数据植入到HTML模板中的占位符中而产生的（这是一种比使用静态网站有效得多的存储大量内容的方式）动态网站可以基于用户提供的个人信息或者偏好设置来返回不同的数据，并且可以展示作为返回一个回应的内容的一部分的其他操作（比如发送通知）。大多数支持动态网站的代码必须运行在服务器上。编写这些代码就是所谓的“服务器端编程”（有些时候也称“后端脚本编写”）。 ![web_app_steps](/images/web/web_app_steps.png) 对于动态资源的请求则会指向（2）服务器端代码(在图中显示为Web Application（网络应用））。在处理“动态请求”时，服务器会首先解释请求，从数据库中读取被请求的信息，然后将这些被检索的信息组合到HTML模板中（4）,最后返回一个包含所生成的HTML页面的回应（5,6） ### 服务器端框架 [服务端web框架](https://developer.mozilla.org/zh-CN/docs/learn/Server-side/First_steps/Web_frameworks) * Django (Python) * Flask (Python) * Express (Node.js/JavaScript) * Ruby on Rails (Ruby) * ASP.NET * Mojolicious (Perl) ### 服务器编程语言 ![web_language](/images/web/web_language.webp) ### Django Web 框架(python) Django 是一个高级的 Python 网络框架，可以快速开发安全和可维护的网站。由经验丰富的开发者构建，Django负责处理网站开发中麻烦的部分，因此你可以专注于编写应用程序，而无需重新开发。它是免费和开源的，有活跃繁荣的社区，丰富的文档，以及很多免费和付费的解决方案。 ### Express Web Framework (Node.js/JavaScript) Node（正式名称 Node.js）是一个开源的、跨平台的运行时环境，有了它，开发人员可以使用 JavaScript 创建各种服务器端工具和应用程序。 Express 是最流行的 Node 框架，是许多其它流行 Node 框架的底层库。 ### 网站开发的基本步骤 1. 选择云服务器（阿里云，腾讯云，百度云） 2. 购买域名 3. 页面设计，效果图 4. 程序开发 5. 程序测试 6. 购买https证书 7. 程序上线 8. 网站备案

24.406452

140

0.791435

yue_Hant

0.769173

b59afb4d570d765157413ab773bd45ebdee286a2

442

md

Markdown

_equipment/exchangers.md

fluidprocess/jekyll-serif-theme

a3513fd977289574444c5531a929104e9954dcd7

[ "MIT" ]

null

_equipment/exchangers.md

fluidprocess/jekyll-serif-theme

a3513fd977289574444c5531a929104e9954dcd7

[ "MIT" ]

null

_equipment/exchangers.md

fluidprocess/jekyll-serif-theme

a3513fd977289574444c5531a929104e9954dcd7

[ "MIT" ]

1

2021-04-10T11:30:28.000Z

--- title: "Маслоохладители" date: 2018-11-19T10:47:58+10:00 draft: false image: "images/equipment/exchanger.png" jobtitle: "Оборудование" promoted: true weight: 1 layout: equipment --- Теплообменники масло-масло, либо вода-масло производительностью до 30м3/час, по маслу максимальной температуры 110°C. Одноходовые, либо двухходовые, максимальным давлением до 1,6 МПа. Материальное исполнение - углеродистая сталь, либо коррозионностойкое.

31.571429

183

0.798643

rus_Cyrl

0.836843

b59c52f2a299d8e917490c2637747e86c0eab2b5

2,139

md

Markdown

README.md

mpyw/twhelp

725a03f97b9b587e733d89a748d233d626eec46f

[ "MIT" ]

7

2016-12-19T14:29:17.000Z

2021-12-30T17:00:02.000Z

README.md

mpyw/twhelp-go

725a03f97b9b587e733d89a748d233d626eec46f

[ "MIT" ]

3

2016-11-15T20:52:12.000Z

2021-07-02T21:28:42.000Z

README.md

mpyw/twhelp-go

725a03f97b9b587e733d89a748d233d626eec46f

[ "MIT" ]

3

2016-11-15T19:02:59.000Z

2019-11-21T04:35:29.000Z

# twhelp Twitter OAuth CLI Helper distributed by Golang cross-compilation. ## Requirements **Nothing**. Feel free to download from [releases](https://github.com/mpyw/twhelp/releases). ...Oops, x64(amd64) CPU architecture required at least. ## Usage ```ShellSession mpyw@localhost:~$ ./twhelp -h Options: -h, --help Show help. [ Output Format ] Default Output line by line. -i, --ini Output as INI. -y, --yaml Output as YAML. -j, --json Output as JSON. -a, --array Output as array compatible with most languages. -A, --assoc Output as PHP-style associative array. -e, --env Output as environmental uppercase variables. [ OAuth Process ] Default xAuth manipulation with OAuth scraping. -x, --xauth Pure xAuth. Only available with official keys. -o, --oauth Pure OAuth. You have to authorize via web browser. [ OAuth Credentials ] Insufficient components will be required to input via STDIN. Password is masked. --ck <value> Specify consumer_key in advance. --cs <value> Specify consumer_secret in advance. --sn <value> Specify screen_name or email in advance. --pw <value> Specify password in advance. (Not masked, DEPRECATED) --app <value> Speficy consumer_key and consumer_secret with app name. app name | full name ------------------------------------ android | Twitter for Andriod win | Twitter for Windows wp | Twitter for Windows Phone google | Twitter for Google TV iphone | Twitter for iPhone ipad | Twitter for iPad mac | Twitter for Mac deck | TweetDeck Your own applications can also be defined in /Users/mpyw/.twhelp.ini Example: [my_app_01] consumer_key = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" consumer_secret = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" mpyw@localhost:~$ ```

32.409091

79

0.591865

eng_Latn

0.750917

b59ce7e0726e923f55ca6b87d17529156d04fcec

2,581

md

Markdown

signal_processing/fir_filter/fir_filter.md

hitomecha/qiita

6b1099b0289cfe1069ce99a3e54db5a84214232f

[ "Apache-2.0" ]

null

signal_processing/fir_filter/fir_filter.md

hitomecha/qiita

6b1099b0289cfe1069ce99a3e54db5a84214232f

[ "Apache-2.0" ]

null

signal_processing/fir_filter/fir_filter.md

hitomecha/qiita

6b1099b0289cfe1069ce99a3e54db5a84214232f

[ "Apache-2.0" ]

null

--- title: R言語を用いたFIRフィルタの作成 tags: R author: hitomecha slide: false --- 初心者向きにR言語を用いたFIRフィルターの作成方法をまとめました。基本的な流れは、前回投稿した[R言語を用いたIIRフィルターの作成](https://qiita.com/hitomecha/items/80d6e3309aa33941cb5e)とほぼ同じです。 ## パッケージの準備 signal パッケージ[1]を使用し、FIRフィルターを作成します。まず、パッケージをインストールします。 ```R #signalパッケージのダウンロード install.packages("signal") #ライブラリーの読み込み library("signal") ``` ## 入力データの準備入力データは10Hzと50Hzの正弦波の合成波を使用します。 ```R #入力データの作成（周波数が10Hzと50Hzのサイン波のデータの合成、サンプリング周波数：1kHz、１０秒間のデータ） time <- seq(from=0, by=1/1000, length=10000) #時間軸 data <- sin(2*pi*10*time) + sin(2*pi*50*time) #入力データの図示 plot(time, data, t="l", xlim=c(1, 1.5)) ``` <img src="https://qiita-image-store.s3.amazonaws.com/0/293436/ba610be0-f14a-761c-e13e-4656e1a3682c.png" width=50%> 上図より、2つの周波数の合成波になっています。また、周波数解析を行うと、 ```R data_fft <- fft(data) data_psd <- abs(data_fft)^2 plot_fft <- seq(from=1/10000, by=1000/10000, to=500) #入力データの周波数特性の図示 plot(plot_fft, data_psd[1:(length(data_psd)/2)], t="l", log="x", xlab="frequency (Hz)", ylab="PSD (1/Hz)") ``` <img src="https://qiita-image-store.s3.amazonaws.com/0/293436/c415c59a-4cfa-117f-0958-da7c01fcb98d.png" width=50%> ピークが2つ（10Hzと50Hz）になっていることがわかります。 ## FIRフィルターの設計今回はFIRフィルターを実装するために、signalパッケージのfir1()を使用します。5〜15Hzを通すバンドパスフィルターを実装します。 ```R #バンドパスフィルタの設計 #FIRフィルターの各パラメータ fil_N <- 128 #フィルターの次数 fs <- 1000 #サンプリング周波数 fn <- fs/2 #ナイキスト周波数 fc <- c(5,15) #帯域通過周波数 fc_norm <- fc/fn #周波数の正規化 fir_filter <- fir1(fil_N, fc_norm, type="pass") ``` fir1()では、帯域周波数をナイキスト周波数で割った正規化周波数を使います。typeは、pass, low, high, stopの指定により、様々な種類のフィルターを実装できます。 ## フィルター特性の確認 ```R freqz(fir_filter, Fs=fs) #フィルター特性の図示 ``` <img src="https://qiita-image-store.s3.amazonaws.com/0/293436/204628bc-a5d9-7a80-d73b-fc88484a268b.png" width=70%> 5〜15Hzのバンドパスフィルターを設計できました。 ## 設計したフィルターを入力データに通す ```R #設計したフィルターを入力データに適応 data_fil <- filtfilt(fir_filter, data) ``` フィルターによる位相遅れを防ぐためにfiltfilt()を使用し、順方向と逆方向の両方の処理を行うゼロ位相デジタルフィルター処理を実装します。 ## フィルターを通したデータの確認 ```R #フィルターを通したデータの図示 plot(time, data_fil, t="l", xlim=c(1, 1.5)) #周波数特性の図示 data_fft <- fft(data_fil) data_psd <- abs(data_fft)^2 plot(plot_fft, data_psd[1:(length(data_psd)/2)], t="l", log="x", xlab="frequency (Hz)", ylab="PSD (1/Hz)") ``` <img src="https://qiita-image-store.s3.amazonaws.com/0/293436/b078c3d8-b1a3-6718-93ca-e9006517f10d.png" width=50%><img src="https://qiita-image-store.s3.amazonaws.com/0/293436/6007a42c-da36-bab5-65fc-1bb5dc442b49.png" width=50%> フィルターにより50Hz成分がなくなりました。 ### 参考文献 [1] Uwe Ligges et al. "Signal Processing", ver. 0.7-6, https://cran.r-project.org/web/packages/signal/signal.pdf, 参照July 7, 2018.

26.336735

228

0.740798

yue_Hant

0.254223

b59d8f3601f6945021b6863a91d0a1cba55eb304

190

md

Markdown

README.md

yami-beta/pwa-tutorial

dfcd8dfcad7263677c685177afd07274f069e72b

[ "Apache-2.0" ]

null

README.md

yami-beta/pwa-tutorial

dfcd8dfcad7263677c685177afd07274f069e72b

[ "Apache-2.0" ]

null

README.md

yami-beta/pwa-tutorial

dfcd8dfcad7263677c685177afd07274f069e72b

[ "Apache-2.0" ]

null

# pwa-tutorial This is personal repository for learning Progressive Web App. Original repository is [googlecodelabs/your-first-pwapp](https://github.com/googlecodelabs/your-first-pwapp).

38

109

0.805263

eng_Latn

0.862031

b59df830d8c2a0d2c547e47e9980ed956b210fd2

2,348

md

Markdown

docs/theme/custom-css.md

jerdog/gitpitch

16603efa4b514688bdefba519bf9b52d4f4599dd

[ "MIT" ]

null

docs/theme/custom-css.md

jerdog/gitpitch

16603efa4b514688bdefba519bf9b52d4f4599dd

[ "MIT" ]

null

docs/theme/custom-css.md

jerdog/gitpitch

16603efa4b514688bdefba519bf9b52d4f4599dd

[ "MIT" ]

null

# Custom CSS The [Theme Builder](/theme/builder.md) is recommended for making basic theme customizations for your slide decks. For more targeted customization you can activate custom CSS for any slide deck. As a presentation author you can define and activate new CSS style rules that override the default style rules inherited from the base theme for your slide deck. ?> The base theme for your slide deck is defined by the [Theme Template](/theme/template.md). ### Activation To enable custom CSS style rules you must activate the `theme-override` setting in the [PITCHME.yaml](/conventions/pitchme-yaml.md) for your slide deck. For example: ```yaml theme-override : assets/css/PITCHME.css ``` Once activated, all custom CSS style rules will be applied to the content on your slides. ### Sample Slide The following CSS snippet declares a custom style rule that activates a striped-effect using alternating colors on list items: ```css ul.striped-list-items { color: #001F3F; } ul.striped-list-items > li:nth-child(even){ color: white; } ``` These custom style rules must be activated using the `theme-override` setting in the [PITCHME.yaml](/conventions/pitchme-yaml.md) for our sample deck. Once activated we can enable our custom `striped-list-items` style directly on any instance of the [list widget](/list/widgets.md) as shown here: ![Sample slide demonstrating list widget custom style](../_images/gitpitch-lists-styles-custom.png) ?> Note the activation of the custom **striped-list-items** style on the sample list widget above. ### Web Inspector If you intend activating custom CSS style rules that override the base theme we recommend using a *Web Inspector* to directly inspect the content on your slides. By inspecting existing content you can quickly learn what style rules you may need to override to enable custom styles for your deck. Web Inspectors are typically a *Developer Tools* feature in your browser. Inspectors give you an opportunity to experiment with *tweaks* and *overrides* and see the results instantly updated in your slideshow directly within the browser. Once you have achieved the effects you are after using the Web Inspector you can then capture the new rules in your own custom CSS file. To then activate those custom CSS styles using the `theme-override` setting as described above.

48.916667

296

0.781942

eng_Latn

0.99759

b59e3e55bbb8c0ac5f37fdda1c7917b624b0ecca

475

md

Markdown

slides/motivation.md

sezna/EthCC-2021

b0100dd6e952772f54e06ec67c2ab2362a92f800

[ "MIT" ]

null

slides/motivation.md

sezna/EthCC-2021

b0100dd6e952772f54e06ec67c2ab2362a92f800

[ "MIT" ]

null

slides/motivation.md

sezna/EthCC-2021

b0100dd6e952772f54e06ec67c2ab2362a92f800

[ "MIT" ]

null

# What is Sway? Note: Sway was motivated by Solidity and Rust. We believe Rust made a lot of correct decisions in its implementation, and we want to combine that with the ergonomic first-class blockchain support that Solidity brings to the table. Look at its adoption: it is used more than approaches that import libraries and APIs into existing general purpose langauges to accomplish the same task. Using a language designed for this domain is what people want.

52.777778

126

0.791579

eng_Latn

0.999938

b59ebd14a5da08f176eabf0abd7c46cc7587c77f

3,955

md

Markdown

pages/media/propresenter/preparing-a-video-for-pro-presenter.md

NewValleyChurch/documentation-theme-jekyll

58b4ff83e07d91eadf8ca239f3d8444a3eb1dd45

[ "MIT", "BSD-3-Clause" ]

null

pages/media/propresenter/preparing-a-video-for-pro-presenter.md

NewValleyChurch/documentation-theme-jekyll

58b4ff83e07d91eadf8ca239f3d8444a3eb1dd45

[ "MIT", "BSD-3-Clause" ]

null

pages/media/propresenter/preparing-a-video-for-pro-presenter.md

NewValleyChurch/documentation-theme-jekyll

58b4ff83e07d91eadf8ca239f3d8444a3eb1dd45

[ "MIT", "BSD-3-Clause" ]

null

--- title: "How to: Prepare a Video for ProPresenter" layout: page comments: true sidebar: main_sidebar toc: true topnav: topnav image_folder: images document_folder: documents keywords: video summary: "A quick guide to displaying video on the sanctuary screen for Sunday Morning Service" permalink: peparing-a-video-for-pro-presenter.html folder: media --- ## Steps: # When the Video we need to play is smaller than our screen. ## Create the Video Document 1. Obtain highest quality copy of original or rendered original as possible. 2. Save the file to /Volumes/Blue/ProPresenter/Video Any video that we download to be presented needs to be organized in this folder, which is a centralized network location. 3. In ProPresenter, create a new document: - Press ⌘ + N. {% include image.html file="crashvideos.jpg" %} - In `New File Name:` enter the title of the Video. Omit the word video from the title as that would be redundant. a) The video is going to be saved to the /Volumes/Blue/ProPresenter/**Video** folder, b) the video will have an extension that indicates that it's a video (*.mov, *.mp4, etc.), and c) we're going to categorize it as a video. - Click the Template dropdown and select an appropriate video template for the slide. - Under Category, select Video. - For Size, select 3600 X 1200. ## Set the Slide Cues for the first slide This will depend on what you want to have happen. 1. Open the cue palette (Shift-CTRL-C) or right click the slide -> Add Cue -> Cue Palette. 1. Clear the appropriate elements from whatever was last displayed by dragging each cue from the cue palette to the first slide in the document. 1. If there are any backgrounds unique to this video, use the Media Cue "Graphic" to browse to the Images folder (/Volumes/Blue/ProPresenter/Images). If you chose a video template that already has a static background that we use regularly, you don't need additional graphics. 1. Add a stage display cue that's appropriate for this point in the service. 1. Add a timer cue and choose an appropriate timer countdown with the action "Reset and Start Timer" 1. Add any prop cues that apply such as logos, transparent overlays, etc. 1. Add any masks, messages or social media cues that apply. 1. Close the Cue Palette ## Add the Video to the Slide {% include important.html content="There is a specific way to reference a video in ProPresenter. Dragging and dropping a video into ProPresenter will cause problems. Make sure you reference the video as explained here." %} 1. Right click the slide in the document where the video will be displayed. At this point, it's probably the first and only slide. 1. Click `Edit Slide`. 1. Click the `Add Video to Slide` button on the toolbar above the slide. 1. Choose the video file that was saved to the /Volumes/Blue/ProPresenter/Video folder. 1. Click Select. 1. The video should insert itself dead center on the slide inside of, or directly on top of the frame placeholder in the slide. 1. Click the Object Properties icon in the slide properties inspector on the right. 1. Change the width and height of the element to match the size of the frame on the template. In this case, 1920X1080 would be a standard aspect ratio. If the video is rendered at a lower resolution, such as 1280X720, you can still use 1920X1080 as your dimensions. If you don't know the original dimensions of the video, you can find out by using the Mac Finder to browse to /Volumes/Blue/ProPresenter/Video. Right click the video file and click `Get Info` then click the arrow next to `More Info.` This will show you the Dimensions. The most important aspect of this is making sure that the ratio of length X width remains the same, and that you don't blow up a small video to be too large for it's resolution. 1. Set the X and Y coordinates to be 840 and 60 respectively. 1. Close the slide editor and test your new slide.

56.5

718

0.758028

eng_Latn

0.998294

b5a03179a9955442cc910455bd56ab10262d3593

4,434

md

Markdown

_posts/2011-06-20-pulp-community-release-13.md

goosemania/pulpproject.org

3b9bbece6177dd5be870c653eb35fa9d7e0f223b

[ "MIT" ]

5

2017-07-27T15:53:49.000Z

2021-07-18T21:46:00.000Z

_posts/2011-06-20-pulp-community-release-13.md

goosemania/pulpproject.org

3b9bbece6177dd5be870c653eb35fa9d7e0f223b

[ "MIT" ]

138

2016-07-28T20:07:10.000Z

2022-03-21T13:43:38.000Z

_posts/2011-06-20-pulp-community-release-13.md

goosemania/pulpproject.org

3b9bbece6177dd5be870c653eb35fa9d7e0f223b

[ "MIT" ]

48

2016-05-19T19:00:31.000Z

2022-02-22T07:45:52.000Z

--- id: 351 title: Pulp Community Release 13 date: 2011-06-20T14:17:02+00:00 author: Jay Dobies layout: post guid: http://blog.pulpproject.org/?p=351 permalink: /2011/06/20/pulp-community-release-13/ categories: - Releases --- <img src="http://website-pulp.rhcloud.com/wp-content/uploads/2011/06/cr-13-2.png" alt="" title="cr-13-2" width="442" height="161" class="alignnone size-full wp-image-352" srcset="http://www.pulpproject.org/wp-content/uploads/2011/06/cr-13-2-300x109.png 300w, http://www.pulpproject.org/wp-content/uploads/2011/06/cr-13-2.png 442w" sizes="(max-width: 442px) 100vw, 442px" /> ## Installation Installation instructions can be found [in the Pulp User Guide](http://pulpproject.org/ug/UGInstallation.html#installation) at the [Pulp project web site.](http://www.pulpproject.org) ## Enhancements * [Errata enhancements](https://fedorahosted.org/pulp/wiki/PulpCli#ErrataActions) including: * Ability to search errata using various parameters such as id, type, and repository association. * Ability to list all errata including orphaned errata filtered by type. * Tasks are now persisted to the database instead of simply being stored in memory. * Unscheduled tasks will now resume if interrupted by a Pulp crash or restart. * Task history for repository and CDS syncs available. * Administrative transparency into the task subsystem can be found in the `pulp-admin`. To enable support for this command, edit `/etc/pulp/client.conf` and set `[admin] expose_task_command = True`. </ul> * Repository discovery enhancements from the previous sprint’s implementation: * Support added for discovering authenticated repositories. * Support added for discovering mirror lists and redirected URLs. * Increased process visibility through incremental feedback. * A yum plugin has been added to automatically update consumer profile information in the Pulp server after all yum transactions. * [CDS Clusters](http://pulpproject.org/ug/UGCDS.html#clusters) have been added, which will automatically maintain consistency of repository associations across all CDS instances in the cluster, allowing for one-step provisioning of CDS instances to support high load scenarios. * Consumers now have support for protected repositories. When a consumer certificate is specified for a repository in Pulp, it is downloaded to the consumer and referenced in the repository definition. * Fixed 22 bugs, accessible through [bugzilla.](https://bugzilla.redhat.com/buglist.cgi?target_release=Sprint%2024&query_format=advanced&product=Pulp&classification=Other) ## Upgrade Notes * Run `pulp-migrate` to upgrade to the latest database changes. * Fedora 13 is no longer supported. * The x.509 private key and certificates were consolidated to be stored as a single, combined file. Any x.509 `--key` CLI options are optional so long as the file referenced in `--cert` option contains both the private key and certificate. After upgrading Pulp, existing certificates stored on the file system will no longer be valid unless the private key and certificates are combined. This has the following effects on upgraded systems: * Repositories that have been defined with feed or consumer certificates will need to be updated with the certificate information again. Even if the optional `--key` support is used, this step needs to occur again so the Pulp server will correctly combine and store the certificate and private key on the server. * Consumer certificates may be manually combined (alternatively, the consumer can be deleted and re-registered). To manually upgrade a consumer, combine the `key.pem` and `cert.pem` files in the `/etc/pki/consumer` directory into a single file named `cert.pem`. * Users will need to regenerate their user certificate by logging out and then logging back in (`pulp-admin auth logout` and `pulp-admin auth login -u [user] -p [password]` respectively. ## Fedora 15 Support The Fedora 15 build requires mongo 1.7.5 due to an issue in version 1.8 that can cause the mongo shell to hang. Users installing or upgrading pulp on an F15 instance that already has mongo 1.8 installed will need to manually downgrade to mongo 1.7.5. ## Build Versions * Pulp: 0.191 * Grinder: 0.103 * Gofer: 0.41

86.941176

446

0.750789

eng_Latn

0.989755

b5a09e1e0b802f4e60ad827122e26b94877184f7

71

md

Markdown

README.md

jakkor/backbone_handlebars_example

7f50d00b9fc3b0010b809a9548f748e9097823da

[ "MIT" ]

null

README.md

jakkor/backbone_handlebars_example

7f50d00b9fc3b0010b809a9548f748e9097823da

[ "MIT" ]

null

README.md

jakkor/backbone_handlebars_example

7f50d00b9fc3b0010b809a9548f748e9097823da

[ "MIT" ]

null

Work in progress... Proper readme and description will be added later.

23.666667

50

0.788732

eng_Latn

0.997497

b5a12a5d8e35a08bc179cac6c8fac102f506084f

6,008

md

Markdown

_toolbox/G-y-links.md

gcpeixoto/gcpeixoto.github.io

d913bafb8a183769f7d016b3d88cb022b21ac864

[ "MIT" ]

null

_toolbox/G-y-links.md

gcpeixoto/gcpeixoto.github.io

d913bafb8a183769f7d016b3d88cb022b21ac864

[ "MIT" ]

null

_toolbox/G-y-links.md

gcpeixoto/gcpeixoto.github.io

d913bafb8a183769f7d016b3d88cb022b21ac864

[ "MIT" ]

null

--- title: G-ψ - Useful links --- ## Geology glossary - [Illustrated Geologic Glossary by CPRM Brazil (PT only)](http://sigep.cprm.gov.br/glossario/index.html) ## Oil and gas glossaries - [PPSA Glossary (PT only)](http://www.presalpetroleo.gov.br/ppsa/glossario-da-industria-de-petroleo-e-gas/a) - [PPSA Abbreviation List (PT only)](https://www.presalpetroleo.gov.br/ppsa/legislacao/siglario) - [Schlumberger Oilfield Glossary](https://www.glossary.oilfield.slb.com) ## TRL and CRL TRL (_Technological Readiness Level_) and CRL (_Commercial Readiness Level_) are measurement systems used to assess the maturity level of a particular technology from research to market. In academia, TRL has been adapted to R,D&I value chain. - [Original TRL by NASA](https://www.nasa.gov/directorates/heo/scan/engineering/technology/txt_accordion1.html) - [TRL by CERTI](https://certi.org.br/blog/trl-desenvolvimento-projetos/) - [TRL/CRL by Petrobras](../_media/files/trl-crl-petrobras.png) ## Virtual MIDI for online meetings - [BlackHole](https://github.com/ExistentialAudio/BlackHole) ## Teaching-learning resources - [Cmap Tools](https://cmap.ihmc.us/cmaptools/), for knowledge modeling. - [OER Commons](https://www.oercommons.org), a public digital library of open educational resources. - [Internet Archives](https://archive.org//), a lot of stuff - [Wikimedia Commons](https://commons.wikimedia.org/wiki/Main_Page), media file repository making available public domain and freely licensed educational media content (images, sound and video clips). - [Europeana](https://www.europeana.eu/en), European archives, libraries and museums to share cultural heritage for enjoyment, education and research. - [MERLOT](https://www.merlot.org/merlot/index.htm), curated online learning and support materials. ## Platforms - [Bandcamp](bandcamp.com), all about music. - [The Music of 3Blue1Brwon](https://vincerubinetti.bandcamp.com/album/the-music-of-3blue1brown), free to download; attribution for usage. - [Sketchfab]([https://sketchfab.com), AR and 3D models. - [Free Music Archive](https://freemusicarchive.org), filmaking songs and soundtracks. - [SkillsCommons](https://www.skillscommons.org), commons for workforce and team training. - [Jamendo](https://www.jamendo.com/start), free music to download (for personal use). For public stream/professional, checking out. - [Unsplash](https://unsplash.com), freely-usable images. - [Pixabay](https://pixabay.com/pt/), pics, vecs, vids, and more free to use. - [Pexels](https://www.pexels.com), free stock photos and vids. - [Stocksnap](https://stocksnap.io), pics. ## Scientific societies, agencies, and related events ### Brazil - [ABCM - Brazilian Society of Mechanical Sciences and Engineering](https://abcm.org.br) - COBEM - International Congress of Mechanical Engineering (biannually) - CONEM - National Congress of Mechanical Engineering (biannually) - CREEM - National Congress of Mechanical Engineering Students (annually) - ENCIT - Brazilian Congress of Thermal Sciences and Engineering (biannually) - [ABEAMA - Brazilian Association of Alternative Energies and Environment](https://abeama.org.br) - [ABMEC - Brazilian Association of Computational Methods in Engineering](http://www.abmec.org.br) - CILAMCE - Ibero-Latin-American Congress on Computational Methods in Engineering (annually) - PANACM - Pan American Congress on Computational Mechanics - [ABSOLAR - Brazilian Solar Photovoltaic Energy Association](https://www.absolar.org.br) - [CGEE - Centro de Gestão e Estudos Estratégicos](https://www.cgee.org.br) - [CGI - Comitê Gestor da Internet no Brasil](https://www.cgi.br) - [IBP - Brazilian Petroleum, Gas and Biofuels Institute](https://www.ibp.org.br) - RIO Oil & Gas - [SBMAC - Brazilian Society of Computational and Applied Mathematics](https://www.sbmac.org.br) - CMAC - Congress of Applied and Computational Mathematics (regional) - CNMAC - National Congress of Applied and Computational Mathematics - ERMAC - Regional Meeting of Applied and Computational Mathematics - [SPE - Society of Petroleum Engineers](https://www.spe.org/en/) - OTC - Offshore Technology Conference ### International - [IACM - International Association on Computational Mechanics](https://iacm.info/#) - WCCM - World Congress on Computational Mechanics - [NIST - U.S. National Institute of Standards and Technology](https://www.nist.gov) - [OSTI - U.S. Dept. of Energy Office of Scientific and Technical Information](https://www.osti.gov) - [USACM - U.S. Association on Computational Mechanics](https://www.usacm.org) - USNCCN - U.S. National Congress on Computational Mechanics - MMLDT-CSET (2021) - Mechanistic Machine Learning and Digital Twins for Computational Science, Engineering & Technology ## Interesting companies, startups, spin-offs - [Axonal](https://www.axonal.com.br) - Patent and intellectual property consulting. - [Centre for Net Zero](https://www.centrefornetzero.org) - Pioneering research that gets us to net zero quickly, fairly and affordably. - [DWL USA](http://dwl-usa.com/aidatasolutions/) - AI for Measurement While Drilling. - [equadratures](https://equadratures.org) - First and foremost a scientific organisation with a global footprint. We are proud to make freely available the various modules and codes we develop, and see their use across a range of data science problems. - [Green Domus](https://www.greendomus.com.br) - Specialized in the sustainability sector, Green Domus provides consulting, auditing and verification services. - [Intelie](https://www.intelie.com/#oilgas) - Research on event correlation in real-time and anomaly detection, along with experience in management and agile development of IT projects - [Wood Mackenzie](https://www.woodmac.com/short-term-analytics/) - Short-term analytics for energy market. ## Journal watchlist - [Data Centric Engineering](https://www.cambridge.org/core/journals/data-centric-engineering) - [Journal of Petroleum Technology](https://jpt.spe.org)

60.08

253

0.764814

eng_Latn

0.45539

b5a18e11b66f0f9bd438fadef6ae9cf44c554c88

1,122

md

Markdown

spring_2019/week_09.md

Schmaj/rcos-status-updates

116659cc571c6aa042b5d55a2a51ff2ce9e91a68

[ "MIT" ]

null

spring_2019/week_09.md

Schmaj/rcos-status-updates

116659cc571c6aa042b5d55a2a51ff2ce9e91a68

[ "MIT" ]

null

spring_2019/week_09.md

Schmaj/rcos-status-updates

116659cc571c6aa042b5d55a2a51ff2ce9e91a68

[ "MIT" ]

null

## Last Week's Accomplishments > This last week I have implemented a basic algorithm for a demo during the presentation. I have also added more tests to the project to ensure the demo runs smoothly. Afterwards, I went back to OpenCircuits proper in order to fix a bug with the Demux. The outputs were not updating, and the output count would not change from 4. To fix the first issue, I forced all the outputs to 0 before activating the correct port. The second issue was more challenging. The setOutputs method was not being called at all, so I called it in the setInputs method. This fixed the changing, but it was still limited to 8 outputs, when the limit should be 256. After more class diving, I learned where the outputs get "clamped" and raised the limit. ## This Week's Plan > This week's plan is to prepare for the presentation next week. This includes making and modifying the slides, preparing what to say and when, and and mentally preparing for speaking in front of an audience. ## Anything Blocking? > There is currently nothing blocking development yet. At least nothing foreseen. ## Notes

43.153846

91

0.777184

eng_Latn

0.999951

b5a490117b4621429aa77ed2afb2702e8f093a46

41

md

Markdown

_includes/03-links.md

readefries/markdown-portfolio

79fe4f94ac83c4f04f7f4b732191b269dff7409e

[ "MIT" ]

null

_includes/03-links.md

readefries/markdown-portfolio

79fe4f94ac83c4f04f7f4b732191b269dff7409e

[ "MIT" ]

7

2020-10-26T11:06:27.000Z

2020-10-26T13:59:10.000Z

_includes/03-links.md

readefries/markdown-portfolio

79fe4f94ac83c4f04f7f4b732191b269dff7409e

[ "MIT" ]

null

[GitHub](https://github.com/readefries/)

20.5

40

0.731707

zul_Latn

0.353146

b5a54122dd37bbc269a9606576fa6a29ecefb450

1,385

md

Markdown

README.md

Games-of-Threads/DBEX1-KFS

ff7627ab1a4cfe6966bbdd76da11f4877e149e7b

[ "MIT" ]

null

README.md

Games-of-Threads/DBEX1-KFS

ff7627ab1a4cfe6966bbdd76da11f4877e149e7b

[ "MIT" ]

null

README.md

Games-of-Threads/DBEX1-KFS

ff7627ab1a4cfe6966bbdd76da11f4877e149e7b

[ "MIT" ]

null

# Database excercise 1 (Key-Value Stores) This is for the first database assignment related to key-value storage, ## how to use ### step 1. Have windows running either on a virtual machine or base. ### step 2. download the this repository either with a browser or git commands through terminal ### step 3. Navigate to the release folder from the root folder and execute the program. (note I'm unsure if it's needed but .NET framework may be needed other than the base windows, but don't think about it until you experience errors) ### step 4. Engage with the system #### Commands text commands from base is the following. ``` add check exit ``` every command is executed with a enter key, and some commands have a press a key to continue without a prompt to allow overview. #### add this commands allows you to add new people entries to the system, it follows a strict structure that goes as follows. first you give it the index key, this can be 0 but I recommend choosing any positive integer. second it ask for a name, comply with a string name, please don't use ; or [ or ] :( third it as for a status, comply like previously. You succesfully added a person if you followed this correctly. #### check input the integer of the entry you wish to check, input 0 if you wish to check all. #### exit this exits the application with a little bye bye! note.

39.571429

147

0.742238

eng_Latn

0.999916

b5a6130762217fec409110a718462d2f81e144b8

275

md

Markdown

_datasets/Zurich.md

mitchvolpi/mitchvolpi.github.io

1b3f55920b2033bbee37c71a2a022819da27e432

[ "MIT" ]

null

_datasets/Zurich.md

mitchvolpi/mitchvolpi.github.io

1b3f55920b2033bbee37c71a2a022819da27e432

[ "MIT" ]

null

_datasets/Zurich.md

mitchvolpi/mitchvolpi.github.io

1b3f55920b2033bbee37c71a2a022819da27e432

[ "MIT" ]

null

--- title: "Zurich Summer Dataset v0.1" collection: datasets permalink: /_datasets/zurich excerpt: '' date: 2016 paperurl: 'http://academicpages.github.io/files/paper1.pdf' citation: 'Your Name, You. (2009). "Paper Title Number 1." <i>Journal 1</i>. 1(1).' --> ---

30.555556

97

0.694545

yue_Hant

0.737765

b5a69980d6591ff01b5ac385a9116c1ac552e03e

5,885

md

Markdown

06_cnn/README.md

gabrielle-ohlson/MS_038_F21

1f1f46dd597cd61838aa4577728e5083c8d12783

[ "MIT" ]

73

2020-08-27T15:28:56.000Z

2022-03-25T16:35:36.000Z

06_cnn/README.md

gabrielle-ohlson/MS_038_F21

1f1f46dd597cd61838aa4577728e5083c8d12783

[ "MIT" ]

2

2020-09-30T12:52:46.000Z

2020-11-01T19:59:18.000Z

06_cnn/README.md

gabrielle-ohlson/MS_038_F21

1f1f46dd597cd61838aa4577728e5083c8d12783

[ "MIT" ]

10

2020-09-01T02:32:47.000Z

2022-03-16T21:45:12.000Z

# Convolutional Neural Network (CNN) - [Week 6 CNN Slides](https://docs.google.com/presentation/d/1YMlrmpkewAZE5abcoruBztRvsTdVvq1BjtqXauW66Zg/edit?usp=sharing) ## Session A: What is CNN? ### Objectives: - Understand when and why you might train your own model from scratch versus use a pre-trained model or transfer learning. - Learn about the Google “Quick, Draw!” dataset. - Understand how ato work with image data for training your own model. ### Quick, Draw! Data - [Data and Documentation](https://github.com/googlecreativelab/quickdraw-dataset) - [Video tutorial: Replaying Drawings with node server](https://thecodingtrain.com/CodingChallenges/122.1-quick-draw) - [Video tutorial: Replaying Drawings with Google Web API](https://thecodingtrain.com/CodingChallenges/122.2-quick-draw) - [Preparing Data as Images for Doodle Classifer Part 1](https://youtu.be/gX7U6WA7Ffk) - [Preparing Data as Images for Doodle Classifer Part 2](https://youtu.be/wMe6qcpD8jI) ### Examples - [Displaying MNIST](https://editor.p5js.org/ima_ml/sketches/ndqnn8p3F) - [Displaying Quick, Draw! 28x28 images](https://editor.p5js.org/ima_ml/sketches/wOO4nvwyw) - [Animating Quick, Draw! paths](https://editor.p5js.org/ima_ml/sketches/aT9zxHX7n) ### Creative Quick, Draw! projects - [Letter collages](http://frauzufall.de/en/2017/google-quick-draw/) by [Deborah Schmidt](http://frauzufall.de/) - [Face tracking experiment](https://www.instagram.com/p/BUU8TuQD6_v/) by [Neil Mendoza](http://www.neilmendoza.com/) - [Faces of Humanity](http://project.laboiteatortue.com/facesofhumanity/) by [Tortue](www.laboiteatortue.com) - [Scribbling Speech](http://xinyue.de/scribbling-speech.html) by [Xinyue Yang](http://xinyue.de/) - [How do you draw a circle?](https://qz.com/994486/the-way-you-draw-circles-says-a-lot-about-you/) ### Other Related Projects: - [Machine Learning for Visualization by Ian Johnson](https://medium.com/@enjalot/machine-learning-for-visualization-927a9dff1cab) - [MegaPixels: Faces](https://ahprojects.com/megapixels-glassroom/) curated by Tactical Tech, design and development by Adam Harvey - [Watch What Neural Networks See](https://experiments.withgoogle.com/what-neural-nets-see) by Gene Kogan - [Recognizing Human Facial Expressions With Machine Learning](https://thoughtworksarts.io/blog/recognizing-facial-expressions-machine-learning/) by Angelica Perez ## Session B: Doodle Classification ### Objectives - Learn to train an image classifier (no convolutional layers) with ml5.js. - Learn the distinction between different types of layers of a neural network, specifically “What is a convolutional layer?” - Learn to feed the input of a graphics canvas into a machine learning model. ### Video Tutorials - [What is Convolutional Neural Network Part 1](https://youtu.be/qPKsVAI_W6M?list=PLRqwX-V7Uu6YPSwT06y_AEYTqIwbeam3y) - [What is Convolutional Neural Network Part 2](https://youtu.be/pRWq_mtuppU?list=PLRqwX-V7Uu6YPSwT06y_AEYTqIwbeam3y) ### Convolutional Neural Nets - [Original 1998 "LetNet5" paper: "Gradient-Based Learning Applied to Document Recognition"](http://yann.lecun.com/exdb/publis/pdf/lecun-01a.pdf) by Y. Lecun, L. Bottou, Y. Bengio, P. Haffner - [Interactive Node-Link Visualizations of Convolutional Neural Networks](http://scs.ryerson.ca/~aharley/vis/) - [How computers got shockingly good at recognizing images](https://arstechnica.com/science/2018/12/how-computers-got-shockingly-good-at-recognizing-images/) by Timothy B. Lee - [Image Kernels Explained Visually](http://setosa.io/ev/image-kernels/) by Victor Powell - [A visual and intuitive understanding of deep learning, CNNs](https://www.youtube.com/watch?v=Oqm9vsf_hvU) (0:00 - 9:40) by Octavio Good ### Examples - [p5.js Convolution demo](https://editor.p5js.org/codingtrain/sketches/BN1lE-gyl) - [p5.js Convolution demo -- max pooling](https://editor.p5js.org/codingtrain/sketches/GMRfsK7Wn) - [Training a model with `ml5.neuralNetwork()` and Google Quick, Draw! images](https://editor.p5js.org/ima_ml/sketches/bL6jONrFQ) - [Classifying Drawings with ml5's DoodleNet](https://editor.p5js.org/ima_ml/sketches/IbXlN6voN) (model trained by @yining1023) ### Assignment 6 Due Sunday October 18 #### Reading - [An Intuitive Explanation of Convolutional Neural Networks](https://ujjwalkarn.me/2016/08/11/intuitive-explanation-convnets/) by Ujjwal Karn - [Exploring and Visualizing an Open Global Dataset](https://research.googleblog.com/2017/08/exploring-and-visualizing-open-global.html) by Google Research #### Reflection - After playing [Quick, Draw](https://quickdraw.withgoogle.com/) in class, reviewing the [Quick, Draw](https://quickdraw.withgoogle.com/data), and reading the above [Exploring and Visualizing an Open Global Dataset](https://research.googleblog.com/2017/08/exploring-and-visualizing-open-global.html) by Google Research, consider the following question. How can visualization help diagnose "data for inclusion" and "identify concrete ways that anyone can improve the variety of data, as well as check for potential biases." #### Coding Exercise - Build off of one of the following code examples (or invent your own) to develop you own creative use of Quick, Draw data. - [Rendering Quick, Draw drawings](https://editor.p5js.org/ima_ml/sketches/vCfQL93k7) - [Animating Quick, Draw! paths](https://editor.p5js.org/ima_ml/sketches/aT9zxHX7n) - [Classifying Drawings with ml5's DoodleNet: output in DOM element](https://editor.p5js.org/ima_ml/sketches/IbXlN6voN) -- *Can you make this one work with webcam input instead of canvas?* - [Classifying Drawings with ml5's DoodleNet: output in separate canvas](https://editor.p5js.org/ima_ml/sketches/XIZEoKBTL) Complete a blog post with thoughts on the Quick, Draw dataset and your code exercise. [Link from the homework wiki](https://github.com/ml5js/Intro-ML-Arts-IMA-F20/wiki/Assignment-6).

65.388889

522

0.772642

eng_Latn

0.472791

b5a74a69c78105e8abbb139e5ecf45e0e707a237

3,151

md

Markdown

_posts/2017-04-24-mono-linux-package-repository-changes-beginning-with-5-0.md

anuragsharma33/website

f7eaf5450b42fc4ac27da49bc6ac32f56544c0c8

[ "MIT" ]

345

2015-01-02T06:05:22.000Z

2022-03-27T21:04:20.000Z

_posts/2017-04-24-mono-linux-package-repository-changes-beginning-with-5-0.md

anuragsharma33/website

f7eaf5450b42fc4ac27da49bc6ac32f56544c0c8

[ "MIT" ]

240

2015-01-02T09:21:19.000Z

2022-01-14T20:15:19.000Z

_posts/2017-04-24-mono-linux-package-repository-changes-beginning-with-5-0.md

anuragsharma33/website

f7eaf5450b42fc4ac27da49bc6ac32f56544c0c8

[ "MIT" ]

1,100

2015-01-01T15:55:14.000Z

2022-03-30T17:00:45.000Z

--- layout: blog title: "Mono Linux package repository changes, beginning with Mono 5.0" author: Jo Shields tags: [linux,plans] --- Up to now, Linux packages on mono-project.com have come in two flavours – RPM built for CentOS 7 (and RHEL 7), and .deb built for Debian 7. Universal packages that work on the named distributions, and anything newer. Except that's not entirely true. Firstly, there have been "compatibility repositories" users need to add, to deal with ABI changes in libtiff, libjpeg, and Apache, since Debian 7. Then there's the packages for ARM64 and PPC64el – neither of those architectures is available in Debian 7, so they're published in the Debian 7 repo but actually built on Debian 8. A large reason for this is difficulty in our package publishing pipeline – apt only allows one version-architecture mix in the repository at once, so I can't have, say, 4.8.0.520-0xamarin1 built on AMD64 on both Debian 7 and Ubuntu 16.04. We've been working hard on a new package build/publish pipeline, which can properly support multiple distributions, based on Jenkins Pipeline. This new packaging system also resolves longstanding issues such as "can't really build anything except Mono" and "`Architecture: All` packages still get built on Jo's laptop, with no public build logs" ![Mono repo pipeline](/images/mono-repo-changes-pipeline-screenshot.png) So, here's the old build matrix: | Distribution | Architectures | |--------------|---------------| | Debian 7 | ARM hard float, ARM soft float, ARM64 (actually Debian 8), AMD64, i386, PPC64el (actually Debian 8) | | CentOS 7 | AMD64 | And here's the new one: | Distribution | Architectures | |--------------|---------------| | Debian 7 | ARM hard float (v7), ARM soft float, AMD64, i386 | | Debian 8 | ARM hard float (v7), ARM soft float, ARM64, AMD64, i386, PPC64el | | Raspbian 8 | ARM hard float (v6) | | Ubuntu 12.04 (*) | ARM hard float (v7), AMD64, i386 | | Ubuntu 14.04 | ARM hard float (v7), ARM64, AMD64, i386, PPC64el | | Ubuntu 16.04 | ARM hard float (v7), ARM64, AMD64, i386, PPC64el | | CentOS 6 | AMD64, i386 | | CentOS 7 | AMD64 | The compatibility repositories will no longer be needed on recent Ubuntu or Debian – just use the right repository for your system. If your distribution isn't listed... sorry, but we need to draw a line somewhere on support, and the distributions listed here are based on heavy analysis of our web server logs and bug requests. You'll want to change your package manager repositories to reflect your system more accurately, once Mono 5.0 is published (__*Update:*__ Mono 5.0 is now live, please check out the new instructions on the [download page](/download/stable/#download-lin)). We're debating some kind of automated handling of this, but I'm loathe to touch users' sources.list without their knowledge. CentOS builds are going to be late – I've been doing all my prototyping against the Debian builds, as I have better command of the tooling. Hopefully no worse than a week or two. (*) this is mainly for Travis CI support which still uses Ubuntu 12.04 for now (despite it being EOL)

65.645833

345

0.733101

eng_Latn

0.994212

b5a81c5537d84046c273b1e49dc522466a592436

1,815

md

Markdown

README.md

svnovikov/testrail-reporter

8e946679e4fc3f05cfc6fe1badce3d1b970d3195

[ "Apache-2.0" ]

1

2018-03-20T15:58:45.000Z

README.md

svnovikov/testrail-reporter

8e946679e4fc3f05cfc6fe1badce3d1b970d3195

[ "Apache-2.0" ]

null

README.md

svnovikov/testrail-reporter

8e946679e4fc3f05cfc6fe1badce3d1b970d3195

[ "Apache-2.0" ]

null

Purpose ------- Repository contains script to report results from XML file to TestRail. Only tests from XML will be added to run. Requirements ------------ - python 2.7 - [testrail-python](https://github.com/travispavek/testrail-python) Settings -------- **Your XML file structure** Only test group name and status of test case are significant to reporter for now: ```xml <xml> <testsuite errors='0' failures='0' skip='0' tests='7'> <testcase name='your_test_group_is_here'/> <testcase name='your_another_test_group_is_here'/> </testsuite> </xml> ``` By default `0` status is mapped to `passed` on TestRail, `1` is mapped to `failed` test. **Your TestRail settings** Required environment variables: ```bash export TESTRAIL_USER_EMAIL= export TESTRAIL_USER_KEY= export TESTRAIL_URL= export TESTRAIL_PROJECT= # name of the project where to find tests export TESTRAIL_MILESTONE= # is used for creating of plans and runs export TESTRAIL_SUITE= # name of the suite where to get tests for the run export TESTRAIL_PLAN= # name of the plan where to collect the run ``` Optional environment variables: ```bash export XML_PATH= # path to your XML file with test results; default is 'nosetests.xml' export TESTRAIL_RUN= # name of the run; by default is equal to test suite ``` Start ----- To run script which will add test results to TestRail, you may use: ```bash python reporter.py ``` Logic of work ------------- Script finds the suite in your TestRail project, then gets all cases from this suite and filters them to consider only those tests, which test groups are presented in your XML file. Then it finds test plan (or creates it if test plan whith specified name doesn't exist) and finds or creates test run within the plan. Finally, it adds test results for the run.

28.809524

359

0.732231

eng_Latn

0.989201

b5a87f0eedf58facbac0e27785d6ba8bd5118798

140

md

Markdown

CHANGELOG.md

alsuren/rebazel

57c6d6caa3f4d5d3378ec9bda9a63ae1fae1a5d4

[ "MIT" ]

19

2017-06-19T14:53:47.000Z

2022-02-19T08:45:09.000Z

CHANGELOG.md

alsuren/rebazel

57c6d6caa3f4d5d3378ec9bda9a63ae1fae1a5d4

[ "MIT" ]

4

2017-07-31T14:05:31.000Z

2021-07-09T13:54:05.000Z

CHANGELOG.md

alsuren/rebazel

57c6d6caa3f4d5d3378ec9bda9a63ae1fae1a5d4

[ "MIT" ]

3

2017-07-31T06:18:31.000Z

2021-07-08T14:46:23.000Z

# 0.1.{1,4} (02.-01-2019) * update deps * ensure std{out,err} of child process is being inherited # 0.1.0 (06-19-2017) * initial release

15.555556

57

0.657143

eng_Latn

0.963404

b5a8d49b13ac586d43d28d833444c3bcfabfd678

368

md

Markdown

content/zh/blog/ubuntu/ubuntu_disk.md

xueqing/myblog

b37876cc1f7bcaaa987a57626b7dae0e944c868f

[ "MIT" ]

null

content/zh/blog/ubuntu/ubuntu_disk.md

xueqing/myblog

b37876cc1f7bcaaa987a57626b7dae0e944c868f

[ "MIT" ]

null

content/zh/blog/ubuntu/ubuntu_disk.md

xueqing/myblog

b37876cc1f7bcaaa987a57626b7dae0e944c868f

[ "MIT" ]

2

2020-06-24T06:23:41.000Z

2020-10-08T10:26:37.000Z

--- title: "ubuntu 查看磁盘空间" authors: [kiki] tags: [ubuntu, linux] categories: [blog] draft: false --- - `df -hl`显示目前所有文件系统的可用空间及使用情形 - `-h`表示使用`human readable`的输出，即使用 GB，MB 等易读的格式 - `Filesystem`表示文件系统 - `Mounted on`表示挂载点 - `Size``Used``Avail``Use`分别表示分割区的容量、已使用的大小、剩下的大小及使用的百分比 - `du -sh *`显示当前目录下各个文件及目录占用空间大小 - `du`查询文件或文件夹的磁盘使用空间，可以添加`--max-depth=`限制目录深度

23

58

0.701087

yue_Hant

0.601145

b5ab18d24b4cedcc2fd98aed7c6e1b65d4d540ce

875

md

Markdown

content/archive/internal/jkylearmstrong-fundamentals-of-data-wrangling.md

alexholcombe/bookdown.org

127a2854817b46451bbfd7fa873942ce626ecdc6

[ "MIT" ]

58

2018-07-17T01:46:40.000Z

2021-12-25T00:58:36.000Z

content/archive/internal/jkylearmstrong-fundamentals-of-data-wrangling.md

alexholcombe/bookdown.org

127a2854817b46451bbfd7fa873942ce626ecdc6

[ "MIT" ]

68

2018-07-19T06:30:30.000Z

2022-03-02T07:08:14.000Z

content/archive/internal/jkylearmstrong-fundamentals-of-data-wrangling.md

alexholcombe/bookdown.org

127a2854817b46451bbfd7fa873942ce626ecdc6

[ "MIT" ]

100

2018-07-21T07:52:07.000Z

2022-03-01T11:17:08.000Z

--- title: "Fundamentals of Wrangling Healthcare Data with R" author: "J. Kyle Armstrong" date: "2021-06-14T16:30:30Z" link: "https://bookdown.org/jkylearmstrong/Fundamentals-of-Data-Wrangling/" length_weight: "100%" repo: "jkylearmstrong/Jeff_Data_Wrangling" pinned: false --- Fundamentals to Data Wrangling and programming with R v 4.1; examples with Health Related Data [...] Data Wrangling is the process of gathering, selecting, transforming and mapping “raw data” into another format with the intent of making it more appropriate and valuable for a variety of downstream analytic purposes. The Primary goal in data wrangling is to assure quality and useful data. Also known as “data cleaning,” “data processing,” or “data munging”; many professionals will tell you that data management related tasks will consume upwards of 80% of their time, leaving only 20% for ...

72.916667

595

0.782857

eng_Latn

0.991215

b5ab4f3fdbe947bacd05fa44e852e2ba43a38330

791

md

Markdown

_posts/2021-02-10-cybrary-podcast-52.md

jmymy/jmymy.github.io

0f54d314460fecf72eb71686fc07107dedbd66aa

[ "MIT" ]

null

_posts/2021-02-10-cybrary-podcast-52.md

jmymy/jmymy.github.io

0f54d314460fecf72eb71686fc07107dedbd66aa

[ "MIT" ]

null

_posts/2021-02-10-cybrary-podcast-52.md

jmymy/jmymy.github.io

0f54d314460fecf72eb71686fc07107dedbd66aa

[ "MIT" ]

null

--- layout: post title: Funding | The VC’s Perspective & The Entrepreneur’s Dilemma| The Cybrary Podcast Ep. 52 date: 2021-02-10 03:49 image: /images/cybrarypodcast.jpeg tag: Podcast categories: [podcast, youtube] link: https://open.spotify.com/episode/4JwIODhYQkNP5egvMKIAFF --- Have you wondered what’s involved in venture capital fund raising? In this episode of the Cybrary Podcast, we welcome Les Craig, Co-founder of RedOwl Analytics and current Partner at Next Frontier Capital. From their years of experience in Cybersecurity, Les, Mike, and Jonathan talk about the successes and pitfalls of starting businesses, what founders should understand about venture capital firms when seeking funding, and the importance of building connections and forming trusted relationships.

71.909091

501

0.79646

eng_Latn

0.991213

b5ab6269445545ec0f1628138f88b6818d4ea4af

78,966

md

Markdown

security-updates/SecurityBulletins/2006/ms06-036.md

MicrosoftDocs/security-updates.pt-br

41600ce6b74586b6e44b480e21ffcd62b9524fcb

[ "CC-BY-4.0", "MIT" ]

1

2020-05-19T20:16:43.000Z

security-updates/SecurityBulletins/2006/ms06-036.md

MicrosoftDocs/security-updates.pt-br

41600ce6b74586b6e44b480e21ffcd62b9524fcb

[ "CC-BY-4.0", "MIT" ]

216

2017-12-12T22:09:38.000Z

2018-12-10T00:42:52.000Z

security-updates/SecurityBulletins/2006/ms06-036.md

MicrosoftDocs/security-updates.pt-br

41600ce6b74586b6e44b480e21ffcd62b9524fcb

[ "CC-BY-4.0", "MIT" ]

2

2018-01-15T07:03:29.000Z

2021-11-18T13:14:23.000Z

--- TOCTitle: 'MS06-036' Title: 'Microsoft MS06-036 - Crítica' ms:assetid: 'ms06-036' ms:contentKeyID: 61233540 ms:mtpsurl: 'https://technet.microsoft.com/pt-BR/library/ms06-036(v=Security.10)' --- Microsoft MS06-036 - Crítica ============================================== Vulnerabilidade no serviço do Cliente DHCP pode permitir a execução remota de códigos (914388) ---------------------------------------------------------------------------------------------- Publicado: terça-feira, 11 de julho de 2006 **Versão:** 1.0 #### Resumo **Quem deve ler este documento:** Clientes que usam o Microsoft Windows **Impacto da vulnerabilidade:** Execução Remota de Código **Classificação máxima de gravidade:** Crítica **Recomendação:** Os clientes devem aplicar a atualização imediatamente. **Substituição da atualização de segurança:** Nenhuma **Advertências:** O [artigo 914388 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/xyz) documenta os problemas atualmente conhecidos que os clientes podem enfrentar ao instalar esta atualização de segurança. O artigo também documenta as soluções recomendadas para esses problemas. Para obter mais informações, consulte o [artigo 914388 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/xyz). **Locais de softwares testados e de download de atualização de segurança:** **Softwares afetados:** - Microsoft Windows 2000 Service Pack 4 - [Fazer o download da atualização](http://www.microsoft.com/downloads/details.aspx?familyid=) - Microsoft Windows XP Service Pack 1 e Microsoft Windows XP Service Pack 2 – [Fazer o download da atualização](http://www.microsoft.com/downloads/details.aspx?familyid=) - Microsoft Windows XP Professional x64 Edition – [Fazer o download da atualização](http://www.microsoft.com/downloads/details.aspx?familyid=) - Microsoft Windows Server 2003 e Microsoft Windows Server 2003 Service Pack 1 – [Fazer o download da atualização](http://www.microsoft.com/downloads/details.aspx?familyid=) - Microsoft Windows Server 2003 para sistemas baseados no Itanium e Microsoft Windows Server 2003 com SP1 para sistemas baseados no Itanium – [Fazer o download da atualização](http://www.microsoft.com/downloads/details.aspx?familyid=) - Microsoft Windows Server 2003 x64 Edition - [Fazer o download da atualização](http://www.microsoft.com/downloads/details.aspx?familyid=) **Softwares não afetados:** - Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE) e Microsoft Windows Millennium Edition (Me) - Os softwares dessa lista foram testados para se determinar se as versões são afetadas. Outras versões já não incluem suporte para a atualização de segurança ou podem não ser afetadas. Para determinar o ciclo de vida do suporte para seu produto e sua versão, visite o [site Ciclo de Vida do Suporte Microsoft](http://go.microsoft.com/fwlink/?linkid=21742). **Observação** As atualizações de segurança do Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1 e Windows Server 2003 x64 Edition também se aplicam ao Windows Server 2003 R2. ### Informações Gerais Sinopse ------- <span></span> **Sinopse:** Esta atualização elimina uma vulnerabilidade descoberta recentemente e reportada em particular, assim como problemas adicionais descobertos por investigações internas. A vulnerabilidade reportada em particular está documentada na seção “Detalhes da vulnerabilidade” deste boletim. Recomendamos que os clientes apliquem a atualização imediatamente. **Classificação de Gravidade e Identificadores de Vulnerabilidade:** | Identificadores de Vulnerabilidade | Impacto da Vulnerabilidade | Windows 2000 (site em inglês) | Windows XP Service Pack 1 | Windows XP Service Pack 2 | Windows Server 2003 | Windows Server 2003 Service Pack 1 | |------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-------------------------------|---------------------------|---------------------------|---------------------|------------------------------------| | Vulnerabilidade de saturação de buffer no serviço do Cliente DHCP - [CVE-2006-2372](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2006-2372) | Execução Remota de Código | Crítica | Crítica | Crítica | Crítica | Crítica | | **Gravidade agregada de todas as vulnerabilidades** | | **Crítica** | **Crítica** | **Crítica** | **Crítica** | **Crítica** | Essa [avaliação](http://www.microsoft.com/brasil/security/boletins/rating.mspx) baseia-se nos tipos de sistemas afetados pela vulnerabilidade, seus padrões comuns de implantação e o efeito da exploração da vulnerabilidade sobre eles. **Observação** As atualizações de segurança do Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1 e Windows Server 2003 x64 Edition também se aplicam ao Windows Server 2003 R2. **Observação** As classificações de gravidade das versões de sistema operacional não x86 mapeiam para as versões de sistemas operacionais x86 da seguinte forma: - A classificação de gravidade do Microsoft Windows XP Professional x64 Edition é a mesma do Windows XP Service Pack 2. - A classificação de gravidade do Microsoft Windows Server 2003 para sistemas baseados no Itanium é a mesma do Windows Server 2003. - A classificação de gravidade do Microsoft Windows Server 2003 com SP1 para sistemas baseados no Itanium é a mesma do Windows Server 2003 Service Pack 1. - A classificação de gravidade do Microsoft Windows Server 2003 x64 Edition é a mesma do Windows Server 2003 Service Pack 1. Perguntas mais freqüentes relacionadas a esta atualização de segurança ---------------------------------------------------------------------- <span></span> **O Windows 98, o Windows 98 Second Edition ou o Windows Millennium Edition são afetados drasticamente por uma ou mais vulnerabilidades apresentadas neste boletim de segurança?** Não. Os sistemas Windows 98, Windows 98 Second Edition e Windows Millennium Edition não possuem o componente afetado. **O suporte estendido para a atualização de segurança do Microsoft Windows NT Workstation 4.0 Service Pack 6a e do Windows 2000 Service Pack 2 foi encerrado em 30 de junho de 2004. O suporte estendido para a atualização de segurança do Microsoft Windows NT Server 4.0 Service Pack 6a foi encerrado em 31 de dezembro de 2004. O suporte estendido para a atualização de segurança do Microsoft Windows 2000 Service Pack 3 foi encerrado em 30 de junho de 2005. Ainda estou usando um desses sistemas operacionais. O que devo fazer?** O ciclo de vida do Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2 e Windows 2000 Service Pack 3 chegou ao fim. Os clientes que possuem essas versões de sistema operacional devem priorizar a migração para as versões com suporte, a fim de evitar uma possível exposição a vulnerabilidades. Para obter mais informações sobre o ciclo de vida do produto Windows, visite o [site do Microsoft Support Lifecycle](http://go.microsoft.com/fwlink/?linkid=21742). Para obter mais informações sobre o período de suporte estendido da atualização de segurança dessas versões de sistema operacional, visite o [site Microsoft Product Support Services](http://go.microsoft.com/fwlink/?linkid=33328). Os clientes que precisarem de suporte adicional para o estes produtos deverão entrar em contato com o representante da equipe da conta da Microsoft, o gerente técnico da conta ou o representante do parceiro Microsoft apropriado para obter opções de suporte personalizadas. Os clientes sem um contrato Alliance, Premier ou Authorized podem entrar em contato com o escritório de vendas local da Microsoft. Para obter informações de contato, visite o site de [Informações internacionais da Microsoft](http://go.microsoft.com/fwlink/?linkid=33329), selecione o país e clique em **Go** para ver uma lista de telefones. Ao ligar, peça para falar com o gerente de vendas local de Suporte Premier. Para obter mais informações, consulte a seção [Perguntas mais freqüentes sobre o ciclo de vida do suporte ao produto sistema operacional Windows](http://go.microsoft.com/fwlink/?linkid=33330). **Posso usar o MBSA (Microsoft Baseline Security Analyzer) para determinar se esta atualização é necessária?** A tabela a seguir fornece o resumo de detecção do MBSA para esta atualização de segurança. | Software | MBSA 1.2.1 | MBSA 2.0 | |------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------| | Microsoft Windows 2000 Service Pack 4 | Sim | Sim | | Microsoft Windows XP Service Pack 1 e Microsoft Windows XP Service Pack 2 | Sim | Sim | | Microsoft Windows XP Professional x64 Edition | Não | Sim | | Microsoft Windows Server 2003 e Microsoft Windows Server 2003 Service Pack 1 | Sim | Sim | | Microsoft Windows Server 2003 para sistemas baseados no Itanium e Microsoft Windows Server 2003 com Service Pack 1 para sistemas baseados no Itanium | Não | Sim | | Família do Microsoft Windows Server 2003 x64 Edition | Não | Sim | Para obter mais informações sobre o MBSA, visite o [site do MBSA](http://www.microsoft.com/brasil/technet/seguranca/mbsa/). Para obter mais informações sobre os softwares não detectados no momento pelo Microsoft Update e o MBSA 2.0, consulte o [artigo 895660 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/895660) **Posso usar o SMS (Systems Management Server) para determinar se esta atualização é necessária?** A tabela a seguir fornece o resumo de detecção de SMS para esta atualização de segurança. | Software | SMS 2.0 | SMS 2003 | |------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------| | Microsoft Windows 2000 Service Pack 4 | Sim | Sim | | Microsoft Windows XP Service Pack 1 e Microsoft Windows XP Service Pack 2 | Sim | Sim | | Microsoft Windows XP Professional x64 Edition | Não | Sim | | Microsoft Windows Server 2003 e Microsoft Windows Server 2003 Service Pack 1 | Sim | Sim | | Microsoft Windows Server 2003 para sistemas baseados no Itanium e Microsoft Windows Server 2003 com Service Pack 1 para sistemas baseados no Itanium | Não | Sim | | Família do Microsoft Windows Server 2003 x64 Edition | Não | Sim | O SMS usa o MBSA para detecção. Assim, o SMS tem a mesma limitação listada anteriormente neste boletim relacionada aos softwares que o MBSA não detecta. Para o SMS 2.0, o SMS SUS Feature Pack, que inclui a ferramenta Security Update Inventory Tool, pode ser usado pelo SMS para detectar atualizações de segurança. O SMS SUIT usa o mecanismo do MBSA 1.2.1 para detecção. Para obter mais informações sobre a ferramenta Inventário da Atualização de Segurança, visite o seguinte [site da Microsoft](http://support.microsoft.com/kb/894154/). Para obter mais informações sobre as limitações da ferramenta Security Update Inventory Tool, consulte o [artigo 306460 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/306460/). O SMS SUS Feature Pack também inclui a ferramenta Office Inventory da Microsoft para detectar atualizações necessárias para aplicativos do Microsoft Office. Para o SMS 2003, ferramenta de inventário do SMS 2003 para Microsoft Updates pode ser usada pelo SMS para detectar as atualizações de segurança oferecidas pelo [Microsoft Update](http://update.microsoft.com/microsoftupdate) e que tenham suporte do [Windows Server Update Services](http://www.microsoft.com/brasil/technet/seguranca/wsus/default.mspx). Para obter mais informações sobre a ferramenta de inventário do SMS 2003 para Microsoft Updates, consulte o seguinte [site da Microsoft](http://go.microsoft.com/fwlink/?linkid=50757). O SMS 2003 também pode usar a ferramenta Office Inventory da Microsoft para detectar as atualizações necessárias dos aplicativos do Microsoft Office. Para obter mais informações sobre o SMS, visite o [site do SMS](http://www.microsoft.com/brasil/sms). Detalhes da Vulnerabilidade --------------------------- <span></span> #### Vulnerabilidade de saturação de buffer no serviço do Cliente DHCP - CVE-2006-2372 Há uma vulnerabilidade de execução remota de código no serviço do Cliente DHCP que pode permitir a um invasor que tenha explorado com sucesso essa vulnerabilidade assumir total controle do sistema afetado. #### Fatores atenuantes da vulnerabilidade de saturação de buffer no serviço do Cliente DHCP - CVE-2006-2372: - Para que um ataque seja bem-sucedido, o invasor deve enviar, da mesma sub-rede, uma comunicação DHCP malformada ao host afetado. #### Soluções alternativas para a vulnerabilidade de saturação de buffer no serviço do Cliente DHCP - CVE-2006-2372: A Microsoft testou as seguintes soluções alternativas. Apesar de essas soluções alternativas não corrigirem a vulnerabilidade subjacente, elas ajudam a bloquear vetores de ataque conhecidos. Quando uma solução alternativa reduz a funcionalidade, ela é indicada na seção a seguir. - **Use um endereço IP estático** Para configurar o sistema para usar um endereço IP estático, siga estes passos: 1. Obtenha um endereço IP estático de seu administrador de rede 2. Clique em **Iniciar** e em **Painel de Controle**. Em seguida, clique em **Conexões de Rede e de Internet**. 3. Clique com o botão direito do mouse na conexão desejada para usar o endereço IP estático e, em seguida, clique em **Propriedades**. 4. Selecione **Protocolo da Internet (TCP/IP)** e clique em **Propriedades**. 5. Na guia **Geral**, clique nos botões de opção **Usar o seguinte endereço IP** e **Usar os seguintes endereços de servidor DNS**. 6. Digite seu endereço IP estático, máscara de sub-rede, gateway padrão e servidores DNS. 7. Clique em **OK** duas vezes. 8. Repita os passos de 3 a 7 para cada adaptador de rede. - **Desative o serviço do Cliente DHCP** Desativar o serviço do Cliente DHCP ajudará a proteger o sistema afetado das tentativas de explorar esta vulnerabilidade. Para desabilitar o serviço do Cliente DHCP, siga estes passos: 1. Clique em **Iniciar** e em **Painel de controle** .Como alternativa, aponte para **Configurações** e clique em **Painel de Controle**. 2. Clique duas vezes em **Ferramentas Administrativas**. 3. Clique duas vezes em **Serviços**. 4. Clique duas vezes em **Cliente DHCP**. 5. Na lista **Tipo de inicialização**, clique em **Desativado**. 6. Clique em **Parar** e em **OK**. Você também pode interromper e desativar o serviço DHCP usando o seguinte comando no prompt de comando: `sc stop DHCP & sc config DHCP start= disabled` **Impacto da solução alternativa:** Se você desativar o serviço DHCP, não poderá recuperar automaticamente um endereço IP com que se conectar à rede. #### Perguntas freqüentes sobre a vulnerabilidade de saturação de buffer no serviço do Cliente DHCP - CVE-2006-2372: **Qual é o escopo da vulnerabilidade?** Esta é uma vulnerabilidade de execução remota de código no serviço do Cliente DHCP. O invasor que explorar com êxito essa vulnerabilidade poderá assumir o controle total de um sistema afetado. O invasor poderá instalar programas; exibir, alterar ou excluir dados; ou criar novas contas com direitos totais de usuário. **O que provoca a vulnerabilidade?** Um buffer não verificado no serviço do Cliente DHCP. **O que é o DHCP?** O DHCP (Dynamic Host Configuration Protocol) é um padrão do Protocolo de Internet criado para reduzir a complexidade da administração dos endereços de rede. O DHCP faz isso usando um computador servidor para gerenciar centralmente endereços IP e outros detalhes de configuração relacionados usados na rede. O Windows Server fornece o serviço do Servidor DHCP, que permite que o computador servidor aja como um servidor DHCP e forneça definições de configuração para computadores cliente ativados por DHCP usando o serviço do Cliente DHCP na sua rede, conforme descrito no IETF [RFC 2131](http://www.faqs.org/rfcs/rfc2131.html) do DHCP. **Para que um invasor pode usar a vulnerabilidade?** Um invasor que explorar com êxito essa vulnerabilidade poderá assumir o controle total do sistema afetado. **Quem pode explorar a vulnerabilidade?** Um usuário anônimo pode explorar a vulnerabilidade enviando uma comunicação DHCP malformada a um cliente afetado no mesmo segmento de rede. Um ataque fica limitado a uma sub-rede local em um cenário típico de configuração padrão de rede onde o encaminhamento de DHCP ou BOOTP não está ativado. **De que forma o invasor pode explorar a vulnerabilidade?** Um invasor pode explorar a vulnerabilidade respondendo a uma solicitação DHCP do cliente na sub-rede local com pacotes malformados. **Quais são os principais sistemas que correm riscos com a vulnerabilidade?** O Microsoft Windows 2000, o Windows XP e o Windows Server 2003 são os que mais correm risco com essa vulnerabilidade. **O Windows 98, o Windows 98 Second Edition ou o Windows Millennium Edition são drasticamente afetados por essa vulnerabilidade?** Não. Os sistemas Windows 98, Windows 98 Second Edition e Windows Millennium Edition não possuem o componente afetado. **A vulnerabilidade pode ser explorada pela Internet?** Um invasor pode tentar explorar essa vulnerabilidade através da Internet. As práticas recomendadas de firewall e as configurações de firewall padrão podem ajudar na proteção contra ataques originados na Internet. A Microsoft forneceu informações sobre como você pode ajudar a proteger o seu PC. Os usuários finais podem visitar o site [Proteja seu PC](http://www.microsoft.com/brasil/proteja). Os profissionais de TI podem visitar o site [Centro de Orientacoes de Seguranca](http://www.microsoft.com/brasil/security/guidance) (em inglês). **O que a atualização faz?** A atualização remove a vulnerabilidade por validar o modo como o cliente DHCP lida com comunicações relacionadas a DHCP. **Quando esse boletim de segurança foi lançado, essa vulnerabilidade já tinha sido divulgada publicamente?** Não. A Microsoft recebeu informações sobre essa vulnerabilidade por meio de divulgação responsável. A Microsoft não recebeu nenhuma informação indicando que essa vulnerabilidade tenha sido divulgada publicamente quando este boletim de segurança foi lançado pela primeira vez. Este boletim de segurança trata a vulnerabilidade exposta em particular, assim como problemas adicionais descobertos por investigações internas **Quando este boletim de segurança foi lançado, a Microsoft tinha recebido algum relatório informando que essa vulnerabilidade estava sendo explorada?** Não. A Microsoft não recebeu nenhuma informação indicando que essa vulnerabilidade tenha sido usada publicamente para atacar clientes e não testemunhou nenhum exemplo de publicação de código de verificação de conceito, quando este boletim de segurança foi lançado pela primeira vez. Informações de atualização de segurança --------------------------------------- <span></span> **Softwares afetados:** Para obter informações sobre uma atualização de segurança específica para seu software afetado, clique no link apropriado: #### Windows Server 2003 (todas as versões) **Pré-requisitos** Esta atualização de segurança requer o Windows Server 2003 ou Windows Server 2003 Service Pack 1. **Observação** As atualizações de segurança para Microsoft Windows Server 2003 e Microsoft Windows Server 2003 Service Pack 1 também se aplicam ao Microsoft Windows Server 2003 R2. **Inclusão em Service Packs futuros:** A atualização desse problema será incluída em um service pack ou conjunto de atualizações futuro. **Informações sobre instalação** Esta atualização de segurança oferece suporte às seguintes opções de instalação: <p></p> <table class="dataTable"> <caption> Opções de instalação da atualização de segurança para as quais há suporte </caption> <tr class="thead"> <th style="border:1px solid black;" > Opção </th> <th style="border:1px solid black;" > Descrição </th> </tr> <tr> <td style="border:1px solid black;"> **/help** </td> <td style="border:1px solid black;"> Exibe as opções de linha de comando. </td> </tr> <tr> <th colspan="2"> Modos de instalação </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/passive** </td> <td style="border:1px solid black;"> Modo de instalação autônomo. Não é necessária a interação do usuário, mas o status da instalação é exibido. Se a reinicialização for necessária no fim da instalação, uma caixa de diálogo será apresentada para o usuário com um timer avisando que o computador será reiniciado em 30 segundos. </td> </tr> <tr> <td style="border:1px solid black;"> **/quiet** </td> <td style="border:1px solid black;"> Modo silencioso. O mesmo que modo autônomo, mas nenhuma mensagem de status ou de erro é exibida. </td> </tr> <tr> <th colspan="2"> Opções de reinicialização </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/norestart** </td> <td style="border:1px solid black;"> Não reinicia quando a instalação é concluída. </td> </tr> <tr> <td style="border:1px solid black;"> **/forcerestart** </td> <td style="border:1px solid black;"> Reinicia o computador após a instalação e força o fechamento de outros aplicativos no desligamento sem antes salvar os arquivos abertos. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/warnrestart\[:x\]** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo com um timer avisando ao usuário que o computador será reiniciado em *x* segundos. (A configuração padrão é 30 segundos.) Destina-se ao uso com as opções **/quiet** ou **/passive**. </td> </tr> <tr> <td style="border:1px solid black;"> **/promptrestart** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo solicitando que o usuário local permita a reinicialização. </td> </tr> <tr> <th colspan="2"> Opções especiais </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/overwriteoem** </td> <td style="border:1px solid black;"> Sobrescreve arquivos OEM sem notificação. </td> </tr> <tr> <td style="border:1px solid black;"> **/nobackup** </td> <td style="border:1px solid black;"> Não faz backup de arquivos necessários à desinstalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/forceappsclose** </td> <td style="border:1px solid black;"> Força o encerramento de outros programas quando o computador é desligado. </td> </tr> <tr> <td style="border:1px solid black;"> **/log: path** </td> <td style="border:1px solid black;"> Permite o redirecionamento dos arquivos de log da instalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/integrate:caminho** </td> <td style="border:1px solid black;"> Integra a atualização nos arquivos-fonte do Windows. Esses arquivos se encontram no caminho especificado na opção. </td> </tr> <tr> <td style="border:1px solid black;"> **/extract\[:caminho\]** </td> <td style="border:1px solid black;"> Extrai os arquivos sem iniciar o programa de instalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/ER** </td> <td style="border:1px solid black;"> Habilita o relatório de erros estendido. </td> </tr> <tr> <td style="border:1px solid black;"> **/verbose** </td> <td style="border:1px solid black;"> Habilita o registro extenso. Durante a instalação, cria %Windir%\\CabBuild.log. Esse log detalha os arquivos copiados. Se você usar esta opção, a instalação será bem mais lenta. </td> </tr> </table> **Observação** É possível combinar essas opções em uma única linha de comando. Para obter compatibilidade com versões anteriores, a atualização de segurança também oferece suporte a várias opções de instalação utilizadas por versões anteriores do programa de instalação. Para obter mais informações sobre opções com suporte de segurança, consulte o [artigo 262841 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/262841). Para obter mais informações sobre o instalador Update.exe, visite [o site Microsoft TechNet](http://www.microsoft.com/brasil/technet). **Informações de implantação** Para instalar a atualização de segurança sem nenhuma intervenção do usuário, utilize o seguinte comando em um prompt de comando para o Windows Server 2003: **Windowsserver2003- kb914388-x86-enu /quiet** **Observação** O uso da opção **/quiet** eliminará todas as mensagens. Isso inclui a eliminação de mensagens de falha. Os administradores devem usar um dos métodos com suporte para verificar se a instalação foi bem-sucedida quando utilizarem a opção **/quiet**. Os administradores também devem analisar o arquivo KB914388.log para obter informações sobre quaisquer mensagens de falha quando usarem essa opção. Para instalar a atualização de segurança sem forçar a reinicialização do sistema, use o seguinte comando em um prompt de comando para o Windows Server 2003: **Windowsserver2003-kb914388-x86-enu /norestart** Para obter informações sobre como implantar esta atualização de segurança com os serviços de atualização de software, visite o [site Software Update Services](http://www.microsoft.com/brasil/technet/seguranca/sus/). Para obter mais informações sobre como implantar esta atualização de segurança usando o recurso Windows Server Update Services, visite o [site do Windows Server Update Services](http://www.microsoft.com/brasil/technet/seguranca/wsus/default.mspx). Esta atualização de segurança também está disponível no [site Microsoft Update](http://update.microsoft.com/microsoftupdate). **Requisitos de reinicialização** É necessário reiniciar o sistema depois de aplicar esta atualização de segurança. Para obter mais informações sobre os motivos pelos quais você será solicitado a reiniciar, consulte o [artigo 887012 (em inglês) da Base de Conhecimento Microsoft.](http://support.microsoft.com/kb/887012) Esta atualização de segurança não oferece suporte a HotPatching. Para obter mais informações sobre HotPatching, consulte o [artigo 897341 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/897341). **Informações sobre remoção** Para remover esta atualização, use a ferramenta Adicionar ou Remover Programas no Painel de Controle. Os administradores de sistema também podem usar o utilitário Spuninst.exe para remover esta atualização de segurança. O utilitário Spuninst.exe está localizado na pasta %Windir%\\$NTUninstallKB914388$\\Spuninst. <p></p> <table class="dataTable"> <caption> Opções do Spuninst.exe para as quais existe suporte </caption> <tr class="thead"> <th style="border:1px solid black;" > Opção </th> <th style="border:1px solid black;" > Descrição </th> </tr> <tr> <td style="border:1px solid black;"> **/help** </td> <td style="border:1px solid black;"> Exibe as opções de linha de comando. </td> </tr> <tr> <th colspan="2"> Modos de instalação </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/passive** </td> <td style="border:1px solid black;"> Modo de instalação autônomo. Não é necessária a interação do usuário, mas o status da instalação é exibido. Se a reinicialização for necessária no fim da instalação, uma caixa de diálogo será apresentada para o usuário com um timer avisando que o computador será reiniciado em 30 segundos. </td> </tr> <tr> <td style="border:1px solid black;"> **/quiet** </td> <td style="border:1px solid black;"> Modo silencioso. O mesmo que modo autônomo, mas nenhuma mensagem de status ou de erro é exibida. </td> </tr> <tr> <th colspan="2"> Opções de reinicialização </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/norestart** </td> <td style="border:1px solid black;"> Não reinicia quando a instalação é concluída. </td> </tr> <tr> <td style="border:1px solid black;"> **/forcerestart** </td> <td style="border:1px solid black;"> Reinicia o computador após a instalação e força o fechamento de outros aplicativos no desligamento sem antes salvar os arquivos abertos. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/warnrestart\[:x\]** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo com um timer avisando ao usuário que o computador será reiniciado em *x* segundos. (A configuração padrão é 30 segundos.) Destina-se ao uso com as opções **/quiet** ou **/passive**. </td> </tr> <tr> <td style="border:1px solid black;"> **/promptrestart** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo solicitando que o usuário local permita a reinicialização. </td> </tr> <tr> <th colspan="2"> Opções especiais </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/forceappsclose** </td> <td style="border:1px solid black;"> Força o encerramento de outros programas quando o computador é desligado. </td> </tr> <tr> <td style="border:1px solid black;"> **/log:caminho** </td> <td style="border:1px solid black;"> Permite o redirecionamento dos arquivos de log da instalação. </td> </tr> </table> **Informações sobre o arquivo** A versão em inglês desta atualização de segurança tem os atributos de arquivo relacionados na tabela abaixo. As datas e as horas destes arquivos estão de acordo com a hora universal coordenada (UTC). Quando você exibe as informações do arquivo, ele é convertido para a hora local. Para saber a diferença entre o UTC e o horário local, use a guia **Fuso Horário** na ferramenta Data e Hora, no Painel de Controle. Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition com SP1; Windows Server 2003, Standard Edition com SP1; Windows Server 2003, Enterprise Edition com SP1; Windows Server 2003, Datacenter Edition com SP1; Windows Server 2003 R2, Web Edition; Windows Server 2003 R2, Standard Edition; Windows Server 2003 R2, Datacenter Edition; Windows Server 2003 R2, Enterprise Edition; Windows Small Business Server 2003 R2: | Nome do arquivo | Versão | Data | Hora | Tamanho | Pasta | |-----------------|---------------|--------------------|-------|---------|--------| | Dhcpcsvc.dll | 5.2.3790.536 | 19 de maio de 2006 | 02:56 | 104.448 | RTMGDR | | Iphlpapi.dll | 5.2.3790.536 | 19 de maio de 2006 | 02:56 | 84.992 | RTMGDR | | Dhcpcsvc.dll | 5.2.3790.536 | 19 de maio de 2006 | 02:53 | 104.448 | RTMQFE | | Iphlpapi.dll | 5.2.3790.536 | 19 de maio de 2006 | 02:53 | 85.504 | RTMQFE | | Dhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 03:18 | 117.248 | SP1GDR | | Iphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 03:18 | 95.232 | SP1GDR | | Dhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 03:38 | 117.248 | SP1QFE | | Iphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 03:38 | 95.232 | SP1QFE | Windows Server, 2003 Enterprise Edition para sistemas baseados no Itanium; Windows Server 2003, Datacenter Edition para sistemas baseados no Itanium; Windows Server 2003, Enterprise Edition com SP1 para sistemas baseados no Itanium e Windows Server 2003, Datacenter Edition com SP1 para sistemas baseados no Itanium: | Nome do arquivo | Versão | Data | Hora | Tamanho | CPU | Pasta | |-----------------|---------------|--------------------|-------|---------|-------|-------------| | Dhcpcsvc.dll | 5.2.3790.536 | 19 de maio de 2006 | 04:18 | 287.232 | IA-64 | RTMGDR | | Iphlpapi.dll | 5.2.3790.536 | 19 de maio de 2006 | 04:18 | 229.888 | IA-64 | RTMGDR | | Wdhcpcsvc.dll | 5.2.3790.536 | 19 de maio de 2006 | 04:18 | 104.448 | x86 | RTMGDR\\WOW | | Wiphlpapi.dll | 5.2.3790.536 | 19 de maio de 2006 | 04:18 | 84.992 | x86 | RTMGDR\\WOW | | Dhcpcsvc.dll | 5.2.3790.536 | 19 de maio de 2006 | 04:18 | 287.232 | IA-64 | RTMQFE | | Iphlpapi.dll | 5.2.3790.536 | 19 de maio de 2006 | 04:18 | 230.400 | IA-64 | RTMQFE | | Wdhcpcsvc.dll | 5.2.3790.536 | 19 de maio de 2006 | 04:18 | 104.448 | x86 | RTMQFE\\WOW | | Wiphlpapi.dll | 5.2.3790.536 | 19 de maio de 2006 | 04:18 | 85.504 | x86 | RTMQFE\\WOW | | Dhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:22 | 308.736 | IA-64 | SP1GDR | | Iphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:22 | 261.632 | IA-64 | SP1GDR | | Wdhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:22 | 117.248 | x86 | SP1GDR\\WOW | | Wiphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:22 | 95.232 | x86 | SP1GDR\\WOW | | Dhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:18 | 308.736 | IA-64 | SP1QFE | | Iphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:18 | 261.632 | IA-64 | SP1QFE | | Wdhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:18 | 117.248 | x86 | SP1QFE\\WOW | | Wiphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:18 | 95.232 | x86 | SP1QFE\\WOW | Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; e Windows Server 2003, Datacenter x64 Edition; Windows Server 2003 R2, Standard x64 Edition; Windows Server 2003 R2, Enterprise x64 Edition; e Windows Server 2003 R2, Datacenter x64 Edition: | Nome do arquivo | Versão | Data | Hora | Tamanho | CPU | Pasta | |-----------------|---------------|--------------------|-------|---------|-----|-------------| | Dhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:23 | 225.792 | x64 | SP1GDR | | Iphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:23 | 182.784 | x64 | SP1GDR | | Wdhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:23 | 117.248 | x86 | SP1GDR\\WOW | | Wiphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:23 | 95.232 | x86 | SP1GDR\\WOW | | Dhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:17 | 225.792 | x64 | SP1QFE | | Iphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:17 | 182.784 | x64 | SP1QFE | | Wdhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:17 | 117.248 | x86 | SP1QFE\\WOW | | Wiphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:17 | 95.232 | x86 | SP1QFE\\WOW | **Observações**: Quando você instalar essas atualizações de segurança, o instalador verificará se um ou mais arquivos que estão sendo atualizados no sistema já foram atualizados por um hotfix da Microsoft. Se você já tiver instalado um hotfix para atualizar um desses arquivos, o instalador copiará os arquivos RTMQFE, SP1QFE ou SP2QFE para o sistema. Do contrário, o instalador copiará os arquivos RTMGDR, SP1GDR ou SP2GDR para o sistema. As atualizações de segurança podem não conter todas as variações desses arquivos. Para obter mais informações sobre esse comportamento, consulte o [artigo 824994 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/824994). Para obter mais informações sobre esse comportamento, consulte o [artigo 824994 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/824994). Para obter mais informações sobre o instalador Update.exe, visite o [site Microsoft TechNet](http://www.microsoft.com/brasil/technet). Para obter mais informações sobre a terminologia que aparece neste boletim, como *hotfix*, consulte o [artigo 824684 (em inglês) do Microsoft](http://support.microsoft.com/kb/824684) Knowledge Base. **Verificando a aplicação da atualização** - **Microsoft Baseline Security Analyzer** Para verificar se uma atualização de segurança foi aplicada em um sistema afetado, você pode utilizar a ferramenta MBSA (Microsoft Baseline Security Analyzer). Essa ferramenta permite que os administradores examinem os sistemas locais e remotos para saber se faltam atualizações de segurança ou se existem problemas de configuração comuns. Para obter mais informações sobre o MBSA, visite o site [Microsoft Baseline Security Analyzer](http://www.microsoft.com/brasil/technet/seguranca/mbsa/) (em inglês). - **Verificação de versão de arquivo** **Observação** Como existem várias versões do Microsoft Windows, as etapas a seguir podem ser diferentes no seu computador. Se isso acontecer, consulte a documentação do produto para completar estas etapas. 1. Clique em **Iniciar** e, em seguida, clique em **Pesquisar**. 2. No painel **Resultados da Pesquisa**, clique em **Todos os arquivos e pastas**, em **Search Companion**. 3. Na caixa **Todo ou parte do nome do arquivo**, digite um nome de arquivo da tabela de informações de arquivo correta e clique em **Pesquisar**. 4. Na lista de arquivos, clique com o botão direito do mouse em um nome de arquivo da tabela de informações de arquivo correta e clique em **Propriedades**. **Observação** Dependendo da versão do sistema operacional ou dos programas instalados, alguns dos arquivos listados na tabela de informações de arquivos podem não estar instalados. 5. Na guia **Versão**, determine a versão do arquivo instalado no computador comparando-o com a versão documentada na tabela de informações de arquivos correta. **Observação** Atributos com versão diferente da versão do arquivo podem ser alterados durante a instalação. A comparação de outros atributos de arquivo com as informações na tabela não é um método suportado para verificar se a atualização foi aplicada. Além disso, em alguns casos, arquivos podem ser renomeados durante a instalação. Se as informações sobre o arquivo ou a versão não estiverem presentes, use um dos outros métodos disponíveis para verificar a instalação da atualização. - **Verificação da chave do Registro** Também é possível verificar os arquivos que esta atualização de segurança instalou analisando as seguintes chaves do Registro: Windows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition com SP1; Windows Server 2003, Standard Edition com SP1; Windows Server 2003, Enterprise Edition com SP1; Windows Server 2003, Datacenter Edition com SP1; Windows Server 2003, Enterprise Edition para sistemas baseados no Itanium; Windows Server 2003, Datacenter Edition para sistemas baseados no Itanium; Windows Server 2003, Enterprise Edition com SP1 para sistemas baseados no Itanium; Windows Server 2003, Datacenter Edition com SP1 para sistemas baseados no Itanium; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; e Windows Server 2003, Datacenter x64 Edition: HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Updates\\Windows Server 2003\\SP2\\KB914388\\Filelist **Observação** Essa chave do Registro pode não conter uma lista completa de arquivos instalados. Além disso, é possível que essa chave do Registro não seja criada corretamente caso o administrador ou um OEM integre ou adicione a atualização de segurança aos arquivos fonte da instalação do Windows. #### Windows XP (todas as versões) **Pré-requisitos** Esta atualização de segurança requer o Microsoft Windows XP Service Pack 1 ou uma versão posterior. [Para obter mais informações, consulte o artigo](http://support.microsoft.com/kb/322389)322389 (em inglês) da Base de Conhecimento Microsoft. **Inclusão em Service Packs futuros:** A atualização desse problema será incluída em um service pack ou conjunto de atualizações futuro. **Informações sobre instalação** Esta atualização de segurança oferece suporte às seguintes opções de instalação: <p></p> <table class="dataTable"> <caption> Opções de instalação da atualização de segurança para as quais há suporte </caption> <tr class="thead"> <th style="border:1px solid black;" > Opção </th> <th style="border:1px solid black;" > Descrição </th> </tr> <tr> <td style="border:1px solid black;"> **/help** </td> <td style="border:1px solid black;"> Exibe as opções de linha de comando. </td> </tr> <tr> <th colspan="2"> Modos de instalação </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/passive** </td> <td style="border:1px solid black;"> Modo de instalação autônomo. Não é necessária a interação do usuário, mas o status da instalação é exibido. Se a reinicialização for necessária no fim da instalação, uma caixa de diálogo será apresentada para o usuário com um timer avisando que o computador será reiniciado em 30 segundos. </td> </tr> <tr> <td style="border:1px solid black;"> **/quiet** </td> <td style="border:1px solid black;"> Modo silencioso. O mesmo que modo autônomo, mas nenhuma mensagem de status ou de erro é exibida. </td> </tr> <tr> <th colspan="2"> Opções de reinicialização </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/norestart** </td> <td style="border:1px solid black;"> Não reinicia quando a instalação é concluída. </td> </tr> <tr> <td style="border:1px solid black;"> **/forcerestart** </td> <td style="border:1px solid black;"> Reinicia o computador após a instalação e força o fechamento de outros aplicativos no desligamento sem antes salvar os arquivos abertos. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/warnrestart\[:x\]** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo com um timer avisando ao usuário que o computador será reiniciado em *x* segundos. (A configuração padrão é 30 segundos.) Destina-se ao uso com as opções **/quiet** ou **/passive**. </td> </tr> <tr> <td style="border:1px solid black;"> **/promptrestart** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo solicitando que o usuário local permita a reinicialização. </td> </tr> <tr> <th colspan="2"> Opções especiais </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/overwriteoem** </td> <td style="border:1px solid black;"> Sobrescreve arquivos OEM sem notificação. </td> </tr> <tr> <td style="border:1px solid black;"> **/nobackup** </td> <td style="border:1px solid black;"> Não faz backup de arquivos necessários à desinstalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/forceappsclose** </td> <td style="border:1px solid black;"> Força o encerramento de outros programas quando o computador é desligado. </td> </tr> <tr> <td style="border:1px solid black;"> **/log:caminho** </td> <td style="border:1px solid black;"> Permite o redirecionamento dos arquivos de log da instalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/integrate:caminho** </td> <td style="border:1px solid black;"> Integra a atualização nos arquivos-fonte do Windows. Esses arquivos se encontram no caminho especificado na opção. </td> </tr> <tr> <td style="border:1px solid black;"> **/extract\[:caminho\]** </td> <td style="border:1px solid black;"> Extrai os arquivos sem iniciar o programa de instalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/ER** </td> <td style="border:1px solid black;"> Habilita o relatório de erros estendido. </td> </tr> <tr> <td style="border:1px solid black;"> **/verbose** </td> <td style="border:1px solid black;"> Habilita o registro extenso. Durante a instalação, cria %Windir%\\CabBuild.log. Esse log detalha os arquivos copiados. Se você usar esta opção, a instalação será bem mais lenta. </td> </tr> </table> **Observação** É possível combinar essas opções em uma única linha de comando. Para obter compatibilidade com versões anteriores, a atualização de segurança também oferece suporte às opções de instalação utilizadas por versões anteriores do utilitário de instalação. Para obter mais informações sobre opções com suporte de segurança, consulte o [artigo 262841 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/262841). Para obter mais informações sobre o instalador Update.exe, visite [o site Microsoft TechNet](http://www.microsoft.com/brasil/technet). **Informações de implantação** Para instalar a atualização de segurança sem qualquer intervenção do usuário, use o seguinte comando em um prompt de comando do Microsoft Windows XP: **Windowsxp- kb914388-x86-enu /quiet** **Observação** O uso da opção **/quiet** eliminará todas as mensagens. Isso inclui a eliminação de mensagens de falha. Os administradores devem usar um dos métodos com suporte para verificar se a instalação foi bem-sucedida quando utilizarem a opção **/quiet**. Os administradores também devem analisar o arquivo KB914388.log para obter informações sobre quaisquer mensagens de falha quando usarem essa opção. Para instalar a atualização de segurança sem forçar a reinicialização do sistema, use o seguinte comando em um prompt de comando do Windows XP: **Windowsxp- kb914388-x86-enu /norestart** Para obter informações sobre como implantar esta atualização de segurança com os serviços de atualização de software, visite o [site Software Update Services](http://www.microsoft.com/brasil/technet/seguranca/sus/). Para obter mais informações sobre como implantar esta atualização de segurança usando o recurso Windows Server Update Services, visite o [site do Windows Server Update Services](http://www.microsoft.com/brasil/technet/seguranca/wsus/default.mspx). Esta atualização de segurança também está disponível no [site Microsoft Update](http://update.microsoft.com/microsoftupdate). **Requisitos de reinicialização** É necessário reiniciar o sistema depois de aplicar essa atualização de segurança. Para reduzir a possibilidade de uma reinicialização ser solicitada, interrompa todos os serviços afetados e feche todos os aplicativos que possam usar os arquivos afetados antes de instalar a atualização de segurança. Para obter mais informações sobre os motivos pelos quais você será solicitado a reiniciar, consulte o [artigo 887012 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/887012). **Informações sobre remoção** Para remover esta atualização de segurança, use a ferramenta Adicionar ou Remover Programas no Painel de Controle. Os administradores de sistema também podem usar o utilitário Spuninst.exe para remover esta atualização de segurança. O utilitário Spuninst.exe está localizado na pasta %Windir%\\$NTUninstallKB914388$\\Spuninst. <p></p> <table class="dataTable"> <caption> Opções do Spuninst.exe para as quais existe suporte </caption> <tr class="thead"> <th style="border:1px solid black;" > Opção </th> <th style="border:1px solid black;" > Descrição </th> </tr> <tr> <td style="border:1px solid black;"> **/help** </td> <td style="border:1px solid black;"> Exibe as opções de linha de comando. </td> </tr> <tr> <th colspan="2"> Modos de instalação </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/passive** </td> <td style="border:1px solid black;"> Modo de instalação autônomo. Não é necessária a interação do usuário, mas o status da instalação é exibido. Se a reinicialização for necessária no fim da instalação, uma caixa de diálogo será apresentada para o usuário com um timer avisando que o computador será reiniciado em 30 segundos. </td> </tr> <tr> <td style="border:1px solid black;"> **/quiet** </td> <td style="border:1px solid black;"> Modo silencioso. O mesmo que modo autônomo, mas nenhuma mensagem de status ou de erro é exibida. </td> </tr> <tr> <th colspan="2"> Opções de reinicialização </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/norestart** </td> <td style="border:1px solid black;"> Não reinicia quando a instalação é concluída. </td> </tr> <tr> <td style="border:1px solid black;"> **/forcerestart** </td> <td style="border:1px solid black;"> Reinicia o computador após a instalação e força o fechamento de outros aplicativos no desligamento sem antes salvar os arquivos abertos. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/warnrestart\[:x\]** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo com um timer avisando ao usuário que o computador será reiniciado em *x* segundos. (A configuração padrão é 30 segundos.) Destina-se ao uso com as opções **/quiet** ou **/passive**. </td> </tr> <tr> <td style="border:1px solid black;"> **/promptrestart** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo solicitando que o usuário local permita a reinicialização. </td> </tr> <tr> <th colspan="2"> Opções especiais </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/forceappsclose** </td> <td style="border:1px solid black;"> Força o encerramento de outros programas quando o computador é desligado. </td> </tr> <tr> <td style="border:1px solid black;"> **/log:caminho** </td> <td style="border:1px solid black;"> Permite o redirecionamento dos arquivos de log da instalação. </td> </tr> </table> **Informações sobre o arquivo** A versão em inglês desta atualização de segurança tem os atributos de arquivo relacionados na tabela abaixo. As datas e as horas destes arquivos estão de acordo com a hora universal coordenada (UTC). Quando você exibe as informações do arquivo, ele é convertido para a hora local. Para saber a diferença entre o UTC e o horário local, use a guia **Fuso Horário** na ferramenta Data e Hora, no Painel de Controle. Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005 e Windows XP Media Center Edition 2005: | Nome do arquivo | Versão | Data | Hora | Tamanho | Pasta | |-----------------|---------------|--------------------|-------|---------|--------| | 6to4svc.dll | 5.1.2600.1847 | 19 de maio de 2006 | 12:15 | 95.232 | SP1QFE | | Dhcpcsvc.dll | 5.1.2600.1847 | 19 de maio de 2006 | 12:15 | 103.936 | SP1QFE | | Dnsapi.dll | 5.1.2600.1847 | 19 de maio de 2006 | 12:15 | 140.288 | SP1QFE | | Inetmib1.dll | 5.1.2600.1847 | 19 de maio de 2006 | 12:15 | 31.232 | SP1QFE | | Iphlpapi.dll | 5.1.2600.1847 | 19 de maio de 2006 | 12:15 | 83.456 | SP1QFE | | Ipv6.exe | 5.1.2600.1847 | 19 de maio de 2006 | 08:46 | 48.640 | SP1QFE | | Ipv6mon.dll | 5.1.2600.1847 | 19 de maio de 2006 | 12:15 | 54.272 | SP1QFE | | Netsh.exe | 5.1.2600.1847 | 19 de maio de 2006 | 08:44 | 83.456 | SP1QFE | | Tcpip6.sys | 5.1.2600.1847 | 19 de maio de 2006 | 08:46 | 203.008 | SP1QFE | | Tunmp.sys | 5.1.2600.1847 | 19 de maio de 2006 | 08:44 | 11.776 | SP1QFE | | Ws2\_32.dll | 5.1.2600.1847 | 19 de maio de 2006 | 12:15 | 70.656 | SP1QFE | | Wship6.dll | 5.1.2600.1847 | 19 de maio de 2006 | 12:15 | 13.312 | SP1QFE | | Xpob2res.dll | 5.1.2600.1847 | 19 de maio de 2006 | 08:51 | 159.232 | SP1QFE | | Dhcpcsvc.dll | 5.1.2600.2912 | 19 de maio de 2006 | 12:59 | 111,616 | SP2GDR | | Dnsapi.dll | 5.1.2600.2912 | 19 de maio de 2006 | 12:59 | 148.480 | SP2GDR | | Iphlpapi.dll | 5.1.2600.2912 | 19 de maio de 2006 | 12:59 | 94.720 | SP2GDR | | Dhcpcsvc.dll | 5.1.2600.2912 | 19 de maio de 2006 | 13:46 | 112.128 | SP2QFE | | Dnsapi.dll | 5.1.2600.2912 | 19 de maio de 2006 | 13:46 | 147.456 | SP2QFE | | Iphlpapi.dll | 5.1.2600.2912 | 19 de maio de 2006 | 13:46 | 94.720 | SP2QFE | Windows XP Professional x64: | Nome do arquivo | Versão | Data | Hora | Tamanho | CPU | Pasta | |-----------------|---------------|--------------------|-------|---------|-----|-------------| | Dhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:23 | 225.792 | x64 | SP1GDR | | Iphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:23 | 182.784 | x64 | SP1GDR | | Wdhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:23 | 117.248 | x86 | SP1GDR\\WOW | | Wiphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:23 | 95.232 | x86 | SP1GDR\\WOW | | Dhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:17 | 225.792 | x64 | SP1QFE | | Iphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:17 | 182.784 | x64 | SP1QFE | | Wdhcpcsvc.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:17 | 117.248 | x86 | SP1QFE\\WOW | | Wiphlpapi.dll | 5.2.3790.2706 | 19 de maio de 2006 | 04:17 | 95.232 | x86 | SP1QFE\\WOW | **Observações**: Quando você instalar essas atualizações de segurança, o instalador verificará se um ou mais arquivos que estão sendo atualizados no sistema já foram atualizados por um hotfix da Microsoft. Se você já tiver instalado um hotfix para atualizar um desses arquivos, o instalador copiará os arquivos RTMQFE, SP1QFE ou SP2QFE para o sistema. Do contrário, o instalador copiará os arquivos RTMGDR, SP1GDR ou SP2GDR para o sistema. As atualizações de segurança podem não conter todas as variações desses arquivos. Para obter mais informações sobre esse comportamento, consulte o [artigo 824994 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/824994). Para obter mais informações sobre o instalador Update.exe, visite o [site Microsoft TechNet](http://www.microsoft.com/brasil/technet). Para obter mais informações sobre a terminologia que aparece neste boletim, como *hotfix*, consulte o [artigo 824684 (em inglês) do Microsoft](http://support.microsoft.com/kb/824684) Knowledge Base. **Verificando a aplicação da atualização** - **Microsoft Baseline Security Analyzer** Para verificar se uma atualização de segurança foi aplicada em um sistema afetado, você pode utilizar a ferramenta MBSA (Microsoft Baseline Security Analyzer). Essa ferramenta permite que os administradores examinem os sistemas locais e remotos para saber se faltam atualizações de segurança ou se existem problemas de configuração comuns. Para obter mais informações sobre o MBSA, visite o site [Microsoft Baseline Security Analyzer](http://www.microsoft.com/brasil/technet/seguranca/mbsa/) (em inglês). - **Verificação de versão de arquivo** **Observação** Como existem várias versões do Microsoft Windows, as etapas a seguir podem ser diferentes no seu computador. Se isso acontecer, consulte a documentação do produto para completar estas etapas. 1. Clique em **Iniciar** e, em seguida, clique em **Pesquisar**. 2. No painel **Resultados da Pesquisa**, clique em **Todos os arquivos e pastas**, em **Search Companion**. 3. Na caixa **Todo ou parte do nome do arquivo**, digite um nome de arquivo da tabela de informações de arquivo correta e clique em **Pesquisar**. 4. Na lista de arquivos, clique com o botão direito do mouse em um nome de arquivo da tabela de informações de arquivo correta e clique em **Propriedades**. **Observação** Dependendo da versão do sistema operacional ou dos programas instalados, alguns dos arquivos listados na tabela de informações de arquivos podem não estar instalados. 5. Na guia **Versão**, determine a versão do arquivo instalado no computador comparando-o com a versão documentada na tabela de informações de arquivos correta. **Observação** Atributos com versão diferente da versão do arquivo podem ser alterados durante a instalação. A comparação de outros atributos de arquivo com as informações na tabela não é um método suportado para verificar se a atualização foi aplicada. Além disso, em alguns casos, arquivos podem ser renomeados durante a instalação. Se as informações sobre o arquivo ou a versão não estiverem presentes, use um dos outros métodos disponíveis para verificar a instalação da atualização. - **Verificação da chave do Registro** Também é possível verificar os arquivos que esta atualização de segurança instalou analisando as seguintes chaves do Registro: Para Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005 e Windows XP Media Center Edition 2005: HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Updates\\Windows XP\\SP3\\KB914388\\Filelist Para Windows XP Professional x64 Edition: HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Updates\\Windows XP Version 2003\\SP2\\KB911820\\Filelist **Observação** Estas chaves do Registro podem não conter uma lista completa dos arquivos instalados. Além disso, talvez essas chaves do Registro não sejam criadas corretamente se um administrador ou um OEM integrar ou adicionar a atualização de segurança aos arquivos fonte da instalação do Windows. #### Windows 2000 (todas as versões) **Pré-requisitos** No caso do Windows 2000, esta atualização de segurança requer o Service Pack 4 (SP4). Para o Small Business Server 2000, esta atualização de segurança requer que o Small Business Server 2000 Service Pack 1a (SP1a) ou o Small Business Server 2000 esteja em execução no Windows 2000 Server Service Pack 4 (SP4). Os softwares relacionados foram testados para determinar se suas versões são afetadas. Outras versões já não incluem suporte para a atualização de segurança ou podem não ser afetadas. Para determinar o ciclo de vida do suporte para seu produto e sua versão, visite o [site do Microsoft Support Lifecycle](http://go.microsoft.com/fwlink/?linkid=21742). Para obter mais informações sobre como obter o service pack mais recente, consulte o artigo [260910](http://support.microsoft.com/kb/260910) (em inglês) da Base de Conhecimento Microsoft. **Inclusão em Service Packs futuros:** A atualização desse problema poderá ser incluída em um conjunto de atualizações futuro. **Informações sobre instalação** Esta atualização de segurança oferece suporte às seguintes opções de instalação: <p></p> <table class="dataTable"> <caption> Opções de instalação da atualização de segurança para as quais há suporte </caption> <tr class="thead"> <th style="border:1px solid black;" > Opção </th> <th style="border:1px solid black;" > Descrição </th> </tr> <tr> <td style="border:1px solid black;"> **/help** </td> <td style="border:1px solid black;"> Exibe as opções de linha de comando. </td> </tr> <tr> <th colspan="2"> Modos de instalação </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/passive** </td> <td style="border:1px solid black;"> Modo de instalação autônomo. Não é necessária a interação do usuário, mas o status da instalação é exibido. Se a reinicialização for necessária no fim da instalação, uma caixa de diálogo será apresentada para o usuário com um timer avisando que o computador será reiniciado em 30 segundos. </td> </tr> <tr> <td style="border:1px solid black;"> **/quiet** </td> <td style="border:1px solid black;"> Modo silencioso. O mesmo que modo autônomo, mas nenhuma mensagem de status ou de erro é exibida. </td> </tr> <tr> <th colspan="2"> Opções de reinicialização </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/norestart** </td> <td style="border:1px solid black;"> Não reinicia quando a instalação é concluída. </td> </tr> <tr> <td style="border:1px solid black;"> **/forcerestart** </td> <td style="border:1px solid black;"> Reinicia o computador após a instalação e força o fechamento de outros aplicativos no desligamento sem antes salvar os arquivos abertos. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/warnrestart\[:x\]** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo com um timer avisando ao usuário que o computador será reiniciado em *x* segundos. (A configuração padrão é 30 segundos.) Destina-se ao uso com as opções **/quiet** ou **/passive**. </td> </tr> <tr> <td style="border:1px solid black;"> **/promptrestart** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo solicitando que o usuário local permita a reinicialização. </td> </tr> <tr> <th colspan="2"> Opções especiais </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/overwriteoem** </td> <td style="border:1px solid black;"> Sobrescreve arquivos OEM sem notificação. </td> </tr> <tr> <td style="border:1px solid black;"> **/nobackup** </td> <td style="border:1px solid black;"> Não faz backup de arquivos necessários à desinstalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/forceappsclose** </td> <td style="border:1px solid black;"> Força o encerramento de outros programas quando o computador é desligado. </td> </tr> <tr> <td style="border:1px solid black;"> **/log:caminho** </td> <td style="border:1px solid black;"> Permite o redirecionamento dos arquivos de log da instalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/integrate:caminho** </td> <td style="border:1px solid black;"> Integra a atualização nos arquivos-fonte do Windows. Esses arquivos se encontram no caminho especificado na opção. </td> </tr> <tr> <td style="border:1px solid black;"> **/extract\[:caminho\]** </td> <td style="border:1px solid black;"> Extrai os arquivos sem iniciar o programa de instalação. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/ER** </td> <td style="border:1px solid black;"> Habilita o relatório de erros estendido. </td> </tr> <tr> <td style="border:1px solid black;"> **/verbose** </td> <td style="border:1px solid black;"> Habilita o registro extenso. Durante a instalação, cria %Windir%\\CabBuild.log. Esse log detalha os arquivos copiados. Se você usar esta opção, a instalação será bem mais lenta. </td> </tr> </table> **Observação** É possível combinar essas opções em uma única linha de comando. Para obter compatibilidade com versões anteriores, a atualização de segurança também oferece suporte às opções de instalação utilizadas por versões anteriores do utilitário de instalação. Para obter mais informações sobre opções com suporte de segurança, consulte o [artigo 262841 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/262841). Para obter mais informações sobre o instalador Update.exe, visite [o site Microsoft TechNet](http://www.microsoft.com/brasil/technet). Para obter mais informações sobre a terminologia que aparece neste boletim, como *hotfix*, consulte o [artigo 824684 (em inglês) do Microsoft](http://support.microsoft.com/kb/824684) Knowledge Base. **Informações de implantação** Para instalar a atualização de segurança sem nenhuma intervenção do usuário, use o seguinte comando em um prompt de comando do Windows 2000 Service Pack 4: **Windows2000- kb914388-x86-enu /quiet** **Observação** O uso da opção **/quiet** eliminará todas as mensagens. Isso inclui a eliminação de mensagens de falha. Os administradores devem usar um dos métodos com suporte para verificar se a instalação foi bem-sucedida quando utilizarem a opção **/quiet**. Os administradores também devem analisar o arquivo KB914388.log para obter informações sobre quaisquer mensagens de falha quando usarem essa opção. Para instalar a atualização de segurança sem forçar a reinicialização do sistema, use o seguinte comando em um prompt de comando do Windows XP Service Pack 4: **Windows2000- kb914388-x86-enu /norestart** Para obter informações sobre como implantar esta atualização de segurança com os serviços de atualização de software, visite o site [Serviços de Atualização de Software](http://www.microsoft.com/brasil/technet/seguranca/sus/). Para obter mais informações sobre como implantar esta atualização de segurança usando o recurso Windows Server Update Services, visite o [site do Windows Server Update Services](http://www.microsoft.com/brasil/technet/seguranca/wsus/default.mspx). Esta atualização de segurança também está disponível no [site Microsoft Update](http://update.microsoft.com/microsoftupdate). **Requisitos de reinicialização** É necessário reiniciar o sistema depois de aplicar essa atualização de segurança. **Informações sobre remoção** Para remover esta atualização de segurança, use a ferramenta Adicionar ou Remover Programas no Painel de Controle. Os administradores de sistema também podem usar o utilitário Spuninst.exe para remover esta atualização de segurança. O utilitário Spuninst.exe está localizado na pasta %Windir%\\$NTUninstallKB914388$\\Spuninst. <p></p> <table class="dataTable"> <caption> Opções do Spuninst.exe para as quais existe suporte </caption> <tr class="thead"> <th style="border:1px solid black;" > Opção </th> <th style="border:1px solid black;" > Descrição </th> </tr> <tr> <td style="border:1px solid black;"> **/help** </td> <td style="border:1px solid black;"> Exibe as opções de linha de comando. </td> </tr> <tr> <th colspan="2"> Modos de instalação </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/passive** </td> <td style="border:1px solid black;"> Modo de instalação autônomo. Não é necessária a interação do usuário, mas o status da instalação é exibido. Se a reinicialização for necessária no fim da instalação, uma caixa de diálogo será apresentada para o usuário com um timer avisando que o computador será reiniciado em 30 segundos. </td> </tr> <tr> <td style="border:1px solid black;"> **/quiet** </td> <td style="border:1px solid black;"> Modo silencioso. O mesmo que modo autônomo, mas nenhuma mensagem de status ou de erro é exibida. </td> </tr> <tr> <th colspan="2"> Opções de reinicialização </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/norestart** </td> <td style="border:1px solid black;"> Não reinicia quando a instalação é concluída. </td> </tr> <tr> <td style="border:1px solid black;"> **/forcerestart** </td> <td style="border:1px solid black;"> Reinicia o computador após a instalação e força o fechamento de outros aplicativos no desligamento sem antes salvar os arquivos abertos. </td> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/warnrestart\[:x\]** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo com um timer avisando ao usuário que o computador será reiniciado em *x* segundos. (A configuração padrão é 30 segundos.) Destina-se ao uso com as opções **/quiet** ou **/passive**. </td> </tr> <tr> <td style="border:1px solid black;"> **/promptrestart** </td> <td style="border:1px solid black;"> Exibe uma caixa de diálogo solicitando que o usuário local permita a reinicialização. </td> </tr> <tr> <th colspan="2"> Opções especiais </th> </tr> <tr class="alternateRow"> <td style="border:1px solid black;"> **/forceappsclose** </td> <td style="border:1px solid black;"> Força o encerramento de outros programas quando o computador é desligado. </td> </tr> <tr> <td style="border:1px solid black;"> **/log:caminho** </td> <td style="border:1px solid black;"> Permite o redirecionamento dos arquivos de log da instalação. </td> </tr> </table> **Informações sobre o arquivo** A versão em inglês desta atualização de segurança tem os atributos de arquivo relacionados na tabela abaixo. As datas e as horas destes arquivos estão de acordo com a hora universal coordenada (UTC). Quando você exibe as informações do arquivo, ele é convertido para a hora local. Para saber a diferença entre o UTC e o horário local, use a guia **Fuso Horário** na ferramenta Data e Hora, no Painel de Controle. Windows 2000 Service Pack 4 e Small Business Server 2000: | Nome do arquivo | Versão | Data | Hora | Tamanho | |-----------------|---------------|--------------------|-------|---------| | Dhcpcsvc.dll | 5.0.2195.7085 | 19 de maio de 2006 | 21:48 | 89.872 | | Dnsapi.dll | 5.0.2195.7085 | 19 de maio de 2006 | 21:48 | 136.976 | | Iphlpapi.dll | 5.0.2195.7097 | 19 de maio de 2006 | 21:48 | 68.368 | **Verificando a aplicação da atualização** - **Microsoft Baseline Security Analyzer** Para verificar se uma atualização de segurança foi aplicada em um sistema afetado, você pode utilizar a ferramenta MBSA (Microsoft Baseline Security Analyzer). Essa ferramenta permite que os administradores examinem os sistemas locais e remotos para saber se faltam atualizações de segurança ou se existem problemas de configuração comuns. Para obter mais informações sobre o MBSA, visite o site [Microsoft Baseline Security Analyzer](http://www.microsoft.com/brasil/technet/seguranca/mbsa/) (em inglês). - **Verificação de versão de arquivo** **Observação** Como existem várias versões do Microsoft Windows, as etapas a seguir podem ser diferentes no seu computador. Se isso acontecer, consulte a documentação do produto para completar estas etapas. 1. Clique em **Iniciar** e, em seguida, clique em **Pesquisar**. 2. No painel **Resultados da Pesquisa**, clique em **Todos os arquivos e pastas**, em **Search Companion**. 3. Na caixa **Todo ou parte do nome do arquivo**, digite um nome de arquivo da tabela de informações de arquivo correta e clique em **Pesquisar**. 4. Na lista de arquivos, clique com o botão direito do mouse em um nome de arquivo da tabela de informações de arquivo correta e clique em **Propriedades**. **Observação** Dependendo da versão do sistema operacional ou dos programas instalados, alguns dos arquivos listados na tabela de informações de arquivos podem não estar instalados. 5. Na guia **Versão**, determine a versão do arquivo instalado no computador comparando-o com a versão documentada na tabela de informações de arquivos correta. **Observação** Atributos com versão diferente da versão do arquivo podem ser alterados durante a instalação. A comparação de outros atributos de arquivo com as informações na tabela não é um método suportado para verificar se a atualização foi aplicada. Além disso, em alguns casos, arquivos podem ser renomeados durante a instalação. Se as informações sobre o arquivo ou a versão não estiverem presentes, use um dos outros métodos disponíveis para verificar a instalação da atualização. - **Verificação da chave do Registro** Também é possível verificar os arquivos instalados por esta atualização de segurança analisando a seguinte chave do Registro: HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Microsoft\\Updates\\Windows 2000\\SP5\\KB914388\\Filelist **Observação** Essa chave do Registro pode não conter uma lista completa de arquivos instalados. Além disso, talvez essa chave do Registro não seja criada corretamente quando um administrador ou um OEM integrar ou adicionar a atualização de segurança aos arquivos fonte da instalação do Windows. ### Outras informações **Agradecimentos** A Microsoft [agradece](http://go.microsoft.com/fwlink/?linkid=21127) à pessoa citada abaixo por trabalhar conosco para ajudar a proteger os clientes: - Mariano Nuñez Di Croce, da [Cybsec Security Systems](http://www.cybsec.com/) por relatar a vulnerabilidade de saturação de buffer no serviço do Cliente DHCP - CVE-2006-2372 **Obtendo Outras Atualizações de Segurança:** As atualizações para outros problemas de segurança estão disponíveis nos seguintes locais: - As atualizações de segurança estão disponíveis no [Centro de Download da Microsoft](http://go.microsoft.com/fwlink/?linkid=21129). você poderá encontrá-las com mais facilidade, executando uma pesquisa com a palavra-chave "patch\_de\_segurança". - Atualizações para plataformas do cliente estão disponíveis no [site Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747). **Suporte:** - Os clientes nos EUA e Canadá podem receber suporte técnico dos [Serviços de suporte ao produto Microsoft](http://go.microsoft.com/fwlink/?linkid=21131) pelo telefone 1-866-PCSAFETY. As ligações para obter suporte associado a atualizações de segurança são gratuitas. - Os clientes de outros países podem obter suporte nas subsidiárias locais da Microsoft. O suporte associado a atualizações de segurança é gratuito. Para obter mais informações sobre como entrar em contato com a Microsoft a fim de obter suporte a problemas, visite o site de [Suporte Internacional](http://go.microsoft.com/fwlink/?linkid=21155). **Recursos de segurança:** - O site [Microsoft TechNet Security](http://www.microsoft.com/brasil/technet/seguranca) fornece informações adicionais sobre segurança em produtos da Microsoft. - [Microsoft Software Update Services](http://www.microsoft.com/brasil/technet/seguranca/sus/) - [Microsoft Windows Server Update Services](http://www.microsoft.com/brasil/technet/seguranca/wsus/default.mspx) - [MBSA](http://www.microsoft.com/brasil/technet/seguranca/mbsa/) (Microsoft Baseline Security Analyzer) - [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130) - [Microsoft Update](http://update.microsoft.com/microsoftupdate) - Catálogo do Windows Update: Para obter mais informações sobre o Catálogo do Windows Update, consulte o [artigo 323166 (em inglês) da Base de Conhecimento Microsoft](http://support.microsoft.com/kb/323166). - [Office Update](http://go.microsoft.com/fwlink/?linkid=21135) **Software Update Services:** Usando o Microsoft Software Update Services (SUS), os administradores podem implantar de maneira rápida e confiável as últimas atualizações críticas e de segurança em servidores que executem o Windows 2000 e o Windows Server 2003 e em sistemas desktop que executem o Windows 2000 Professional ou o Windows XP Professional. Para obter mais informações sobre como implantar atualizações de segurança usando os serviços de atualização de software, visite o site [Software Update Services](http://www.microsoft.com/brasil/technet/seguranca/sus/). **Windows Server Update Services:** Usando o WSUS (Windows Server Update Services), os administradores podem implantar de forma rápida e confiável as mais recentes atualizações críticas e de segurança dos sistemas operacionais Windows 2000 e posterior, Office XP e posterior, Exchange Server 2003, e SQL Server 2000 nos sistemas operacionais Windows 2000 e posteriores. Para obter mais informações sobre como implantar atualizações de segurança usando o recurso Windows Server Update Services, visite o [site do Windows Server Update Services](http://www.microsoft.com/brasil/technet/seguranca/wsus/default.mspx). **Systems Management Server:** O SMS (Microsoft Systems Management Server) fornece uma solução corporativa altamente configurável para gerenciar atualizações. Ao usar o SMS, os administradores podem identificar os sistemas baseados no Windows que precisam de atualizações de segurança, bem como executar uma implantação controlada dessas atualizações em toda a empresa com o mínimo de interrupção para os usuários finais. Para obter mais informações sobre como os administradores podem usar o SMS 2003 para implantar atualizações de segurança, visite o site [Gerenciamento de Patches de Segurança do SMS 2003](http://go.microsoft.com/fwlink/?linkid=22939). Os usuários do SMS 2.0 também podem usar o [Software Updates Service Feature Pack](http://go.microsoft.com/fwlink/?linkid=33340) (site em inglês) para ajudar a implantar atualizações de segurança. Para obter mais informações sobre o SMS, visite o [site do SMS](http://www.microsoft.com/brasil/sms) **Observação:** o SMS usa o Microsoft Baseline Security Analyzer, a Microsoft Office Detection Tool e a Enterprise Update Scanning Tool para oferecer amplo suporte à detecção e à implantação da atualização do boletim de segurança. Algumas atualizações de software podem não ser detectadas por essas ferramentas. Os administradores podem usar os recursos de inventário do SMS nesses casos para apontar as atualizações de sistemas específicos. Para obter mais informações sobre esse procedimento, consulte o seguinte [site](http://go.microsoft.com/fwlink/?linkid=33341). Algumas atualizações de segurança exigirão direitos administrativos quando o sistema for reiniciado. Os administradores podem usar a Elevated Rights Deployment Tool (disponível no [SMS 2003 Administration Feature Pack](http://go.microsoft.com/fwlink/?linkid=33387) e no [SMS 2.0 Administration Feature Pack](http://go.microsoft.com/fwlink/?linkid=21161)) (sites em inglês) para instalar essas atualizações. **Aviso de isenção de responsabilidade:** As informações fornecidas no Base de Conhecimento Microsoft são apresentadas "no estado em que se encontram", sem garantia de qualquer tipo. A Microsoft se isenta de todas as garantias, expressas ou implícitas, inclusive as garantias de comercialização e adequação a um propósito específico. Em hipótese alguma a Microsoft Corporation ou seus fornecedores serão responsáveis por quaisquer danos, inclusive danos diretos, indiretos, incidentais, conseqüenciais, danos por lucros cessantes ou danos especiais, mesmo que a Microsoft Corporation ou seus fornecedores tenham sido alertados da possibilidade dos referidos danos. Como alguns estados não permitem a exclusão ou limitação de responsabilidade por danos conseqüenciais ou indiretos, a limitação acima pode não ser aplicável a você. **Revisões:** - V1.0 (11 de julho de 2006): Boletim publicado. *Built at 2014-04-18T01:50:00Z-07:00*

57.597374

975

0.723831

por_Latn

0.998559

b5ab62c9ed46afa682ed39495a85d0dad2f48797

4,349

md

Markdown

docs/extensibility/debugger/debug-engine.md

MicrosoftDocs/visualstudio-docs.cs-cz

3861d52726f1a515cfa62d590513a3c7a1b8019b

[ "CC-BY-4.0", "MIT" ]

1

2020-05-20T07:48:22.000Z

docs/extensibility/debugger/debug-engine.md

MicrosoftDocs/visualstudio-docs.cs-cz

3861d52726f1a515cfa62d590513a3c7a1b8019b

[ "CC-BY-4.0", "MIT" ]

7

2018-10-02T15:01:11.000Z

2021-11-05T20:25:20.000Z

docs/extensibility/debugger/debug-engine.md

MicrosoftDocs/visualstudio-docs.cs-cz

3861d52726f1a515cfa62d590513a3c7a1b8019b

[ "CC-BY-4.0", "MIT" ]

7

2018-10-01T22:49:53.000Z

2021-10-09T11:24:44.000Z

--- title: Ladění modulu | Microsoft Docs description: Zjistěte, jak ladicí modul funguje s interpretem nebo operačním systémem a poskytuje služby, jako je řízení spouštění, zarážky a vyhodnocení výrazů. ms.custom: SEO-VS-2020 ms.date: 11/04/2016 ms.topic: reference helpviewer_keywords: - debug engines ms.assetid: 148b1efc-ca07-4d8e-bdfc-c723a760c620 author: leslierichardson95 ms.author: lerich manager: jmartens ms.technology: vs-ide-debug ms.workload: - vssdk ms.openlocfilehash: 4836141f50f2db13ad0fd303168d291b56ab1643 ms.sourcegitcommit: 68897da7d74c31ae1ebf5d47c7b5ddc9b108265b ms.translationtype: MT ms.contentlocale: cs-CZ ms.lasthandoff: 08/13/2021 ms.locfileid: "122111746" --- # <a name="debug-engine"></a>Ladicí modul Ladicí modul (DE) spolupracuje s interpretem nebo operačním systémem a poskytuje ladicí služby, jako je řízení spouštění, zarážky a vyhodnocení výrazů. DE zodpovídá za monitorování stavu laděného programu. K tomu destrukce používá jakékoli metody, které jsou k dispozici v podporovaném modulu runtime, ať už z procesoru nebo z rozhraní API dodaných runtime. Například modul CLR (Common Language Runtime) poskytuje mechanismy pro monitorování spuštěného programu prostřednictvím rozhraní ICorDebugXXX. DE, která podporuje CLR, používá příslušná rozhraní ICorDebugXXX k sledování laděného programu spravovaného kódu. Všechny změny stavu pak předá správci ladění relací (SDM), který tyto informace předá integrovanému vývojovému [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] prostředí (IDE). > [!NOTE] > Ladicí modul cílí na konkrétní modul runtime, to znamená na systém, ve kterém se spouští laděné programy. Modul CLR je modul runtime pro spravovaný kód a modul runtime Win32 je pro nativní Windows aplikací. Pokud jazyk, který vytvoříte, může cílit na jeden z těchto dvou modulů runtime, [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] již poskytuje potřebné ladicí moduly. Vše, co musíte implementovat, je vyhodnocovač výrazů. ## <a name="debug-engine-operation"></a>Operace ladicího modulu Monitorovací služby jsou implementované prostřednictvím rozhraní DE a mohou způsobit přechod ladicího balíčku mezi různými provozními režimy. Další informace najdete v tématu [Provozní režimy.](../../extensibility/debugger/operational-modes.md) Pro běhové prostředí je obvykle k dispozici pouze jedna implementace DE. > [!NOTE] > I když existují samostatné implementace DE pro Transact-SQL [!INCLUDE[jsprjscript](../../debugger/debug-interface-access/includes/jsprjscript_md.md)] a , VBScript [!INCLUDE[jsprjscript](../../debugger/debug-interface-access/includes/jsprjscript_md.md)] a sdílejí jednu de. [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] ladění umožňuje ladicím modulům spustit jeden ze dvou způsobů: buď ve stejném procesu jako prostředí, nebo ve stejném procesu jako cílový [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] program, který se ladí. K druhému formuláři obvykle dochází, když je laděné procesy ve skutečnosti skript spuštěný v interpretu. Ladicí modul musí mít znalosti interpreta, aby mohl skript monitorovat. V tomto případě je interpret ve skutečnosti modul runtime. ladicí moduly jsou pro konkrétní implementace modulu runtime. Kromě toho lze implementaci jedné destrukce rozdělit napříč hranicemi procesu a počítače (například vzdálené ladění). DE zpřístupňuje [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] rozhraní ladění. Veškerá komunikace je prostřednictvím modelu COM. Bez ohledu na to, jestli je DE načtený v procesu, mimo proces nebo na jiném počítači, nemá vliv na komunikaci komponent. De pracuje s komponentou vyhodnocovače výrazů, aby umožnila DE pro tento konkrétní modul runtime pochopit syntaxi výrazů. De také pracuje s komponentou obslužné rutiny symbolů pro přístup k symbolickým ladicím informacím generovaným kompilátorem jazyka. Další informace najdete v tématu [Vyhodnocovač výrazů a](../../extensibility/debugger/expression-evaluator.md) [Poskytovatel symbolů](../../extensibility/debugger/symbol-provider.md). ## <a name="see-also"></a>Viz také - [Komponenty ladicího programu](../../extensibility/debugger/debugger-components.md) - [Vyhodnocovač výrazů](../../extensibility/debugger/expression-evaluator.md) - [Zprostředkovatel symbolů](../../extensibility/debugger/symbol-provider.md)

92.531915

700

0.804323

ces_Latn

0.999332

b5ab7fcdab7980873c46a32d5dfce05878dfede0

267

md

Markdown

README.md

HowProgrammingWorks/SQL

81db440a70856898e825fa8df3167957954d83b8

[ "MIT" ]

6

2019-10-31T02:33:45.000Z

2020-12-12T16:59:00.000Z

README.md

HowProgrammingWorks/SQL

81db440a70856898e825fa8df3167957954d83b8

[ "MIT" ]

null

README.md

HowProgrammingWorks/SQL

81db440a70856898e825fa8df3167957954d83b8

[ "MIT" ]

1

2019-11-10T14:30:48.000Z

# Structured Query Language [![Введение в SQL: SELECT](https://img.youtube.com/vi/Z679c8S0d7I/0.jpg)](https://youtu.be/Z679c8S0d7I) [![Введение в SQL: CREATE, ALTER, DROP, ключи, индексы](https://img.youtube.com/vi/QF0v29ZneYE/0.jpg)](https://youtu.be/QF0v29ZneYE)

44.5

132

0.734082

kor_Hang

0.186841

b5acedb292dcb36d2548bd6f7b97e7ffada7fb46

79

md

Markdown

Linux/parted.md

markfranciose/cheat_sheet_of_cheat_sheets

d126bbbb499af43098d3938e35df3381833cecac

[ "MIT" ]

null

Linux/parted.md

markfranciose/cheat_sheet_of_cheat_sheets

d126bbbb499af43098d3938e35df3381833cecac

[ "MIT" ]

20

2020-07-21T01:52:53.000Z

2022-02-27T09:44:44.000Z

Linux/parted.md

markfranciose/drops_of_knowledge

d126bbbb499af43098d3938e35df3381833cecac

[ "MIT" ]

null

list partition layout, gpt/mbr, size, filesystem, name, flags ```parted -l```

26.333333

77

0.696203

eng_Latn

0.92666

b5ad415fb9ddf332f569b147d1837b590257758d

164

md

Markdown

README.md

AndreaCimminoArriaga/wot-discovery-testing

26e94b300a050537bb71e11afaa7f5ac9c7e9ea2

[ "MIT" ]

3

2021-06-09T14:17:08.000Z

2021-06-17T10:18:54.000Z

README.md

AndreaCimminoArriaga/wot-discovery-testing

26e94b300a050537bb71e11afaa7f5ac9c7e9ea2

[ "MIT" ]

8

2021-06-10T11:26:55.000Z

2022-03-28T14:13:57.000Z

README.md

AndreaCimminoArriaga/wot-discovery-testing

26e94b300a050537bb71e11afaa7f5ac9c7e9ea2

[ "MIT" ]

3

2021-06-10T10:41:05.000Z

2021-07-06T12:57:40.000Z

# WoT Discovery Testing Test suites for [W3C WoT Discovery](https://www.w3.org/TR/wot-discovery/) APIs. Test suites: * [Directory](./directory) * [DNS-SD](./dnssd)

27.333333

79

0.707317

kor_Hang

0.363484

b5adb52460ec20451eaef0e5a64a017b74c0b9e1

704

md

Markdown

_pages/about.md

Avyiel/lucasvienna.dev

d6c62fc734bc79139e38444ac4d72748cda5b568

[ "MIT" ]

null

_pages/about.md

Avyiel/lucasvienna.dev

d6c62fc734bc79139e38444ac4d72748cda5b568

[ "MIT" ]

4

2019-08-14T19:33:27.000Z

2021-09-27T21:53:12.000Z

_pages/about.md

Avyiel/lucasvienna.dev

d6c62fc734bc79139e38444ac4d72748cda5b568

[ "MIT" ]

null

--- layout: page title: About subtitle: A few words about me permalink: /about --- #### _Student, hacker, translator. I like to solve problems and build things._ Lucas is a software developer originally from São Paulo, Brazil and currently living in Karlsruhe, Germany. He studies Business Informatics at the Karlsruhe University of Applied Sciences (HsKA), and is a working student at [EDOMO](https://edomo.de). He is a web and mobile developer with experience in edge AI and IoT, a professional translator with a background in AAA videogames and web/mobile applications, and an enthusiat for automation, containers and CI/CD development. His current focus is **DevOps**, **REST APIs** and **Vue**.

46.933333

250

0.768466

eng_Latn

0.996732

b5b015b602f781bc6bef3fdff515a069a1f91958

1,506

md

Markdown

deploy/README.md

jingtaozhang18/fission

8ff61fe51359d8927a0058061640b87bdc6cf5af

[ "Apache-2.0" ]

1

2020-09-04T03:27:00.000Z

deploy/README.md

jingtaozhang18/fission

8ff61fe51359d8927a0058061640b87bdc6cf5af

[ "Apache-2.0" ]

null

deploy/README.md

jingtaozhang18/fission

8ff61fe51359d8927a0058061640b87bdc6cf5af

[ "Apache-2.0" ]

2

2020-09-04T03:27:02.000Z

2020-09-04T03:29:49.000Z

# 基于Minikube的Fission 及其依赖的基础环境部署 ## 部署使用的命令版本如下 | command | version | | :------: | :--------: | | minikube | v1.14.0 | | kubectl | v1.18.5 | | helm | v3.2.4 | | ktctl | 0.0.13-rc7 | ## 部署流程 ### 创建minikube集群创建集群之前，需要先确认创建集群的**名称**`CONTEXT_NAME`和集群使用的虚拟化技术`--driver`，具体细节请参考minikube的[官网](https://kubernetes.io/zh/docs/setup/learning-environment/minikube/) 。 ```shell deploy$ make start_minikube ``` ### 获取集群信息创建好集群之后，使用如下命令获取集群的`DOCKER_TLS_VERIFY`、`DOCKER_HOST`、`DOCKER_CERT_PATH`和`MINIKUBE_ACTIVE_DOCKERD`信息，对应修改Makefile中的变量 ```shell deploy$ minikube docker-env ``` ### 创建基础环境和Fission 环境现在可以通过以下命令完成基础设施环境和Fission环境的复现，具体完成的任务如下： ```shell deploy$ make init_fission_cluster ``` 部署minikube的基础设施环境，包括： * 本地存储类 * NFS存储类 * 注册到Rancher中 * Kafka * Keda *ps：如果有PVC创建失败的问题，可以手动设置一下默认存储类为`local-path`* 编译Fission的组件镜像，包括： * Bundle * Fetcher * Preupgradechecks * Builder * Cli * FluentdWrapper * DataFlowVisualizationFrontend * DataFlowVisualizationBackend 编译Fission的ENV环境，包括： * Python 使用helm3部署Fission环境，并创建一个Python的ENV环境。 *ps：部署脚本只兼容`fission-all`，对`fission-core`暂时不兼容* ## 开发工具在对某个组件的代码进行修改的时候，可以采用本地运行该组件，使用`ktctl`工具替换掉集群中对应的组件，将流量导向本地运行的组件，同时使用http代理将本地运行的组件的流量导回集群中。参考命令： ```bash deploy$ make kt_vpn deploy$ make kt_exchange_executor ``` 同时提供推送全部改动过的fission镜像到仓库中，并通过仓库中的镜像在其他的集群中部署Fission服务。相关命令如下： ``` bash deploy$ make push_fission_images deploy$ make install_fission_public ``` *脚本中的仓库地址`ml.jingtao.fun`是jingtao的私有仓库，但是暂时没有认证保护，请大佬们手下留情，之后会设置密码限制推送*

16.193548

149

0.749668

yue_Hant

0.639587

b5b15d7e3982efcb42d546b2661106157aa9ba84

6,471

md

Markdown

README.md

awesome-archive/Automatic_Speech_Recognition

28c7f78064006a68fb12001b37e3893a87cb798c

[ "MIT" ]

null

README.md

awesome-archive/Automatic_Speech_Recognition

28c7f78064006a68fb12001b37e3893a87cb798c

[ "MIT" ]

null

README.md

awesome-archive/Automatic_Speech_Recognition

28c7f78064006a68fb12001b37e3893a87cb798c

[ "MIT" ]

null

# Automatic-Speech-Recognition End-to-end automatic speech recognition system implemented in TensorFlow. ## Recent Updates - [x] **Support TensorFlow r1.0** (2017-02-24) - [x] **Support dropout for dynamic rnn** (2017-03-11) - [x] **Support running in shell file** (2017-03-11) - [x] **Support evaluation every several training epoches automatically** (2017-03-11) - [x] **Fix bugs for character-level automatic speech recognition** (2017-03-14) - [x] **Improve some function apis for reusable** (2017-03-14) - [x] **Add scaling for data preprocessing** (2017-03-15) - [x] **Add reusable support for LibriSpeech training** (2017-03-15) - [x] **Add simple n-gram model for random generation or statistical use** (2017-03-23) - [x] **Improve some code for pre-processing and training** (2017-03-23) - [x] **Replace TABs with blanks and add nist2wav converter script** (2017-04-20) ## Recommendation If you want to replace feed dict operation with Tensorflow multi-thread and fifoqueue input pipeline, you can refer to my repo [TensorFlow-Input-Pipeline](https://github.com/zzw922cn/TensorFlow-Input-Pipeline) for more example codes. My own practices prove that fifoqueue input pipeline would improve the training speed in some time. If you want to look the history of speech recognition, I have collected the significant papers since 1981 in the ASR field. You can read awesome paper list in my repo [awesome-speech-recognition-papers](https://github.com/zzw922cn/awesome-speech-recognition-papers), all download links of papers are provided. I will update it every week to add new papers, including speech recognition, speech synthesis and language modelling. I hope that we won't miss any important papers in speech domain. All my public repos will be updated in future, thanks for your stars! ## Performance ### PER based dynamic BLSTM on TIMIT database, with casual tuning because time it limited ![image](https://github.com/zzw922cn/Automatic_Speech_Recognition/blob/master/PER.png) ## Content This is a powerful library for **automatic speech recognition**, it is implemented in TensorFlow and support training with CPU/GPU. This library contains followings models you can choose to train your own model: * Data Pre-processing * Acoustic Modeling * RNN * BRNN * LSTM * BLSTM * GRU * BGRU * Dynamic RNN * Deep Residual Network * Seq2Seq with attention decoder * etc. * CTC Decoding * Evaluation(Mapping some similar phonemes) * Saving or Restoring Model * Mini-batch Training * Training with GPU or CPU with TensorFlow * Keeping logging of epoch time and error rate in disk ## Usage <pre> python train.py --mfcc_dir '/data/mfcc/' --label_dir '/data/label/' --keep False --save True --evaluation False --learning_rate 0.001 --batch_size 32 --num_feature 39 --num_hidden 128 --num_classes 28 --save_dir '/src/save/' --restore_from '/src/save/' --model_checkpoint_path '/src/save/' </pre> Instead of configuration in command line, you can also set the arguments above in [train.py](https://github.com/zzw922cn/Automatic-Speech-Recognition/blob/master/src/main/train.py) in practice. ## Implementation Details ### Data preprocessing #### TIMIT corpus The original TIMIT database contains 6300 utterances, but we find the 'SA' audio files occurs many times, it will lead bad bias for our speech recognition system. Therefore, we removed the all 'SA' files from the original dataset and attain the new TIMIT dataset, which contains only 5040 utterances including 3696 standard training set and 1344 test set. Automatic Speech Recognition is to transcribe a raw audio file into character sequences. Data preprocessing is to convert a raw audio file into feature vectors of several frames. Here, we first split each audio file by a 20ms hamming window with an overlap of 10ms, and then calculate the 12 mel frequency ceptral coefficients appended by an energy variable for each frame. Based on this vector of length 13, we calculate the delta coefficients and delta-delta coefficients, therefore, we attain totally 39 coefficients for each frame. Therefore, each audio file is splited to several frames by hamming window, and each frame is extracted to a feature vector of length 39. If you want to attain the feature vector of different length, you can reset the settings in the file [timit\_preprocess.py](https://github.com/zzw922cn/Automatic-Speech-Recognition/blob/master/src/feature/timit_preprocess.py). In folder data/mfcc, each file is a feature matrix with size timeLength\*39 of one audio file; in folder data/label, each file is a label vector according to the mfcc file. If you want to set your own data preprocessing, you can edit [calcmfcc.py](https://github.com/zzw922cn/Automatic-Speech-Recognition/blob/master/src/feature/calcmfcc.py) or [timit\_preprocess.py](https://github.com/zzw922cn/Automatic-Speech-Recognition/blob/master/src/feature/timit_preprocess.py). Since the original TIMIT dataset contains 61 phonemes, we use 61 phonemes for training and evaluation, but when scoring, we mappd the 61 phonemes into 39 phonemes for better performance. We do this mapping according to the paper [Speaker-independent phone recognition using hidden Markov models](http://repository.cmu.edu/cgi/viewcontent.cgi?article=2768&context=compsci). The mapping details are as follows: | original phoneme(s) | mapped into phoneme | | :------------------ | :-------------------: | | ux | uw | | axr | er | | em | m | | nx, n | en | | eng | ng | | hv | hh | | cl, bcl, dcl, gcl, epi, h#, kcl, pau, pcl, tcl, vcl | sil | | l | el | | zh | sh | | aa | ao | | ix | ih | | ax | ah | #### LibriSpeech corpus TODO #### Wall Street Journal corpus TODO ### Core Features + dynamic RNN(GRU, LSTM) + Residual Network(Deep CNN) + CTC Decoding + TIMIT Phoneme Edit Distance(PER) ## Future Work - [ ] Add Attention Mechanism - [ ] Add more efficient dynamic computation graph without padding - [ ] List experimental results - [ ] Implement more ASR models following newest investigations - [ ] Provide fast TensorFlow Input Pipeline ## Contact Me If my code is helpful to you, please give me a **star and fork** to encourage me to keep updating. Thank you. For any questions, welcome to send email to :**[email protected]**. If you use wechat, you can follow me by searching wechat public media id:**deeplearningdigest**, I would push several articles every week to share my deep learning practices with you. Thanks!

51.357143

899

0.753516

eng_Latn

0.970136

b5b171a6f9b246e855e18e84e257bd1ee46f6c83

2,201

md

Markdown

src/tr/2019-03/09/03.md

PrJared/sabbath-school-lessons

94a27f5bcba987a11a698e5e0d4279b81a68bc9a

[ "MIT" ]

68

2016-10-30T23:17:56.000Z

2022-03-27T11:58:16.000Z

src/tr/2019-03/09/03.md

PrJared/sabbath-school-lessons

94a27f5bcba987a11a698e5e0d4279b81a68bc9a

[ "MIT" ]

367

2016-10-21T03:50:22.000Z

2022-03-28T23:35:25.000Z

src/tr/2019-03/09/03.md

PrJared/sabbath-school-lessons

94a27f5bcba987a11a698e5e0d4279b81a68bc9a

[ "MIT" ]

109

2016-08-02T14:32:13.000Z

2022-03-31T10:18:41.000Z

--- title: Tabita’nın Hizmeti ve Tanıklığı date: 26/08/2019 --- Kilise, İsa’nın öngördüğü gibi “Yeruşalim’de, bütün Yahudiye ve Samiriye’de ve dünyanın dört bucağında” (Elç. 1:8) yayılmaya başlayınca, yeni imanlılar İsa’nın imanını ve hizmetini sürdürdüler. Bunlardan biri de Yafa kentindeki Tabita’ydı. Anlaşılan İsa’nın belli bir talimatını ciddiye almıştı, öyle ki giysisi olmayanları giydirme işini bizzat İsa için yapıyordu (bkz. Mat. 25:38, 40). `Elçilerin İşleri 9:36 ayetinde Tabita’nın ve hizmetinin tanımını oku. Senin hayatın ve hizmetin bu ayettekine benzer şekilde nasıl anlatılabilirdi? Nasıl anlatılmak istersin?` Tabita’nın hizmeti, anlaşıldığı kadarıyla onun “öğrenci” (bkz. Elç. 9:36) olarak tanımlanacağı ve sadakatinin, gayretinin ve başkalarına odaklanmasının yaşadığı kentin dışında bile tanınacağı seviyedeydi. Petrus komşu Lidda kentini ziyaret ederken, Yafalılar Tabita’nın ani ölümü üzerine ondan gelmesini istediler (bkz. Elç. 9:37–41). Petrus Yafa’ya vardığında, Tabita’nın yoksullar için çalışması sırasında yardım ettiği birçok insan tarafından karşılandı. Ona Tabita’nın diktiği giysileri gösterdiler ve şüphesiz kendilerine ve başkalarına nasıl yardım ettiğine dair öyküler anlatılar. Petrus’un bundan sonra Tabita için dua etmiş olması ve Allah’ın onu diriltmesi tabi ki hayatlarını başkalarına hizmet etmeye adamış kişilerin yaşamlarının her zaman iyi gideceğinin güvencesi değil. Sonuçta Tabita hastalık çekmiş ve ölmüştü, kilisedeki dul kadınlara hizmet etmesi için atanan ilk yardımcılardan biri olan İstefanos da ilk şehit olmuştu (bkz. Elç. 7:54–60). Hizmet hayatı pürüzsüz bir patika değildir; hatta zaman zaman çok daha zor bir yol olabilir. Fakat bu öyküde Allah Yafalıların üzerinde güçlü bir etki bırakmak için Tabita’nın hem hayatında hem de ölümünde fark edilen Kendi sevgisini ve kudretini kullandı: “Bu olayın haberi bütün Yafa’ya yayıldı ve birçokları Rabb’e inandı” (Elç. 9:42). `Hayatını yitiren sen olsaydın, senin katkıların da Tabita’nın hizmeti gibi hatırlanır ve özlenir miydi? Nasıl daha iyi bir hizmet mirası bırakabiliriz? Başkalarına hizmette kullanabileceğin –Tabita’nın giysi dikebilmesi gibi¬– hangi pratik becerilere sahipsin?`

122.277778

465

0.818264

tur_Latn

0.999997

b5b2083b63c3e54aa1739f53c91f36fe75ad8904

969

md

Markdown

CHANGELOG.md

vsoch/containershare

2a0c13f0a1950df4fcffe94aba584254267f7d85

[ "BSD-3-Clause" ]

4

2018-08-07T17:12:33.000Z

2020-10-16T22:20:00.000Z

CHANGELOG.md

vsoch/repo2docker-containers

2a0c13f0a1950df4fcffe94aba584254267f7d85

[ "BSD-3-Clause" ]

8

2018-07-29T23:06:16.000Z

2018-08-10T02:54:32.000Z

CHANGELOG.md

vsoch/repo2docker-containers

2a0c13f0a1950df4fcffe94aba584254267f7d85

[ "BSD-3-Clause" ]

1

2020-04-23T02:24:30.000Z

# CHANGELOG This is a manually generated log to track changes to the repository for each release. Each section should include general headers such as **Implemented enhancements** and **Merged pull requests**. All closed issued and bug fixes should be represented. Critical items to know are: - renamed commands - deprecated / removed commands - changed defaults - backward incompatible changes (recipe file format? image file format?) - migration guidance (how to convert images?) - changed behaviour (recipe sections work differently) ## [master](https://github.com/vsoch/containershare/tree/master) (master) - templates for conda and r have been added, along with "templates" tag (8-10-2018) - added scripts/create.py to create a containershare folder from the library.json (8-09-2018) - this CHANGELOG ## [0.0.3](https://github.com/vsoch/containershare/releases/tag/0.0.3) (0.0.3) - original release with web interface, 3 examples, and JOSS paper

40.375

94

0.759546

eng_Latn

0.99572

b5b242cda17f6b2347cdd40434c6ab8cb4bcd631

32

md

Markdown

README.md

Asterisk-346Production/PondokWebSkripsi

069e5a90fedf671d57b7a4c865ef00e3fab9835c

[ "Apache-2.0" ]

null

README.md

Asterisk-346Production/PondokWebSkripsi

069e5a90fedf671d57b7a4c865ef00e3fab9835c

[ "Apache-2.0" ]

null

README.md

Asterisk-346Production/PondokWebSkripsi

069e5a90fedf671d57b7a4c865ef00e3fab9835c

[ "Apache-2.0" ]

null

# PondokWebSkripsi upload later

10.666667

18

0.84375

ind_Latn

0.966423

b5b3867f28880e23c12fb74219190d8092aa1fda

123

md

Markdown

README.md

wizzomafizzo/js-snake

5811878e6cce4eedb509813fbf641cd301e7e21d

[ "MIT" ]

null

README.md

wizzomafizzo/js-snake

5811878e6cce4eedb509813fbf641cd301e7e21d

[ "MIT" ]

null

README.md

wizzomafizzo/js-snake

5811878e6cce4eedb509813fbf641cd301e7e21d

[ "MIT" ]

null

# js-snake JavaScript implementation of Snake ![woohoo](https://raw.github.com/wizzomafizzo/js-snake/master/screenie.png)

24.6

75

0.788618

kor_Hang

0.133426

b5b3e545bf26873b2269ad4f2c6aa1567fcc75d5

357

md

Markdown

deployment.md

jwspaeth/FAA-Project

afa9d3bec10deead48c4b17dff69df2e02691e41

[ "MIT" ]

null

deployment.md

jwspaeth/FAA-Project

afa9d3bec10deead48c4b17dff69df2e02691e41

[ "MIT" ]

2

2019-10-20T00:42:40.000Z

2019-10-30T18:06:11.000Z

deployment.md

jwspaeth/FAA-Project

afa9d3bec10deead48c4b17dff69df2e02691e41

[ "MIT" ]

null

# Deployment Since this is a machine learning model, deployment is a little different than with a standard application. The user must set up configurations for the dataset before running the model. Running the model is as easy as running ./main. Since this product is purely for internal use, deployment is not necessary other than delivering the model.

59.5

125

0.803922

eng_Latn

0.999964

b5b6efeb36902d9657546a57c8fc7610f85024db

350

md

Markdown

README.md

egberts/vim-2-tiered-recursion-syntax

fc1b74f694e48c4c70bf3bf037be1a725d21ce08

[ "MIT" ]

null

README.md

egberts/vim-2-tiered-recursion-syntax

fc1b74f694e48c4c70bf3bf037be1a725d21ce08

[ "MIT" ]

null

README.md

egberts/vim-2-tiered-recursion-syntax

fc1b74f694e48c4c70bf3bf037be1a725d21ce08

[ "MIT" ]

null

# vim-2-tiered-recursion-syntax How to perform recursive syntax using 2-tiered near-similar syntaxes. This is a repost from Vim StackExchange on a real problem of writing recursive Vim syntax for the ISC Bind9 named configuratin file, specifically the `acl` keyword and its `address_match_list`. Source: https://vi.stackexchange.com/a/24498/18880

35

69

0.802857

eng_Latn

0.979383

b5b8cdf3eb42f872bca57cefe2b4edf82527f743

52

md

Markdown

README.md

npillmayer/fp

cd59007faf1649738da5f281e583b9cf5df27a26

[ "BSD-3-Clause" ]

1

2022-03-17T13:02:52.000Z

README.md

npillmayer/fp

cd59007faf1649738da5f281e583b9cf5df27a26

[ "BSD-3-Clause" ]

null

README.md

npillmayer/fp

cd59007faf1649738da5f281e583b9cf5df27a26

[ "BSD-3-Clause" ]

null

# fp Experiments with Go1.18 functional programming

17.333333

46

0.826923

eng_Latn

0.990009

b5b9528cf643bc8a7396d0c66ab2eceb6f23938b

3,642

md

Markdown

docs/benchmarks/03.04.2021/SortingNetworks.Benchmarks.SN19Benchmark-report-github.md

petarpetrovt/sorting-networks

dda423e85693f7ed70545fe8dbb939328534a269

[ "MIT" ]

2

2020-09-17T18:16:54.000Z

2020-11-16T07:04:42.000Z

docs/benchmarks/03.04.2021/SortingNetworks.Benchmarks.SN19Benchmark-report-github.md

petarpetrovt/sorting-networks

dda423e85693f7ed70545fe8dbb939328534a269

[ "MIT" ]

22

2020-09-17T18:17:33.000Z

2021-04-17T07:02:27.000Z

docs/benchmarks/03.04.2021/SortingNetworks.Benchmarks.SN19Benchmark-report-github.md

petarpetrovt/sorting-networks

dda423e85693f7ed70545fe8dbb939328534a269

[ "MIT" ]

1

2020-09-17T18:05:56.000Z

``` ini BenchmarkDotNet=v0.12.1.1521-nightly, OS=Windows 10.0.19042.867 (20H2/October2020Update) AMD Ryzen 7 3700X, 1 CPU, 16 logical and 8 physical cores .NET SDK=6.0.100-preview.2.21155.3 [Host] : .NET 6.0.0 (6.0.21.15406), X64 RyuJIT .NET 5.0 : .NET 5.0.4 (5.0.421.11614), X64 RyuJIT .NET 6.0 : .NET 6.0.0 (6.0.21.15406), X64 RyuJIT .NET Core 3.1 : .NET Core 3.1.13 (CoreCLR 4.700.21.11102, CoreFX 4.700.21.11602), X64 RyuJIT .NET Framework 4.8 : .NET Framework 4.8 (4.8.4300.0), X64 RyuJIT InvocationCount=1 UnrollFactor=1 ``` | Method | Job | Runtime | Length | Count | Mean | Error | StdDev | Gen 0 | Gen 1 | Gen 2 | Allocated | |---------------------- |------------------- |------------------- |------- |--------- |---------:|--------:|--------:|------:|------:|------:|----------:| | BoseNelson_Comparable | .NET 5.0 | .NET 5.0 | 19 | 12000000 | 124.8 ms | 0.15 ms | 0.12 ms | - | - | - | - | | BoseNelson_Branchless | .NET 5.0 | .NET 5.0 | 19 | 12000000 | 196.4 ms | 0.28 ms | 0.23 ms | - | - | - | - | | Insertion_Comparable | .NET 5.0 | .NET 5.0 | 19 | 12000000 | 125.6 ms | 0.45 ms | 0.40 ms | - | - | - | - | | BoseNelson_Comparable | .NET 6.0 | .NET 6.0 | 19 | 12000000 | 127.6 ms | 1.08 ms | 0.96 ms | - | - | - | 144 B | | BoseNelson_Branchless | .NET 6.0 | .NET 6.0 | 19 | 12000000 | 196.0 ms | 0.12 ms | 0.09 ms | - | - | - | 144 B | | Insertion_Comparable | .NET 6.0 | .NET 6.0 | 19 | 12000000 | 132.5 ms | 2.62 ms | 2.57 ms | - | - | - | 144 B | | BoseNelson_Comparable | .NET Core 3.1 | .NET Core 3.1 | 19 | 12000000 | 124.9 ms | 0.25 ms | 0.21 ms | - | - | - | - | | BoseNelson_Branchless | .NET Core 3.1 | .NET Core 3.1 | 19 | 12000000 | 196.0 ms | 0.10 ms | 0.08 ms | - | - | - | - | | Insertion_Comparable | .NET Core 3.1 | .NET Core 3.1 | 19 | 12000000 | 135.4 ms | 0.98 ms | 0.86 ms | - | - | - | - | | BoseNelson_Comparable | .NET Framework 4.8 | .NET Framework 4.8 | 19 | 12000000 | 133.6 ms | 0.52 ms | 0.49 ms | - | - | - | - | | BoseNelson_Branchless | .NET Framework 4.8 | .NET Framework 4.8 | 19 | 12000000 | 570.1 ms | 0.73 ms | 0.68 ms | - | - | - | - | | Insertion_Comparable | .NET Framework 4.8 | .NET Framework 4.8 | 19 | 12000000 | 176.5 ms | 0.30 ms | 0.25 ms | - | - | - | - | | BoseNelson_Comparable | CoreRT 6.0 | CoreRT 6.0 | 19 | 12000000 | NA | NA | NA | - | - | - | - | | BoseNelson_Branchless | CoreRT 6.0 | CoreRT 6.0 | 19 | 12000000 | NA | NA | NA | - | - | - | - | | Insertion_Comparable | CoreRT 6.0 | CoreRT 6.0 | 19 | 12000000 | NA | NA | NA | - | - | - | - | Benchmarks with issues: SN19Benchmark.BoseNelson_Comparable: CoreRT 6.0(Runtime=CoreRT 6.0, InvocationCount=1, UnrollFactor=1) [Length=19, Count=12000000] SN19Benchmark.BoseNelson_Branchless: CoreRT 6.0(Runtime=CoreRT 6.0, InvocationCount=1, UnrollFactor=1) [Length=19, Count=12000000] SN19Benchmark.Insertion_Comparable: CoreRT 6.0(Runtime=CoreRT 6.0, InvocationCount=1, UnrollFactor=1) [Length=19, Count=12000000]

98.432432

154

0.466502

yue_Hant

0.727463

b5ba444a78ca9e1d39f858a1a9e008f6d2a0bc8c

329

md

Markdown

plugins/README.md

AliHenry/gee-pos-admin

109544bcd30dfff5e0058ee95b1f133cbf1fb8f0

[ "MIT" ]

null

plugins/README.md

AliHenry/gee-pos-admin

109544bcd30dfff5e0058ee95b1f133cbf1fb8f0

[ "MIT" ]

null

plugins/README.md

AliHenry/gee-pos-admin

109544bcd30dfff5e0058ee95b1f133cbf1fb8f0

[ "MIT" ]

null

# PLUGINS This directory contains your Javascript plugins that you want to run before instantiating the root vue.js application. More information about the usage of this directory in the documentation: https://nuxtjs.org/guide/plugins **This directory is not required, you can delete it if you don't want to use it.**

36.555556

119

0.772036

eng_Latn

0.997935

b5baa1edbb1ee3a6d173d2b4ba39dd15cd5fa5bc

25,019

md

Markdown

articles/iot-dps/concepts-device-oem-security-practices.md

changeworld/azure-docs.pl-pl

f97283ce868106fdb5236557ef827e56b43d803e

[ "CC-BY-4.0", "MIT" ]

null

articles/iot-dps/concepts-device-oem-security-practices.md

changeworld/azure-docs.pl-pl

f97283ce868106fdb5236557ef827e56b43d803e

[ "CC-BY-4.0", "MIT" ]

null

articles/iot-dps/concepts-device-oem-security-practices.md

changeworld/azure-docs.pl-pl

f97283ce868106fdb5236557ef827e56b43d803e

[ "CC-BY-4.0", "MIT" ]

null

--- title: Praktyki dotyczące zabezpieczeń dla producentów — usługa inicjowania obsługi administracyjnej urządzeń Usługi Azure IoT description: Omówi typowe praktyki zabezpieczeń dla producentów OEM i urządzeń, którzy przygotowują urządzenia do zarejestrowania się w usłudze inicjowania obsługi administracyjnej urządzeń usługi Azure IoT (DPS). author: timlt ms.author: timlt ms.date: 3/02/2020 ms.topic: conceptual ms.service: iot-dps ms.custom: iot-p0-scenario, iot-devices-deviceOEM ms.reviewer: nberdy ms.openlocfilehash: 3854f353e4ea0b78c0162681e0b89d37419105d8 ms.sourcegitcommit: c5661c5cab5f6f13b19ce5203ac2159883b30c0e ms.translationtype: MT ms.contentlocale: pl-PL ms.lasthandoff: 04/01/2020 ms.locfileid: "80529522" --- # <a name="security-practices-for-azure-iot-device-manufacturers"></a>Praktyki dotyczące zabezpieczeń dla producentów urządzeń IoT platformy Azure Ponieważ coraz więcej producentów zwalnia urządzenia IoT, warto zidentyfikować wskazówki dotyczące typowych praktyk. W tym artykule podsumowano zalecane praktyki zabezpieczeń, które należy wziąć pod uwagę podczas wytwarzania urządzeń do użytku z usługą inicjowania obsługi administracyjnej urządzeń usługi Azure IoT (DPS). > [!div class="checklist"] > * Wybieranie opcji uwierzytelniania urządzenia > * Instalowanie certyfikatów na urządzeniach IoT > * Integracja modułu TPM (Trusted Platform Module) z procesem produkcyjnym ## <a name="selecting-device-authentication-options"></a>Wybieranie opcji uwierzytelniania urządzenia Ostatecznym celem każdego środka bezpieczeństwa urządzenia IoT jest stworzenie bezpiecznego rozwiązania IoT. Jednak problemy, takie jak ograniczenia sprzętowe, koszty i poziom wiedzy na temat zabezpieczeń, mają wpływ na opcje, które wybierzesz. Ponadto twoje podejście do zabezpieczeń wpływa na sposób, w jaki urządzenia IoT łączą się z chmurą. Chociaż istnieje [kilka elementów zabezpieczeń IoT](https://www.microsoft.com/research/publication/seven-properties-highly-secure-devices/) do rozważenia, kluczowym elementem, który napotka każdego klienta jest typ uwierzytelniania do użycia. Trzy powszechnie stosowane typy uwierzytelniania to certyfikaty X.509, moduły zaufanej platformy (TPM) i klucze symetryczne. Chociaż istnieją inne typy uwierzytelniania, większość klientów, którzy twórz rozwiązania na platformie Azure IoT używać jednego z tych trzech typów. Poniżej dalsza część artykułu Ankieta zalet i wad korzystania z każdego typu uwierzytelniania. ### <a name="x509-certificate"></a>Certyfikat X.509 Certyfikaty X.509 to rodzaj tożsamości cyfrowej, której można używać do uwierzytelniania. Standard certyfikatu X.509 jest udokumentowany w [IETF RFC 5280](https://tools.ietf.org/html/rfc5280). W usłudze Azure IoT istnieją dwa sposoby uwierzytelniania certyfikatów: - Odcisk palca. Algorytm odcisku palca jest uruchamiany na certyfikacie w celu wygenerowania ciągu szesnastkowego. Wygenerowany ciąg jest unikatowym identyfikatorem certyfikatu. - Uwierzytelnianie urzędu certyfikacji na podstawie pełnego łańcucha. Łańcuch certyfikatów to hierarchiczna lista wszystkich certyfikatów potrzebnych do uwierzytelnienia certyfikatu jednostki końcowej (EE). Aby uwierzytelnić certyfikat EE, konieczne jest uwierzytelnienie każdego certyfikatu w łańcuchu, w tym zaufanego głównego urzędu certyfikacji. Plusy dla X.509: - X.509 jest najbezpieczniejszym typem uwierzytelniania obsługiwanym w usłudze Azure IoT. - X.509 umożliwia wysoki poziom kontroli do celów zarządzania certyfikatami. - Wielu dostawców jest dostępnych do dostarczania rozwiązań uwierzytelniania opartych na architekturze X.509. Minusy dla X.509: - Wielu klientów może być konieczne poleganie na zewnętrznych dostawców dla swoich certyfikatów. - Zarządzanie certyfikatami może być kosztowne i zwiększa całkowity koszt rozwiązania. - Zarządzanie cyklem życia certyfikatów może być trudne, jeśli logistyka nie jest dobrze przemyślana. ### <a name="trusted-platform-module-tpm"></a>Moduł TPM Moduł TPM, znany również jako [ISO/IEC 11889,](https://www.iso.org/standard/66510.html)jest standardem do bezpiecznego generowania i przechowywania kluczy kryptograficznych. Moduł TPM odnosi się również do wirtualnego lub fizycznego urządzenia We/Wy, które współdziała z modułami implementuuuującym standard. Urządzenie TPM może istnieć jako oddzielny sprzęt, zintegrowany sprzęt, moduł oparty na oprogramowaniu układowym lub moduł oparty na oprogramowaniu. Istnieją dwie kluczowe różnice między TPM i kluczy symetrycznych: - Układy TPM mogą również przechowywać certyfikaty X.509. - Zaświadczanie tpm w dps używa klucza poręczenia modułu TPM (EK), forma uwierzytelniania asymetrycznego. W przypadku uwierzytelniania asymetrycznego klucz publiczny jest używany do szyfrowania, a oddzielny klucz prywatny jest używany do odszyfrowywania. Natomiast klucze symetryczne używają uwierzytelniania symetrycznego, gdzie klucz prywatny jest używany zarówno do szyfrowania, jak i odszyfrowywania. Plusy dla modułu TPM: - TPM są dołączone jako standardowy sprzęt na wielu urządzeniach z systemem Windows, z wbudowaną obsługą systemu operacyjnego. - Zaświadczanie modułu TPM jest łatwiejsze do zabezpieczenia niż poświadczenie klucza symetrycznego opartego na symetrii symetrycznego symetrycznego symetrycznego symetrycznego symetrycznego symetrycznego sygnatury dostępu współdzielonego (SYGNATURA WSPÓŁDZIELONA). - Można łatwo wygasnąć i odnowić lub przetoczyć poświadczenia urządzenia. Dps automatycznie rolkach poświadczeń Usługi IoT Hub, gdy urządzenie TPM jest ze względu na ponowne aprovisioning. Wady dla TPM: - TPM są złożone i mogą być trudne w użyciu. - Tworzenie aplikacji z TPM jest trudne, chyba że masz fizyczny moduł TPM lub emulator jakości. - Może być trzeba przeprojektować płytę urządzenia, aby uwzględnić moduł TPM w sprzęcie. - Jeśli rolki EK na moduł TPM, niszczy tożsamość modułu TPM i tworzy nowy. Chociaż układ fizyczny pozostaje taki sam, ma nową tożsamość w rozwiązaniu IoT. ### <a name="symmetric-key"></a>Klucz symetryczny W przypadku kluczy symetrycznych ten sam klucz jest używany do szyfrowania i odszyfrowywania wiadomości. W rezultacie ten sam klucz jest znany zarówno urządzeniu, jak i usłudze, która go uwierzytelnia. Usługa Azure IoT obsługuje połączenia kluczy symetrycznych oparte na tokenach Symetrycznego Symetrycznego Symetrycznego Symetrycznego Symetrycznego. Uwierzytelnianie za klucz symetryczny wymaga znacznej odpowiedzialności właściciela, aby zabezpieczyć klucze i osiągnąć równy poziom zabezpieczeń za pomocą uwierzytelniania X.509. Jeśli używasz kluczy symetrycznych, zalecaną praktyką jest ochrona kluczy przy użyciu sprzętowego modułu zabezpieczeń (HSM). Plusy dla klucza symetrycznego: - Korzystanie z kluczy symetrycznych jest najprostszym, najniższym kosztem sposobem rozpoczęcia pracy z uwierzytelnianiem. - Korzystanie z kluczy symetrycznych usprawnia proces, ponieważ nie ma nic dodatkowego do wygenerowania. Minusy dla klucza symetrycznego: - Klucze symetryczne podjąć znaczny wysiłek, aby zabezpieczyć klucze. Ten sam klucz jest współużytkowany przez urządzenie i chmurę, co oznacza, że klucz musi być chroniony w dwóch miejscach. Natomiast wyzwaniem z certyfikatami TPM i X.509 jest udowodnienie posiadania klucza publicznego bez ujawniania klucza prywatnego. - Klucze symetryczne ułatwiają przestrzeganie złych praktyk w zakresie zabezpieczeń. Powszechną tendencją w przypadku kluczy symetrycznych jest zakodowanie niezaszyfrowanych kluczy na urządzeniach. Chociaż praktyka ta jest wygodna, pozostawia klucze narażone. Możesz ograniczyć pewne ryzyko, bezpiecznie przechowując klucz symetryczny na urządzeniu. Jeśli jednak priorytetem jest ostatecznie bezpieczeństwo, a nie wygoda, użyj certyfikatów X.509 lub modułu TPM do uwierzytelniania. ### <a name="shared-symmetric-key"></a>Udostępniony klucz symetryczny Istnieje odmiana uwierzytelniania klucza symetrycznego, znana jako udostępniony klucz symetryczny. Takie podejście polega na użyciu tego samego klucza symetrycznego we wszystkich urządzeniach. Zaleca się unikanie używania udostępnionych kluczy symetrycznych na urządzeniach. Pro dla udostępnionego klucza symetrycznego: - Prosty do wdrożenia i niedrogi do produkcji na dużą skalę. Wady dla udostępnionego klucza symetrycznego: - Bardzo podatny na ataki. Ryzyko znacznie przeważa nad korzyściami płynącymi z łatwego wdrożenia. - Każdy może podszyć się pod Twoje urządzenia, jeśli uzyska klucz udostępniony. - Jeśli korzystasz z udostępnionego klucza symetrycznego, który zostanie naruszony, prawdopodobnie utracisz kontrolę nad urządzeniami. ### <a name="making-the-right-choice-for-your-devices"></a>Dokonywanie właściwego wyboru dla twoich urządzeń Aby wybrać metodę uwierzytelniania, upewnij się, że bierzesz pod uwagę zalety i koszty każdego podejścia dla unikatowego procesu produkcyjnego. W przypadku uwierzytelniania urządzeń zwykle istnieje odwrotna relacja między tym, jak bezpieczne jest dane podejście, a jego wygodą. ## <a name="installing-certificates-on-iot-devices"></a>Instalowanie certyfikatów na urządzeniach IoT Jeśli do uwierzytelniania urządzeń IoT używasz certyfikatów X.509, w tej sekcji znajdziesz wskazówki dotyczące integracji certyfikatów z procesem produkcyjnym. Musisz podjąć kilka decyzji. Obejmują one decyzje dotyczące typowych zmiennych certyfikatów, kiedy wygenerować certyfikaty i kiedy je zainstalować. Jeśli używasz haseł, możesz zapytać, dlaczego nie możesz używać tego samego certyfikatu na wszystkich urządzeniach, w taki sam sposób, w jaki możesz używać tego samego hasła na wszystkich urządzeniach. Po pierwsze, używanie tego samego hasła wszędzie jest niebezpieczne. Praktyka naraziła firmy na poważne ataki DDoS, w tym ten, który zdjął DNS na wschodnim wybrzeżu USA kilka lat temu. Nigdy nie używaj tego samego hasła wszędzie, nawet w przypadku kont osobistych. Po drugie, certyfikat nie jest hasłem, ale unikatową tożsamością. Hasło jest jak tajny kod, którego każdy może użyć do otwarcia drzwi w zabezpieczonym budynku. To coś, co wiesz, i można dać hasło każdemu, aby uzyskać wejście. Zaświadczenie jest jak prawo jazdy ze zdjęciem i innymi szczegółami, które możesz pokazać strażnikowi, aby dostać się do zabezpieczonego budynku. Jest związany z tym, kim jesteś. Pod warunkiem, że strażnik dokładnie dopasowuje ludzi z prawem jazdy, tylko ty możesz użyć swojego prawa jazdy (tożsamości), aby uzyskać wejście. ### <a name="variables-involved-in-certificate-decisions"></a>Zmienne związane z decyzjami o świadectwie Należy wziąć pod uwagę następujące zmienne i jak każdy z nich wpływa na cały proces produkcyjny. #### <a name="where-the-certificate-root-of-trust-comes-from"></a>W przypadku gdy katalog główny certyfikatu zaufania pochodzi z Zarządzanie infrastrukturą kluczy publicznych (PKI) może być kosztowne i skomplikowane. Zwłaszcza jeśli Twoja firma nie ma żadnego doświadczenia w zarządzaniu pki. Dostępne możliwości to: - Użyj infrastruktury kluczy publicznych innych firm. Certyfikaty podpisywania pośredniego można kupić od dostawcy certyfikatów innej firmy. Można też użyć prywatnego urzędu certyfikacji(CA). - Użyj zarządzanej przez siebie infrastruktury kluczy publicznych. Można utrzymywać własny system infrastruktury kluczy publicznych i generować własne certyfikaty. - Użyj usługi zabezpieczeń [usługi Azure Sphere.](https://azure.microsoft.com/services/azure-sphere/) Ta opcja dotyczy tylko urządzeń usługi Azure Sphere. #### <a name="where-certificates-are-stored"></a>W przypadku przechowywania certyfikatów Istnieje kilka czynników, które mają wpływ na decyzję o miejscu przechowywania certyfikatów. Czynniki te obejmują typ urządzenia, oczekiwane marże zysku (niezależnie od tego, czy możesz sobie pozwolić na bezpieczną pamięć masową), możliwości urządzenia i istniejącą technologię zabezpieczeń na urządzeniu, z którego można korzystać. Rozważmy następujące opcje: - W sprzętowym module zabezpieczeń (HSM). Zaleca się korzystanie z modułu HSM. Sprawdź, czy na płycie sterującej urządzenia jest już zainstalowany moduł HSM. Jeśli wiesz, że nie masz modułu HSM, skontaktuj się z producentem sprzętu, aby zidentyfikować moduł HSM spełniający Twoje potrzeby. - W bezpiecznym miejscu na dysku, takim jak zaufane środowisko wykonywania (TEE). - W lokalnym systemie plików lub magazynie certyfikatów. Na przykład magazyn certyfikatów systemu Windows. #### <a name="connectivity-at-the-factory"></a>Łączność w fabryce Łączność w fabryce określa, jak i kiedy otrzymasz certyfikaty do zainstalowania na urządzeniach. Opcje łączności są następujące: - Łączność. Łączność jest optymalna, usprawnia proces generowania certyfikatów lokalnie. - Brak łączności. W takim przypadku do generowania certyfikatów urządzeń lokalnie i w trybie offline używany jest podpisany certyfikat urzędu certyfikacji. - Brak łączności. W takim przypadku można uzyskać certyfikaty, które zostały wygenerowane z wyprzedzeniem. Możesz też użyć infrastruktury kluczy publicznych w trybie offline do lokalnego generowania certyfikatów. #### <a name="audit-requirement"></a>Wymóg audytu W zależności od typu wytwarzanych urządzeń może być wymagane przez przepisy, aby utworzyć ścieżkę inspekcji sposobu instalowania tożsamości urządzeń na urządzeniach. Inspekcja zwiększa koszty produkcji. Tak więc w większości przypadków, tylko zrobić to w razie potrzeby. Jeśli nie masz pewności, czy audyt jest wymagany, skontaktuj się z działem prawnym firmy. Opcje inspekcji to: - Nie jest to branża wrażliwa. Inspekcja nie jest wymagana. - Branża wrażliwa. Certyfikaty powinny być instalowane w bezpiecznym pomieszczeniu zgodnie z wymogami certyfikacji zgodności. Jeśli potrzebujesz bezpiecznego pomieszczenia do instalowania certyfikatów, prawdopodobnie wiesz już, w jaki sposób certyfikaty są instalowane na urządzeniach. I prawdopodobnie masz już system audytu. #### <a name="length-of-certificate-validity"></a>Długość ważności certyfikatu Podobnie jak prawo jazdy, certyfikaty mają datę wygaśnięcia, która jest ustawiona podczas ich tworzenia. Oto opcje dotyczące długości ważności certyfikatu: - Odnowienie nie jest wymagane. Takie podejście używa długiego okresu odnawiania, więc nigdy nie trzeba odnawiać certyfikatu w okresie istnienia urządzenia. Chociaż takie podejście jest wygodne, jest również ryzykowne. Możesz zmniejszyć ryzyko, używając bezpiecznego magazynu, takiego jak moduł HSM na urządzeniach. Jednak zalecaną praktyką jest unikanie używania certyfikatów długotrwałych. - Wymagane odnowienie. Musisz odnowić certyfikat w okresie istnienia urządzenia. Długość ważności certyfikatu zależy od kontekstu i będziesz potrzebować strategii odnawiania. Strategia powinna obejmować, gdzie otrzymujesz certyfikaty i jakiego typu funkcje over-the-air urządzenia muszą używać w procesie odnawiania. ### <a name="when-to-generate-certificates"></a>Kiedy wygenerować certyfikaty Możliwości łączności internetowej w fabryce będą miały wpływ na proces generowania certyfikatów. Istnieje kilka opcji, kiedy do generowania certyfikatów: - Wstępnie załadowane certyfikaty. Niektórzy dostawcy modułu HSM oferują usługę premium, w której dostawca modułu HSM instaluje certyfikaty dla odbiorcy. Po pierwsze, klienci dają dostawcy HSM dostęp do certyfikatu podpisywania. Następnie dostawca modułu HSM instaluje certyfikaty podpisane przez ten certyfikat podpisywania na każdym pliku HSM, który klient kupuje. Wszystko, co klient musi zrobić, to zainstalować moduł HSM na urządzeniu. Usługa ta zwiększa koszty, ale pomaga usprawnić proces produkcyjny. I rozwiązuje pytanie, kiedy zainstalować certyfikaty. - Certyfikaty generowane przez urządzenie. Jeśli urządzenia generują certyfikaty wewnętrznie, należy wyodrębnić publiczny certyfikat X.509 z urządzenia, aby zarejestrować go w dps. - Połączona fabryka. Jeśli fabryka ma łączność, można wygenerować certyfikaty urządzeń, gdy ich potrzebujesz. - Fabryka offline z własną pki. Jeśli fabryka nie ma łączności i używasz własnej infrastruktury kluczy publicznych z obsługą w trybie offline, możesz wygenerować certyfikaty, gdy są potrzebne. - Fabryka w trybie offline z pomocą infrastruktury kluczy publicznych innych firm. Jeśli fabryka nie ma łączności i używasz infrastruktury kluczy publicznych innych firm, należy wygenerować certyfikaty z wyprzedzeniem. I konieczne będzie wygenerowanie certyfikatów z lokalizacji, która ma łączność. ### <a name="when-to-install-certificates"></a>Kiedy zainstalować certyfikaty Po wygenerowaniu certyfikatów dla urządzeń IoT można je zainstalować w urządzeniach. Jeśli używasz wstępnie załadowanych certyfikatów z modułem HSM, proces ten jest uproszczony. Po zainstalowaniu modułu HSM w urządzeniu kod urządzenia może uzyskać do niego dostęp. Następnie wywołasz interfejsy API hsm, aby uzyskać dostęp do certyfikatu, który jest przechowywany w modułie HSM. Takie podejście jest najwygodniejsze dla procesu produkcyjnego. Jeśli nie używasz wstępnie załadowanego certyfikatu, należy zainstalować certyfikat jako część procesu produkcyjnego. Najprostszym rozwiązaniem jest zainstalowanie certyfikatu w modułie HSM w tym samym czasie, w tym co miga początkowy obraz oprogramowania układowego. Proces musi dodać krok, aby zainstalować obraz na każdym urządzeniu. Po tym kroku można uruchomić końcowe kontrole jakości i inne kroki, zanim zapakujesz i wyślesz urządzenie. Dostępne są narzędzia programowe, które umożliwiają uruchomienie procesu instalacji i ostateczne sprawdzenie jakości w jednym kroku. Można zmodyfikować te narzędzia, aby wygenerować certyfikat lub wyciągnąć certyfikat z wstępnie wygenerowanego magazynu certyfikatów. Następnie oprogramowanie może zainstalować certyfikat, w którym trzeba go zainstalować. Narzędzia programowe tego typu umożliwiają uruchamianie produkcji na dużą skalę. Po zainstalowaniu certyfikatów na urządzeniach następnym krokiem jest dowiedzenie się, jak zarejestrować urządzenia za pomocą [dps](about-iot-dps.md). ## <a name="integrating-a-tpm-into-the-manufacturing-process"></a>Integracja modułu TPM z procesem produkcyjnym Jeśli używasz modułu TPM do uwierzytelniania urządzeń IoT, ta sekcja zawiera wskazówki. Wskazówki obejmują powszechnie używane urządzenia TPM 2.0, które mają obsługę klucza kodu uwierzytelniania wiadomości opartego na skrótach (HMAC). Specyfikacja modułu TPM dla układów TPM jest standardem ISO utrzymywanym przez Trusted Computing Group. Więcej informacji na temat modułu TPM można znaleźć w specyfikacjach [modułów TPM 2.0](https://trustedcomputinggroup.org/tpm-library-specification/) i [ISO/IEC 11889](https://www.iso.org/standard/66510.html). ### <a name="taking-ownership-of-the-tpm"></a>Przejęcie na własność modułu TPM Kluczowym krokiem w produkcji urządzenia z chipem TPM jest przejęcie na własność modułu TPM. Ten krok jest wymagany, aby można było podać klucz do właściciela urządzenia. Pierwszym krokiem jest wyodrębnienie klucza poręczenia (EK) z urządzenia. Następnym krokiem jest rzeczywiście roszczenia własności. Sposób osiągnięcia tego celu zależy od tego, którego modułu TPM i systemu operacyjnego używasz. W razie potrzeby skontaktuj się z producentem modułu TPM lub deweloperem systemu operacyjnego urządzenia, aby ustalić, jak zgłosić prawo własności. W procesie produkcyjnym można wyodrębnić EK i ubiegać się o własność w różnym czasie, co zwiększa elastyczność. Wielu producentów korzysta z tej elastyczności, dodając sprzętowy moduł zabezpieczeń (HSM), aby zwiększyć bezpieczeństwo swoich urządzeń. W tej sekcji przedstawiono wskazówki dotyczące tego, kiedy wyodrębnić ek, kiedy do przejęcia własności modułu TPM i zagadnienia dotyczące integracji tych kroków w harmonogramie produkcji. > [!IMPORTANT] > W poniższych wskazówkach przyjęto założenie, że używany jest dyskretny, firmware lub zintegrowany moduł TPM. W miejscach, w których ma to zastosowanie, wskazówki dodają uwagi dotyczące korzystania z modułu TPM niedyskretnego lub programowego. Jeśli używasz modułu TPM oprogramowania, mogą istnieć dodatkowe kroki, których ta wskazówka nie zawiera. Programy TPM oprogramowania mają wiele implementacji, które wykraczają poza zakres tego artykułu. Ogólnie rzecz biorąc, możliwe jest zintegrowanie modułu TPM oprogramowania z następującą ogólną osią czasu produkcji. Jednak podczas gdy emulowane oprogramowanie moduł TPM nadaje się do prototypowania i testowania, nie może zapewnić takiego samego poziomu zabezpieczeń jak dyskretny, firmware lub zintegrowany moduł TPM. W praktyce należy unikać używania modułu TPM oprogramowania w produkcji. ### <a name="general-manufacturing-timeline"></a>Ogólny harmonogram produkcji Na poniższej osi czasu pokazano, jak moduł TPM przechodzi przez proces produkcyjny i kończy się w urządzeniu. Każdy proces produkcyjny jest unikatowy, a ta oś czasu pokazuje najczęstsze wzorce. Oś czasu zawiera wskazówki dotyczące tego, kiedy należy podjąć pewne działania za pomocą kluczy. #### <a name="step-1-tpm-is-manufactured"></a>Krok 1: TPM jest produkowany - Jeśli kupujesz tpm do użytku w urządzeniach, sprawdź, czy będą one wyodrębnić publiczne klucze poparcia (EK_pubs) dla Ciebie. Jest to przydatne, jeśli producent udostępnia listę EK_pubs z dostarczonymi urządzeniami. > [!NOTE] > Można udzielić producentowi modułu TPM dostępu do zapisu na liście rejestracji przy użyciu zasad dostępu współużytkującego w usłudze inicjowania obsługi administracyjnej. Takie podejście pozwala im dodać TPM do listy rejestracji dla Ciebie. Ale to jest na wczesnym etapie procesu produkcyjnego i wymaga zaufania do producenta modułu TPM. Zrób to na własne ryzyko. - Jeśli produkujesz TPM do sprzedaży producentom urządzeń, rozważ nadanie klientom listy EK_pubs wraz z ich fizycznymi tpmami. Zapewnienie klientom EK_pubs pozwala zaoszczędzić krok w ich procesie. - Jeśli produkujesz TPM do użycia z własnymi urządzeniami, określ, który punkt w procesie jest najwygodniejszy do wyodrębnienia EK_pub. EK_pub można wyodrębnić w dowolnym z pozostałych punktów na osi czasu. #### <a name="step-2-tpm-is-installed-into-a-device"></a>Krok 2: Moduł TPM jest zainstalowany w urządzeniu W tym momencie procesu produkcyjnego należy wiedzieć, które wystąpienie DPS urządzenie będzie używane z. W rezultacie można dodać urządzenia do listy rejestracji do automatycznego inicjowania obsługi administracyjnej. Aby uzyskać więcej informacji na temat automatycznego inicjowania obsługi administracyjnej urządzeń, zobacz [dokumentację DPS](about-iot-dps.md). - Jeśli nie wyodrębniłeś EK_pub, teraz jest dobry moment, aby to zrobić. - W zależności od procesu instalacji modułu TPM ten krok jest również dobry czas, aby przejąć na własność modułu TPM. #### <a name="step-3-device-has-firmware-and-software-installed"></a>Krok 3: Urządzenie ma zainstalowane oprogramowanie układowe i oprogramowanie W tym momencie procesu zainstaluj klienta DPS wraz z zakresem identyfikatora i globalnym adresem URL do inicjowania obsługi administracyjnej. - Teraz jest ostatnia szansa, aby wyodrębnić EK_pub. Jeśli osoba trzecia zainstaluje oprogramowanie na urządzeniu, warto najpierw wyodrębnić EK_pub. - Ten punkt w procesie produkcyjnym jest idealny do przejęcia na własność modułu TPM. > [!NOTE] > Jeśli używasz modułu TPM oprogramowania, możesz go teraz zainstalować. Wyodrębnić EK_pub w tym samym czasie. #### <a name="step-4-device-is-packaged-and-sent-to-the-warehouse"></a>Krok 4: Urządzenie jest pakowane i wysyłane do magazynu Urządzenie może siedzieć w magazynie przez 6-12 miesięcy przed wdrożeniem. #### <a name="step-5-device-is-installed-into-the-location"></a>Krok 5: Urządzenie jest zainstalowane w lokalizacji Po dotarciu urządzenia do ostatecznej lokalizacji, przechodzi przez automatyczne inicjowanie obsługi administracyjnej za pomocą dps. Aby uzyskać więcej informacji, zobacz [Pojęcia dotyczące automatycznej obsługi administracyjnej](concepts-auto-provisioning.md) i [zaświadczanie modułu TPM](concepts-tpm-attestation.md). ## <a name="resources"></a>Resources Oprócz zalecanych rozwiązań w zakresie zabezpieczeń w tym artykule usługa Azure IoT udostępnia zasoby ułatwiające wybieranie bezpiecznego sprzętu i tworzenie bezpiecznych wdrożeń IoT: - Zalecenia dotyczące [zabezpieczeń](../iot-fundamentals/security-recommendations.md) usługi Azure IoT, aby poprowadzić proces wdrażania. - [Usługa Azure Security Center](https://azure.microsoft.com/services/security-center/) oferuje usługę ułatwiające tworzenie bezpiecznych wdrożeń IoT. - Aby uzyskać pomoc dotyczącą oceny środowiska sprzętowego, zobacz oficjalny dokument [Oceniający zabezpieczenia IoT](https://download.microsoft.com/download/D/3/9/D3948E3C-D5DC-474E-B22F-81BA8ED7A446/Evaluating_Your_IOT_Security_whitepaper_EN_US.pdf). - Aby uzyskać pomoc dotyczącą wybierania bezpiecznego sprzętu, zobacz [Odpowiedni bezpieczny sprzęt do wdrożenia IoT](https://download.microsoft.com/download/C/0/5/C05276D6-E602-4BB1-98A4-C29C88E57566/The_right_secure_hardware_for_your_IoT_deployment_EN_US.pdf).

129.632124

1,021

0.82885

pol_Latn

0.999991

b5bad88c9939bceb8623299a16fea4f9347c250f

710

md

Markdown

files/en/getting_started_guide/install_splynx/install_splynx.md

RuntimeErrorovich/docs

bc6416abdd0c2a24cdd0810f7694d0e987f37a91

[ "MIT" ]

null

files/en/getting_started_guide/install_splynx/install_splynx.md

RuntimeErrorovich/docs

bc6416abdd0c2a24cdd0810f7694d0e987f37a91

[ "MIT" ]

null

files/en/getting_started_guide/install_splynx/install_splynx.md

RuntimeErrorovich/docs

bc6416abdd0c2a24cdd0810f7694d0e987f37a91

[ "MIT" ]

null

Install Splynx ISP Framework ============================ For the installation, please use a clear Debian or Ubuntu server. Log in as root: Ubuntu: `sudo su` Debian: `su` Insert Timezone configuration: `dpkg-reconfigure tzdata` Update CA certificates for HTTPS: `apt-get install ca-certificates` `update-ca-certificates` Install Splynx: `wget -qO- https://deb.splynx.com/setup | bash -` `apt-get install splynx` or update it: `apt-get update` `apt-get install splynx` If you make a mistake when you enter the license code, or the mysql root password you can use: `dpkg-reconfigure splynx` The installation procedure has been tested on: * Debian 7, 8 * Ubuntu 14.04, 15.04, 15.10, 16.04, 16.10

16.904762

94

0.711268

eng_Latn

0.674369

b5badf0d2f9c168c1ab39b4c632fb04dc7b66882

482

md

Markdown

content/post/2019-03-29-3d.md

Ishizuka427/hugo.suwa3.me

b39d419ab3a48edc95ad7c9652bb2ce6beef84b9

[ "Apache-2.0" ]

2

2020-12-08T02:07:04.000Z

2020-12-08T19:55:15.000Z

content/post/2019-03-29-3d.md

Ishizuka427/hugo.suwa3.me

b39d419ab3a48edc95ad7c9652bb2ce6beef84b9

[ "Apache-2.0" ]

4

2021-11-16T01:17:06.000Z

2021-11-27T08:42:53.000Z

content/post/2019-03-29-3d.md

Ishizuka427/hugo.suwa3.me

b39d419ab3a48edc95ad7c9652bb2ce6beef84b9

[ "Apache-2.0" ]

null

--- title: "3D" date: "2019-03-29T13:00:37.000Z" categories: - "%e6%9c%aa%e5%88%86%e9%a1%9e" tags: --- お昼にFabCafeへ行ったの。職場から近いので、ふらっと行けるの良いね。 https://fabcafe.com/tokyo/fab/ 3Dプリンターやレーザーカッターを使うことができるものづくりカフェ . ワークショップ行きたいなあ。とおもって、HPで調べたり店員さんに訊いてみたりしたよ。 3Dプリンターのclassも HPには反映されていないけれど、来月末にあるらしい。 . まずはレーザーカッターのclassだから Illustrator入れたいなあ。 . 楽しみが増えて嬉しい♡ . 夕方はTully's ![](/images/2019-03-29-18-11-246077441085310673548.jpg) がんばってロング・グッドバイ読み終わらせるぞ。 ٩(ˊᗜˋ\*)وえいおー

10.478261

56

0.740664

jpn_Jpan

0.42991

b5bb2fcf256335f61851fc02a1f4405431e5f8ca

49

md

Markdown

README.md

agosse/demod

953b6c9478e88f7ce12d2fe669228202106612d6

[ "MIT" ]

null

README.md

agosse/demod

953b6c9478e88f7ce12d2fe669228202106612d6

[ "MIT" ]

null

README.md

agosse/demod

953b6c9478e88f7ce12d2fe669228202106612d6

[ "MIT" ]

null

# demod Acoustic demodulator framework and tools

16.333333

40

0.836735

eng_Latn

0.962683

b5bdccac3af61ea7815da3362d99777b4d855ac8

134

md

Markdown

content/friends.en.md

aimerneige/Blog

943f2b09e44d1d047e97d45d034fdd619417aac5

[ "MIT" ]

null

content/friends.en.md

aimerneige/Blog

943f2b09e44d1d047e97d45d034fdd619417aac5

[ "MIT" ]

null

content/friends.en.md

aimerneige/Blog

943f2b09e44d1d047e97d45d034fdd619417aac5

[ "MIT" ]

1

2022-03-07T01:38:23.000Z

--- title: "Friends" url: "/en/friends" ShowToc: false --- {{< friends >}} > 感谢 https://guanqr.com/tech/website/add-blogroll/ 提供的代码

13.4

56

0.641791

yue_Hant

0.21881

b5bdd215d8df4c9437a1ed33025dffcdb5bdb875

303

md

Markdown

.github/ISSUE_TEMPLATE/Bug_report.md

aloy-nora/lnmp

52e33d6424d7fdf619a4717a9561f56a9a8e1751

[ "Apache-2.0" ]

512

2017-09-22T16:20:15.000Z

2022-03-31T05:24:21.000Z

.github/ISSUE_TEMPLATE/Bug_report.md

aloy-nora/lnmp

52e33d6424d7fdf619a4717a9561f56a9a8e1751

[ "Apache-2.0" ]

863

2017-09-12T00:52:03.000Z

2022-02-12T07:37:17.000Z

.github/ISSUE_TEMPLATE/Bug_report.md

aloy-nora/lnmp

52e33d6424d7fdf619a4717a9561f56a9a8e1751

[ "Apache-2.0" ]

127

2017-10-13T17:38:10.000Z

2022-03-19T04:55:46.000Z

--- name: Bug report about: Create a report to help us improve ---

9.774194

41

0.610561

yue_Hant

0.412519

b5be0f125276157991222395cb77e45bb3c24fc5

3,560

md

Markdown

README.md

AndresDFX/Template

14cfdd5856b4bdbe44a3adf25de3e059b40751ad

[ "RSA-MD" ]

1

2020-03-23T00:28:28.000Z

README.md

AndresDFX/Template

14cfdd5856b4bdbe44a3adf25de3e059b40751ad

[ "RSA-MD" ]

null

README.md

AndresDFX/Template

14cfdd5856b4bdbe44a3adf25de3e059b40751ad

[ "RSA-MD" ]

null

<div align="justify"> <u><h1>Plantilla de Documentación de Soporte </u></h1> --- <u><h2> Descripcion</u></h2> Esto es un archivo README. Debe contener la documentación de soporte uso de la herramienta digital. Las siguientes secciones son las secciones recomendadas que debes poner incluir en cualquier herramienta digital. Puedes descargar este archivo para que te sirva como plantilla. Asegúrate de empezar este archivo con una breve descripción sobre las funcionalidades y contexto de la herramienta digital. Sé conciso y al grano. --- <u><h2> Guía de usuario</u></h2> Explica los pasos básicos sobre cómo usar la herramienta digital. Es una buena sección para mostrar capturas de pantalla o gifs que ayuden a entender la herramienta digital. --- <u><h2> Guía de usuario</u></h2> Paso a paso de cómo instalar la herramienta digital. En esta sección es recomendable explicar la arquitectura de carpetas y módulos que componen el sistema. Según el tipo de herramienta digital, el nivel de complejidad puede variar. En algunas ocasiones puede ser necesario instalar componentes que tienen dependencia con la herramienta digital. Si este es el caso, añade también la siguiente sección. La guía de instalación debe contener de manera específica: - Los requisitos del sistema operativo para la compilación (versiones específicas de librerías, software de gestión de paquetes y dependencias, SDKs y compiladores, etc.). - Las dependencias propias del proyecto, tanto externas como internas (orden de compilación de sub-módulos, configuración de ubicación de librerías dinámicas, etc.). - Pasos específicos para la compilación del código fuente y ejecución de tests unitarios en caso de que el proyecto disponga de ellos. --- <u><h2> Dependencias</u></h2> Descripción de los recursos externos que generan una dependencia para la reutilización de la herramienta digital (librerías, frameworks, acceso a bases de datos y licencias de cada recurso). Es una buena práctica describir las últimas versiones en las que ha sido probada la herramienta digital. Puedes usar este estilo de letra diferenciar los comandos de instalación. --- <u><h2> Como contribuir</u></h2> [CONTRIBUTING](./CONTRIBUTING.md) Esta sección explica a desarrolladores cuáles son las maneras habituales de enviar una solicitud de adhesión de nuevo código (“pull requests”), cómo declarar fallos en la herramienta y qué guías de estilo se deben usar al escribir más líneas de código. También puedes hacer un listado de puntos que se pueden mejorar de tu código para crear ideas de mejora. --- <u><h2> Autores</u></h2> Nombra a el/los autor/es original/es. Consulta con ellos antes de publicar un email o un nombre personal. Una manera muy común es dirigirlos a sus cuentas de redes sociales. --- <u><h2> Informacion adicional</u></h2> Esta es la sección que permite agregar más información de contexto al proyecto como alguna web de relevancia, proyectos similares o que hayan usado la misma tecnología. --- <u><h2> Licencia</u></h2> [LICENCIA](./LICENSE.md) La licencia especifica los permisos y las condiciones de uso que el desarrollador otorga a otros desarrolladores que usen y/o modifiquen la herramienta digital. Incluye en esta sección una note con el tipo de licencia otorgado a esta herramienta digital. El texto de la licencia debe estar incluído en un archivo *LICENSE.md* o *LICENSE.txt* en la carpeta raíz. Si desconoces qué tipos de licencias existen y cuál es la mejor para cada caso, te recomendamos visitar la página https://choosealicense.com/. </div>

58.360656

391

0.785955

spa_Latn

0.996883

b5bf267b1589f04000a3e66e9536df3b305457b6

3,989

md

Markdown

README.md

EzraLopez/nearbychat

650c245d21ab6bd70d80cff1be3789a9cde98f3c

[ "MIT" ]

108

2018-05-05T01:09:01.000Z

2021-10-06T00:21:58.000Z

README.md

EzraLopez/nearbychat

650c245d21ab6bd70d80cff1be3789a9cde98f3c

[ "MIT" ]

7

2018-05-05T02:15:21.000Z

2021-03-17T23:54:43.000Z

README.md

EzraLopez/nearbychat

650c245d21ab6bd70d80cff1be3789a9cde98f3c

[ "MIT" ]

11

2018-05-06T02:08:22.000Z

2019-09-04T20:10:12.000Z

# Nearby Chat [![Build Status](https://travis-ci.com/EzraLopez/nearbychat.svg?branch=master)](https://travis-ci.com/EzraLopez/nearbychat) Experimental Android app demonstrating the use of [Nearby Messages API](https://developers.google.com/nearby/messages/overview) for communicating between devices within close proximity of each other (within about 100 feet). The devices don't have to be on the same network, but they do have to be connected to the Internet. <a href='https://lh3.googleusercontent.com/STKvfQlGMDOAj56sNvArmlEv1FjTGMwaeMjuC80NCUm1IBTRNQyqmpCAK_dtCrQgJEMwwqxqL3Tj_S2cfXfx4xGTba5vrL1tIfRstPOGocdwK95s1YGB2KUwp4yOwZmRIFSVKlCJRkmYCSpDU6TWWVnbAUfuKXgofaK4Z9oht1rbnPj44MHtDCgjXH2ao5PGQuN2r-GaAvPEHAd53g47T20s0xSafalllOSnSJb2sJ68sFXH-RvF-RxRJGRvWJnkZF1U2ftz6qyX0ZyxFK0Du6M67qf9XA1vSO4M3dDoae1a0MrRrQNKHLyPchuywyAqfE4CCoeUiFPPkaa8l1dTaLpQ5eIgG-VMgm4yVOrDhHp5M19vzxyZ3SbTnzg5sRR6rAc3tSaFwW7HbrODdKis6wi1j4cEGBTgPqGQ-3k98LlcFTpTVRebyMdocVmkegG-LzRfVnQI8dTkA56uRezUK_cjplmh2RYSeTulDsJzkFCFlQK-8JKMBN2hebb1Gj1pieyMu8Pv0Uie_Cn1vImkUTCo3YB4KQQ7vjfHhx8C3hUJdqNPy6D2fA7BA4pYM20-b98w35ZYCPVX2MXfzzlZq9NkfBElqxNCpBcPdGG5LScUMRLKqabNfoXB6rr5QNEPeUALajWoxc2ttp1d1XXt9a2tV5SYF8cyhA=w1139-h703-no'><img width='100%' height='100%' alt='Screenshot 1' src='https://lh3.googleusercontent.com/STKvfQlGMDOAj56sNvArmlEv1FjTGMwaeMjuC80NCUm1IBTRNQyqmpCAK_dtCrQgJEMwwqxqL3Tj_S2cfXfx4xGTba5vrL1tIfRstPOGocdwK95s1YGB2KUwp4yOwZmRIFSVKlCJRkmYCSpDU6TWWVnbAUfuKXgofaK4Z9oht1rbnPj44MHtDCgjXH2ao5PGQuN2r-GaAvPEHAd53g47T20s0xSafalllOSnSJb2sJ68sFXH-RvF-RxRJGRvWJnkZF1U2ftz6qyX0ZyxFK0Du6M67qf9XA1vSO4M3dDoae1a0MrRrQNKHLyPchuywyAqfE4CCoeUiFPPkaa8l1dTaLpQ5eIgG-VMgm4yVOrDhHp5M19vzxyZ3SbTnzg5sRR6rAc3tSaFwW7HbrODdKis6wi1j4cEGBTgPqGQ-3k98LlcFTpTVRebyMdocVmkegG-LzRfVnQI8dTkA56uRezUK_cjplmh2RYSeTulDsJzkFCFlQK-8JKMBN2hebb1Gj1pieyMu8Pv0Uie_Cn1vImkUTCo3YB4KQQ7vjfHhx8C3hUJdqNPy6D2fA7BA4pYM20-b98w35ZYCPVX2MXfzzlZq9NkfBElqxNCpBcPdGG5LScUMRLKqabNfoXB6rr5QNEPeUALajWoxc2ttp1d1XXt9a2tV5SYF8cyhA=w1139-h703-no'/></a> <p align="center"><a href='https://play.google.com/store/apps/details?id=com.esdraslopez.android.nearbychat&pcampaignid=github'><img width='250px' alt='Get it on Google Play' src='https://play.google.com/intl/en_us/badges/images/generic/en_badge_web_generic.png'/></a></p> * No need to sign up for anything * Usernames are optional * Only text-based chat is currently supported - URLs, emails, phone numbers, and addresses are clickable and will be opened with any installed app that supports them Nearby uses a combination of Bluetooth, Bluetooth Low Energy, Wi-Fi and near-ultrasonic audio to communicate between devices. Push notifications are not currently supported due to API limitations. You must have the app in the foreground to guarantee you will receive messages from devices around you. The app is not meant to be used for extended periods of time. Nearby's use of radios and sensors will consume battery at a higher rate than usual. (Battery consumption will decrease with earshot mode - not yet implemented, but you could help. Remember, it is a fully open source app 😀) ## Run Locally * Get an API Key. You may reuse an existing Android Key, but to create a new one follow the steps below: 1. Go to the [Google Developers Console](https://console.developers.google.com/flows/enableapi?apiid=copresence&keyType=CLIENT_SIDE_ANDROID&reusekey=true). 2. Create or select a project. 3. Name the API Key. E.g. ```nearbychat-debug``` 4. Optionally apply Application and API restrictions. I highly encourage you to do it. Use ```com.esdraslopez.android.nearbychat``` as the Application restriction and ```Nearby Messages API``` as the API restriction. 5. Click on create. * Place the key in your ```gradle.properties (Global Properties)``` file like this: ``` NearbyChat_NearbyMessagesAPIKeyDebug="YOUR_API_KEY" ``` ## Project Status Beta. Issues with [label "planned"](https://github.com/EzraLopez/nearbychat/labels/planned) are currently in development or will be soon.

117.323529

1,518

0.844071

eng_Latn

0.595371

b5c0bdc1fc772abeac4a7e98d95b272f944ea0ac

95

md

Markdown

content/osmand/navigation/public-transport-navigation.md

airon90/docs

a2e244d3dee2bb8e8ada940d816150f290cd18ec

[ "CC-BY-4.0", "MIT" ]

null

content/osmand/navigation/public-transport-navigation.md

airon90/docs

a2e244d3dee2bb8e8ada940d816150f290cd18ec

[ "CC-BY-4.0", "MIT" ]

null

content/osmand/navigation/public-transport-navigation.md

airon90/docs

a2e244d3dee2bb8e8ada940d816150f290cd18ec

[ "CC-BY-4.0", "MIT" ]

null

--- title: "Public Transport navigation" intro: "Public Transport navigation" versions: '*' ---

19

36

0.715789

yue_Hant

0.259799

b5c31f26490da95f04caff465f30a41933c7d29b

138

md

Markdown

README.md

afking/lisa

12e29703e6a1ab5d6e6104a84713469a079f9caf

[ "MIT" ]

null

README.md

afking/lisa

12e29703e6a1ab5d6e6104a84713469a079f9caf

[ "MIT" ]

null

README.md

afking/lisa

12e29703e6a1ab5d6e6104a84713469a079f9caf

[ "MIT" ]

null

# lisa Playing with Lisa/S ## GDB ``` sudo arm-none-eabi-gdb ./ap.elf target extended-remote /dev/ttyACM0 monitor swdp_scan attach 1 ```

12.545455

35

0.717391

eng_Latn

0.582083

b5c3f5f9bb33021cc7fafbd2b6fabef255cdf299

4,515

md

Markdown

_wiki/Bookmarks/tutorial.md

ruter/Ruter-Blog

ccdad70d71e026d3212518c4b1fb4dad80199a48

[ "MIT" ]

2

2020-04-29T03:56:25.000Z

2020-11-12T12:06:03.000Z

_wiki/Bookmarks/tutorial.md

ruter/Ruter-Blog

ccdad70d71e026d3212518c4b1fb4dad80199a48

[ "MIT" ]

null

_wiki/Bookmarks/tutorial.md

ruter/Ruter-Blog

ccdad70d71e026d3212518c4b1fb4dad80199a48

[ "MIT" ]

4

2018-01-09T09:58:31.000Z

2020-04-25T14:15:06.000Z

--- layout: wiki title: "Tutorial" date: 2016-11-09 00:33 updated: 2016-11-09 13:36 keywords: 教程, 文档 categories: Bookmarks --- # Docker + [Docker Tutorial Series](http://blog.flux7.com/blogs/docker/docker-tutorial-series-part-1-an-introduction) # Python + [Django 博客入门](https://www.gitbook.com/book/shenxgan/django/details) + [Django搭建简易博客教程](https://andrew-liu.gitbooks.io/django-blog/content/) + [Django Tutorial](http://daikeren.github.io/django_tutorial/) + [Django 使用 Paginator 实现分页功能](https://mozillazg.com/2013/01/django-pagination-by-use-paginator.html#.VWfexK2lyko) + [Flask之旅](https://spacewander.github.io/explore-flask-zh/index.html) + [使用 Flask 设计 RESTful APIs](http://www.pythondoc.com/flask-restful/index.html) + [Python 风格指南](http://zh-google-styleguide.readthedocs.io/en/latest/google-python-styleguide/contents/) + [Awesome Python ](http://awesome-python.com/) - A curated list of awesome Python frameworks, libraries, software and resources. + [pycrumbs](https://github.com/kirang89/pycrumbs) - Bits and bytes of Python from the Internet + [简明 Python 教程](http://old.sebug.net/paper/python/) + [Google's Python Class](https://developers.google.com/edu/python/) + [Virtualenv简明教程](http://www.jianshu.com/p/08c657bd34f1) + [Python爬虫学习系列教程](http://cuiqingcai.com/1052.html) + [Requests: 让 HTTP 服务人类](http://docs.python-requests.org/zh_CN/latest/index.html) + [Stackoverflow about Python](https://taizilongxu.gitbooks.io/stackoverflow-about-python/content/) # iOS + [AppCoda Community](http://www.appcoda.com/) - Learn iOS Programming and Build iPhone App + [HACKING WITH SWIFT](https://www.hackingwithswift.com/) + [禅与 Objective-C 编程艺术](http://wiki.jikexueyuan.com/project/objc-zen-book/) + [iOS开发UI基础—手写控件](http://www.cnblogs.com/wendingding/p/3742073.html) + [iOS开发多线程篇—GCD介绍](http://www.cnblogs.com/wendingding/p/3806821.html) + [CocoaPods详解之----使用篇](http://blog.csdn.net/wzzvictory/article/details/18737437) + [Cocoa Dev Central: Learn Objective-C](http://cocoadevcentral.com/d/learn_objectivec/) + [SwiftGG](http://swift.gg/) - 高质量的 Swift 译文网站 + [Swifter](http://swifter.tips/) - 每周三更新，向您介绍 SWIFT 的必备 TIP + [iOS抓包利器Charles](http://wonderffee.github.io/blog/2013/07/13/best-packet-capture-tool-charles-in-ios/) + [三种经典iPhone上网络抓包方法详解](http://blog.tingyun.com/web/article/detail/261) # Lua + [The.Lua.Tutorial](http://luatut.com/) # Unity3D + [Unity获取游戏对象详解](http://www.xuanyusong.com/archives/2768) # Web + [W3Schools Online Web Tutorials](http://www.w3schools.com/) - THE WORLD'S LARGEST WEB DEVELOPER SITE + [HTML&CSS编码规范](http://codeguide.bootcss.com/) - 编写灵活、稳定、高质量的 HTML 和 CSS 代码的规范。 # 编辑器与IDE + [A vim Tutorial and Primer](https://danielmiessler.com/study/vim/) + [Vim入门基础](http://www.jianshu.com/p/bcbe916f97e1) + [简明 Vim 练级攻略](http://developer.51cto.com/art/201306/398243.htm) # 算法 + [白话经典算法系列](http://blog.csdn.net/MoreWindows/article/category/859207) + [演算法筆記](http://www.csie.ntnu.edu.tw/~u91029/index.html) + [十大基础实用算法及其讲解](http://blog.jobbole.com/71648/) - 配GIF图演示 # 数据库 + [Redis实战](http://redisinaction.com/index.html) + [画图解释 SQL join 语句](http://blog.jobbole.com/40443/) + [十步完全理解 SQL](http://blog.jobbole.com/55086/) # 其他 + [傅里叶分析之掐死教程（完整版）](https://zhuanlan.zhihu.com/p/19763358?columnSlug=wille) + [正则表达式30分钟入门教程](http://deerchao.net/tutorials/regex/regex.htm) + [Pro Git book](https://git-scm.com/book/zh/v2) + [Git教程 - 廖雪峰](http://www.liaoxuefeng.com/wiki/0013739516305929606dd18361248578c67b8067c8c017b000) + [RESTful API 设计指南](http://www.ruanyifeng.com/blog/2014/05/restful_api.html) + [Learn X in Y minutes](https://learnxinyminutes.com/) + [Programming-Alpha-To-Omega](https://github.com/justjavac/Programming-Alpha-To-Omega) - 从零开始学编程系列汇总(从Α到Ω) + [tutorialspoint](http://www.tutorialspoint.com/index.htm) - Tutorials for Tex Commands, Agile Testing, Apache Tajo, C++ Library, MariaDB, SAP QM, SAP SOLMAN, SAP SCM, MS Access, KoaJS, OAuth2.0, Scrapy, SAP CCA, SAP PM, SAPUI5, Cognos, Internet of Things, Rural Marketing, Trampolining, Golf, CakePHP, SAP EWM, Web Dynpro, Angular2, Framework7, Arduino, CherryPy, Firebase,SAP C4C, SAP Dashboard, SAP PI, ExpressJS, Design Thinking, Internet Security, PyGTK, Apache Drill, Excel Charts, Elastic Search, Computer Security, Extreme Programming, Behavior Driven Development, Conversion Rate Optimization, SAP Basis, Business Law, Kanban, Erlang, SAP Payroll, ASP.Net WP, PouchDB, MFC, SAP HR, Yii, Clojure, Aurelia, CoffeeScript, CPanel, Laravel, SAP Webi, MS SQL Server, pinterest, Indian Polity, Teradata, Windows10

59.407895

816

0.749945

yue_Hant

0.707714

b5c5b1e5907ff0eaf1411fd3689505fac6e2b8bd

493

md

Markdown

mongodb/sharding/README.md

ziru/docker-apps

ab13253e849c2aec0cea5074909a60cf30a3f189

[ "Apache-2.0" ]

null

mongodb/sharding/README.md

ziru/docker-apps

ab13253e849c2aec0cea5074909a60cf30a3f189

[ "Apache-2.0" ]

null

mongodb/sharding/README.md

ziru/docker-apps

ab13253e849c2aec0cea5074909a60cf30a3f189

[ "Apache-2.0" ]

null

Step 1: Start config servers - connect to one config server - run commands in `start-config-svr.js` Step 2: Start shard servers - connect to one server in shard 1, and run commands in `start-s1.js` - connect to one server in shard 2, and run commands in `start-s2.js` Step 3: Add shards to config servers - connect to mongos - run commands in `add-shards.js` Step 4: Test sharded cluster - connect to mongos - run commands in `enable-ranged-sharding.js`, or `enable-hashed-sharding.js`

24.65

77

0.740365

eng_Latn

0.995107

b5c5cfa29b0b1497d15dcc1638ad1568443d138b

64

md

Markdown

README.md

felixklauke/actuarius

7bbf74a10924a2a7e993e82fe300aa358cbf92db

[ "MIT" ]

3

2017-10-19T17:41:32.000Z

2020-05-24T08:32:25.000Z

README.md

FelixKlauke/actuarius

7bbf74a10924a2a7e993e82fe300aa358cbf92db

[ "MIT" ]

21

2019-12-12T06:15:39.000Z

2021-06-25T15:28:37.000Z

README.md

felixklauke/actuarius

7bbf74a10924a2a7e993e82fe300aa358cbf92db

[ "MIT" ]

null

# Actuarius A simple and lightweight DNS Server implementation.

21.333333

51

0.828125

eng_Latn

0.868437

b5c683cbd1781fc74ce066a00ea3a75f2afb0e40

117

md

Markdown

fastsim-2021a/fastsim/tests/README.md

DIRECTLab/EVPRE

320e59a6b027a19b725a2a5e9cb2c366ba84a8da

[ "MIT" ]

null

fastsim-2021a/fastsim/tests/README.md

DIRECTLab/EVPRE

320e59a6b027a19b725a2a5e9cb2c366ba84a8da

[ "MIT" ]

2

2021-08-18T02:01:34.000Z

2021-09-13T17:41:53.000Z

fastsim-2021a/fastsim/tests/README.md

DIRECTLab/EVPRE

320e59a6b027a19b725a2a5e9cb2c366ba84a8da

[ "MIT" ]

1

2021-08-11T17:29:47.000Z

This directory contains informal test scripts. In the future, it will likely conform to python's unittest package.

117

0.803419

eng_Latn

0.999079

b5c6c76e6a8420e9786b0b76aa85c4f99bdcf786

2,378

md

Markdown

sample_page.md

NixonGenoA/NixonGenoA.github.io

5bf9be396e0e17e4590c3bdcf22e7794d439cfa1

[ "Unlicense" ]

null

sample_page.md

NixonGenoA/NixonGenoA.github.io

5bf9be396e0e17e4590c3bdcf22e7794d439cfa1

[ "Unlicense" ]

null

sample_page.md

NixonGenoA/NixonGenoA.github.io

5bf9be396e0e17e4590c3bdcf22e7794d439cfa1

[ "Unlicense" ]

null

24.265306

470

0.731707

eng_Latn

0.271993

b5c71a6171151f739261ec15d44758e9dc47654f

12,257

md

Markdown

docs/Bestiary/b/beetle.md

petersgiles/savage-tales-of-adventure

2196083c62f52cc782ad19d632c14c30e9b78f1b

[ "MIT" ]

null

docs/Bestiary/b/beetle.md

petersgiles/savage-tales-of-adventure

2196083c62f52cc782ad19d632c14c30e9b78f1b

[ "MIT" ]

2

2021-05-11T13:23:13.000Z

2021-06-28T19:56:48.000Z

docs/Bestiary/b/beetle.md

petersgiles/savage-tales-of-adventure

2196083c62f52cc782ad19d632c14c30e9b78f1b

[ "MIT" ]

null

# Beetle No description for this creature yet. **Attributes:** Agility d8, Smarts d4, Spirit d6, Strength d12+3, Vigor d12 **Skills:** Fighting d8, Climbing d10, Notice d4 **Charisma:** -; **Pace:** 7; **Parry:** 6; **Toughness:** 18 (3) **Edges:** Level Headed **Special Abilities** - **Armour +3:** Carapace. - **Bite:** Str+d10; Grab. - **Darkvision:** No vision penalties for darkness (range 12"). - **Blindsense:** Can sense and approximately pinpoint things within 12", attacks using blindsense are made at -2. - **Grab:** Pin your opponent if you hit with a raise, they require a raise on an opposed Strength roll to escape. - **Flight:** Flying Pace of 5" and Climb -2. - **Burrow:** Can burrow and reappear within 5". - **Size +7:** Increases Toughness by +7. - **Large:** -2 to attack medium-sized foes, they receive +2 to their attacks. **Giant blister beetle** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d6, Vigor d8 **Skills:** Fighting d4, Stealth d6 **Charisma:** -; **Pace:** 6; **Parry:** 4; **Toughness:** 7 (2) **Special Abilities** - **Armour +2:** Green carapace. - **Bite:** Str+d4. - **Darkvision:** No vision penalties for darkness (range 12"). - **Tremorsense:** Can sense and accurately pinpoint anything within 12" that's in contact with the ground. - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Immunities:** Poison and mind-affecting effects. - **Size -1:** Reduces Toughness by -1. **Giant bombardier beetle** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d10, Vigor d8 **Skills:** Fighting d6 **Charisma:** -; **Pace:** 6; **Parry:** 5; **Toughness:** 8 (2) **Special Abilities** - **Armour +2:** Natural armour. - **Bite:** Str+d4. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Breath Weapon:** All targets within a Cone Template must make an Agility roll at -2 or suffer 2d6 acid damage. - **Immunity:** Mind-affecting effects. **Giant boring beetle** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d12, Vigor d10 **Skills:** Fighting d6 **Charisma:** -; **Pace:** 5; **Parry:** 5; **Toughness:** 11 (2) **Special Abilities** - **Armour +2:** Greenish-gray carapace. - **Bite:** Str+d6. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Immunity:** Mind-affecting effects. - **Size +2:** Nine feet long; Toughness +2. **Carrion beetle** No description for this creature yet. **Attributes:** Agility d8, Smarts d4 (M), Spirit d8, Strength d12+1, Vigor d12 **Skills:** Fighting d6, Climbing d10, Notice d6 **Charisma:** -; **Pace:** 6; **Parry:** 5; **Toughness:** 12 (2) **Special Abilities** - **Armour +2:** Natural armour. - **Bite:** Str+d6. - **Claws:** Str+d6. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Burrow:** Can burrow and reappear within 5". - **Wall Walker:** Can automatically move across vertical or inverted surfaces with Pace 4". - **Breath Weapon:** All targets within a Cone Template must make an Agility roll at -2 or suffer 2d8 acid damage. - **Immunity:** Paralysis. - **Size +2:** Increases Toughness by +2. **Giant death watch beetle** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d12+2, Vigor d10 **Skills:** Fighting d6 **Charisma:** -; **Pace:** 6; **Parry:** 5; **Toughness:** 9 (2) **Special Abilities** - **Armour +2:** Green carapace. - **Bite:** Str+d4. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Immunities:** Mind-affecting effects and death magic. **Beetle, fire** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d6, Vigor d6 **Skills:** Fighting d4-2 **Charisma:** -; **Pace:** 6; **Parry:** 2; **Toughness:** 4 **Special Abilities** - **Bite:** Str+d4. - **Low Light Vision:** No penalties for dim or dark lighting. - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Flight:** Flying Pace of 6" and Climb -1. - **Immunity:** Mind-affecting effects. - **Size -1:** Reduces Toughness by -1. **Beetle, flash** No description for this creature yet. **Attributes:** Agility d10, Smarts d4 (M), Spirit d8, Strength d8, Vigor d10 **Skills:** Fighting d4 **Charisma:** -; **Pace:** 6; **Parry:** 4; **Toughness:** 7 (1) **Special Abilities** - **Armour +1:** Natural armour. - **Bite:** Str+d4. - **Low Light Vision:** No penalties for dim or dark lighting. - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Flight:** Flying Pace of 6" and Climb -1. - **Immunity:** Mind-affecting effects. - **Size -1:** Reduces Toughness by -1. **Goliath stag beetle** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d12+4, Vigor d12+2 **Skills:** Fighting d8 **Charisma:** -; **Pace:** 6; **Parry:** 6; **Toughness:** 20 (3) **Special Abilities** - **Armour +3:** Natural armour. - **Bite:** Str+d8. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Flight:** Flying Pace of 6" and Climb -1. - **Immunity:** Mind-affecting effects. - **Size +8:** Twenty-five feet long; Toughness +8. - **Huge:** -4 to attack medium-sized foes, they receive +4 to their attacks. **Giant mining beetle** No description for this creature yet. **Attributes:** Agility d10, Smarts d4 (M), Spirit d8, Strength d8, Vigor d10 **Skills:** Fighting d4 **Charisma:** -; **Pace:** 6; **Parry:** 4; **Toughness:** 7 (1) **Special Abilities** - **Armour +1:** Carapace. - **Bite:** Str+d4. - **Low Light Vision:** No penalties for dim or dark lighting. - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Flight:** Flying Pace of 6" and Climb -1. - **Burrow:** Can burrow and reappear within 5". - **Immunity:** Mind-affecting effects. - **Size -1:** Reduces Toughness by -1. **Requiem beetle** No description for this creature yet. **Attributes:** Agility d8, Smarts d4 (M), Spirit d6, Strength d12+5, Vigor d12+2 **Skills:** Fighting d12+2, Notice d8 **Charisma:** -; **Pace:** 8; **Parry:** 9; **Toughness:** 24 (5) **Edges:** Frenzy, Sweep **Special Abilities** - **Armour +5:** Red carapace. - **Claws:** Str+d8; Constrict. - **Bite:** Str+d8. - **Darkvision:** No vision penalties for darkness (range 12"). - **Tremorsense:** Can sense and accurately pinpoint anything within 20" that's in contact with the ground. - **Constrict:** Pin opponent on a raise, inflict Str+d6 per round after that, they require a raise on an opposed Strength roll to escape. - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Immunities:** Acid and mind-affecting effects. - **Size +10:** Forty feet long; Toughness +10. - **Huge:** -4 to attack medium-sized foes, they receive +4 to their attacks. **Giant rhinoceros beetle** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d12+2, Vigor d12 **Skills:** Fighting d8 **Charisma:** -; **Pace:** 5; **Parry:** 6; **Toughness:** 14 (3) **Special Abilities** - **Armour +3:** Grayish-brown carapace. - **Horns:** Str+d6. - **Bite:** Str+d6. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Gore:** +4 damage when first moving adjacent to foe. - **Size +3:** Twelve feet long; Toughness +3. **Giant saw-toothed beetle** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d10, Vigor d8 **Skills:** Fighting d6 **Charisma:** -; **Pace:** 6; **Parry:** 5; **Toughness:** 8 (2) **Special Abilities** - **Armour +2:** Carapace. - **Bite:** Str+d4; Grab. - **Darkvision:** No vision penalties for darkness (range 12"). - **Scent:** Can navigate, track and detect creatures by scent (range 6", halved for upwind and doubled for downwind, doubled again for very strong scents). Only adjacent creatures can be pinpointed accurately. - **Grab:** Pin your opponent if you hit with a raise, they require a raise on an opposed Strength roll to escape. - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Immunity:** Mind-affecting effects. **Scarab beetle** No description for this creature yet. **Attributes:** Agility d8, Smarts d4 (M), Spirit d6, Strength d12+2, Vigor d10 **Skills:** Fighting d6, Climbing d12 **Charisma:** -; **Pace:** 7; **Parry:** 5; **Toughness:** 13 (3) **Special Abilities** - **Armour +3:** Natural armour. - **Bite:** Str+d6; Gnaw. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Flight:** Flying Pace of 5" and Climb 0. - **Wall Walker:** Can automatically move across vertical or inverted surfaces with Pace 5". - **Immunities:** Disease, paralysis, mind-affecting effects and death magic. - **Size +3:** Increases Toughness by +3. **Slicer beetle** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d12+2, Vigor d10 **Skills:** Fighting d6 **Charisma:** -; **Pace:** 7; **Parry:** 5; **Toughness:** 12 (2) **Special Abilities** - **Armour +2:** Natural armour. - **Bite:** Str+d6. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Flight:** Flying Pace of 5" and Climb -1. - **Immunity:** Mind-affecting effects. - **Size +3:** Ten feet long; Toughness +3. **Beetle, giant stag** No description for this creature yet. **Attributes:** Agility d6, Smarts d4 (M), Spirit d6, Strength d12+1, Vigor d10 **Skills:** Fighting d6 **Charisma:** -; **Pace:** 5; **Parry:** 5; **Toughness:** 11 (2) **Special Abilities** - **Armour +2:** Natural armour. - **Bite:** Str+d6. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Flight:** Flying Pace of 5" and Climb -1. - **Immunity:** Mind-affecting effects. - **Size +2:** Ten feet long; Toughness +2. **Stalk beetle** No description for this creature yet. **Attributes:** Agility d8, Smarts d4 (M), Spirit d6, Strength d12, Vigor d8 **Skills:** Fighting d6, Climbing d10 **Charisma:** -; **Pace:** 6; **Parry:** 5; **Toughness:** 8 (2) **Special Abilities** - **Armour +2:** Natural armour. - **Bite:** Str+d4. - **Darkvision:** No vision penalties for darkness (range 12"). - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Burrow:** Can burrow and reappear within 4". - **Wall Walker:** Can automatically move across vertical or inverted surfaces with Pace 5". - **Immunity:** Mind-affecting effects. **Giant water beetle** No description for this creature yet. **Attributes:** Agility d8, Smarts d4 (M), Spirit d6, Strength d10, Vigor d10 **Skills:** Fighting d6, Stealth d4, Swimming d10 **Charisma:** -; **Pace:** 4; **Parry:** 5; **Toughness:** 9 (2) **Special Abilities** - **Armour +2:** Carapace. - **Bite:** Str+d4. - **Darkvision:** No vision penalties for darkness (range 12"). - **Watersense:** Can sense and accurately pinpoint anything within 12" that's in contact with the water. - **Mindless:** Immune to mind-affecting magic. - **Fearless:** Immune to fear and Intimidation. - **Aquatic:** Swimming Pace of 10", and cannot drown. - **Immunity:** Mind-affecting effects. - **Weakness:** Water dependency.

36.697605

72

0.671779

eng_Latn

0.765311

b5c75d6b36241c9e7ba809c9e486d15d2746cf82

5,938

md

Markdown

_end-user/r-scripts/run-prebuilt-r-scripts.md

mark-plummer/master-branch-test

0236a3e8b1e3701dda497cedde6ccaa2712ebc16

[ "MIT", "BSD-3-Clause" ]

null

_end-user/r-scripts/run-prebuilt-r-scripts.md

mark-plummer/master-branch-test

0236a3e8b1e3701dda497cedde6ccaa2712ebc16

[ "MIT", "BSD-3-Clause" ]

1

2022-02-26T07:03:33.000Z

_end-user/r-scripts/run-prebuilt-r-scripts.md

mark-plummer/master-branch-test

0236a3e8b1e3701dda497cedde6ccaa2712ebc16

[ "MIT", "BSD-3-Clause" ]

null

--- title: [Run prebuilt R scripts on answers] summary: "Anyone with R privileges can run an R analysis ThoughtSpot using provided scripts, you don't need to be an expert. " last_updated: tbd sidebar: mydoc_sidebar permalink: /:collection/:path.html --- If you have R privileges on your ThoughtSpot instance, you can run R analyses on search results, and save and share the resulting visualization with others. The users you share visualizations with do not need R privileges. ## Run an R analysis 1. Click the **R** icon ![R icon]({{ site.baseurl }}/images/r-icon-inline.png){: .inline} on the toolbar for any search result (answer). ![]({{ site.baseurl }}/images/r-icon-marketspot.png) From here, you have options to write a custom script, or load a pre-built or ThoughtSpot provided script. 2. In the Analyze dialog, click the ellipses icon ![more options menu icon]({{ site.baseurl }}/images/icon-ellipses.png){: .inline} next to the **Custom R Script** panel, and choose **Load**. ![]({{ site.baseurl }}/images/r-load-prebuilt.png) This brings up a list of pre-built scripts, both provided by ThoughtSpot and any created by programmers on your team. ![]({{ site.baseurl }}/images/r-load-list-of-scripts.png) 4. Select a script, then choose the columns you want to include in the analysis and the output file type (PNG or CSV). Note that the output file type must match the script. For example, if you select one of the ThoughtSpot provided time series scripts, the comment at the top of the script provides guidance on what columns to select. ``` # NOTE: Only two columns are needed for this analysis. # The first column should represent some date column # and the second should be some numeric measure column. ``` Also, scroll through the script to identify whether it's coded to produce graphical (PNG) or tabular (CSV) output. The time series scripts are both set up to produce graphical output, as indicated by a line like this at the end of the scripts. ``` png(#output_file#, width=1000); print(img); ``` 5. Select **Run Analysis** to execute the script. ## Time Series Outlier Example In this example, we ran an analysis for **Time Series Outlier Detection** on search results that show sales totals by date. ![]({{ site.baseurl }}/images/r-run-time-series-outliers-script.png) Note that we included a date column and a measure, and selected PNG as the output to match what the script requires. The original search could have had more columns than this, but you can always structure the analysis properly by selecting only the date column and measure column you want to focus on. In this case, no outliers were found, so the R visualization matches the original search result line graph. ## Time Series Forecast Example In this example, we ran a **Time Series Forecast** on the same search result. ![]({{ site.baseurl }}/images/r-run-time-forecast-script.png) ## Diverging Bars Example Here is an example of taking a script found online and repurposing it for a use case in ThoughtSpot. Antony Chen demo'ed this in a SpotOn webinar. You can find his full presentation on Custom R Scripts and demo at [SpotOn Learning: ThoughtSpot 5.0 BI and Data Science Features](https://community.thoughtspot.com/t/m2dftj) in the Community. Consider this script, found on this website of [Top 50 ggplot2 Visualizations - The Master List (With Full R Code)](http://r-statistics.co/Top50-Ggplot2-Visualizations-MasterList-R-Code.html). A direct link to this script is [here](http://r-statistics.co/Top50-Ggplot2-Visualizations-MasterList-R-Code.html#Diverging%20Bars). ``` library(ggplot2) theme_set(theme_bw()) # Data Prep data("mtcars") # load data mtcars$`car name` <- rownames(mtcars) # create new column for car names mtcars$mpg_z <- round((mtcars$mpg - mean(mtcars$mpg))/sd(mtcars$mpg), 2) # compute normalized mpg mtcars$mpg_type <- ifelse(mtcars$mpg_z < 0, "below", "above") # above / below avg flag mtcars <- mtcars[order(mtcars$mpg_z), ] # sort mtcars$`car name` <- factor(mtcars$`car name`, levels = mtcars$`car name`) # convert to factor to retain sorted order in plot. # Diverging Barcharts ggplot(mtcars, aes(x=`car name`, y=mpg_z, label=mpg_z)) + geom_bar(stat='identity', aes(fill=mpg_type), width=.5) + scale_fill_manual(name="Mileage", labels = c("Above Average", "Below Average"), values = c("above"="#00ba38", "below"="#f8766d")) + labs(subtitle="Normalised mileage from 'mtcars'", title= "Diverging Bars") + coord_flip() ``` You can modify the script above to support the phone sales use case discussed in the webinar. In this script, `mtcars` is replaced with references to our phone sales (`df$Sales`) and `car name` is replaced with `Device Name` both from the column data in the search example used in the webinar demo. The script uses the ThoughtSpot _data frame_ object (`df`), and adds two lines at the end to specify output type as a `png` image. ``` library(ggplot2) theme_set(theme_bw()) # Data Prep df$sales_z <- round((df$Sales - mean(df$Sales))/sd(df$Sales), 2) # compute normalized mpg df$sales_type <- ifelse(df$sales_z < 0, "below", "above") # above / below avg flag df <- df[order(df$sales_z), ] # sort df$`Device Name` <- factor(df$`Device Name`, levels = df$`Device Name`) # convert to factor to retain sorted order in plot. # Diverging Barcharts img <- ggplot(df, aes(x=`Device Name`, y=sales_z, label=sales_z)) + geom_bar(stat='identity', aes(fill=sales_type), width=.5) + scale_fill_manual(name="Sales", labels = c("Above Average", "Below Average"), values = c("above"="#00ba38", "below"="#f8766d")) + labs(subtitle="Normalised Sales for Phones", title= "Diverging Bars") + coord_flip() png(#output_file#, width=1000, height=1000) print(img) ```

41.816901

325

0.714045

eng_Latn

0.97551

b5c7d0f2c3b420020b663663305f16250d368db9

34

md

Markdown

posts/hello-world.md

Alexphanor/www

374029d7b4939b34d11559a963613307ba8c0068

[ "Apache-2.0" ]

null

posts/hello-world.md

Alexphanor/www

374029d7b4939b34d11559a963613307ba8c0068

[ "Apache-2.0" ]

null

posts/hello-world.md

Alexphanor/www

374029d7b4939b34d11559a963613307ba8c0068

[ "Apache-2.0" ]

null

## hello world this is great! :D

8.5

17

0.647059

eng_Latn

0.999583

b5c7d7b55fdb561fbfd4fc758451fdf581db2ff6

79

md

Markdown

dataset/original/colon/README.md

ExaNLP/sket

5ebe516f4454da246301532c353af57c1660ec69

[ "MIT" ]

4

2021-07-30T16:06:35.000Z

2022-01-07T09:44:11.000Z

dataset/original/colon/README.md

ExaNLP/sket

5ebe516f4454da246301532c353af57c1660ec69

[ "MIT" ]

null

dataset/original/colon/README.md

ExaNLP/sket

5ebe516f4454da246301532c353af57c1660ec69

[ "MIT" ]

1

2021-09-07T04:58:31.000Z

# Colon datasets Put here datasets containing Colon Cancer pathology reports.

19.75

60

0.822785

eng_Latn

0.942256

b5c9f8471b3f22ffcf7041bde7e6aa7669626e0d

48

md

Markdown

README.md

JustJokerX/AIRS

f21fc4db051dbe8986acc1d8cfde2dd6b69a1020

[ "MIT" ]

1

2017-06-07T13:25:10.000Z

README.md

JustJokerX/AIRS

f21fc4db051dbe8986acc1d8cfde2dd6b69a1020

[ "MIT" ]

null

README.md

JustJokerX/AIRS

f21fc4db051dbe8986acc1d8cfde2dd6b69a1020

[ "MIT" ]

null

# AIRS Artifical Intelligent & Robot Studio

16

40

0.791667

kor_Hang

0.188223

b5cae910c9f4b10b8dd1a0073c3a160ee0d59891

2,374

md

Markdown

docs/development/architecture.md

hamalcij/pfamannot

0d92b264bfb880678f13ebc7599c60c3c0bba091

[ "MIT" ]

null

docs/development/architecture.md

hamalcij/pfamannot

0d92b264bfb880678f13ebc7599c60c3c0bba091

[ "MIT" ]

null

docs/development/architecture.md

hamalcij/pfamannot

0d92b264bfb880678f13ebc7599c60c3c0bba091

[ "MIT" ]

null

[//]: # (pfamannot) [//]: # (Protein Family Annotator) [//]: # () [//]: # (docs/development/architecture.md) [//]: # (Copyright © 2020 Jan Hamalčík) [//]: # () [//]: # (Programmer's documentation of Architecture class) [//]: # () # `class Architecture` `class Architecture` represents a protein's architecture (see [theory](../user/theory.md)) by storing ordered domains belonging to given protein in a container. The class is defined in [source/architecture.hpp](../../source/architecture.hpp) and its methods are implemented in [source/architecture.cpp](../../source/architecture.cpp). ## Using-declarations ```cpp using setOfDomains = std::set<Domains, DomainComparator>; ``` `setOfDomains` denotes a set consisting of `Domain` instances. These are sorted upon insertion by the `DomainComparator` functor, which guarantees that inserted domains will be kept in correct order as in given protein. --- ## Private variables ```cpp setOfDomains architecture_; ``` Variable `architecture_` stores the architecture of the protein represented by an instance of `class Architecture`. It should only contain domains that are present in the protein represented by the instance. --- ## Constructor ```cpp Architecture::Architecture(const std::string& pfamID, const int& from, const int& to); ``` Emplaces a new instance of `class Domain` to newly created `architecture_` by the construction of `Architecture`. An architecture cannot exist without at least one domain. Following parameters have to be specified: * `const std::string domain` is the domain's Pfam ID. Its format should always be `PFxxxxx`, where `x` is a digit. * `const int from` is the position of domain's first amino acid in given protein. Its value should always be less than `to`. * `const int to` is the position of domain's last amino acid in given protein. Its value should always be greater than `from`. --- ## Public functions ```cpp void Architecture::emplace(const std::string& pfamID, const int& from, const int& to); ``` Same as [constructor](#Constructor). In this case, however, at least one domain from represented protein already exists and this adds another domain. --- ```cpp const setOfDomains& Architecture::getArchitecture() const ``` Returns constant reference to private variable `setOfDomains architecture_`. --- [Next](downloader.md) [Previous](domainComparator.md)

26.087912

86

0.738837

eng_Latn

0.985379

b5cc9dbea150f241dca1ff2b4fa289dc7f3b2eac

4,595

md

Markdown

synctera/docs/AddVendorAccountsRequest.md

synctera/client-libraries-go

13c5188a61aa0cb48401974c33b5aac6179efdfc

[ "Apache-2.0" ]

3

2021-09-23T00:18:52.000Z

2022-01-07T17:02:23.000Z

synctera/docs/AddVendorAccountsRequest.md

synctera/client-libraries-go

13c5188a61aa0cb48401974c33b5aac6179efdfc

[ "Apache-2.0" ]

null

synctera/docs/AddVendorAccountsRequest.md

synctera/client-libraries-go

13c5188a61aa0cb48401974c33b5aac6179efdfc

[ "Apache-2.0" ]

3

2022-03-17T02:40:43.000Z

2022-03-17T17:21:05.000Z

# AddVendorAccountsRequest ## Properties Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **CustomerId** | **string** | The identifier for the customer associated with these accounts. | **CustomerType** | **string** | The type of customer. | **Vendor** | [**ExternalAccountVendorValues**](ExternalAccountVendorValues.md) | | **VendorAccessToken** | **string** | The token provided to link external accounts. For Plaid, this is their `access_token`. | **VendorAccountIds** | **[]string** | The list of vendor account IDs that the customer chose to link. For Plaid, these are `account_id`s. | ## Methods ### NewAddVendorAccountsRequest `func NewAddVendorAccountsRequest(customerId string, customerType string, vendor ExternalAccountVendorValues, vendorAccessToken string, vendorAccountIds []string, ) *AddVendorAccountsRequest` NewAddVendorAccountsRequest instantiates a new AddVendorAccountsRequest object This constructor will assign default values to properties that have it defined, and makes sure properties required by API are set, but the set of arguments will change when the set of required properties is changed ### NewAddVendorAccountsRequestWithDefaults `func NewAddVendorAccountsRequestWithDefaults() *AddVendorAccountsRequest` NewAddVendorAccountsRequestWithDefaults instantiates a new AddVendorAccountsRequest object This constructor will only assign default values to properties that have it defined, but it doesn't guarantee that properties required by API are set ### GetCustomerId `func (o *AddVendorAccountsRequest) GetCustomerId() string` GetCustomerId returns the CustomerId field if non-nil, zero value otherwise. ### GetCustomerIdOk `func (o *AddVendorAccountsRequest) GetCustomerIdOk() (*string, bool)` GetCustomerIdOk returns a tuple with the CustomerId field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetCustomerId `func (o *AddVendorAccountsRequest) SetCustomerId(v string)` SetCustomerId sets CustomerId field to given value. ### GetCustomerType `func (o *AddVendorAccountsRequest) GetCustomerType() string` GetCustomerType returns the CustomerType field if non-nil, zero value otherwise. ### GetCustomerTypeOk `func (o *AddVendorAccountsRequest) GetCustomerTypeOk() (*string, bool)` GetCustomerTypeOk returns a tuple with the CustomerType field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetCustomerType `func (o *AddVendorAccountsRequest) SetCustomerType(v string)` SetCustomerType sets CustomerType field to given value. ### GetVendor `func (o *AddVendorAccountsRequest) GetVendor() ExternalAccountVendorValues` GetVendor returns the Vendor field if non-nil, zero value otherwise. ### GetVendorOk `func (o *AddVendorAccountsRequest) GetVendorOk() (*ExternalAccountVendorValues, bool)` GetVendorOk returns a tuple with the Vendor field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetVendor `func (o *AddVendorAccountsRequest) SetVendor(v ExternalAccountVendorValues)` SetVendor sets Vendor field to given value. ### GetVendorAccessToken `func (o *AddVendorAccountsRequest) GetVendorAccessToken() string` GetVendorAccessToken returns the VendorAccessToken field if non-nil, zero value otherwise. ### GetVendorAccessTokenOk `func (o *AddVendorAccountsRequest) GetVendorAccessTokenOk() (*string, bool)` GetVendorAccessTokenOk returns a tuple with the VendorAccessToken field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetVendorAccessToken `func (o *AddVendorAccountsRequest) SetVendorAccessToken(v string)` SetVendorAccessToken sets VendorAccessToken field to given value. ### GetVendorAccountIds `func (o *AddVendorAccountsRequest) GetVendorAccountIds() []string` GetVendorAccountIds returns the VendorAccountIds field if non-nil, zero value otherwise. ### GetVendorAccountIdsOk `func (o *AddVendorAccountsRequest) GetVendorAccountIdsOk() (*[]string, bool)` GetVendorAccountIdsOk returns a tuple with the VendorAccountIds field if it's non-nil, zero value otherwise and a boolean to check if the value has been set. ### SetVendorAccountIds `func (o *AddVendorAccountsRequest) SetVendorAccountIds(v []string)` SetVendorAccountIds sets VendorAccountIds field to given value. [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

33.786765

191

0.781066

eng_Latn

0.460947

b5ccf612c60a1e3535e781b9a746ee486d278f0f

3,485

md

Markdown

business-logic/RequestsAndResponses.md

etkeys/innovation-portal-flask

c96899fb53f1ce8ea61ddc1c40b8df894911476d

[ "Apache-2.0" ]

null

business-logic/RequestsAndResponses.md

etkeys/innovation-portal-flask

c96899fb53f1ce8ea61ddc1c40b8df894911476d

[ "Apache-2.0" ]

null

business-logic/RequestsAndResponses.md

etkeys/innovation-portal-flask

c96899fb53f1ce8ea61ddc1c40b8df894911476d

[ "Apache-2.0" ]

null

# BLS Requests and Reponses ## Backend exception When an exception occurs in BLS during the handling of a UI/UX request. ### Response `HTTP Response: 500` ```json { "exception-details":{ "message":"<message_string>", "number":<number>, "stack-trace":"<stack_trace_as_string>" } } ``` ## Change featured projects (Admin) Change featured projects lists. The admin should be able to search projects and select a up to a configured number. The project IDs should be sent back to BLS. TODO ## Change project owner (Admin) If a "faculty member" wishes to create a project that will later be assigned to a student, the faculty member must create the project then have an administrator assign the project to whoever they designate. TODO ## Create a project ### Request `Route: /project` ```json { "request":"project-create", "creator": "<userid>", "project-description":"<project-description>", "project-name":"<project-name>" } ``` ### Response `HTTP Response: 201` ```json { "response":"OK", "projectid":"<projectid>" } ``` ## Fill display case: Featured Provide a list of projects that are flagged as "Featured" ### Request `Route: /display` ```json { "request":"display-featured" } ``` ### Response `HTTP Response: 200` ```json { "count":<number>, "projects": [ { "description":"<description>", "projectid":<projectid>, "thumnailloc":"<path_to_thumnail>" } ] } ``` ## Fill display case: Simple search User fills in words (space delimited) into the search box in the main menu bar. ### Request `Route: /display` ```json { "request":"display-simple-search", "filter": [ "word|tag","word|tag", "word|tag"] } ``` ### Response _Same as **Fill display case: Featured**._ ## Login ### Request `Route: /authentication` ```json { "request":"authentication-logon", "credentials":{ "passwordhash":"<hashed_password>", "username":"<username>" } } ``` ### Response #### Not successful `HTTP Response: 401` ```json { "message":"<reason_for_not_success>" } ``` #### Successful `HTTP Response: 200` ```json { "userdef":{ "permissions":{ "creator":[<projectid>, ...], "moderator":[<projectid>, ...], "participant":[<projectid>, ...], "special-user-flag":"<permission_type>" }, "user-display-name":"<user_display_name>", "useremail":"<user_email>", "username":"<user_name>" } } ``` Will need to pass back some sort of token. ## Project collaborator uploads artifact ### Request `Route: /project` ```json { "request":"project-artifact-upload", "artifact-location":"<file_full_name>", "artifact-type":"<file_type>", "projectid":"<projectid>", "userid":"<userid>" } ``` ### Response #### Accepted `HTTP Response: 202` ```json { "resouceid":"<resourceid>" } ``` `<resouceid>` is some sort of unique identifier associated with that particular artifact. It should be a git hash or some other GUID from a document database. #### Rejected User does not have permissions: `HTTP Response: 403` ## User requests to join a project ### Request `Route: /project` ```json { "request":"project-join", "project":<projectid>, "requestor":"<userid>" } ``` ### Response `HTTP Response: 201` ```json { "response":"OK", "collab-link-id":"<collab-link-id>" } ```

16.059908

206

0.614347

eng_Latn

0.821383

b5cd44bab9b9f98f1d637b0909c555004d66868e

1,233

md

Markdown

README.md

wiktor-k/ssh-agent-lib

4ca0f436c99e816d6ef70a7af80e5509899827f3

[ "MIT" ]

null

README.md

wiktor-k/ssh-agent-lib

4ca0f436c99e816d6ef70a7af80e5509899827f3

[ "MIT" ]

null

README.md

wiktor-k/ssh-agent-lib

4ca0f436c99e816d6ef70a7af80e5509899827f3

[ "MIT" ]

null

# ssh-agent-lib A collection of types for writing custom SSH agents. This makes it possible to utilize remote keys not supported by the default OpenSSH agent. ## Example This example starts listening on a Unix socket `connect.sock` and processes requests. ```rust,no_run use ssh_agent_lib::agent::Agent; use ssh_agent_lib::proto::message::{Message, SignRequest}; struct MyAgent; impl Agent for MyAgent { type Error = (); fn handle(&self, message: Message) -> Result<Message, ()> { match message { Message::SignRequest(request) => { // get the signature by signing `request.data` let signature = vec![]; Ok(Message::SignResponse(signature)) }, _ => Ok(Message::Failure), } } } fn main() -> Result<(), Box<dyn std::error::Error + Send + Sync>> { let agent = MyAgent; let socket = "connect.sock"; let _ = std::fs::remove_file(socket); agent.run_unix(socket)?; Ok(()) } ``` For more elaborate example see `examples` directory. ## Note This library has been forked from [sekey/ssh-agent.rs](https://github.com/sekey/ssh-agent.rs) as the upstream seems not be maintained (at least as of 2022).

24.176471

67

0.639903

eng_Latn

0.906544

b5cdd61d757ec9714ed1ad92f601267395e06eac

1,637

md

Markdown

README.md

usco/usco-3md-parser

6fca3376b61c451bedb615fca25b7481084583ec

[ "MIT" ]

null

README.md

usco/usco-3md-parser

6fca3376b61c451bedb615fca25b7481084583ec

[ "MIT" ]

null

README.md

usco/usco-3md-parser

6fca3376b61c451bedb615fca25b7481084583ec

[ "MIT" ]

1

2016-08-29T10:14:19.000Z

# usco-3mf-parser [![GitHub version](https://badge.fury.io/gh/usco%2Fusco-3mf-parser.svg)](https://badge.fury.io/gh/usco%2Fusco-3mf-parser) [![Build Status](https://travis-ci.org/usco/usco-3mf-parser.svg?branch=master)](https://travis-ci.org/usco/usco-3mf-parser) [![Dependency Status](https://david-dm.org/usco/usco-3mf-parser.svg)](https://david-dm.org/usco/usco-3mf-parser) [![devDependency Status](https://david-dm.org/usco/usco-3mf-parser/dev-status.svg)](https://david-dm.org/usco/usco-3mf-parser#info=devDependencies) > Fast and efficient [3mf](https://en.wikipedia.org/wiki/3D_Manufacturing_Format) format parser - Optimized for speed (webworkers) - And low memory consumption (streams) - works in the Node.js & browser ## Table of Contents - [Install](#install) - [Usage](#usage) - [API](#api) - [Contribute](#contribute) - [License](#license) ## Install ``` npm i @usco/3mf-parser ``` ## Usage ```JavaScript import makeParsedStream from '@usco/3mf-parser' fs.createReadStream('./someFile.3mf', { encoding: null}) // 'binary' .pipe(makeParsedStream()) .on('data', function (parsed) { console.log('parsed', parsed) //DO what you want with the data }) ``` ## API ## Contribute See [the contribute file](contribute.md)! PRs accepted. Small note: If editing the Readme, please conform to the [standard-readme](https://github.com/RichardLitt/standard-readme) specification. Code is written in the standard style. [![JavaScript Style Guide](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard) ## License [MIT © Mark Moissette](./LICENSE)

25.184615

147

0.708613

kor_Hang

0.187442

b5cede0e75e938f858a4aba36939ee69d78a4ffa

1,363

md

Markdown

README.md

ziguzagu/capistrano-scm-tar

8ce7bda8e8941b374eed98e9308180020c397250

[ "MIT" ]

2

2016-01-27T22:58:15.000Z

2018-11-08T12:02:20.000Z

README.md

ziguzagu/capistrano-scm-tar

8ce7bda8e8941b374eed98e9308180020c397250

[ "MIT" ]

3

2015-09-29T15:03:23.000Z

2020-02-29T06:52:27.000Z

README.md

ziguzagu/capistrano-scm-tar

8ce7bda8e8941b374eed98e9308180020c397250

[ "MIT" ]

3

2015-09-03T06:30:35.000Z

2019-03-06T12:39:46.000Z

# capistrano-scm-tar [![Gem Version](https://badge.fury.io/rb/capistrano-scm-tar.svg)](https://badge.fury.io/rb/capistrano-scm-tar) [![Maintainability](https://api.codeclimate.com/v1/badges/0c077beb6ef93cd84d3e/maintainability)](https://codeclimate.com/github/ziguzagu/capistrano-scm-tar/maintainability) [![Test Coverage](https://api.codeclimate.com/v1/badges/0c077beb6ef93cd84d3e/test_coverage)](https://codeclimate.com/github/ziguzagu/capistrano-scm-tar/test_coverage) A tar strategy for Capistrano 3 to deploy tarball. ## Installation Add this line to your application's Gemfile: ```ruby gem 'capistrano-scm-tar' ``` ## Usage Set `tar` as `scm` option in your `config/deploy.rb`: ```ruby set :scm, :tar ``` Build a release package of your project and upload it to the server you run capistrano: ```shell tar czf /tmp/v1.0.0.tar.gz * scp /tmp/v1.0.0.tar.gz example.com:/tmp/v1.0.0.tar.gz ``` And then, deploy it: ```shell cap deploy package=/tmp/v1.0.0.tar.gz ``` The basename of tarball is used for the revision number of capistrano setting by `set_current_revision`. ## Contributing Bug reports and pull requests are welcome on GitHub at [https://github.com/toreta/time_second](https://github.com/toreta/time_second). ## License The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

28.395833

172

0.75055

eng_Latn

0.549568

b5ceee97843358eab21ad09e62fea97b5d50615d

10,352

md

Markdown

articles/app-service-logic/app-service-logic-monitor-your-connectors.md

SunnyDeng/azure-content-dede

edb0ac8eec176b64971ec219274a4a922dd00fec

[ "CC-BY-3.0" ]

2

2020-08-29T21:10:59.000Z

2021-07-25T10:13:02.000Z

articles/app-service-logic/app-service-logic-monitor-your-connectors.md

SunnyDeng/azure-content-dede

edb0ac8eec176b64971ec219274a4a922dd00fec

[ "CC-BY-3.0" ]

null

articles/app-service-logic/app-service-logic-monitor-your-connectors.md

SunnyDeng/azure-content-dede

edb0ac8eec176b64971ec219274a4a922dd00fec

[ "CC-BY-3.0" ]

null

<properties pageTitle="Verwalten und Überwachen von Connectors und API-Apps in App Service | Microsoft Azure" description="Anzeigen der Leistung von Connectors und API-Apps in Azure App Service; Microservices-Architektur" services="app-service\logic" documentationCenter=".net,nodejs,java" authors="MandiOhlinger" manager="dwrede" editor="cgronlun"/> <tags ms.service="app-service-logic" ms.workload="integration" ms.tgt_pltfrm="na" ms.devlang="na" ms.topic="article" ms.date="09/29/2015" ms.author="mandia"/> # Verwalten und Überwachen integrierter API-Apps und Connectors Sie haben eine integrierte API-App erstellt. Was nun? In Azure ist jede API-App eine separate in Azure gehostete Website. Daher können Sie einfach erkennen, wie viele Anforderungen gestellt und wie viele Daten vom Connector verwendet wurden. Sie können Ihre App-API auch sichern, Warnungen erstellen, Tinfoil Security aktivieren sowie Benutzer und Rollen hinzufügen. In diesem Thema werden einige der Möglichkeiten zum Verwalten Ihrer App-API beschrieben. Um diese integrierten Features anzuzeigen, öffnen Sie die API-App im [Azure-Portal](http://go.microsoft.com/fwlink/p/?LinkID=525040). Wenn sich die API-App in Ihrem Startmenü befindet, wählen Sie sie aus, um das Eigenschaftenfenster zu öffnen. Sie können auch auf **Durchsuchen** klicken, **API-Apps** auswählen und dann Ihre API-App auswählen: ![][browse] ## Anzeigen der von Ihnen eingegebenen Eigenschaften Wenn Sie die API-App öffnen, stehen mehrere Features und Aufgaben zur Verfügung: ![][settings] Ihre Möglichkeiten: - Unter **Einstellungen** werden spezifische Informationen zur API-App gezeigt, einschließlich Details zu Ihrem Abonnement, und die Benutzer mit Zugriff auf Ihre API-App aufgelistet. Sie können auch die Anzahl der Instanzen Ihrer App-API mithilfe des Features "Staffelung" erhöhen oder verringern, das neben anderen Features zur Verfügung steht. - Klicken Sie zum Steuern der API-App auf die Schaltflächen **Starten** und **Beenden**. - Wenn Produktupdates an den zugrunde liegenden Dateien erfolgen, die von Ihrer App-API verwendet werden, können Sie auf **Aktualisieren** klicken, um die neuesten Versionen zu erhalten. Wenn z. B. eine Korrektur oder ein Sicherheitsupdate von Microsoft veröffentlicht wird, wird Ihre App-API durch Klicken auf **Aktualisieren** automatisch mit dieser Korrektur aktualisiert. - Klicken Sie auf **Plan ändern**, um ein Upgrade oder Downgrade anhand der Datenverwendung Ihrer API-App vorzunehmen. Dieses Feature dient auch zum Anzeigen Ihrer Datennutzung. - Wenn Sie einen Connector erstellen, der Tabellen aufweist, wie z. B. der SQL-Connector, können Sie optional den Namen einer Tabelle eingeben, mit der eine Verbindung hergestellt werden soll. Ein Schema auf Grundlage der Tabelle wird automatisch erstellt und ist verfügbar, wenn Sie auf **Schemas herunterladen** klicken. Dieses heruntergeladene Schema können Sie dann zum Erstellen einer Transformation oder Zuordnung nutzen. ## Ändern Sie den Connector oder API-Konfigurationswerte, die Sie eingegeben haben. Nachdem Sie Connector konfiguriert oder erstellt haben, können Sie die Werte ändern, die Sie eingegeben haben. Wenn Sie z. B. den SQL-Connector konfiguriert haben und den SQL Server-Namen oder Tabellennamen ändern möchten, ist dies auf dem Blatt "API-App" für den Connector möglich. Dazu müssen diese Schritte ausgeführt werden: 1. Öffnen Sie Ihren Connector oder Ihre API-App. In diesem Fall wird das Blatt "API-App" geöffnet. 2. Klicken Sie unter **Essentials** auf den Link unter der Eigenschaft "Host". Der Link wird als *slackconnector* oder *microsoftsqlconnector123* angezeigt: ![][apiapphost] 3. Klicken Sie auf dem Blatt "API-App-Host" auf **Einstellungen**. Klicken Sie auf dem Blatt "Einstellungen" auf **Anwendungseinstellungen**. Der Konfigurationswerte sind unter **App-Einstellungen** aufgeführt: ![][hostsettings] 4. Klicken Sie auf die Einstellung, die Sie ändern möchten, geben den neuen Wert ein, und **speichern** Sie Ihre Änderungen. ## Installieren des Hybrid Connection Managers (optional) ![][hcsetup] Der Hybrid Connection Manager bietet Ihnen die Möglichkeit zur Verbindungsherstellung mit einem lokalen System, beispielsweise SQL Server oder SAP. Diese Hybridkonnektivität verwendet Azure Service Bus zur Verbindungsherstellung und zur Steuerung der Sicherheit zwischen Ihren Azure-Ressourcen und Ihren lokalen Ressourcen. Siehe [Verwenden des Hybrid Connection Managers in Azure App Service](app-service-logic-hybrid-connection-manager.md). > [AZURE.NOTE]Der Hybrid Connection Manager wird nur benötigt, wenn Sie auf eine lokale Ressource hinter der Firewall eine Verbindung herstellen wollen. Wenn Sie keine Verbindung mit einem lokalen System herstellen möchten, ist der Hybrid Connection Manager ggf. nicht auf Ihrem Blatt "Connector" aufgeführt. ## Überwachen der Leistung Leistungsmetriken sind integrierte Features und gehören zu jeder API-App, die Sie erstellen. Diese Metriken sind spezifisch für Ihre in Azure gehostete API-App. Beispielmetriken: ![][monitoring] Sie können: - Durch Auswahl von **Anforderungen und Fehler** können Sie unterschiedliche Leistungsmetriken hinzufügen, beispielsweise gängige HTTP-Fehlercodes wie die HTTP-Statuscodes 200, 400 oder 500. Sie können auch Antwortzeiten, die Anzahl von Anforderungen an eine API-App sowie die Menge ein- und ausgehender Daten anzeigen. Auf der Grundlage der Leistungsmetriken können Sie E-Mail-Warnungen erstellen, wenn eine Metrik einen gewählten Schwellenwert überschreitet. - Unter **Nutzung** ist es möglich, die **CPU**-Auslastung durch die API-App, das aktuelle **Nutzungskontingent** in MB und die maximale Datennutzung basierend auf Ihrem Tarif anzuzeigen. Über **Geschätzte Ausgaben** können Sie die potenziellen Kosten für die Ausführung Ihrer API-App anzeigen. - Wählen Sie **Prozesse**, um den Prozess-Explorer zu öffnen. Dieser zeigt Ihre Webinstanzen und ihre Eigenschaften, einschließlich Threadanzahl und Arbeitsspeichernutzung. Mithilfe dieser Tools können Sie bestimmen, ob der App Service-Plan basierend auf Ihren Geschäftsanforderungen zentral hoch- oder herunterskaliert werden sollte. Diese Features sind in das Portal integriert, sodass keine zusätzliche Tools erforderlich sind. ## Steuern der Sicherheit Für API-Apps gilt die rollenbasierte Sicherheit. Diese Rollen gelten für die gesamte Azure-Umgebung, einschließlich API-Apps und anderer Azure-Ressourcen. Es gibt die folgenden Rollen: Rolle | Beschreibung --- | --- Besitzer | Verfügen über Vollzugriff auf die Verwaltungsfunktionen und können anderen Benutzern oder Gruppen Zugriff gewähren. Mitwirkender | Verfügen über Vollzugriff auf die Verwaltungsfunktionen. Können anderen Benutzern oder Gruppen keinen Zugriff gewähren. Reader | Können alle Ressourcen mit Ausnahme geheimer Schlüssel anzeigen. Benutzerzugriffsadministrator | Können alle Ressourcen anzeigen, Rollen erstellen/verwalten und Supporttickets erstellen/verwalten. Siehe [Rollenbasierte Zugriffssteuerung über das Microsoft Azure-Portal](role-based-access-control-configure.md). Sie können Benutzer problemlos hinzufügen und ihnen bestimmte Rollen für Ihre API-App zuweisen. Das Portal zeigt die Benutzer, die Zugriff haben, und die ihnen zugewiesene Rolle: ![][access] - Wählen Sie **Benutzer** aus, um einen Benutzer hinzuzufügen, eine Rolle zuzuweisen und einen Benutzer zu entfernen. - Wählen Sie **Rollen** aus, um alle Benutzer mit einer bestimmten Rolle anzuzeigen, einen Benutzer einer Rolle hinzuzufügen und einen Benutzer aus einer Rolle zu entfernen. ## Weitere praktische Optionen - Wählen Sie **API-Definition** aus, um die für Ihre spezifische API automatisch erstellte Swagger-Datei zu öffnen. - Wählen Sie **Abhängigkeiten** aus, um die von Ihrer API-App benötigten Dateien anzuzeigen. Wenn Sie z. B. den SAP-Connector verwenden, installieren Sie einige zusätzlichen Dateien für den lokalen Hybrid Connection Manager. Diese Abhängigkeiten werden auf dem Blatt "API-App" angezeigt. > [AZURE.IMPORTANT]Wenn Sie die Eigenschaften Ihrer API-App öffnen und unter **Essentials** nachsehen, gibt es die Links **Host** und **Gateway**, über die neue Blätter geöffnet werden: > > ![][host] > > Diese Eigenschaften sind spezifisch für die Website, die Ihre API-App hostet. Bei Verwendung einer integrierten API-App oder eines Connectors gelten die meisten dieser Eigenschaften nicht wirklich, und es wird empfohlen, dass Sie diese Eigenschaften nicht aktualisieren. Wenn Sie Ihre eigenen API-App in Visual Studio erstellt und in Ihrem Azure-Abonnement bereitgestellt haben, können Sie die Blätter "Host" und "Gateway" verwenden. Unter [Verwalten von API-Apps](../app-service-api/app-service-api-manage-in-portal.md) finden weitere Informationen zu den Aufgaben, die Sie auf diesen Blättern für Ihre benutzerdefiniert erstellte API-App ausführen können. >[AZURE.NOTE]Wenn Sie Azure Logik-Apps ausprobieren möchten, ehe Sie sich für ein Azure-Konto anmelden, können Sie unter [Logik-App testen](https://tryappservice.azure.com/?appservice=logic) sofort kostenlos eine kurzlebige Starter-Logik-App in App Service erstellen. Keine Kreditkarte und keine Verpflichtungen erforderlich. ## Weitere Informationen [Überwachen von Logik-App](app-service-logic-monitor-your-logic-apps.md)<br/>[Liste der Connectors und API-Apps in Microsoft Azure App Service](app-service-logic-connectors-list.md)<br/>[Rollenbasierte Zugriffssteuerung über das Microsoft Azure-Portal](role-based-access-control-configure.md)<br/>[Verwenden des Hybrid Connection Managers in Azure App Service](app-service-logic-hybrid-connection-manager.md)  [browse]: ./media/app-service-logic-monitor-your-connectors/browse.png [settings]: ./media/app-service-logic-monitor-your-connectors/settings.png [hcsetup]: ./media/app-service-logic-monitor-your-connectors/hcsetup.png [monitoring]: ./media/app-service-logic-monitor-your-connectors/monitoring.png [access]: ./media/app-service-logic-monitor-your-connectors/access.png [host]: ./media/app-service-logic-monitor-your-connectors/host.png [hostsettings]: ./media/app-service-logic-monitor-your-connectors/hostsettings.png [apiapphost]: ./media/app-service-logic-monitor-your-connectors/apiapphost.png

76.681481

659

0.803613

deu_Latn

0.998044

b5cf477897587c86ed2ecc2ae62d7b02e870f5a5

1,801

md

Markdown

Software Testing Concepts/Test types/Integration tests/README.md

lkrust/QARoadMap

c14009ef948df811dcc6123016e35d80654fc70c

[ "CC0-1.0" ]

5

2020-10-21T13:55:14.000Z

2020-11-09T19:26:31.000Z

Software Testing Concepts/Test types/Integration tests/README.md

lkrust/QARoadMap

c14009ef948df811dcc6123016e35d80654fc70c

[ "CC0-1.0" ]

null

Software Testing Concepts/Test types/Integration tests/README.md

lkrust/QARoadMap

c14009ef948df811dcc6123016e35d80654fc70c

[ "CC0-1.0" ]

1

2020-10-21T13:55:16.000Z

# Software Testing concepts > Test types > Unit Test ## Texts: - [ ] [Wikipedia](https://en.wikipedia.org/wiki/Integration_testing) - [ ] [softwaretestingfundamentals](https://softwaretestingfundamentals.com/integration-testing/) ## Exercises: ### 1. What integration test? <Details> <summary>Answer</summary> Integration Testing is a level of software testing where individual units are combined and tested to verify if they are working as they intend to when integrated. The main aim here is to test the interface between the modules. </Details> ### 2. Why we need integration testing? <Details> <summary>Answer</summary> Integration testing is executed to establish whether the components interact with each other consort to the specification or not. Integration testing in large refers to joining all the components resulting in the complete system. It is further performed by the developer or the software Tester or by both. Example- checking that a Payroll system interacts as required with the Human Resource system. </Details> ### 3. what are the integration Testing Types? <Details> <summary>Answer</summary> - Top-down testing approach <br>- Bottom-up testing approach <br>- Big-Bang testing approach <br>- Sandwiched testing approach </Details> ### 4. What are the advantages of integration Testing? <Details> <summary>Answer</summary> - It makes sure that integrated modules work properly as intended <br>- The tester can start testing once the modules to be tested are available <br>- It detects errors related to the interface between modules <br>- Helps modules interact with API’s and other third-party tools <br>- Typically covers a large volume of the system, so more efficient <br>- Increases the test coverage and improves the reliability of tests </Details>

36.755102

400

0.77457

eng_Latn

0.997829

b5d0d4d0cf4cb79fc4e1bd75661c2cbb9541391e

1,927

markdown

Markdown

website/docs/r/inline_hook.html.markdown

patluri43/terraform-provider-okta

7f1c9eab49cb7e2421c0110c2c2c254f9f2d1dca

[ "MIT" ]

1

2019-10-08T17:33:20.000Z

website/docs/r/inline_hook.html.markdown

patluri43/terraform-provider-okta

7f1c9eab49cb7e2421c0110c2c2c254f9f2d1dca

[ "MIT" ]

null

website/docs/r/inline_hook.html.markdown

patluri43/terraform-provider-okta

7f1c9eab49cb7e2421c0110c2c2c254f9f2d1dca

[ "MIT" ]

1

2019-10-18T18:44:36.000Z

--- layout: "okta" page_title: "Okta: okta_inline_hook" sidebar_current: "docs-okta-resource-inline-hook" description: |- Creates an inline hook. --- # okta_inline_hook Creates an inline hook. This resource allows you to create and configure an inline hook. ## Example Usage ```hcl resource "okta_inline_hook" "example" { name = "example" version = "1.0.1" type = "com.okta.oauth2.tokens.transform" channel = { version = "1.0.0" uri = "https://example.com/test" method = "POST" } auth = { key = "Authorization" type = "HEADER" value = "secret" } } ``` ## Argument Reference The following arguments are supported: * `name` - (Required) The inline hook display name. * `version` - (Required) The version of the hook. * `type` - (Required) The type of hook to create. [See here for supported types](https://developer.okta.com/docs/reference/api/inline-hooks/#supported-inline-hook-types). * `headers` - (Optional) Map of headers to send along in inline hook request. * `key` - (Required) Header name. * `value` - (Required) Header value. * `auth` - (Optional) Authentication required for inline hook request. * `key` - (Required) Key to use for authentication, usually the header name, for example `"Authorization"`. * `value` - (Required) Authentication secret. * `type` - (Optional) Auth type, default is `"HEADER"`. * `channel` - (Optional) Details of the endpoint the inline hook will hit. * `version` - (Required) The version of the endpoint. * `uri` - (Required) The URI the hook will hit. * `type` - (Optional) The type of hook to trigger. Currently only `"HTTP"` is supported. * `method` - (Optional) The request method to use. Default is `"POST"`. ## Attributes Reference * `id` - The ID of the inline hooks. ## Import An inline hook can be imported via the Okta ID. ``` $ terraform import okta_inline_hook.example <hook id> ```

26.39726

170

0.676181

eng_Latn

0.919213

b5d16140c43fdcc75f7a13575ac407cb77f25683

6,002

md

Markdown

Docs/Get-MacmonEndpoint.md

falkheiland/PSmacmon

a86882375dea86bb4757a45e62baa51af46121ae

[ "MIT" ]

2

2019-01-23T15:43:08.000Z

2020-12-01T08:36:08.000Z

Docs/Get-MacmonEndpoint.md

falkheiland/PSmacmon

a86882375dea86bb4757a45e62baa51af46121ae

[ "MIT" ]

null

Docs/Get-MacmonEndpoint.md

falkheiland/PSmacmon

a86882375dea86bb4757a45e62baa51af46121ae

[ "MIT" ]

1

2019-01-23T15:43:08.000Z

--- external help file: PSmacmon-help.xml Module Name: PSmacmon online version: https://github.com/falkheiland/PSmacmon/blob/master/Docs/Get-MacmonEndpoint.md schema: 2.0.0 --- # Get-MacmonEndpoint ## SYNOPSIS Get Endpoint from the macmon NAC via RESTAPI. ## SYNTAX ### All (Default) ``` Get-MacmonEndpoint -HostName <String> [-TCPPort <Int32>] [-ApiVersion <String>] [-Credential <PSCredential>] [-Fields <String>] [-Sort <String>] [-Limit <Int32>] [-Offset <Int32>] [-Filter <String>] [<CommonParameters>] ``` ### MAC ``` Get-MacmonEndpoint -HostName <String> [-TCPPort <Int32>] [-ApiVersion <String>] [-Credential <PSCredential>] [-MACAddress <String>] [-Fields <String>] [<CommonParameters>] ``` ## DESCRIPTION Get Endpoint from the macmon NAC via RESTAPI. ## EXAMPLES ### Example 1 ```powershell $Params = @{ Hostname = 'MACMONSERVER' Credential = Get-Credential } Get-MacmonEndpoint @Params ``` ``` mac : 00-19-99-B4-2C-06 type : CORPORATE comment : wakeupTime : active : True identityStoreId : -1 staticIps : {} userValues : endpointGroup : inventory : created : 2018-12-05T09:59:15.918Z identity : 00-19-99-B4-2C-06 lastChangeTime : 2018-12-05T09:59:15.918Z expireTime : authorizedVlans : {} endpointGroupId : 120 endpointDeviceStatus : mac : 00-19-99-B1-3C-15 type : CORPORATE comment : wakeupTime : active : True identityStoreId : -1 staticIps : {} userValues : endpointGroup : inventory : created : 2018-12-05T09:59:15.918Z identity : PC012345.acme.org lastChangeTime : 2018-12-05T09:59:15.918Z expireTime : authorizedVlans : {} endpointGroupId : 102 endpointDeviceStatus : ``` Get all endpoints (excerpt). ### Example 2 ```powershell $Params = @{ Hostname = 'MACMONSERVER' Fields = 'mac,endpointDeviceStatus.lastIp' Sort = '-mac' Limit = 1 Offset = 10 Filter = 'endpointGroupId==150' } Get-MacmonEndpoint @Params ``` ``` mac endpointDeviceStatus --- -------------------- F0-92-1C-64-C5-8F @{lastIp=192.168.6.17} ``` Get mac and lastIP address from 11th endpoint from endpointgroup with ID 150 sorted by mac descending. ### Example 3 ```powershell '00-00-FF-FF-FF-FF' | Get-MacmonEndpoint -Hostname 'MACMONSERVER' ``` ``` mac : 00-00-FF-FF-FF-FF type : CORPORATE comment : wakeupTime : active : False identityStoreId : -1 staticIps : {} userValues : endpointGroup : inventory : created : 2018-12-05T09:59:15.917Z identity : 00-00-FF-FF-FF-FF lastChangeTime : 2018-12-05T09:59:15.917Z expireTime : authorizedVlans : {} endpointGroupId : 10 endpointDeviceStatus : ``` Get Endpoint with MACAddress '00-00-FF-FF-FF-FF'. ## PARAMETERS ### -HostName IP-Address or Hostname of the macmon NAC ```yaml Type: String Parameter Sets: (All) Aliases: Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -TCPPort TCP Port API (Default: 443) ```yaml Type: Int32 Parameter Sets: (All) Aliases: Required: False Position: Named Default value: 443 Accept pipeline input: False Accept wildcard characters: False ``` ### -ApiVersion API Version to use (Default: 1.0) ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: 1.0 Accept pipeline input: False Accept wildcard characters: False ``` ### -Credential Credentials for the macmon NAC ```yaml Type: PSCredential Parameter Sets: (All) Aliases: Required: False Position: Named Default value: (Get-Credential -Message 'Enter your credentials') Accept pipeline input: False Accept wildcard characters: False ``` ### -MACAddress MAC Address of the endpoint group ```yaml Type: String Parameter Sets: MAC Aliases: Required: False Position: Named Default value: None Accept pipeline input: True (ByValue) Accept wildcard characters: False ``` ### -Fields Select string (e.g. 'address,networkDeviceGroupId') ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Sort Sort string (e.g. 'active,address') ```yaml Type: String Parameter Sets: All Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Limit Limit int (e.g. 10) ```yaml Type: Int32 Parameter Sets: All Aliases: Required: False Position: Named Default value: 0 Accept pipeline input: False Accept wildcard characters: False ``` ### -Offset Offset int (e.g. 10) ```yaml Type: Int32 Parameter Sets: All Aliases: Required: False Position: Named Default value: 0 Accept pipeline input: False Accept wildcard characters: False ``` ### -Filter Filter string (e.g. '(id >=4 and id <= 10) and active == true and nac != true') ```yaml Type: String Parameter Sets: All Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUTS ## OUTPUTS ## NOTES ## RELATED LINKS [https://github.com/falkheiland/PSmacmon](https://github.com/falkheiland/PSmacmon) [https://MACMONSERVER/man/index.php?controller=ApiDocuController](https://MACMONSERVER/man/index.php?controller=ApiDocuController)

20.62543

216

0.665945

yue_Hant

0.356487

b5d269a43eb0f1f4023b4afde6c8fdac01791b48

349

md

Markdown

Partie réglementaire - Décrets en Conseil d'Etat/Livre Ier/Titre III/Article R131-29.md

steeve/france.code-penal

3735c397927db488ed31d137bff549c2452f633d

[ "CC-BY-4.0" ]

156

2015-04-01T07:37:28.000Z

2022-01-17T00:16:18.000Z

Partie réglementaire - Décrets en Conseil d'Etat/Livre Ier/Titre III/Article R131-29.md

steeve/france.code-penal

3735c397927db488ed31d137bff549c2452f633d

[ "CC-BY-4.0" ]

1

2018-12-21T09:04:30.000Z

Partie réglementaire - Décrets en Conseil d'Etat/Livre Ier/Titre III/Article R131-29.md

steeve/france.code-penal

3735c397927db488ed31d137bff549c2452f633d

[ "CC-BY-4.0" ]

10

2015-04-01T14:27:55.000Z

2021-01-28T10:36:54.000Z

Article R131-29 ---- Le juge de l'application des peines s'assure de l'exécution du travail d'intérêt général soit par lui-même, soit par l'intermédiaire d'un agent de probation. Si le travail à exécuter est inscrit sur la liste d'un autre ressort, il délègue son pouvoir de contrôle au juge de l'application des peines territorialement compétent.

38.777778

80

0.793696

fra_Latn

0.994752

b5d32878732c990fa77f34c89622036c176d7047

21

md

Markdown

README.md

rayuzaki83/go-app

474346dff951b7c74f521e20526a32a4878b0331

[ "MIT" ]

null

README.md

rayuzaki83/go-app

474346dff951b7c74f521e20526a32a4878b0331

[ "MIT" ]

null

README.md

rayuzaki83/go-app

474346dff951b7c74f521e20526a32a4878b0331

[ "MIT" ]

null

# go-app Testing Go

7

11

0.666667

eng_Latn

0.477045

b5d39f3040cebdd0c711d89b29dfd1d2621fe169

1,901

md

Markdown

Why.md

bobg/tredd

657787f8ff7949a16dca451239c4e496443e5c46

[ "MIT" ]

3

2019-03-26T12:48:33.000Z

2021-08-13T22:30:33.000Z

Why.md

bobg/tredd

657787f8ff7949a16dca451239c4e496443e5c46

[ "MIT" ]

3

2020-10-07T15:19:55.000Z

2020-11-02T01:58:36.000Z

Why.md

bobg/tredd

657787f8ff7949a16dca451239c4e496443e5c46

[ "MIT" ]

3

2020-10-07T19:43:52.000Z

2020-10-16T19:00:07.000Z

# Why Tredd The Internet was going to be great. Then [advertising took over and turned everything to shit](https://www.nytimes.com/2018/01/31/technology/internet-advertising-business.html). It would be better if the customers of online services were [the users instead of the advertisers](https://rushkoff.com/you-are-not-facebooks-customer/). But that means paying for the services we all now receive for free. Of course they’re not really free, and that’s the problem. The price is the hijacking of our attention, and ultimately our _intention_, using increasingly sophisticated tactics from [psychological warfare](https://www.psychologytoday.com/us/blog/psych-unseen/201803/the-internet-psychological-warfare-and-mass-conspiracy). Nevertheless, the services _feel_ free, which means they are subject to [the zero-price effect](https://market.subwiki.org/wiki/Zero_price_effect). The zero-price effect means service providers can expect a significant drop in demand when charging even slightly more than zero. Some services employ [the freemium model](https://en.wikipedia.org/wiki/Freemium): they are ad-supported when offered for free, but they can also be paid for by the user to eliminate ads and perhaps unlock additional features. Enough people choosing the payment option of freemium would loosen the grip that Internet advertising has on us all. But the implementation of freemium is problematic. Never mind the price: the _payment mechanisms_ of freemium involve too much overhead. Each provider has its own separate payment “flow.” Monthly subscriptions must be renewed. Pricing tiers are coarse. Think about it: How many different service providers do _you_ want to deal with signing up for? The goal of Tredd is to solve this part of the killing-advertising problem. It demonstrates a uniform infrastructure for per-use micropayments that can be shared by all service providers.

46.365854

140

0.809048

eng_Latn

0.998363

b5d3ab595227d9846a7ad79f05006ee1c2c4e081

8,502

md

Markdown

pages/accounting.md

18F/pclob

331e90c1e07109509b5bed4f46e9db1a9abfdce8

[ "CC0-1.0", "MIT" ]

null

pages/accounting.md

18F/pclob

331e90c1e07109509b5bed4f46e9db1a9abfdce8

[ "CC0-1.0", "MIT" ]

72

2017-07-12T19:01:45.000Z

2020-04-22T22:40:47.000Z

pages/accounting.md

18F/pclob

331e90c1e07109509b5bed4f46e9db1a9abfdce8

[ "CC0-1.0", "MIT" ]

3

2018-11-08T20:11:22.000Z

2021-02-04T11:01:43.000Z

--- layout: report-list permalink: /accounting/ title: ACCOUNTANT collection: Accountant --- **Job Title:** Accountant **Agency:** Privacy and Civil Liberties Oversight Board **Salary Range:** $86,335 – $157,709/ Per Year **Series/Grade:** The agency uses the Administratively Determined system in which rank is attached to the individual. The salary range for this position is statutorily capped at $160,100. **Position Information:** This is an opportunity for permanent employment in the excepted service. You will be required to serve a two-year trial period. **Duty Location:** Washington, DC **Who May Apply:** Open to the public. U.S. citizenship required. **Security Clearance:** Must have or be able to obtain a TOP SECRET – Sensitive Compartmented Information (TS-SCI) Security clearance. If you already have a TS/SCI clearance, please highlight your last investigation date in your application. **Agency Mission** The Privacy and Civil Liberties Oversight Board's responsibilities comprise two basic functions: oversight and advice. In its oversight role, the Board is authorized to continually review the implementation of executive branch policies, procedures, regulations, and information sharing practices relating to efforts to protect the nation from terrorism, in order to ensure that privacy and civil liberties are protected. The Board is also authorized to continually review any other actions of the executive branch relating to efforts to protect the nation from terrorism, in order to determine whether such actions appropriately protect privacy and civil liberties and whether they are consistent with governing laws, regulations, and policies regarding privacy and civil liberties. In its advice role, the Board is authorized to review proposed legislation, regulations, and policies related to efforts to protect the nation from terrorism (as well as the implementation of new and existing policies and legal authorities), in order to advise the President and executive branch agencies on ensuring that privacy and civil liberties are appropriately considered in their development and implementation. The primary purpose of this position is to perform duties as an Accountant, working under general supervision of the Chief Financial Officer, is to provide general accounting, financial management and financial reporting support. The accountant will be expected to process accounts payable/receivables, capitalization, advances/prepayments accounting, reconciliations and provide other assistance with the accounting/financial management workload of the Agency’s Office of the Chief Financial Officer. In addition, the Accountant will also be required to apply knowledge and interpret the Generally Accepted Accounting Principles (GAAP), US Standard General Ledger, Fund Balance with Treasury (FBwT), Capitalization of Property and Leases, Adjusted Trial balance (ATB), etc. Serve as a professional accountant with the ability to research and analyze various financial statements and disclosures to determine compliance with the GAAP, which may include applying accounting principles, techniques, and theories to solve complex financial issues. Provide technical advice and assistance by working independently with accounting, audit, or other multi-discipline teams to resolve accounting and financial issues to include the correction of differences identified between the subsidiary ledger balances and the control account balances in the general ledger. Prior experience conducting a wide range of acquisition lifecycle activities as it relates to the Federal Acquisition Regulation (FAR) guidelines and US Government contracting is preferred. **Major Duties and Responsibilities** 1. Provide general accounting, financial statement, and reporting support. 2. Create trial balance to financial statement crosswalks and other crosswalks. Apply the knowledge and understanding in the areas of financial reporting in compliance with the Generally Accepted Accounting Principles (GAAP) and Federal Accounting Standards Advisory Board (FASAB). 3. Perform a variety of activities related to the daily financial operations of the Agency's accounting system, such as review, analyze, compile, reconcile and report the financial data of the Agency on a monthly, quarterly, and annual basis. 4. Create budgetary to proprietary tie-outs. 5. Provide support to accounts payable, accrual estimates and accrual accounting. 6. Assist the agency with capital lease determinations. 7. Complete advances, prepayments, and related budgetary and proprietary accounts (such as GL 480200 - undelivered orders, obligations, prepaid/advanced, etc.) processes and procedures. 8. Review and analyze accounts payable/receivables documentation/billing, and other related financial management support. 9. Perform various elements of the federal government financial audit processes and procedures. 10. Interpret audit findings and analyze the corresponding regulations and the impacts to auditable processes. 11. Support and provide analysis to process and apply technical expertise to devise new or revised accounting policies/procedures, categorize accounting transactions, and improve accounting operations. 12. Document the design and implementation of complementary user entity controls. 13. Conduct studies and projects to improve policy, procedures, and controls in the organization to ensure adherence to proper budgetary and financial accounting standards and determine the feasibility of proposed and mandated accounting changes. 14. Serve as alternate Contracting Officer's Representative (COR), assisting Lead COR in procurement oversight. 15. Other duties assigned by the Chief Financial Officer, as needed. **Educational Requirements** Specialized study should include at minimum a bachelor’s degree in accounting or a degree in a related field such as business administration, finance, or public administration that included or was supplemented by 24 semester hours in accounting with five (5) to seven (7) years of accounting experience. The applicant must also possess active credentials as a Certified Public Accountant (CPA) or Certified Government Financial Manager (CGFM). Strong writing skills, proficiency in oral presentation and briefing, and subject matter expertise in financial management are essential for this position. **Application Process** Please send the following required documents to [PCLOB Jobs](mailto:[email protected]?subject=Accountant) with the title “Accountant”: Cover letter, resume, and writing sample (10 pages or less). All submitted materials must be at the UNCLASSIFIED level. If all the materials above are not received, your application will be evaluated solely on the information available and you may not receive full consideration or may not be considered eligible. Candidates selected for an interview may be asked to provide references and undergo a writing assessment. A candidate’s application may be considered for other eligible vacant positions at the agency. The candidate will be contacted if considered for another eligible vacant position. **Closing Date** A panel will convene to evaluate applications on a rolling basis until the position is filled. A review of your application will be made to determine whether you meet the job requirements. To determine if you are qualified for this job, your resume and supporting documentation will be evaluated. Candidates will be placed into categories of “best qualified”, “qualified”, and “not qualified”. If, after reviewing your resume and or supporting documentation, a determination is made that you have inflated your qualifications and/or experience, you may be placed in a different category. Please follow all instructions carefully. Errors or omissions may affect your categorization. **No Travel Expenses for Interview** Candidates from outside the Washington, D.C., area may be selected for a telephone or in-person interview. If selected for an in-person interview, any travel or lodging will be at the applicant’s personal expense. **Telework, Travel and Benefits** Telework may be made available per agency policy. If you use public transportation, part of your transportation costs may be subsidized. Our budget office can provide additional information on how this program is run. A career with the U.S. Government provides employees with a comprehensive benefits package.

101.214286

1,355

0.813691

eng_Latn

0.999318