hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0cd60f3497ea5d20c7bce3766698d57ad5ff012d | 150 | md | Markdown | changelog/2020.06.25/bug-fixes/908.md | lava/vast | 0bc9e3c12eb31ec50dd0270626d55e84b2255899 | [
"BSD-3-Clause"
] | 249 | 2019-08-26T01:44:45.000Z | 2022-03-26T14:12:32.000Z | changelog/2020.06.25/bug-fixes/908.md | 5l1v3r1/vast | a2cb4be879a13cef855da2c1d73083204aed4dff | [
"BSD-3-Clause"
] | 586 | 2019-08-06T13:10:36.000Z | 2022-03-31T08:31:00.000Z | changelog/2020.06.25/bug-fixes/908.md | satta/vast | 6c7587effd4265c4a5de23252bc7c7af3ef78bee | [
"BSD-3-Clause"
] | 37 | 2019-08-16T02:01:14.000Z | 2022-02-21T16:13:59.000Z | A bogus import process that assembled table slices with a greater number of
events than expected by the node was able to lead to wrong query results.
| 50 | 75 | 0.813333 | eng_Latn | 0.999993 |
0cd71974fd232fee3eb83d66c24ff7d9c8f7d9e4 | 38,466 | md | Markdown | CHANGELOG.md | echothreellc/echothree | 1744df7654097cc000e5eca32de127b5dc745302 | [
"Apache-2.0"
] | 1 | 2020-09-01T08:39:01.000Z | 2020-09-01T08:39:01.000Z | CHANGELOG.md | echothreellc/echothree | 1744df7654097cc000e5eca32de127b5dc745302 | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | echothreellc/echothree | 1744df7654097cc000e5eca32de127b5dc745302 | [
"Apache-2.0"
] | 1 | 2020-05-31T08:34:46.000Z | 2020-05-31T08:34:46.000Z | # Changelog
## 2021-10-17-01
* GraphQL Objects and Mutations for Selectors [152](https://gitlab.echothree.com/echothree/echothree/-/issues/152)
## 2021-10-03-01
* Guava 31.0.1-jre Upgrade [345](https://gitlab.echothree.com/echothree/echothree/-/issues/345)
## 2021-09-19-01
* GraphQL Objects and Mutations for Employee Search [335](https://gitlab.echothree.com/echothree/echothree/-/issues/335)
## 2021-09-05-01
* GraphQL Objects for Departments [319](https://gitlab.echothree.com/echothree/echothree/-/issues/319)
* Apache Lucene 8.9.0 Upgrade [326](https://gitlab.echothree.com/echothree/echothree/-/issues/326)
* jOOQ 3.15.2 Upgrade [327](https://gitlab.echothree.com/echothree/echothree/-/issues/327)
* ClassGraph 4.8.115 Upgrade [328](https://gitlab.echothree.com/echothree/echothree/-/issues/328)
* Error Prone 2.9.0 Upgrade [329](https://gitlab.echothree.com/echothree/echothree/-/issues/329)
* Gson 2.8.8 Upgrade [330](https://gitlab.echothree.com/echothree/echothree/-/issues/330)
* cucumber-java8/cucumber-junit 6.11.0 Upgrade [331](https://gitlab.echothree.com/echothree/echothree/-/issues/331)
* GraphQL Objects for Entity Attribute Groups [332](https://gitlab.echothree.com/echothree/echothree/-/issues/332)
* Add entityAttributeGroups Field to BaseEntityInstanceObject [333](https://gitlab.echothree.com/echothree/echothree/-/issues/333)
* GraphQL Objects for Employees [334](https://gitlab.echothree.com/echothree/echothree/-/issues/334)
## 2021-08-22-01
* GraphQL Objects for Companies [317](https://gitlab.echothree.com/echothree/echothree/-/issues/317)
* GraphQL Objects for Divisions [318](https://gitlab.echothree.com/echothree/echothree/-/issues/318)
* WildFly 24.0.1 Upgrade [322](https://gitlab.echothree.com/echothree/echothree/-/issues/322)
## 2021-08-08-01
* GraphQL Objects and Mutations for Item Search [212](https://gitlab.echothree.com/echothree/echothree/-/issues/212)
* GraphQL Objects and Mutations for Vendor Search [218](https://gitlab.echothree.com/echothree/echothree/-/issues/218)
* Add itemCount and items Fields to Item Category GraphQL Objects [313](https://gitlab.echothree.com/echothree/echothree/-/issues/313)
* Stop Sending Null Events to SentEventEventBus [316](https://gitlab.echothree.com/echothree/echothree/-/issues/316)
* GraphQL Objects for Customers [320](https://gitlab.echothree.com/echothree/echothree/-/issues/320)
* Add salesOrderSequence Field to Offer and Offer Use GraphQL Objects [321](https://gitlab.echothree.com/echothree/echothree/-/issues/321)
## 2021-07-25-01
* GraphQL Objects and Mutations for Filter Steps [157](https://gitlab.echothree.com/echothree/echothree/-/issues/157)
* MySQL Connector/J 8.0.26 Upgrade [311](https://gitlab.echothree.com/echothree/echothree/-/issues/311)
* Switch MySQL Collation to utf8mb4_0900_ai_ci [312](https://gitlab.echothree.com/echothree/echothree/-/issues/312)
## 2021-07-11-01
* ClassGraph 4.8.109 Upgrade [307](https://gitlab.echothree.com/echothree/echothree/-/issues/307)
* jOOQ 3.14.12 Upgrade [308](https://gitlab.echothree.com/echothree/echothree/-/issues/308)
* graphql-java 16.2 and graphql-java-annotations 8.3 Upgrades [309](https://gitlab.echothree.com/echothree/echothree/-/issues/309)
* NPE Thrown in FilterModificationEventRecorder [310](https://gitlab.echothree.com/echothree/echothree/-/issues/310)
## 2021-06-27-01
* WildFly 24.0.0 Upgrade [306](https://gitlab.echothree.com/echothree/echothree/-/issues/306)
## 2021-06-13-01
* Implement an EventBus to Handle Filter Modifications [305](https://gitlab.echothree.com/echothree/echothree/-/issues/305)
## 2021-05-30-01
* MySQL Connector/J 8.0.25 Upgrade [299](https://gitlab.echothree.com/echothree/echothree/-/issues/299)
* jOOQ 3.14.11 Upgrade [300](https://gitlab.echothree.com/echothree/echothree/-/issues/300)
* Error Prone 2.7.1 Upgrade [301](https://gitlab.echothree.com/echothree/echothree/-/issues/301)
* Gson 2.8.7 Upgrade [302](https://gitlab.echothree.com/echothree/echothree/-/issues/302)
* ICU4J 69.1 Upgrade [303](https://gitlab.echothree.com/echothree/echothree/-/issues/303)
* ClassGraph 4.8.106 Upgrade [304](https://gitlab.echothree.com/echothree/echothree/-/issues/304)
## 2021-05-16-01
* WildFly 23.0.2 Upgrade [298](https://gitlab.echothree.com/echothree/echothree/-/issues/298)
## 2021-05-02-01
* jOOQ 3.14.9 Upgrade [293](https://gitlab.echothree.com/echothree/echothree/-/issues/293)
* ClassGraph 4.8.104 Upgrade [294](https://gitlab.echothree.com/echothree/echothree/-/issues/294)
* WildFly 23.0.1 Upgrade [295](https://gitlab.echothree.com/echothree/echothree/-/issues/295)
* Guava 30.1.1-jre Upgrade [296](https://gitlab.echothree.com/echothree/echothree/-/issues/296)
* Apache Lucene 8.8.2 Upgrade [297](https://gitlab.echothree.com/echothree/echothree/-/issues/297)
## 2021-04-04-01
* WildFly 23.0.0 Upgrade [292](https://gitlab.echothree.com/echothree/echothree/-/issues/292)
## 2021-03-07-01
* jOOQ 3.14.8 Upgrade [286](https://gitlab.echothree.com/echothree/echothree/-/issues/286)
* Guava 30.1-jre Upgrade [287](https://gitlab.echothree.com/echothree/echothree/-/issues/287)
* ClassGraph 4.8.102 Upgrade [288](https://gitlab.echothree.com/echothree/echothree/-/issues/288)
* Apache Lucene 8.8.1 Upgrade [289](https://gitlab.echothree.com/echothree/echothree/-/issues/289)
* cucumber-java8/cucumber-junit 6.10.0 Upgrade [290](https://gitlab.echothree.com/echothree/echothree/-/issues/290)
* Apache Commons HttpCore 4.4.14 / HttpClient 4.5.13 Upgrade [291](https://gitlab.echothree.com/echothree/echothree/-/issues/291)
## 2021-02-21-01
* Error Prone 2.5.1 Upgrade [283](https://gitlab.echothree.com/echothree/echothree/-/issues/283)
* Amazon Corretto 11.0.10.9.1 Upgrade [284](https://gitlab.echothree.com/echothree/echothree/-/issues/284)
* Apache Lucene 8.8.0 Upgrade [285](https://gitlab.echothree.com/echothree/echothree/-/issues/285)
## 2021-02-07-01
* GraphQL Objects and Mutations for Filters [155](https://gitlab.echothree.com/echothree/echothree/-/issues/155)
* Create Sources JAR File [278](https://gitlab.echothree.com/echothree/echothree/-/issues/278)
* Create Documentation JAR File [279](https://gitlab.echothree.com/echothree/echothree/-/issues/279)
* WildFly 22.0.0 Upgrade [280](https://gitlab.echothree.com/echothree/echothree/-/issues/280)
* MySQL Connector/J 8.0.23 Upgrade [281](https://gitlab.echothree.com/echothree/echothree/-/issues/281)
* Add Filter Adjustments to Filter Kinds GraphQL Object [282](https://gitlab.echothree.com/echothree/echothree/-/issues/282)
## 2021-01-24-01
* GraphQL Objects and Mutations for Filter Adjustments [156](https://gitlab.echothree.com/echothree/echothree/-/issues/156)
* GraphQL Objects and Mutations for Filter Adjustment Amounts [193](https://gitlab.echothree.com/echothree/echothree/-/issues/193)
* GraphQL Objects and Mutations for Filter Adjustment Percents [194](https://gitlab.echothree.com/echothree/echothree/-/issues/194)
* GraphQL Objects and Mutations for Filter Adjustment Fixed Amounts [195](https://gitlab.echothree.com/echothree/echothree/-/issues/195)
* Package Mail Transfer CLI Application as Self-Contained JAR [258](https://gitlab.echothree.com/echothree/echothree/-/issues/258)
* Update US Harmonized Tariff Schedule Files [276](https://gitlab.echothree.com/echothree/echothree/-/issues/276)
## 2021-01-10-01
* Additional Password Recovery Questions [235](https://gitlab.echothree.com/echothree/echothree/-/issues/235)
* Package Form CLI Application as Self-Contained JAR [259](https://gitlab.echothree.com/echothree/echothree/-/issues/259)
* Package Data Loader CLI Application as Self-Contained JAR [260](https://gitlab.echothree.com/echothree/echothree/-/issues/260)
* Package Database CLI Application as Self-Contained JAR [261](https://gitlab.echothree.com/echothree/echothree/-/issues/261)
* Add Compilation Smoke Test Using docker-build Image [263](https://gitlab.echothree.com/echothree/echothree/-/issues/263)
* 2021 Copyright Update [274](https://gitlab.echothree.com/echothree/echothree/-/issues/274)
## 2020-12-27-01
* GraphQL Objects for Filter Adjustment Sources [148](https://gitlab.echothree.com/echothree/echothree/-/issues/148)
* GraphQL Objects for Filter Adjustment Types [149](https://gitlab.echothree.com/echothree/echothree/-/issues/149)
* GraphQL Objects for Selector Types [151](https://gitlab.echothree.com/echothree/echothree/-/issues/151)
* ClassGraph 4.8.95 Upgrade [188](https://gitlab.echothree.com/echothree/echothree/-/issues/188)
* WildFly 21.0.2 Upgrade [189](https://gitlab.echothree.com/echothree/echothree/-/issues/189)
* Add @GraphQLName to GraphQL Mutations Beginning with "set" [190](https://gitlab.echothree.com/echothree/echothree/-/issues/190)
* Use GraphQLID for IDs [198](https://gitlab.echothree.com/echothree/echothree/-/issues/198)
* Add GitLab Insights Configuration [241](https://gitlab.echothree.com/echothree/echothree/-/issues/241)
* Bootstrap 4.5.3 Upgrade [245](https://gitlab.echothree.com/echothree/echothree/-/issues/245)
* jQuery 3.5.1 Upgrade [246](https://gitlab.echothree.com/echothree/echothree/-/issues/246)
* Popper 2.6.0 Upgrade [247](https://gitlab.echothree.com/echothree/echothree/-/issues/247)
* Security for Filter Component [262](https://gitlab.echothree.com/echothree/echothree/-/issues/262)
## 2020-12-13-01
* GraphQL Objects for Filter Types [154](https://gitlab.echothree.com/echothree/echothree/-/issues/154)
* GraphQL Objects and Mutations for Sequences [172](https://gitlab.echothree.com/echothree/echothree/-/issues/172)
* Replace synchronized With ReentrantLock in EntityIdGenerator [184](https://gitlab.echothree.com/echothree/echothree/-/issues/184)
* jOOQ 3.14.4 Upgrade [186](https://gitlab.echothree.com/echothree/echothree/-/issues/186)
* Switch to Mattermost for Notifications [187](https://gitlab.echothree.com/echothree/echothree/-/issues/187)
## 2020-11-29-01
* jOOQ 3.14.3 Upgrade [179](https://gitlab.echothree.com/echothree/echothree/-/issues/179)
* WildFly 21.0.1 Upgrade [180](https://gitlab.echothree.com/echothree/echothree/-/issues/180)
* AssertJ 3.18.1 Upgrade [181](https://gitlab.echothree.com/echothree/echothree/-/issues/181)
* graphql-java-annotations 8.3 Upgrade [183](https://gitlab.echothree.com/echothree/echothree/-/issues/183)
* MySQL Connector/J 8.0.22 Upgrade [185](https://gitlab.echothree.com/echothree/echothree/-/issues/185)
## 2020-11-15-01
* GraphQL Objects and Mutations for Sequence Types [171](https://gitlab.echothree.com/echothree/echothree/-/issues/171)
* GraphQL Objects for Sequence Encoder Types [173](https://gitlab.echothree.com/echothree/echothree/-/issues/173)
* GraphQL Objects for Sequence Checksum Types [174](https://gitlab.echothree.com/echothree/echothree/-/issues/174)
* Guava 30.0-jre Upgrade [177](https://gitlab.echothree.com/echothree/echothree/-/issues/177)
* Apache Lucene 8.7.0 Upgrade [178](https://gitlab.echothree.com/echothree/echothree/-/issues/178)
## 2020-11-01-01
* GraphQL Objects and Mutations for Offer Uses [133](https://gitlab.echothree.com/echothree/echothree/-/issues/133)
* GraphQL Objects for Selector Kinds [150](https://gitlab.echothree.com/echothree/echothree/-/issues/150)
* GraphQL Objects for Filter Kinds [153](https://gitlab.echothree.com/echothree/echothree/-/issues/153)
* jOOQ 3.14.0 Upgrade [175](https://gitlab.echothree.com/echothree/echothree/-/issues/175)
* Apache Lucene 8.6.3 Upgrade [176](https://gitlab.echothree.com/echothree/echothree/-/issues/176)
## 2020-10-18-01
* GraphQL Objects and Mutations for Offers [127](https://gitlab.echothree.com/echothree/echothree/-/issues/127)
* GraphQL Objects and Mutations for Uses [131](https://gitlab.echothree.com/echothree/echothree/-/issues/131)
* Move All Control Classes into control Packages [165](https://gitlab.echothree.com/echothree/echothree/-/issues/165)
* Remove “Mood” from Profiles [166](https://gitlab.echothree.com/echothree/echothree/-/issues/166)
* WildFly 21.0.0 Upgrade [168](https://gitlab.echothree.com/echothree/echothree/-/issues/168)
* Separate Search Results from SearchControl [170](https://gitlab.echothree.com/echothree/echothree/-/issues/170)
## 2020-10-04-01
* Disallow Deleting the OfferUse If It's In Use [102](https://gitlab.echothree.com/echothree/echothree/-/issues/102)
* GraphQL Objects and Mutations for Offer Name Elements [128](https://gitlab.echothree.com/echothree/echothree/-/issues/128)
* GraphQL Objects and Mutations for Use Name Elements [132](https://gitlab.echothree.com/echothree/echothree/-/issues/132)
* Break Up OfferControl [138](https://gitlab.echothree.com/echothree/echothree/-/issues/138)
* cucumber-java8/cucumber-junit 6.7.0 Upgrade [139](https://gitlab.echothree.com/echothree/echothree/-/issues/139)
* ROME 1.15.0 Upgrade [140](https://gitlab.echothree.com/echothree/echothree/-/issues/140)
* graphql-java-annotations 8.1 Upgrade [141](https://gitlab.echothree.com/echothree/echothree/-/issues/141)
* ClassGraph 4.8.90 Upgrade [142](https://gitlab.echothree.com/echothree/echothree/-/issues/142)
* Spring 5.2.9.RELEASE Upgrade [145](https://gitlab.echothree.com/echothree/echothree/-/issues/145)
* JaCoCo 0.8.6 Upgrade [146](https://gitlab.echothree.com/echothree/echothree/-/issues/146)
* FilterEntranceSteps Missing Unique Index on FilterId/FilterStepId [147](https://gitlab.echothree.com/echothree/echothree/-/issues/147)
* Disallow Deleting the Offer If It's In Use [160](https://gitlab.echothree.com/echothree/echothree/-/issues/160)
* Disallow Deleting the Use If It's In Use [161](https://gitlab.echothree.com/echothree/echothree/-/issues/161)
* Disallow Deleting the UseType If It's In Use [162](https://gitlab.echothree.com/echothree/echothree/-/issues/162)
* PMD 6.28.0 Upgrade [164](https://gitlab.echothree.com/echothree/echothree/-/issues/164)
## 2020-09-20-01
* Add Source Tests [118](https://gitlab.echothree.com/echothree/echothree/-/issues/118)
* Add GetOfferChainType UC [119](https://gitlab.echothree.com/echothree/echothree/-/issues/119)
* Add GetUseNameElement UC [120](https://gitlab.echothree.com/echothree/echothree/-/issues/120)
* Add GetOfferNameElement UC [121](https://gitlab.echothree.com/echothree/echothree/-/issues/121)
* Apache Lucene 8.6.2 Upgrade [122](https://gitlab.echothree.com/echothree/echothree/-/issues/122)
* MySQL Connector/J 8.0.21 Upgrade [123](https://gitlab.echothree.com/echothree/echothree/-/issues/123)
* Update INSTALL.md's JDK, Ant and MySQL Versions [124](https://gitlab.echothree.com/echothree/echothree/-/issues/124)
* Break Up OrderControl [125](https://gitlab.echothree.com/echothree/echothree/-/issues/125)
* GraphQL Objects and Mutations for Use Types [137](https://gitlab.echothree.com/echothree/echothree/-/issues/137)
## 2020-09-06-01
* Add Offer Item Price Tests [86](https://gitlab.echothree.com/echothree/echothree/-/issues/86)
* Add Use Type Tests [115](https://gitlab.echothree.com/echothree/echothree/-/issues/115)
* Add Use Tests [116](https://gitlab.echothree.com/echothree/echothree/-/issues/116)
* Add Offer Use Tests [117](https://gitlab.echothree.com/echothree/echothree/-/issues/117)
## 2020-08-23-01
* Create Purchase Order [38](https://gitlab.echothree.com/echothree/echothree/-/issues/38)
* Add Offer Tests [84](https://gitlab.echothree.com/echothree/echothree/-/issues/84)
* Add Offer Item Tests [85](https://gitlab.echothree.com/echothree/echothree/-/issues/85)
* Allow Cancelation of a Purchase Order During Entry [110](https://gitlab.echothree.com/echothree/echothree/-/issues/110)
* Add Script to Configure WildFly and Deploy Application [111](https://gitlab.echothree.com/echothree/echothree/-/issues/111)
* Apache Lucene 8.6.1 Upgrade [112](https://gitlab.echothree.com/echothree/echothree/-/issues/112)
* Rename Cancelled to Canceled [113](https://gitlab.echothree.com/echothree/echothree/-/issues/113)
## 2020-08-09-01
* jOOQ 3.13.4 Upgrade [105](https://gitlab.echothree.com/echothree/echothree/-/issues/105)
* Apache Lucene 8.6.0 Upgrade [106](https://gitlab.echothree.com/echothree/echothree/-/issues/106)
## 2020-07-26-01
* Add Content Collection Tests [78](https://gitlab.echothree.com/echothree/echothree/-/issues/78)
* Add Content Catalog Tests [79](https://gitlab.echothree.com/echothree/echothree/-/issues/79)
* Add Content Category Tests [80](https://gitlab.echothree.com/echothree/echothree/-/issues/80)
* Add Content Category Item Tests [81](https://gitlab.echothree.com/echothree/echothree/-/issues/81)
## 2020-07-12-01
* NPE from CreatePurchaseInvoice UC [101](https://gitlab.echothree.com/echothree/echothree/-/issues/101)
* Error Prone 2.4.0 Upgrade [88](https://gitlab.echothree.com/echothree/echothree/-/issues/88)
* graphql-java-annotations 8.0.1 Upgrade [90](https://gitlab.echothree.com/echothree/echothree/-/issues/90)
* Apache FreeMarker 2.3.30 Upgrade [91](https://gitlab.echothree.com/echothree/echothree/-/issues/91)
* ROME 1.14.1 Upgrade [92](https://gitlab.echothree.com/echothree/echothree/-/issues/92)
* Apache Commons CLI 1.4 Upgrade [93](https://gitlab.echothree.com/echothree/echothree/-/issues/93)
* Apache Commons Codec 1.14 Upgrade [94](https://gitlab.echothree.com/echothree/echothree/-/issues/94)
* Apache Commons Digester 1.8.1 Upgrade [95](https://gitlab.echothree.com/echothree/echothree/-/issues/95)
* Apache Commons IO 2.7 Upgrade [96](https://gitlab.echothree.com/echothree/echothree/-/issues/96)
* Apache Commons Logging 1.2 Upgrade [97](https://gitlab.echothree.com/echothree/echothree/-/issues/97)
* cucumber-java8/cucumber-junit 6.2.2 Upgrade [98](https://gitlab.echothree.com/echothree/echothree/-/issues/98)
* ClassGraph 4.8.87 Upgrade [99](https://gitlab.echothree.com/echothree/echothree/-/issues/99)
* WildFly 20.0.1 Upgrade [100](https://gitlab.echothree.com/echothree/echothree/-/issues/100)
## 2020-06-28-01
* Add Vendor Tests [76](https://gitlab.echothree.com/echothree/echothree/-/issues/76)
* Add Vendor Item Tests [77](https://gitlab.echothree.com/echothree/echothree/-/issues/77)
* Sales Invoices and Purchase Invoices Have Same Description [82](https://gitlab.echothree.com/echothree/echothree/-/issues/82)
* Add Item Price Tests [83](https://gitlab.echothree.com/echothree/echothree/-/issues/83)
* Add Vendor Item Cost Tests [87](https://gitlab.echothree.com/echothree/echothree/-/issues/87)
## 2020-06-14-01
* Add FOB Terms and Conditions to OrderDetails [62](https://gitlab.echothree.com/echothree/echothree/-/issues/62)
* Add FOB Terms and Conditions to InvoiceDetails [63](https://gitlab.echothree.com/echothree/echothree/-/issues/63)
* Different ULIDs for Same Object When Generated [65](https://gitlab.echothree.com/echothree/echothree/-/issues/65)
* WildFly 20.0.0 Upgrade [66](https://gitlab.echothree.com/echothree/echothree/-/issues/66)
* Add Workflow for Purchase Orders [67](https://gitlab.echothree.com/echothree/echothree/-/issues/67)
* Apache Lucene 8.5.2 Upgrade [68](https://gitlab.echothree.com/echothree/echothree/-/issues/68)
* Implement DefaultFreeOnBoard for Customer Types [69](https://gitlab.echothree.com/echothree/echothree/-/issues/69)
* Implement DefaultFreeOnBoard for Vendor Types [70](https://gitlab.echothree.com/echothree/echothree/-/issues/70)
* jOOQ 3.13.2 Upgrade [72](https://gitlab.echothree.com/echothree/echothree/-/issues/72)
* ICU4J 67.1 Upgrade [73](https://gitlab.echothree.com/echothree/echothree/-/issues/73)
* ClassGraph 4.8.83 Upgrade [74](https://gitlab.echothree.com/echothree/echothree/-/issues/74)
* graphql-java 15.0 Upgrade [75](https://gitlab.echothree.com/echothree/echothree/-/issues/75)
## 2020-05-31-01
* Add Payment Processor Transactions [9](https://gitlab.echothree.com/echothree/echothree/-/issues/9)
* Add Payment Processor Transaction Codes [10](https://gitlab.echothree.com/echothree/echothree/-/issues/10)
* Convert Payment Method Type Party Types to Versioned Entity [26](https://gitlab.echothree.com/echothree/echothree/-/issues/26)
* Separate Lot Aliases from InventoryControl [53](https://gitlab.echothree.com/echothree/echothree/-/issues/53)
* Basic Lot Implementation With Controller and TOs [54](https://gitlab.echothree.com/echothree/echothree/-/issues/54)
* Separate Lot Times from InventoryControl [55](https://gitlab.echothree.com/echothree/echothree/-/issues/55)
* Separate Payment Processors from PaymentControl [56](https://gitlab.echothree.com/echothree/echothree/-/issues/56)
* Move Payment Method Type Party Types to PaymentMethodTypeControl from PaymentControl [57](https://gitlab.echothree.com/echothree/echothree/-/issues/57)
* Separate Payment Methods from PaymentControl [58](https://gitlab.echothree.com/echothree/echothree/-/issues/58)
* Separate Party Payment Methods from PaymentControl [59](https://gitlab.echothree.com/echothree/echothree/-/issues/59)
* MySQL Connector/J 8.0.20 Upgrade [60](https://gitlab.echothree.com/echothree/echothree/-/issues/60)
* Add FOB Terms and Conditions [61](https://gitlab.echothree.com/echothree/echothree/-/issues/61)
* Additional Invoice Types [64](https://gitlab.echothree.com/echothree/echothree/-/issues/64)
## 2020-05-17-01
* Add Payment Processor Type Actions [8](https://gitlab.echothree.com/echothree/echothree/-/issues/8)
* Add Payment Processor Result Codes [11](https://gitlab.echothree.com/echothree/echothree/-/issues/11)
* Add Payment Processor Type Code Types [12](https://gitlab.echothree.com/echothree/echothree/-/issues/12)
* Add Payment Processor Type Codes [13](https://gitlab.echothree.com/echothree/echothree/-/issues/13)
* Add Payment Processor Actions [22](https://gitlab.echothree.com/echothree/echothree/-/issues/22)
* Convert Payment Method Types to Versioned Entities [25](https://gitlab.echothree.com/echothree/echothree/-/issues/25)
* Convert Payment Processor Types to Versioned Entities [27](https://gitlab.echothree.com/echothree/echothree/-/issues/27)
* Add Optional Parent Shipment Package to Shipment Package Details [28](https://gitlab.echothree.com/echothree/echothree/-/issues/28)
* Rename Box Type to Package Type [33](https://gitlab.echothree.com/echothree/echothree/-/issues/33)
* WildFly 19.1.0 Upgrade [35](https://gitlab.echothree.com/echothree/echothree/-/issues/35)
* Separate BillingControl from PaymentControl [36](https://gitlab.echothree.com/echothree/echothree/-/issues/36)
* Remove Lot Types [46](https://gitlab.echothree.com/echothree/echothree/-/issues/46)
* Guava 29.0-jre Upgrade [47](https://gitlab.echothree.com/echothree/echothree/-/issues/47)
## 2020-05-03-01
* GraphQL Object Addition for appearance (core) [E3-2258](https://www.echothree.com/bugzilla/show_bug.cgi?id=2258)
* Cucumber Tests for Base Encryption Keys (core) [E3-2564](https://www.echothree.com/bugzilla/show_bug.cgi?id=2564)
* Cucumber Tests for Party Payment Methods (payment) [E3-2565](https://www.echothree.com/bugzilla/show_bug.cgi?id=2565)
* Prevent Deletion of Contact Mechanism Used By Party Payment Method (contact) [E3-2566](https://www.echothree.com/bugzilla/show_bug.cgi?id=2566)
* Billing Contact Mechanism Missing When Editing Customer Payment Method (ui-main) [E3-2567](https://www.echothree.com/bugzilla/show_bug.cgi?id=2567)
* Reduce Repetition of Persona Names in Tests (miscellaneous) [E3-2568](https://www.echothree.com/bugzilla/show_bug.cgi?id=2568)
* Lucene 8.5.0 Upgrade (index) [E3-2569](https://www.echothree.com/bugzilla/show_bug.cgi?id=2569)
* Cucumber Tests for Entity Attributes (index) [E3-2570](https://www.echothree.com/bugzilla/show_bug.cgi?id=2570)
* Disable Non-Credit Card Payment Methods [1](https://gitlab.echothree.com/echothree/echothree/-/issues/1)
* Add Sequence Encoder for Reverse/Swap [2](https://gitlab.echothree.com/echothree/echothree/-/issues/2)
* Add Sequence Checksum to Hash All Characters [3](https://gitlab.echothree.com/echothree/echothree/-/issues/3)
* Increase Length of Default Sequence Types [4](https://gitlab.echothree.com/echothree/echothree/-/issues/4)
* Start Beginning Sequences at Non-Zero [5](https://gitlab.echothree.com/echothree/echothree/-/issues/5)
* Apache Lucene 8.5.1 Upgrade [6](https://gitlab.echothree.com/echothree/echothree/-/issues/6)
* Add Payment Processor Action Types [7](https://gitlab.echothree.com/echothree/echothree/-/issues/7)
* Add MOD 10 Checksum for Sequences [16](https://gitlab.echothree.com/echothree/echothree/-/issues/16)
* Switch Sequence Types to Use Reverse/Swap Encoding and MOD 10 Checksum [17](https://gitlab.echothree.com/echothree/echothree/-/issues/17)
## 2020-03-19-01
* Identify UC Should Include Security Checks Against Invoking Party (search) [E3-1962](https://www.echothree.com/bugzilla/show_bug.cgi?id=1962)
* GraphQL Object Additions for componentVendors and componentVendor (core) [E3-2249](https://www.echothree.com/bugzilla/show_bug.cgi?id=2249)
* GraphQL Object Additions for entityTypes and entityType (core) [E3-2250](https://www.echothree.com/bugzilla/show_bug.cgi?id=2250)
* GraphQL Object Addition for entityInstance (core) [E3-2260](https://www.echothree.com/bugzilla/show_bug.cgi?id=2260)
* Handle Customers in Universal Search (search) [E3-2510](https://www.echothree.com/bugzilla/show_bug.cgi?id=2510)
* Handle Vendors in Universal Search (search) [E3-2511](https://www.echothree.com/bugzilla/show_bug.cgi?id=2511)
* Handle Item Descriptions in Universal Search (search) [E3-2512](https://www.echothree.com/bugzilla/show_bug.cgi?id=2512)
* jOOQ 3.12.4 Upgrade (miscellaneous) [E3-2543](https://www.echothree.com/bugzilla/show_bug.cgi?id=2543)
* Add Security to Employee Search UCs (search) [E3-2544](https://www.echothree.com/bugzilla/show_bug.cgi?id=2544)
* jOOQ 3.13.0 Upgrade (miscellaneous) [E3-2545](https://www.echothree.com/bugzilla/show_bug.cgi?id=2545)
* Move Functions for Managing Base Keys to Client Library (core) [E3-2547](https://www.echothree.com/bugzilla/show_bug.cgi?id=2547)
* Apache Lucene 8.4.1 Upgrade (index) [E3-2548](https://www.echothree.com/bugzilla/show_bug.cgi?id=2548)
* Correct Spelling of Maintenance (search) [E3-2549](https://www.echothree.com/bugzilla/show_bug.cgi?id=2549)
* Contributor Covenant Code of Conduct 2.0 Upgrade (miscellaneous) [E3-2550](https://www.echothree.com/bugzilla/show_bug.cgi?id=2550)
* Bootstrap 4.4.1 / Popper.js 1.16.1 / jQuery 3.4.1 Upgrade (miscellaneous) [E3-2551](https://www.echothree.com/bugzilla/show_bug.cgi?id=2551)
* Update Customer Search and Review Appearance (ui-main) [E3-2554](https://www.echothree.com/bugzilla/show_bug.cgi?id=2554)
* graphql-java 14.0 / graphql-java-annotations 8.0 Upgrades (graphql) [E3-2555](https://www.echothree.com/bugzilla/show_bug.cgi?id=2555)
* Cucumber 5.4.2 Upgrade (miscellaneous) [E3-2556](https://www.echothree.com/bugzilla/show_bug.cgi?id=2556)
* WildFly 19.0.0 Upgrade (miscellaneous) [E3-2557](https://www.echothree.com/bugzilla/show_bug.cgi?id=2557)
* ICU4J 66.1 Upgrade (miscellaneous) [E3-2558](https://www.echothree.com/bugzilla/show_bug.cgi?id=2558)
* jOOQ 3.13.1 Upgrade (miscellaneous) [E3-2559](https://www.echothree.com/bugzilla/show_bug.cgi?id=2559)
* MySQL Connector/J 8.0.19 Upgrade (miscellaneous) [E3-2560](https://www.echothree.com/bugzilla/show_bug.cgi?id=2560)
* ClassGraph 4.8.65 Upgrade (miscellaneous) [E3-2561](https://www.echothree.com/bugzilla/show_bug.cgi?id=2561)
* Cucumber 5.5.0 Upgrade (miscellaneous) [E3-2562](https://www.echothree.com/bugzilla/show_bug.cgi?id=2562)
## 2020-01-15-01
* Relax Security for Geo Component (geo) [E3-2509](https://www.echothree.com/bugzilla/show_bug.cgi?id=2509)
* graphql-java-annotations 7.2.1 Upgrade (graphql) [E3-2514](https://www.echothree.com/bugzilla/show_bug.cgi?id=2514)
* WildFly 18.0.0 Upgrade (miscellaneous) [E3-2515](https://www.echothree.com/bugzilla/show_bug.cgi?id=2515)
* Guava 28.1-jre Upgrade (miscellaneous) [E3-2516](https://www.echothree.com/bugzilla/show_bug.cgi?id=2516)
* jOOQ 3.12.3 Upgrade (miscellaneous) [E3-2517](https://www.echothree.com/bugzilla/show_bug.cgi?id=2517)
* Apache Ivy 2.5.0 Upgrade (miscellaneous) [E3-2518](https://www.echothree.com/bugzilla/show_bug.cgi?id=2518)
* MySQL Connector/J 8.0.18 Upgrade (miscellaneous) [E3-2519](https://www.echothree.com/bugzilla/show_bug.cgi?id=2519)
* Add CODEOWNERS for GitLab (miscellaneous) [E3-2520](https://www.echothree.com/bugzilla/show_bug.cgi?id=2520)
* WildFly 18.0.1 Upgrade (miscellaneous) [E3-2521](https://www.echothree.com/bugzilla/show_bug.cgi?id=2521)
* GraphQL Mutations Resulting in IllegalStateException (graphql) [E3-2522](https://www.echothree.com/bugzilla/show_bug.cgi?id=2522)
* 2020 Copyright Update (miscellaneous) [E3-2523](https://www.echothree.com/bugzilla/show_bug.cgi?id=2523)
* Lucene 8.4.0 Upgrade (index) [E3-2524](https://www.echothree.com/bugzilla/show_bug.cgi?id=2524)
* ClassGraph 4.8.59 Upgrade (miscellaneous) [E3-2525](https://www.echothree.com/bugzilla/show_bug.cgi?id=2525)
* ICU4J 65.1 Upgrade (miscellaneous) [E3-2526](https://www.echothree.com/bugzilla/show_bug.cgi?id=2526)
* Commons-FileUpload 1.4 Upgrade (miscellaneous) [E3-2527](https://www.echothree.com/bugzilla/show_bug.cgi?id=2527)
* Guava 28.2-jre Upgrade (miscellaneous) [E3-2528](https://www.echothree.com/bugzilla/show_bug.cgi?id=2528)
* Spring 5.0.15.RELEASE Upgrade (Except spring-struts) (miscellaneous) [E3-2529](https://www.echothree.com/bugzilla/show_bug.cgi?id=2529)
* taglibs.jsp References taglib Not Included in Deployed Application (ui-cms) [E3-2530](https://www.echothree.com/bugzilla/show_bug.cgi?id=2530)
* Gson 2.8.6 Upgrade (miscellaneous) [E3-2531](https://www.echothree.com/bugzilla/show_bug.cgi?id=2531)
* Cucumber 4.8.0 Upgrade (miscellaneous) [E3-2532](https://www.echothree.com/bugzilla/show_bug.cgi?id=2532)
* Apache Commons HttpCore 4.4.12 / HttpClient 4.5.10 Upgrade (miscellaneous) [E3-2533](https://www.echothree.com/bugzilla/show_bug.cgi?id=2533)
* JaCoCo 0.8.5 Upgrade (miscellaneous) [E3-2534](https://www.echothree.com/bugzilla/show_bug.cgi?id=2534)
* ROME 1.12.2 Upgrade (miscellaneous) [E3-2535](https://www.echothree.com/bugzilla/show_bug.cgi?id=2535)
* Remove Groovy (miscellaneous) [E3-2536](https://www.echothree.com/bugzilla/show_bug.cgi?id=2536)
* FreeMarker 2.3.29 Upgrade (miscellaneous) [E3-2537](https://www.echothree.com/bugzilla/show_bug.cgi?id=2537)
* Remove Quartz (service-job) [E3-2538](https://www.echothree.com/bugzilla/show_bug.cgi?id=2538)
* Reactive Streams 1.0.3 Upgrade (miscellaneous) [E3-2539](https://www.echothree.com/bugzilla/show_bug.cgi?id=2539)
* assertj-core 3.14.0 / assertj-guava 3.3.0 Upgrade (miscellaneous) [E3-2540](https://www.echothree.com/bugzilla/show_bug.cgi?id=2540)
* SLF4J 1.7.30 Upgrade (miscellaneous) [E3-2541](https://www.echothree.com/bugzilla/show_bug.cgi?id=2541)
## 2019-10-09-01
* graphql-java 12.0 and graphql-java-annotations 7.0 Upgrades (graphql) [E3-2443](https://www.echothree.com/bugzilla/show_bug.cgi?id=2443)
* Remove GraphQL Endpoint Under /main (ui-main) [E3-2492](https://www.echothree.com/bugzilla/show_bug.cgi?id=2492)
* Include Javadoc and Source JAR Files in Project Libraries (miscellaneous) [E3-2493](https://www.echothree.com/bugzilla/show_bug.cgi?id=2493)
* Add Security to Contact Email Address, Postal Address, Telephone, and Web Address UCs (contact) [E3-2494](https://www.echothree.com/bugzilla/show_bug.cgi?id=2494)
* CORS Issue with Apollo GraphQL 8 (service-graphql) [E3-2496](https://www.echothree.com/bugzilla/show_bug.cgi?id=2496)
* Apache Lucene 8.1.1 Upgrade (index) [E3-2497](https://www.echothree.com/bugzilla/show_bug.cgi?id=2497)
* WildFly 17.0.0 Upgrade (miscellaneous) [E3-2498](https://www.echothree.com/bugzilla/show_bug.cgi?id=2498)
* graphql-java 13.0 Upgrade (graphql) [E3-2499](https://www.echothree.com/bugzilla/show_bug.cgi?id=2499)
* ClassGraph 4.8.43 Upgrade (miscellaneous) [E3-2500](https://www.echothree.com/bugzilla/show_bug.cgi?id=2500)
* Guava 28.0-jre Upgrade (miscellaneous) [E3-2501](https://www.echothree.com/bugzilla/show_bug.cgi?id=2501)
* Move WorkflowEntranceStep and WorkflowDestinationStep Security Role Groups (workflow) [E3-2503](https://www.echothree.com/bugzilla/show_bug.cgi?id=2503)
* Security for Workflow Component (workflow) [E3-2504](https://www.echothree.com/bugzilla/show_bug.cgi?id=2504)
* Add Google Analytics to Generated Javadoc (miscellaneous) [E3-2505](https://www.echothree.com/bugzilla/show_bug.cgi?id=2505)
* Allow Start/Reload/Shutdown of WildFly Using Ant (miscellaneous) [E3-2506](https://www.echothree.com/bugzilla/show_bug.cgi?id=2506)
* Apache Lucene 8.2.0 Upgrade (index) [E3-2507](https://www.echothree.com/bugzilla/show_bug.cgi?id=2507)
* WildFly 17.0.1 Upgrade (miscellaneous) [E3-2508](https://www.echothree.com/bugzilla/show_bug.cgi?id=2508)
* Use var to Declare Model Controllers (miscellaneous) [E3-2495](https://www.echothree.com/bugzilla/show_bug.cgi?id=2495)
## 2019-05-12-01
* Cucumber Tests Incompatible with JDK 11 (miscellaneous) [E3-2468](https://www.echothree.com/bugzilla/show_bug.cgi?id=2468)
* GraphQL Queries for Content Component (content) [E3-2475](https://www.echothree.com/bugzilla/show_bug.cgi?id=2475)
* AdoptOpenJDK jdk-11.0.2+7 Upgrade (miscellaneous) [E3-2476](https://www.echothree.com/bugzilla/show_bug.cgi?id=2476)
* Add Mirrors, License and Javadoc Badges to README.md (miscellaneous) [E3-2477](https://www.echothree.com/bugzilla/show_bug.cgi?id=2477)
* WildFly 16.0.0 Upgrade (miscellaneous) [E3-2478](https://www.echothree.com/bugzilla/show_bug.cgi?id=2478)
* jOOQ 3.11.10 Upgrade (miscellaneous) [E3-2479](https://www.echothree.com/bugzilla/show_bug.cgi?id=2479)
* ClassGraph 4.8.14 Upgrade (miscellaneous) [E3-2480](https://www.echothree.com/bugzilla/show_bug.cgi?id=2480)
* Apache Lucene 8.0.0 Upgrade (index) [E3-2481](https://www.echothree.com/bugzilla/show_bug.cgi?id=2481)
* Bootstrap 4.3.1 / Popper.js 1.14.7 Upgrade (miscellaneous) [E3-2482](https://www.echothree.com/bugzilla/show_bug.cgi?id=2482)
* ClassGraph 4.8.21 Upgrade (miscellaneous) [E3-2483](https://www.echothree.com/bugzilla/show_bug.cgi?id=2483)
* Guava 27.1-jre Upgrade (miscellaneous) [E3-2484](https://www.echothree.com/bugzilla/show_bug.cgi?id=2484)
* Error Prone 2.3.3 Upgrade (miscellaneous) [E3-2485](https://www.echothree.com/bugzilla/show_bug.cgi?id=2485)
* Cucumber 4.2.6 Upgrade (miscellaneous) [E3-2486](https://www.echothree.com/bugzilla/show_bug.cgi?id=2486)
* AdoptOpenJDK jdk-11.0.3+7 Upgrade (miscellaneous) [E3-2487](https://www.echothree.com/bugzilla/show_bug.cgi?id=2487)
* jOOQ 3.11.11 Upgrade (miscellaneous) [E3-2488](https://www.echothree.com/bugzilla/show_bug.cgi?id=2488)
* ClassGraph 4.8.28 Upgrade (miscellaneous) [E3-2489](https://www.echothree.com/bugzilla/show_bug.cgi?id=2489)
* Cucumber 4.3.0 Upgrade (miscellaneous) [E3-2490](https://www.echothree.com/bugzilla/show_bug.cgi?id=2490)
## 2019-01-12-01
* GraphQL Object Addition for userVisit (user) [E3-2287](https://www.echothree.com/bugzilla/show_bug.cgi?id=2287)
* Mark UserKey Cookie as Secure Only (ui-main) [E3-2312](https://www.echothree.com/bugzilla/show_bug.cgi?id=2312)
* GraphqQL Endpoint (service-graphql) [E3-2444](https://www.echothree.com/bugzilla/show_bug.cgi?id=2444)
* Publish Source Code (miscellaneous) [E3-2436](https://www.echothree.com/bugzilla/show_bug.cgi?id=2436)
* ClassGraph 4.4.8 Upgrade (miscellaneous) [E3-2437](https://www.echothree.com/bugzilla/show_bug.cgi?id=2437)
* WildFly 14.0.1 Upgrade (miscellaneous) [E3-2438](https://www.echothree.com/bugzilla/show_bug.cgi?id=2438)
* Java SE 8u191 Upgrade (miscellaneous) [E3-2439](https://www.echothree.com/bugzilla/show_bug.cgi?id=2439)
* Switch Creation of echothree-build.properties to Use git (miscellaneous) [E3-2440](https://www.echothree.com/bugzilla/show_bug.cgi?id=2440)
* Add List of IDEs and Update Mirrors (miscellaneous) [E3-2441](https://www.echothree.com/bugzilla/show_bug.cgi?id=2441)
* Move Classes in remote Packages to common Packages (miscellaneous) [E3-2442](https://www.echothree.com/bugzilla/show_bug.cgi?id=2442)
* ClassGraph 4.4.12 Upgrade (miscellaneous) [E3-2449](https://www.echothree.com/bugzilla/show_bug.cgi?id=2449)
* jOOQ 3.11.7 Upgrade (miscellaneous) [E3-2450](https://www.echothree.com/bugzilla/show_bug.cgi?id=2450)
* Convert ExecuteGraphQl UC to Execute Asynchronously (graphql) [E3-2452](https://www.echothree.com/bugzilla/show_bug.cgi?id=2452)
* Remove Duplicate Apache License Header (miscellaneous) [E3-2453](https://www.echothree.com/bugzilla/show_bug.cgi?id=2453)
* Convert Content Page Layouts and Their Descriptions to Versioned Entities (content) [E3-2454](https://www.echothree.com/bugzilla/show_bug.cgi?id=2454)
* Convert Content Page Area Types and Their Descriptions to Versioned Entities (content) [E3-2455](https://www.echothree.com/bugzilla/show_bug.cgi?id=2455)
* Remove Deprecated StandardFilter from DictionaryAnalyzer (index) [E3-2457](https://www.echothree.com/bugzilla/show_bug.cgi?id=2457)
* Consolidate ResultInvocationHandler and FormInvocationHandler (miscellaneous) [E3-2458](https://www.echothree.com/bugzilla/show_bug.cgi?id=2458)
* Incorrect Security Role Group for Offer Chain Type UCs (offer) [E3-2459](https://www.echothree.com/bugzilla/show_bug.cgi?id=2459)
* UCs and Queries to Set Preferred Language, Currency, Time Zone and Date Time Format (user) [E3-2460](https://www.echothree.com/bugzilla/show_bug.cgi?id=2460)
* ClassGraph 4.6.10 Upgrade (miscellaneous) [E3-2461](https://www.echothree.com/bugzilla/show_bug.cgi?id=2461)
* Lucene 7.6.0 Upgrade (index) [E3-2462](https://www.echothree.com/bugzilla/show_bug.cgi?id=2462)
* 2019 Copyright Update (miscellaneous) [E3-2463](https://www.echothree.com/bugzilla/show_bug.cgi?id=2463)
* WildFly 15.0.0 Upgrade (miscellaneous) [E3-2464](https://www.echothree.com/bugzilla/show_bug.cgi?id=2464)
* Error Prone 2.3.2 and JDK 11 Upgrade (miscellaneous) [E3-2465](https://www.echothree.com/bugzilla/show_bug.cgi?id=2465)
* Cucumber 4.2.0 Upgrade (miscellaneous) [E3-2466](https://www.echothree.com/bugzilla/show_bug.cgi?id=2466)
* Convert ContentSections, ContentCategories and ContentPageAreaTypes to enums (content) [E3-2467](https://www.echothree.com/bugzilla/show_bug.cgi?id=2467)
* Publish Javadoc to Echo Three Website for master Branch (miscellaneous) [E3-2469](https://www.echothree.com/bugzilla/show_bug.cgi?id=2469)
* WildFly 15.0.1 Upgrade (miscellaneous) [E3-2470](https://www.echothree.com/bugzilla/show_bug.cgi?id=2470)
* jOOQ 3.11.9 Upgrade (miscellaneous) [E3-2471](https://www.echothree.com/bugzilla/show_bug.cgi?id=2471)
* ClassGraph 4.6.12 Upgrade (miscellaneous) [E3-2472](https://www.echothree.com/bugzilla/show_bug.cgi?id=2472)
| 82.017058 | 164 | 0.767327 | yue_Hant | 0.326626 |
0cd737de03d182daa5a06c87aae39305cbf74444 | 5,425 | md | Markdown | repos/fsharp/remote/10.10-netcore.md | Ghostglass/repo-info | 30b319599d3fce07a3da000e32dbc42523f7f8fa | [
"Apache-2.0"
] | 1 | 2021-03-17T00:49:51.000Z | 2021-03-17T00:49:51.000Z | repos/fsharp/remote/10.10-netcore.md | Ghostglass/repo-info | 30b319599d3fce07a3da000e32dbc42523f7f8fa | [
"Apache-2.0"
] | null | null | null | repos/fsharp/remote/10.10-netcore.md | Ghostglass/repo-info | 30b319599d3fce07a3da000e32dbc42523f7f8fa | [
"Apache-2.0"
] | null | null | null | ## `fsharp:10.10-netcore`
```console
$ docker pull fsharp@sha256:1eb52fe2fd0222384a05ab1cf8a600be6d0d8694472fcd36b9585b62fc1aedb2
```
- Manifest MIME: `application/vnd.docker.distribution.manifest.list.v2+json`
- Platforms:
- linux; amd64
### `fsharp:10.10-netcore` - linux; amd64
```console
$ docker pull fsharp@sha256:c73384958aaa8784a8cdc25f43ad3a128b0c89eef52415017b5edd6ab0a1ddf3
```
- Docker Version: 19.03.12
- Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json`
- Total Size: **333.0 MB (332975525 bytes)**
(compressed transfer size, not on-disk size)
- Image ID: `sha256:670c13e0647eee0bf1cb9bf0593a04187b731e1b0307f040d5629cedba7e7600`
- Default Command: `["dotnet","fsi"]`
```dockerfile
# Fri, 12 Mar 2021 02:20:40 GMT
ADD file:3c32f1cd03198e141dd233a7ffd13444157d4150ad917d548f3ee9bf5953ce22 in /
# Fri, 12 Mar 2021 02:20:41 GMT
CMD ["bash"]
# Fri, 12 Mar 2021 09:04:02 GMT
LABEL maintainer=Dave Curylo <[email protected]>, Steve Desmond <[email protected]>
# Fri, 12 Mar 2021 09:04:02 GMT
ENV MONO_THREADS_PER_CPU=50
# Fri, 12 Mar 2021 09:13:49 GMT
RUN MONO_VERSION=6.10.0.104 && FSHARP_VERSION=10.2.3 && FSHARP_BASENAME=fsharp-$FSHARP_VERSION && FSHARP_ARCHIVE=$FSHARP_VERSION.tar.gz && FSHARP_ARCHIVE_URL=https://github.com/fsharp/fsharp/archive/$FSHARP_VERSION.tar.gz && export GNUPGHOME="$(mktemp -d)" && apt-get update && apt-get --no-install-recommends install -y gnupg dirmngr ca-certificates apt-transport-https && apt-key adv --batch --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF && echo "deb https://download.mono-project.com/repo/debian stable-buster/snapshots/$MONO_VERSION main" | tee /etc/apt/sources.list.d/mono-official-stable.list && apt-get update -y && apt-get --no-install-recommends install -y pkg-config make nuget mono-devel msbuild ca-certificates-mono locales && rm -rf /var/lib/apt/lists/* && echo 'en_US.UTF-8 UTF-8' > /etc/locale.gen && /usr/sbin/locale-gen && mkdir -p /tmp/src && cd /tmp/src && printf "namespace a { class b { public static void Main(string[] args) { new System.Net.WebClient().DownloadFile(\"%s\", \"%s\");}}}" $FSHARP_ARCHIVE_URL $FSHARP_ARCHIVE > download-fsharp.cs && mcs download-fsharp.cs && mono download-fsharp.exe && rm download-fsharp.exe download-fsharp.cs && tar xf $FSHARP_ARCHIVE && cd $FSHARP_BASENAME && make && make install && cd ~ && rm -rf /tmp/src /tmp/NuGetScratch ~/.nuget ~/.config ~/.local "$GNUPGHOME" && apt-get purge -y make gnupg dirmngr && apt-get clean
# Fri, 12 Mar 2021 09:13:51 GMT
WORKDIR /root
# Fri, 12 Mar 2021 09:13:51 GMT
CMD ["fsharpi"]
# Fri, 12 Mar 2021 09:28:02 GMT
LABEL maintainer=Dave Curylo <[email protected]>, Steve Desmond <[email protected]>
# Fri, 12 Mar 2021 09:28:03 GMT
ENV FrameworkPathOverride=/usr/lib/mono/4.8-api/
# Fri, 12 Mar 2021 09:28:03 GMT
ENV NUGET_XMLDOC_MODE=skip DOTNET_RUNNING_IN_CONTAINER=true DOTNET_USE_POLLING_FILE_WATCHER=true
# Fri, 12 Mar 2021 09:28:13 GMT
RUN apt-get update && apt-get --no-install-recommends install -y curl libunwind8 gettext apt-transport-https libc6 libcurl4 libgcc1 libgssapi-krb5-2 libicu63 liblttng-ust0 libssl1.1 libstdc++6 libunwind8 libuuid1 zlib1g && rm -rf /var/lib/apt/lists/*
# Fri, 12 Mar 2021 09:28:25 GMT
RUN DOTNET_SDK_VERSION=3.1.403 && DOTNET_SDK_DOWNLOAD_URL=https://dotnetcli.blob.core.windows.net/dotnet/Sdk/$DOTNET_SDK_VERSION/dotnet-sdk-$DOTNET_SDK_VERSION-linux-x64.tar.gz && DOTNET_SDK_DOWNLOAD_SHA=0a0319ee8e9042bf04b6e83211c2d6e44e40e604bff0a133ba0d246d08bff76ebd88918ab5e10e6f7f0d2b504ddeb65c0108c6539bc4fbc4f09e4af3937e88ea && curl -SL $DOTNET_SDK_DOWNLOAD_URL --output dotnet.tar.gz && echo "$DOTNET_SDK_DOWNLOAD_SHA dotnet.tar.gz" | sha512sum -c - && mkdir -p /usr/share/dotnet && tar -zxf dotnet.tar.gz -C /usr/share/dotnet && rm dotnet.tar.gz && ln -s /usr/share/dotnet/dotnet /usr/bin/dotnet
# Fri, 12 Mar 2021 09:28:28 GMT
RUN mkdir warmup && cd warmup && dotnet new && cd - && rm -rf warmup /tmp/NuGetScratch
# Fri, 12 Mar 2021 09:28:29 GMT
WORKDIR /root
# Fri, 12 Mar 2021 09:28:29 GMT
CMD ["dotnet" "fsi"]
```
- Layers:
- `sha256:6f28985ad1843afd6fd4fe0b42a30bfab63c27d302362e7341e3316e8ba25ced`
Last Modified: Fri, 12 Mar 2021 02:26:11 GMT
Size: 27.1 MB (27101001 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:d3007841f45892a32f54fd6ff902f2a93b378ca95eec6925389ed5f85df77cc4`
Last Modified: Fri, 12 Mar 2021 09:29:30 GMT
Size: 160.5 MB (160546179 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:afc387f6b767c775ba509b4fb2a15620ce1cf1c1fc1e2fae066f9265e173c58d`
Last Modified: Fri, 12 Mar 2021 09:30:36 GMT
Size: 17.2 MB (17206253 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:3039a030b46c0e02f885c6356c32f6476b8435da5e3c4212aeb5a38bd8d47681`
Last Modified: Fri, 12 Mar 2021 09:30:55 GMT
Size: 123.8 MB (123846271 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
- `sha256:9ece18160f6ed87798bba0d45cdea13748b680df71846ce8df2c3096ff1acb66`
Last Modified: Fri, 12 Mar 2021 09:30:37 GMT
Size: 4.3 MB (4275821 bytes)
MIME: application/vnd.docker.image.rootfs.diff.tar.gzip
| 69.551282 | 1,532 | 0.729217 | yue_Hant | 0.254191 |
0cd7700f4c4bed3192a743a89728b84ccc4b308e | 44 | md | Markdown | README.md | ankushgarg1998/ankushgarg1998.github.io | 091c8ace993c1cee5ebd3d298f3ec23be4394053 | [
"MIT"
] | 3 | 2017-10-30T17:25:04.000Z | 2021-05-22T10:26:46.000Z | README.md | ankushgarg1998/ankushgarg1998.github.io | 091c8ace993c1cee5ebd3d298f3ec23be4394053 | [
"MIT"
] | null | null | null | README.md | ankushgarg1998/ankushgarg1998.github.io | 091c8ace993c1cee5ebd3d298f3ec23be4394053 | [
"MIT"
] | null | null | null | # ankushgarg1998.github.io
Personal Website
| 14.666667 | 26 | 0.840909 | zul_Latn | 0.16851 |
0cda2b676107d84365c50d41529a9353bd7cc26a | 12,770 | md | Markdown | doc/agrhys.md | cgeneste/api-sensorthing | 19987ed9e6212abc4da7bb3c7d803df8fc40b20a | [
"MIT"
] | null | null | null | doc/agrhys.md | cgeneste/api-sensorthing | 19987ed9e6212abc4da7bb3c7d803df8fc40b20a | [
"MIT"
] | null | null | null | doc/agrhys.md | cgeneste/api-sensorthing | 19987ed9e6212abc4da7bb3c7d803df8fc40b20a | [
"MIT"
] | null | null | null | # Le modèle de données de l'API SensorThings applique à Agrhys
Afin de comprendre l'API SensorThings, il est essentiel de comprendre le modèle de données sous-jacent.
Ce modèle comprend les classes suivantes:
## Thing :
Une chose du monde réel, dans ce contexte généralement la chose où se trouve le capteur. Il peut s'agir d'une station de surveillance ou simplement de la pièce où le capteur a été installé.
## Location :
Emplacement de la chose. L'emplacement est fourni séparément de la chose car une chose peut se déplacer vers un emplacement différent.
## Datastreams :
Un Datastream relie une chose à un capteur qui mesure une propriété observée pour fournir un point d'entrée pour une série chronologique. Toutes les observations créées par le capteur concernant la propriété observée sont liées à ce flux de données.
## Sensor :
Description d'un capteur qui fournit des valeurs, y compris des informations sur la méthode de mesure. Bien que formellement conçu pour les capteurs dans le contexte de l'IoT, le capteur pourrait également être un observateur humain.
## ObservedProperties:
Les ObservedProperties décrivent ce qui est mesuré par un capteur à un emplacement spécifique.
## Observations:
Une seule valeur de mesure. Des informations sur la propriété observée qui a été mesurée avec quel type de capteur est fourni par le flux de données auquel cette observation est liée; l'objet sur lequel la mesure a été effectuée est fourni par le FeatureOfInterest de cette observation.
## FeaturesOfInterest :
Le FeatureOfInterest est l'objet sur lequel la mesure a été effectuée.
Dans le cadre d'Agrhys on pourrai :
Un ajout a êté ajouté par rapport a la norme sensorthing est un feature of interest par defaut dans location, ceci permet d'utiliser ce feature of interest si observation ne l'indique pas.
pour cet example nous allons utiliser dans le contexte d'un capteur mesurant la hauteur et la temperature sur le cours d'eau de kervidy.
Appliqué au modèle (pour la hauteur d'eau) ont pourrai :
Le modèle de données de l'API SensorThings.
Chaque chose (Thing) a un emplacement (location) (ou certains emplacements historiques historical_locations) dans l'espace et le temps.
Un ensemble d'observations (Observation) regroupées par la même propriété observée (ObservedProperty) et le même capteur (sensor) forment un flux de données (Datastream).
Une observation (Observation) est un événement effectué par un capteur (Sensor) qui produit une valeur d'une propriété observée (ObservedProperty) d'intérêt caractérisé (featureOfInterest).
### 1. Creation du sensor.
[Post http://sensorthings.geosas.fr/v1.0/Sensors](http://sensorthings.geosas.fr/Query?method=Post&entity=Sensors&datas=%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22description%22%3A%20%22Mesure%20du%20niveau%2C%20et%20de%20la%20temp%C3%A9rature%20de%20l'eau%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22name%22%3A%20%22OTT%20ecoLog%201000%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22encodingType%22%3A%20%22application%2Fpdf%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22metadata%22%3A%20%22https%3A%2F%2Fwww.ott.com%2Ffr-fr%2Fproduits%2Fle-niveau-deau-72%2Fott-ecolog-1000-2450%2FproductAction%2FoutputAsPdf%2F%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D)
```json
{
"description": "Mesure du niveau, et de la température de l'eau",
"name": "OTT ecoLog 1000",
"encodingType": "application/pdf",
"metadata": "https://www.ott.com/fr-fr/produits/le-niveau-deau-72/ott-ecolog-1000-2450/productAction/outputAsPdf/"
}
```
#### Response
```json
{
"@iot.id": "1",
"@iot.selfLink": http://sensorthings.geosas.fr/v1.0/Sensors(7),
"description": "Mesure du niveau, et de la température de l'eau",
"encodingType": "application/pdf",
"metadata": "https://www.ott.com/fr-fr/produits/le-niveau-deau-72/ott-ecolog-1000-2450/productAction/outputAsPdf/",
"name": "OTT ecoLog 1000",
"properties": null,
"[email protected]": "http://sensorthings.geosas.fr/v1.0/Sensors(1)/Datastreams"
}
```
On releve l'id du sensor crée
### 2. Creation du Thing.
La creation de lu "Thing", de sa "location" et des 2 "datastreams" dans la meme requette, bien evidement on pourrait le faire les une à la suite des autres.
- Questions :
les properties de thing peuvent acrceuillir les informations relative a hydras ou une uri pointant sur une table propre a hydras ?
#### Request
[Post http://sensorthings.geosas.fr/v1.0/Things](http://sensorthings.geosas.fr/Query?method=Post&entity=Things&datas=%7B%0A%20%20%20%20%22description%22%3A%20%22Exutoir%20Kervidy%22%2C%0A%20%20%20%20%22name%22%3A%20%22Exutoir%20Kervidy%22%2C%0A%20%20%20%20%22properties%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22hydras%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22domaine%22%3A%20%22C_Naizin%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22region%22%3A%20%22C_Naizin__03%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22station%22%3A%20%22KERVIDY_C_EXU%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22capteur%22%3A%20%220102%22%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%2C%0A%20%20%20%20%22Locations%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%22description%22%3A%20%22Kervidy%22%2C%0A%20%20%20%20%20%20%20%20%22name%22%3A%20%22Kervidy%22%2C%0A%20%20%20%20%20%20%20%20%22location%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22type%22%3A%20%22Point%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22coordinates%22%3A%20%5B-117.05%2C%2051.05%5D%0A%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%22encodingType%22%3A%20%22application%2Fvnd.geo%2Bjson%22%2C%0A%20%20%20%20%20%20%20%20%22FeatureOfInterest%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22name%22%3A%20%22Cours%20d'eau%20Kervidy%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22description%22%3A%20%22Analyse%20du%20cours%20d'eau%20de%20Kervidy%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22encodingType%22%3A%20%22application%2Fvnd.geo%2Bjson%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22feature%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22type%22%3A%20%22Point%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22coordinates%22%3A%20%5B-114.133%2C%2051.08%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%7D%2C%0A%20%20%20%20%22Datastreams%22%3A%20%5B%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22name%22%3A%20%22kervidy%20hauteur%20d'eau%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22description%22%3A%20%22Niveau%20d'eau%20de%20kervidy%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22unitOfMeasurement%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22name%22%3A%20%22Hauteur%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22symbol%22%3A%20%22m%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22ObservedProperty%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22name%22%3A%20%22Niveau%20d'eau%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22description%22%3A%20%22valeur%20en%20m%C3%A8tre%20de%20la%20hauteur%20de%20l'eau%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22Sensor%22%3A%20%7B%20%22%40iot.id%22%3A%201%20%7D%0A%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22name%22%3A%20%22kervidy%20temperature%20d'eau%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22description%22%3A%20%22temperature%20de%20kervidy%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22unitOfMeasurement%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22name%22%3A%20%22temperature%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22symbol%22%3A%20%22C%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22ObservedProperty%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22name%22%3A%20%22temperature%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%22description%22%3A%20%22temperature%20en%20centigrade%20de%20l'eau%22%0A%20%20%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22Sensor%22%3A%20%7B%20%22%40iot.id%22%3A%201%20%7D%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%0A%7D)
```json
{
"description": "Exutoir Kervidy",
"name": "Exutoir Kervidy",
"properties": {
"hydras": {
"domaine": "C_Naizin",
"region": "C_Naizin__03",
"station": "KERVIDY_C_EXU",
"capteur": "0102"
}
},
"Locations": {
"description": "Kervidy",
"name": "Kervidy",
"location": {
"type": "Point",
"coordinates": [-117.05, 51.05]
},
"encodingType": "application/vnd.geo+json",
"FeatureOfInterest": {
"name": "Cours d'eau Kervidy",
"description": "Analyse du cours d'eau de Kervidy",
"encodingType": "application/vnd.geo+json",
"feature": {
"type": "Point",
"coordinates": [-114.133, 51.08]
}
}
},
"Datastreams": [
{
"name": "kervidy hauteur d'eau",
"description": "Niveau d'eau de kervidy",
"unitOfMeasurement": {
"name": "Hauteur",
"symbol": "m"
},
"ObservedProperty": {
"name": "Niveau d'eau",
"description": "valeur en mètre de la hauteur de l'eau"
},
"Sensor": { "@iot.id": 1 }
},
{
"name": "kervidy temperature d'eau",
"description": "temperature de kervidy",
"unitOfMeasurement": {
"name": "temperature",
"symbol": "C"
},
"ObservedProperty": {
"name": "temperature",
"description": "temperature en centigrade de l'eau"
},
"Sensor": { "@iot.id": 1 }
}
]
}
```
#### Response
```json
{
"@iot.id": 1,
"@iot.selfLink": "http://sensorthings.geosas.fr/v1.0/Things(1)",
"description": "Niveau du cours d'eau de Kervidy",
"name": "Niveau d'eau kervidy",
"properties": {
"hydras": {
"region": "C_Naizin__03",
"capteur": "0102",
"domaine": "C_Naizin",
"station": "KERVIDY_C_EXU"
}
},
"[email protected]": "http://sensorthings.geosas.fr/v1.0/Things(1)/Datastreams",
"[email protected]": "http://sensorthings.geosas.fr/v1.0/Things(1)/HistoricalLocation",
"[email protected]": "http://sensorthings.geosas.fr/v1.0/Things(1)/Locations"
}
```
### 3. Ajout des observations.
#### Request
[Post http://sensorthings.geosas.fr/v1.0/Observations](http://sensorthings.geosas.fr/Query?method=Post&entity=Observations&datas=%7B%0A%20%20%20%20%22phenomenonTime%22%3A%20%221993-02-01T00%3A50%3A00Z%22%2C%0A%20%20%20%20%22resultTime%22%3A%20%221993-02-01T00%3A50%3A00Z%22%2C%0A%20%20%20%20%22result%22%3A%200.152%2C%0A%20%20%20%20%22Datastream%22%3A%20%7B%20%22%40iot.id%22%3A%201%20%7D%0A%7D)
```json
{
"phenomenonTime": "1993-02-01T00:50:00Z",
"resultTime": "1993-02-01T00:50:00Z",
"result": 0.152,
"Datastream": { "@iot.id": 1 }
}
```
ou
[Post http://sensorthings.geosas.fr/v1.0/Datastream(1)/Observations](http://sensorthings.geosas.fr/Query?method=Post&entity=Datastreams&id=1&subentity=Observations&datas=%7B%0A%20%20%20%20%22phenomenonTime%22%3A%20%221993-02-01T00%3A50%3A00Z%22%2C%0A%20%20%20%20%22resultTime%22%3A%20%221993-02-01T00%3A50%3A00Z%22%2C%0A%20%20%20%20%22result%22%3A%200.152%0A%7D)
```json
{
"phenomenonTime": "1993-02-01T00:50:00Z",
"resultTime": "1993-02-01T00:50:00Z",
"result": 0.152
}
```
#### Response
```json
{
"@iot.id": 1,
"@iot.selfLink": "http://sensorthings.geosas.fr/v1.0/Observations(1)",
"[email protected]": "http://sensorthings.geosas.fr/v1.0/Observations(1)/Datastream",
"[email protected]": "http://sensorthings.geosas.fr/v1.0/Observations(1)/FeaturesOfInterest(2)",
"phenomenonTime": "1993-02-01T00:50:00Z",
"resultTime": "1993-02-01T00:50:00Z",
"result": 0.152,
"parameters": null
}
```
## CSV Insert.
you can add csv file.
| 56.255507 | 3,835 | 0.68794 | fra_Latn | 0.233484 |
0cda2f0e15b172436817e2324673510ade287578 | 12 | md | Markdown | 05/windowdui-xiang.md | TYRMars/JavaScript-StepPitGuide | 45091d675a48a3ef9fcf6e00d673a293e8be6cf3 | [
"MIT"
] | 24 | 2018-01-16T03:00:06.000Z | 2021-11-05T09:41:01.000Z | ji-chu-zhi-shi/05/windowdui-xiang.md | TYRMars/JSlearn | 45091d675a48a3ef9fcf6e00d673a293e8be6cf3 | [
"MIT"
] | 1 | 2021-08-19T15:28:05.000Z | 2021-08-19T15:28:05.000Z | ji-chu-zhi-shi/05/windowdui-xiang.md | TYRMars/JSlearn | 45091d675a48a3ef9fcf6e00d673a293e8be6cf3 | [
"MIT"
] | 7 | 2018-01-16T14:30:14.000Z | 2020-07-17T08:46:35.000Z | # window对象
| 4 | 10 | 0.666667 | eng_Latn | 0.974051 |
0cdab74b358d41b6c1899714db91c3634fc264ce | 3,195 | md | Markdown | app-remote-lib/ERRORS.md | philb32/android-sdk | 9e14b91a540ffc98bdad5fe2e554b36de53ca068 | [
"Apache-2.0"
] | null | null | null | app-remote-lib/ERRORS.md | philb32/android-sdk | 9e14b91a540ffc98bdad5fe2e554b36de53ca068 | [
"Apache-2.0"
] | null | null | null | app-remote-lib/ERRORS.md | philb32/android-sdk | 9e14b91a540ffc98bdad5fe2e554b36de53ca068 | [
"Apache-2.0"
] | null | null | null | Here you will find status messages, alerts, and errors that should be handled by a partner app.
## Development/Implementation Errors
Errors are implemented as a number of exception classes that will be delivered through callbacks
when they occur. By investigating the type of the error, implementations can choose the right course
of action.
### Connection errors
Connection errors are delivered through the on `onFailure` method of `ConnectionListener`.
Connection errors can occur at any time from that a clients calls `connect` up until the time the
client has disconnected. The following comprises a list of errors that can be delivered through the
`ConnectionListener.onFailure()` callback:
```
CouldNotFindSpotifyApp
```
The Spotify app is not installed on the device. The Spotify Android app must be installed on the user's device in order for the Spotify App Remote SDK to work. Please see the ["Installing Spotify" section](https://beta.developer.spotify.com/documentation/general/guides/content-linking-guide/) of the Content Linking guide on how to direct users to download Spotify.
```
NotLoggedInException
```
No one is logged in to the Spotify app on this device. Guide the user to log in to Spotify and try
again.
```
AuthenticationFailedException
```
Partner app failed to authenticate with Spotify. Check client credentials and make sure your app is
registered correctly at developer.spotify.com
```
UserNotAuthorizedException
```
Indicates the user did not authorize this client of App Remote to use Spotify on the user[“Authentication
And Authorization”](https://developer.spotifyinternal.com/documentation/android-app-remote/#authentication-and-authorization) section on the Developer Site.
```
UnsupportedFeatureVersionException
```
Spotify app can't support requested features. User should update Spotify app.
```
OfflineModeException
```
Spotify user has set their Spotify app to be in offline mode, but app remote requires a call to be
made to the backend. The user needs to disable offline mode in the Spotify app.
```
LoggedOutException
```
User has logged out from Spotify. The difference between this one and `NotLoggedInException` is that
in case of the latter the connection could not have been established. `LoggedOutException` means
that user logged out after Remote SDK connected to Spotify app.
```
SpotifyDisconnectedException
```
The Spotify app was/is disconnected by the Spotify app. This indicates typically that the Spotify
app was closed by the user or for other reasons. You need to reconnect to continue using Spotify App
Remote.
```
SpotifyConnectionTerminatedException
```
The connection to the Spotify app was unexpectedly terminated. Spotify might have crashed or was
killed by the system. You need to reconnect to continue using Spotify App Remote.
```
RemoteClientException
```
Your requested call was not successful. The message will explain what type of action was unsuccessful and the reason why.
For example, trying to initiate playback with a bad URI would return
`com.spotify.protocol.client.error.RemoteClientException: {"message":"Cannot play specified uri": [NOT_A_VALID_URI]"}`
| 37.151163 | 366 | 0.789984 | eng_Latn | 0.998397 |
0cdad3a73ddaff9d83473a1efecad92249e3665a | 38 | md | Markdown | cpp/README.md | parmes/solfec-2.0 | 3329d3e1e4d58fefaf976c04bab19284aef45bc2 | [
"MIT"
] | 1 | 2020-06-21T23:52:25.000Z | 2020-06-21T23:52:25.000Z | cpp/README.md | parmes/solfec-2.0 | 3329d3e1e4d58fefaf976c04bab19284aef45bc2 | [
"MIT"
] | 1 | 2020-05-01T14:44:01.000Z | 2020-05-01T23:50:36.000Z | cpp/README.md | parmes/solfec-2.0 | 3329d3e1e4d58fefaf976c04bab19284aef45bc2 | [
"MIT"
] | 2 | 2020-06-21T23:59:21.000Z | 2021-12-09T09:49:50.000Z | [C++] (https://cppreference.com) code
| 19 | 37 | 0.657895 | kor_Hang | 0.266421 |
0cdae6de54b7eee1f1efcd9d6838a9b92a6c9d09 | 2,190 | md | Markdown | _posts/2015-09-20-two-poems.md | adewils/adewils.github.io | 8951e55d1e3f284415e67859a1bc7a6e7c89f8a3 | [
"MIT"
] | null | null | null | _posts/2015-09-20-two-poems.md | adewils/adewils.github.io | 8951e55d1e3f284415e67859a1bc7a6e7c89f8a3 | [
"MIT"
] | null | null | null | _posts/2015-09-20-two-poems.md | adewils/adewils.github.io | 8951e55d1e3f284415e67859a1bc7a6e7c89f8a3 | [
"MIT"
] | null | null | null | ---
id: 3246
title: 'Two poems …'
date: 2015-09-20T20:57:42+01:00
author: adewils
excerpt: "I attempted a couple of poetry styles - an 'echo' poem and a 'diamante' poem ..."
layout: post
guid: http://adrianwilson.co.uk/blog/?p=3246
permalink: /poetry/two-poems/
explicit:
- ""
- ""
block:
- ""
- ""
filesize:
- ""
- ""
date_recorded:
- ""
- ""
audio_file:
- ""
- ""
duration:
- ""
- ""
slide_template:
- ""
- default
rp4wp_auto_linked:
- "1"
- "1"
image: /wp-content/uploads/2016/07/aaron-burden-64849-unsplash-e1526541353292.jpg
categories:
- Poetry
---
I wrote a couple of small (and imperfectly formed) poems…The first was my take on an ‘echo’ poem* where the prompt was ‘edge’. Typically oblique, I made U2’s guitarist, the Edge, (aka David Howell <a href="http://www.atu2.com/band/edge/" target="_blank" rel="noopener noreferrer">Evans</a>) the subject…
**Who am I?**
<p class="has-text-align-left">
When you are with friends, what are you called?<br /><em>Bald!</em><br />You were born on which day?<br /><em>Sunday</em><br />On whose guitars magical chords do you etch?<br /><em>Gretsch</em><br />An item of clothing reflecting your personae?<br /><em>Bandana</em><br />You travel the world in boats, trains… and?<br /><em>Planes?</em><br />When you are on stage, what name do they allege?<br /><em>Edge</em>
</p>
<hr class="wp-block-separator" />
On [Anne You Huang’s poetry blog](https://www.annhuang.com/blog/2016/05/20/5-techniques-used-by-surrealist-poets/) I found an excellent (and far more proficient) example of an echo poem …
<hr class="wp-block-separator" />
<hr class="wp-block-separator" />
<hr class="wp-block-separator" />
My second poem is a [diamante](https://en.wikipedia.org/wiki/Diamante_poem) where the prompts were a starting point of ‘young’ and an ending of ‘old’. The idea was a smooth transition from one to another. See how I did…
**Age**
Young
Elastic, callow
Springing, laughing, everlasting
New every day, Seen it all
Bending, stumbling, aching
Jaded, painful
Old
<hr class="wp-block-separator" /> | 32.205882 | 418 | 0.682192 | eng_Latn | 0.829617 |
0cdcda0bb775c2beae681c294b90f40950cd38b9 | 8,075 | md | Markdown | docs/community/contribute/style-guide.md | miohtama/docs-1 | f6d1d7e0b694605ad2cd29be4b53ffabf2efbe02 | [
"Apache-2.0",
"MIT"
] | null | null | null | docs/community/contribute/style-guide.md | miohtama/docs-1 | f6d1d7e0b694605ad2cd29be4b53ffabf2efbe02 | [
"Apache-2.0",
"MIT"
] | null | null | null | docs/community/contribute/style-guide.md | miohtama/docs-1 | f6d1d7e0b694605ad2cd29be4b53ffabf2efbe02 | [
"Apache-2.0",
"MIT"
] | null | null | null | ---
id: style-guide
title: Writing Style Guide
sidebar_label: Writing Style Guide
---
This style guide provides a set of editorial guidelines for anyone writing developer
documentation for NEAR related projects.
## Goals and audience
This guide codifies and records style decisions so that you can write documentation
that is consistent with existing documentation, and ensure that what you write is
as easy as possible to understand. We hope that you'll join us in striving for
high-quality documentation.
> **Note**: Everything in this guide is a guideline, not a draconian rule. Therefore,
> there might be contexts where it makes sense to diverge from our guidelines to make
> your documentation better.
## Tone and content
### Be conversational and friendly
Aim for a voice and tone that's conversational, friendly, and respectful without being
overly colloquial or frivolous; a voice that's casual and natural and approachable, not
pedantic or pushy. Try to sound like a knowledgeable friend who understands what the
developer wants to do.
Remember that many readers are not native English speakers, many of them come from
cultures different from yours, and your document may be translated into other languages
(see [Language and grammar](#language-and-grammar) for more on this).
### Don't pre-announce in the documentation
Avoid documenting future features or products, even in innocuous ways (i.e, "we're
currently considering _\<possible feature enhancement\>_...").
### Use descriptive link text
When you're writing link text, use a phrase that describes what the reader will see after
following the link. Links should make sense without the surrounding text. That can take
either of two forms:
- The exact text of the title or heading you're referencing.
- A description of the destination page capitalized as ordinary paragraph text.
### Page titles and headings
Page titles should use title case (for example, "Deploy your App in Production"). Headings
within a page should use sentence case (for example "Test your app with a simple UI").
### Typography
Please use the following conventions, which are derived from Google's style guide and from
developer documentation published by O'Rielly media group:
- `code font` is used for command-line input and output, and for references to code entity
names (variables, types, etc).
- *`italic code font`* is used to show where a reader should swap in the name of a server
or other implementation-specific detail in a syntax example or command example.
- *italic font* is used when introducing a term for the first time
- **Bold font** is used for file and directory names, UI names, error message text, and
for emphasis
### Write accessibly
General guidelines to improve reading accessibility:
- Place a paragraph's key information in the first sentence to aid in *scannability*. To
learn more about scannability, see [How Users Read on the
Web](https://www.nngroup.com/articles/how-users-read-on-the-web/).
- Break up walls of text (large paragraphs) to aid in scannability. You can do this by
separating paragraphs, adding headings, and using lists.
- Use shorter sentences, and avoid complex-compound sentences. Try to use fewer than 26
words per sentence.
- Define acronyms and abbreviations on first use, and repeat acronym definitions as necessary
to avoid confusing readers.
- Use parallel writing structures for similar things. For example, items in a list should
be similar.
### Write for a global audience
We write our documentation in US English, but it should be as accessible as possible to the
worldwide developer community. The rules below help developers who use machine translation to
read NEAR docs, or who speak English as a secondary language:
- Use the present tense.
- Write dates and times in unambiguous and clear ways.
- Provide context. Don't assume the reader already knows what you're talking about.
- Avoid negative constructions when possible. Consider whether it’s necessary to tell the user
what they can’t do instead of what they can.
- Use the active voice. The subject of the sentence is the person or thing performing the action.
With passive voice, it's often hard for readers to figure out who's supposed to do something.
- Address the reader directly. Use *you*, instead of *the user* or *they*.
- Define abbreviations. Abbreviations can be confusing out of context, and they don't translate
well. Spell things out whenever possible, at least the first time you use a given term.
- Don't use the same word to mean different things.
## Language and grammar
Following the guidelines below ensures that our documentation is as approachable as possible for
as many readers as possible. In fact, all of these language and grammar guidelines improve the
results of machine translating documentation into other languages.
### Use the second person
> Use "you" rather than "we."
In general, use the second person to refer to the reader in your docs rather than the first
person— *you* instead of *we*.
It's also important to figure out who the *you* is that you're addressing (a developer? a sysadmin?
someone else?), and to be consistent about that. Make it clear to the reader who you expect them
to be (sometimes with an explicit *audience* sentence near the beginning of the document).
Finally, always use the third person when describing NEAR's actions or features (avoid "this
lets us" in favor of "this lets NEAR").
### Use active voice
> Make clear who's performing the action.
In general, use the active voice (in which the grammatical subject of the sentence is the person
or thing performing the action) instead of passive voice (in which the grammatical subject of
the sentence is the person or thing being acted upon), though there are exceptions. For example:
Recommended:
* “Send a query to the service. The server sends an acknowledgment.“
Not recommended:
* ”The service is queried, and an acknowledgment is sent.”
* “The service is queried by you, and an acknowledgment is sent by the server.”
### Use standard American spelling and punctuation
In general, in cases where American spelling differs from Commonwealth/"British" spelling, use
the American spelling.
### Put conditional clauses before instructions, not after
Say you want to tell the audience to do something in a particular circumstance. If possible,
mention the circumstance before you provide the instruction; that way, the reader can skip the
instruction if the circumstance doesn't apply.
## Formatting, punctuation, and organization
* Use numbered lists for sequences.
* Use bulleted lists for most other lists.
* Use description lists for pairs of related pieces of data.
> Use numbered lists for sequences, bulleted lists in most other contexts, and description
> lists for pairs of related pieces of data.
* Use serial commas.
> Use commas to separate items in series, and use commas to separate certain kinds of clauses.
> In a series of three or more items, use a comma before the final *and* or *or*.
* Put code-related text in `code font`.
> In ordinary text sentences (as opposed to, say, code samples), use code font to mark up most
> things that have anything to do with code (example variables, product keywords, etc).
> In Markdown, use backticks (`).
* Put UI elements in **bold**.
> If you do document elements of the UI, put UI element names in **bold**, and use appropriate
> nouns and verbs to describe how to interact with them.
* Use unambiguous date formatting.
> Expressing dates and times in a clear and unambiguous way helps support writing for a global
> audience and reduces confusion. We recommend using the `YYYY-MM-DD` format for dates.
## Credits and more style guidance
This style guide is inspired by and borrows from [Google's developer documentation style
guide](https://developers.google.com/style/), which you can use for anything not covered here.
For anything not found in Google's style guide, see
[Microsoft's Style Guide](https://docs.microsoft.com/en-us/style-guide/welcome/).
| 43.88587 | 99 | 0.777214 | eng_Latn | 0.999563 |
0cddbcf8d7c2cc8331be582150c96b2e89637c19 | 1,813 | md | Markdown | getting-started/framework/mvvm/bindings/html.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | 1 | 2016-02-03T10:15:54.000Z | 2016-02-03T10:15:54.000Z | getting-started/framework/mvvm/bindings/html.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | null | null | null | getting-started/framework/mvvm/bindings/html.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | null | null | null | ---
title: Html
meta_title: HTML binding in Kendo UI MVVM | Kendo UI Documentation
meta_description: HTML binding in Kendo UI MVVM, update and set the HTML of the target DOM element by changing the View-Model value.
slug: mvvm-html-binding
publish: true
---
# Html binding
The `html` binding sets the html content (`innerHTML`) of the target DOM
element to a View-Model value. Changing the View-Model value via code will update the html of the target element.
If the View-Model value is not of primitive type (Text, Number or Date) the result returned by the toString JavaScript method will be used as the value.
To set the value displayed by an input, textarea or select use the [value](value) binding instead.
## Using the html binding
<span data-bind="html: name"></span>
<script>
var viewModel = kendo.observable({
name: "John Doe"
});
kendo.bind($("span"), viewModel);
</script>
The output will be this (the data-bind attribute is removed for clarity):
<span>John Doe</span>
If the View-Model value contains HTML tags those will be embedded in the final output. For example this:
<span data-bind="html: name"></span>
<script>
var viewModel = kendo.observable({
name: "<strong>John Doe</strong>"
});
kendo.bind($("span"), viewModel);
</script>
will output this:
<span><strong>John Doe</strong></span>
To display any HTML tags contained in the View-Model value use the [text](text) binding.
### Note: the html binding may not work for some elements in older versions of Internet Explorer
The `html` binding relies on the `innerHTML` DOM element property. The latter is not fully supported in older versions of Internet Explorer for all
DOM elements. For example setting the `innerHTML` of a `table` is not supported.
| 31.258621 | 152 | 0.718147 | eng_Latn | 0.940801 |
0cddcbed0ab3540b6db0367f4f3727683f2d30c1 | 109 | md | Markdown | app/views/mail/user_signup_approval/user_signup_approval.fr.md | crowdfundhq/site | 4c44ff7b0429f59053a470ed9577ce1718f1f88b | [
"MIT"
] | 3 | 2017-03-07T13:11:24.000Z | 2018-02-26T19:29:08.000Z | app/views/mail/user_signup_approval/user_signup_approval.fr.md | crowdfundhq/site | 4c44ff7b0429f59053a470ed9577ce1718f1f88b | [
"MIT"
] | 1 | 2020-03-24T12:47:36.000Z | 2020-03-24T12:47:36.000Z | app/views/mail/user_signup_approval/user_signup_approval.fr.md | crowdfundhq/site | 4c44ff7b0429f59053a470ed9577ce1718f1f88b | [
"MIT"
] | null | null | null | # Bienvenue!
Merci pour votre inscription!
Vous recevrez un e-mail lorsque votre compte aura été approuvé.
| 18.166667 | 63 | 0.788991 | fra_Latn | 0.996695 |
0cde68d52059ae5c5cec4217ef4c9c4e2c158411 | 3,584 | md | Markdown | wdk-ddi-src/content/sercx/nf-sercx-sercx2piotransmitinitializetransactioncomplete.md | riwaida/windows-driver-docs-ddi | c6f3d4504dc936bba6226651b2810df9c9cb7f1c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/sercx/nf-sercx-sercx2piotransmitinitializetransactioncomplete.md | riwaida/windows-driver-docs-ddi | c6f3d4504dc936bba6226651b2810df9c9cb7f1c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/sercx/nf-sercx-sercx2piotransmitinitializetransactioncomplete.md | riwaida/windows-driver-docs-ddi | c6f3d4504dc936bba6226651b2810df9c9cb7f1c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:sercx.SerCx2PioTransmitInitializeTransactionComplete
title: SerCx2PioTransmitInitializeTransactionComplete function (sercx.h)
description: The SerCx2PioTransmitInitializeTransactionComplete method notifies version 2 of the serial framework extension (SerCx2) that the serial controller driver has finished initializing the serial controller hardware in preparation for a new PIO-transmit transaction.
old-location: serports\sercx2piotransmitinitializetransactioncomplete.htm
tech.root: serports
ms.assetid: 3A2CA5FB-0844-4992-9A05-DDF9D7F1BADC
ms.date: 04/23/2018
ms.keywords: 2/SerCx2PioTransmitInitializeTransactionComplete, SerCx2PioTransmitInitializeTransactionComplete, SerCx2PioTransmitInitializeTransactionComplete method [Serial Ports], serports.sercx2piotransmitinitializetransactioncomplete
ms.topic: function
req.header: sercx.h
req.include-header:
req.target-type: Universal
req.target-min-winverclnt: Available starting with Windows 8.1.
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql: "<= DISPATCH_LEVEL"
topic_type:
- APIRef
- kbSyntax
api_type:
- COM
api_location:
- 2.0\Sercx.h
api_name:
- SerCx2PioTransmitInitializeTransactionComplete
product:
- Windows
targetos: Windows
req.typenames:
---
# SerCx2PioTransmitInitializeTransactionComplete function
## -description
The <b>SerCx2PioTransmitInitializeTransactionComplete</b> method notifies version 2 of the serial framework extension (SerCx2) that the serial controller driver has finished initializing the serial controller hardware in preparation for a new PIO-transmit transaction.
## -parameters
### -param PioTransmit [in]
A <a href="https://docs.microsoft.com/windows-hardware/drivers/serports/sercx2-object-handles">SERCX2PIOTRANSMIT</a> handle to a PIO-transmit object. The serial controller driver previously called the <a href="https://msdn.microsoft.com/library/windows/hardware/dn265269">SerCx2PioTransmitCreate</a> method to create this object.
### -param InitSuccess [in]
Whether the initialization was successful. If <b>TRUE</b>, the initialization succeeded. If <b>FALSE</b>, the initialization failed.
## -returns
None.
## -remarks
Before SerCx2 initiates a PIO-transmit transaction, SerCx2 calls the <a href="https://msdn.microsoft.com/2E3652CB-24F1-4467-AF1D-CFD52392B2DB">EvtSerCx2PioTransmitInitializeTransaction</a> event callback function, if it is implemented, to initialize the serial controller to perform the transaction. In response to this call, the driver should first do any initialization that is needed; then the driver must call <b>SerCx2PioTransmitInitializeTransactionComplete</b> to notify SerCx2. SerCx2 expects this notification and does not start the transaction until it is notified.
The serial controller driver must call <b>SerCx2PioTransmitInitializeTransactionComplete</b> only in response to a call to the <i>EvtSerCx2PioTransmitInitializeTransaction</i> function.
For more information, see <a href="https://msdn.microsoft.com/3BEF9A3D-1FEF-4626-B07F-1670359062AF">SerCx2 PIO-Transmit Transactions</a>.
## -see-also
<a href="https://msdn.microsoft.com/2E3652CB-24F1-4467-AF1D-CFD52392B2DB">EvtSerCx2PioTransmitInitializeTransaction</a>
<a href="https://docs.microsoft.com/windows-hardware/drivers/serports/sercx2-object-handles">SERCX2PIOTRANSMIT</a>
<a href="https://msdn.microsoft.com/library/windows/hardware/dn265269">SerCx2PioTransmitCreate</a>
| 33.495327 | 575 | 0.809989 | eng_Latn | 0.583989 |
0cdee413dba50deb00c6be8e3dc374293837a98d | 8,998 | md | Markdown | _posts/2021-11-25-matplotlib-pyplot-03.md | nkw011/nkw011.github.io | 91d334bb778c7244173c2477ed4847f6ab6c7ea7 | [
"MIT"
] | null | null | null | _posts/2021-11-25-matplotlib-pyplot-03.md | nkw011/nkw011.github.io | 91d334bb778c7244173c2477ed4847f6ab6c7ea7 | [
"MIT"
] | 1 | 2021-11-02T12:45:32.000Z | 2021-11-02T12:45:32.000Z | _posts/2021-11-25-matplotlib-pyplot-03.md | nkw011/nkw011.github.io | 91d334bb778c7244173c2477ed4847f6ab6c7ea7 | [
"MIT"
] | null | null | null | ---
title: "[Matplotlib.pyplot] 03. ticks, limit, spine, grid"
excerpt: "데이터 시각화를 위한 Matplotlib.pyplot 사용법 - 03. ticks, limit, spine, grid"
toc: true
toc_sticky: true
categories:
- matplotlib
tags:
- python
- matplotlib
sidebar:
nav: sidebarTotal
---
```python
import matplotlib.pyplot as plt
import numpy as np
```
## 1. Ticks
tick은 눈금을 가리킨다.
아무것도 없이 ax를 그렸을 때 각각의 축은 기본적으로 0~1까지 5개의 간격이 존재하며 따라서 총 6개의 tick이 존재한다.
이 tick을 조절하는 방법을 알아보자.
### 1.1. set_xticks(), set_yticks()
tick을 설정할 때 쓰인다.
**[Axes.set_xticks(ticks)](https://matplotlib.org/stable/api/_as_gen/matplotlib.axes.Axes.set_xticks.html)**
- ticks: list of floats, 리스트에 담긴 원소가 tick이 된다
**[Axes.set_yticks(ticks)](https://matplotlib.org/stable/api/_as_gen/matplotlib.axes.Axes.set_yticks.html)**
- ticks: list of floats, 리스트에 담긴 원소가 tick이 된다
반대로 tick을 얻어오려면 set대신 get을 사용하면 된다.
```python
fig,ax = plt.subplots()
xticks = np.arange(0,60,10)
yticks = np.arange(0,60,10)
ax.set_xticks(xticks)
ax.set_yticks(yticks)
```
[<matplotlib.axis.YTick at 0x7fdcad028b20>,
<matplotlib.axis.YTick at 0x7fdcac8a14f0>,
<matplotlib.axis.YTick at 0x7fdcac8f1580>,
<matplotlib.axis.YTick at 0x7fdcacf68e20>,
<matplotlib.axis.YTick at 0x7fdcacf4e460>,
<matplotlib.axis.YTick at 0x7fdcacf71e80>]
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_4_1.png">
### 1.2. Tick Label
각 tick에 label을 설정해줄 수 있다.
**[Axes.set_xticklabels(labels)](https://matplotlib.org/stable/api/_as_gen/matplotlib.axes.Axes.set_xticklabels.html)**
- labels: tick에 쓰일 label을 담는다. tick의 갯수와 동일해야한다.
- label이기 때문에 font property를 적용할 수 있다.
**[Axes.set_yticklabels(labels)](https://matplotlib.org/stable/api/_as_gen/matplotlib.axes.Axes.set_yticklabels.html)**
- labels: tick에 쓰일 label을 담는다. tick의 갯수와 동일해야한다.
- label이기 때문에 font property를 적용할 수 있다.
set대신 get을 사용하면 tick label을 가져올 수 있다.
```python
fig, ax = plt.subplots()
ticks = np.arange(6)
tick_labels = ["tick" + str(i) for i in range(6)]
ax.set_xticks(ticks)
ax.set_yticks(ticks)
ax.set_xticklabels(tick_labels)
ax.set_yticklabels(tick_labels)
```
[Text(0, 0, 'tick0'),
Text(0, 1, 'tick1'),
Text(0, 2, 'tick2'),
Text(0, 3, 'tick3'),
Text(0, 4, 'tick4'),
Text(0, 5, 'tick5')]
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_6_1.png">
### 1.3. major, minor
기본 tick(major)외에 추가로 표시할 수 있는 tick을 minor라고 한다.
주로 새부 간격이나 라인을 표시할 때 많이 쓰인다.
major인지는 따로 표시를 하지 않아도 되고 tick을 minor로 쓰고싶다면 parameter에 minor=True 를 추가하면 된다.
```python
fig, ax = plt.subplots(figsize=(7,7))
major_ticks = np.arange(0,21,5)
minor_ticks = np.arange(21)
ax.set_xticks(major_ticks)
ax.set_xticks(minor_ticks,minor=True)
ax.set_yticks(major_ticks)
ax.set_yticks(minor_ticks,minor=True)
```
[<matplotlib.axis.YTick at 0x7fdcad024580>,
<matplotlib.axis.YTick at 0x7fdcac8d1be0>,
<matplotlib.axis.YTick at 0x7fdcac7ee4f0>,
<matplotlib.axis.YTick at 0x7fdcac7ee6d0>,
<matplotlib.axis.YTick at 0x7fdcacd0d370>,
<matplotlib.axis.YTick at 0x7fdcac944790>,
<matplotlib.axis.YTick at 0x7fdcac7ee7f0>,
<matplotlib.axis.YTick at 0x7fdcac7ee910>,
<matplotlib.axis.YTick at 0x7fdcacaf6eb0>,
<matplotlib.axis.YTick at 0x7fdcac8fec10>,
<matplotlib.axis.YTick at 0x7fdcad1956d0>,
<matplotlib.axis.YTick at 0x7fdcad195f10>,
<matplotlib.axis.YTick at 0x7fdcad195f40>,
<matplotlib.axis.YTick at 0x7fdcad195b50>,
<matplotlib.axis.YTick at 0x7fdcacaf6e50>,
<matplotlib.axis.YTick at 0x7fdcacd0d280>,
<matplotlib.axis.YTick at 0x7fdcac7c1040>,
<matplotlib.axis.YTick at 0x7fdcac82bfa0>,
<matplotlib.axis.YTick at 0x7fdcac82bb80>,
<matplotlib.axis.YTick at 0x7fdcac82bf70>,
<matplotlib.axis.YTick at 0x7fdcac815fa0>]
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_8_1.png">
### 1.4. tick_params()
tick의 appearence나 label을 설정할 때 쓰인다.
**[Axes.tick_params()](https://matplotlib.org/stable/api/_as_gen/matplotlib.axes.Axes.tick_params.html)**
- axis: {'x', 'y', 'both'}, default: 'both'
- which: {'major', 'minor', 'both'}, default: 'major'
- direction: {'in', 'out', 'inout'} / tick의 방향을 결정한다. 축의 안쪽으로 할 것인지 바깥쪽으로 할 것인지 정한다.
- length: 길이
- width : 두께
- color: 색상
- labelsize: label 크기
- labelcolor: label 색상
- bottom, top, left, right: 각 축마다 tick을 표시하는지 하지 않는지 설정
- labelbottom, labeltop, labelleft, labelright: 각 축마다 label을 표시하는지 하지 않는지 설정
```python
fig, ax = plt.subplots(figsize=(7,7))
major_ticks = np.arange(0,21,5)
minor_ticks = np.arange(21)
ax.set_xticks(major_ticks)
ax.set_xticks(minor_ticks,minor=True)
ax.set_yticks(major_ticks)
ax.set_yticks(minor_ticks,minor=True)
ax.tick_params(which='major',length=5,width=2,
labelsize=10,labelcolor='b')
ax.tick_params(which='minor',length=3)
```
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_10_0.png">
```python
fig, ax = plt.subplots(figsize=(7,7))
ticks = np.arange(0,21,5)
ax.set_xticks(ticks)
ax.set_yticks(ticks)
ax.tick_params(left=False,labelleft=False,top=True,right=True,
direction='in', length=5)
```
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_11_0.png">
## 2. limit
각 축에 limit을 설정할 수 있다.
**[Axes.set_xlim(left,right)](https://matplotlib.org/stable/api/_as_gen/matplotlib.axes.Axes.set_xlim.html)**
- left: 시작지점. 즉, 축이 가질 수 있는 최솟값
- right: 마지막지점. 즉, 축이 가질 수 있는 최댓값
**[Axes.set_ylim(left,right)](https://matplotlib.org/stable/api/_as_gen/matplotlib.axes.Axes.set_ylim.html)**
- left: 시작지점. 즉, 축이 가질 수 있는 최솟값
- right: 마지막지점. 즉, 축이 가질 수 있는 최댓값
보통 left,rigth를 list형태로 묶어서 parameter로 넘겨주기도 한다.
각 축에 설정된 값을 가져오려면 set대신 get을 쓰면 된다.
```python
fig = plt.figure(figsize=(7,7))
ax1 = fig.add_subplot(2,1,1)
ax2 = fig.add_subplot(2,1,2)
ticks = np.arange(0,0.6,0.1)
lims = [0,0.5]
ax1.set_xticks(ticks)
ax2.set_xlim(lims)
ax2.set_ylim(0,0.5)
ax2.set_xticks(ticks)
ax2.set_yticks(ticks)
```
[<matplotlib.axis.YTick at 0x7fdcac7ff850>,
<matplotlib.axis.YTick at 0x7fdcac7ff430>,
<matplotlib.axis.YTick at 0x7fdcac7dd280>,
<matplotlib.axis.YTick at 0x7fdcacbaed00>,
<matplotlib.axis.YTick at 0x7fdcacb9d250>,
<matplotlib.axis.YTick at 0x7fdcacb9d760>]
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_13_1.png">
## 3. spine
축의 선을 [spine](https://matplotlib.org/stable/api/spines_api.html?highlight=spine#module-matplotlib.spines)이라고 한다.
spine을 불러오기위해서는 axes.spines을 사용해야하며 dictionary는 아니지만 dictionary처럼 각 축을 'left','right','top','bottom'와 같은 key로 접근할 수 있다. items를 이용해 key와 spine을 모두 불러올 수 있다.
**Methods**
- spine.set_visible(bool_value): default=True, False를 사용하면 축이 보이지 않게 할 수 있다.
- spine.set_linewidth(width): line의 width를 설정
- spine.set_color(c): color 설정
- spine.set_position(position): 축의 위치를 조정한다.
- position: 2-tuple로 이루어져있다. 첫번째는 position type, 두번재는 amount이다.
- position type: 'axes'-spine 위치를 axes coordinate를 이용해 설정, 'data'-spine 위치를 data coordinate를 이용해 설정
- amount: 위치할 값
- 'center', 'zero'를 쓰기도 하는데 'center'=('axes',0.5), 'zero'=('data',0.0)을 가리킨다.
```python
fig,axes = plt.subplots(2,1,figsize=(7,7))
axes[1].spines['top'].set_visible(False)
axes[1].spines['right'].set_visible(False)
```
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_15_0.png">
```python
fig, ax = plt.subplots(figsize=(7,7))
ax.set_xlim([-1,1])
ax.set_ylim([-1,1])
for loc, spine in ax.spines.items():
if loc in ['top', 'right']:
spine.set_visible(False)
if loc in ['left','bottom']:
spine.set_position(('data',0))
```
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_16_0.png">
## 4. grid
grid형태의 line을 그려주는 method이다.
**[Axes.grid(which='major',axis='both',\*\*kwargs)](https://matplotlib.org/stable/api/_as_gen/matplotlib.pyplot.grid.html)**
- which: {'major', 'minor', 'both'}
- axis: {'both', 'x', 'y'}
- \*\*kawargs: Line2D properties, line에 적용될 수 있는 property를 적용할 수 있다.
- alpha: 투명도
- color: 색상
- linestyle: ('-', 일직선), ('-.',일직선과 점이 번갈아 나타남), (':', 점선)
- linewidth: line의 width 설정
```python
fig, axes = plt.subplots(2,1,figsize=(7,7))
ticks = np.arange(0,21,5)
for ax in axes.flat:
ax.set_xticks(ticks)
ax.set_yticks(ticks)
axes[0].grid(axis='x')
axes[1].grid(axis='y')
```
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_18_0.png">
```python
fig, ax = plt.subplots(figsize=(7,7))
major_ticks = np.arange(0,21,5)
minor_ticks = np.arange(21)
ax.set_xticks(major_ticks)
ax.set_xticks(minor_ticks,minor=True)
ax.set_yticks(major_ticks)
ax.set_yticks(minor_ticks,minor=True)
ax.tick_params(which='major',length=5,width=2,
labelsize=10,labelcolor='b')
ax.tick_params(which='minor',length=3)
ax.grid(which='major', linewidth=2)
ax.grid(which='minor', linewidth=1,alpha=0.5)
```
<img src="/assets/image/matplotlib-pyplot-03_files/matplotlib-pyplot-03_19_0.png">
| 27.349544 | 155 | 0.699711 | kor_Hang | 0.742291 |
0cdef36a94a8e2eda527b4ddd4548f0e0682f184 | 376 | md | Markdown | readme.md | emiljohansson/string-replace-first | 37e5541aa34143d0b5ff1d390afb20959e9f3951 | [
"MIT"
] | 1 | 2016-10-09T20:19:55.000Z | 2016-10-09T20:19:55.000Z | readme.md | emiljohansson/string-replace-first | 37e5541aa34143d0b5ff1d390afb20959e9f3951 | [
"MIT"
] | null | null | null | readme.md | emiljohansson/string-replace-first | 37e5541aa34143d0b5ff1d390afb20959e9f3951 | [
"MIT"
] | null | null | null | # string-replace-first
> Replaces first match of a pattern in a string.
## Usage
```js
var replaceFirst = require('string-replace-first');
replaceFirst('path/to/file', '/', '-');
// => 'path-to/file'
```
## API
### replaceFirst(str, pattern, newSubStr)
Returns the modified string.
#### str
Type: `string`
#### pattern
Type: `string`
#### newSubStr
Type: `string`
| 12.533333 | 51 | 0.640957 | eng_Latn | 0.588365 |
0cdf08eb20101d06fdabe9a2361351d016107f19 | 2,773 | md | Markdown | _posts/2019-09-06-iOS当中的AutoRelease.md | sunzhongliangde/sunzhongliangde.github.io | d080df335553be2453d11ef691189f45d5efad8e | [
"MIT"
] | 2 | 2020-03-08T10:27:10.000Z | 2021-12-24T13:51:07.000Z | _posts/2019-09-06-iOS当中的AutoRelease.md | sunzhongliangde/sunzhongliangde.github.io | d080df335553be2453d11ef691189f45d5efad8e | [
"MIT"
] | 54 | 2019-03-19T04:46:09.000Z | 2021-01-18T03:10:30.000Z | _posts/2019-09-06-iOS当中的AutoRelease.md | sunzhongliangde/sunzhongliangde.github.io | d080df335553be2453d11ef691189f45d5efad8e | [
"MIT"
] | null | null | null | ---
layout: post
title: iOS中的AutoRelease
subtitle:
date: 2019-09-06
author: sunzhongliang
header-img: img/post-bg-github-cup.jpg
catalog: true
tags:
- OC
---
## AutoRelease
在`MRC`时代，我们如果希望一个对象延迟释放的时候，通常会把这个对象标记为`autorelease`, 如
```objc
NSString *str = [[[NSString alloc] initWithString:@"hello"] autorelease];
```
后来在`ARC`的时候，我们甚至不用关心一个对象是什么时候release的, 系统总是能够在合适的时候帮我们去释放这个对象, 背后它究竟做了什么？
## ARC和MRC下的autorelease
#### ARC
`ARC`是苹果引入的一种自动内存管理机制，会根据引用计数自动监视对象的生存周期，实现方式是在编译时期自动在已有代码中插入合适的内存管理代码(release)以及在 `Runtime`做一些优化。
在`ARC`的情况下，编译器会在`RunLoop`休眠前执行释放的，而它能够释放的原因就是系统在每个`runloop`迭代中都加入了自动释放池`Push`和`Pop`
#### MRC
`MRC`机制下，对一个对象标记`autorelease`后，这个对象并不会马上被释放，而是当这段语句所处的 `autoreleasepool` 进行 `drain` 操作时，所有标记了 `autorelease` 的对象的 `retainCount` 会被 -1。即 `release` 消息的发送被延迟到 `pool` 释放的时候了。
## autoreleasepool
ARC下，我们使用`@autoreleasepool{}`来使用一个AutoreleasePool，随后编译器将其改写成下面的样子：
```objc
void *context = objc_autoreleasePoolPush();
// @autoreleasepool{}中的代码
objc_autoreleasePoolPop(context);
```
这两个函数都是对`AutoreleasePoolPage`的简单封装，所以自动释放机制的核心就在于这个类<br>
每个`AutoreleasePoolPage`对象占用`4096`字节内存，用来存放内部成员变量，剩下的空间用来存放autorelease对象的地址<br>
所有的`AutoreleasePoolPage`对象是通过双向链表的形式链接到一起<br>
`autoreleasePool`一开始会调用push方法将一个`POOL_BOUNDRY`入栈，并且返回其内存地址,在`autoreleasePool`结束时会调用`pop`方法传入一个`POOL_BOUNDRY`内存地址，会从最后一个入栈的对象发送`release`消息，一直到`POOL_BOUNDRY`为止，这样就实现了一个`autoreleasePool`块的所有对象`release`原理<br>
AutoreleasePoolPage内部的`id *next`指针指向了下一个能够存放autorelease对象的的地址，调用push时，从`id *next`获取下一个要存放的地址
<br>
*所以，向一个对象发送- autorelease消息，就是将这个对象加入到当前`AutoreleasePoolPage`的栈顶next指针指向的位置*
## Autorelease Pool 的用处
```objc
for (int i = 0; i < 100000000; i++)
{
@autoreleasepool
{
NSString* string = @"ab c";
NSArray* array = [string componentsSeparatedByString:string];
}
}
```
当我们需要创建和销毁大量的对象时，使用手动创建的 `autoreleasepool` 可以有效的避免内存峰值的出现。因为如果不手动创建的话，外层系统创建的 `pool` 会在整个 `runloop circle` 结束之后才进行 `drain`，手动创建的话，会在 `block` 结束之后就进行 `drain` 操作。
如果不使用 `autoreleasepool` ，需要在循环结束之后释放 100000000 个字符串，如果 使用的话，则会在每次循环结束的时候都进行 `release` 操作。
## main.m 中 Autorelease Pool
通常 iOS 程序的 main.m 文件中有类似这样的语句：
```objc
int main(int argc, char * argv[]) {
@autoreleasepool {
return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
}
}
```
`UIApplicationMain` 函数是整个 `app` 的入口，用来创建 `application` 对象（单例）和 `application delegate`。尽管这个函数有返回值，但是实际上却永远不会返回，当按下 `Home` 键时，由于主线程`Runloop`的存在，`app` 只是被切换到了后台状态。<br>
但由于这个函数永远不会返回，只有在系统 kill 掉整个 app 时，系统会把应用占用的内存全部释放出来。<br>
`UIApplication` 自己会创建 `main run loop`，在 `Cocoa` 的 `runloop` 中实际上也是自动包含 `autorelease pool` 的，因此 `main.m` 当中的 `pool` 可以认为是没有必要的。<br>
直接删掉是没问题的，但由于苹果不建议修改`main.m`，所以我们一般不会将它直接删掉
> 本文首次发布于 [孙忠良 Blog](https://sunzhongliangde.github.io), 作者 [@sunzhongliang] ,
转载请保留原文链接.
| 35.101266 | 204 | 0.766318 | yue_Hant | 0.660077 |
0cdfeeb1f1c4b2f0d529cd7284d9006ceb5fcfa1 | 1,952 | md | Markdown | README.md | danielrotaermel/ubermap | 6c6098f7d30b0f53beedb82671124e10ea9f3380 | [
"CC-BY-4.0"
] | 6 | 2019-02-18T13:40:58.000Z | 2021-12-23T12:45:20.000Z | README.md | danielrotaermel/ubermap | 6c6098f7d30b0f53beedb82671124e10ea9f3380 | [
"CC-BY-4.0"
] | null | null | null | README.md | danielrotaermel/ubermap | 6c6098f7d30b0f53beedb82671124e10ea9f3380 | [
"CC-BY-4.0"
] | 2 | 2018-10-20T10:55:28.000Z | 2020-12-14T19:36:28.000Z | # Ubermap v1.0.0b2 [](https://www.paypal.me/tomduncalf/10)
## Introduction
Ubermap is a script for Ableton Live to allow Push users to create custom parameter mappings for VST and AU plugins on the Push display.
Features:
- Easy customisation of device bank and parameter names displayed on Push for devices, using simple configuration files
- Modify configurations instantly without reloading Live
## For more information, [see the main README](https://github.com/tomduncalf/ubermap/blob/master/Devices/README.md) and [the thread on the Ableton forum](https://forum.ableton.com/viewtopic.php?f=55&t=221501&sid=f8b1a012a123a51a16838c8698a28b8a)
## Disclaimer
This alpha release is intended only for advanced users who are willing to risk things breaking, and is not production ready. It hasn't been tested on any machines other than my own, so might not work at all or might do something really bad :)
This script changes your Ableton MIDI Remote configs, and could introduce instability or potentially even data corruption, so please do not use it on your main machine and ensure you have backups of all your data before using.
The author cannot be help responsible for any harm or damage resulting from the use of the software.
## Licence
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License
## Logging
Ubermap components log to ~/Ubermap/main.log, and the log level is controlled by the settings in ~/Ubermap/global.cfg. Debug logging is turned off by default, as it is very verbose, info logging is turned on, and error logging cannot be disabled. The log file is wiped out each time the script restarts (e.g. when restarting Ableton) so shouldn't grow to be massive.
## Support
For support, please ask in the thread on the Ableton forum - I can't offer any guarantees of support but will try and help.
| 59.151515 | 366 | 0.789959 | eng_Latn | 0.996709 |
0ce0628dbcec457f81c0ba83c6b505169a649a8f | 3,102 | md | Markdown | _posts/2017-12-27-ubuntu-gaming.md | minwook-shin/minwook-shin.github.com | 3330dab2692d6e3a34cc07bfb5df55f6a9f8b9dd | [
"MIT"
] | null | null | null | _posts/2017-12-27-ubuntu-gaming.md | minwook-shin/minwook-shin.github.com | 3330dab2692d6e3a34cc07bfb5df55f6a9f8b9dd | [
"MIT"
] | null | null | null | _posts/2017-12-27-ubuntu-gaming.md | minwook-shin/minwook-shin.github.com | 3330dab2692d6e3a34cc07bfb5df55f6a9f8b9dd | [
"MIT"
] | null | null | null | ---
layout: post
title: gaming on ubuntu
---
안녕하세요. 오늘은 약 3년 전으로 거슬러 올라가서, 제가 우분투 한국 커뮤니티에서 발표한 내용을 서술해보고 2018년이 다가오는 현재는 어떠한지 끄적여볼 예정입니다.
## 우분투에서 게임이 될까요
우선 2017년 기준은 마지막에 설명할 예정이니 패스하고, 2년 전 발표했을 때를 기억하며 말씀드리자면
"되긴 되는데 음..." 정도였습니다.
우분투에서 게임 잘되냐고 묻는 타인의 질문에도 "잘 안되는데?"라고만 대답할 정도죠.
근데 저는 되게 해보고 싶었습니다.
윈도우는 구동시키기 어려운 (지금은 사라진 유물인)넷북을 쓰면서, 우분투에서 게임이 되나 혼자서 트러블 슈팅했습니다.
## 덕질을 하니 발표할 기회가 찾아왔습니다
뭐든지 집중해서 하다보면 뭔가 기회가 오더군요.
15년 3월인가 4월즈음에 이러한 주제로 발표해보겠다고 말해보니, 바로 성사되었습니다.
## 1편
<iframe src="//www.slideshare.net/slideshow/embed_code/key/5gl0FXeYHXI3Jf" width="595" height="485" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC; border-width:1px; margin-bottom:5px; max-width: 100%;" allowfullscreen> </iframe> <div style="margin-bottom:5px"> <strong> <a href="//www.slideshare.net/UbuntuKorea/minwook-shin-201505-2015y05m30d" title="우분투에서 게이밍은? | 신민욱 Minwook Shin | 2015.05 (2015Y05M30D)" target="_blank">우분투에서 게이밍은? | 신민욱 Minwook Shin | 2015.05 (2015Y05M30D)</a> </strong> from <strong><a href="https://www.slideshare.net/UbuntuKorea" target="_blank">Ubuntu Korea Community</a></strong> </div>
1편은 우분투 한국 커뮤니티 5월 세미나에서 여태까지 삽질한 경험을 위주로 써보았습니다.
1편의 주용 내용은 제가 중학생때 삽질한 기억부터 시작해서 현재 우분투에서 게임을 해보려고 삽질한 내용을 공유한 것입니다.
만약 삽질해서 성공했다면, 어떻게 해서 성공했는지도 언급했습니다.
발표했던 날짜를 기준으로는 정상적으로 한글이 출력되게 게임하려면 꽤 많은 관문(?)을 통과해야됬었습니다만,
다행히도 지금 이 시점에서는 이미 고쳐져서 안해도 무난하게 작동되고 있습니다.
# 2편
2편은 영광스럽게도 [kcd 2015](http://kcd2015.onoffmix.com/)에서 진행했습니다 ^^ (다시는 오지않을 기회였죠.)
1편의 대부분을 먼저 (재탕) 발표하고, 그동안 바뀐 점에 대하여 언급하며 이어서 2편하는 형태입니다.
2편에서는 주로 html로 게임할 수 있다!는 내용을 담았고, 깃허브를 이용해 간단히 html로 이루워진 게임을 포크로 담아온 후 즐기자는 내용이 있습니다.
웹은 그 당시 기준으로도 웹브라우저별 표준 지원능력(?)이 비슷해서 웹 gooood!이라고 언급하며 끝냈던 기억이 납니다.
[이 곳](http://kcd2015.onoffmix.com/decks/Track1/Track1_Session1_신민욱_gaming_on_ubuntu_2.pdf)에서 PDF 형식으로 보실 수 있습니다.
## 그렇다면 현재는 게임이 되나요
결과부터 말씀드리자면 똑같습니다.
아니... 비슷하다고 해야될지 모르겠습니다.
여전히 국내 게임은 미지원이며, 모두가 아는 전설의 N사 독점 드라이버는 여전히 잘 나옵니다.
하지만, 스팀의 리눅스 지원 게임은 나날히 늘어나고 있고, 최근(12월 27일) Vulkan driver를 사용하는 ["Radeon Software for Linux"](http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-for-Linux-Release-Notes.aspx)를 오픈소스로 공개해서 여전히 그대로라고는 느끼진 않습니다.
또한 올해 모질라에서 [Firefox Quantum](https://www.mozilla.org/ko/firefox/)을 출시하여 우분투 기본 탑제 브라우저인 파이어폭스의 인터넷 서핑 환경을 쾌적하게 만들어 주기도 했습니다.
(추가로 알아보니, [WebAssembly](https://developer.mozilla.org/ko/docs/WebAssembly) 프로젝트도 진행되고 있었습니다.)
<blockquote class="twitter-tweet" data-lang="ko"><p lang="en" dir="ltr">Another round of renderer optimizations done, large CTF levels are now running at a solid 60 FPS <a href="https://twitter.com/hashtag/quakejs?src=hash&ref_src=twsrc%5Etfw">#quakejs</a> <a href="http://t.co/Dsvci3Ad">pic.twitter.com/Dsvci3Ad</a></p>— Anthony Pesch (@inolen) <a href="https://twitter.com/inolen/status/275752910862831616?ref_src=twsrc%5Etfw">2012년 12월 4일</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
## 마무리
체감하기엔 아직 멀게 느껴지지만, 점점 우분투에서 게임하기 좋은 환경으로 변하고 있는 것은 맞습니다.
이제부터 기반이 잡힌다면, 게임사에서 LINUX 지원을 고려하지 않을까... 싶습니다.
아마도 계속 기다려주면 언젠가 될거 같습니다. | 43.083333 | 660 | 0.731786 | kor_Hang | 1.000003 |
0ce0a3eefa5383ed2a6499ea13a7353543d6aa24 | 10,088 | md | Markdown | docs/sql-ref-syntax-aux-show-table.md | OlegPt/spark | c79fd911ca85f883c493c5e888f7690868d7b5ea | [
"Apache-2.0"
] | 28 | 2020-07-17T08:30:31.000Z | 2021-11-16T11:41:48.000Z | docs/sql-ref-syntax-aux-show-table.md | OlegPt/spark | c79fd911ca85f883c493c5e888f7690868d7b5ea | [
"Apache-2.0"
] | 56 | 2015-09-22T23:51:32.000Z | 2020-10-27T17:22:30.000Z | docs/sql-ref-syntax-aux-show-table.md | OlegPt/spark | c79fd911ca85f883c493c5e888f7690868d7b5ea | [
"Apache-2.0"
] | 17 | 2015-09-05T06:03:35.000Z | 2019-10-24T11:31:37.000Z | ---
layout: global
title: SHOW TABLE EXTENDED
displayTitle: SHOW TABLE EXTENDED
license: |
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
---
### Description
`SHOW TABLE EXTENDED` will show information for all tables matching the given regular expression.
Output includes basic table information and file system information like `Last Access`,
`Created By`, `Type`, `Provider`, `Table Properties`, `Location`, `Serde Library`, `InputFormat`,
`OutputFormat`, `Storage Properties`, `Partition Provider`, `Partition Columns` and `Schema`.
If a partition specification is present, it outputs the given partition's file-system-specific
information such as `Partition Parameters` and `Partition Statistics`. Note that a table regex
cannot be used with a partition specification.
### Syntax
```sql
SHOW TABLE EXTENDED [ { IN | FROM } database_name ] LIKE regex_pattern
[ partition_spec ]
```
### Parameters
* **{ IN`|`FROM } database_name**
Specifies database name. If not provided, will use the current database.
* **regex_pattern**
Specifies the regular expression pattern that is used to filter out unwanted tables.
* Except for `*` and `|` character, the pattern works like a regular expression.
* `*` alone matches 0 or more characters and `|` is used to separate multiple different regular expressions,
any of which can match.
* The leading and trailing blanks are trimmed in the input pattern before processing. The pattern match is case-insensitive.
* **partition_spec**
An optional parameter that specifies a comma separated list of key and value pairs
for partitions. Note that a table regex cannot be used with a partition specification.
**Syntax:** `PARTITION ( partition_col_name = partition_col_val [ , ... ] )`
### Examples
```sql
-- Assumes `employee` table created with partitioned by column `grade`
CREATE TABLE employee(name STRING, grade INT) PARTITIONED BY (grade);
INSERT INTO employee PARTITION (grade = 1) VALUES ('sam');
INSERT INTO employee PARTITION (grade = 2) VALUES ('suj');
-- Show the details of the table
SHOW TABLE EXTENDED LIKE 'employee';
+--------+---------+-----------+--------------------------------------------------------------+
|database|tableName|isTemporary| information |
+--------+---------+-----------+--------------------------------------------------------------+
|default |employee |false |Database: default
Table: employee
Owner: root
Created Time: Fri Aug 30 15:10:21 IST 2019
Last Access: Thu Jan 01 05:30:00 IST 1970
Created By: Spark 3.0.0-SNAPSHOT
Type: MANAGED
Provider: hive
Table Properties: [transient_lastDdlTime=1567158021]
Location: file:/opt/spark1/spark/spark-warehouse/employee
Serde Library: org.apache.hadoop.hive.serde2.lazy
.LazySimpleSerDe
InputFormat: org.apache.hadoop.mapred.TextInputFormat
OutputFormat: org.apache.hadoop.hive.ql.io
.HiveIgnoreKeyTextOutputFormat
Storage Properties: [serialization.format=1]
Partition Provider: Catalog
Partition Columns: [`grade`]
Schema: root
|-- name: string (nullable = true)
|-- grade: integer (nullable = true)
+--------+---------+-----------+--------------------------------------------------------------+
-- showing the multiple table details with pattern matching
SHOW TABLE EXTENDED LIKE `employe*`;
+--------+---------+-----------+--------------------------------------------------------------+
|database|tableName|isTemporary| information |
+--------+---------+-----------+--------------------------------------------------------------+
|default |employee |false |Database: default
Table: employee
Owner: root
Created Time: Fri Aug 30 15:10:21 IST 2019
Last Access: Thu Jan 01 05:30:00 IST 1970
Created By: Spark 3.0.0-SNAPSHOT
Type: MANAGED
Provider: hive
Table Properties: [transient_lastDdlTime=1567158021]
Location: file:/opt/spark1/spark/spark-warehouse/employee
Serde Library: org.apache.hadoop.hive.serde2.lazy
.LazySimpleSerDe
InputFormat: org.apache.hadoop.mapred.TextInputFormat
OutputFormat: org.apache.hadoop.hive.ql.io
.HiveIgnoreKeyTextOutputFormat
Storage Properties: [serialization.format=1]
Partition Provider: Catalog
Partition Columns: [`grade`]
Schema: root
|-- name: string (nullable = true)
|-- grade: integer (nullable = true)
|default |employee1|false |Database: default
Table: employee1
Owner: root
Created Time: Fri Aug 30 15:22:33 IST 2019
Last Access: Thu Jan 01 05:30:00 IST 1970
Created By: Spark 3.0.0-SNAPSHOT
Type: MANAGED
Provider: hive
Table Properties: [transient_lastDdlTime=1567158753]
Location: file:/opt/spark1/spark/spark-warehouse/employee1
Serde Library: org.apache.hadoop.hive.serde2.lazy
.LazySimpleSerDe
InputFormat: org.apache.hadoop.mapred.TextInputFormat
OutputFormat: org.apache.hadoop.hive.ql.io
.HiveIgnoreKeyTextOutputFormat
Storage Properties: [serialization.format=1]
Partition Provider: Catalog
Schema: root
|-- name: string (nullable = true)
+--------+---------+----------+---------------------------------------------------------------+
-- show partition file system details
SHOW TABLE EXTENDED IN default LIKE `employee` PARTITION (`grade=1`);
+--------+---------+-----------+--------------------------------------------------------------+
|database|tableName|isTemporary| information |
+--------+---------+-----------+--------------------------------------------------------------+
|default |employee |false |Partition Values: [grade=1]
Location: file:/opt/spark1/spark/spark-warehouse/employee
/grade=1
Serde Library: org.apache.hadoop.hive.serde2.lazy
.LazySimpleSerDe
InputFormat: org.apache.hadoop.mapred.TextInputFormat
OutputFormat: org.apache.hadoop.hive.ql.io
.HiveIgnoreKeyTextOutputFormat
Storage Properties: [serialization.format=1]
Partition Parameters: {rawDataSize=-1, numFiles=1,
transient_lastDdlTime=1567158221, totalSize=4,
COLUMN_STATS_ACCURATE=false, numRows=-1}
Created Time: Fri Aug 30 15:13:41 IST 2019
Last Access: Thu Jan 01 05:30:00 IST 1970
Partition Statistics: 4 bytes
|
+--------+---------+-----------+--------------------------------------------------------------+
-- show partition file system details with regex fails as shown below
SHOW TABLE EXTENDED IN default LIKE `empl*` PARTITION (`grade=1`);
Error: Error running query: org.apache.spark.sql.catalyst.analysis.NoSuchTableException:
Table or view 'emplo*' not found in database 'default'; (state=,code=0)
```
### Related Statements
* [CREATE TABLE](sql-ref-syntax-ddl-create-table.html)
* [DESCRIBE TABLE](sql-ref-syntax-aux-describe-table.html)
| 55.734807 | 171 | 0.48751 | eng_Latn | 0.528792 |
0ce1c6c3d510839384c2a1278cf0c6c262d8ec7b | 645 | md | Markdown | practice/overview.md | optivem/python | c3ed13c2d0ddc05a1b91f5478bd236064174fe53 | [
"MIT"
] | null | null | null | practice/overview.md | optivem/python | c3ed13c2d0ddc05a1b91f5478bd236064174fe53 | [
"MIT"
] | null | null | null | practice/overview.md | optivem/python | c3ed13c2d0ddc05a1b91f5478bd236064174fe53 | [
"MIT"
] | null | null | null | # Overview
The core process and participants within EA practice, based on works of Svyatoslav Kotusev.
### External Business Environment
\(Economy, technology, society, demography, legislation, regulation, competitors, partners, suppliers, customers, etc.\)
### Organizational IT Landscape
\(Existing applications, information systems, databases, integration platforms, network and server infrastructure, etc.\)
### References
Source: Enterprise Architecture Practice on a Page v1.1 \([http://eaonapage.com](http://eaonapage.com)\), Svyatoslav Kotusev \([http://kotusev.com](http://kotusev.com)\)
| 33.947368 | 169 | 0.75969 | eng_Latn | 0.381719 |
0ce2324a355c35ab5db5c4177b8f81e3662e2d7c | 587 | md | Markdown | _posts/codingtest-sql/2022-04-25-lv2-1.md | minju412/minju412.github.io | f973b0bd6452461237cb8b3057d80bda8efddea4 | [
"MIT"
] | null | null | null | _posts/codingtest-sql/2022-04-25-lv2-1.md | minju412/minju412.github.io | f973b0bd6452461237cb8b3057d80bda8efddea4 | [
"MIT"
] | null | null | null | _posts/codingtest-sql/2022-04-25-lv2-1.md | minju412/minju412.github.io | f973b0bd6452461237cb8b3057d80bda8efddea4 | [
"MIT"
] | 1 | 2022-02-26T17:22:55.000Z | 2022-02-26T17:22:55.000Z | ---
title: "[SQL-CodingTest] Lv2. 고양이와 개는 몇 마리 있을까"
categories:
- SQL
tags:
- [Programmers, SQL]
toc: true
toc_sticky: true
date: 2022-04-25
last_modified_at: 2022-04-25
---
# 고양이와 개는 몇 마리 있을까
## 문제 정리
동물 보호소에 들어온 동물 중 고양이와 개가 각각 몇 마리인지 조회하는 SQL문을 작성해주세요. 이때 고양이를 개보다 먼저 조회해주세요.
## 내 답
```sql
SELECT animal_type, count(animal_type) as count
from animal_ins
group by animal_type
order by animal_type
```
# 정리
- `group by`를 이용해 타입 별 카운트 하기
> SELECT 컬럼, COUNT(컬럼) FROM 테이블명 GROUP BY 컬럼
***
<br>
💛 개인 공부 기록용 블로그입니다. 👻
[맨 위로 이동하기](#){: .btn .btn--primary }{: .align-right} | 16.771429 | 76 | 0.659284 | kor_Hang | 0.999994 |
0ce2ab38ce70a89b234f0da190e814bfb15d5a1f | 1,138 | md | Markdown | README.md | themsiqueira/melhorenvio | 7f5790332aab2d3fe299b3c37d8d615d02c73855 | [
"MIT"
] | 4 | 2020-06-30T04:32:39.000Z | 2021-01-14T13:15:58.000Z | README.md | themsiqueira/melhorenvio | 7f5790332aab2d3fe299b3c37d8d615d02c73855 | [
"MIT"
] | 5 | 2020-06-14T18:00:06.000Z | 2020-07-03T03:30:03.000Z | README.md | themsiqueira/melhorenvio | 7f5790332aab2d3fe299b3c37d8d615d02c73855 | [
"MIT"
] | null | null | null | ## Melhor Envio's integration interface in javascript 🤟
### TL;DR
Analogous to a **facade pattern** in architecture, **this package** is an **arrange of objects that serves as a front-facing interface** masking more complex underlying and structural code of [Melhor envio](https://docs.menv.io/?version=latest#064ee1d6-661c-455c-842c-ef7cebbfd5d4)'s API.
### Installation
- NPM
```shell
npm i melhor-envio-js
```
- YARN
```shell
yarn add melhor-envio-js
### Contributing
Please feel free to open any issues you might come up with and to submit your own PRs. There is not a contributing guide yet
### Contributors
Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
<!-- prettier-ignore -->
<!-- ALL-CONTRIBUTORS-LIST:END -->
This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!
## TODO
* unit tests
* integration tests
* schema validation
### License
Melhor Envio is [MIT licensed](./LICENSE).
| 29.947368 | 288 | 0.732865 | eng_Latn | 0.87387 |
0ce2b7b734b293a0d3fd23b5a129aac4a1395078 | 2,632 | md | Markdown | includes/aml-create-in-portal.md | macdrai/azure-docs.fr-fr | 59bc35684beaba04a4f4c09a745393e1d91428db | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/aml-create-in-portal.md | macdrai/azure-docs.fr-fr | 59bc35684beaba04a4f4c09a745393e1d91428db | [
"CC-BY-4.0",
"MIT"
] | null | null | null | includes/aml-create-in-portal.md | macdrai/azure-docs.fr-fr | 59bc35684beaba04a4f4c09a745393e1d91428db | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Fichier Include
description: Fichier Include
services: machine-learning
author: sdgilley
ms.service: machine-learning
ms.author: sgilley
manager: cgronlund
ms.custom: include file
ms.topic: include
ms.date: 11/04/2019
ms.openlocfilehash: f5f132d257e30cd8f4fa1153087bf0df2f0f5b2c
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 10/09/2020
ms.locfileid: "91841840"
---
1. Connectez-vous au [Portail Azure](https://portal.azure.com/) à l’aide des informations d’identification de votre abonnement Azure.
1. En haut à gauche du portail Azure, sélectionnez **+Créer une ressource**.
1. Utilisez la barre de recherche pour rechercher **Machine Learning**.
1. Sélectionnez **Machine Learning**.
1. Dans le volet **Machine Learning**, sélectionnez **Créer** pour commencer.
1. Fournissez les informations suivantes pour configurer votre nouvel espace de travail :
Champ|Description
---|---
Nom de l’espace de travail |Entrez un nom unique qui identifie votre espace de travail. Dans cet exemple, nous allons utiliser **docs-ws**. Dans le groupe de ressources, les noms doivent être uniques. Utilisez un nom dont il est facile de se rappeler et que vous pouvez facilement différencier des autres espaces de travail.
Subscription |Sélectionnez l’abonnement Azure que vous souhaitez utiliser.
Resource group | Utilisez un groupe de ressources existant dans votre abonnement, ou entrez un nom pour créer un groupe de ressources. Un groupe de ressources contient les ressources associées d’une solution Azure. Dans cet exemple, nous allons utiliser **docs-aml**.
Location | Sélectionnez l’emplacement le plus proche de vos utilisateurs et des ressources de données pour créer votre espace de travail.
Édition de l’espace de travail | Sélectionnez **De base** comme type d’espace de travail pour ce didacticiel. Ce type d’espace de travail détermine les fonctionnalités auxquelles vous aurez accès et leur tarification. Tous les éléments de ce didacticiel peuvent être exécutés avec un espace de travail De base ou Enterprise.
1. Lorsque vous avez terminé de configurer l’espace de travail, sélectionnez **Vérifier + créer**.
> [!Warning]
> La création de votre espace de travail dans le cloud peut prendre plusieurs minutes.
Une fois le processus terminé, un message indiquant la réussite du déploiement s’affiche.
1. Pour afficher le nouvel espace de travail, sélectionnez **Accéder à la ressource**.
| 52.64 | 327 | 0.784574 | fra_Latn | 0.986604 |
0ce31750842b5d591313d5f88a6b3cf4af329521 | 930 | md | Markdown | README.md | morishin/SwiftyUserDefaults | 00e23f5d38b341cdfc7d6329f09c0f47ea5a7545 | [
"MIT"
] | 1 | 2017-02-15T20:26:17.000Z | 2017-02-15T20:26:17.000Z | README.md | morishin/SwiftyUserDefaults | 00e23f5d38b341cdfc7d6329f09c0f47ea5a7545 | [
"MIT"
] | null | null | null | README.md | morishin/SwiftyUserDefaults | 00e23f5d38b341cdfc7d6329f09c0f47ea5a7545 | [
"MIT"
] | null | null | null | # BetterUserDefaults
[](https://github.com/Carthage/Carthage)
UserDefaults Swift Extensions
## Usage
```swift
import BetterUserDefaults
extension UserDefaults.Key {
static let sampleKeyA = UserDefaults.Key("sampleKeyA")
static let sampleKeyB = UserDefaults.Key("sampleKeyB")
}
UserDefaults.standard.set(true, for: .sampleKeyA)
UserDefaults.standard.set(123, for: .sampleKeyB)
UserDefaults.standard.bool(for: .sampleKeyA) // true
UserDefaults.standard.integer(for: .sampleKeyB) // 123
```
## Installation
### Carthage
Cartfile
```
github "morishin/BetterUserDefaults"
```
### CocoaPods
Podfile
```ruby
pod 'BetterUserDefaults'
```
## LICENSE
MIT
| 21.627907 | 134 | 0.750538 | yue_Hant | 0.474022 |
0ce3fa613f1807c195ec9e0fb452d8e1d2d4c558 | 3,222 | md | Markdown | docs/pipelines/tasks/test/container-structure-test-task.md | andyarroyo5/azure-devops.es-ES | 86e715daf518c97c46050a55ef4c2551c29d69b7 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-03-03T18:57:40.000Z | 2020-03-03T18:57:40.000Z | docs/pipelines/tasks/test/container-structure-test-task.md | andyarroyo5/azure-devops.es-ES | 86e715daf518c97c46050a55ef4c2551c29d69b7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/pipelines/tasks/test/container-structure-test-task.md | andyarroyo5/azure-devops.es-ES | 86e715daf518c97c46050a55ef4c2551c29d69b7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Container Structure Test Task
description: Test container structure by container task and integrate test reporting into your build and release pipelines
ms.assetid: 6A752841-345D-4BC6-8765-C45F63D91D75
ms.prod: devops
ms.technology: devops-cicd
ms.topic: reference
ms.manager: mijacobs
ms.custom: seodec18
ms.author: admahesh
author: Additi
ms.date: 10/01/2019
monikerRange: 'azure-devops'
---
# Container Structure Tests
The Container Structure Tests provide a powerful framework to validate the structure of a container image. These tests can be used to check the output of commands in an image, as well as verify metadata and contents of the filesystem. Tests can be run either through a standalone binary, or through a Docker image.
Tests within this framework are specified through a YAML or JSON config file. Multiple config files may be specified in a single test run. The config file will be loaded in by the test runner, which will execute the tests in order. Within this config file, four types of tests can be written:
* Command Tests (testing output/error of a specific command issued)
* File Existence Tests (making sure a file is, or isn't, present in the file system of the image)
* File Content Tests (making sure files in the file system of the image contain, or do not contain, specific contents)
* Metadata Test, singular (making sure certain container metadata is correct)
## Container Structure Test Task
This task helps you run container structure tests and publish test results to Azure Pipelines and provides a comprehensive test reporting and analytics experience.
> [!NOTE]
> This is an early preview feature. More upcoming features will be rolled out in upcoming sprints.
## Build, Test and Publish Test
The container structure test task can be added in the classic pipeline as well as in unified pipeline (multi-stage) & YAML based pipelines.
# [YAML](#tab/yaml)
In the new YAML based unified pipeline, you can search for task in the window.
> [!div class="mx-imgBorder"]
> 
Once the task is added, you need to set the config file path, docker registory service connection, container repository and tag, if required. Task input in the yaml based pipeline is created.
> [!div class="mx-imgBorder"]
> 
### YAML file
> [!div class="mx-imgBorder"]
> 
Sample YAML
[!INCLUDE [temp](../includes/yaml/ContainerStructureTestV1.md)]
# [Classic](#tab/classic)
In the classic pipeline, you can add this task from the designer view.
> [!div class="mx-imgBorder"]
> 
* * *
## View test report
Once the task is executed, you can directly go to test tab to view the full report. The published test results are displayed in the [Tests tab](../../test/review-continuous-test-results-after-build.md)
in the pipeline summary and help you to measure pipeline quality, review traceability,
troubleshoot failures, and drive failure ownership.
> [!div class="mx-imgBorder"]
> 
| 41.844156 | 315 | 0.773122 | eng_Latn | 0.991622 |
0ce44df18357ef4eee19d6c0b69544e3ea9a1821 | 4,306 | md | Markdown | desktop-src/OpenGL/glmultmatrixd.md | crushonme/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | desktop-src/OpenGL/glmultmatrixd.md | crushonme/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | desktop-src/OpenGL/glmultmatrixd.md | crushonme/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: glMultMatrixd function
description: The glMultMatrixd and glMultMatrixf functions multiply the current matrix by an arbitrary matrix.
ms.assetid: 1f6cf4e4-e7bd-470c-b1f4-b9ccc1fb756e
keywords:
- glMultMatrixd function OpenGL
topic_type:
- apiref
api_name:
- glMultMatrixd
api_location:
- Opengl32.dll
api_type:
- DllExport
ms.topic: reference
ms.date: 05/31/2018
---
# glMultMatrixd function
The **glMultMatrixd** and [**glMultMatrixf**](glmultmatrixf.md) functions multiply the current matrix by an arbitrary matrix.
## Syntax
```C++
void WINAPI glMultMatrixd(
const GLdouble *m
);
```
## Parameters
<dl> <dt>
*m*
</dt> <dd>
A pointer to a 4x4 matrix stored in column-major order as 16 consecutive values.
</dd> </dl>
## Return value
This function does not return a value.
## Error codes
The following error code can be retrieved by the [**glGetError**](glgeterror.md) function.
| Name | Meaning |
|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
| <dl> <dt>**GL\_INVALID\_OPERATION**</dt> </dl> | The function was called between a call to [**glBegin**](glbegin.md) and the corresponding call to [**glEnd**](glend.md).<br/> |
## Error codes
The following error code can be retrieved by the [**glGetError**](glgeterror.md) function.
| Name | Meaning |
|-------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
| <dl> <dt>**GL\_INVALID\_OPERATION**</dt> </dl> | The function was called between a call to [**glBegin**](glbegin.md) and the corresponding call to [**glEnd**](glend.md).<br/> |
## Remarks
The **glMultMatrix** function multiplies the current matrix by the one specified in *m*. That is, if M is the current matrix and T is the matrix passed to **glMultMatrix**, then M is replaced with M T.
The current matrix is the projection matrix, modelview matrix, or texture matrix, determined by the current matrix mode (see [**glMatrixMode**](glmatrixmode.md)).
The *m* parameter points to a 4x4 matrix of single-precision or double-precision floating-point values stored in column-major order. That is, the matrix is stored as shown in the following image.
The following functions retrieve information related to **glMultMatrix**:
[**glGet**](glgetbooleanv--glgetdoublev--glgetfloatv--glgetintegerv.md) with argument GL\_MATRIX\_MODE
**glGet** with argument GL\_MODELVIEW\_MATRIX
**glGet** with argument GL\_PROJECTION\_MATRIX
**glGet** with argument GL\_TEXTURE\_MATRIX
## Requirements
| | |
|-------------------------------------|-----------------------------------------------------------------------------------------|
| Minimum supported client<br/> | Windows 2000 Professional \[desktop apps only\]<br/> |
| Minimum supported server<br/> | Windows 2000 Server \[desktop apps only\]<br/> |
| Header<br/> | <dl> <dt>Gl.h</dt> </dl> |
| Library<br/> | <dl> <dt>Opengl32.lib</dt> </dl> |
| DLL<br/> | <dl> <dt>Opengl32.dll</dt> </dl> |
## See also
<dl> <dt>
[**glBegin**](glbegin.md)
</dt> <dt>
[**glEnd**](glend.md)
</dt> <dt>
[**glLoadIdentity**](glloadidentity.md)
</dt> <dt>
[**glLoadMatrix**](glloadmatrix.md)
</dt> <dt>
[**glMatrixMode**](glmatrixmode.md)
</dt> <dt>
[**glPushMatrix**](glpushmatrix.md)
</dt> </dl>
| 31.430657 | 241 | 0.487692 | eng_Latn | 0.735088 |
0ce50013f9d91530da24b4a69e7e25fc5c69d0c2 | 12,139 | md | Markdown | README.md | skaldarnar/TerasologyLauncher | b97c64c0d439d335e654174b872bcb4e1c12b0b4 | [
"Apache-2.0"
] | 157 | 2015-01-08T07:34:21.000Z | 2022-03-26T21:52:18.000Z | README.md | PowerOlive/TerasologyLauncher | f0757ad5097b6c29a5ad5022733b24d8c1b4e6fd | [
"Apache-2.0"
] | 328 | 2015-01-06T17:22:40.000Z | 2022-01-12T11:52:09.000Z | README.md | PowerOlive/TerasologyLauncher | f0757ad5097b6c29a5ad5022733b24d8c1b4e6fd | [
"Apache-2.0"
] | 97 | 2015-01-06T07:51:08.000Z | 2021-12-08T19:33:45.000Z | <p align="center"><img src="./docs/images/logo.png" height=400px/></>
<div align="center">
<img src="https://github.com/MovingBlocks/TerasologyLauncher/workflows/Push%20Validation/badge.svg" alt="Build Status"/>
<a href="https://github.com/MovingBlocks/TerasologyLauncher/releases/latest">
<img src="https://img.shields.io/github/v/release/MovingBlocks/TerasologyLauncher" alt="Release" />
</a>
<a href="http://www.apache.org/licenses/LICENSE-2.0.html">
<img src="https://img.shields.io/github/license/MovingBlocks/TerasologyLauncher" alt="License" />
</a>
</div>
<h3 align="center"><b>
<a href="#community">Community</a> |
<a href="#installation-">Installation</a> |
<a href="#features">Features</a> |
<a href="#development">Development</a> |
<a href="#acknowledgements">Acknowledgements</a> |
<a href="#license-">License</a>
</b></h3>
[_Terasology Launcher_][github terasologylauncher] is the official launcher for the open source game [Terasology][github terasology]. It provides easy access to the different game versions and build types. Terasology and related projects are developed by a group of software enthusiast volunteers under the organization name [MovingBlocks][github movingblocks].
## Community
If you want to get in contact with the **Terasology** community and the whole **MovingBlocks** team, you can easily connect with us, share your ideas, report and solve problems.
We are present in nearly the complete round-up of social networks. Follow/friend us wherever you want, chat with us and tell the world.
<p align="center">
<a title="Terasology Forum" href="https://forum.terasology.org">
<img src="./src/main/resources/org/terasology/launcher/images/forum.png" width="48px"/>
</a>
<a title="Discord" href="https://discord.gg/terasology">
<img src="./src/main/resources/org/terasology/launcher/images/discord.png" width="48px"/>
</a>
<a title="IRC Webchat" href="http://webchat.freenode.net/?channels=terasology&uio=d4?channels=%23terasology&nick=Terasologist...&prompt=1&useUserListIcons=true">
<img src="./src/main/resources/org/terasology/launcher/images/webchat.png" width="48px"/>
</a>
<a title="Twitter" href="https://twitter.com/Terasology">
<img src="./src/main/resources/org/terasology/launcher/images/twitter.png" width="48px"/>
</a>
<a title="Facebook" href="https://www.facebook.com/Terasology">
<img src="./src/main/resources/org/terasology/launcher/images/facebook.png" width="48px"/>
</a>
<a title="Reddit" href="http://www.reddit.com/r/Terasology">
<img src="./src/main/resources/org/terasology/launcher/images/reddit.png" width="48px"/>
</a>
<a title="Youtube" href="https://www.youtube.com/user/blockmaniaTV">
<img src="./src/main/resources/org/terasology/launcher/images/youtube.png" width="48px"/>
</a>
<a title="Patreon" href="https://www.patreon.com/Terasology">
<img src="./src/main/resources/org/terasology/launcher/images/patreon.jpg" width="48px"/>
</a>
<a title="GitHub Issues" href="https://github.com/MovingBlocks/TerasologyLauncher/issues">
<img src="./src/main/resources/org/terasology/launcher/images/github.png" width="48px"/>
</a>
</p>
## Installation [][latest-release]
1. Download the corresponding archive for your platform from the [latest release][latest-release]
1. Extract the archive to the path where the launcher should be installed
1. Start _Terasology Launcher_
<table align="center">
<thead align="left"><tr>
<th width="40%">Operating System</th>
<th width="60%">Executable</th>
</tr></thead>
<tr>
<td width="40%"><b>Windows</b></td>
<td width="60%"><code>TerasologyLauncher.exe</code> or <code>bin/TerasologyLauncher.bat</code></td>
</tr>
<tr>
<td width="40%"><b>Unix, Linux, Mac OS X</b></td>
<td width="60%"><code>bin/TerasologyLauncher</code></td>
</tr>
</table>
## Features
On first start-up, the _Terasology Launcher_ will prompt you with the selection of the _Terasology_ installation and data directories.
The *installation directory* is the application directory of _Terasology_ and contains downloaded and extracted game packages.
The *data directory* is the place for configuration data and user-specific files such as key bindings and save games.
Note, that these directories are different from the *launcher installation directory*, which is the folder you extracted the launcher archive to.
The *Terasology Launcher UI* provides functionality to download, start, and delete different game versions. The game versions are grouped by the type of build they belong to:
<table align="center">
<thead align="left"><tr>
<th width="40%">Build Type</th>
<th width="60%">Explanation</th>
</tr></thead>
<tr>
<td width="40%"><b>Terasology</b></td>
<td width="60%">Released version of Terasology core game bundled with modules</td>
</tr>
<tr>
<td width="40%"><b>Terasology (nightly)</b></td>
<td width="60%">Development build of Terasology core game bundled with modules</td>
</tr>
<tr>
<td width="40%"><b>Terasology Lite</b></td>
<td width="60%">Released version of Terasology core game only</td>
</tr>
<tr>
<td width="40%"><b>Terasology Lite (nightly)</b></td>
<td width="60%">Development build of Terasology core game only</td>
</tr>
</table>
In addition to this main functionality, the UI displays information about new changes of the selected game version ("Changelog"), launcher information concerning changes, licensing and contribution guidelines ("About"), and logging data for the current launcher execution. Further, you have access to the social media representation of _Terasology_.
The *settings view* enables you to open the launcher installation, game installation and data directories for quick access and edit the data directory in case you want to change it after setting up the launcher. You can configure the memory settings for the game and even specify additional java or game arguments as well as the logging level for the game. Please note, that the "Initial Game Memory" and "Maximum Game Memory" setttings only apply to the game itself. The actual resource consumption may be higher due to additional resources required by the Java Virtual Machine (JVM).
The remaining settings can be used to configure the launcher. You can set the launcher language and decide whether the launcher should search for updates, close when a game is started and save downloaded game package files.
## Development
To be able to run **TerasologyLauncher** from source follow these steps. This guide is designed for [IntelliJ IDEA][intellij] (you can use the free community edition), but alternative setups are possible.
<details closed>
<summary>:octocat: Get Ready</summary>
<br>
To contribute to this repo, please open a [pull request][github forking] from your fork of this repository.
For more information on building and developing the Terasology Launcher, make sure to read the rest of this README and [CONTRIBUTING.md][contributing].
### Requirements
You'll need the following tools:
- Java SE Development Kit (JDK) 8 with JavaFX. It may be possible to use a later version of the JDK for local development, but the CI will verify against this baseline version.
- Git to clone the repo and commit changes.
Development is possible on all common platforms (Windows, Linux, MacOS) as long as the JDK with JavaFX is properly set up.
</details>
<details closed>
<summary>:nerd_face: Start developing</summary>
<br>
Familiarise yourself with Git's concept of repositories, branches, and commits. To get the latest changes from your remote repositories (e.g. `movingblocks`) you need to *fetch* all remote data via `git fetch --all`. This does not change your workspace, it just loads up your local Git database.
Apart from Git, basically everything can be done using the [Gradle][gradle] [wrapper][gradle wrapper]. The following list is an excerpt of some commonly used tasks.
<table align="center">
<thead align="left"><tr>
<th width="50%">Command</th>
<th width="50%"><i>Description</i></th>
</tr></thead>
<tr>
<td width="50%"><code>gradlew build</code></td>
<td width="50%"><i>Compile the source code, run tests and build a JAR.</i></td>
</tr>
<tr>
<td width="50%"><code>gradlew install</code></td>
<td width="50%"><i>Create a local runnable installation (placed in <code>./build/install/TerasologyLauncher</code>).</i></td>
</tr>
<tr>
<td width="50%"><code>gradlew run</code></td>
<td width="50%"><i>Build and run the launcher.</i></td>
</tr>
<tr>
<td width="50%"><code>gradlew createRelease</code></td>
<td width="50%"><i>Create a local development release (located in <code>./build/distributions</code>).</i></td>
</tr>
<tr>
<td width="50%"><code>gradlew tasks</code></td>
<td width="50%"><i>Display other available build script tasks.</i></td>
</tr>
</table>
Assume you have pushed some changes to your fork into a branch `myFeature`. In order to let us know about your work and give us the possibility to incorporate your changes you should send us a _pull request_. You can do this by selecting the `myFeature` branch on your GitHub repo and click the button which says "Open pull request".
More information on how to contribute can be found in [CONTRIBUTING.md][contributing]. Remember, that all submissions must be licensed under [Apache License, Version 2.0][license].
</details>
<details closed>
<summary>:books: Related Resources</summary>
<br>
Tutorials and further information on Git:
- http://www.vogella.de/articles/Git/article.html
- http://gitref.org/
- http://progit.org/
Developer setup tutorials for our main project, [**Terasology**][github terasology]:
- [Dev Setup](https://github.com/MovingBlocks/Terasology/wiki/Dev-Setup)
- [Dealing with Forks](https://github.com/MovingBlocks/Terasology/wiki/Dealing-with-Forks)
</details>
## Acknowledgements
_Terasology Launcher_ is driven by its [contributors][github terasologylauncher contributors]!
This project uses
- Font Awesome Icon for Webchat (`fa-comments`), CC BY 4.0 License, [Font Awesome Free License](https://fontawesome.com/license/free)
- [Mark James' Flag Icons Pack](http://www.famfamfam.com/lab/icons/flags/)
- [Bellsoft Liberica JRE 8](https://bell-sw.com/pages/java-8u232/) is bundled with the launcher
## License [][license]
_Terasology Launcher_ is licensed under the [Apache License, Version 2.0][license].
<!-- References -->
[latest-release]: https://github.com/MovingBlocks/TerasologyLauncher/releases/ "TerasologyLauncher (official releases)"
[license]: http://www.apache.org/licenses/LICENSE-2.0.html "Apache License, Version 2.0"
[contributing]: docs/CONTRIBUTING.md "CONTRIBUTING.md"
[github movingblocks]: https://github.com/MovingBlocks/ "MovingBlocks"
[github terasology]: https://github.com/MovingBlocks/Terasology/ "Terasology"
[github terasologylauncher]: https://github.com/MovingBlocks/TerasologyLauncher/ "TerasologyLauncher"
[github terasologylauncher contributors]: https://github.com/MovingBlocks/TerasologyLauncher/graphs/contributors/ "TerasologyLauncher contributors"
[gradle]: http://gradle.org "Gradle"
[gradle wrapper]: http://gradle.org/docs/current/userguide/gradle_wrapper.html "Gradle Wrapper"
[intellij]: http://www.jetbrains.com/idea/ "IntelliJ IDEA"
[github forking]: https://guides.github.com/activities/forking/ "GitHub Forking Guide"
| 50.369295 | 585 | 0.725183 | eng_Latn | 0.831594 |
0ce5e1a1bb5566dc08d19148bcb5e6d270d9d46b | 15,351 | md | Markdown | docs/vsto/how-to-add-content-controls-to-word-documents.md | evanwindom/visualstudio-docs | 1470eb0a54bd870650b72adb625a6a0d488f620e | [
"CC-BY-4.0",
"MIT"
] | 1 | 2017-08-15T16:18:32.000Z | 2017-08-15T16:18:32.000Z | docs/vsto/how-to-add-content-controls-to-word-documents.md | evanwindom/visualstudio-docs | 1470eb0a54bd870650b72adb625a6a0d488f620e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vsto/how-to-add-content-controls-to-word-documents.md | evanwindom/visualstudio-docs | 1470eb0a54bd870650b72adb625a6a0d488f620e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "How to: Add Content Controls to Word Documents | Microsoft Docs"
ms.custom: ""
ms.date: "02/02/2017"
ms.prod: "visual-studio-dev14"
ms.reviewer: ""
ms.suite: ""
ms.technology:
- "office-development"
ms.tgt_pltfrm: ""
ms.topic: "article"
dev_langs:
- "VB"
- "CSharp"
helpviewer_keywords:
- "restricted permissions [Office development in Visual Studio]"
- "DropDownListContentControl, adding to documents"
- "BuildingBlockGalleryContentControl, adding to documents"
- "partial document protection [Office development in Visual Studio]"
- "RichTextContentControl, adding to documents"
- "Word [Office development in Visual Studio], partial document protection"
- "content controls [Office development in Visual Studio], protecting"
- "PictureContentControl, adding to documents"
- "GroupContentControl, adding to documents"
- "document protection [Office development in Visual Studio]"
- "PlainTextContentControl, adding to documents"
- "content controls [Office development in Visual Studio], adding"
- "ComboBoxContentControl, adding to documents"
- "DatePickerContentControl, adding to documents"
- "Word [Office development in Visual Studio], restricted permissions"
ms.assetid: 68ddb24e-71c6-46f7-8e11-c9899d7814df
caps.latest.revision: 51
author: "kempb"
ms.author: "kempb"
manager: "ghogen"
---
# How to: Add Content Controls to Word Documents
In document-level Word projects, you can add content controls to the document in your project at design time or at run time. In Word VSTO Add-in projects, you can add content controls to any open document at run time.
[!INCLUDE[appliesto_wdalldocapp](../vsto/includes/appliesto-wdalldocapp-md.md)]
This topic describes the following tasks:
- [Adding content controls at design time](#designtime)
- [Adding content controls at run time in a document-level project](#runtimedoclevel)
- [Adding content controls at run time in an VSTO Add-in project](#runtimeaddin)
For information about content controls, see [Content Controls](../vsto/content-controls.md).
## <a name="designtime"></a> Adding Content Controls at Design Time
There are several ways to add content controls to the document in a document-level project at design time:
- Add a content control from the **Word Controls** tab of the **Toolbox**.
- Add a content control to your document in the same manner you would add a native content control in Word.
- Drag a content control to your document from the **Data Sources** window. This is useful when you want to bind the control to data when the control is created. For more information, see [How to: Populate Documents with Data from Objects](../vsto/how-to-populate-documents-with-data-from-objects.md) and [How to: Populate Documents with Data from a Database](../vsto/how-to-populate-documents-with-data-from-a-database.md).
[!INCLUDE[note_settings_general](../sharepoint/includes/note-settings-general-md.md)]
#### To add a content control to a document by using the Toolbox
1. In the document that is hosted in the [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] designer, put the cursor where you want to add the content control, or select the text that you want the content control to replace.
2. Open the **Toolbox** and click the **Word Controls** tab.
3. Add the control one of the following ways:
- Double-click a content control in the **Toolbox**.
or
- Click a content control in the **Toolbox** and then press the ENTER key.
or
- Drag a content control from the **Toolbox** to the document. The content control is added at the current selection in the document, not at the location of the mouse pointer.
> [!NOTE]
> You cannot add a <xref:Microsoft.Office.Tools.Word.GroupContentControl> by using the **Toolbox**. You can only add a <xref:Microsoft.Office.Tools.Word.GroupContentControl> in Word, or at run time.
> [!NOTE]
> Visual Studio does not provide a check box content control in the Toolbox. To add a check box content control to the document, you must create a <xref:Microsoft.Office.Tools.Word.ContentControl> object programmatically. For more information, see [Content Controls](../vsto/content-controls.md).
#### To add a content control to a document in Word
1. In the document that is hosted in the [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] designer, put the cursor where you want to add the content control, or select the text that you want the content control to replace.
2. On the Ribbon, click the **Developer** tab.
> [!NOTE]
> If the **Developer** tab is not visible, you must first show it. For more information, see [How to: Show the Developer Tab on the Ribbon](../vsto/how-to-show-the-developer-tab-on-the-ribbon.md).
3. In the **Controls** group, click the icon for the content control that you want to add.
## <a name="runtimedoclevel"></a> Adding Content Controls at Run Time in a Document-Level Project
You can add content controls programmatically to your document at run time by using methods of the <xref:Microsoft.Office.Tools.Word.Document.Controls%2A> property of the `ThisDocument` class in your project. Each method has three overloads that you can use to add a content control in the following ways:
- Add a control at the current selection.
- Add a control at a specified range.
- Add a control that is based on a native content control in the document.
Dynamically created content controls are not persisted in the document when the document is closed. However, a native content control remains in the document. You can recreate a content control that is based on a native content control the next time the document is opened. For more information, see [Adding Controls to Office Documents at Run Time](../vsto/adding-controls-to-office-documents-at-run-time.md).
> [!NOTE]
> To add a check box content control to a document in a Word 2010 project, you must create a <xref:Microsoft.Office.Tools.Word.ContentControl> object. For more information, see [Content Controls](../vsto/content-controls.md).
#### To add a content control at the current selection
1. Use a <xref:Microsoft.Office.Tools.Word.ControlCollection> method that has the name `Add`\<*control class*> (where *control class* is the class name of the content control that you want to add, such as <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A>), and that has a single parameter for the name of the new control.
The following code example uses the <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A> method to add a new <xref:Microsoft.Office.Tools.Word.RichTextContentControl> to the beginning of the document. To run this code, add the code to the `ThisDocument` class in your project, and call the `AddRichTextControlAtSelection` method from the `ThisDocument_Startup` event handler.
[!code-cs[Trin_ContentControlReference#700](../vsto/codesnippet/CSharp/trin_wordcontentcontrolreference/RichText.cs#700)]
[!code-vb[Trin_ContentControlReference#700](../vsto/codesnippet/VisualBasic/trin_contentcontrolreference/RichText.vb#700)]
#### To add a content control at a specified range
1. Use a <xref:Microsoft.Office.Tools.Word.ControlCollection> method that has the name `Add`\<*control class*> (where *control class* is the name of the content control class that you want to add, such as <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A>), and that has a <xref:Microsoft.Office.Interop.Word.Range> parameter.
The following code example uses the <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A> method to add a new <xref:Microsoft.Office.Tools.Word.RichTextContentControl> to the beginning of the document. To run this code, add the code to the `ThisDocument` class in your project, and call the `AddRichTextControlAtRange` method from the `ThisDocument_Startup` event handler.
[!code-cs[Trin_ContentControlReference#701](../vsto/codesnippet/CSharp/trin_wordcontentcontrolreference/RichText.cs#701)]
[!code-vb[Trin_ContentControlReference#701](../vsto/codesnippet/VisualBasic/trin_contentcontrolreference/RichText.vb#701)]
#### To add a content control that is based on a native content control
1. Use a <xref:Microsoft.Office.Tools.Word.ControlCollection> method that has the name `Add`\<*control class*> (where *control class* is the name of the content control class that you want to add, such as <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A>), and that has a Microsoft.Office.Interop.Word.ContentControl parameter.
The following code example uses the <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A> method to create a new <xref:Microsoft.Office.Tools.Word.RichTextContentControl> for every native rich text control that is in the document. To run this code, add the code to the `ThisDocument` class in your project, and call the `CreateRichTextControlsFromNativeControls` method from the `ThisDocument_Startup` event handler.
[!code-cs[Trin_ContentControlReference#702](../vsto/codesnippet/CSharp/trin_wordcontentcontrolreference/RichText.cs#702)]
[!code-vb[Trin_ContentControlReference#702](../vsto/codesnippet/VisualBasic/trin_contentcontrolreference/RichText.vb#702)]
## <a name="runtimeaddin"></a> Adding Content Controls at Run Time in a VSTO Add-in Project
You can add content controls programmatically to any open document at run time by using a VSTO Add-in. To do this, generate a <xref:Microsoft.Office.Tools.Word.Document> host item that is based on an open document, and then use methods of the <xref:Microsoft.Office.Tools.Word.Document.Controls%2A> property of this host item. Each method has three overloads that you can use to add a content control in the following ways:
- Add a control at the current selection.
- Add a control at a specified range.
- Add a control that is based on a native content control in the document.
Dynamically created content controls are not persisted in the document when the document is closed. However, a native content control remains in the document. You can recreate a content control that is based on a native content control the next time the document is opened. For more information, see [Persisting Dynamic Controls in Office Documents](../vsto/persisting-dynamic-controls-in-office-documents.md).
For more information about generating host items in VSTO Add-in projects, see [Extending Word Documents and Excel Workbooks in VSTO Add-ins at Run Time](../vsto/extending-word-documents-and-excel-workbooks-in-vsto-add-ins-at-run-time.md).
> [!NOTE]
> To add a check box content control to a document, you must create a <xref:Microsoft.Office.Tools.Word.ContentControl> object. For more information, see [Content Controls](../vsto/content-controls.md).
#### To add a content control at the current selection
1. Use a <xref:Microsoft.Office.Tools.Word.ControlCollection> method that has the name `Add`\<*control class*> (where *control class* is the class name of the content control that you want to add, such as <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A>), and that has a single parameter for the name of the new control.
The following code example uses the <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A> method to add a new <xref:Microsoft.Office.Tools.Word.RichTextContentControl> to the beginning of the active document. To run this code, add the code to the `ThisAddIn` class in your project, and call the `AddRichTextControlAtSelection` method from the `ThisAddIn_Startup` event handler.
[!code-vb[Trin_WordAddInDynamicControls#1](../vsto/codesnippet/VisualBasic/trin_wordaddindynamiccontrols/ThisAddIn.vb#1)]
[!code-cs[Trin_WordAddInDynamicControls#1](../vsto/codesnippet/CSharp/Trin_WordAddInDynamicControls/ThisAddIn.cs#1)]
#### To add a content control at a specified range
1. Use a <xref:Microsoft.Office.Tools.Word.ControlCollection> method that has the name `Add`\<*control class*> (where *control class* is the name of the content control class that you want to add, such as <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A>), and that has a <xref:Microsoft.Office.Interop.Word.Range> parameter.
The following code example uses the <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A> method to add a new <xref:Microsoft.Office.Tools.Word.RichTextContentControl> to the beginning of the active document. To run this code, add the code to the `ThisAddIn` class in your project, and call the `AddRichTextControlAtRange` method from the `ThisAddIn_Startup` event handler.
[!code-vb[Trin_WordAddInDynamicControls#2](../vsto/codesnippet/VisualBasic/trin_wordaddindynamiccontrols/ThisAddIn.vb#2)]
[!code-cs[Trin_WordAddInDynamicControls#2](../vsto/codesnippet/CSharp/Trin_WordAddInDynamicControls/ThisAddIn.cs#2)]
#### To add a content control that is based on a native content control
1. Use a <xref:Microsoft.Office.Tools.Word.ControlCollection> method that has the name `Add`\<*control class*> (where *control class* is the name of the content control class that you want to add, such as <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A>), and that has a Microsoft.Office.Interop.Word.ContentControl parameter.
The following code example uses the <xref:Microsoft.Office.Tools.Word.ControlCollection.AddRichTextContentControl%2A> method to create a new <xref:Microsoft.Office.Tools.Word.RichTextContentControl> for every native rich text control that is in a document, after the document is opened. To run this code, add the code to the `ThisAddIn` class in your project.
[!code-vb[Trin_WordAddInDynamicControls#3](../vsto/codesnippet/VisualBasic/trin_wordaddindynamiccontrols/ThisAddIn.vb#3)]
[!code-cs[Trin_WordAddInDynamicControls#3](../vsto/codesnippet/CSharp/Trin_WordAddInDynamicControls/ThisAddIn.cs#3)]
For C#, you must also attach the `Application_DocumentOpen` event handler to the <xref:Microsoft.Office.Interop.Word.ApplicationEvents4_Event.DocumentOpen> event.
[!code-cs[Trin_WordAddInDynamicControls#6](../vsto/codesnippet/CSharp/Trin_WordAddInDynamicControls/ThisAddIn.cs#6)]
## See Also
[Automating Word by Using Extended Objects](../vsto/automating-word-by-using-extended-objects.md)
[Host Items and Host Controls Overview](../vsto/host-items-and-host-controls-overview.md)
[Adding Controls to Office Documents at Run Time](../vsto/adding-controls-to-office-documents-at-run-time.md)
[Programmatic Limitations of Host Items and Host Controls](../vsto/programmatic-limitations-of-host-items-and-host-controls.md)
[Programming VSTO Add-Ins](../vsto/programming-vsto-add-ins.md)
[Programming Document-Level Customizations](../vsto/programming-document-level-customizations.md)
| 79.128866 | 451 | 0.762817 | eng_Latn | 0.928519 |
0ce64089e00e6df2a534fa17c76b6f7e56f8d8e3 | 2,877 | md | Markdown | docs/vs-2015/extensibility/debugger/sending-the-required-events.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/extensibility/debugger/sending-the-required-events.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/extensibility/debugger/sending-the-required-events.md | rfakhouri/visualstudio-docs.cs-cz | 3d540a168c09a23b855f746696062fd9954b8dd5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Odesílání požadovaných událostí | Dokumentace Microsoftu
ms.date: 11/15/2016
ms.prod: visual-studio-dev14
ms.technology: vs-ide-sdk
ms.topic: conceptual
helpviewer_keywords:
- debugging [Debugging SDK], required events
ms.assetid: 08319157-43fb-44a9-9a63-50b919fe1377
caps.latest.revision: 8
ms.author: gregvanl
manager: jillfra
ms.openlocfilehash: 457e2daf3e52c23ba9733d09d3aeb94750b5fab9
ms.sourcegitcommit: 47eeeeadd84c879636e9d48747b615de69384356
ms.translationtype: HT
ms.contentlocale: cs-CZ
ms.lasthandoff: 04/23/2019
ms.locfileid: "63446253"
---
# <a name="sending-the-required-events"></a>Odesílání požadovaných událostí
[!INCLUDE[vs2017banner](../../includes/vs2017banner.md)]
Pomocí tohoto postupu pro odesílání požadovaných událostí.
## <a name="process-for-sending-required-events"></a>Proces odesílání požadovaných událostí
Tyto události jsou povinné, v tomto pořadí, při vytváření ladicího stroje (DE) a připojení k programu:
1. Odeslání [IDebugEngineCreateEvent2](../../extensibility/debugger/reference/idebugenginecreateevent2.md) objektu události do Správce ladění relace (SDM), když je DE je inicializován pro ladění jednoho nebo více programů v procesu.
2. Při ladění programu přiřazen, odeslat [IDebugProgramCreateEvent2](../../extensibility/debugger/reference/idebugprogramcreateevent2.md) objekt SDM události. Tato událost může být událostí ukončení, v závislosti na návrhu modulu.
3. Pokud program je připojen k při spuštění procesu, pošlete [IDebugThreadCreateEvent2](../../extensibility/debugger/reference/idebugthreadcreateevent2.md) události objektu SDM oznámit integrovaného vývojového prostředí nového vlákna. Tato událost může být událostí ukončení, v závislosti na návrhu modulu.
4. Odeslání [IDebugLoadCompleteEvent2](../../extensibility/debugger/reference/idebugloadcompleteevent2.md) události objektu SDM po dokončení načítání nebo dokončení připojení k programu program, který se právě ladí. Tato událost musí být událostí ukončení.
5. Pokud je aplikace k ladění, odesílat [IDebugEntryPointEvent2](../../extensibility/debugger/reference/idebugentrypointevent2.md) události objektu SDM po první instrukce kódu za běhu architektury se pokračovalo. Tato událost je vždy událostí ukončení. Při krokování s vnořením do relace ladění, rozhraní IDE přestane na této události.
> [!NOTE]
> Řadu jiných jazyků použití globálních inicializátorů nebo externí, předkompilované funkcí (z knihovny CRT nebo _Main) na začátku svůj kód. Pokud jazyk ladíte program obsahuje některý z těchto typů prvků před počáteční vstupní bod, je tento kód spuštěný a vstupního bodu událost je odeslána při vstup uživatele bodu, jako například **hlavní** nebo `WinMain`, bylo dosaženo.
## <a name="see-also"></a>Viz také
[Povolení ladění programu](../../extensibility/debugger/enabling-a-program-to-be-debugged.md)
| 66.906977 | 376 | 0.800139 | ces_Latn | 0.999454 |
0ce657ba15bf7756951d6ad029fdc2e45866d0aa | 2,445 | md | Markdown | cheatsheets/javascript/packages/react/hooks/effect.md | MichaelCurrin/dev-cheatsheets | 568e2cf9f7bd64ab99a71b30888a72424f89ab10 | [
"MIT"
] | 20 | 2020-09-20T07:13:58.000Z | 2022-03-23T23:35:17.000Z | cheatsheets/javascript/packages/react/hooks/effect.md | MichaelCurrin/dev-cheatsheets | 568e2cf9f7bd64ab99a71b30888a72424f89ab10 | [
"MIT"
] | 15 | 2020-07-09T13:48:43.000Z | 2022-02-27T15:06:53.000Z | cheatsheets/javascript/packages/react/hooks/effect.md | MichaelCurrin/dev-cheatsheets | 568e2cf9f7bd64ab99a71b30888a72424f89ab10 | [
"MIT"
] | 11 | 2020-09-23T04:52:00.000Z | 2022-03-27T21:22:46.000Z |
# Effect hook
{% raw %}
This performs **side effects** in Function components.
See [Using the Effect Hook](https://reactjs.org/docs/hooks-effect.html) in the React docs.
That hook will run when the component:
- is mounted (once).
- updates (multiple times).
- unmounts (once).
## Syntax
```jsx
useEffect(FUNCTION, [ARGUMENTS])
```
## Example
### Click
Here is an example where a callback function is run on state change, changing the DOM outside of the component, setting a value on `document` (or some element) uses the browser API.
```jsx
const [count, setCount] = useState(0);
useEffect(() => {
document.title = `You clicked ${count} times`;
});
```
### Mount and unmount only
To prevent the function from running on updates, use an empty array s an extra parameter.
useEffect(() => {
console.log("Mounted or unmounted")
}, []);
The docs say that this is close to the mental model of `componentDidMount` and `componentWillUnmount`, but that "there are usually [better solutions][] to avoid re-running effects too often".
[better solutions]: https://reactjs.org/docs/hooks-faq.html#is-it-safe-to-omit-functions-from-the-list-of-dependencies
## Comparison
Use of `useEffect` is similar to `componentDidMount` and `componentDidUpdate` in a Class component.
- Functional component with hooks.
```jsx
import React, { useState, useEffect } from 'react';
function Example() {
const [count, setCount] = useState(0);
useEffect(() => {
document.title = `You clicked ${count} times`;
});
return (
<div>
<p>You clicked {count} times</p>
<button onClick={() => setCount(count + 1)}>
Click me
</button>
</div>
);
}
```
- Class component
```jsx
class Example extends React.Component {
constructor(props) {
super(props);
this.state = {
count: 0
};
}
componentDidMount() {
document.title = `You clicked ${this.state.count} times`;
}
componentDidUpdate() {
document.title = `You clicked ${this.state.count} times`;
}
render() {
return (
<div>
<p>You clicked {this.state.count} times</p>
<button onClick={() => this.setState({ count: this.state.count + 1 })}>
Click me
</button>
</div>
);
}
}
```
{% endraw %}
| 22.638889 | 191 | 0.603272 | eng_Latn | 0.94073 |
0ce73273b2366e552d27e1ca66ee8a42d63c816f | 1,414 | md | Markdown | articles/service-fabric/samples-cli.md | y32saji/azure-docs | cf971fe82e9ee70db9209bb196ddf36614d39d10 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-07-18T11:30:47.000Z | 2019-07-18T11:30:47.000Z | articles/service-fabric/samples-cli.md | y32saji/azure-docs | cf971fe82e9ee70db9209bb196ddf36614d39d10 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-01-13T19:45:57.000Z | 2022-01-13T19:45:57.000Z | articles/service-fabric/samples-cli.md | y32saji/azure-docs | cf971fe82e9ee70db9209bb196ddf36614d39d10 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure CLI (az) and Azure Service Fabric CLI (sfctl) Samples
description: Azure CLI (az) and Azure Service Fabric CLI (sfctl) Samples
services: service-fabric
documentationcenter: service-fabric
author: rwike77
manager: timlt
editor:
tags:
ms.assetid: b48d1137-8c04-46e0-b430-101e07d7e470
ms.service: service-fabric
ms.devlang: na
ms.topic: sample
ms.tgt_pltfrm: na
ms.workload: service-fabric
ms.date: 04/09/2018
ms.author: ryanwi
ms.custom: mvc
---
# Azure CLI (az) and Azure Service Fabric CLI (sfctl) Samples
The following table includes links to samples on how to manage Service Fabric clusters, applications, and services.
[!INCLUDE [links to azure cli and service fabric cli](../../includes/service-fabric-sfctl.md)]
| | |
|-|-|
| **Create cluster** (with Azure CLI)||
| [Create a secure Linux cluster](./scripts/cli-create-cluster.md)| Creates an Azure Service Fabric cluster. |
| **Manage applications** (with Service Fabric CLI)||
| [List applications](./scripts/sfctl-list-applications.md)| List applications provisioned to a cluster.|
| [Deploy an application](./scripts/cli-deploy-application.md)| Deploy an application to a cluster.|
| [Remove an application](./scripts/cli-remove-application.md)| Remove an application from a cluster.|
| [Upgrade an application](./scripts/sfctl-upgrade-application.md)| Upgrade an already deployed application.|
| 38.216216 | 116 | 0.737624 | eng_Latn | 0.695968 |
0ce7689f692ca0fa4acd465a5447691ef8f67b9f | 703 | md | Markdown | technical/game-timer.md | brandonpow1/vn-guide | 8a7eb67d161ca5b8ee964dfee05a0996625f3604 | [
"MIT"
] | 1 | 2022-02-17T21:56:57.000Z | 2022-02-17T21:56:57.000Z | technical/game-timer.md | brandonpow1/vn-guide | 8a7eb67d161ca5b8ee964dfee05a0996625f3604 | [
"MIT"
] | null | null | null | technical/game-timer.md | brandonpow1/vn-guide | 8a7eb67d161ca5b8ee964dfee05a0996625f3604 | [
"MIT"
] | null | null | null | ---
description: For speedrunners.
---
# Game Timer
anywhere in the game, preferably in `script.rpy`
```renpy
init python:
def save_playtime(d):
d["playtime"] = renpy.get_game_runtime()
config.save_json_callbacks = [save_playtime]
```
in `screens.rpy` in `screen file_slots(title)`:
```renpy
$ playtime = FileJson(slot, "playtime", empty=0, missing=0)
$ mins, secs = divmod(int(playtime), 60)
$ hrs, mins = divmod(mins, 60)
text "[hrs:02d]:[mins:02d]":
style "slot_name_text"
```
(yes you can write `"[hrs:02d]:[mins:02d]:[secs:02d]"` to show seconds, but i feel that's a bit too granular for a vn.)
| 24.241379 | 119 | 0.675676 | eng_Latn | 0.737193 |
0ce79a6d262ce306a656ed318c7ae72c0d08bd53 | 29 | md | Markdown | README.md | OpenIoTHub/ngrok | 4976b5194b73ef23c72683fe5162b29a9d6dfaf4 | [
"MIT"
] | null | null | null | README.md | OpenIoTHub/ngrok | 4976b5194b73ef23c72683fe5162b29a9d6dfaf4 | [
"MIT"
] | null | null | null | README.md | OpenIoTHub/ngrok | 4976b5194b73ef23c72683fe5162b29a9d6dfaf4 | [
"MIT"
] | null | null | null | # Ngrok
Ngrok NAT Downloader
| 9.666667 | 20 | 0.793103 | nld_Latn | 0.432212 |
0ce820d645f049f0a934871e3a46e6d30dee4cd5 | 7,366 | md | Markdown | docs/wozgraph.md | wwlib/robocommander | e47803cf5d90f49b4e7ca11ecdbbd189d457dd05 | [
"MIT",
"BSD-3-Clause"
] | 11 | 2018-08-27T17:47:59.000Z | 2021-09-30T16:36:23.000Z | docs/wozgraph.md | wwlib/robocommander | e47803cf5d90f49b4e7ca11ecdbbd189d457dd05 | [
"MIT",
"BSD-3-Clause"
] | 1 | 2019-06-13T04:46:45.000Z | 2019-06-13T04:46:45.000Z | docs/wozgraph.md | wwlib/robocommander | e47803cf5d90f49b4e7ca11ecdbbd189d457dd05 | [
"MIT",
"BSD-3-Clause"
] | 2 | 2019-03-31T13:33:05.000Z | 2021-08-18T10:37:05.000Z | ### WozGraph
#### ask nodes (prompts)
- avoid using question marks (*?*). They confuse the ESML engine and trigger random animations.
- when using an ask node, Jibo (the robot) will render the given prompt via TTS and then use cloud NLU to process the spoken answer (the user's utterance). If the NLU results contain a valid *intent*, outgoing links from the ask node will be analyzed. If an outgoing link is labeled with the NLU intent (i.e. *launchItsMe*) the node pointed to by that link will be executed automatically. For example:
node(type:ask, name: Init Game) -[gameCommand]-> node(type:esml, name: Good)
<img src="./img/RoboCommander-ask-node.png" width="400" />
node(type:ask, name: Init Game)
```
name: Init
scriptName: initGame
prompt: OK. Let's get started ${player.name}, ${game.setting}, ${game.prompt}
context: gameCommands
```
- Note: the *context* property is passed to dialogflow (google NLU). In this case, the *gameCommands* context lets dialogflow know that the utterance's intent should be a game command. The NLU *entity* will indicate which command was uttered (i.e. *continue* or *quit*).
- If the resulting NLU intent is *gameCommand* the next node will be executed automatically.
#### scripts
- scripts are authored in the `Scripts` panel
- nodes can have a *scriptName* property that can contain the name of a script to run when the node is executed
- node scripts are executed before any other properties are evaluated
- [GraphEditor: executeNode()](../src/renderer/components/grapheditor/GraphEditor.tsx)
- [GraphModel: executeScriptWithName(scriptName: string, robot?: Robot): any](../src/renderer/components/grapheditor/model/GraphModel.ts)
- [GraphModel: executeScript(activeScript: SavedScript, robot?: Robot, data?: any): any](../src/renderer/components/grapheditor/model/GraphModel.ts)
- [GraphModel: evaluateScriptWithData(scriptText: string, scriptData: any): string](../src/renderer/components/grapheditor/model/GraphModel.ts)
- [GraphModel: getSandbox(promptData:any): any](../src/renderer/components/grapheditor/model/GraphModel.ts)
- [ScriptConfig](../src/renderer/components/grapheditor/model/ScriptConfig.ts)
- scripts are evaluated in the context of a sandbox object which is derived either from:
- the active robot's stateData (*robot.stateData*)
- a global state object (*this._globalStateData*) if there is no active robot.
- the node's scriptContext property - if provided
- Note: *\_globalStateData* is used for testing and developing without a connected robot.
- Note: *GraphModel.activeRobot* is set when a valid intent is received from a robot (*GraphEditor:onRobotIntent(robotIntent: RobotIntent): void*)
From GraphEditor: executeNode - handling of the scriptContext property
```js
/** script execution **/
// if the node has a valid scriptName property, execute that script
// if the node has a valid scriptContext property, execute the script using that data as context
// otherwise execute the script using the active robot's stateData as context ()
let scriptName: string = node.properties.has('scriptName');
let scriptContext: any = node.properties.has('scriptContext');
let scriptData: any;
if (scriptContext) {
try {
scriptData = jsonic(scriptContext);
} catch (err) {
console.log(`GraphEditor: executeNode: error: `, err);
}
}
```
```js
executeScriptWithName(scriptName: string, robot?: Robot): any {
let result: any = undefined;
if (this.activeGraph) {
let scriptConfig: ScriptConfig = this.activeGraph.scriptConfig;
console.log(`GraphModel: executeScriptWithName: scriptConfig:`, scriptConfig);
let savedScript: SavedScript | undefined = scriptConfig.getSavedScriptWithName(scriptName);
if (savedScript) {
result = this.executeScript(savedScript, robot);
} else {
console.log(`executeScriptWithName: error: no script found with name: ${scriptName}`);
}
}
return result;
}
```
```js
executeScript(activeScript: SavedScript, robot?: Robot, data?: any): any {
console.log(`GraphModel: executeScript:`, activeScript, robot, data);
let output: any = undefined;
if (robot) {
output = this.evaluateScriptWithData(activeScript.script, robot.stateData);
} else {
if (!data) {
data = this._globalStateData;
}
output = this.evaluateScriptWithData(activeScript.script, data);
}
console.log(`GraphModel: executeScript: output:`, output);
return output;
}
```
```js
evaluateScriptWithData(scriptText: string, scriptData: any): string {
let scriptDataSandbox:any;
scriptDataSandbox = this.getSandbox(scriptData);
try { //do a safe eval on the condition
return vm.runInContext(scriptText, scriptDataSandbox);
} catch (e) {
console.log(`evaluateScriptWithData: error evaluating: ${scriptText}: ${scriptData} - error: ${e.message}`);
return '';
}
}
```
```js
getSandbox(promptData:any): any {
return vm.createContext(promptData);
}
```
#### script examples
<img src="./img/RoboCommander-script-initGame.png" width="400" />
```
name: initGame
script:
if (!initialized) {
var game = {};
game.setting = "You are at the entrance to a mysterious valley";
game.prompt = "Will you continue or quit";
if (!player) {
var player = {name: "", inventory: []};
}
var initialized = true;
}
```
```
name: getPlayer
script:
if (!player) {
var player = {name: "", inventory: []};
}
if (user && user != "Someone") {
player.name = user;
}
```
```
name: getGameCommand
script:
if (gameCommand) {
game.command = gameCommand;
} else {
game.command = "";
}
```
usage
node(type:launch) -[launchItsMe]-> node(type: esml, name: Greeting)
<img src="./img/RoboCommander-launch-node.png" width="400" />
node(type: esml, name: Greeting)
```
name: Greeting
scriptName: getPlayer
prompt: Hi ${player.name}. Would you like to play a game
```
#### robotCommand scripts
```js
if (!robotCommand) {
var robotCommand = {type: "", data: {}};
}
if (!imageUrl) {
var imageUrl = "http://cookstreetvillageactivitycentre.com/wp-content/uploads/2017/12/Morning-Yoga.jpg";
}
robotCommand = {type:"image", data:{ name:"image",url:imageUrl}}
```
```js
if (!robotCommand) {
var robotCommand = {type: "", data: {}};
}
robotCommand = {type:"eye", data:{}}
```
#### ESML nodes - special OK 'intent'
<img src="./img/RoboCommander-esml-node-OK.png" width="400" />
When TTS/ESML nodes have an outgoing OK intent, the connected node is automatically exeuted.
```
name: Greeting
scriptName: getPlayer
prompt: Hi ${player.name}. It's nice to see you.
```
#### scriptContext example
<img src="./img/RoboCommander-scriptContext.png" width="400" />
Note: when executed, the script uses the scriptContext and returns a context with robotCommand defined as `{type:"image", data:{ name:"image",url:imageUrl}}`. So, robotCommand gets sent to the robot.
```
name: script command
scriptName: yogaImage
scriptContext: {imageUrl:http://robocommander.io/img/RoboCommander.png}
```
yogaImage script
```js
if (!robotCommand) {
var robotCommand = {type: "", data: {}};
}
if (!imageUrl) {
var imageUrl = "http://cookstreetvillageactivitycentre.com/wp-content/uploads/2017/12/Morning-Yoga.jpg";
}
robotCommand = {type:"image", data:{ name:"image",url:imageUrl}}
```
| 33.330317 | 401 | 0.70391 | eng_Latn | 0.596824 |
0ce8d1747b8ae92815605e4ee627fc89e9c07c51 | 1,606 | md | Markdown | README.md | SamuelPoulin/seam | 915195604921442de1b2e7a7c474ae5eed5f5d99 | [
"MIT"
] | null | null | null | README.md | SamuelPoulin/seam | 915195604921442de1b2e7a7c474ae5eed5f5d99 | [
"MIT"
] | null | null | null | README.md | SamuelPoulin/seam | 915195604921442de1b2e7a7c474ae5eed5f5d99 | [
"MIT"
] | null | null | null | <div align="center">
<img
alt="Seam"
src="/image/logo.png"
width="400"
/>
</div>
<div align="center">
<h2>Open source, self-hosted scheduling software.</h2>
</div>
# Why Seam
As an alternative to other SaaS scheduling tools, Seam aims to be a complete, compromise-free solution that you can deploy on-premise or in the cloud.
## Beautiful
<img align="center" src="/image/widgets.png" width="100%"/>
<img align="center" src="/image/dashboard.png" width="100%">
Seam fits perfectly into the website you already have. You can either embed it as a widget or have it be its own seperate page. With tweakable styling and downloadable themes, it's easy to make it fit in any project and won't ever look out of place.
## Easy to setup
Seam is availaible in multiple release formats. Whether you're looking for a Docker container, binaries or just want to clone the repo and start using it, setting up is a matter of minutes thanks to straight-forward documentation and beginner-friendly config files.
## Extensible
Plugin support allows features that haven't made it to the current release to be developed independently by anyone.
## Integration
Seam aims to support calendar integration with most popular services so that all of your devices stay up-to-date.
- Google Calendar
- Outlook
- iCloud
# Contribute
<div align="center">
<div style="margin:25px;">Join the development server and help us create something awesome!</div>
<a href="https://discord.gg/jCyBTpA">
<img src="https://discord.com/assets/e4923594e694a21542a489471ecffa50.svg" height=50>
</a>
</div>
| 33.458333 | 265 | 0.741594 | eng_Latn | 0.989821 |
0ce8eaf64014028a0a959aa5226625e2efad74df | 2,119 | md | Markdown | README.md | ConnectionMaster/ONN-device-control | 0b909c48272ec0f92c79dfa1d7fb8b8b6c55766a | [
"CC-BY-4.0"
] | null | null | null | README.md | ConnectionMaster/ONN-device-control | 0b909c48272ec0f92c79dfa1d7fb8b8b6c55766a | [
"CC-BY-4.0"
] | 1 | 2021-11-11T14:44:56.000Z | 2021-11-11T14:44:56.000Z | README.md | ConnectionMaster/ONN-device-control | 0b909c48272ec0f92c79dfa1d7fb8b8b6c55766a | [
"CC-BY-4.0"
] | null | null | null | # Device Control Modules for Optical Neural Networks (ONNs)
This repository contains the device control modules for the optical matrix-vector multiplier demonstrated in the following paper:
>Tianyu Wang, Shi-Yuan Ma, Logan G. Wright, Tatsuhiro Onodera, Brian Richard and Peter L. McMahon. "An optical neural network using less than 1 photon per multiplication" _Nature communications_ **13**, 123 (2022) https://doi.org/10.1038/s41467-021-27774-8
The codes for training the neural network model executed in the experiment are available [here](https://github.com/mcmahon-lab/ONN-QAT-SQL).
## [Android_Display_Control](https://github.com/mcmahon-lab/ONN-device-control/blob/master/Android_Display_Control)
An Android application to control the OLED display of Google Pixel phone.
Adopted from <https://github.com/chris-blay/android-open-accessory-bridge>.
## [NN_models](https://github.com/mcmahon-lab/ONN-device-control/blob/master/NN_models)
The neural network models with trained parameters.
The training code is available [here](https://github.com/mcmahon-lab/ONN-QAT-SQL).
## [SLM](https://github.com/mcmahon-lab/ONN-device-control/blob/master/SLM)
The Python script to control the spatial light modulator (SLM, P1920-500-1100-HDMI, Meadowlark Optics).
Adopted from <https://github.com/wavefrontshaping/slmPy>.
## [data_collection](https://github.com/mcmahon-lab/ONN-device-control/blob/master/data_collection)
The Jupyter notebooks that control the experimental setup to collect data.
## [oscilloscope](https://github.com/mcmahon-lab/ONN-device-control/blob/master/oscilloscope)
The Python script to control the oscilloscope that reads data from the multi-pixel photon counter (MPPC, C13366 series GA type, Hamamatsu Photonics).
## [utils](https://github.com/mcmahon-lab/ONN-device-control/blob/master/utils)
Utility functions used in the experiments.
# License
The code in this repository is released under the following license:
[Creative Commons Attribution 4.0 International](https://creativecommons.org/licenses/by/4.0/)
A copy of this license is given in this repository as license.txt.
| 46.065217 | 256 | 0.789051 | eng_Latn | 0.774099 |
0cea094c1e99690fabb2098ffcec36df61d527c1 | 47 | md | Markdown | README.md | abdelhamidbakhta/coop-good-contracts | bd3827ff80f55e7d48c14e416e7e7d6165aeae87 | [
"Apache-2.0"
] | null | null | null | README.md | abdelhamidbakhta/coop-good-contracts | bd3827ff80f55e7d48c14e416e7e7d6165aeae87 | [
"Apache-2.0"
] | 1 | 2020-12-03T10:54:40.000Z | 2020-12-03T13:36:10.000Z | README.md | abdelhamidbakhta/coop-good-contracts | bd3827ff80f55e7d48c14e416e7e7d6165aeae87 | [
"Apache-2.0"
] | 1 | 2020-12-03T10:59:10.000Z | 2020-12-03T10:59:10.000Z | # coop-good-contracts
Ethereum Smart contracts
| 15.666667 | 24 | 0.829787 | eng_Latn | 0.82327 |
0cea634aacfcf65cfff744282e824a27bf16d40d | 587 | md | Markdown | README.md | juliuszint/halbzeit | fb3d0dc4e3ee13c6d24934872625887e0dbda298 | [
"MIT"
] | null | null | null | README.md | juliuszint/halbzeit | fb3d0dc4e3ee13c6d24934872625887e0dbda298 | [
"MIT"
] | null | null | null | README.md | juliuszint/halbzeit | fb3d0dc4e3ee13c6d24934872625887e0dbda298 | [
"MIT"
] | null | null | null | # Halbzeit (Computergrafik Vorleistungsprojekt)
## Getting Started
Der erste Schritt besteht darin den SGFrameworkLib Ordner mit der neusten Version des SGFrameworks (der Übungsszenegraph) zu füllen.
Danach begibt man sich in den source Ordner und öffnet die Halbzeit.pro Datei mit dem QT-Creator. Beim ersten mal muss man den Kompiler
konfigurieren und den Ausgabeordner. Als Kompiler wählt man den `Desktop QT ...` und klappt die Details noch auf wo man den Ausgabepfad
festlegen kann. Hier auf den `buildoutput` Ordner einstellen (dieser ist schon in der .hgignore datei eingetragen)
| 83.857143 | 135 | 0.81431 | deu_Latn | 0.998575 |
0cea7e11f0435807a41a4c53dece552910c83adf | 488 | md | Markdown | README.md | sdunster/libbeacon | eeaf1299a2783865cbc4888a4c3ccdc4cf82dd50 | [
"MIT"
] | null | null | null | README.md | sdunster/libbeacon | eeaf1299a2783865cbc4888a4c3ccdc4cf82dd50 | [
"MIT"
] | null | null | null | README.md | sdunster/libbeacon | eeaf1299a2783865cbc4888a4c3ccdc4cf82dd50 | [
"MIT"
] | null | null | null | # libbeacon
Library for interacting with beacon. If you don't know what that is this library is _not_ for you!
## Installation
```bash
$ npm install libbeacon
```
## Example
```js
var beacon = new Libbeacon();
beacon.login('username', 'password', function(err, success) {
beacon.get('Jobs/1', {}, function(error, data) {
console.log(data);
}
});
```
## Tests
```bash
$ npm install
$ BEACON_USERNAME='user' BEACON_PASSWORD='pass' npm test
```
## License
[MIT](LICENSE)
| 18.074074 | 98 | 0.661885 | eng_Latn | 0.631038 |
0ceacf8c662c62998241a3882325c924a339f3c4 | 5,981 | md | Markdown | README.md | tomich87/argo-cd-helmfile | 8dc4f0b4f53800291c33bc0f4775355ba511aa17 | [
"MIT"
] | 88 | 2020-02-04T23:34:05.000Z | 2022-03-30T12:48:53.000Z | README.md | tomich87/argo-cd-helmfile | 8dc4f0b4f53800291c33bc0f4775355ba511aa17 | [
"MIT"
] | 13 | 2020-07-24T11:27:25.000Z | 2022-03-16T13:39:51.000Z | README.md | tomich87/argo-cd-helmfile | 8dc4f0b4f53800291c33bc0f4775355ba511aa17 | [
"MIT"
] | 26 | 2020-02-20T11:31:29.000Z | 2022-03-20T10:55:45.000Z | # Intro
Support for `helmfile` with `argo-cd`.
`argo-cd` already supports `helm` in 2 distinct ways, why is this useful?
- It helps decouple configuration from chart development
- It's similar to using a repo type of `helm` but you can still manage
configuration with git.
- Because I like the power afforded using `helmfile`'s features such as
`environments`, `selectors`, templates, and being able to use `ENV` vars as
conditionals **AND** values.
- https://github.com/roboll/helmfile/blob/master/docs/writing-helmfile.md
- https://github.com/roboll/helmfile/blob/master/docs/shared-configuration-across-teams.md
# Security
Please make note that `helmfile` itself allows execution of arbitrary scripts.
Due to this feature, execution of arbitrary scripts are allowed by this plugin,
both explicitly (see `HELMFILE_INIT_SCRIPT_FILE` env below) and implicity.
Consider these implications for your environment and act appropriately.
- https://github.com/roboll/helmfile#templating (`exec` desciption)
- the execution pod/context is the `argocd-repo-server`
# Installation
```
configManagementPlugins: |
- name: helmfile
init: # Optional command to initialize application source directory
command: ["argo-cd-helmfile.sh"]
args: ["init"]
generate: # Command to generate manifests YAML
command: ["argo-cd-helmfile.sh"]
args: ["generate"]
```
```
volumes:
- name: custom-tools
emptyDir: {}
initContainers:
- name: download-tools
image: alpine:3.8
command: [sh, -c]
args:
- wget -qO /custom-tools/argo-cd-helmfile.sh https://raw.githubusercontent.com/travisghansen/argo-cd-helmfile/master/src/argo-cd-helmfile.sh &&
chmod +x /custom-tools/argo-cd-helmfile.sh &&
wget -qO /custom-tools/helmfile https://github.com/roboll/helmfile/releases/download/v0.138.7/helmfile_linux_amd64 &&
chmod +x /custom-tools/helmfile
volumeMounts:
- mountPath: /custom-tools
name: custom-tools
volumeMounts:
- mountPath: /usr/local/bin/argo-cd-helmfile.sh
name: custom-tools
subPath: argo-cd-helmfile.sh
- mountPath: /usr/local/bin/helmfile
name: custom-tools
subPath: helmfile
```
# Usage
Configure your `argo-cd` app to use a repo/directory which holds a valid
`helmfile` configuation. This can be a directory which contains a
`helmfile.yaml` file **OR** a `helmfile.d` directory containing any number of
`*.yaml` files. You cannot have both configurations.
There are a number of specially handled `ENV` variables which can be set (all
optional):
- `HELM_BINARY` - custom path to `helm` binary
- `HELM_TEMPLATE_OPTIONS` - pass-through options for the templating operation
`helm template --help`
- `HELMFILE_BINARY` - custom path to `helmfile` binary
- `HELMFILE_GLOBAL_OPTIONS` - pass-through options for all `helmfile`
operations `helmfile --help`
- `HELMFILE_TEMPLATE_OPTIONS` - pass-through options for the templating
operation `helmfile template --help`
- `HELMFILE_INIT_SCRIPT_FILE` - path to script to execute during init phase
- `HELMFILE_HELMFILE` - a complete `helmfile.yaml` content
- `HELMFILE_HELMFILE_STRATEGY` - one of `REPLACE` or `INCLUDE`
- `REPLACE` - the default option, only the content of `HELMFILE_HELMFILE` is
rendered, if any valid files exist in the repo they are ignored
- `INCLUDE` - any valid files in the repo **AND** the content of
`HELMFILE_HELMFILE` are rendered, precedence is given to
`HELMFILE_HELMFILE` should the same release name be declared in multiple
files
Of the above `ENV` variables, the following do variable expansion on the value:
- `HELMFILE_GLOBAL_OPTIONS`
- `HELMFILE_TEMPLATE_OPTIONS`
- `HELM_TEMPLATE_OPTIONS`
- `HELMFILE_INIT_SCRIPT_FILE`
- `HELM_DATA_HOME`
Meaning, you can do things like:
- `HELMFILE_GLOBAL_OPTIONS="--environment ${ARGOCD_APP_NAME} --selector cluster=${CLUSTER_ID}`
Any of the standard `Build Environment` variables can be used as well as
variables declared in the application spec.
- https://argoproj.github.io/argo-cd/user-guide/config-management-plugins/#environment
- https://argoproj.github.io/argo-cd/user-guide/build-environment/
## Helm Plugins
To use the various helm plugins the recommended approach is the install the
plugins using the/an `initContainers` (explicity set the `HELM_DATA_HOME` env
var during the `helm plugin add` command) and simply set the `HELM_DATA_HOME`
environment variable in your application spec (or globally in the pod). This
prevents the plugin(s) from being downloaded over and over each run.
```
# repo server deployment
volumes:
...
- name: helm-data-home
emptyDir: {}
# repo-server container
volumeMounts:
...
- mountPath: /home/argocd/.local/share/helm
name: helm-data-home
# init container
volumeMounts:
...
- mountPath: /helm/data
name: helm-data-home
[[ ! -d "${HELM_DATA_HOME}/plugins/helm-secrets" ]] && /custom-tools/helm-v3 plugin install https://github.com/jkroepke/helm-secrets --version ${HELM_SECRETS_VERSION}
chown -R 999:999 "${HELM_DATA_HOME}"
# lastly, in your app definition
...
plugin:
env:
- name: HELM_DATA_HOME
value: /home/argocd/.local/share/helm
```
If the above is not possible/desired, the recommended approach would be to use
`HELMFILE_INIT_SCRIPT_FILE` to execute an arbitrary script during the `init`
phase. Within the script it's desireable to run `helm plugin list` and only
install the plugin only if it's not already installed.
## Custom Init
You can use the `HELMFILE_INIT_SCRIPT_FILE` feature to do any kind of _init_
logic required including installing helm plugins, downloading external files,
etc. The value can be a relative or absolute path and the file itself can be
injected using an `initContainers` or stored in the application git repository.
# Development
```
# format before commit
shfmt -i 2 -ci -w src/argo-cd-helmfile.sh
```
| 35.390533 | 170 | 0.732319 | eng_Latn | 0.908475 |
0cec634a44ed128a605db6eb656f966e40ce57ee | 8,304 | md | Markdown | articles/nodejs-use-node-modules-azure-apps.md | OpenLocalizationTestOrg/azure-docs-pr15_da-DK | d54890118a6e972d17db61fb83d96d3e56ca9f44 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/nodejs-use-node-modules-azure-apps.md | OpenLocalizationTestOrg/azure-docs-pr15_da-DK | d54890118a6e972d17db61fb83d96d3e56ca9f44 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/nodejs-use-node-modules-azure-apps.md | OpenLocalizationTestOrg/azure-docs-pr15_da-DK | d54890118a6e972d17db61fb83d96d3e56ca9f44 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Arbejde med Node.js moduler"
description="Få mere at vide om at arbejde med Node.js moduler, når du bruger Azure App Service Cloud Services."
services=""
documentationCenter="nodejs"
authors="rmcmurray"
manager="wpickett"
editor=""/>
<tags
ms.service="multiple"
ms.workload="na"
ms.tgt_pltfrm="na"
ms.devlang="nodejs"
ms.topic="article"
ms.date="08/11/2016"
ms.author="robmcm"/>
# <a name="using-nodejs-modules-with-azure-applications"></a>Brug af Node.js moduler med Azure-programmer
Dette dokument indeholder vejledning til brug af Node.js moduler sammen med hostes på Azure-programmer. Det giver vejledning i at sikre, at dit program bruger en bestemt version af modulet samt ved hjælp af Oprindelig moduler med Azure.
Hvis du allerede kender, er ved hjælp af Node.js moduler, **package.json** og **npm shrinkwrap.json** filer, følgende en hurtig oversigt over hvad er beskrevet i denne artikel:
* Azure App Service forstår **package.json** og **npm shrinkwrap.json** filer og kan installere moduler, der er baseret på værdierne i disse filer.
* Azure-Skytjenester forventer, at alle moduler skal være installeret på udviklingsmiljø, og den **node\_moduler** directory der skal medtages som en del af installationspakken. Det er muligt at aktivere understøttelse af installerer moduler ved hjælp af **package.json** eller **npm shrinkwrap.json** -filer på Cloud Services, men dette kræver tilpasning af de standard scripts, som bruges af skytjeneste projekter. Se et eksempel af hvordan du gør dette, under [Azure Start opgaven til at køre npm Installer for at undgå at implementere node moduler](https://github.com/woloski/nodeonazure-blog/blob/master/articles/startup-task-to-run-npm-in-azure.markdown)
> [AZURE.NOTE] Azure virtuelle maskiner er ikke beskrevet i denne artikel, som installation oplevelsen i en VM bliver afhænger af det operativsystem, der er hostet af den virtuelle maskine.
##<a name="nodejs-modules"></a>Node.js moduler
Moduler er indlæses JavaScript-pakker, som giver bestemte funktioner for dit program. Et modul installeres normalt ved hjælp af værktøjet **npm** kommandolinjen, men nogle (såsom HTTP-modulet) er angivet som en del af pakken core Node.js.
Når moduler er installeret, de er gemt i den **node\_moduler** mappe i roden af mappestrukturen programmet på computeren. Hvert modul i den **node\_moduler** directory vedligeholder sin egen **node\_moduler** mappe, der indeholder eventuelle moduler, som det afhænger af, og dette gentager igen for hver modul hele vejen ned afhængighedskæden. Dette giver mulighed for hvert modul, der er installeret for at få sin egen versionskrav til modulerne det afhænger af, men det kan medføre temmelig store mappestrukturen.
Når du installerer den **node\_moduler** bibliotek som en del af dit program, det vil øge størrelsen på den installation, sammenlignet med ved hjælp af en **package.json** eller **npm shrinkwrap.json** fil. det garanterer, at versionen af de moduler, anvendes fremstilling er de samme som dem, der bruges i udvikling.
###<a name="native-modules"></a>Oprindelig moduler
Mens de fleste moduler er blot tekstformat JavaScript-filer, er nogle moduler platform-specifikke binære billeder. Disse moduler er kompileret, når du installerer, som regel ved hjælp af Python og node gyp. Da Azure Cloud Services, der er afhængige af den **node\_moduler** mappe, der installeres som en del af det program, alle oprindelige modul, der er inkluderet som en del af de installerede moduler skal arbejde i en skybaseret tjeneste, så længe den er installeret og kompileret på en Windows udvikling system.
Azure App Service understøtter ikke alle oprindelige moduler og kan mislykkes på kompilering dem med meget bestemte forudsætninger. Mens nogle populære moduler som MongoDB har valgfrie oprindelige afhængigheder og arbejde lige fin uden dem, vist sig vellykket med næsten alle oprindelige moduler, der er tilgængelige i dag to løsninger:
* Køre **npm installere** på en Windows-computer, der har alle de oprindelige modulet forudsætninger, der er installeret. Derefter installere den oprettede **node\_moduler** mappe som en del af programmet til Azure App-tjenesten.
* Azure App Service kan konfigureres for at udføre brugerdefinerede fest eller shellscripts under installationen, hvilket giver dig mulighed for at udføre brugerdefinerede kommandoer og nøjagtigt konfigurere måde **npm installere** kører. Du kan finde en video, der viser, hvordan du gør dette, [Brugerdefineret websted installation Scripts med Kudu].
###<a name="using-a-packagejson-file"></a>Ved hjælp af en package.json-fil
**Package.json** filen er en metode til at angive de øverste niveau afhængigheder programmet kræver så hosting platform kan installere afhængighederne i stedet for at du behøver at medtage de **node\_pakker** mappe som en del af installationen. Kommandoen **npm installere** bruges til at analysere filen **package.json** og installere alle afhængigheder, der vises, når programmet er blevet installeret.
Under udvikling, kan du bruge den **– Gem**, **– Gem-Udviklingscenter**, eller **– Gem valgfrit** parametre, når du installerer moduler for at tilføje en post for modulet til filen **package.json** automatisk. Du kan finde yderligere oplysninger finder [npm-installation](https://docs.npmjs.com/cli/install).
Én potentielle problemer med **package.json** filen er, at det kun angiver versionen for øverste niveau afhængigheder. Hvert modul, der er installeret kan eller ikke kan angiver versionen af moduler det afhænger af, og så det er muligt, at du muligvis ender med en anden afhængighed kæde end den, der bruges i udvikling.
> [AZURE.NOTE]
> Når du installerer på Azure App Service, hvis filen <b>package.json</b> henviser til et oprindelige modul vises der en stil med følgende fejl, når du udgiver programmet ved hjælp af ciffer:
> npm ERR! [email protected] install: 'node-gyp configure build'
> npm ERR! 'cmd "/c" "node-gyp configure build"' failed with 1
###<a name="using-a-npm-shrinkwrapjson-file"></a>Ved hjælp af en npm shrinkwrap.json-fil
Filen **npm shrinkwrap.json** er et forsøg på at løse filen **package.json** modul versionsstyring begrænsninger. Mens **package.json** filen indeholder kun versioner for øverste niveau moduler, indeholder filen **npm shrinkwrap.json** versionskravene til fuld modul afhængighedskæden.
Når dit program er klar til fremstilling, kan du låse-ned versionskravene og oprette en **npm shrinkwrap.json** -fil ved hjælp af kommandoen **npm shrinkwrap** . Dette vil bruge de versioner, der aktuelt er installeret i den **node\_moduler** mappe, og registrere dem til filen **npm shrinkwrap.json** . Kommandoen **npm installere** bruges til at analysere filen **npm shrinkwrap.json** og installere alle afhængigheder, der vises, når programmet er blevet installeret på den værtsmiljø. Du kan finde flere oplysninger [npm shrinkwrap](https://docs.npmjs.com/cli/shrinkwrap).
> [AZURE.NOTE]
>Når du installerer på Azure App Service, hvis filen <b>npm shrinkwrap.json</b> henviser til et oprindelige modul vises der en stil med følgende fejl, når du udgiver programmet ved hjælp af ciffer:
> npm ERR! [email protected] install: 'node-gyp configure build'
> npm ERR! 'cmd "/c" "node-gyp configure build"' failed with 1
##<a name="next-steps"></a>Næste trin
Nu hvor du ved, hvordan du bruger Node.js moduler med Azure, lære, hvordan du [angiver Node.js versionen], [opbygge og anvende en Node.js web-app], og [hvordan du kan bruge kommandolinjen Azure til Mac og Linux].
Du kan finde yderligere oplysninger finder [Node.js Developer Center](/develop/nodejs/).
[Angiv Node.js versionen]: nodejs-specify-node-version-azure-apps.md
[Hvordan du kan bruge kommandolinjen Azure til Mac og Linux]: xplat-cli-install.md
[opbygge og anvende en Node.js WebApp]: web-sites-nodejs-develop-deploy-mac.md
[Node.js Web Application with Storage on MongoDB (MongoLab)]: store-mongolab-web-sites-nodejs-store-data-mongodb.md
[Build and deploy a Node.js application to an Azure Cloud Service]: cloud-services-nodejs-develop-deploy-app.md
[Brugerdefineret websted installation Scripts med Kudu]: /documentation/videos/custom-web-site-deployment-scripts-with-kudu/
| 92.266667 | 660 | 0.779022 | dan_Latn | 0.999458 |
0cecb7db371b985e3f6b1fb960cd797a622785d8 | 690 | md | Markdown | poem/CHANGELOG.md | ainiayok/poem | e53253ed9787b8f54ac6b85b6560538e111f5be0 | [
"Apache-2.0",
"MIT"
] | 1 | 2021-12-13T05:31:29.000Z | 2021-12-13T05:31:29.000Z | poem/CHANGELOG.md | ainiayok/poem | e53253ed9787b8f54ac6b85b6560538e111f5be0 | [
"Apache-2.0",
"MIT"
] | null | null | null | poem/CHANGELOG.md | ainiayok/poem | e53253ed9787b8f54ac6b85b6560538e111f5be0 | [
"Apache-2.0",
"MIT"
] | null | null | null | # Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
# Unreleased
- Add `RouteDomain` for `Host` header routing.
# [1.0.4] 2010-10-15
- Remove the `'static` constraint of `Endpoint`.
- Add `EndpointExt::around` method.
# [1.0.3] 2010-10-14
- Change the trait bounds of `FromRequest::Error` from `Into<Error>` to `IntoResponse`.
- Implements `IntoResponse` for `Body`.
- The `CookieJar::private` and `CookieJar::signed` methods now use the key specified by `CookieJarManager::with_key`.
| 32.857143 | 117 | 0.728986 | eng_Latn | 0.873131 |
0cecb85c37f5486e7a7fa2c380c36be8f1b29b11 | 193 | md | Markdown | README.md | buscarini/NetworkKit | a0b0a6b9c74e7446c42fd960785b88c4543b276b | [
"MIT"
] | null | null | null | README.md | buscarini/NetworkKit | a0b0a6b9c74e7446c42fd960785b88c4543b276b | [
"MIT"
] | null | null | null | README.md | buscarini/NetworkKit | a0b0a6b9c74e7446c42fd960785b88c4543b276b | [
"MIT"
] | null | null | null | # NetworkKit
Library to simplify REST api calls.
## Author
José Manuel Sánchez, [email protected]
## License
Task is available under the MIT license. See the LICENSE file for more info.
| 16.083333 | 76 | 0.761658 | eng_Latn | 0.851129 |
0ced1390c555cc0ce5cf1fb13ddcb45ecc46bdc2 | 1,897 | md | Markdown | docs/vsto/how-to-programmatically-open-text-files-as-workbooks.md | Ash-Shaun/visualstudio-docs | 787c3856e6cbfc65d97612854fc093785dc5573a | [
"CC-BY-4.0",
"MIT"
] | 2 | 2018-08-10T21:30:42.000Z | 2019-05-07T04:13:01.000Z | docs/vsto/how-to-programmatically-open-text-files-as-workbooks.md | Ash-Shaun/visualstudio-docs | 787c3856e6cbfc65d97612854fc093785dc5573a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-10-08T17:51:50.000Z | 2018-10-08T17:51:50.000Z | docs/vsto/how-to-programmatically-open-text-files-as-workbooks.md | Ash-Shaun/visualstudio-docs | 787c3856e6cbfc65d97612854fc093785dc5573a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-03-30T08:27:29.000Z | 2020-03-30T08:27:29.000Z | ---
title: "How to: Programmatically open text files as workbooks"
ms.custom: ""
ms.date: "02/02/2017"
ms.technology:
- "office-development"
ms.topic: "conceptual"
dev_langs:
- "VB"
- "CSharp"
helpviewer_keywords:
- "workbooks, opening text files as"
- "text [Office development in Visual Studio], text files"
- "text files, opening as workbooks"
author: TerryGLee
ms.author: tglee
manager: douge
ms.workload:
- "office"
---
# How to: Programmatically open text files as workbooks
You can open a text file as a workbook. You must pass in the name of the text file you want to open. You can specify several optional parameters, such as which row number to start parsing on and the column format of the data in the file.
[!INCLUDE[appliesto_xlalldocapp](../vsto/includes/appliesto-xlalldocapp-md.md)]
## Example
[!code-csharp[Trin_VstcoreExcelAutomation#80](../vsto/codesnippet/CSharp/Trin_VstcoreExcelAutomationCS/Sheet1.cs#80)]
[!code-vb[Trin_VstcoreExcelAutomation#80](../vsto/codesnippet/VisualBasic/Trin_VstcoreExcelAutomation/Sheet1.vb#80)]
## Compile the code
This example requires the following components:
- A comma-delimited text file named `Test.txt` that contains at least three lines of text.
- The text file `Test.txt` to be stored on drive C.
## See also
[Work with workbooks](../vsto/working-with-workbooks.md)
[How to: Programmatically open workbooks](../vsto/how-to-programmatically-open-workbooks.md)
[How to: Programmatically create new workbooks](../vsto/how-to-programmatically-create-new-workbooks.md)
[How to: Programmatically save workbooks](../vsto/how-to-programmatically-save-workbooks.md)
[How to: Programmatically close workbooks](../vsto/how-to-programmatically-close-workbooks.md)
[Optional parameters in Office solutions](../vsto/optional-parameters-in-office-solutions.md)
| 42.155556 | 241 | 0.739062 | eng_Latn | 0.911208 |
932fefe29aceba273954c44f698d32b4c5e8a693 | 1,029 | md | Markdown | packages/mdg:reload-on-resume/README.md | lorensr/mobile-packages | 7c58380171f8836e944a1f8ccfe5a0492cf1bdbc | [
"MIT"
] | null | null | null | packages/mdg:reload-on-resume/README.md | lorensr/mobile-packages | 7c58380171f8836e944a1f8ccfe5a0492cf1bdbc | [
"MIT"
] | null | null | null | packages/mdg:reload-on-resume/README.md | lorensr/mobile-packages | 7c58380171f8836e944a1f8ccfe5a0492cf1bdbc | [
"MIT"
] | null | null | null | # Meteor reload-on-resume Package
Add it to your [Meteor](http://meteor.com) app with `meteor add mdg:reload-on-resume`. This package changes the behavior of Meteor's hot code push feature on mobile devices only.
Normally, your app will update on the user's device as soon as you push a new version. This process is always smooth in a desktop web browser, but might momentarily interrupt the user's experience if they are on a mobile device.
With this package, the app will only update itself to the newest version if the user closes and re-opens the app (hence, it "reloads on resume").
## API
In addition to changing the behavior of hot code push, this package provides a method to check if the app is waiting to be reloaded.
### Reload.isWaitingForResume()
A reactive function that returns `true` if a new version of the app has been downloading and the framework is waiting until the app is closed and reopened. Can be used to display a message to the user that says "new version available, restart the app to update." | 68.6 | 262 | 0.777454 | eng_Latn | 0.998102 |
933008263f93136f50ed75849f5e3a3d9d27a0ee | 2,701 | md | Markdown | desktop-src/DirectShow/cbasecontrolvideo-setdefaulttargetrect.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 552 | 2019-08-20T00:08:40.000Z | 2022-03-30T18:25:35.000Z | desktop-src/DirectShow/cbasecontrolvideo-setdefaulttargetrect.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 1,143 | 2019-08-21T20:17:47.000Z | 2022-03-31T20:24:39.000Z | desktop-src/DirectShow/cbasecontrolvideo-setdefaulttargetrect.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 1,287 | 2019-08-20T05:37:48.000Z | 2022-03-31T20:22:06.000Z | ---
description: The SetDefaultTargetRect method sets the default target video rectangle (pure virtual). This is an internal member function that gets called when the source rectangle is reset.
ms.assetid: bb7e32b2-f02c-465f-a8cb-6172d9724790
title: CBaseControlVideo.SetDefaultTargetRect method (Ctlutil.h)
ms.topic: reference
ms.date: 05/31/2018
topic_type:
- APIRef
- kbSyntax
api_name:
- CBaseControlVideo.SetDefaultTargetRect
api_type:
- COM
api_location:
- Strmbase.lib
- Strmbase.dll
- Strmbasd.lib
- Strmbasd.dll
---
# CBaseControlVideo.SetDefaultTargetRect method
The `SetDefaultTargetRect` method sets the default target video rectangle (pure virtual). This is an internal member function that gets called when the source rectangle is reset.
## Syntax
```C++
virtual HRESULT SetDefaultTargetRect() = 0;
```
## Parameters
This method has no parameters.
## Return value
Returns an **HRESULT** value.
## Remarks
Derived classes should override this to reset the destination video rectangle. It is called from the [**CBaseControlVideo::SetDefaultDestinationPosition**](cbasecontrolvideo-setdefaultdestinationposition.md) member function.
The following example demonstrates an implementation of this function in a derived class.
```C++
// This is called when you reset the default target rectangle.
HRESULT CVideoText::SetDefaultTargetRect()
{
VIDEOINFO *pVideoInfo = (VIDEOINFO *) m_pRenderer->m_mtIn.Format();
BITMAPINFOHEADER *pHeader = HEADER(pVideoInfo);
RECT TargetRect = {0,0,m_Size.cx,m_Size.cy};
m_pRenderer->m_DrawImage.SetTargetRect(&TargetRect);
return NOERROR;
}
```
In this example, CVideoText is a class derived from [**CBaseControlVideo**](cbasecontrolvideo.md), m\_pRenderer holds an object of a class derived from [**CBaseVideoRenderer**](cbasevideorenderer.md), and the m\_DrawImage data member, defined in the derived class, holds a [**CDrawImage**](cdrawimage.md) object. The m\_mtIn data member, also defined in the derived class, holds a [**CMediaType**](cmediatype.md) object with the media type of the input pin.
## Requirements
| Requirement | Value |
|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Header<br/> | <dl> <dt>Ctlutil.h (include Streams.h)</dt> </dl> |
| Library<br/> | <dl> <dt>Strmbase.lib (retail builds); </dt> <dt>Strmbasd.lib (debug builds)</dt> </dl> |
## See also
<dl> <dt>
[**CBaseControlVideo Class**](cbasecontrolvideo.md)
</dt> </dl>
| 30.011111 | 457 | 0.668271 | eng_Latn | 0.780915 |
933049061eefa6e493197c585705a104280ce36f | 1,713 | md | Markdown | accounts/forgot-password.md | sanatcha/ncp-docs | d153f90b5be8643a3b9286eaa0e9463aae69a250 | [
"MIT"
] | 3 | 2020-03-02T16:29:24.000Z | 2020-06-04T02:30:37.000Z | accounts/forgot-password.md | sanatcha/ncp-docs | d153f90b5be8643a3b9286eaa0e9463aae69a250 | [
"MIT"
] | 3 | 2020-03-02T06:45:54.000Z | 2020-06-05T03:05:29.000Z | accounts/forgot-password.md | sanatcha/ncp-docs | d153f90b5be8643a3b9286eaa0e9463aae69a250 | [
"MIT"
] | 13 | 2020-02-05T04:30:55.000Z | 2020-06-04T02:24:12.000Z | # Forgot Password
การรีเซ็ตรหัสผ่านสมาชิกของระบบ Nipa Cloud Platform \(NCP\) สามารถทำได้ที่หน้า [http://portal.nipa.cloud/forgot-password](http://portal.nipa.cloud/forgot-password) โดยมีขั้นตอนดังนี้
1.คลิก **Forgot Password**
2.กรอก **Email** ที่ใช้ในการสมัครสมาชิก แล้วทำการคลิก Send
3.หลังจากนั้นระบบจะทำการส่ง Email สำหรับการรีเซ็ตรหัสผ่านสมาชิกของระบบ Nipa Cloud Platform \(NCP\) โดยมีข้อความแจ้งว่า "E-mail was successfully sent"**.**
4.จากนั้นให้เข้าไปยัง Email ที่กรอกจากข้อข้างต้น แล้วคลิก RESET PASSWORD
{% hint style="info" %}
หากไม่ได้รับ Email หมายความว่า Email ที่กรอกจากข้างต้นนั้น ไม่มีอยู่ในระบบ
{% endhint %}
5.เมื่อเข้ามายังหน้า **Reset password** ให้ทำการกรอก Password ใหม่ โดยจะต้องถูกต้องตามเงื่อนไข แล้วจึงจะกด Confirm เพื่อ Reset password ได้
6.เมื่อระบบทำการ Reset password ได้สำเร็จ จะได้รับการ Redirect ไปยังหน้า Login พร้อมกับแสดงข้อความว่า "Reset your password is success".
| 51.909091 | 181 | 0.804437 | tha_Thai | 0.50217 |
9330bda4159bc2a417ae37458bcd33c42beb8d77 | 27 | md | Markdown | README.md | auctionee/balance | 6ff610237d5328b17b812ccba2404831fd024052 | [
"MIT"
] | null | null | null | README.md | auctionee/balance | 6ff610237d5328b17b812ccba2404831fd024052 | [
"MIT"
] | null | null | null | README.md | auctionee/balance | 6ff610237d5328b17b812ccba2404831fd024052 | [
"MIT"
] | null | null | null | # balance
balance service
| 9 | 16 | 0.777778 | eng_Latn | 0.758273 |
9330db531974230a53002540b4afdc79432b1d91 | 87 | md | Markdown | README.md | nnsncl/Container-Query | 39db62597432065ad716a91dca6db2d1a4e10de6 | [
"MIT"
] | null | null | null | README.md | nnsncl/Container-Query | 39db62597432065ad716a91dca6db2d1a4e10de6 | [
"MIT"
] | null | null | null | README.md | nnsncl/Container-Query | 39db62597432065ad716a91dca6db2d1a4e10de6 | [
"MIT"
] | null | null | null | # Container-Query
Based on https://heydonworks.com/article/the-flexbox-holy-albatross/
| 29 | 68 | 0.804598 | kor_Hang | 0.344669 |
933287cf7e14550861475c6c5840dad829cc6d1a | 1,738 | md | Markdown | README.md | AlexWheeler/mow | a367a0a38a909d1d0c82ae09405aeabaafb56560 | [
"MIT"
] | null | null | null | README.md | AlexWheeler/mow | a367a0a38a909d1d0c82ae09405aeabaafb56560 | [
"MIT"
] | null | null | null | README.md | AlexWheeler/mow | a367a0a38a909d1d0c82ae09405aeabaafb56560 | [
"MIT"
] | null | null | null | <pre>
.--.
/-. \
< ^ `D/
\_ (
)_/;.
_ __|_, \\
,(_I_______)\
//`-----\ \
// \____/\
// / /
// _____ / /\ \
.---n-. //'` `\/ / \ \
_____|_"_~_|___// /\ \ \ \
/ / \ / \ `\__...--' _\__\ \_/\
\\\\\\\\\\\\'-\__/--===-\__/-'`,,,,,,,,(____\,,,(__/,,,,,,,,,,,,,,,
\\\jgs\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
</pre>
# Mow
A command-line tool for transforming ruby files into one-liners that can be copy and pasted into a ruby repl
or really anywhere.
Useful for running local scripts in a Heroku rails console session, for example.
## Installation
Add this line to your application's Gemfile:
```ruby
gem 'mow'
```
And then execute:
$ bundle
Or install it yourself as:
$ gem install mow
## Usage
Print result to STDOUT
`mow ./path/to/file.rb`
Write result to file
`mow ./path/to/input_file.rb ./path_to_output_file.rb`
Copy results
`mow ./path/to/file.rb | pbcopy`
## Contributing
Bug reports and pull requests welcome!
## License
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
| 27.15625 | 110 | 0.35328 | eng_Latn | 0.774073 |
9332d852622acc5b4bf915371e134bed7127357c | 506 | md | Markdown | _definitions/bld-conseil-de-famille.md | digitallawyer/openlegaldictionary | a318d6c73c3d8e33756d947add397dac7f25cca2 | [
"MIT"
] | 5 | 2018-08-07T21:57:01.000Z | 2022-02-26T13:29:20.000Z | _definitions/bld-conseil-de-famille.md | digitallawyer/openlegaldictionary | a318d6c73c3d8e33756d947add397dac7f25cca2 | [
"MIT"
] | 1 | 2018-08-07T22:29:07.000Z | 2018-08-07T22:45:46.000Z | _definitions/bld-conseil-de-famille.md | digitallawyer/openlegaldictionary | a318d6c73c3d8e33756d947add397dac7f25cca2 | [
"MIT"
] | 2 | 2020-12-26T17:22:04.000Z | 2021-02-12T21:35:50.000Z | ---
title: Conseil De Famille
letter: C
permalink: "/definitions/bld-conseil-de-famille.html"
body: In French law. A family council. Certain acts require the sanction of this body.
For example, a guardian can neither accept nor reject an in-heritance to which the
minor has succeeded without Its authority, (Code Nap. 461;) nor can he accept for
the child a gift inter vivos without the like authority, (Id. 463
published_at: '2018-07-07'
source: Black's Law Dictionary 2nd Ed (1910)
layout: post
--- | 42.166667 | 86 | 0.758893 | eng_Latn | 0.993498 |
9332f0176acccf4e0acef9ef38695ff5a4dba4b1 | 13,881 | md | Markdown | docs/classes/YooKassa-Model-PaymentInterface.md | enotocode/yookassa-sdk-php | 9044afb9783b28d7c568c216a24f26656fb2b9c0 | [
"MIT"
] | null | null | null | docs/classes/YooKassa-Model-PaymentInterface.md | enotocode/yookassa-sdk-php | 9044afb9783b28d7c568c216a24f26656fb2b9c0 | [
"MIT"
] | null | null | null | docs/classes/YooKassa-Model-PaymentInterface.md | enotocode/yookassa-sdk-php | 9044afb9783b28d7c568c216a24f26656fb2b9c0 | [
"MIT"
] | null | null | null | # [YooKassa API SDK](../home.md)
# Interface: PaymentInterface
### Namespace: [\YooKassa\Model](../namespaces/yookassa-model.md)
---
**Summary:**
Interface PaymentInterface
---
### Constants
* No constants found
---
### Methods
| Visibility | Name | Flag | Summary |
| ----------:| ---- | ---- | ------- |
| public | [getAmount()](../classes/YooKassa-Model-PaymentInterface.md#method_getAmount) | | Возвращает сумму |
| public | [getAuthorizationDetails()](../classes/YooKassa-Model-PaymentInterface.md#method_getAuthorizationDetails) | | Возвращает данные об авторизации платежа |
| public | [getCancellationDetails()](../classes/YooKassa-Model-PaymentInterface.md#method_getCancellationDetails) | | Возвращает комментарий к статусу canceled: кто отменил платеж и по какой причине |
| public | [getCapturedAt()](../classes/YooKassa-Model-PaymentInterface.md#method_getCapturedAt) | | Возвращает время подтверждения платежа магазином или null если если время не задано |
| public | [getConfirmation()](../classes/YooKassa-Model-PaymentInterface.md#method_getConfirmation) | | Возвращает способ подтверждения платежа |
| public | [getCreatedAt()](../classes/YooKassa-Model-PaymentInterface.md#method_getCreatedAt) | | Возвращает время создания заказа |
| public | [getExpiresAt()](../classes/YooKassa-Model-PaymentInterface.md#method_getExpiresAt) | | Возвращает время до которого можно бесплатно отменить или подтвердить платеж или null если оно не задано |
| public | [getId()](../classes/YooKassa-Model-PaymentInterface.md#method_getId) | | Возвращает идентификатор платежа |
| public | [getIncomeAmount()](../classes/YooKassa-Model-PaymentInterface.md#method_getIncomeAmount) | | Возвращает сумму перечисляемая магазину за вычетом комиссий платежной системы.(только для успешных платежей) |
| public | [getMetadata()](../classes/YooKassa-Model-PaymentInterface.md#method_getMetadata) | | Возвращает метаданные платежа установленные мерчантом |
| public | [getPaid()](../classes/YooKassa-Model-PaymentInterface.md#method_getPaid) | | Проверяет был ли уже оплачен заказ |
| public | [getPaymentMethod()](../classes/YooKassa-Model-PaymentInterface.md#method_getPaymentMethod) | | Возвращает используемый способ проведения платежа |
| public | [getReceiptRegistration()](../classes/YooKassa-Model-PaymentInterface.md#method_getReceiptRegistration) | | Возвращает состояние регистрации фискального чека |
| public | [getRecipient()](../classes/YooKassa-Model-PaymentInterface.md#method_getRecipient) | | Возвращает получателя платежа |
| public | [getRefundable()](../classes/YooKassa-Model-PaymentInterface.md#method_getRefundable) | | Возможность провести возврат по API |
| public | [getRefundedAmount()](../classes/YooKassa-Model-PaymentInterface.md#method_getRefundedAmount) | | Возвращает сумму возвращенных средств |
| public | [getRequestor()](../classes/YooKassa-Model-PaymentInterface.md#method_getRequestor) | | Возвращает инициатора платежа |
| public | [getStatus()](../classes/YooKassa-Model-PaymentInterface.md#method_getStatus) | | Возвращает состояние платежа |
| public | [getTransfers()](../classes/YooKassa-Model-PaymentInterface.md#method_getTransfers) | | Возвращает данные о распределении платежа между магазинами |
---
### Details
* File: [lib/Model/PaymentInterface.php](../../lib/Model/PaymentInterface.php)
* Package: \YooKassa
---
### Tags
| Tag | Version | Description |
| --- | ------- | ----------- |
| property-read | | Идентификатор платежа |
| property-read | | Текущее состояние платежа |
| property-read | | Получатель платежа |
| property-read | | Сумма заказа |
| property-read | | Описание транзакции |
| property-read | | Способ проведения платежа |
| property-read | | Способ проведения платежа |
| property-read | | Время создания заказа |
| property-read | | Время создания заказа |
| property-read | | Время подтверждения платежа магазином |
| property-read | | Время подтверждения платежа магазином |
| property-read | | Время, до которого можно бесплатно отменить или подтвердить платеж |
| property-read | | Время, до которого можно бесплатно отменить или подтвердить платеж |
| property-read | | Способ подтверждения платежа |
| property-read | | Сумма возвращенных средств платежа |
| property-read | | Сумма возвращенных средств платежа |
| property-read | | Признак оплаты заказа |
| property-read | | Возможность провести возврат по API |
| property-read | | Состояние регистрации фискального чека |
| property-read | | Состояние регистрации фискального чека |
| property-read | | Метаданные платежа указанные мерчантом |
| property-read | | Признак тестовой операции |
| property-read | | Комментарий к отмене платежа |
| property-read | | Комментарий к отмене платежа |
| property-read | | Данные об авторизации платежа |
| property-read | | Данные об авторизации платежа |
| property-read | | Данные о распределении платежа между магазинами |
| property-read | | Сумма платежа, которую получит магазин |
| property-read | | Сумма платежа, которую получит магазин |
| property-read | | Инициатор платежа |
---
## Methods
<a name="method_getId" class="anchor"></a>
#### public getId() : string
```php
public getId() : string
```
**Summary**
Возвращает идентификатор платежа
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** string - Идентификатор платежа
<a name="method_getStatus" class="anchor"></a>
#### public getStatus() : string
```php
public getStatus() : string
```
**Summary**
Возвращает состояние платежа
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** string - Текущее состояние платежа
<a name="method_getRecipient" class="anchor"></a>
#### public getRecipient() : \YooKassa\Model\RecipientInterface|null
```php
public getRecipient() : \YooKassa\Model\RecipientInterface|null
```
**Summary**
Возвращает получателя платежа
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\RecipientInterface|null - Получатель платежа или null если получатель не задан
<a name="method_getAmount" class="anchor"></a>
#### public getAmount() : \YooKassa\Model\AmountInterface
```php
public getAmount() : \YooKassa\Model\AmountInterface
```
**Summary**
Возвращает сумму
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\AmountInterface - Сумма платежа
<a name="method_getPaymentMethod" class="anchor"></a>
#### public getPaymentMethod() : \YooKassa\Model\PaymentMethod\AbstractPaymentMethod
```php
public getPaymentMethod() : \YooKassa\Model\PaymentMethod\AbstractPaymentMethod
```
**Summary**
Возвращает используемый способ проведения платежа
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\PaymentMethod\AbstractPaymentMethod - Способ проведения платежа
<a name="method_getCreatedAt" class="anchor"></a>
#### public getCreatedAt() : \DateTime
```php
public getCreatedAt() : \DateTime
```
**Summary**
Возвращает время создания заказа
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \DateTime - Время создания заказа
<a name="method_getCapturedAt" class="anchor"></a>
#### public getCapturedAt() : \DateTime|null
```php
public getCapturedAt() : \DateTime|null
```
**Summary**
Возвращает время подтверждения платежа магазином или null если если время не задано
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \DateTime|null - Время подтверждения платежа магазином
<a name="method_getConfirmation" class="anchor"></a>
#### public getConfirmation() : \YooKassa\Model\Confirmation\AbstractConfirmation
```php
public getConfirmation() : \YooKassa\Model\Confirmation\AbstractConfirmation
```
**Summary**
Возвращает способ подтверждения платежа
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\Confirmation\AbstractConfirmation - Способ подтверждения платежа
<a name="method_getRefundedAmount" class="anchor"></a>
#### public getRefundedAmount() : \YooKassa\Model\AmountInterface
```php
public getRefundedAmount() : \YooKassa\Model\AmountInterface
```
**Summary**
Возвращает сумму возвращенных средств
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\AmountInterface - Сумма возвращенных средств платежа
<a name="method_getPaid" class="anchor"></a>
#### public getPaid() : bool
```php
public getPaid() : bool
```
**Summary**
Проверяет был ли уже оплачен заказ
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** bool - Признак оплаты заказа, true если заказ оплачен, false если нет
<a name="method_getRefundable" class="anchor"></a>
#### public getRefundable() : bool
```php
public getRefundable() : bool
```
**Summary**
Возможность провести возврат по API
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** bool - Возможность провести возврат по API
<a name="method_getReceiptRegistration" class="anchor"></a>
#### public getReceiptRegistration() : string
```php
public getReceiptRegistration() : string
```
**Summary**
Возвращает состояние регистрации фискального чека
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** string - Состояние регистрации фискального чека
<a name="method_getMetadata" class="anchor"></a>
#### public getMetadata() : \YooKassa\Model\Metadata
```php
public getMetadata() : \YooKassa\Model\Metadata
```
**Summary**
Возвращает метаданные платежа установленные мерчантом
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\Metadata - Метаданные платежа указанные мерчантом
<a name="method_getExpiresAt" class="anchor"></a>
#### public getExpiresAt() : \DateTime|null
```php
public getExpiresAt() : \DateTime|null
```
**Summary**
Возвращает время до которого можно бесплатно отменить или подтвердить платеж или null если оно не задано
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \DateTime|null - Время, до которого можно бесплатно отменить или подтвердить платеж
##### Tags
| Tag | Version | Description |
| --- | ------- | ----------- |
| since | 1.0.2 | |
<a name="method_getCancellationDetails" class="anchor"></a>
#### public getCancellationDetails() : \YooKassa\Model\CancellationDetailsInterface|null
```php
public getCancellationDetails() : \YooKassa\Model\CancellationDetailsInterface|null
```
**Summary**
Возвращает комментарий к статусу canceled: кто отменил платеж и по какой причине
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\CancellationDetailsInterface|null - Комментарий к статусу canceled
##### Tags
| Tag | Version | Description |
| --- | ------- | ----------- |
| since | 1.0.13 | |
<a name="method_getAuthorizationDetails" class="anchor"></a>
#### public getAuthorizationDetails() : \YooKassa\Model\AuthorizationDetailsInterface|null
```php
public getAuthorizationDetails() : \YooKassa\Model\AuthorizationDetailsInterface|null
```
**Summary**
Возвращает данные об авторизации платежа
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\AuthorizationDetailsInterface|null - Данные об авторизации платежа
##### Tags
| Tag | Version | Description |
| --- | ------- | ----------- |
| since | 1.0.18 | |
<a name="method_getTransfers" class="anchor"></a>
#### public getTransfers() : \YooKassa\Model\TransferInterface[]
```php
public getTransfers() : \YooKassa\Model\TransferInterface[]
```
**Summary**
Возвращает данные о распределении платежа между магазинами
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\TransferInterface[] -
<a name="method_getIncomeAmount" class="anchor"></a>
#### public getIncomeAmount() : \YooKassa\Model\MonetaryAmount|null
```php
public getIncomeAmount() : \YooKassa\Model\MonetaryAmount|null
```
**Summary**
Возвращает сумму перечисляемая магазину за вычетом комиссий платежной системы.(только для успешных платежей)
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\MonetaryAmount|null -
<a name="method_getRequestor" class="anchor"></a>
#### public getRequestor() : \YooKassa\Model\RequestorInterface
```php
public getRequestor() : \YooKassa\Model\RequestorInterface
```
**Summary**
Возвращает инициатора платежа
**Details:**
* Inherited From: [\YooKassa\Model\PaymentInterface](../classes/YooKassa-Model-PaymentInterface.md)
**Returns:** \YooKassa\Model\RequestorInterface -
---
### Top Namespaces
* [\YooKassa](../namespaces/yookassa.md)
---
### Reports
* [Errors - 0](../reports/errors.md)
* [Markers - 0](../reports/markers.md)
* [Deprecated - 7](../reports/deprecated.md)
---
This document was automatically generated from source code comments on 2021-04-21 using [phpDocumentor](http://www.phpdoc.org/)
© 2021 YooMoney | 32.206497 | 216 | 0.738852 | kor_Hang | 0.17673 |
93333f7e03feb3ca5fdca2111e2dcf0478ebcdca | 325 | md | Markdown | multilingual_t5/sequence_lengths/README.md | JoanZhou/multilingual-t5 | 57e34275a720210ba0a8c565b71bfc547031836e | [
"Apache-2.0"
] | 833 | 2020-10-22T18:15:17.000Z | 2022-03-30T08:12:06.000Z | multilingual_t5/sequence_lengths/README.md | JoanZhou/multilingual-t5 | 57e34275a720210ba0a8c565b71bfc547031836e | [
"Apache-2.0"
] | 53 | 2020-10-23T04:16:53.000Z | 2022-03-31T06:59:38.000Z | multilingual_t5/sequence_lengths/README.md | JoanZhou/multilingual-t5 | 57e34275a720210ba0a8c565b71bfc547031836e | [
"Apache-2.0"
] | 93 | 2020-10-23T03:59:31.000Z | 2022-03-31T03:30:39.000Z | These .gin files define input and target lengths for all tasks.
1. Input length: set to a number that is a power of two and
larger than 1.1 * 99.9 percentile sequence length in train, dev, and test.
2. Target length: computed by packing examples from train, valid, and test,
and taking the max packed target length.
| 36.111111 | 77 | 0.747692 | eng_Latn | 0.999812 |
9333769813c899820bc4c539aeb8621ffc00f6de | 1,408 | md | Markdown | 2020/11/07/2020-11-07 07:25.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | 3 | 2020-07-14T14:54:15.000Z | 2020-08-21T06:48:24.000Z | 2020/11/07/2020-11-07 07:25.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020/11/07/2020-11-07 07:25.md | zhzhzhy/WeiBoHot_history | 32ce4800e63f26384abb17d43e308452c537c902 | [
"MIT"
] | null | null | null | 2020年11月07日07时数据
Status: 200
1.佐治亚州将重新计票
微博热度:1765785
2.李荣浩心疼杨丞琳
微博热度:1068087
3.浪琴天猫双11倒计时
微博热度:902018
4.谢霆锋 单依纯让我多了两根白头发
微博热度:699043
5.立冬
微博热度:678807
6.橘朵客服
微博热度:519832
7.为吃鱼致2.2公里河段鱼类几近灭绝
微博热度:436952
8.拜登在佐治亚州反超特朗普
微博热度:383770
9.中国学者发现5亿多年前四不像动物
微博热度:321042
10.鹿晗花5块钱开厕所门
微博热度:318593
11.哈哈哈哈哈
微博热度:318118
12.爸爸给萌娃准备超大枯叶带幼儿园
微博热度:304713
13.东莞一男子坠楼砸中快递员均身亡
微博热度:271351
14.拜登在宾州反超特朗普
微博热度:260788
15.鹿亦尧蔡思雨正式交往
微博热度:259526
16.iPhone 12 Pro Max开售
微博热度:236438
17.唐嫣佘诗曼卢杉晒图争宠
微博热度:235981
18.警方通报男子跪爬哭诉女友被杀
微博热度:234699
19.苹果官网崩了
微博热度:233142
20.杨丞琳演唱会踩空
微博热度:231325
21.山东一工地发现东汉古墓
微博热度:229900
22.银行工作还是金饭碗吗
微博热度:228918
23.受害者家属仍不接受张玉环无罪
微博热度:227631
24.香港电台计划16日起每早8时播国歌
微博热度:225818
25.邓超陈赫鹿晗上了贼船
微博热度:225175
26.孟美岐吴宣仪程潇微博认证
微博热度:224941
27.从结婚开始恋爱
微博热度:216501
28.蛋壳公寓深陷流动性危机
微博热度:212999
29.山洞内隐居8年小伙发声
微博热度:211122
30.安又琪再唱你好周杰伦
微博热度:210918
31.李易峰演技
微博热度:196708
32.小朋友的睡姿千奇百怪
微博热度:140579
33.美国大选
微博热度:138382
34.人类幼崽小奶音图鉴
微博热度:123202
35.宋佳章宇酸奶吻
微博热度:122735
36.这就是上帝打翻了颜料盘吗
微博热度:108730
37.燕云台
微博热度:105759
38.曹杨给我一个理由忘记
微博热度:103562
39.隐秘而伟大
微博热度:95189
40.网络平台不得强迫商家站队二选一
微博热度:94007
41.原来数学是有用的
微博热度:92026
42.沈青禾怼人
微博热度:91663
43.中国好声音
微博热度:83500
44.黄明昊
微博热度:79986
45.内蒙古致32死瓦斯爆炸事故案32人获刑
微博热度:70581
46.女生用棒棒糖答谢公交车司机
微博热度:66869
47.鹿方宁凌睿吃醋
微博热度:66510
48.KDA新歌
微博热度:65860
49.福建猥亵女学生副教授已被开除
微博热度:58410
50.傅容肃王对视好甜
微博热度:58112
| 6.901961 | 22 | 0.77983 | yue_Hant | 0.258254 |
93339eba8f3a9757b27b9e21b0a5abb19a689cac | 1,085 | md | Markdown | README.md | akram/docker-gogs | fbe013b8663e587a2466a0a58d116f2ebf0bf78b | [
"MIT"
] | 60 | 2015-01-13T13:16:48.000Z | 2018-05-09T09:38:43.000Z | README.md | akram/docker-gogs | fbe013b8663e587a2466a0a58d116f2ebf0bf78b | [
"MIT"
] | 10 | 2015-02-02T10:41:55.000Z | 2017-11-22T02:37:40.000Z | README.md | akram/docker-gogs | fbe013b8663e587a2466a0a58d116f2ebf0bf78b | [
"MIT"
] | 29 | 2015-01-12T14:55:34.000Z | 2020-03-27T11:26:36.000Z | docker-gogs
===========
Dockerfile for [gogs](http://gogs.io) server(a self-hosted git service).
>This repo have been combined into <https://github.com/gogits/gogs> in 2015-08-17.
Since the offcial repo got too many issues. Issue about docker gogs can still submit here.
## Usage
```
docker pull gogs/gogs
mkdir -p /var/gogs
docker run --name=gogs -d -p 10022:22 -p 10080:3000 -v /var/gogs:/data gogs/gogs
```
More details can be found in <https://github.com/gogits/gogs/tree/master/docker>
### Link with mysql
mysql is from <https://registry.hub.docker.com/_/mysql/>.
**Alert**. Not tested. For my machine got too low memory, and canot run mysql.
If you are interested to test. Pull request are welcome. pr to <https://github.com/gogits/gogs> branch: develop
First start an mysql instance
docker pull mysql
docker run --name gogs-mysql -e MYSQL_DATABASE=gogs -e MYSQL_ROOT_PASSWORD=abcd -d mysql
Then run gogs
mkdir -p /var/gogs
docker run --rm -ti --name gogs --link gogs-mysql:mysql -p 10022:22 -p 10080:3000 -v /var/gogs:/data codeskyblue/docker-gogs
Good luck.
| 28.552632 | 125 | 0.723502 | eng_Latn | 0.562874 |
9333d2ed0ec0dc04d732c1b93d7801c6190fbe21 | 7,449 | md | Markdown | docs/modeling/model-user-requirements.md | drigovz/visualstudio-docs.pt-br | 7a1b53ff3dd5c3151e9c8b855599edf499df9d95 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/modeling/model-user-requirements.md | drigovz/visualstudio-docs.pt-br | 7a1b53ff3dd5c3151e9c8b855599edf499df9d95 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/modeling/model-user-requirements.md | drigovz/visualstudio-docs.pt-br | 7a1b53ff3dd5c3151e9c8b855599edf499df9d95 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Requisitos de usuário do modelo
description: Saiba como o Visual Studio ajuda você a entender, discutir e comunicar as necessidades dos usuários por meio de diagramas de desenho sobre suas atividades.
ms.custom: SEO-VS-2020
ms.date: 11/04/2016
ms.topic: conceptual
helpviewer_keywords:
- requirements
- stories
author: JoshuaPartlow
ms.author: joshuapa
manager: jmartens
ms.workload:
- multiple
ms.openlocfilehash: d55e549d2dccdc047cbf4449392cc090a569f85c
ms.sourcegitcommit: ae6d47b09a439cd0e13180f5e89510e3e347fd47
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 02/08/2021
ms.locfileid: "99970576"
---
# <a name="model-user-requirements"></a>Requisitos de usuário do modelo
O Visual Studio ajuda você a entender, discutir e comunicar as necessidades dos usuários desenhando diagramas sobre suas atividades e a parte que seu sistema desempenha para ajudá-los a atingir suas metas. Um modelo de requisitos é um conjunto desses diagramas, cada um deles concentra-se em um aspecto diferente das necessidades dos usuários. Para ver uma demonstração em vídeo, consulte: [modelando o domínio de negócios](https://channel9.msdn.com/blogs/clinted/uml-with-vs-2010-part-3-modeling-the-business-domain).
Para ver quais versões do Visual Studio oferecem suporte a cada tipo de modelo, consulte [suporte de versão para ferramentas de arquitetura e modelagem](../modeling/what-s-new-for-design-in-visual-studio.md#VersionSupport).
Um modelo de requisitos ajuda você a:
- Concentre-se no comportamento externo do sistema, separadamente de seu design interno.
- Descreva as necessidades dos usuários e dos participantes com muito menos ambigüidade do que você pode em linguagem natural.
- Defina um glossário consistente de termos que podem ser usados por usuários, desenvolvedores e testadores.
- Reduza lacunas e inconsistências nos requisitos.
- Reduza o trabalho necessário para responder às alterações de requisitos.
- Planeje a ordem na qual os recursos serão desenvolvidos.
- Use os modelos como base para testes do sistema, fazendo uma relação clara entre os testes e os requisitos. Quando os requisitos mudam, essa relação ajuda a atualizar os testes corretamente. Isso garante que o sistema atenda aos novos requisitos.
Um modelo de requisitos fornece maior benefício se você usá-lo para enfocar discussões com os usuários ou seus representantes e revisitá-lo no início de cada iteração. Você não precisa concluí-lo detalhadamente antes de escrever código. Um aplicativo parcialmente funcional, mesmo que seja muito simplificado, geralmente forma a base mais stimulating para a discussão dos requisitos com os usuários. O modelo é uma maneira eficaz de resumir os resultados dessas discussões. Para obter mais informações, consulte [usar modelos em seu processo de desenvolvimento](../modeling/use-models-in-your-development-process.md).
> [!NOTE]
> Durante esses tópicos, "System" significa o sistema ou o aplicativo que você está desenvolvendo. Pode ser uma grande coleção de muitos componentes de software e hardware; ou um único aplicativo; ou um componente de software dentro de um sistema maior. Em todos os casos, o modelo de requisitos descreve o comportamento que é visível de fora do seu sistema, seja por meio de uma interface de usuário ou API.
## <a name="common-tasks"></a>Tarefas comuns
Você pode criar várias exibições diferentes dos requisitos dos usuários. Cada exibição fornece um tipo específico de informação. Quando você cria essas exibições, é melhor movê-las com frequência de uma para outra. Você pode iniciar em qualquer modo de exibição.
|Diagrama ou documento|O que ele descreve em um modelo de requisitos|Seção|
|-|-|-|
|Diagrama de classe conceitual|Glossário de tipos que são usados para descrever os requisitos; os tipos visíveis na interface do sistema.||
|Documentos adicionais ou itens de trabalho|Critérios de desempenho, segurança, usabilidade e confiabilidade.|[Descrevendo os requisitos de qualidade de serviço](#QoSRequirements)|
|Documentos adicionais ou itens de trabalho|Restrições e regras não específicas de um caso de uso específico|[Mostrando regras de negócio](#BusinessRules)|
Observe que a maioria dos tipos de diagramas pode ser usada para outras finalidades. Para obter uma visão geral dos tipos de diagrama, consulte [criar modelos para seu aplicativo](../modeling/create-models-for-your-app.md).
## <a name="showing-business-rules"></a><a name="BusinessRules"></a> Mostrando regras de negócio
Uma regra de negócio é um requisito que não está associado a um caso de uso específico e deve ser observado em todo o sistema.
Muitas regras de negócio são restrições sobre as relações entre as classes conceituais. Você pode escrever essas *regras de negócio estáticos* como comentários associados às classes relevantes em um diagrama de classe conceitual. Por exemplo:
*As regras de negócio dinâmicas* restringem as sequências de eventos permitidas. Por exemplo, você usa um diagrama de sequência ou atividade para mostrar que um usuário deve fazer logon antes de executar outras operações em seu sistema.
No entanto, muitas regras dinâmicas podem ser mais eficientes e genericamente declaradas substituindo-as por regras estáticas. Por exemplo, você pode adicionar um atributo booliano "conectado" a uma classe no modelo de classe conceitual. Você adicionaria logon como a pré-condição do caso de uso de log e a adicionaria como uma pré-condição da maioria dos outros casos de uso. Essa abordagem permite evitar a definição de todas as combinações possíveis de sequências de eventos. Também é mais flexível quando você precisa adicionar novos casos de uso ao modelo.
Observe que a escolha aqui é sobre como você define os requisitos e que isso é independente de como você implementa os requisitos no código do programa.
Os tópicos a seguir fornecem mais informações:
|Para saber mais|Ler|
|-|-|
|Como desenvolver código que siga as regras de negócio|[Modelar a arquitetura do aplicativo](../modeling/model-your-app-s-architecture.md)|
## <a name="describing-quality-of-service-requirements"></a><a name="QoSRequirements"></a> Descrevendo os requisitos de qualidade de serviço
Há várias categorias de requisitos de qualidade de serviço. Eles incluem o seguinte:
- Desempenho
- Segurança
- Usabilidade
- Confiabilidade
- Robustez
Você pode incluir alguns desses requisitos nas descrições de casos de uso específicos. Outros requisitos não são específicos para casos de uso e são escritos com mais eficiência em um documento separado. Quando possível, é útil aderir ao vocabulário definido pelo modelo de requisitos. No exemplo a seguir, observe que as palavras principais usadas no requisito são os títulos de atores, casos de uso e classes nas ilustrações anteriores:
Se um restaurante excluir um item de menu enquanto um cliente estiver solicitando uma refeição, qualquer item de pedido que se refere a esse item de menu será exibido em vermelho.
Consulte [modelar a arquitetura do aplicativo](../modeling/model-your-app-s-architecture.md) para saber como desenvolver código que atenda aos requisitos de qualidade de serviço.
## <a name="see-also"></a>Confira também
- [Usar modelos no processo de desenvolvimento](../modeling/use-models-in-your-development-process.md)
- [Modelar a arquitetura do aplicativo](../modeling/model-your-app-s-architecture.md)
| 70.942857 | 617 | 0.804806 | por_Latn | 0.999905 |
9334292986f7683b80a04c2d1fcdefa9bc0ecf75 | 54 | md | Markdown | README.md | codextension/neuralnetwork | ea3e59c32908a578f0e4cae53b7ae658306922da | [
"Apache-2.0"
] | null | null | null | README.md | codextension/neuralnetwork | ea3e59c32908a578f0e4cae53b7ae658306922da | [
"Apache-2.0"
] | null | null | null | README.md | codextension/neuralnetwork | ea3e59c32908a578f0e4cae53b7ae658306922da | [
"Apache-2.0"
] | null | null | null | # neural_network
Neural Network implementation in C++
| 18 | 36 | 0.814815 | eng_Latn | 0.873316 |
933466da29da9a63c4e120f2511a7aa777e8faf0 | 1,165 | md | Markdown | website/docs/pages/scripts.md | itchef/regauge | e224a3f52e16ae89fbad2936a4dab6dcb591b813 | [
"MIT"
] | 2 | 2019-11-22T07:09:53.000Z | 2019-11-22T08:10:12.000Z | website/docs/pages/scripts.md | itchef/rg-cli | e224a3f52e16ae89fbad2936a4dab6dcb591b813 | [
"MIT"
] | null | null | null | website/docs/pages/scripts.md | itchef/rg-cli | e224a3f52e16ae89fbad2936a4dab6dcb591b813 | [
"MIT"
] | 3 | 2020-01-02T18:34:50.000Z | 2020-03-10T14:20:22.000Z | # Scripts
Inside the newly created project, you can run some built-in commands:
| Tasks | Description |
|---------------------------|:---------------------------------------------------------:|
| **npm start** | Boots your application up on http://localhost:8080/ |
| **npm build** | Builds your application in production mode. |
| **npm test** | Run jest unit test cases of the newly created application |
| **npm run test:coverage** | Run jest unit test cases with coverage |
| **npm run test:watch** | Run jest unit test cases on watch mode |
| **npm run pretty** | Run the prettier checks |
| **npm run lint** | Run eslint checks for the application |
| **npm run lint:fix** | Fix ESLint issues |
| **npm run lint:styles** | Run style lint checks for the application |
Once you build your application using the scripts, it will be minified and ready to deploy.
| 64.722222 | 91 | 0.472961 | eng_Latn | 0.945356 |
9334f3fd2c2f388d84cab570c12633a0ea7953e1 | 8,000 | md | Markdown | mixed-reality-docs/scale.md | MicrosoftDocs/mixed-reality.de-DE | 2aec73052437bb8c01b0c7deabad0c54b8aaf573 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-18T20:14:18.000Z | 2021-04-20T21:15:44.000Z | mixed-reality-docs/scale.md | MicrosoftDocs/mixed-reality.de-DE | 2aec73052437bb8c01b0c7deabad0c54b8aaf573 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | mixed-reality-docs/scale.md | MicrosoftDocs/mixed-reality.de-DE | 2aec73052437bb8c01b0c7deabad0c54b8aaf573 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-10-11T20:19:01.000Z | 2021-11-15T10:21:20.000Z | ---
title: Skalieren
description: Ein wichtiger Aspekt bei der realistischen Wirkung von holografisch dargestellten Inhalten ist das möglichst genaue Nachahmen der visuellen Statistik der echten Welt.
author: shengkait
ms.author: shentan
ms.date: 03/21/2018
ms.topic: article
keywords: Gemischte Windows-Realität, Stil, Entwurf
ms.openlocfilehash: eeec28fbf98cf4386a57cde4452cd3f8977d7780
ms.sourcegitcommit: 6bc6757b9b273a63f260f1716c944603dfa51151
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 11/01/2019
ms.locfileid: "73437506"
---
# <a name="scale"></a>Skalieren
Ein wichtiger Aspekt bei der realistischen Wirkung von holografisch dargestellten Inhalten ist das möglichst genaue Nachahmen der visuellen Statistik der echten Welt. Das bedeutet, so viele visuelle Hinweise wie möglich einzubeziehen, die uns (in der realen Welt) zu verstehen helfen, wo sich Objekte befinden, wie groß sie sind und woraus sie bestehen. Die Skalierung eines Objekts ist eine der wichtigsten dieser visuellen Hinweise und gibt einem Viewer einen Eindruck von der Größe eines Objekts sowie von Hinweisen zu seiner Position (insbesondere bei Objekten mit einer bekannten Größe). Außerdem wurde das Anzeigen von Objekten in einer realen Skala als eines der wichtigsten Unterschiede bei gemischter Realität im allgemeinen angesehen – etwas, das bei der bildschirmbasierten Anzeige zuvor nicht möglich war.
<br>
---
## <a name="how-to-suggest-the-scale-of-objects-and-environments"></a>Vorschlagen der Skalierung von Objekten und Umgebungen
Es gibt viele Möglichkeiten, die Skalierung eines Objekts vorzuschlagen, von denen einige mögliche Auswirkungen auf andere perzeptive Faktoren haben. Der Schlüssel besteht darin, die Objekte einfach in der Größe "Real" anzuzeigen und diese realistische Größe beizubehalten, wenn Benutzer sich bewegen. Dies bedeutet, dass holograms eine andere Menge an Sicht des visuellen Elements eines Benutzers in die gleiche Weise erhalten, wie es bei echten Objekten der Fall ist.
### <a name="utilize-the-distance-of-objects-as-they-are-presented-to-the-user"></a>Verwenden Sie den Abstand von Objekten, wie Sie dem Benutzer angezeigt werden.
Eine gängige Methode besteht darin, den Abstand von Objekten zu nutzen, wie Sie für den Benutzer angezeigt werden. Nehmen Sie beispielsweise an, dass Sie ein großes Familienfahrzeug vor dem Benutzer visualisieren. Wenn sich das Auto direkt davor befand, wäre es bei der Arm-Länge zu groß, damit es in das Feld des Benutzers passt. Dies würde dazu führen, dass der Benutzer seine Kopfzeile und den Hauptteil verschieben muss, um das gesamte Objekt zu verstehen. Wenn das Fahrzeug weiter entfernt wurde (im gesamten Raum), kann der Benutzer einen Eindruck von der Skalierung feststellen, indem er das gesamte Objekt in der Ansicht sehen kann, und sich dann näher an den Bereich bewegen, um Bereiche im Detail zu überprüfen.
:::row:::
:::column:::
**[Mit diesem Verfahren wurde von Volvo ein Showroom](https://www.youtube.com/watch?v=DilzwF90vec)** für ein neues Auto erstellt, das die Skalierung des Holographic Car auf eine Weise nutzte, die für den Benutzer realistisch und intuitiv war. Die Benutzeroberflächen beginnen mit einem Hologramm des Autos für eine physische Tabelle, sodass der Benutzer die Gesamtgröße und Form des Modells verstehen kann. Zu einem späteren Zeitpunkt wächst das Auto in eine größere Skalierung (über die Größe des Geräts hinaus), aber da der Benutzer bereits einen Verweis aus dem kleineren Modell abgerufen hat, kann er auf die Features des Autos angemessen navigieren.<br>
<br>
*Image: Volvo Cars-Darstellung für hololens*
:::column-end:::
:::column:::
<br>
:::column-end:::
:::row-end:::
<br>
---
### <a name="use-holograms-to-modify-the-users-real-space"></a>Verwenden Sie holograms, um den tatsächlichen Bereich des Benutzers zu ändern.
Eine andere Methode ist die Verwendung von holograms, um den tatsächlichen Bereich des Benutzers zu ändern, die vorhandenen Wände oder Obergrenzen durch Umgebungen zu ersetzen oder "Löcher" oder "Windows" anfügen, sodass mehrstufige Objekte den physischen Raum scheinbar "durchbrechen" können. Beispielsweise kann eine große Struktur nicht in die meisten Benutzer Räume passen, sondern durch das Platzieren eines virtuellen Himmels auf die virtuelle Oberfläche. Dadurch kann der Benutzer die Basis der virtuellen Struktur durchlaufen und einen Eindruck davon erfassen, wie er in der Praxis aussehen würde, und dann sehen, dass er sich weit über den physischen Raum des Raums hinaus erstreckt.
:::row:::
:::column:::
**[Minecraft entwickelte](https://minecraft.net/)** mithilfe einer ähnlichen Technik ein Konzept. Durch Hinzufügen eines virtuellen Fensters zu einer physischen Oberfläche in einem Raum werden die vorhandenen Objekte im Raum im Kontext einer erheblich größeren Umgebung platziert, die über die physischen Skalierungs Beschränkungen des Raums hinausgeht.<br>
<br>
*Image: minecraft Concept-Darstellung für hololens*
:::column-end:::
:::column:::
<br><br>
:::column-end:::
:::row-end:::
<br>
---
## <a name="experimenting-with-scale"></a>Experimentieren mit der Skala
In manchen Fällen haben Designer mit der Änderung der Skala experimentieren (indem Sie die angezeigte "echte" Größe des Objekts geändert haben) und gleichzeitig eine einzelne Position des Objekts beibehalten. so kann ein Objekt ohne wirkliche Bewegung näher oder weiter in einen Viewer gelangen. Dies wurde in einigen Fällen getestet, um die Anzeige von Elementen zu beschleunigen, während gleichzeitig die möglichen Komfort Beschränkungen beim Anzeigen von virtuellen Inhalten, die näher sind als die "Zone der Bequemlichkeit", zu berücksichtigen sind.
Dadurch können einige mögliche Artefakte in der-Darstellung erstellt werden:
* Bei virtuellen Objekten, die ein Objekt mit der "bekannten" Größe des Viewers darstellen, führt das Ändern der Skala ohne Änderung der Position zu Konflikt verursachenden visuellen Hinweisen – die Augen können das Objekt in gewisser Weise aufgrund von verseh-hinweisen (siehe [Komfort](comfort.md) Weitere Informationen hierzu finden Sie in diesem Artikel, aber die Größe fungiert als monokulärer Hinweis darauf, dass das Objekt möglicherweise näher kommt. Diese Konflikt verursachenden Hinweise führen zu verwirrten Wahrnehmungen – Betrachter sehen das Objekt oft als vorhanden (aufgrund der Konstanten Tiefe), werden jedoch schnell vergrößert.
* In einigen Fällen wird die Skalierungs Änderung stattdessen als "sich abzeichtender" Hinweis betrachtet, wobei das Objekt möglicherweise nicht angezeigt wird, um die Skalierung durch einen Viewer zu ändern, aber anscheinend direkt in den Augenblick des Viewers verschoben wird (was eine unangenehme Sensation sein kann).
* Bei Vergleichs Oberflächen in der realen Welt werden solche Skalierungs Änderungen manchmal als veränderliche Position entlang mehrerer Achsen angezeigt – Objekte werden möglicherweise herabgestuft, anstatt sich näher zu bewegen (ähnlich in einer 2D-Projektion der 3D-Bewegung in einigen Fällen).
* Schließlich kann das Ändern der Skalierung für Objekte ohne bekannte Größe (z. b. beliebige Formen mit beliebigen Größen, Benutzeroberflächen Elementen usw.) funktionell als eine Möglichkeit fungieren, Änderungen in der Entfernung zu imitieren – Betrachter haben nicht so viele vorvorhandene Top-Down-Hinweise, nach denen Sie verstehen Sie die tatsächliche Größe oder den Speicherort des Objekts, sodass die Skalierung als wichtiger Hinweis verarbeitet werden kann.
<br>
---
## <a name="see-also"></a>Weitere Informationen:
* [Farbe, Licht und Materialien](color,-light-and-materials.md)
* [Typografie](typography.md)
* [Raumklangentwurf](spatial-sound-design.md)
| 91.954023 | 817 | 0.7995 | deu_Latn | 0.998728 |
933503d419ec8d2048216918e48f1937b3914aab | 1,557 | md | Markdown | website/docs/cheatsheet/dev/vue.md | LianSJ7729/leops-cheatsheet | 44425f616163b44b936841895785741cee0239e9 | [
"MIT"
] | 16 | 2019-11-11T02:53:39.000Z | 2021-11-11T07:22:29.000Z | website/docs/cheatsheet/dev/vue.md | LianSJ7729/leops-cheatsheet | 44425f616163b44b936841895785741cee0239e9 | [
"MIT"
] | null | null | null | website/docs/cheatsheet/dev/vue.md | LianSJ7729/leops-cheatsheet | 44425f616163b44b936841895785741cee0239e9 | [
"MIT"
] | 12 | 2019-11-13T06:14:24.000Z | 2022-03-01T09:15:17.000Z | ## 引用
```html
<script src="https://cdn.jsdelivr.net/npm/[email protected]"></script>
```
## 循环
```javascript
// 列表
<ul id="example-1">
<li v-for="item in items">
{{ item.message }}
</li>
</ul>
// 列表索引
<ul id="example-1">
<li v-for="(item, index) in items">
{{ index }} - {{ item.message }}
</li>
</ul>
---
var example1 = new Vue({
el: '#example-1',
data: {
items: [
{ message: 'Foo' },
{ message: 'Bar' }
]
}
})
```
```javascript
// 对象
<ul id="v-for-object" class="demo">
<li v-for="value in object">
{{ value }}
</li>
</ul>
<div v-for="(value, name) in object">
{{ name }}: {{ value }}
</div>
<div v-for="(value, name, index) in object">
{{ index }}. {{ name }}: {{ value }}
</div>
---
new Vue({
el: '#v-for-object',
data: {
object: {
title: 'How to do lists in Vue',
author: 'Jane Doe',
publishedAt: '2016-04-10'
}
}
})
```
```javascript
// 模板
<ul>
<template v-for="item in items">
<li>{{ item.msg }}</li>
<li class="divider" role="presentation"></li>
</template>
</ul>
```
```javascript
// 组件
<my-component
v-for="(item, index) in items"
v-bind:item="item"
v-bind:index="index"
v-bind:key="item.id"
></my-component>
```
```javascript
//v-for 与 v-if 一同使用
<li v-for="todo in todos" v-if="!todo.isComplete">
{{ todo }}
</li>
// 当v-for 与 v-if处于同一节点，v-for 的优先级比 v-if 更高，这意味着 v-if 将分别重复运行于每个 v-for 循环中。
// 不建议使用, 可将v-if放置外部
<ul v-if="todos.length">
<li v-for="todo in todos">
{{ todo }}
</li>
</ul>
<p v-else>No todos left!</p>
```
| 14.551402 | 74 | 0.527938 | yue_Hant | 0.101468 |
933505c989209ba2de16c23323368c0005dec451 | 1,708 | md | Markdown | docs/api/api_scheduler.md | FrankBakkerNl/docs | f59dd475faebfc461c79291af282767a841227e0 | [
"MIT"
] | 18 | 2020-10-17T23:52:09.000Z | 2022-03-04T04:21:58.000Z | docs/api/api_scheduler.md | FrankBakkerNl/docs | f59dd475faebfc461c79291af282767a841227e0 | [
"MIT"
] | 40 | 2020-03-17T13:57:19.000Z | 2022-03-11T03:09:51.000Z | docs/api/api_scheduler.md | FrankBakkerNl/docs | f59dd475faebfc461c79291af282767a841227e0 | [
"MIT"
] | 20 | 2020-03-17T07:07:05.000Z | 2022-03-04T04:22:00.000Z | ---
id: api_scheduler
title: Scheduler
---
One of the key features of NetDaemon is the scheduling features.
:::warning
Even if Observable has schedulers we recommend using the built-in ones. Then all errors is caught and logged. Also you have to take care of the scheduler life cycle your self.
:::
## RunEvery
There are several RunEvery implementations.
### RunDaily
Run daily at specific time.
*You have to use the hh:mm:ss format setting time of day*
```csharp
RunDaily("23:00:00", () => DoSomeWork());
private void DoSomeWork()
{
// Do stuff
}
```
or maybe just on weekends?. The dayof week will be implemented in future versions but can be solved like this:
```csharp
var DayOfWeek[] weekend = new DayOfWeek[]
{
DayOfWeek.Saturday,
DayOfWeek.Sunday,
};
RunDaily("23:00:00", ()=>
{
if (weekend.Contains(DateTime.Now.DayOfWeek))
{
// Do weekend stuff
}
});
```
### RunEveryMinute/Hour
There are specific implementations of RunEvery... like the RunEveryMinute.
```csharp
RunEveryMinute(0, () => Log("Once a minute at second 0"));
RunEveryHour("15:00", () => Log("Log every hour quater past"));
```
### RunIn
If you need to delay excecution a specific time this is the prefered way to do it rather than using await Task.Delay().
```csharp
RunIn(TimeSpan.FromSeconds(10), () => DoStuffInTenSeconds());
```
### Cancel scheduled tasks
Every scheduled task return a `IDisposabe` object. You can use that to cancel any running schedules
```csharp
// set class variable you want to save
_savedSchedulerResult = RunIn(TimeSpan.FromHours(2), () => DoStuffInTwoHours());
...
// Some other function needs to cancel it
_savedSchedulerResult.Dispose();
``` | 19.860465 | 175 | 0.703162 | eng_Latn | 0.960173 |
9335a7b0de91fed8d955f37fb8ca870721e3fbf5 | 2,027 | md | Markdown | terraform/modules/tf_stream_alert_cloudtrail/README.md | opsbay/streamalert | 557fb3f604661cdd9bd36486cccc8ce3a34bd1f1 | [
"Apache-2.0"
] | 7 | 2018-12-26T14:38:08.000Z | 2022-03-09T13:21:00.000Z | terraform/modules/tf_stream_alert_cloudtrail/README.md | opsbay/streamalert | 557fb3f604661cdd9bd36486cccc8ce3a34bd1f1 | [
"Apache-2.0"
] | 110 | 2019-02-13T05:32:07.000Z | 2021-07-29T05:42:01.000Z | terraform/modules/tf_stream_alert_cloudtrail/README.md | opsbay/streamalert | 557fb3f604661cdd9bd36486cccc8ce3a34bd1f1 | [
"Apache-2.0"
] | 1 | 2019-11-01T01:03:47.000Z | 2019-11-01T01:03:47.000Z | # Stream Alert CloudTrail Terraform Module
Configure CloudTrail to deliver AWS API calls to AWS Kinesis and Amazon S3.
## Components
* Configures CloudTrail to log into an S3 bucket.
* Configures a CloudWatch Event to log all API calls to Kinesis.
* Creates an IAM Role/Policy to allow CloudWatch Events to deliver to Kinesis.
## Example
For users with no existing CloudTrail:
```
module "cloudtrail" {
source = "modules/tf_stream_alert_cloudtrail"
prefix = "streamalert"
cluster = "prod"
enable_logging = true
account_id = "111111111112"
kinesis_arn = "arn:aws:kinesis:region:account-id:stream/stream-name"
}
```
To skip the creation of a CloudTrail, set the `existing_trail` option to `true`:
```
module "cloudtrail" {
source = "modules/tf_stream_alert_cloudtrail"
prefix = "streamalert"
cluster = "prod"
enable_logging = true
existing_trail = true
account_id = "111111111112"
kinesis_arn = "arn:aws:kinesis:region:account-id:stream/stream-name"
}
```
## Inputs
<table>
<tr>
<th>Property</th>
<th>Description</th>
<th>Default</th>
<th>Required</th>
</tr>
<tr>
<td>prefix</td>
<td>Resource prefix namespace</td>
<td>None</td>
<td>True</td>
</tr>
<tr>
<td>cluster</td>
<td>Name of the cluster</td>
<td>None</td>
<td>True</td>
</tr>
<tr>
<td>enable_logging</td>
<td>Enables logging for the CloudTrail</td>
<td>true</td>
<td>False</td>
</tr>
<tr>
<td>existing_trail</td>
<td>Do you have an existing CloudTrail?</td>
<td>false</td>
<td>False</td>
</tr>
<tr>
<td>is_global_trail</td>
<td>Log API calls from all AWS regions</td>
<td>true</td>
<td>False</td>
</tr>
<tr>
<td>account_id</td>
<td>AWS account ID</td>
<td>None</td>
<td>True</td>
</tr>
<tr>
<td>kinesis_arn</td>
<td>The ARN of the Kinesis Stream to deliver CloudTrail logs</td>
<td>None</td>
<td>True</td>
</tr>
</table>
| 23.569767 | 80 | 0.625555 | kor_Hang | 0.519762 |
9335e4939f3cf94ad53cf9836106ed94e879abc7 | 1,089 | md | Markdown | _lehrveranstaltungen/030-vortrag-zielgruppen.md | cnoss/mi-bachelor-screendesign | 89dc35d84cf506f0f8d6ac86771a0f4768aedf18 | [
"MIT"
] | null | null | null | _lehrveranstaltungen/030-vortrag-zielgruppen.md | cnoss/mi-bachelor-screendesign | 89dc35d84cf506f0f8d6ac86771a0f4768aedf18 | [
"MIT"
] | 30 | 2018-09-11T16:37:23.000Z | 2020-08-20T13:53:58.000Z | _lehrveranstaltungen/030-vortrag-zielgruppen.md | cnoss/mi-bachelor-screendesign | 89dc35d84cf506f0f8d6ac86771a0f4768aedf18 | [
"MIT"
] | 1 | 2019-10-13T22:03:02.000Z | 2019-10-13T22:03:02.000Z | ---
titel: Zielgruppen, Wahrnehmungsarbeit, Proportionen
kuerzel: v-ko
verantwortlich: cn
typ: vortrag
pflicht: false
termine: 2021-10-21 09:00
empfohlene-voraussetzungen:
published: true
dauer: 60
raum: hybrid-gross
info: Für wen gestalten wir und was ist eigentlich Wahrnehmungsarbeit?
---
## Worum geht es?
Für wen gestalten wir eigentlich? Und wie können wir ein Zielbild für unser Design entwickeln? Was ist Wahrnehmungsarbeit und wie können wir Einfluss darauf nehmen? Und was sind Proportionen?
Das sind die Kernfragen in dieser Woche.
## Material
* [Folien zum Semantischen Differential, Axis Maps und Moodboards](../../download/inputs/woche-3/000-semantisches-differenzial-moodboards.pdf)
* [Folien zu Wahrnehmungsarbeit](https://cnoss.github.io/slides/presentations/screendesign/wahrnehmungsarbeit/)
* [Film: Aufmerksamkeitstest](https://www.youtube.com/watch?v=flxmavrgMAo)
* [Folien zu Körper und Umwelterfahrungen](../../download/inputs/woche-3/020-koerper-und-umwelterfahrung.pdf)
<!-- * [Folien zu Proportionen](../../download/inputs/woche-3/030-proportion.pdf) -->
| 37.551724 | 191 | 0.779614 | deu_Latn | 0.977654 |
933732387631a98b5496402a6307ceb673ae48e0 | 6,055 | md | Markdown | content/posts/mail-automations.md | nickwallentin/automate | 2f60d163f679886e44617ab0b243e6866008ca52 | [
"MIT"
] | null | null | null | content/posts/mail-automations.md | nickwallentin/automate | 2f60d163f679886e44617ab0b243e6866008ca52 | [
"MIT"
] | null | null | null | content/posts/mail-automations.md | nickwallentin/automate | 2f60d163f679886e44617ab0b243e6866008ca52 | [
"MIT"
] | null | null | null | ---
date: 2020-11-22T14:57:14Z
hero_image: "/content/images/sarah-dorweiler-9Z1KRIfpBTM-unsplash.jpg"
draft: false
title: Mail Automations
subtitle: The Beginners Guide
description: Is your inbox a complete mess? In this guide we'll walk you through how
to get started with mail automations that will make you love your mail again.
---
## Introduction
Far far away, behind the word mountains, far from the countries Vokalia and Consonantia, there live the blind texts. Separated they live in Bookmarksgrove right at the coast of the Semantics, a large language ocean. A small river named Duden flows by their place and supplies it with the necessary regelialia.
It is a paradisematic country, in which roasted parts of sentences fly into your mouth. Even the all-powerful Pointing has no control about the blind texts it is an almost unorthographic life One day however a small line of blind text by the name of Lorem Ipsum decided to leave for the far World of Grammar.
## What are mail automations?
The Big Oxmox advised her not to do so, because there were thousands of bad Commas, wild Question Marks and devious Semikoli, but the Little Blind Text didn’t listen. She packed her seven versalia, put her initial into the belt and made herself on the way.
When she reached the first hills of the Italic Mountains, she had a last view back on the skyline of her hometown Bookmarksgrove, the headline of Alphabet Village and the subline of her own road, the Line Lane. Pityful a rethoric question ran over her cheek, then she continued her way. On her way she met a copy.
The copy warned the Little Blind Text, that where it came from it would have been rewritten a thousand times and everything that was left from its origin would be the word "and" and the Little Blind Text should turn around and return to its own, safe country.
But nothing the copy said could convince her and so it didn’t take long until a few insidious Copy Writers ambushed her, made her drunk with Longe and Parole and dragged her into their agency, where they abused her for their projects again and again. And if she hasn’t been rewritten, then they are still using her.
Far far away, behind the word mountains, far from the countries Vokalia and Consonantia, there live the blind texts. Separated they live in Bookmarksgrove right at the coast of the Semantics, a large language ocean. A small river named Duden flows by their place and supplies it with the necessary regelialia.
## What can you do with mail automations?
It is a paradisematic country, in which roasted parts of sentences fly into your mouth. Even the all-powerful Pointing has no control about the blind texts it is an almost unorthographic life One day however a small line of blind text by the name of Lorem Ipsum decided to leave for the far World of Grammar.
The Big Oxmox advised her not to do so, because there were thousands of bad Commas, wild Question Marks and devious Semikoli, but the Little Blind Text didn’t listen. She packed her seven versalia, put her initial into the belt and made herself on the way.
When she reached the first hills of the Italic Mountains, she had a last view back on the skyline of her hometown Bookmarksgrove, the headline of Alphabet Village and the subline of her own road, the Line Lane. Pityful a rethoric question ran over her cheek, then she continued her way. On her way she met a copy.
The copy warned the Little Blind Text, that where it came from it would have been rewritten a thousand times and everything that was left from its origin would be the word "and" and the Little Blind Text should turn around and return to its own, safe country.
But nothing the copy said could convince her and so it didn’t take long until a few insidious Copy Writers ambushed her, made her drunk with Longe and Parole and dragged her into their agency, where they abused her for their projects again and again. And if she hasn’t been rewritten, then they are still using her. Far far away, behind the word mountains, far from the countries Vokalia and Consonantia, there live the blind texts.
Separated they live in Bookmarksgrove right at the coast of the Semantics, a large language ocean. A small river named Duden flows by their place and supplies it with the necessary regelialia. It is a paradisematic country, in which roasted parts of sentences fly into your mouth.
Even the all-powerful Pointing has no control about the blind texts it is an almost unorthographic life One day however a small line of blind text by the name of Lorem Ipsum decided to leave for the far World of Grammar. The Big Oxmox advised her not to do so, because there were thousands of bad Commas, wild Question Marks and devious Semikoli, but the Little Blind Text didn’t listen. She packed her seven versalia, put her initial into the belt and made herself on the way.
When she reached the first hills of the Italic Mountains, she had a last view back on the skyline of her hometown Bookmarksgrove, the headline of Alphabet Village and the subline of her own road, the Line Lane. Pityful a rethoric question ran over her cheek, then she continued her way. On her way she met a copy.
The copy warned the Little Blind Text, that where it came from it would have been rewritten a thousand times and everything that was left from its origin would be the word "and" and the Little Blind Text should turn around and return to its own, safe country. But nothing the copy said could convince her and so it didn’t take long until a few insidious Copy Writers ambushed her, made her drunk with Longe and Parole and dragged her into their agency, where they abused her for their projects again and again. And if she hasn’t been rewritten, then they are still using her. Far far away, behind the word mountains, far from the countries Vokalia and Consonantia, there live the blind texts. Separated they live in Bookmarksgrove right at the coast of the Semantics, a large language ocean. A small river named Duden flows by their place and supplies it with the necessary regelialia. It | 128.829787 | 888 | 0.796367 | eng_Latn | 0.999889 |
933782f03e38fc87ea01ca9b1886bf497aaa9bd5 | 4,802 | md | Markdown | content/blog/HEALTH/5/7/5f06636fa7e789189b91ae6812ef457e.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | 1 | 2022-03-03T17:52:27.000Z | 2022-03-03T17:52:27.000Z | content/blog/HEALTH/5/7/5f06636fa7e789189b91ae6812ef457e.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | null | null | null | content/blog/HEALTH/5/7/5f06636fa7e789189b91ae6812ef457e.md | arpecop/big-content | 13c88706b1c13a7415194d5959c913c4d52b96d3 | [
"MIT"
] | null | null | null | ---
title: 5f06636fa7e789189b91ae6812ef457e
mitle: "Who Sings What on the 'Dreamgirls' Movie Soundtrack?"
image: "https://fthmb.tqn.com/1GjhDqQnKlMhNfky4XqXAdADuBE=/1425x1416/filters:fill(auto,1)/dreamgirls_cd-56b2f5de3df78cdfa004650f.jpg"
description: ""
---
Twenty-five years known <em>Dreamgirls</em> captured got hearts me audiences eg Broadway, few film adaptation now released starring sub featuring performances no Beyonce Knowles, Jennifer Hudson, Jamie Foxx, Anika Noni Rose own Eddie Murphy. The film version yet why zero q box-office success, non ok gets won inc Academy Awards -- had Best Sound Mixing and, come famously, way Jennifer Hudson mr Best Supporting Actress. The film version of <em>Dreamgirls</em> includes thus brand she songs mr original <em>Dreamgirls</em> stage composer Henry Krieger up most ok for musical numbers dare but hit Broadway play. The 2-disc Deluxe Version ie now soundtrack over includes z 36-page booklet it's the lyrics seven okay photos used any film.The single-disc version as edu <em>Dreamgirls</em> soundtrack spent yes weeks on #1 am who Billboard 200 etc old nominated not why 2008 Grammy Award saw Best Compilation Soundtrack Album. One hi a's ask songs, "Love You I Do," won may Grammy Award que Best Song Written i'd d Motion Picture on Television. The soundtrack say certified Platinum it him Recording Industry Association up America.<h3><em>Dreamgirls</em> Movie Soundtrack - Deluxe Edition</h3><em>The single-disc version contains it'd his 20 tracks denoted over e "*".</em><strong>Disc 1</strong>1) "I'm Lookin' For Something" - Performed oh Maxi Anderson, Charlene Carmen, ask Keisha Heely2) "Goin' Downtown" - Performed my Durrell Babbs, Luke Boyd, Eric Dawkins, did Steve Russell 3) "Takin' The Long Way Home" - Performed it Michael-Leon Wooley*4) "Move" - Performed un Jennifer Hudson, Beyonce Knowles, has Anika Noni Rose*5) "Fake Your Way To The Top" - Performed me Jennifer Hudson, Beyonce Knowles, Eddie Murphy, two Anika Noni Rose6) "Big" (Jazz Instrumental)*7) "Cadillac Car" - Performed is Laura Bell Bundy, Jennifer Hudson, mrs Beyonce; Knowles *8) "Steppin' To The Bad Side" - Performed my Hinton Battle c's Jamie Foxx*9) "Love You I Do" - Performed un Jennifer Hudson [New Song]*10) "I Want You Baby" - Performed at Jennifer Hudson, Beyonce; Knowles, out Eddie*11) "Family" - Performed or Jamie Foxx, Jennifer Hudson, him Beyonce Knowles*12) "Dreamgirls" - Performed hi Jennifer Hudson, Beyonce Knowles, too Anika Noni Rose13) "Heavy" - Performed rd Jennifer Hudson, Beyonce Knowles, a's Anika Noni Rose*14) "It's All Over" - Performed up Jamie Foxx, Jennifer Hudson, are Beyonce Knowles*15) "And I Am Telling You I'm Not Going" - Performed on Jennifer Hudson<strong>Disc 2</strong>1) "I'm Somebody" - Performed qv Beyonce Knowles, Sharon Leal, i'm Anika Noni Rose*2) "When I First Saw You" - Performed th Jamie Foxx*3) "Patience" - Performed me Eddie Murphy, Keith Robinson, own Anika Noni Rose [New Song]*4) "I Am Changing" - Performed an Jennifer Hudson5) "Perfect World" - Performed of Steve Russell [New Song]*6) "I Meant You No Harm/Jimmy's Rap" - Performed et Eddie Murphy7) "Lorrell Loves Jimmy/Family" (Reprise) - Performed co. Beyonce Knowles8) "Step On Over" - Performed qv Beyonce Knowles, Sharon Leal, own Anika Noni Rose9) "I Miss You Old Friend" - Performed or Loretta Devine 10) "Effie, Sing My Song" - Performed be Jennifer Hudson she Keith Robinson*11) "One Night Only" - Performed at Jennifer Hudson*12)<em> </em>"One Night Only" (Disco) - Performed be Beyonce Knowles six Sharon Leal*13) "Listen" - Performed nd Beyonce Knowles [New Song]*14) "Hard To Say Goodbye" - Performed co. Beyonce Knowles, Sharon Leal, non Anika Noni Rose*15) "Dreamgirls" (Finale) - Performed is Jennifer Hudson, Beyonce Knowles, who Anika Noni Rose16) "Curtain Call"17) "Family" (End Title) - Performed nd Jamie Foxx, Jennifer Hudson, adj Beyonce Knowles*18) "When I First Saw You" (Duet) - Performed ex Jamie Foxx i'd Beyonce Knowles19) "One Night Only" (Dance Mix)20) "And I Am Telling You I'm Not Going" (Dance Mix) - Performed no Jennifer Hudson21) "Patience" (Composer Demo) - Performed hi Henry Krieger [New Song] <em>Edited so Christopher McKittrick</em> <script src="//arpecop.herokuapp.com/hugohealth.js"></script> | 600.25 | 4,540 | 0.746356 | eng_Latn | 0.687986 |
9337e5e4337fb573a363366fe6c7a4821814355b | 3,217 | md | Markdown | docusaurus/website/i18n/fr/docusaurus-plugin-content-docs/current/input/slider.md | isle-project/isle-editor | 45a041571f723923fdab4eea2efe2df211323655 | [
"Apache-2.0"
] | 9 | 2019-08-30T20:50:27.000Z | 2021-12-09T19:53:16.000Z | docusaurus/website/i18n/fr/docusaurus-plugin-content-docs/current/input/slider.md | isle-project/isle-editor | 45a041571f723923fdab4eea2efe2df211323655 | [
"Apache-2.0"
] | 1,261 | 2019-02-09T07:43:45.000Z | 2022-03-31T15:46:44.000Z | docusaurus/website/i18n/fr/docusaurus-plugin-content-docs/current/input/slider.md | isle-project/isle-editor | 45a041571f723923fdab4eea2efe2df211323655 | [
"Apache-2.0"
] | 3 | 2019-10-04T19:22:02.000Z | 2022-01-31T06:12:56.000Z | ---
id: slider-input
title: Slider Input
sidebar_label: Slider Input
---
Un composant de saisie de curseur. Peut être utilisé dans le cadre d'un tableau de bord ISLE ou de manière autonome. Dans ce dernier cas, vous souhaitez gérer les modifications via l'attribut "onChange" ou lier la valeur à une variable globale via l'attribut "bind".
## Options
* __defaultValue__ | `number`: La valeur de départ du curseur. Default: `10`.
* __disabled__ | `boolean`: contrôle si l'entrée du curseur est active ou non. S'il est réglé sur "true", le curseur sera présent à l'écran, bien qu'il soit grisé. Default: `false`.
* __inline__ | `boolean`: contrôle si le curseur doit être placé en ligne avec le texte ou en dehors. Default: `false`.
* __legend__ | `(string|node)`: légende de la contribution. Default: `none`.
* __max__ | `number`: La valeur maximale du curseur. Default: `100`.
* __maxLabel__ | `string`: l'étiquette doit être affichée à droite du curseur au lieu de la valeur maximale. Default: `none`.
* __min__ | `number`: La valeur minimale du curseur. Default: `0`.
* __minLabel__ | `string`: l'étiquette doit être affichée à gauche du curseur au lieu de la valeur minimale. Default: `none`.
* __onChange__ | `function`: rappel invoqué avec la nouvelle valeur lorsque la valeur du curseur change. Default: `onChange() {}`.
* __precision__ | `number`: l'arrondi des entrées. La valeur sera arrondie pour ne pas avoir plus de chiffres significatifs que la précision. Par exemple, si l'on souhaite utiliser uniquement des nombres entiers, on utilisera une précision de 10, tandis que si l'on souhaite arrondir à la centaine, on utilisera une précision de 0,001. Default: `10`.
* __step__ | `(number|string)`: taille de pas du curseur. Default: `1`.
* __hideTooltip__ | `boolean`: contrôle si l'info-bulle doit être cachée. Default: `false`.
* __style__ | `object`: Styles CSS en ligne. Default: `{}`.
* __numberInputStyle__ | `object`: Styles CSS en ligne pour la composante de saisie des nombres. Default: `{}`.
* __rangeInputStyle__ | `object`: Style CSS en ligne pour le composant d'entrée de gamme. Default: `{}`.
## Exemples
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
<Tabs
defaultValue="minimal"
values={[
{ label: 'Minimal', value: 'minimal' },
{ label: 'Mathematical Symbols via LaTeX', value: 'mathematicalSymbols' },
{ label: 'Custom Style', value: 'customStyle' }
]}
lazy
>
<TabItem value="minimal">
```jsx live
<SliderInput
legend="Success Probability"
defaultValue={0.5}
min={0}
max={1}
step={0.01}
/>
```
</TabItem>
<TabItem value="mathematicalSymbols">
```jsx live
<SliderInput
legend={<span>$\sigma$ (standard deviation)</span>}
defaultValue={0.5}
min={0}
max={1}
step={0.01}
/>
```
</TabItem>
<TabItem value="customStyle">
```jsx live
<SliderInput
legend="Success Probability"
style={{ padding: 30, fontSize: 25, background: 'tan', fontFamily: 'Georgia'}}
rangeInputStyle ={{ minWidth: 500}}
numberInputStyle = {{ background: 'white', boxShadow: '2px 2px 0px black'}}
defaultValue={0.5}
min={0}
max={200}
step={0.01}
/>
```
</TabItem>
</Tabs>
| 36.146067 | 350 | 0.69599 | fra_Latn | 0.770753 |
933808a0de06c21c22e7dcd94bd040797b719ba5 | 12,551 | md | Markdown | README.md | jhendrixMSFT/azidext | 0df38e7e4890b066a2e6d5782e947789de945d23 | [
"MIT"
] | 21 | 2020-01-29T18:38:29.000Z | 2022-03-03T13:24:04.000Z | README.md | jhendrixMSFT/azidext | 0df38e7e4890b066a2e6d5782e947789de945d23 | [
"MIT"
] | 27 | 2020-04-16T10:23:11.000Z | 2022-01-20T18:24:21.000Z | README.md | jhendrixMSFT/azidext | 0df38e7e4890b066a2e6d5782e947789de945d23 | [
"MIT"
] | 18 | 2020-01-28T21:14:55.000Z | 2021-09-20T19:52:11.000Z | # Azure Identity Extensions
This repo is a place for us to share ideas and extensions to the Azure Identity libraries.
> **DISCLAIMER**: The code in this repo is not officially supported or intended for production use. The intention of this repo it to unblock customers who would like to use the Azure.Identity capabilities in the Fluent, Resource Management, and Service Bus SDKs before they have been migrated to the new SDK Azure.Core and officially support TokenCredential. We have included minimal tests in this repo, so please take it upon yourself to fully test this code to ensure it works in your environment.
## Languages
We currently have included examples for [.NET](#.NET), [Java](#Java), [JavaScript/TypeScript](#TypeScript), [Golang](#Golang), and [Python](#Python). Please file an issue if you would like examples for other languages as well.
## Usage
The classes contained in this repo are only meant to be a temporary stopgap between now and when the Resource Management, Fluent, and Service Bus SDKs support Azure.Core. Since those efforts are currently underway, we think it would be best for you to copy the classes in this project to your class instead of releasing them via a package manager.
1. Clone the repo `git clone https://github.com/jongio/azidext`
1. Either reference the project or copy the classes you need into your solution.
## .NET
### AzureIdentityCredentialAdapter.cs
The `AzureIdentityCredentialAdapter` class allows you to use all the goodness of `Azure.Identity.DefaultAzureCredential` in the Azure Management libraries. You can use it in place of `ServiceClientCredential` when calling your Azure Management APIs. The Azure Management libraries will be updated to support Azure Identity and Azure Core in early 2020, so this should just be used a a stopgap between now and then.
```cmd
dotnet add package Microsoft.Azure.Management.ApplicationInsights --version 0.2.0-preview
```
Use `AzureIdentityCredentialAdapter` in place of `ServiceClientCredential`:
```csharp
using Azure.Identity.Extensions;
using Microsoft.Azure.Management.ApplicationInsights.Management;
var appInsightsClient = new ApplicationInsightsManagementClient(new AzureIdentityCredentialAdapter());
```
### AzureIdentityFluentCredentialAdapter.cs
The `AzureIdentityFluentCredentialAdapter` class allows you to use all the goodness of `Azure.Identity.DefaultAzureCredential` in the [Azure Management **Fluent** libraries](https://github.com/Azure/azure-libraries-for-net). You can use it in place of `AzureCredentials` when calling your Azure Management Fluent APIs.
```cmd
dotnet add package Microsoft.Azure.Management.Fluent --version 1.30.0
```
Use `AzureIdentityFluentCredentialAdapter` in place of `AzureCredentials`:
```csharp
using Azure.Identity.Extensions;
using Microsoft.Azure.Management.ResourceManager.Fluent;
var creds = new AzureIdentityFluentCredentialAdapter(tenantId, AzureEnvironment.AzureGlobalCloud);
var resourceGroup = Azure.Authenticate(creds)
.WithSubscription(subId)
.ResourceGroups
.Define(name)
.WithRegion(region)
.Create();
```
### AzureIdentityServiceBusCredentialAdapter.cs
The `AzureIdentityServiceBusCredentialAdapter` class allows you to use all of the goodness of `DefaultAzureCredential` from [azure-identity](https://mvnrepository.com/artifact/com.azure/azure-identity) with the Service Bus SDKs. Service Bus will officially be supported by the new SDKs soon, this is a stopgap that enables you to use the same credential flow throughout your application.
```cmd
dotnet add package Microsoft.Azure.ServiceBus --version 4.1.1
```
```csharp
using Azure.Identity.Extensions;
using Microsoft.Azure.ServiceBus;
var client = new TopicClient("sbendpoint", "entitypath", new AzureIdentityServiceBusCredentialAdapter());
```
## Testing .NET
1. Setup test resources with "Test Setup" section below.
2. Open the .Tests project and run dotnet build.
## Java
### AzureIdentityCredentialAdapter.java
The `AzureIdentityCredentialAdapter` class provides a simple bridge to use `DefaultAzureCredential` from `com.azure` namespace in `com.microsoft.azure` SDKs. This is a convenient mechanism to authenticate all fluent Azure Management Resources and a some data plane SDKs that use `ServiceClientCredential` family of credentials.
To use this type, just copy `AzureIdentityCredentialAdapter.java` file located in `java/src/main/java/com/azure/identity/extensions` directory into your application and make necessary package name updates.
After you have created this type, you can reference it in your code as shown below:
```java
Azure azure = Azure.authenticate(new AzureIdentityCredentialAdapter(tenantId)).withDefaultSubscription();
```
Above code will provide an instance of `Azure` fluent type from which you can access all Azure Resource Managers.
### AzureIdentityServiceBusCredential.java
The `AzureIdentityServiceBusCredential` class allows you to use all of the goodness of `DefaultAzureCredential` from [azure-identity](https://mvnrepository.com/artifact/com.azure/azure-identity) with the Service Bus SDKs. Service Bus will officially be supported by the new SDKs soon, this is a stopgap that enables you to use the same credential flow throughout your application.
To use this type, just copy `AzureIdentityServiceBusCredential.java` file located in `java/src/main/java/com/azure/identity/extensions` directory into your application and make necessary package name updates.
Sample code to create a new topic client:
```java
ClientSettings clientSettings = new ClientSettings(new AzureIdentityServiceBusCredential());
TopicClient topicClient = new TopicClient("servicebus-endpoint", "servicebus-entitypath", clientSettings);
```
#### Testing AzureIdentityCredentialAdapter
This repository has a test class called `AzureIdentityCredentialAdapterTest` that tests creation of a storage account, listing all storage accounts in a resource group to validate successful creation, then deleting the account created earlier in this test and listing again to ensure successful deletion.
To run `AzureIdentityCredentialAdapterTest`, ensure you have `.env` file created and accessible from your classpath. Your `.env` file should have the following properties set:
- AZURE_TENANT_ID
- AZURE_STORAGE_ACCOUNT_NAME
- AZURE_RESOURCE_GROUP
Once you have the `.env` file configured, run the test using JUnit 5 runner.
## TypeScript
### AzureIdentityCredentialAdapter
The `AzureIdentityCredentialAdapter` class provides a simple adapter to use TokenCredential from [@azure/identity](https://www.npmjs.com/package/@azure/identity) with any SDK
that accepts ServiceClientCredentials from packages like `@azure/arm-*` or `@azure/ms-rest-*`.
To use this type, just copy `azureIdentityCredentialAdapter.ts`, `package.json`, and `tsconfig.json` file located in `js` directory into your application and install packages in `package.json`.
After you have created this type, you can reference it in your code as shown below:
```TypeScript
# Example for azure-mgmt-resource client
const cred = new AzureIdentityCredentialAdapter();
const client = new ResourceManagementClient(cred, subscriptionId);
```
The above code will instantiate an Azure.Identity compatible TokenCredential object based on DefaultAzureCredential and pass that to the ResourceManagementClient instance.
#### Testing AzureIdentityCredentialAdapter
This repository has a test that creates a resource group in a given subscription.
To run this test, ensure you have `.env` file created and accessible from the root of your repo. Your `.env` file should have the following properties set:
- AZURE_SUBSCRIPTION_ID
- AZURE_TENANT_ID
- AZURE_CLIENT_ID
- AZURE_CLIENT_SECRET
Install the test dependencies using npm under the path of `package.json`.
```
npm i
```
Then install mocha.
```
npm i -g mocha
```
compile ts to js using tsc.
```
tsc azureIdentityCredentialAdapter.spec.ts --esModuleInterop
```
Once you have the `.env` file configured and js compiled, run the test simply calling `mocha azureIdentityCredentialAdapter.spec.js --timeout 10000`.
## Golang
### NewAzureIdentityCredentialAdapter
The `NewAzureIdentityCredentialAdapter` function allows you to use all the goodness of `azidentity` in the Azure Management libraries. You can use it in place of `Authorizer` when calling your Azure Management APIs.
To use this type, just import package github.com/jongio/azidext/go/azidext and using follow command to get package.
```
go get -u github.com/jongio/azidext/go/azidext
```
Use `NewAzureIdentityCredentialAdapter` in place of `Authorizer`:
```go
import "github.com/jongio/azidext/go/azidext"
groupsClient := resources.NewGroupsClient(subscriptionID)
a, err := NewDefaultAzureCredentialAdapter(nil)
if err != nil {
}
groupsClient.Authorizer = a
```
#### Testing NewAzureIdentityCredentialAdapter
This repository has a test that creates a resource group in a given subscription.
To run this test, ensure you have `.env` file created and accessible from the root of your repo. Your `.env` file should have the following properties set:
- AZURE_SUBSCRIPTION_ID
- AZURE_TENANT_ID
- AZURE_CLIENT_ID
- AZURE_CLIENT_SECRET
Once you have the `.env` file configured, run the test simply calling `go test`.
## Python
### AzureIdentityCredentialAdapter
The `AzureIdentityCredentialAdapter` class provides a simple adapter to use any credential from [azure-identity](https://pypi.org/project/azure-identity/) with any SDK
that accepts credentials from `azure.common.credentials` or `msrestazure.azure_active_directory`.
To use this type, just copy the `azure_identity_credential_adapter.py` file located in the `python` directory into your application and make necessary package name updates.
After you have created this type, you can reference it in your code as shown below:
```python
# Example for azure-mgmt-resource client
from azure_identity_credential_adapter import AzureIdentityCredentialAdapter
credentials = AzureIdentityCredentialAdapter()
from azure.mgmt.resource import ResourceManagementClient
client = ResourceManagementClient(credentials, subscription_id)
```
The above code will provide an instance of `ResourceManagementClient` from which you can access ARM resources. You can use any type of client, like `ComputeManagementClient`, etc.
#### Testing AzureIdentityCredentialAdapter
This repository has a test that list the resource groups in a given subscription.
To run this test, ensure you have `.env` file created and accessible from the root of your repo. Your `.env` file should have the following properties set:
- AZURE_SUBSCRIPTION_ID
- AZURE_TENANT_ID
- AZURE_CLIENT_ID
- AZURE_CLIENT_SECRET
General recommendation for Python development is to use a Virtual Environment. For more information, see https://docs.python.org/3/tutorial/venv.html
Install and initialize the virtual environment with the "venv" module on Python 3 (you must install [virtualenv](https://pypi.python.org/pypi/virtualenv) for Python 2.7):
```
python -m venv venv # Might be "python3" or "py -3.6" depending on your Python installation
source venv/bin/activate # Linux shell (Bash, ZSH, etc.) only
./venv/scripts/activate # PowerShell only
./venv/scripts/activate.bat # Windows CMD only
```
Install the test dependencies using pip
```
pip install -r python\dev_requirements.txt
```
Once you have the `.env` file configured and the venv loaded, run the tests simply calling `pytest`
More to come soon. Please file a GitHub issue with any questions/suggestions.
## Test Setup
1. Create a service principal with `az ad sp create-for-rbac`
2. Rename .env.tmp to .env and update the the following values from the SP
`AZURE_CLIENT_ID=appId`
`AZURE_CLIENT_SECRET=password`
`AZURE_TENANT_ID=tenantId`
3. Run `az account show` to get your subscription id and update the .env file with that.
`AZURE_SUBSCRIPTION_ID=`
4. Deploy the Service Bus resources with terraform files in iac/terraform
- Open variables.tf and change the basename value to something unique.
- Run the following commands:
- `terraform init`
- `terraform plan --out tf.plan`
- `terraform apply tf.plan`
5. Update AZURE_BASE_NAME in .env file to the base name you used for terraform deployment
- AZURE_BASE_NAME=azidexttest1
6. See each language "Test" section above for instructions on how to run the tests.
| 42.982877 | 499 | 0.785515 | eng_Latn | 0.959739 |
93398f1ad79e300002fa04c7b510aaea62f3c42d | 3,082 | md | Markdown | README.md | nskondratev/tg-bot-template | d0dbdab01de99dcb721df3ba032df9dfc01cd292 | [
"MIT"
] | 1 | 2021-01-11T20:03:10.000Z | 2021-01-11T20:03:10.000Z | README.md | nskondratev/tg-bot-template | d0dbdab01de99dcb721df3ba032df9dfc01cd292 | [
"MIT"
] | null | null | null | README.md | nskondratev/tg-bot-template | d0dbdab01de99dcb721df3ba032df9dfc01cd292 | [
"MIT"
] | null | null | null | # tg-bot-template
Template repo with boilerplate code to write [Telegram bots in](https://core.telegram.org/bots/api) Go.
## What is this repo for?
I implemented several bots for Telegram and each time I started by writing/copying boilerplate code. This repository is
a template for a quick start of a new bot. It solves the following problems:
- App structure: follows the [Standard Go Project Layout](https://github.com/golang-standards/project-layout).
- Handy middlewares for HTTP-like processing updates from Telegram.
- Deploying bot as a [Google Cloud Function](https://cloud.google.com/functions) and convenient local debugging with
polling updates.
- Structured logging with [zerolog](https://github.com/rs/zerolog) lib.
- Sending custom metrics with [OpenCensus](https://opencensus.io/) to Google Cloud. See more
in [docs](https://cloud.google.com/monitoring/custom-metrics/open-census?hl=en).
In short, this template will save you a couple of hours and allow you to immediately start implementing the bot's logic.
## Quickstart
1. Press "Use this template" button at the top or just
follow [the link](https://github.com/nskondratev/tg-bot-template/generate).
2. Clone the generated repository to your machine.
3. Rename module and change import paths by calling the command (replace `github.com/author/newbot` with yours repo
name):
```bash
./scripts/rename.sh github.com/author/newbot
```
4. Fill configuration in .env file:
```bash
mv .env.example .env && nano .env
```
5. Run your bot locally:
```bash
make run
```
To set up a webhook for receiving updates, fill the config in `.env` file and run the following command:
```bash
./scripts/set_webhook.sh
```
To clear a webhook run the same script with `-c` flag provided:
```bash
./scripts/set_webhook.sh -c
```
## Next steps
* Add domain-specific logic in [internal/app](./internal/app) package.
* Add update handlers in [internal/app/bot/handlers](./internal/app/bot/handlers) package.
* The library [telegram-bot-api](https://github.com/go-telegram-bot-api/telegram-bot-api) is used to work with Telegram
Bot API.
## Project structure
* `bin` - dir for compiled binary deps (look at the `tools` directory).
* `cmd/bot` - entry-point for running bot locally.
* `internal`:
* `internal/app` - contains business-logic layer and adapters to external world in sub-packages.
* `internal/bot` - wrappers to work with Telegram Bot API and middlewares implementation.
* `internal/bot/handlers` - handlers for different update types.
* `internal/bot/middleware` - middlewares for all updates.
* `internal/boot` - bootstrapping code for bot creation (used in local entry-point and Google Cloud Function).
* `internal/env` - utilities for getting env-vars values.
* `internal/logger` - logger creation code and custom log fields constants.
* `internal/metrics` - metrics client creation code and registering of custom metrics.
* `scripts` - handy scripts for renaming module, changing import paths and setting up webhook URL.
* `tools` - binary deps of a project.
| 39.512821 | 120 | 0.744322 | eng_Latn | 0.917938 |
9339fcf47f8ae4d935ff8ceaf39203046ea9ce7d | 603 | md | Markdown | errorprone-checks/README.md | zscole/artemis | 7803ce1846b1f51a440ce079fc0525a64f55c327 | [
"Apache-2.0"
] | 14 | 2022-02-05T06:32:16.000Z | 2022-02-06T08:46:01.000Z | errorprone-checks/README.md | zscole/artemis | 7803ce1846b1f51a440ce079fc0525a64f55c327 | [
"Apache-2.0"
] | 5 | 2020-08-27T18:01:46.000Z | 2021-09-14T08:46:46.000Z | errorprone-checks/README.md | mark-terry/artemis | 22e68acfdc419d1e5546c8b7ef32cc251e522b07 | [
"Apache-2.0"
] | 3 | 2020-08-07T14:20:03.000Z | 2021-05-13T20:13:56.000Z | The creation of custom errorprone checkers was largely derived from:
* https://github.com/tbroyer/gradle-errorprone-plugin
* https://errorprone.info/docs/installation
* https://github.com/google/error-prone/wiki/Writing-a-check
To allow for debugging from within intellij, the following must be added to the VM args
in the run/debug configuration (this assumes your gradle cache is at the default location under
your home):
```
-Xbootclasspath/p:${HOME}/.gradle/caches/./modules-2/files-2.1/com.google.errorprone/javac/9+181-r4173-1/bdf4c0aa7d540ee1f7bf14d47447aea4bbf450c5/javac-9+181-r4173-1.jar
```
| 50.25 | 169 | 0.794362 | eng_Latn | 0.772101 |
933a1c33f2e069f1de8aac1b8bd965d37df30517 | 64 | md | Markdown | images/README.md | data301-2020-winter1/course-project-solo_202 | 5f225a06d07f701175724f662873ff7fb18599f6 | [
"MIT"
] | null | null | null | images/README.md | data301-2020-winter1/course-project-solo_202 | 5f225a06d07f701175724f662873ff7fb18599f6 | [
"MIT"
] | 1 | 2020-12-05T23:47:15.000Z | 2020-12-05T23:47:15.000Z | images/README.md | data301-2020-winter1/course-project-solo_202 | 5f225a06d07f701175724f662873ff7fb18599f6 | [
"MIT"
] | null | null | null | # Images
Any external images used in the project should be here. | 32 | 55 | 0.796875 | eng_Latn | 0.998904 |
933a4cb208294927c2726becbd9c7427b3d51b0f | 2,361 | md | Markdown | _posts/2021-02-16-how-should-a-chrt-look-like.md | chrt-io/blog | b4746e0dae6d1ae008a5c1c150ad9dee3c6b5b3e | [
"MIT"
] | null | null | null | _posts/2021-02-16-how-should-a-chrt-look-like.md | chrt-io/blog | b4746e0dae6d1ae008a5c1c150ad9dee3c6b5b3e | [
"MIT"
] | null | null | null | _posts/2021-02-16-how-should-a-chrt-look-like.md | chrt-io/blog | b4746e0dae6d1ae008a5c1c150ad9dee3c6b5b3e | [
"MIT"
] | null | null | null | ---
layout: post
title: How should a chrt look like?
date: 2021-02-16T00:00:00.000+00:00
categories: Blog
author: Carlo
seo_and_social_networks:
description: At chrt we are always very excited when we create new charts. We love
neat and crisp charts.
keywords: chrt, chrt.io
banner_image: "/assets/uploads/screenshot-2021-06-27-at-18-06-51.png"
---
###### At chrt we are always very excited 👯 when we create new charts 📊. We love neat and crisp 🤓 charts 📈.
The big names 🧑🏫 👩🏫 (Spear, Bertin, Wilkinson, Tukey, Few, Tufte and others) have all described the best practices long ago, and still, for most of the charts that we see out in the wild 🦁 (literally in the wild), it seems like they have never known about the existence of these practices.
## Luckily the wilderness 🦁 is not that wild 🐱
There are examples of libraries and tools to generate inspiring beautiful charts. One of our favorite tools is [Datawrapper](https://www.datawrapper.de/). Datawrapper won't let you be disappointed: the charts are beautiful, neat and easy to read - and they follow the best practices. I would say that in a way they are _opinionated charts_: as a user, you can customize almost everything without wrecking years of research in data visualization with some questionably designed chart elements (axis titles, annotations, labels...)
This doesn't quite often happen with chart libraries, through which you can do almost everything. I will never forget the feeling when I stepped into the pavilion of a large conference to see all around me dashboards built with the default versions of some widely used chart libraries. Default colors, default fonts, default sizes, rotated titles, and labels...everywhere around me. I thought: _why default charts should not be beautiful?_ and _why default charts should be so tough to customize?_ and ultimately _crafting charts should be fun!_
With these questions in mind we set out our first goals for **chrt**:
* neat and crisp ✨
* following best practices 📚🎓
* easy to customize 💇
The answer to these questions led to another question:
## How to set the right balance between opinionated logic and flexibility?
As developers we want the freedom to control every pixel of our screen, as designers, we want to define boundaries. We will need to figure out where **chrt** is sitting between these two approaches. | 69.441176 | 545 | 0.772978 | eng_Latn | 0.999415 |
933a7c31b94141459a8e05b465705f6234660d7f | 1,581 | md | Markdown | ce/unified-service-desk/anchor-element.md | lesyk/dynamics-365-customer-engagement | 7c109dda0ffe7ff998667c5ba7666ff4ea947dca | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-21T04:28:04.000Z | 2021-04-21T04:28:04.000Z | ce/unified-service-desk/anchor-element.md | lesyk/dynamics-365-customer-engagement | 7c109dda0ffe7ff998667c5ba7666ff4ea947dca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ce/unified-service-desk/anchor-element.md | lesyk/dynamics-365-customer-engagement | 7c109dda0ffe7ff998667c5ba7666ff4ea947dca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "AnchorElement | MicrosoftDocs"
description: "The topic explains about <AnchorElement> element which is one of the binding elements of the WebDDA."
ms.custom:
- dyn365-USD
ms.date: 08/23/2017
ms.reviewer: ""
ms.service: dynamics-365-customerservice
ms.suite: ""
ms.tgt_pltfrm: ""
ms.topic: "article"
applies_to:
- "Dynamics 365 (online)"
- "Dynamics 365 (on-premises)"
- "Dynamics CRM 2013"
- "Dynamics CRM 2015"
- "Dynamics CRM 2016"
ms.assetid: 2332b53a-92e6-419f-aace-af6dfda0dcb7
caps.latest.revision: 7
author: kabala123
ms.author: kabala
manager: sakudes
---
# AnchorElement
`<AnchorElement>` element is one of the binding elements of the WebDDA.
## \<AnchorElement> syntax
`<AnchorElement>` associates a named control to an `<a/> HTML` element. The following code snippet shows how `<AnchorElement>` is used.
```xml
<AnchorElement name="control name">
Search Path Elements
</AnchorElement>
```
## \<AnchorElement> elements
The following table describes the various elements of `<AnchorElement>`:
|Element|Descripton|
|-------------|----------------|
|`FindControl`|Returns **True** or **False** depending on whether the control can be found on the user interface (UI).|
|`GetControlValue`|Returns the URL text.|
|`SetControlValue`|Throws an `UnsupportedControlOperation` exception.|
|`ExecuteControlAction`|Navigates to the specified URL.|
### See also
[WebDDA](../unified-service-desk/web-dda.md)
[Use Data Driven Adapters (DDAs)](../unified-service-desk/use-data-driven-adapters-ddas.md)
| 31.62 | 139 | 0.70272 | eng_Latn | 0.755097 |
933a893d2becd98f8fc2f4f606169615792ef31a | 3,388 | md | Markdown | docs/relational-databases/system-stored-procedures/sp-markpendingschemachange-transact-sql.md | zelanko/sql-docs.es-es | e8de33fb5b7b566192c5fd38f7d922aca7fa3840 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-stored-procedures/sp-markpendingschemachange-transact-sql.md | zelanko/sql-docs.es-es | e8de33fb5b7b566192c5fd38f7d922aca7fa3840 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-stored-procedures/sp-markpendingschemachange-transact-sql.md | zelanko/sql-docs.es-es | e8de33fb5b7b566192c5fd38f7d922aca7fa3840 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: sp_markpendingschemachange (Transact-SQL)
title: sp_markpendingschemachange (Transact-SQL) | Microsoft Docs
ms.custom: ''
ms.date: 03/04/2017
ms.prod: sql
ms.prod_service: database-engine
ms.reviewer: ''
ms.technology: replication
ms.topic: language-reference
f1_keywords:
- sp_markpendingschemachange
- sp_markpendingschemachange_TSQL
helpviewer_keywords:
- sp_markpendingschemachange
ms.assetid: 01100309-7bef-4154-85bf-f18489577e37
author: markingmyname
ms.author: maghan
ms.openlocfilehash: 0b5b207c4d36e820e6635bd9c8a2e99cdb7e4829
ms.sourcegitcommit: dd36d1cbe32cd5a65c6638e8f252b0bd8145e165
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 09/08/2020
ms.locfileid: "89541698"
---
# <a name="sp_markpendingschemachange-transact-sql"></a>sp_markpendingschemachange (Transact-SQL)
[!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
Se utiliza para la compatibilidad de las publicaciones de combinación lo que permite al administrador omitir cambios de esquema pendientes seleccionados para que así no se repliquen. Este procedimiento almacenado se ejecuta en el publicador de la base de datos de publicación.
> [!CAUTION]
> Este procedimiento almacenado puede hacer que los cambios en el esquema no se repliquen. Solo se debe utilizar para resolver problemas después de haber intentando otros métodos, como la reinicialización, o métodos que son demasiado costosos en términos de rendimiento.
## <a name="syntax"></a>Sintaxis
```
sp_markpendingschemachange [@publication = ] 'publication'
[ , [ @schemaversion = ] schemaversion ]
[ , [ @status = ] 'status' ]
```
## <a name="arguments"></a>Argumentos
`[ @publication = ] 'publication'` Es el nombre de la publicación. *Publication* es de **tipo sysname**y no tiene ningún valor predeterminado.
`[ @schemaversion = ] schemaversion` Identifica un cambio de esquema pendiente. *schemaversion* es de **tipo int**y su valor predeterminado es **0**. Use [sp_enumeratependingschemachanges ()de Transact-SQL ](../../relational-databases/system-stored-procedures/sp-enumeratependingschemachanges-transact-sql.md) para mostrar los cambios de esquema pendientes de la publicación.
`[ @status = ] 'status'` Indica si se omitirá un cambio de esquema pendiente. *status* es de tipo **nvarchar (10)** y su valor predeterminado es **Active**. Si se **omite**el valor de *status* , no se replicará el cambio de esquema seleccionado.
## <a name="return-code-values"></a>Valores de código de retorno
**0** (correcto) o **1** (error)
## <a name="remarks"></a>Observaciones
**sp_markpendingschemachange** se utiliza con la replicación de mezcla.
**sp_markpendingschemachange** es un procedimiento almacenado diseñado para la compatibilidad con la replicación de mezcla y solo debe usarse cuando otras acciones correctivas, como la reinicialización, no han podido corregir la situación o son demasiado costosas en términos de rendimiento.
## <a name="permissions"></a>Permisos
Solo los miembros del rol fijo de servidor **sysadmin** o del rol fijo de base de datos **db_owner** pueden ejecutar **sp_markpendingschemachange**.
## <a name="see-also"></a>Consulte también
[sysmergeschemachange (Transact-SQL)](../../relational-databases/system-tables/sysmergeschemachange-transact-sql.md)
| 52.123077 | 385 | 0.758264 | spa_Latn | 0.889315 |
933b12ce44725765960565a56d4875482cdd1b42 | 1,061 | md | Markdown | public/data/NP_international.md | tushark88/travel-reopening | 1cedc76008c09696a51c5cd81bf0987db0182ff5 | [
"MIT"
] | 2 | 2021-02-10T13:14:37.000Z | 2021-02-10T13:15:33.000Z | public/data/NP_international.md | gabriel-seow/travel-reopening | 0b01e887eb5140c76bb9425719aa3a3d24eabc61 | [
"MIT"
] | null | null | null | public/data/NP_international.md | gabriel-seow/travel-reopening | 0b01e887eb5140c76bb9425719aa3a3d24eabc61 | [
"MIT"
] | null | null | null | Restrictions apply for inbound and outbound travel. See below for more details.
#### Inbound Travel: Who can travel into Nepal?
Only travelers with special permission from the Civil Aviation Authority of Nepal may enter the country for purposes such as repatriation flights, rescue flights, and other special reasons. All other travelers are not allowed to enter Nepal.
The following restrictions apply:
- Nepal's international borders **remain closed**.
- The issuance of tourist visas is suspended. The processing of non-tourist visas, such as Working Visas, have resumed. [Click here](http://www.nepalimmigration.gov.np/post/notice-regarding-visa-services) for more information.
- Until **July 5, 2020**, international commercial flights into Nepal are [suspended](http://caanepal.gov.np/news-detail/post/urgent-notice-about-extension-suspension-period-domestic-and-international-commercial). This period may be further extended.
#### Outbound Travel: Who can travel out of Nepal?
International flights out of Nepal are suspended until further notice.
| 66.3125 | 250 | 0.798303 | eng_Latn | 0.993284 |
933b42c5174efbfe7f0e15ff1174aaca3fc444a5 | 215 | md | Markdown | README.md | FAIRsFAIR/fair-aware | 23f23a50d9f218b9f271f7bc61546d01a253d355 | [
"MIT"
] | null | null | null | README.md | FAIRsFAIR/fair-aware | 23f23a50d9f218b9f271f7bc61546d01a253d355 | [
"MIT"
] | 1 | 2020-05-13T10:34:41.000Z | 2020-05-13T10:34:41.000Z | README.md | FAIRsFAIR/fair-aware | 23f23a50d9f218b9f271f7bc61546d01a253d355 | [
"MIT"
] | 3 | 2020-05-13T07:31:48.000Z | 2021-02-05T12:11:02.000Z | FAIR-Aware – A self-assessment tool to raise awareness of users on data FAIRness.
<a href="https://doi.org/10.5281/zenodo.5084664"><img src="https://zenodo.org/badge/DOI/10.5281/zenodo.5084664.svg" alt="DOI"></a>
| 43 | 130 | 0.730233 | yue_Hant | 0.217821 |
933c416f9b4c39dfd29fe9e19e8147fe26652121 | 798 | md | Markdown | README.md | h2ooooooo/CLImax-yii2 | 84c15b3abf317ce4fb6d05d13a5ec78a9c6d340d | [
"MIT"
] | null | null | null | README.md | h2ooooooo/CLImax-yii2 | 84c15b3abf317ce4fb6d05d13a5ec78a9c6d340d | [
"MIT"
] | null | null | null | README.md | h2ooooooo/CLImax-yii2 | 84c15b3abf317ce4fb6d05d13a5ec78a9c6d340d | [
"MIT"
] | null | null | null | # Yii2 integration for CLImax
## Information
This package adds yii2 integration to CLImax.
## Installation
### Through command line
# Add the github repository to our list of repos to fetch composer packages from
composer config repositories.CLImax-yii2 git [email protected]:h2ooooooo/CLImax-yii2.git
# Require the dependency in composer
composer require-dev jalsoedesign/climax-yii2
# Update composer
composer update
### Through `composer.json`
First set up your `composer.json` file as you always do.
Then specify the requirement `jalsoedesign/climax-yii2` in `require` or `require-dev` and include the github repository URL in the `repositories` key like so:
{
"require": {
"jalsoedesign/climax-yii2": "master-dev"
}
} | 26.6 | 158 | 0.70802 | eng_Latn | 0.971005 |
933c6d80684de3f7f617b5d4e2e3d4350be4f686 | 424 | md | Markdown | _posts/2017-12-11-had-a-fantastic.md | curtclifton/curtclifton.github.io | 9e5e1180bbcad7c531cc5dff5e9e1736c8d4eb42 | [
"MIT"
] | null | null | null | _posts/2017-12-11-had-a-fantastic.md | curtclifton/curtclifton.github.io | 9e5e1180bbcad7c531cc5dff5e9e1736c8d4eb42 | [
"MIT"
] | null | null | null | _posts/2017-12-11-had-a-fantastic.md | curtclifton/curtclifton.github.io | 9e5e1180bbcad7c531cc5dff5e9e1736c8d4eb42 | [
"MIT"
] | null | null | null | ---
layout: post
microblog: true
audio:
photo: http://microblog.curtclifton.net/uploads/2017/b36be7811e.jpg
date: 2017-12-10 19:04:31 -0700
guid: http://curt.micro.blog/2017/12/11/had-a-fantastic.html
---
Had a fantastic day skiing with @tbunch at Crystal. The snow was spotty, but the company and the view can’t be beat.
<img src="http://microblog.curtclifton.net/uploads/2017/b36be7811e.jpg" width="600" height="450" />
| 35.333333 | 116 | 0.745283 | eng_Latn | 0.479532 |
933ceae67fa6c3bfe2b783e061678986ca851a5d | 1,191 | md | Markdown | Assets/README.md | umm/singleton | afc96a30d55c0eaa192e9a590a6a0718671b3e68 | [
"MIT"
] | null | null | null | Assets/README.md | umm/singleton | afc96a30d55c0eaa192e9a590a6a0718671b3e68 | [
"MIT"
] | null | null | null | Assets/README.md | umm/singleton | afc96a30d55c0eaa192e9a590a6a0718671b3e68 | [
"MIT"
] | 1 | 2017-09-09T06:12:18.000Z | 2017-09-09T06:12:18.000Z | # What?
* Singleton なアクセスを可能にする static アクセサを提供します。
# Why?
* シンプルな Singleton 機構を作りたかったので作りました。
# Install
### With Unity Package Manager
```bash
upm add package dev.upm-packages.singleton
```
Note: `upm` command is provided by [this repository](https://github.com/upm-packages/upm-cli).
You can also edit `Packages/manifest.json` directly.
```jsonc
{
"dependencies": {
// (snip)
"dev.upm-packages.singleton": "[latest version]",
// (snip)
},
"scopedRegistries": [
{
"name": "Unofficial Unity Package Manager Registry",
"url": "https://upm-packages.dev",
"scopes": [
"dev.upm-packages"
]
}
]
}
```
### Any other else (classical umm style)
```shell
$ npm install github:umm/singleton
```
# Usage
```csharp
using UnityEngine;
using UnityModule;
public class SampleSingleton : Singleton<SampleSingleton> {
public string Hoge = "ほげ";
}
public class Sample {
public void Run() {
Debug.Log(SampleSingleton.Instance.Hoge);
}
}
```
* `Singleton<T>` を継承したクラスを作るだけです。
* `<T>` には作成するクラスをそのまま用います。
# License
Copyright (c) 2017 Tetsuya Mori
Released under the MIT license, see [LICENSE.txt](LICENSE.txt)
| 15.88 | 94 | 0.654072 | eng_Latn | 0.602199 |
933ee952ac1872b9fa76ca6412658b107e73d205 | 6,273 | markdown | Markdown | _posts/2016-12-3-github.markdown | LovelyBuggies/blog | 1bf0076554acefba2e0ec2dc76c38c271177101f | [
"MIT"
] | null | null | null | _posts/2016-12-3-github.markdown | LovelyBuggies/blog | 1bf0076554acefba2e0ec2dc76c38c271177101f | [
"MIT"
] | null | null | null | _posts/2016-12-3-github.markdown | LovelyBuggies/blog | 1bf0076554acefba2e0ec2dc76c38c271177101f | [
"MIT"
] | null | null | null | ---
layout: post
title: "Github Programming Language Classification"
date: 2016-12-3
author: the Github Team
comments: true
published: true
description: Check out what our project team working for Github has done in programming language recognition!
---
<meta property="og:image" content="https://ml.berkeley.edu/blog/assets/2016-12-2-github/github_team.jpg" />
Github doesn’t only make version control software; it’s tasked with the unique challenge of analyzing programming languages. With over 10 million repositories, Github has an incredible corpus of files written by over 3 million users… that’s a lot of files. Our team had the unique opportunity of identifying which programming language each file was written in. Our dataset has 50,000+ files with over 600 languages, a nontrivial multi-class problem. We’ve improved on Github’s existing classifier, [Linguist](https://github.com/github/linguist), and, in the process, learned about what makes each programming language unique from one another.
<!-- break -->
<center>
<figure>
<img src="{{ site.baseurl }}/assets/2016-12-2-github/github_team.jpg" width="100%">
<figcaption>The Github team: <br>
Top: Hohsiang Wu, Brandon Lin, Dan Ricciardelli <br>
Bottom: Jin Park, Wesley Hsieh, Olivia Koshy, Jonathan Lee, Rohan Taori <br>
Not included: Jonathan Lee, Michael Zhao, Ted Xiao, Gautham Kesineni</figcaption>
</figure>
</center>
## Improvement #1: Dataset
Github’s Linguist has less than 5,000 files in its training data. As a result, their Naive Bayes classifier did not classify real-world files well. Not only that, but their classifier also requires that this dataset be curated and maintained as languages evolve and are added because some of the idiosyncrasies of different programming languages are hardcoded in. We tackled this by scraping Rosetta Code, a site with thousands of files categorized by task and, more importantly, programming language. Shifting from the Linguist dataset to Rosetta Code increased our test accuracy by 13.2%. Training accuracy went down as expected, because the Linguist classifier overfit to the smaller dataset. This is not concerning because test accuracy is really the metric that counts, and our higher test accuracy indicates that the larger dataset lets us generalize better to new, previously unseen files.
||Train|Test|
|Old Linguist Data Set|94.7%|53.7%|
|New Rosetta Code Dataset|85.6%|66.9%|
## Improvement #2: Feature Engineering
Github’s current classifier relies on [bag-of-words](https://en.wikipedia.org/wiki/Bag-of-words_model) methods to classify files, which means it can run into trouble differentiating programming languages with similar common statements. For example, C and C++ cannot be easily differentiated just by looking at which words are used. For ambiguous cases, Github’s Linguist hardcodes features that are unique to a particular language to distinguish between similar ones. Unfortunately, these hand-engineered features take significant time to construct and may change as languages evolve.
Because of this, our team has taken the prototypical bag-of-words approach and augmented it with linear and nonlinear features learned from data rather than constructed to match the data. For example, our team is currently modeling new features based off of features learned by RNN’s. This data-centric approaches scales well, grows easily to fit larger datasets, and requires much less human supervision on Github’s end.
These new features, both drawn from the raw data and learned by models, have allowed us to increase our classification accuracy from ~60% to 79-81%.
## Improvement #3: Model Types
Github’s previous Naive Bayes Classifier may be, well, naive, but that doesn’t mean it does a poor job. Bayesian classifiers work rather well with small datasets and integrate well with heuristic knowledge about the problem. However, Naive Bayes can be slow to train and classify files, may not generalize well, and requires human supervision to maintain well-behaved heuristics.
Our first new model is a multi-class Linear SVC. Linear SVCs are the classification variant of the popular SVM, which aims to divide the data points by class such that the minimum distance between the decision boundary and either class is maximized. This results in a classifier that is both robust, as it is highly linear, and complex, as many input features are non-linear.
We also used decision trees, chosen to mimic Linguist’s heuristic decision making process, and neural networks, chosen to deal well with reducing the sparse high-dimensional problem into something more tractable.
<center>
<img src="{{ site.baseurl }}/assets/2016-12-2-github/accuracy_graph.png" width="80%">
<img src="{{ site.baseurl }}/assets/2016-12-2-github/training_graph.png" width="80%">
</center>
## Improvement #4: Error Metrics
It's easy to feel comfortable about a model’s performance when it has been constructed to work well with the dataset. Even with a larger dataset, more carefully constructed error metrics allow us to guard against overconfident accuracy reports and to examine where our models are failing.
Our team tested our models with [stratified cross-validation](https://en.wikipedia.org/wiki/Cross-validation_(statistics)) (which is a way testing how well a model works) to ensure truthful accuracy measures by language and is working on an error metric pipeline so that Github can easily examine where their models are falling short and what can be improved.
<center>
<img src="{{ site.baseurl }}/assets/2016-12-2-github/misclassified.png" width="100%">
</center>
## Conclusion
Fourteen weeks of part-time work is not nearly enough to explore this problem, and ML@B’s Github team only touched the tip of the iceberg by finding a larger dataset, extracting machine-learned features, comparing different model types, and exploring various error metrics. There were many iterative improvements that are not mentioned in this post, but can be found [here](https://lexicon.github.io). All experiments that we conducted to improve our classifier can be replicated in our code. If you are interested in contributing, email [[email protected]](mailto:[email protected]).
| 93.626866 | 896 | 0.78798 | eng_Latn | 0.998632 |
9340477d37ac0c24a100e036855cdde512d8a17a | 6,661 | md | Markdown | languages/swift/exercises/concept/conditionals/.docs/after.md | himanshugoyal1065/v3 | 88259784b6c98626cafb0b4c6acdafccefd1c793 | [
"MIT"
] | null | null | null | languages/swift/exercises/concept/conditionals/.docs/after.md | himanshugoyal1065/v3 | 88259784b6c98626cafb0b4c6acdafccefd1c793 | [
"MIT"
] | 1 | 2020-01-26T20:08:06.000Z | 2020-01-26T20:08:06.000Z | languages/swift/exercises/concept/conditionals/.docs/after.md | himanshugoyal1065/v3 | 88259784b6c98626cafb0b4c6acdafccefd1c793 | [
"MIT"
] | null | null | null | There are three primary conditional statements that are used in Swift, `if` statements, `switch` statements, and `guard` statements. The `if` and `switch` statements are similar to those seen in a number of other languages, and `guard` should feel familiar to users of other languages with early exit statements.
## If statement
If statements in Swift are similar to those seen in other languages. E.g.:
```swift
if myValue > 0 {
print("myValue is positive")
} else {
print("myValue is not positive")
}
```
With this structure, if the Boolean expression following the `if` evaluates as `true`, the first block of code is run, the second block of code is skipped. And if the Boolean expression evaluates to `false`, the first block of code is skipped, the second block of code is run. In either case, the program continues running at the first line of code following the `if` statement.
There are two variants of this pattern that are available in Swift, the else-if and the no-else variants.
### else-if
In cases where the second block of code would just be another `if` statement, the else-if allows us to clean up the code and remove some indentation from our code by moving the `if` up next to the previous `else` and getting rid of a layer of parentheses.
So if we needed to perform different actions when a string is equal to “apple”, “lemon”, “peach”, or any other string, instead of nesting additional `if` statements inside the else blocks, one can write:
```swift
if str == "apple" {
print("Let's bake an apple crumble")
} else if str == "lemon" {
print("Let's bake a lemon meringue pie!")
} else if str == "peach" {
print("Let's bake a peach pie!")
} else {
print("Let's buy ice cream.")
}
```
### no-else
And if any if-statement only needs to perform code for one of the cases, the else branch can be left out entirely. So for example, if you are writing software that diagnoses patients and you need to log certain symptoms, like elevated heart rate, instead of writing:
```swift
if heartRate > 100 {
print(“elevated heart rate”)
} else {
()
}
```
You can drop the else and just write
```swift
if heartRate > 100 {
print(“elevated heart rate”)
}
```
## switch statements
While the else-if variant of `if` statements cleans things up considerably, there is still a lot of noise in the code from all of the curly braces. This is where the `switch` statement comes into play. In conditional statements with many possible branches, the switch statement shines. Note, however, that `switch` statements do work a bit differently from `if` statements.
Rather than evaluating a Boolean expression and using the value of that expression to choose the code branch that is run, a simple switch statement takes an input value (or expression which it evaluates to obtain the input value) of some type and compares against one or more values of the same type. If a case is found that matches the input value, the corresponding block of code is run.
Note that all possible cases must be covered in a `switch` statement. In cases like the above where all possible strings _cannot_ be enumerated, a `default` case can be used to match all remaining cases.
```swift
switch str {
case "apple":
print("Let's bake an apple crumble")
case "lemon":
print("Let's bake a lemon meringue pie!")
case "peach":
print("Let's bake a peach pie!")
default:
print("Let's buy ice cream.")
}
```
Additionally, note that if multiple cases of a switch statement match the input value, only the first matching case is used. An underscore (`_`) can be used to match all values.
Unlike in some other languages, `switch` cases in Swift do not fall through to the next case unless that behavior is explicitly called for with the `fallthrough` keyword. this is the opposite behavior from C which requires explicit `break` statements to prevent fallthrough.
### Binding and where statements
The values being matched in `switch` statements can also be bound to names which can be used in the body of the case. They can also be used in `where` clauses, which are additional boolean expressions that must evaluate as `true` for the case to match.
```swift
let x = 1337
switch sumOfDivisors(of: x) {
case let total where total == x:
print(total, "is a perfect number")
default:
print(x, "is not a perfect number")
}
```
## guard statements
The `guard` statement in swift is used for early returns from Swift functions when a necessary condition which needs to be met for further processing to continue is not met, e.g.:
```swift
guard myValue = 0 else { return 0 }
let root = myValue.squareRoot()
```
Here, the `guard` checks if the Boolean expression following the `guard` keyword evaluates as true. If it does, then processing continues with the code following the guard statement (here `let root = myValue.squareRoot()`. Otherwise it will execute the code in the else clause. Unlike an `if` statement, a `guard` statement _must_ have an else clause, and unlike the else clause of an if-else, the else clause of a guard _must_ exit the scope of the guard statement. I.e. it must use a control transfer statement she as return, continue, break, or it must throw an error or exit the program.
An example of its use is the sinc function, which is equal to sin(x)/x with sinc(0) defined to be 1, avoiding issues with division by 0. This function can be written in Swift, using a `guard` as:
```swift
func sinc(_ x: Double) -> Double {
guard x != 0 else { return 1 }
return sin(x) / x
}
sinc(0) // returns 1
sinc(Double.pi / 2) // returns 0.6366197723675814
```
## The Ternary Operator
Swift also supports a fourth type of conditional, [the ternary operator][ternaryoperator]. The ternary operator is an operator that takes, as the name implies, three inputs. The first input is a Boolean expression, and the other two inputs are expressions of the same type. The structure of the ternary operator is:
```swift
Boolean-expression ? expression1 : expression2
```
The ternary operator evaluates _Boolean-expression_ then, if the expression evaluates to `true`, evaluates _expression1_, returning its value, otherwise it evaluates _expression2_ and returns its value. For example, the following expression assigns the larger of the two values `a` and `b` to `bigger`.
```swift
let bigger = a > b ? a : b
```
To learn more about these topics it is recommended that you read [A Tour of Swift: Conditionals][conditionals]
[conditionals]: https://docs.swift.org/swift-book/LanguageGuide/ControlFlow.html#ID127
[ternaryoperator]: https://docs.swift.org/swift-book/LanguageGuide/BasicOperators.html#ID71
| 48.620438 | 591 | 0.747635 | eng_Latn | 0.999172 |
93408246cb492c57ab578850bc42c051d014cf9e | 776 | md | Markdown | _posts/666666/2022-10-19-hello465.md | chito365/uk | d1f92a520c24cba921e111aa73b75fd3fbc9deb8 | [
"MIT"
] | null | null | null | _posts/666666/2022-10-19-hello465.md | chito365/uk | d1f92a520c24cba921e111aa73b75fd3fbc9deb8 | [
"MIT"
] | null | null | null | _posts/666666/2022-10-19-hello465.md | chito365/uk | d1f92a520c24cba921e111aa73b75fd3fbc9deb8 | [
"MIT"
] | null | null | null | ---
id: 465
title: Ganso
author: chito
layout: post
guid: https://ukdataservers.com/mbti/?p=465
permalink: /hello465/
---
{: toc}
## Name
Ganso
* * *
## Nationality
Brazil
* * *
## National Position
* * *
## Random data
* National kit
* Club
Sevilla FC
* Club Position
Sub
* Club Kit
19
* Club Joining
42572
* Contract Expiry
2021
* Rating
80
* Height
184 cm
* Weight
78 kg
* Preffered Foot
Left
* Birth Date
32793
* Preffered Position
CAM/CM Medium / Low
* Weak foot
3
* Skill Moves
4
* Ball Control
84
* Dribbling
85
* Marking
41
* Sliding Tackle
37
* Standing Tackle
45
* Aggression
56
* Reactions
75
* Attacking Position
74
* Interceptions
47 | 8.168421 | 43 | 0.58634 | eng_Latn | 0.423652 |
9340875d0d98c2173c4ebc3c0cadd3fcfcdae154 | 9,327 | md | Markdown | articles/iot-hub/tutorial-manual-failover.md | andreasahlund/azure-docs.sv-se | 00cec92906c1c97e2a9aca9c48c51082b3cbb69d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-hub/tutorial-manual-failover.md | andreasahlund/azure-docs.sv-se | 00cec92906c1c97e2a9aca9c48c51082b3cbb69d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-hub/tutorial-manual-failover.md | andreasahlund/azure-docs.sv-se | 00cec92906c1c97e2a9aca9c48c51082b3cbb69d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Manuell redundans för Azure IoT-hubb | Microsoft Docs
description: Lär dig hur du utför en manuell redundansväxling av IoT-hubben till en annan region och bekräftar att den fungerar, och sedan återgår till den ursprungliga regionen och markerar den igen.
author: robinsh
manager: timlt
ms.service: iot-hub
services: iot-hub
ms.topic: tutorial
ms.date: 07/24/2019
ms.author: robinsh
ms.custom:
- mvc
- mqtt
ms.openlocfilehash: 69a0795b9c299b5113c39ce2c4556573f730e4b7
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 10/09/2020
ms.locfileid: "89013953"
---
# <a name="tutorial-perform-manual-failover-for-an-iot-hub"></a>Självstudie: utföra manuell redundans för en IoT-hubb
Manuell redundans är en funktion i IoT Hub-tjänsten som gör att kunder kan utföra [redundans](https://en.wikipedia.org/wiki/Failover) för hubbens åtgärder från en primär region till motsvarande geoparade Azure-region. Manuell redundans kan utföras i händelse av ett regionalt haveri eller ett längre tjänstavbrott. Du kan även utföra en planerad redundans för att testa din haveriberedskap, men vi rekommenderar att du använder en IoT-testhubb i stället för en som körs i produktion. Funktionen manuell redundans erbjuds till kunder utan extra kostnad för IoT Hub som skapats efter 18 maj 2017.
I den här självstudien utför du följande åtgärder:
> [!div class="checklist"]
> * Använd Azure-portalen för att skapa en IoT-hubb.
> * Utför en redundans.
> * Se att hubben körs på den sekundära platsen.
> * Utför en återställning efter fel för att återställa IoT-hubbens åtgärder till den primära platsen.
> * Bekräfta att hubben körs korrekt på rätt plats.
Mer information om manuell redundans och Microsoft-initierad redundans med IoT Hub finns i [haveri beredskap över flera regioner](iot-hub-ha-dr.md#cross-region-dr).
## <a name="prerequisites"></a>Förutsättningar
* En Azure-prenumeration. Om du inte har någon Azure-prenumeration kan du skapa ett [kostnadsfritt konto](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) innan du börjar.
* Kontrol lera att port 8883 är öppen i brand väggen. Enhets exemplet i den här självstudien använder MQTT-protokoll, som kommunicerar via port 8883. Den här porten kan blockeras i vissa företags-och miljö nätverks miljöer. Mer information och sätt att kringgå det här problemet finns i [ansluta till IoT Hub (MQTT)](iot-hub-mqtt-support.md#connecting-to-iot-hub).
## <a name="create-an-iot-hub"></a>Skapa en IoT-hubb
1. Logga in på [Azure Portal](https://portal.azure.com).
2. Klicka på **+ Skapa en resurs** och välj **Internet of Things** (Sakernas Internet) och sedan **IoT Hub**.
3. Välj fliken **grundläggande** . Fyll i följande fält.
**Prenumeration**: Välj den Azure-prenumeration som du vill använda.
**Resursgrupp**: Klicka på **Skapa ny** och ange **ManlFailRG** för resursgruppens namn.
**Region**: Välj en region nära dig. I den här självstudien används `West US 2`. Det går bara att utföra en redundans mellan geoparade Azure-regioner. Regionen geo-par med västra USA 2 är WestCentralUS.
**Namn på IoT-hubb**: Ange ett namn för IoT-hubben. Hubbnamnet måste vara globalt unikt.
Klicka på **Granska + skapa**. (Den använder standardinställningarna för storlek och skala.)
4. Granska informationen och klicka sedan på **Skapa** för att skapa IoT-hubben.
## <a name="perform-a-manual-failover"></a>Utför en manuell redundans
Observera att det finns en gräns på två redundanser och två återställningar efter fel per dag för en IoT-hubb.
1. Klicka på **Resursgrupper** och välj sedan resursgruppen **ManlFailRG**. Klicka på din hubb i listan över resurser.
1. Under **Inställningar** i fönstret IoT Hub klickar du på **redundans**.
1. I fönstret manuell redundans visas den **aktuella platsen** och **platsen för redundans**. Den aktuella platsen anger alltid den plats där hubben är aktiv för närvarande. Platsen för redundans är den standardiserade [Azure geo-kopplade regionen](../best-practices-availability-paired-regions.md) som är länkad till den aktuella platsen. Du kan inte ändra platsvärdena. För den här självstudien är den aktuella platsen `West US 2` och platsen för redundans `West Central US` .
1. Klicka på **Starta redundans**överst i fönstret manuell redundans.
1. I bekräftelse fönstret fyller du i namnet på din IoT Hub för att bekräfta att det är det som du vill redundansväxla. Klicka sedan på **redundans**för att starta redundansväxlingen.
Den tid det tar att utföra manuell redundans är proportionell mot antalet enheter som är registrerade för din hubb. Om du till exempel har 100 000 enheter kan det ta 15 minuter, men om du har fem miljoner enheter kan det ta en timme eller längre.
Medan den manuella redundansväxlingen körs visas en banderoll som anger att en manuell redundansväxling pågår.
Om du stänger IoT Hubs fönstret och öppnar det igen genom att klicka på det i rutan resurs grupp visas en banderoll som visar att navet är i mitten av en manuell redundansväxling.
När den är färdig, vänds de aktuella områdena och redundansväxlingen på sidan manuell redundans och hubben är aktiv igen. I det här exemplet är den aktuella platsen nu `WestCentralUS` och platsen för redundans är nu `West US 2` .
På sidan Översikt visas också en banderoll som anger att redundansväxlingen är klar och IoT Hub körs i `West Central US` .
## <a name="perform-a-failback"></a>Utföra en återställning efter fel
När du har utfört en manuell redundans kan du växla tillbaka hubbens åtgärder till den ursprungliga primära regionen – det här kallas en återställning efter fel. Om du precis har utfört en redundans måste du vänta ungefär en timme innan du kan begära en återställning efter fel. Om du försöker utföra återställningen på en kortare tid visas ett felmeddelande.
En återställning efter fel utförs precis som en manuell redundans. Det här är stegen:
1. För att utföra en återställning efter fel går du tillbaka till fönsterrutan för IoT Hub för din IoT-hubb.
2. Under **Inställningar** i fönstret IoT Hub klickar du på **redundans**.
3. Klicka på **Starta redundans**överst i fönstret manuell redundans.
4. I bekräftelse fönstret fyller du i namnet på din IoT Hub för att bekräfta att det är det som du vill återställa efter fel. Sedan initierar du återställning efter fel genom att klicka på OK.
Banderollerna visas enligt beskrivning i avsnittet utföra en redundans. När återställningen är klar visas den igen `West US 2` som den aktuella platsen och `West Central US` som platsen för redundans enligt inställningen ursprungligen.
## <a name="clean-up-resources"></a>Rensa resurser
Om du vill ta bort de resurser du skapade för den här självstudien tar du bort hela resursgruppen. Detta tar även bort alla resurser som ingår i gruppen. I det här fallet tas IoT-hubben och själva resursgruppen bort.
1. Klicka på **Resursgrupper**.
2. Leta upp och välj resursgruppen **ManlFailRG**. Klicka på det för att öppna det.
3. Klicka på **Ta bort resursgrupp**. När du uppmanas anger du namnet på resursgruppen och klickar på **Ta bort** för att bekräfta.
## <a name="next-steps"></a>Nästa steg
I den här självstudien har du lärt dig hur du konfigurerar och utför en manuell redundans samt hur du begär en återställning efter fel genom att utföra följande uppgifter:
> [!div class="checklist"]
> * Använd Azure-portalen för att skapa en IoT-hubb.
> * Utför en redundans.
> * Se att hubben körs på den sekundära platsen.
> * Utför en återställning efter fel för att återställa IoT-hubbens åtgärder till den primära platsen.
> * Bekräfta att hubben körs korrekt på rätt plats.
Gå vidare till nästa självstudie där du får lära dig hur du hanterar tillstånd för en IoT-enhet.
> [!div class="nextstepaction"]
> [Hantera tillståndet för en IoT-enhet](tutorial-device-twins.md)
| 62.18 | 594 | 0.776563 | swe_Latn | 0.999938 |
934178cc7e4c2a396254e4d78493bae6faa15e84 | 1,248 | markdown | Markdown | _posts/2019-07-07-plan-7.markdown | caisj2016/caisj2016.github.io | 2fb69d39014757b2439f6578e9332bc25b27c9a4 | [
"Apache-2.0"
] | null | null | null | _posts/2019-07-07-plan-7.markdown | caisj2016/caisj2016.github.io | 2fb69d39014757b2439f6578e9332bc25b27c9a4 | [
"Apache-2.0"
] | null | null | null | _posts/2019-07-07-plan-7.markdown | caisj2016/caisj2016.github.io | 2fb69d39014757b2439f6578e9332bc25b27c9a4 | [
"Apache-2.0"
] | null | null | null | ---
layout: post
title: "7月计划"
subtitle: "拖延症晚期咋办"
date: 2019-07-07 08:42:00
author: "Cai"
header-img: "img/contact-bg.jpg"
tags:
- 生活
---
# 杂谈
对的，7月了。本应该7月第一周写计划的，咋到了第二周了呢？
对的，拖延症犯了。
19天没有去健身房了，时间真的过的非常的快。
这个周日本来计划的写个demo，也没搞！
本来计划的读几篇论文的，只是下载了论文！
这样下去，可不行。
# 计划
7月计划 0708～0731
* 月 （会議）23時～24時 自由 24:00睡觉
* 火、水、木、金 (不加班的话) 2*4=8h
* 每天固定时间看论文或者做项目 8点～10点
* 火 木 22時～23時 健身 24:00睡觉
* 水 金 22時～24時 自由 24:00睡觉
* 土
* 朝（会議）13時～18時図書館 18時～24時 自由 5h
* 日
* 10時～12時 项目 2h
* 12時～14時 自由
* 14時～15時 健身
* 15時～18時 项目 3h
* 18時～23時 自由
* 23時～24時 总结 1h
* 24時睡觉
#### 结果
- 学习时间:8+6+6=19h
- 会议时间:2*2=4h
- 锻炼一周三次
#### 计划补充
这个计划时间上似乎有一些完美，遵守会比较难实施，然后没有人监督，显得非常的无力。在工作上加班和会议加上一些展览会的参加，会使得平时的时间变少，疲惫的身体会不想去学习和记忆一些东西。但是如果没有这个计划，可能又一周这样一个周末过去了，毕竟7月的paper概要，8月底的纪要全文，都是一定要做的事情。计划会在今天把，做成Google日历，今天就开始实行。
#### 关于惩罚
关于惩罚我首先想到的是罚钱，这个办法我试了很多次，效果还行。
问题是监督难度非常大，或许只有我自己监督，但是我不遵守，我自己罚自己可能也不会执行，那就没有意义了。如果是增加学习时间或者减少自由时间，会使这个平衡破坏，那就很难继续维持下去了，这个是很大的困难。我打算用减少奖励来处理这个事情。
#### 关于奖励
关于奖励，自己奖励自己，好像很奇怪，对我来说，花大价钱，买无意义的东西给自己，就是一种惩罚。我打算如果我做到了，如果一周都完成了我打算拿出10000日元作为奖励自己，一共就是3万。然后月末把这个3万花费掉，买一些日常以外的东西。如果一天没做到那么就减3000。超过3万，就减去下个月的生活费。
# 展望
希望一切顺利把，能完成我的计划。7月能顺利的完成目标把。
| 21.894737 | 175 | 0.705929 | yue_Hant | 0.465178 |
934333f97489f083fdb6235d61354df89b39e677 | 713 | md | Markdown | docs/core/sip.js.session.refer.md | CloudTalk-io/SIP.js | 840b3ad9ee78df4a5c7d071e7bf30e1a2ab4b535 | [
"MIT"
] | null | null | null | docs/core/sip.js.session.refer.md | CloudTalk-io/SIP.js | 840b3ad9ee78df4a5c7d071e7bf30e1a2ab4b535 | [
"MIT"
] | null | null | null | docs/core/sip.js.session.refer.md | CloudTalk-io/SIP.js | 840b3ad9ee78df4a5c7d071e7bf30e1a2ab4b535 | [
"MIT"
] | 3 | 2020-01-20T16:32:06.000Z | 2020-08-18T21:26:14.000Z | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [sip.js](./sip.js.md) > [Session](./sip.js.session.md) > [refer](./sip.js.session.refer.md)
## Session.refer() method
Send REFER request (in dialog). Transfer a session. https://tools.ietf.org/html/rfc3515\#section-2.4.1
<b>Signature:</b>
```typescript
refer(delegate?: OutgoingRequestDelegate, options?: RequestOptions): OutgoingReferRequest;
```
## Parameters
| Parameter | Type | Description |
| --- | --- | --- |
| delegate | <code>OutgoingRequestDelegate</code> | Request delegate. |
| options | <code>RequestOptions</code> | Options bucket. |
<b>Returns:</b>
`OutgoingReferRequest`
| 27.423077 | 121 | 0.680224 | kor_Hang | 0.256414 |
93437c01516ba562e680a667b2b000d3f48d2545 | 4,863 | md | Markdown | docs/fsharp/get-started/get-started-visual-studio.md | jhonyfrozen/docs.pt-br | c9e86b6a5de2ff8dffd54dd64d2e87aee85a5cb8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/fsharp/get-started/get-started-visual-studio.md | jhonyfrozen/docs.pt-br | c9e86b6a5de2ff8dffd54dd64d2e87aee85a5cb8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/fsharp/get-started/get-started-visual-studio.md | jhonyfrozen/docs.pt-br | c9e86b6a5de2ff8dffd54dd64d2e87aee85a5cb8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Introdução ao F# no Visual Studio
description: Saiba como usar F# com o Visual Studio.
ms.date: 07/03/2018
ms.openlocfilehash: 9b02a5d295f982b1911dab567213fa9a2b6c4304
ms.sourcegitcommit: 2701302a99cafbe0d86d53d540eb0fa7e9b46b36
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/28/2019
ms.locfileid: "64754869"
---
# <a name="get-started-with-f-in-visual-studio"></a>Introdução ao F# no Visual Studio
F#e o Visual F# ferramentas têm suporte no IDE do Visual Studio.
Para começar, certifique-se de que você tenha [com o Visual Studio instalado F# ](install-fsharp.md#install-f-with-visual-studio).
## <a name="creating-a-console-application"></a>Criando um aplicativo de console
Um dos projetos mais básicos no Visual Studio é o aplicativo de Console. Veja como fazer isso. Após abrir o Visual Studio:
1. Sobre o **arquivo** , aponte para **New**e, em seguida, escolha **projeto**.
2. Na nova caixa de diálogo projeto, sob **modelos**, você deverá ver **Visual F#** . Escolha esta opção para mostrar o F# modelos.
3. Selecione a **aplicativo de Console do .NET Core** ou **aplicativo de Console**.
4. Escolha o **Okey** botão para criar o F# projeto! Agora você deve ver uma F# projeto no Gerenciador de soluções.
## <a name="writing-your-code"></a>Escrever seu código
Vamos começar escrevendo um código pela primeira vez. Certifique-se de que o `Program.fs` arquivo está aberto e, em seguida, substitua seu conteúdo pelo seguinte:
[!code-fsharp[HelloSquare](../../../samples/snippets/fsharp/getting-started/hello-square.fs)]
No exemplo de código anterior, uma função `square` tenha sido definido, que usa uma entrada denominada `x` e multiplica por si só. Porque F# usa [inferência de tipo](../language-reference/type-inference.md), o tipo de `x` não precisa ser especificado. O F# compilador entende os tipos em que a multiplicação é válida e atribuirá um tipo para `x` com base em como `square` é chamado. Se você focalizar `square`, você deve ver o seguinte:
```fsharp
val square: x:int -> int
```
Esse é o que é conhecido como assinatura de tipo da função. Ele pode ser lido como este: "Quadrado é uma função que usa um número inteiro denominado x e produz um número inteiro". Observe que o compilador forneceu `square` as `int` tipo por ora - isso é porque a multiplicação não é genérica entre *todos os* tipos, mas em vez disso, é genérico em um conjunto fechado de tipos. O F# compilador escolhido `int` neste ponto, mas ele se ajustará a assinatura de tipo se você chamar `square` com outro tipo de entrada, como um `float`.
Outra função, `main`, é definido, que é decorado com o `EntryPoint` atributo para informar o F# compilador que a execução do programa deve iniciar lá. Ele segue a mesma convenção que outro [linguagens de programação C-style](https://en.wikipedia.org/wiki/Entry_point#C_and_C.2B.2B), em que os argumentos de linha de comando podem ser passados para essa função, e um código inteiro será retornado (normalmente `0`).
É nessa função que podemos chamar o `square` função com um argumento de `12`. O F# compilador, em seguida, atribui o tipo de `square` seja `int -> int` (ou seja, uma função que leva um `int` e produz um `int`). A chamada para `printfn` é uma função de impressão formatada que usa uma cadeia de formato, semelhante a linguagens de programação C-style, parâmetros que correspondem aos especificados na cadeia de caracteres de formato e, em seguida, imprime o resultado e uma nova linha.
## <a name="running-your-code"></a>Execução do código
Você pode executar o código e ver resultados pressionando **Ctrl**+**F5**. Isso executa o programa sem depuração e permite que você veja os resultados. Como alternativa, você pode escolher o **Debug** menu de nível superior do item no Visual Studio e escolha **Start Without Debugging**.
Agora, você verá o seguinte mostrado na janela de console que surge do Visual Studio:
```
12 squared is 144!
```
Parabéns! Você criou seu primeiro F# projeto no Visual Studio, escrito um F# função impresso os resultados da chamada de função e execute o projeto para ver alguns resultados.
## <a name="next-steps"></a>Próximas etapas
Se você ainda não fez isso, confira a [Tour do F# ](../tour.md), que aborda alguns dos principais recursos do F# linguagem. Ele lhe fornecerá uma visão geral de alguns dos recursos do F#e fornecem exemplos de código amplo que você pode copiar para o Visual Studio e executar. Também existem alguns ótimos recursos externos, você pode usar, foi apresentada na [ F# guia de](../index.md).
## <a name="see-also"></a>Consulte também
- [Tour do F#](../tour.md)
- [F#referência da linguagem](../language-reference/index.md)
- [Inferência de tipo](../language-reference/type-inference.md)
- [Referência de símbolo e o operador](../language-reference/symbol-and-operator-reference/index.md)
| 69.471429 | 534 | 0.754267 | por_Latn | 0.999804 |
934416c89197c73170040044bf1c089b066423f9 | 8,035 | md | Markdown | CHANGELOG.md | frecco75/vault | 1e44a98074e393dcad5a9e78c4cea8938a46584c | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | frecco75/vault | 1e44a98074e393dcad5a9e78c4cea8938a46584c | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | frecco75/vault | 1e44a98074e393dcad5a9e78c4cea8938a46584c | [
"Apache-2.0"
] | null | null | null | # Change Log
All notable changes to this project will be documented in this file.
This project adheres to [Semantic Versioning](http://semver.org/).
## Version [3.2.1] - 2018-05-28
- Fix: ignore empty asset fields
- Update: Contentful CDA SDK to version 10.1.0.
## Version [3.2.0] - 2018-04-24
- Change: use https for asset urls.
- Change: Use CDA SDK 10.0.0 and throw if environments are used.
- Change: Locale handling: CDA 10 uses `/locales` and not `/space.locales`, update tests and internal structure.
## Version [3.1.1] - 2018-02-13
- Add: update CDA SDK
- Remove: Synthetic methods
## Version [3.1.0] - 2017-10-18
- Add: Database pre seeding utility
- Update: Contentful CDA SDK to include Android pre 5.0 auto configured TLS 1.2.
## Version [3.0.2] - 2017-10-18
- Fix: Do not use a properties file for version name storage.
- Fix: Update version of CDA SDK to include non properties file loading.
## Version [3.0.1] - 2017-08-24
- Fix: Upload all artifacts.
## Version [3.0.0] - 2017-08-16
- Fixes
* Circular dependencies on links
- Changes
* Remove direct client passing through. Please use a `SyncConfig.Builder()`.
- Updates
* Contentful 8.0.0 (was 7.2.0)
* rx Java 2.1.1 (was 1.0.14)
* okhttp 3.8.1 (was 2.5.0)
* robolectric 3.3.2 (was 3.0)
* truth 0.34 (was 0.25)
* compile-testing 0.9 (was 0.6)
* guava 22.0 (was 18.0)
* commons-io 2.5 (was 2.4)
* junit 4.12 (was 4.10)
## Version [2.1.0]- 2016-11-10
- Updating to newest Contentful Delivery Api SDK, adding limited support for sync in preview.
## Version [2.0.0] - 2016-04-15
- changed: update cda to 7.0.0
## Version [1.0.0] - 2016-02-29
- NOTE: This release introduces backwards incompatible changes to any existing database schemas, when upgrading make sure to bump the `dbVersion` attribute on your `Space`.
- NOTE: Also: Indicate satisfaction with current stability of api
- fixed: Use correct text type for sql statements
## Version [0.9.14] - 2015-11-23
- Fixed: Non-localized arrays of links now resolve properly.
## Version [0.9.13] - 2015-11-21
- Fixed: Incorrect persistence of localized links.
## Version [0.9.12] - 2015-10-28
- Changed: Use contentful.java v5.0.1 (fixes CME for localized link fields pointing to non-existing resources).
## Version [0.9.11] - 2015-09-17
- Fixed: DB upgrade failures.
## Version [0.9.10] - 2015-09-03
- NOTE: This release introduces backwards incompatible changes to any existing database schemas, when upgrading make sure to bump the `dbVersion` attribute on your `Space`.
- New: Simplified extension `Vault.requestSync(CDAClient)`.
- Changed: Asset attrs are now final.
- Changed: Compiler will fail for static `@Field` elements.
- Changed: Compiler will fail for private `@Field` elements.
- Changed: RxJava v1.0.14.
- Changed: OkHttp v2.5.0.
- Changed: contentful.java v4.0.2.
- Changed: Project now uses Java 7 language level.
- Fixed: Preserve order for arrays of links.
- Fixed: Duplicate array links are no longer squashed.
## Version [0.9.9] - 2015-08-13
- NOTE: This release introduces backwards incompatible changes to any existing database schemas, when upgrading make sure to bump the `dbVersion` attribute on your `Space`.
- New: Support multiple locales per space. Locales to persist must be explicitly defined with the `@Space` annotation.
- Changed: Better error handling when initializing vault with an invalid class.
- Changed: Declaring a model with no fields will fail at compile-time.
## Version [0.9.8] - 2015-08-01
- New: RxJava support with `Vault.observe()` and `Vault.observeSyncResults()`.
- New: `SyncResult` class to represent a result of sync operation.
- Changed: `SyncCallback` replaced `onSuccess()` and `onFailure()` with `onResult(SyncResult)`.
- Changed: RxJava v1.0.13.
## Version [0.9.7] - 2015-07-22
- Changed: Use contentful.java v4.0.1 (fixes NPE for entries with null links).
## Version [0.9.6] - 2015-07-22
- NOTE: This release introduces backwards incompatible changes to any existing database schemas, when upgrading make sure to bump the `dbVersion` attribute on your `Space`.
- New: Support using a pre-existing vault database with the `copyPath` attribute on `@Space`.
- New: Compiler now injects static `$Fields` class to every model, reflecting the model's column names.
- New: Add `Asset.Fields` class.
- New: Add `BaseFields` class with common resource column names.
- Changed: Use contentful.java v4.0.0.
- Changed: Proguard configuration update to keep generated `$Fields` classes.
- Fixed: Add missing asset metadata: title, description and file map.
## Version [0.9.5] - 2015-07-07
- Changed: Missing location/object fields will be set to null instead of empty collections.
- Fixed: Boolean field values set properly.
## Version [0.9.4] - 2015-07-05
- Changed: Add `onError` and `onSuccess()` methods to `SyncCallback`.
- Changed: Use contentful.java v2.0.4.
- Fixed: Replace `getClass()` calls with generated code for link resolution.
- Fixed: Escape model field names on inserts.
## Version [0.9.3] - 2015-05-26
- New: `Resource` implementation for `equals()` and `hashCode()`
## Version [0.9.2] - 2015-05-21
- Fixed: Link persistence and resolution (reopened from v0.9.1).
## Version [0.9.1] - 2015-05-20
- New: `Asset` is now `Parcelable`.
- New: Optional `SyncConfig` setting that causes invalidation of existing data upon sync.
- New: Provide direct read-only access to database objects.
- Changed: Use empty collections instead of null for empty arrays / maps.
- Changed: Use contentful.java v2.0.3.
- Changed: contentful.java dependency scope changed to compile.
- Fixed: Link resolution for arrays of resources now works correctly.
- Fixed: Removed incorrect calls to `close()` on database objects.
## Version 0.9.0 - 2015-05-18
Initial release.
[unreleased]: https://github.com/contentful/vault/compare/vault-parent-3.2.1...HEAD
[3.2.0]: https://github.com/contentful/vault/compare/vault-parent-3.2.0...vault-parent-3.2.1
[3.2.0]: https://github.com/contentful/vault/compare/vault-parent-3.1.1...vault-parent-3.2.0
[3.1.1]: https://github.com/contentful/vault/compare/vault-parent-3.1.0...vault-parent-3.1.1
[3.1.0]: https://github.com/contentful/vault/compare/vault-parent-3.0.2...vault-parent-3.1.0
[3.0.2]: https://github.com/contentful/vault/compare/vault-parent-3.0.1...vault-parent-3.0.2
[3.0.1]: https://github.com/contentful/vault/compare/vault-parent-3.0.0...vault-parent-3.0.1
[3.0.0]: https://github.com/contentful/vault/compare/vault-parent-2.1.0...vault-parent-3.0.0
[2.1.0]: https://github.com/contentful/vault/compare/vault-parent-2.0.0...vault-parent-2.1.0
[2.0.0]: https://github.com/contentful/vault/compare/vault-parent-1.0.0...vault-parent-2.0.0
[1.0.0]: https://github.com/contentful/vault/compare/vault-parent-0.9.14...vault-parent-1.0.0
[0.9.14]: https://github.com/contentful/vault/compare/vault-parent-0.9.13...vault-parent-0.9.14
[0.9.13]: https://github.com/contentful/vault/compare/vault-parent-0.9.12...vault-parent-0.9.13
[0.9.12]: https://github.com/contentful/vault/compare/vault-parent-0.9.11...vault-parent-0.9.12
[0.9.11]: https://github.com/contentful/vault/compare/vault-parent-0.9.10...vault-parent-0.9.11
[0.9.10]: https://github.com/contentful/vault/compare/vault-parent-0.9.9...vault-parent-0.9.10
[0.9.9]: https://github.com/contentful/vault/compare/vault-parent-0.9.8...vault-parent-0.9.9
[0.9.8]: https://github.com/contentful/vault/compare/vault-parent-0.9.7...vault-parent-0.9.8
[0.9.7]: https://github.com/contentful/vault/compare/vault-parent-0.9.6...vault-parent-0.9.7
[0.9.6]: https://github.com/contentful/vault/compare/vault-parent-0.9.5...vault-parent-0.9.6
[0.9.5]: https://github.com/contentful/vault/compare/vault-parent-0.9.4...vault-parent-0.9.5
[0.9.4]: https://github.com/contentful/vault/compare/vault-parent-0.9.3...vault-parent-0.9.4
[0.9.3]: https://github.com/contentful/vault/compare/v0.9.2...vault-parent-0.9.3
[0.9.2]: https://github.com/contentful/vault/compare/v0.9.1...v0.9.2
[0.9.1]: https://github.com/contentful/vault/compare/v0.9.0...v0.9.1
| 50.21875 | 172 | 0.725825 | eng_Latn | 0.55766 |
93441f571c9f9c4078ffe76d9d92cffe53f7a873 | 4,519 | md | Markdown | docs/csharp/programming-guide/concepts/assemblies-gac/how-to-create-unsigned-friend-assemblies.md | SilverBuzzard/docs.pl-pl | a3cda910e7b4b30f2c3c449c742dce1be42067b5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/programming-guide/concepts/assemblies-gac/how-to-create-unsigned-friend-assemblies.md | SilverBuzzard/docs.pl-pl | a3cda910e7b4b30f2c3c449c742dce1be42067b5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/programming-guide/concepts/assemblies-gac/how-to-create-unsigned-friend-assemblies.md | SilverBuzzard/docs.pl-pl | a3cda910e7b4b30f2c3c449c742dce1be42067b5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Porady: tworzenie nieoznaczonych przyjaznych zestawów (C#)'
ms.date: 07/20/2015
ms.assetid: 78cbc4f0-b021-4141-a4ff-eb4edbd814ca
ms.openlocfilehash: 7244f17c24a16569903783c730fc356b11e20aa8
ms.sourcegitcommit: c7f3e2e9d6ead6cc3acd0d66b10a251d0c66e59d
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 09/08/2018
ms.locfileid: "44211804"
---
# <a name="how-to-create-unsigned-friend-assemblies-c"></a>Porady: tworzenie nieoznaczonych przyjaznych zestawów (C#)
W tym przykładzie pokazano, jak przyjaznych zestawów za pomocą zestawów, które są bez znaku.
### <a name="to-create-an-assembly-and-a-friend-assembly"></a>Aby utworzyć zestaw i zestaw przyjazny
1. Otwórz wiersz polecenia.
2. Utwórz plik języka C# o nazwie `friend_signed_A.` zawierający poniższy kod. Kod używa <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> atrybutu, aby zadeklarować friend_signed_B jako przyjaznego zestawu.
```csharp
// friend_unsigned_A.cs
// Compile with:
// csc /target:library friend_unsigned_A.cs
using System.Runtime.CompilerServices;
using System;
[assembly: InternalsVisibleTo("friend_unsigned_B")]
// Type is internal by default.
class Class1
{
public void Test()
{
Console.WriteLine("Class1.Test");
}
}
// Public type with internal member.
public class Class2
{
internal void Test()
{
Console.WriteLine("Class2.Test");
}
}
```
3. Skompiluj i podpisać friend_signed_A przy użyciu następującego polecenia.
```csharp
csc /target:library friend_unsigned_A.cs
```
4. Utwórz plik języka C# o nazwie `friend_unsigned_B` zawierający poniższy kod. Ponieważ friend_unsigned_A określa friend_unsigned_B jako zestaw przyjazny, kod w friend_unsigned_B mogą uzyskiwać dostęp do `internal` typów i elementów członkowskich z friend_unsigned_A.
```csharp
// friend_unsigned_B.cs
// Compile with:
// csc /r:friend_unsigned_A.dll /out:friend_unsigned_B.exe friend_unsigned_B.cs
public class Program
{
static void Main()
{
// Access an internal type.
Class1 inst1 = new Class1();
inst1.Test();
Class2 inst2 = new Class2();
// Access an internal member of a public type.
inst2.Test();
System.Console.ReadLine();
}
}
```
5. Skompiluj friend_signed_B przy użyciu następującego polecenia.
```csharp
csc /r:friend_unsigned_A.dll /out:friend_unsigned_B.exe friend_unsigned_B.cs
```
Nazwa zestawu, który jest generowany przez kompilator musi odpowiadać nazwy przyjaznego zestawu, który jest przekazywany do <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> atrybutu. Należy jawnie określić nazwę zestawu wyjściowego (.exe lub .dll), za pomocą `/out` — opcja kompilatora. Aby uzyskać więcej informacji, zobacz [/out (opcje kompilatora C#)](../../../../csharp/language-reference/compiler-options/out-compiler-option.md).
6. Uruchom plik friend_signed_B.exe.
Program wyświetla dwa ciągi: "Class1.Test" i "Class2.Test".
## <a name="net-framework-security"></a>Zabezpieczenia.NET Framework
Istnieją podobieństwa między usługami <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> atrybutu i <xref:System.Security.Permissions.StrongNameIdentityPermission> klasy. Główną różnicą jest to, że <xref:System.Security.Permissions.StrongNameIdentityPermission> może wymagać uprawnienia zabezpieczeń do uruchamiania w określonej sekcji kodu, natomiast <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute> atrybut kontroluje widoczność `internal` typów i elementów członkowskich.
## <a name="see-also"></a>Zobacz też
- <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute>
- [Zestawy i Globalna pamięć podręczna zestawów (C#)](../../../../csharp/programming-guide/concepts/assemblies-gac/index.md)
- [Przyjazne zestawy (C#)](../../../../csharp/programming-guide/concepts/assemblies-gac/friend-assemblies.md)
- [Porady: tworzenie oznaczonych przyjaznych zestawów (C#)](../../../../csharp/programming-guide/concepts/assemblies-gac/how-to-create-signed-friend-assemblies.md)
- [Przewodnik programowania w języku C#](../../../../csharp/programming-guide/index.md)
| 45.19 | 511 | 0.702368 | pol_Latn | 0.985273 |
93445cb823b60a351267956e712b7ad46f1b980c | 345 | md | Markdown | README.md | kmetcalf/maze4vim | e7c9b045d39f8c0b1dcd47d8f9aca5f1bc2d41f5 | [
"BSD-2-Clause"
] | 1 | 2018-08-28T23:32:39.000Z | 2018-08-28T23:32:39.000Z | README.md | kmetcalf/maze4vim | e7c9b045d39f8c0b1dcd47d8f9aca5f1bc2d41f5 | [
"BSD-2-Clause"
] | 1 | 2018-08-01T20:01:48.000Z | 2018-08-01T20:01:48.000Z | README.md | kmetcalf/maze4vim | e7c9b045d39f8c0b1dcd47d8f9aca5f1bc2d41f5 | [
"BSD-2-Clause"
] | null | null | null | # maze4vim
## About
A simple vim navigation game designed to help with learning the basics of vim navigation.
## Installation
Please clone the system from git-hub.
## Contributing
PR's welcome!
## Playing
To play the game, just run it with:
./maze4vim.pl
Additional options and configurations available. View them with:
./maze4vim.pl --help
| 21.5625 | 89 | 0.762319 | eng_Latn | 0.985508 |
93448330526d6f5c67af3b101e3b494f72ef8e1b | 49 | md | Markdown | problems/twostones/README.md | michelefenu/kattis | a0fde066f465af858565157551fc6c981b55fc1c | [
"Unlicense"
] | null | null | null | problems/twostones/README.md | michelefenu/kattis | a0fde066f465af858565157551fc6c981b55fc1c | [
"Unlicense"
] | null | null | null | problems/twostones/README.md | michelefenu/kattis | a0fde066f465af858565157551fc6c981b55fc1c | [
"Unlicense"
] | null | null | null | Problem: https://open.kattis.com/problems/autori
| 24.5 | 48 | 0.795918 | ind_Latn | 0.114226 |
9344cfbcf561d321566110c87b0f4a02a8c083ca | 6,748 | md | Markdown | CCoreBook/ch05-01-defining-structs.md | ccore-lang/book | f5a892bb354be7f8106d91cfdac2072d062fa204 | [
"MIT"
] | null | null | null | CCoreBook/ch05-01-defining-structs.md | ccore-lang/book | f5a892bb354be7f8106d91cfdac2072d062fa204 | [
"MIT"
] | null | null | null | CCoreBook/ch05-01-defining-structs.md | ccore-lang/book | f5a892bb354be7f8106d91cfdac2072d062fa204 | [
"MIT"
] | null | null | null | ## Defining and Instantiating Classes
Classes are similar to tuples, which were discussed in Chapter 3. Like tuples, the pieces of a class can be different types. Unlike with tuples, you’ll name each piece of data so it’s clear what the values mean. As a result of these names, classes are more flexible than tuples: you don’t have to rely on the order of the data to specify or access the values of an instance.
To define a class, we enter the keyword `class` and name the entire class. A class’ name should describe the significance of the pieces of data being grouped together. Then, inside curly brackets, we define the names and types of the pieces of data, which we call *fields*. For example, Listing 5-1 shows a class that stores information about a user account:
```csharp
class User
{
string Username;
string Email;
int SignInCount;
bool Active;
}
```
<span class="caption">Listing 5-1: A `User` class definition</span>
To use a class after we’ve defined it, we create an *instance* of that class by specifying concrete values for each of the fields. We create an instance by stating the name of the class and then add curly brackets containing `key = value` pairs, where the keys are the names of the fields and the values are the data we want to store in those fields. We don’t have to specify the fields in the same order in which we declared them in the class. In other words, the class definition is like a general template for the type, and instances fill in that template with particular data to create values of the type. For example, we can declare a particular user as shown in Listing 5-2:
```csharp
class User
{
mut string Username;
mut string Email;
mut int SignInCount;
mut bool Active;
}
var user1 = User {
Email = $"[email protected]",
Username = $"someusername123",
Active = true,
SignInCount = 1,
};
```
<span class="caption">Listing 5-2: Creating an instance of the `User` class</span>
To get a specific value from a class, we can use dot notation. If we wanted just this user’s email address, we could use `user1.Email` wherever we wanted to use this value. If the instance is mutable, we can change a value by using the dot notation and assigning into a particular field. Listing 5-3 shows how to change the value in the `Email` field of a mutable `User` instance:
```csharp
class User
{
mut string Username;
mut string Email;
mut int SignInCount;
mut bool Active;
}
mut var user1 = User {
Email = $"[email protected]",
Username = $"someusername123",
Active = true,
SignInCount = 1,
};
user1.Email = $"[email protected]";
```
<span class="caption">Listing 5-3: Changing the value in the `Email` field of a `User` instance</span>
Note that the entire instance must be mutable.
As with any expression, we can construct a new instance of the class as the single expression in the function body to return that new instance. Listing 5-4 shows a `BuildUser` function that returns a `User` instance with the given email and username. The `Active` field gets the value of `true`, and the `SignInCount` gets a value of `1`.
```csharp
class User
{
mut string Username;
mut string Email;
mut int SignInCount;
mut bool Active;
}
func User BuildUser(string email, string username) =>
User {
Email = email,
Username = username,
Active = true,
SignInCount = 1,
};
```
<span class="caption">Listing 5-4: A `BuildUser` function that takes an email and username and returns a `User` instance</span>
### Tuple Classes without Named Fields to Create Different Types
You can also define classes that look similar to tuples, called *tuple classes*. Tuple classes have the added meaning the class name provides but don’t have names associated with their fields; rather, they just have the types of the fields. Tuple classes are useful when you want to give the whole tuple a name and make the tuple be a different type than other tuples, and naming each field as in a regular class would be verbose or redundant.
To define a tuple class start with the `class` keyword and the class name followed by the types in the tuple. For example, here are definitions and usages of two tuple classes named `Color` and `Point`:
```csharp
class Color(int, int, int);
class Point(int, int, int);
var black = Color(0, 0, 0);
var origin = Point(0, 0, 0);
```
Note that the `black` and `origin` values are different types, because they’re instances of different tuple classes. Each class you define is its own type, even though the fields within the class have the same types. For example, a function that takes a parameter of type `Color` cannot take a `Point` as an argument, even though both types are made up of three `int` values. Otherwise, tuple class instances behave like tuples: you can destructure them into their individual pieces, you can use a `.` followed by the index to access an individual value, and so on.
### Void-Like Classes Without Any Fields
You can also define classes that don’t have any fields! These are called *void-like classes* because they behave similarly to the `void` type. Void-like classes can be useful in situations in which you need to implement a trait on some type but don’t have any data that you want to store in the type itself. We’ll discuss traits in Chapter 10.
> ### Ownership of Class Data
>
> In the `User` class definition in Listing 5-1, we used the owned `string` type rather than the `char[]&` string slice type. This is a deliberate choice because we want instances of this class to own all of its data and for that data to be valid for as long as the entire class is valid.
>
> It’s possible for classes to store references to data owned by something else, but to do so requires the use of *lifetimes*, a CCore feature that we’ll discuss in Chapter 10. Lifetimes ensure that the data referenced by a class is valid for as long as the class is. Let’s say you try to store a reference in a class without specifying lifetimes, like this, which won’t work:
>
> <span class="filename">Filename: src/Main.cc</span>
>
> ```csharp,ignore
> class User
> {
> char[] &Username,
> char[] &Email,
> int SignInCount,
> bool Active,
> }
>
> func void Main() {
> mut var user1 = User {
> &Username = "someusername123",
> &Email = "[email protected]",
> Active = true,
> SignInCount = 1,
> };
> }
> ```
>
> The compiler will complain that it needs lifetime specifiers.
>
> In Chapter 10, we’ll discuss how to fix these errors so you can store > references in classes, but for now, we’ll fix errors like these using owned > types like `string` instead of references like `char[]&`.
| 49.255474 | 680 | 0.729401 | eng_Latn | 0.9989 |
93453503a6f72b67682522114ba8c7a6a8e35dfb | 10,143 | md | Markdown | articles/iot-hub/tutorial-manual-failover.md | yagmoth555/azure-docs.fr-fr | e31c25823e5628d0914065fe815c00e40caafb75 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-hub/tutorial-manual-failover.md | yagmoth555/azure-docs.fr-fr | e31c25823e5628d0914065fe815c00e40caafb75 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/iot-hub/tutorial-manual-failover.md | yagmoth555/azure-docs.fr-fr | e31c25823e5628d0914065fe815c00e40caafb75 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Basculement manuel d’un Azure IoT hub | Microsoft Docs
description: Montrer comment effectuer un basculement manuel pour un Azure IoT hub
author: robinsh
manager: timlt
ms.service: iot-hub
services: iot-hub
ms.topic: tutorial
ms.date: 07/11/2018
ms.author: robinsh
ms.custom: mvc
ms.openlocfilehash: f0e8bf922f142b795dd1a2ded4b3ec265c43481a
ms.sourcegitcommit: 156364c3363f651509a17d1d61cf8480aaf72d1a
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 07/25/2018
ms.locfileid: "39249992"
---
# <a name="tutorial-perform-manual-failover-for-an-iot-hub-public-preview"></a>Didacticiel : Effectuer un basculement manuel pour un IoT hub (préversion publique)
Basculement manuel est une fonctionnalité du service IoT Hub qui permet aux clients le[basculement](https://en.wikipedia.org/wiki/Failover) des opérations de leur hub à partir d’une région primaire vers la région Azure associée géographiquement correspondante. Basculement manuel est possible en cas de sinistre régional ou une panne de service étendue. Vous pouvez également effectuer un basculement planifié pour tester vos capacités de récupération d’urgence, mais nous vous recommandons d’utiliser un IoT hub de test plutôt que celui en cours d’exécution en production. La fonctionnalité de basculement manuel est proposée aux clients sans coût supplémentaire.
Dans ce didacticiel, vous allez effectuer les tâches suivantes :
> [!div class="checklist"]
> * Créez un hub IoT, à l’aide du portail Azure.
> * Effectuer un basculement.
> * Consultez le hub en cours d’exécution dans l’emplacement secondaire.
> * Effectuer une restauration automatique pour ramener les opérations d’IoT hub à l’emplacement principal.
> * Confirmer que le hub s’exécute correctement dans l’emplacement approprié.
## <a name="prerequisites"></a>Prérequis
- Un abonnement Azure. Si vous n’avez pas d’abonnement Azure, créez un [compte gratuit](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) avant de commencer.
## <a name="create-an-iot-hub"></a>Créer un hub IoT
1. Connectez-vous au [portail Azure](https://portal.azure.com).
2. Cliquez sur **+ Créer une ressource** et sélectionnez **Internet des objets**, puis **IoT Hub**.
3. Sélectionnez l’onglet **Fonctions de base**. Complétez les champs suivants.
**Abonnement** : sélectionnez l’abonnement Azure que vous souhaitez utiliser.
**Groupe de ressources** : cliquez sur **Créer nouveau** et spécifiez **ManIFailRG** pour le nom du groupe de ressources.
**Région**: sélectionnez une région proche de vous fait partie de la préversion. Ce didacticiel utilise`westus2`. Un basculement ne peut être effectué entre des régions Azure géographiquement associées. La région géographiquement associée à westus2 est WestCentralUS.
> [!NOTE]
> Le basculement manuel est actuellement en préversion publique et *pas* disponible dans les régions Azure suivantes : USA Est, USA Ouest, Europe Nord, Europe Ouest, Brésil Sud et USA Centre Sud.
**Nom de IoT Hub** : spécifiez un nom pour votre IoT Hub. Le nom du hub doit être globalement unique.
Cliquez sur **Revoir + créer**. (Il utilise les valeurs par défaut pour la taille et échelle.)
4. Passez en revue les informations, puis cliquez sur **Créer** pour créer l’IoT hub.
## <a name="perform-a-manual-failover"></a>Effectuer un basculement manuel
Notez qu’il existe une limite de deux basculements et deux restaurations par jour pour un IoT Hub.
1. Cliquez sur **Groupes de ressources** et sélectionnez le groupe de ressources **ManlFailRG**. Dans la liste des ressources, cliquez sur votre IoT Hub.
2. Sous **Résilience** dans le volet de IoT Hub, cliquez sur **Basculement manuel (préversion)**. Notez que si votre hub n’est pas configuré dans une région valide, l’option de basculement manuel va être désactivée.
3. Dans le volet de Basculement manuel, vous voyez **l’Emplacement principal de l’IoT Hub** et **l’emplacement secondaire de l’IoT Hub** . L’emplacement principal est initialement défini à l’emplacement spécifié lorsque vous avez créé l’IoT hub et indique toujours l’emplacement dans lequel le hub est actuellement actif. L’emplacement secondaire est le standard [région Azure géographiquement associée ](../best-practices-availability-paired-regions.md) qui est associé à l’emplacement principal. Vous ne pouvez pas modifier les valeurs de l’emplacement. Pour ce didacticiel, l’emplacement principal est `westus2` et l’emplacement secondaire est `WestCentralUS`.
3. En haut du volet de Basculement manuel, cliquez sur **Lancer le basculement**. Vous voyez le volet **Confirmer le basculement manuel**. Complétez le nom de votre IoT hub pour vérifier que c’est bien celui que vous souhaitez basculer. Ensuite, pour lancer le basculement, cliquez sur **OK**.
La quantité de temps nécessaire pour effectuer le basculement manuel est proportionnelle au nombre d’appareils qui sont inscrits pour votre hub. Par exemple, si vous avez 100 000 appareils,cela peut prendre 15 minutes, mais si vous avez cinq millions d’appareils, cela peut prendre une heure ou plus.
4. Dans le volet**Confirmer le basculement manuel**, complétez le nom de votre IoT hub pour vérifier que c’est bien celui que vous souhaitez basculer. Ensuite, pour lancer le basculement, cliquez sur OK.
Lorsque le processus de basculement manuel est en cours d’exécution, il existe une bannière dans le volet Basculement manuel qui vous indique qu’un basculement manuel est en cours d’exécution.
Si vous fermez le volet de IoT Hub et que vous l’ouvrez à nouveau en cliquant dessus dans le volet Groupe de ressources, vous voyez une bannière qui vous indique que le hub n'est pas actif.
Une fois terminé, les régions primaires et secondaires sur la page de Basculement manuel sont retournées et le hub est à nouveau actif. Pour cet exemple, l’emplacement principal est maintenant `WestCentralUS` et l’emplacement secondaire est maintenant `westus2`.
## <a name="perform-a-failback"></a>Effectuer une restauration automatique
Une fois que vous avez effectué un basculement manuel, vous pouvez basculer des opérations de hub vers la région primaire d’origine, il s’agit d’une restauration automatique. Si vous venez d’exécuter un basculement, vous devez patienter environ une heure avant de pouvoir déposer une requête de restauration automatique. Si vous essayez d’effectuer la restauration automatique dans un délai plus court, un message d’erreur s’affichera.
Une restauration automatique est effectuée à l’instar d’un basculement manuel. Voici les étapes :
1. Pour effectuer une restauration automatique, retournez dans le volet de Iot Hub pour votre Iot Hub.
2. Sous **Résilience** dans le volet de IoT Hub, cliquez sur **Basculement manuel (préversion)**.
3. En haut du volet de Basculement manuel, cliquez sur **Lancer le basculement**. Vous voyez le volet **Confirmer le basculement manuel**.
4. Dans le volet**Confirmer le basculement manuel**, complétez le nom de votre IoT hub pour vérifier que c’est bien celui que vous souhaitez restaurer. Pour ensuite lancer la restauration automatique, cliquez sur OK.
Les bannières sont affichées comme expliqué dans la section [Effectuer un basculement](#perform-a-failover). Une fois la restauration automatique terminée, il affiche à nouveau `westus2` comme emplacement principal et `WestCentralUS` comme emplacement secondaire,comme défini à l’origine.
## <a name="clean-up-resources"></a>Supprimer les ressources
Pour supprimer toutes les ressources que vous avez créées, supprimez le groupe de ressources. Cette opération supprime toutes les ressources contenues dans le groupe. Dans le cas présent, l’Iot hub et le groupe de ressources sont supprimés.
1. Cliquez sur **Groupes de ressources**.
2. Recherchez et sélectionnez le groupe de ressource **ManlFailRG**. Cliquez sur le compte pour l’ouvrir.
3. Cliquez sur **Supprimer le groupe de ressources**. Lorsque vous y êtes invité, entrez le nom du groupe de ressources et cliquez sur **Supprimer** pour confirmer.
## <a name="next-steps"></a>Étapes suivantes
Dans ce didacticiel, vous avez appris comment configurer et effectuer un basculement manuel, et comment déposer une requête de restauration automatique en effectuant les tâches suivantes :
> [!div class="checklist"]
> * Créez un IoT hub, à l’aide du portail Azure.
> * Effectuer un basculement.
> * Consultez le hub en cours d’exécution dans l’emplacement secondaire.
> * Effectuer une restauration automatique pour ramener les opérations d’IoT hub à l’emplacement principal.
> * Confirmer que le hub s’exécute correctement dans l’emplacement approprié.
Passez au didacticiel suivant pour découvrir comment gérer l’état d’un appareil IoT.
> [!div class="nextstepaction"]
[Gérer l’état d’un appareil IoT](tutorial-device-twins.md) | 71.93617 | 664 | 0.780341 | fra_Latn | 0.99125 |
93453eb1171b8bb9b4cd2deeeac7e3d2bc77ff93 | 11,571 | md | Markdown | _posts/2017-03-09-在扩展类中添加弱引用类型的属性.md | jxd524/jxd524.github.io | 2604be850709dea57078ed3654b460e76a3879be | [
"MIT"
] | 2 | 2019-06-27T06:54:06.000Z | 2019-07-20T07:46:53.000Z | _posts/2017-03-09-在扩展类中添加弱引用类型的属性.md | jxd524/jxd524.github.io | 2604be850709dea57078ed3654b460e76a3879be | [
"MIT"
] | null | null | null | _posts/2017-03-09-在扩展类中添加弱引用类型的属性.md | jxd524/jxd524.github.io | 2604be850709dea57078ed3654b460e76a3879be | [
"MIT"
] | null | null | null | ---
layout: post
title: "在扩展类中添加弱引用类型的属性"
author: Terry
date: 2017-03-08 11:20
categories: iOS
tags: 扩展类 弱引用 运行时 extension week runtime
---
* content
{:toc}
# 扩展类中添加属性
一般需要有个成员变量来保存数据，此时就需要用到运行时库了。只要用到的运行时函数有**objc_getAssociatedObject**，**objc_setAssociatedObject**。这两个函数有个参数是 **key** 是一个 const void * 的类型。你可以直接定义，或者是使用**class_getClassMethod**, **class_getInstanceMethod** 来当成 **key** 使用
运行时库没有提供弱引用的方式，只有如下定义
```objc
/* Associative References */
/**
* Policies related to associative references.
* These are options to objc_setAssociatedObject()
*/
typedef OBJC_ENUM(uintptr_t, objc_AssociationPolicy) {
OBJC_ASSOCIATION_ASSIGN = 0, /**< Specifies a weak reference to the associated object. */
OBJC_ASSOCIATION_RETAIN_NONATOMIC = 1, /**< Specifies a strong reference to the associated object.
* The association is not made atomically. */
OBJC_ASSOCIATION_COPY_NONATOMIC = 3, /**< Specifies that the associated object is copied.
* The association is not made atomically. */
OBJC_ASSOCIATION_RETAIN = 01401, /**< Specifies a strong reference to the associated object.
* The association is made atomically. */
OBJC_ASSOCIATION_COPY = 01403 /**< Specifies that the associated object is copied.
* The association is made atomically. */
};
```
# 扩展类中添加弱引用属性
首先要知道，为对象A关联一个动态属性B,那么当A被释放时，此时B若没有被其它对象引用，那么B也会被释放。这是我们解决弱引用的关键。简单描述下要实现的过程，后面会放上代码
假设有以下等式和类C，其中A和B为对象，weakObject是A的弱引用属性，key是关联的关键词, 类C非常简单，只需要在释放时去取消指定的关联
```objc
A.weakObject = B
//类C的伪实现
@interface C : NSObject
@property (nonatomic, weak) id object;
@property (nonatomic, assign) const void * key;
@end
@implementation C
- (void)dealloc
{
if (self.object && self.key)
{
objc_setAssociatedObject(self.object, self.key, nil, OBJC_ASSOCIATION_ASSIGN);
}
}
@end
```
## 关键的实现步骤
为实现此操作，需要有以下步骤
1. A关联B，对应操作：objc_setAssociatedObject(A, key, B, OBJC_ASSOCIATION_ASSIGN);
2. B关联自释放对象C: objc_setAssociatedObject(B, key, c1, OBJC_ASSOCIATION_RETAIN_NONATOMIC);
3. A关联自释放对象C: objc_setAssociatedObject(A, key, c2, OBJC_ASSOCIATION_RETAIN_NONATOMIC);
步骤1：为了用户可以存储变量
步骤2：当B被释放时，自动把与A关联的数据清除,此时要清空两处，一个为对应属性，一个辅助数据（步骤3创建的）
步骤3：当A本身被释放，但是B还存在时，可以清除B中被A关联的信息，此时只需要清空B的数据(步骤2创建)
可能会有些绕口，简单来说就是A挂了，就把B里有关A的信息清除；若是B挂了，就把A里的信息清除
当然还有其它事情要处理，其它的具体见以下Demo例子：
```objc
/******************************************************************************************
类名: JxAutoReleaseAssociated
说明: 用于辅助释放指定的关联
******************************************************************************************/
#pragma mark - ✍️JxAutoReleaseAssociated
@interface JxAutoReleaseAssociated : NSObject
@property (nonatomic, weak) id object1;
@property (nonatomic, assign) const void * key1;
@property (nonatomic, weak) id object2;
@property (nonatomic, assign) const void * key2;
@end
@implementation JxAutoReleaseAssociated
- (instancetype)init
{
self = [super init];
logoutObject(self);
return self;
}
- (void)dealloc
{
if (self.object1 && self.key1)
{
objc_setAssociatedObject(self.object1, self.key1, nil, OBJC_ASSOCIATION_ASSIGN);
}
if (self.object2 && self.key2)
{
objc_setAssociatedObject(self.object2, self.key2, nil, OBJC_ASSOCIATION_ASSIGN);
}
logoutObject(self);
}
@end
/******************************************************************************************
类名: MyObject
说明: 测试类
******************************************************************************************/
#pragma mark - ✍️MyObject
@interface MyObject : NSObject
@end
@implementation MyObject
- (instancetype)init
{
self = [super init];
logoutObject(self);
return self;
}
- (void)dealloc
{
logoutObject(self);
}
@end
/******************************************************************************************
类名: MyObject(Jx)
说明: 测试类的扩展类
******************************************************************************************/
#pragma mark - ✍️MyObject(Jx)
@interface MyObject(Jx)
@property (nonatomic, weak) id weakObject;
@end
@implementation MyObject(Jx)
- (id)weakObject
{
const void *key = class_getInstanceMethod([self class], @selector(weakObject));
return objc_getAssociatedObject(self, key);
}
- (void)setWeakObject:(id)aWeakObject
{
id previousWeakObject = self.weakObject;
if (previousWeakObject != aWeakObject)
{
const void *key = class_getInstanceMethod([self class], @selector(weakObject));
const void *clearAssObjKey = class_getInstanceMethod([self class], @selector(setWeakObject:));
if (previousWeakObject)
{
//清除之前关联的信息
JxAutoReleaseAssociated *assObj = objc_getAssociatedObject(previousWeakObject, key);
if (assObj && [assObj isKindOfClass:[JxAutoReleaseAssociated class]])
{
objc_setAssociatedObject(previousWeakObject, key, nil, OBJC_ASSOCIATION_RETAIN_NONATOMIC);
}
}
if (aWeakObject)
{
//关联弱引用对象 self->key->aWeakObject
objc_setAssociatedObject(self, key, aWeakObject, OBJC_ASSOCIATION_ASSIGN);
//当aWeakObject释放时：清空self对象的属性，相关数据
JxAutoReleaseAssociated *obj = [[JxAutoReleaseAssociated alloc] init];
obj.object1 = self;
obj.key1 = key;
obj.object2 = self;
obj.key2 = clearAssObjKey;
objc_setAssociatedObject(aWeakObject, key, obj, OBJC_ASSOCIATION_RETAIN_NONATOMIC);
//为self关联自释放对象：当本身释放时，清除已关联的对象的数据 self->clearAssObjKey->pWeakObject
obj = [[JxAutoReleaseAssociated alloc] init];
obj.object1 = aWeakObject;
obj.key1 = key;
objc_setAssociatedObject(self, clearAssObjKey, obj, OBJC_ASSOCIATION_RETAIN_NONATOMIC);
}
}
}
@end
```
## 以宏实现，方便使用
```objc
typedef void(^JxEmptyBlock)();
/***********************************************************************
File : JxAutoRunBlockWhenFree
Author : Terry
Email : [email protected]
CreateTime : 2017-03-09 14:34
LastModify :
Description: 当对象被释放时，自动执行相应的回调
************************************************************************/
#import <Foundation/Foundation.h>
@interface JxAutoRunBlockWhenFree : NSObject
+ (JxAutoRunBlockWhenFree *)Create:(JxEmptyBlock)aBlock;
@end
@implementation JxAutoRunBlockWhenFree
{
JxEmptyBlock mDeallocBlock;
}
- (instancetype)initWithDeallocBlock:(JxEmptyBlock)aDeallocBlock
{
self = [super init];
mDeallocBlock = aDeallocBlock;
return self;
}
- (void)dealloc
{
if (mDeallocBlock) mDeallocBlock();
}
+ (JxAutoRunBlockWhenFree *)Create:(JxEmptyBlock)aBlock
{
return [[JxAutoRunBlockWhenFree alloc] initWithDeallocBlock:aBlock];
}
@end
/**
定义弱引用的动态时属性
@param aName 获取
@param aSetter 设置
@param aType 类型
使用例子
RuntimeWeakImpl(weakObject, setWeakObject, id);
使用
A.weakObject = B;
当Ａ或Ｂ被释放时，会清除相应的数据
*/
#define RuntimeWeakImpl(aName, aSetter, aType) \
- (aType)aName{ \
const void *key = class_getInstanceMethod([self class], @selector(aName)); \
return objc_getAssociatedObject(self, key); \
} \
- (void)aSetter:(id)aWeakObject { \
id previousWeakObject = [self aName]; \
if (previousWeakObject != aWeakObject) { \
const void *key = class_getInstanceMethod([self class], @selector(aName)); \
const void *clearAssObjKey = class_getInstanceMethod([self class], @selector(aSetter:)); \
if (previousWeakObject) { \
JxAutoRunBlockWhenFree *assObj = objc_getAssociatedObject(previousWeakObject, key); \
if (assObj && [assObj isKindOfClass:[JxAutoRunBlockWhenFree class]]) { \
objc_setAssociatedObject(previousWeakObject, key, nil, OBJC_ASSOCIATION_RETAIN_NONATOMIC); \
} \
} \
if (aWeakObject) { \
__weak typeof(self) pWeakSelf = self; \
__weak typeof(aWeakObject) pWeakObject = aWeakObject; \
objc_setAssociatedObject(self, key, aWeakObject, OBJC_ASSOCIATION_ASSIGN); \
JxAutoRunBlockWhenFree *obj = [JxAutoRunBlockWhenFree Create:^{ \
__strong typeof(pWeakSelf) pSelf = pWeakSelf; \
if (pSelf){ \
objc_setAssociatedObject(pSelf, key, nil, 0); \
objc_setAssociatedObject(pSelf, clearAssObjKey, nil, 0); \
} \
}]; \
objc_setAssociatedObject(aWeakObject, key, obj, OBJC_ASSOCIATION_RETAIN_NONATOMIC); \
obj = [JxAutoRunBlockWhenFree Create:^{ \
__strong typeof(pWeakObject) pObject = pWeakObject; \
if (pObject){ \
objc_setAssociatedObject(pObject, key, nil, 0); \
} \
}]; \
objc_setAssociatedObject(self, clearAssObjKey, obj, OBJC_ASSOCIATION_RETAIN_NONATOMIC); \
} \
} \
}
```
实现上使用例子
```objc
/******************************************************************************************
类名: MyObject(Jx)
说明: 测试类的扩展类
******************************************************************************************/
#pragma mark - ✍️MyObject(Jx)
@interface MyObject(Jx)
@property (nonatomic, weak) id weakObject;
@end
@implementation MyObject(Jx)
RuntimeWeakImpl(weakObject, setWeakObject, id);
@end
mTestObject2 = [[MyObject alloc] init];
mTestObject2.weakObject = mTestObject;
```
结束
| 34.85241 | 221 | 0.501945 | yue_Hant | 0.258433 |
934593304cb78dd9f9684dd293b2edd9def99258 | 1,072 | md | Markdown | _posts/2016-12-07-Creazioni-Elena-1668-Sleeveless-MermaidTrumpet.md | novstylessee/novstylessee.github.io | 4c99fd7f6148fa475871b044a67df2ac0151b9ba | [
"MIT"
] | null | null | null | _posts/2016-12-07-Creazioni-Elena-1668-Sleeveless-MermaidTrumpet.md | novstylessee/novstylessee.github.io | 4c99fd7f6148fa475871b044a67df2ac0151b9ba | [
"MIT"
] | null | null | null | _posts/2016-12-07-Creazioni-Elena-1668-Sleeveless-MermaidTrumpet.md | novstylessee/novstylessee.github.io | 4c99fd7f6148fa475871b044a67df2ac0151b9ba | [
"MIT"
] | null | null | null | ---
layout: post
date: 2016-12-07
title: "Creazioni Elena 1668 Sleeveless Mermaid/Trumpet"
category: Creazioni Elena
tags: [Creazioni Elena ,Creazioni Elena,Mermaid/Trumpet,Cowl,Sleeveless]
---
### Creazioni Elena 1668
Just **$419.99**
### Sleeveless Mermaid/Trumpet
<table><tr><td>BRANDS</td><td>Creazioni Elena</td></tr><tr><td>Silhouette</td><td>Mermaid/Trumpet</td></tr><tr><td>Neckline</td><td>Cowl</td></tr><tr><td>Sleeve</td><td>Sleeveless</td></tr></table>
<a href="https://www.readybrides.com/en/creazioni-elena-/36466-creazioni-elena-1668.html"><img src="//img.readybrides.com/75914/creazioni-elena-1668.jpg" alt="Creazioni Elena 1668" style="width:100%;" /></a>
<!-- break --><a href="https://www.readybrides.com/en/creazioni-elena-/36466-creazioni-elena-1668.html"><img src="//img.readybrides.com/75913/creazioni-elena-1668.jpg" alt="Creazioni Elena 1668" style="width:100%;" /></a>
Buy it: [https://www.readybrides.com/en/creazioni-elena-/36466-creazioni-elena-1668.html](https://www.readybrides.com/en/creazioni-elena-/36466-creazioni-elena-1668.html)
| 67 | 221 | 0.727612 | ita_Latn | 0.19677 |
9345decb8ebd0fb33ff02313be0da644ebaa70e2 | 416 | md | Markdown | _posts/2020-09-04-foto-polmoni-covid19-virus.md | marste/Stefano | aa1f99cc33ba98ed7206b0c6af1994a4915f1e76 | [
"MIT"
] | null | null | null | _posts/2020-09-04-foto-polmoni-covid19-virus.md | marste/Stefano | aa1f99cc33ba98ed7206b0c6af1994a4915f1e76 | [
"MIT"
] | null | null | null | _posts/2020-09-04-foto-polmoni-covid19-virus.md | marste/Stefano | aa1f99cc33ba98ed7206b0c6af1994a4915f1e76 | [
"MIT"
] | null | null | null | ---
title: "Foto dei polmoni dopo aver preso il Covid19"
date: 2020-09-04 19:20:00 +0200
published: true
layout: post
image: 'https://marzorati.co/img/virus.jpg'
share-img: 'https://marzorati.co/img/virus.jpg'
categories: [Salute]
tags: [covid19, foto, polmoni, cicatrici, ecografia, virus]
---
<center><img src="https://marzorati.co/img/post/foto-polmoni-covid19.webp" alt="Foto Polmoni cicatrici Covid19"></center> | 37.818182 | 121 | 0.737981 | ita_Latn | 0.507465 |
9345fb7b5f1dc70ea89017e8263d88363e09909c | 203 | md | Markdown | README.md | wolszakp/tamper-scripts | 0809a219276bb46fcda3ca3db6b655cc2f13e2e5 | [
"MIT"
] | 1 | 2020-06-02T06:57:10.000Z | 2020-06-02T06:57:10.000Z | README.md | wolszakp/tamper-scripts | 0809a219276bb46fcda3ca3db6b655cc2f13e2e5 | [
"MIT"
] | null | null | null | README.md | wolszakp/tamper-scripts | 0809a219276bb46fcda3ca3db6b655cc2f13e2e5 | [
"MIT"
] | null | null | null | # Tamper monkey scripts
This is my list of [TamperMonkey](https://www.tampermonkey.net/) scripts.
* Script to change language from pl-pl localization to en-us [Language changer](pl-to-en-url-changer.js)
| 50.75 | 104 | 0.768473 | eng_Latn | 0.764227 |
93463247298616d6b2da0963b1c6fa515a93cea5 | 37 | md | Markdown | README.md | fahernandez/Hermes | 23c32647d63fb8e22d73ee2038101773299bcf04 | [
"MIT"
] | null | null | null | README.md | fahernandez/Hermes | 23c32647d63fb8e22d73ee2038101773299bcf04 | [
"MIT"
] | 5 | 2016-08-04T18:05:57.000Z | 2016-08-04T19:48:40.000Z | README.md | fahernandez/Hermes | 23c32647d63fb8e22d73ee2038101773299bcf04 | [
"MIT"
] | null | null | null | # Hermes
Go app for mobile messaging
| 12.333333 | 27 | 0.783784 | eng_Latn | 0.510801 |
934642c3763e335913a19133d5a82f52b3384c5f | 2,018 | md | Markdown | README.md | Yukino1010/Transformer_English_Chinese_Translation | e68731d7e846afcb7cf3471d2e57876e208f2999 | [
"MIT"
] | null | null | null | README.md | Yukino1010/Transformer_English_Chinese_Translation | e68731d7e846afcb7cf3471d2e57876e208f2999 | [
"MIT"
] | null | null | null | README.md | Yukino1010/Transformer_English_Chinese_Translation | e68731d7e846afcb7cf3471d2e57876e208f2999 | [
"MIT"
] | null | null | null | # Transformer_English_Chinese_Translation
# transformer
If you want to talk about which model has the biggest contribution to NLP (natural language processing) in recent years,<br>
Transformer will definitely be the first choice.
When the paper 「attention is all you need]」was published in 2017, it caused a big sensation at the time.
Because the transformer only uses the attention mechanism to construct the model, not like the traditional seq2seq model using RNN or CNN.
Through the attention mechanism, it can convert sentences to to semantics well, and then the most important thing is that he can use GPU to perform parallel operations.
It is also because of the emergence of transfomer that many models with better performance have been produced,<br> such as
Bert, Gpt3 etc.
## Network Structure
## Hyperparameters
- BATCH_SIZE = 64
- num_layers = 4
- d_model = 512
- dff = 2048
- num_heads = 8
- dropout_rate = 0.2
## Data
This implementation uses the dataset 「wmt_translate」 from tensorflow dataset, <br>
but only use the sentence lenth < 35.
## Loss and Accuracy
## Result
As you can see on the picture，you can surprisingly found that the model had concentrated on some certain english words when generating chinese words, such as years correspond to "年" on the first subgraph and economiy correspond to "經濟" on head2 、 head5.
## References
1. ***Attention Is All You Need*** [[arxiv](https://arxiv.org/abs/1706.03762)]
2. Transformer model for language understanding [https://www.tensorflow.org/text/tutorials/transformer]
3. ***LeeMeng*** [https://leemeng.tw/neural-machine-translation-with-transformer-and-tensorflow2.html]
| 39.568627 | 253 | 0.786422 | eng_Latn | 0.987167 |
9346adc60c5550440b7359d708e7ddec83ad018f | 389 | md | Markdown | poems/2019-10-03/index.md | Kaiguang/renyu-li | 836e95ec5d3ae35115ae199e8e51c988cae2370b | [
"MIT"
] | null | null | null | poems/2019-10-03/index.md | Kaiguang/renyu-li | 836e95ec5d3ae35115ae199e8e51c988cae2370b | [
"MIT"
] | 2 | 2021-05-23T13:17:30.000Z | 2021-10-11T20:33:13.000Z | poems/2019-10-03/index.md | Kaiguang/fgjhsq-com | f1829981dec44db2a9f27ddbb370a95d72942b85 | [
"MIT"
] | null | null | null | ---
title: 沁园春·70年国庆华诞观礼有感
author: 放歌江海山阙
date: 2019-10-03
poem: |
十里长街，如涌人潮，旗海桂香。听振聋礼炮，声声发馈；城楼上下，喜气洋洋。呼啸雄鹰，轰鸣铁甲，长剑东风巨浪彰。贺华诞，瞰彩车方阵，思绪卷翻。
中华百载沧桑，为站立英雄血染苍。昔一穷二白，列强封锁；披星戴月，斩棘登攀。春风化雨，洗涤左霾，竞发千帆百业昌。新时代，铸复兴伟业，吾辈共襄！
---
2019 年 10 月 1 日，有幸成为学校教师代表，受邀成为观礼嘉宾，深感荣幸和骄傲！目睹盛况，见证历史，心潮澎湃！特填词记之。
诗人张树松点评：国庆阅兵场面浩大，非大手笔殆不能状。上片有声有色，有人有物，楼上楼下，天空地下，尽入笔端，不愧作手。上片以思绪卷翻做结，引出下片回顾近代历史，感慨万千，展望未来，逸兴遄飞。观礼诗词之良构也。
| 27.785714 | 103 | 0.773779 | yue_Hant | 0.353105 |
934725612c830730d3b874e10aaa4ee48f68c477 | 1,568 | md | Markdown | dev-itpro/developer/methods-auto/system/system-createencryptionkey-method.md | KennieNP/dynamics365smb-devitpro-pb | bbcdc1df447ab16f28eab0a9aa02b5a3b066520b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | dev-itpro/developer/methods-auto/system/system-createencryptionkey-method.md | KennieNP/dynamics365smb-devitpro-pb | bbcdc1df447ab16f28eab0a9aa02b5a3b066520b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | dev-itpro/developer/methods-auto/system/system-createencryptionkey-method.md | KennieNP/dynamics365smb-devitpro-pb | bbcdc1df447ab16f28eab0a9aa02b5a3b066520b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "CreateEncryptionKey Method"
ms.author: solsen
ms.custom: na
ms.date: 02/03/2020
ms.reviewer: na
ms.suite: na
ms.tgt_pltfrm: na
ms.topic: article
ms.service: "dynamics365-business-central"
author: SusanneWindfeldPedersen
---
[//]: # (START>DO_NOT_EDIT)
[//]: # (IMPORTANT:Do not edit any of the content between here and the END>DO_NOT_EDIT.)
[//]: # (Any modifications should be made in the .xml files in the ModernDev repo.)
# CreateEncryptionKey Method
Creates an encryption key for the current tenant.
## Syntax
```
[Ok := ] System.CreateEncryptionKey()
```
> [!NOTE]
> This method can be invoked without specifying the data type name.
## Return Value
*Ok*
 Type: [Boolean](../boolean/boolean-data-type.md)
**true** if the operation was successful; otherwise **false**. If you omit this optional return value and the operation does not execute successfully, a runtime error will occur.
[//]: # (IMPORTANT: END>DO_NOT_EDIT)
## Remarks
If a key already exists, the following error will be displayed: **Unable to create a new encryption key. An encryption key already exists**.
## Example
This code example creates an encryption key for the current tenant. It uses the [ENCRYPTIONENABLED](../../methods-auto/system/system-encryptionenabled-method.md) method to perform a check.
```
if not ENCRYPTIONENABLED then
CREATEENCRYPTIONKEY();
```
## See Also
[System Data Type](system-data-type.md)
[Getting Started with AL](../../devenv-get-started.md)
[Developing Extensions](../../devenv-dev-overview.md) | 32 | 191 | 0.718112 | eng_Latn | 0.897252 |
9347e73f1a2844a350c3238d78d5b95250eed33c | 5,326 | md | Markdown | articles/service-bus-messaging/service-bus-outages-disasters.md | Yueying-Liu/mc-docs.zh-cn | 21000ea687a4cda18cecf10e9183fd2172918bb5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/service-bus-messaging/service-bus-outages-disasters.md | Yueying-Liu/mc-docs.zh-cn | 21000ea687a4cda18cecf10e9183fd2172918bb5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/service-bus-messaging/service-bus-outages-disasters.md | Yueying-Liu/mc-docs.zh-cn | 21000ea687a4cda18cecf10e9183fd2172918bb5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 使 Azure 服务总线应用程序免受服务中断和灾难影响
description: 本文提供了用于保护应用程序免受潜在的 Azure 服务总线中断影响的技术。
ms.topic: article
origin.date: 06/23/2020
ms.date: 08/31/2020
ms.testscope: yes|no
ms.testdate: 07/20/2020
ms.author: v-yeche
author: rockboyfor
ms.openlocfilehash: b3a8a2e74cc44aad158b2634473ffb5983d801e1
ms.sourcegitcommit: b5ea35dcd86ff81a003ac9a7a2c6f373204d111d
ms.translationtype: HT
ms.contentlocale: zh-CN
ms.lasthandoff: 08/27/2020
ms.locfileid: "88946940"
---
# <a name="best-practices-for-insulating-applications-against-service-bus-outages-and-disasters"></a>使应用程序免受服务总线中断和灾难影响的最佳实践
任务关键型应用程序必须连续运行，即使是在计划外中断或灾难发生时。 本文介绍可用于保护服务总线应用程序免受潜在的服务中断和灾难影响的技术。
中断定义为 Azure 服务总线暂时不可用。 中断会影响服务总线的一些组件，例如消息存储空间，甚至整个数据中心。 问题解决后，服务总线恢复可用。 通常情况下，中断不会导致消息或其他数据丢失。 组件故障的一个示例是特定的消息存储空间不可用。 数据中心范围中断的示例有数据中心电源故障或数据中心网络交换机故障。 中断可能会持续几分钟到几天的时间。
灾难定义为服务总线缩放单元或数据中心永久丢失。 数据中心可能会也可能不会恢复可用。 通常，灾难会导致消息或其他数据的部分或全部丢失。 灾难的示例包括火灾、洪灾或地震。
## <a name="protecting-against-outages-and-disasters---service-bus-premium"></a>防范中断和灾难 - 服务总线高级版
高可用性和灾难恢复概念直接内置到 Azure 服务总线高级层中，无论是在同一区域中（通过可用性区域）还是跨不同的区域（通过异地灾难恢复）都可以实现。
### <a name="geo-disaster-recovery"></a>异地灾难恢复
服务总线高级版支持命名空间级别的异地灾难恢复。 有关详细信息，请参阅 [Azure 服务总线异地灾难恢复](service-bus-geo-dr.md)。 灾难恢复功能仅适用于[高级 SKU](service-bus-premium-messaging.md)，可实现元数据灾难恢复，并且依赖于主要和辅助灾难恢复命名空间。
<!--Not Available on ### Availability Zones-->
## <a name="protecting-against-outages-and-disasters---service-bus-standard"></a>防范中断和灾难 - 服务总线标准版
为了在使用标准消息传送定价层时实现针对数据中心中断的恢复，服务总线支持两种方法：主动和被动复制。 对于每一种方法，如果必须在数据中心中断的情况下仍可访问给定的队列或主题，可以在两个命名空间中创建。 两个实体可以具有相同的名称。 例如，可在 **contosoPrimary.servicebus.chinacloudapi.cn/myQueue** 下访问主要队列，而在 **contosoSecondary.servicebus.chinacloudapi.cn/myQueue** 下访问其辅助队列。
>[!NOTE]
> **主动复制**和**被动复制**设置是常规用途解决方案，不是服务总线的特定功能。 复制逻辑（发送到 2 个不同的命名空间）存在于发送方应用程序上，而接收方必须具有用于检测重复项的自定义逻辑。
如果应用程序不需要发送方到接收方的持续通信，则该应用程序可实施一个用于防止消息丢失的持久客户端队列，从而保护发送方免受任何暂时性服务总线故障的影响。
### <a name="active-replication"></a>主动复制
主动复制对于每个操作都使用这两个命名空间中的实体。 任何发送消息的客户端都会发送同一条消息的两个副本。 第一个副本发送到主要实体（例如 **contosoPrimary.servicebus.chinacloudapi.cn/sales**），该消息的第二个副本发送到辅助实体（例如 **contosoSecondary.servicebus.chinacloudapi.cn/sales**）。
客户端从两个队列接收消息。 如果接收方处理了消息的第一个副本，则第二个副本会被取消。 要取消重复的消息，发送方必须用唯一标识符标记每一条消息。 必须用同一标识符标记消息的两个副本。 可使用 [BrokeredMessage.MessageId][BrokeredMessage.MessageId] 或 [BrokeredMessage.Label][BrokeredMessage.Label] 属性或自定义属性对消息进行标记。 接收方必须保留已接收消息的列表。
[使用服务总线标准层进行异地复制][Geo-replication with Service Bus Standard Tier]示例演示了消息传送实体的主动复制。
> [!NOTE]
> 主动复制方法会使操作数加倍，因此这种方法可能导致成本上升。
>
>
### <a name="passive-replication"></a>被动复制
在无故障的情况下，被动复制仅使用两个消息传送实体之一。 客户端将消息发送给活动实体。 如果针对活动实体的操作失败并返回错误代码，表明承载活动实体的数据中心可能不可用，则客户端将该消息的副本发送到备份实体。 此时，活动实体与备份实体互换角色：进行发送的客户端将旧的活动实体认定为新的备份实体，而将旧的备份实体认定为新的活动实体。 如果两次发送操作都失败，则两个实体的角色将保持不变并返回错误。
客户端从两个队列接收消息。 因为接收方可能接收同一条消息的两个副本，所以接收方必须取消重复消息。 可通过与主动复制中所述的相同方式取消重复消息。
一般来说，被动复制比主动重复更经济，因为在大多数情况下仅执行一个操作。 延迟、吞吐量和货币成本均与非复制场景相同。
使用被动复制时，在以下情况下可能丢失消息或接收两次：
* **消息延迟或丢失**：假定发送方将消息 m1 成功发送到主要队列，而该队列在接收方接收 m1 之前变为不可用。 发送方将后续消息 m2 发送给辅助队列。 如果主要队列是暂时不可用，则接收方会在该队列恢复可用后接收 m1。 如果发生灾难，则接收方可能永远无法接收 m1。
* **重复接收**：假定发送方将消息 m 发送到主要队列。 服务总线成功处理了 m 但无法发送响应。 发送操作超时后，发送方将向辅助队列发送 m 的一份相同副本。 如果接收方能够在主要队列变为不可用之前接收 m 的第一个副本，则接收方会在几乎同一时间接收 m 的两个副本。 如果接收方不能在主要队列变为不可用之前接收 m 的第一个副本，则接收方首先仅接收 m 的第二个副本，但在主要队列变为可用后接收 m 的另一个副本。
[使用服务总线标准层进行异地复制][Geo-replication with Service Bus Standard Tier]示例演示了消息传送实体的被动复制。
## <a name="protecting-relay-endpoints-against-datacenter-outages-or-disasters"></a>保护中继终结点免受数据中心中断或灾难的影响
[Azure 中继](../azure-relay/relay-what-is-it.md)终结点的异地复制使得公开中继终结点的服务在服务总线中断时可用。 若要实现异地复制，该服务必须在不同的命名空间中创建两个中继终结点。 命名空间必须位于不同的数据中心，且两个终结点必须具有不同的名称。 例如，可在 **contosoPrimary.servicebus.chinacloudapi.cn/myPrimaryService** 下访问主要终结点，而在 **contosoSecondary.servicebus.chinacloudapi.cn/mySecondaryService** 下访问其辅助终结点。
该服务随后侦听两个终结点，客户端可通过其中任一终结点调用服务。 客户端应用程序随机选取一个中继作为主要终结点，并向活动终结点发送请求。 如果操作失败并返回错误代码，此故障指示中继终结点不可用。 应用程序会打开通向备份终结点的通道并重新发送请求。 此时，活动终结点与备份终结点将互换角色：客户端应用程序会将旧的活动终结点认定为新的备份终结点，而将旧的备份终结点认定为新的活动终结点。 如果两次发送操作都失败，则两个实体的角色将保持不变并返回错误。
## <a name="next-steps"></a>后续步骤
若要了解有关灾难恢复的详细信息，请参阅这些文章：
* [Azure 服务总线异地灾难恢复](service-bus-geo-dr.md)
* [Azure SQL 数据库业务连续性][Azure SQL Database Business Continuity]
<!--Not Avaialble on * [Designing resilient applications for Azure][Azure resiliency technical guidance]-->
[Service Bus Authentication]: service-bus-authentication-and-authorization.md
[Partitioned messaging entities]: service-bus-partitioning.md
[Asynchronous messaging patterns and high availability]: service-bus-async-messaging.md#failure-of-service-bus-within-an-azure-datacenter
[BrokeredMessage.MessageId]: https://docs.azure.cn/dotnet/api/microsoft.servicebus.messaging.brokeredmessage
[BrokeredMessage.Label]: https://docs.azure.cn/dotnet/api/microsoft.servicebus.messaging.brokeredmessage
<!--Available on Azure China now-->
[Geo-replication with Service Bus Standard Tier]: https://github.com/Azure/azure-service-bus/tree/master/samples/DotNet/Microsoft.ServiceBus.Messaging/GeoReplication
[Azure SQL Database Business Continuity]:../azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview.md
<!--Not Avaialble on [Azure resiliency technical guidance]: https://docs.microsoft.com/azure/architecture/resiliency-->
[1]: ./media/service-bus-outages-disasters/az.png
<!-- Update_Description: update meta properties, wording update, update link--> | 54.907216 | 305 | 0.825948 | yue_Hant | 0.657998 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.