Datasets:

BramVanroy

/

stack_md_lid

like 4

ce66dc84270570bd687b915513c26576dd47eeec

md

Markdown

.github/ISSUE_TEMPLATE.md

ldez/atom-autocomplete-asciidoc

3040d1e6ce56e54501c30cac360715a021eadfdf

.github/ISSUE_TEMPLATE.md

ldez/atom-autocomplete-asciidoc

3040d1e6ce56e54501c30cac360715a021eadfdf

.github/ISSUE_TEMPLATE.md

ldez/atom-autocomplete-asciidoc

3040d1e6ce56e54501c30cac360715a021eadfdf

## Description Your description. ## Screenshots Your screenshot.

eng_Latn

ce67a99fa92360b09643f98e4aa6518ce45b407d

md

Markdown

docs/Way of Working/Release-Steps_Entity.md

ochiu/entity

60f5851d4cd52a0607f7c6329a5c6d14d782f1a4

2020-05-21T18:08:00.000Z

2020-05-21T18:08:00.000Z

docs/Way of Working/Release-Steps_Entity.md

ochiu/entity

60f5851d4cd52a0607f7c6329a5c6d14d782f1a4

docs/Way of Working/Release-Steps_Entity.md

ochiu/entity

60f5851d4cd52a0607f7c6329a5c6d14d782f1a4

- Note: This release notes are currently used by Entity team only. - We work with Relationships team to document/ update their release process. Here an example: https://app.zenhub.com/workspaces/entity-5bf2f2164b5806bc2bf60531/issues/bcgov/entity/2485 **Prior to moving into production, the following steps should be completed or confirmed:** - [ ] Update version number in the code being released - [ ] Ensure deployment steps are filled in - remove/replace placeholders - [ ] Create a draft release in GitHub and confirm the correct commits are present - [ ] Add version # and release # to this ticket - [ ] Dev to send commit list to QA (or otherwise publish changelog) - commits are in the draft release for <Release Number> - [ ] QA to schedule the release with staff/ clients (daytime's best or when staff are available for rollback) - [ ] All dev/test pipeline test suites green - [ ] Dev/ QA chat to plan prod verification testing (unless already automated) Release the code to production and complete smoke test (STEPS BELOW) Finalise/publish the release in GitHub, tagging it Merge release branch back to master (if applicable) - [ ] Change openshift builds/pipelines back to master (if applicable) - [ ] colin-api-base - [ ] legal-api - [ ] update-colin-filings - [ ] update-legal-filings - [ ] entity-filer - [ ] entity- pay ---- **Deployment Steps** **DEV:** - [ ] config map changes - [ ] are there any dependencies, such as an auth/pay deployment or keycloak changes? - [ ] one-time steps to be done: - [ ] rebuild colin-updater - [ ] rebuild legal-updater - [ ] dev verification - [ ] QA verification **TEST:** - [ ] one-time steps to be done: - [ ] rebuild colin-updater - [ ] rebuild legal-updater - [ ] DEV verification - [ ] QA verification **PROD:** - [ ] link colin event ids 102132378 and 102132380 to filing_id = 251 before running colin-updater <This step might be specific to a particular release> - [ ] one-time steps to be done: - [ ] build colin-updater - [ ] rebuild legal-updater **Notify PO and CM** - [ ] Send the PO a message in RocketChat if a release was successfully implemented - [ ] PO will send Trish a message if a release was successfully implemented: [email protected] - and [email protected]

eng_Latn

ce6828b928765857f84c2565111f72538a5e9785

md

Markdown

Glorp.package/InfixFunction.class/README.md

akgrant43/Glorp

fbd722ec0f0f6bffb6a4a2ee9f09186d8445c6fb

Glorp.package/InfixFunction.class/README.md

akgrant43/Glorp

fbd722ec0f0f6bffb6a4a2ee9f09186d8445c6fb

Glorp.package/InfixFunction.class/README.md

akgrant43/Glorp

fbd722ec0f0f6bffb6a4a2ee9f09186d8445c6fb

This is a function that is infix. That is, it prints its name in between its arguments. For example, + for string concatenation, || for logical OR. Instance Variables: arguments <Collection of GlorpExpression> Our post-arguments (the first one being the base). functionParts <Array of: String> The parts of our name. For a two-argument function, this is just the same as an array containing the name, but for one with more (e.g. BETWEEN AND) it contains the different portions of the name.

eng_Latn

ce69444bf41eecc2ffa2bfdfb92db11edcdc293e

md

Markdown

SIP_2021 - Task4 - Numpy, OpenCV and PIL/README.md

Harshal-Atmaramani/SummerInternshipProgram2021

9f8c936817f7daed3190ccd6ff96c5e6ab91ad2e

2021-06-09T07:06:56.000Z

2021-06-09T07:06:56.000Z

SIP_2021 - Task4 - Numpy, OpenCV and PIL/README.md

Harshal-Atmaramani/SummerInternshipProgram2021

9f8c936817f7daed3190ccd6ff96c5e6ab91ad2e

SIP_2021 - Task4 - Numpy, OpenCV and PIL/README.md

Harshal-Atmaramani/SummerInternshipProgram2021

9f8c936817f7daed3190ccd6ff96c5e6ab91ad2e

2021-08-24T04:45:22.000Z

2021-08-24T04:45:22.000Z

### This task is one of many tasks that were given to summer interns at Linuxworld Informatics Pvt Ltd by our belowed Mr. Vimal Daga Sir. #### The Task Description 📄 is as follows: Summer - Task 04 👨🏻‍💻 ⚜️ Team Task 🔅 Task 4.1 📌 Create image by yourself using Python Code. 🔅 Task 4.2 📌 Take 2 image crop some part of both image and swap it. 🔅 Task 4.3 📌 Take 2 image (we have used 4) and combine it to form single image. For example collage. ### We have used Google Colaboratory to do the task since it is collaborative and uses cloud resources to process the code. If you intend to use the code in this repository, kindly make sure either to use Google Colaboratory or make necessary changes so as to use in Jupyter Notebook. ### Some point of differences between Google Colaboratory and Jupyter Notebook are listed below: 1. from google.colab.patches import cv2_imshow is equal to import cv2 in Jupyter NB. 2. cv2_imread in Colab is equal to cv2.imread in Jupyter NB. 3. cv2_imshow in Colab is equal to three statements in Jupyter NB. cv2.imshow('Img_Name', arr_var) cv2.waitKey() cv2.destroyAllWindows()

eng_Latn

ce6989b2edf59de40bd07c6d926927006f45e632

md

Markdown

docs/Reference/Collection/CollectionManipulation.md

jamesm-macrometa/jsC8

80f1234b5460ae8f885d2706ac854eb67382221b

2019-04-29T10:28:06.000Z

2022-03-20T09:31:43.000Z

docs/Reference/Collection/CollectionManipulation.md

jamesm-macrometa/jsC8

80f1234b5460ae8f885d2706ac854eb67382221b

2020-08-17T12:38:35.000Z

2022-03-12T12:34:01.000Z

docs/Reference/Collection/CollectionManipulation.md

jamesm-macrometa/jsC8

80f1234b5460ae8f885d2706ac854eb67382221b

2019-04-12T06:27:43.000Z

2022-01-19T22:58:53.000Z

## Manipulating the collection These functions implement [the HTTP API for modifying collections](https://developer.document360.io/docs/using-c8-rest-api) ## client.createCollection `async client.createCollection(collectionName, [properties], [isEdge]): Object` Creates collection **Arguments** - **collectionName**: `string` Name of the collection - **properties**: `Object` (optional) For more information on the 'properties` object, see [the HTTP API documentation for creating collections](https://developer.document360.io/docs/using-c8-rest-api). - **isEdge**: `boolean` (optional) If yes then it will create an Edge Collection. Default is false. Note:- If this prop is provided then no need to pass type in properties object. **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); await client.createCollection('some-collection'); ``` ## client.deleteCollection `async client.deleteCollection(collectionName, [opts]): Object` Deletes collection **Arguments** - **collectionName**: `string` Name of the collection - **opts**: `Object` (optional) An object with the following properties: - **isSystem**: `boolean` (Default: `false`) Whether the collection should be dropped even if it is a system collection. This parameter must be set to `true` when dropping a system collection. **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); await client.deleteCollection('some-collection'); ``` ## client.hasCollection `async client.hasCollection(collectionName): Boolean` Returns true if collection exists otherwise false **Arguments** - **collectionName**: `string` Name of the collection **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const hasCollection = await client.hasCollection('some-collection'); ``` ## client.getCollection `async client.getCollection(collectionName): Object` Returns collection info **Arguments** - **collectionName**: `string` Name of the collection **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collection = await client.getCollection('some-collection'); ``` ## client.getCollections `async client.getCollections(collectionName): Array<Object>` Returns collections info **Arguments** - **collectionName**: `string` Name of the collection **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collections = await client.getCollections('some-collection'); ``` ## client.getCollectionIds `async client.getCollectionIds(collectionName): Array<Object>` Returns collection Ids **Arguments** - **collectionName**: `string` Name of the collection **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collectionIds = await client.getCollectionIds('some-collection'); ``` ## client.getCollectionKeys `async client.getCollectionKeys(collectionName): Array<Object>` Returns collections keys **Arguments** - **collectionName**: `string` Name of the collection **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collectionKeys = await client.getCollectionKeys('some-collection'); ``` ## client.onCollectionChange `async client.onCollectionChange(collectionName, [subscriptionName], [dcName]): void` **Arguments** - **collectionName**: `string` Name of the collection - **dcName**: `string` (optional) The dcName for the consumer. - **subscriptionName**: `string` (optional) The name of the subscription. **Methods** `listener.on('open', callback )` `listener.on('message', callback )` `listener.on('close', callback )` `listener.on('error', callback )` `listener.close()` **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const listener = await client.onCollectionChange("some-collection"); listener.on('message',(msg) => console.log("message=>", msg)); listener.on('open',() => console.log("connection open")); listener.on('close',() => console.log("connection closed")); ``` ## client.enableCollectionStream `async client.enableCollectionStream(collectionName, enableStream): Object` Updates the collection stream flag. **Arguments** - **collectionName**: `string` Name of the collection - **enableStream**: `boolean` Whether the stream should be enabled on the collection or not. This parameter must be set to `true` when enabling a stream on the collection. **NOTE**: You can't set the flag to `false` as on-demand stream deletion is not allowed. **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collection = await client.enableCollectionStream('some-collection', enableStream); ``` # Advanced User ## collection.create `async collection.create([properties]): Object` Creates a collection with the given `properties` for this collection's name, then returns the server response. **Arguments** - **properties**: `Object` (optional) For more information on the 'properties` object, see [the HTTP API documentation for creating collections](https://developer.document360.io/docs/using-c8-rest-api). **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collection = client.collection('potatoes'); await collection.create() // the document collection "potatoes" now exists // -- or -- const collection = client.edgeCollection('friends'); await collection.create({ waitForSync: true // always sync document changes to disk }); // the edge collection "friends" now exists ``` Note:-(To make the collection as `spot`, pass the `isSpot: true` in the `properties` object.) ## collection.onChange `collection.onChange(dcName, subscriptionName): void` **Arguments** - **dcName**: `string`` The dcName for the consumer. - **subscriptionName**: `string` The name of the subscription. **Methods** `listener.on('open', callback )` `listener.on('message', callback )` `listener.on('close', callback )` `listener.on('error', callback )` `listener.close()` **Examples** ```js const listener = await collection.onChange("fed.macrometa.io", "mySub"); listener.on('message',(msg) => console.log("message=>", msg)); listener.on('open',() => console.log("connection open")); listener.on('close',() => console.log("connection closed")); ``` ## collection.rename `async collection.rename(name): Object` Renames the collection. The `Collection` instance will automatically update its name when the rename succeeds. **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collection = client.collection('some-collection'); const result = await collection.rename('new-collection-name') assert.equal(result.name, 'new-collection-name'); assert.equal(collection.name, result.name); // result contains additional information about the collection ``` ## collection.truncate `async collection.truncate(): Object` Deletes **all documents** in the collection in the client. **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collection = client.collection('some-collection'); await collection.truncate(); // the collection "some-collection" is now empty ``` ## collection.drop `async collection.drop([properties]): Object` Deletes the collection from the client. **Arguments** - **properties**: `Object` (optional) An object with the following properties: - **isSystem**: `boolean` (Default: `false`) Whether the collection should be dropped even if it is a system collection. This parameter must be set to `true` when dropping a system collection. **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collection = client.collection('some-collection'); await collection.drop(); // the collection "some-collection" no longer exists ``` ## collection.enableCollectionStream `async collection.enableCollectionStream(enableStream): Object` Updates the collection stream flag. **Arguments** - **enableStream**: `boolean` Whether the stream should be enabled on the collection or not. This parameter must be set to `true` when enabling a stream on the collection. **NOTE**: You can't set the flag to `false` as on-demand stream deletion is not allowed. **Examples** ```js const client = new jsc8({url: "https://gdn1.macrometa.io", token: "XXXX"}); //---- OR ---- const client = new jsc8({url: "https://gdn1.macrometa.io", apiKey: "XXXX"}); const collection = client.collection('some-collection'); await collection.enableCollectionStream(enableStream); ```

eng_Latn

ce6a483e38d412ea4aea9e7b46bc0fbf4622482d

md

Markdown

README.md

james-alvey-42/ReinforcementLearning

7658a3e8b77147bf738648575b1d9525d3dbd44c

README.md

james-alvey-42/ReinforcementLearning

7658a3e8b77147bf738648575b1d9525d3dbd44c

README.md

james-alvey-42/ReinforcementLearning

7658a3e8b77147bf738648575b1d9525d3dbd44c

# Reinforcement Learning A repository to learn and practice ideas in reinforcement learning, starting with classical problems such as the multi-armed bandit and moving towards more complex control tasks and risk evaluation. The main reference is [this book](https://web.stanford.edu/class/psych209/Readings/SuttonBartoIPRLBook2ndEd.pdf) by Sutton and Barto. ## Contents * *Multi-Armed Bandit:* An implementation of the multi-armed bandit problem to illustrate the trade-off between the greedy and exploratory strategies. A summary of the theory and the code can be found [here](https://james-alvey-42.github.io/multiarmedbandit). <img src="img/multi-armed-bandit.png" height="300"/>

eng_Latn

3b7bd7958b9da80383128e00582731cf41827593

md

Markdown

articles/active-directory/hybrid/tshoot-connect-sync-errors.md

md2perpe/azure-docs.sv-se

64bdd85952bc1d194f86a3a80e616ca967bb6235

articles/active-directory/hybrid/tshoot-connect-sync-errors.md

md2perpe/azure-docs.sv-se

64bdd85952bc1d194f86a3a80e616ca967bb6235

articles/active-directory/hybrid/tshoot-connect-sync-errors.md

md2perpe/azure-docs.sv-se

64bdd85952bc1d194f86a3a80e616ca967bb6235

--- title: 'Azure AD Connect: Felsök fel under synkronisering | Microsoft Docs' description: Beskriver hur du felsöker fel påträffades vid synkronisering med Azure AD Connect. services: active-directory documentationcenter: '' author: billmath manager: daveba ms.assetid: 2209d5ce-0a64-447b-be3a-6f06d47995f8 ms.service: active-directory ms.workload: identity ms.tgt_pltfrm: na ms.devlang: na ms.topic: article ms.date: 10/29/2018 ms.subservice: hybrid ms.author: billmath ms.collection: M365-identity-device-management ms.openlocfilehash: f63aebb9a9bbefe84ac36b92cd69e0d93de0ab76 ms.sourcegitcommit: d4dfbc34a1f03488e1b7bc5e711a11b72c717ada ms.translationtype: MT ms.contentlocale: sv-SE ms.lasthandoff: 06/13/2019 ms.locfileid: "66298761" --- # <a name="troubleshooting-errors-during-synchronization"></a>Felsök fel under synkronisering Fel kan uppstå när identitetsdata synkroniseras från Windows Server Active Directory (AD DS) till Azure Active Directory (AD Azure). Den här artikeln innehåller en översikt över olika typer av synkroniseringsfel några möjliga scenarier som orsakar dessa fel och potentiella sätt att åtgärda felen. Den här artikeln innehåller vanliga fel och kan inte omfatta alla eventuella fel. Den här artikeln förutsätter att läsaren är bekant med den underliggande [designbegrepp för Azure AD och Azure AD Connect](plan-connect-design-concepts.md). Med den senaste versionen av Azure AD Connect \(augusti 2016 eller högre\), en rapport om synkroniseringsfel är tillgängliga i den [Azure-portalen](https://aka.ms/aadconnecthealth) som en del av Azure AD Connect Health för synkronisering. Från och med 1 September 2016 [Azure Active Directory duplicerad Attributåterhämtning](how-to-connect-syncservice-duplicate-attribute-resiliency.md) funktionen aktiveras som standard för alla de *nya* Azure Active Directory-klienter. Den här funktionen ska aktiveras automatiskt för befintliga klienter under de kommande månaderna. Azure AD Connect utför tre typer av åtgärder från kataloger den bevarar synkroniserade: Importera, synkronisering och Export. Fel kan ske i alla åtgärder. Den här artikeln fokuserar främst på fel vid Export till Azure AD. ## <a name="errors-during-export-to-azure-ad"></a>Fel vid Export till Azure AD Följande avsnitt beskrivs olika typer av synkroniseringsfel som kan uppstå under exportåtgärden till Azure AD med Azure AD-anslutningsappen. Den här anslutningen kan identifieras av namnformat som ”contoso. *onmicrosoft.com*”. Fel vid Export till Azure AD anger att åtgärden \(lägga till, uppdatera, ta bort osv\) gjordes ett försök av Azure AD Connect \(Synkroniseringsmotorn\) på Azure Active Directory misslyckades.  ## <a name="data-mismatch-errors"></a>Matchningsfel datafel ### <a name="invalidsoftmatch"></a>InvalidSoftMatch #### <a name="description"></a>Beskrivning * När Azure AD Connect \(Synkroniseringsmotorn\) instruerar Azure Active Directory för att lägga till eller uppdatera objekt, Azure AD matchar en inkommande objekt med hjälp av den **sourceAnchor** attributet den **immutableId** attribut för objekt i Azure AD. Den här matchning kallas en **hårda matchar**. * När Azure AD **inte hittar** objekt som matchar den **immutableId** attributet med den **sourceAnchor** attribut för det inkommande objektet innan du etablerar en ny objekt att det faller tillbaka om du vill använda ProxyAddresses och UserPrincipalName-attribut för att hitta en matchning. Den här matchning kallas en **mjuk matchar**. Mjuk matchar har utformats för att matcha objekt som redan finns i Azure AD (som kommer i Azure AD) med de nya objekten att lägga till/uppdatera under synkroniseringen som representerar samma entitet (användare, grupper) lokalt. * **InvalidSoftMatch** felet uppstår när hårda matchar inte hitta något matchande objekt **AND** mjuk matchning hittar en matchande objekt men objektet har ett annat värde för *immutableId* än den inkommande objektets *SourceAnchor*, föreslå att matchande objekt har synkroniserats med ett annat objekt från på lokala Active Directory. Med andra ord för mjuk matchningen för att fungera, objektet ska vara mjuk matchas med bör inte ha något värde för den *immutableId*. Om något objekt med *immutableId* set med ett värde misslyckas hård-matchningen men som uppfyller kriterierna för ungefärlig matchning åtgärden skulle resultera i en InvalidSoftMatch synkroniseringsfel. Azure Active Directory-schemat tillåter inte två eller flera objekt som ska ha samma värde för följande attribut. \(Detta är inte en fullständig förteckning.\) * ProxyAddresses * UserPrincipalName * onPremisesSecurityIdentifier * ObjectId > [!NOTE] > [Azure AD-attributet duplicerad Attributåterhämtning](how-to-connect-syncservice-duplicate-attribute-resiliency.md) funktionen också distribueras som standardbeteendet för Azure Active Directory. Detta minskar antalet synkroniseringsfel som setts av Azure AD Connect (samt andra sync-klienter) genom att göra Azure AD mer motståndskraftig i hanteringen av den duplicerade ProxyAddresses och UserPrincipalName-attribut finns i lokala AD-miljö. Den här funktionen löser inte dubblettfel. Därför måste data fortfarande kan åtgärdas. Men den ger etablering av nya objekt som annars blockeras från håller på att etableras på grund av duplicerade värden i Azure AD. Detta minskar också antalet synkroniseringsfel som returneras till klienten synkronisering. > Om den här funktionen är aktiverad för din klient, visas inte InvalidSoftMatch synkroniseringsfel som visas under etableringen av nya objekt. > > #### <a name="example-scenarios-for-invalidsoftmatch"></a>Exempelscenarier för InvalidSoftMatch 1. Det finns två eller flera objekt med samma värde för attributet ProxyAddresses i den lokala Active Directory. Endast en etableras om i Azure AD. 2. Det finns två eller flera objekt med samma värde för attributet userPrincipalName i den lokala Active Directory. Endast en etableras om i Azure AD. 3. Ett objekt har lagts till i lokalt Active Directory med samma värde för attributet ProxyAddresses som för ett befintligt objekt i Azure Active Directory. Objektet har lagts till i lokala komma inte etableras i Azure Active Directory. 4. Ett objekt har lagts till i lokala Active Directory med samma värdet för userPrincipalName-attribut med ett konto i Azure Active Directory. Objektet komma inte etableras i Azure Active Directory. 5. Ett synkroniserat konto har flyttats från skog A till skog B. Azure AD Connect (Synkroniseringsmotorn) har använt ObjectGUID-attributet för att beräkna SourceAnchor. Värdet för SourceAnchor skiljer sig efter överflyttningen skog. Det nya objektet (från skog B) kan inte synkroniseras med det befintliga objektet i Azure AD. 6. Ett synkroniserat objekt har av misstag tagits bort från lokala Active Directory och ett nytt objekt har skapats i Active Directory för samma entitet (till exempel användare) utan att ta bort kontot i Azure Active Directory. Det nya kontot inte kan synkronisera med det befintliga Azure AD-objektet. 7. Azure AD Connect har avinstallerats och installerats om. Under ominstallationen, har ett annat attribut valts som SourceAnchor. Alla objekt som tidigare har synkroniserats stoppats synkroniseras med InvalidSoftMatch fel. #### <a name="example-case"></a>Exempel fall: 1. **Bob Smith** är en synkroniserade användare i Azure Active Directory från på lokala Active Directory *contoso.com* 2. Bob Smith **UserPrincipalName** har angetts som **bobs\@contoso.com**. 3. **”abcdefghijklmnopqrstuv ==”** är den **SourceAnchor** beräknas genom att Azure AD Connect med Bob Smith **objectGUID** från lokala Active Directory, vilket är den **immutableId** för Bob Smith i Azure Active Directory. 4. Bob innehåller också följande värden för den **proxyAddresses** attribut: * smtp: [email protected] * smtp: [email protected] * **SMTP: bob\@contoso.com** 5. En ny användare **Bob Taylor**, har lagts till i lokalerna Active Directory. 6. Bob Taylor **UserPrincipalName** har angetts som **bobt\@contoso.com**. 7. **”abcdefghijkl0123456789 ==” ”** är den **sourceAnchor** beräknas genom att Azure AD Connect med Bob Taylor **objectGUID** från på lokala Active Directory. Bob Taylor objektet har inte synkroniserats till Azure Active Directory ännu. 8. Bob Taylor har följande värden för attributet proxyAddresses * smtp: [email protected] * smtp: [email protected] * **SMTP: bob\@contoso.com** 9. Under synkronisering, Azure AD Connect identifierar att lägga till Bob Taylor i lokala Active Directory och be Azure AD för att göra samma ändring. 10. Azure AD först utför hårda matchning. Det vill säga söks om ett objekt med immutableId är lika med ”abcdefghijkl0123456789 ==”. Hårda matchning fungerar inte eftersom inga andra objekt i Azure AD har den immutableId. 11. Azure AD försöker ungefärlig matchning Bob Taylor. Det vill säga söks om ett objekt med proxyAddresses motsvarar värdena, inklusive smtp: [email protected] 12. Azure AD hittar Bob Smith objekt som matchar villkor som ungefärlig matchning. Men det här objektet har värdet för immutableId = ”abcdefghijklmnopqrstuv ==”. vilket betyder att det här objektet har synkroniserats från ett annat objekt från lokala Active Directory. Därför Azure AD kan inte ungefärlig matchning dessa objekt och resulterar i en **InvalidSoftMatch** fel. #### <a name="how-to-fix-invalidsoftmatch-error"></a>Hur du löser InvalidSoftMatch fel Den vanligaste orsaken till felet InvalidSoftMatch är två objekt med olika SourceAnchor \(immutableId\) har samma värde för ProxyAddresses och/eller UserPrincipalName-attribut, som används under en ungefärlig matchning bearbeta på Azure AD. För att åtgärda ogiltig mjuk matchning 1. Identifiera duplicerade proxyAddresses, userPrincipalName eller andra attribut-värde som orsakar felet. Även identifiera vilka två \(eller flera\) objekt som är inblandade i konflikten. Rapporten som genereras av [Azure AD Connect Health för synkronisering](https://aka.ms/aadchsyncerrors) kan hjälpa dig identifiera de två objekten. 2. Identifiera vilka objekt ska fortsätta att få det duplicerade värdet och vilket objekt bör inte. 3. Ta bort duplicerade värdet från det objekt som inte ska ha värdet. Du bör göra ändringen i katalogen där objektet kommer från. I vissa fall kan behöva du ta bort ett objekt i konflikt. 4. Om du gjort ändringen i lokalt AD, kan Azure AD Connect synkroniserar ändringen. Synkronisera felrapporter i Azure AD Connect Health för synkronisering uppdateras var 30: e minut och inkludera fel från det senaste synkroniseringsförsöket. > [!NOTE] > ImmutableId, bör per definition inte ändra av objektet. Om Azure AD Connect inte har konfigurerats med några av scenarierna i åtanke från listan ovan, du kan hamna i en situation där Azure AD Connect beräknar ett annat värde för SourceAnchor för AD-objekt som representerar samma entitet (samma användare/grupp / Kontakta osv) som har en befintlig Azure AD-objekt som du vill fortsätta att använda. > > #### <a name="related-articles"></a>Relaterade artiklar * [Dubblett eller ogiltigt attribut förhindra katalogsynkronisering i Office 365](https://support.microsoft.com/kb/2647098) ### <a name="objecttypemismatch"></a>ObjectTypeMismatch #### <a name="description"></a>Beskrivning När Azure AD försöker matcha mjuk två objekt, är det möjligt att två objekt i olika ”objekttyp” (till exempel användare, grupp, kontakt och så vidare) har samma värden för de attribut som används för att utföra mjuk matchningen. Eftersom duplicering av dessa attribut inte tillåts i Azure AD, kan åtgärden resultera i ”ObjectTypeMismatch” synkroniseringsfel. #### <a name="example-scenarios-for-objecttypemismatch-error"></a>Exempelscenarier för ObjectTypeMismatch fel * En e-postaktiverad säkerhetsgrupp skapas i Office 365. Administratören lägger till en ny användare eller kontakt i lokalt AD (som inte är synkroniserad med Azure AD ännu) med samma värde för attributet ProxyAddresses som Office 365-grupp. #### <a name="example-case"></a>Exempel fallet 1. Administratören skapar en ny e-postaktiverad säkerhetsgrupp i Office 365 för Skatteverket och ger en e-postadress som [email protected]. Den här gruppen har tilldelats värdet på attributet ProxyAddresses för **smtp: skatt\@contoso.com** 2. En ny användare ansluter Contoso.com och ett konto har skapats för användaren på plats med proxyAddress som **smtp: skatt\@contoso.com** 3. När Azure AD Connect kommer att synkronisera det nya användarkontot, får den felet ”ObjectTypeMismatch”. #### <a name="how-to-fix-objecttypemismatch-error"></a>Hur du löser ObjectTypeMismatch fel Den vanligaste orsaken till felet ObjectTypeMismatch är två objekt av annan typ (användare, grupp, kontakt och så vidare) har samma värde för attributet ProxyAddresses. För att kunna åtgärda ObjectTypeMismatch: 1. Identifiera duplicerade proxyAddresses (eller andra attribut) värde som orsakar felet. Även identifiera vilka två \(eller flera\) objekt som är inblandade i konflikten. Rapporten som genereras av [Azure AD Connect Health för synkronisering](https://aka.ms/aadchsyncerrors) kan hjälpa dig identifiera de två objekten. 2. Identifiera vilka objekt ska fortsätta att få det duplicerade värdet och vilket objekt bör inte. 3. Ta bort duplicerade värdet från det objekt som inte ska ha värdet. Observera att du ska göra ändringen i katalogen där objektet kommer från. I vissa fall kan behöva du ta bort ett objekt i konflikt. 4. Om du gjort ändringen i lokalt AD, kan Azure AD Connect synkroniserar ändringen. Felrapport för synkronisering i Azure AD Connect Health för synkronisering uppdateras var 30: e minut och innehåller fel från det senaste synkroniseringsförsöket. ## <a name="duplicate-attributes"></a>Duplicera attribut ### <a name="attributevaluemustbeunique"></a>AttributeValueMustBeUnique #### <a name="description"></a>Beskrivning Azure Active Directory-schemat tillåter inte två eller flera objekt som ska ha samma värde för följande attribut. Det är att varje objekt i Azure AD måste ha ett unikt värde av dessa attribut för en viss instans. * ProxyAddresses * UserPrincipalName Om Azure AD Connect försöker lägga till ett nytt objekt eller uppdatera ett befintligt objekt med ett värde för ovanstående attribut som redan har tilldelats till ett annat objekt i Azure Active Directory, resulterar åtgärden i ”AttributeValueMustBeUnique” sync-fel. #### <a name="possible-scenarios"></a>Möjliga scenarier: 1. Dubblettvärde har tilldelats ett redan synkroniserade objekt som står i konflikt med ett annat synkroniserat objekt. #### <a name="example-case"></a>Exempel fall: 1. **Bob Smith** är en synkroniserade användare i Azure Active Directory från på lokala Active Directory contoso.com 2. Bob Smith **UserPrincipalName** lokalt har angetts som **bobs\@contoso.com**. 3. Bob innehåller också följande värden för den **proxyAddresses** attribut: * smtp: [email protected] * smtp: [email protected] * **SMTP: bob\@contoso.com** 4. En ny användare **Bob Taylor**, har lagts till i lokalerna Active Directory. 5. Bob Taylor **UserPrincipalName** har angetts som **bobt\@contoso.com**. 6. **Bob Taylor** har följande värden för den **ProxyAddresses** attribut i. smtp: [email protected] ii. smtp: [email protected] 7. Bob Taylor objekt synkroniseras med Azure AD har. 8. Administratören har valt att uppdatera Bob Taylor **ProxyAddresses** attributet med följande värde: jag. **SMTP: bob\@contoso.com** 9. Azure AD försöker uppdatera Bob Taylor objektet i Azure AD med ovanstående värde, men som misslyckas åtgärden som att ProxyAddresses värdet har redan tilldelats Bob Smith, vilket resulterar i ”AttributeValueMustBeUnique”-fel. #### <a name="how-to-fix-attributevaluemustbeunique-error"></a>Hur du löser AttributeValueMustBeUnique fel Den vanligaste orsaken till felet AttributeValueMustBeUnique är två objekt med olika SourceAnchor \(immutableId\) har samma värde för ProxyAddresses och/eller UserPrincipalName-attribut. För att åtgärda felet för AttributeValueMustBeUnique 1. Identifiera duplicerade proxyAddresses, userPrincipalName eller andra attribut-värde som orsakar felet. Även identifiera vilka två \(eller flera\) objekt som är inblandade i konflikten. Rapporten som genereras av [Azure AD Connect Health för synkronisering](https://aka.ms/aadchsyncerrors) kan hjälpa dig identifiera de två objekten. 2. Identifiera vilka objekt ska fortsätta att få det duplicerade värdet och vilket objekt bör inte. 3. Ta bort duplicerade värdet från det objekt som inte ska ha värdet. Observera att du ska göra ändringen i katalogen där objektet kommer från. I vissa fall kan behöva du ta bort ett objekt i konflikt. 4. Om du gjort ändringen i lokalt AD, kan Azure AD Connect synkroniseras ändringen för felet för att hämta har åtgärdats. #### <a name="related-articles"></a>Relaterade artiklar -[Dubblett eller ogiltigt attribut förhindra katalogsynkronisering i Office 365](https://support.microsoft.com/kb/2647098) ## <a name="data-validation-failures"></a>Dataverifiering ### <a name="identitydatavalidationfailed"></a>IdentityDataValidationFailed #### <a name="description"></a>Beskrivning Azure Active Directory tillämpar olika begränsningar för själva informationen innan dessa data ska skrivas till katalogen. Det här är så att slutanvändarna får bästa möjliga upplevelse när du använder de program som är beroende av den här informationen. #### <a name="scenarios"></a>Scenarier a. Värdet för attributet UserPrincipalName har ogiltigt/stöds inte tecken. b. Attributet UserPrincipalName följer inte formatet som krävs. #### <a name="how-to-fix-identitydatavalidationfailed-error"></a>Hur du löser IdentityDataValidationFailed fel a. Se till att attributet userPrincipalName har stöds tecken och format som krävs. #### <a name="related-articles"></a>Relaterade artiklar * [Förbereda för att etablera användare via katalogsynkronisering på Office 365](https://support.office.com/article/Prepare-to-provision-users-through-directory-synchronization-to-Office-365-01920974-9e6f-4331-a370-13aea4e82b3e) ### <a name="federateddomainchangeerror"></a>FederatedDomainChangeError #### <a name="description"></a>Beskrivning Det här fallet resulterar i en **”FederatedDomainChangeError”** synkronisera fel när du suffix för en användares UserPrincipalName ändras från en federerad domän till en annan federerad domän. #### <a name="scenarios"></a>Scenarier För en synkroniserad användare ändrades UserPrincipalName-suffix från en federerad domän till en annan federerad domän lokalt. Till exempel *UserPrincipalName = bob\@contoso.com* har ändrats till *UserPrincipalName = bob\@fabrikam.com*. #### <a name="example"></a>Exempel 1. Bob Smith, ett konto för Contoso.com, hämtar läggas till som en ny användare i Active Directory med UserPrincipalName [email protected] 2. Bob flyttas till en annan avdelning contoso.com som kallas Fabrikam.com och deras UserPrincipalName ändras till [email protected] 3. Både contoso.com och fabrikam.com domäner är federerade domäner med Azure Active Directory. 4. Bobs userPrincipalName uppdateras inte och resulterar i ett ”FederatedDomainChangeError” synkroniseringsfel. #### <a name="how-to-fix"></a>Hur du åtgärdar Om en användares UserPrincipalName suffix har uppdaterats från bob @**contoso.com** till bob\@**fabrikam.com**, där båda **contoso.com** och **Fabrikam.com** är **federerade domäner**, Följ stegen nedan för att åtgärda sync-fel 1. Uppdatera användarens UserPrincipalName i Azure AD från [email protected] till [email protected]. Du kan använda följande PowerShell-kommando med Azure AD PowerShell-modulen: `Set-MsolUserPrincipalName -UserPrincipalName [email protected] -NewUserPrincipalName [email protected]` 2. Tillåt kommer nästa synkroniseringscykel att försöka synkronisering. Den här tidssynkronisering kommer att lyckas och den kommer att uppdatera UserPrincipalName Bob till [email protected] som förväntat. #### <a name="related-articles"></a>Relaterade artiklar * [Ändringarna synkroniserats inte med Azure Active Directory Sync-verktyget när du har ändrat UPN-namnet för ett användarkonto om du vill använda en annan federerad domän](https://support.microsoft.com/help/2669550/changes-aren-t-synced-by-the-azure-active-directory-sync-tool-after-you-change-the-upn-of-a-user-account-to-use-a-different-federated-domain) ## <a name="largeobject"></a>LargeObject ### <a name="description"></a>Beskrivning När ett attribut överskrider den tillåtna storleksgränsen, längdbegränsningen eller gränsvärdet som anges av Azure Active Directory-schemat, synkroniseringsåtgärden resulterar i den **LargeObject** eller **ExceededAllowedLength**fel. Det här felet uppstår vanligen för följande attribut * userCertificate * userSMIMECertificate * thumbnailPhoto * proxyAddresses ### <a name="possible-scenarios"></a>Möjliga scenarier 1. Bobs userCertificate-attributet lagrar för många certifikat som har tilldelats Bob. Dessa kan innehålla äldre, utgångna certifikat. Hård gräns är 15 certifikat. Mer information om hur du hanterar LargeObject-fel med userCertificate-attributet finns i artikeln [hantera LargeObject-fel som orsakats av userCertificate-attributet](tshoot-connect-largeobjecterror-usercertificate.md). 2. Bobs userSMIMECertificate attributet lagrar för många certifikat som har tilldelats Bob. Dessa kan innehålla äldre, utgångna certifikat. Hård gräns är 15 certifikat. 3. Bobs thumbnailPhoto i Active Directory är för stor för att synkroniseras i Azure AD. 4. Ett objekt har för många ProxyAddresses tilldelad vid automatisk ifyllning av attributet ProxyAddresses i Active Directory. ### <a name="how-to-fix"></a>Hur du åtgärdar 1. Kontrollera att attributet som orsakar felet ligger inom den tillåtna begränsningen. ## <a name="existing-admin-role-conflict"></a>Befintliga administratörsroll konflikt ### <a name="description"></a>Beskrivning En **konflikt med befintliga Admin-rollen** inträffar på ett användarobjekt under synkroniseringen när användarobjektet har: - administrativ behörighet och - samma UserPrincipalName som ett befintligt Azure AD-objekt Azure AD Connect är inte tillåtet att mjuk matchar ett användarobjekt från den lokala AD med ett användarobjekt i Azure AD som har en administrativ roll som tilldelats. Mer information finns i [Azure AD UserPrincipalName population](plan-connect-userprincipalname.md)  ### <a name="how-to-fix"></a>Hur du åtgärdar Du löser detta problem genom att göra något av följande: - Ändra UserPrincipalName till ett värde som inte matchar som en administratör i Azure AD – vilket skapar en ny användare i Azure AD med matchande UserPrincipalName - ta bort administrativ roll från Admin-användare i Azure AD, vilket gör att mjuk matchning mellan lokala användarobjektet och det befintliga objektet för Azure AD-användare. >[!NOTE] >Du kan tilldela administrativa rollen Dete befintliga användarobjekt igen när mjuk matchning mellan lokala användarobjektet och för Azure AD user-objektet har slutförts. ## <a name="related-links"></a>Relaterade länkar * [Hitta Active Directory-objekt i Active Directory Administrationscenter](https://technet.microsoft.com/library/dd560661.aspx) * [Hur du frågar Azure Active Directory för ett objekt med Azure Active Directory PowerShell](https://msdn.microsoft.com/library/azure/jj151815.aspx)

swe_Latn

3b7c53bcfec0661330cccedf6f0b0e0828e940e6

md

Markdown

content/publication/knowledgebert/index.md

jivatneet/starter-academic

2667a77fa442d1a09c2b508d80cbaf7aaa6eb387

content/publication/knowledgebert/index.md

jivatneet/starter-academic

2667a77fa442d1a09c2b508d80cbaf7aaa6eb387

content/publication/knowledgebert/index.md

jivatneet/starter-academic

2667a77fa442d1a09c2b508d80cbaf7aaa6eb387

--- # Documentation: https://wowchemy.com/docs/managing-content/ title: "No Need to Know Everything! Efficiently Augmenting Language Models With External Knowledge" authors: [admin, "Sumit Bhatia", "Milan Aggarwal", "Rachit Bansal", "Balaji Krishnamurthy"] date: 2021-09-11T22:43:22+05:30 doi: "" # Schedule page publish date (NOT publication's date). publishDate: 2021-03-26T22:43:22+05:30 # Publication type. # Legend: 0 = Uncategorized; 1 = Conference paper; 2 = Journal article; # 3 = Preprint / Working Paper; 4 = Report; 5 = Book; 6 = Book section; # 7 = Thesis; 8 = Patent publication_types: ["3"] # Publication name and optional abbreviated publication name. publication: "*Workshop on Commonsense Reasoning and Knowledge Bases (CSKB) at AKBC 2021*" publication_short: "*Workshop on Commonsense Reasoning and Knowledge Bases (CSKB) at AKBC*" abstract: "Large transformer-based pre-trained language models have achieved impressive performance on a variety of knowledge-intensive tasks and can capture semantic, syntactic, and factual knowledge in their parameters. However, storing large amounts of factual knowledge in the parameters of the model is sub-optimal given the resource requirements and ever-growing amounts of knowledge. Instead of packing all the knowledge in the model parameters, we argue that a more efficient alternative is to provide contextually relevant structured knowledge to the model and train it to use that knowledge. This allows the training of the language model to be de-coupled from the external knowledge source and the latter can be updated without affecting the parameters of the language model. Empirical evaluation using different subsets of LAMA probe reveals that such an approach allows smaller language models with access to external knowledge to achieve significant and robust outperformance over much larger language models." # Summary. An optional shortened abstract. summary: "" tags: [] categories: [] featured: false # Custom links (optional). # Uncomment and edit lines below to show custom links. # links: # - name: Follow # url: https://twitter.com # icon_pack: fab # icon: twitter url_pdf: 'https://openreview.net/pdf?id=fn5K7VfI3MV' url_code: url_dataset: url_poster: url_project: url_slides: url_source: url_video: links: - url: 'https://akbc-cskb.github.io/videos/17.mp4' # icon_pack: fab # icon: twitter name: Talk # Featured image # To use, add an image named `featured.jpg/png` to your page's folder. # Focal points: Smart, Center, TopLeft, Top, TopRight, Left, Right, BottomLeft, Bottom, BottomRight. image: caption: "" focal_point: "" preview_only: false # Associated Projects (optional). # Associate this publication with one or more of your projects. # Simply enter your project's folder or file name without extension. # E.g. `internal-project` references `content/project/internal-project/index.md`. # Otherwise, set `projects: []`. projects: [] # Slides (optional). # Associate this publication with Markdown slides. # Simply enter your slide deck's filename without extension. # E.g. `slides: "example"` references `content/slides/example/index.md`. # Otherwise, set `slides: ""`. slides: "" ---

eng_Latn

3b7c7def664eae86548e13766eaa67e5963a8e55

md

Markdown

README.md

Aquaticholic/Luddite-Project-Template

128d90f6f83f3a2f438b46be659213cc8d682549

README.md

Aquaticholic/Luddite-Project-Template

128d90f6f83f3a2f438b46be659213cc8d682549

README.md

Aquaticholic/Luddite-Project-Template

128d90f6f83f3a2f438b46be659213cc8d682549

# Luddite-Project-Template

eng_Latn

3b811a0ddf4a7f630f0a6c3fabeee2b7d38ae13f

md

Markdown

Design Challenges.md

Isaac-Irvine/Text-Cluedo

46b95993d555533e306a1703c67d426c5ef18045

Design Challenges.md

Isaac-Irvine/Text-Cluedo

46b95993d555533e306a1703c67d426c5ef18045

Design Challenges.md

Isaac-Irvine/Text-Cluedo

46b95993d555533e306a1703c67d426c5ef18045

2021-09-15T08:11:37.000Z

2021-09-15T08:11:37.000Z

* The way we implemented the player turns and loading of the game was completely different. (Constructor had to be changed) * player.turn() had to be recreated. Lots of getters in the Player class had to be added. * PlayerState had to be created, since player actions are not iterative anymore. *These are just bullet points which may be useful for the report*

eng_Latn

3b811e50ce633c8a1f65d714c0f831b478b32d3a

md

Markdown

bing_burp/README.md

tymyrddin/reomais

818812d3d2f82172f5d3f573846d4d7d27a838c9

bing_burp/README.md

tymyrddin/reomais

818812d3d2f82172f5d3f573846d4d7d27a838c9

bing_burp/README.md

tymyrddin/reomais

818812d3d2f82172f5d3f573846d4d7d27a838c9

# Bing for Burp Microsoft’s Bing search engine has search capabilities that allow querying for all websites it finds on a single IP address using the “IP” search modifier. Bing will also tell you [all of the subdomains of a given domain](/crawler) if you use the “domain” search modifier. Scraping Bing for it is not very ethical, but using Bing's API and parsing the results in a script is another matter.

eng_Latn

3b812f3351664d534fb966542883f94d5be4eaa4

md

Markdown

_posts/2003-05-24-more-on-cat-sars-link.md

kerim/keywords

b16bf75bd1e6347b57e3e3ca62012ec198c110f8

2017-08-10T12:37:13.000Z

2017-08-10T12:37:13.000Z

_posts/2003-05-24-more-on-cat-sars-link.md

kerim/keywords

b16bf75bd1e6347b57e3e3ca62012ec198c110f8

_posts/2003-05-24-more-on-cat-sars-link.md

kerim/keywords

b16bf75bd1e6347b57e3e3ca62012ec198c110f8

--- title: More on Cat-SARS link author: Kerim layout: post permalink: /archives/2003/05/24/more-on-cat-sars-link/ categories: - Old Blog Import --- Here is a much better explanation, from the <a href="http://www.washingtonpost.com/wp-dyn/articles/A33143-2003May23.html?nav=hptop_ts" onclick="_gaq.push(['_trackEvent', 'outbound-article', 'http://www.washingtonpost.com/wp-dyn/articles/A33143-2003May23.html?nav=hptop_ts', 'Washington Post']);" >Washington Post</a>, of the research that shows the cat-SARS link: > The long-sought discovery came when a team of researchers from the University of Hong Kong and the Chinese government tested 25 animals from eight species being sold at a live animal market in the province of Guangdong, where the disease first emerged. > > > The tests found a virus that appeared virtually identical to the SARS virus in saliva and feces of six catlike animals, known as masked palm civets. The researchers directly isolated virus from four of the animals and found pieces of genetic material from the microbe in two others. Tests also showed genetic evidence of the virus in feces of another animal, known as a raccoon dog, and an eighth animal, a Chinese ferret badger, had antibodies to the virus in its blood. None of the animals was sick. > > > > A detailed genetic analysis of the virus isolated from the animals found it was identical to the SARS virus from human patients except that it lacked one sequence. The missing genetic material carries instructions for the production of a small protein, known as a peptide, and may have been the change that allowed the virus to jump to humans and then spread readily, Stohr said. >

eng_Latn

3b81b4fadf98800c3059db7bc15e0680f813ce32

md

Markdown

README.md

ramr/prom-haproxy-exporter

9d0890af19622dbbf335daaf0b90784ee71518a0

2020-09-01T20:13:45.000Z

2020-09-01T20:13:45.000Z

README.md

ramr/openshift-prometheus-haproxy-demo

9d0890af19622dbbf335daaf0b90784ee71518a0

README.md

ramr/openshift-prometheus-haproxy-demo

9d0890af19622dbbf335daaf0b90784ee71518a0

openshift-prometheus-haproxy-demo ================================= Demo repository to publish the OpenShift HAProxy router statistics using the prometheus haproxy exporter to prometheus. Demo ---- 1. Start your OpenShift cluster as you would normally. Instructions will vary depending on how you do this in your environment. Example for a development environment, you can do this as follows: export WORKAREA="/home/ramr/workarea"; export GOPATH="${WORKAREA}" mkdir -p "${WORKAREA}/src/github.com/openshift" cd "${WORKAREA}/src/github.com/openshift" git clone https://github.com/openshift/origin.git cd origin make # or make release to also build the images nohup ./_output/local/bin/linux/amd64/openshift start --loglevel=4 &> /tmp/openshift.log & 2. Create a router service account and add it to the privileged SCC. echo '{ "kind": "ServiceAccount", "apiVersion": "v1", "metadata": { "name": "router" } }' | oc create -f - Either manually edit the privileged SCC and add the router account. oc edit scc privileged # ... # users: # - system:serviceaccount:openshift-infra:build-controller # - system:serviceaccount:default:router Or you can use jq to script it: sudo yum install -y jq oc get scc privileged -o json | jq '.users |= .+ ["system:serviceaccount:default:router"]' | oc replace scc -f - 3. Pull down the prometheus and haproxy-exporter images. docker pull prom/haproxy-exporter docker pull prom/prometheus 4. Start the router using the router service account we created above and make sure you expose the haproxy metrics. oadm router --credentials=$KUBECONFIG --service-account=router \ --replicas=1 --latest-images --expose-metrics 5. As mentioned in the https://github.com/ramr/nodejs-header-echo repo, create a deployment, service and route. # Update submodule to the nodejs-header-echo repo and build images. (cd nodejs-header-echo && git submodule update --init --recursive && make) # Create deployment + secure/insecure services. oc create -f nodejs-header-echo/openshift/dc.json oc create -f nodejs-header-echo/openshift/secure-service.json oc create -f nodejs-header-echo/openshift/insecure-service.json # Add a route that allows http and https. oc create -f nodejs-header-echo/openshift/edge-secured-allow-http-route.json # check the routes. oc get routes 6. Wait a bit for the service to become available. curl -vvv -H "Host: allow-http.header.test" http://127.0.0.1/ 7. Run the prometheus server that will scrape the haproxy metrics. Note: we use port 9999 as some environments have cockpit running on port 9090 on the host. make run || echo "see alternative instructions below ..." echo "Alternatively, you can just start the docker container." docker run -p 0.0.0.0:9999:9090 -dit ramr/openshift-prometheus-test 8. View the haproxy statistics in the prometheus display at: http://<node-ipaddr>:9999/consoles/haproxy.html 9. Generate some demo load and you will see the haproxy stats within prometheus. ab -c 5 -t 30 -H "Host: allow-http.header.test" http://127.0.0.1/

eng_Latn

3b81df107769153540730ab916e7b430d74aa220

md

Markdown

README.md

Temmy1/my-gatsby-blog

bf10d9f158e4ded00c6b297d688affacbf2b7377

README.md

Temmy1/my-gatsby-blog

bf10d9f158e4ded00c6b297d688affacbf2b7377

README.md

Temmy1/my-gatsby-blog

bf10d9f158e4ded00c6b297d688affacbf2b7377

## Моя страница с блогом Сделано с помощью Gatsby, на основе [gatsby-starter-default](https://github.com/gatsbyjs/gatsby-starter-default).

dan_Latn

3b830632bfccb0520b45e3d84d26096b83782b75

md

Markdown

README.md

geoprocesamiento-2020-i/geoprocesamiento-2020-i.github.io

e6a4ccf1824b8cee495e709183ac337941380129

2020-03-15T22:30:48.000Z

2020-06-10T22:44:41.000Z

README.md

geoprocesamiento-2020-i/geoprocesamiento-2020-i.github.io

e6a4ccf1824b8cee495e709183ac337941380129

README.md

geoprocesamiento-2020-i/geoprocesamiento-2020-i.github.io

e6a4ccf1824b8cee495e709183ac337941380129

2020-04-20T19:12:30.000Z

2021-11-17T22:18:25.000Z

# GF-0604: Procesamiento de datos geográficos ## Universidad de Costa Rica ### Escuela de Geografía #### Descripción del curso Este es un curso introductorio al procesamiento de datos geográficos mediante el lenguaje de programación R. Se estudian los fundamentos de la sintaxis de este lenguaje, sus bibliotecas geoespaciales y sus capacidades para generar gráficos y modelos estadísticos. #### Programa * [Programa del curso (modificado el 2020-04-14)](https://github.com/geoprocesamiento-2020i/programa-curso/blob/master/GF-0604-Procesamiento_datos_geograficos-Programa_curso-2020-I-20200414.pdf) #### Lecciones * [01 Introducción a la arquitectura de computadoras y a los lenguajes de programación](https://geoprocesamiento-2020i.github.io/leccion-01-introduccion/) * [02 La sintaxis Markdown](https://geoprocesamiento-2020i.github.io/leccion-02-markdown/) * [03 La sintaxis R Markdown](https://rmarkdown.rstudio.com/) * [04 El lenguaje de programación R - Introducción](https://geoprocesamiento-2020i.github.io/leccion-04-r-introduccion/) * [05 El lenguaje de programación R - Graficación](https://geoprocesamiento-2020i.github.io/leccion-05-r-graficacion/) * [06 El lenguaje de programación R - Datos vectoriales](https://geoprocesamiento-2020i.github.io/leccion-06-r-datos-vectoriales/) Lecturas previas: - [Geocomputation with R - Chapter 1 Introduction](https://geocompr.robinlovelace.net/intro.html) - [Geocomputation with R - Chapter 2 Geographic data in R](https://geocompr.robinlovelace.net/spatial-class.html) - (Opcional) [Why R? Webinar 004 - Robin Lovelace + Jakub Nowosad - Recent changes in R spatial](https://www.youtube.com/watch?v=Va0STgco7-4) * [07 El lenguaje de programación R - Datos vectoriales - operaciones con atributos](https://geoprocesamiento-2020i.github.io/leccion-07-r-datos-vectoriales-atributos/) Lecturas previas: - [Geocomputation with R - Chapter 3 Attribute data operations](https://geocompr.robinlovelace.net/attr.html) * [08 El paquete Leaflet](https://geoprocesamiento-2020i.github.io/leccion-08-leaflet/) * [09 El lenguaje de programación R - Datos vectoriales - operaciones espaciales](https://geoprocesamiento-2020i.github.io/leccion-09-r-datos-vectoriales-operaciones-espaciales/) Lecturas previas: - [Geocomputation with R - Chapter 4 Spatial data operations](https://geocompr.robinlovelace.net/spatial-operations.html) * [10 El lenguaje de programación R - Datos raster](https://geoprocesamiento-2020i.github.io/leccion-10-r-datos-raster/) Lecturas previas: - [Geocomputation with R - Chapter 2 Geographic data in R - Raster data](https://geocompr.robinlovelace.net/spatial-class.html#raster-data) - [Geocomputation with R - Chapter 3 Attribute data operations - Manipulating raster objects](https://geocompr.robinlovelace.net/attr.html#manipulating-raster-objects) - [Geocomputation with R - Chapter 4 Spatial data operations - Spatial operations on raster data](https://geocompr.robinlovelace.net/spatial-operations.html#spatial-ras) #### Laboratorios * [01 Markdown](https://geoprocesamiento-2020i.github.io/laboratorio-01-markdown/) * [02 R - Graficación 1](https://geoprocesamiento-2020i.github.io/laboratorio-02-r-graficacion-basica/) * [03 R - Datos vectoriales 1](https://geoprocesamiento-2020i.github.io/laboratorio-03-r-datos-vectoriales-1/) * [04 R - Datos raster 1](https://geoprocesamiento-2020i.github.io/laboratorio-04-r-datos-raster-1/) #### Tareas programadas * [01 Tablero de control sobre COVID-19 (básico)](https://geoprocesamiento-2020i.github.io/tarea-01-tablero-control-covid19/) * [02 Tablero de control sobre COVID-19 (avanzado)](https://geoprocesamiento-2020i.github.io/tarea-02-tablero-control-covid19/) #### Tutoriales * [Git](https://geoprocesamiento-2020i.github.io/tutorial-git/) * [flexdashboard](https://geoprocesamiento-2020i.github.io/tutorial-flexdashboard/) * [rgbif](https://geoprocesamiento-2020i.github.io/tutorial-rgbif/) #### Otros * [Datos utilizados durante el curso](https://github.com/geoprocesamiento-2020i/datos) * [Videos de las lecciones](https://www.youtube.com/playlist?list=PL1gEgLSwAJeLl246l2ArAZUQw3ChvlalH) Este sitio ha sido construído con las siguientes herramientas y sintaxis: - [GitHub Pages](https://pages.github.com/) - [Jekyll](https://jekyllrb.com/) - [RStudio](https://rstudio.com/) - [Markdown](https://daringfireball.net/projects/markdown/) - [R Markdown - ioslides_presentation](https://bookdown.org/yihui/rmarkdown/ioslides-presentation.html) - [R Markdown - html_document](https://bookdown.org/yihui/rmarkdown/html-document.html) #### Licencia de uso <a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Licencia Creative Commons" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br /><span xmlns:dct="http://purl.org/dc/terms/" property="dct:title">Los contenidos de este curso</span>, escrito por <a xmlns:cc="http://creativecommons.org/ns#" href="https://github.com/mfvargas" property="cc:attributionName" rel="cc:attributionURL">Manuel Vargas</a>, se comparten mediante una <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Licencia Creative Commons Atribución 4.0 Internacional</a>.

spa_Latn

3b830f5d193c65b9a93ad898b7093c9b5ef0497c

md

Markdown

README.md

MaikeMota/PI-2017-1

9c21cf77952271dc613cb2c5a204f028596c4c44

2018-04-09T13:45:45.000Z

2018-04-09T13:45:45.000Z

README.md

MaikeMota/PI-2017-1

9c21cf77952271dc613cb2c5a204f028596c4c44

README.md

MaikeMota/PI-2017-1

9c21cf77952271dc613cb2c5a204f028596c4c44

# PI-2017-1 Repositório dos Códigos Fontes do Projeto Integrador 2017-1

por_Latn

3b8426715edd2afc94ea8688b5e20b39c56dbee0

md

Markdown

README.md

hopemanryan/datanyze-schematics

6b73701c26fe3de6e6f54c4947c7bf3069341273

README.md

hopemanryan/datanyze-schematics

6b73701c26fe3de6e6f54c4947c7bf3069341273

README.md

hopemanryan/datanyze-schematics

6b73701c26fe3de6e6f54c4947c7bf3069341273

# Datanyze Schemaitcs ##### Component: ``` schenmatics .:comp --path ./ ``` ##### Service: ``` schenmatics .:service --path ./ ``` Both Schematics will ask a small list of questions in order to build you component This is not as a smart as ng schematics :) Please fork and update as you wish tutorial: https://medium.com/@tomastrajan/total-guide-to-custom-angular-schematics-5c50cf90cdb4

eng_Latn

3b84606b0b95a0101810ad61a557e392d15b6d79

md

Markdown

README.md

wangdehu/os

094515f4dbfa51375ff4b508c873ab7b6b8ac1f6

2018-11-14T16:10:48.000Z

2021-06-10T12:49:38.000Z

README.md

wangdehu/os

094515f4dbfa51375ff4b508c873ab7b6b8ac1f6

README.md

wangdehu/os

094515f4dbfa51375ff4b508c873ab7b6b8ac1f6

# os To do it! Do all what I can! os.md中为完成操作系统的感受与经验 参考资料：　 - 《汇编语言》王爽 - 《x86汇编语言:从实模式到保护模式》李忠 王晓波 - 《现代操作系统》AnderwS.Tanenbaum - 《深入理解计算机系统》布赖恩特（Bryant,R.E.）等 - [uCore OS实验指导书](https://chyyuu.gitbooks.io/ucore_os_docs/) - [ucore_os_lab项目](https://github.com/chyyuu/ucore_os_lab) - 《跟我一起写Makefile》陈皓

yue_Hant

3b84edda157b46cb5d4c5cd632e928a77cf64a64

md

Markdown

docs/CONTRIBUTING.md

DevTwerx/the-digger

c5c41e20504c0ffa840ba22404300131e3e39a49

docs/CONTRIBUTING.md

DevTwerx/the-digger

c5c41e20504c0ffa840ba22404300131e3e39a49

2020-03-03T00:11:57.000Z

2020-03-03T22:30:25.000Z

docs/CONTRIBUTING.md

DevTwerx/the-digger

c5c41e20504c0ffa840ba22404300131e3e39a49

# Making your contribution! Hi! This is a super small project, but I assure you, we appreciate your desire to provide a contribution of any sort, even if it's just a bug report! ### Bug reports If you have a bug, submit it as a Github issue, with as much information as possible. We do have a [code of conduct](https://github.com/DevTwerx/the-digger/blob/master/documentation/CODE_OF_CONDUCT.md) that we would appreciate you abide by. ### Features If you want to help submit work for an existing work item (we aren't at this point considering random new features from people!) please just submit a pull request against the appropriate feature branch, link the related work item, and provide some description of your code. Someone will be along to review your pull request with all due haste, I'm sure!

eng_Latn

3b855a7cf0376f641368e8d9f9ce5354b6c7fe03

md

Markdown

investigating-with-grr/flows/starting.md

simstoykov/grr-doc

94443f0e83ad01a7005e53ab85eab94b34b6aa3b

2015-01-02T13:57:39.000Z

2022-02-20T01:49:55.000Z

investigating-with-grr/flows/starting.md

simstoykov/grr-doc

94443f0e83ad01a7005e53ab85eab94b34b6aa3b

2015-01-20T14:34:42.000Z

2021-11-24T22:56:56.000Z

investigating-with-grr/flows/starting.md

simstoykov/grr-doc

94443f0e83ad01a7005e53ab85eab94b34b6aa3b

2015-01-20T12:22:31.000Z

2022-02-22T05:26:54.000Z

# Starting Flows To start a new Flow simply click on the *Start new flows* option on the left panel while having a client selected. The main panel will populate with the holy trinity of panels. The tree view shows all the Flows organized by category. For example, in order to start a *FileFinder* flow, expand the *FileSystem* category and select the corresponding item. The flow view will populate with a form with all the user-configurable parameters for this flow. What’s more, because each parameter has a well-defined type, GRR shows you widgets to select a value for each of them. The FileFinder flow accepts a range parameters: 1. *Paths*. This is a list of textual paths that you want to look at. 2. *Pathtype*. Which VFS handler you want to use for the path. Available options are: - **OS**. Uses the OS "open" facility. These are the most straightforward for a first user. Examples of *os* paths are `C:/Windows` on Windows or `/etc/init.d/` on Linux/OSX. - **TSK**. Use Sleuthkit. Because Sleuthkit is invoked a path to the device is needed along the actual directory path. Examples of *tsk* paths are `\\?\Volume{19b4a721-6e90-12d3-fa01-806e6f6e6963}\Windows` for Windows or `/dev/sda1/init.d/` on Linux (But GRR is smart enough to figure out what you want if you use `C:\Windows` or `/init.d/` instead even though there is some guessing involved). - **REGISTRY**. Windows-related. You can open the live Windows registry as if it was a virtual filesystem. So you can specify a path such as `HKEY_LOCAL_MACHINE/Select/Current`. - **MEMORY** and **TMPFILE** are internal and should not be used in most cases. 3. *Condition*. The *FileFinder* can filter files based on condition like file size or file contents. The different conditions should be self explanatory. Multiple conditions can be stacked, the file will only be processed if it fulfills them all. 4. *Action*. Once a file passes all the conditions, the action decides what should be done with it. Options are **STAT**, **HASH** and **DOWNLOAD**. Stat basically just indicates if a file exists, this is mostly used to list directories (path `C:\Windows\*` and action STAT). Hash returns a list of hashes of the file and Download collects the file from the client and stores it on the server. For this example, a good set of arguments would be a directory listing, something like path `C:\Windows\*` or `/tmp/*` and action **STAT**. Once you’ve filled in each required field, click on *Launch* and if all parameters validated, the Flow will run. Now you can go to the *Manage launched flows* view to find it running or track it. > **Important** > Not all flows might be available on every platform. When trying to run > a flow that’s not available in the given platform an error will show > up. ### Available flows ### The easiest ways to see the current flows is to check in the AdminUI under StartFlow. These have useful documentation. Note that by default only BASIC flows are shown in the Admin UI. By clicking the settings (gear icon) in the top right, you can enable ADVANCED flows. With this set you will see many of the underlying flows which are sometimes useful, but require a deeper understanding of GRR.

eng_Latn

3b860b995bda7af57c091b50e2ec8f8c44692df1

md

Markdown

README.md

oceanprotocol/github-projects

2f6cccd351529ff931a4df7b89aa89eeddbec0dc

2018-11-21T21:07:25.000Z

2019-04-25T21:16:57.000Z

README.md

oceanprotocol/github-projects

2f6cccd351529ff931a4df7b89aa89eeddbec0dc

2019-04-27T07:13:21.000Z

2022-03-28T01:16:24.000Z

README.md

oceanprotocol/github-projects

2f6cccd351529ff931a4df7b89aa89eeddbec0dc

2021-12-31T08:55:01.000Z

2022-01-10T04:36:23.000Z

[](https://oceanprotocol.com) <h1 align="center">github-projects</h1> > Microservice to cache and expose GitHub projects for use throughout [oceanprotocol.com](https://oceanprotocol.com). [](https://travis-ci.com/oceanprotocol/github-projects) [](https://github.com/oceanprotocol/eslint-config-oceanprotocol) [](https://greenkeeper.io/) <img src="http://forthebadge.com/images/badges/powered-by-electricity.svg" height="20"/> <img src="http://forthebadge.com/images/badges/as-seen-on-tv.svg" height="20"/> <img src="http://forthebadge.com/images/badges/uses-badges.svg" height="20"/> ## API Endpoint: [`https://oceanprotocol-github.now.sh`](https://oceanprotocol-github.now.sh) ### GET / **200**: Returns a list of all public projects as follows ```json [ { "name": "project-name", "description": "The description", "url": "https://github.com/oceanprotocol/project", "stars": 3040, "forks": 293, "isFork": false, "isArchived": false, "topics": [ "oceanprotocol", "oceanprotocol-driver", "python" ] } ] ``` ## Development Install dependencies: ```bash npm install -g now npm install ``` And run the server: ```bash npm start ``` ## Test Run the tests: ```bash npm test ``` ## Deployment Every branch is automatically deployed to [Now](https://zeit.co/now) with their GitHub integration. A link to a deployment will appear under each Pull Request. The latest deployment of the `master` branch is automatically aliased to `oceanprotocol-github.now.sh`, configured as `alias` in [`now.json`](now.json). ### Manual Deployment If needed, app can be deployed manually. Make sure to switch to Ocean Protocol org before deploying: ```bash # first run now login now switch # deploy now # switch alias to new deployment now alias ``` ## Authors - Matthias Kretschmann ([@kremalicious](https://github.com/kremalicious)) - [Ocean Protocol](https://oceanprotocol.com)

eng_Latn

3b868872d4a1cb328bb6f2fea416cbf5376cac08

md

Markdown

README.md

TeckZy/BlockChain-App-UI-Landing-Page

83afb83ab7b46f94ea81ccfbbdffb8f65865fd7c

README.md

TeckZy/BlockChain-App-UI-Landing-Page

83afb83ab7b46f94ea81ccfbbdffb8f65865fd7c

2021-09-02T11:46:45.000Z

2022-03-02T08:48:35.000Z

README.md

TeckZy/BlockChain-App-UI-Landing-Page

83afb83ab7b46f94ea81ccfbbdffb8f65865fd7c

# BlockChain-App-UI-Landing-Page ## Installation - All the `code` required to get started ### Clone - Clone this repo to your local machine using `https://github.com/TeckZy/BlockChain-App-UI-Landing-Page.git` ### Setup and Run > update and install this package first > now install npm and bower packages ```shell $ npm install $ npm run start ``` --- --- ## Team > Or Contributors/People Manoj --- ## License [](http://badges.mit-license.org) - **[MIT license](http://opensource.org/licenses/mit-license.php)** - Copyright 2015 © <a href="https://github.com/TeckZy" target="_blank">TecKzy</a>.

eng_Latn

3b86ddf752004a200d3efb31c3880f04f8f4c214

md

Markdown

proposals/subnet_management/20210805T1240Z.md

egeyar/nns-proposals

0e4752e7e84ac66739db6bb680f34f335818f93b

2021-05-22T05:04:41.000Z

2022-03-09T12:12:24.000Z

proposals/subnet_management/20210805T1240Z.md

egeyar/nns-proposals

0e4752e7e84ac66739db6bb680f34f335818f93b

2021-05-23T14:43:14.000Z

2021-11-12T17:10:11.000Z

proposals/subnet_management/20210805T1240Z.md

egeyar/nns-proposals

0e4752e7e84ac66739db6bb680f34f335818f93b

2021-05-21T11:20:51.000Z

2021-10-20T23:51:17.000Z

Proposing on [mainnet] to upgrade subnet 5 [w4asl-4nmyj-qnr7c-6cqq4-tkwmt-o26di-iupkq-vx4kt-asbrx-jzuxh-4ae] to the replica version c47a773b97f9e45b2760caaee4ad24aa6d5c9b69

eng_Latn

3b875451ca18272ae54a09e5f2c070ec202b294d

md

Markdown

_posts/2021-07-12-Come-fuck-my-pussy-the-way-it-should-be-fucked-20210712222940287928.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

_posts/2021-07-12-Come-fuck-my-pussy-the-way-it-should-be-fucked-20210712222940287928.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

_posts/2021-07-12-Come-fuck-my-pussy-the-way-it-should-be-fucked-20210712222940287928.md

ipussy/ipussy.github.io

95d19a74e38bb54303cf18057a99a57c783e76bf

--- title: "Come fuck my pussy the way it should be fucked." metadate: "hide" categories: [ Pussy ] image: "https://preview.redd.it/rrd4h6wcusa71.jpg?auto=webp&s=4ce6b01f8600c79213bee9e3746af5236b338693" thumb: "https://preview.redd.it/rrd4h6wcusa71.jpg?width=1080&crop=smart&auto=webp&s=469537982055bbcf6c4d30d978d2693d9231ae46" visit: "" --- Come fuck my pussy the way it should be fucked.

yue_Hant

3b879a7c0d75dcf8ffbe1fcbb7b9d96c6560cec4

md

Markdown

README.md

dvlden/rollup-config

67ff8507313387fe0376595bc8b45b2b0a9c358c

2019-05-26T17:05:32.000Z

2020-10-05T15:27:21.000Z

README.md

dvlden/rollup-config

67ff8507313387fe0376595bc8b45b2b0a9c358c

2021-10-01T17:09:08.000Z

2021-10-01T17:09:13.000Z

README.md

dvlden/rollup-config

67ff8507313387fe0376595bc8b45b2b0a9c358c

# Rollup Config Config is fully transparent. You don't need to touch it, unless you want to implement some additional plugins or change output formats. It is currently configured to output `ES` and `CJS` with type definitions. For the purpose of module building it is as minimal as possible. Tests are handled by the Jest testing framework. ## Getting started - `git clone https://github.com/dvlden/rollup-lib-config.git` - `npm i` ### Commands - `npm run test` - run all tests - `npm run build` - clean output directory and build for production ## Important Notes If you cloned my repository and want to use this for modules development, before you push any changes to Git or Npm, make sure to update some important files. - package.json - readme - license

eng_Latn

3b87cb5bc1c08b60ad70346787e1b0b31d2eac6f

md

Markdown

src/patterns/StateInitializer/README.md

isan26/react-patterns

8060f3601c380a83569f73cd98a811df8fbff694

2022-03-30T15:19:19.000Z

2022-03-30T15:19:19.000Z

src/patterns/StateInitializer/README.md

isan26/react-patterns

8060f3601c380a83569f73cd98a811df8fbff694

src/patterns/StateInitializer/README.md

isan26/react-patterns

8060f3601c380a83569f73cd98a811df8fbff694

# State Initializer ## The problem How can we setup a component when we use it, and feed it his firsts values? Imagine we have a counter and we need this counter to start not at 0 but at 10, how do we configure a component to take his initial state. ## The solution The state initializer pattern works by providing the initial state first through the component's props and setting his internal state. ## Consequences Components with this pattern can be used multiple times in different ways, the can be configure first and them used. This has to be made carefully because there is the restriction that if the prop used to initiate the component's values changes after the component is render can cause for mistakes because the component was initialized and won't get the change.

eng_Latn

3b88757ce8f21cb4cb22282f8257613f450a4b4c

md

Markdown

_posts/2016-09-07-why-wai-khru.md

neizod/neizod.github.io

725f1306413c81ce8982091216575c0235cf1c2b

2016-02-28T21:49:50.000Z

2022-03-17T20:23:49.000Z

_posts/2016-09-07-why-wai-khru.md

neizod/neizod.github.io

725f1306413c81ce8982091216575c0235cf1c2b

_posts/2016-09-07-why-wai-khru.md

neizod/neizod.github.io

725f1306413c81ce8982091216575c0235cf1c2b

2018-10-13T05:45:20.000Z

2022-01-29T03:38:32.000Z

--- title: ทำไมต้องไหว้ครู tags: - Thought - Tredition - Education date: 2016-09-07 01:55:55 +0700 --- พิธีกรรมอันหนึ่งที่ผมสงสัยมาตั้งแต่เด็กๆ ก็คงหนีไม่พ้นพิธีกรรมในโรงเรียนอย่างการไหว้ครู ที่จริงเมื่อฟังแนวคิดโดยรวมแล้ว พิธีไหว้ครูนี่เป็นอะไรที่เข้าท่านะ ความรู้ไม่ใช่สิ่งที่ได้มาง่ายๆ นอกจากจะบูชาความรู้แล้ว เราไม่ควรลืมแสดงความเคารพต่อครูบาอาจารย์ที่ถ่ายทอดวิชาความรู้นั้นแก่เราด้วย แต่ปัญหาที่คาใจมาตลอดคือ ทำไมงานไหว้ครูถึงได้จัดหลังเปิดเทอมไม่กี่วัน/เดือนเองหละ? ยังไม่ทันสอบกลางภาคเรียนแรกเลยก็ต้องมาจัดพานไหว้ครู ยังไม่ทันได้ความรู้อะไรมากมายแต่กลับต้องมาแสดงออกถึงความนอบน้อมในการเป็นศิษย์เสียแล้ว ถ้าย้ายงานไหว้ครูไปจัดตอนปลายภาคเรียน มันอาจจะดูเข้าท่ามากกว่านี้ เพราะถือว่าได้รับความรู้เต็มที่แล้วจึงควรกราบไหว้ครูและความรู้นั้นๆ หรือว่าเราจะเข้าใจผิดไปเอง นึกว่าจะเคารพหลักวิชาความรู้เป็นหลัก แต่แท้จริงแล้วกลับมองเพียงเปลือกที่ตัวบุคคล ต้องหมอบคลานเข้าไปกราบกรานขอให้อาจารย์รับเป็นศิษย์ ไม่เช่นนั้นแล้วก็จะไม่ยอมถ่ายทอดวิชาให้? พอมองในมุมนี้ ครูที่หวงความรู้จนถึงขั้นต้องให้คนมากราบกรานก่อนถึงจะสอนวิชาความรู้ให้ ก็ดูแล้วไม่น่าเคารพและฝากตัวเป็นศิษย์ด้วยเลยซักนิด แน่นอนว่าครูก็มีสิทธิ์เลือกศิษย์ และศิษย์ก็ต้องเลือกครู แต่การวางตัวสูงส่งว่ามีความรู้เหนือกว่าแล้วกดหัวคนอื่นลง มันไม่น่าในวิถีปัญญาชนเลยนี่หน่า

tha_Thai

3b88f709b424902ee724b7e9bb6444146f06e381

md

Markdown

meeting-notes/2021/Q1/2021-01-29--sow-gomobile-ipfs.md

LFGaming/community-1

b6aff6d8cbbc008667789891d24a545eb293ed11

2020-05-01T09:53:30.000Z

2022-03-11T16:49:20.000Z

meeting-notes/2021/Q1/2021-01-29--sow-gomobile-ipfs.md

LFGaming/community-1

b6aff6d8cbbc008667789891d24a545eb293ed11

2019-08-30T15:30:06.000Z

2020-04-06T16:55:07.000Z

meeting-notes/2021/Q1/2021-01-29--sow-gomobile-ipfs.md

LFGaming/community-1

b6aff6d8cbbc008667789891d24a545eb293ed11

2020-04-30T09:36:25.000Z

2021-09-16T15:41:03.000Z

# SOW Update - Gomobile IPFS - 29 Jan This is our fifth follow-up report regarding the gomobile-ipfs SOW. This report is mainly an outline of our conversation with Dietrich on 27 jan, 2021. ## Updates on Gomobile-IPFS * We extended gomobile-ipfs configuration, so we can integrate it within Berty Messenger * We prepared the codebase in order to make it easy to add new drivers over time * Everything was made in a way that allows various usages: - **full** gomobile-ipfs: use the library without custom go code - **hybrid** gomobile-ipfs: extend & make custom configuration of the library with go code * At the end of the week, Berty Messenger will depends on gomobile-ipfs, we will then start using it on a daily basis Current architecture detailed here: https://github.com/berty/berty/blob/master/docs/architecture/2020-11-27-adr-gomobile-ipfs.md Our plan stays the same as before: 1. we experiment drivers, concepts on Berty, and then 2. we can port the stable components on gomobile-ipfs, for everyone. ### Next steps: - add drivers interface, that will be exposed to both `gomobile-ipfs/bind` package & `berty/bridgeframework` package - move basic drivers from Berty to gomobile-ipfs - native-logger driver - connectivty driver - discuss with PL team about mobile optimizations - rendezvous-point: what's the future of https://github.com/libp2p/go-libp2p-rendezvous/pull/1 - recycling connections when switching from a network to another - long-term roadmap stays the same as before: https://github.com/berty/community/blob/master/meeting-notes/2020/Q4/2020-11-27--sow-gomobile-ipfs.md ## Current Snapshots of the architecture at Berty: * [Gomobile-IPFS](https://github.com/berty/berty/blob/master/docs/architecture/2020-11-27-adr-gomobile-ipfs.md) * [GRPC-bridge](https://github.com/berty/berty/blob/master/docs/architecture/2020-11-27-adr-berty-grpc-bridge.txt) ## Read our previous reports: * [Report #3](https://github.com/berty/community/blob/master/meeting-notes/2020/Q4/2020-11-27--sow-gomobile-ipfs.md) * [Report #2](https://github.com/berty/community/blob/master/meeting-notes/2020/Q4/2020-11-02--sow-gomobile-ipfs.md) * [Report #1](https://github.com/berty/community/blob/master/meeting-notes/2020/Q4/2020-10-20--sow-gomobile-ipfs.md) * [Report #0](https://github.com/berty/community/blob/master/meeting-notes/2020/Q4/2020-10-02--sow-gomobile-ipfs.md)

eng_Latn

3b890721ebfeeddbb7abc7aa772cf3dad13abaec

markdown

Markdown

_posts/2019-12-17-cancelling-hhvm-4.37.markdown

lexidor/hhvm.com

90b0d75bea9d302b4b74bec82069f4bf2f87d55d

2016-11-28T02:47:23.000Z

2021-12-11T00:06:27.000Z

_posts/2019-12-17-cancelling-hhvm-4.37.markdown

lexidor/hhvm.com

90b0d75bea9d302b4b74bec82069f4bf2f87d55d

2018-07-02T18:38:11.000Z

2022-03-31T21:25:52.000Z

_posts/2019-12-17-cancelling-hhvm-4.37.markdown

lexidor/hhvm.com

90b0d75bea9d302b4b74bec82069f4bf2f87d55d

2017-01-20T18:55:37.000Z

2022-03-02T21:05:20.000Z

--- title: "Holiday schedule: cancelling HHVM 4.37" layout: post author: fred category: blog --- We have decided to cancel next week's release of HHVM 4.37, and expect to delay 4.38 until Thursday, the 2nd of January. HHVM 4.31 will be supported until the release of HHVM 4.38 or above. As HHVM 4.32 has long-term-support (LTS), it is unaffected by this change. Our usual schedule is to release on Mondays or Tuesdays, and we expect many people - both at Facebook, and among our users - to be on vacation for Tuesday and Wednesday for the next two weeks. We believe that releasing new versions with breaking changes at this time would not be in the best interests of our users, especially as we would be less able to support them during this time. We look forward to continuing the evolution of Hack and HHVM in 2020.

eng_Latn

3b89e34b02035e4d261d4708f1fb7d93240ed698

md

Markdown

_drafts/2010-08-05-post-teaser-image-og-override.md

Cobuilding/cobuilding.ca

e700dfc0c71071c3d192eb86606e40a80f828ea0

_drafts/2010-08-05-post-teaser-image-og-override.md

Cobuilding/cobuilding.ca

e700dfc0c71071c3d192eb86606e40a80f828ea0

2020-12-08T01:07:33.000Z

2021-03-03T17:02:02.000Z

_drafts/2010-08-05-post-teaser-image-og-override.md

Cobuilding/cobuilding.ca

e700dfc0c71071c3d192eb86606e40a80f828ea0

--- title: 'Post: Teaser Image with OpenGraph Override' header: teaser: "/assets/images/page-header-teaser.png" og_image: "/assets/images/page-header-og-image.png" categories: - Layout - Uncategorized tags: - edge case - image - layout last_modified_at: 2017-10-26T15:12:19.000-04:00 --- This post has a teaser image with an OpenGraph override. ```yaml header: teaser: /assets/images/page-header-teaser.png og_image: /assets/images/page-header-og-image.png ```

eng_Latn

3b8ac0926751f64bf8e0452b541e6b2c7897b397

md

Markdown

projects/qiskit_nature.md

unitaryfund/unitaryhackdev

c7b45e3978ee39164447fa228541ed49508feaef

2022-03-29T13:24:40.000Z

2022-03-29T13:24:40.000Z

projects/qiskit_nature.md

unitaryfund/unitaryhackdev

c7b45e3978ee39164447fa228541ed49508feaef

2022-03-22T08:17:05.000Z

2022-03-31T23:26:20.000Z

projects/qiskit_nature.md

unitaryfund/unitaryhackdev

c7b45e3978ee39164447fa228541ed49508feaef

2022-03-14T18:16:27.000Z

2022-03-28T18:59:16.000Z

--- title: Qiskit Nature emoji: 👩🏽‍🔬 project_url: "https://github.com/Qiskit/qiskit-nature/" metaDescription: Quantum applications in chemistry, physics, and biology. date: 2022-04-27 summary: qiskit-nature is a Qiskit application module for chemistry, physics, and biology. tags: - python - quantum-chemistry - algorithms bounties: - name: Implement a succ_full ansatz option issue_num: 91 value: 200 - name: Improve performance of mode_based_mapping method in QubitMapper issue_num: 644 value: 50 --- [Qiskit](https://qiskit.org) is an open-source SDK for working with quantum computers at the level of pulses, circuits, and application modules. The `qiskit-nature` package is a Qiskit application module for chemistry, physics, and biology. If it is your first time contributing to `qiskit-nature`, please take a look at our [contribution guidelines](https://github.com/Qiskit/qiskit-nature/blob/main/CONTRIBUTING.md). > If you want to participate with a simpler issue, check out our [list of unassigned `good first issues`](https://github.com/Qiskit/qiskit-nature/issues?q=is%3Aopen+is%3Aissue+no%3Aassignee+label%3A%22good+first+issue%22). > For support from the community, please [join the Qiskit Slack community](https://ibm.co/joinqiskitslack) and use our [Qiskit Slack channel](https://qiskit.slack.com) for discussion. The channels `#qiskit-dev` and `#qiskit-pr-help` might be a good place for questions on the development and the PRing process respectively.

eng_Latn

3b8af66f27c882ee4348cd4e2130e2833eb3dd26

md

Markdown

api/README.md

TayaPenskaya/SoftwareTesting

f83b781b285a09625dc421fa30eba7e72d518105

api/README.md

TayaPenskaya/SoftwareTesting

f83b781b285a09625dc421fa30eba7e72d518105

api/README.md

TayaPenskaya/SoftwareTesting

f83b781b285a09625dc421fa30eba7e72d518105

# Express + Node.js + MongoDB ## Methods API * register user: ```curl -H "Content-Type: application/json" -d '{"username":"name", "password":"pass"}' http://localhost:port/api/users/register``` * login: ```curl -H "Content-Type: application/json" -H "Authorization: Bearer ${TOKEN}" -d '{"username":"name", "password":"pass"}' http://localhost:port/api/users/login``` * create new table: ```curl -H "Content-Type: application/json" -H 'Authorization: Bearer ${TOKEN}' -d '{"seats":10, "rake":5}' http://localhost:port/api/tables``` * get all tables: ```curl -i -H "Accept: application/json" -H "Content-Type: application/json" -H 'Authorization: Bearer ${TOKEN}' -X GET http://localhost:port/api/tables``` * play on table: ```curl -H "Content-Type: application/json" -H 'Authorization: Bearer ${TOKEN}' -d '{"table":{"id":"table_id"}}' http://localhost:port/api/tables/table_id/play ``` * unsubscribe from table: ```curl -X DELETE -H "Content-Type: application/json" -H 'Authorization: Bearer ${TOKEN}' -d '{"table":{"id":"table_id"}}' http://localhost:port/api/tables/table_id/play``` * mongo: ``` > mongo > show databases > use poker > show collections > show users > db.users.find() > db.tables.find() ``` ## Полезные ссылки * [JWT](https://stackabuse.com/authentication-and-authorization-with-jwts-in-express-js/) * [Lib for JWT in Express](https://github.com/auth0/express-jwt) * [Mongoose](https://mongoosejs.com/docs/index.html) * [Passport](https://www.npmjs.com/package/passport) * [JWT docs](https://www.npmjs.com/package/jsonwebtoken) * [Article about JWT && NodeJs](https://bezkoder.com/node-js-mongodb-auth-jwt/)

yue_Hant

3b8b91a3f30945623cc5a72bf071c9a17feadaa4

md

Markdown

documentation/services/integrationService.md

PhilipSkinner/elementary

6b31f282aa85b407569526d679fe6826f68f6d2c

2020-02-17T07:51:21.000Z

2022-03-31T20:45:47.000Z

documentation/services/integrationService.md

PhilipSkinner/elementary

6b31f282aa85b407569526d679fe6826f68f6d2c

2020-03-10T21:24:35.000Z

2021-03-26T22:19:16.000Z

documentation/services/integrationService.md

PhilipSkinner/elementary

6b31f282aa85b407569526d679fe6826f68f6d2c

2020-09-18T13:37:11.000Z

2022-02-21T10:26:42.000Z

[Back to Services](/documentation/services) # Integrations Service The integrations service allows you to call into any integrations defined within the system. It surfaces the following methods: * callIntegration These methods are covered in more detail below. ### callIntegration Parameters: * `name` - string, the name of the ruleset to call * `method` - string, the HTTP method to call the integration using * `params` - object, the query parameters (or body) to send to the integration endpoint * `token` - string, the access token to use to access the API *optional* Calls the named integration with the paramters given and returns the JSON response (as a parsed object) within a promise. This method can reject with an error and needs to be handled correctly. This can be called from your controllers like so: ``` module.exports = { events : { load : (event) => { return this.integrationService.callIntegration( "getWeatherReport", "get", { location : "Cullingworth, UK" } ).then((result) => { ... }).catch((err) => { ... }); } } }; ```

eng_Latn

3b8c1241b3594935d8c8a2e088c7e760bc83ae21

md

Markdown

results/metaproteomics/README.md

mkorlevic/Korlevic_SelectiveRemoval_FrontMicrobiol_2021

b9c06ce5bf45821eae652846c89e73e16d55274d

results/metaproteomics/README.md

mkorlevic/Korlevic_SelectiveRemoval_FrontMicrobiol_2021

b9c06ce5bf45821eae652846c89e73e16d55274d

2020-11-16T13:54:32.000Z

2020-11-16T14:13:51.000Z

results/metaproteomics/README.md

mkorlevic/Korlevic_SelectiveRemoval_FrontMicrobiol_2021

b9c06ce5bf45821eae652846c89e73e16d55274d

2020-11-17T08:15:07.000Z

2021-01-18T08:45:20.000Z

This directory contains data produced in the metaprotemic analysis.

eng_Latn

3b8c6db2196049569dd300fe8f03ccce9ab44458

md

Markdown

posts/kr/intro.md

virgosoy/axios-docs

4c458519d5cc6f4b8f8684187346f2a970194adb

2020-12-03T13:35:42.000Z

2022-03-28T13:44:53.000Z

posts/kr/intro.md

virgosoy/axios-docs

4c458519d5cc6f4b8f8684187346f2a970194adb

2020-06-29T13:56:11.000Z

2022-03-16T10:58:13.000Z

posts/kr/intro.md

virgosoy/axios-docs

4c458519d5cc6f4b8f8684187346f2a970194adb

2020-11-20T15:46:59.000Z

2022-03-23T13:05:12.000Z

--- title: '시작하기' description: '브라우저와 node.js에서 사용할 수 있는 Promise 기반 HTTP 클라이언트 라이브러리' next_title: '기본 예제' next_link: '/kr/docs/example' --- # Axios란? Axios는 node.js와 브라우저를 위한 *[Promise 기반](https://javascript.info/promise-basics)* HTTP 클라이언트 입니다. 그것은 *[동형](https://www.lullabot.com/articles/what-is-an-isomorphic-application)* 입니다(동일한 코드베이스로 브라우저와 node.js에서 실행할 수 있습니다). 서버 사이드에서는 네이티브 node.js의 `http` 모듈을 사용하고, 클라이언트(브라우저)에서는 XMLHttpRequests를 사용합니다. # 특징 - 브라우저를 위해 [XMLHttpRequests](https://developer.mozilla.org/ko/docs/Web/API/XMLHttpRequest) 생성 - node.js를 위해 [http](http://nodejs.org/api/http.html) 요청 생성 - [Promise](https://developer.mozilla.org/ko/docs/Web/JavaScript/Reference/Global_Objects/Promise) API를 지원 - 요청 및 응답 인터셉트 - 요청 및 응답 데이터 변환 - 요청 취소 - JSON 데이터 자동 변환 - [XSRF](https://ko.wikipedia.org/wiki/%EC%82%AC%EC%9D%B4%ED%8A%B8_%EA%B0%84_%EC%9A%94%EC%B2%AD_%EC%9C%84%EC%A1%B0)를 막기위한 클라이언트 사이드 지원 # 설치 npm 사용하기: ```bash $ npm install axios ``` bower 사용하기: ```bash $ bower install axios ``` yarn 사용하기: ```bash $ yarn add axios ``` jsDelivr CDN 사용하기: ```html <script src="https://cdn.jsdelivr.net/npm/axios/dist/axios.min.js"></script> ``` unpkg CDN 사용하기: ```html <script src="https://unpkg.com/axios/dist/axios.min.js"></script> ```

kor_Hang

3b8cabf5b0eb9f544e5d06cd92f4e15201c2cbc0

md

Markdown

src/main/resources/docs/description/no-proto.md

tobiasweibel/codacy-eslint

7e61c731de618d26efa89eba0ffe495b56e8fe0d

src/main/resources/docs/description/no-proto.md

tobiasweibel/codacy-eslint

7e61c731de618d26efa89eba0ffe495b56e8fe0d

2019-12-27T17:33:01.000Z

2022-03-31T01:04:15.000Z

src/main/resources/docs/description/no-proto.md

tobiasweibel/codacy-eslint

7e61c731de618d26efa89eba0ffe495b56e8fe0d

2020-01-29T14:26:30.000Z

2021-07-27T13:22:02.000Z

Although __proto__ property has been deprecated as of ECMAScript 3.1 and shouldn't be used in the code, keep in mind that if you need to support legacy browsers, you might want to turn this rule off, since support for getPrototypeOf is not yet universal. When an object is created __proto__ is set to the original prototype property of the object’s constructor function. getPrototypeOf is the preferred method of getting "the prototype". ``` //Bad: var a = obj.__proto__; var a = obj["__proto__"]; //Good: var a = Object.getPrototypeOf(obj); ``` [Source](http://eslint.org/docs/rules/no-proto)

eng_Latn

3b8d382fd7b922de60455a49ee3ee79899baf01e

md

Markdown

README.md

cedd82/FightSearchV3

8a89ddf61064d9c69377e0c0ce1e81621c56f6ce

README.md

cedd82/FightSearchV3

8a89ddf61064d9c69377e0c0ce1e81621c56f6ce

README.md

cedd82/FightSearchV3

8a89ddf61064d9c69377e0c0ce1e81621c56f6ce

FightSearch is a .net core and angular 7 web application. It serves as a video aggregator for mma bouts for UFC, bellator, pride, strikeforce and WEC. It can be visited at https://www.mmavideosearch.com Fights can be filtered on a variety of data not available on https://www.ufc.tv and http://www.bellator.com/videos. This is acheived by obtaining data from other sources and matching them to the videos. This is not done as part of this project but another one The EF query only hits one table as it's constructed when updating the data which is only done every couple of months, so it allows faster performance than joining over 3 tables. Not a huge performance improvement but it was a pragmatic solution for what i needed. I strive to keep this up to date with the latest technologies. Originally it was written in angularjs and asp.net web api. It is now in angular 7 and .net core 2.1

eng_Latn

3b8e104d2d55cd48833d9d818896ff432555919d

md

Markdown

content/past_project/pipeline.md

aeksco/hugo-scratchpad

0af0d68a5f9062bfc640a33c032566fcd6e09fd6

content/past_project/pipeline.md

aeksco/hugo-scratchpad

0af0d68a5f9062bfc640a33c032566fcd6e09fd6

content/past_project/pipeline.md

aeksco/hugo-scratchpad

0af0d68a5f9062bfc640a33c032566fcd6e09fd6

--- title: "Pipeline" github: "pipeline" website: "https://poly.rpi.edu/pipeline/" --- Content organization, tracking, and distribution for media organizations.

eng_Latn

3b8f29ad42cd4bc3a4238c9f14d803d2be59955a

md

Markdown

cmd/stitching_sql/README.md

GanLuo96214/Stitching-SQL

1ceedbb9f8bd7cdef174cd755eff73ea54e37dda

2020-08-06T01:38:20.000Z

2020-08-06T01:38:20.000Z

cmd/stitching_sql/README.md

ganluo960214/StitchingSQLGo

1ceedbb9f8bd7cdef174cd755eff73ea54e37dda

cmd/stitching_sql/README.md

ganluo960214/StitchingSQLGo

1ceedbb9f8bd7cdef174cd755eff73ea54e37dda

# Stitching Sql generate mapper and list from type and type cost ## flags ``` usage: go:generate stitching_sql -type=example -file-name=u_can_set_file_name_or_by_default__-type_stitching_sql.go -type data type data type,must be set -file-name newly generated file name, default as "-type_stitching_sql.go" file name of the generated file ``` ## usage ```shell script go get -u github.com/ganLuo960214/StitchingSQLGo/cmd/stitching_sql ```

eng_Latn

3b9121450ded57e49f6de8bac182dba5f8ca679e

md

Markdown

_posts/2021-04-26-linux-setting-mariaDB.md

kha0213/kha0213.github.io

56c3c410e4ca4d165349576b7fb3f80e18923d2a

_posts/2021-04-26-linux-setting-mariaDB.md

kha0213/kha0213.github.io

56c3c410e4ca4d165349576b7fb3f80e18923d2a

_posts/2021-04-26-linux-setting-mariaDB.md

kha0213/kha0213.github.io

56c3c410e4ca4d165349576b7fb3f80e18923d2a

--- title: "Linux Create MariaDB Server" categories: - linux tags: - linux - mariaDB - Server last_modified_at: 2021-04-26T00:40:00-00:00 --- # Linux Quick start ## 1. Install WSL [wsl설치 : https://docs.microsoft.com/ko-kr/windows/wsl/install-win10](https://docs.microsoft.com/ko-kr/windows/wsl/install-win10) 윈도우 상에서 Linux를 편하게 다루는 WSL이라는 도구가 있다. Microsoft에서 정식으로 지원하는 것이니 이제 윈도우에서도 편하게 Linux를 다룰 수 있다. 우분투를 깔고 MariaDB Server를 설치해보자. 설치 가이드 대로 따라 하면 된다. ## 2. Install Ubuntu ## 3. Install mariaDB 1. sudo apt update && sudo apt-get -y upgrade apt-get은 우분투(+데미안) 계열의 리눅스에서 쓰이는 패키지 관리 명령어 도구이다. 해당 명령어는 레지파토리에서 업데이트 패키지가 있는지 체크하고 설치된 패키지를 업데이트하는 것이다. [참고 : https://blog.outsider.ne.kr/346](https://blog.outsider.ne.kr/346) 2. sudo apt-get install -y mariadb-server 자동으로 mariadb 까지 설치가 된다. 접속은 mysql -u root -p 로 확인해 보자. * mariaDB 10.4버전 부터는 sudo mysql 하여하 한다. [참조 : https://www.nemonein.xyz/2019/07/2254/](https://www.nemonein.xyz/2019/07/2254/) ```xml sudo mysql ``` 에서 권한이 없어서 아래와 같은 에러가 발생했다. * ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' [참고 : https://jimnong.tistory.com/807](https://jimnong.tistory.com/807) windows PowerShell 에서 ```xml wsl --list --verbose ``` 로 상태 확인하고 ```xml wsl -t ubuntu ``` 로 종료하였다. 하지만 역시 인증 되지 않아 다음과 같은 방법을 사용했다. [참고 : https://thinkpro.tistory.com/16](https://thinkpro.tistory.com/16) $sudo visudo 에서 권한을 추가하였다. 하지만 역시 실행이 되지 않았다. ```xml mysql <!--이 명령어도 실행이 되지 않아서--> sudo service mysql restart <!--서버를 다시 실행시키고--> sudo mysql -u root -p mysql <!--이걸로 mysql이 들어가졌다.--> sudo mysql <!--최종 실행 --> ``` 😀결과 ```markdown Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 39 Server version: 10.3.25-MariaDB-0ubuntu0.20.04.1 Ubuntu 20.04 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. ``` ## 4. mariaDB setting [참고 : https://jdm.kr/blog/132](https://jdm.kr/blog/132) ```sql create database db_name; create user 'username'@'ipaddress' identified by 'password'; grant all privileges on db_name.* to 'username'@'ipaddress'; flush privileges; -- 확인 select host, user from mysql.user; ``` 😀결과 ```markdown +--------------+---------+ | host | user | +--------------+---------+ | (ip address) | username| | localhost | root | +--------------+---------+ ``` * 외부에서도 접속 가능하게 변경 root 권한으로 돌아가서 /etc/mysql/mariadb.conf.d/ 폴더에서 50-server.cnf 파일 읽어서 bind-address 부분을 0.0.0.0 으로 변경하면 외부어디에서나 접속 가능하다. (기본은 127.0.0.1) 🐤Tip : ubuntu에서 root 비밀번호 잃어버렸을 때 1. 윈도우에서 cmd 접속 2. 우분투 접속시 root로 접속하도록 설정 변경 * ubuntu.exe config --default-user root 3. 우분투 실행 4. passwd 명령어로 패스워드 변경 5. 다시 윈도우 cmd에서 내 기본계정으로 설정 변경

kor_Hang

3b95376bd88d7c3617ad59ba82b7637d99f0322a

md

Markdown

_posts/2015-03-10-startup_talk.md

luizcarvalho/luizcarvalho.github.io

55d451c4d14ddec3d2721d604651ac832b710989

2015-08-08T03:52:29.000Z

2017-04-30T14:18:06.000Z

_posts/2015-03-10-startup_talk.md

luizcarvalho/luizcarvalho.github.io

55d451c4d14ddec3d2721d604651ac832b710989

2015-07-10T18:34:28.000Z

2022-02-26T03:48:50.000Z

_posts/2015-03-10-startup_talk.md

luizcarvalho/luizcarvalho.github.io

55d451c4d14ddec3d2721d604651ac832b710989

--- layout: default thumb_url: "http://res.cloudinary.com/drlko5ghb/image/upload/v1473634263/r5kcn4bypmnmdmv5p8dw.webp" modal_id: 10 date: 2015-03-10 title: Startup Talk subtitle: Evento semanal sobre Startups prioridade: 8 medium_post_url: https://medium.com/p/131b96795078 ---

kor_Hang

3b957689e8517ef6b3fe4b01735a8fe9991903f3

md

Markdown

README.md

songhailong/HLEmoji

dd57fcdaef090ba08e66bde4814a71302cad5f9a

2018-10-16T06:41:10.000Z

2018-10-16T06:41:10.000Z

README.md

songhailong/HLEmoji

dd57fcdaef090ba08e66bde4814a71302cad5f9a

README.md

songhailong/HLEmoji

dd57fcdaef090ba08e66bde4814a71302cad5f9a

# HLEmoji 表情键盘

lit_Latn

3b95af4655672c0d44ebcd59e4ffd773b2c660d5

md

Markdown

pages/api/heft.heftconfiguration.heftpackagejson.md

elliot-nelson/rushstack.io-website

073c8c2621055dc26f8aa0baeef294a3ca832030

2019-11-08T06:57:43.000Z

2022-02-04T23:30:01.000Z

pages/api/heft.heftconfiguration.heftpackagejson.md

elliot-nelson/rushstack.io-website

073c8c2621055dc26f8aa0baeef294a3ca832030

2019-09-05T05:20:57.000Z

2022-02-26T05:34:54.000Z

pages/api/heft.heftconfiguration.heftpackagejson.md

elliot-nelson/rushstack.io-website

073c8c2621055dc26f8aa0baeef294a3ca832030

2019-11-08T06:57:46.000Z

2022-03-25T15:59:47.000Z

--- layout: page navigation_source: api_nav improve_this_button: false --- <!-- Do not edit this file. It is automatically generated by API Documenter. --> [Home](./index.md) &gt; [@rushstack/heft](./heft.md) &gt; [HeftConfiguration](./heft.heftconfiguration.md) &gt; [heftPackageJson](./heft.heftconfiguration.heftpackagejson.md) ## HeftConfiguration.heftPackageJson property The Heft tool's package.json <b>Signature:</b> ```typescript get heftPackageJson(): IPackageJson; ```

eng_Latn

3b96638248d2382558e2328c06b2ca889dc05d1d

md

Markdown

joystik.md

ismamera/ARDUINO

5e78d445715ee54da61fb54309ec6c52803259c4

joystik.md

ismamera/ARDUINO

5e78d445715ee54da61fb54309ec6c52803259c4

joystik.md

ismamera/ARDUINO

5e78d445715ee54da61fb54309ec6c52803259c4

hoy en classe estamos trabajando el joystikck para lo cual yo echo la conexion de cables macho/hembra

spa_Latn

3b97121bcbf3fe9789dcf44f60a7ffb0216b4614

md

Markdown

README.md

LIDS-UNICAMP/ODISF

df9710affe22d9f5f1e0632ce1368083fcfbfea1

2022-01-23T16:50:21.000Z

2022-02-23T15:30:57.000Z

README.md

LIDS-UNICAMP/ODISF

df9710affe22d9f5f1e0632ce1368083fcfbfea1

README.md

LIDS-UNICAMP/ODISF

df9710affe22d9f5f1e0632ce1368083fcfbfea1

## Object-based Dynamic and Iterative Spanning Forest (ODISF) This is the implementation of the superpixel segmentation method _Object-based Dynamic and Iterative Spanning Forest_(ODISF) as proposed in - **F.Belém, B.Perret, J.Cousty, S.Guimarães, A.Falcão.** [_Towards a Simple and Efficient Object-based Superpixel Delineation Framework_](https://ieeexplore.ieee.org/document/9643123). In 34th International Conference on Graphics, Patterns and Images (SIBGRAPI), pg 346-353. 2021. This software includes a program for running the ODISF method, and another one for assisting the visualization of the segmentation by overlaying the superpixel borders. Please cite the aforementioned paper if you use any of this software in your own project. ### Hardware, Setup and Requirements The project was developed in **C** under a **Linux-based** operational system; therefore, it is **NOT GUARANTEED** to work properly in other systems (_e.g._ Windows and macOS). Moreover, the same applies for **non-GCC** compilers, such as Clang and MinGW. All code within this project were developed, compiled and tested using the following programs: - **[GNU GCC](https://gcc.gnu.org/)**: version 7.5.0 - **[GNU Make](https://www.gnu.org/software/make/)**: version 4.1 This code was implemented and evaluated in a computer with the following specifications: - **Model:** Acer X555LB - **Operational System:** Linux Mint v20.2 x86_64 kernel version 5.4.0-86-generic - **Order:** Little-Endian - **CPU:** 4x Dual-core Intel(R) Core(TM) i5-5200 @ 2.20 GHz - **Memory:** 8GB RAM ; 480 SSD The library has in-built support for handling **PNM** images. For enabling external library support, please refer to the [README](externals/README.md) file within the **externals** folder. ### Compiling If your computer meets the aforementioned requirements, you may run the commands below for compiling the library and all the demonstration programs. ```bash make lib make demo ``` Or simply run one of the following commands for compiling both latter at once. ```bash make make all ``` For removing the files generated from compilation, one may run the following rule. ```bash make clean ``` ### Running After compiling, one may run ODISF for segmenting an image through the following command ```bash ./bin/RunODISF --img path/to/image.ppm --objsm path/to/objsm.pgm --out path/to/segm.pgm ``` Briefly, `--img`,`--objsm`, and `--out` indicate the paths to the image to be segmented and its object saliency map, and to the resulting segmentation, respectively. For other arguments, one may run ```bash ./bin/RunODISF --help ``` for more information. Given such segmentation, it is possible to draw the superpixel borders over the original image for a better visualization by the following command ```bash ./bin/RunOvlayBorders --img path/to/image.ppm --labels path/to/segm.pgm --out path/to/overlay.ppm ``` In this case, `--img`,`--labels`, and `--out` indicate the paths to the original image and segmentation, and to the resulting overlay image, respectively. Likewise, for other arguments, one may run ```bash ./bin/RunOvlayBorders --help ``` for more information. ### License All codes within this project are under the **MIT License**. See the [LICENSE](LICENSE) file for more details. ### Acknowledgements This work was financially supported by the following brazilian research funding agencies: - Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq) - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES) - Fundação de Amparo à Pesquisa do Estado de Minas Gerais (FAPEMIG) - Fundação de Amparo à Pesquisa do Estado de São Paulo (FAPESP) ### Contact If you have any questions or faced an unexpected behavior (_e.g._ bugs), please feel free to contact the authors through the following email addresses: - **Felipe C. Belém**: [[email protected]](mailto:[email protected]) - **Benjamin Perret**: [[email protected]](mailto:[email protected]) - **Jean Cousty**: [[email protected]](mailto:[email protected]) - **Silvio Jamil F. Guimarães**: [[email protected]](mailto:[email protected]) - **Alexandre X. Falcão**: [[email protected]](mailto:[email protected])

eng_Latn

3b973d82547e0311060fd975f6de44779c4f77ad

md

Markdown

README.md

JaimeBarranquero1989/cal_I

97d6c35908d03528be6f762a06453d4c0b65597d

README.md

JaimeBarranquero1989/cal_I

97d6c35908d03528be6f762a06453d4c0b65597d

README.md

JaimeBarranquero1989/cal_I

97d6c35908d03528be6f762a06453d4c0b65597d

# cal_I Esto es una prueba de la utilizacion de Git por Jaime Barranquero

spa_Latn

3b97a5eb2e40cfacd92ce3e2f2cf0fe990693b93

md

Markdown

_posts/2018-08-31-web worker学习笔记.md

wwjwentworth/wwjwentworth.github.io

967e7be72499be1d2ba86259a9566731dbf5f757

2018-05-10T13:50:59.000Z

2018-05-10T13:51:03.000Z

_posts/2018-08-31-web worker学习笔记.md

wwjwentworth/wwjwentworth.github.io

967e7be72499be1d2ba86259a9566731dbf5f757

_posts/2018-08-31-web worker学习笔记.md

wwjwentworth/wwjwentworth.github.io

967e7be72499be1d2ba86259a9566731dbf5f757

2018-06-22T14:24:18.000Z

2018-06-22T14:24:18.000Z

--- layout: post date:       2018-08-31 author: WWJ header-img: img/post-bg-universe.jpg catalog: true tags: Web Worker --- # webWorker > 允许一段javascript代码运行在主线程之外的另一个线程。 **如何创建** `index.js` ```javascript const worker = new Worker("./task.js"); ```  在谷歌浏览器下会报错，原因是谷歌浏览不支持使用本地方式使用Web Worker，简单的方法就是在本地开启一个服务，方法只需全局安装`http-server`，然后在`index.js`对应的文件路径下启动服务 全局安装：npm install http-server -g 启动服务：http-server `worker`是主线程与其他线程之间的通讯桥梁，主线程和其他线程可以通过 ```javascript onmessage：监听消息 postMessage:发送消息 ``` 案例如下 ``` //主线程 index.js var worker = new Worker("worker.js"); worker.onmessage = function(event){ // 主线程收到子线程的消息 }; // 主线程向子线程发送消息 worker.postMessage({ type: "start", value: 12345 }); //web task.js onmessage = function(event){ // 收到 }; postMessage({ type: "debug", message: "Starting processing..." }); ``` **如何终止** 如意我们不想再继续运行worker了，那么就可以在主线程中使用`worker.terminate()`或者在相应的其他线程使用`self.close()` **错误机制** ```javascript worker.onerror = function (error) { console.log(error.filename, error.lineno, error.message); } // error.filename：出错的脚步名称 // error.lineno：出错的行号 // error.message：错误信息 ``` **shared worker** > web worker只在当前页面下运行，一旦页面关闭就会终止，而shared worker可以同时在多个页面下使用，不会因为关闭了其中一个页面而终止运行 ```javascript const worker = new ShareWorker('./task.js') ``` 共享线程也使用onmessge监听事件，使用postMessage发送数据 ```javascript worker.post.onmessage = function(){ // code } worker.post.postMessage = function() { // code } ``` ### web worker与异步的区别 `web worker`是真正意义上的多线程，由`worker`开启的子线程与主线程互不干扰，也互不阻塞，而异步其实还是在主线程上运行，只不过是会先将异步的任务添加到事件队列中，等到主线程上没有任务了才会依次去执行事件队列里面的任务，如果异步任务被阻塞了，主线程也会被阻塞

yue_Hant

3b9917feaf87073dae4ea7829a98d0fa6c512233

md

Markdown

README.md

shr4ppy/cassetteWinder

d19fbd2650a19a147d5a0847805790c9a973e9ec

README.md

shr4ppy/cassetteWinder

d19fbd2650a19a147d5a0847805790c9a973e9ec

README.md

shr4ppy/cassetteWinder

d19fbd2650a19a147d5a0847805790c9a973e9ec

# cassetteWinder ## About This is a utility for my hobby of recording cassettes. Counting the minutes and seconds of songs with a reasonable margin of error as to not make it overrun the length of a cassette is strenuous and irritating. This script simply does the counting quickly, easily, and creates an easy to read tracklist so you can easily fast-forward to whatever song you want. ## Usage Simply run main.py. On linux, this program will need superuser permissions in order to create files. The loop will run you through the whole process. A spotify account will be needed. Log in at https://developer.spotify.com and create a new application. Thus, write your client ID, client secret and callback id (which ideally is http://localhost:8080/callback) in credentials.py.

eng_Latn

3b9991a8c19e346a79c2d4744c43fbb896c87a54

md

Markdown

README.md

lexbel/git_issue_tracker

4c7c27ae4a5d3b6c1b31e422ab8a2d3abce56cb0

README.md

lexbel/git_issue_tracker

4c7c27ae4a5d3b6c1b31e422ab8a2d3abce56cb0

2020-03-26T21:54:15.000Z

2020-03-26T21:54:15.000Z

README.md

lexbel/git_issue_tracker

4c7c27ae4a5d3b6c1b31e422ab8a2d3abce56cb0

# Git issue tracker This app track changes in git by receiving web hook from BitBucket and synchronize found issues with Jira in terms of fix version. So it gives 100% guarantee that fix version is set correctly. BitBucket or Jira could be changed to any other Git or Bug tracker system (should be written by your own). ## How does it work 1. Webhook (on push) should be set up on the git server. 2. Git itself should be installed where this application is started 3. Extend `IssueHandler` and implement your own workflow with your bug-tracker system. IE, set **fixVersion** directly to each task or only for story without subtasks or just add comment where it was merged. For myself I used it together with [automationforjira] for further no-code processing of received data. 4. Extend `WebHookDataParser` if you use as git server something different from BitBucket. ## Variables to override if needed - `TRACKED_BRANCH_REGEXP` : which branches do we track, by default it is set to `(release/.*|hotfix/.*|support/.*|develop|dev)`. Here is used git-flow branch model - `MERGE_PATTERN_SEARCH_TO_SKIP` : merge pattern which should not be tracked, by default it is set to `Merge.*((release\/|support\/|hotfix\/)|(tag)).*(develop|dev).*`. - `WHITE_LISTED_REPOS` : repositories' name which available for further processing, by default [automationforjira]: https://automationforjira.com/

eng_Latn

3b99977fe529ac87511f56fefbf2a37cb5867ca7

md

Markdown

content/post/2013-03-01-a-bit-more-on-the-fire.md

mnsh16/blog

3d9936f0a406229679be405402c50d267fd166bd

2017-05-01T04:58:04.000Z

2021-04-06T18:58:30.000Z

content/post/2013-03-01-a-bit-more-on-the-fire.md

mnsh16/blog

3d9936f0a406229679be405402c50d267fd166bd

2017-04-30T04:49:24.000Z

2021-06-13T20:17:58.000Z

content/post/2013-03-01-a-bit-more-on-the-fire.md

mnsh16/blog

3d9936f0a406229679be405402c50d267fd166bd

2017-04-30T05:27:33.000Z

2021-02-13T09:56:51.000Z

--- title: A bit more on the fire author: Karl Broman date: '2013-03-01' categories: - News tags: - news slug: a-bit-more-on-the-fire --- The [Daily Cardinal](http://host.madison.com/daily-cardinal/) reports that [there were no overhead sprinklers](http://tinyurl.com/cuyhdtl) in the area of the fire yesterday. Fire fighters thought that sprinklers had gone off, but it was really a broken water pipe. And there are no sprinklers in my office, either. I thought they were required, but I guess only in new construction. There's a [short TV report](http://www.nbc15.com/home/headlines/Fire-Reported-at-UW-Medical-Science-Building-193836731.html) (after a commercial) at the [channel 15 site](http://www.nbc15.com). A graduate student interviewed said, "I have multiple copies of my data, but they're all in that building." I hope we all learn from this: Off-site backups (at least with something like [DropBox](http://www.dropbox.com)) are important.

eng_Latn

3b99a0eccd69acbc9387dfed1535cd4008e5bbd2

md

Markdown

skype/skype-ps/skype/Remove-CsAnalogDevice.md

v-anpasi/office-powershell-docs

40f1950d2157f58117f34fe779332a58df0fe6b1

2021-05-31T15:24:18.000Z

2021-05-31T15:24:18.000Z

skype/skype-ps/skype/Remove-CsAnalogDevice.md

v-anpasi/office-powershell-docs

40f1950d2157f58117f34fe779332a58df0fe6b1

skype/skype-ps/skype/Remove-CsAnalogDevice.md

v-anpasi/office-powershell-docs

40f1950d2157f58117f34fe779332a58df0fe6b1

--- external help file: applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 schema: 2.0.0 --- # Remove-CsAnalogDevice ## SYNOPSIS **Below Content Applies To:** Lync Server 2010 Removes an existing device from the collection of analog devices that can be managed by using Microsoft Lync Server 2010. An analog device is a telephone or other device that is connected to the public switched telephone network (PSTN). **Below Content Applies To:** Lync Server 2013 Removes an existing device from the collection of analog devices that can be managed by using Lync Server. An analog device is a telephone or other device that is connected to the public switched telephone network (PSTN). This cmdlet was introduced in Lync Server 2010. **Below Content Applies To:** Skype for Business Server 2015 Removes an existing device from the collection of analog devices that can be managed by using Skype for Business Server 2015. An analog device is a telephone or other device that is connected to the public switched telephone network (PSTN). This cmdlet was introduced in Lync Server 2010. ## SYNTAX ``` Remove-CsAnalogDevice [-Identity] <UserIdParameter> [-WhatIf] [-Confirm] [<CommonParameters>] ``` ## DESCRIPTION **Below Content Applies To:** Lync Server 2010 Analog devices include telephones, fax machines, modems, and teletype/telecommunication devices for the deaf (TTY/TDD) devices connected to the public switched telephone network (PSTN). Unlike devices that take advantage of Enterprise Voice (the Voice over Internet Protocol (VoIP) solution offered by Microsoft), analog devices do not transmit information by using digital packets. Instead, information is transmitted by using a continuous signal. This signal is commonly referred to as an analog signal; hence the term "analog devices." In order to enable administrators to manage analog devices for organizations, Lync Server 2010 lets you associate analog devices with Active Directory contact objects. After a device has been associated with a contact object, you can then manage the analog device by assigning policies and dial plans to the contact. Over time, you might need to delete a contact object associated with an analog device. For example, if you phase out all of your fax machines, you will no longer need to have analog devices (and contact objects) associated with those machines. The Remove-CsAnalogDevice cmdlet provides a way for you to delete analog devices. When you run this cmdlet, the device will be deleted from the list of analog devices returned by Get-CsAnalogDevice. Additionally, the contact object associated with that device will be deleted from Active Directory Domain Services (AD DS). Who can run this cmdlet: By default, members of the following groups are authorized to run the Remove-CsAnalogDevice cmdlet locally: RTCUniversalUserAdmins. Permissions to run this cmdlet for specific sites or specific Active Directory organizational units (OUs) can be assigned by using the Grant-CsOUPermission cmdlet. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt: Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Remove-CsAnalogDevice"} **Below Content Applies To:** Lync Server 2013 Analog devices include telephones, fax machines, modems, and teletype/telecommunication device for the deaf (TTY/TDD) devices connected to the public switched telephone network (PSTN). Unlike devices that take advantage of Enterprise Voice (the Voice over Internet Protocol (VoIP) solution offered by Microsoft), analog devices do not transmit information by using digital packets. Instead, information is transmitted by using a continuous signal. This signal is commonly referred to as an analog signal; hence the term "analog devices." In order to enable administrators to manage analog devices for organizations, Lync Server lets you associate analog devices with Active Directory contact objects. After a device has been associated with a contact object, you can then manage the analog device by assigning policies and dial plans to the contact. Over time, you might need to delete a contact object associated with an analog device. For example, if you phase out all of your fax machines, you will no longer need to have analog devices (and contact objects) associated with those machines. The Remove-CsAnalogDevice cmdlet provides a way for you to delete analog devices. When you run this cmdlet, the device will be deleted from the list of analog devices returned by Get-CsAnalogDevice. Additionally, the contact object associated with that device will be deleted from Active Directory Domain Services (AD DS). Who can run this cmdlet: By default, members of the following groups are authorized to run the Remove-CsAnalogDevice cmdlet locally: RTCUniversalUserAdmins. Permissions to run this cmdlet for specific sites or specific Active Directory organizational units (OUs) can be assigned by using the Grant-CsOUPermission cmdlet. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt: Get-CsAdminRole | Where-Object {$_.Cmdlets -match "Remove-CsAnalogDevice"} **Below Content Applies To:** Skype for Business Server 2015 Analog devices include telephones, fax machines, modems, and teletype/telecommunication device for the deaf (TTY/TDD) devices connected to the public switched telephone network (PSTN). Unlike devices that take advantage of Enterprise Voice (the Voice over Internet Protocol (VoIP) solution offered by Microsoft), analog devices do not transmit information by using digital packets. Instead, information is transmitted by using a continuous signal. This signal is commonly referred to as an analog signal; hence the term "analog devices." In order to enable administrators to manage analog devices for organizations, Skype for Business Server 2015 lets you associate analog devices with Active Directory contact objects. After a device has been associated with a contact object, you can then manage the analog device by assigning policies and dial plans to the contact. Over time, you might need to delete a contact object associated with an analog device. For example, if you phase out all of your fax machines, you will no longer need to have analog devices (and contact objects) associated with those machines. The Remove-CsAnalogDevice cmdlet provides a way for you to delete analog devices. When you run this cmdlet, the device will be deleted from the list of analog devices returned by the Get-CsAnalogDevice cmdlet. Additionally, the contact object associated with that device will be deleted from Active Directory Domain Services. ## EXAMPLES ### -------------------------- Example 1 ------------------------ (Lync Server 2010) ``` Remove-CsAnalogDevice -Identity "CN={e5e7daba-394e-46ec-95a1-1f2a9947aad2},CN=Users,DC=litwareinc,DC=com" ``` Example 1 deletes the analog device that has the Identity CN={e5e7daba-394e-46ec-95a1-1f2a9947aad2},CN=Users,DC=litwareinc,DC=com. ### -------------------------- EXAMPLE 1 -------------------------- (Lync Server 2013) ``` ``` Example 1 deletes the analog device that has the Identity CN={e5e7daba-394e-46ec-95a1-1f2a9947aad2},CN=Users,DC=litwareinc,DC=com. Remove-CsAnalogDevice -Identity "CN={e5e7daba-394e-46ec-95a1-1f2a9947aad2},CN=Users,DC=litwareinc,DC=com" ### -------------------------- EXAMPLE 1 -------------------------- (Skype for Business Server 2015) ``` ``` Example 1 deletes the analog device that has the Identity CN={e5e7daba-394e-46ec-95a1-1f2a9947aad2},CN=Users,DC=litwareinc,DC=com. Remove-CsAnalogDevice -Identity "CN={e5e7daba-394e-46ec-95a1-1f2a9947aad2},CN=Users,DC=litwareinc,DC=com" ### -------------------------- Example 2 ------------------------ (Lync Server 2010) ``` Get-CsAnalogDevice -Filter {DisplayName -eq "Building 14 Receptionist"} | Remove-CsAnalogDevice ``` The command shown in Example 2 deletes any analog devices that have been assigned the display name "Building 14 Receptionist". To carry out this task, the command first calls Get-CsAnalogDevice along with the Filter parameter; the filter value {DisplayName -eq "Building 14 Receptionist"} limits the returned objects to analog devices where the DisplayName property is equal to "Building 14 Receptionist". The returned items are then piped to, and removed by, Remove-CsAnalogDevice. ### -------------------------- EXAMPLE 2 -------------------------- (Lync Server 2013) ``` ``` The command shown in Example 2 deletes any analog devices that have been assigned the display name "Building 14 Receptionist". To carry out this task, the command first calls Get-CsAnalogDevice along with the Filter parameter; the filter value {DisplayName -eq "Building 14 Receptionist"} limits the returned objects to analog devices where the DisplayName property is equal to "Building 14 Receptionist". The returned items are then piped to, and removed by, Remove-CsAnalogDevice. Get-CsAnalogDevice -Filter {DisplayName -eq "Building 14 Receptionist"} | Remove-CsAnalogDevice ### -------------------------- EXAMPLE 2 -------------------------- (Skype for Business Server 2015) ``` ``` The command shown in Example 2 deletes any analog devices that have been assigned the display name "Building 14 Receptionist". To carry out this task, the command first calls the Get-CsAnalogDevice cmdlet along with the Filter parameter; the filter value {DisplayName -eq "Building 14 Receptionist"} limits the returned objects to analog devices where the DisplayName property is equal to "Building 14 Receptionist". The returned items are then piped to, and removed by, the Remove-CsAnalogDevice cmdlet. Get-CsAnalogDevice -Filter {DisplayName -eq "Building 14 Receptionist"} | Remove-CsAnalogDevice ### -------------------------- Example 3 ------------------------ (Lync Server 2010) ``` Get-CsAnalogDevice -Filter {VoicePolicy -eq "RedmondVoicePolicy"} | Remove-CsAnalogDevice ``` The preceding command deletes all of the analog devices that have been assigned the voice policy RedmondVoicePolicy. To do this, Get-CsAnalogDevice and the Filter parameter are used to retrieve all of the analog devices where the VoicePolicy property is equal to RedmondVoicePolicy. The filtered collection is then piped to the Remove-CsAnalogDevice cmdlet, which deletes each item in that collection. ### -------------------------- EXAMPLE 3 -------------------------- (Lync Server 2013) ``` ``` Example 3 deletes all of the analog devices that have been assigned the voice policy RedmondVoicePolicy. To do this, Get-CsAnalogDevice and the Filter parameter are used to retrieve all of the analog devices where the VoicePolicy property is equal to RedmondVoicePolicy. The filtered collection is then piped to the Remove-CsAnalogDevice cmdlet, which deletes each item in that collection. Get-CsAnalogDevice -Filter {VoicePolicy -eq "RedmondVoicePolicy"} | Remove-CsAnalogDevice ### -------------------------- EXAMPLE 3 -------------------------- (Skype for Business Server 2015) ``` ``` Example 3 deletes all of the analog devices that have been assigned the voice policy RedmondVoicePolicy. To do this, the Get-CsAnalogDevice cmdlet and the Filter parameter are used to retrieve all of the analog devices where the VoicePolicy property is equal to RedmondVoicePolicy. The filtered collection is then piped to the Remove-CsAnalogDevice cmdlet, which deletes each item in that collection. Get-CsAnalogDevice -Filter {VoicePolicy -eq "RedmondVoicePolicy"} | Remove-CsAnalogDevice ### -------------------------- Example 4 ------------------------ (Lync Server 2010) ``` Get-CsAnalogDevice -Filter {AnalogFax -eq $True} | Remove-CsAnalogDevice ``` The command shown in Example 4 removes all the analog fax machines currently in use in the organization. To carry out this task, Get-CsAnalogDevice is called first along with the Filter parameter; the filter value {AnalogFax -eq $True} picks out only those devices where the AnalogFax property is equal to True. In turn, this filtered collection is piped to Remove-CsAnalogDevice, which removes each item in the collection. ### -------------------------- EXAMPLE 4 -------------------------- (Lync Server 2013) ``` ``` The command shown in Example 4 removes all the analog fax machines currently in use in the organization. To carry out this task, Get-CsAnalogDevice is called first along with the Filter parameter; the filter value {AnalogFax -eq $True} picks out only those devices where the AnalogFax property is equal to True. In turn, this filtered collection is piped to Remove-CsAnalogDevice, which removes each item in the collection. Get-CsAnalogDevice -Filter {AnalogFax -eq $True} | Remove-CsAnalogDevice ### -------------------------- EXAMPLE 4 -------------------------- (Skype for Business Server 2015) ``` ``` The command shown in Example 4 removes all the analog fax machines currently in use in the organization. To carry out this task, the Get-CsAnalogDevice cmdlet is called first along with the Filter parameter; the filter value {AnalogFax -eq $True} picks out only those devices where the AnalogFax property is equal to True. In turn, this filtered collection is piped to the Remove-CsAnalogDevice cmdlet, which removes each item in the collection. Get-CsAnalogDevice -Filter {AnalogFax -eq $True} | Remove-CsAnalogDevice ## PARAMETERS ### -Identity **Below Content Applies To:** Lync Server 2010 Unique identifier for the analog device to be removed. Analog devices are identified by using the Active Directory distinguished name (DN) of the associated contact object. By default, these devices, use a GUID (globally unique identifier) as their common name; that means analog devices will typically have an Identity similar to this: CN={ce84964a-c4da-4622-ad34-c54ff3ed361f},OU=Redmond,DC=Litwareinc,DC=com. Because of that you might find it easier to retrieve analog devices by using the Get-CsAnalogDevice cmdlet, and then piping the returned objects to Remove-CsAnalogDevice. **Below Content Applies To:** Lync Server 2013 Unique identifier for the analog device to be removed. Analog devices are identified by using the Active Directory distinguished name (DN) of the associated contact object. By default, these devices, use a globally unique identifier (GUID) as their common name; that means analog devices will typically have an Identity similar to this: CN={ce84964a-c4da-4622-ad34-c54ff3ed361f},OU=Redmond,DC=Litwareinc,DC=com. Because of that you might find it easier to retrieve analog devices by using the Get-CsAnalogDevice cmdlet, and then piping the returned objects to Remove-CsAnalogDevice. **Below Content Applies To:** Skype for Business Server 2015 Unique identifier for the analog device to be removed. Analog devices are identified by using the Active Directory distinguished name (DN) of the associated contact object. By default, these devices, use a globally unique identifier (GUID) as their common name; that means analog devices will typically have an Identity similar to this: CN={ce84964a-c4da-4622-ad34-c54ff3ed361f},OU=Redmond,DC=Litwareinc,DC=com. Because of that you might find it easier to retrieve analog devices by using the Get-CsAnalogDevice cmdlet, and then piping the returned objects to the Remove-CsAnalogDevice cmdlet. ```yaml Type: UserIdParameter Parameter Sets: (All) Aliases: Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 Required: True Position: 1 Default value: None Accept pipeline input: True (ByPropertyName, ByValue) Accept wildcard characters: False ``` ### -WhatIf Describes what would happen if you executed the command without actually executing the command. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: wi Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Confirm Prompts you for confirmation before executing the command. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf Applicable: Lync Server 2010, Lync Server 2013, Skype for Business Server 2015 Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUTS ### Microsoft.Rtc.Management.ADConnect.Schema.OCSADAnalogDeviceContact object. Remove-CsAnalogDevice accepts pipelined instances of the analog device object. ### Microsoft.Rtc.Management.ADConnect.Schema.OCSADAnalogDeviceContact object. The Remove-CsAnalogDevice cmdlet accepts pipelined instances of the analog device object. ## OUTPUTS ### Remove-CsAnalogDevice deletes existing instances of the Microsoft.Rtc.Management.ADConnect.Schema.OCSADAnalogDeviceContact object. ### The Remove-CsAnalogDevice cmdlet deletes existing instances of the Microsoft.Rtc.Management.ADConnect.Schema.OCSADAnalogDeviceContact object. ## NOTES ## RELATED LINKS [Online Version](http://technet.microsoft.com/EN-US/library/61250894-fde6-476d-aaa2-ec5692af02b3(OCS.14).aspx) [Get-CsAnalogDevice]() [Move-CsAnalogDevice]() [New-CsAnalogDevice]() [Set-CsAnalogDevice]() [Online Version](http://technet.microsoft.com/EN-US/library/61250894-fde6-476d-aaa2-ec5692af02b3(OCS.15).aspx) [Online Version](http://technet.microsoft.com/EN-US/library/61250894-fde6-476d-aaa2-ec5692af02b3(OCS.16).aspx)

eng_Latn

3b9a49e777566be27c0e47c880f200734ed177ee

md

Markdown

README.md

BioMaRu/indiedish-test-react

4f80fc4cc86724f938afbc6db66bc6746798a9a1

README.md

BioMaRu/indiedish-test-react

4f80fc4cc86724f938afbc6db66bc6746798a9a1

README.md

BioMaRu/indiedish-test-react

4f80fc4cc86724f938afbc6db66bc6746798a9a1

# React Version Pure React using ES6(ECMA2015) syntax, no jquery, no bootstrap, no other library ## How to run 1. **Install [Node 4.0.0 or greater](https://nodejs.org)** - (5.0 or greater is recommended for optimal build performance). 2. **Clone the project**. `git clone https://github.com/BioMaRu/indiedish-test-react.git`. 3. **Go to project directory**. `cd indiedish-test-react` 4. **Install Dependencies**. `npm install` 5. **Run the app**. `npm start`

eng_Latn

3b9adbfa47e241bafdfe12cf9b8d1ad31e94c532

md

Markdown

docs/description/E2522.md

h314to/codacy-cfn-lint-old

863a22f22c6d2d52c5d920e10b9a3eb25511d650

docs/description/E2522.md

h314to/codacy-cfn-lint-old

863a22f22c6d2d52c5d920e10b9a3eb25511d650

docs/description/E2522.md

h314to/codacy-cfn-lint-old

863a22f22c6d2d52c5d920e10b9a3eb25511d650

Making sure CloudFormation properties that require at least one property from a list. More than one can be included. [SOURCE](https://github.com/awslabs/cfn-python-lint)

eng_Latn

3b9b16d5502d2ac275be685ae50435b89cf196c9

md

Markdown

README.md

ironsideshu/SnowplowDashDBConn

cbffdf56d132f01083f667b5e7bda3d12a1577f1

README.md

ironsideshu/SnowplowDashDBConn

cbffdf56d132f01083f667b5e7bda3d12a1577f1

README.md

ironsideshu/SnowplowDashDBConn

cbffdf56d132f01083f667b5e7bda3d12a1577f1

## WIP Custom jar for pushing shredded Snowplow part files in a HDFS into DashDB tables. Current iteration only facilitate movement of atomic-events part files into a DashDB 'events' table. Build with Maven (mvn install) Mandatory jar arguments: \-\-dbhost \<DashDB Host (no port)\> \-\-dbtable \<DashDB Table\> \-\-dbuser \<DashDB Username\> \-\-dbpassword \<DashDB Password\> \-\-hdfspath \<Part Files folder in HDFS\>

eng_Latn

3b9bcd6c5f3482271f53031263f4df2a11cff6ab

md

Markdown

doc/compiler.md

JeffTheK/ubiquit

d3f9c3780d73613d796bf7a30b9e96ebd9465730

2021-06-27T07:29:09.000Z

2022-03-09T12:33:48.000Z

doc/compiler.md

JeffTheK/ubiquit

d3f9c3780d73613d796bf7a30b9e96ebd9465730

2021-06-26T13:43:34.000Z

2022-03-09T12:34:55.000Z

doc/compiler.md

JeffTheK/ubiquit

d3f9c3780d73613d796bf7a30b9e96ebd9465730

2021-06-26T13:34:18.000Z

2022-03-09T11:40:42.000Z

# Compiler ## Usage Invoke with `ubc` (short for ubiquit compiler). ## Arguments * `-no-warnings` - disables all warnings * `-debug` - adds extra code for debug, doesn't optimize the code * `-release` - removes debug code, optimizes as much as possible ## Example ````shell ubc src/main.ub src/foo.ub ````

eng_Latn

3b9d8ce8aa7d067d121553a9cc3b796feb59249f

md

Markdown

README.md

wojciech-zurek/kotlin-spring-boot-prometheus-grafana-example

fd15ff1987a61f572ba57b59e797fd0824be6737

2018-04-15T02:57:22.000Z

2022-01-27T11:03:39.000Z

README.md

trongnghia203/kotlin-spring-boot-prometheus-grafana-example

fd15ff1987a61f572ba57b59e797fd0824be6737

README.md

trongnghia203/kotlin-spring-boot-prometheus-grafana-example

fd15ff1987a61f572ba57b59e797fd0824be6737

2018-09-28T17:10:46.000Z

2020-07-20T16:53:40.000Z

# Spring Boot 2.0 metrics with Actuator, Prometheus and Grafana example  ## Intro: - [Spring Boot Actuator](https://docs.spring.io/spring-boot/docs/current/reference/html/production-ready.html) - [Prometheus](https://prometheus.io/) - [Grafana](https://grafana.com/) ## How to... implement metrics in Spring Boot and export to Prometheus and Grafana? #### 1. Create new Spring Boot application or use exist one #### 2. Add dependencies to your project ```gradle compile('org.springframework.boot:spring-boot-starter-actuator') runtime("io.micrometer:micrometer-registry-prometheus") ``` #### 3. Expose metrics and prometheus endpoints in application.properties ``` management.endpoints.web.exposure.include=health,info,metrics,prometheus ``` #### 4. Use prepared metrics by Spring creators or create custom metrics for your app Inject MeterRegistry, create and manage your application set of meters. Example: ```kotlin @Autowired fun setCounter(meterRegistry: MeterRegistry) { //counters -> increment value messageCounter = meterRegistry.counter("service.message.counter") operationCounter = meterRegistry.counter("service.message.long.operation.counter") //gauges -> shows the current value of a meter. lastMessageLength = meterRegistry.gauge("service.message.last.message.length", AtomicInteger())!! //shows collection size (queue message, cache size etc...). In real app the collection implementation used should be thread safe. messages = meterRegistry.gaugeCollectionSize("service.message.message.size", emptyList(), mutableListOf())!! //timer -> measures the time taken for short tasks and the count of these tasks. timer = meterRegistry.timer("service.message.long.operation.run.timer") //other meters... } ``` #### 5. Run you application For example: ```bash ./gradlew bootRun ``` #### 6. Check your working metrics (JSON format) ```bash curl http://localhost:8080/actuator/metrics {"names":["jvm.buffer.memory.used","jvm.memory.used","jvm.gc.memory.allocated","jvm.memory.committed","tomcat.sessions.created","tomcat.sessions.expired","tomcat.global.request.max","tomcat.global.error","jvm.gc.max.data.size","service.hello.operation.run.timer","service.message.operation.counter","logback.events","system.cpu.count","jvm.memory.max","jvm.buffer.total.capacity","jvm.buffer.count","process.files.max","jvm.threads.daemon","process.start.time","service.message.counter","tomcat.global.sent","tomcat.sessions.active.max","tomcat.threads.config.max","service.message.last.length","jvm.gc.live.data.size","process.files.open","process.cpu.usage","service.message.message.size","tomcat.servlet.request","process.uptime","tomcat.global.received","system.load.average.1m","tomcat.cache.hit","http.server.requests","jvm.gc.pause","tomcat.servlet.error","tomcat.servlet.request.max","tomcat.cache.access","tomcat.threads.busy","tomcat.sessions.active.current","system.cpu.usage","jvm.threads.live","jvm.classes.loaded","jvm.classes.unloaded","jvm.threads.peak","tomcat.threads.current","tomcat.global.request","jvm.gc.memory.promoted","tomcat.sessions.rejected","tomcat.sessions.alive.max"]}% ``` #### 7. Check your working metrics (Prometheus format) ```bash curl http://localhost:8080/actuator/prometheus # HELP jvm_gc_memory_promoted_bytes_total Count of positive increases in the size of the old generation memory pool before GC to after GC # TYPE jvm_gc_memory_promoted_bytes_total counter jvm_gc_memory_promoted_bytes_total 24576.0 ... ``` #### 8. Check your custom metrics (Prometheus format) ```bash curl -s http://localhost:8080/actuator/prometheus |grep service_message # HELP service_message_last_message_length # TYPE service_message_last_message_length gauge service_message_last_message_length 18.0 # HELP service_message_message_size # TYPE service_message_message_size gauge service_message_message_size 4.0 # HELP service_message_long_operation_run_timer_seconds # TYPE service_message_long_operation_run_timer_seconds summary service_message_long_operation_run_timer_seconds_count 74.0 service_message_long_operation_run_timer_seconds_sum 265.597506794 service_message_long_operation_run_timer_seconds_max 6.9341843 ... ``` #### 9. Add Spring Boot app scrape config to prometheus.yml [More info](https://prometheus.io/docs/prometheus/latest/configuration/configuration/) ``` - job_name: 'spring-boot-example-metric' # Override the global default and scrape targets from this job every 5 seconds. scrape_interval: 5s metrics_path: '/actuator/prometheus' # path to spring boot metrics static_configs: - targets: ['spring-boot-example-metric:8080'] # host and port ``` #### 10. Open Prometheus dashboard and check Spring Boot endpoint status (menu: Status/Targets)  #### 11. Add dashboard for system or custom metric (menu: Graph)  #### 12. Open Grafana dashboard and add Prometheus data source  #### 13. Create new dashboard for system or custom metric  or use already created. For example: [JVM (Micrometer) Dashboard](https://grafana.com/dashboards/4701) ## Working example ### Status [](https://travis-ci.org/wojciech-zurek/kotlin-spring-boot-prometheus-grafana-example) ### Requirements Docker and docker-compose ### Stack - kotlin - gradle - spring boot 2.0 (mvc, actuator) - docker and docker-compose (I'm using Linux) - prometheus - grafana ### Download ```bash git clone https://github.com/wojciech-zurek/kotlin-spring-boot-prometheus-grafana-example.git ``` ### How to build and run #### 1. Compile project and build docker images ```bash cd kotlin-spring-boot-prometheus-grafana-example/ ./build.sh ``` #### 2. Check docker images ```bash docker images REPOSITORY TAG IMAGE ID CREATED SIZE eu.wojciechzurek/spring-boot-example-metric 0.0.1 3499dee25307 About an hour ago 123MB eu.wojciechzurek/spring-boot-example-metric latest 3499dee25307 About an hour ago 123MB eu.wojciechzurek/custom-prometheus 0.0.1 17aaa34718de About an hour ago 112MB eu.wojciechzurek/custom-prometheus latest 17aaa34718de About an hour ago 112MB grafana/grafana latest 18cae91912fc 5 days ago 301MB ``` #### 3. Run docker-compose ```bash cd kotlin-spring-boot-prometheus-grafana-example/ docker-compose up ``` #### 4. Check docker containers status ```bash docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 449f44b8a1d5 eu.wojciechzurek/custom-prometheus:latest "/bin/prometheus --c…" 41 minutes ago Up 41 minutes 0.0.0.0:9090->9090/tcp kotlinspringbootprometheusgrafanaexample_prometheus_1 348e2b0150be grafana/grafana "/run.sh" 41 minutes ago Up 41 minutes 0.0.0.0:3000->3000/tcp kotlinspringbootprometheusgrafanaexample_grafana_1 ab91021df26b eu.wojciechzurek/spring-boot-example-metric:latest "java -Djava.securit…" 41 minutes ago Up 41 minutes 0.0.0.0:8080->8080/tcp spring-boot-example-metric ``` #### 5. Services URL - example spring boot controller: http://localhost:8080/message - Prometheus dashboard http://localhost:9000/ - Grafana dashboard (**login: admin, password: admin**) http://localhost:3000/ #### 6. Open Grafana dashboard and add Prometheus type, direct access source (HTTP URL: http://localhost:9000/) #### 7. Test app and check metrics ```bash curl http://localhost:8080/message Hello Spring World% ``` #### 8. Optional upload example dashboard Go to: [http://localhost:3000/dashboard/import](http://localhost:3000/dashboard/import) and import [grafana-spring-boot-example.json](/grafana-spring-boot-example.json)

eng_Latn

3b9e5e9cd18a1626ed80e5a000083351033e7a9d

md

Markdown

articles/mobile-engagement/mobile-engagement-ios-release-notes.md

OpenLocalizationTestOrg/azure-docs-pr15_pl-PL

18fa7535e7cdf4b159e63a40776995fa95f1f314

articles/mobile-engagement/mobile-engagement-ios-release-notes.md

OpenLocalizationTestOrg/azure-docs-pr15_pl-PL

18fa7535e7cdf4b159e63a40776995fa95f1f314

articles/mobile-engagement/mobile-engagement-ios-release-notes.md

OpenLocalizationTestOrg/azure-docs-pr15_pl-PL

18fa7535e7cdf4b159e63a40776995fa95f1f314

<properties pageTitle="Azure iOS zaangażowania Mobile SDK wersji | Microsoft Azure" description="Najnowszych aktualizacji i procedury dla systemu iOS SDK dla zaangażowania Mobile Azure" services="mobile-engagement" documentationCenter="mobile" authors="piyushjo" manager="erikre" editor="" /> <tags ms.service="mobile-engagement" ms.workload="mobile" ms.tgt_pltfrm="mobile-ios" ms.devlang="objective-c" ms.topic="article" ms.date="09/12/2016" ms.author="piyushjo" /> #<a name="azure-mobile-engagement-ios-sdk-release-notes"></a>Informacje o wersji Azure iOS zaangażowania Mobile SDK ##<a name="400-09122016"></a>4.0.0 (2016-09-12) - Stałe powiadomienie nie actioned na urządzeniach z systemem iOS 10. - Oznaczanie jako przestarzałego XCode 7. ##<a name="324-06302016"></a>3.2.4 (2016-06-30) - Stały agregacji między dzienniki techniczne i inne dzienniki. ##<a name="323-06072016"></a>3.2.3 (2016-06-07) - Stałe błędu którym dostarczenia opinii nie jest zgłoszony podczas aplikacja działa w tle. - Zoptymalizowane, wysyłanie techniczne dzienników. ##<a name="322-04072016"></a>3.2.2 (2016-04-07) - Stały błędu na anulowanie żądania HTTP, który czasami powoduje awarię. ##<a name="321-12112015"></a>3.2.1 (2015-12-11) - Stałe opóźnienie wyzwolenia nowego wystąpienia aplikacji przez powiadomienie o głębokości łącza ##<a name="320-10082015"></a>3.2.0 (2015-10-08) - Włączone Bitcode w zestawie SDK, aby nadać mu Praca z **Xcode 7**. - Stały błędy związane z powiadomienia w aplikacji app. - Powiadomienia w aplikacji wprowadzone niezawodne w przypadku baterii i inne scenariusze tego typu. - Usunięte dodatkowe konsoli dzienniki generowane przez 3 biblioteki stron. ##<a name="310-08262015"></a>3.1.0 (2015-08-26) - Naprawianie błędu zgodności iOS 9 z biblioteką programu innej firmy. Została ona powoduje awarię podczas wysyłania sprawdza wyniki, informacje o aplikacji lub dodatkowe dane. ##<a name="300-06192015"></a>3.0.0 (2015-06-19) - Telefon komórkowy zaangażowania używa odbiorcze powiadomienia Push. - Porzucone pomocy technicznej dla systemu iOS 4.X. Począwszy od tej wersji docelowej wdrażania aplikacji musi mieć co najmniej iOS 6. ##<a name="220-05212015"></a>2.2.0 (2015-05-21) - Identyfikator urządzenia zaangażowania Mobile dla urządzeń < iOS 6 teraz jest oparty na identyfikator GUID wygenerowane podczas instalacji. ##<a name="210-04242015"></a>2.1.0 (2015-04-24) - Dodano szybkiej zgodności. - Kliknięcie powiadomienia o akcji, który jest używany adres URL teraz wykonać prawo, po otwarciu aplikacji. - Dodano brakujący plik nagłówka w pakiecie SDK. - Rozwiązanie problemu związanego wyłączenie reporter awarie zaangażowania Mobile. ##<a name="200-02172015"></a>2.0.0 (2015-02-17) - Początkowy wersji Azure zaangażowania urządzeń przenośnych - Identyfikator aplikacji/sdkKey konfiguracji zastępuje Konfiguracja parametry połączenia. - Usunięte interfejsu API do wysyłania i odbierania wiadomości XMPP dowolnego z dowolnego jednostek XMPP. - Usunięte interfejsu API do wysyłania i odbierania wiadomości między urządzeniami. - Ulepszenia zabezpieczeń. - Śledzenie SmartAd usunięte.

pol_Latn

3ba1596b93976781fdf4c2a40cb6986f092baa84

md

Markdown

container/docker.md

kawakami-o3/til

0c21499ef5aed237aa0d2f839069cfe87a8e1fe5

2019-04-16T14:37:06.000Z

2019-04-16T14:37:06.000Z

container/docker.md

kawakami-o3/til

0c21499ef5aed237aa0d2f839069cfe87a8e1fe5

container/docker.md

kawakami-o3/til

0c21499ef5aed237aa0d2f839069cfe87a8e1fe5

# docker https://docs.docker.com/get-started/ https://jawsdays2019.jaws-ug.jp/session/1527/ ## 逆引きtips ### イメージビルド ``` cd dockerfile-dir docker build -t image-name:image-tag . ``` ### コンテナ起動 ``` docker run --rm -it --init -p 3000:3000 -v from-dir:to-dir -u `id -u`:`id -g` image-name:image-tag ``` * `--rm` : 終了時にコンテナ削除 * `--it` : `-i` と `-t`. 入手力を保持. 逆は `-d`. * `-p` : ポート指定 * `-v` : ディレクトリ指定 * `-u` : UID, GID 指定 ### イメージ削除 ``` docker image rm image-id docker image prune ``` ### コンテナ削除 ``` docker container rm container-id docker container prune ``` ## docker run が失敗するケース1 ``` docker: Error response from daemon: failed to create endpoint pedantic_margulis on network bridge: failed to add the host (...) <=> sandbox (...) pair interfaces: operation not supported. ``` というエラーが出る場合は、カーネル更新が行われた可能性がある。再起動後に再度 `docker run` を試してみると良い。 * https://qastack.jp/server/738773/docker-failed-to-add-the-pair-interfaces-operation-not-supported

yue_Hant

3ba173df9964e6ff2d21f2671c9af7922613d52c

md

Markdown

docs/javascript/DailyNote/README.md

Laulou-hsh/VuePressBlog

953bdc72683e6acd757cc00914eba1450a2998b6

2021-01-18T09:01:06.000Z

2021-01-18T09:01:06.000Z

docs/javascript/DailyNote/README.md

Laulou-hsh/VuePressBlog

953bdc72683e6acd757cc00914eba1450a2998b6

2020-11-06T11:55:25.000Z

2020-12-07T03:32:35.000Z

docs/javascript/DailyNote/README.md

githubsgeek/VuePressBlog

953bdc72683e6acd757cc00914eba1450a2998b6

--- title: 日常笔记 sidebar: auto --- <style> .go-to-top { display: block !important; } </style> * 2021年07月03日 > [一行 JS 实现功能的代码](2021703.md) > * 2021年06月18日 > [理解JS闭包9大使用场景](20210618.md) * 2021年04月23日 > [字节：如何模拟实现 new 操作符](20210423.md) * 2021年03月16日 > [常用的前端JavaScript方法封装](20210316.md) * 2021年03月02日 > [JS语法 ES6、ES7、ES8、ES9、ES10、ES11、ES12新特性](20210302.md) * 2021年02月20日 > [JavaScript正则表达式](20210220.md) * 2021年01月15日 > [JavaScript防抖和节流](20210115.md) * 2020年12月23日 > [8个常用的JavaScript数组方法](20201223.md)

yue_Hant

3ba291c0ed576a06862b2ac3d48dac7ef271215a

md

Markdown

campus/README.md

MuhammadZubair210/InstagramExpo

30369bd95a63cd362cb888726cbc9525152578a9

campus/README.md

MuhammadZubair210/InstagramExpo

30369bd95a63cd362cb888726cbc9525152578a9

2021-09-01T06:20:08.000Z

2021-09-01T16:45:03.000Z

campus/README.md

MuhammadZubair210/InstagramExpo

30369bd95a63cd362cb888726cbc9525152578a9

Install Libs: ```sh yarn ``` Run with: ```sh exp start ```

eng_Latn

3ba32569b47725028aff604bcf1272b48543f9ce

md

Markdown

docs/extensibility/debugger/reference/idebugcanstopevent2-canstop.md

MicrosoftDocs/visualstudio-docs.tr-tr

ff0c41f814d042e7d4a0e457839db4a191a59f81

2018-09-14T23:12:51.000Z

2021-08-22T21:23:28.000Z

docs/extensibility/debugger/reference/idebugcanstopevent2-canstop.md

huriyilmaz/visualstudio-docs.tr-tr

9459e8aaaeb3441455be384a2b011dbf306ce691

2018-07-20T23:01:49.000Z

2021-04-15T20:00:12.000Z

docs/extensibility/debugger/reference/idebugcanstopevent2-canstop.md

huriyilmaz/visualstudio-docs.tr-tr

9459e8aaaeb3441455be384a2b011dbf306ce691

2018-01-11T11:53:37.000Z

2022-03-06T16:38:31.000Z

--- description: Hata ayıklama altyapısına (DE) geçerli kod konumunda durdurulup durdurulmayacağını bildirir veya yürütmeye devam edin. title: 'IDebugCanStopEvent2:: CanStop | Microsoft Docs' ms.date: 11/04/2016 ms.topic: reference f1_keywords: - IDebugCanStopEvent2::CanStop helpviewer_keywords: - IDebugCanStopEvent2::CanStop ms.assetid: 7d61adbe-6b3d-41f3-86a1-45d9cc01a7f8 author: leslierichardson95 ms.author: lerich manager: jmartens ms.technology: vs-ide-debug ms.workload: - vssdk dev_langs: - CPP - CSharp ms.openlocfilehash: dd575d6bb1afdf296eff6ec3ac3a08a9551618b8 ms.sourcegitcommit: b12a38744db371d2894769ecf305585f9577792f ms.translationtype: MT ms.contentlocale: tr-TR ms.lasthandoff: 09/13/2021 ms.locfileid: "126636369" --- # <a name="idebugcanstopevent2canstop"></a>IDebugCanStopEvent2::CanStop Hata ayıklama altyapısına (DE) geçerli kod konumunda durdurulup durdurulmayacağını bildirir veya yürütmeye devam edin. ## <a name="syntax"></a>Sözdizimi ```cpp HRESULT CanStop ( BOOL fCanStop ); ``` ```csharp int CanStop ( int fCanStop ); ``` ## <a name="parameters"></a>Parametreler `fCanStop`\ 'ndaki `TRUE`Geçerli kod konumunda durmalı sıfır olmayan (), aksi takdirde sıfır ( `FALSE` ). ## <a name="return-value"></a>Dönüş Değeri Başarılı olursa, döndürür `S_OK` ; Aksi takdirde, bir hata kodu döndürür. ## <a name="remarks"></a>Açıklamalar Bu olayın alıcısı genellikle [GetReason](../../../extensibility/debugger/reference/idebugcanstopevent2-getreason.md) yöntemini çağırarak, onun durdurmak istediği nedeni tespit edin ve ardından `IDebugCanStopEvent2::CanStop` yöntemi uygun Yanıtla çağırır. DE duruyorsa, durdurma nedenini açıklayan bir olay gönderir. Tipik olarak gönderilen iki olay, [IDebugBreakEvent2](../../../extensibility/debugger/reference/idebugbreakevent2.md) arabirimi tarafından temsil edilen bir kullanıcı veya sinyal kesmesi ve [IDebugBreakpointEvent2](../../../extensibility/debugger/reference/idebugbreakpointevent2.md) arabirimi tarafından temsil edilen bir kesme noktası olayı vardır. ## <a name="see-also"></a>Ayrıca bkz. - [IDebugCanStopEvent2](../../../extensibility/debugger/reference/idebugcanstopevent2.md) - [IDebugBreakEvent2](../../../extensibility/debugger/reference/idebugbreakevent2.md) - [IDebugBreakpointEvent2](../../../extensibility/debugger/reference/idebugbreakpointevent2.md) - [GetReason](../../../extensibility/debugger/reference/idebugcanstopevent2-getreason.md)

tur_Latn

3ba47408992bad9efc5313bfd94703ad4e1eea2b

md

Markdown

README.md

oguzhancokyilmaz/Symfony_KurumsalSite_2013010213025

95e0add8b19aa43e32a9d621f55086e971edeabd

README.md

oguzhancokyilmaz/Symfony_KurumsalSite_2013010213025

95e0add8b19aa43e32a9d621f55086e971edeabd

README.md

oguzhancokyilmaz/Symfony_KurumsalSite_2013010213025

95e0add8b19aa43e32a9d621f55086e971edeabd

"# Symfony_KurumsalSite_2013010213025"

nob_Latn

3ba4f363be48ffe347c0bfc7c45f1972e82a36c5

md

Markdown

_posts/2016-11-03-when-genetic-tests-are-basically-horoscopes.md

drgarybennett/drgarybennett.github.io

c302adf1e9c03adb64dcc7fbfe12cdb0c77d587a

_posts/2016-11-03-when-genetic-tests-are-basically-horoscopes.md

drgarybennett/drgarybennett.github.io

c302adf1e9c03adb64dcc7fbfe12cdb0c77d587a

_posts/2016-11-03-when-genetic-tests-are-basically-horoscopes.md

drgarybennett/drgarybennett.github.io

c302adf1e9c03adb64dcc7fbfe12cdb0c77d587a

--- id: 1274 title: When genetic tests are basically horoscopes date: 2016-11-03T11:27:18+00:00 author: ggbjr layout: post guid: http://drgarybennett.com/?p=1274 permalink: /2016/11/03/when-genetic-tests-are-basically-horoscopes/ categories: - cool tech - digital health ---  Fantastic piece [in today&#8217;s Inside Stat](https://www.statnews.com/2016/11/03/genetic-testing-fitness-nutrition/). > The tips I got back were almost comically generic. One piece of advice from Kinetic Diagnostics on how to compensate for my increased risk of muscle cramping? “Do proper stretching and muscle warm ups before and after exercise.” > > DNAFit’s recommendation to make up for a variant that predisposes me to to see fewer gains from endurance training? “Stay sufficiently hydrated.” > > Kinetic Diagnostics said I was at elevated risk of high blood pressure; DNAFit said I was likely to experience fewer problems with blood pressure. They both offered the same advice, supposedly tailored to my genotype: exercise. > > (When I later asked them about this recommendation, the companies acknowledged that such advice could benefit anyone but insisted that people with my genotype would find it especially useful.) I suspect that this will mostly be interpreted as an indictment of the athletics genetic testing &#8220;industry.&#8221; And, they seem to deserve it. But there&#8217;s a bigger issue here: many similar companies enter the market with laughably limited evidence that their &#8220;personalized recommendations&#8221; are actually informed by science. > Then there were the interpretations that flat-out contradicted one another. > > The tests each looked at different regions of my genome — which may have been necessary to distinguish themselves from their competitors, but which in and of itself suggests just how much this field is in its infancy. So it wasn’t possible to compare the complete results from each company head-to-head. > > But among the scores of data points, I found 20 genetic variants that showed up on two or more test results. The companies all gave me the same genetic readout on those variants, so I have little doubt they correctly analyzed the cells in the cheek swab I’d sent them. In six cases, however, the interpretation I got from one company directly contradicted the interpretation from another. I&#8217;m sensitive to the idea that [the long time it takes to generate] evidence frequently slows the process of bringing innovative tools to market. However, this is a helpful reminder that speed can also disadvantage consumers (while rewarding founders).

eng_Latn

3ba67ddbef29ef0d7816e0238b52f0f792fb7b14

md

Markdown

notes.md

Suranjandas7/Tropicana

fcfe020ba95cb6d0bbc597b1aa99d5076e9093b2

notes.md

Suranjandas7/Tropicana

fcfe020ba95cb6d0bbc597b1aa99d5076e9093b2

notes.md

Suranjandas7/Tropicana

fcfe020ba95cb6d0bbc597b1aa99d5076e9093b2

To-do: 1. Write a testing framework 2. Implement Pandas

eng_Latn

3ba6b8f050892f0325d5ecffb32b7a940c216649

md

Markdown

README.md

asaladino/smart-form-helper

9df95386b559c262ae8a0d6eaed76f3f52d08197

README.md

asaladino/smart-form-helper

9df95386b559c262ae8a0d6eaed76f3f52d08197

README.md

asaladino/smart-form-helper

9df95386b559c262ae8a0d6eaed76f3f52d08197

# Smart Form Helper Helps generate c# from an Ektron smart form xsd. This is useful when you have a widget that is dependant on a smart form. This app is as is and will never be updated. In fact, may your god have mercy on you if you have Ektron (or any of it's incarnations) as your cms. There are plenty of real cms' out there, they are free and superior.  One item to note, make sure you know where the xsd.exe executable is. 

eng_Latn