BramVanroy/stack_md_lid · Datasets at Hugging Face

d0b515895741523122f027d2315e835cc5f34263

3,715

md

Markdown

docs/interfaces/_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md

cuonglnhust/instagram-private-api-tcom

9ee21e8356b7bfef5ee9ddc2fdf72d53a62d93eb

[ "MIT" ]

2

2020-08-29T14:35:20.000Z

2020-09-09T13:02:54.000Z

docs/interfaces/_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md

cuonglnhust/instagram-private-api-tcom

9ee21e8356b7bfef5ee9ddc2fdf72d53a62d93eb

[ "MIT" ]

null

docs/interfaces/_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md

cuonglnhust/instagram-private-api-tcom

9ee21e8356b7bfef5ee9ddc2fdf72d53a62d93eb

[ "MIT" ]

null

> **[instagram-private-api-tcom](../README.md)** [Globals](../README.md) / ["responses/list-reel-media-viewer.feed.response"](../modules/_responses_list_reel_media_viewer_feed_response_.md) / [ListReelMediaViewerFeedResponseLocation](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md) / # Interface: ListReelMediaViewerFeedResponseLocation ## Hierarchy * **ListReelMediaViewerFeedResponseLocation** ## Index ### Properties * [address](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#address) * [city](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#city) * [external_source](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#external_source) * [facebook_places_id](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#facebook_places_id) * [lat](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#lat) * [lng](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#lng) * [name](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#name) * [pk](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#pk) * [short_name](_responses_list_reel_media_viewer_feed_response_.listreelmediaviewerfeedresponselocation.md#short_name) ## Properties ### address • **address**: *string* *Defined in [responses/list-reel-media-viewer.feed.response.ts:182](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L182)* ___ ### city • **city**: *string* *Defined in [responses/list-reel-media-viewer.feed.response.ts:183](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L183)* ___ ### external_source • **external_source**: *string* *Defined in [responses/list-reel-media-viewer.feed.response.ts:187](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L187)* ___ ### facebook_places_id • **facebook_places_id**: *number* *Defined in [responses/list-reel-media-viewer.feed.response.ts:188](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L188)* ___ ### lat • **lat**: *number* *Defined in [responses/list-reel-media-viewer.feed.response.ts:186](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L186)* ___ ### lng • **lng**: *number* *Defined in [responses/list-reel-media-viewer.feed.response.ts:185](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L185)* ___ ### name • **name**: *string* *Defined in [responses/list-reel-media-viewer.feed.response.ts:181](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L181)* ___ ### pk • **pk**: *number* *Defined in [responses/list-reel-media-viewer.feed.response.ts:180](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L180)* ___ ### short_name • **short_name**: *string* *Defined in [responses/list-reel-media-viewer.feed.response.ts:184](https://github.com/cuonglnhust/instagram-private-api-tcom/blob/3e16058/src/responses/list-reel-media-viewer.feed.response.ts#L184)*

39.105263

279

0.805653

eng_Latn

0.135131

d0b520f7e161543a92dcfead440862a26266d1d9

345

md

Markdown

wiki/translations/it/Category_Inspection.md

dwhr-pi/FreeCAD-documentation

0c889672d80e7969dcabe83f5ddf503e72a4f5bb

[ "CC0-1.0" ]

null

wiki/translations/it/Category_Inspection.md

dwhr-pi/FreeCAD-documentation

0c889672d80e7969dcabe83f5ddf503e72a4f5bb

[ "CC0-1.0" ]

null

wiki/translations/it/Category_Inspection.md

dwhr-pi/FreeCAD-documentation

0c889672d80e7969dcabe83f5ddf503e72a4f5bb

[ "CC0-1.0" ]

null

# Category:Inspection/it This category lists pages related to the [Inspection Workbench/it](Inspection_Workbench/it.md). ### Contents: [Artwork Inspection/it](Artwork_Inspection/it.md) [Inspection Workbench/it](Inspection_Workbench/it.md) --- ![](images/Right_arrow.png) [documentation index](../README.md) > Category:Inspection/it

26.538462

107

0.750725

yue_Hant

0.650783

d0b6105b94d98a04c21732de2144c68ea29644f9

2,361

md

Markdown

posts/2016/10/grodno-historic-context/fara.md

irnc/notes

9eb54cb845c2b05dac54f491129b197c9492b03a

[ "MIT" ]

3

2017-02-24T09:44:37.000Z

2017-07-07T10:53:32.000Z

posts/2016/10/grodno-historic-context/fara.md

irnc/notes

9eb54cb845c2b05dac54f491129b197c9492b03a

[ "MIT" ]

1

2019-11-28T21:50:01.000Z

2019-11-29T12:36:54.000Z

posts/2016/10/grodno-historic-context/fara.md

irnc/notes

9eb54cb845c2b05dac54f491129b197c9492b03a

[ "MIT" ]

1

2017-03-05T22:08:34.000Z

![][memorial-people] [memorial-people]: 14563419_1117619158316591_2888037775170688986_n.jpg [memorial-people-ref]: https://www.facebook.com/andrzej.poczobut.9/posts/666226263543630?comment_id=666254606874129&reply_comment_id=666578563508400&comment_tracking=%7B%22tn%22%3A%22R%22%7D ![][memorial-text] [memorial-text]: 14606440_1117631641648676_1759854369539394991_n.jpg [memorial-text-ref]: https://www.facebook.com/andrzej.poczobut.9/posts/666226263543630?comment_id=666254606874129&reply_comment_id=666599166839673&comment_tracking=%7B%22tn%22%3A%22R%22%7D --- ![][fara-ruin] [fara-ruin]: 14606256_1117170158361491_5362720091115896236_n.jpg ## Воспоминания > Мимо этого костела в детстве часто проходила. Помню, как из поломанной крыши стая воронья вылетала с карканьем. [1-ref]: https://www.facebook.com/andrzej.poczobut.9/posts/666226263543630?comment_id=666254606874129&reply_comment_id=666290106870579&comment_tracking=%7B%22tn%22%3A%22R0%22%7D > А я с друзьями бегал в этот костел, если он был открыт, чтобы набрать .... тонких длинных трубок для наматывания пряжи - делали длинные палки из трубок или просто гудели, как трубачи :). (Там в последние годы был склад тонко-суконного комбината) [2-ref]: https://www.facebook.com/andrzej.poczobut.9/posts/666226263543630?comment_id=666254606874129&reply_comment_id=666291240203799&comment_tracking=%7B%22tn%22%3A%22R%22%7D --- ![][fara-1940x]: [fara-1940x]: 14556781_1120281184724162_8924969292857527655_o.jpg --- ![Grodno. Ogólny widok][1935] > Grodno. Ogólny widok [ref][1935-ref] - 1935 год. [1935]: 14566263_666622590170664_1165659341494968033_o.jpg [1935-ref]: https://www.facebook.com/photo.php?fbid=1118427431569097&set=p.1118427431569097&type=3&theater --- ![][garniz] > Kościół garnizonowy na mejscu Fary Witoldowej został odbudowany dopiero w latach 20. Na zdjęciu jest pierwsza wersja tego kościoła, a druga - mała wyższy dach. [garniz]: 14567618_1117151741696666_748982303214382299_o.jpg [garniz-ref]: https://www.facebook.com/photo.php?fbid=1117151741696666&set=p.1117151741696666&type=3&theater --- ![1915?][1915?] - судя по наличию столбов, не раньше 1913 года - см. фото 1913, там столбов нет [1915?]: 14543944_1117080921703748_3849031950084709990_o.jpg [1915?-ref]: https://www.facebook.com/photo.php?fbid=1117080921703748&set=p.1117080921703748&type=3&theater

38.080645

247

0.795849

yue_Hant

0.113726

d0b988311f112559ca51d9258902abeb0d82d5ca

1,447

md

Markdown

README.md

pangers/SimpleString

dbe551eb118be5d46e1ed6b77b2ab377db73645b

[ "MIT" ]

1

2018-12-13T06:17:54.000Z

README.md

pangers/SimpleString

dbe551eb118be5d46e1ed6b77b2ab377db73645b

[ "MIT" ]

null

README.md

pangers/SimpleString

dbe551eb118be5d46e1ed6b77b2ab377db73645b

[ "MIT" ]

null

# SimpleString Used to simply style strings in iOS applications with the least amount of friction possible. ## Example ```swift let text: NSAttributedString = "Hello".attributedString .font(with: UIFont.boldSystemFont(ofSize: 32)) .colored(.red) + " World".attributedString .font(with: UIFont.systemFont(ofSize: 18)) .colored(.purple) label.attributedText = text.align(.center) ``` ![Hello World](Images/HelloWorld.png) ## Available APIs ```swift // Styling a string let text: NSAttributedString = "SimpleString".attributedString // Convert string to attributed string .font(with: UIFont.systemFont(ofSize: 24)) // UIFont .colored(.orange) // UIColor .align(.center) // NSTextAlignment .lineBreakMode(.byWordWrapping) // NSLineBreakMode // Combining attributed strings let firstText: NSAttributedString = ... let secondText: NSAttributedString = ... let combinedText: NSAttributedString = firstText + secondText ``` ## Installation ### Cocoapods Add to your `Podfile` ```rb pod 'SimpleString' ``` Then run `pod install`. ### Carthage Add to your `Cartfile` ``` github "pangers/SimpleString" ``` Then run `carthage update`. ## Licence SimpleString is released under an MIT license. See [License.md](License) for more information.

22.968254

94

0.641327

eng_Latn

0.5595

d0b9eee5097ee68bf8155281733f45bfe5d93e72

1,685

md

Markdown

docs/spec/TEMPLATE.md

henrybell/kf

23c5ffded7b3ef07112a5b680f3aa44c40d1724d

[ "Apache-2.0" ]

5

2019-04-30T20:46:30.000Z

2019-05-27T14:25:56.000Z

docs/spec/TEMPLATE.md

henrybell/kf

23c5ffded7b3ef07112a5b680f3aa44c40d1724d

[ "Apache-2.0" ]

165

2019-05-01T15:50:40.000Z

2019-06-25T16:29:17.000Z

docs/spec/TEMPLATE.md

henrybell/kf

23c5ffded7b3ef07112a5b680f3aa44c40d1724d

[ "Apache-2.0" ]

3

2019-05-01T21:48:38.000Z

2019-06-05T18:51:27.000Z

# ConceptName  Cloud Foundry ConceptName are mapped to Kubernetes BackingObjects.  | Action | `kf` Action | |--------|-------------| | Create | create Foo | | Get | get Foo | | List | list Foo | | Set X | get Foo; update `path.to.X`; update Foo | ## Metadata This section contains meta data mappings for the Kubernetes object. ### Labels  * `app.kubernetes.io/managed-by` - set to be `kf`. ### Annotations  * _None_ ### Parent  This resource has namespace as an implicit parent. ## Required Policies  These policies must be enforced to ensure the model remains valid. * _No required policies._ ## Optional Policies  * _No optional policies._

22.171053

80

0.72819

eng_Latn

0.997802

d0ba3457b2ed158ca2ecb2593d21b2a5ee4c315e

567

md

Markdown

docs/client/configuration.md

crybapp/mesa

de6518a9d5a32fb00221622d1dec8a54fe538fd9

[ "MIT" ]

22

2019-10-08T08:36:24.000Z

2020-11-26T15:52:45.000Z

docs/client/configuration.md

mesafoundation/mesa

de6518a9d5a32fb00221622d1dec8a54fe538fd9

[ "MIT" ]

11

2020-01-04T06:05:40.000Z

2020-12-08T12:39:16.000Z

docs/client/configuration.md

mesafoundation/mesa

de6518a9d5a32fb00221622d1dec8a54fe538fd9

[ "MIT" ]

1

2020-09-12T17:13:24.000Z

# Configuration Mesa's Client component allows for the following configuration to be passed in during initialization: ```js { // Optional: enable/disable auto connection to the Mesa server once the client object has been instantiated. Enabled by default. Once disabled, use the 'connect()' method in order to connect the client to the Mesa server autoConnect?: boolean } ``` To supply this config, pass it into the Client constructor as you would with any other configuration: ```js const client = new Client('ws://localhost:4000', { // Options go here }) ```

35.4375

222

0.753086

eng_Latn

0.996819

d0baaea8eba76a01da951ed7313740cbcea1d93b

3,353

md

Markdown

README.md

RamiSh/vsts-node-api

d6507c1188ee90a7df2bca3f9bfc397a2838d2b4

[ "MIT" ]

null

README.md

RamiSh/vsts-node-api

d6507c1188ee90a7df2bca3f9bfc397a2838d2b4

[ "MIT" ]

null

README.md

RamiSh/vsts-node-api

d6507c1188ee90a7df2bca3f9bfc397a2838d2b4

[ "MIT" ]

null

# Visual Studio Team Services Client for Node.js Integrate with Visual Studio Team Services from your Node.js apps. ### Install the library ``` npm install vso-node-api --save ``` ## News 6.3.2 has been released and is out of preview. This release contains the latest generated 4.0 VSTS/TFS api contracts. It also consumes the latest typed-rest-client. Note: as of released 6.3.2 version, the web api create methods need to be async so you must use await. For example, note the `await` [in this sample](https://github.com/Microsoft/vsts-node-api/blob/master/samples/build.ts#L11) ## Get started ### Samples See [samples](./samples) for complete coding examples ### Install the library ``` npm install vso-node-api --save ``` ![Intellisense](docs/intellisense.png) ### Create a connection ```javascript let vsts = require('vso-node-api'); // your collection url let collectionUrl = "https://fabrikam.visualstudio.com/defaultcollection"; // ideally from config let token: string = "cbdeb34vzyuk5l4gxc4qfczn3lko3avfkfqyb47etahq6axpcqha"; let authHandler = vsts.getPersonalAccessTokenHandler(token); let connect = new vsts.WebApi(collectionUrl, authHandler); ``` ### Get an instance of a client ```javascript import * as ba from 'vso-node-api/BuildApi'; let vstsBuild: ba.IBuildApi = connection.getBuildApi(); ``` #### Available clients These clients are available in the new 6.x preview API (`npm install vso-node-api@preview`) * Build * Core * Dashboard * ExtensionManagement * FeatureManagement * FileContainer * Git * Locations * Notification * Policy * Profile * ProjectAnalysis * Release * SecurityRoles * TaskAgent * Task * Test * Tfvc * Work * WorkItemTracking * WorkItemTrackingProcess * WorkItemTrackingProcessDefinitions ### Use the client Coding is easy using linear coding with async/await in typescript ```javascript import * as bi from 'vso-node-api/interfaces/BuildInterfaces'; async function run() { let project: string = 'myProject'; let defs: bi.DefinitionReference[] = await vstsBuild.getDefinitions(project); defs.forEach((defRef: bi.DefinitionReference) => { console.log(defRef.name + ' (' + defRef.id + ')'); }); } run(); ``` ## APIs To see what APIs are available, see the appropriate client interface. For example, [GitApi.ts](https://github.com/Microsoft/vsts-node-api/blob/master/api/GitApi.ts) ## Running Samples Pre-reqs: [Node >= 4.4.7 LTS](https://nodejs.org) and [typescript (tsc) >= 1.8](https://www.npmjs.com/package/typescript) Run `npm install` first Set environment variables using set or export: ```bash API_URL=https://fabrikam.visualstudio.com/defaultcollection // use your token API_TOKEN=cbdeb34vzyuk5l4gxc4qfczn3lko3avfkfqyb47etahq6axpcqha API_PROJECT=myProject ``` Run samples: ```bash $ npm run samples ``` Run a specific sample: ```bash $ npm run samples -- http ``` ## Contributing To contribute to this repository, see the [contribution guide](./CONTRIBUTING.md) ## Code of Conduct This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.

24.474453

332

0.73904

eng_Latn

0.667983

d0bbed8b3a9324ea899097f2bde8d649843b53d5

7,643

md

Markdown

includes/core-changes/windowsforms/5.0/null-args-cause-argumentnullexception.md

turibbio/docs.it-it

2212390575baa937d6ecea44d8a02e045bd9427c

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

null

includes/core-changes/windowsforms/5.0/null-args-cause-argumentnullexception.md

turibbio/docs.it-it

2212390575baa937d6ecea44d8a02e045bd9427c

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

null

includes/core-changes/windowsforms/5.0/null-args-cause-argumentnullexception.md

turibbio/docs.it-it

2212390575baa937d6ecea44d8a02e045bd9427c

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

null

--- ms.openlocfilehash: 00f89e6ae49982917fa7591c3283adec3947eed2 ms.sourcegitcommit: 63bb83322814f5e5e5c5b69939b14a3139a6ca7e ms.translationtype: MT ms.contentlocale: it-IT ms.lasthandoff: 06/25/2020 ms.locfileid: "85365647" --- ### <a name="winforms-methods-now-throw-argumentnullexception"></a>I metodi WinForms ora generano ArgumentNullException Alcuni Windows Forms metodi generano ora un oggetto <xref:System.ArgumentNullException> per gli argomenti null, in cui in precedenza è stato generato un oggetto <xref:System.NullReferenceException> . #### <a name="change-description"></a>Descrizione modifica: In precedenza, determinati metodi di Windows Forms generavano un' <xref:System.NullReferenceException> eccezione se veniva passato un argomento null. A partire da .NET 5,0, questi metodi generano <xref:System.ArgumentNullException> invece un oggetto per gli argomenti null. La generazione di un oggetto è <xref:System.ArgumentNullException> conforme al comportamento del runtime .NET. Consente inoltre di migliorare l'esperienza di debug, comunicando chiaramente che un argomento è null e quale argomento è. #### <a name="version-introduced"></a>Versione introdotta .NET 5,0 #### <a name="recommended-action"></a>Azione consigliata Se si chiama uno di questi metodi e il codice attualmente rileva un oggetto <xref:System.NullReferenceException> per gli argomenti null, rilevare <xref:System.ArgumentNullException> invece un oggetto. Inoltre, è consigliabile aggiornare il codice per impedire il passaggio di argomenti null ai metodi elencati. #### <a name="category"></a>Category Windows Forms #### <a name="affected-apis"></a>API interessate Nella tabella seguente sono elencati i metodi e i parametri interessati: > [!div class="mx-tdBreakAll"] > | Metodo | Nome parametro | Versione aggiunta | > |-|-|-| > | <xref:System.Windows.Forms.Control.ControlCollection.%23ctor(System.Windows.Forms.Control)> | `owner` | 5,0 Anteprima 1 | > | <xref:System.Windows.Forms.TabControl.GetToolTipText(System.Object)?displayProperty=nameWithType> | `item` | 5,0 Anteprima 1 | > | <xref:System.Windows.Forms.TableLayoutControlCollection.%23ctor(System.Windows.Forms.TableLayoutPanel)> | `container` | 5,0 Anteprima 1 | > | <xref:System.Windows.Forms.ToolStripRenderer.OnRenderArrow(System.Windows.Forms.ToolStripArrowRenderEventArgs)?displayProperty=nameWithType> | `e` | 5,0 Anteprima 1 | > | <xref:System.Windows.Forms.ToolStripRenderer.OnRenderItemCheck(System.Windows.Forms.ToolStripItemImageRenderEventArgs)?displayProperty=nameWithType> | `e` | 5,0 Anteprima 1 | > | <xref:System.Windows.Forms.ToolStripRenderer.OnRenderItemImage(System.Windows.Forms.ToolStripItemImageRenderEventArgs)?displayProperty=nameWithType> | `e` | 5,0 Anteprima 1 | > | <xref:System.Windows.Forms.ToolStripRenderer.OnRenderItemText(System.Windows.Forms.ToolStripItemTextRenderEventArgs)?displayProperty=nameWithType> | `e` | 5,0 Anteprima 1 | > | <xref:System.Windows.Forms.ToolStripRenderer.OnRenderStatusStripSizingGrip(System.Windows.Forms.ToolStripRenderEventArgs)?displayProperty=nameWithType> > | `e` | 5,0 Anteprima 1 | > | <xref:System.Windows.Forms.DataGridViewComboBoxEditingControl.ApplyCellStyleToEditingControl(System.Windows.Forms.DataGridViewCellStyle)?displayProperty=nameWithType> | `dataGridViewCellStyle` | 5,0 Anteprima 2 | > | <xref:System.Windows.Forms.RichTextBox.LoadFile(System.IO.Stream,System.Windows.Forms.RichTextBoxStreamType)?displayProperty=nameWithType> | `data` | 5,0 Anteprima 2 | > | <xref:System.Windows.Forms.ListBox.IntegerCollection.%23ctor(System.Windows.Forms.ListBox)> | `owner` | 5,0 Preview 5 | > | <xref:System.Windows.Forms.ListBox.IntegerCollection.CopyTo(System.Array,System.Int32)?displayProperty=nameWithType> | `destination` | 5,0 Preview 5 | > | <xref:System.Windows.Forms.ListViewGroup.System%23Runtime%23Serialization%23ISerializable%23GetObjectData(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)?displayProperty=nameWithType> | `info` | 5,0 Preview 5 | > | <xref:System.Windows.Forms.VisualStyles.VisualStyleRenderer.%23ctor(System.String,System.Int32,System.Int32)> | `className` | 5,0 Preview 5 | > | <xref:System.Windows.Forms.ListBox.ObjectCollection.%23ctor(System.Windows.Forms.ListBox)> | `owner` | 5,0 Preview 6 | > | <xref:System.Windows.Forms.ListBox.ObjectCollection.%23ctor(System.Windows.Forms.ListBox,System.Object[])> | `owner`, `value` | 5,0 Preview 6 | > | <xref:System.Windows.Forms.ListBox.ObjectCollection.%23ctor(System.Windows.Forms.ListBox,System.Windows.Forms.ListBox.ObjectCollection)> | `owner`, `value` | 5,0 Preview 6 | > | <xref:System.Windows.Forms.ListBox.ObjectCollection.AddRange(System.Object[])?displayProperty=nameWithType> | `items` | 5,0 Preview 6 | > | <xref:System.Windows.Forms.ListBox.ObjectCollection.AddRange(System.Windows.Forms.ListBox.ObjectCollection)?displayProperty=nameWithType> | `value` | 5,0 Preview 6 | > | <xref:System.Windows.Forms.ListBox.ObjectCollection.CopyTo(System.Object[],System.Int32)?displayProperty=nameWithType> | `destination` | 5,0 Preview 6 | > | <xref:System.Windows.Forms.ListBox.ObjectCollection.System%23Collections%23ICollection%23CopyTo(System.Array,System.Int32)?displayProperty=nameWithType> | `destination`d | 5,0 Preview 6 |

87.850575

310

0.806751

yue_Hant

0.936198

d0bc4024179ab16658a5cdb70b97036387d4ba6b

4,500

md

Markdown

docs/rules/no-mixed-requires.md

spadgos/eslint

ce88bc2b8302abec9641d748e53d4e5ff089fd75

[ "MIT" ]

null

docs/rules/no-mixed-requires.md

spadgos/eslint

ce88bc2b8302abec9641d748e53d4e5ff089fd75

[ "MIT" ]

null

docs/rules/no-mixed-requires.md

spadgos/eslint

ce88bc2b8302abec9641d748e53d4e5ff089fd75

[ "MIT" ]

null

# Disallow Mixed Requires (no-mixed-requires) In the Node.js community it is often customary to separate the `require`d modules from other variable declarations, sometimes also grouping them by their type. This rule helps you enforce this convention. ## Rule Details When this rule is enabled, each `var` statement must satisfy the following conditions: * either none or all variable declarations must be require declarations (default) * all require declarations must be of the same type (grouping) This rule distinguishes between six kinds of variable declaration types: * `core`: declaration of a required [core module][1] * `file`: declaration of a required [file module][2] * `module`: declaration of a required module from the [node_modules folder][3] * `computed`: declaration of a required module whose type could not be determined (either because it is computed or because require was called without an argument) * `uninitialized`: a declaration that is not initialized * `other`: any other kind of declaration In this document, the first four types are summed up under the term *require declaration*. ```javascript var fs = require('fs'), // "core" \ async = require('async'), // "module" |- these are "require declaration"s foo = require('./foo'), // "file" | bar = require(getName()), // "computed" / baz = 42, // "other" bam; // "uninitialized" ``` ## Options This rule comes with two boolean options. Both are turned off by default. You can set those in your `eslint.json`: ```json { "no-mixed-requires": [2, {"grouping": true, "allowCall": true}] } ``` The second way to configure this rule is with boolean. This way of setting is deprecated. ```json { "no-mixed-requires": [2, true] } ``` If enabled, violations will be reported whenever a single `var` statement contains require declarations of mixed types (see the examples below). The following patterns are considered problems: ```js /*eslint no-mixed-requires: 2*/ var fs = require('fs'), i = 0; ``` The following patterns are not considered problems: ```js /*eslint no-mixed-requires: 2*/ // only require declarations (grouping off) var eventEmitter = require('events').EventEmitter, myUtils = require('./utils'), util = require('util'), bar = require(getBarModuleName()); // only non-require declarations var foo = 42, bar = 'baz'; // always valid regardless of grouping because all declarations are of the same type var foo = require('foo' + VERSION), bar = require(getBarModuleName()), baz = require(); ``` ### grouping The following patterns are considered problems when grouping is turned on: ```js /*eslint no-mixed-requires: [2, {"grouping": true}]*/ // invalid because of mixed types "core" and "file" var fs = require('fs'), async = require('async'); // invalid because of mixed types "file" and "unknown" var foo = require('foo'), bar = require(getBarModuleName()); ``` ### allowCall The following patterns are not considered problems when `allowCall` is turned on: ```js var async = require('async'), debug = require('diagnostics')('my-module'), eslint = require('eslint'); ``` The following patterns are always considered problems regardless of `allowCall`: ```js var async = require('async'), debug = require('diagnostics').someFunction('my-module'), /* Allow Call doesn't allow calling any function */ eslint = require('eslint'); ``` ## Known Limitations * The implementation is not aware of any local functions with the name `require` that may shadow Node.js' global `require`. * Internally, the list of core modules is retrieved via `require("repl")._builtinLibs`. If you use different versions of Node.js for ESLint and your application, the list of core modules for each version may be different. The above mentioned `_builtinLibs` property became available in 0.8, for earlier versions a hardcoded list of module names is used as a fallback. If your version of Node.js is older than 0.6 that list may be inaccurate. ## When Not To Use It If you use a pattern such as [UMD][4] where the `require`d modules are not loaded in variable declarations, this rule will obviously do nothing for you. [1]: http://nodejs.org/api/modules.html#modules_core_modules [2]: http://nodejs.org/api/modules.html#modules_file_modules [3]: http://nodejs.org/api/modules.html#modules_loading_from_node_modules_folders [4]: https://github.com/umdjs/umd

34.351145

221

0.712444

eng_Latn

0.995071

d0bc6081f7fa432f6672d98aff2272a5ad3180ba

1,771

md

Markdown

README.md

nandra/meta-scipy

1c07824202af668ef1539c3de392cf737c5ba3fd

[ "MIT" ]

null

README.md

nandra/meta-scipy

1c07824202af668ef1539c3de392cf737c5ba3fd

[ "MIT" ]

null

README.md

nandra/meta-scipy

1c07824202af668ef1539c3de392cf737c5ba3fd

[ "MIT" ]

null

meta-scipy ========== This layer contains a recipe for building Scipy in the OpenEmbedded build system, as well as a series of patches and `bbappend` files necessary to build the recipe. Table of Contents ----------------- - [Dependencies](#dependencies) - [Installation](#installation) - [Contributing](#contributing) Dependencies ------------ This layer depends on: * [meta-oe][] * [meta-python][] [meta-oe]: https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ [meta-python]: https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ Installation ------------ Clone this repository with the tag or branch corresponding to your OpenEmbedded version and add it to your workspace. For example, if using `warrior`: git clone -b warrior https://github.com/gpanders/meta-scipy meta-scipy bitbake-layers add-layer meta-scipy You will also need to enable FORTRAN support by adding the following to your `local.conf` file: FORTRAN_forcevariable = ",fortran" RUNTIMETARGET_append_pn-gcc-runtime = " libquadmath" If you're using a custom distribution, you can alternatively include the two above lines in your `distro.conf` file. Contributing ------------ This repository serves as a community hub for a full OpenEmbedded Scipy solution. If you're able to get Scipy working for your platform or application, please consider [contributing your changes][firstcontributions]. You can also update the [wiki][], which is publicly editable. Contributions should be well-tested and should adhere to the [OpenEmbedded style guide][styleguide]. [firstcontributions]: https://firstcontributions.github.io/ [wiki]: https://github.com/gpanders/meta-scipy/wiki [styleguide]: https://www.openembedded.org/wiki/Styleguide

30.534483

90

0.750423

eng_Latn

0.971542

d0bc6b1f9682462b2f54dea4a1b4c5e1a70ef1ec

4,964

markdown

Markdown

_posts/2017-06-05-What-is-linguistics.markdown

zhangwenfan123/zwfV3

19829d333a6c310363dae267e94a60d1df1c12f0

[ "MIT" ]

1

2017-07-17T01:06:57.000Z

_posts/2017-06-05-What-is-linguistics.markdown

zhangwenfan123/zwfV3

19829d333a6c310363dae267e94a60d1df1c12f0

[ "MIT" ]

null

_posts/2017-06-05-What-is-linguistics.markdown

zhangwenfan123/zwfV3

19829d333a6c310363dae267e94a60d1df1c12f0

[ "MIT" ]

null

--- layout: post title: "What is linguistics? " date: 2017-06-05 23:00:00 categories: Linguistics tags: Linguistics comments: false --- * content {:toc} [语言学（linguistics）](https://en.wikipedia.org/wiki/Linguistics)是以人类语言为研究对象的学科，探索范围包括语言的性质、功能、结构、运用和历史发展，以及其他与语言有关的问题。语言学被普遍定义为对语言的一种科学化、系统化的理论研究。  上述的定义来自于百度百科，这个描述基本上把语言学是做什么的，研究的具体范围做了个大杂烩。接下来我摘录一段[胡明扬](http://baike.baidu.com/link?url=aE1mULLNsl7bCde84q9p4-fznhJyLytXN8uCQ38jqaUppmuOZGagU1lXZWl5unImwnAOnFvufzOASULX7Cc5NuZNIqbUhLd3nRp0K0wIJFB3p2L_W9YmavkGvWfQsymZ)老先生在其主编的[《语言学概论》](https://www.baidu.com/s?wd=%E8%AF%AD%E8%A8%80%E5%AD%A6%E6%A6%82%E8%AE%BA%20%E8%83%A1%E6%98%8E%E6%89%AC)中进行的一段描述： >如果不考虑哲学家对“语言”的哲学思考的话，到目前为止，语言学家研究语言主要有三种不同额角度。一种是着眼于语言的“本体”，也就是重点研究语音、语法、语汇、语义等语言系统内部的结构规律；一种是着眼于语言的社会功能，也就是重点研究语言在社会中的功能以及语言和社会之间的关系和相互影响；还有一种着眼于研究语言和思维之间的关系，也就是重点研究语言和思维之间的相互关系和影响。 --- 胡明扬老先生的这段描述基本上概括了，现代语言学者进行语言学研究的主要方向。在近几十年当中，语言学研究的这三个方向都分别取得了巨大的进展。而且在原有基础上，分化出了更为详细的学科分类，例如：音韵学，语音学，训诂学，方言学，音系学，语法学，语义学，词汇学等等。越来越多的分支，意味着越来越宽松包容和自由的研究环境，也同时意味着我们对语言现象本身的了解也越来越深。但是，从另一个角度来说，似乎也给后来的学者带来了更多的干扰，可能会让一些学者过分沉迷于细节，出现只见树木不见森林的情况。基于胡老先生概括的三个方向，我把相关领域的发展历史和一些进展简单的做一个整理，希望可以让各位对语言学现象的研究有个更清晰的了解。 ### 语言的本体 ##### 古希腊的先贤按照胡明扬老先生的概括，语言本体的研究是对语音，语法，语汇，语义等语言系统内部的研究。如果按照这个思路，关于语言本体的研究，几乎可以追溯到当年古希腊三贤的时代。凡是对西方哲学史有了解的人，对这三贤应该是很熟悉了。下面我简单介绍一下这当年的希腊三贤： >[苏格拉底](https://en.wikipedia.org/wiki/Socrates)：（希腊语：Σωκράτης，英译：Socrates，公元前469-公元前399年），古希腊著名的思想家、哲学家、教育家、公民陪审员。他本身没有著作，他的言论主要由柏拉图等人保留下来。他和他的学生柏拉图，以及柏拉图的学生亚里士多德并称为“古希腊三贤”，被后人广泛地认为是西方哲学的奠基者。 >[柏拉图](https://en.wikipedia.org/wiki/Plato)：（Plato，Πλάτeων，公元前427年—公元前347年），古希腊伟大的哲学家，也是全部西方哲学乃至整个西方文化最伟大的哲学家和思想家之一。他写下了许多哲学的对话录，并且在雅典创办了著名的学院。柏拉图是苏格拉底的学生，也是亚里士多德的老师，他们三人被广泛认为是西方哲学的奠基者。 >[亚里士多德](https://en.wikipedia.org/wiki/Aristotle)：古代先哲，古希腊人，世界古代史上伟大的哲学家、科学家和教育家之一，堪称希腊哲学的集大成者。他是柏拉图的学生，亚历山大的老师。作为一位百科全书式的科学家，他几乎对每个学科都做出了贡献。他的写作涉及伦理学、形而上学、心理学、经济学、神学、政治学、修辞学、自然科学、教育学、诗歌、风俗，以及雅典法律。亚里士多德的著作构建了西方哲学的第一个广泛系统，包含道德、美学、逻辑和科学、政治和玄学。大部分情况下，我们在谈论他们的时候，都是将他们放到一起进行讨论。我们目前知道苏格拉底是柏拉图的老师，柏拉图是亚里士多德的老师，但是由于年代的久远和文献的残缺不全，有关于苏格拉底和柏拉图的详细情况，大多源于其学生的转述和整理。但是从亚里士多德那对于几乎所有学科的贡献，足以看出这三贤的能量之强大，实在是超出一般人的想象。而亚里士多德的工作，就包括了修辞学和逻辑相关的研究。从这里就可以看出，西方语言学相关的本体研究，从一开始就是源自哲学的深刻思辨，这深刻的思辨本质上也不仅仅是对语言的思考，而是对一切万物背后本质和原理探索的一种态度，一种信仰。随后在整个西方哲学的发展过程中，语言学和逻辑学相关的工作就从来没有缺席。包括西方最出现的字典，也是在公元前5世纪的古代希腊诞生。当时以词汇表（Glossai）的方式出现，主要为诗歌及何马文章内艰深的字词作解释。在中东地区，公元8世纪由Al-Khalil编写第一部阿拉伯文词典。对英语民族来说，最早的字典却是双语字典。因为古代英语缺乏词汇，双语词典为他们提供拉丁文或法文中相当的英文字。这样的工作在那个时代，完全可以称得上是对词汇学的深入研究成果了。 --- ##### 古印度的传奇古代语文研究或者成为语言本体研究的另一个重要发源地就是古印度，同时古印度也是四大文明古国之一。印度有文献记载的最早的语言就是公元前一千年前的《梨俱吠陀》的吠陀梵语。[梵语][Sinhalese]在语言的分类中属于印欧语系中的一类，和希腊语以及拉丁语都有着渊源关系。 [Sinhalese]:https://en.wikipedia.org/wiki/Sinhalese_language 古印度语言传统中最重要的代表就是巴尼尼语法，又称[《梵语语法八篇》。][IndiaAncient] 就在这部公元前四世纪作品中，包含了语法描写、语音和音位、语义理论，以诗歌的形式体现。 [IndiaAncient]:http://baike.baidu.com/link?url=KG-t6OGxplZqRjcK9YrM5fRx-_q2Z2nDbjggq7mT--Qh1amL2QjYQBzx09nZCNtRdbot0pWjV26XUfORx1Nood1cEE8nuXuJHB8KDtYWmcLjF8XYlNhdZr5V2zgOZlZyBrYKwCWKI8xeUlVLCnk56q >巴尼尼是个人名，根据《大唐西域记》的记载，他于公元前4世纪出生在今天的巴基斯坦境内。巴尼尼语法的研究对象就是用梵语写成的吠陀经文。巴尼尼语法就是解释、诵读这种经文的一师徒相传的口诀，它本身的体裁就是一种经体。它一共概括了3996条梵语语法和语音的规则，用诗歌和韵文的形式写出，分章分节，便于记忆。作为四大文明古国之一，古印度其实对整个西方文明发展史有着不可磨灭的影响。尤其是对于西方古典科学体系的形成有着极其重要的作用。而大家最为熟知的可能就是今天世界通用的阿拉伯数字，最早便是由印度人发明，而后由阿拉伯人传向欧洲。公元前5世纪到公元前4世纪左右成书的《准绳经》是现存古印度最早的数学著作，这是一部讲述祭坛修筑的书。这部书表明，他们那时已经知道了勾股定理，并使用圆周率π为3.09，古印度人在天文计算的时候已经运用了三角形，公元499年成书的《圣使集》中有关数学的内容共有66条，包括了算术运算、乘方、开方以及一些代数学、几何学和三角学的规则。甚至在其中还包括了一些对无理数的研究以及对于“零”这个数的深入思考。从现代科学的角度来说，古印度在处理这些语言材料的时候，进行了系统有效的整理，并将其中一些复杂的符号做了充分的简化。这些工作对于语言本身来说是让语言更加的统一和通用了。对于人和社会来说是让人的沟通和表达变的更加高效了，这也为后来西方科学意识的发展和高度抽象和形式化的哲学和数学的发展提供了坚实的基础。光从这一点来说，古印度对于当今世界科学的重要性就是不言而喻的。 ##### 现代语言本体研究上面有关古希腊和古印度的例子，是为了充分说明：其实在人类文明和语言出现的早期，人类就从来没有停止过对语言的思考和研究，同时借助语言也进行了深刻的哲学反思。语言本身即是一种表达，科学研究是一种对客观事实真相的探索。探索的过程中，需要借助语言工具，甚至在发展的过程中这类语言逐步的分化出来，成为一些约定的特殊形式符号。科学的发展即伴随语言学的发展，相辅相成，互为推动。现在西方语言学的科学研究则是在文艺复兴之后的事情。在当时的时代，西方的文化空前的开放，对各种语言和文字极其的包容。在这样一个环境下自然而然的产生了很多有关语言学的工作。而在现代语言学本体研究发展的过程中，你又会听到一个熟悉的名字：莱布尼茨。这哥们除了和牛顿对怼之外，还作了很多具体的工作。莱布尼茨利用其巨大的学术声望和广泛联系，采用通信以及其他的方式调查世界各地的语言，得到各地的学者，传教士，旅行家，外交官甚至是国家君主的支持。在莱布尼茨的影响下，俄国女皇叶卡捷琳娜更是亲自主持了一项大规模的语言调查，并亲自编辑出版了《全球语言比较词汇》（1787年出版于彼得堡）。在此基础上，后面又有很多语言学专家进行了各种语言本体的研究，甚至将欧洲的语言划分成了11种不同类型的基础语系。而其中有一个很重要的插曲，就是对于梵语的发现和深入研究。 >[威廉·琼斯爵士](https://en.wikipedia.org/wiki/William_Jones_(philologist))（Sir William Jones,1746年9月28日－1794年4月27日），英国东方学家、语言学家、法学家、翻译家、外语学习天才。曾在印度当法官，用业余时间学习东方语言。威廉·琼斯最早正式提出印欧语假说，揭示了梵语、希腊语、拉丁语、日尔曼语、凯尔特语之间的同族关系，成为历史比较语言学的奠基人，也有人认为他是语言科学的奠基人。他还是英国第一位汉学家。另有同名的美国政治家威廉·琼斯。1786年2月2日，在亚洲学会发表第三周年演讲（The Third Anniversary Discourse），演讲中有一段话正式提出梵语与拉丁语、希腊语同源，这一思想被称为经典的构想（formulation），即著名的“印欧语假说”，琼斯的这一次演讲成了语言学史上的一件大事。在此之后，西方语言学家开始对各种语言的历史起源进行了大量的研究和深入调查。人类对于各种不同语言之间的关系也是历史上第一次看的如此清晰，虽然还存在着很多的争议。而这些研究的方式和内容几乎都是对语言本身特点的各种深入，语言的发音，拼写，语法的特点等等，都成为研究不同语言之间关系的具体对比内容。当然一直到今天，这些研究依然还在继续。在大量顶尖语言学家的工作中，自然科学的各种方法都被使用，甚至是进化论和生命科学的相关理论。当今的语言学研究，至少在宏观层面上已经不仅仅是对语言本身固有材料的整理和研究了。更多的情况下，语言学家研究的是语言学本身与社会的文化，人类思维的形成，心理学等各个领域之间形成的交叉内容。尤其是在进入现代社会以来，计算机技术的出现和发展，给本来似乎是个慢性子的语言学研究工作带来了极大的推动和变化。在接下来的篇章中，会从另外两个方面对”社会的语言学”和“智慧的语言学”进行进一步的阐述。

73

404

0.873086

yue_Hant

0.53969

d0bccd1e902fa36d515b882938e239b87392e6e0

6,303

md

Markdown

_includes/stats/el/pos/ADP.md

xidongbo/docs

2745640d072534cb19e632c75ed255b82b8ddbfc

[ "Apache-2.0" ]

1

2021-08-18T08:52:27.000Z

_includes/stats/el/pos/ADP.md

xidongbo/docs

2745640d072534cb19e632c75ed255b82b8ddbfc

[ "Apache-2.0" ]

null

_includes/stats/el/pos/ADP.md

xidongbo/docs

2745640d072534cb19e632c75ed255b82b8ddbfc

[ "Apache-2.0" ]

null

-------------------------------------------------------------------------------- ## Treebank Statistics (UD_Greek) There are 43 `ADP` lemmas (1%), 60 `ADP` types (1%) and 5105 `ADP` tokens (9%). Out of 11 observed tags, the rank of `ADP` is: 7 in number of lemmas, 8 in number of types and 5 in number of tokens. The 10 most frequent `ADP` lemmas: <em>στου, για, με, από, σε, κατά, προς, μεταξύ, μέχρι, μετά</em> The 10 most frequent `ADP` types: <em>για, με, από, σε, στην, στο, στη, στις, κατά, στον</em> The 10 most frequent ambiguous lemmas: <em>μεταξύ</em> ([ADP]() 70, [ADV]() 8), <em>μετά</em> ([ADP]() 51, [ADV]() 31), <em>λόγω</em> ([ADP]() 20, [NOUN]() 5), <em>παρά</em> ([ADP]() 15, [CONJ]() 5), <em>πριν</em> ([ADV]() 21, [ADP]() 10, [CONJ]() 4), <em>βάσει</em> ([ADP]() 7, [NOUN]() 2), <em>ως</em> ([ADV]() 123, [ADP]() 1) The 10 most frequent ambiguous types: <em>με</em> ([ADP]() 688, [PRON]() 2), <em>μεταξύ</em> ([ADP]() 68, [ADV]() 8), <em>μετά</em> ([ADP]() 39, [ADV]() 28), <em>μέσω</em> ([ADP]() 29, [NOUN]() 2), <em>λόγω</em> ([ADP]() 19, [NOUN]() 13), <em>παρά</em> ([ADP]() 10, [CONJ]() 5), <em>πριν</em> ([ADV]() 19, [ADP]() 8, [CONJ]() 4), <em>βάσει</em> ([ADP]() 5, [NOUN]() 2), <em>ως</em> ([ADV]() 112, [ADP]() 1) * <em>με</em> * [ADP]() 688: <em>Η Σπόρτινγκ Λισαβόνας νίκησε την Μάντσεστερ Σίτι <b>με</b> σκορ 1:0</em> * [PRON]() 2: <em>Όμως το μόνο που ζητώ είναι να δανειστώ την ψήφο σας για τον πρώτο γύρο : πρώτον , επειδή μπορεί να είναι η μόνη σας ευκαιρία να <b>με</b> ψηφίσετε και δεύτερον , επειδή οι πολλές ψήφοι θα θέσουν σε δοκιμασία τις Ομάδες που βρίσκονται πίσω από τους κκ. Cox και Martin .</em> * <em>μεταξύ</em> * [ADP]() 68: <em>Είναι ένα πλέγμα έργων το οποίο <b>μεταξύ</b> άλλων περιλαμβάνει :</em> * [ADV]() 8: <em>Στο <b>μεταξύ</b> , έχουν υλοποιηθεί όλα τα στοιχεία αυτής της στρατηγικής .</em> * <em>μετά</em> * [ADP]() 39: <em>Η Κούβα <b>μετά</b> την επανάσταση</em> * [ADV]() 28: <em>Η Γαλλία δήλωσε ότι « ο αλ Σενούσι έχει συλληφθεί <b>μετά</b> από συνεργασία Γάλλων και Μαυριτανών πρακτόρων .</em> * <em>μέσω</em> * [ADP]() 29: <em>Οι όροι ανακοινώθηκαν από την Εθνική Επιτροπή Άμυνας της Πιονγκγιάνγκ , <b>μέσω</b> του Κρατικού Πρακτορείου Ειδήσεων .</em> * [NOUN]() 2: <em>Την περίοδο 1943-44 ο ΕΛΑΣ συγκρούστηκε με τον ΕΔΕΣ και την ΕΚΚΑ εν <b>μέσω</b> γερμανικής κατοχής .</em> * <em>λόγω</em> * [ADP]() 19: <em>Σήμερα , χάνουμε πολύ χρόνο <b>λόγω</b> κακής προετοιμασίας των ψηφοφοριών .</em> * [NOUN]() 13: <em>Επιθυμώ , καταρχάς , να δηλώσω ότι οι κατηγορίες οι οποίες βαρύνουν τους εν <b>λόγω</b> βουλευτές είναι σοβαρές .</em> * <em>παρά</em> * [ADP]() 10: <em>καλύτερα να καίγεται το σπίτι του γείτονα <b>παρά</b> το δικό μου !</em> * [CONJ]() 5: <em>Η προσπάθεια ανακούφισης της φτώχειας δεν μπορεί <b>παρά</b> να είναι σωστή .</em> * <em>πριν</em> * [ADV]() 19: <em>Το έκανε <b>πριν</b> από την 11η_Σεπτεμβρίου .</em> * [ADP]() 8: <em>Το δάσος με τα πεύκα και τις κουκουναριές ( pinus pinea ) σταματάει μόλις λίγα μέτρα <b>πριν</b> τη θάλασσα .</em> * [CONJ]() 4: <em>" Το ζήτημα είναι να μεσολαβήσουμε πρώτα στον υπολογιστή <b>πριν</b> προχωρήσουμε στον ασθενή .</em> * <em>βάσει</em> * [ADP]() 5: <em>Φυσικά , η Επιτροπή κρίνει την προκείμενη περίπτωση <b>βάσει</b> των πολιτικών κριτηρίων της Κοπεγχάγης .</em> * [NOUN]() 2: <em>Όσον αφορά την αξιολόγηση των αποτελεσμάτων της Βαρκελώνης , θα σας κρίνουμε επί τη <b>βάσει</b> του ελέγχου προόδου .</em> * <em>ως</em> * [ADV]() 112: <em>Ήταν το επίσημο λιμάνι <b>ως</b> το 1883 .</em> * [ADP]() 1: <em>Αφού όμως η Ελλάδα απέσυρε τη στρατιωτική δύναμη που είχε στο νησί , αναγνωρίζοντας την αυτονομία του , θα έπρεπε και η Κρήτη , για να μην φέρει σε δύσκολη θέση την Αθήνα , να δεχθεί <b>ως</b> προσωρινή λύση την αυτονομία , εναποθέτοντας τις ελπίδες για οριστική λύση στις Μεγάλες Δυνάμεις .</em> ## Morphology The form / lemma ratio of `ADP` is 1.395349 (the average of all parts of speech is 1.776033). The 1st highest number of forms (8) was observed with the lemma “στου”: <em>στ', στα, στη, στην, στις, στο, στον, στους</em>. The 2nd highest number of forms (4) was observed with the lemma “από”: <em>απ', από, απ’, αφ'</em>. The 3rd highest number of forms (3) was observed with the lemma “κατά”: <em>καθ', κατ', κατά</em>. `ADP` occurs with 3 features: [el-feat/Case]() (1612; 32% instances), [el-feat/Gender]() (1612; 32% instances), [el-feat/Number]() (1612; 32% instances) `ADP` occurs with 6 feature-value pairs: `Case=Acc`, `Gender=Fem`, `Gender=Masc`, `Gender=Neut`, `Number=Plur`, `Number=Sing` `ADP` occurs with 7 feature combinations. The most frequent feature combination is `_` (3493 tokens). Examples: <em>για, με, από, σε, κατά, προς, μεταξύ, μέχρι, μετά, εν</em> ## Relations `ADP` nodes are attached to their parents using 4 different relations: [el-dep/case]() (5002; 98% instances), [el-dep/mark]() (92; 2% instances), [el-dep/conj]() (6; 0% instances), [el-dep/root]() (5; 0% instances) Parents of `ADP` nodes belong to 11 different parts of speech: [NOUN]() (4221; 83% instances), [PRON]() (256; 5% instances), [CONJ]() (186; 4% instances), [VERB]() (141; 3% instances), [ADV]() (98; 2% instances), [NUM]() (81; 2% instances), [ADJ]() (73; 1% instances), [PUNCT]() (39; 1% instances), [ROOT]() (5; 0% instances), [ADP]() (4; 0% instances), [PART]() (1; 0% instances) 5008 (98%) `ADP` nodes are leaves. 81 (2%) `ADP` nodes have one child. 7 (0%) `ADP` nodes have two children. 9 (0%) `ADP` nodes have three or more children. The highest child degree of a `ADP` node is 5. Children of `ADP` nodes are attached using 9 different relations: [el-dep/cc]() (42; 33% instances), [el-dep/punct]() (27; 21% instances), [el-dep/nmod]() (25; 20% instances), [el-dep/advmod]() (14; 11% instances), [el-dep/appos]() (12; 9% instances), [el-dep/conj]() (4; 3% instances), [el-dep/dep]() (2; 2% instances), [el-dep/amod]() (1; 1% instances), [el-dep/remnant]() (1; 1% instances) Children of `ADP` nodes belong to 9 different parts of speech: [CONJ]() (42; 33% instances), [NOUN]() (33; 26% instances), [PUNCT]() (28; 22% instances), [ADV]() (13; 10% instances), [ADP]() (4; 3% instances), [ADJ]() (3; 2% instances), [NUM]() (2; 2% instances), [PRON]() (2; 2% instances), [PART]() (1; 1% instances)

72.448276

407

0.631921

ell_Grek

0.895365

d0bda18f91441e9b58f73d5653b9b86e55cd51ae

11,715

md

Markdown

articles/active-directory-domain-services/active-directory-ds-admin-guide-join-windows-vm.md

OpenLocalizationTestOrg/azure-docs-pr15_hu-HU

ac1600ab65c96c83848e8b2445ac60e910561a25

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

null

articles/active-directory-domain-services/active-directory-ds-admin-guide-join-windows-vm.md

OpenLocalizationTestOrg/azure-docs-pr15_hu-HU

ac1600ab65c96c83848e8b2445ac60e910561a25

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

null

articles/active-directory-domain-services/active-directory-ds-admin-guide-join-windows-vm.md

OpenLocalizationTestOrg/azure-docs-pr15_hu-HU

ac1600ab65c96c83848e8b2445ac60e910561a25

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

null

<properties pageTitle="Azure Active Directory tartományi szolgáltatások: Vegye fel a Windows Server virtuális egy felügyelt tartományba |} Microsoft Azure" description="A Windows Server virtuális gép csatlakozzon az Azure Active Directory tartományi szolgáltatások" services="active-directory-ds" documentationCenter="" authors="mahesh-unnikrishnan" manager="stevenpo" editor="curtand"/> <tags ms.service="active-directory-ds" ms.workload="identity" ms.tgt_pltfrm="na" ms.devlang="na" ms.topic="article" ms.date="10/02/2016" ms.author="maheshu"/> # <a name="join-a-windows-server-virtual-machine-to-a-managed-domain"></a>Vegye fel a Windows Server virtuális gép egy felügyelt tartományba > [AZURE.SELECTOR] - [Azure klasszikus portál – Windows](active-directory-ds-admin-guide-join-windows-vm.md) - [A PowerShell - Windows](active-directory-ds-admin-guide-join-windows-vm-classic-powershell.md) <br> Ez a cikk bemutatja, hogyan be szeretne kapcsolódni egy virtuális gép fut a Windows Server 2012 R2 az Azure Active Directory tartományi szolgáltatások felügyelt tartományhoz az Azure klasszikus portálon. ## <a name="step-1-create-the-windows-server-virtual-machine"></a>Lépés: 1: A Windows Server virtuális gép létrehozása Kövesse az utasításokat a [virtuális gép létrehozása az Azure klasszikus portálon Windows rendszerű](../virtual-machines/virtual-machines-windows-classic-tutorial.md) oktatóprogram során tagolt. Fontos, hogy az újonnan létrehozott virtuális gép Azure Active Directory tartományi szolgáltatások engedélyezve ugyanahhoz a virtuális hálózathoz csatlakozik ahhoz. A gyors létrehozása beállítás nem engedélyezi a csatlakozás a virtuális gép virtuális hálózathoz. Ezért akkor használja a "A gyűjtemény" beállítás a virtuális gép létrehozása. A következő lépésekkel hozhat létre, amelyben az Azure Active Directory tartományi szolgáltatások engedélyezte a virtuális hálózathoz csatlakozik a Windows virtuális géphez. 1. Az Azure klasszikus portálra a parancssávon a ablak alján kattintson az **Új**gombra. 2. Alapján **számítja ki**akkor kattintson a **virtuális gép**, majd **A gyűjtemény**. 3. Első képernyőjén segítségével **Válassza ki a képet** a virtuális gép elérhető képek a listából. Válassza ki a megfelelő képet. ![Jelölje ki a kép](./media/active-directory-domain-services-admin-guide/create-windows-vm-select-image.png) 4. A második képernyő segítségével válassza ki a számítógép nevét, méretét, és felügyeleti felhasználónév és jelszó. Használja a réteg és az alkalmazás vagy terhelést futtatásához szükséges méretét. A felhasználó nevét, válassza a Itt a számítógépen egy helyi rendszergazdai felhasználói. Írja be ide a tartományi fiók hitelesítő adatait. ![Virtuális gép konfigurálása](./media/active-directory-domain-services-admin-guide/create-windows-vm-config.png) 5. A harmadik képernyő lehetővé teszi a hálózat, tárolására és elérhetőség erőforrások konfigurálása. Győződjön meg arról, jelölje ki a virtuális hálózat, amelyben engedélyezett a Azure Active Directory tartományi szolgáltatások, a **Régió/affinitás csoport/virtuális hálózati** legördülő listából. A virtuális gép értelemszerűen adja meg a egy **Felhőalapú szolgáltatás DNS-nevét** . ![Jelölje ki a virtuális gép virtuális hálózati](./media/active-directory-domain-services-admin-guide/create-windows-vm-select-vnet.png) > [AZURE.WARNING] Győződjön meg arról, hogy a virtuális gép, amelyben az Azure Active Directory tartományi szolgáltatások engedélyezte virtuális hálózatához csatlakozik. A virtuális gép eredményeként "Lásd" a tartományt, és a feladatokat, például a tartományhoz. Ha úgy dönt, hogy egy másik virtuális hálózaton a virtuális gép létrehozása, Csatlakozás virtuális hálózat, amelyben az Azure Active Directory tartományi szolgáltatások engedélyezte a virtuális hálózat. 6. A negyedik képernyő teszi lehetővé a virtuális Agent telepítse és állítsa be, a rendelkezésre álló bővítmények részét. ![Kész](./media/active-directory-domain-services-admin-guide/create-windows-vm-done.png) 7. A virtuális gép létrehozását követően a a klasszikus portál sorolja fel az új virtuális gép csoportban a **virtuális gépeken futó** csomópontot. A virtuális gép és felhőbeli szolgáltatástól automatikusan indított, mind **operációs rendszert futtató**néven jelenik meg a állapotát. ![Virtuális gép már működik](./media/active-directory-domain-services-admin-guide/create-windows-vm-running.png) ## <a name="step-2-connect-to-the-windows-server-virtual-machine-using-the-local-administrator-account"></a>Lépés: 2: A Windows Server virtuális gépet használ, a helyi rendszergazdafiók csatlakoztatása Most azt csatlakozni az újonnan létrehozott Windows Server virtuális gép, a tartomány csatlakozni. Használja a virtuális gép való létrehozásakor meghatározott helyi rendszergazdai hitelesítő adatait. Hajtsa végre az alábbi lépésekkel csatlakozhat a virtuális gépen. 1. Nyissa meg a klasszikus portálon **virtuális gépeken futó** csomópontot. Jelölje ki a virtuális gépen, 1 lépésben a létrehozott, és a parancssávon az ablak alján kattintson a **Csatlakozás** gombra. ![Csatlakozás Windows virtuális géphez](./media/active-directory-domain-services-admin-guide/connect-windows-vm.png) 2. A klasszikus portál kéri, hogy a fájl megnyitását vagy mentését egy, a virtuális gépen való kapcsolódáshoz használt '.rdp' kiterjesztésű. Kattintson arra a fájlra, amikor a letöltés befejeződik. 3. Jelentkezzen be a parancssorba írja be a **rendszergazdai hitelesítő adataival**, amely a virtuális gép létrehozásakor megadott. Ha például "localhost\mahesh" használtuk ebben a példában. Ekkor meg kell kell bejelentkeznie az újonnan létrehozott Windows virtuális géphez helyi rendszergazdai hitelesítő adataival. A következő lépésként vegye fel a virtuális gép a tartományba. ## <a name="step-3-join-the-windows-server-virtual-machine-to-the-aad-ds-managed-domain"></a>Lépés 3: A Windows Server virtuális gépen AAD-tartományi felügyelt csatlakozás Hajtsa végre az alábbi lépéseket a Windows Server virtuális gép AAD-tartományi felügyelt csatlakoztatni. 1. A Windows Server kapcsolódni a 2 látható módon. Nyissa meg a kezdőképernyőn **Kiszolgálókezelő**. 2. A kiszolgáló Manager ablak bal oldali ablaktáblájában kattintson a **Helyi kiszolgálóra** . ![Indítsa el a Kiszolgálókezelő virtuális gépen](./media/active-directory-domain-services-admin-guide/join-domain-server-manager.png) 3. A **Tulajdonságok** csoportban kattintson a **munkacsoport** . A **Rendszertulajdonságok** tulajdonság lapon kattintson a **Módosítás** a tartományhoz. ![Rendszerlap tulajdonságai](./media/active-directory-domain-services-admin-guide/join-domain-system-properties.png) 4. Adja meg a tartomány nevét a Azure Active Directory tartományi szolgáltatások felügyelt az a **tartomány** mezőben lévő értéket tartományát, és kattintson az **OK gombra**. ![Adja meg a tartományhoz a tartomány](./media/active-directory-domain-services-admin-guide/join-domain-system-properties-specify-domain.png) 5. Adja meg a hitelesítő adatait, és a tartományhoz kéri. Győződjön meg arról, hogy akkor **Adja meg a felhasználó a AAD Adatközpont rendszergazdáknak tartozó hitelesítő adatok** csoport. Csak a csoport tagjai gépek vegye fel a felügyelt tartományba jogosultsága. ![Adja meg a hitelesítő adatok tartomány illesztés](./media/active-directory-domain-services-admin-guide/join-domain-system-properties-specify-credentials.png) 6. Hitelesítő adatok az alábbi módszerek egyikével adhatók meg: - Egyszerű Felhasználónévi formázása: Adja meg a felhasználói fiók UPN-utótag beállítva az Azure Active Directory. Ebben a példában a felhasználó "Péter" UPN-utótag van '[email protected]'. - SAMAccountName formátum: az SAMAccountName formátum adhatja meg a fiók nevét. Ebben a példában a felhasználó "Péter" kellene "CONTOSO100\bob" adja meg. > [AZURE.NOTE] **Azt javasoljuk, hogy az egyszerű Felhasználónévi formátum használata a hitelesítő adatait.** Az SAMAccountName is lehet automatikusan létrehozott Ha a felhasználó egyszerű Felhasználónévi előtag túl hosszú (például az "joereallylongnameuser"). Ha több felhasználó van a Azure AD-bérlő azonos UPN előtaggal (például "Péter"), a SAMAccountName formátum lehetnek a szolgáltatás által automatikusan létrehozott. Ezekben az esetekben az egyszerű Felhasználónévi formátum használható biztos, hogy jelentkezzen be a tartományt. 7. Után tartomány illesztés sikeres, megjelenik a következő üzenet üdvözli meg a tartományhoz. Indítsa újra a virtuális gép a tartomány join művelet elvégzéséhez. ![Üdvözli a tartomány](./media/active-directory-domain-services-admin-guide/join-domain-done.png) ## <a name="troubleshooting-domain-join"></a>Tartomány illesztés – hibaelhárítás ### <a name="connectivity-issues"></a>Kapcsolódási problémák Ha a virtuális gép nem tudja a tartomány keresése, olvassa el az alábbi hibaelhárítási lépéseket: - Győződjön meg arról, hogy a a virtuális gép csatlakoztatva van-e, mint a virtuális hálózatához engedélyezte a tartományi szolgáltatások. Ha nem, akkor a virtuális gép nem tud csatlakozni a tartomány, és ezért nem tudja a tartományhoz. - Ha a virtuális gép egy másik virtuális hálózathoz csatlakozik, győződjön meg arról, hogy virtuális hálózat, amelyben a tartományi szolgáltatások engedélyezte a virtuális hálózathoz csatlakoztatva van-e. - Próbálja meg a ping a tartomány felügyelt tartomány (például: "ping contoso100.com") a tartomány nevét használja. Ha nem sikerült, próbálja meg a ping az IP-címek tartomány megjelenik a lapon, ha engedélyezve van az Azure Active Directory tartományi szolgáltatások (például "küldjön ping parancsot 10.0.0.4"). Ha tudja a ping az IP-cím, de nem a tartomány, DNS előfordulhat, hogy megfelelően konfigurálva. Előfordulhat, hogy nem konfigurálta az IP-címek a tartomány DNS-kiszolgálók virtuális hálózatok. - Próbálja ki a virtuális gépen ("ipconfig/flushdns"), a DNS-feloldó gyorsítótárának kiürítése. Ha a párbeszédpanelt, amely rákérdez a hitelesítő adatait, és a tartományhoz tartozó, nem rendelkezik a csatlakozási problémákat tapasztal. ### <a name="credentials-related-issues"></a>Hitelesítő adatokkal kapcsolatos problémák Ha problémái vannak a hitelesítő adatait, és nem tudja a tartományhoz olvassa el az alábbi lépéseket. - Próbálja meg az egyszerű Felhasználónévi formátum használata a hitelesítő adatait. A fiók az SAMAccountName lehet, automatikusan létrehozott a bérlő azonos UPN előtaggal több felhasználó esetén, vagy ha az egyszerű Felhasználónévi előtag túl hosszú. Emiatt a fiók SAMAccountName formátumának eltérhet azt számíthat, vagy használja a helyszíni tartomány. - Próbálja meg használni egy felhasználói fiókot, a "AAD Adatközpont rendszergazdák" csoport gépek csatlakozik a felügyelt tartományhoz tartozó hitelesítő adatait. - Ellenőrizze, hogy a [Jelszó-szinkronizálás engedélyezve](active-directory-ds-getting-started-password-sync.md) megfelelően a az első lépések útmutató című témakörben ismertetett lépéseket. - Győződjön meg róla, a felhasználó (UPN) használja az Azure Active Directory beállítva (például '[email protected]') bejelentkezni. - Győződjön meg arról, hogy meg van várta jelszó-szinkronizálás tartaniuk a az első lépések útmutató elvégzéséhez. ## <a name="related-content"></a>Kapcsolódó tartalom - [Azure Active Directory tartományi szolgáltatások – első lépések útmutató](./active-directory-ds-getting-started.md) - [Az Azure Active Directory tartományi szolgáltatások felügyelt tartomány felügyelete](./active-directory-ds-admin-guide-administer-domain.md)

79.693878

545

0.805805

hun_Latn

1.000009

d0bdd8616127a9a0284dd92cd466deb4816fd278

79

markdown

Markdown

_tags/1176.markdown

sawyerh/organizedwonder

ec1c09e67d13776b134a1e4968b6413ca35f3780

[ "MIT" ]

2

2016-01-06T17:13:12.000Z

2016-07-03T03:28:36.000Z

_tags/1176.markdown

sawyerh/organizedwonder

ec1c09e67d13776b134a1e4968b6413ca35f3780

[ "MIT" ]

null

_tags/1176.markdown

sawyerh/organizedwonder

ec1c09e67d13776b134a1e4968b6413ca35f3780

[ "MIT" ]

null

--- title: "building" id: tag.id permalink: "/tags/building" videos: [1311] ---

13.166667

27

0.64557

lit_Latn

0.103071

d0be44b4ee11a368b97cd5bc2d17abe62d508f0d

1,566

md

Markdown

articles/azure-percept/overview-8020-integration.md

majacQ/azure-docs.fr-fr

7d9b6e9689de261ce63ac9d6de8894c5ff2ec608

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

43

2017-08-28T07:44:17.000Z

2022-02-20T20:53:01.000Z

articles/azure-percept/overview-8020-integration.md

majacQ/azure-docs.fr-fr

7d9b6e9689de261ce63ac9d6de8894c5ff2ec608

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

676

2017-07-14T20:21:38.000Z

2021-12-03T05:49:24.000Z

articles/azure-percept/overview-8020-integration.md

majacQ/azure-docs.fr-fr

7d9b6e9689de261ce63ac9d6de8894c5ff2ec608

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

153

2017-07-11T00:08:42.000Z

2022-01-05T05:39:03.000Z

--- title: Intégration du DK Azure Percept au système 80/20 description: Apprenez-en davantage sur l’intégration du DK Azure Percept au système de rails 80/20. author: MrHamlet ms.author: amiyouss ms.service: azure-percept ms.topic: conceptual ms.date: 03/24/2021 ms.custom: template-concept ms.openlocfilehash: eafd3e24fad7549c68908deb4632053fdfc994e4 ms.sourcegitcommit: 40866facf800a09574f97cc486b5f64fced67eb2 ms.translationtype: HT ms.contentlocale: fr-FR ms.lasthandoff: 08/30/2021 ms.locfileid: "123222019" --- # <a name="azure-percept-dk-8020-integration"></a>Intégration du DK Azure Percept au système 80/20 L’ Azure Percept DK et l’accessoire Audio ont été conçus pour s’intégrer avec le [système de rails en aluminium 80/20](https://8020.net/). ## <a name="8020-features"></a>Fonctionnalités 80/20 La carte porteuse d’Azure Percept DK, l’appareil Azure Percept Vision et l’accessoire Azure Percept Audio sont fabriqués avec des connecteurs 80/20 1010 intégrés, qui permettent des configuration de montage sans fin avec des rails 80/20. Cette intégration permet aux clients et aux générateurs de solutions d’étendre plus facilement leur preuve de concepts aux environnements de production. Regardez cette vidéo pour plus d’informations sur l’utilisation d’Azure Percept DK avec 80/20 : </br> > [!VIDEO https://www.youtube.com/embed/Dg6mtD9psLU] ## <a name="next-steps"></a>Étapes suivantes > [!div class="nextstepaction"] > [Acheter un kit Azure Percept DK sur la boutique en ligne de Microsoft](https://go.microsoft.com/fwlink/p/?LinkId=2155270)

46.058824

390

0.786718

fra_Latn

0.813123

d0be8085ec3a24e197cb325c2ad86a68237b3b77

150

md

Markdown

APO/README.md

Mikbac/Engineering-studies

348e29ef0418d44dd0fc99cdb6c7883e2694bb30

[ "BSD-3-Clause" ]

null

APO/README.md

Mikbac/Engineering-studies

348e29ef0418d44dd0fc99cdb6c7883e2694bb30

[ "BSD-3-Clause" ]

null

APO/README.md

Mikbac/Engineering-studies

348e29ef0418d44dd0fc99cdb6c7883e2694bb30

[ "BSD-3-Clause" ]

null

# Prototyp rozkładu jazdy ## Funkcjonalności: - [x] Możliwośc sprawdzenia rozkładu jazdy ## Przykaład działania: ![example](img/example1.png)

11.538462

42

0.726667

pol_Latn

0.999858

d0bf0922ae3ca68e34021dca9cfffd0407c2f756

84

md

Markdown

README.md

msk-access/msk-access.github.io

a2378c159562fc2478305442dc5e18cd3bc36132

[ "Apache-2.0" ]

null

README.md

msk-access/msk-access.github.io

a2378c159562fc2478305442dc5e18cd3bc36132

[ "Apache-2.0" ]

2

2021-09-27T23:14:22.000Z

2022-02-26T05:42:31.000Z

README.md

msk-access/msk-access.github.io

a2378c159562fc2478305442dc5e18cd3bc36132

[ "Apache-2.0" ]

null

### Documentation for MSK-ACCESS workflows Hosted at https://msk-access.github.io/

21

42

0.761905

kor_Hang

0.531254

d0bf0d2f84b06aef602c5bcba013dbc39b588d97

794

md

Markdown

_posts/2019-08-17-por-eduardo-embaixador-bolsonaro-oferece-cargos-e-orcamento-bilionario-a-senadores.md

tatudoquei/tatudoquei.github.io

a3a3c362424fda626d7d0ce2d9f4bead6580631c

[ "MIT" ]

null

_posts/2019-08-17-por-eduardo-embaixador-bolsonaro-oferece-cargos-e-orcamento-bilionario-a-senadores.md

tatudoquei/tatudoquei.github.io

a3a3c362424fda626d7d0ce2d9f4bead6580631c

[ "MIT" ]

null

_posts/2019-08-17-por-eduardo-embaixador-bolsonaro-oferece-cargos-e-orcamento-bilionario-a-senadores.md

tatudoquei/tatudoquei.github.io

a3a3c362424fda626d7d0ce2d9f4bead6580631c

[ "MIT" ]

1

2022-01-13T07:57:24.000Z

--- layout: post item_id: 2697123656 title: >- Por Eduardo embaixador, Bolsonaro oferece cargos e orçamento bilionário a senadores author: Tatu D'Oquei date: 2019-08-17 05:00:11 pub_date: 2019-08-17 05:00:11 time_added: 2019-08-19 07:55:03 category: tags: [] image: https://img.huffingtonpost.com/asset/5d56e5c92200002f00f6925c.jpeg?ops=1200_630 --- O ministro da Casa Civil, Onyx Lorenzoni, tem andado com duas planilhas embaixo dos braços nas últimas semanas. Em uma, contabiliza os senadores que prometem votar a favor da indicação de Eduardo Bolsonaro para a embaixada dos Estados Unidos. **Link:** [https://www.huffpostbrasil.com/entry/eduardo-bolsonaro-cargos_br_5d56dd76e4b056fafd0b67f9](https://www.huffpostbrasil.com/entry/eduardo-bolsonaro-cargos_br_5d56dd76e4b056fafd0b67f9)

41.789474

242

0.797229

por_Latn

0.90859

d0bf1fc06b179978d611114ae3635c209e832ae4

3,017

md

Markdown

CONTRIBUTING.md

tigrannajaryan/opentelemetry-collector-releases

5ff6e58041022017e0040d502414f3995b3a7e6b

[ "Apache-2.0" ]

34

2021-09-01T14:21:30.000Z

2022-03-29T01:41:08.000Z

CONTRIBUTING.md

tigrannajaryan/opentelemetry-collector-releases

5ff6e58041022017e0040d502414f3995b3a7e6b

[ "Apache-2.0" ]

56

2021-08-30T17:35:41.000Z

2022-03-24T19:51:21.000Z

CONTRIBUTING.md

tigrannajaryan/opentelemetry-collector-releases

5ff6e58041022017e0040d502414f3995b3a7e6b

[ "Apache-2.0" ]

29

2021-08-31T19:34:03.000Z

2022-03-31T02:35:37.000Z

# Contribution guidelines This repository contains a set of resources that ultimately results in OpenTelemetry Collector distributions. This document contains information needed to start contributing to this repository, including how to add new distributions. ## Understanding this repository ### Distribution directory Each distribution has its own directory at the root of this repository, such as `opentelemetry-collector`. Within each one of those, you'll find at least two files: - `Dockerfile`, determining how to build the container image for this distribution - `manifest.yaml`, which is used with [ocb](https://github.com/open-telemetry/opentelemetry-collector/tree/main/cmd/builder) to generate the sources for the distribution. Within each distribution, you are expected to be able to build it using the builder, like: ```shell ocb --config manifest.yaml ``` You can build all distributions by running: ```shell make build ``` If you only interested in generating the sources for the distributions, use: ```shell make generate ``` ### Distribution configurations Due to an incompatibility between `goreleaser` and how this directory is structured, the default configuration files to be included in the container images should be placed under [./configs](./configs) instead of within the distribution's main directory. ### Scripts The main `Makefile` is mostly a wrapper around scripts under the [./scripts](./scripts) directory. ### goreleaser [goreleaser](https://goreleaser.com) plays a big role in producing the final artifacts. Given that the final configuration file for this tool would be huge and would cause relatively big changes for each new distribution, a `Makefile` target exists to generate the `.goreleaser.yaml` for the repository. The `Makefile` contains a list of distributions (`DISTRIBUTIONS`) that is passed down to the script, which will generate snippets based on the templates from `./scripts/goreleaser-templates/`. Adding a new distribution is then only a matter of adding the distribution's directory, plus adding it to the Makefile. Adding a new snippet is only a matter of adding a new template. Once there's a change either to the templates or to the list of distributions, a new `.goreleaser.yaml` file can be generated with: ```shell make generate-goreleaser ``` After that, you can test the goreleaser build process with: ```shell make goreleaser-verify ``` #### Building multi-architecture Docker images goreleaser will build Docker images for x86_64 and arm64 processors. The build process involves executing `RUN` steps on the target architecture, which means the system you run it on needs support for emulating foreign architectures. This is accomplished by installing [qemu](https://www.qemu.org/), and then [enabling support](https://github.com/multiarch/qemu-user-static#readme) for qemu within Docker: ```shell apt-get install qemu binfmt-support qemu-user-static docker run --rm --privileged multiarch/qemu-user-static --reset -p yes ```

45.712121

680

0.785217

eng_Latn

0.998018

d0bf5c7bf5622634101188f390fc02bb9b633bfb

658

md

Markdown

README.md

ZeroX-DG/emacs-github-pr

94eba5980e8bea2f1e834b788a3758bba7715c6b

[ "MIT" ]

1

2019-05-16T20:42:49.000Z

README.md

ZeroX-DG/emacs-github-pr

94eba5980e8bea2f1e834b788a3758bba7715c6b

[ "MIT" ]

null

README.md

ZeroX-DG/emacs-github-pr

94eba5980e8bea2f1e834b788a3758bba7715c6b

[ "MIT" ]

null

# github-pr <p align="center"> <img src="assets/demo.gif" width="80%" /> </p> ## About this project github-pr is a simple emacs package for easier reviewing Github PR without leaving emacs. This also the project that I used to learn elisp (I created this package after learned about elisp for a few hours so I'm not sure if this project will survive :smile:) ## Todo - [x] List all PRs in menu for user to pick - [x] Checkout PR - [ ] Show PR body with <kbd>TAB</kbd> key - [ ] Exit PR branch - [ ] Maybe add comment on PR if that possible :smile: - [ ] Label a PR is also a good feature - [ ] I can't think of anything else ## License - [MIT](LICENSE)

31.333333

258

0.694529

eng_Latn

0.990095

d0c02719b4686b497b858dd987c347f6a2470bf6

3,160

markdown

Markdown

_posts/2019-05-24-comparing-two-lists.markdown

jacoby/jacoby.github.io

6a3c5245ed2e3b60d9e83692f34747f77f573917

[ "Apache-2.0" ]

3

2017-11-09T17:40:09.000Z

2019-05-27T17:45:29.000Z

_posts/2019-05-24-comparing-two-lists.markdown

jacoby/jacoby.github.io

6a3c5245ed2e3b60d9e83692f34747f77f573917

[ "Apache-2.0" ]

12

2019-05-28T01:46:37.000Z

2022-01-26T01:57:48.000Z

_posts/2019-05-24-comparing-two-lists.markdown

jacoby/jacoby.github.io

6a3c5245ed2e3b60d9e83692f34747f77f573917

[ "Apache-2.0" ]

2

2017-07-24T07:53:05.000Z

2019-08-14T23:38:28.000Z

--- layout: post title: "Comparing Two Lists" author: "Dave Jacoby" date: "2019-05-24 10:48:23 -0400" categories: "" --- [Olaf Alders](https://twitter.com/olafalders/) demonstrated [creating a Twitter list of CPAN authors](http://www.olafalders.com/2019/05/23/creating-a-twitter-list-of-cpan-authors/), using a tool simply named [`t`](https://github.com/sferik/t). That someone make such a good all-in-one Twitter tool while my scripts are in an un-unified state gives me some small amount of shame, but that's not why I'm writing. His list comes from [MetaCPAN](https://metacpan.org/) and [`MetaCPAN::Client`](https://metacpan.org/pod/MetaCPAN::Client). I have created another list over time, containing developers and organizations that use Perl but may not tweet primarily about it, much less contribute to CPAN. I compared the lists to see who I should pay attention to but don't, but that isn't why I'm writing. I'm writing because I used `t` to get his list and my list, and there is an easy way to compare two lists in Perl. [`List::Compare`](https://metacpan.org/pod/List::Compare). Give `List::Compare` two arrayrefs and you can get back: - **Union:** the entries in both list - **Intersection:** The entries that both lists share - **Unique:** The entries only in the first list - **Complement:** The entries only in the second list I prepared this infographic. ![Quick Visual Guide to List::Compare](https://jacoby.github.io/images/list_compare.jpg) I pulled the list membership with [`t list members olafalders/cpan-authors`](https://twitter.com/olafalders/lists/cpan-authors) and [`t list members jacobydave/perl`](https://twitter.com/jacobydave/lists/perl), put them into files, and used the following code to give me who is in both, who is just in Olaf's and who is just in mine. ```perl #!/usr/bin/env perl use strict; use warnings; use utf8; use feature qw{ postderef say signatures state switch }; no warnings qw{ experimental::postderef experimental::smartmatch experimental::signatures }; use List::Compare; my @dave = open_and_dump('dave_perl'); my @olaf = open_and_dump('olaf_perl'); my $lc = List::Compare->new( \@dave, \@olaf ); say join "\n\t", q{INTERSECTION}, sort { lc $a cmp lc $b } $lc->get_intersection; say join "\n\t", q{UNIQUE (Dave)}, sort { lc $a cmp lc $b } $lc->get_unique; say join "\n\t", q{COMPLEMENT (Olaf)}, sort { lc $a cmp lc $b } $lc->get_complement; sub open_and_dump($filename) { if ( -f $filename && open my $fh, '<', $filename ) { my @arr = map { chomp; $_ } <$fh>; return @arr; } } ``` I won't put that list here, because it's _so_ easy to make your own and time will change both lists, but the number of lines of code dedicated to playing with lists is smaller than the number of lines dedicated to file reading. This is compact and readable, and oh so cool. So, try `List::Compare`. If you have any questions or comments, I would be glad to hear it. Ask me on [Twitter](https://twitter.com/jacobydave) or [make an issue on my blog repo](https://github.com/jacoby/jacoby.github.io).

49.375

411

0.701899

eng_Latn

0.979446

d0c168294eb54aea8e9baaa2ccd548eb8cd834b0

2,140

md

Markdown

docs/interfaces/_responses_highlights_repository_create_reel_response_.highlightsrepositorycreatereelresponsecropped_image_version.md

leafdropco/api

c0d2ddedba0daddfb64e5e2e82096e491e5522f2

[ "MIT" ]

null

docs/interfaces/_responses_highlights_repository_create_reel_response_.highlightsrepositorycreatereelresponsecropped_image_version.md

leafdropco/api

c0d2ddedba0daddfb64e5e2e82096e491e5522f2

[ "MIT" ]

3

2020-09-07T01:31:13.000Z

2021-05-10T10:15:31.000Z

docs/interfaces/_responses_highlights_repository_create_reel_response_.highlightsrepositorycreatereelresponsecropped_image_version.md

leafdropco/api

c0d2ddedba0daddfb64e5e2e82096e491e5522f2

[ "MIT" ]

null

> **[instagram-private-api](../README.md)** [Globals](../README.md) / ["responses/highlights.repository.create-reel.response"](../modules/_responses_highlights_repository_create_reel_response_.md) / [HighlightsRepositoryCreateReelResponseCropped_image_version](_responses_highlights_repository_create_reel_response_.highlightsrepositorycreatereelresponsecropped_image_version.md) / # Interface: HighlightsRepositoryCreateReelResponseCropped_image_version ## Hierarchy * **HighlightsRepositoryCreateReelResponseCropped_image_version** ## Index ### Properties * [estimated_scans_sizes](_responses_highlights_repository_create_reel_response_.highlightsrepositorycreatereelresponsecropped_image_version.md#estimated_scans_sizes) * [height](_responses_highlights_repository_create_reel_response_.highlightsrepositorycreatereelresponsecropped_image_version.md#height) * [url](_responses_highlights_repository_create_reel_response_.highlightsrepositorycreatereelresponsecropped_image_version.md#url) * [width](_responses_highlights_repository_create_reel_response_.highlightsrepositorycreatereelresponsecropped_image_version.md#width) ## Properties ### estimated_scans_sizes • **estimated_scans_sizes**: *number[]* *Defined in [responses/highlights.repository.create-reel.response.ts:34](https://github.com/dilame/instagram-private-api/blob/e9c516c/src/responses/highlights.repository.create-reel.response.ts#L34)* ___ ### height • **height**: *number* *Defined in [responses/highlights.repository.create-reel.response.ts:32](https://github.com/dilame/instagram-private-api/blob/e9c516c/src/responses/highlights.repository.create-reel.response.ts#L32)* ___ ### url • **url**: *string* *Defined in [responses/highlights.repository.create-reel.response.ts:33](https://github.com/dilame/instagram-private-api/blob/e9c516c/src/responses/highlights.repository.create-reel.response.ts#L33)* ___ ### width • **width**: *number* *Defined in [responses/highlights.repository.create-reel.response.ts:31](https://github.com/dilame/instagram-private-api/blob/e9c516c/src/responses/highlights.repository.create-reel.response.ts#L31)*

42.8

337

0.831776

eng_Latn

0.142622

d0c174f04d05cf7e709518a31ac8077944dbbf3c

157

md

Markdown

aboutme.md

qinxinlei/qinxinlei.github.io

3fc985224ec6203a862383478082775c52f19899

[ "MIT" ]

null

aboutme.md

qinxinlei/qinxinlei.github.io

3fc985224ec6203a862383478082775c52f19899

[ "MIT" ]

null

aboutme.md

qinxinlei/qinxinlei.github.io

3fc985224ec6203a862383478082775c52f19899

[ "MIT" ]

null

--- layout: page title: 关于我 # subtitle: Why you'd want to go on a date with me --- 我的名字叫雷沁欣，以下是关于我的一些信息: - 1997年9月生，目前单身。 ### 我的故事如果你想了解更多关于我的故事，欢迎直接戳我~

12.076923

50

0.694268

eng_Latn

0.899139

d0c1ed636bcf6e6da24fcd4f69510dd01e1d8292

41

md

Markdown

README.md

wishful-project/wishrem_rem_backend

71d5874ff25fb2fedb78acea6ac2442a17fce0a0

[ "Apache-2.0" ]

null

README.md

wishful-project/wishrem_rem_backend

71d5874ff25fb2fedb78acea6ac2442a17fce0a0

[ "Apache-2.0" ]

null

README.md

wishful-project/wishrem_rem_backend

71d5874ff25fb2fedb78acea6ac2442a17fce0a0

[ "Apache-2.0" ]

1

2020-06-05T08:23:12.000Z

# rem_backend REM backend python scripts

13.666667

26

0.829268

eng_Latn

0.500475

d0c24e3842ba25704520dade2457938df1d0107b

30

md

Markdown

README.md

DECORUS11/Node.js

ea68768f82b749c2ca0d3060413a74b0b4de8820

[ "MIT" ]

null

README.md

DECORUS11/Node.js

ea68768f82b749c2ca0d3060413a74b0b4de8820

[ "MIT" ]

null

README.md

DECORUS11/Node.js

ea68768f82b749c2ca0d3060413a74b0b4de8820

[ "MIT" ]

null

# Node.js Learning new things

10

19

0.766667

eng_Latn

0.796798

d0c2f8b4e7ab4f1e6c7594bf6ff81b07bdb1ecf6

1,033

md

Markdown

CHANGELOG.md

run-crank/vscode-crank-scenario-language

6baeef1d41f9789b0243353a14856e58b1a3360e

[ "MIT" ]

null

CHANGELOG.md

run-crank/vscode-crank-scenario-language

6baeef1d41f9789b0243353a14856e58b1a3360e

[ "MIT" ]

4

2020-04-03T17:45:17.000Z

2022-02-26T20:01:20.000Z

CHANGELOG.md

run-crank/vscode-crank-scenario-language

6baeef1d41f9789b0243353a14856e58b1a3360e

[ "MIT" ]

null

# Change Log All notable changes to the "Crank Scenario Language" extension will be documented in this file. The format is based on [Keep a Changelog](http://keepachangelog.com/). ## v0.3.0 - 2020.03.27 - Added IntelliSense support for _dynamic_ `{{tokens}}`, for steps that follow others that provide them. Note: Dynamic token support was added in Crank in `v0.10.0`, and may not yet be fully supported/exposed by all Cog versions. - Fixed a bug where IntelliSense would not show up due to a case mismatch on some Scenario step expression text. ## v0.2.0 - 2019.11.10 - Added IntelliSense support for defined `{{tokens}}` when present in scenario. ## v0.1.1 - 2019.11.10 - YAML format specification for `.crank.yml` files. - IntelliSense support for step expression text (based on Crank cog registry) - IntelliSense support for data keys (based on Crank cog registry) - IntelliSense support for cog and stepId keys (based on Crank cog registry) - File contextual menu item to run the given scenario in a VS Code terminal

44.913043

95

0.755082

eng_Latn

0.986743

d0c5a6adc8e4edea169a7bb72089108d23e9600d

2,940

md

Markdown

README.md

mapto/-

532ec719c44eaad405d1bd7b339e92ecbdbe9021

[ "MIT" ]

2

2020-04-02T19:44:12.000Z

2020-04-08T19:18:17.000Z

README.md

mapto/-

532ec719c44eaad405d1bd7b339e92ecbdbe9021

[ "MIT" ]

5

2020-04-26T15:36:52.000Z

2020-05-14T19:21:29.000Z

README.md

mapto/-

532ec719c44eaad405d1bd7b339e92ecbdbe9021

[ "MIT" ]

2

2020-04-07T18:03:25.000Z

2020-04-21T09:05:34.000Z

<h1 align="center">Не се сърди, 4oBe4e!</h1> <p align="left"> <a href="https://github.com/mapto/4oBe4e/actions"><img alt="build status" src="https://github.com/mapto/4oBe4e/workflows/build/badge.svg"> </a> <a href="https://repl.it/@mapto/4oBe4e"><img alt="repl.it" src="https://repl.it/public/images/logo-small.png" height="20"> </a> </p> ## Game rules https://bg.wikipedia.org/wiki/Не_се_сърди,_човече ## Mockups and Design <p align="left"><img src="https://github.com/mapto/4oBe4e/raw/master/mockup.png" width="70%"></p> ``` -0--1--2--3--4--5--6--7--8--9--0--1--2--3--4--5--6--7--8- -1- -1- -2- (D)(E)(1) [B][B] -2- -3- (C)<F>(2) [B][B] -3- -4- (B)<G>(3) -4- -5- [R][R] (7)(8)(9)(A)<H>(4)(5)(6)(7) -5- -6- [R][R] (6) <I>{B}{B} (8) -6- -7- (5){R}{R} <J>{B}{B} (9) -7- -8- (1)(2)(3)(4){R}{R} (A)(B)(C)(D) -8- -9- (E)<F><G><H><I><J> <J><I><H><G><F>(E) -9- -0- (D)(C)(B)(A) {G}{G}(4)(3)(2)(1) -0- -1- (9) {Y}{Y}<J> {G}{G}(5) -1- -2- (8) {Y}{Y}<I> (6) [G][G] -2- -3- (7)(6)(5)(4)<H>(A)(9)(8)(7) [G][G] -3- -4- (3)<G>(B) -4- -5- [Y][Y] (2)<F>(C) -5- -6- [Y][Y] (1)(E)(D) -6- -7- -7- -0--1--2--3--4--5--6--7--8--9--0--1--2--3--4--5--6--7--8- [ home ] ( path ) < finish > { target } ``` ### How to move: - [ home ] - Home positions, each piece has its own position. When a player draws 6, can take one piece out of start position and move it to their corresponding (1) - ( path ) - Shared positions, one player's pieces can stack on top of each other. Pieces move clockwise. If a piece lands on one piece of another player, the hit piece returns to its start position. If the target cell has more than one pieces, I cannot move my piece there. Once a full circle is performed, the piece turns from (E) to <F> and further - < finish > - Safe zone, other players cannot enter the safe zone of a player. Pieces can stack on top of each other. If a player draws more than it takes to get to their corresponding { finish }, the piece cannot move. - { target } - Target positions, each piece has its own position. Once all the pieces of a player are here, they win the game. ## Setup ### Git flow ``` # NB: Assuming you are in the project folder $ git status $ git stage . $ git commit -m"<message>" $ git pull $ git push ``` ### Pipenv ``` # NB: Assuming you are in the project folder $ export PIPENV_VENV_IN_PROJECT=true $ pip3 install --upgrade pip $ pip3 install pipenv $ pipenv --python /usr/bin/python3 $ pipenv sync --dev ```

43.235294

351

0.497959

eng_Latn

0.88545

d0c5e7ea30785753c9d63106cbafa6464b64d78f

1,665

md

Markdown

HW/hw8.md

hpbl/if1004

aa4eaebb8d74afbe07d8d85aa1a07030c1c794d0

[ "MIT" ]

null

HW/hw8.md

hpbl/if1004

aa4eaebb8d74afbe07d8d85aa1a07030c1c794d0

[ "MIT" ]

null

HW/hw8.md

hpbl/if1004

aa4eaebb8d74afbe07d8d85aa1a07030c1c794d0

[ "MIT" ]

null

# Homework 8 This homework will aiding you in understand the backgroud, main issues, challenges and benefits of the adoption of Microservices. ## Introduction to Microservices challenges and opportunities Reading pr listen the following articles: - [Cloud Native Architectures - a Conversation with Matt Stine](https://www.infoq.com/articles/cloud-native-architectures-matt-stine/) (May 2, 2015), InfoQ - [Cloud-native architectures will be the default soon](https://www.networkworld.com/article/3200131/data-center/cloud-native-architectures-will-be-the-default-soon.html), By Andy Patrizio, Network World | JUN 9, 2017 - [Simon Brown on the Role of the Software Architect in a Continuous Delivery Environment](https://www.infoq.com/podcasts/simon-brown-architecture), Podcast with Simon Brown by Wesley Reisz on Sep 23, 2017, InfoQ - [The Top 10 Adages in Continuous Deployment](https://www.infoq.com/articles/cd-adages), Posted by Chris Parnin et al. on Sep 19, 2017. Estimated reading time: 25 minutes, InfoQ. Now, in your words, try to answer these questions: * In your own words, explainwhat brings the DevOps idea closer to the technologies, tools and processes around the concept of microservices? * How does Microservice Architecture (Style or Pattern) differ than a Software Oriented Architecture? What differences in architecture and "business drivers" (or quality attributes) allow for a Microservice model? * Explain the concepts and features of the [Twelve-Factor Applications](https://12factor.net/). * Explain the principle of Antifragile (Random House) from Nassim Taleb applied tpo Microservices and DevOps. _**Due Sunday, 10/09, 17:00**_.

79.285714

217

0.79039

eng_Latn

0.913413

d0c60514019134b1b99ed650eb1f831096d1e072

1,770

md

Markdown

docs/en/advanced-concepts/settings.md

xuvw/appium

7da327f643b9870903ccbec190410c21e031d2ed

[ "Apache-2.0" ]

1

2015-11-03T14:21:37.000Z

docs/en/advanced-concepts/settings.md

xuvw/appium

7da327f643b9870903ccbec190410c21e031d2ed

[ "Apache-2.0" ]

null

docs/en/advanced-concepts/settings.md

xuvw/appium

7da327f643b9870903ccbec190410c21e031d2ed

[ "Apache-2.0" ]

null

## Settings Settings are a new concept introduced by appium. They are currently not a part of the Mobile JSON Wire Protocol, or the Webdriver spec. Settings are a way to specify the behavior of the appium server. Settings are: - Mutable, they can be changed during a session - Only relevant during the session they are applied. They are reset for each new session. - Control the way the appium server behaves during test automation. They do not apply to controlling the app or device under test. An example of a setting would be `ignoreUnimportantViews` for Android. Android can be set to ignore elements in the View Hierarchy which it deems irrelevant. Setting this can cause tests to run faster. A user who *wants* to access the ignored elements however, would want to disable `ignoreUnimportantViews`, and reenable it afterwards. Another example of a use-case for settings would be telling appium to ignore elements which are not visible. Settings are implemented via the following API endpoints: **POST** /session/:sessionId/appium/settings >Expects a JSON hash of settings, where keys correspond to setting names, and values to the value of the setting. ``` { settings: { ignoreUnimportantViews : true } } ``` **GET** /session/:sessionId/appium/settings >Returns a JSON hash of all the currently specified settings. ``` { settings: { ignoreUnimportantViews : true } } ``` ### Supported Settings **"ignoreUnimportantViews"** - Boolean which sets whether Android devices should use `setCompressedLayoutHeirarchy()` which ignores all views which are marked IMPORTANT_FOR_ACCESSIBILITY_NO or IMPORTANT_FOR_ACCESSIBILITY_AUTO (and have been deemed not important by the system), in an attempt to make things less confusing or faster.

41.162791

336

0.776271

eng_Latn

0.998657

d0c60e791020530cc54c7bde0fc4294afba25a85

25,922

md

Markdown

ko/contribute/notation.md

CHH3213/PX4-fork

034347e959e0e9ca2d4e6bbd4f1f4b9c4f9455cb

[ "CC-BY-4.0" ]

222

2015-10-06T18:30:04.000Z

2020-10-06T12:42:28.000Z

ko/contribute/notation.md

CHH3213/PX4-fork

034347e959e0e9ca2d4e6bbd4f1f4b9c4f9455cb

[ "CC-BY-4.0" ]

850

2015-10-22T09:58:17.000Z

2020-10-28T15:55:37.000Z

ko/contribute/notation.md

CHH3213/PX4-fork

034347e959e0e9ca2d4e6bbd4f1f4b9c4f9455cb

[ "CC-BY-4.0" ]

693

2015-10-07T23:45:27.000Z

2020-10-26T11:37:06.000Z

!REDIRECT "https://docs.px4.io/master/ko/contribute/notation.html" # 용어 다음 용어, 기호, 장식 문자는 이 안내서 전체의 텍스트와 다이어그램에 활용합니다. ## 표기 - 굵은 서체 변형은 벡터, 행렬을 나타내며, 굵지 않은 서체는 스칼라 배열을 나타냅니다. - 각 변수의 기본 프레임은 로컬 프레임 $$\ell$$ 입니다. 우측 [위첨자](#superscripts)는 좌표 프레임을 나타냅니다. 우측 위첨자가 없으면 $$\ell$$ 기본 프레임임을 가정합니다. 회전 행렬일 경우 예외입니다. 우측 아래첨자로 현재 프레임을 나타내며 우측 위첨자로 대상 프레임을 나타냅니다. - 변수와 아래 첨자는 동일한 문자를 쓸 수 있으나, 늘 다른 의미를 지닙니다. ## 약어 | 축약어 | 확장 | | ----------- | ------------------------------------------------------ | | AOA | 받음각. *alpha*로 표기 | | AOS | 횡활각. *beta*로 표기 | | FRD | 오른손 법칙에 따라 기체의 앞부분을 X축, 오른쪽 방향을 Y축, 아래 방향을 Z축으로 두는 좌표계 | | FW | 고정익 | | MC | 멀티콥터 | | MPC 또는 MCPC | 멀티콥터 위치 조종기. MPC는 모델 예측 제어라고도 합니다. | | NED | 오른손 법칙에 따라 X 축은 진북을 가리키고 Y 축은 진동, Z 축은 아래를 가리키는 좌표계 | | PID | 비례, 적분, 미분 동작 조종기. | ## 기호 | 변수 | 설명 | | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | $$x,y,z$$ | x, y, z 각 좌표를 따르는 변환 | | $$\boldsymbol{\mathrm{r}}$$ | $$\boldsymbol{\mathrm{r}} = [x \quad y \quad z]^{T}$$ 벡터 위치 | | $$\boldsymbol{\mathrm{v}}$$ | $$\boldsymbol{\mathrm{v}} = \boldsymbol{\mathrm{\dot{r}}}$$ 속도 벡터 | | $$\boldsymbol{\mathrm{a}}$$ | $$\boldsymbol{\mathrm{a}} = \boldsymbol{\mathrm{\dot{v}}} = \boldsymbol{\mathrm{\ddot{r}}}$$ 가속 벡터 | | $$\alpha$$ | 공격 각도 (AOA). | | $$b$$ | 주익 길이 (끝에서 끝까지) | | $$S$$ | 주익 넓이 | | $$AR$$ | 종횡비 $$AR = b^2/S$$ | | $$\beta$$ | 측면 경사도 (AOS) | | $$c$$ | 주익현 길이 | | $$\delta$$ | 기체 역학 제어 표면 이탈각(손실각). 손실 값이 양인 경우 부모멘트를 생성합니다. | | $$\phi,\theta,\psi$$ | 오일러 각. roll(=Bank), pitch, yaw(=Heading). | | $$\Psi$$ | 고도 벡터. $$\Psi = [\phi \quad \theta \quad \psi]^T$$. | | $$X,Y,Z$$ | x, y, z 축 방향의 힘 | | $$\boldsymbol{\mathrm{F}}$$ | $$\boldsymbol{\mathrm{F}}= [X \quad Y \quad Z]^T$$ 힘의 벡터 | | $$D$$ | 견인력 | | $$C$$ | 측풍력 | | $$L$$ | 양력 | | $$g$$ | 중력 | | $$l,m,n$$ | x, y, z 좌표 축 주변의 모멘트 | | $$\boldsymbol{\mathrm{M}}$$ | $$\boldsymbol{\mathrm{M}} = [l \quad m \quad n]^T$$ 모멘트 벡터 | | $$M$$ | 마하 계수. 항공기 크기에 따라 무시할 수 있습니다. | | $$\boldsymbol{\mathrm{q}}$$ | 4원수 벡터 영역. | | $$\boldsymbol{\mathrm{\tilde{q}}}$$ | 해밀터니언 고도 4원수 $$\boldsymbol{\mathrm{\tilde{q}}} = (q_0, q_1, q_2, q_3) = (q_0, \boldsymbol{\mathrm{q}})$$. $$\boldsymbol{\mathrm{\tilde{q}}}$$ 로컬 프레임 $$\ell$$에 상대적인 고도를 설명합니다. 바디 프레임에 벡터가 주어졌을 때 로컬 프레임을 나타낸다면 다음 수식을 활용할 수 있습니다: $$\boldsymbol{\mathrm{\tilde{v}}}^\ell = \boldsymbol{\mathrm{\tilde{q}}} \, \boldsymbol{\mathrm{\tilde{v}}}^b \, \boldsymbol{\mathrm{\tilde{q}}}^*$$ ($$\boldsymbol{\mathrm{\tilde{q}}}$$이 단일 요소가 아니라면, $$\boldsymbol{\mathrm{\tilde{q}}}^*$$ 대신 $$\boldsymbol{\mathrm{\tilde{q}}}^{-1}$$). $$\boldsymbol{\mathrm{\tilde{v}}}$$는 *4원화* 벡터 $$\boldsymbol{\mathrm{\tilde{v}}} = (0,\boldsymbol{\mathrm{v}})$$을(를) 나타냅니다. | | $$\boldsymbol{\mathrm{R}}_\ell^b$$ | 회전 행렬. $$\ell$$ 프레임에서 $$b$$ 프레임으로의 벡터 회전. $$\boldsymbol{\mathrm{v}}^b = \boldsymbol{\mathrm{R}}_\ell^b \boldsymbol{\mathrm{v}}^\ell$$. | | $$\Lambda$$ | 끝단 젖힘각 | | $$\lambda$$ | 완만도 $$\lambda = c_{tip}/c_{root}$$ | | $$w$$ | 풍속 | | $$p,q,r$$ | 몸통 축 x, y, z 주변의 각율(각가속도) | | $$\boldsymbol{\omega}^b$$ | 바디 프레임 $$\boldsymbol{\omega}^b = [p \quad q \quad r]^T$$의 각율(각가속도) 벡터 | | $$\boldsymbol{\mathrm{x}}$$ | 일반 상태 벡터 | ### 아래첨자 / 인덱스 | 아래첨자 / 인덱스 | 설명 | | ---------- | ------------------------ | | $$a$$ | 보조익 | | $$e$$ | 승강타 | | $$r$$ | 방향타 | | $$Aero$$ | 기체역학 | | $$T$$ | 강제 추력 | | $$w$$ | 상대 항속 | | $$x,y,z$$ | x, y, z 축에 따른 벡터 요소 | | $$N,E,D$$ | 북, 동, 하 글로벌 방위에 따른 벡터 요소 | <a id="superscripts"></a> ### Superscripts / Indices | 위첨자 / 인덱스 | 설명 | | --------- | ------------------- | | $$\ell$$ | 로컬 프레임 PX4 기본 상대 변수 | | $$b$$ | 바디 프레임 | | $$w$$ | 윈드 프레임 | ## 장식 기호 | 장식 기호 | 설명 | | --------------- | ------ | | $$()^*$$ | 켤레 복소수 | | $$\dot{()}$$ | 시간 미분 | | $$\hat{()}$$ | 추정 | | $$\bar{()}$$ | 평균 | | $$()^{-1}$$ | 역행렬 | | $$()^T$$ | 전치행렬 | | $$\tilde{()}$$ | 4원화 |

270.020833

725

0.071638

kor_Hang

0.985273

d0c6870a17da190451ef36ad9ae71ca95b80fd69

6,840

md

Markdown

multithreading/【MSB007】volatile修饰引用类型示例.md

GudaoFQ/Ability_Note

ddf011036abaf51066284337d1e5efcce203bab0

[ "MIT" ]

8

2020-09-30T08:29:01.000Z

2021-05-13T14:06:59.000Z

multithreading/【MSB007】volatile修饰引用类型示例.md

GudaoFQ/Ability_Note

ddf011036abaf51066284337d1e5efcce203bab0

[ "MIT" ]

1

2021-01-21T07:27:54.000Z

multithreading/【MSB007】volatile修饰引用类型示例.md

GudaoFQ/Ability_Note

ddf011036abaf51066284337d1e5efcce203bab0

[ "MIT" ]

1

2021-05-13T14:07:59.000Z

## Volatile修饰List【引用类型】 ### 奇怪的知识 ```shell 故事是这样的：说是有一道阿里的面试题，是这样描述的：给定一个容器，提供两个方法add，size，写两个线程：线程一：添加10个元素到容器中线程二：实现监控元素个数，当个数到5个的时候，线程2给出提示并结束 ``` #### 先按照正常思路码代码 ```java public class WithoutVolatile { //提供一个容器 List list = new ArrayList(); //list中加参数操作 public void add(String name){ this.list.add(name); } //查看list大小 public int size(){ return this.list.size(); } public static void main(String[] args) { WithoutVolatile wVolatile = new WithoutVolatile(); //新建一个线程B,用于监控容器的个数 new Thread(()->{ while(true){ if(wVolatile.size()==5){ break; } } System.out.println("线程t2 结束"); },"t2").start(); //这是一个线程A,添加Object到容器中 new Thread(()->{ for (int i = 0; i < 10; i++) { wVolatile.add(new Object()); System.out.println("add："+i); } },"t1").start(); } } ``` ![multithreading-volatile引用可见性.jpg](../resource/multithreading/multithreading-volatile引用可见性.jpg) #### 思考一个问题 > 是不是我线程A改完链表后没有把数据跟线程B说啊，线程B不知道情况。那我们就让线程A改完后通知线程B，加个volatile吧，直接怼在ArrayList上吧，不管了。 ```java public class WithoutVolatile { //提供一个容器 volatile List list = new ArrayList(); //list中加参数操作 public void add(String name){ this.list.add(name); } //查看list大小 public int size(){ return this.list.size(); } public static void main(String[] args) { WithoutVolatile wVolatile = new WithoutVolatile(); //新建一个线程B,用于监控容器的个数 new Thread(()->{ while(true){ if(wVolatile.size()==5){ break; } } System.out.println("线程t2 结束"); },"t2").start(); //这是一个线程A,添加Object到容器中 new Thread(()->{ for (int i = 0; i < 10; i++) { //这两行代码互换对结果影响比较大 wVolatile.add(new Object()); System.out.println("add："+i); } },"t1").start(); } } ``` 有意思的事情发生了，运行结果有时可以有时不可以。而且最重要的是当线程A的输出打印代码在前在后会导致运行结果的较大差异。打印结果在后的程序运行成功的概率更大！奇怪？ > 这里有两个疑问 1. 我们都知道volatile可以保持变量在线程之间的可见性。那为什么对于引用类型程序有时却不能保证，特别是打印语句在前的时候特别明显，难道有内鬼? 2. 为什么打印的代码在前在后会造成运行结果的较大差异呢？ **有疑问，www.baidu.com，输入：volatile可以修饰引用对象么，然后点了第一个链接，没错是它，随便看看。** ```markdown 原来，**volatile修饰引用对象只是修饰了其引用值，而不是其引用的内容的可见性，但是有一个地方是被修饰的引用对象当其他线程需要获取的所有变量都会从主内存去获取**。（有合理的解释当然就拿来凑合着用，留下了没有技术的泪水）。这说明，**线程B对添加了volatile的Arraylist对象访问都是从内存中获取的，这里没毛病吧**，however，线程A修改后并不会通知其他线程：我修改了Arraylist，其他线程注意哦。线程也不会立马将修改的更新到内存中。这就造成线程B没办法从内存中读取到修改后的值，可能等到线程A添加到第六个对象到Arraylist中时才更新到内存，这时线程B已经没办法获取到5了。 ``` ##### 事实上，线程会在cpu空闲的时候将更新的值刷新到内存中。我们可以尝试一下，让线程A在更新后稍作休息。 ```java public class WithoutVolatile { volatile List list = new ArrayList(); public void add(Object o){ list.add(o); } public int size(){ return list.size(); } public static void main(String[] args) { WithoutVolatile wVolatile = new WithoutVolatile(); new Thread(()->{ while(true){ if(wVolatile.size()==5){ break; } } System.out.println("线程t2 结束"); },"t2").start(); new Thread(()->{ for (int i = 0; i < 10; i++) { // 这两行代码互换对结果影响比较大 wVolatile.add(new Object()); /** * * 下面两行代码都是让线程休息，好让线程将值更新到内存中 * */ System.out.println("add "+i); try { Thread.sleep(1); } catch (InterruptedException e) { e.printStackTrace(); } } },"t1").start(); } } ``` 这个时候运行得到的结果是正确的。（本人尝试了10几遍） ##### 接下来我来猜一下打印语句的疑问：（猜测） > 前面说过，线程稍作休息，将改变的值刷新到内存中。会不会我们的系统在打印的时候cpu这个时候有空把更新的值写到内存中呢？但是又由于打印的时间是在是短的不行，比休息1毫秒还短。我想这就有可能解释为什么打印语句在后的时候还是有可能造成运行结果不正确，线程B无法拿到正确的值的原因。 ##### 然而，这个时候可能有一个调皮的人就说，那我就是不用volatile修饰容器呢？ > 分析一下：<br> 不加volatile？那我线程A和线程B变量不可见哦，我线程B好像不能每次都是从内存中读数据了哦，因为我while（true）那可是快的飞起，可能没时间从内存中更新数据。而且线程A也就不会及时从线程工作内存中更新值到内存。我们来想想怎么解决。 1. 既然线程B没有时间从内存中更新，那我给你时间更新便是。 2. 既然线程A不会及时将更改的值刷新到内存，那我也给你充足的时间更新呗。 ```java public class WithoutVolatile { //不加volatile List list = new ArrayList(); public void add(Object o){ list.add(o); } public int size(){ return list.size(); } public static void main(String[] args) { WithoutVolatile wVolatile = new WithoutVolatile(); new Thread(()->{ while(true){ //System.out.println(wVolatile.size());//线程有可能暂停 if(wVolatile.size()==5){ break; } //休息一毫秒钟 try { Thread.sleep(1); } catch (InterruptedException e) { e.printStackTrace(); } } System.out.println("线程t2 结束"); },"t2").start(); new Thread(()->{ for (int i = 0; i < 10; i++) { wVolatile.add(new Object()); System.out.println("add "+i); //休息1毫秒钟 try { Thread.sleep(1); } catch (InterruptedException e) { e.printStackTrace(); } } },"t1").start(); } } ``` ##### 这个时候，嘿嘿，运行的结果很如意。但是我们需要注意的是 * 线程B的休息时间不能长于线程A的休息时间。因为当线程B的休息时间过长，会导致线程A都把值改了两个了，线程B才检测到改变了两个值，这个时候就无法指定某个值结束线程B了。 #### 总结 ![multithreading-volatile引用可见性线程存储抽象图.jpg](../resource/multithreading/multithreading-volatile引用可见性线程存储抽象图.jpg) ```java //问题：volatile修饰对象和数组时，只是保证其引用地址的可见性，可为什么我加了volatile之后下面的代码会马上打印“结束”，如果不给数组加volatile就永远不会打印。volatile修饰对象和数组时，线程对其域或元素操作的详细步骤是什么？ class Test{ public static volatile int[] ints = new int[5]; public static void main(String[] args) throws Exception { Object o = new Object(); new Thread(() -> { //线程A try { TimeUnit.MILLISECONDS.sleep(100); } catch (InterruptedException e) { e.printStackTrace(); } ints[0] = 2; }).start(); new Thread(() -> { //线程B while (true) { if (ints[0] == 2) { System.out.println("结束"); break; } } }).start(); } } ``` 首先如果不给数组加volatile就永远不会打印这个理解是错误的，就算不加volatile，cpu在空闲的时候也会将int[0]的值从线程缓存刷新到主存，只是while(true)太快了，导致cpu一直没空。你可以试试看加一行代码后是什么结果： ```java //修改 if (ints[0] == 2) { System.out.println("结束"); break; } System.out.println("waiting"); ``` > 因为System.out.pringln()源码中有synchronized关键字，是很耗时的，这时候cpu就有空去刷新int[0]的值到主存了了。 volitile的作用就是强制将int[0]的值刷新到主存中，保证其在各个线程中的可见性

28.983051

191

0.554532

kor_Hang

0.151626

d0c7038b5ddd5c31f988e66096acedfb4776874c

2,207

md

Markdown

_items/spell-gem.md

5ecompendium/emporium

cbe91e179331570268e873bf3eb1d275755b7740

[ "MIT" ]

1

2019-12-17T19:25:36.000Z

_items/spell-gem.md

5ecompendium/emporium

cbe91e179331570268e873bf3eb1d275755b7740

[ "MIT" ]

null

_items/spell-gem.md

5ecompendium/emporium

cbe91e179331570268e873bf3eb1d275755b7740

[ "MIT" ]

1

2019-12-17T19:25:44.000Z

--- layout: item title: "Spell Gem" sources: [OotA.223] tags: [wondrous item, uncommon] category: "Wondrous Item" rarity: "Uncommon, rare, very rare, or legendary (attunement optional)" --- A _spell gem_ can contain one spell from any class's spell list. You become aware of the spell when you learn the gem's properties. While holding the gem, you can cast the spell from it as an action if you know the spell or if the spell is on your class's spell list. Doing so doesn't require any components, and doesn't require attunement. The spell then disappears from the gem. If the spell is of a higher level than you can normally cast, you must make an ability check using your spellcasting ability to determine whether you can cast it successfully. The DC equals 10 + the spell's level. On a failed check, the spell disappears from the gem with no other effect. Each spell gem has a maximum level for the spell it can store. The spell level determines the gem's rarity and the stored spell's saving throw DC and attack bonus, as shown in the Spell Gem table. You can imbue the gem with a spell if you're attuned to it and it's empty. To do so, you cast the spell while holding the gem. The spell is stored in the gem instead of having any effect. Casting the spell must require either 1 action or 1 minute or longer, and the spell's level must be no higher than the gem's maximum. If the spell belongs to the school of abjuration and requires material components that are consumed, you must provide them, but they can be worth half as much as normal. Once imbued with a spell, the gem can't be imbued again until the next dawn. Deep gnomes created these magic gemstones and keep the creation process a secret. # Spell Gem Max. Spell Level | Gemstone | Rarity | Save DC | Attack Bonus :---------------:|:--------:|:------:|:-------:|:-----------: Cantrip | Obsidian | Uncommon | 13 | +5 1st | Lapis lazuli | Uncommon | 13 | +5 2nd | Quartz | Rare | 13 | +5 3rd | Bloodstone | Rare | 15 | +7 4th | Amber | Very rare | 15 | +9 5th | Jade | Very rare | 17 | +9 6th | Topaz | Very rare | 17 | +10 7th | Star ruby | Legendary | 18 | +10 8th | Ruby | Legendary | 18 | +10 9th | Diamond | Legendary | 19 | +11

64.911765

491

0.722247

eng_Latn

0.9992

d0c7c4a698bf58e0b6e627183a18ea993878a2d6

1,131

md

Markdown

node_modules/telegraph-uploader/README.md

DABOZE/Queen-Alexa

d24743fd7b48e6e68d08b74c56f00eb73035d1c0

[ "MIT" ]

4

2022-01-29T15:28:14.000Z

2022-01-31T10:17:42.000Z

node_modules/telegraph-uploader/README.md

DABOZE/Queen-Alexa

d24743fd7b48e6e68d08b74c56f00eb73035d1c0

[ "MIT" ]

null

node_modules/telegraph-uploader/README.md

DABOZE/Queen-Alexa

d24743fd7b48e6e68d08b74c56f00eb73035d1c0

[ "MIT" ]

9

2022-01-13T00:02:35.000Z

2022-02-21T09:45:33.000Z

# telegraph-uploader A package that helps you to upload media files to [telegra.ph](https://telegra.ph). ## Usage #### `uploadByBuffer` `uploadByBuffer(buffer, contentType, [agent]) => Promise<Response>` #### `uploadByUrl` `uploadByUrl(url, [agent]) => Promise<Response>` #### Agent An instance of `https.Agent` class (you can use this for proxies, search [`https-proxy-agent`](https://npmjs.com/https-proxy-agent), [`socks5-proxy-agent`](https://npmjs.com/https-proxy-agent) etc.) #### Response `{link: String, path: String}` ## Examples #### By buffer ```javascript const {uploadByBuffer} = require('telegraph-uploader') const fs = require('fs') uploadByBuffer(fs.readFileSync('image.png'), 'image/png') .then((result) => { console.log(result) /* { link: 'https://telegra.ph/file/...', path: '/file/...', } */ }) ``` #### By URL ```javascript const {uploadByUrl} = require('telegraph-uploader') uploadByUrl('https://link.to/image') .then((result) => { console.log(result) /* { link: 'https://telegra.ph/file/...', path: '/file/...', } */ }) ```

23.5625

198

0.616269

kor_Hang

0.410509

d0c8729c97faa80d36526d4207c194f468e19fd2

275

md

Markdown

README.md

snychka/Python-Baseball

df76f79d77c27ccd8bc8bcb0ec9012ea90505a58

[ "MIT" ]

null

README.md

snychka/Python-Baseball

df76f79d77c27ccd8bc8bcb0ec9012ea90505a58

[ "MIT" ]

null

README.md

snychka/Python-Baseball

df76f79d77c27ccd8bc8bcb0ec9012ea90505a58

[ "MIT" ]

null

# Building Baseball Data Visualizations with Python - Draft Project Not ready for use. ``` Retrosheet Notice: The information used here was obtained free of charge from and is copyrighted by Retrosheet. Interested parties may contact Retrosheet at "www.retrosheet.org". ```

39.285714

160

0.792727

eng_Latn

0.992613

d0c882bed7dfdad424e73ed94d6dd9763573bc0b

25,429

md

Markdown

src/patternfly/components/Drawer/examples/Drawer.md

marusak/patternfly

54d84400dd39b954b3fb5f2730857e7d7327298f

[ "MIT" ]

1,591

2015-01-07T05:41:04.000Z

2022-03-31T11:06:39.000Z

src/patternfly/components/Drawer/examples/Drawer.md

marusak/patternfly

54d84400dd39b954b3fb5f2730857e7d7327298f

[ "MIT" ]

3,284

2015-01-02T15:48:14.000Z

2022-03-31T17:46:15.000Z

src/patternfly/components/Drawer/examples/Drawer.md

marusak/patternfly

54d84400dd39b954b3fb5f2730857e7d7327298f

[ "MIT" ]

395

2015-01-01T11:59:58.000Z

2022-03-21T15:25:30.000Z

--- id: Drawer section: components cssPrefix: pf-c-drawer --- import './Drawer.css' ## Examples ### Closed panel on right (default) ```hbs {{#> drawer drawer--id="closed-panel-right-example"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Expanded panel on right ```hbs {{#> drawer drawer--id="expanded-panel-right-example" drawer-panel--IsOpen="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Closed panel on left ```hbs {{#> drawer drawer--id="closed-panel-left-example" drawer--IsPanelLeft="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Expanded panel on left ```hbs {{#> drawer drawer--id="expanded-panel-left-example" drawer-panel--IsOpen="true" drawer--IsPanelLeft="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Closed panel on bottom ```hbs {{#> drawer drawer--id="closed-panel-bottom-example" drawer--IsPanelBottom="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. <br><br> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Expanded panel on bottom ```hbs {{#> drawer drawer--id="expanded-panel-bottom-example" drawer-panel--IsOpen="true" drawer--IsPanelBottom="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. <br><br> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate.{{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Expanded inline panel ```hbs {{#> drawer drawer--id="expanded-inline-panel-example" drawer-panel--IsOpen="true" drawer--IsInline="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Expanded inline panel on left ```hbs {{#> drawer drawer--id="expanded-inline-panel-left-example" drawer-panel--IsOpen="true" drawer--IsInline="true" drawer--IsPanelLeft="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Static ```hbs {{#> drawer drawer--id="static-example" drawer-panel--IsOpen="true" drawer--IsStatic="true"}} {{#> drawer-main}} {{#> drawer-content}} Static drawers don't have interactive elements. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Stacked content body elements ```hbs {{#> drawer drawer--id="stacked-content-body-elements-example" drawer-panel--IsOpen="true"}} {{#> drawer-main}} {{#> drawer-content drawer-content--NoBody="true"}} {{#> drawer-body}} content-body {{/drawer-body}} {{#> drawer-body drawer-body--modifier="pf-m-padding"}} content-body with padding {{/drawer-body}} {{#> drawer-body}} content-body {{/drawer-body}} {{/drawer-content}} {{#> drawer-panel}} {{#> drawer-body}} {{#> drawer-head}} {{#> drawer-actions}} {{> drawer-close}} {{/drawer-actions}} {{#> drawer-header}} drawer-panel {{/drawer-header}} {{/drawer-head}} {{/drawer-body}} {{#> drawer-body drawer-body--modifier="pf-m-no-padding"}} drawer-panel with no padding {{/drawer-body}} {{#> drawer-body}} drawer-panel {{/drawer-body}} {{/drawer-panel}} {{/drawer-main}} {{/drawer}} ``` ### Modified content padding ```hbs {{#> drawer drawer--id="modified-content-example" drawer-panel--IsOpen="true"}} {{#> drawer-main}} {{#> drawer-content drawer-body--modifier="pf-m-padding"}} <b>Drawer content padding.</b> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Modified panel padding ```hbs {{#> drawer drawer--id="modified-panel-padding-example" drawer-panel--IsOpen="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Modified panel width ```hbs {{#> drawer drawer--id="modified-panel-width-example" drawer-panel--IsOpen="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel drawer-panel--modifier="pf-m-width-75 pf-m-width-33-on-lg pf-m-width-25-on-2xl"}} {{/drawer-main}} {{/drawer}} ``` ### Additional section above main ```hbs {{#> drawer drawer--id="additional-section-above-main" drawer-panel--IsOpen="true"}} {{#> drawer-section}} drawer-section {{/drawer-section}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Resizable panel ```hbs {{#> drawer drawer--id="resizable-panel-example" drawer-panel--IsOpen="true" drawer-panel--IsResizable="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Resizable left panel ```hbs {{#> drawer drawer--id="resizable-left-panel-example" drawer--IsPanelLeft="true" drawer-panel--IsOpen="true" drawer-panel--IsResizable="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Resizable bottom panel ```hbs {{#> drawer drawer--id="resizable-bottom-panel-example" drawer-panel--IsOpen="true" drawer--IsPanelBottom="true" drawer-panel--IsResizable="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. <br><br> Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate.{{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Resizable inline panel ```hbs {{#> drawer drawer--id="expanded-inline-panel-example" drawer-panel--IsOpen="true" drawer--IsInline="true" drawer-panel--IsResizable="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel}} {{/drawer-main}} {{/drawer}} ``` ### Panel with light-200 background ```hbs {{#> drawer drawer--id="panel-with-light-200-background" drawer-panel--IsOpen="true"}} {{#> drawer-main}} {{#> drawer-content}} Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus pretium est a porttitor vehicula. Quisque vel commodo urna. Morbi mattis rutrum ante, id vehicula ex accumsan ut. Morbi viverra, eros vel porttitor facilisis, eros purus aliquet erat, nec lobortis felis elit pulvinar sem. Vivamus vulputate, risus eget commodo eleifend, eros nibh porta quam, vitae lacinia leo libero at magna. Maecenas aliquam sagittis orci, et posuere nisi ultrices sit amet. Aliquam ex odio, malesuada sed posuere quis, pellentesque at mauris. Phasellus venenatis massa ex, eget pulvinar libero auctor pretium. Aliquam erat volutpat. Duis euismod justo in quam ullamcorper, in commodo massa vulputate. {{/drawer-content}} {{> drawer-example-panel drawer-panel--modifier="pf-m-light-200"}} {{/drawer-main}} {{/drawer}} ``` ### Accessibility | Class | Applied to | Outcome | | -- | -- | -- | | `role="separator"` | `.pf-c-drawer__splitter` | Indicates that the splitter is a separator. **Required** | | `tabindex="0"` | `.pf-c-drawer__splitter` | Inserts the splitter into the tab order of the page so that it is focusable. **Required** | | `aria-orientation="horizontal"` | `.pf-c-drawer__splitter` | Indicates that the splitter is oriented horizontally. | | `aria-orientation="vertical"` | `.pf-c-drawer__splitter.pf-m-vertical` | Indicates that the splitter is oriented vertically. | ### Usage | Class | Applied to | Outcome | | -- | -- | -- | | `.pf-c-drawer__splitter` | `<div>` | Initiates the splitter. | | `.pf-c-drawer__splitter-handle` | `<div>` | Initiates the splitter handle element. | | `.pf-m-vertical` | `.pf-c-drawer__splitter` | Modifies the splitter to be vertical. | ## Documentation ### Accessibility | Attribute | Applied to | Outcome | | -- | -- | -- | | `aria-expanded="true"` | `action that opens drawer` | Indicates that the expandable content is visible. **Required** | | `aria-expanded="false"` | `action that opens drawer` | Indicates that the expandable content is hidden. **Required** | | `hidden` | `.pf-c-drawer__panel` | Hides the drawer panel from assistive technologies. **Required** | ### Usage | Class | Applied to | Outcome | | -- | -- | -- | | `.pf-c-drawer` | `<div>` | Initiates the drawer container. **Required** | | `.pf-c-drawer__section` | `<div>` | Initiates a drawer section area. This element can be used above or below `.pf-c-drawer__main` for titles, toolbars, footers, etc. | | `.pf-c-drawer__main` | `<div>` | Initiates the drawer main area. **Required** | | `.pf-c-drawer__content` | `<div>` | Initiates the drawer content container. **Required** | | `.pf-c-drawer__panel` | `<aside>` | Initiates the drawer panel container. **Required** | | `.pf-c-drawer__panel-main` | `<div>` | Initiates the drawer panel main container for resizable drawers only. | | `.pf-c-drawer__body` | `<div>` | Initiates a drawer body container and is the child of `.pf-c-drawer__content`, `.pf-c-drawer__panel` and `.pf-c-drawer__panel-main`. **Required** | | `.pf-c-drawer__head` | `<div>` | Initiates a drawer head container. This container positions `.pf-c-drawer__actions`, if present. | | `.pf-c-drawer__actions` | `<div>` | Identifies the drawer close button. | | `.pf-c-drawer__close` | `<div>` | Identifies the drawer close button. | | `.pf-m-panel-left` | `.pf-c-drawer` | Modifies the drawer panel to expand from the left. | | `.pf-m-panel-bottom` | `.pf-c-drawer` | Modifies the drawer panel to expand from the bottom. **Note:** percentage based panel sizes require the drawer component's parent element have an implicit or explicit height. | | `.pf-m-expanded` | `.pf-c-drawer` | Modifies the drawer panel for the expanded state. | | `.pf-m-static{-on-[lg, xl, 2xl]}` | `.pf-c-drawer` | Modifies the drawer panel state to always show both content and panel. | | `.pf-m-inline{-on-[lg, xl, 2xl]}` | `.pf-c-drawer` | Modifies the drawer so the content element and panel element are displayed side by side. `.pf-m-inline` used without a breakpoint will default to the `md` breakpoint. | | `.pf-m-no-border` | `.pf-c-drawer__panel` | Modifies the drawer panel border treatment to disable all border treatment. | | `.pf-m-padding` | `.pf-c-drawer__body` | Modifies the element to add padding. | | `.pf-m-no-padding` | `.pf-c-drawer__body` | Modifies the element to remove padding. | | `.pf-m-no-background` | `.pf-c-drawer__section`, `.pf-c-drawer__content`, `.pf-c-drawer__panel` | Modifies the drawer body/panel background color to transparent. | | `.pf-m-light-200` | `.pf-c-drawer__section`, `.pf-c-drawer__content`, `.pf-c-drawer__panel` | Modifies the drawer body/panel background color to light grey. | | `.pf-m-width-{25, 33, 50, 66, 75, 100}{-on-[breakpoint]}` | `.pf-c-drawer__panel` | Modifies the drawer panel width. | | `.pf-m-resizable` | `.pf-c-drawer__panel` | Modifies the drawer panel to be resizable. Intended for use with the `.pf-c-drawer__splitter` element. | | `--pf-c-drawer__panel--md--FlexBasis--min` | `.pf-c-drawer__panel` | Defines the drawer panel minimum size. | | `--pf-c-drawer__panel--md--FlexBasis` | `.pf-c-drawer__panel` | Defines the drawer panel size. | | `--pf-c-drawer__panel--md--FlexBasis--max` | `.pf-c-drawer__panel` | Defines the drawer panel maximum size. |

78.003067

741

0.735853

eng_Latn

0.245072

d0c968734ca2485d9c3f284e64a5a17ebe5de25b

2,310

md

Markdown

README.md

yyuu/fluent-logger-python

8b3c948c9d20e7e883f03b3751bc5a15f8c8cadd

[ "Apache-2.0" ]

null

README.md

yyuu/fluent-logger-python

8b3c948c9d20e7e883f03b3751bc5a15f8c8cadd

[ "Apache-2.0" ]

null

README.md

yyuu/fluent-logger-python

8b3c948c9d20e7e883f03b3751bc5a15f8c8cadd

[ "Apache-2.0" ]

null

# A Python structured logger for Fluentd Many web/mobile applications generate huge amount of event logs (c,f. login, logout, purchase, follow, etc). To analyze these event logs could be really valuable for improving the service. However, the challenge is collecting these logs easily and reliably. [Fluentd](http://github.com/fluent/fluentd) solves that problem by having: easy installation, small footprint, plugins, reliable buffering, log forwarding, etc. **fluent-logger-python** is a Python library, to record the events from Python application. ## Installation This library is distributed as 'fluent-logger' python package. Please execute the following command to install it. $ pip install fluent-logger On Python 2.5, you have to install 'simplejson' in addition. ## Configuration Fluent daemon must be lauched with the following configuration: <source> type tcp port 24224 </source> <match app.**> type stdout </match> ## Usage ### Event-Based Interface First, you need to call logger.setup() to create global logger instance. This call needs to be called only once, at the beggining of the application for example. By default, the logger assumes fluent daemon is launched locally. You can also specify remote logger by passing the options. from fluent import sender # for local fluent sender.setup('app') # for remote fluent sender.setup('app', host='host', port=24224) Then, please create the events like this. This will send the event to fluent, with tag 'app.follow' and the attributes 'from' and 'to'. from fluent import event # send event to fluentd, with 'app.follow' tag event.Event('follow', { 'from': 'userA', 'to': 'userB' }) ### Python logging.Handler interface This client-library also has FluentHanler class for Python logging module. import logging from fluent import handler logging.basicConfig(level=logging.INFO) l = logging.getLogger('fluent.test') l.addHandler(handler.FluentHandler('app.follow', host='host', port=24224)) l.info({ 'from': 'userA', 'to': 'userB' }) ## Contributors * [Ken Sato](https://github.com/ksato9700) * [Naoki Inada](http://github.com/methane) ## License Apache License, Version 2.0

28.875

257

0.709524

eng_Latn

0.974688

d0c9c1ea9709bea6a674bfbf12b3bc1f71c99e79

2,106

md

Markdown

content/project/SPE/index.md

BoChenYS/starter-academic

ba9dbc8ce68f20dbfddd087c184792df1fe4bf3a

[ "MIT" ]

null

content/project/SPE/index.md

BoChenYS/starter-academic

ba9dbc8ce68f20dbfddd087c184792df1fe4bf3a

[ "MIT" ]

null

content/project/SPE/index.md

BoChenYS/starter-academic

ba9dbc8ce68f20dbfddd087c184792df1fe4bf3a

[ "MIT" ]

null

--- title: Sattelite Pose Estimation summary: Estimate the relative attitude and position of a known spacecraft. tags: - SPE date: "2019-06-01T00:00:00Z" # Optional external URL for project (replaces project detail page). external_link: "" image: caption: focal_point: Smart links: - icon: github icon_pack: fab name: Follow url: https://github.com/BoChenYS/satellite-pose-estimation url_code: "" url_pdf: "https://arxiv.org/pdf/1908.11542.pdf" url_slides: "" url_video: https://youtu.be/2hzdLqnvQas # Slides (optional). # Associate this project with Markdown slides. # Simply enter your slide deck's filename without extension. # E.g. `slides = "example-slides"` references `content/slides/example-slides.md`. # Otherwise, set `slides = ""`. --- Estimating the 6DOF pose of space-borne objects (e.g., satellites, spacecraft, orbital debris) is a crucial step in many space operations such as docking, non-cooperative proximity tasks (e.g., debris removal), and inter-spacecraft communications (e.g., establishing quantum links). Existing solutions are mainly based on active sensor-based systems, e.g., the TriDAR system which uses LiDAR. Recently, monocular pose estimation techniques for space applications are drawing significant attention due to their lower power consumption and relatively simple requirements. In this project, we propose an approach to estimate the 6DOF pose of a satellite, relative to a canonical pose, from a single image. Our approach combines machine learning and geometric optimisation, by predicting the coordinates of a set of landmarks in the input image, associating the landmarks to their corresponding 3D points on an a priori reconstructed 3D model, then solving for the object pose using non-linear optimisation. Our approach is not only novel for this specific pose estimation task, which helps to further open up a relatively new domain for machine learning and computer vision, but it also demonstrates superior accuracy and won the first place in the recent Kelvins Pose Estimation Challenge organised by the European Space Agency (ESA).

60.171429

762

0.7849

eng_Latn

0.990229

d0ca7101d46553773648faf71e15c608521ce54b

1,998

md

Markdown

Intelligent-asset/Tutorials/ISVs/tblO365AssignedPlans.md

MicrosoftDocs/intelligent-asset-manager

400efedf29b0263a8d7e984cd5ee26e2aabcdd95

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

3

2020-05-18T19:32:54.000Z

2020-12-13T07:47:59.000Z

Intelligent-asset/Tutorials/ISVs/tblO365AssignedPlans.md

MicrosoftDocs/intelligent-asset-manager

400efedf29b0263a8d7e984cd5ee26e2aabcdd95

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

14

2018-08-12T03:34:59.000Z

2019-11-22T02:16:29.000Z

Intelligent-asset/Tutorials/ISVs/tblO365AssignedPlans.md

MicrosoftDocs/intelligent-asset-manager

400efedf29b0263a8d7e984cd5ee26e2aabcdd95

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

7

2018-07-10T00:34:47.000Z

2019-10-14T04:41:08.000Z

--- title: in.tblO365AssignedPlans - UI Input Schema description: Input Schema of Table in.tblO365AssignedPlans, shows the data points and types included on this table. --- # in.tblO365AssignedPlans - Input Schema Table Office 365 Service Plans assigned to users or to the entire organization. | Name | Data Type | Mandatory | Key | Comment | |------------------------|---------------|-----------|-----------------------------------|------------------------------------------------------------------------------| | DataSourceId | varchar(32) | Y | | Unique ID of the source of this record. | | ServicePlanId | nvarchar(128) | Y | | A GUID that identifies the service plan. | | TenantId | nvarchar(128) | Y | FK > tblO365Organization.TenantId | The unique identifier for the tenant. | | AssignedOrganizationId | nvarchar(128) | | | If this ServicePlan is assigned to the entire organization, Organization ID. | | AssignedUserId | nvarchar(128) | | | If this ServicePlan is assigned to a user, the User ID. | | ServiceName | nvarchar(256) | | | The name of the service; for example, “Exchange”. | | CapabilityStatus | varchar(32) | | | For example, "Enabled", or "Provisioned" | | AssignedDateTime | datetime | | | Data and time at which the service plan was assigned. |

111

170

0.401902

eng_Latn

0.948216

d0ca7510cfcac382cc84edf667b38af748301296

46

md

Markdown

README.md

palmeidaprog/machine_learning_aula

05aaa91a75f0d5390b766b8f793ad2d1410acf35

[ "MIT" ]

null

README.md

palmeidaprog/machine_learning_aula

05aaa91a75f0d5390b766b8f793ad2d1410acf35

[ "MIT" ]

null

README.md

palmeidaprog/machine_learning_aula

05aaa91a75f0d5390b766b8f793ad2d1410acf35

[ "MIT" ]

null

# machine_learning_aula Machine Learning aula

15.333333

23

0.869565

eng_Latn

0.3047

d0cb5262ce49aeafa258081df77f015b7b9ef850

8,064

md

Markdown

README.md

db47h/factoplan

55031b277583cc438da76cadd52c0ec520bfb7de

[ "MIT" ]

null

README.md

db47h/factoplan

55031b277583cc438da76cadd52c0ec520bfb7de

[ "MIT" ]

null

README.md

db47h/factoplan

55031b277583cc438da76cadd52c0ec520bfb7de

[ "MIT" ]

null

# Factoplan A simple command-line factory planner for [Factorio]. Given a list of "wanted" items and the rates at which one wants to get them, it produces a list of needed factories (mining drills, assembly machines, etc.) and what they should produce. ## Installation Prerequisites: [LUA] and [Go]. The list of production recipes and items is not provided with Factoplan. This is mostly because I do not want to have to keep this repo in sync with the latest Factorio experimental versions. However, the provided LUA importer script will extract the necessary data from your Factorio game files. Once done, you'll just need to recompile Factoplan. In short: ```bash go get github.com/db47h/factoplan #if you have no GOPATH set this will be $HOME/go/src/github.com/db47h/factoplan cd $GOPATH/src/github.com/db47h/factoplan # replace the second arg with the actual path to your Factorio installation lua ./importer.lua "$HOME/.local/share/Steam/steamapps/common/Factorio" # recompile and install. This writes a single file (the factoplan executable) to # $GOBIN if defined, else $GOPATH/bin or $HOME/go/bin as a last resort go install ``` And you're all set. Note that you will need to repeat the import and install steps every time you update Factorio. ## Usage `factoplan -list` will give you a list of known items. For example, we want to produce every minute: - 2.4 solar panels per minute - 2 accumulators - 20 piercing rounds magazines - 4 cannon-shells Just run: factoplan solar-panel:2.4 accumulator:2.0 piercing-rounds-magazine:10 cannon-shell:4 This will produce: ```txt # Factory Item items/m items/s -- --------------------- ----------------------- ------- ------- 1 assembling-machine-3 accumulator 2.0 0.03 1 assembling-machine-3 cannon-shell 4.0 0.07 1 assembling-machine-3 copper-cable 108.0 1.80 1 assembling-machine-3 electronic-circuit 36.0 0.60 1 assembling-machine-3 firearm-magazine 10.0 0.17 1 assembling-machine-3 piercing-rounds-magazine 10.0 0.17 1 assembling-machine-3 solar-panel 2.4 0.04 1 chemical-plant battery 10.0 0.17 1 chemical-plant explosives 4.0 0.07 1 chemical-plant plastic-bar 8.0 0.13 1 chemical-plant sulfur 22.0 0.37 1 chemical-plant sulfuric-acid 200.0 3.33 4 electric-furnace copper-plate 126.0 2.10 7 electric-furnace iron-plate 244.0 4.07 4 electric-furnace steel-plate 30.0 0.50 1 electric-mining-drill coal 6.0 0.10 5 electric-mining-drill copper-ore 126.0 2.10 9 electric-mining-drill iron-ore 244.0 4.07 1 oil-refinery petroleum-gas 410.0 6.83 ``` The first column is the number of factories needed to produce the listed item at the given rate. Note that the item rates are the those required to achieve the set goals; they do not necessarily match the given number of factories (which are rounded up). To illustrate this, consider our example where in order to produce the requested rates of solar panels, accumulators and amo, we need to produce 4.07 iron ore per second. However, the 9 mining drills announced are capable of producing 4.5 items per second. This is not a bug, just a missing feature where the displayed items rates should be what will be really produced. The item rates can still give a good estimate of the required belt speeds. ## Limitations For any given production, the selected type of factory (or assembly machine) will be the one that requires the lesser amount of factories to do the job. Energy consumption is not taken into consideration. i.e. for very small production units, you may see one assembly machine 1, never more (since a single assembly machine 3 can replace a pair of 1's), occasionally a pair of assembly machine 2, but that's it. The current algorithm cannot handle multiple recipes producing the same item (like solid fuel from petroleum gas and from light oil). As a result, the following recipes are removed during the import: - basic-oil-processing - coal-liquefaction - heavy-oil-cracking - light-oil-cracking - solid-fuel-from-petroleum-gas - solid-fuel-from-heavy-oil - kovarex-enrichment-process - nuclear-fuel-reprocessing Facotplan still gives rough production needs for uranium and oil as well as their derivates, but these are not accurate: giving an optimal setup would require a much more complex algorithm. Also oil production can easily be controlled using simple circuit network logic (the difficult part is not to produce enough, but to prevent production stalls due to overflow). The only recipe considered to produce petrleum gas is advanced-oil-processing and solid fuel from light oil. ## Pseudo items In order to help with production planning for research, a few pseudo items have been added: - automation-science - logistic-science - military-science - production-science - utility-science - space-science They are agregates that represent one research point for a tech that requires 30 seconds of research. Each item above is an aggregate of itself added to the previous one. i.e. military-science is automation + logistic + military (that last one is weighted at 0.8, see below). You can see them as a quick way of checking how many research labs are needed (plus what's needed to keep them busy) for that many research points / minute. For example here is the output of, `factoplan logistic-science:12`: ```txt # Factory Item items/m items/s -- --------------------- ----------------------- ------- ------- 1 assembling-machine-3 automation-science-pack 12.0 0.20 1 assembling-machine-3 copper-cable 36.0 0.60 1 assembling-machine-3 electronic-circuit 12.0 0.20 1 assembling-machine-3 inserter 12.0 0.20 1 assembling-machine-3 iron-gear-wheel 30.0 0.50 1 assembling-machine-3 logistic-science-pack 12.0 0.20 1 assembling-machine-3 transport-belt 12.0 0.20 1 electric-furnace copper-plate 30.0 0.50 3 electric-furnace iron-plate 90.0 1.50 1 electric-mining-drill copper-ore 30.0 0.50 3 electric-mining-drill iron-ore 90.0 1.50 6 lab logistic-science 12.0 0.20 ``` For technologies with a 30 seconds cycle, this setup will keep the 6 labs busy. For technologies with a lower cycle, this will not be optimal (i.e. some labs will be idle), but technologies with low cycles are generally cheap. For technologies with a 60 second cycle, this same setup could keep 12 labs busy. So just build more labs! Again, this is only a helper. The actual "ingredients" for the "sepace-science" item are: - automation-science-pack: 1 - logistic-science-pack: 1 - military-science-pack: 0.8 - chemical-science-pack: 1 - production-science-pack: 0.4 - utility-science-pack: 1 - space-science-pack: 1 The non-round values for military and production science packs are based on guesstimates for end-game infinite research (where not all techs need these). These certainly need to be refined base on data extracted from the game tech tree. Also see https://wiki.factorio.com/Technologies The "space-science-pack" is also a pseudo-item added as a by-product of producing rocket parts in the rocket silo. The current value is 10 space-science packs for 1 rocket-part, but this is wrong and needs to be corrected, as well as the whole rocket-part recipe that needs to account for the 40 something seconds where a silo stops production to launch a rocket. ## TODO - Show production needs for resources without a recipe (like water and oil) - A graphwiz export with item rates would be nice. [Factorio]: https://www.factorio.com/ [Go]: https://golang.org/ [LUA]: https://www.lua.org/

53.403974

625

0.705481

eng_Latn

0.996051

d0cbfd90fd1193ec57149d5ead6c29dc2e54c7a5

3,669

md

Markdown

content/guides/live-progress-bar/25-login/index.md

tazamun/website

6331f339945f184d19c123f822222958e0cbcc79

[ "MIT" ]

null

content/guides/live-progress-bar/25-login/index.md

tazamun/website

6331f339945f184d19c123f822222958e0cbcc79

[ "MIT" ]

null

content/guides/live-progress-bar/25-login/index.md

tazamun/website

6331f339945f184d19c123f822222958e0cbcc79

[ "MIT" ]

null

--- title: Logging in to tazamun description: "Step three: How to login to the server using HTTP auth" --- Since we already have an express server running let's just use it to add an authentication endpoint. ### Adding a HTTP authentication endpoint First thing we'll need to do is add a HTTP endpoint that responds to a POST request with the correct structure: ```json { // The user unique id "id": "uuid", // The data used by the server for permission purposes "serverData": {}, // The data returned to the user on a successful login "clientData": {} } ``` So putting that into express as a post will look like: ```javascript // A very basic token function function isValidToken (token) { return token !== 'this-is-my-token' } app.post('/realtime-login', (req, res) => { if (isValidToken(req.body.token) === false) { response.status(401) return } response.json({ id: 'the-only-authenticated-user', serverData: { role: 'admin' }, clientData: {} }) }) ``` ### Configuring tazamun In order to use HTTP Authentication please enable the following auth module in your server config ```yaml auth: - type: http options: # a post request will be send to this url on every incoming connection endpointUrl: http://localhost:9090/realtime-login # any of these will be treated as access granted permittedStatusCodes: [ 200 ] # if the webhook didn't respond after this amount of milliseconds, the connection will be rejected requestTimeout: 2000 # the codes which the auth handler should retry. This is useful for when the API you depend on is # flaky or going through a not so blue/green deployment retryStatusCodes: [ 404, 504 ] # the maximum amount of retries before returning a false login retryAttempts: 3 # the time in milliseconds between retries retryInterval: 5000 ``` ## Connecting client to tazamun To ensure it works we need to connect the client to tazamun. To do so you simply just create a tazamun instance. ```javascript const client = new TazamunClient('localhost:6020/tazamun') ``` You can then look at and monitor the tazamun connection status in order to see if your connected, useful to react to when the connection is ever lost. ```javascript // Getting the connection state client.getConnectionState() // This will return AWAITING_AUTHENTICATION client.on('connectionStateChanged', (newState) => { // newState will be OPEN when the connection has been correctly authenticated }) ``` ## Logging client into tazamun Great! You now have a connection to the server. The last thing to do is login. In order to do you so you can either use Promises, async/await or a login callback. For code readability I will be using async/await for all examples in this guide. ```javascript async () => { const clientData = await client.login({ token: 'this-is-my-token' }) client.getConnectionState() // This will return OPEN } ``` ## Enabling open-auth for anonymous users In this application we actually don't actually care about the front-end permissions, since anyone can request a progress event. This is where multiple authentication providers can shine. By just adding an open authentication as the last (in this case second) authentication layer all users are accepted, but we'll be able differently permission anonymous users to greatly limit their impact ```yaml auth: - type: http options: ... - type: open ``` And to login in the browser just add: ```javascript const client = tazamun("localhost:6020/tazamun") // Since it's open we don't need pass anything in client.login() ```

30.831933

390

0.720087

eng_Latn

0.99203

d0cc64da4ae124b0c84291a6b781b03bf4f1848b

4,519

md

Markdown

IterationPlan.md

chriscoombs/quickstart-datalake-cognizant-talend

8b2d0f8cc06afb315294b8d91b13c3d7b1029f01

[ "Apache-2.0" ]

1

2019-01-22T03:04:48.000Z

IterationPlan.md

chriscoombs/quickstart-datalake-cognizant-talend

8b2d0f8cc06afb315294b8d91b13c3d7b1029f01

[ "Apache-2.0" ]

null

IterationPlan.md

chriscoombs/quickstart-datalake-cognizant-talend

8b2d0f8cc06afb315294b8d91b13c3d7b1029f01

[ "Apache-2.0" ]

null

# Talend-AWS-Cognizant Iteration Plan Product Backlog - Release 2 * Support Talend 6.4.1 * Use AWS Code Commit * Add CI Server * Move Nexus and CI server to separate subnet * Add support for multiple environments, environments share access to Nexus which is placed in a separate subnet. * Add option to generate passwords * Validate PCI template end-to-end * Add ELB to PCI master. * Snapshot stack configuration * Developers guide for utility scripts and factory * CI test case documents * Capture launch parameters in aws cli cfn script in credentials bucket * Load git with App Team’s Talend project Release 1.0 - Target 9/22 ** Iteration 0.5.0 - Self-contained Resources, Capture App Credentials, No AWS Secrets ** * DataSource configuration parameterizatoin * Add Studio server instance to Talend baseline. * Update and re-test factory scripts * Add parameter labels and grouping for entry point templates * Refactor and simplify the credential lambda function * Use IAM role with s3fs * Move s3fs github dependency to talend repo * Add credentials for git, nexus, and tac to credentials bucket * Add policies for bucket access to IAM roles * EMR Shutdown issues documented * Bastion issue replicated with original bastion stack * Gitlab project url fixed * Parameters files and other AWS CI support artifacts. Iteration 0.4.0 - Servers and Credentials * Add an Auto-Scaling element for the job server. * Clean out old RDS from DataSource template. * Add DataSource to oodle-basic template. * Add metaservlet scripts to TAC to create users * Fix Gitlab bug. * Add error protection retry around yum and apt-get operations * Remove TUI LicenseUser and LicensePassword parameters * Credentials Bucket * Persist credentials from all servers in separate property files in the same secure bucket * Add lambda for Redshift credentials Iteration 0.3.0 - Self-Contained Scripts and Naming Conventions * Standardize Outputs * Standard Tags for EC2 instances * StackId * StackName * Name - role of server, e.g. TAC, Nexus, Jobserver, Logserver, Git * Naming Conventions * Parameters: camel case with initial cap * Mappings: camel case with initial cap for categories, uppercase for final attribute * Conditions: either camel case with ending "Condition", or begin with "is" prefix * Resources: camel case with initial cap * Outputs: camel case with initial cap for resources or stacks, camel case with initial lowercase for primitives like IP or DNS name * Autonomous and self-contained * Refactor hard coded references for updated_hosts.sh to Mappings * Move github script zip file to use just s3 with QSS3Bucket and QSS3KeyPrefix * Refactor updates_hossts to use QSS3Bucket and QSS3KeyPrefix * Git * Add Git to Security Group configuration * Fix git security group so it is not wide open Iteration 0.2.0 - Database and Git Bootstrap TAC Database * Updated the TAC template to create the TAC and AMC databases. Add supporting parameters to TAC template as well as Servers and Master templates. (in progress) Git Integration * Setup the configuration scripts for Git so that on each boot a git repo is created * Wire git repo configuration and access credentials to the TAC configuration in the master template using the talend_servers nested stack parameters. * Add Git server to the basic OODLE template (the one using just AWS VPC). * Move Git server from Datasource template to the its own template. Move the template from the datasource git repo to its own file under templates in the quickstart-datalake-cognizant-talend folder. Version Control * Modify Talend baseline stack to use AWS conventions of qss3bucket. * Rename templates to .template rather than .json. * Use qss3prefix for versioning in the s3 bucket folder structure only. Not used in git structure. Iteration 0.1.0 - Initial Internal Release This first internal release is included in the corresponding 0.1.0 release of the quickstart-datalake-cognizant-talend. The talend_master template uses the talend_servers template to provision Nexus, Logserver, TAC, and Jobserver instances from their respective templates. The talend_master wires the talend_network template resources to each of the server templates. The talend_master and talend_network templates are intended to provide a simple integration test fixture for the talend_servers template. The individual servers and the talend_servers template are the unit of deployment used by other Cloud Formation scripts.

48.074468

353

0.788891

eng_Latn

0.966039

d0cd1116ed18eb992414d8aed61320b45a4cb391

7,139

md

Markdown

Teams/upgrade-to-Teams-execute-SkypeforBusinessOnline.md

ASolom1/OfficeDocs-SkypeForBusiness

53ee203316f296e27eb3e54febfc4a71086a5f1c

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

null

Teams/upgrade-to-Teams-execute-SkypeforBusinessOnline.md

ASolom1/OfficeDocs-SkypeForBusiness

53ee203316f296e27eb3e54febfc4a71086a5f1c

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

null

Teams/upgrade-to-Teams-execute-SkypeforBusinessOnline.md

ASolom1/OfficeDocs-SkypeForBusiness

53ee203316f296e27eb3e54febfc4a71086a5f1c

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

null

--- title: Upgrade from Skype for Business Online to Microsoft Teams author: dstrome ms.author: dstrome manager: serdars ms.topic: article ms.service: msteams audience: admin ms.reviewer: landerl description: Learn how to upgrade your organization to Microsoft Teams from a Skype for Business Online deployment. ms.localizationpriority: medium search.appverid: MET150 f1.keywords: - CSH ms.custom: - Teams-upgrade-guidance - seo-marvel-apr2020 ms.collection: - Teams_ITAdmin_JourneyFromSfB - M365-collaboration appliesto: - Microsoft Teams --- # Upgrade from Skype for Business Online to Teams ![Upgrade journey diagram, emphasizing Deployment and Implementation.](media/upgrade-banner-deployment.png "Stages of the upgrade journey, with emphasis on the Deployment and Implementation stage") This article is part of Deployment and Implementation stage of your upgrade journey. Before proceeding, confirm that you've completed the following activities: - [Enlisted your project stakeholders](upgrade-enlist-stakeholders.md) - [Defined your project scope](./upgrade-define-project-scope.md) - [Understood coexistence and interoperability of Skype for Business and Teams](./teams-and-skypeforbusiness-coexistence-and-interoperability.md) - [Chosen your upgrade journey](upgrade-and-coexistence-of-skypeforbusiness-and-teams.md) - [Prepared your environment](./upgrade-prepare-environment.md) - [Prepared your organization](./upgrade-prepare-organization.md) - [Conducted a pilot](./pilot-essentials.md) Follow the guidance in this article if you have wholly deployed Skype for Business Online and want to upgrade your users from Skype for Business to Teams. You can upgrade users selectively or all-in, based on the upgrade journey that your organization has chosen, by assigning the appropriate coexistence and upgrade mode to your users. > [!IMPORTANT] > Skype for Business Online was retired on July 31, 2021. To maximize benefit realization and ensure your organization has proper time to implement your upgrade, we encourage you to begin your journey to Microsoft Teams today. Remember that a successful upgrade aligns technical and user readiness, so be sure to leverage the guidance herein as you navigate your journey to Microsoft Teams. ## Assign the coexistence and upgrade mode You can upgrade your users to TeamsOnly mode by assigning the UpgradeToTeams instance of TeamsUpgradePolicy, which can be performed by using the Microsoft Teams admin center or a Skype for Business remote Windows PowerShell session. You can do this either on a per user basis, or on a tenant-wide basis if you want to upgrade the entire tenant in one step. For more information, see [Setting your coexistence and upgrade settings](./setting-your-coexistence-and-upgrade-settings.md) and [TeamsUpgradePolicy: managing migration and coexistence](upgrade-to-teams-on-prem-tools.md). ## Upgrade all users to Teams at one time Follow these steps to upgrade all of your users to Teams at one time. ### Step 1: Notify the users of the change (optional) 1. In the Microsoft Teams admin center, select **Org-wide settings** > **Teams upgrade**. 2. Under **Coexistence mode**, change the **Notify Skype for Business users that an upgrade to Teams is available** switch to **On**. ### Step 2: Set the coexistence mode to TeamsOnly for the organization 1. In the Microsoft Teams admin center, select **Org-wide settings**. 2. Select **Teams Only** mode from the **Coexistence mode** drop-down list. ## Upgrade users in stages Follow these steps if you want to gradually upgrade your users to TeamsOnly. ### Step 1: Identify groups of users for upgrade Often organizations may choose to upgrade their organizations in success waves of users. You'll want to identify these users first so you can easily search for them in the Microsoft Teams admin center. Alternatively, you may want to use PowerShell to more efficiently do this. Once you have identified the set of users for a given upgrade wave, continue with the remaining steps. ### Step 2: Set notification for the users in the current upgrade wave (optional) If using the Microsoft Teams admin center, you can configure TeamsUpgradePolicy for up to 20 user at once: 1. In the Microsoft Teams admin center, select **Users**, and find and multi-select the checkbox for up to 20 users who should be upgraded. 2. Select **Edit settings** in the upper left corner of the listview. 3. In the **Edit settings** pane on the right, under **Teams upgrade**, change **Notify the Skype for Business user** switch to **On**. Note: If the value of coexistence mode is "Use Org-wide settings", you won't see this switch, so you'll need to first explicitly set the Coexistence mode for these users to whatever the default value is for the org. Alternatively, you may find it easier to enable notifications for groups of users at once using PowerShell. ### Step 3: Set the coexistence mode for users to Teams Only When you are ready to upgrade the users in the current wave to use Teams as their only application, set the Coexistence mode for the users to Teams Only. If using the Microsoft Teams admin center, you can configure TeamsUpgradePolicy for up to 20 user at once: 1. In the Microsoft Teams admin center, select **Users**, and then select the checkbox for up to 20 users. 2. Select **Edit settings** in the upper left corner of the listview. 3. In the **Edit settings** pane on the right, under **Teams upgrade** section, set the coexistence mode to **Teams Only** in the drop-down list. Alternatively, you may find it easier to upgrade groups of users at once using PowerShell. ### Step 4: Repeat steps 1-3 for successive waves of users As you validate your upgrade to Teams Only mode and are ready to expand, repeat the previous steps to apply TeamsOnly to more users. ## Phone System and PSTN connectivity options Phone System with Teams is supported after the user is in TeamsOnly mode. (If the user is in Islands mode, Phone System is only supported with Skype for Business.) ### PSTN connectivity options When considering Public Switched Telephone Network (PSTN) connectivity options, there are two possible scenarios when moving from Skype for Business Online to TeamsOnly mode: - A user in Skype for Business Online, with a Microsoft Calling Plan. Upon upgrade, this user will continue to have a Microsoft Calling plan. This is the simplest scenario requiring only a couple of steps. For more information, see [From Skype for Business Online with Microsoft Calling Plans](upgrade-to-teams-on-prem-pstn-considerations.md#from-skype-for-business-online-with-microsoft-calling-plans). - A user in Skype for Business Online, with on-premises voice functionality through Skype for Business on-premises or Cloud Connector Edition. The user’s upgrade to Teams needs to be coordinated with migration of the user to Direct Routing to ensure the TeamsOnly user has PSTN functionality. For more information see, [From Skype for Business Online with on-premises voice](upgrade-to-teams-on-prem-pstn-considerations.md#from-skype-for-business-online-with-on-premises-voice).

66.719626

479

0.789186

eng_Latn

0.993309

d0cd26a0adc2615fb41276dd2499469550d585d0

1,330

md

Markdown

nnvm/docs/how_to/deploy.md

CynthiaProtector/helo

ad9e22363a92389b3fa519ecae9061c6ead28b05

[ "Apache-2.0" ]

9

2019-04-19T04:45:18.000Z

2021-01-07T06:31:15.000Z

src/nnvm/docs/how_to/deploy.md

tashby/turicreate

7f07ce795833d0c56c72b3a1fb9339bed6d178d1

[ "BSD-3-Clause" ]

3

2021-09-08T02:18:00.000Z

2022-03-12T00:39:44.000Z

src/nnvm/docs/how_to/deploy.md

tashby/turicreate

7f07ce795833d0c56c72b3a1fb9339bed6d178d1

[ "BSD-3-Clause" ]

5

2019-09-18T20:21:23.000Z

2020-11-22T11:18:15.000Z

Deploy Compiled Modules ======================= NNVM compiled modules are fully embedded in TVM runtime as long as ```GRAPH_RUNTIME``` option is enabled in tvm runtime. Check out the [TVM documentation](http://docs.tvmlang.org/) for how to deploy TVM runtime to your system. In a nutshell, we will need three items to deploy a compiled module. Checkout our tutorials on getting started with NNVM compiler for more details. - The graph json data which contains the execution graph. - The tvm module library of compiled functions. - The parameter blobs for stored parameters. We can then use TVM's runtime API to deploy the compiled module. Here is an example in python. ```python import tvm # tvm module for compiled functions. loaded_lib = tvm.module.load("deploy.so") # json graph loaded_json = open(temp.relpath("deploy.json")).read() # parameters in binary loaded_params = bytearray(open(temp.relpath("deploy.params"), "rb").read()) fcreate = tvm.get_global_func("tvm.graph_runtime.create") ctx = tvm.gpu(0) gmodule = fcreate(loaded_json, loaded_lib, ctx.device_type, ctx.device_id) set_input, get_output, run = gmodule["set_input"], gmodule["get_output"], gmodule["run"] set_input("x", tvm.nd.array(x_np)) gmodule["load_params"](loaded_params) run() out = tvm.nd.empty(shape) get_output(0, out) print(out.asnumpy()) ```

35

93

0.748872

eng_Latn

0.896211

d0cd8331a012f075e3393b8b1930858219c72b68

1,808

md

Markdown

articles/virtual-machines/windows/classic/connect-vms-classic.md

CosmoHuang/azure-docs.zh-cn

f4707b0ff0677024bab25636b163d1e3d8bed3e8

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

null

articles/virtual-machines/windows/classic/connect-vms-classic.md

CosmoHuang/azure-docs.zh-cn

f4707b0ff0677024bab25636b163d1e3d8bed3e8

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

null

articles/virtual-machines/windows/classic/connect-vms-classic.md

CosmoHuang/azure-docs.zh-cn

f4707b0ff0677024bab25636b163d1e3d8bed3e8

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

null

--- title: 连接云服务中的 Windows VM | Microsoft Docs description: 将使用经典部署模型创建的 Windows 虚拟机连接到 Azure 云服务或虚拟网络。 services: virtual-machines-windows documentationcenter: '' author: cynthn manager: jeconnoc editor: '' tags: azure-service-management ROBOTS: NOINDEX ms.assetid: c1cbc802-4352-4d2e-9e49-4ccbd955324b ms.service: virtual-machines-windows ms.workload: infrastructure-services ms.tgt_pltfrm: vm-windows ms.devlang: na ms.topic: article ms.date: 06/06/2017 ms.author: cynthn ms.openlocfilehash: b5778336b2dfb3d65cb678c96525ec22da1634a0 ms.sourcegitcommit: 5b2ac9e6d8539c11ab0891b686b8afa12441a8f3 ms.translationtype: HT ms.contentlocale: zh-CN ms.lasthandoff: 04/06/2018 --- # <a name="connect-windows-virtual-machines-created-with-the-classic-deployment-model-with-a-virtual-network-or-cloud-service"></a>将使用经典部署模型创建的 Windows 虚拟机连接到虚拟网络或云服务 > [!IMPORTANT] > Azure 提供两个不同的部署模型用于创建和处理资源：[资源管理器和经典模型](../../../resource-manager-deployment-model.md)。本文介绍如何使用经典部署模型。 Microsoft 建议大多数新部署使用资源管理器模型。使用经典部署模型创建的 Windows 虚拟机始终放置在云服务中。云服务充当容器，并提供唯一的公用 DNS 名称、公用 IP 地址，以及一组通过 Internet 访问虚拟机的终结点。云服务可以位于虚拟网络中，但这不是必要条件。如果云服务不在虚拟网络中，就称为*独立*云服务。独立云服务中的虚拟机使用其他虚拟机的公用 DNS 名称与其通信，流量通过 Internet 传送。如果云服务是在虚拟网络中，则该云服务中的虚拟机可与虚拟网络中的其他所有虚拟机通信，而不需要通过 Internet 传送任何流量。如果将虚拟机放在相同的独立云服务中，仍然可以使用负载均衡和可用性集。有关详细信息，请参阅[对虚拟机进行负载均衡](../../virtual-machines-windows-load-balance.md?toc=%2fazure%2fvirtual-machines%2fwindows%2ftoc.json)和[管理虚拟机的可用性](../../virtual-machines-windows-manage-availability.md?toc=%2fazure%2fvirtual-machines%2fwindows%2ftoc.json)。不过，无法组织子网上的虚拟机，也无法将独立云服务连接到本地网络。下面是一个示例： [!INCLUDE [virtual-machines-common-classic-connect-vms](../../../../includes/virtual-machines-common-classic-connect-vms.md)] ## <a name="next-steps"></a>后续步骤创建虚拟机后，建议[添加数据磁盘](attach-disk.md)，以便服务和工作负荷有地方存储数据。

46.358974

321

0.800332

yue_Hant

0.370549

d0ce844f73a440daa72ec67c6d2c1dd43601fd3e

5,646

md

Markdown

docs/2014/tools/sql-server-profiler/sql-server-profiler-templates-and-permissions.md

CeciAc/sql-docs.fr-fr

0488ed00d9a3c5c0a3b1601a143c0a43692ca758

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

null

docs/2014/tools/sql-server-profiler/sql-server-profiler-templates-and-permissions.md

CeciAc/sql-docs.fr-fr

0488ed00d9a3c5c0a3b1601a143c0a43692ca758

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

null

docs/2014/tools/sql-server-profiler/sql-server-profiler-templates-and-permissions.md

CeciAc/sql-docs.fr-fr

0488ed00d9a3c5c0a3b1601a143c0a43692ca758

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

1

2020-03-04T05:50:54.000Z

--- title: Modèles et autorisations de SQL Server Profiler | Microsoft Docs ms.custom: '' ms.date: 06/13/2017 ms.prod: sql-server-2014 ms.reviewer: '' ms.technology: profiler ms.topic: conceptual helpviewer_keywords: - Profiler [SQL Server Profiler], about SQL Server Profiler - SQL Server Profiler, about SQL Server Profiler ms.assetid: 6d00378a-5d74-463b-9ed6-a2685306a9d2 author: stevestein ms.author: sstein manager: craigg ms.openlocfilehash: 7d7e92758707217a42afbd41649720907adfeaa3 ms.sourcegitcommit: 3026c22b7fba19059a769ea5f367c4f51efaf286 ms.translationtype: MT ms.contentlocale: fr-FR ms.lasthandoff: 06/15/2019 ms.locfileid: "68211056" --- # <a name="sql-server-profiler-templates-and-permissions"></a>Modèles et autorisations du générateur de SQL Server Profiler [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] indique comment [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] résout les requêtes en interne. Les administrateurs peuvent ainsi voir exactement quelles sont les expressions multidimensionnelles ou les instructions [!INCLUDE[tsql](../../includes/tsql-md.md)] qui sont soumises au serveur et comment celui-ci accède à la base de données ou au cube pour renvoyer des jeux de résultats. Le [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)]vous permet d'effectuer les opérations suivantes : - Créer une trace basée sur un modèle réutilisable - Observer les résultats de la trace au fil de son exécution - Stocker les résultats de la trace dans une table - Démarrer, arrêter, suspendre et modifier les résultats de la trace en fonction des besoins - Relire les résultats de la trace Utilisez le [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] pour surveiller uniquement les événements qui vous intéressent. Si les traces deviennent trop volumineuses, vous pouvez les filtrer en fonction des informations de votre choix, de manière à ce que seul un sous-ensemble des données d’événement soit recueilli. La surveillance d'un trop grand nombre d'événements s'ajoute à la charge du serveur et du processus de surveillance, et peut considérablement accroître la taille du fichier ou de la table de trace, en particulier si le processus de surveillance se prolonge sur une période importante. > [!NOTE] > Les valeurs des colonnes de traces supérieures à 1 Go renvoient une erreur et sont tronquées dans la sortie de trace. ## <a name="in-this-section"></a>Dans cette section |Rubrique|Description| |-----------|-----------------| |[Modèles du Générateur de profils SQL Server](sql-server-profiler-templates.md)|Contient des informations relatives aux modèles de trace prédéfinis fournis avec le [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)].| |[Autorisations nécessaires pour exécuter SQL Server Profiler](permissions-required-to-run-sql-server-profiler.md)|Contient des informations relatives aux autorisations requises pour exécuter le [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)].| |[Enregistrer des traces et de modèles de trace](save-traces-and-trace-templates.md)|Contient des informations relatives à l'enregistrement de la sortie de la trace et des définitions de la trace dans un modèle.| |[Modifier des modèles de trace](modify-trace-templates.md)|Contient des informations relatives à la modification des modèles de trace à l'aide du [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] ou de [!INCLUDE[tsql](../../includes/tsql-md.md)].| |[Démarrer une trace](start-a-trace.md)|Contient des informations relatives à ce qui se passe quand vous démarrez, quand vous suspendez ou quand vous arrêtez une trace.| |[Mettre en corrélation une trace avec les données du journal de performances Windows](correlate-a-trace-with-windows-performance-log-data.md)|Contient des informations relatives à la corrélation des données du journal de performances Windows avec une trace à l'aide du Générateur de profils [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] .| |[Afficher et analyser des traces avec SQL Server Profiler](view-and-analyze-traces-with-sql-server-profiler.md)|Contient des informations relatives à l'utilisation de traces pour la résolution de problèmes de données, à l'affichage des noms d'objet dans une trace et à la recherche d'événements dans une trace.| |[Analyser des blocages à l'aide de SQL Server Profiler](analyze-deadlocks-with-sql-server-profiler.md)|Contient des informations relatives à l'utilisation du [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] pour identifier la cause d'un blocage.| |[Analyser des requêtes avec des résultats SHOWPLAN dans SQL Server Profiler](analyze-queries-with-showplan-results-in-sql-server-profiler.md)|Contient des informations relatives à l'utilisation du [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] pour collecter et afficher les résultats des classes d'événements Showplan et Showplan Statistics.| |[Filtrer des traces avec SQL Server Profiler](filter-traces-with-sql-server-profiler.md)|Contient des informations relatives à l'utilisation du [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)]pour définir des filtres sur les colonnes de données afin de filtrer la sortie de la trace.| |[Relire des traces](replay-traces.md)|Contient des informations qui expliquent ce qu'est la relecture d'une trace et qui indiquent les conditions nécessaires à sa réalisation.| ## <a name="see-also"></a>Voir aussi [SQL Server Profiler](sql-server-profiler.md) [Démarrer SQL Server Profiler](start-sql-server-profiler.md)

88.21875

620

0.776302

fra_Latn

0.881494

d0cf3794ffba2adc88e520502dc13ca5b19b7aec

6,158

md

Markdown

INSTALL.md

Magnusgaertner/pytorch3d

eb04a488c57da0e4e5651f5f37349e058cbfedc7

[ "BSD-3-Clause" ]

null

INSTALL.md

Magnusgaertner/pytorch3d

eb04a488c57da0e4e5651f5f37349e058cbfedc7

[ "BSD-3-Clause" ]

null

INSTALL.md

Magnusgaertner/pytorch3d

eb04a488c57da0e4e5651f5f37349e058cbfedc7

[ "BSD-3-Clause" ]

null

# Installation ## Requirements ### Core library The core library is written in PyTorch. Several components have underlying implementation in CUDA for improved performance. A subset of these components have CPU implementations in C++/PyTorch. It is advised to use PyTorch3D with GPU support in order to use all the features. - Linux or macOS or Windows - Python 3.6, 3.7 or 3.8 - PyTorch 1.4, 1.5.0, 1.5.1, 1.6.0, 1.7.0, or 1.7.1. - torchvision that matches the PyTorch installation. You can install them together as explained at pytorch.org to make sure of this. - gcc & g++ ≥ 4.9 - [fvcore](https://github.com/facebookresearch/fvcore) - [ioPath](https://github.com/facebookresearch/iopath) - If CUDA is to be used, use a version which is supported by the corresponding pytorch version and at least version 9.2. - If CUDA is to be used and you are building from source, the CUB library must be available. We recommend version 1.10.0. The runtime dependencies can be installed by running: ``` conda create -n pytorch3d python=3.8 conda activate pytorch3d conda install -c pytorch pytorch=1.7.1 torchvision cudatoolkit=10.2 conda install -c conda-forge -c fvcore -c iopath fvcore iopath ``` For the CUB build time dependency, if you are using conda, you can continue with ``` conda install -c bottler nvidiacub ``` Otherwise download the CUB library from https://github.com/NVIDIA/cub/releases and unpack it to a folder of your choice. Define the environment variable CUB_HOME before building and point it to the directory that contains `CMakeLists.txt` for CUB. For example on Linux/Mac, ``` curl -LO https://github.com/NVIDIA/cub/archive/1.10.0.tar.gz tar xzf 1.10.0.tar.gz export CUB_HOME=$PWD/cub-1.10.0 ``` ### Tests/Linting and Demos For developing on top of PyTorch3D or contributing, you will need to run the linter and tests. If you want to run any of the notebook tutorials as `docs/tutorials` or the examples in `docs/examples` you will also need matplotlib and OpenCV. - scikit-image - black - isort - flake8 - matplotlib - tdqm - jupyter - imageio - plotly - opencv-python These can be installed by running: ``` # Demos and examples conda install jupyter pip install scikit-image matplotlib imageio plotly opencv-python # Tests/Linting pip install black 'isort<5' flake8 flake8-bugbear flake8-comprehensions ``` ## Installing prebuilt binaries for PyTorch3D After installing the above dependencies, run one of the following commands: ### 1. Install with CUDA support from Anaconda Cloud, on Linux only ``` # Anaconda Cloud conda install pytorch3d -c pytorch3d ``` Or, to install a nightly (non-official, alpha) build: ``` # Anaconda Cloud conda install pytorch3d -c pytorch3d-nightly ``` ### 2. Install from PyPI, on Mac only. This works with pytorch 1.7.1 only. The build is CPU only. ``` pip install pytorch3d ``` ### 3. Install wheels for Linux We have prebuilt wheels with CUDA for Linux for PyTorch 1.7.0 and 1.7.1, for each of the CUDA versions that they support. These are installed in a special way. For example, to install for Python 3.6, PyTorch 1.7.0 and CUDA 10.1 ``` pip install pytorch3d -f https://dl.fbaipublicfiles.com/pytorch3d/packaging/wheels/py36_cu101_pyt170/download.html ``` In general, from inside IPython, or in Google Colab or a jupyter notebook, you can install with ``` import sys import torch version_str="".join([ f"py3{sys.version_info.minor}_cu", torch.version.cuda.replace(".",""), f"_pyt{torch.__version__[0:5:2]}" ]) !pip install pytorch3d -f https://dl.fbaipublicfiles.com/pytorch3d/packaging/wheels/{version_str}/download.html ``` ## Building / installing from source. CUDA support will be included if CUDA is available in pytorch or if the environment variable `FORCE_CUDA` is set to `1`. ### 1. Install from GitHub ``` pip install "git+https://github.com/facebookresearch/pytorch3d.git" ``` To install using the code of the released version instead of from the main branch, use the following instead. ``` pip install "git+https://github.com/facebookresearch/pytorch3d.git@stable" ``` For CUDA builds with versions earlier than CUDA 11, set `CUB_HOME` before building as described above. **Install from Github on macOS:** Some environment variables should be provided, like this. ``` MACOSX_DEPLOYMENT_TARGET=10.14 CC=clang CXX=clang++ pip install "git+https://github.com/facebookresearch/pytorch3d.git" ``` ### 2. Install from a local clone ``` git clone https://github.com/facebookresearch/pytorch3d.git cd pytorch3d && pip install -e . ``` To rebuild after installing from a local clone run, `rm -rf build/ **/*.so` then `pip install -e .`. You often need to rebuild pytorch3d after reinstalling PyTorch. For CUDA builds with versions earlier than CUDA 11, set `CUB_HOME` before building as described above. **Install from local clone on macOS:** ``` MACOSX_DEPLOYMENT_TARGET=10.14 CC=clang CXX=clang++ pip install -e . ``` **Install from local clone on Windows:** If you are using pre-compiled pytorch 1.4 and torchvision 0.5, you should make the following changes to the pytorch source code to successfully compile with Visual Studio 2019 (MSVC 19.16.27034) and CUDA 10.1. Change python/Lib/site-packages/torch/include/csrc/jit/script/module.h L466, 476, 493, 506, 536 ``` -static constexpr * +static const * ``` Change python/Lib/site-packages/torch/include/csrc/jit/argument_spec.h L190 ``` -static constexpr size_t DEPTH_LIMIT = 128; +static const size_t DEPTH_LIMIT = 128; ``` Change python/Lib/site-packages/torch/include/pybind11/cast.h L1449 ``` -explicit operator type&() { return *(this->value); } +explicit operator type& () { return *((type*)(this->value)); } ``` After patching, you can go to "x64 Native Tools Command Prompt for VS 2019" to compile and install ``` cd pytorch3d python3 setup.py install ``` After installing, verify whether all unit tests have passed ``` cd tests python3 -m unittest discover -p *.py ``` # FAQ ### Can I use Docker? We don't provide a docker file but see [#113](https://github.com/facebookresearch/pytorch3d/issues/113) for a docker file shared by a user (NOTE: this has not been tested by the PyTorch3D team).

33.835165

275

0.75138

eng_Latn

0.96952

d0cfc44ffe1f30ff53a914d50b091dbaa84a726b

1,899

markdown

Markdown

_posts/2015-01-20-programming-for-physicians-a-crash-course.markdown

365zph/365zph.github.io

c5fc8b1ec00511214632d94db0ac86dedc4f0afa

[ "MIT" ]

null

_posts/2015-01-20-programming-for-physicians-a-crash-course.markdown

365zph/365zph.github.io

c5fc8b1ec00511214632d94db0ac86dedc4f0afa

[ "MIT" ]

null

_posts/2015-01-20-programming-for-physicians-a-crash-course.markdown

365zph/365zph.github.io

c5fc8b1ec00511214632d94db0ac86dedc4f0afa

[ "MIT" ]

null

--- author: viviworld comments: true date: 2015-01-20 00:15:09+00:00 layout: post link: http://www.labazhou.net/2015/01/programming-for-physicians-a-crash-course/ slug: programming-for-physicians-a-crash-course title: 面向医生的编程---速成课程 wordpress_id: 1550 categories: - 编程 tags: - module - oop - python - 教程 - 数据科学 --- 原文地址（original source）：[http://programmingforphysicians.com/](http://programmingforphysicians.com/) 欢迎阅读这份关于编程的速成课程，其受众人群是医生。为什么是医生？因为从历史角度看，医生不是最有可能学习计算机编程的职业，然而，当代能够[说计算机语言](http://www.labazhou.net/2014/12/programming-languages-as-languages/)（至少在某种程度），对于总体科学研究技能而言，是一个受欢迎的加分项，尤其是[数据科学](http://en.wikipedia.org/wiki/Data_science)。早些时候，我写过一篇评论文章“[为什么医生可能想学习计算机编程](http://www.surgicalneurologyint.com/text.asp?2013/4/1/30/109461)”，阐述了我是如何考虑这个观点的。简而言之，计算机编程有三个主要部分： * 数据输入 * 数据操作 * 数据输出注意，这是一个高级的、非常笼统的综述。**输入**可以是用户输入的一些文本、鼠标点击、在移动设备上的触碰和手势、从磁盘载入的文件、来自web的数据库，甚至自动化输入（例如，在某个特定时间触发代码）。**输出**也可以是一些文本、图像、声音、视频、或任何你能想象到的、将被发送给用户或某些服务器的东东。正如你猜测的，数据**操作**是较有意思的环节，会有魔法发生。实际上，没有太多的魔法。粗略地讲，数据操作也有三个主要部分： * 计算 * 条件语句 * 循环变量是你能够用来存储信息的参数。当我说“存储”时，我没有显式地指出“存在磁盘”或“存在线上”。首先，它意味着保留（或者如官方的叫法，分配）你计算机上的某些（工作）内存，你可以把信息临时放在那里。代码被执行后，当你不再需要它时，变量就从内存中擦除了。如果你想存储某些信息（存到磁盘、闪存盘或远程服务器上）供日后使用，你不得不明确地去实现。顺便说一句，本教程没有涵盖后者。但是了解它是有好处的。对于当下，变量是你经常用来操作的某种参数。我猜，**计算**更像是自解释的。从历史角度看，计算机被开发为高级计算器，仅在后来才添加了其它功能。计算不同于简单的数学，更多的是复杂的处理，但本质相同。 **条件语句**，正如它的叫法。对于护士而言，你可能说，如果病人温度高于39摄氏度，那么你想预定血培养（blood culture），否则他们应该在两小时后再次测量体温。条件语句，或“if-else语句”，用于在程序里做决定。 **循环**被用于重复的语句。计算机在多次重复同样任务上，要比人类强很多，循环就是因此而产生的。有两种循环，所谓的for循环和while循环。我们将详细谈到它们。随着编程规模的扩大，你需要一种方式来组织代码。函数是避免重复代码的方法，在更大型的项目里，你能够针对性地使用模块（module）或类（class）。我们来一窥函数，按照我们的方式使用一些内置模块。 <blockquote>注意：模块和类是不一样的。模块本质上只是带有一些函数的文件，而类被用于叫做面向对象编程（OOP）的编程风格里。OOP不在本教程范围内。</blockquote> 在本教程里，我们将使用编程语言[Python](https://www.python.org/)。它有着非常直接和可读的语法，开源、可完全自由使用，当你掌握基础之后，你就能发现那些使用起来比较有意思的科学上的模块。好了，背景信息介绍得已经足够多了……让我们开始吧！

26.375

345

0.789363

yue_Hant

0.462349

d0d01505ba1af5086bf17f66c69912b2fa722192

2,671

md

Markdown

docs/vsto/working-with-contact-items.md

MicrosoftDocs/visualstudio-docs.de-de

edda581743b0eede0b99441d8e52a8d0e133dec8

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

10

2018-09-27T09:13:44.000Z

2021-09-08T07:12:47.000Z

docs/vsto/working-with-contact-items.md

MicrosoftDocs/visualstudio-docs.de-de

edda581743b0eede0b99441d8e52a8d0e133dec8

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

68

2018-02-07T12:07:58.000Z

2021-03-19T00:35:58.000Z

docs/vsto/working-with-contact-items.md

MicrosoftDocs/visualstudio-docs.de-de

edda581743b0eede0b99441d8e52a8d0e133dec8

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

41

2018-01-05T16:53:02.000Z

2021-10-09T11:00:50.000Z

--- title: Arbeiten mit Kontaktelementen description: Erfahren Sie, dass die ContactItem-Klasse die Methoden und Eigenschaften enthält, die Sie zum Ausführen von Aufgaben mit Kontakten verwenden. ms.custom: SEO-VS-2020 ms.date: 02/02/2017 ms.topic: conceptual dev_langs: - VB - CSharp helpviewer_keywords: - Outlook [Office development in Visual Studio], contacts - contacts [Office development in Visual Studio], about contacts - e-mail [Office development in Visual Studio], contacts - contacts [Office development in Visual Studio] author: John-Hart ms.author: johnhart manager: jmartens ms.technology: office-development ms.workload: - office ms.openlocfilehash: fcfb73f1a6333f893d73f6e61204941fa4f913e3 ms.sourcegitcommit: 68897da7d74c31ae1ebf5d47c7b5ddc9b108265b ms.translationtype: MT ms.contentlocale: de-DE ms.lasthandoff: 08/13/2021 ms.locfileid: "122025367" --- # <a name="work-with-contact-items"></a>Arbeiten mit Kontaktelementen Die <xref:Microsoft.Office.Interop.Outlook.ContactItem> -Klasse enthält die Methoden und Eigenschaften, die Sie zum Ausführen von Aufgaben mit Kontakten verwenden. |Aufgabe|Vorgehensweise| |----------|---------------| |Abrufen aller Kontakte, deren Nachname eine angegebene Zeichenfolge enthält.|[Vorgehensweise: Programmgesteuerter Zugriff auf Outlook Kontakte](../vsto/how-to-programmatically-access-outlook-contacts.md)| |Suchen eines Kontakts nach Vor- und Nachname.|[Vorgehensweise: Programmgesteuertes Suchen nach einem bestimmten Kontakt](../vsto/how-to-programmatically-search-for-a-specific-contact.md)| |Erstellen eines neuen Kontakts und Ausfüllen der Kontaktinformationen.|[Vorgehensweise: Programmgesteuertes Hinzufügen eines Eintrags zu Outlook Kontakten](../vsto/how-to-programmatically-add-an-entry-to-outlook-contacts.md)| |Suchen nach Kontakten, deren E-Mail-Adresse eine bestimmte Domäne enthält.|[Vorgehensweise: Programmgesteuertes Suchen nach einer E-Mail-Adresse in Kontakten](../vsto/how-to-programmatically-search-for-an-e-mail-address-in-contacts.md)| |Löschen eines Kontakts, der einen angegebenen Namen aufweist.|[Vorgehensweise: Programmgesteuertes Löschen Outlook Kontakte](../vsto/how-to-programmatically-delete-outlook-contacts.md)| Weitere Informationen zu Outlook Tasks und zum Outlook-Objektmodell finden Sie unter [übersicht über Outlook-Objektmodell.](../vsto/outlook-object-model-overview.md) ## <a name="see-also"></a>Siehe auch - [Arbeiten mit E-Mail-Elementen](../vsto/working-with-mail-items.md) - [Arbeiten mit Ordnern](../vsto/working-with-folders.md) - [Arbeiten mit Kalenderelementen](../vsto/working-with-calendar-items.md) - [Outlook Lösungen](../vsto/outlook-solutions.md)

58.065217

237

0.798203

deu_Latn

0.884607

d0d0f1659da01e1fba87a77dcfd426871440d772

60

md

Markdown

README.md

JotaGo/rock-paper-scissor

575677ad8d65a70fd535dfddf9fa97c8a4ca8e5c

[ "MIT" ]

null

README.md

JotaGo/rock-paper-scissor

575677ad8d65a70fd535dfddf9fa97c8a4ca8e5c

[ "MIT" ]

null

README.md

JotaGo/rock-paper-scissor

575677ad8d65a70fd535dfddf9fa97c8a4ca8e5c

[ "MIT" ]

null

# rock-paper-scissor Rock, paper and scissor game in Python

20

38

0.783333

eng_Latn

0.995821

d0d138a7cea68e629c3672725ca688892f5752da

1,491

md

Markdown

creator/ScriptAPI/mojang-minecraft/ItemCooldownComponent.md

Lapis256/minecraft-creator

0b1afe2b871d154ad8513b50c1bf9b78fb032f62

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

null

creator/ScriptAPI/mojang-minecraft/ItemCooldownComponent.md

Lapis256/minecraft-creator

0b1afe2b871d154ad8513b50c1bf9b78fb032f62

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

null

creator/ScriptAPI/mojang-minecraft/ItemCooldownComponent.md

Lapis256/minecraft-creator

0b1afe2b871d154ad8513b50c1bf9b78fb032f62

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

null

--- # DO NOT TOUCH — This file was automatically generated. See https://github.com/Mojang/MinecraftScriptingApiDocsGenerator to modify descriptions, examples, etc. author: jakeshirley ms.author: jashir ms.prod: gaming title: mojang-minecraft.ItemCooldownComponent Class description: Contents of the mojang-minecraft.ItemCooldownComponent class. --- # ItemCooldownComponent Class >[!IMPORTANT] >These APIs are experimental as part of GameTest Framework. As with all experiments, you may see changes in functionality in updated Minecraft versions. Check the Minecraft Changelog for details on any changes to GameTest Framework APIs. Where possible, this documentation reflects the latest updates to APIs in Minecraft beta versions. When present on an item, this item is edible by entities. ## Properties ### **cooldownCategory** `read-only cooldownCategory: string;` Represents the cooldown category - a string - that this item is associated with. Type: *string* ### **cooldownTicks** `read-only cooldownTicks: number;` Amount of time, in ticks, that remain for this item cooldown. Type: *number* ### **id** `read-only id: string;` Identifier of this component. Should always be 'minecraft:cooldown'. Type: *string* ## Methods - [startCooldown](#startcooldown) ### **startCooldown** ` startCooldown(player: Player): void ` Starts a new cooldown period for this item. #### **Parameters** - **player**: [*Player*](Player.md) > [!WARNING] > This function can throw errors.

25.706897

336

0.757881

eng_Latn

0.957375

d0d14c830f8b1997795e94c7f17fa59e5d3a8b81

1,931

md

Markdown

_posts/2016-09-16-15/09/16.md

JJ031/Jidbog31

7391285488d44f89e83ddb55a8cf4e7258841d52

[ "MIT" ]

null

_posts/2016-09-16-15/09/16.md

JJ031/Jidbog31

7391285488d44f89e83ddb55a8cf4e7258841d52

[ "MIT" ]

null

_posts/2016-09-16-15/09/16.md

JJ031/Jidbog31

7391285488d44f89e83ddb55a8cf4e7258841d52

[ "MIT" ]

null

--- title: First Project- Fuzebox lesson 1 layout: post author: jaymin.bhatt permalink: /15/09/16/ source-id: 1XhnsDhUcR-7Iy5wf-HGcpMl5L0WeCPJUcYuGskLZhsg published: true --- <table> <tr> <td>Title</td> <td>Changing colour Fuzebox lesson 1</td> <td>Date</td> <td>7/10/16</td> </tr> </table> <table> <tr> <td>Starting point:</td> <td>Complete Project 1 inside the Fuzebox Manual</td> </tr> <tr> <td>Target for this lesson?</td> <td>To set up my fuzebox and complete the first project</td> </tr> <tr> <td>Did I reach my target? (add details to "Lesson Review")</td> <td>I reached my target to complete project 1.</td> </tr> </table> <table> <tr> <td>Lesson Review</td> </tr> <tr> <td>How did I learn? What strategies were effective? </td> </tr> <tr> <td>My partner and I, received a power cable, a mouse, a Manual and a machine. Once we plugged everything into the right places, we opened the manual and started on Project 1. The first thing our manual told us to do was to Enter the words 'Hello World' onto the editor on Fuzebox. When we entered the String, the programme duplicated the ‘Hello World’ this was because we had to enter ‘Repeat’ Onto the Editor. This would repeat the process multiple times. </td> </tr> <tr> <td>What limited my learning? Which habits do I need to work on? </td> </tr> <tr> <td>My partner and I, were a bit slow as this was something new. We needed to be more confident and approach the Programme with more recognition that we had experience in some aspects of Computing.</td> </tr> <tr> <td>What will I change for next time? How will I improve my learning?</td> </tr> <tr> <td>I need to have a lot more confidence in my work and need to keep on following the Manual but at the same time, use my knowledge to help me with the long projects.</td> </tr> </table> ** **

29.707692

469

0.670637

eng_Latn

0.990695

d0d1a78380c500a6c744918b522069273ea9d20f

1,827

md

Markdown

bsp_for_art-badge/packages/online-packages/btstack-v0.0.1/README_zh.md

Rbb666/SDK

cdf0bfeeb35b989ccf13c41b9625059de5fec87b

[ "Apache-2.0" ]

1

2022-01-09T12:34:03.000Z

project/smarthome/packages/btstack-v0.0.1/README_zh.md

jerryxiee/STM32-RT_Thread-link_H750

f64f5f20c3735db6e77d492e8365a2d459f3c8a4

[ "Apache-2.0" ]

null

project/smarthome/packages/btstack-v0.0.1/README_zh.md

jerryxiee/STM32-RT_Thread-link_H750

f64f5f20c3735db6e77d492e8365a2d459f3c8a4

[ "Apache-2.0" ]

null

# RT-Thread_BTstack ## 1. 介绍 BTstack 软件包是RT-Thread 基于 [btstack](https://github.com/bluekitchen/btstack) 开源蓝牙协议栈的适配，该协议栈支持多种蓝牙卡片，非常适合用于小型嵌入式蓝牙设备，支持几乎所有的主流的蓝牙卡片，支持无RTOS操作。 ## 2. 主要支持的Profile和Protocol **Protocols:** L2CAP (incl. LE Data Channels), RFCOMM, SDP, BNEP, AVDTP, AVCTP, ATT, SM (incl. LE Secure Connections). **Profiles:** GAP, IOP, HFP, HSP, SPP, PAN, A2DP, AVRCP incl. Browsing, GATT. **GATT Services:** Battery, Cycling Power, Cycling Speed and Cadence, Device Information, Heart Rate, HID over GATT (HOG), Mesh Provisioning, Mesh Proxy, Nordic SPP, u-Blox SPP. GATT Services are in general easy to implement and require short development time. For more GATT Services please contact us, or follow the [implementation guidelines](https://bluekitchen-gmbh.com/btstack/profiles/#gatt-generic-attribute-profile). ### 3. 许可声明 BTstack 非商业用途是免费的。但是，对于商业用途，<a href="mailto:[email protected]">请联系BTstack官方</a>关于你的项目以获得商业合作。 ## 4. 注意事项 BTstack支持很多蓝牙卡片，目前在RT-thread系统上，只支持AP6212卡片（基于ART-H750开发板），后续会支持更多蓝牙卡片。 ## 5. 目录结构本目录基本参考 [btstack](https://github.com/bluekitchen/btstack)的目录创建，适配的代码放在rtt_adapter上面，其余代码基本和源BTstack代码一致，如需更新可以自行从github上更新 ``` BTstack ├───chipset /* Bluetooth control adapter */ │ ├───bcm /* Bluetooth control AP6212(BCM) adapter */ ├───docs /* Markdown about*/ ├───example /* bt stack exampl about*/ ├───platform │ ├───posix /* btstack posix api */ ├───port │ ├───posix-h4-bcm /* btstack posix port */ ├───rtt_adapter /* the different code about the example */ └───src /* btstack source code */ ``` ## 6. 联系方式 & 感谢 - 维护：supperthomas - 主页：https://github.com/supperthomas/RTT_PACKAGE_BTSTACK

36.54

248

0.660646

yue_Hant

0.300123

d0d2b0976fe8ecc699cd3f513d304b8d6cbc606a

29,154

md

Markdown

src/components/tree/doc/index.fr-FR.md

lixi-ui/lixi-ui-vue

672b812473bb8f3330d0fe89ba9526fbd6f901b6

[ "MIT" ]

null

src/components/tree/doc/index.fr-FR.md

lixi-ui/lixi-ui-vue

672b812473bb8f3330d0fe89ba9526fbd6f901b6

[ "MIT" ]

null

src/components/tree/doc/index.fr-FR.md

lixi-ui/lixi-ui-vue

672b812473bb8f3330d0fe89ba9526fbd6f901b6

[ "MIT" ]

null

## Tree Affiche un ensemble de données possédant plusieurs niveaux de hiérarchie ou d'imbrication. ### Usage Voici la structure basique. :::demo ```html <lx-tree :data="data" :props="defaultProps" @node-click="handleNodeClick"></lx-tree> <script> export default { data() { return { data: [{ label: 'Niveau un 1', children: [{ label: 'Niveau deux 1-1', children: [{ label: 'Niveau trois 1-1-1' }] }] }, { label: 'Niveau un 2', children: [{ label: 'Niveau deux 2-1', children: [{ label: 'Niveau trois 2-1-1' }] }, { label: 'Niveau deux 2-2', children: [{ label: 'Niveau trois 2-2-1' }] }] }, { label: 'Niveau un 3', children: [{ label: 'Niveau deux 3-1', children: [{ label: 'Niveau trois 3-1-1' }] }, { label: 'Niveau deux 3-2', children: [{ label: 'Niveau trois 3-2-1' }] }] }], defaultProps: { children: 'children', label: 'label' } }; }, methods: { handleNodeClick(data) { console.log(data); } } }; </script> ``` ::: ### Sélection Vous pouvez activer la sélection des noeuds. :::demo cet exemple montre également comment charger des données de manière asynchrone. ```html <lx-tree :props="props" :load="loadNode" lazy show-checkbox @check-change="handleCheckChange"> </lx-tree> <script> export default { data() { return { props: { label: 'name', children: 'zones' }, count: 1 }; }, methods: { handleCheckChange(data, checked, indeterminate) { console.log(data, checked, indeterminate); }, handleNodeClick(data) { console.log(data); }, loadNode(node, resolve) { if (node.level === 0) { return resolve([{ name: 'Root1' }, { name: 'Root2' }]); } if (node.level > 3) return resolve([]); var hasChild; if (node.data.name === 'region1') { hasChild = true; } else if (node.data.name === 'region2') { hasChild = false; } else { hasChild = Math.random() > 0.5; } setTimeout(() => { var data; if (hasChild) { data = [{ name: 'zone' + this.count++ }, { name: 'zone' + this.count++ }]; } else { data = []; } resolve(data); }, 500); } } }; </script> ``` ::: ### Noeud-feuille personnalisés en mode lazy :::demo Les données d'un noeud ne sont pas accessibles tant que la noeud n'est pas cliqué, l'arbre ne peut donc pas prédire si un noeud sera une feuille. C'est pourquoi un bouton de menu est ajouté à chaque noeud, et si c'est une feuille il disparaîtra après le clic. Vous pouvez également dire par avance à l'arbre si un noeud est une feuille, pour éviter l'apparition du bouton de menu. ```html <lx-tree :props="props" :load="loadNode" lazy show-checkbox> </lx-tree> <script> export default { data() { return { props: { label: 'name', children: 'zones', isLeaf: 'leaf' }, }; }, methods: { loadNode(node, resolve) { if (node.level === 0) { return resolve([{ name: 'region' }]); } if (node.level > 1) return resolve([]); setTimeout(() => { const data = [{ name: 'leaf', leaf: true }, { name: 'zone' }]; resolve(data); }, 500); } } }; </script> ``` ::: ### Checkbox désactivées Les checkbox des noeuds peuvent être désactivées individuellement. :::demo Dans cet exemple, la propriété `disabled` est ajoutée à `defaultProps`, et certains noeuds ont `disabled:true`. Les checkbox correspondantes sont donc désactivées. ```html <lx-tree :data="data" :props="defaultProps" show-checkbox> </lx-tree> <script> export default { data() { return { data: [{ id: 1, label: 'Niveau un 1', children: [{ id: 3, label: 'Niveau deux 2-1', children: [{ id: 4, label: 'Niveau trois 3-1-1' }, { id: 5, label: 'Niveau trois 3-1-2', disabled: true }] }, { id: 2, label: 'Niveau deux 2-2', disabled: true, children: [{ id: 6, label: 'Niveau trois 3-2-1' }, { id: 7, label: 'Niveau trois 3-2-2', disabled: true }] }] }], defaultProps: { children: 'children', label: 'label', disabled: 'disabled', }, }; } }; </script> ``` ::: ### Ouverture et sélection par défaut Certains noeuds peuvent être ouverts et/ou sélectionnés par défaut. :::demo Utilisez `default-expanded-keys` et `default-checked-keys` pour réglez respectivement les noeuds ouverts et les noeuds sélectionnés par défaut. Notez que `node-key` est requis dans ce cas. Sa valeurs est le nom d'une clé dans l'objets data, et sa valeur devrait être unique dans tout l'arbre. ```html <lx-tree :data="data" show-checkbox node-key="id" :default-expanded-keys="[2, 3]" :default-checked-keys="[5]" :props="defaultProps"> </lx-tree> <script> export default { data() { return { data: [{ id: 1, label: 'Niveau un 1', children: [{ id: 4, label: 'Niveau deux 1-1', children: [{ id: 9, label: 'Niveau trois 1-1-1' }, { id: 10, label: 'Niveau trois 1-1-2' }] }] }, { id: 2, label: 'Niveau un 2', children: [{ id: 5, label: 'Niveau deux 2-1' }, { id: 6, label: 'Niveau deux 2-2' }] }, { id: 3, label: 'Niveau un 3', children: [{ id: 7, label: 'Niveau deux 3-1' }, { id: 8, label: 'Niveau deux 3-2' }] }], defaultProps: { children: 'children', label: 'label' } }; } }; </script> ``` ::: ### Sélectionner des noeuds :::demo Cet exemple montre comment récupérer et sélectionner des noeuds. Vous pouvez utiliser deux approches: les noeuds ou les clés. Dans le cas des clés, `node-key` est requis. ```html <lx-tree :data="data" show-checkbox default-expand-all node-key="id" ref="tree" highlight-current :props="defaultProps"> </lx-tree> <div class="buttons"> <lx-button @click="getCheckedNodes">Récupération par noeud</lx-button> <lx-button @click="getCheckedKeys">Récupération par clé</lx-button> <lx-button @click="setCheckedNodes">Sélection par noeud</lx-button> <lx-button @click="setCheckedKeys">Sélection par clé</lx-button> <lx-button @click="resetChecked">Reset</lx-button> </div> <script> export default { methods: { getCheckedNodes() { console.log(this.$refs.tree.getCheckedNodes()); }, getCheckedKeys() { console.log(this.$refs.tree.getCheckedKeys()); }, setCheckedNodes() { this.$refs.tree.setCheckedNodes([{ id: 5, label: 'Niveau deux 2-1' }, { id: 9, label: 'Niveau trois 1-1-1' }]); }, setCheckedKeys() { this.$refs.tree.setCheckedKeys([3]); }, resetChecked() { this.$refs.tree.setCheckedKeys([]); } }, data() { return { data: [{ id: 1, label: 'Niveau un 1', children: [{ id: 4, label: 'Niveau deux 1-1', children: [{ id: 9, label: 'Niveau trois 1-1-1' }, { id: 10, label: 'Niveau trois 1-1-2' }] }] }, { id: 2, label: 'Niveau un 2', children: [{ id: 5, label: 'Niveau deux 2-1' }, { id: 6, label: 'Niveau deux 2-2' }] }, { id: 3, label: 'Niveau un 3', children: [{ id: 7, label: 'Niveau deux 3-1' }, { id: 8, label: 'Niveau deux 3-2' }] }], defaultProps: { children: 'children', label: 'label' } }; } }; </script> ``` ::: ### Contenu personnalisé Le contenu des noeuds peut être personnalisé, afin de pouvoir ajouter des icônes ou des boutons par exemple. :::demo Il existe deux méthodes de personnalisation: `render-content` et les slots avec portée. Utilisez `render-content` pour assigner une fonction de rendu qui va générer le contenu des noeuds. Voire la documentation de Vue pour plus d'informations. Si vous préférez les slots, vous aurez accès à `node` et `data` dans le scope, corerspondant à l'objet TreeNode et aux données du noeud courant. Notez que la démo de `render-content` ne marche pas dans jsfiddle car il ne supporte pas JSX. Dans un vrai projet, `render-content` marchera si les dépendances sont satisfaites. ```html <div class="custom-tree-container"> <div class="block"> <p>Avec render-content</p> <lx-tree :data="data" show-checkbox node-key="id" default-expand-all :expand-on-click-node="false" :render-content="renderContent"> </lx-tree> </div> <div class="block"> <p>Avec un slot</p> <lx-tree :data="data" show-checkbox node-key="id" default-expand-all :expand-on-click-node="false"> <template #default="{ node, data }"> <span class="custom-tree-node"> <span>{{ node.label }}</span> <span> <a @click="append(data)"> Append </a> <a @click="remove(node, data)"> Delete </a> </span> </span> </template> </lx-tree> </div> </div> <script> let id = 1000; export default { data() { const data = [{ id: 1, label: 'Niveau un 1', children: [{ id: 4, label: 'Niveau deux 1-1', children: [{ id: 9, label: 'Niveau trois 1-1-1' }, { id: 10, label: 'Niveau trois 1-1-2' }] }] }, { id: 2, label: 'Niveau un 2', children: [{ id: 5, label: 'Niveau deux 2-1' }, { id: 6, label: 'Niveau deux 2-2' }] }, { id: 3, label: 'Niveau un 3', children: [{ id: 7, label: 'Niveau deux 3-1' }, { id: 8, label: 'Niveau deux 3-2' }] }]; return { data: JSON.parse(JSON.stringify(data)), } }, methods: { append(data) { const newChild = { id: id++, label: 'testtest', children: [] }; if (!data.children) { data.children = [] } data.children.push(newChild); this.data = [...this.data] }, remove(node, data) { const parent = node.parent; const children = parent.data.children || parent.data; const index = children.findIndex(d => d.id === data.id); children.splice(index, 1); this.data = [...this.data] }, renderContent(h, { node, data, store }) { return h("span", { class: "custom-tree-node" }, h("span", null, node.label), h("span", null, h("a", { onClick: () => this.append(data) }, "Append "), h("a", { onClick: () => this.remove(node, data) }, "Delete"))); } } }; </script> <style> .custom-tree-node { flex: 1; display: flex; align-items: center; justify-content: space-between; font-size: 14px; padding-right: 8px; } </style> ``` ::: ### Filtrage Les noeuds peuvent être filtrés par mot-clé. :::demo Utilisez la méthode `filter` de l'instance de Tree pour pouvoir filtrer les noeuds, son paramètre étant le mot-clé. Notez que pour que cela fonctionne, `filter-node-method` est requis, sa valeur étant la méthode de filtrage. ```html <lx-input placeholder="Filter keyword" v-model="filterText"> </lx-input> <lx-tree class="filter-tree" :data="data" :props="defaultProps" default-expand-all :filter-node-method="filterNode" ref="tree"> </lx-tree> <script> export default { watch: { filterText(val) { this.$refs.tree.filter(val); } }, methods: { filterNode(value, data) { if (!value) return true; return data.label.indexOf(value) !== -1; } }, data() { return { filterText: '', data: [{ id: 1, label: 'Niveau un 1', children: [{ id: 4, label: 'Niveau deux 1-1', children: [{ id: 9, label: 'Niveau trois 1-1-1' }, { id: 10, label: 'Niveau trois 1-1-2' }] }] }, { id: 2, label: 'Niveau un 2', children: [{ id: 5, label: 'Niveau deux 2-1' }, { id: 6, label: 'Niveau deux 2-2' }] }, { id: 3, label: 'Niveau un 3', children: [{ id: 7, label: 'Niveau deux 3-1' }, { id: 8, label: 'Niveau deux 3-2' }] }], defaultProps: { children: 'children', label: 'label' } }; } }; </script> ``` ::: ### Accordéon Vous pouvez utiliser un mode accordéon afin que seul un noeud par niveau soit ouvert. :::demo ```html <lx-tree :data="data" :props="defaultProps" accordion @node-click="handleNodeClick"> </lx-tree> <script> export default { data() { return { data: [{ label: 'Niveau un 1', children: [{ label: 'Niveau deux 1-1', children: [{ label: 'Niveau trois 1-1-1' }] }] }, { label: 'Niveau un 2', children: [{ label: 'Niveau deux 2-1', children: [{ label: 'Niveau trois 2-1-1' }] }, { label: 'Niveau deux 2-2', children: [{ label: 'Niveau trois 2-2-1' }] }] }, { label: 'Niveau un 3', children: [{ label: 'Niveau deux 3-1', children: [{ label: 'Niveau trois 3-1-1' }] }, { label: 'Niveau deux 3-2', children: [{ label: 'Niveau trois 3-2-1' }] }] }], defaultProps: { children: 'children', label: 'label' } }; }, methods: { handleNodeClick(data) { console.log(data); } } }; </script> ``` ::: ### Noeuds déplaçables Vous pouvez déplacer les noeuds par drag'n drop en ajoutant l'attribut `draggable`. :::demo ```html <lx-tree :data="data" node-key="id" default-expand-all @node-drag-start="handleDragStart" @node-drag-enter="handleDragEnter" @node-drag-leave="handleDragLeave" @node-drag-over="handleDragOver" @node-drag-end="handleDragEnd" @node-drop="handleDrop" draggable :allow-drop="allowDrop" :allow-drag="allowDrag"> </lx-tree> <script> export default { data() { return { data: [{ label: 'Niveau un 1', children: [{ label: 'Niveau deux 1-1', children: [{ label: 'Niveau trois 1-1-1' }] }] }, { label: 'Niveau un 2', children: [{ label: 'Niveau deux 2-1', children: [{ label: 'Niveau trois 2-1-1' }] }, { label: 'Niveau deux 2-2', children: [{ label: 'Niveau trois 2-2-1' }] }] }, { label: 'Niveau un 3', children: [{ label: 'Niveau deux 3-1', children: [{ label: 'Niveau trois 3-1-1' }] }, { label: 'Niveau deux 3-2', children: [{ label: 'Niveau trois 3-2-1' }] }] }], defaultProps: { children: 'children', label: 'label' } }; }, methods: { handleDragStart(node, ev) { console.log('drag start', node); }, handleDragEnter(draggingNode, dropNode, ev) { console.log('tree drag enter: ', dropNode.label); }, handleDragLeave(draggingNode, dropNode, ev) { console.log('tree drag leave: ', dropNode.label); }, handleDragOver(draggingNode, dropNode, ev) { console.log('tree drag over: ', dropNode.label); }, handleDragEnd(draggingNode, dropNode, dropType, ev) { console.log('tree drag end: ', dropNode && dropNode.label, dropType); }, handleDrop(draggingNode, dropNode, dropType, ev) { console.log('tree drop: ', dropNode.label, dropType); }, allowDrop(draggingNode, dropNode, type) { if (dropNode.data.label === 'Niveau deux 3-1') { return type !== 'inner'; } else { return true; } }, allowDrag(draggingNode) { return draggingNode.data.label.indexOf('Niveau trois 3-1-1') === -1; } } }; </script> ``` ::: ### Attributs | Attribut | Description | Type | Valeurs acceptées | Défaut | | --------------------- | ---------------------------------------- | --------------------------- | --------------- | ------- | | data | Données de l'arbre | array | — | — | | empty-text | Texte à afficher quand il n'y a pas de données. | string | — | — | | node-key | Identifiant unique pour chaque noeud, doit être unique dans tout l'arbre. | string | — | — | | props | Options de configuration, voir table suivante. | object | — | — | | render-after-expand | Si les noeuds enfants doivent être générés seulement après la première ouverture du parent. | boolean | — | true | | load | Méthode pour charger les noeuds enfants, uniquement en mode `lazy`. | function(node, resolve) | — | — | | render-content | Fonction de rendu pour les noeuds. | Function(h, { node, data, store }) | — | — | | highlight-current | Si le noeud courant est mis en valeur. | boolean | — | false | | default-expand-all | Si tous les noeuds sont ouverts par défaut. | boolean | — | false | | expand-on-click-node | Si l'ouverture se fait aussi en cliquant sur le noeud. Si `false`, l'ouverture ne se fera qu'en cliquant sur l'icône. | boolean | — | true | | check-on-click-node | Si la sélection se fait aussi en cliquant sur le noeud. Si `false`, la sélection ne se fera qu'en cliquant sur la checkbox. | boolean | — | false | | auto-expand-parent | Si un noeud parent est automatiquement ouvert quand un noeud enfant s'ouvre. | boolean | — | true | | default-expanded-keys | Tableau des clés des noeuds initialement ouverts. | array | — | — | | show-checkbox | Si un noeud est sélectionnable. | boolean | — | false | | check-strictly | Si la sélection d'un noeud affecte celle de son parent quand `show-checkbox` est `true`. | boolean | — | false | | default-checked-keys | Tableau des clés des noeuds initialement sélectionnés. | array | — | — | | current-node-key | Clé du noeud initialement sélectionné. | string, number | — | — | | filter-node-method | Fonction exécutée sur chaque noeud pour le filtrage. Si elle retourne `false`, les noeuds seront cachés. | Function(value, data, node) | — | — | | accordion | Si les noeuds fonctionnent en mode accordéon. | boolean | — | false | | indent | Indentation horizontale des noeuds en px. | number | — | 16 | | icon-class | Icône pour chaque noeud. | string | - | - | | lazy | Si les noeuds sont chargés en mode lazy, utilisé avec l'attribut `load`. | boolean | — | false | | draggable | Si les noeuds sont déplaçables par drag'n drop. | boolean | — | false | | allow-drag | Fonction exécutée avant le déplacement d'un noeud. Si `false` est retourné, le noeud ne sera pas déplaçable. | Function(node) | — | — | | allow-drop | Fonction exécutée avant le placement d'un noeud. Si `false` est retourné, le noeud ne pourra être placé sur la zone en question. `type` a trois valeurs possibles: 'prev' (insertion avant le noeud cible), 'inner' (insertion dans le noeud cible) and 'next' (insertion après le noeud cible). | Function(draggingNode, dropNode, type) | — | — | ### props | Attribut | Description | Type | Valeurs acceptées | Défaut | | --------- | ---------------------------------------- | ------ | --------------- | ------- | | label | Détermine quelle clé de l'objet noeud représente le label. | string, function(data, node) | — | — | | children | Détermine quelle clé de l'objet noeud représente les noeuds enfants. | string | — | — | | disabled | Détermine quelle clé de l'objet noeud représente la désactivation du noeud. | boolean, function(data, node) | — | — | | isLeaf | Détermine si le noeud est une feuille, ne marche qu'avec le mode lazy loading. | boolean, function(data, node) | — | — | ### Méthodes `Tree` possède les méthodes suivantes, qui retourne la sélection de noeuds actuelle. | Méthode | Description | Paramètres | | --------------- | ---------------------------------------- | ---------------------------------------- | | filter | Filtre les noeuds. | Accepte un paramètre qui sera le premier paramètre de `filter-node-method`. | | updateKeyChildren | Ajoute de nouvelles données au noeud, ne marche que lorsque `node-key` est assigné. | (key, data) Accepte deux paramètres: 1. clé du noeud 2. nouvelles données. | | getCheckedNodes | Si le noeud peut-être sélectionné (`show-checkbox` est `true`), il retourne un tableau des noeuds sélectionnés. | (leafOnly, includeHalfChecked) Accepte deux booléen: 1. Défaut à `false`. Si `true`, retourne seulement un tableau des sous-noeuds sélectionnés. 2. Défaut à `false`. Si `true`, retourne la moitié des noeuds sélectionnés. | | setCheckedNodes | Détermine quels noeuds sont sélectionnés, ne marche que si `node_key` est assigné. | Un tableau de noeuds qui doivent être sélectionnés. | | getCheckedKeys | Si le noeud peut être sélectionné (`show-checkbox` est `true`), retourne un tableau de clés des noeuds sélectionnés. | (leafOnly) Booléen, défaut à `false`. Si à `true`, Il retourne seulement un tableau des sous-noeuds sélectionnés. | | setCheckedKeys | Détermine quels noeuds sont sélectionnés, ne marche que si `node_key` est assigné. | (keys, leafOnly) Accepte deux paramètres: 1. un tableau de clés de noeuds à sélectionner 2. un booléen avec pour défaut `false`. Si à `true`, Il retourne seulement un tableau des sous-noeuds sélectionnés. | | setChecked | Détermine si un noeud est sélectionnable, ne marche que si `node_key` est assigné. | (key/data, checked, deep) Accepte trois paramètres: 1. La clé ou les données du noeud 2. un booléen indiquant si sélectionné. 3. un booléen indiquant si profond. | | getHalfCheckedNodes | Si le noeud peut être sélectionné (`show-checkbox` est `true`), retourne la moitié des noeuds sélectionnés. | - | | getHalfCheckedKeys | Si le noeud peut être sélectionné (`show-checkbox` est `true`), retourne les clés de la moitié des noeuds sélectionnés. | - | | getCurrentKey | retourne la clé du noeud actuellement en valeur (`null` si aucun noeud n'est en valeur). | — | | getCurrentNode | retourne les données du noeud actuellement en valeur (`null` si aucun noeud n'est en valeur). | — | | setCurrentKey | Met un noeud en valeur par sa clé, ne marche que si `node_key` est assigné. | (key, shouldAutoExpandParent=true) 1. la clé du noeud. Si `null`, annule la sélection actuelle. 2. whether to automatically expand parent node | | setCurrentNode | Met un noeud en valeur, ne marche que si `node_key` est assigné. | (node, shouldAutoExpandParent=true) 1. le noeud. 2. whether to automatically expand parent node | | getNode | Retourne le noeud grâce à sa clé ou ses données. | (data) la clé ou les données du noeud. | | remove | Supprime un noeud, ne marche que si node-key est assigné. | (data) le noeud ou ses données à supprimer. | | append | Ajoute un noeud à un autre noeud. | (data, parentNode) 1. les données du noeud à ajouter 2. les données du parent, clé ou données. | | insertBefore | Insère un noeud avant un autre noeud. | (data, refNode) 1. Les données du noeud à insérer 2. Clé ou noeud de référence. | | insertAfter | Insère un noeud après un autre noeud. | (data, refNode) 1. Les données du noeud à insérer 2. Clé ou noeud de référence. | ### Évènements | Nom | Description | Paramètres | | -------------- | ---------------------------------------- | ---------------------------------------- | | node-click | Se déclenche quand est cliqué. | Le noeud cliqué, la propriété `node` de TreeNode, TreeNode lui-même. | | node-contextmenu | Se déclenche quand un noeud reçoit un clic droit. | L'évènement, le noeud cliqué, la propriété `node` de TreeNode, TreeNode lui-même. | | check-change | Se déclenche quand quand la sélection d'un noeud change. | Le noeud modifié, si le noeud est sélectionné, si des enfants sont sélectionnés. | | check | Se déclenche après un clic sur le checkbox. | Le noeud modifié, l'objet statut de l'arbre avec quatre propriétés: checkedNodes, checkedKeys, halfCheckedNodes, halfCheckedKeys. | | current-change | Se déclenche quand le noeud courant changes. | Le noeud courant, la propriété `node` de TreeNode | | node-expand | Se déclenche quand le noeud courant s'ouvre. | Le noeud ouvert, la propriété `node` de TreeNode, TreeNode lui-même. | | node-collapse | Se déclenche quand le noeud courant se ferme. | Le noeud fermé, la propriété `node` de TreeNode, TreeNode lui-même. | | node-drag-start | Se déclenche quand le déplacement commence. | Le noeud déplacé, l'évènement. | | node-drag-enter | Se déclenche quand le noeud déplacé entre dans un autre noeud. | Le noeud déplacé, l'autre noeud, l'évènement. | | node-drag-leave | Se déclenche quand le noeud déplacé quitte un autre noeud. | Le noeud déplacé, l'autre noeud, l'évènement. | | node-drag-over | Se déclenche quand le noeud passe au-dessus d'un autre noeud (comme l'évènement mouseover). | Le noeud déplacé, l'autre noeud, l'évènement. | | node-drag-end | Se déclenche quand le déplacement se termine. | Le noeud déplacé, le noeud d'arrivée (peut-être `undefined`), le type de placement (before / after / inner), l'évènement. | | node-drop | Se déclenche après que le noeud déplacé soit placé. | Le noeud déplacé, le noeud d'arrivée, le type de placement (before / after / inner), l'évènement. | ### Slot avec portée | Nom | Description | |------|--------| | — | Le contenu personnalisé des noeuds. les paramètres sont { node, data }. |

33.395189

575

0.521884

fra_Latn

0.806698

d0d2eed009d9d808d9b9b4a5d2757d4d98f21e1e

23

md

Markdown

README.md

anjones1000/anjones1000.github.io

76993b7d721bfaa0d2ab96c7939e1c7ee286f46a

[ "MIT" ]

null

README.md

anjones1000/anjones1000.github.io

76993b7d721bfaa0d2ab96c7939e1c7ee286f46a

[ "MIT" ]

null

README.md

anjones1000/anjones1000.github.io

76993b7d721bfaa0d2ab96c7939e1c7ee286f46a

[ "MIT" ]

null

# anjones1000.github.io

23

0.826087

swe_Latn

0.188289

d0d44998b8b95d7e602b67933ca601019919c0e9

92

md

Markdown

README.md

bytemaster-0xff/DroneTek

9b88b30e7d442833b8bab3302d93dc6463d67619

[ "MIT" ]

null

README.md

bytemaster-0xff/DroneTek

9b88b30e7d442833b8bab3302d93dc6463d67619

[ "MIT" ]

null

README.md

bytemaster-0xff/DroneTek

9b88b30e7d442833b8bab3302d93dc6463d67619

[ "MIT" ]

null

# DroneTek Collection of software, hardware and design resources for the Nivek Drone Family

30.666667

80

0.826087

eng_Latn

0.976117

d0d44c87f99b152523e9d72c93b40222ad830786

6,309

md

Markdown

docs-archive-a/2014/database-engine/availability-groups/windows/transact-sql-statements-for-always-on-availability-groups.md

v-alji/sql-docs-archive-pr.es-es

410a49b0a08c22fd4bc973078b563238d69c8b44

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

1

2021-11-25T21:09:51.000Z

docs-archive-a/2014/database-engine/availability-groups/windows/transact-sql-statements-for-always-on-availability-groups.md

v-alji/sql-docs-archive-pr.es-es

410a49b0a08c22fd4bc973078b563238d69c8b44

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

1

2021-11-25T02:22:05.000Z

2021-11-25T02:27:15.000Z

docs-archive-a/2014/database-engine/availability-groups/windows/transact-sql-statements-for-always-on-availability-groups.md

v-alji/sql-docs-archive-pr.es-es

410a49b0a08c22fd4bc973078b563238d69c8b44

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

1

2021-09-29T08:53:04.000Z

--- title: Información general sobre las instrucciones Transact-SQL para Grupos de disponibilidad AlwaysOn (SQL Server) | Microsoft Docs ms.custom: '' ms.date: 04/27/2017 ms.prod: sql-server-2014 ms.reviewer: '' ms.technology: high-availability ms.topic: conceptual helpviewer_keywords: - Availability Groups [SQL Server], about - Availability Groups [SQL Server], Transact-SQL statements ms.assetid: 184d0a81-2259-4db9-9d0d-01aac0b502c8 author: MashaMSFT ms.author: mathoma ms.openlocfilehash: ff25fecf54cfdd1d9c03d1586f0272896542bfa7 ms.sourcegitcommit: ad4d92dce894592a259721a1571b1d8736abacdb ms.translationtype: MT ms.contentlocale: es-ES ms.lasthandoff: 08/04/2020 ms.locfileid: "87750185" --- # <a name="overview-of-transact-sql-statements-for-alwayson-availability-groups-sql-server"></a>Información general sobre instrucciones Transact-SQL para grupos de disponibilidad de AlwaysOn (SQL Server) En este tema se presentan las instrucciones [!INCLUDE[tsql](../../../includes/tsql-md.md)] que admiten la implementación de [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] y la creación y administración de un grupo de disponibilidad, réplica de disponibilidad y base de datos de disponibilidad dados. ## <a name="create-endpoint"></a><a name="CreateEndpoint"></a>CREAR PUNTO DE CONEXIÓN [crear punto de conexión... POR DATABASE_MIRRORING](/sql/t-sql/statements/create-endpoint-transact-sql) crea un extremo de creación de reflejo de la base de datos, si no existe ninguno en la instancia del servidor. Cada instancia de servidor en el que vaya a implementar [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] o la creación de reflejo de la base de datos requiere un extremo de creación de reflejo de la base de datos. Ejecute esta instrucción en la instancia de servidor en la que se va a crear el extremo. Puede crear solo un extremo de creación de reflejo de la base de datos en una instancia de servidor determinada. Para obtener más información, vea [El punto de conexión de creación de reflejo de la base de datos (SQL Server)](../../database-mirroring/the-database-mirroring-endpoint-sql-server.md). ## <a name="create-availability-group"></a><a name="CreateAG"></a>CREAR GRUPO DE DISPONIBILIDAD [CREATE AVAILABILITY GROUP](/sql/t-sql/statements/create-availability-group-transact-sql) crea un nuevo grupo de disponibilidad y, opcionalmente, una escucha del grupo de disponibilidad. Como mínimo, debe especificar la instancia del servidor local, que se convertirá en la réplica principal inicial. Opcionalmente, puede especificar también hasta cuatro réplicas secundarias. Ejecute CREATE AVAILABILITY GROUP en la instancia de [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] en la que desea hospedar la réplica principal inicial del nuevo grupo de disponibilidad. Esta instancia de servidor debe residir en un nodo de un clúster de conmutación por error de Windows Server (WSFC) (para obtener más información, vea [requisitos previos, restricciones y recomendaciones para Grupos de disponibilidad AlwaysOn (SQL Server)](prereqs-restrictions-recommendations-always-on-availability.md). ## <a name="alter-availability-group"></a><a name="AlterAG"></a>ALTER AVAILABILITY GROUP [ALTER AVAILABILITY GROUP](/sql/t-sql/statements/alter-availability-group-transact-sql) admite el cambio de un grupo de disponibilidad existente o una escucha de grupo de disponibilidad y la conmutación por error en un grupo de disponibilidad. Ejecute ALTER AVAILABILITY GROUP en la instancia de [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] que hospeda la réplica principal actual. ## <a name="alter-database--set-hadr-"></a><a name="AlterDb"></a>ALTER DATABASE... ESTABLECER HADR... Las opciones de la cláusula [SET HADR](/sql/t-sql/statements/alter-database-transact-sql-set-hadr) de la instrucción ALTER DATABASE permiten combinar una base de datos secundaria con el grupo de disponibilidad de la base de datos principal correspondiente, quitar una base de datos combinada y suspender la sincronización de datos en una base de datos combinada, y reanudar la sincronización de datos. ## <a name="drop-availability-group"></a><a name="DropAG"></a>QUITAR GRUPO DE DISPONIBILIDAD [DROP AVAILABILITY GROUP](/sql/t-sql/statements/drop-availability-group-transact-sql) quita un grupo de disponibilidad especificado y todas sus réplicas. DROP AVAILABILITY GROUP se puede ejecutar desde cualquier nodo de [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] del clúster de conmutación por error de WSFC. ## <a name="restrictions-on-the-availability-group-transact-sql-statements"></a><a name="Restrictions"></a>Restricciones en las instrucciones de Transact-SQL de grupo de disponibilidad Las instrucciones CREATE AVAILABILITY GROUP, ALTER AVAILABILITY GROUP y DROP AVAILABILITY GROUP de [!INCLUDE[tsql](../../../includes/tsql-md.md)] tienen las siguientes restricciones: - Excepto en DROP AVAILABILITY GROUP, la ejecución de estas instrucciones requiere que el servicio HADR esté habilitado en la instancia de [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]. Para obtener más información, vea [Habilitar y deshabilitar grupos de disponibilidad AlwaysOn (SQL Server)](enable-and-disable-always-on-availability-groups-sql-server.md). - Estas instrucciones no se pueden ejecutar en transacciones o por lotes. - Aunque llevan a cabo el máximo de acciones para efectuar la limpieza después de un error, estas instrucciones no garantizan que revertirán todos los cambios al producirse un error. No obstante, los sistemas se deben controlar correctamente y, a continuación, ignorar los errores parciales. - Estas instrucciones no admiten expresiones o variables. - Si se ejecuta una instrucción de [!INCLUDE[tsql](../../../includes/tsql-md.md)] mientras está en curso otra acción o recuperación de grupo de disponibilidad, la instrucción devuelve un error. Espere a que se complete la acción o la recuperación, e intente de nuevo la instrucción, si es necesario. ## <a name="see-also"></a>Consulte también [Información general de Grupos de disponibilidad AlwaysOn (SQL Server)](overview-of-always-on-availability-groups-sql-server.md)

98.578125

534

0.774925

spa_Latn

0.926269

d0d4d51b08554546426d91e0a31d84a05d8b2aa7

3,233

md

Markdown

docs/ado/guide/remote-data-service/system-requirements-for-the-address-book-application.md

in4matica/sql-docs.de-de

b5a6c26b66f347686c4943dc8307b3b1deedbe7e

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

null

docs/ado/guide/remote-data-service/system-requirements-for-the-address-book-application.md

in4matica/sql-docs.de-de

b5a6c26b66f347686c4943dc8307b3b1deedbe7e

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

null

docs/ado/guide/remote-data-service/system-requirements-for-the-address-book-application.md

in4matica/sql-docs.de-de

b5a6c26b66f347686c4943dc8307b3b1deedbe7e

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

null

--- title: System Anforderungen für die Adressbuch Anwendung | Microsoft-Dokumentation ms.prod: sql ms.prod_service: connectivity ms.technology: connectivity ms.custom: '' ms.date: 11/09/2018 ms.reviewer: '' ms.topic: conceptual helpviewer_keywords: - address book application scenario [ADO] - RDS scenarios [ADO] ms.assetid: da385405-1c9a-478b-9bf6-fba70015324c author: MightyPen ms.author: genemi ms.openlocfilehash: 2450cc97229a6629d4c2895f3960e3033d129789 ms.sourcegitcommit: b87d36c46b39af8b929ad94ec707dee8800950f5 ms.translationtype: MT ms.contentlocale: de-DE ms.lasthandoff: 02/08/2020 ms.locfileid: "67922039" --- # <a name="system-requirements-for-the-address-book-application"></a>Systemanforderungen für die Adress Book-Anwendung Zum Einrichten der Address Book-Beispielanwendung müssen Sie die folgenden Software-und Datenbankanforderungen erfüllen: > [!IMPORTANT] > Ab Windows 8 und Windows Server 2012 sind RDS-Server Komponenten nicht mehr im Windows-Betriebssystem enthalten (weitere Details finden Sie unter Windows 8 und [Windows Server 2012 Compatibility Cookbook](https://www.microsoft.com/download/details.aspx?id=27416) ). RDS-Client Komponenten werden in einer zukünftigen Version von Windows entfernt. Nutzen Sie diese Funktionen bei Neuentwicklungen nicht mehr, und planen Sie die Änderung von Anwendungen, die diese Funktion zurzeit verwenden. Anwendungen, die RDS verwenden, sollten zu [WCF Data Service](https://go.microsoft.com/fwlink/?LinkId=199565)migriert werden. ## <a name="software-requirements"></a>Softwareanforderungen Die Softwareanforderungen für den Server Computer zum Ausführen dieser Webanwendung umfassen Folgendes: - Microsoft Windows NT® Server 4,0, mit Service Pack 3 oder höher oder Microsoft Windows® 2000 Server. - Microsoft Internetinformationsdienste (IIS), Version 3,0 oder höher, mit Active Server Seiten. Die Softwareanforderungen für den Client Computer für die Ausführung dieser Webanwendung umfassen Folgendes: - Microsoft Internet Explorer 4,0 oder höher. - Microsoft Windows NT 4,0 Workstation oder Server, Windows 2000 oder Microsoft Windows 98. ## <a name="database-requirements"></a>Datenbankanforderungen Um dieses Beispiel verwenden zu können, benötigen Sie Folgendes: - Eine operative Microsoft® SQL Server Version 6,5 oder höher. - Berechtigungen zum Erstellen der Datenbank und Auffüllen der Datenbank mit den Beispiel Daten. - Überprüfung der gefüllten Daten über Enterprise Manager oder die isql-Hilfsprogramme (in SQL Server 7,0) als Query Analyzer bezeichnet. Wenn Sie nicht über Berechtigungen verfügen, muss der Datenbankadministrator möglicherweise das System einrichten und ihnen Zugriffsberechtigungen für die Datenbank erteilen oder die Datenbank für Sie einrichten. ## <a name="see-also"></a>Weitere Informationen [Ausführen des Adressbuch-SQL-Skripts](../../../ado/guide/remote-data-service/running-the-address-book-sql-script.md) [DataControl-Objekt (RDS)](../../../ado/reference/rds-api/datacontrol-object-rds.md) [Ausführen der Adress Book-Beispielanwendung](../../../ado/guide/remote-data-service/running-the-address-book-sample-application.md)

54.79661

621

0.786885

deu_Latn

0.938702

d0d4d774dac3e598df59073bc5142bd8a9570821

271

md

Markdown

README.md

electric-feel/localbike

22c557fa03f690c6a42dd33031d3d2fb3e2e58db

[ "MIT" ]

1

2018-04-16T02:54:07.000Z

README.md

electric-feel/localbike

22c557fa03f690c6a42dd33031d3d2fb3e2e58db

[ "MIT" ]

null

README.md

electric-feel/localbike

22c557fa03f690c6a42dd33031d3d2fb3e2e58db

[ "MIT" ]

null

localbike ========= Free Crowd-Sourced Bike Sharing ## Links * <http://mongoosejs.com/docs/index.html> * <https://devcenter.heroku.com/articles/nodejs-mongoose> * <http://pixelhandler.com/blog/2012/02/09/develop-a-restful-api-using-node-js-with-express-and-mongoose/>

24.636364

106

0.730627

yue_Hant

0.515555

d0d57a04d5b45e7952efdf876185e0415630af5c

863

md

Markdown

README.md

rupak10987/Shaders

63d38f80805d4f765524779aca4868f6d9ea2880

[ "MIT" ]

null

README.md

rupak10987/Shaders

63d38f80805d4f765524779aca4868f6d9ea2880

[ "MIT" ]

null

README.md

rupak10987/Shaders

63d38f80805d4f765524779aca4868f6d9ea2880

[ "MIT" ]

1

2022-03-23T23:49:49.000Z

# Shaders In this repository I put some GLSL Shader codes, which I learnt throughout the opengl course. <h1><b>Overview</b></h1> ![procedural varooni](https://user-images.githubusercontent.com/83497932/118073538-d8173800-b3cd-11eb-9c92-250f1d6dcd2f.png) ![noise](https://user-images.githubusercontent.com/83497932/118073572-ec5b3500-b3cd-11eb-82db-baa543821ff3.png) ![flora_shader](https://user-images.githubusercontent.com/83497932/118073637-0a289a00-b3ce-11eb-9702-5d4e79564811.png)![fractal](https://user-images.githubusercontent.com/83497932/120026665-39691900-c014-11eb-92b5-ae96f8b791bd.png) <h1><b>Instructions</b></h1> These codes can run on Visual Studio Codes with the "GLSL-CANVAS" and "GLSL Shader Support" extensions enabled. The easy way is to run the code in online glsl editor. link down below. https://thebookofshaders.com/edit.php

41.095238

468

0.78679

eng_Latn

0.294371

d0d5a92a2301f419817546d6687b3c68c136bc5c

890

md

Markdown

README.md

bartvanbenthem/gofound-restfull

e1aba9cbf3741d466a66b50fa95af0a4bdfed6ae

[ "MIT" ]

null

README.md

bartvanbenthem/gofound-restfull

e1aba9cbf3741d466a66b50fa95af0a4bdfed6ae

[ "MIT" ]

null

README.md

bartvanbenthem/gofound-restfull

e1aba9cbf3741d466a66b50fa95af0a4bdfed6ae

[ "MIT" ]

null

# gofound-restful Project template for creating an RESTful webservice in Go, with relational database backend and example content. ### Used packages * github.com/go-chi/chi * github.com/jackc/pgconn * github.com/jackc/pgx/v4 * github.com/dgrijalva/jwt-go * golang.org/x/crypto ## Prerequisites Run db script to install, configure and start PostgreSQL, when the database is started this scrpt creates the database and inserts data from the go_software.sql configuration file. ```shell $ sudo ./build/scripts/db/install-postgresql.sh ``` Test the repository ``` shell $ go test -v -cover ./... ``` ## Start the API Server ```shell $ ./build/bin/server ``` ```bash 2021/01/01 00:00:00 Connecting to database... 2021/01/01 00:00:00 Connected to database 2021/01/01 00:00:00 Starting server on port 4000 ``` ### Simulate client-side behaviour ```shell $ ./build/client-test/client-test ```

25.428571

180

0.738202

eng_Latn

0.871992

d0d5eb79d90885e9afba9b52f95b23823ed912da

15,904

md

Markdown

articles/storage/blobs/storage-quickstart-blobs-javascript-client-libraries.md

Ksantacr/azure-docs.es-es

d3abf102433fd952aafab2c57a55973ea05a9acb

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

null

articles/storage/blobs/storage-quickstart-blobs-javascript-client-libraries.md

Ksantacr/azure-docs.es-es

d3abf102433fd952aafab2c57a55973ea05a9acb

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

null

articles/storage/blobs/storage-quickstart-blobs-javascript-client-libraries.md

Ksantacr/azure-docs.es-es

d3abf102433fd952aafab2c57a55973ea05a9acb

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

null

--- title: 'Guía de inicio rápido de Azure: Creación de un blob en el almacenamiento de objetos mediante JavaScript y HTML en el explorador' description: Aprenda a usar una instancia de BlobService para cargar, enumerar y eliminar blobs con JavaScript en una página HTML. services: storage keywords: storage, javascript, html author: mhopkins-msft ms.custom: mvc ms.service: storage ms.author: mhopkins ms.reviewer: seguler ms.date: 11/14/2018 ms.topic: quickstart ms.subservice: blobs ms.openlocfilehash: df697ab31875c8f806456c1e60820e7e8d752539 ms.sourcegitcommit: f6ba5c5a4b1ec4e35c41a4e799fb669ad5099522 ms.translationtype: HT ms.contentlocale: es-ES ms.lasthandoff: 05/06/2019 ms.locfileid: "65149574" ---  # <a name="quickstart-upload-list-and-delete-blobs-using-javascripthtml-in-the-browser"></a>Inicio rápido: Carga, enumeración y eliminación de blobs con JavaScript y HTML en el explorador En esta guía de inicio rápido se muestra cómo administrar blobs a partir de código que se ejecuta completamente en el explorador. El enfoque aquí usado muestra cómo utilizar las medidas de seguridad necesarias para garantizar el acceso protegido a su cuenta de Blob Storage. Para completar esta guía de inicio rápido, necesitará una [suscripción de Azure](https://azure.microsoft.com/free/?WT.mc_id=A261C142F). ## <a name="prerequisites"></a>Requisitos previos [!INCLUDE [storage-quickstart-prereq-include](../../../includes/storage-quickstart-prereq-include.md)] ## <a name="setting-up-storage-account-cors-rules"></a>Configuración de reglas de CORS de cuenta de almacenamiento Para que la aplicación web pueda tener acceso a un almacenamiento de blobs desde el cliente, la cuenta debe configurarse para habilitar el [uso compartido de recursos entre orígenes](https://docs.microsoft.com/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services), o CORS. Vuelva a Azure Portal y seleccione la cuenta de almacenamiento. Para definir una nueva regla de CORS, vuelva a la sección **Configuración** y haga clic en el vínculo **CORS**. A continuación, haga clic en el botón **Agregar** para abrir la ventana **Agregar regla de CORS**. En esta guía de inicio rápido, se crea una regla de CORS abierta: ![Configuración de CORS de la cuenta de Azure Blob Storage](media/storage-quickstart-blobs-javascript-client-libraries/azure-blob-storage-cors-settings.png) En la tabla siguiente se describe cada opción de configuración de CORS y se explican los valores que se utilizan para definir la regla. |Configuración |Valor | DESCRIPCIÓN | |---------|---------|---------| | Orígenes permitidos | * | Acepta una lista delimitada por comas de dominios establecidos como orígenes aceptables. Establecer el valor en `*` permite el acceso de todos los dominios a la cuenta de almacenamiento. | | Verbos permitidos | delete, get, head, merge, post, options y put | Enumera los verbos HTTP permitidos para ejecutar en la cuenta de almacenamiento. Para los fines de esta guía de rápido, seleccione todas las opciones disponibles. | | Encabezados permitidos | * | Define una lista de encabezados de solicitud (incluidos los encabezados con prefijo) permitidos por la cuenta de almacenamiento. Establecer el valor en `*` permite el acceso de todos los encabezados. | | Encabezados expuestos | * | Enumera los encabezados de respuesta permitidos por la cuenta. Establecer el valor en `*` permite que la cuenta envíe cualquier encabezado. | | Antigüedad máxima (segundos) | 86400 | La cantidad máxima de tiempo que el explorador almacena en caché la solicitud OPTIONS preparatoria. El valor *86400* permite que la memoria caché permanezca un día completo. | > [!IMPORTANT] > Asegúrese de que cualquier configuración que utilice en producción exponga la cantidad mínima de acceso necesaria para la cuenta de almacenamiento a fin de mantener un acceso seguro. La configuración de CORS descrita aquí es adecuada para una guía de inicio rápido, ya que define una directiva de seguridad flexible. Sin embargo, esta configuración no se recomienda para un contexto real. A continuación, se usa Azure Cloud Shell para crear un token de seguridad. [!INCLUDE [Open the Azure cloud shell](../../../includes/cloud-shell-try-it.md)] ## <a name="create-a-shared-access-signature"></a>Creación de una firma de acceso compartido La firma de acceso compartido (SAS) es usada por el código que se ejecuta en el explorador para autorizar las solicitudes para Blob Storage. Mediante el uso de una firma de acceso compartido, el cliente puede autorizar el acceso a los recursos de almacenamiento sin la clave de acceso de cuenta ni la cadena de conexión. Para más información, consulte [Uso de firmas de acceso compartido (SAS)](../common/storage-dotnet-shared-access-signature-part-1.md). Puede crear una SAS mediante la CLI de Azure a través de Azure Cloud Shell o con el Explorador de Azure Storage. En la tabla siguiente se describen los parámetros para los que necesita proporcionar valores con el fin de generar una firma de acceso compartido con la CLI. | Parámetro |DESCRIPCIÓN | Marcador de posición | |----------------|-------------|-------------| | *expiry* | La fecha de expiración del token de acceso en formato AAAA-MM-DD. Escriba la fecha de mañana para usarla con este guía de inicio rápido. | *FUTURE_DATE* | | *account-name* | El nombre de la cuenta de almacenamiento. Utilice el nombre que se reservó en un paso anterior. | *YOUR_STORAGE_ACCOUNT_NAME* | | *account-key* | La clave de la cuenta de almacenamiento. Utilice la clave que se reservó en un paso anterior. | *YOUR_STORAGE_ACCOUNT_KEY* | El siguiente script utiliza la CLI de Azure para crear una firma de acceso compartido que puede pasar a un servicio de blob de JavaScript. > [!NOTE] > Para obtener mejores resultados, quite los espacios adicionales entre los parámetros antes de pegar el comando en Azure Cloud Shell. ```bash az storage account generate-sas --permissions racwdl --resource-types sco --services b --expiry FUTURE_DATE --account-name YOUR_STORAGE_ACCOUNT_NAME --account-key YOUR_STORAGE_ACCOUNT_KEY ``` Puede encontrar un poco críptica la serie de valores después de cada parámetro. Los valores de estos parámetros se toman de la primera letra de sus permisos correspondientes. La siguiente tabla explica la procedencia de los valores: | Parámetro | Valor | DESCRIPCIÓN | |------------------|---------|---------| | *permissions* | racwdl | Esta firma de acceso compartido permite *leer*, *anexar*, *crear*, *escribir*, *eliminar* y *enumerar*. | | *resource-types* | sco | Los recursos afectados por las firmas de acceso compartido son *servicio*, *contenedor* y *objeto*. | | *services* | b | El servicio afectado por la firma de acceso compartido es el servicio *blob*. | Ahora que se ha generado la firma de acceso compartido, copie el valor devuelto en la consola en el editor de texto. Usará este valor en un paso posterior. > [!IMPORTANT] > En producción, pase siempre los tokens de SAS mediante SSL. Además, los tokens de SAS deben generarse en el servidor y enviarse a la página HTML para pasarlos de vuelta a Azure Blob Storage. Un enfoque que se puede considerar consiste en utilizar una función sin servidor para generar tokens de SAS. Azure Portal incluye plantillas de función que ofrecen la posibilidad de generar una firma de acceso compartido con una función de JavaScript. ## <a name="implement-the-html-page"></a>Implementación de la página HTML ### <a name="set-up-the-web-application"></a>Configuración de la aplicación web Las bibliotecas de cliente JavaScript de Azure Storage no funcionarán directamente desde el sistema de archivos y deben ser atendidas desde un servidor web. Por lo tanto, en los pasos siguientes se explica cómo usar el servidor web local simple con Node.js. > [!NOTE] > En esta sección se muestra cómo crear un servidor web local que requiere que Node.js esté instalado en la máquina. Si no desea instalar Node.js, puede usar cualquier otro medio para ejecutar un servidor web local. En primer lugar, cree una nueva carpeta para el proyecto y asígnele el nombre *azure-blobs-javascript*. A continuación, abra un símbolo del sistema en la carpeta *azure-blobs-javascript* y escriba el comando siguiente a fin de preparar la aplicación para instalar el módulo de servidor web: ```bash npm init -y ``` Al ejecutar *init*, se agregan los archivos necesarios para instalar un módulo de servidor web. Para instalar el módulo, escriba el comando siguiente: ```bash npm i http-server ``` A continuación, edite el archivo *package.json* y reemplace la definición de *scripts* existente con el siguiente fragmento de código: ```javascript "scripts": { "start": "http-server" } ``` Por último, en el símbolo del sistema, escriba `npm start` para iniciar el servidor web: ```bash npm start ``` ### <a name="get-the-blob-storage-client-library"></a>Obtención de la biblioteca de cliente de Blob Storage [Descargue las bibliotecas de cliente JavaScript](https://aka.ms/downloadazurestoragejs), extraiga el contenido del archivo zip y coloque los archivos de script desde la carpeta *bundle* a una carpeta denominada *scripts*. ### <a name="add-the-client-script-reference-to-the-page"></a>Incorporación de la referencia de script de cliente a la página Cree una página HTML en la raíz de la carpeta *azure-blobs-javascript* y asígnele el nombre *index.html*. Una vez creada la página, agréguele las marcas siguientes. ```html <!DOCTYPE html> <html> <body> <button id="create-button">Create Container</button> <input type="file" id="fileinput" /> <button id="upload-button">Upload</button> <button id="list-button">List</button> <button id="delete-button">Delete</button> </body> <script src="scripts/azure-storage.blob.min.js" charset="utf-8"></script> <script> // Blob-related code goes here </script> </html> ``` Estas marcas agregan lo siguiente a la página: - una referencia a *scripts/azure-storage.blob.js* - botones que se utilizan para crear un contenedor, cargar, enumerar y eliminar blobs - un elemento *INPUT* que se usa para cargar un archivo - un marcador de posición para código específico del almacenamiento ### <a name="create-an-instance-of-blobservice"></a>Creación de una instancia de BlobService El [BlobService](https://azure.github.io/azure-storage-node/BlobService.html) proporciona una interfaz a Azure Blob Storage. Para crear una instancia del servicio, debe proporcionar el nombre de cuenta de almacenamiento y la firma de acceso compartido generados en un paso anterior. ```javascript const account = { name: YOUR_STORAGE_ACCOUNT_NAME, sas: YOUR_SAS }; const blobUri = 'https://' + account.name + '.blob.core.windows.net'; const blobService = AzureStorage.Blob.createBlobServiceWithSas(blobUri, account.sas); ``` ### <a name="create-a-blob-container"></a>Creación de un contenedor de blobs Con el servicio blob creado, ahora puede crear un nuevo contenedor para almacenar un blob cargado. El método [createContainerIfNotExists](https://azure.github.io/azure-storage-node/BlobService.html#createContainerIfNotExists__anchor) crea un contenedor nuevo y no devuelve un error si el contenedor ya existe. ```javascript document.getElementById('create-button').addEventListener('click', () => { blobService.createContainerIfNotExists('mycontainer', (error, container) => { if (error) { // Handle create container error } else { console.log(container.name); } }); }); ``` ### <a name="upload-a-blob"></a>Carga de un blob Para cargar un blob desde un formulario HTML, obtendrá una referencia al archivo seleccionado desde un elemento *INPUT*. El archivo seleccionado está disponible mediante la matriz `files` cuando el *tipo* del elemento está establecido en *file*. Desde el script, puede hacer referencia al elemento HTML y pasar el archivo seleccionado al servicio blob. ```javascript document.getElementById('upload-button').addEventListener('click', () => { const file = document.getElementById('fileinput').files[0]; blobService.createBlockBlobFromBrowserFile('mycontainer', file.name, file, (error, result) => { if(error) { // Handle blob error } else { console.log('Upload is successful'); } }); }); ``` El método [createBlockBlobFromBrowserFile](https://azure.github.io/azure-storage-node/BlobService.html#createBlockBlobFromBrowserFile__anchor) utiliza el archivo del explorador directamente para realizar la carga en un contenedor de blobs. ### <a name="list-blobs"></a>Enumeración de blobs Una vez que ha cargado un archivo en el contenedor de blobs, tiene acceso a una lista de blobs en el contenedor mediante el método [listBlobsSegmented](https://azure.github.io/azure-storage-node/BlobService.html#listBlobsSegmented__anchor). ```javascript document.getElementById('list-button').addEventListener('click', () => { blobService.listBlobsSegmented('mycontainer', null, (error, results) => { if (error) { // Handle list blobs error } else { results.entries.forEach(blob => { console.log(blob.name); }); } }); }); ``` El método *listBlobsSegmented* devuelve una colección de blobs. De forma predeterminada, la cantidad de la colección es 5000 blobs, pero puede ajustar este valor para adaptarlo a sus necesidades. El [ejemplo de continuación](https://github.com/Azure/azure-storage-node/blob/master/examples/samples/continuationsample.js#L132) muestra cómo trabajar con un gran número de blobs y cómo la biblioteca de cliente admite la paginación. ### <a name="delete-blobs"></a>Eliminar blobs Puede eliminar el blob que cargó mediante una llamada a [deleteBlobIfExists](https://azure.github.io/azure-storage-node/BlobService.html#deleteBlobIfExists__anchor). ```javascript document.getElementById('delete-button').addEventListener('click', () => { var blobName = YOUR_BLOB_NAME; blobService.deleteBlobIfExists('mycontainer', blobName, (error, result) => { if (error) { // Handle delete blob error } else { console.log('Blob deleted successfully'); } }); }); ``` > [!WARNING] > Para que este ejemplo de código funcione, debe proporcionar un valor de cadena para *blobName*. ## <a name="clean-up-resources"></a>Limpieza de recursos Para limpiar los recursos creados durante esta guía de inicio rápido, vuelva a [Azure Portal](https://portal.azure.com) y seleccione la cuenta de almacenamiento. Una vez seleccionada, para eliminar la cuenta de almacenamiento, vaya a: **Información general > Eliminar cuenta de almacenamiento**. ## <a name="next-steps"></a>Pasos siguientes Explore los ejemplos para aprender a descargar blobs e informar del progreso durante las cargas de archivos. > [!div class="nextstepaction"] > [Bibliotecas de cliente de Blob Storage](https://github.com/Azure/azure-storage-node/tree/master/browser)

60.70229

455

0.725289

spa_Latn

0.965382

d0d60f9d01a7cee7b73b512f454116099e98f97d

71,118

md

Markdown

repos/php/remote/8.1.0alpha2-apache-buster.md

terrorizer1980/repo-info

7385726db2704ed54c2cbaa6e127949e18683338

[ "Apache-2.0" ]

null

repos/php/remote/8.1.0alpha2-apache-buster.md

terrorizer1980/repo-info

7385726db2704ed54c2cbaa6e127949e18683338

[ "Apache-2.0" ]

null

repos/php/remote/8.1.0alpha2-apache-buster.md

terrorizer1980/repo-info

7385726db2704ed54c2cbaa6e127949e18683338

[ "Apache-2.0" ]

1

2021-07-03T15:49:49.000Z

## `php:8.1.0alpha2-apache-buster` ```console $ docker pull php@sha256:054eb5f9edeb904be2d94bf036ce0169824f6303c9cebfbbdc001ccef40572d5 ``` - Manifest MIME: `application/vnd.docker.distribution.manifest.list.v2+json` - Platforms: - linux; amd64 - linux; arm variant v5 - linux; arm variant v7 - linux; arm64 variant v8 - linux; 386 - linux; mips64le - linux; s390x ### `php:8.1.0alpha2-apache-buster` - linux; amd64 ```console $ docker pull php@sha256:9ac98c0bac0278220bc0d78671571fa49109aa9495fdc9baaa9a88a98dea5e6c ``` - Docker Version: 20.10.7 - Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json` - Total Size: **148.9 MB (148934733 bytes)** (compressed transfer size, not on-disk size) - Image ID: `sha256:98b73e617209c729a10bd87321485978a701eb9df0beafb51f9c3ad96893d569` - Entrypoint: `["docker-php-entrypoint"]` - Default Command: `["apache2-foreground"]` ```dockerfile # Wed, 23 Jun 2021 00:20:40 GMT ADD file:4903a19c327468b0e08e4f463cfc162c66b85b4618b5803d71365862f6302e0b in / # Wed, 23 Jun 2021 00:20:40 GMT CMD ["bash"] # Wed, 23 Jun 2021 11:48:30 GMT RUN set -eux; { echo 'Package: php*'; echo 'Pin: release *'; echo 'Pin-Priority: -1'; } > /etc/apt/preferences.d/no-debian-php # Wed, 23 Jun 2021 11:48:30 GMT ENV PHPIZE_DEPS=autoconf dpkg-dev file g++ gcc libc-dev make pkg-config re2c # Wed, 23 Jun 2021 11:48:48 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends $PHPIZE_DEPS ca-certificates curl xz-utils ; rm -rf /var/lib/apt/lists/* # Wed, 23 Jun 2021 11:48:49 GMT ENV PHP_INI_DIR=/usr/local/etc/php # Wed, 23 Jun 2021 11:48:50 GMT RUN set -eux; mkdir -p "$PHP_INI_DIR/conf.d"; [ ! -d /var/www/html ]; mkdir -p /var/www/html; chown www-data:www-data /var/www/html; chmod 777 /var/www/html # Wed, 23 Jun 2021 11:55:42 GMT ENV APACHE_CONFDIR=/etc/apache2 # Wed, 23 Jun 2021 11:55:42 GMT ENV APACHE_ENVVARS=/etc/apache2/envvars # Wed, 23 Jun 2021 11:55:51 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends apache2; rm -rf /var/lib/apt/lists/*; sed -ri 's/^export ([^=]+)=(.*)$/: ${\1:=\2}\nexport \1/' "$APACHE_ENVVARS"; . "$APACHE_ENVVARS"; for dir in "$APACHE_LOCK_DIR" "$APACHE_RUN_DIR" "$APACHE_LOG_DIR" ; do rm -rvf "$dir"; mkdir -p "$dir"; chown "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$dir"; chmod 777 "$dir"; done; rm -rvf /var/www/html/*; ln -sfT /dev/stderr "$APACHE_LOG_DIR/error.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/access.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/other_vhosts_access.log"; chown -R --no-dereference "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$APACHE_LOG_DIR" # Wed, 23 Jun 2021 11:55:53 GMT RUN a2dismod mpm_event && a2enmod mpm_prefork # Wed, 23 Jun 2021 11:55:55 GMT RUN { echo '<FilesMatch \.php$>'; echo '\tSetHandler application/x-httpd-php'; echo '</FilesMatch>'; echo; echo 'DirectoryIndex disabled'; echo 'DirectoryIndex index.php index.html'; echo; echo '<Directory /var/www/>'; echo '\tOptions -Indexes'; echo '\tAllowOverride All'; echo '</Directory>'; } | tee "$APACHE_CONFDIR/conf-available/docker-php.conf" && a2enconf docker-php # Wed, 23 Jun 2021 11:55:55 GMT ENV PHP_EXTRA_BUILD_DEPS=apache2-dev # Wed, 23 Jun 2021 11:55:55 GMT ENV PHP_EXTRA_CONFIGURE_ARGS=--with-apxs2 --disable-cgi # Wed, 23 Jun 2021 11:55:56 GMT ENV PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 11:55:56 GMT ENV PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 11:55:56 GMT ENV PHP_LDFLAGS=-Wl,-O1 -pie # Wed, 23 Jun 2021 11:55:57 GMT ENV GPG_KEYS=528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 39B641343D8C104B2B146DC3F9C39DC0B9698544 F1F692238FBC1666E5A5CCD4199F9DFEF6FFBAFD # Mon, 28 Jun 2021 19:27:31 GMT ENV PHP_VERSION=8.1.0alpha2 # Mon, 28 Jun 2021 19:27:31 GMT ENV PHP_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz PHP_ASC_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz.asc # Mon, 28 Jun 2021 19:27:31 GMT ENV PHP_SHA256=916e96eda029198134dd20e50a98b539d70ef204aa241e017c8b2c736222e4c6 # Mon, 28 Jun 2021 19:27:41 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr; rm -rf /var/lib/apt/lists/*; mkdir -p /usr/src; cd /usr/src; curl -fsSL -o php.tar.xz "$PHP_URL"; if [ -n "$PHP_SHA256" ]; then echo "$PHP_SHA256 *php.tar.xz" | sha256sum -c -; fi; if [ -n "$PHP_ASC_URL" ]; then curl -fsSL -o php.tar.xz.asc "$PHP_ASC_URL"; export GNUPGHOME="$(mktemp -d)"; for key in $GPG_KEYS; do gpg --batch --keyserver keyserver.ubuntu.com --recv-keys "$key"; done; gpg --batch --verify php.tar.xz.asc php.tar.xz; gpgconf --kill all; rm -rf "$GNUPGHOME"; fi; apt-mark auto '.*' > /dev/null; apt-mark manual $savedAptMark > /dev/null; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false # Mon, 28 Jun 2021 19:27:41 GMT COPY file:ce57c04b70896f77cc11eb2766417d8a1240fcffe5bba92179ec78c458844110 in /usr/local/bin/ # Mon, 28 Jun 2021 19:32:26 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends libargon2-dev libcurl4-openssl-dev libedit-dev libonig-dev libsodium-dev libsqlite3-dev libssl-dev libxml2-dev zlib1g-dev ${PHP_EXTRA_BUILD_DEPS:-} ; rm -rf /var/lib/apt/lists/*; export CFLAGS="$PHP_CFLAGS" CPPFLAGS="$PHP_CPPFLAGS" LDFLAGS="$PHP_LDFLAGS" ; docker-php-source extract; cd /usr/src/php; gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; debMultiarch="$(dpkg-architecture --query DEB_BUILD_MULTIARCH)"; if [ ! -d /usr/include/curl ]; then ln -sT "/usr/include/$debMultiarch/curl" /usr/local/include/curl; fi; ./configure --build="$gnuArch" --with-config-file-path="$PHP_INI_DIR" --with-config-file-scan-dir="$PHP_INI_DIR/conf.d" --enable-option-checking=fatal --with-mhash --with-pic --enable-ftp --enable-mbstring --enable-mysqlnd --with-password-argon2 --with-sodium=shared --with-pdo-sqlite=/usr --with-sqlite3=/usr --with-curl --with-libedit --with-openssl --with-zlib --with-pear $(test "$gnuArch" = 's390x-linux-gnu' && echo '--without-pcre-jit') --with-libdir="lib/$debMultiarch" ${PHP_EXTRA_CONFIGURE_ARGS:-} ; make -j "$(nproc)"; find -type f -name '*.a' -delete; make install; find /usr/local/bin /usr/local/sbin -type f -executable -exec strip --strip-all '{}' + || true; make clean; cp -v php.ini-* "$PHP_INI_DIR/"; cd /; docker-php-source delete; apt-mark auto '.*' > /dev/null; [ -z "$savedAptMark" ] || apt-mark manual $savedAptMark; find /usr/local -type f -executable -exec ldd '{}' ';' | awk '/=>/ { print $(NF-1) }' | sort -u | xargs -r dpkg-query --search | cut -d: -f1 | sort -u | xargs -r apt-mark manual ; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; pecl update-channels; rm -rf /tmp/pear ~/.pearrc; php --version # Mon, 28 Jun 2021 19:32:27 GMT COPY multi:e4407f0002276f00cc93b01e48696c1f677a5f7d3d194b3a84bec1cc5e733bcb in /usr/local/bin/ # Mon, 28 Jun 2021 19:32:28 GMT RUN docker-php-ext-enable sodium # Mon, 28 Jun 2021 19:32:28 GMT ENTRYPOINT ["docker-php-entrypoint"] # Mon, 28 Jun 2021 19:32:28 GMT STOPSIGNAL SIGWINCH # Mon, 28 Jun 2021 19:32:28 GMT COPY file:e3123fcb6566efa979f945bfac1c94c854a559d7b82723e42118882a8ac4de66 in /usr/local/bin/ # Mon, 28 Jun 2021 19:32:29 GMT WORKDIR /var/www/html # Mon, 28 Jun 2021 19:32:29 GMT EXPOSE 80 # Mon, 28 Jun 2021 19:32:29 GMT CMD ["apache2-foreground"] ``` - Layers: - `sha256:b4d181a07f8025e00e0cb28f1cc14613da2ce26450b80c54aea537fa93cf3bda` Last Modified: Wed, 23 Jun 2021 00:25:39 GMT Size: 27.1 MB (27145851 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:78b85dd8f01492a64ab518247894d5b93db91b5ef9c770b601b37f612278b602` Last Modified: Wed, 23 Jun 2021 13:53:31 GMT Size: 228.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:8589b26a90be6577309788924232d8900e0e44f0a7fb4ca01c32c6467578a27d` Last Modified: Wed, 23 Jun 2021 13:53:50 GMT Size: 76.7 MB (76680976 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:f5af5d6419462987bdb2cd60de0729dcf0c35933ca87692f2eb9ca1ae292a642` Last Modified: Wed, 23 Jun 2021 13:53:31 GMT Size: 270.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:614ec6f0b8d6a562071e6a2584ca97b4237364aa3b78b00aa6c601a00c80d019` Last Modified: Wed, 23 Jun 2021 13:54:26 GMT Size: 18.7 MB (18679261 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:12b28f3797fbefaacc6339a39139cd689c6038bdbe1ee96bd947d58397be3538` Last Modified: Wed, 23 Jun 2021 13:54:22 GMT Size: 474.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:96bcb7d2e6b049343069918b727a239aa0ae67500a2f20744af37dd6c89d90d9` Last Modified: Wed, 23 Jun 2021 13:54:22 GMT Size: 515.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:7c28cf9edfa5f9d3b42ae9022ba1d1c6d9b8ec3c1ca75d64a9958a0ffc35c464` Last Modified: Tue, 29 Jun 2021 00:37:40 GMT Size: 11.6 MB (11635792 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:94fc3da3efd6c2cb723eaf519336ae3eaf82cf5df5d769ff81980363e5ff1211` Last Modified: Tue, 29 Jun 2021 00:37:37 GMT Size: 492.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:da267d1e395c7ba4aaa3065dc374cd75baa6390cfdadc2336db439e8068a1a40` Last Modified: Tue, 29 Jun 2021 00:37:40 GMT Size: 14.8 MB (14787457 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:182702162f66277b829fdf339fbc93eaa35544c5c58a0ef326cfc7bb3033072f` Last Modified: Tue, 29 Jun 2021 00:37:37 GMT Size: 2.3 KB (2276 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:7e23422ab943784bcddda7371004cfdd0a393c6d13747240b85303daa0a73388` Last Modified: Tue, 29 Jun 2021 00:37:37 GMT Size: 245.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:dbde3f61cfcf5b983016da64ba644c3e2ce53ab21c427d10dd6e5efa3f8370ab` Last Modified: Tue, 29 Jun 2021 00:37:37 GMT Size: 896.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip ### `php:8.1.0alpha2-apache-buster` - linux; arm variant v5 ```console $ docker pull php@sha256:24e1ff4fd95ce82e178aa3689648c87903f8242a244a9301a08aa4365f02d4a6 ``` - Docker Version: 20.10.7 - Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json` - Total Size: **126.9 MB (126884367 bytes)** (compressed transfer size, not on-disk size) - Image ID: `sha256:39ac5dfce9099d30644743fc1955bf920135c313bff91ebc3f1d081e165220b3` - Entrypoint: `["docker-php-entrypoint"]` - Default Command: `["apache2-foreground"]` ```dockerfile # Tue, 22 Jun 2021 23:50:09 GMT ADD file:78d4ced31112d85490c684f350aceeebfc72a804262c7ad3e033257e3894f5c4 in / # Tue, 22 Jun 2021 23:50:11 GMT CMD ["bash"] # Wed, 23 Jun 2021 06:34:32 GMT RUN set -eux; { echo 'Package: php*'; echo 'Pin: release *'; echo 'Pin-Priority: -1'; } > /etc/apt/preferences.d/no-debian-php # Wed, 23 Jun 2021 06:34:32 GMT ENV PHPIZE_DEPS=autoconf dpkg-dev file g++ gcc libc-dev make pkg-config re2c # Wed, 23 Jun 2021 06:35:18 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends $PHPIZE_DEPS ca-certificates curl xz-utils ; rm -rf /var/lib/apt/lists/* # Wed, 23 Jun 2021 06:35:19 GMT ENV PHP_INI_DIR=/usr/local/etc/php # Wed, 23 Jun 2021 06:35:21 GMT RUN set -eux; mkdir -p "$PHP_INI_DIR/conf.d"; [ ! -d /var/www/html ]; mkdir -p /var/www/html; chown www-data:www-data /var/www/html; chmod 777 /var/www/html # Wed, 23 Jun 2021 06:41:07 GMT ENV APACHE_CONFDIR=/etc/apache2 # Wed, 23 Jun 2021 06:41:08 GMT ENV APACHE_ENVVARS=/etc/apache2/envvars # Wed, 23 Jun 2021 06:41:31 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends apache2; rm -rf /var/lib/apt/lists/*; sed -ri 's/^export ([^=]+)=(.*)$/: ${\1:=\2}\nexport \1/' "$APACHE_ENVVARS"; . "$APACHE_ENVVARS"; for dir in "$APACHE_LOCK_DIR" "$APACHE_RUN_DIR" "$APACHE_LOG_DIR" ; do rm -rvf "$dir"; mkdir -p "$dir"; chown "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$dir"; chmod 777 "$dir"; done; rm -rvf /var/www/html/*; ln -sfT /dev/stderr "$APACHE_LOG_DIR/error.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/access.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/other_vhosts_access.log"; chown -R --no-dereference "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$APACHE_LOG_DIR" # Wed, 23 Jun 2021 06:41:33 GMT RUN a2dismod mpm_event && a2enmod mpm_prefork # Wed, 23 Jun 2021 06:41:35 GMT RUN { echo '<FilesMatch \.php$>'; echo '\tSetHandler application/x-httpd-php'; echo '</FilesMatch>'; echo; echo 'DirectoryIndex disabled'; echo 'DirectoryIndex index.php index.html'; echo; echo '<Directory /var/www/>'; echo '\tOptions -Indexes'; echo '\tAllowOverride All'; echo '</Directory>'; } | tee "$APACHE_CONFDIR/conf-available/docker-php.conf" && a2enconf docker-php # Wed, 23 Jun 2021 06:41:35 GMT ENV PHP_EXTRA_BUILD_DEPS=apache2-dev # Wed, 23 Jun 2021 06:41:35 GMT ENV PHP_EXTRA_CONFIGURE_ARGS=--with-apxs2 --disable-cgi # Wed, 23 Jun 2021 06:41:36 GMT ENV PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 06:41:36 GMT ENV PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 06:41:36 GMT ENV PHP_LDFLAGS=-Wl,-O1 -pie # Wed, 23 Jun 2021 06:41:37 GMT ENV GPG_KEYS=528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 39B641343D8C104B2B146DC3F9C39DC0B9698544 F1F692238FBC1666E5A5CCD4199F9DFEF6FFBAFD # Mon, 28 Jun 2021 18:58:42 GMT ENV PHP_VERSION=8.1.0alpha2 # Mon, 28 Jun 2021 18:58:42 GMT ENV PHP_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz PHP_ASC_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz.asc # Mon, 28 Jun 2021 18:58:43 GMT ENV PHP_SHA256=916e96eda029198134dd20e50a98b539d70ef204aa241e017c8b2c736222e4c6 # Mon, 28 Jun 2021 18:59:02 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr; rm -rf /var/lib/apt/lists/*; mkdir -p /usr/src; cd /usr/src; curl -fsSL -o php.tar.xz "$PHP_URL"; if [ -n "$PHP_SHA256" ]; then echo "$PHP_SHA256 *php.tar.xz" | sha256sum -c -; fi; if [ -n "$PHP_ASC_URL" ]; then curl -fsSL -o php.tar.xz.asc "$PHP_ASC_URL"; export GNUPGHOME="$(mktemp -d)"; for key in $GPG_KEYS; do gpg --batch --keyserver keyserver.ubuntu.com --recv-keys "$key"; done; gpg --batch --verify php.tar.xz.asc php.tar.xz; gpgconf --kill all; rm -rf "$GNUPGHOME"; fi; apt-mark auto '.*' > /dev/null; apt-mark manual $savedAptMark > /dev/null; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false # Mon, 28 Jun 2021 18:59:03 GMT COPY file:ce57c04b70896f77cc11eb2766417d8a1240fcffe5bba92179ec78c458844110 in /usr/local/bin/ # Mon, 28 Jun 2021 19:04:20 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends libargon2-dev libcurl4-openssl-dev libedit-dev libonig-dev libsodium-dev libsqlite3-dev libssl-dev libxml2-dev zlib1g-dev ${PHP_EXTRA_BUILD_DEPS:-} ; rm -rf /var/lib/apt/lists/*; export CFLAGS="$PHP_CFLAGS" CPPFLAGS="$PHP_CPPFLAGS" LDFLAGS="$PHP_LDFLAGS" ; docker-php-source extract; cd /usr/src/php; gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; debMultiarch="$(dpkg-architecture --query DEB_BUILD_MULTIARCH)"; if [ ! -d /usr/include/curl ]; then ln -sT "/usr/include/$debMultiarch/curl" /usr/local/include/curl; fi; ./configure --build="$gnuArch" --with-config-file-path="$PHP_INI_DIR" --with-config-file-scan-dir="$PHP_INI_DIR/conf.d" --enable-option-checking=fatal --with-mhash --with-pic --enable-ftp --enable-mbstring --enable-mysqlnd --with-password-argon2 --with-sodium=shared --with-pdo-sqlite=/usr --with-sqlite3=/usr --with-curl --with-libedit --with-openssl --with-zlib --with-pear $(test "$gnuArch" = 's390x-linux-gnu' && echo '--without-pcre-jit') --with-libdir="lib/$debMultiarch" ${PHP_EXTRA_CONFIGURE_ARGS:-} ; make -j "$(nproc)"; find -type f -name '*.a' -delete; make install; find /usr/local/bin /usr/local/sbin -type f -executable -exec strip --strip-all '{}' + || true; make clean; cp -v php.ini-* "$PHP_INI_DIR/"; cd /; docker-php-source delete; apt-mark auto '.*' > /dev/null; [ -z "$savedAptMark" ] || apt-mark manual $savedAptMark; find /usr/local -type f -executable -exec ldd '{}' ';' | awk '/=>/ { print $(NF-1) }' | sort -u | xargs -r dpkg-query --search | cut -d: -f1 | sort -u | xargs -r apt-mark manual ; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; pecl update-channels; rm -rf /tmp/pear ~/.pearrc; php --version # Mon, 28 Jun 2021 19:04:21 GMT COPY multi:e4407f0002276f00cc93b01e48696c1f677a5f7d3d194b3a84bec1cc5e733bcb in /usr/local/bin/ # Mon, 28 Jun 2021 19:04:22 GMT RUN docker-php-ext-enable sodium # Mon, 28 Jun 2021 19:04:23 GMT ENTRYPOINT ["docker-php-entrypoint"] # Mon, 28 Jun 2021 19:04:23 GMT STOPSIGNAL SIGWINCH # Mon, 28 Jun 2021 19:04:24 GMT COPY file:e3123fcb6566efa979f945bfac1c94c854a559d7b82723e42118882a8ac4de66 in /usr/local/bin/ # Mon, 28 Jun 2021 19:04:24 GMT WORKDIR /var/www/html # Mon, 28 Jun 2021 19:04:25 GMT EXPOSE 80 # Mon, 28 Jun 2021 19:04:25 GMT CMD ["apache2-foreground"] ``` - Layers: - `sha256:532d6df30af5174ac6e1b379c32b8f464d44651ac060376a560c4a76a87704a7` Last Modified: Wed, 23 Jun 2021 00:01:46 GMT Size: 24.9 MB (24878945 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:dc4201a900b66f4e05c8ee53ef7ecdffa56d4cfc141826c4899ba2c7ea1565c3` Last Modified: Wed, 23 Jun 2021 08:37:06 GMT Size: 224.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:8759f5b6f404f221d7035198880caf6e5b60d43c01daf59b9c7ff32e8ba5038f` Last Modified: Wed, 23 Jun 2021 08:37:51 GMT Size: 58.8 MB (58820428 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:0bee84cde96b6e1abd89640d87273fd846cad74593b3ec8bdd0167bb76f06398` Last Modified: Wed, 23 Jun 2021 08:37:06 GMT Size: 270.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:0d04a75937c26e6facc2a34e28c4f30008fb2c8c38d4a6109ab3bd73a1a4d516` Last Modified: Wed, 23 Jun 2021 08:38:40 GMT Size: 18.0 MB (18026172 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:06ecd491048519ab1e7d82a3cf53d86795ba9b3b230f90332de7efe0d76f16cd` Last Modified: Wed, 23 Jun 2021 08:38:29 GMT Size: 476.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:96b63bc3f991d218876d985827b11cbce08ca267e836215529cbbfbd0a0abf7b` Last Modified: Wed, 23 Jun 2021 08:38:29 GMT Size: 517.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:a3a1810006e54728143b4f68e9b52c60c8a78600c573b9dcd5238cd46144a3c9` Last Modified: Mon, 28 Jun 2021 20:57:22 GMT Size: 11.6 MB (11633889 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:27746cb058a273c45a0272129d02b89a35ee8afec73d9ffe3247e7bf7efe6ad9` Last Modified: Mon, 28 Jun 2021 20:57:17 GMT Size: 492.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:95d065ee0bbd604bfba5501f4f84ba6ed2058248fe9ce6e3db05f2b74fe500d7` Last Modified: Mon, 28 Jun 2021 20:57:28 GMT Size: 13.5 MB (13519531 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:e902ef226d559edde11e9b82be06cc24deb0178331a0c0649a52e33895944e07` Last Modified: Mon, 28 Jun 2021 20:57:17 GMT Size: 2.3 KB (2278 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:297d52b4c8b1fd44eb373a88d516dd387c8b8e66d20dc3ce2899595d91a2d8a5` Last Modified: Mon, 28 Jun 2021 20:57:17 GMT Size: 249.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:b2e3b9bc82103050961b713c9527f9778a6f7f84eec83aabda559946a0251c68` Last Modified: Mon, 28 Jun 2021 20:57:17 GMT Size: 896.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip ### `php:8.1.0alpha2-apache-buster` - linux; arm variant v7 ```console $ docker pull php@sha256:9ac50a9208a3bcbbdb28fad945fbfdb1cfd116c7c18ae88abd722139e2678d6d ``` - Docker Version: 20.10.7 - Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json` - Total Size: **124.1 MB (124139182 bytes)** (compressed transfer size, not on-disk size) - Image ID: `sha256:883822b0735ce9647bfbb7aad1772b4abb9ff4ef0d89d948782ece421e4659b4` - Entrypoint: `["docker-php-entrypoint"]` - Default Command: `["apache2-foreground"]` ```dockerfile # Wed, 23 Jun 2021 00:20:31 GMT ADD file:8d200a3bbe985ff355343675c5555852f27550a9e367969df6bc98034efb8fd4 in / # Wed, 23 Jun 2021 00:20:31 GMT CMD ["bash"] # Wed, 23 Jun 2021 08:21:24 GMT RUN set -eux; { echo 'Package: php*'; echo 'Pin: release *'; echo 'Pin-Priority: -1'; } > /etc/apt/preferences.d/no-debian-php # Wed, 23 Jun 2021 08:21:25 GMT ENV PHPIZE_DEPS=autoconf dpkg-dev file g++ gcc libc-dev make pkg-config re2c # Wed, 23 Jun 2021 08:22:06 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends $PHPIZE_DEPS ca-certificates curl xz-utils ; rm -rf /var/lib/apt/lists/* # Wed, 23 Jun 2021 08:22:07 GMT ENV PHP_INI_DIR=/usr/local/etc/php # Wed, 23 Jun 2021 08:22:08 GMT RUN set -eux; mkdir -p "$PHP_INI_DIR/conf.d"; [ ! -d /var/www/html ]; mkdir -p /var/www/html; chown www-data:www-data /var/www/html; chmod 777 /var/www/html # Wed, 23 Jun 2021 08:27:04 GMT ENV APACHE_CONFDIR=/etc/apache2 # Wed, 23 Jun 2021 08:27:04 GMT ENV APACHE_ENVVARS=/etc/apache2/envvars # Wed, 23 Jun 2021 08:27:25 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends apache2; rm -rf /var/lib/apt/lists/*; sed -ri 's/^export ([^=]+)=(.*)$/: ${\1:=\2}\nexport \1/' "$APACHE_ENVVARS"; . "$APACHE_ENVVARS"; for dir in "$APACHE_LOCK_DIR" "$APACHE_RUN_DIR" "$APACHE_LOG_DIR" ; do rm -rvf "$dir"; mkdir -p "$dir"; chown "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$dir"; chmod 777 "$dir"; done; rm -rvf /var/www/html/*; ln -sfT /dev/stderr "$APACHE_LOG_DIR/error.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/access.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/other_vhosts_access.log"; chown -R --no-dereference "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$APACHE_LOG_DIR" # Wed, 23 Jun 2021 08:27:27 GMT RUN a2dismod mpm_event && a2enmod mpm_prefork # Wed, 23 Jun 2021 08:27:28 GMT RUN { echo '<FilesMatch \.php$>'; echo '\tSetHandler application/x-httpd-php'; echo '</FilesMatch>'; echo; echo 'DirectoryIndex disabled'; echo 'DirectoryIndex index.php index.html'; echo; echo '<Directory /var/www/>'; echo '\tOptions -Indexes'; echo '\tAllowOverride All'; echo '</Directory>'; } | tee "$APACHE_CONFDIR/conf-available/docker-php.conf" && a2enconf docker-php # Wed, 23 Jun 2021 08:27:29 GMT ENV PHP_EXTRA_BUILD_DEPS=apache2-dev # Wed, 23 Jun 2021 08:27:29 GMT ENV PHP_EXTRA_CONFIGURE_ARGS=--with-apxs2 --disable-cgi # Wed, 23 Jun 2021 08:27:30 GMT ENV PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 08:27:30 GMT ENV PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 08:27:30 GMT ENV PHP_LDFLAGS=-Wl,-O1 -pie # Wed, 23 Jun 2021 08:27:31 GMT ENV GPG_KEYS=528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 39B641343D8C104B2B146DC3F9C39DC0B9698544 F1F692238FBC1666E5A5CCD4199F9DFEF6FFBAFD # Mon, 28 Jun 2021 19:53:38 GMT ENV PHP_VERSION=8.1.0alpha2 # Mon, 28 Jun 2021 19:53:39 GMT ENV PHP_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz PHP_ASC_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz.asc # Mon, 28 Jun 2021 19:53:39 GMT ENV PHP_SHA256=916e96eda029198134dd20e50a98b539d70ef204aa241e017c8b2c736222e4c6 # Mon, 28 Jun 2021 19:53:55 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr; rm -rf /var/lib/apt/lists/*; mkdir -p /usr/src; cd /usr/src; curl -fsSL -o php.tar.xz "$PHP_URL"; if [ -n "$PHP_SHA256" ]; then echo "$PHP_SHA256 *php.tar.xz" | sha256sum -c -; fi; if [ -n "$PHP_ASC_URL" ]; then curl -fsSL -o php.tar.xz.asc "$PHP_ASC_URL"; export GNUPGHOME="$(mktemp -d)"; for key in $GPG_KEYS; do gpg --batch --keyserver keyserver.ubuntu.com --recv-keys "$key"; done; gpg --batch --verify php.tar.xz.asc php.tar.xz; gpgconf --kill all; rm -rf "$GNUPGHOME"; fi; apt-mark auto '.*' > /dev/null; apt-mark manual $savedAptMark > /dev/null; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false # Mon, 28 Jun 2021 19:53:56 GMT COPY file:ce57c04b70896f77cc11eb2766417d8a1240fcffe5bba92179ec78c458844110 in /usr/local/bin/ # Mon, 28 Jun 2021 19:58:41 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends libargon2-dev libcurl4-openssl-dev libedit-dev libonig-dev libsodium-dev libsqlite3-dev libssl-dev libxml2-dev zlib1g-dev ${PHP_EXTRA_BUILD_DEPS:-} ; rm -rf /var/lib/apt/lists/*; export CFLAGS="$PHP_CFLAGS" CPPFLAGS="$PHP_CPPFLAGS" LDFLAGS="$PHP_LDFLAGS" ; docker-php-source extract; cd /usr/src/php; gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; debMultiarch="$(dpkg-architecture --query DEB_BUILD_MULTIARCH)"; if [ ! -d /usr/include/curl ]; then ln -sT "/usr/include/$debMultiarch/curl" /usr/local/include/curl; fi; ./configure --build="$gnuArch" --with-config-file-path="$PHP_INI_DIR" --with-config-file-scan-dir="$PHP_INI_DIR/conf.d" --enable-option-checking=fatal --with-mhash --with-pic --enable-ftp --enable-mbstring --enable-mysqlnd --with-password-argon2 --with-sodium=shared --with-pdo-sqlite=/usr --with-sqlite3=/usr --with-curl --with-libedit --with-openssl --with-zlib --with-pear $(test "$gnuArch" = 's390x-linux-gnu' && echo '--without-pcre-jit') --with-libdir="lib/$debMultiarch" ${PHP_EXTRA_CONFIGURE_ARGS:-} ; make -j "$(nproc)"; find -type f -name '*.a' -delete; make install; find /usr/local/bin /usr/local/sbin -type f -executable -exec strip --strip-all '{}' + || true; make clean; cp -v php.ini-* "$PHP_INI_DIR/"; cd /; docker-php-source delete; apt-mark auto '.*' > /dev/null; [ -z "$savedAptMark" ] || apt-mark manual $savedAptMark; find /usr/local -type f -executable -exec ldd '{}' ';' | awk '/=>/ { print $(NF-1) }' | sort -u | xargs -r dpkg-query --search | cut -d: -f1 | sort -u | xargs -r apt-mark manual ; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; pecl update-channels; rm -rf /tmp/pear ~/.pearrc; php --version # Mon, 28 Jun 2021 19:58:43 GMT COPY multi:e4407f0002276f00cc93b01e48696c1f677a5f7d3d194b3a84bec1cc5e733bcb in /usr/local/bin/ # Mon, 28 Jun 2021 19:58:45 GMT RUN docker-php-ext-enable sodium # Mon, 28 Jun 2021 19:58:45 GMT ENTRYPOINT ["docker-php-entrypoint"] # Mon, 28 Jun 2021 19:58:46 GMT STOPSIGNAL SIGWINCH # Mon, 28 Jun 2021 19:58:46 GMT COPY file:e3123fcb6566efa979f945bfac1c94c854a559d7b82723e42118882a8ac4de66 in /usr/local/bin/ # Mon, 28 Jun 2021 19:58:46 GMT WORKDIR /var/www/html # Mon, 28 Jun 2021 19:58:47 GMT EXPOSE 80 # Mon, 28 Jun 2021 19:58:47 GMT CMD ["apache2-foreground"] ``` - Layers: - `sha256:8452be1adf00f91570fe21a8e61aaf4c12e014daf67d7de65d984f4e8ecca2f1` Last Modified: Wed, 23 Jun 2021 00:31:49 GMT Size: 22.7 MB (22746055 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:fb9600bb4c83e3ef3465228eed7d6e9dfed7dc9078d2ab47f0bbdc8ccd6cb2b4` Last Modified: Wed, 23 Jun 2021 11:51:40 GMT Size: 227.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:8e4b7395146be79190767115c26cc6b70ac8d5af36c4a7acf9de1f34d06b41d7` Last Modified: Wed, 23 Jun 2021 11:52:18 GMT Size: 59.5 MB (59514051 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:3641f6e3173b95d08e8b4ec00f48cb7e09d9813f88a086a422173594dfc93ddd` Last Modified: Wed, 23 Jun 2021 11:51:40 GMT Size: 268.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:6f7d1aa9268ffe2596e041fe0130bbdc37fb7e587a9b8d7c5346360e2f27b41d` Last Modified: Wed, 23 Jun 2021 11:53:09 GMT Size: 17.5 MB (17481801 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:2d56adf5c38075c402f8bf5f30dee3d2dd1d1f5c327b12641f29af33f5ba950a` Last Modified: Wed, 23 Jun 2021 11:52:58 GMT Size: 476.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:17bf5eeb5d260e70dda8e6cf6bf12b837eca9e5650117ad4e659861a5ecc31f5` Last Modified: Wed, 23 Jun 2021 11:52:58 GMT Size: 518.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:cb1af33ef2837390423c2b005970046730944a13d5ae7a5c5a5e8abe1120b5b3` Last Modified: Mon, 28 Jun 2021 23:28:20 GMT Size: 11.6 MB (11633938 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:9b55bdf078d8785c098aa7ef43731258ba5d8d74dd82c0ebed13f68dbb05e594` Last Modified: Mon, 28 Jun 2021 23:28:15 GMT Size: 492.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:1a6e730902214e32370a9c2071b3fbabb314213067562f40c441c6c05a6abd33` Last Modified: Mon, 28 Jun 2021 23:28:26 GMT Size: 12.8 MB (12757947 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:e698b950d25eb9ca6b1f02ba080045800fb8b64d6bd58e07e2b52891ca074e07` Last Modified: Mon, 28 Jun 2021 23:28:15 GMT Size: 2.3 KB (2272 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:300a52de59b85c86ad5c561f63223dcabbee327f45123416d4b846cf98e7b2e4` Last Modified: Mon, 28 Jun 2021 23:28:16 GMT Size: 246.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:2dc24f9d8b33fd157c7eb6e6faa8bb7af4debdb7db02257ef64b24c48af6202c` Last Modified: Mon, 28 Jun 2021 23:28:15 GMT Size: 891.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip ### `php:8.1.0alpha2-apache-buster` - linux; arm64 variant v8 ```console $ docker pull php@sha256:e6f884387300b3cc54e4a0c348fa87f64dac16dd1507517a86ce77e677ca5cc2 ``` - Docker Version: 20.10.7 - Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json` - Total Size: **141.3 MB (141304301 bytes)** (compressed transfer size, not on-disk size) - Image ID: `sha256:ffe397a7d7aa5a74e13f9d0f6a5e540092a09b9abf8498f0d9b9b1d72958a28d` - Entrypoint: `["docker-php-entrypoint"]` - Default Command: `["apache2-foreground"]` ```dockerfile # Tue, 22 Jun 2021 23:49:40 GMT ADD file:beee00b59da720f68e12e2ba2a8134207c80c777ddb4ceb03c71e3e4c3f51c93 in / # Tue, 22 Jun 2021 23:49:40 GMT CMD ["bash"] # Wed, 23 Jun 2021 08:48:19 GMT RUN set -eux; { echo 'Package: php*'; echo 'Pin: release *'; echo 'Pin-Priority: -1'; } > /etc/apt/preferences.d/no-debian-php # Wed, 23 Jun 2021 08:48:19 GMT ENV PHPIZE_DEPS=autoconf dpkg-dev file g++ gcc libc-dev make pkg-config re2c # Wed, 23 Jun 2021 08:48:34 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends $PHPIZE_DEPS ca-certificates curl xz-utils ; rm -rf /var/lib/apt/lists/* # Wed, 23 Jun 2021 08:48:34 GMT ENV PHP_INI_DIR=/usr/local/etc/php # Wed, 23 Jun 2021 08:48:35 GMT RUN set -eux; mkdir -p "$PHP_INI_DIR/conf.d"; [ ! -d /var/www/html ]; mkdir -p /var/www/html; chown www-data:www-data /var/www/html; chmod 777 /var/www/html # Wed, 23 Jun 2021 08:53:46 GMT ENV APACHE_CONFDIR=/etc/apache2 # Wed, 23 Jun 2021 08:53:47 GMT ENV APACHE_ENVVARS=/etc/apache2/envvars # Wed, 23 Jun 2021 08:53:55 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends apache2; rm -rf /var/lib/apt/lists/*; sed -ri 's/^export ([^=]+)=(.*)$/: ${\1:=\2}\nexport \1/' "$APACHE_ENVVARS"; . "$APACHE_ENVVARS"; for dir in "$APACHE_LOCK_DIR" "$APACHE_RUN_DIR" "$APACHE_LOG_DIR" ; do rm -rvf "$dir"; mkdir -p "$dir"; chown "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$dir"; chmod 777 "$dir"; done; rm -rvf /var/www/html/*; ln -sfT /dev/stderr "$APACHE_LOG_DIR/error.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/access.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/other_vhosts_access.log"; chown -R --no-dereference "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$APACHE_LOG_DIR" # Wed, 23 Jun 2021 08:53:56 GMT RUN a2dismod mpm_event && a2enmod mpm_prefork # Wed, 23 Jun 2021 08:53:57 GMT RUN { echo '<FilesMatch \.php$>'; echo '\tSetHandler application/x-httpd-php'; echo '</FilesMatch>'; echo; echo 'DirectoryIndex disabled'; echo 'DirectoryIndex index.php index.html'; echo; echo '<Directory /var/www/>'; echo '\tOptions -Indexes'; echo '\tAllowOverride All'; echo '</Directory>'; } | tee "$APACHE_CONFDIR/conf-available/docker-php.conf" && a2enconf docker-php # Wed, 23 Jun 2021 08:53:57 GMT ENV PHP_EXTRA_BUILD_DEPS=apache2-dev # Wed, 23 Jun 2021 08:53:57 GMT ENV PHP_EXTRA_CONFIGURE_ARGS=--with-apxs2 --disable-cgi # Wed, 23 Jun 2021 08:53:57 GMT ENV PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 08:53:57 GMT ENV PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 08:53:58 GMT ENV PHP_LDFLAGS=-Wl,-O1 -pie # Wed, 23 Jun 2021 08:53:58 GMT ENV GPG_KEYS=528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 39B641343D8C104B2B146DC3F9C39DC0B9698544 F1F692238FBC1666E5A5CCD4199F9DFEF6FFBAFD # Mon, 28 Jun 2021 19:46:00 GMT ENV PHP_VERSION=8.1.0alpha2 # Mon, 28 Jun 2021 19:46:00 GMT ENV PHP_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz PHP_ASC_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz.asc # Mon, 28 Jun 2021 19:46:00 GMT ENV PHP_SHA256=916e96eda029198134dd20e50a98b539d70ef204aa241e017c8b2c736222e4c6 # Mon, 28 Jun 2021 19:46:10 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr; rm -rf /var/lib/apt/lists/*; mkdir -p /usr/src; cd /usr/src; curl -fsSL -o php.tar.xz "$PHP_URL"; if [ -n "$PHP_SHA256" ]; then echo "$PHP_SHA256 *php.tar.xz" | sha256sum -c -; fi; if [ -n "$PHP_ASC_URL" ]; then curl -fsSL -o php.tar.xz.asc "$PHP_ASC_URL"; export GNUPGHOME="$(mktemp -d)"; for key in $GPG_KEYS; do gpg --batch --keyserver keyserver.ubuntu.com --recv-keys "$key"; done; gpg --batch --verify php.tar.xz.asc php.tar.xz; gpgconf --kill all; rm -rf "$GNUPGHOME"; fi; apt-mark auto '.*' > /dev/null; apt-mark manual $savedAptMark > /dev/null; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false # Mon, 28 Jun 2021 19:46:11 GMT COPY file:ce57c04b70896f77cc11eb2766417d8a1240fcffe5bba92179ec78c458844110 in /usr/local/bin/ # Mon, 28 Jun 2021 19:51:00 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends libargon2-dev libcurl4-openssl-dev libedit-dev libonig-dev libsodium-dev libsqlite3-dev libssl-dev libxml2-dev zlib1g-dev ${PHP_EXTRA_BUILD_DEPS:-} ; rm -rf /var/lib/apt/lists/*; export CFLAGS="$PHP_CFLAGS" CPPFLAGS="$PHP_CPPFLAGS" LDFLAGS="$PHP_LDFLAGS" ; docker-php-source extract; cd /usr/src/php; gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; debMultiarch="$(dpkg-architecture --query DEB_BUILD_MULTIARCH)"; if [ ! -d /usr/include/curl ]; then ln -sT "/usr/include/$debMultiarch/curl" /usr/local/include/curl; fi; ./configure --build="$gnuArch" --with-config-file-path="$PHP_INI_DIR" --with-config-file-scan-dir="$PHP_INI_DIR/conf.d" --enable-option-checking=fatal --with-mhash --with-pic --enable-ftp --enable-mbstring --enable-mysqlnd --with-password-argon2 --with-sodium=shared --with-pdo-sqlite=/usr --with-sqlite3=/usr --with-curl --with-libedit --with-openssl --with-zlib --with-pear $(test "$gnuArch" = 's390x-linux-gnu' && echo '--without-pcre-jit') --with-libdir="lib/$debMultiarch" ${PHP_EXTRA_CONFIGURE_ARGS:-} ; make -j "$(nproc)"; find -type f -name '*.a' -delete; make install; find /usr/local/bin /usr/local/sbin -type f -executable -exec strip --strip-all '{}' + || true; make clean; cp -v php.ini-* "$PHP_INI_DIR/"; cd /; docker-php-source delete; apt-mark auto '.*' > /dev/null; [ -z "$savedAptMark" ] || apt-mark manual $savedAptMark; find /usr/local -type f -executable -exec ldd '{}' ';' | awk '/=>/ { print $(NF-1) }' | sort -u | xargs -r dpkg-query --search | cut -d: -f1 | sort -u | xargs -r apt-mark manual ; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; pecl update-channels; rm -rf /tmp/pear ~/.pearrc; php --version # Mon, 28 Jun 2021 19:51:01 GMT COPY multi:e4407f0002276f00cc93b01e48696c1f677a5f7d3d194b3a84bec1cc5e733bcb in /usr/local/bin/ # Mon, 28 Jun 2021 19:51:02 GMT RUN docker-php-ext-enable sodium # Mon, 28 Jun 2021 19:51:02 GMT ENTRYPOINT ["docker-php-entrypoint"] # Mon, 28 Jun 2021 19:51:02 GMT STOPSIGNAL SIGWINCH # Mon, 28 Jun 2021 19:51:02 GMT COPY file:e3123fcb6566efa979f945bfac1c94c854a559d7b82723e42118882a8ac4de66 in /usr/local/bin/ # Mon, 28 Jun 2021 19:51:02 GMT WORKDIR /var/www/html # Mon, 28 Jun 2021 19:51:03 GMT EXPOSE 80 # Mon, 28 Jun 2021 19:51:03 GMT CMD ["apache2-foreground"] ``` - Layers: - `sha256:448f6bf000e31217a7c202c659b03b7f8ac8d3ae6b03ef7a2f8339be2f00ff4a` Last Modified: Tue, 22 Jun 2021 23:55:25 GMT Size: 25.9 MB (25914993 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:9ce6585fd70baac65871dafb05b7f408940165f163c30d7e0f9ec3518709e908` Last Modified: Wed, 23 Jun 2021 10:25:12 GMT Size: 226.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:3ab6c01ccebb7fc71b44dfe6966672e34b47ea5e22d53a11e4481e76243cd44b` Last Modified: Wed, 23 Jun 2021 10:25:24 GMT Size: 70.4 MB (70356352 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:92ed9f96098643713fabf62c17f792254db16c6623e3cec0b4a4ea602af2e742` Last Modified: Wed, 23 Jun 2021 10:25:12 GMT Size: 271.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:6852e08c882a542c19980b469e16cebe09c20c56cb6a883fe46d7fa71c77a5bf` Last Modified: Wed, 23 Jun 2021 10:26:10 GMT Size: 18.6 MB (18579813 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:650d5012e5fa16b3bcc69043ccc3b45a8e75bd3651354579204af7abe7ae4eae` Last Modified: Wed, 23 Jun 2021 10:26:01 GMT Size: 470.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:390447f485b4746ca973bb40b4a5ef8edc132fc2fd3b4c1e3681b22c5fa1ca47` Last Modified: Wed, 23 Jun 2021 10:26:01 GMT Size: 512.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:625769953c398b8d3d6c31f1f5dc11383f7c69f1cd42b9f1f74339f2bb2bbee0` Last Modified: Mon, 28 Jun 2021 22:52:45 GMT Size: 11.6 MB (11634557 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:f8f41a051673a4a1cbbf9342434fc0baa93fdb407fd88a85d801c1316e61263f` Last Modified: Mon, 28 Jun 2021 22:52:41 GMT Size: 495.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:69337de0851f89f5b7bc9d7c8a0d3561fb69906e4c3d81aef59523cae720b6f4` Last Modified: Mon, 28 Jun 2021 22:52:44 GMT Size: 14.8 MB (14813193 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:b89f2e6dbf248c637c6f5595dc1c36e91d145a750cdea106d79e57de7334bd49` Last Modified: Mon, 28 Jun 2021 22:52:41 GMT Size: 2.3 KB (2279 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:6be6a7467bc8db50d3c5c964bfae6e439e0ed0fb1c7a34fb6412ded7a1d1cfb7` Last Modified: Mon, 28 Jun 2021 22:52:41 GMT Size: 245.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:82b2d26fb7dd048ff5fb2de3d04a2a4ea4b53e23665a7265898524fabfff42c3` Last Modified: Mon, 28 Jun 2021 22:52:41 GMT Size: 895.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip ### `php:8.1.0alpha2-apache-buster` - linux; 386 ```console $ docker pull php@sha256:a5523c2fefeb4f55cc243f4c7d4e9bc9daa25171fc4e5913658ead388ae1581e ``` - Docker Version: 20.10.7 - Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json` - Total Size: **154.9 MB (154889985 bytes)** (compressed transfer size, not on-disk size) - Image ID: `sha256:ae10d36a2bc17045684fc5b23c142e8e0bbcb88921da9cfb0bfefebaa3ff781f` - Entrypoint: `["docker-php-entrypoint"]` - Default Command: `["apache2-foreground"]` ```dockerfile # Tue, 22 Jun 2021 23:39:35 GMT ADD file:48f656ac6733911048b3de850490438d0233b3badc11861fca62062d4edfaf40 in / # Tue, 22 Jun 2021 23:39:35 GMT CMD ["bash"] # Wed, 23 Jun 2021 09:40:27 GMT RUN set -eux; { echo 'Package: php*'; echo 'Pin: release *'; echo 'Pin-Priority: -1'; } > /etc/apt/preferences.d/no-debian-php # Wed, 23 Jun 2021 09:40:27 GMT ENV PHPIZE_DEPS=autoconf dpkg-dev file g++ gcc libc-dev make pkg-config re2c # Wed, 23 Jun 2021 09:40:49 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends $PHPIZE_DEPS ca-certificates curl xz-utils ; rm -rf /var/lib/apt/lists/* # Wed, 23 Jun 2021 09:40:49 GMT ENV PHP_INI_DIR=/usr/local/etc/php # Wed, 23 Jun 2021 09:40:50 GMT RUN set -eux; mkdir -p "$PHP_INI_DIR/conf.d"; [ ! -d /var/www/html ]; mkdir -p /var/www/html; chown www-data:www-data /var/www/html; chmod 777 /var/www/html # Wed, 23 Jun 2021 09:49:27 GMT ENV APACHE_CONFDIR=/etc/apache2 # Wed, 23 Jun 2021 09:49:27 GMT ENV APACHE_ENVVARS=/etc/apache2/envvars # Wed, 23 Jun 2021 09:49:43 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends apache2; rm -rf /var/lib/apt/lists/*; sed -ri 's/^export ([^=]+)=(.*)$/: ${\1:=\2}\nexport \1/' "$APACHE_ENVVARS"; . "$APACHE_ENVVARS"; for dir in "$APACHE_LOCK_DIR" "$APACHE_RUN_DIR" "$APACHE_LOG_DIR" ; do rm -rvf "$dir"; mkdir -p "$dir"; chown "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$dir"; chmod 777 "$dir"; done; rm -rvf /var/www/html/*; ln -sfT /dev/stderr "$APACHE_LOG_DIR/error.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/access.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/other_vhosts_access.log"; chown -R --no-dereference "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$APACHE_LOG_DIR" # Wed, 23 Jun 2021 09:49:44 GMT RUN a2dismod mpm_event && a2enmod mpm_prefork # Wed, 23 Jun 2021 09:49:46 GMT RUN { echo '<FilesMatch \.php$>'; echo '\tSetHandler application/x-httpd-php'; echo '</FilesMatch>'; echo; echo 'DirectoryIndex disabled'; echo 'DirectoryIndex index.php index.html'; echo; echo '<Directory /var/www/>'; echo '\tOptions -Indexes'; echo '\tAllowOverride All'; echo '</Directory>'; } | tee "$APACHE_CONFDIR/conf-available/docker-php.conf" && a2enconf docker-php # Wed, 23 Jun 2021 09:49:46 GMT ENV PHP_EXTRA_BUILD_DEPS=apache2-dev # Wed, 23 Jun 2021 09:49:47 GMT ENV PHP_EXTRA_CONFIGURE_ARGS=--with-apxs2 --disable-cgi # Wed, 23 Jun 2021 09:49:47 GMT ENV PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 09:49:47 GMT ENV PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 09:49:47 GMT ENV PHP_LDFLAGS=-Wl,-O1 -pie # Wed, 23 Jun 2021 09:49:48 GMT ENV GPG_KEYS=528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 39B641343D8C104B2B146DC3F9C39DC0B9698544 F1F692238FBC1666E5A5CCD4199F9DFEF6FFBAFD # Mon, 28 Jun 2021 19:48:08 GMT ENV PHP_VERSION=8.1.0alpha2 # Mon, 28 Jun 2021 19:48:09 GMT ENV PHP_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz PHP_ASC_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz.asc # Mon, 28 Jun 2021 19:48:09 GMT ENV PHP_SHA256=916e96eda029198134dd20e50a98b539d70ef204aa241e017c8b2c736222e4c6 # Mon, 28 Jun 2021 19:48:25 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr; rm -rf /var/lib/apt/lists/*; mkdir -p /usr/src; cd /usr/src; curl -fsSL -o php.tar.xz "$PHP_URL"; if [ -n "$PHP_SHA256" ]; then echo "$PHP_SHA256 *php.tar.xz" | sha256sum -c -; fi; if [ -n "$PHP_ASC_URL" ]; then curl -fsSL -o php.tar.xz.asc "$PHP_ASC_URL"; export GNUPGHOME="$(mktemp -d)"; for key in $GPG_KEYS; do gpg --batch --keyserver keyserver.ubuntu.com --recv-keys "$key"; done; gpg --batch --verify php.tar.xz.asc php.tar.xz; gpgconf --kill all; rm -rf "$GNUPGHOME"; fi; apt-mark auto '.*' > /dev/null; apt-mark manual $savedAptMark > /dev/null; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false # Mon, 28 Jun 2021 19:48:25 GMT COPY file:ce57c04b70896f77cc11eb2766417d8a1240fcffe5bba92179ec78c458844110 in /usr/local/bin/ # Mon, 28 Jun 2021 19:56:10 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends libargon2-dev libcurl4-openssl-dev libedit-dev libonig-dev libsodium-dev libsqlite3-dev libssl-dev libxml2-dev zlib1g-dev ${PHP_EXTRA_BUILD_DEPS:-} ; rm -rf /var/lib/apt/lists/*; export CFLAGS="$PHP_CFLAGS" CPPFLAGS="$PHP_CPPFLAGS" LDFLAGS="$PHP_LDFLAGS" ; docker-php-source extract; cd /usr/src/php; gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; debMultiarch="$(dpkg-architecture --query DEB_BUILD_MULTIARCH)"; if [ ! -d /usr/include/curl ]; then ln -sT "/usr/include/$debMultiarch/curl" /usr/local/include/curl; fi; ./configure --build="$gnuArch" --with-config-file-path="$PHP_INI_DIR" --with-config-file-scan-dir="$PHP_INI_DIR/conf.d" --enable-option-checking=fatal --with-mhash --with-pic --enable-ftp --enable-mbstring --enable-mysqlnd --with-password-argon2 --with-sodium=shared --with-pdo-sqlite=/usr --with-sqlite3=/usr --with-curl --with-libedit --with-openssl --with-zlib --with-pear $(test "$gnuArch" = 's390x-linux-gnu' && echo '--without-pcre-jit') --with-libdir="lib/$debMultiarch" ${PHP_EXTRA_CONFIGURE_ARGS:-} ; make -j "$(nproc)"; find -type f -name '*.a' -delete; make install; find /usr/local/bin /usr/local/sbin -type f -executable -exec strip --strip-all '{}' + || true; make clean; cp -v php.ini-* "$PHP_INI_DIR/"; cd /; docker-php-source delete; apt-mark auto '.*' > /dev/null; [ -z "$savedAptMark" ] || apt-mark manual $savedAptMark; find /usr/local -type f -executable -exec ldd '{}' ';' | awk '/=>/ { print $(NF-1) }' | sort -u | xargs -r dpkg-query --search | cut -d: -f1 | sort -u | xargs -r apt-mark manual ; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; pecl update-channels; rm -rf /tmp/pear ~/.pearrc; php --version # Mon, 28 Jun 2021 19:56:11 GMT COPY multi:e4407f0002276f00cc93b01e48696c1f677a5f7d3d194b3a84bec1cc5e733bcb in /usr/local/bin/ # Mon, 28 Jun 2021 19:56:13 GMT RUN docker-php-ext-enable sodium # Mon, 28 Jun 2021 19:56:14 GMT ENTRYPOINT ["docker-php-entrypoint"] # Mon, 28 Jun 2021 19:56:14 GMT STOPSIGNAL SIGWINCH # Mon, 28 Jun 2021 19:56:14 GMT COPY file:e3123fcb6566efa979f945bfac1c94c854a559d7b82723e42118882a8ac4de66 in /usr/local/bin/ # Mon, 28 Jun 2021 19:56:15 GMT WORKDIR /var/www/html # Mon, 28 Jun 2021 19:56:15 GMT EXPOSE 80 # Mon, 28 Jun 2021 19:56:16 GMT CMD ["apache2-foreground"] ``` - Layers: - `sha256:33af2dcb865e65d53cdeb843b67a0ef62151fa32df292293e7c6b0eb728ac5ac` Last Modified: Tue, 22 Jun 2021 23:46:23 GMT Size: 27.8 MB (27797411 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:851ded1e6779ac12f2623fa13c3d156987e0e3748e10171438e042c4a18cada8` Last Modified: Wed, 23 Jun 2021 12:27:42 GMT Size: 226.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:3b9108f1298d19c1c39f13396485b32141017e3d97dcc7093d43854940c92b6c` Last Modified: Wed, 23 Jun 2021 12:28:14 GMT Size: 81.2 MB (81230041 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:a4a8cc691843125fa492ce4109092746e47e36d222eceef5b59dd10271176374` Last Modified: Wed, 23 Jun 2021 12:27:42 GMT Size: 270.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:f1ce571916f9fd350c507c0b0f4ba7db9c473cb95da721dfeab5acd167c05197` Last Modified: Wed, 23 Jun 2021 12:29:05 GMT Size: 19.1 MB (19115037 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:7abad9c9b3f342c41ff79e0b1832309d795f17e4aaafd51a979891c9c747684c` Last Modified: Wed, 23 Jun 2021 12:28:58 GMT Size: 473.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:b6ecb5db768b6cdd9c3b371c253bc49fc82700b113499943217799b6cf74aab9` Last Modified: Wed, 23 Jun 2021 12:28:58 GMT Size: 516.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:d8209e58e54cc9ec10025fc281184518ed505912b061397713d782c3d922eb96` Last Modified: Tue, 29 Jun 2021 01:16:36 GMT Size: 11.6 MB (11635155 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:eaa5be4056b8527b5e0f8114e4a94f8334db5124f24577dd3354ca265f34909f` Last Modified: Tue, 29 Jun 2021 01:16:31 GMT Size: 495.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:f50489e41b307b44875751a01d18a38aec5c7a348698a1a275aacdb5e4f06a9f` Last Modified: Tue, 29 Jun 2021 01:16:40 GMT Size: 15.1 MB (15106939 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:53e5ad30ebf453bd263105a97d7f1fa8f659be184b4a76bd8997b2223cad2f81` Last Modified: Tue, 29 Jun 2021 01:16:32 GMT Size: 2.3 KB (2279 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:22d84136b034ace855c912b7b5dbbdd38dc07bb35416e1a33d1158a90ba02d94` Last Modified: Tue, 29 Jun 2021 01:16:31 GMT Size: 247.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:be73c9bcda7041e9367fec59e5a202791dbac22bccd64cf31ba6580f3a42ccb1` Last Modified: Tue, 29 Jun 2021 01:16:31 GMT Size: 896.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip ### `php:8.1.0alpha2-apache-buster` - linux; mips64le ```console $ docker pull php@sha256:cb8ca583be6678726e03811b83d537cf52d256bc3a5a1f859940ec165e430c9b ``` - Docker Version: 20.10.7 - Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json` - Total Size: **131.2 MB (131222688 bytes)** (compressed transfer size, not on-disk size) - Image ID: `sha256:217f41c54bcb8cbb3bdf87af55c4e3a02868920224c466ecfb7657f267d422bf` - Entrypoint: `["docker-php-entrypoint"]` - Default Command: `["apache2-foreground"]` ```dockerfile # Wed, 23 Jun 2021 00:09:29 GMT ADD file:ca8422268fc66c67d19fd3a33a14a9bd6280ef21404677767ffd561a8ecf6724 in / # Wed, 23 Jun 2021 00:09:30 GMT CMD ["bash"] # Wed, 23 Jun 2021 02:39:12 GMT RUN set -eux; { echo 'Package: php*'; echo 'Pin: release *'; echo 'Pin-Priority: -1'; } > /etc/apt/preferences.d/no-debian-php # Wed, 23 Jun 2021 02:39:13 GMT ENV PHPIZE_DEPS=autoconf dpkg-dev file g++ gcc libc-dev make pkg-config re2c # Wed, 23 Jun 2021 02:40:00 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends $PHPIZE_DEPS ca-certificates curl xz-utils ; rm -rf /var/lib/apt/lists/* # Wed, 23 Jun 2021 02:40:01 GMT ENV PHP_INI_DIR=/usr/local/etc/php # Wed, 23 Jun 2021 02:40:03 GMT RUN set -eux; mkdir -p "$PHP_INI_DIR/conf.d"; [ ! -d /var/www/html ]; mkdir -p /var/www/html; chown www-data:www-data /var/www/html; chmod 777 /var/www/html # Wed, 23 Jun 2021 02:52:56 GMT ENV APACHE_CONFDIR=/etc/apache2 # Wed, 23 Jun 2021 02:52:57 GMT ENV APACHE_ENVVARS=/etc/apache2/envvars # Wed, 23 Jun 2021 02:53:22 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends apache2; rm -rf /var/lib/apt/lists/*; sed -ri 's/^export ([^=]+)=(.*)$/: ${\1:=\2}\nexport \1/' "$APACHE_ENVVARS"; . "$APACHE_ENVVARS"; for dir in "$APACHE_LOCK_DIR" "$APACHE_RUN_DIR" "$APACHE_LOG_DIR" ; do rm -rvf "$dir"; mkdir -p "$dir"; chown "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$dir"; chmod 777 "$dir"; done; rm -rvf /var/www/html/*; ln -sfT /dev/stderr "$APACHE_LOG_DIR/error.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/access.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/other_vhosts_access.log"; chown -R --no-dereference "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$APACHE_LOG_DIR" # Wed, 23 Jun 2021 02:53:24 GMT RUN a2dismod mpm_event && a2enmod mpm_prefork # Wed, 23 Jun 2021 02:53:26 GMT RUN { echo '<FilesMatch \.php$>'; echo '\tSetHandler application/x-httpd-php'; echo '</FilesMatch>'; echo; echo 'DirectoryIndex disabled'; echo 'DirectoryIndex index.php index.html'; echo; echo '<Directory /var/www/>'; echo '\tOptions -Indexes'; echo '\tAllowOverride All'; echo '</Directory>'; } | tee "$APACHE_CONFDIR/conf-available/docker-php.conf" && a2enconf docker-php # Wed, 23 Jun 2021 02:53:27 GMT ENV PHP_EXTRA_BUILD_DEPS=apache2-dev # Wed, 23 Jun 2021 02:53:27 GMT ENV PHP_EXTRA_CONFIGURE_ARGS=--with-apxs2 --disable-cgi # Wed, 23 Jun 2021 02:53:27 GMT ENV PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 02:53:27 GMT ENV PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Wed, 23 Jun 2021 02:53:28 GMT ENV PHP_LDFLAGS=-Wl,-O1 -pie # Wed, 23 Jun 2021 02:53:28 GMT ENV GPG_KEYS=528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 39B641343D8C104B2B146DC3F9C39DC0B9698544 F1F692238FBC1666E5A5CCD4199F9DFEF6FFBAFD # Mon, 28 Jun 2021 19:20:36 GMT ENV PHP_VERSION=8.1.0alpha2 # Mon, 28 Jun 2021 19:20:36 GMT ENV PHP_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz PHP_ASC_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz.asc # Mon, 28 Jun 2021 19:20:36 GMT ENV PHP_SHA256=916e96eda029198134dd20e50a98b539d70ef204aa241e017c8b2c736222e4c6 # Mon, 28 Jun 2021 19:20:57 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr; rm -rf /var/lib/apt/lists/*; mkdir -p /usr/src; cd /usr/src; curl -fsSL -o php.tar.xz "$PHP_URL"; if [ -n "$PHP_SHA256" ]; then echo "$PHP_SHA256 *php.tar.xz" | sha256sum -c -; fi; if [ -n "$PHP_ASC_URL" ]; then curl -fsSL -o php.tar.xz.asc "$PHP_ASC_URL"; export GNUPGHOME="$(mktemp -d)"; for key in $GPG_KEYS; do gpg --batch --keyserver keyserver.ubuntu.com --recv-keys "$key"; done; gpg --batch --verify php.tar.xz.asc php.tar.xz; gpgconf --kill all; rm -rf "$GNUPGHOME"; fi; apt-mark auto '.*' > /dev/null; apt-mark manual $savedAptMark > /dev/null; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false # Mon, 28 Jun 2021 19:20:57 GMT COPY file:ce57c04b70896f77cc11eb2766417d8a1240fcffe5bba92179ec78c458844110 in /usr/local/bin/ # Mon, 28 Jun 2021 19:33:33 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends libargon2-dev libcurl4-openssl-dev libedit-dev libonig-dev libsodium-dev libsqlite3-dev libssl-dev libxml2-dev zlib1g-dev ${PHP_EXTRA_BUILD_DEPS:-} ; rm -rf /var/lib/apt/lists/*; export CFLAGS="$PHP_CFLAGS" CPPFLAGS="$PHP_CPPFLAGS" LDFLAGS="$PHP_LDFLAGS" ; docker-php-source extract; cd /usr/src/php; gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; debMultiarch="$(dpkg-architecture --query DEB_BUILD_MULTIARCH)"; if [ ! -d /usr/include/curl ]; then ln -sT "/usr/include/$debMultiarch/curl" /usr/local/include/curl; fi; ./configure --build="$gnuArch" --with-config-file-path="$PHP_INI_DIR" --with-config-file-scan-dir="$PHP_INI_DIR/conf.d" --enable-option-checking=fatal --with-mhash --with-pic --enable-ftp --enable-mbstring --enable-mysqlnd --with-password-argon2 --with-sodium=shared --with-pdo-sqlite=/usr --with-sqlite3=/usr --with-curl --with-libedit --with-openssl --with-zlib --with-pear $(test "$gnuArch" = 's390x-linux-gnu' && echo '--without-pcre-jit') --with-libdir="lib/$debMultiarch" ${PHP_EXTRA_CONFIGURE_ARGS:-} ; make -j "$(nproc)"; find -type f -name '*.a' -delete; make install; find /usr/local/bin /usr/local/sbin -type f -executable -exec strip --strip-all '{}' + || true; make clean; cp -v php.ini-* "$PHP_INI_DIR/"; cd /; docker-php-source delete; apt-mark auto '.*' > /dev/null; [ -z "$savedAptMark" ] || apt-mark manual $savedAptMark; find /usr/local -type f -executable -exec ldd '{}' ';' | awk '/=>/ { print $(NF-1) }' | sort -u | xargs -r dpkg-query --search | cut -d: -f1 | sort -u | xargs -r apt-mark manual ; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; pecl update-channels; rm -rf /tmp/pear ~/.pearrc; php --version # Mon, 28 Jun 2021 19:33:34 GMT COPY multi:e4407f0002276f00cc93b01e48696c1f677a5f7d3d194b3a84bec1cc5e733bcb in /usr/local/bin/ # Mon, 28 Jun 2021 19:33:36 GMT RUN docker-php-ext-enable sodium # Mon, 28 Jun 2021 19:33:36 GMT ENTRYPOINT ["docker-php-entrypoint"] # Mon, 28 Jun 2021 19:33:37 GMT STOPSIGNAL SIGWINCH # Mon, 28 Jun 2021 19:33:37 GMT COPY file:e3123fcb6566efa979f945bfac1c94c854a559d7b82723e42118882a8ac4de66 in /usr/local/bin/ # Mon, 28 Jun 2021 19:33:37 GMT WORKDIR /var/www/html # Mon, 28 Jun 2021 19:33:38 GMT EXPOSE 80 # Mon, 28 Jun 2021 19:33:38 GMT CMD ["apache2-foreground"] ``` - Layers: - `sha256:4b9d1870c33c63bfde89c401b4af9582fbbff99d4036171a7a456706bf805d6d` Last Modified: Wed, 23 Jun 2021 00:15:49 GMT Size: 25.8 MB (25812890 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:2c90d345f251f9a0ec80cf41b5f35febb67c1c989281d9e68b2aeefee1c00143` Last Modified: Wed, 23 Jun 2021 05:55:09 GMT Size: 227.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:d6bf25841fee636dffd0610ecca37bade0d96a921f21482eda088538659d329a` Last Modified: Wed, 23 Jun 2021 05:55:57 GMT Size: 61.4 MB (61404106 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:1b88a019f1da6587ce2665903b08be861bc197f91d09bfbfb6e62a368de4a231` Last Modified: Wed, 23 Jun 2021 05:55:08 GMT Size: 224.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:e208dcf88dd78c21b0c19c351345924790c3caa4bbca1580e2e289d738c874ab` Last Modified: Wed, 23 Jun 2021 05:56:42 GMT Size: 18.6 MB (18611849 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:7fe3845bbf14eccd94071a1ab8d234fe05503b03c7d92b53ed1643a1ca33d9a4` Last Modified: Wed, 23 Jun 2021 05:56:29 GMT Size: 436.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:f8ec3aa526d170c9dd2f45b8bd19f5f8f080e143f30ba8431c0e6d9105ec4d0c` Last Modified: Wed, 23 Jun 2021 05:56:29 GMT Size: 496.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:bdd270282d77f7bd72bd1969cea7885b07a966d1abff2e8421a3beec03203774` Last Modified: Mon, 28 Jun 2021 22:22:33 GMT Size: 11.6 MB (11633159 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:2bd3319a73bc192e911903ef2f6015608213b3efaa0fbfd39555cec75aa30f40` Last Modified: Mon, 28 Jun 2021 22:22:27 GMT Size: 492.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:23b699270f1e6f2e87b523cf186381bf3f1d61bc4722fdf96a1c62bf0e67d7a2` Last Modified: Mon, 28 Jun 2021 22:22:39 GMT Size: 13.8 MB (13755386 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:fe60d36671e78c25031f1857c1b270f50f444148d7e26166bbf2f848f71bd449` Last Modified: Mon, 28 Jun 2021 22:22:27 GMT Size: 2.3 KB (2279 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:37ae07058cc8991beec3aeca0f66445155dd406dab25a67006e1c7f58e217115` Last Modified: Mon, 28 Jun 2021 22:22:27 GMT Size: 247.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:acf3d981b6d76c31c851d2fda017c12e0ccfd6062cb42a8dd7951e417cd395e8` Last Modified: Mon, 28 Jun 2021 22:22:27 GMT Size: 897.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip ### `php:8.1.0alpha2-apache-buster` - linux; s390x ```console $ docker pull php@sha256:f4f640a3c4cce6a23fe18db31f3d9aee95a0845149f990da30ce46ada1af071b ``` - Docker Version: 20.10.7 - Manifest MIME: `application/vnd.docker.distribution.manifest.v2+json` - Total Size: **134.3 MB (134262472 bytes)** (compressed transfer size, not on-disk size) - Image ID: `sha256:d8ec605befb0838cbe0b92faee5692307ce64cd518f6ba5aca880ba0e894b564` - Entrypoint: `["docker-php-entrypoint"]` - Default Command: `["apache2-foreground"]` ```dockerfile # Tue, 22 Jun 2021 23:42:28 GMT ADD file:a53e5772eefa4592eeff989f279dcc870986db7207b419dc3ae61cae85fce41f in / # Tue, 22 Jun 2021 23:42:29 GMT CMD ["bash"] # Sat, 26 Jun 2021 00:09:50 GMT RUN set -eux; { echo 'Package: php*'; echo 'Pin: release *'; echo 'Pin-Priority: -1'; } > /etc/apt/preferences.d/no-debian-php # Sat, 26 Jun 2021 00:09:50 GMT ENV PHPIZE_DEPS=autoconf dpkg-dev file g++ gcc libc-dev make pkg-config re2c # Sat, 26 Jun 2021 00:10:11 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends $PHPIZE_DEPS ca-certificates curl xz-utils ; rm -rf /var/lib/apt/lists/* # Sat, 26 Jun 2021 00:10:15 GMT ENV PHP_INI_DIR=/usr/local/etc/php # Sat, 26 Jun 2021 00:10:16 GMT RUN set -eux; mkdir -p "$PHP_INI_DIR/conf.d"; [ ! -d /var/www/html ]; mkdir -p /var/www/html; chown www-data:www-data /var/www/html; chmod 777 /var/www/html # Sat, 26 Jun 2021 00:13:55 GMT ENV APACHE_CONFDIR=/etc/apache2 # Sat, 26 Jun 2021 00:13:55 GMT ENV APACHE_ENVVARS=/etc/apache2/envvars # Sat, 26 Jun 2021 00:14:06 GMT RUN set -eux; apt-get update; apt-get install -y --no-install-recommends apache2; rm -rf /var/lib/apt/lists/*; sed -ri 's/^export ([^=]+)=(.*)$/: ${\1:=\2}\nexport \1/' "$APACHE_ENVVARS"; . "$APACHE_ENVVARS"; for dir in "$APACHE_LOCK_DIR" "$APACHE_RUN_DIR" "$APACHE_LOG_DIR" ; do rm -rvf "$dir"; mkdir -p "$dir"; chown "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$dir"; chmod 777 "$dir"; done; rm -rvf /var/www/html/*; ln -sfT /dev/stderr "$APACHE_LOG_DIR/error.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/access.log"; ln -sfT /dev/stdout "$APACHE_LOG_DIR/other_vhosts_access.log"; chown -R --no-dereference "$APACHE_RUN_USER:$APACHE_RUN_GROUP" "$APACHE_LOG_DIR" # Sat, 26 Jun 2021 00:14:08 GMT RUN a2dismod mpm_event && a2enmod mpm_prefork # Sat, 26 Jun 2021 00:14:09 GMT RUN { echo '<FilesMatch \.php$>'; echo '\tSetHandler application/x-httpd-php'; echo '</FilesMatch>'; echo; echo 'DirectoryIndex disabled'; echo 'DirectoryIndex index.php index.html'; echo; echo '<Directory /var/www/>'; echo '\tOptions -Indexes'; echo '\tAllowOverride All'; echo '</Directory>'; } | tee "$APACHE_CONFDIR/conf-available/docker-php.conf" && a2enconf docker-php # Sat, 26 Jun 2021 00:14:09 GMT ENV PHP_EXTRA_BUILD_DEPS=apache2-dev # Sat, 26 Jun 2021 00:14:10 GMT ENV PHP_EXTRA_CONFIGURE_ARGS=--with-apxs2 --disable-cgi # Sat, 26 Jun 2021 00:14:10 GMT ENV PHP_CFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Sat, 26 Jun 2021 00:14:10 GMT ENV PHP_CPPFLAGS=-fstack-protector-strong -fpic -fpie -O2 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 # Sat, 26 Jun 2021 00:14:10 GMT ENV PHP_LDFLAGS=-Wl,-O1 -pie # Sat, 26 Jun 2021 00:14:11 GMT ENV GPG_KEYS=528995BFEDFBA7191D46839EF9BA0ADA31CBD89E 39B641343D8C104B2B146DC3F9C39DC0B9698544 F1F692238FBC1666E5A5CCD4199F9DFEF6FFBAFD # Mon, 28 Jun 2021 18:47:55 GMT ENV PHP_VERSION=8.1.0alpha2 # Mon, 28 Jun 2021 18:47:55 GMT ENV PHP_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz PHP_ASC_URL=https://downloads.php.net/~patrickallaert/php-8.1.0alpha2.tar.xz.asc # Mon, 28 Jun 2021 18:47:55 GMT ENV PHP_SHA256=916e96eda029198134dd20e50a98b539d70ef204aa241e017c8b2c736222e4c6 # Mon, 28 Jun 2021 18:48:04 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends gnupg dirmngr; rm -rf /var/lib/apt/lists/*; mkdir -p /usr/src; cd /usr/src; curl -fsSL -o php.tar.xz "$PHP_URL"; if [ -n "$PHP_SHA256" ]; then echo "$PHP_SHA256 *php.tar.xz" | sha256sum -c -; fi; if [ -n "$PHP_ASC_URL" ]; then curl -fsSL -o php.tar.xz.asc "$PHP_ASC_URL"; export GNUPGHOME="$(mktemp -d)"; for key in $GPG_KEYS; do gpg --batch --keyserver keyserver.ubuntu.com --recv-keys "$key"; done; gpg --batch --verify php.tar.xz.asc php.tar.xz; gpgconf --kill all; rm -rf "$GNUPGHOME"; fi; apt-mark auto '.*' > /dev/null; apt-mark manual $savedAptMark > /dev/null; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false # Mon, 28 Jun 2021 18:48:05 GMT COPY file:ce57c04b70896f77cc11eb2766417d8a1240fcffe5bba92179ec78c458844110 in /usr/local/bin/ # Mon, 28 Jun 2021 18:51:42 GMT RUN set -eux; savedAptMark="$(apt-mark showmanual)"; apt-get update; apt-get install -y --no-install-recommends libargon2-dev libcurl4-openssl-dev libedit-dev libonig-dev libsodium-dev libsqlite3-dev libssl-dev libxml2-dev zlib1g-dev ${PHP_EXTRA_BUILD_DEPS:-} ; rm -rf /var/lib/apt/lists/*; export CFLAGS="$PHP_CFLAGS" CPPFLAGS="$PHP_CPPFLAGS" LDFLAGS="$PHP_LDFLAGS" ; docker-php-source extract; cd /usr/src/php; gnuArch="$(dpkg-architecture --query DEB_BUILD_GNU_TYPE)"; debMultiarch="$(dpkg-architecture --query DEB_BUILD_MULTIARCH)"; if [ ! -d /usr/include/curl ]; then ln -sT "/usr/include/$debMultiarch/curl" /usr/local/include/curl; fi; ./configure --build="$gnuArch" --with-config-file-path="$PHP_INI_DIR" --with-config-file-scan-dir="$PHP_INI_DIR/conf.d" --enable-option-checking=fatal --with-mhash --with-pic --enable-ftp --enable-mbstring --enable-mysqlnd --with-password-argon2 --with-sodium=shared --with-pdo-sqlite=/usr --with-sqlite3=/usr --with-curl --with-libedit --with-openssl --with-zlib --with-pear $(test "$gnuArch" = 's390x-linux-gnu' && echo '--without-pcre-jit') --with-libdir="lib/$debMultiarch" ${PHP_EXTRA_CONFIGURE_ARGS:-} ; make -j "$(nproc)"; find -type f -name '*.a' -delete; make install; find /usr/local/bin /usr/local/sbin -type f -executable -exec strip --strip-all '{}' + || true; make clean; cp -v php.ini-* "$PHP_INI_DIR/"; cd /; docker-php-source delete; apt-mark auto '.*' > /dev/null; [ -z "$savedAptMark" ] || apt-mark manual $savedAptMark; find /usr/local -type f -executable -exec ldd '{}' ';' | awk '/=>/ { print $(NF-1) }' | sort -u | xargs -r dpkg-query --search | cut -d: -f1 | sort -u | xargs -r apt-mark manual ; apt-get purge -y --auto-remove -o APT::AutoRemove::RecommendsImportant=false; pecl update-channels; rm -rf /tmp/pear ~/.pearrc; php --version # Mon, 28 Jun 2021 18:51:44 GMT COPY multi:e4407f0002276f00cc93b01e48696c1f677a5f7d3d194b3a84bec1cc5e733bcb in /usr/local/bin/ # Mon, 28 Jun 2021 18:51:46 GMT RUN docker-php-ext-enable sodium # Mon, 28 Jun 2021 18:51:47 GMT ENTRYPOINT ["docker-php-entrypoint"] # Mon, 28 Jun 2021 18:51:47 GMT STOPSIGNAL SIGWINCH # Mon, 28 Jun 2021 18:51:48 GMT COPY file:e3123fcb6566efa979f945bfac1c94c854a559d7b82723e42118882a8ac4de66 in /usr/local/bin/ # Mon, 28 Jun 2021 18:51:48 GMT WORKDIR /var/www/html # Mon, 28 Jun 2021 18:51:49 GMT EXPOSE 80 # Mon, 28 Jun 2021 18:51:49 GMT CMD ["apache2-foreground"] ``` - Layers: - `sha256:d08eb187b3111e87e1b138f7b93df64c5470da613a64d0adc804e17e12aed4dc` Last Modified: Tue, 22 Jun 2021 23:45:45 GMT Size: 25.8 MB (25760716 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:61297595675dd5f94c60485ec6670e0d45420c73a569aebae232822f3805f5f4` Last Modified: Sat, 26 Jun 2021 02:18:36 GMT Size: 226.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:80ab5f68c432394e6815ad9808418b4300224b46b5898a0f90a1fedbfdf9ca7f` Last Modified: Sat, 26 Jun 2021 02:18:46 GMT Size: 64.7 MB (64710315 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:6def165c1dbb7cd43c8e70e00b2ec5aa53eae70056635c2ff93bdaf25ec061ef` Last Modified: Sat, 26 Jun 2021 02:18:36 GMT Size: 270.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:c0b3e7236868c26c00547364caef50791abcea8d5a62d4fac4ff00f1acf28308` Last Modified: Sat, 26 Jun 2021 02:19:14 GMT Size: 18.5 MB (18525085 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:8ae502a4e5daabc91e5f674004c64396c939ee72f05af0b913531fd51c79a37e` Last Modified: Sat, 26 Jun 2021 02:19:11 GMT Size: 472.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:10c27e0c3d22fb08edda2488324e9cbcd02f8ff31f5bad766bdd1470e2ea7048` Last Modified: Sat, 26 Jun 2021 02:19:11 GMT Size: 512.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:824063ee8dd8e5a85f74707bf68edaf9b3cd6c331e34eed6c89c9414583c61a7` Last Modified: Mon, 28 Jun 2021 21:04:18 GMT Size: 11.6 MB (11634294 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:b75e092617f5fbd682aa5e73a3c6a2e201fa59500c84cfb6ee464cfab1beeec9` Last Modified: Mon, 28 Jun 2021 21:04:15 GMT Size: 493.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:dea0e8d73f3ee62a929b61254ae90189404aff5591ea93b75032da7ca1e342ef` Last Modified: Mon, 28 Jun 2021 21:04:18 GMT Size: 13.6 MB (13626667 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:0a66121ad1cac398eff39de9073b1552eb58d6ff62141b476c6367ff6a13f0a8` Last Modified: Mon, 28 Jun 2021 21:04:15 GMT Size: 2.3 KB (2279 bytes) MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:3cb0bdec1c41f2c9e91c0d5759e3270e17c0a750548d547bc7cf489971065667` Last Modified: Mon, 28 Jun 2021 21:04:16 GMT Size: 247.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip - `sha256:256a6442b8d0d03ffa408557ddfdd2a33b1930edefa857eac2926fba941f1e07` Last Modified: Mon, 28 Jun 2021 21:04:15 GMT Size: 896.0 B MIME: application/vnd.docker.image.rootfs.diff.tar.gzip

74.004162

1,940

0.721899

yue_Hant

0.283449

d0d665751d3e83ee5b65b8554f0081d9e53035b5

20

md

Markdown

tms_rs/README.md

robotpilot/ros_tms

3d6b6579e89aa9cb216cd3cb6157fabc553c18f1

[ "BSD-3-Clause" ]

54

2015-01-06T06:58:28.000Z

2021-05-02T07:49:37.000Z

tms_rs/README.md

robotpilot/ros_tms

3d6b6579e89aa9cb216cd3cb6157fabc553c18f1

[ "BSD-3-Clause" ]

114

2015-01-07T06:42:21.000Z

2022-02-12T05:54:04.000Z

tms_rs/README.md

robotpilot/ros_tms

3d6b6579e89aa9cb216cd3cb6157fabc553c18f1

[ "BSD-3-Clause" ]

24

2015-03-27T08:35:59.000Z

2020-06-08T13:05:31.000Z

# TMS Robot Service

10

19

0.75

deu_Latn

0.562505

d0d6dac4f43e5d90ae9dfef199069fdb6226eb52

786

md

Markdown

Desktop/README.md

kurema/kBasicPrograms

6744ebc5663aa423f0a3d9d7c672737e0e724477

[ "MIT" ]

null

Desktop/README.md

kurema/kBasicPrograms

6744ebc5663aa423f0a3d9d7c672737e0e724477

[ "MIT" ]

null

Desktop/README.md

kurema/kBasicPrograms

6744ebc5663aa423f0a3d9d7c672737e0e724477

[ "MIT" ]

null

#携帯デスクトップ ##取扱説明書 ver 1.02 ###このソフトについてこのソフトは、携帯ベーシック上で、実行可能な簡易デスクトップ環境です。内部に複数の専用ソフトウェアを持ち、簡易ウィンドウ内で実行可能です。プログラミングの技術があれば、改造・内部ソフトウェアの追加が可能です（再配布は禁止です）。 ###インターフェイスについて直感的で分かりやすいユーザーインターフェイスです。 * 左ソフトキーでメニューの呼出しが可能です。 * 各内部ソフトに対応するキーを押せば、簡単に起動することができ、ウインドウが重なる様子を見ることができます。 * #（いげた）キーで全画面モードのオン・オフが可能です。 ※ウィンドウの移動・サイズ切り替えは不可能です。 ###内部ソフトウェアについて内部ソフトウェアには以下のものがあります。 * 画面テスト（1） * 三種類の画面描画テストが楽しめます。 * 簡易ＣＵＩ（2） * ＣＵＩの実行が可能です。 * 番号入力式のＣＵＩで、0番がヘルプ。 * 時間・情報・色表示等があります。 * 9番で終了後携帯デスクトップ本体の操作が可能です。 * 簡易時計（3） * アナログ時計です。 * 簡易電卓（5） * 簡易電卓です。 * 数字入力→選択（Ｆキー）→演算内容選択→選択→数字入力→選択。 * 四則演算、三角関数、メモリー計算等が出来ます。言語仕様により小数点以下が扱えないほか三角関数は百倍した値が返されます。 ###数字入力について数字キーで入力。上下キーで一ずつ増減、左キーで一桁削除。右キーで±変更。右ソフトキーでリセット。Ｆキーで決定。その他は随意割り当てです。 ###備考このソフトは、ボーダフォン環境下のtochiro氏の「携帯basic V」で動作確認しています。

22.457143

114

0.790076

jpn_Jpan

0.75823

d0d78f6f97f69b715ca482a93073ceb1edcf9582

12,851

md

Markdown

README.md

Jonzky/CSGOFloat

c1664190bcfded757be3c4d34abe977aea724d5a

[ "MIT" ]

null

README.md

Jonzky/CSGOFloat

c1664190bcfded757be3c4d34abe977aea724d5a

[ "MIT" ]

null

README.md

Jonzky/CSGOFloat

c1664190bcfded757be3c4d34abe977aea724d5a

[ "MIT" ]

null

<p align="center"> <a href="https://csgofloat.com/"> <img src="http://i.imgur.com/dzGQk7W.png"/> </a> </p> [![GitHub stars](https://img.shields.io/github/stars/Step7750/CSGOFloat.svg)](https://github.com/Step7750/CSGOFloat/stargazers) [![GitHub forks](https://img.shields.io/github/forks/Step7750/CSGOFloat.svg)](https://github.com/Step7750/CSGOFloat/network) [![GitHub issues](https://img.shields.io/github/issues/Step7750/CSGOFloat.svg)](https://github.com/Step7750/CSGOFloat/issues) [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/Step7750/CSGOFloat/LICENSE) [![Website](https://img.shields.io/website-up-down-green-red/https/csgofloat.com.svg)](https://csgofloat.com) [![Chrome Web Store](https://img.shields.io/chrome-web-store/d/jjicbefpemnphinccgikpdaagjebbnhg.svg)](https://chrome.google.com/webstore/detail/csgofloat-market-checker/jjicbefpemnphinccgikpdaagjebbnhg) [![Docker](https://img.shields.io/docker/pulls/step7750/csgofloat.svg)](https://hub.docker.com/r/step7750/csgofloat) CSGOFloat is a free and open source API service that allows you to obtain the float and paint seed of any CSGO item using its inspect link. ### Repo Links [CSGOFloat-Extension](https://github.com/Step7750/CSGOFloat-Extension) [CSGOFloat-Website](https://github.com/Step7750/CSGOFloat-Website) ## Table of Contents * [API](https://github.com/Step7750/CSGOFloat#api) * [`GET /`](https://github.com/Step7750/CSGOFloat#get-) * [Examples](https://github.com/Step7750/CSGOFloat#examples) * [`GET /` (Using an Inspect URL)](https://github.com/Step7750/CSGOFloat#get--using-an-inspect-url) * [Examples](https://github.com/Step7750/CSGOFloat#examples-1) * [Reply](https://github.com/Step7750/CSGOFloat#reply) * [Errors](https://github.com/Step7750/CSGOFloat#errors) * [How to Install](https://github.com/Step7750/CSGOFloat#how-to-install) * [Docker](https://github.com/Step7750/CSGOFloat#docker) * [Manual](https://github.com/Step7750/CSGOFloat#manual) * [Steps](https://github.com/Step7750/CSGOFloat#steps) * [How to First Login a Bot](https://github.com/Step7750/CSGOFloat#how-to-first-login-a-bot) * [Breaking Changes](https://github.com/Step7750/CSGOFloat#breaking-changes) * [Args](https://github.com/Step7750/CSGOFloat#args) # API **!! If you want to heavily use the public API, please host this repo yourself !!** ### `https://api.csgofloat.com` ### `GET /` Parameters s, a, d, m can be found in the inspect link of a csgo item. | Parameter | Description | |:-------------:|:-------------| | s | Optional: If an inventory item, fill out this parameter from the inspect URL | | a | Required: Inspect URL "a" param | | d | Required: Inspect URL "d" param | | m | Optional: If a market item, fill out this parameter from the inspect URL | ##### Examples `https://api.csgofloat.com/?m=563330426657599553&a=6710760926&d=9406593057029549017` `https://api.csgofloat.com/?s=76561198084749846&a=6777992090&d=3378412659870065794` ### `GET /` (Using an Inspect URL) | Parameter | Description | |:-------------:|:-------------| | url | Required: Inspect URL of the CSGO item | ##### Examples `https://api.csgofloat.com/?url=steam://rungame/730/76561202255233023/+csgo_econ_action_preview%20S76561198084749846A698323590D7935523998312483177` `https://api.csgofloat.com/?url=steam://rungame/730/76561202255233023/+csgo_econ_action_preview%20M625254122282020305A6760346663D30614827701953021` ### Reply The reply of this API is based upon [this CSGO protobuf](https://github.com/SteamDatabase/GameTracking-CSGO/blob/a00b71ec84b24e0773c5fbd595eb91e17fa57f8f/Protobufs/cstrike15_gcmessages.proto#L729). | Attribute | Data Type | Description | |:-------------:|:-------------:|:--------------| | itemid | uint32 | Item ID | | defindex | uint32 | Weapon ID | | paintindex | uint32 | Paint ID of the weapon (skin) | | rarity | uint32 | Rarity value of the weapon | | quality | uint32 | Quality of the weapon | | paintwear | uint32 | Wear of the exterior of the skin | | paintseed | uint32 | Seed for the RNG that defines how to place the skin texture | | killeatervalue | uint32 | If the item is StatTrak, this is the amount of kills | | customname | string | If the item has a nametag, this is the custom name | | stickers | array | Contains data on the placement of stickers | | origin | uint32 | Origin ID of the weapon | | floatvalue | float | Exterior wear of the skin in its float representation | | imageurl | string | Optional: Image of the item | | min | float | Minimum wear of the skin | | max | float | Maximum wear of the skin | | item_name | uint32 | Optional: Name of the skin | | weapon_type | string | Weapon type name | | origin_name | string | Origin name (Trade-Up, Dropped, etc...) | | quality_name | string | Quality name (Souvenir, Stattrak, etc...) | | rarity_name | string | Rarity name (Covert, Mil-Spec, etc...) | | wear_name | string | Wear name (Factory New, Minimal Wear, etc...) | | full_item_name | string | Full Item Name (ex. SSG 08 Blue Spruce (Minimal Wear)) | ```json { "iteminfo": { "accountid": null, "itemid": "13874827217", "defindex": 7, "paintindex": 282, "rarity": 5, "quality": 4, "paintseed": 361, "killeaterscoretype": null, "killeatervalue": null, "customname": null, "stickers": [], "inventory": 11, "origin": 8, "questid": null, "dropreason": null, "musicindex": null, "s": "0", "a": "13874827217", "d": "4649025583329100061", "m": "2608048286785948758", "floatvalue": 0.22740158438682556, "imageurl": "http://media.steampowered.com/apps/730/icons/econ/default_generated/weapon_ak47_cu_ak47_cobra_light_large.7494bfdf4855fd4e6a2dbd983ed0a243c80ef830.png", "min": 0.1, "max": 0.7, "weapon_type": "AK-47", "item_name": "Redline", "rarity_name": "Classified", "quality_name": "Unique", "origin_name": "Found in Crate", "wear_name": "Field-Tested", "full_item_name": "AK-47 | Redline (Field-Tested)" } } ``` ### `POST /bulk` Allows you to request the inspect link data for multiple items at once. NOTE: Ensure that you send proper `Content-Type: application/json` headers Request Body: ```json { "links": [ {"link": "steam://rungame/730/76561202255233023/+csgo_econ_action_preview%20M2906459769049600931A18971892678D9403672490970763167"}, {"link": "steam://rungame/730/76561202255233023/+csgo_econ_action_preview%20M2907585668964658722A17231546984D5353704955732169451"} ] } ``` Example Response: ```json { "18971892678": { "origin": 8, "quality": 4, "rarity": 5, "a": "18971892678", "d": "9403672490970763167", "paintseed": 49, "defindex": 7, "paintindex": 282, // STUB... }, "17231546984": { "origin": 4, "quality": 4, "rarity": 4, "a": "17231546984", "d": "5353704955732169451", "paintseed": 597, "defindex": 9, "paintindex": 838, // STUB... }, ... } ``` ### `GET /stats` Gives some data on the current status of your bots and queue. Example: ```json {"bots_online":100,"bots_total":100,"queue_size":20,"queue_concurrency":100} ``` ## Errors ##### Error Codes | Code | Description | |:-------------:|:-------------| | 1 | Improper Parameter Structure | | 2 | Invalid Inspect Link Structure | | 3 | You may only have X pending request(s) at a time | | 4 | Valve's servers didn't reply in time | | 5 | Valve's servers appear to be offline, please try again later! | | 6 | Something went wrong on our end, please try again | | 7 | Improper body format | | 8 | Bad Secret | ##### Example Error ```json { "error": "Valve's servers didn't reply in time", "code": 4 } ``` If using a `/bulk` request and the error only applies to a specific inspect link, the returned response for it will be replaced while other inspect links will be processed normally. If the error applies to the entire request (ie. bad post body), it will return a root-level error as shown above. Example: ``` { "18971892678": { "origin": 8, "quality": 4, "rarity": 5, "a": "18971892678", "d": "9403672490970763167", "paintseed": 49, "defindex": 7, "paintindex": 282, // STUB... }, "16231546984": { "error": "Valve's servers didn't reply in time", "code": 4, "status": 500 } } ``` # How to Install In order to retrieve float values for weapons in this way, you must have Steam account(s) with a copy of CS:GO. Each account can request 1 float per second. CSGOFloat allows you to have as many bots as you'd like by inputting the login info into config.js. Each instance of CSGOFloat can operate around 300 accounts. It is recommended to either configure a Postgres server or setup another cache such as Varnish or Nginx in front of your server. ## Docker Pull the [image](https://hub.docker.com/r/step7750/csgofloat) from docker and mount the config directory ``` docker pull step7750/csgofloat:latest docker run -d --name csgofloat -v /host/config:/config -p 80:80 -p 443:443 step7750/csgofloat:latest ``` The first time you start the docker container, it'll copy the `config.js` file to the config directory and stop. You'll need to edit this file and include your bots login information and then start the docker again. See the section [How to First Login a Bot](https://github.com/Step7750/CSGOFloat#how-to-first-login-a-bot) for further info. ## Manual Requires Node.js v8+! Clone the repo (or `npm install csgofloat`) and install the Node.js dependencies using `npm install` or `yarn install` in the root directory. #### Steps: 1. Copy `config.example.js` to `config.js` 2. Add your bot(s) login information to `config.js` 3. Edit `config.js` with your desired settings 4. Ensure Postgres is running if you've set it's database url 5. Run `node index.js` in the main directory 6. [How to First Login a Bot](https://github.com/Step7750/CSGOFloat#how-to-first-login-a-bot) 7. Navigate to the IP that the server is hosted on and query the API using the docs above! ## How to First Login a Bot **Note**: If the bot has never logged into the steam client before and doesn't have Mobile 2FA enabled (fresh account), you can just input the username and password and it should successfully log in without email 2FA If your bot doesn't own CS:GO, CSGOFloat will automatically try to obtain a license for it during startup. * Using Email 2FA * Only fill in the `user` and `pass` fields for the bot (make sure the `auth` field is empty or removed) * Start up CSGOFloat * It will tell you that an auth code was sent to your email * Input the code from your email into the `auth` field for the bot * Restart CSGOFloat * It should successfully login and create a sentry file in the current [node-steam-user config directory](https://github.com/DoctorMcKay/node-steam-user#datadirectory) * The `auth` field can now be optionally removed in your login file for further logins * Using Mobile 2FA * Fill in the `user` and `pass` fields for the bot * Fill in the `auth` field with the `shared_secret` for the bot * Start up CSGOFloat * It should successfully login and create a sentry file in the current [node-steam-user config directory](https://github.com/DoctorMcKay/node-steam-user#datadirectory) * You'll need to keep the `auth` field filled in for future logins ## Breaking Changes ### v3.0 -> v4.0 * MongoDB is no longer supported, use Postgres instead * Socket.io access is no longer supported * Built-in HTTPS handling has been removed, reverse proxy to HTTP instead ### v2.0 -> v3.0 * Since we now use node-steam-user instead of node-steam, the sentry folder location now [depends on your system](https://github.com/DoctorMcKay/node-steam-user#datadirectory). If you'd like to migrate sentry files from v2.0 rather than having to reauthenticate email 2FA accounts, you'll need to copy your sentry files and rename them to match node-steam-user's format * `allow_simultaneous_requests` has now been replaced by `max_simultaneous_requests`. You can set `max_simultaneous_requests` to `-1` to allow an infinite amount of simultaneous requests by the same IP. ## Args ### `-c`/`--config` (default `./config.js`) CSGOFloat config file location ### `-s`/`--steam_data` (default [node-steam-user config directory](https://github.com/DoctorMcKay/node-steam-user#datadirectory)) node-steam-user config directory

38.942424

369

0.683682

eng_Latn

0.749704

d0d8c49d8df0acb6729c1c00fb04a9445e8fd402

417

md

Markdown

README.md

border-radius/tnw

c03b85d073bf198c218717685e41e66a100a944a

[ "MIT" ]

null

README.md

border-radius/tnw

c03b85d073bf198c218717685e41e66a100a944a

[ "MIT" ]

null

README.md

border-radius/tnw

c03b85d073bf198c218717685e41e66a100a944a

[ "MIT" ]

null

# tnw get fresh autistic jokes right in your telegram ### Installation Clone https://github.com/border-radius/tnw repo and install dependencies with `npm install`. Create `config.json` like this: ```json { "mongodb": "mongodb://localhost/tnw", "token": "telegram_bot_token", "bnwtoken": "bnw_bot_token", "blacklist": [], "options": { "polling": 5 } } ``` Launch with `node index` or `npm start`

17.375

92

0.671463

eng_Latn

0.600945

d0d91d71292199d201ee2fea97a4e4af76edbe66

1,350

md

Markdown

it/restart/2021/passaporto-vaccinale-sicurezza-diritti.md

reale/eutopian.eu

7f360a5c67ec9559f0d408b2d956de4242df89d3

[ "BSD-3-Clause" ]

null

it/restart/2021/passaporto-vaccinale-sicurezza-diritti.md

reale/eutopian.eu

7f360a5c67ec9559f0d408b2d956de4242df89d3

[ "BSD-3-Clause" ]

null

it/restart/2021/passaporto-vaccinale-sicurezza-diritti.md

reale/eutopian.eu

7f360a5c67ec9559f0d408b2d956de4242df89d3

[ "BSD-3-Clause" ]

null

--- layout: page title: "Passaporto vaccinale tra sicurezza e diritti" lang: it ref: passaporto-vaccinale-sicurezza-diritti permalink: /it/restart/2021/passaporto-vaccinale-sicurezza-diritti cover: /assets/images/passaporto-vaccinale-sicurezza-diritti.png child_of_ref: restart-2021 --- PASSAPORTO VACCINALE: pur tra mille perplessità e distinguo l'Europa sembra orientata verso un accordo. Gli Stati Uniti nel frattempo passano da un'adesione entusiastica (con l'ordinanza di pugno di Biden) alla presa di coscienza di difficoltà normative e pratiche nell'implementazione concreta. Tra esigenze di tutela della privacy e di non-discriminazione, incognite sulla governance sanitaria e questioni tecniche di interoperabilità e cybersecurity, il panorama non è di facile decifrabilità. Come bilanciamo il diritto alla salute e il diritto alla privacy? Ne parliamo 16 marzo alle 20:00 con: * Andrea Danielli, imprenditore regtech, esperto di identità digitale * Diego Dimalta, presidente Privacy Network * Angelica Giambelluca, giornalista professionista in ambito medico e founder agenzia MEDORA * Nicola Marino, co-founder INTECH-Innovative Training Technologies * Enrica Massella Ducci Teri, Agenzia per l'Italia Digitale * Francesco Paolo Micozzi, avvocato cassazionista e professore di Informatica Giuridica, Università degli Studi di Perugia

54

295

0.825185

ita_Latn

0.989582

d0d95c28374a0704718abef3cb7b76783d07c3aa

74

md

Markdown

_posts/2015-03-05-lunch.md

itu-algorithms/algorithms.itu.dk

9a9f6b5488b30a5d719f9246ffa57ae42f9f44be

[ "MIT" ]

null

_posts/2015-03-05-lunch.md

itu-algorithms/algorithms.itu.dk

9a9f6b5488b30a5d719f9246ffa57ae42f9f44be

[ "MIT" ]

null

_posts/2015-03-05-lunch.md

itu-algorithms/algorithms.itu.dk

9a9f6b5488b30a5d719f9246ffa57ae42f9f44be

[ "MIT" ]

null

--- title: Joint lunch category: events place: 4A09 time: 12.15–13:00 ---

10.571429

18

0.675676

eng_Latn

0.701118

d0da0c0f6ce4da23ab626fc6e6f9e8c0d35cefc6

1,424

md

Markdown

dataset/cropweed/README.md

Brilhador/lacci

c45160c2dd534e1a788c3a1124c30170f9a247ce

[ "FSFAP" ]

null

dataset/cropweed/README.md

Brilhador/lacci

c45160c2dd534e1a788c3a1124c30170f9a247ce

[ "FSFAP" ]

3

2020-11-13T17:46:16.000Z

2022-02-09T23:44:59.000Z

dataset/cropweed/README.md

Brilhador/lacci

c45160c2dd534e1a788c3a1124c30170f9a247ce

[ "FSFAP" ]

null

A Crop/Weed Field Image Dataset ============= The Crop/Weed Field Image Dataset (CWFID) accompanies the following publication: "Sebastian Haug, Jörn Ostermann: A Crop/Weed Field Image Dataset for the Evaluation of Computer Vision Based Precision Agriculture Tasks, [CVPPP 2014](http://www.plant-phenotyping.org/CVPPP2014) Workshop, [ECCV 2014](http://eccv2014.org)" This dataset comprises field [images](images), vegetation segmentation [masks](masks) and crop/weed plant type [annotations](annotations). The paper provides details, e.g. on the field setting, acquisition conditions, image and ground truth data format. You can download the complete dataset here: [Download CWFID](http://github.com/cwfid/dataset/releases). Paper ----- Paper available [here](http://rd.springer.com/chapter/10.1007%2F978-3-319-16220-1_8). Bibtex: ``` @inproceedings{haug15, author={Haug, Sebastian and Ostermann, J{\"o}rn}, title={A Crop/Weed Field Image Dataset for the Evaluation of Computer Vision Based Precision Agriculture Tasks}, year={2015}, booktitle={Computer Vision - ECCV 2014 Workshops}, doi={10.1007/978-3-319-16220-1_8}, url={http://dx.doi.org/10.1007/978-3-319-16220-1_8}, pages={105--116}, } ``` Use --- All data is subject to copyright and may only be used for non-commercial research. In case of use please cite our publication. Contact Sebastian Haug ([email protected]) for any questions.

44.5

319

0.752809

eng_Latn

0.645571

d0da108ca393064b52699aafa890829971b322d1

583

md

Markdown

posts/post-607.md

chrisnager/give-n-go

0f902c8fdd94adcb87466f35ef7ccd8f840df946

[ "Unlicense", "MIT" ]

1

2019-04-30T22:52:40.000Z

posts/post-607.md

chrisnager/give-n-go

0f902c8fdd94adcb87466f35ef7ccd8f840df946

[ "Unlicense", "MIT" ]

null

posts/post-607.md

chrisnager/give-n-go

0f902c8fdd94adcb87466f35ef7ccd8f840df946

[ "Unlicense", "MIT" ]

null

--- type: photo state: queue source: https://d13yacurqjgara.cloudfront.net/users/49803/screenshots/1982200/solareclipse.gif link: https://dribbble.com/shots/1982200-Solar-Eclipse tags: illustrations, loaders id: '122776046092' --- <p data-height="332" data-theme-id="6516" data-slug-hash="oXpBeN" data-default-tab="result" data-user="zerobrainwash" class='codepen'><a href='http://codepen.io/zerobrainwash/pen/oXpBeN/'>Solar Eclipse</a> by Karolis (<a href='http://codepen.io/zerobrainwash'>@zerobrainwash</a>) on <a href='http://codepen.io'>CodePen</a> and Dribbble inspiration</p>

58.3

351

0.754717

yue_Hant

0.182284

d0dadacc98f138c814a5d5b1d397a0455359dfbd

15,755

md

Markdown

README.md

gvssr/adaptive-lighting

57a032f2830b0a09f62cbb344bcf489bc528b6bd

[ "Apache-2.0" ]

513

2020-09-26T19:44:15.000Z

2022-03-31T19:59:11.000Z

README.md

gvssr/adaptive-lighting

57a032f2830b0a09f62cbb344bcf489bc528b6bd

[ "Apache-2.0" ]

233

2020-10-05T08:31:05.000Z

2022-03-28T17:49:57.000Z

README.md

gvssr/adaptive-lighting

57a032f2830b0a09f62cbb344bcf489bc528b6bd

[ "Apache-2.0" ]

77

2020-10-13T22:33:41.000Z

2022-03-18T10:44:03.000Z

[![hacs_badge](https://img.shields.io/badge/HACS-Default-orange.svg)](https://github.com/custom-components/hacs) ![Version](https://img.shields.io/github/v/release/basnijholt/adaptive-lighting) # Adaptive Lighting component for Home Assistant ![](https://github.com/home-assistant/brands/raw/b4a168b9af282ef916e120d31091ecd5e3c35e66/core_integrations/adaptive_lighting/icon.png) _Try out this code by adding https://github.com/basnijholt/adaptive-lighting to your custom repos in [HACS (Home Assistant Community Store)](https://hacs.xyz/) and install it!_ The `adaptive_lighting` platform changes the settings of your lights throughout the day. It uses the position of the sun to calculate the color temperature and brightness that is most fitting for that time of the day. Scientific research has shown that this helps to maintain your natural circadian rhythm (your biological clock) and might lead to improved sleep, mood, and general well-being. In practical terms, this means that after the sun sets, the brightness of your lights will decrease to a certain minimum brightness, while the color temperature will be at its coolest color temperature at noon, after which it will decrease and reach its warmest color at sunset. Around sunrise, the opposite will happen. Additionally, the integration provides a way to define and set your lights in "sleep mode". When "sleep mode" is enabled, the lights will be at a minimal brightness and have a very warm color. The integration creates 4 switches (in this example the component's name is `"living_room"`): 1. `switch.adaptive_lighting_living_room`, which turns the Adaptive Lighting integration on or off. It has several attributes that show the current light settings. 2. `switch.adaptive_lighting_sleep_mode_living_room`, which when activated, turns on "sleep mode" (you can set a specific `sleep_brightness` and `sleep_color_temp`). 3. `switch.adaptive_lighting_adapt_brightness_living_room`, which sets whether the integration should adapt the brightness of the lights (if supported by the light). 4. `switch.adaptive_lighting_adapt_color_living_room`, which sets whether the integration should adapt the color of the lights (if supported by the light). ## Taking back control Although having your lights automatically adapt is great most of the time, there might be times at which you want to set the lights to a different color/brightness and keep it that way. For this purpose, the integration (when `take_over_control` is enabled) automatically detects whether someone (e.g., person toggling the light switch) or something (automation) changes the lights. If this happens *and* the light is already on, the light that was changed gets marked as "manually controlled" and the Adaptive Lighting component will stop adapting that light until it turns off and on again (or if you use the service call `adaptive_lighting.set_manual_control`). This mechanism works by listening to all `light.turn_on` calls that change the color or brightness and by noting that the component did not make the call. Additionally, there is an option to detect all state changes (when `detect_non_ha_changes` is enabled), so also changes to the lights that were not made by a `light.turn_on` call (e.g., through an app or via something outside of Home Assistant.) It does this by comparing a light's state to Adaptive Lighting's previously used settings. Whenever a light gets marked as "manually controlled", an `adaptive_lighting.manual_control` event is fired, such that one can use this information in automations. ## Configuration This integration is both fully configurable through YAML _and_ the frontend. (**Configuration** -> **Integrations** -> **Adaptive Lighting**, **Adaptive Lighting** -> **Options**) Here, the options in the frontend and in YAML have the same names. ```yaml # Example configuration.yaml entry adaptive_lighting: lights: - light.living_room_lights ``` ### Options | option | description | required | default | type | |-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------|---------| | name | The name to use when displaying this switch. | False | default | string | | lights | List of light entities for Adaptive Lighting to control (may be empty). | False | list | [] | | prefer_rgb_color | Whether to use RGB color adjustment instead of native light color temperature. | False | False | boolean | | initial_transition | How long the first transition is when the lights go from `off` to `on`. | False | 1 | time | | sleep_transition | How long the transition is when when "sleep mode" is toggled | False | 1 | time | | transition | How long the transition is when the lights change, in seconds. | False | 45 | integer | | interval | How often to adapt the lights, in seconds. | False | 90 | integer | | min_brightness | The minimum percent of brightness to set the lights to. | False | 1 | integer | | max_brightness | The maximum percent of brightness to set the lights to. | False | 100 | integer | | min_color_temp | The warmest color temperature to set the lights to, in Kelvin. | False | 2000 | integer | | max_color_temp | The coldest color temperature to set the lights to, in Kelvin. | False | 5500 | integer | | sleep_brightness | Brightness of lights while the sleep mode is enabled. | False | 1 | integer | | sleep_color_temp | Color temperature of lights while the sleep mode is enabled. | False | 1000 | integer | | sunrise_time | Override the sunrise time with a fixed time. | False | time | | | sunrise_offset | Change the sunrise time with a positive or negative offset. | False | 0 | time | | sunset_time | Override the sunset time with a fixed time. | False | time | | | sunset_offset | Change the sunset time with a positive or negative offset. | False | 0 | time | | only_once | Whether to keep adapting the lights (false) or to only adapt the lights as soon as they are turned on (true). | False | False | boolean | | take_over_control | If another source calls `light.turn_on` while the lights are on and being adapted, disable Adaptive Lighting. | False | True | boolean | | detect_non_ha_changes | Whether to detect state changes and stop adapting lights, even not from `light.turn_on`. Needs `take_over_control` to be enabled. Note that by enabling this option, it calls 'homeassistant.update_entity' every 'interval'! | False | False | boolean | | separate_turn_on_commands | Whether to use separate `light.turn_on` calls for color and brightness, needed for some types of lights | False | False | boolean | Full example: ```yaml # Example configuration.yaml entry adaptive_lighting: - name: "default" lights: [] prefer_rgb_color: false transition: 45 initial_transition: 1 interval: 90 min_brightness: 1 max_brightness: 100 min_color_temp: 2000 max_color_temp: 5500 sleep_brightness: 1 sleep_color_temp: 1000 sunrise_time: "08:00:00" # override the sunrise time sunrise_offset: sunset_time: sunset_offset: 1800 # in seconds or '00:15:00' take_over_control: true detect_non_ha_changes: false only_once: false ``` ### Services `adaptive_lighting.apply` applies Adaptive Lighting settings to lights on demand. | Service data attribute | Optional | Description | |---------------------------|----------|-------------------------------------------------------------------------| | `entity_id` | no | The `entity_id` of the switch with the settings to apply. | | `lights` | no | A light (or list of lights) to apply the settings to. | | `transition` | yes | The number of seconds for the transition. | | `adapt_brightness` | yes | Whether to change the brightness of the light or not. | | `adapt_color` | yes | Whether to adapt the color on supporting lights. | | `prefer_rgb_color` | yes | Whether to prefer RGB color adjustment over of native light color temperature when possible. | | `turn_on_lights` | yes | Whether to turn on lights that are currently off. | `adaptive_lighting.set_manual_control` can mark (or unmark) whether a light is "manually controlled", meaning that when a light has `manual_control`, the light is not adapted. | Service data attribute | Optional | Description | |------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------| | `entity_id` | no | The `entity_id` of the switch in which to (un)mark the light as being "manually controlled". | | `lights` | yes | entity_id(s) of lights, if not specified, all lights in the switch are selected. | | `manual_control` | yes | Whether to add ('true') or remove ('false') the light from the 'manual_control' list, default: true | ## Automation examples Reset the `manual_control` status of a light after an hour. ```yaml - alias: "Adaptive lighting: reset manual_control after 1 hour" mode: parallel trigger: platform: event event_type: adaptive_lighting.manual_control variables: light: "{{ trigger.event.data.entity_id }}" switch: "{{ trigger.event.data.switch }}" action: - delay: "01:00:00" - condition: template value_template: "{{ light in state_attr(switch, 'manual_control') }}" - service: adaptive_lighting.set_manual_control data: entity_id: "{{ switch }}" lights: "{{ light }}" manual_control: false ``` Toggle multiple Adaptive Lighting switches to "sleep mode" using an `input_boolean.sleep_mode`. ```yaml - alias: "Adaptive lighting: toggle 'sleep mode'" trigger: - platform: state entity_id: input_boolean.sleep_mode - platform: homeassistant event: start # in case the states aren't properly restored variables: sleep_mode: "{{ states('input_boolean.sleep_mode') }}" action: service: "switch.turn_{{ sleep_mode }}" entity_id: - switch.adaptive_lighting_sleep_mode_living_room - switch.adaptive_lighting_sleep_mode_bedroom ``` # Other See the documentation of the PR at https://deploy-preview-14877--home-assistant-docs.netlify.app/integrations/adaptive_lighting/ and [this video on Reddit](https://www.reddit.com/r/homeassistant/comments/jabhso/ha_has_it_before_apple_has_even_finished_it_i/) to see how to add the integration and set the options. This integration was originally based of the great work of @claytonjn https://github.com/claytonjn/hass-circadian_lighting, but has been 100% rewritten and extended with new features. # Having problems? Please enable debug logging by putting this in `configuration.yaml`: ```yaml logger: default: warning logs: custom_components.adaptive_lighting: debug ``` and after the problem occurs please create an issue with the log (`/config/home-assistant.log`). ### Graphs! These graphs were generated using the values calculated by the Adaptive Lighting sensor/switch(es). ##### Sun Position: ![cl_percent|690x131](https://community-home-assistant-assets.s3.dualstack.us-west-2.amazonaws.com/original/3X/6/5/657ff98beb65a94598edeb4bdfd939095db1a22c.PNG) ##### Color Temperature: ![cl_color_temp|690x129](https://community-home-assistant-assets.s3.dualstack.us-west-2.amazonaws.com/original/3X/5/9/59e84263cbecd8e428cb08777a0413672c48dfcd.PNG) ##### Brightness: ![cl_brightness|690x130](https://community-home-assistant-assets.s3.dualstack.us-west-2.amazonaws.com/original/3X/5/8/58ebd994b62a8b1abfb3497a5288d923ff4e2330.PNG) # Maintainers - @basnijholt - @RubenKelevra

79.570707

313

0.533481

eng_Latn

0.988062

d0db525538f784ab335838ac6d6f5637f2865897

8,586

md

Markdown

articles/app-service/quickstart-dotnet-framework.md

macdrai/azure-docs.fr-fr

59bc35684beaba04a4f4c09a745393e1d91428db

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

null

articles/app-service/quickstart-dotnet-framework.md

macdrai/azure-docs.fr-fr

59bc35684beaba04a4f4c09a745393e1d91428db

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

null

articles/app-service/quickstart-dotnet-framework.md

macdrai/azure-docs.fr-fr

59bc35684beaba04a4f4c09a745393e1d91428db

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

null

--- title: 'Démarrage rapide : Créer une application C# ASP.NET' description: Découvrez comment exécuter des applications web dans Azure App Service en déployant le modèle d’application web C# ASP.NET par défaut à partir de Visual Studio. ms.assetid: 04a1becf-7756-4d4e-92d8-d9471c263d23 ms.topic: quickstart ms.date: 11/20/2020 ms.custom: devx-track-csharp, mvc, devcenter, seodec18 ms.openlocfilehash: a4f7ba288bc27d6079deea9caf0ea315a55d0745 ms.sourcegitcommit: 6a770fc07237f02bea8cc463f3d8cc5c246d7c65 ms.translationtype: HT ms.contentlocale: fr-FR ms.lasthandoff: 11/24/2020 ms.locfileid: "96004053" --- # <a name="create-an-aspnet-framework-web-app-in-azure"></a>Créer une application web ASP.NET Framework dans Azure [Azure App Service](overview.md) offre un service d’hébergement web hautement évolutif appliquant des mises à jour correctives automatiques. Ce guide de démarrage rapide montre comment déployer votre première application web ASP.NET sur Azure App Service. Une fois que vous avez terminé, vous disposez d’un plan App Service. Vous disposez également d’une application App Service et d’une application web déployée. [!INCLUDE [quickstarts-free-trial-note](../../includes/quickstarts-free-trial-note.md)] ## <a name="prerequisites"></a>Prérequis Pour effectuer ce tutoriel, installez <a href="https://www.visualstudio.com/downloads/" target="_blank">Visual Studio 2019</a> avec la charge de travail **Développement web et ASP.NET**. Si vous avez déjà installé Visual Studio 2019 : - Installez les dernières mises à jour dans Visual Studio en sélectionnant **Aide** > **Rechercher les mises à jour**. - Ajoutez la charge de travail en sélectionnant **Outils** > **Obtenir des outils et des fonctionnalités**. ## <a name="create-an-aspnet-web-app"></a>Créer une application web ASP.NET <a name="create-and-publish-the-web-app"></a> Créez une application web ASP.NET en effectuant les étapes suivantes : 1. Ouvrez Visual Studio, puis sélectionnez **Créer un projet**. 2. Dans **Créer un projet**, recherchez et choisissez **Application web ASP.NET (.NET Framework)** , puis sélectionnez **Suivant**. 3. Dans **Configurer votre nouveau projet**, nommez l’application _myFirstAzureWebApp_, puis sélectionnez **Create (Créer)** . ![Configurer votre projet d’application web](./media/quickstart-dotnet-framework/configure-web-app-project-framework.png) 4. Vous pouvez déployer n’importe quel type d’application web ASP.NET dans Azure. Pour ce guide de démarrage rapide, choisissez le modèle **MVC**. 5. Vérifiez que l’option d’authentification a la valeur **Aucune authentification**. Sélectionnez **Create** (Créer). ![Créer une application web ASP.NET](./media/quickstart-dotnet-framework/select-mvc-template-vs2019.png) 6. Dans le menu Visual Studio, sélectionnez **Déboguer** > **Démarrer sans débogage** pour exécuter l’application web localement. ![Exécuter l’application localement](./media/quickstart-dotnet-framework/local-web-app.png) ## <a name="publish-your-web-app"></a>Publier votre application web <a name="launch-the-publish-wizard"></a> 1. Dans l’**Explorateur de solutions**, cliquez avec le bouton droit sur le projet **myFirstAzureWebApp**, puis sélectionnez **Publier**. 1. Dans **Publier**, sélectionnez **Azure** et cliquez sur **Suivant**. 1. Sélectionnez **Azure App Service (Windows)** et cliquez sur **Suivant**.  1. Vos options varient si vous êtes déjà connecté à Azure et si vous avez un compte Visual Studio lié à un compte Azure. Sélectionnez **Ajouter un compte** ou **Connexion** pour vous connecter à votre abonnement Azure. Si vous êtes déjà connecté, sélectionnez le compte souhaité. ![Connexion à Azure](./media/quickstart-dotnet-framework/sign-in-azure-framework-vs2019.png) [!INCLUDE [resource group intro text](../../includes/resource-group.md)] 1. À droite de **Instances d’App Service**, cliquez sur **+** . ![Nouvelle application App Service](./media/quickstart-dotnet-framework/publish-new-app-service.png) 1. Pour **Groupe de ressources**, sélectionnez **Nouveau**. 1. Dans **Nouveau nom du groupe de ressources**, entrez *myResourceGroup*, puis sélectionnez **OK**. [!INCLUDE [app-service-plan](../../includes/app-service-plan.md)] 1. Pour **Plan d’hébergement**, sélectionnez **Nouveau**. 1. Dans la boîte de dialogue **Plan d’hébergement**, entrez les valeurs du tableau suivant, puis sélectionnez **OK**. | Paramètre | Valeur suggérée | Description | |-|-|-| | Plan d’hébergement| myAppServicePlan | Nom du plan App Service. | | Emplacement | Europe Ouest | Centre de données dans lequel l’application web est hébergée. | | Taille | Gratuit | Le [niveau tarifaire](https://azure.microsoft.com/pricing/details/app-service/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio) détermine les fonctionnalités d’hébergement. | ![Créer un plan App Service](./media/quickstart-dotnet-framework/app-service-plan-framework-vs2019.png) 1. Dans **Nom**, entrez un nom d’application unique qui inclut uniquement les caractères valides `a-z`, `A-Z`, `0-9` et `-`. Vous pouvez accepter le nom unique généré automatiquement. L’URL de l’application web est `http://<app-name>.azurewebsites.net`, où `<app-name>` est le nom de votre application. 2. Sélectionnez **Créer** pour créer les ressources Azure. ![Configurer le nom de l’application](./media/quickstart-dotnet-framework/web-app-name-framework-vs2019.png) Une fois l’Assistant terminé, les ressources Azure sont créées pour vous et vous êtes prêt à publier. 3. Sélectionnez **Terminer** pour fermer l’Assistant. 3. Dans la page **Publier**, cliquez sur **Publier**. Visual Studio génère, empaquète et publie l’application sur Azure, puis la démarre dans le navigateur par défaut. ![Application web ASP.NET publiée dans Azure](./media/quickstart-dotnet-framework/published-azure-web-app.png) Le nom d’application spécifié dans la page **Créer un App Service** est utilisé en tant que préfixe d’URL au format `http://<app-name>.azurewebsites.net`. **Félicitations !** Votre application web ASP.NET s’exécute en temps réel dans Azure App Service. ## <a name="update-the-app-and-redeploy"></a>Mise à jour de l’application et redéploiement 1. Dans l’**Explorateur de solutions**, sous votre projet, ouvrez **Vues** > **Accueil** > **Index.cshtml**. 1. Recherchez la balise HTML `<div class="jumbotron">` vers le début, puis remplacez la totalité de l’élément par le code suivant : ```html <div class="jumbotron"> <h1>ASP.NET in Azure!</h1> <p class="lead">This is a simple app that we've built that demonstrates how to deploy a .NET app to Azure App Service.</p> </div> ``` 1. Pour effectuer un redéploiement dans Azure, cliquez avec le bouton droit sur le projet **myFirstAzureWebApp** dans **l’Explorateur de solutions**, puis sélectionnez **Publier**. Sélectionnez ensuite **Publier**. Une fois la publication terminée, Visual Studio lance un navigateur en accédant à l’URL de l’application web. ![Application web ASP.NET mise à jour dans Azure](./media/quickstart-dotnet-framework/updated-azure-web-app.png) ## <a name="manage-the-azure-app"></a>Gérer l’application Azure 1. Pour gérer l’application web, accédez au [Portail Azure](https://portal.azure.com), puis recherchez et sélectionnez **App Services**. ![Sélectionner App Services](./media/quickstart-dotnet-framework/app-services.png) 2. Dans la page **App Services**, sélectionnez le nom de votre application web. ![Navigation au sein du portail pour accéder à l’application Azure](./media/quickstart-dotnet-framework/access-portal-framework-vs2019.png) Vous voyez apparaître la page Vue d’ensemble de votre application web. Ici, vous pouvez effectuer des tâches de gestion de base, par exemple parcourir, arrêter, démarrer, redémarrer et supprimer. ![Vue d’ensemble d’App Service dans le portail Azure](./media/quickstart-dotnet-framework/web-app-general-framework-vs2019.png) Le menu de gauche fournit différentes pages vous permettant de configurer votre application. [!INCLUDE [Clean-up section](../../includes/clean-up-section-portal.md)] ## <a name="next-steps"></a>Étapes suivantes > [!div class="nextstepaction"] > [ASP.NET avec SQL Database](app-service-web-tutorial-dotnet-sqldatabase.md) > [!div class="nextstepaction"] > [Configurer une application ASP.NET](configure-language-dotnet-framework.md)

55.753247

302

0.751805

fra_Latn

0.885283

d0dbe0285b4a4deef3c36edde20d1ff48b7b70b1

179

md

Markdown

{{cookiecutter.project_name}}/docs/src/api_reference/client.md

TvanMeer/cookiecutter-python-package

4ffbe8658bbd371f3e505ba389f02dbe9c1d74f1

[ "MIT" ]

null

{{cookiecutter.project_name}}/docs/src/api_reference/client.md

TvanMeer/cookiecutter-python-package

4ffbe8658bbd371f3e505ba389f02dbe9c1d74f1

[ "MIT" ]

null

{{cookiecutter.project_name}}/docs/src/api_reference/client.md

TvanMeer/cookiecutter-python-package

4ffbe8658bbd371f3e505ba389f02dbe9c1d74f1

[ "MIT" ]

null

# Client Inline documentation from the `Client` class is rendered here. ```{eval-rst} .. autoclass:: {{cookiecutter.project_name}}.client.Client :members: :noindex: ```

17.9

62

0.687151

eng_Latn

0.852306

d0dcb57c388c81f7737cf3becceccbff67796752

2,547

md

Markdown

data/README.md

fkakuma/ofaci-inst

8ac3c05e8de21bbad67f88c64dade8a77d316e7e

[ "Apache-2.0" ]

null

data/README.md

fkakuma/ofaci-inst

8ac3c05e8de21bbad67f88c64dade8a77d316e7e

[ "Apache-2.0" ]

null

data/README.md

fkakuma/ofaci-inst

8ac3c05e8de21bbad67f88c64dade8a77d316e7e

[ "Apache-2.0" ]

null

Data Repository Example for OpenStack External Testing ====================================================== This is an example Data Repository to use with OpenStack External Testing Platform Installer. DO NOT fork this repository. It is intended to be copied to some private location (possibly a private GitHub repository, possibly somewhere else private in your organization). This repository will contain private SSH keys and other sensitive information. Manual Instructions ------------------- Follow these manual instructions to get your data repository set up: 1. Copy the repository somewhere private. 2. Copy the **private** SSH key that you submitted when you registered with the upstream OpenStack Infrastructure team into somewhere in this repo. 3. Create an SSH key pair that you will use for Jenkins. This SSH key pair will live in the `/var/lib/jenkins/.ssh/` directory on the master Jenkins host, and it will be added to the `/home/jenkins/.ssh/authorized_keys` file of all slave hosts:: ssh-keygen -t rsa -b 1024 -N '' -f jenkins_key Once you do the above, copy the `jenkins_key` and `jenkins_key.pub` files into your data repository. 4. Open up `vars.sh` in an editor. 5. Change the value of the `$UPSTREAM_GERRIT_USER` shell variable to the Gerrit username you registered with the upstream OpenStack Infrastructure team [as detailed in these instructions](http://ci.openstack.org/third_party.html#requesting-a-service-account) 6. Change the value of the `$UPSTREAM_GERRIT_SSH_KEY_PATH` shell variable to the **relative** path of the private SSH key file you copied into the repository in step #2. For example, let's say you put your private SSH key file named `mygerritkey` into a directory called `ssh` within the repository, you would set the `$UPSTREAM_GERRIT_SSH_KEY_PATH` value to `ssh/mygerritkey` 7. If for some reason, in step #3 above, you either used a different output filename than `jenkins_key` or put the key pair into some subdirectory of your data repository, then change the value of the `$JENKINS_SSH_KEY_PATH` variable in `vars.sh` to an appropriate value. 8. Change the value of the `$PUBLISH_HOST` to the host (without https:// prefix) you will publish job artifacts to. 9. Examine the files in `etc/jenkins_jobs/config` and modify as you need. Refer to this blog post for more information. 10. Example the `etc/zuul/layout.yaml` file and ensure you set up each upstream project that your testing system intends to run Jenkins jobs for.

45.482143

114

0.749117

eng_Latn

0.99374

d0dd859d6bc5daf2e25c82cf5c7299c53f18beba

640

md

Markdown

api/Word.DropDown.Value.md

ahkon/VBA-Docs

c047d7975de2b0949b496af150d279c505a8595b

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

4

2019-09-07T04:44:48.000Z

2021-12-16T15:05:50.000Z

api/Word.DropDown.Value.md

ahkon/VBA-Docs

c047d7975de2b0949b496af150d279c505a8595b

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

1

2021-06-13T09:32:15.000Z

api/Word.DropDown.Value.md

ahkon/VBA-Docs

c047d7975de2b0949b496af150d279c505a8595b

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

1

2021-06-23T03:40:08.000Z

--- title: DropDown.Value property (Word) keywords: vbawd10.chm153419778 f1_keywords: - vbawd10.chm153419778 ms.prod: word api_name: - Word.DropDown.Value ms.assetid: 9777996d-4e60-f528-6dcd-c4da3b77dff8 ms.date: 06/08/2017 localization_priority: Normal --- # DropDown.Value property (Word) Returns or sets the number of the selected item in a drop-down form field. Read/write **Long**. ## Syntax _expression_.**Value** _expression_ Required. A variable that represents a '[DropDown](Word.DropDown.md)' object. ## See also [DropDown Object](Word.DropDown.md) [!include[Support and feedback](~/includes/feedback-boilerplate.md)]

20

96

0.757813

eng_Latn

0.67011

d0de12d58f9daaa5b39abae0be39b326f3c624fb

9,636

md

Markdown

README.md

mikhailv/cleanenv

ce3ee7fb74f018e1dc0f302520bba3c44ce2f786

[ "MIT" ]

1

2020-08-03T07:38:07.000Z

README.md

mikhailv/cleanenv

ce3ee7fb74f018e1dc0f302520bba3c44ce2f786

[ "MIT" ]

null

README.md

mikhailv/cleanenv

ce3ee7fb74f018e1dc0f302520bba3c44ce2f786

[ "MIT" ]

null

![Clean Env](logo.svg) # Clean Env Minimalistic configuration reader [![Mentioned in Awesome Go](https://awesome.re/mentioned-badge.svg)](https://github.com/avelino/awesome-go) [![GoDoc](https://godoc.org/github.com/ilyakaznacheev/cleanenv?status.svg)](https://godoc.org/github.com/ilyakaznacheev/cleanenv) [![Go Report Card](https://goreportcard.com/badge/github.com/ilyakaznacheev/cleanenv)](https://goreportcard.com/report/github.com/ilyakaznacheev/cleanenv) [![Coverage Status](https://codecov.io/github/ilyakaznacheev/cleanenv/coverage.svg?branch=master)](https://codecov.io/gh/ilyakaznacheev/cleanenv) [![Build Status](https://travis-ci.org/ilyakaznacheev/cleanenv.svg?branch=master)](https://travis-ci.org/ilyakaznacheev/cleanenv) [![Release](https://img.shields.io/github/release/ilyakaznacheev/cleanenv.svg)](https://github.com/ilyakaznacheev/cleanenv/releases/) [![License](https://img.shields.io/github/license/ilyakaznacheev/cleanenv.svg)](https://github.com/ilyakaznacheev/cleanenv/blob/master/LICENSE) ## Overview This is a simple configuration reading tool. It just does the following: - reads and parses configuration structure from the file - reads and overwrites configuration structure from environment variables - writes a detailed variable list to help output ## Content - [Installation](#installation) - [Usage](#usage) - [Read Configuration](#read-configuration) - [Read Environment Variables Only](#read-environment-variables-only) - [Update Environment Variables](#update-environment-variables) - [Description](#description) - [Model Format](#model-format) - [Supported types](#supported-types) - [Custom Functions](#custom-functions) - [Custom Value Setter](#custom-value-setter) - [Custom Value Update](#custom-value-update) - [Supported File Formats](#supported-file-formats) - [Integration](#integration) - [Flag](#flag) - [Examples](#examples) - [Contribution](#contribution) - [Thanks](#thanks) ## Installation To install the package run ```bash go get -u github.com/ilyakaznacheev/cleanenv ``` ## Usage The package is oriented to be simple in use and explicitness. The main idea is to use a structured configuration variable instead of any sort of dynamic set of configuration fields like some libraries does, to avoid unnecessary type conversions and move the configuration through the program as a simple structure, not as an object with complex behavior. There are just several actions you can do with this tool and probably only things you want to do with your config if your application is not too complicated. - read configuration file - read environment variables - read some environment variables again ### Read Configuration You can read a configuration file and environment variables in a single function call. ```go import github.com/ilyakaznacheev/cleanenv type ConfigDatabase struct { Port string `yaml:"port" env:"PORT" env-default:"5432"` Host string `yaml:"host" env:"HOST" env-default:"localhost"` Name string `yaml:"name" env:"NAME" env-default:"postgres"` User string `yaml:"user" env:"USER" env-default:"user"` Password string `yaml:"password" env:"PASSWORD"` } var cfg ConfigDatabase err := cleanenv.ReadConfig("config.yml", &cfg) if err != nil { ... } ``` This will do the following: 1. parse configuration file according to YAML format (`yaml` tag in this case); 1. reads environment variables and overwrites values from the file with the values which was found in the environment (`env` tag); 1. if no value was found on the first two steps, the field will be filled with the default value (`env-default` tag) if it is set. ### Read Environment Variables Only Sometimes you don't want to use configuration files at all, or you may want to use `.env` file format instead. Thus, you can limit yourself with only reading environment variables: ```go import github.com/ilyakaznacheev/cleanenv type ConfigDatabase struct { Port string `env:"PORT" env-default:"5432"` Host string `env:"HOST" env-default:"localhost"` Name string `env:"NAME" env-default:"postgres"` User string `env:"USER" env-default:"user"` Password string `env:"PASSWORD"` } var cfg ConfigDatabase err := cleanenv.ReadEnv(&cfg) if err != nil { ... } ``` ### Update Environment Variables Some environment variables may change during the application run. To get the new values you need to mark these variables as updatable with the tag `env-upd` and then run the update function: ```go import github.com/ilyakaznacheev/cleanenv type ConfigRemote struct { Port string `env:"PORT" env-upd` Host string `env:"HOST" env-upd` UserName string `env:"USERNAME"` } var cfg ConfigRemote cleanenv.ReadEnv(&cfg) // ... some actions in-between err := cleanenv.UpdateEnv(&cfg) if err != nil { ... } ``` Here remote host and port may change in a distributed system architecture. Fields `cfg.Port` and `cfg.Host` can be updated in the runtime from corresponding environment variables. You can update them before the remote service call. Field `cfg.UserName` will not be changed after the initial read, though. ### Description You can get descriptions of all environment variables to use them in the help documentation. ```go import github.com/ilyakaznacheev/cleanenv type ConfigServer struct { Port string `env:"PORT" env-description:"server port"` Host string `env:"HOST" env-description:"server host"` } var cfg ConfigRemote help, err := cleanenv.GetDescription(&cfg, nil) if err != nil { ... } ``` You will get the following: ``` Environment variables: PORT server port HOST server host ``` ## Model Format Library uses tags to configure the model of configuration structure. There are the following tags: - `env="<name>"` - environment variable name (e.g. `env="PORT"`); - `env-upd` - flag to mark a field as updatable. Run `UpdateEnv(&cfg)` to refresh updatable variables from environment; - `env-required` - flag to mark a field as required. If set will return an error during environment parsing when the flagged as required field is empty (default Go value). Tag `env-default` is ignored in this case; - `env-default="<value>"` - default value. If the field wasn't filled from the environment variable default value will be used instead; - `env-separator="<value>"` - custom list and map separator. If not set, the default separator `,` will be used; - `env-description="<value>"` - environment variable description; - `env-layout="<value>"` - parsing layout (for types like `time.Time`); ## Supported types There are following supported types: - `int` (any kind); - `float` (any kind); - `string`; - `boolean`; - slices (of any other supported type); - maps (of any other supported type); - `time.Duration`; - `time.Time` (layout by default is RFC3339, may be overridden by `env-layout`); - any type implementing `cleanenv.Setter` interface. ## Custom Functions To enhance package abilities you can use some custom functions. ### Custom Value Setter To make custom type allows to set the value from the environment variable, you need to implement the `Setter` interface on the field level: ```go type MyField string func (f *MyField) SetValue(s string) error { if s == "" { return fmt.Errorf("field value can't be empty") } *f = MyField("my field is: "+ s) return nil } type Config struct { Field MyField `env="MY_VALUE"` } ``` `SetValue` method should implement conversion logic from string to custom type. ### Custom Value Update You may need to execute some custom field update logic, e.g. for remote config load. Thus, you need to implement the `Updater` interface on the structure level: ```go type Config struct { Field string } func (c *Config) Update() error { newField, err := SomeCustomUpdate() f.Field = newField return err } ``` ## Supported File Formats There are several most popular config file formats supported: - YAML - JSON - TOML - ENV - EDN ## Integration The package can be used with many other solutions. To make it more useful, we made some helpers. ### Flag You can use the cleanenv help together with Golang `flag` package. ```go // create some config structure var cfg config // create flag set using `flag` package fset := flag.NewFlagSet("Example", flag.ContinueOnError) // get config usage with wrapped flag usage fset.Usage = cleanenv.FUsage(fset.Output(), &cfg, nil, fset.Usage) fset.Parse(os.Args[1:]) ``` ## Examples ```go type Config struct { Port string `yaml:"port" env:"PORT" env-default:"8080"` Host string `yaml:"host" env:"HOST" env-default:"localhost"` } var cfg Config err := ReadConfig("config.yml", &cfg) if err != nil { ... } ``` This code will try to read and parse the configuration file `config.yml` as the structure is described in the `Config` structure. Then it will overwrite fields from available environment variables (`PORT`, `HOST`). For more details check the [example](/example) directory. ## Contribution The tool is open-sourced under the [MIT](LICENSE) license. If you will find some error, want to add something or ask a question - feel free to create an issue and/or make a pull request. Any contribution is welcome. ## Thanks Big thanks to a project [kelseyhightower/envconfig](https://github.com/kelseyhightower/envconfig) for inspiration. The logo was made by [alexchoffy](https://www.instagram.com/alexchoffy/). ## Blog Posts [Clean Configuration Management in Golang](https://dev.to/ilyakaznacheev/clean-configuration-management-in-golang-1c89).

31.184466

304

0.731839

eng_Latn

0.922879

d0de71cbab0ebe70e2bfd1b70a8ab1d1d27f116a

7,510

md

Markdown

README.md

Pondorasti/BEW-2.3

2ffe844f8fa43a9ce2ce141e5c88c605a0d19b06

[ "MIT" ]

null

README.md

Pondorasti/BEW-2.3

2ffe844f8fa43a9ce2ce141e5c88c605a0d19b06

[ "MIT" ]

null

README.md

Pondorasti/BEW-2.3

2ffe844f8fa43a9ce2ce141e5c88c605a0d19b06

[ "MIT" ]

null

<p align="center"> <img src="banner.png" height="320" alt="BEW 2.3 @ Make School"> </p> # ACS 3230: Intro to Web Security ## Course Description _This course covers key concepts in internet data security and best practices for keeping information safe. Students will examine historical hacks, learn how to analyze websites and web architectures for classical security vulnerabilities, and learn how to defend against security attacks._ ## Prerequisites - [BEW 1.2](https://make.sc/bew1.2) ## Course Specifics **Course Delivery**: online | 7 weeks | 14 sessions<br> **Course Credits**: 3 units | 37.5 Seat Hours | 75 Total Hours ## Learning Outcomes By the end of the course, you will be able to… 1. Confidently talk about different types of vulnerabilities within the security space. 2. Defend against vulnerabilities and attacks. 3. Apply web security best practices to your projects. 4. Understand and utilize adversarial security techniques. 5. Use practical techniques for securing applications and web servers. ## Schedule **Course Dates:** Monday, March 29 through Wednesday, May 12, 2021 _(7 weeks)_<br> **Class Times:** Monday & Wednesday at 9:30am to 12:15pm _(13 class sessions)_ | Class | Date | Security Category | Topic | | :---: | :---------: | :-------------------------: | -------------------------------------------------------- | --- | | 1 | Mon, Mar 29 | _Social Engineering_ | **[Lesson 1]: How to Hack a Human** | | - | Wed, Mar 31 | **No Class - Cesar Chavez** | | 2 | Mon, Apr 5 | _Culture_ | **[Lesson 2]: Historic Hacks / Ethical Hacking** | | 3 | Wed, Apr 7 | _Web_ | **[Lesson 3]: Server-Side Vulnerabilities** | | 4 | Mon, Apr 12 | _Web_ | **[Lesson 4]: Securing Data: Sanitization & Validation** | | 5 | Wed, Apr 14 | _Web_ | **[Lesson 5]: Client-Side Vulnerabilities** | | | 6 | Mon, Apr 19 | _Operational_ | **[Lesson 6]: You've Been Hacked. What Do?** | | 7 | Wed, Apr 21 | _Web_ | **[Lesson 7]: Cryptography** | | 8 | Wed, Apr 26 | _Web_ | **[Lesson 8]: Encryption** | | 9 | Wed, Apr 28 | _Network_ | **[Lesson 9]: OWASP Top 10** | | 10 | Mon, May 3 | _Operational_ | **[Lesson 10]: DDoS** | | 11 | Wed, May 5 | _Computer_ | Lab Day | | 12 | Mon, May 10 | _1-1 w/ Dani_ | Prepare Study Guide / Mock Interviews | | 13 | Wed, May 12 | _1-1 w/ Dani_ | **Interview Day :one:** _(Surnames `N` - `Z`)_ | ## Class Assignments We will be using [Gradescope] this term, which allows us to provide fast and accurate feedback on your work. All assigned work will be submitted through [Gradescope], and assignment and exam grades will be returned through [Gradescope]. As soon as grades are posted, you will be notified immediately so that you can log in and see your feedback. You may also submit regrade requests if you feel we have made a mistake. Your [Gradescope] login is your Make School email, and your password can be changed at [https://gradescope.com/reset_password](https://gradescope.com/reset_password). The same link can be used if you need to set your password for the first time. ### Tutorials | Name | Description | Due Date | | --------------------------------------- | ----------- | ----------------------- | | [NSE 1: The Threat Landscape] | _TODO_ | **Due 04/19 @ 11:59PM** | | [NSE 2: The Evolution of Cybersecurity] | _TODO_ | **Due 05/05 @ 11:59PM** | ### Challenges | Name | Description | Due Date | | ----------------------------- | ----------- | ----------------------- | | [Historic Hacks Presentation] | _TODO_ | **Due 04/05 @ 11:59PM** | | [Social Engineering] | _TODO_ | **Due 04/07 @ 11:59PM** | | [Jinja SSTI Exploits] | _TODO_ | **Due 04/14 @ 11:59PM** | | [Steganography] | _TODO_ | **Due 04/30 @ 11:59PM** | | [Juice Box] | _TODO_ | **Due 05/10 @ 11:59PM** | ## Evaluation To pass this course you must meet the following requirements: - The certificate earned at the end of each [tutorial](#tutorials) must be turned in on [Gradescope]. - Complete and pass all in class [challenges and assignments](#challenges) on [Gradescope]. - Attend and pass a final Course Reflection interview with the instructor. - Actively participate in class and abide by the attendance policy. - Make up all classwork from all absences. ## Information Resources Any additional resources you may need (online books, etc.) can be found here. You can also find additional resources through the library linked below: - [make.sc/library](http://make.sc/library) ## Make School Course Policies - [Program Learning Outcomes](https://make.sc/program-learning-outcomes) - What you will achieve after finishing Make School, all courses are designed around these outcomes. - [Grading System](https://make.sc/grading-system) - How grading is done at Make School - [Code of Conduct, Equity, and Inclusion](https://make.sc/code-of-conduct) - Learn about Diversity and Inclusion at Make School - [Academic Honesty](https://make.sc/academic-honesty-policy) - Our policies around plagerism, cheating, and other forms of academic misconduct - [Attendance Policy](https://make.sc/attendance-policy) - What we expect from you in terms of attendance for all classes at Make School - [Course Credit Policy](https://make.sc/course-credit-policy) - Our policy for how you obtain credit for your courses - [Disability Services (Academic Accommodations)](https://make.sc/disability-services) - Services and accommodations we provide for students - [Online Learning Tutorial](https://make.sc/online-learning-tutorial) - How to succeed in online learning at Make School - [Student Handbook](https://make.sc/student-handbook) - Guidelines, policies, and resources for all Make School students [gradescope]: https://gradescope.com [lesson 1]: Lessons/SocialEngineering.md [lesson 2]: Lessons/EthicalHacking.md [lesson 3]: Lessons/ServerSideExploits.md [lesson 4]: Lessons/Sanitization.md [lesson 5]: Lessons/ClientSideExploits.md [lesson 6]: Lessons/IncidentResponse.md [lesson 7]: Lessons/Cryptography.md [lesson 8]: Lessons/Encryption.md [lesson 9]: Lessons/OWASP.md [lesson 10]: Lessons/DDoS.md [lesson 11]: Lessons/Drills.md [nse 1: the threat landscape]: https://training.fortinet.com/course/view.php?id=1406 [nse 2: the evolution of cybersecurity]: https://training.fortinet.com/course/view.php?id=2271 [historic hacks presentation]: Lessons/EthicalHacking.md#%f0%9f%92%bb-40m-activity-historical-hacks-research [social engineering]: Lessons/SocialEngineering.md#activity-social-engineering-for-good [jinja ssti exploits]: Lessons/ServerSideExploits.md#%f0%9f%92%bb-60m-in-class-activity-ssti [steganography]: Lessons/Cryptography.md#35m-%f0%9f%92%bb-activity-decoding-a-secret-message [juice box]: Lessons/OWASP.md#60m-%f0%9f%92%bb-activity-juice-shop

61.557377

418

0.627563

eng_Latn

0.840387

d0ded95be4862eb70f6e5a48805fbd7bd344967b

1,137

md

Markdown

docs/mfc/reference/user-defined-handlers.md

insurgent92/cpp-docs.ko-kr

06a8d8eee5c911618f014fb0d58059afd10553f0

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

3

2019-10-11T07:41:28.000Z

2021-06-29T08:27:00.000Z

docs/mfc/reference/user-defined-handlers.md

jacking75/cpp-docs.ko-kr

a3d97df4004aac6e595d7bdb04957fd517fb0a82

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

null

docs/mfc/reference/user-defined-handlers.md

jacking75/cpp-docs.ko-kr

a3d97df4004aac6e595d7bdb04957fd517fb0a82

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

null

--- title: 사용자 정의 처리기 ms.date: 11/04/2016 f1_keywords: - vc.mfc.handlers helpviewer_keywords: - ON_REGISTERED_MESSAGE macro [MFC] - ON_MESSAGE macro [MFC] - user-defined handlers [MFC] ms.assetid: 99478294-bef0-4ba7-a369-25a6abdcdb62 ms.openlocfilehash: 4d2102668b7cc964e6fe3bffdcc6931a2961a737 ms.sourcegitcommit: 6052185696adca270bc9bdbec45a626dd89cdcdd ms.translationtype: MT ms.contentlocale: ko-KR ms.lasthandoff: 10/31/2018 ms.locfileid: "50562255" --- # <a name="user-defined-handlers"></a>사용자 정의 처리기 다음 맵 항목 있는 함수 프로토타입과 일치합니다. |맵 항목|함수 프로토타입| |---------------|------------------------| |ON_MESSAGE ( \<메시지 >, \<memberFxn >)|afx_msg LRESULT memberFxn (WPARAM, LPARAM);| |ON_REGISTERED_MESSAGE ( \<nMessageVariable >, \<memberFxn >)|afx_msg LRESULT memberFxn (WPARAM, LPARAM);| |ON_THREAD_MESSAGE ( \<메시지 >, \<memberFxn >)|afx_msg void memberFxn (WPARAM, LPARAM);| |ON_REGISTERED_THREAD_MESSAGE ( \<nMessageVariable >, \<memberFxn >)|afx_msg void memberFxn (WPARAM, LPARAM);| ## <a name="see-also"></a>참고 항목 [메시지 맵](../../mfc/reference/message-maps-mfc.md)<br/> [WM_ 메시지 처리기](../../mfc/reference/handlers-for-wm-messages.md)

33.441176

110

0.715919

kor_Hang

0.562866

d0df3be6e9686d3711d011ccb6b332aa8e05bf90

60

md

Markdown

README.md

olegmak02/Function

385dfc0190aea828b98bafd921c38cf573294bd7

[ "MIT" ]

null

README.md

olegmak02/Function

385dfc0190aea828b98bafd921c38cf573294bd7

[ "MIT" ]

1

2021-05-10T23:15:36.000Z

README.md

olegmak02/Function

385dfc0190aea828b98bafd921c38cf573294bd7

[ "MIT" ]

null

## Functions, lambda-functions, function contexts, closures

30

59

0.8

eng_Latn

0.779448

d0e0872194bd2665ed488d25d5e1743276130ea5

307

md

Markdown

README.md

TWScore/TLHC-crawler

bbdb9ee95f582118a063c0bdd4adc6b072dda179

[ "WTFPL" ]

1

2018-02-05T03:26:23.000Z

README.md

TWScore/TLHC-crawler

bbdb9ee95f582118a063c0bdd4adc6b072dda179

[ "WTFPL" ]

12

2018-05-24T14:54:38.000Z

2020-05-27T12:00:24.000Z

README.md

TWScore/TLHC-crawler

bbdb9ee95f582118a063c0bdd4adc6b072dda179

[ "WTFPL" ]

null

<p align="center"><img src="https://i.imgur.com/U3n7Was.png" width="400px"></p> 斗六家商的爬蟲跟成績系統 ## 啟動 1. 安裝 `npm install` 2. 執行 `node index.js` 3. 搭拉！ ## Docker [Docker Hub](https://hub.docker.com/r/gnehs/tlhcrawler/) ### 建議掛載檔案/資料夾 `/app/config.js` 首頁的連結和 Slideshow 的設定檔 `/app/ogimage/` 隨機 OGimage 圖片的資料夾

20.466667

79

0.680782

yue_Hant

0.851283

d0e1165817cacceb4401ecd5d46f94abf372702b

17,484

md

Markdown

TerminalVelocity(V0.1.3)/Library/PackageCache/[email protected]/Documentation~/Lit-Shader.md

Xenxibre/AdvancedSpecialisedProject

e7cf0e8f2e92a817468cab74dfea5450f405627f

[ "MIT" ]

null

TerminalVelocity(V0.1.3)/Library/PackageCache/[email protected]/Documentation~/Lit-Shader.md

Xenxibre/AdvancedSpecialisedProject

e7cf0e8f2e92a817468cab74dfea5450f405627f

[ "MIT" ]

null

TerminalVelocity(V0.1.3)/Library/PackageCache/[email protected]/Documentation~/Lit-Shader.md

Xenxibre/AdvancedSpecialisedProject

e7cf0e8f2e92a817468cab74dfea5450f405627f

[ "MIT" ]

null

# Lit Shader The Lit Shader lets you easily create realistic materials in the High Definition Render Pipeline (HDRP). It includes options for effects like subsurface scattering, iridescence, vertex or pixel displacement, and decal compatibility. For more information about Materials, Shaders, and Textures, see the [Unity User Manual](https://docs.unity3d.com/Manual/Shaders.html). ![](Images/HDRPFeatures-LitShader.png) ## Creating a Lit Material To create a new Lit Material, navigate to your Project's Asset window, right-click in the window and select **Create > Material**. This adds a new Material to your Unity Project’s Asset folder. When you create new Materials in HDRP, they use the Lit Shader by default. ## Properties ### Surface Options **Surface Options** control the overall look of your Material's surface and how Unity renders the Material on screen. | **Property** | **Description** | | ------------------------- | ------------------------------------------------------------ | | **Surface Type** | Use the drop-down to define whether your Material supports transparency or not. Materials with a **Transparent Surface Type** are more resource intensive to render than Materials with an **Opaque** **Surface Type**. HDRP exposes more properties, depending on the **Surface Type** you select. For more information about the feature and for the list of properties each **Surface Type** exposes, see the [Surface Type documentation](Surface-Type.html). | | **- Rendering Pass** | Use the drop-down to set the rendering pass that HDRP processes this Material in. For more information on this property, see the [Surface Type documentation](Surface-Type.html). | | **Double-Sided** | Enable the checkbox to make HDRP render both faces of the polygons in your geometry. For more information about the feature and for the list of properties enabling this feature exposes, see the [Double-Sided documentation](Double-Sided.html). | | **Alpha Clipping** | Enable the checkbox to make this Material act like a Cutout Shader. Enabling this feature exposes more properties. For more information about the feature and for the list of properties enabling this feature exposes, see the [Alpha Clipping documentation](Alpha-Clipping.html). | | **Material Type** | Allows you to give your Material a type, which allows you to customize it with different settings depending on the **Material Type** you select. For more information about the feature and for the list of properties each **Material Type** exposes, see the [Material Type documentation](Material-Type.html). | | **Receive Decals** | Enable the checkbox to allow HDRP to draw decals on this Material’s surface. | | **Receive SSR** | Enable the checkbox to make HDRP include this Material when it processes the screen space reflection pass. | | **Geometric Specular AA** | Enable the checkbox to tell HDRP to perform geometric anti-aliasing on this Material. This modifies the smoothness values on surfaces of curved geometry in order to remove specular artifacts. For more information about the feature and for the list of properties enabling this feature exposes, see the [Geometric Specular Anti-aliasing documentation](Geometric-Specular-Anti-Aliasing.html). | | **Displacement Mode** | Use this drop-down to select the method that HDRP uses to alter the height of the Material’s surface. For more information about the feature and for the list of properties each **Displacement Mode ** exposes, see the [Displacement Mode documentation](Displacement-Mode.html). | ### Vertex Animation | **Property** | **Description** | | -------------------------------------- | ------------------------------------------------------------ | | **Motion Vector For Vertex Animation** | Enable this checkbox to make HDRP write motion vectors for GameObjects that use vertex animation. This removes the ghosting that vertex animation can cause. | ### Surface Inputs | **Property** | **Description** | | ------------------------------- | ------------------------------------------------------------ | | **Base Map** | Assign a Texture that controls both the color and opacity of your Material. To assign a Texture to this field, click the radio button and select your Texture in the Select Texture window. Use the color picker to select the color of the Material. If you do not assign a Texture, this is the absolute color of the Material. If you do assign a Texture, the final color of the Material is a combination of the Texture you assign and the color you select. The alpha value of the color controls the transparency level for the Material if you select **Transparent** from the **Surface Type** drop-down. | | **Smoothness** | Use the slider to adjust the smoothness of your Material. Every light ray that hits a smooth surface bounces off at predictable and consistent angles. For a perfectly smooth surface that reflects light like a mirror, set this to a value of 1. Less smooth surfaces reflect light over a wider range of angles (because the light hits the bumps in the microsurface), so the reflections have less detail and spread across the surface in a more diffused pattern.<br />This property only appears when you unassign the Texture in the **Mask Map**. | | **Smoothness Remapping** | Use this min-max slider to remap the smoothness values from the **Mask Map** to the range you specify. Rather than [clamping](https://docs.unity3d.com/ScriptReference/Mathf.Clamp.html) values to the new range, Unity condenses the original range down to the new range uniformly.<br />This property only appears when you assign a **Mask Map**. | | **Ambient Occlusion Remapping** | Use this min-max slider to remap the ambient occlusion values from the **Mask Map** to the range you specify. Rather than [clamping](https://docs.unity3d.com/ScriptReference/Mathf.Clamp.html) values to the new range, Unity condenses the original range down to the new range uniformly.<br />This property only appears when you assign a **Mask Map**. | | **Mask Map** | Assign a Texture that packs different Material maps into each of its RGBA channels.<br />• **Red**: Stores the metallic map. <br />• **Green**: Stores the ambient occlusion map.<br />• **Blue**: Stores the detail mask map.<br />• **Alpha**: Stores the smoothness map. | | **Normal Map Space** | Use this drop-down to select the type of Normal Map space that this Material uses.<br />• **TangentSpace**: Defines the normal map in [tangent space](Glossary.html#TangentSpaceNormalMap). use this to tile a Texture on a Mesh. The normal map Texture must be BC7, BC5, or DXT5nm format.<br />• **ObjectSpace**: Defines the normal maps in [object space](Glossary.html#ObjectSpaceNormalMap). Use this for planar-mapping GameObjects like the terrain. The normal map must be an RGB Texture . | | **Normal Map** | Assign a Texture that defines the normal map for this Material in tangent space. Use the slider to modulate the normal intensity between 0 and 8.<br />This property only appears when you select **TangentSpace** from the **Normal Map Space** drop-down. | | **Normal Map OS** | Assign a Texture that defines the object space normal map for this Material. Use the handle to modulate the normal intensity between 0 and 8.<br />This property only appears when you select **ObjectSpace** from the **Normal Map Space** drop-down. | | **Bent Normal Map** | Assign a Texture that defines the bent normal map for this Material in tangent space. HDRP uses bent normal maps to simulate more accurate ambient occlusion. Note: Bent normal maps only work with diffuse lighting.<br />This property only appears when you select **TangentSpace** from the **Normal Map Space** drop-down.. | | **Bent Normal Map OS** | Assign a Texture that defines the bent normal map for this Material in object space. HDRP uses bent normal maps to simulate more accurate ambient occlusion. Note: Bent normal maps only work with diffuse lighting.<br />This property only appears when you select **ObjectSpace** from the **Normal Map Space** drop-down. | | **Coat Mask** | Assign a Texture that defines the coat mask for this Material. HDRP uses this mask to simulate a clear coat effect on the Material to mimic Materials like car paint or plastics. The Coat Mask value is 0 by default, but you can use the handle to modulate the clear Coat Mask effect using a value between 0 and 1. | | **Base UV Mapping** | Use the drop-down to select the type of UV mapping that HDRP uses to map Textures to this Material’s surface.<br />• Unity manages four UV channels for a vertex: **UV0**, **UV1**, **UV2**, and **UV3**.<br />• **Planar:** A planar projection from top to bottom.<br />• **Triplanar**: A planar projection in three directions:<br />X-axis: Left to right<br />Y-axis: Top to bottom<br />Z-axis: Front to back<br /><br />Unity blends these three projections together to produce the final result. | | **Tiling** | Set an **X** and **Y** UV tile rate for all of the Textures in the **Surface Inputs** section. HDRP uses the **X** and **Y** values to tile these Textures across the Material’s surface, in object space. | | **Offset** | Set an **X** and **Y** UV offset for all of the Textures in the **Surface Inputs** section. HDRP uses the **X** and **Y** values to offset these Textures across the Material’s surface, in object. | ### Detail Inputs | **Property** | **Description** | | -------------------------------- | ------------------------------------------------------------ | | **Detail Map** | Assign a [channel-packed Texture](Glossary.html#ChannelPacking) that HDRP uses to add micro details into the Material. The Detail Map uses the following channel settings:<br />• **Red**: Stores the grey scale as albedo.<br />• **Green**: Stores the green channel of the detail normal map.<br />• **Blue**: Stores the detail smoothness.<br />• **Alpha**: Stores the red channel of the detail normal map. | | **Detail UV Mapping** | Use the drop-down to set the type of UV map to use for the **Detail Map**. If the Material’s **Base UV mapping** property is set to **Planar** or **Triplanar**, the **Detail UV Mapping** is also set to **Planar** or **Triplanar**.<br />The **Detail Map** Texture modifies the appearance of the Material so, by default, HDRP applies the **Tiling** and **Offset** of the **Base UV Map** to the **Detail Map** to synchronize the **Detail Map** and the rest of the Material Textures. HDRP then applies the **Detail Map** **Tiling** and **Offset** properties on top of the **Base Map Tiling** and **Offset**. For example, on a plane, if the **Tiling** for **Base UV Mapping** is 2, and this value is also 2, then the **Detail Map** Texture tiles by 4 on the plane.<br />This workflow allows you to change the **Tiling** of the Texture on the Material, without having to set the **Tiling** of the **Detail UV** too.<br />To separate the **Detail UV Map** from the **Base UV Map** to set it independently, disable the **Lock to Base Tiling/Offset** checkbox. | | **- Lock to Base Tiling/Offset** | Enable the checkbox to make the **Base UV Map**’s **Tiling** and **Offset** properties affect the **Detail Map**. HDRP multiplies these properties by the **Detail UV Map**’s **Tiling** and **Offset** properties respectively. To separate the **Detail UV Map** from the **Base UV Map** to set it independently, disable this checkbox. | | **Tiling** | Set an **X** and **Y** tile rate for the **Detail Map** UV. HDRP uses the **X** and **Y** values to tile the Texture assigned to the **Detail Map** across the Material’s surface, in object space. | | **Offset** | Set an **X** and **Y** offset for the **Detail Map** UV. HDRP uses the **X** and **Y** values to offset the Texture assigned to the **Detail Map** across the Material’s surface, in object space. | | **Detail Albedo Scale** | Use the slider to modulate the albedo of the detail map (red channel) between 0 and 2. This is an overlay effect. | | **Detail Normal Scale** | Use the slider to modulate the intensity of the detail normal map, between 0 and 2. The default value is 1 and has no scale. | | **Detail Smoothness Scale** | Use the slider modulate the smoothness of the detail map (blue channel) between 0 and 2, like an overlay effect. The default value is 1 and has no scale. | ### Transparency Inputs Unity exposes this section if you select **Transparent** from the **Surface Type** drop-down. For information on the properties in this section, see the [Surface Type documentation](Surface-Type.html#TransparencyInputs). <a name="EmissionInputs></a> ### Emission inputs | **Property** | **Description** | | ------------------------------- | ------------------------------------------------------------ | | **Use Emission Intensity** | Enable the checkbox to use a separate LDR color and intensity value to set the emission color for this Material. Disable this checkbox to only use an HDR color to handle the color and emission color intensity. When enabled, this exposes the **Emission Intensity** property. | | **Emission Map** | Assign a Texture that this Material uses for emission. You can also use the color picker to select a color that HDRP multiplies by the Texture. If you do not set an emission texture then HDRP only uses the HDR color to calculate the final emissive color of the Material. You can set the intensity of the HDR color within the HDR color picker. | | **Emission UV Mapping** | Use the drop-down to select the type of UV mapping that HDRP uses for the **Emission Map**.<br />• Unity manages four UV channels for a vertex: **UV0**, **UV1**, **UV2**, and **UV3**.<br />• **Planar:** A planar projection from top to bottom.<br />• **Triplanar**: A planar projection in three directions:<br />X-axis: Left to right<br />Y-axis: Top to bottom<br />Z-axis: Front to back<br /><br />Unity blends these three projections together to produce the final result. | | **- Tiling** | Set an **X** and **Y** tile rate for the **Emission Map** UV. HDRP uses the **X** and **Y** values to tile the Texture assigned to the **Emission Map** across the Material’s surface, in object space. | | **- Offset** | Set an **X** and **Y** offset for the **Emission Map** UV. HDRP uses the **X** and **Y** values to offset the Texture assigned to the **Emission Map** across the Material’s surface, in object space. | | **Emission Intensity** | Set the overall strength of the emission effect for this Material.<br />Use the drop-down to select one of the following [physical light units](Physical-Light-Units.html) to use for intensity:<br />• [Luminance](Physical-Light-Units.html#Luminance)<br />• [EV<sub>100</sub>](Physical-Light-Units.html#EV) | | **Exposure Weight** | Use the slider to set how much effect the exposure has on the emission power. For example, if you create a neon tube, you would want to apply the emissive glow effect at every exposure. | | **Emission Multiply with Base** | Enable the checkbox to make HDRP use the base color of the Material when it calculates the final color of the emission. When enabled, HDRP multiplies the emission color by the base color to calculate the final emission color. | | **Emission** | Enable the checkbox to make the emission color affect global illumination. | | **- Global Illumination** | Use the drop-down to choose how color emission interacts with global illumination.<br />• **Realtime**: Select this option to make emission affect the result of real-time global illumination.<br />• **Baked**: Select this option to make emission only affect global illumination during the baking process.<br />• **None**: Select this option to make emission not affect global illumination. | ### Advanced options | **Property** | **Description** | | --------------------------------------- | ------------------------------------------------------------ | | **Enable GPU instancing** | Enable the checkbox to tell HDRP to render meshes with the same geometry and Material/Shader in one batch when possible. This makes rendering faster. HDRP can not render Meshes in one batch if they have different Materials, or if the hardware does not support GPU instancing. For example, you can not static-batch GameObjects that have an animation based on the object pivot, but the GPU can instance them. | | **Specular Occlusion from Bent normal** | Enable the checkbox to make HDRP use the Bent Normal Map to process specular occlusion for Reflection Probes. |

186

1,091

0.677477

eng_Latn

0.986244

d0e13c7121e87b2866643dca71fae3e6dbf407eb

1,457

md

Markdown

README.md

amalieKo/Balancing-Platform

a8382e51b70480404cb9ec2988e61bc65b9e86c6

[ "MIT" ]

null

README.md

amalieKo/Balancing-Platform

a8382e51b70480404cb9ec2988e61bc65b9e86c6

[ "MIT" ]

null

README.md

amalieKo/Balancing-Platform

a8382e51b70480404cb9ec2988e61bc65b9e86c6

[ "MIT" ]

null

# Balancing platform Short description ### Prerequisites You will need [Python 3](https://www.python.org/) for using the provided files. Also you will need to install all the dependencies listed below. ```bash pip install -r /path/to/requirements.txt or pip install opencv-python pip install numpy pip install pymodbus pip install vpython pip install matplotlib pip install simple-pid pip install pygame ``` ### Installing Clone or download project as zip in any directory. Find correct HSV settings for ball detection with morphological_transform file. Adjust the sliders until the ball is the only thing white. Set the new values in the video_processing file and finish with running main.py ### Example ```bash python main.py ``` ![Output]() ![Output]() ![Output]() ## Built With * [Python](https://www.python.org/) - Python ## Contributing If you want to contribute or find anything wrong, please create a Pull request, or issue adressing the change, or issue. ## Author * **Magnus Øye** - [magnusoy](https://github.com/magnusoy) ## License This project is licensed under the MIT License - see the [LICENSE.md](https://github.com/magnusoy/Arduino-with-Python/blob/master/LICENSE) file for details ## Libraries [OpenCV](https://docs.opencv.org/3.4.1/index.html) [Numpy](http://www.numpy.org/) [Vpython](http://vpython.org/) [Matplotlib](https://matplotlib.org/index.html) [PyModbus](https://pymodbus.readthedocs.io/en/latest/)

20.814286

155

0.743995

eng_Latn

0.905174

d0e1e6792a388e9b5c4e8b09efb9b6f354f72349

827

md

Markdown

PhantomCTF/Reverse/segmentationFault/readme.md

FrigidSec/CTFWriteUps

22f8a98133a7dba3ae87baaa4f110a14b4239cb9

[ "MIT" ]

7

2020-08-23T17:26:19.000Z

2021-12-13T13:16:43.000Z

PhantomCTF/Reverse/segmentationFault/readme.md

MrPr1M3/CTFWriteups

22f8a98133a7dba3ae87baaa4f110a14b4239cb9

[ "MIT" ]

null

PhantomCTF/Reverse/segmentationFault/readme.md

MrPr1M3/CTFWriteups

22f8a98133a7dba3ae87baaa4f110a14b4239cb9

[ "MIT" ]

5

2020-08-24T05:34:58.000Z

2020-10-13T13:24:16.000Z

# Segmentation Fault [Reverse] In this we get a : ``` ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=89d54c514d9f6bec697e52edfee4a495266b3577, for GNU/Linux 3.2.0, with debug_info, not stripped ``` and when running the binary we get a segmentation fault. which on anaysis seems to be caused by `foo()` function. And this was really easy for me, as i like binary patching and this just needed `2 clean patches` either in `JE` and `JNE` instructions or the imm. value of `MOV` opcode. Let's see the CG of the binary : ### BEFORE MOD ![](./_docs/1.png) ![](./_docs/3.png) ### AFTER MOD [vim <3 xxd] ![](./_docs/2.png) ![](./_docs/4.png) ### FLAG And running the binary after that gave us the flag, just like that. ![](./_docs/5.png)

27.566667

223

0.700121

eng_Latn

0.982963

d0e21493f7e7cd8525391757353d56e0f06e40fd

1,655

md

Markdown

docs/csharp/misc/cs1635.md

eOkadas/docs.fr-fr

64202ad620f9bcd91f4360ec74aa6d86e1d4ae15

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

null

docs/csharp/misc/cs1635.md

eOkadas/docs.fr-fr

64202ad620f9bcd91f4360ec74aa6d86e1d4ae15

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

null

docs/csharp/misc/cs1635.md

eOkadas/docs.fr-fr

64202ad620f9bcd91f4360ec74aa6d86e1d4ae15

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

null

--- title: Avertissement du compilateur (niveau 1) CS1635 ms.date: 07/20/2015 f1_keywords: - CS1635 helpviewer_keywords: - CS1635 ms.assetid: e1795880-f7ea-4dca-b15b-4ba549d7ed78 ms.openlocfilehash: 652e4743e8b51413d6d7a6499c2366958fb9063a ms.sourcegitcommit: 986f836f72ef10876878bd6217174e41464c145a ms.translationtype: MT ms.contentlocale: fr-FR ms.lasthandoff: 08/19/2019 ms.locfileid: "69610903" --- # <a name="compiler-warning-level-1-cs1635"></a>Avertissement du compilateur (niveau 1) CS1635 Impossible de restaurer l’avertissement 'code d’avertissement', car il a été désactivé globalement Cet avertissement s’affiche quand vous utilisez l’option de ligne de commande ou le paramètre de projet **/nowarn** pour désactiver un avertissement pour l’ensemble de l’unité de compilation, mais utilisez `#pragma warning restore` pour tenter de restaurer cet avertissement. Pour résoudre cette erreur, supprimez l’option de ligne de commande ou le paramètre de projet /nowarn, ou supprimez `#pragma warning restore` pour les avertissements que vous désactivez via la ligne de commande ou les paramètres de projet. Pour plus d’informations, consultez la rubrique [#pragma warning](../language-reference/preprocessor-directives/preprocessor-pragma-warning.md) . L’exemple suivant génère l’erreur CS1635 : ```csharp // CS1635.cs // compile with: /w:1 /nowarn:162 enum MyEnum {one=1,two=2,three=3}; class MyClass { public static void Main() { #pragma warning disable 162 if (MyEnum.three == MyEnum.two) System.Console.WriteLine("Duplicate"); #pragma warning restore 162 } } ```

39.404762

664

0.755287

fra_Latn

0.865495

d0e291b89e451c47fd5f3f92b43a870a1db0c776

2,496

md

Markdown

docs/introduction.md

kongulov/laravel-nova-lang

c1f1e42b8c4ed044b2e5dd5eb1a23dea366c167b

[ "MIT" ]

1

2019-06-27T11:59:37.000Z

docs/introduction.md

kongulov/laravel-nova-lang

c1f1e42b8c4ed044b2e5dd5eb1a23dea366c167b

[ "MIT" ]

null

docs/introduction.md

kongulov/laravel-nova-lang

c1f1e42b8c4ed044b2e5dd5eb1a23dea366c167b

[ "MIT" ]

null

--- title: Introduction section: Getting Started weight: 1000 featherIcon: info --- **Language files for Laravel Nova translated into 40+ languages.** This is not an official Laravel package, but is built from community contributions. If you are able to help by submitting a new language, reviewing an existing language, or adding missing keys, please read our [contributing guidelines]({{base}}/{{version}}/contributing) and raise a PR. ### Available Languages Total languages **44** Total lines translated **17,207 (92.2%)** * `en` English · **424 (100%)** * `fr` French · **424 (100%)** * `ka` Georgian · **424 (100%)** * `de` German · **424 (100%)** * `es` Spanish · **424 (100%)** * `ar` Arabic · **420 (99.1%)** * `pt‑BR` Brazilian Portuguese · **420 (99.1%)** * `nl` Dutch · **420 (99.1%)** * `it` Italian · **420 (99.1%)** * `km` Khmer · **420 (99.1%)** * `ur` Urdu · **420 (99.1%)** * `cs` Czech · **407 (96%)** * `hu` Hungarian · **407 (96%)** * `id` Indonesian · **407 (96%)** * `ru` Russian · **406 (95.8%)** * `ca` Catalan · **405 (95.5%)** * `nb` Norwegian Bokmål · **404 (95.3%)** * `ro` Romanian · **404 (95.3%)** * `sv` Swedish · **404 (95.3%)** * `tr` Turkish · **404 (95.3%)** * `uk` Ukrainian · **404 (95.3%)** * `uz‑Latn` Uzbek (Latin) · **404 (95.3%)** * `fa` Farsi · **402 (94.8%)** * `af` Afrikaans · **399 (94.1%)** * `bs` Bosnian · **399 (94.1%)** * `ja` Japanese · **399 (94.1%)** * `tk` Turkmen · **398 (93.9%)** * `pl` Polish · **396 (93.4%)** * `zh‑CN` Chinese (Simplified) · **392 (92.5%)** * `zh‑TW` Chinese (Traditional) · **392 (92.5%)** * `pt` Portuguese · **376 (88.7%)** * `da` Danish · **355 (83.7%)** * `eu` Basque · **353 (83.3%)** * `hr` Croatian · **351 (82.8%)** * `fil` Filipino · **351 (82.8%)** * `fi` Finnish · **351 (82.8%)** * `hi` Hindi · **351 (82.8%)** * `sr` Serbian (Cyrillic) · **351 (82.8%)** * `sr‑Latn` Serbian (Latin) · **351 (82.8%)** * `sk` Slovak · **351 (82.8%)** * `sl` Slovenian · **351 (82.8%)** * `lt` Lithuanian · **350 (82.5%)** * `bg` Bulgarian · **348 (82.1%)** * `tl` Tagalog · **344 (81.1%)** See the full list of contributors on [GitHub](https://github.com/coderello/laravel-nova-lang#available-languages).

40.258065

286

0.597756

eng_Latn

0.592649

d0e2a83060ef98ab3c5cc26cea9811c9533cbc55

587

md

Markdown

.github/ISSUE_TEMPLATE/-------bug-report.md

smellman/StudyAtHome

ca86089d5c4be4f528511c9a34ccc6e0bd1a500b

[ "MIT" ]

null

.github/ISSUE_TEMPLATE/-------bug-report.md

smellman/StudyAtHome

ca86089d5c4be4f528511c9a34ccc6e0bd1a500b

[ "MIT" ]

null

.github/ISSUE_TEMPLATE/-------bug-report.md

smellman/StudyAtHome

ca86089d5c4be4f528511c9a34ccc6e0bd1a500b

[ "MIT" ]

null

--- name: バグ報告 / Bug report about: Create a report to help us improve title: '' labels: bug assignees: '' --- ## 起こっている問題 / The Problem - xxxx(できるだけ簡潔に/as concise as possible) ## スクリーンショット / Screenshot   ## 期待する見せ方・挙動 / Expected Behavior - xxxx(できるだけ簡潔に/as concise as possible) ## 起こっている問題の再現手段 / Steps to Reproduce 1. xxx 2. xxx 3. xxx ## 動作環境・ブラウザ / Environment - macOS / Windows / Linux / iOS / Android - Chrome / Safari / Firefox / Edge / Internet Explorer

18.34375

73

0.693356

eng_Latn

0.580917

d0e30010c84d8b66f70fda56de90950f9d89f032

40,998

md

Markdown

official-docs/docs-en/security/faq.md

GitCodeview/lrn_chromium

9f0b93c5a936a16e14eed094bbbd4e37de63c985

[ "MIT" ]

null

official-docs/docs-en/security/faq.md

GitCodeview/lrn_chromium

9f0b93c5a936a16e14eed094bbbd4e37de63c985

[ "MIT" ]

null

official-docs/docs-en/security/faq.md

GitCodeview/lrn_chromium

9f0b93c5a936a16e14eed094bbbd4e37de63c985

[ "MIT" ]

null

# Chrome Security FAQ [TOC] <a name="TOC-Why-are-security-bugs-hidden-in-the-Chromium-issue-tracker-"></a> ## Why are security bugs hidden in the Chromium issue tracker? We must balance a commitment to openness with a commitment to avoiding unnecessary risk for users of widely-used open source libraries. <a name="TOC-Can-you-please-un-hide-old-security-bugs-"></a> ## Can you please un-hide old security bugs? Our goal is to open security bugs to the public once the bug is fixed and the fix has been shipped to a majority of users. However, many vulnerabilities affect products besides Chromium, and we don’t want to put users of those products unnecessarily at risk by opening the bug before fixes for the other affected products have shipped. Therefore, we make all security bugs public within approximately 14 weeks of the fix landing in the Chromium repository. The exception to this is in the event of the bug reporter or some other responsible party explicitly requesting anonymity or protection against disclosing other particularly sensitive data included in the vulnerability report (e.g. username and password pairs). <a name="TOC-Can-I-get-advance-notice-about-security-bugs-"></a> ## Can I get advance notice about security bugs? Vendors of products based on Chromium, distributors of operating systems that bundle Chromium, and individuals and organizations that significantly contribute to fixing security bugs can be added to a list for earlier access to these bugs. You can email us at [email protected] to request to join the list if you meet the above criteria. In particular, vendors of anti-malware, IDS/IPS, vulnerability risk assessment, and similar products or services do not meet this bar. Please note that the safest version of Chrome/Chromium is always the latest stable version — there is no good reason to wait to upgrade, so enterprise deployments should always track the latest stable release. When you do this, there is no need to further assess the risk of Chromium vulnerabilities: we strive to fix vulnerabilities quickly and release often. <a name="TOC-Can-I-see-these-security-bugs-so-that-I-can-back-port-the-fixes-to-my-downstream-project-"></a> ## Can I see these security bugs so that I can back-port the fixes to my downstream project? Many developers of other projects use V8, Chromium, and sub-components of Chromium in their own projects. This is great! We are glad that Chromium and V8 suit your needs. We want to open up fixed security bugs (as described in the previous answer), and will generally give downstream developers access sooner. **However, please be aware that backporting security patches from recent versions to old versions cannot always work.** (There are several reasons for this: The patch won't apply to old versions; the solution was to add or remove a feature or change an API; the issue may seem minor until it's too late; and so on.) We believe the latest stable versions of Chromium and V8 are the most stable and secure. We also believe that tracking the latest stable upstream is usually less work for greater benefit in the long run than backporting. We strongly recommend that you track the latest stable branches, and we support only the latest stable branch. <a name="TOC-Severity-Guidelines"></a> ## How does the Chrome team determine severity of security bugs? See the [severity guidelines](severity-guidelines.md) for more information. Only security issues are considered under the security vulnerability rewards program. Other types of bugs, which we call "functional bugs", are not. <a name="TOC-Are-privacy-issues-considered-security-bugs-"></a> ## Are privacy issues considered security bugs? No. The Chrome Privacy team treats privacy issues, such as leaking information from Incognito, fingerprinting, and bugs related to deleting browsing data as functional bugs. Privacy issues are not considered under the security vulnerability rewards program; the [severity guidelines](severity-guidelines.md) outline the types of bugs that are considered security vulnerabilities in more detail. <a name="TOC-Timing-Attacks"></a> ## Are timing attacks considered security vulnerabilities? Some timing attacks are considered security vulnerabilities, and some are considered privacy vulnerabilities. Timing attacks vary significantly in terms of impact, reliability, and exploitability. Some timing attacks weaken mitigations like ASLR (e.g. [Issue 665930](https://crbug.com/665930)). Others attempt to circumvent the same origin policy, for instance, by using SVG filters to read pixels cross-origin (e.g. [Issue 686253](https://crbug.com/686253) and [Issue 615851](https://crbug.com/615851)). Many timing attacks rely upon the availability of high-resolution timing information [Issue 508166](https://crbug.com/508166); such timing data often has legitimate usefulness in non-attack scenarios making it unappealing to remove. Timing attacks against the browser's HTTP Cache (like [Issue 74987](https://crbug.com/74987)) can potentially leak information about which sites the user has previously loaded. The browser could attempt to protect against such attacks (e.g. by bypassing the cache) at the cost of performance and thus user-experience. To mitigate against such timing attacks, end-users can delete browsing history and/or browse sensitive sites using Chrome's Incognito or Guest browsing modes. Other timing attacks can be mitigated via clever design changes. For instance, [Issue 544765](https://crbug.com/544765) describes an attack whereby an attacker can probe for the presence of HSTS rules (set by prior site visits) by timing the load of resources with URLs "fixed-up" by HSTS. Prior to Chrome 64, HSTS rules [were shared](https://crbug.com/774643) between regular browsing and Incognito mode, making the attack more interesting. The attack was mitigated by changing Content-Security-Policy such that secure URLs will match rules demanding non-secure HTTP urls, a fix that has also proven useful to help to unblock migrations to HTTPS. Similarly, [Issue 707071](https://crbug.com/707071) describes a timing attack in which an attacker could determine what Android applications are installed; the attack was mitigated by introducing randomness in the execution time of the affected API. <a name="TOC-What-are-the-security-and-privacy-guarantees-of-Incognito-mode-"></a> ## What are the security and privacy guarantees of Incognito mode? Bugs in Incognito mode are tracked as privacy bugs, not security bugs. The [Help Center](https://support.google.com/chrome/?p=cpn_incognito) explains what privacy protections Incognito mode attempts to enforce. In particular, please note that Incognito is not a “do not track” mode, and it does not hide aspects of your identity from web sites. Chrome does offer a way to send Do Not Track request to servers; see chrome://settings/?search=do+not+track When in Incognito mode, Chrome does not store any new history, cookies, or other state in non-volatile storage. However, Incognito windows will be able to access some previously-stored state, such as browsing history. <a name="TOC-Are-denial-of-service-issues-considered-security-bugs-"></a> ## Are denial of service issues considered security bugs? No. Denial of Service (DoS) issues are treated as **abuse** or **stability** issues rather than security vulnerabilities. * If you find a reproducible crash, we encourage you to [report it](https://bugs.chromium.org/p/chromium/issues/entry?template=Crash%20Report). * If you find a site that is abusing the user experience (e.g. preventing you from leaving a site), we encourage you to [report it](https://crbug.com/new). DoS issues are not considered under the security vulnerability rewards program; the [severity guidelines](severity-guidelines.md) outline the types of bugs that are considered security vulnerabilities in more detail. <a name="TOC-Are-XSS-filter-bypasses-considered-security-bugs-"></a> ## Are XSS filter bypasses considered security bugs? No. Chromium once contained a reflected XSS filter called the [XSSAuditor](https://www.chromium.org/developers/design-documents/xss-auditor) that was a best-effort second line of defense against reflected XSS flaws found in web sites. The XSS Auditor was [removed in Chrome 78](https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/TuYw-EZhO9g/blGViehIAwAJ). <a name="TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model-"></a> ## Why aren't physically-local attacks in Chrome's threat model? People sometimes report that they can compromise Chrome by installing a malicious DLL in a place where Chrome will load it, by hooking APIs (e.g. [Issue 130284](https://crbug.com/130284)), or by otherwise altering the configuration of the device. We consider these attacks outside Chrome's threat model, because there is no way for Chrome (or any application) to defend against a malicious user who has managed to log into your device as you, or who can run software with the privileges of your operating system user account. Such an attacker can modify executables and DLLs, change environment variables like `PATH`, change configuration files, read any data your user account owns, email it to themselves, and so on. Such an attacker has total control over your device, and nothing Chrome can do would provide a serious guarantee of defense. This problem is not special to Chrome — all applications must trust the physically-local user. There are a few things you can do to mitigate risks from people who have physical control over **your** computer, in certain circumstances. * To stop people from reading your data in cases of device theft or loss, use full disk encryption (FDE). FDE is a standard feature of most operating systems, including Windows Vista and later, Mac OS X Lion and later, and some distributions of Linux. (Some older versions of Mac OS X had partial disk encryption: they could encrypt the user’s home folder, which contains the bulk of a user’s sensitive data.) Some FDE systems allow you to use multiple sources of key material, such as the combination of both a password and a key file on a USB token. When available, you should use multiple sources of key material to achieve the strongest defense. Chrome OS encrypts users’ home directories. * If you share your computer with other people, take advantage of your operating system’s ability to manage multiple login accounts, and use a distinct account for each person. For guests, Chrome OS has a built-in Guest account for this purpose. * Take advantage of your operating system’s screen lock feature. * You can reduce the amount of information (including credentials like cookies and passwords) that Chrome will store locally by using Chrome's Content Settings (chrome://settings/content) and turning off the form auto-fill and password storage features ([chrome://settings/search#password](chrome://settings/search#password)). There is almost nothing you can do to mitigate risks when using a **public** computer. * Assume everything you do on a public computer will become, well, public. You have no control over the operating system or other software on the machine, and there is no reason to trust the integrity of it. * If you must use such a computer, use Incognito mode and close all Incognito windows when you are done browsing to limit the amount of data you leave behind. Note that Incognito mode **provides no protection** if the system has already been compromised as described above. <a name="TOC-Why-aren-t-compromised-infected-machines-in-Chrome-s-threat-model-"></a> ## Why aren't compromised/infected machines in Chrome's threat model? This is essentially the same situation as with physically-local attacks. The attacker's code, when it runs as your user account on your machine, can do anything you can do. (See also [Microsoft's Ten Immutable Laws Of Security](https://web.archive.org/web/20160311224620/https://technet.microsoft.com/en-us/library/hh278941.aspx).) <a name="TOC-What-about-unmasking-of-passwords-with-the-developer-tools-"></a> ## What about unmasking of passwords with the developer tools? One of the most frequent reports we receive is password disclosure using the Inspect Element feature (see [Issue 126398](https://crbug.com/126398) for an example). People reason that "If I can see the password, it must be a bug." However, this is just one of the [physically-local attacks described in the previous section](#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model-), and all of those points apply here as well. The reason the password is masked is only to prevent disclosure via "shoulder-surfing" (i.e. the passive viewing of your screen by nearby persons), not because it is a secret unknown to the browser. The browser knows the password at many layers, including JavaScript, developer tools, process memory, and so on. When you are physically local to the computer, and only when you are physically local to the computer, there are, and always will be, tools for extracting the password from any of these places. <a name="TOC-Does-entering-JavaScript:-URLs-in-the-URL-bar-or-running-script-in-the-developer-tools-mean-there-s-an-XSS-vulnerability-"></a> ## Does entering JavaScript: URLs in the URL bar or running script in the developer tools mean there's an XSS vulnerability? [No](https://crbug.com/81697). Chrome does not attempt to prevent the user from knowingly running script against loaded documents, either by entering script in the Developer Tools console or by typing a JavaScript: URI into the URL bar. Chrome and other browsers do undertake some efforts to prevent *paste* of script URLs in the URL bar (to limit [social-engineering](https://blogs.msdn.microsoft.com/ieinternals/2011/05/19/socially-engineered-xss-attacks/)) but users are otherwise free to invoke script against pages using either the URL bar or the DevTools console. <a name="TOC-Does-executing-JavaScript-from-a-bookmark-mean-there-s-an-XSS-vulnerability-"></a> ## Does executing JavaScript from a bookmark mean there's an XSS vulnerability? No. Chromium allows users to create bookmarks to JavaScript URLs that will run on the currently-loaded page when the user clicks the bookmark; these are called [bookmarklets](https://en.wikipedia.org/wiki/Bookmarklet). <a name="TOC-Does-executing-JavaScript-in-a-PDF-file-mean-there-s-an-XSS-vulnerability-"></a> ## Does executing JavaScript in a PDF file mean there's an XSS vulnerability? No. PDF files have the ability to run JavaScript, usually to facilitate field validation during form fill-out. Note that the set of bindings provided to the PDF are more limited than those provided by the DOM to HTML documents (e.g. no document.cookie). <a name="TOC-Is-Chrome-s-support-for-userinfo-in-HTTP-URLs-e.g.-http:-user:password-example.com-considered-a-vulnerability-"></a> ## Is Chrome's support for userinfo in HTTP URLs (e.g. http://user:[email protected]) considered a vulnerability? [Not at this time](https://crbug.com/626951). Chrome supports HTTP and HTTPS URIs with username and password information embedded within them for compatibility with sites that require this feature. Notably, Chrome will suppress display of the username and password information after navigation in the URL box to limit the effectiveness of spoofing attacks that may try to mislead the user. For instance, navigating to `http://[email protected]` will show an address of `http://evil.example.com` after the page loads. <a name="TOC-Why-isn-t-passive-browser-fingerprinting-including-passive-cookies-in-Chrome-s-threat-model-"></a> <a name="TOC-What-is-Chrome-s-threat-model-for-fingerprinting-"></a> ## What is Chrome's threat model for fingerprinting? > **Update, August 2019:** Please note that this answer has changed. We have > updated our threat model to include fingerprinting. Although [we do not consider fingerprinting issues to be *security vulnerabilities*](#TOC-Are-privacy-issues-considered-security-bugs-), we do now consider them to be privacy bugs that we will try to resolve. We distinguish two forms of fingerprinting. * **Passive fingerprinting** refers to fingerprinting techniques that do not require a JavaScript API call to achieve. This includes (but is not limited to) mechanisms like [ETag cookies](https://en.wikipedia.org/wiki/HTTP_ETag#Tracking_using_ETags) and [HSTS cookies](https://security.stackexchange.com/questions/79518/what-are-hsts-super-cookies). * **Active fingerprinting** refers to fingerprinting techniques that do require a JavaScript API call to achieve. Examples include most of the techniques in [EFF's Panopticlick proof of concept](https://panopticlick.eff.org). For passive fingerprinting, our ultimate goal is (to the extent possible) to reduce the information content available to below the threshold for usefulness. For active fingerprinting, our ultimate goal is to establish a [privacy budget](https://github.com/bslassey/privacy-budget) and to keep web origins below the budget (such as by rejecting some API calls when the origin exceeds its budget). To avoid breaking rich web applications that people want to use, Chrome may increase an origin's budget when it detects that a person is using the origin heavily. As with passive fingerprinting, our goal is to set the default budget below the threshold of usefulness for fingerprinting. These are both long-term goals. As of this writing (August 2019) we do not expect that Chrome will immediately achieve them. For background on fingerprinting and the difficulty of stopping it, see [Arvind Narayanan's site](https://33bits.wordpress.com/about/) and [Peter Eckersley's discussion of the information theory behind Panopticlick](https://www.eff.org/deeplinks/2010/01/primer-information-theory-and-privacy). There is also [a pretty good analysis of in-browser fingerprinting vectors](https://dev.chromium.org/Home/chromium-security/client-identification-mechanisms). <a name="TOC-Where-are-the-security-indicators-located-in-the-browser-window-"></a> ## Where are the security indicators located in the browser window? The topmost portion of the browser window, consisting of the **Omnibox** (or **Location Bar**), navigation icons, menu icon, and other indicator icons, is sometimes called the browser **chrome** (not to be confused with the Chrome Browser itself). Actual security indicators can only appear in this section of the window. There can be no trustworthy security indicators elsewhere. Furthermore, Chrome can only guarantee that it is correctly representing URLs and their origins at the end of all navigation. Quirks of URL parsing, HTTP redirection, and so on are not security concerns unless Chrome is misrepresenting a URL or origin after navigation has completed. Browsers present a dilemma to the user since the output is a combination of information coming from both trustworthy sources (the browser itself) and untrustworthy sources (the web page), and the untrustworthy sources are allowed virtually unlimited control over graphical presentation. The only restriction on the page's presentation is that it is confined to the large rectangular area directly underneath the chrome, called the **viewport**. Things like hover text and URL preview(s), shown in the viewport, are entirely under the control of the web page itself. They have no guaranteed meaning, and function only as the page desires. This can be even more confusing when pages load content that looks like chrome. For example, many pages load images of locks, which look similar to the meaningful HTTPS lock in the Omnibox, but in fact do not convey any meaningful information about the transport security of that page. When the browser needs to show trustworthy information, such as the bubble resulting from a click on the lock icon, it does so by making the bubble overlap chrome. In the case of the lock bubble, it is a small triangular bump in the border of the bubble that overlays the chrome. This visual detail can't be imitated by the page itself since the page is confined to the viewport. <a name="TOC-Why-does-Chrome-show-a-green-lock-even-if-my-HTTPS-connection-is-being-proxied-"></a> ## Why does Chrome show a green lock, even if my HTTPS connection is being proxied? Some types of software intercept HTTPS connections. Examples include anti-virus software, corporate network monitoring tools, and school censorship software. In order for the interception to work, you need to install a private trust anchor (root certificate) onto your computer. This may have happened when you installed your anti-virus software, or when your company's network administrator set up your computer. If that has occurred, your HTTPS connections can be viewed or modified by the software. Since you have allowed the trust anchor to be installed onto your computer, Chrome assumes that you have consented to HTTPS interception. Anyone who can add a trust anchor to your computer can make other changes to your computer, too, including changing Chrome. (See also [Why aren't physically-local attacks in Chrome's threat model?](#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model-).) <a name="TOC-Why-can-t-I-select-Proceed-Anyway-on-some-HTTPS-error-screens-"></a> ## Why can’t I select Proceed Anyway on some HTTPS error screens? A key guarantee of HTTPS is that Chrome can be relatively certain that it is connecting to the true web server and not an impostor. Some sites request an even higher degree of protection for their users (i.e. you): they assert to Chrome (via Strict Transport Security — [HSTS](https://tools.ietf.org/html/rfc6797) — or by other means) that any server authentication error should be fatal, and that Chrome must close the connection. If you encounter such a fatal error, it is likely that your network is under attack, or that there is a network misconfiguration that is indistinguishable from an attack. The best thing you can do in this situation is to raise the issue to your network provider (or corporate IT department). Chrome shows non-recoverable HTTPS errors only in cases where the true server has previously asked for this treatment, and when it can be relatively certain that the current server is not the true server. <a name="TOC-How-does-key-pinning-interact-with-local-proxies-and-filters-"></a> ## How does key pinning interact with local proxies and filters? To enable certificate chain validation, Chrome has access to two stores of trust anchors (i.e. certificates that are empowered as issuers). One trust anchor store is the system or public trust anchor store, and the other other is the local or private trust anchor store. The public store is provided as part of the operating system, and intended to authenticate public internet servers. The private store contains certificates installed by the user or the administrator of the client machine. Private intranet servers should authenticate themselves with certificates issued by a private trust anchor. Chrome’s key pinning feature is a strong form of web site authentication that requires a web server’s certificate chain not only to be valid and to chain to a known-good trust anchor, but also that at least one of the public keys in the certificate chain is known to be valid for the particular site the user is visiting. This is a good defense against the risk that any trust anchor can authenticate any web site, even if not intended by the site owner: if an otherwise-valid chain does not include a known pinned key (“pin”), Chrome will reject it because it was not issued in accordance with the site operator’s expectations. Chrome does not perform pin validation when the certificate chain chains up to a private trust anchor. A key result of this policy is that private trust anchors can be used to proxy (or [MITM](https://en.wikipedia.org/wiki/Man-in-the-middle_attack)) connections, even to pinned sites. “Data loss prevention” appliances, firewalls, content filters, and malware can use this feature to defeat the protections of key pinning. We deem this acceptable because the proxy or MITM can only be effective if the client machine has already been configured to trust the proxy’s issuing certificate — that is, the client is already under the control of the person who controls the proxy (e.g. the enterprise’s IT administrator). If the client does not trust the private trust anchor, the proxy’s attempt to mediate the connection will fail as it should. <a name="TOC-When-is-key-pinning-enabled-"></a> ## When is key pinning enabled? Key pinning is enabled for Chrome-branded, non-mobile builds when the local clock is within ten weeks of the embedded build timestamp. Key pinning is a useful security measure but it tightly couples client and server configurations and completely breaks when those configurations are out of sync. In order to manage that risk we need to ensure that we can promptly update pinning clients in an emergency and ensure that non-emergency changes can be deployed in a reasonable timeframe. Each of the conditions listed above helps ensure those properties: Chrome-branded builds are those that Google provides and they all have an auto-update mechanism that can be used in an emergency. However, auto-update on mobile devices is significantly less effective thus they are excluded. Even in cases where auto-update is generally effective, there are still non-trivial populations of stragglers for various reasons. The ten-week timeout prevents those stragglers from causing problems for regular, non-emergency changes and allows stuck users to still, for example, conduct searches and access Chrome's homepage to hopefully get unstuck. In order to determine whether key pinning is active, try loading [https://pinningtest.appspot.com](https://pinningtest.appspot.com). If key pinning is active the load will _fail_ with a pinning error. <a name="TOC-How-does-certificate-transparency-interact-with-local-proxies-and-filters-"></a> ## How does Certificate Transparency interact with local proxies and filters? Just as [pinning only applies to publicly-trusted trust anchors](#TOC-How-does-key-pinning-interact-with-local-proxies-and-filters-), Chrome only evaluates Certificate Transparency (CT) for publicly-trusted trust anchors. Thus private trust anchors, such as for enterprise middle-boxes and AV proxies, do not need to be publicly logged in a CT log. <a name="TOC-Can-I-use-EMET-to-help-protect-Chrome-against-attack-on-Microsoft-Windows-"></a> ## Can I use EMET to help protect Chrome against attack on Microsoft Windows? There are [known compatibility problems](https://sites.google.com/a/chromium.org/dev/Home/chromium-security/chromium-and-emet) between Microsoft's EMET anti-exploit toolkit and some versions of Chrome. These can prevent Chrome from running in some configurations. Moreover, the Chrome security team does not recommend the use of EMET with Chrome because its most important security benefits are redundant with or superseded by built-in attack mitigations within the browser. For users, the very marginal security benefit is not usually a good trade-off for the compatibility issues and performance degradation the toolkit can cause. <a name="TOC-Why-are-some-web-platform-features-only-available-in-HTTPS-page-loads-"></a> ## Why are some web platform features only available in HTTPS page-loads? The full answer is here: we [Prefer Secure Origins For Powerful New Features](https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features). In short, many web platform features give web origins access to sensitive new sources of information, or significant power over a user's experience with their computer/phone/watch/etc., or over their experience with it. We would therefore like to have some basis to believe the origin meets a minimum bar for security, that the sensitive information is transported over the Internet in an authenticated and confidential way, and that users can make meaningful choices to trust or not trust a web origin. Note that the reason we require secure origins for WebCrypto is slightly different: An application that uses WebCrypto is almost certainly using it to provide some kind of security guarantee (e.g. encrypted instant messages or email). However, unless the JavaScript was itself transported to the client securely, it cannot actually provide any guarantee. (After all, a MITM attacker could have modified the code, if it was not transported securely.) <a name="TOC-Which-origins-are-secure-"></a> ## Which origins are "secure"? Secure origins are those that match at least one of the following (scheme, host, port) patterns: * (https, *, *) * (wss, *, *) * (*, localhost, *) * (*, 127/8, *) * (*, ::1/128, *) * (file, *, —) * (chrome-extension, *, —) That is, secure origins are those that load resources either from the local machine (necessarily trusted) or over the network from a cryptographically-authenticated server. See [Prefer Secure Origins For Powerful New Features](https://sites.google.com/a/chromium.org/dev/Home/chromium-security/prefer-secure-origins-for-powerful-new-features) for more details. <a name="TOC-What-s-the-story-with-certificate-revocation-"></a> ## What's the story with certificate revocation? Chrome's primary mechanism for checking the revocation status of HTTPS certificates is [CRLsets](https://dev.chromium.org/Home/chromium-security/crlsets). Chrome also supports Online Certificate Status Protocol (OCSP). However, the effectiveness of OCSP is is essentially 0 unless the client fails hard (refuses to connect) if it cannot get a live, valid OCSP response. No browser has OCSP set to hard-fail by default, for good reasons explained by Adam Langley (see [https://www.imperialviolet.org/2014/04/29/revocationagain.html](https://www.imperialviolet.org/2014/04/29/revocationagain.html) and [https://www.imperialviolet.org/2014/04/19/revchecking.html](https://www.imperialviolet.org/2014/04/19/revchecking.html)). Stapled OCSP with the Must Staple option (hard-fail if a valid OCSP response is not stapled to the certificate) is a much better solution to the revocation problem than non-stapled OCSP. CAs and browsers are working toward that solution (see the [Internet-Draft](https://tools.ietf.org/html/draft-hallambaker-tlssecuritypolicy-03)). Additionally, non-stapled OCSP poses a privacy problem: in order to check the status of a certificate, the client must query an OCSP responder for the status of the certificate, thus exposing a user's HTTPS browsing history to the responder (a third party). That said, you can use enterprise policies to [enable soft-fail OCSP](https://cloud.google.com/docs/chrome-enterprise/policies/?policy=EnableOnlineRevocationChecks) and hard-fail OCSP for [local trust anchors](https://cloud.google.com/docs/chrome-enterprise/policies/?policy=RequireOnlineRevocationChecksForLocalAnchors). Chrome performs online checking for [Extended Validation](https://cabforum.org/about-ev-ssl/) certificates if it does not already have a non-expired CRLSet entry covering the domain. If Chrome does not get a response, it simply downgrades the security indicator to Domain Validated. See also [Issue 361820](https://crbug.com/361820) for more discussion of the user-facing UX. <a name="TOC-Why-does-the-Password-Manager-ignore-autocomplete-off-for-password-fields-"></a> ## Why does the Password Manager ignore `autocomplete='off'` for password fields? Ignoring `autocomplete='off'` for password fields allows the password manager to give more power to users to manage their credentials on websites. It is the security team's view that this is very important for user security by allowing users to have unique and more complex passwords for websites. As it was originally implemented, autocomplete='off' for password fields took control away from the user and gave control to the web site developer, which was also a violation of the [priority of constituencies](http://www.schemehostport.com/2011/10/priority-of-constituencies.html). For a longer discussion on this, see the [mailing list announcement](https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/zhhj7hCip5c). <a name="TOC-Signout-of-Chrome"></a> ## Signing out of Chrome does not delete previously-synced data? If you have signed into Chrome and subsequently sign out of Chrome, previously saved passwords and other data are not deleted from your device unless you select that option when signing out of Chrome. If you change your Google password, synced data will no longer be updated in Chrome instances until you provide the new password to Chrome on each device configured to sync. However, previously synced data [remains available](https://crbug.com/792967) on each previously-syncing device unless manually removed. <a name="TOC-Why-doesn-t-the-Password-Manager-save-my-Google-password-if-I-am-using-Chrome-Sync-"></a> ## Why doesn't the Password Manager save my Google password if I am using Chrome Sync? In its default mode, Chrome Sync uses your Google password to protect all the other passwords in the Chrome Password Manager. In general, it is a bad idea to store the credential that protects an asset in the same place as the asset itself. An attacker who could temporarily compromise the Chrome Password Manager could, by stealing your Google password, obtain continuing access to all your passwords. Imagine you store your valuables in a safe, and you accidentally forget to close the safe. If a thief comes along, they might steal all of your valuables. That’s bad, but imagine if you had also left the combination to the safe inside as well. Now the bad guy has access to all of your valuables and all of your future valuables, too. The password manager is similar, except you probably would not even know if a bad guy accessed it. To prevent this type of attack, Chrome Password Manager does not save the Google password for the account you sync with Chrome. If you have multiple Google accounts, the Chrome Password Manager will save the passwords for accounts other than the one you are syncing with. <a name="TOC-Does-the-Password-Manager-store-my-passwords-encrypted-on-disk-"></a> ## Does the Password Manager store my passwords encrypted on disk? Chrome generally tries to use the operating system's user storage mechanism wherever possible and stores them encrypted on disk, but it is platform specific: * On Windows, Chrome uses the [Data Protection API (DPAPI)](https://msdn.microsoft.com/en-us/library/ms995355.aspx) to bind your passwords to your user account and store them on disk encrypted with a key only accessible to processes running as the same logged on user. * On macOS, Chrome previously stored credentials directly in the user's Keychain, but for technical reasons, it has switched to storing the credentials in "Login Data" in the Chrome users profile directory, but encrypted on disk with a key that is then stored in the user's Keychain. See [Issue 466638](https://crbug.com/466638) for further explanation. * On Linux, Chrome previously stored credentials directly in the user's Gnome Keyring or KWallet, but for technical reasons, it has switched to storing the credentials in "Login Data" in the Chrome user's profile directory, but encrypted on disk with a key that is then stored in the user's Gnome Keyring or KWallet. If there is no available Keyring or KWallet, the data is not encrypted when stored. * On iOS, passwords are currently stored directly in the iOS Keychain and referenced from the rest of the metadata stored in a separate DB. The plan there is to just store them in plain text in the DB, because iOS gives strong guarantees about only Chrome being able to access its storage. See [Issue 520437](https://crbug.com/520437) to follow this migration. <a name="TOC-I-found-a-phishing-or-malware-site-not-blocked-by-Safe-Browsing.-Is-this-a-security-vulnerability-"></a> ## I found a phishing or malware site not blocked by Safe Browsing. Is this a security vulnerability? Malicious sites not yet blocked by Safe Browsing can be reported via [https://www.google.com/safebrowsing/report_phish/](https://www.google.com/safebrowsing/report_phish/). Safe Browsing is primarily a blocklist of known-unsafe sites; the feature warns the user if they attempt to navigate to a site known to deliver phishing or malware content. You can learn more about this feature in these references: * [https://developers.google.com/safe-browsing/](https://developers.google.com/safe-browsing/) * [https://www.google.com/transparencyreport/safebrowsing/](https://www.google.com/transparencyreport/safebrowsing/) In general, it is not considered a security bug if a given malicious site is not blocked by the Safe Browsing feature, unless the site is on the blocklist but is allowed to load anyway. For instance, if a site found a way to navigate through the blocking red warning page without user interaction, that would be a security bug. A malicious site may exploit a security vulnerability (for instance, spoofing the URL in the **Location Bar**). This would be tracked as a security vulnerability in the relevant feature, not Safe Browsing itself. <a name="TOC-What-is-the-security-story-for-Service-Workers-"></a> ## What is the security story for Service Workers? See our dedicated [Service Worker Security FAQ](https://chromium.googlesource.com/chromium/src/+/master/docs/security/service-worker-security-faq.md). <a name="TOC-What-about-URL-spoofs-using-Internationalized-Domain-Names-IDN-"></a> ## What about URL spoofs using Internationalized Domain Names (IDN)? We try to balance the needs of our international userbase while protecting users against confusable homograph attacks. Despite this, there are a list of known IDN display issues we are still working on. * Please see [this document](https://docs.google.com/document/d/1_xJz3J9kkAPwk3pma6K3X12SyPTyyaJDSCxTfF8Y5sU) for a list of known issues and how we handle them. * [This document](https://www.chromium.org/developers/design-documents/idn-in-google-chrome) describes Chrome's IDN policy in detail. <a name="TOC-Chrome-silently-syncs-extensions-across-devices.-Is-this-a-security-vulnerability-"></a> ## Chrome silently syncs extensions across devices. Is this a security vulnerability? If an attacker has access to one of a victim's devices, the attacker can install an extension which will be synced to the victim's other sync-enabled devices. Similarly, an attacker who phishes a victim's Google credentials can sign in to Chrome as the victim and install an extension, which will be synced to the victim's other sync-enabled devices. Sync thereby enables an attacker to elevate phished credentials or physical access to persistent access on all of a victim's sync-enabled devices. To mitigate this issue, Chrome only syncs extensions that have been installed from the Chrome Web Store. Extensions in the Chrome Web Store are monitored for abusive behavior. In the future, we may pursue further mitigations. However, because an attacker must already have the victim's Google credentials and/or [physical access to a device](#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model), we don't consider this attack a security vulnerability. We **do** consider it a vulnerability if an attacker can get an extension to sync to a victim's device without either of the above preconditions. For example, we consider it a vulnerability if an attacker could craft a request to Google's sync servers that causes an extension to be installed to a user's device, or if an attacker could entice a victim to visit a webpage that causes an extension to be installed on their device(s). Please report such bugs via https://bugs.chromium.org/p/chromium/issues/entry?template=Security+Bug. <a name="TOC-Are-PDF-files-static-content-in-Chromium-"></a> ## Are PDF files static content in Chromium? No. PDF files have some powerful capabilities including invoking printing or posting form data. To mitigate abuse of these capabiliies, such as beaconing upon document open, we require interaction with the document (a "user gesture") before allowing their use. <a name="TOC-Why-arent-null-pointer-dereferences-considered-security-bugs-"></a> ## Why aren't null pointer dereferences considered security bugs? Null pointer dereferences with consistent, small, fixed offsets are not considered security bugs. A read or write to the NULL page results in a non-exploitable crash. If the offset is larger than a page, or if there's uncertainty about whether the offset is controllable, it is considered a security bug.

58.070822

146

0.790185

eng_Latn

0.99722

d0e3476eb86f063e55330f1f715862aa6efd3574

222

md

Markdown

_posts/2016-12-09-t807295995662864384.md

curtclifton/curtclifton.github.io

9e5e1180bbcad7c531cc5dff5e9e1736c8d4eb42

[ "MIT" ]

null

_posts/2016-12-09-t807295995662864384.md

curtclifton/curtclifton.github.io

9e5e1180bbcad7c531cc5dff5e9e1736c8d4eb42

[ "MIT" ]

null

_posts/2016-12-09-t807295995662864384.md

curtclifton/curtclifton.github.io

9e5e1180bbcad7c531cc5dff5e9e1736c8d4eb42

[ "MIT" ]

null

--- layout: post microblog: true audio: photo: date: 2016-12-09 11:48:58 -0700 guid: http://curt.micro.blog/2016/12/09/t807295995662864384.html --- December in Seattle. [https://t.co/EtRwcAcSu9](https://t.co/EtRwcAcSu9)

22.2

71

0.720721

yue_Hant

0.588744

d0e34ee68536591308633125c0a8272bfaf8d84c

754

md

Markdown

packages/react-renderer/demo/list.md

ningpp/lowcode-engine

44ad744aac174f80e06c122a2189f0be75c24e49

[ "MIT" ]

4,047

2021-12-20T07:29:47.000Z

2022-03-31T23:22:40.000Z

packages/react-renderer/demo/list.md

ningpp/lowcode-engine

44ad744aac174f80e06c122a2189f0be75c24e49

[ "MIT" ]

198

2022-01-20T02:51:10.000Z

2022-03-31T13:02:04.000Z

packages/react-renderer/demo/list.md

ningpp/lowcode-engine

44ad744aac174f80e06c122a2189f0be75c24e49

[ "MIT" ]

547

2022-01-11T11:49:54.000Z

2022-03-31T15:08:06.000Z

--- title: 列表 order: 1 --- ````jsx import React, { PureComponent } from 'react'; import ReactDOM from 'react-dom'; import ReactRenderer from '@alilc/lowcode-react-renderer'; import schema from './schemas/list'; import components from './config/components/index'; import utils from './config/utils'; import constants from './config/constants'; class Demo extends PureComponent { static displayName = 'renderer-demo'; render() { return ( <div className="demo"> <ReactRenderer key={schema.fileName} schema={schema} components={components} appHelper={{ utils, constants }} /> </div> ); } } ReactDOM.render(( <Demo /> ), mountNode); ````

19.842105

58

0.599469

eng_Latn

0.585642

d0e354b5f3d8dbab5b59811cbaf9aef25c77eeea

253

md

Markdown

TODO.md

odyssey4me/utopia

45991e26be7d14fc57ab7d80b50fdaa6f0c16287

[ "Apache-2.0" ]

null

TODO.md

odyssey4me/utopia

45991e26be7d14fc57ab7d80b50fdaa6f0c16287

[ "Apache-2.0" ]

null

TODO.md

odyssey4me/utopia

45991e26be7d14fc57ab7d80b50fdaa6f0c16287

[ "Apache-2.0" ]

null

# TODO list 1. Docker for running application containers 2. Docker registry for building and serving images 3. Jenkins for executing things 4. nodepool for single-use jenkins slaves 5. Monitoring with Prometheus 6. Log shipping using the elastic stack

28.111111

50

0.810277

eng_Latn

0.970285

d0e3dc0ba01759f3817c3dbea06a592d6cb6803f

27,277

md

Markdown

docs/controls/data-management/spreadsheet/how-to/validation-to-column.md

DoReMiFaSoLaTiDo/kendo

ae77493280cc149d1c5338becc3505ddb1cf6a8b

[ "Apache-2.0" ]

null

docs/controls/data-management/spreadsheet/how-to/validation-to-column.md

DoReMiFaSoLaTiDo/kendo

ae77493280cc149d1c5338becc3505ddb1cf6a8b

[ "Apache-2.0" ]

1

2022-02-26T12:17:59.000Z

docs/controls/data-management/spreadsheet/how-to/validation-to-column.md

DoReMiFaSoLaTiDo/kendo

ae77493280cc149d1c5338becc3505ddb1cf6a8b

[ "Apache-2.0" ]

null

--- title: Set Validation Rules to Column Ranges page_title: Set Validation Rules to Column Ranges description: "Learn how to set a valdiation rule to a specific column range in Kendo UI Spreadsheet." slug: howto_validationtocolumn_spreadsheet_widget --- # Set Validation Rules to Column Ranges The example below demonstrates how to set a validation rule to a column range. It uses the [`range.validation`](/api/javascript/spreadsheet/range#methods-validation) to apply the validation rule to the specific range. ###### Example ```html <div id="spreadsheet" style="width: 100%;"></div> <script> $(function() { $("#spreadsheet").kendoSpreadsheet({ columns: 26, rows: 30, sheetsbar: false, excel: { // Required to enable Excel Export in some browsers proxyURL: "//demos.telerik.com/kendo-ui/service/export" }, sheets: [ { name: "ContactsForm", mergedCells: [ "A1:E1" ], rows: [ { height: 70, cells: [ { index: 0, value: "CONTACTS FORM", fontSize: 32, background: "rgb(96,181,255)", enable: false, textAlign: "center", color: "white" } ] }, { height: 25, cells: [ { value: "Full Name", background: "rgb(167,214,255)", textAlign: "center", color: "rgb(0,62,117)", enable: false }, { value: "Email", background: "rgb(167,214,255)", textAlign: "center", color: "rgb(0,62,117)", enable: false }, { value: "Date of Birth", background: "rgb(167,214,255)", textAlign: "center", color: "rgb(0,62,117)", enable: false }, { value: "Phone", background: "rgb(167,214,255)", textAlign: "center", color: "rgb(0,62,117)", enable: false }, { value: "Confirmed", background: "rgb(167,214,255)", textAlign: "center", color: "rgb(0,62,117)", enable: false } ] }, { height: 25, cells: [ { value: "Maria Anders", validation: { dataType: "custom", from: "AND(LEN(A3)>3, LEN(A3)200)", allowNulls: true, type: "reject", titleTemplate: "Full Name validation error", messageTemplate: "The full name should be longer than 3 letters and shorter than 200." } }, { value: "[email protected]", validation: { dataType: "custom", from: "AND(NOT(ISERROR(FIND(\"@\", B3))), NOT(ISERROR(FIND(\".\", B3))), ISERROR(FIND(\" \", J1)), LEN(B3)>5)", allowNulls: true, type: "reject", titleTemplate: "Email validation error", messageTemplate: "The value entered is not an valid email address." } }, { value: 31232, format: "m/d/yyyy", validation: { dataType: "date", comparerType: "between", from: "DATEVALUE(\"1/1/1900\")", to: "DATEVALUE(\"1/1/1998\")", allowNulls: true, type: "reject", titleTemplate: "Birth Date validaiton error", messageTemplate: "Birth Date should be between 1899 and 1998 year." } }, { value: 0921123465, validation: { dataType: "custom", from: "AND(ISNUMBER(D3),LEN(D3)<14)", allowNulls: true, type: "reject", titleTemplate: "Phone validation error", messageTemplate: "The value entered is not an valid phone number. Please enter numeric value with less than 14 digits." } }, { value: true } ] }, { height: 25, cells: [ { value: "Ana Trujillo", validation: { dataType: "custom", from: "AND(LEN(A4)>3, LEN(A4)200)", allowNulls: true, type: "reject", titleTemplate: "Full Name validation error", messageTemplate: "The full name should be longer than 3 letters and shorter than 200." } }, { value: "[email protected]", validation: { dataType: "custom", from: "AND(NOT(ISERROR(FIND(\"@\", B4))), NOT(ISERROR(FIND(\".\", B4))), ISERROR(FIND(\" \", J1)), LEN(B4)>5)", allowNulls: true, type: "reject", titleTemplate: "Email validation error", messageTemplate: "The value entered is not an valid email address." } }, { value: 31222, format: "m/d/yyyy", validation: { dataType: "date", comparerType: "between", from: "DATEVALUE(\"1/1/1900\")", to: "DATEVALUE(\"1/1/1998\")", allowNulls: true, type: "reject", titleTemplate: "Birth Date validaiton error", messageTemplate: "Birth Date should be between 1899 and 1998 year." } }, { value: 55554729, validation: { dataType: "custom", from: "AND(ISNUMBER(D4),LEN(D4)<14)", allowNulls: true, type: "reject", titleTemplate: "Phone validation error", messageTemplate: "The value entered is not an valid phone number. Please enter numeric value with less than 14 digits." } }, { value: true } ] }, { height: 25, cells: [ { value: "Antonio Moreno", validation: { dataType: "custom", from: "AND(LEN(A5)>3, LEN(A5)200)", allowNulls: true, type: "reject", titleTemplate: "Full Name validation error", messageTemplate: "The full name should be longer than 3 letters and shorter than 200." } }, { value: "[email protected]", validation: { dataType: "custom", from: "AND(NOT(ISERROR(FIND(\"@\", B5))), NOT(ISERROR(FIND(\".\", B5))), ISERROR(FIND(\" \", J1)), LEN(B5)>5)", allowNulls: true, type: "reject", titleTemplate: "Email validation error", messageTemplate: "The value entered is not an valid email address." } }, { value: 32232, format: "m/d/yyyy", validation: { dataType: "date", comparerType: "between", from: "DATEVALUE(\"1/1/1900\")", to: "DATEVALUE(\"1/1/1998\")", allowNulls: true, type: "reject", titleTemplate: "Birth Date validaiton error", messageTemplate: "Birth Date should be between 1899 and 1998 year." } }, { value: "(5) 555-3932", validation: { dataType: "custom", from: "AND(ISNUMBER(D5),LEN(D5)<14)", allowNulls: true, type: "reject", titleTemplate: "Phone validation error", messageTemplate: "The value entered is not an valid phone number. Please enter numeric value with less than 14 digits." } }, { value: true } ] }, { height: 25, cells: [ { value: "Thomas Hardy", validation: { dataType: "custom", from: "AND(LEN(A6)>3, LEN(A6)200)", allowNulls: true, type: "reject", titleTemplate: "Full Name validation error", messageTemplate: "The full name should be longer than 3 letters and shorter than 200." } }, { value: "[email protected]", validation: { dataType: "custom", from: "AND(NOT(ISERROR(FIND(\"@\", B6))), NOT(ISERROR(FIND(\".\", B6))), ISERROR(FIND(\" \", J1)), LEN(B6)>5)", allowNulls: true, type: "reject", titleTemplate: "Email validation error", messageTemplate: "The value entered is not an valid email address." } }, { value: 21232, format: "m/d/yyyy", validation: { dataType: "date", comparerType: "between", from: "DATEVALUE(\"1/1/1900\")", to: "DATEVALUE(\"1/1/1998\")", allowNulls: true, type: "reject", titleTemplate: "Birth Date validaiton error", messageTemplate: "Birth Date should be between 1899 and 1998 year." } }, { value: 1715557788, validation: { dataType: "custom", from: "AND(ISNUMBER(D6),LEN(D6)<14)", allowNulls: true, type: "reject", titleTemplate: "Phone validation error", messageTemplate: "The value entered is not an valid phone number. Please enter numeric value with less than 14 digits." } }, { value: true } ] }, { height: 25, cells: [ { value: "Christina Toms", validation: { dataType: "custom", from: "AND(LEN(A7)>3, LEN(A7)200)", allowNulls: true, type: "reject", titleTemplate: "Full Name validation error", messageTemplate: "The full name should be longer than 3 letters and shorter than 200." } }, { value: "christina.toms", validation: { dataType: "custom", from: "AND(NOT(ISERROR(FIND(\"@\", B7))), NOT(ISERROR(FIND(\".\", B7))), ISERROR(FIND(\" \", J1)), LEN(B7)>5)", allowNulls: true, type: "reject", titleTemplate: "Email validation error", messageTemplate: "The value entered is not an valid email address." } }, { value: 30102, format: "m/d/yyyy", validation: { dataType: "date", comparerType: "between", from: "DATEVALUE(\"1/1/1900\")", to: "DATEVALUE(\"1/1/1998\")", allowNulls: true, type: "reject", titleTemplate: "Birth Date validaiton error", messageTemplate: "Birth Date should be between 1899 and 1998 year." } }, { value: 0921123465, validation: { dataType: "custom", from: "AND(ISNUMBER(D7),LEN(D7)<14)", allowNulls: true, type: "reject", titleTemplate: "Phone validation error", messageTemplate: "The value entered is not an valid phone number. Please enter numeric value with less than 14 digits." } }, { value: true } ] }, { height: 25, cells: [ { value: "Hanna Moos", validation: { dataType: "custom", from: "AND(LEN(A8)>3, LEN(A8)200)", allowNulls: true, type: "reject", titleTemplate: "Full Name validation error", messageTemplate: "The full name should be longer than 3 letters and shorter than 200." } }, { value: "[email protected]", validation: { dataType: "custom", from: "AND(NOT(ISERROR(FIND(\"@\", B8))), NOT(ISERROR(FIND(\".\", B8))), ISERROR(FIND(\" \", J1)), LEN(B8)>5)", allowNulls: true, type: "reject", titleTemplate: "Email validation error", messageTemplate: "The value entered is not an valid email address." } }, { value: 0, format: "m/d/yyyy", validation: { dataType: "date", comparerType: "between", from: "DATEVALUE(\"1/1/1900\")", to: "DATEVALUE(\"1/1/1998\")", allowNulls: true, type: "reject", titleTemplate: "Birth Date validaiton error", messageTemplate: "Birth Date should be between 1900 and 1998 year." } }, { value: 062108460, validation: { dataType: "custom", from: "AND(ISNUMBER(D8),LEN(D8)<14)", allowNulls: true, type: "reject", titleTemplate: "Phone validation error", messageTemplate: "The value entered is not an valid phone number. Please enter numeric value with less than 14 digits." } }, { value: true } ] }, { height: 25, cells: [ { value: "", validation: { dataType: "custom", from: "AND(LEN(A9)>3, LEN(A9)200)", allowNulls: true, type: "reject", titleTemplate: "Full Name validation error", messageTemplate: "The full name should be longer than 3 letters and shorter than 200." } }, { value: "", validation: { dataType: "custom", from: "AND(NOT(ISERROR(FIND(\"@\", B9))), NOT(ISERROR(FIND(\".\", B9))), ISERROR(FIND(\" \", J1)), LEN(B9)>5)", allowNulls: true, type: "reject", titleTemplate: "Email validation error", messageTemplate: "The value entered is not an valid email address." } }, { value: "", format: "m/d/yyyy", validation: { dataType: "date", comparerType: "between", from: "DATEVALUE(\"1/1/1900\")", to: "DATEVALUE(\"1/1/1998\")", allowNulls: true, type: "reject", titleTemplate: "Birth Date validaiton error", messageTemplate: "Birth Date should be between 1899 and 1998 year." } }, { value: "", validation: { dataType: "custom", from: "AND(ISNUMBER(D9),LEN(D9)<14)", allowNulls: true, type: "reject", titleTemplate: "Phone validation error", messageTemplate: "The value entered is not an valid phone number. Please enter numeric value with less than 14 digits." } }, { value: "" } ] } ], columns: [ { width: 100 }, { width: 215 }, { width: 115 }, { width: 115 }, { width: 115 } ] }, { name: "ListValues", rows: [ //A1:B1 { cells: [ { value: true }, { value: false } ] } ] } ] }); //Get the column range var range = $("#spreadsheet").data("kendoSpreadsheet").activeSheet().range("E3:E100"); //Apply the validation rule range.validation({ dataType: "list", from: "ListValues!A$1:B$1", allowNulls: true, type: "reject", titleTemplate: "Invalid value", messageTemplate: "Valid values are 'true' and 'false'." }); }); </script> ``` ## See Also Other articles on the Kendo UI Spreadsheet: * [Spreadsheet JavaScript API Reference](/api/javascript/ui/spreadsheet) * [How to Bind Charts to Sheet Data]({% slug howto_bindcharttosheet_spreadsheet_widget %}) * [How to Get Flagged Cells Containing Invalid Values]({% slug howto_get_flagged_cells_containing_invalid_values_spreadsheet_widget %})

52.455769

217

0.282839

eng_Latn

0.518749

d0e4289b42e33579efaf2fd7e2cb922e0291b125

14,792

md

Markdown

articles/virtual-machines/linux/create-ssh-keys-detailed.md

nsrau/azure-docs.it-it

9935e44b08ef06c214a4c7ef94d12e79349b56bc

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

null

articles/virtual-machines/linux/create-ssh-keys-detailed.md

nsrau/azure-docs.it-it

9935e44b08ef06c214a4c7ef94d12e79349b56bc

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

null

articles/virtual-machines/linux/create-ssh-keys-detailed.md

nsrau/azure-docs.it-it

9935e44b08ef06c214a4c7ef94d12e79349b56bc

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

null

--- title: Procedura dettagliata per creare una coppia di chiavi SSH description: Informazioni sulla procedura dettagliata per creare e gestire una coppia di chiavi SSH pubblica e privata per le VM Linux in Azure. author: cynthn ms.service: virtual-machines-linux ms.topic: how-to ms.date: 07/31/2020 ms.author: cynthn ms.openlocfilehash: 34a84ed333172ea0931c529d2dbeee1b774ae8c5 ms.sourcegitcommit: a43a59e44c14d349d597c3d2fd2bc779989c71d7 ms.translationtype: MT ms.contentlocale: it-IT ms.lasthandoff: 11/25/2020 ms.locfileid: "96016371" --- # <a name="detailed-steps-create-and-manage-ssh-keys-for-authentication-to-a-linux-vm-in-azure"></a>Procedura dettagliata: Creare e gestire chiavi SSH per l'autenticazione in una macchina virtuale Linux in Azure Con una coppia di chiavi SSH (Secure Shell) è possibile creare una macchina virtuale Linux che usa chiavi SSH per l'autenticazione. Questo articolo illustra come creare e usare una coppia di file di chiavi pubblica/privata RSA SSH per le connessioni client SSH. Per i comandi rapidi, vedere [Come creare e usare una coppia di chiavi SSH pubblica e privata per le macchine virtuali Linux in Azure](mac-create-ssh-keys.md). Per creare chiavi SSH e usarle per connettersi a da un computer **Windows** , vedere [come usare le chiavi SSH con Windows in Azure](ssh-from-windows.md). È anche possibile usare la [portale di Azure](../ssh-keys-portal.md) per creare e gestire le chiavi SSH per la creazione di macchine virtuali nel portale. [!INCLUDE [virtual-machines-common-ssh-overview](../../../includes/virtual-machines-common-ssh-overview.md)] [!INCLUDE [virtual-machines-common-ssh-support](../../../includes/virtual-machines-common-ssh-support.md)] ## <a name="ssh-keys-use-and-benefits"></a>Uso e vantaggi delle chiavi SSH Quando si crea una VM di Azure specificando la chiave pubblica, Azure copia la chiave pubblica (nel formato `.pub`) nella cartella `~/.ssh/authorized_keys` nella VM. Le chiavi SSH in `~/.ssh/authorized_keys` vengono usate per fare in modo che il client trovi la chiave privata corrispondente in una connessione SSH. In una macchina virtuale Linux di Azure che usa chiavi SSH per l'autenticazione, Azure configura il server SSHD in modo da non consentire l'accesso con password, ma solo con le chiavi SSH. La creazione di una VM Linux di Azure con chiavi SSH consente di proteggere la distribuzione delle VM e di risparmiare il tipico passaggio di configurazione post-distribuzione della disabilitazione delle password nel `sshd_config` file. Se non si vogliono usare chiavi SSH, è possibile configurare la VM Linux in modo che usi l'autenticazione mediante password. Se la VM non è connessa a Internet, l'utilizzo di password può essere sufficiente. È comunque necessario gestire le password per ogni VM Linux e mantenere criteri e prassi di integrità per le password stesse, quali una lunghezza minima e l'aggiornamento periodico. ## <a name="generate-keys-with-ssh-keygen"></a>Generare chiavi con ssh-keygen Per creare le chiavi, un comando preferito è `ssh-keygen`, disponibile con le utilità OpenSSH in Azure Cloud Shell, un host macOS o Linux e Windows 10. `ssh-keygen` presenta una serie di domande e quindi scrive una chiave privata e una chiave pubblica corrispondente. Per impostazione predefinita, le chiavi SSH vengono conservate nella directory `~/.ssh`. Se non si dispone di una directory `~/.ssh`, questa viene creata automaticamente dal comando `ssh-keygen` con le autorizzazioni corrette. ### <a name="basic-example"></a>Esempio di base Il `ssh-keygen` comando seguente genera file di chiave pubblica e privata SSH RSA a 4096 bit per impostazione predefinita nella `~/.ssh` Directory. Se nel percorso corrente è presente una coppia di chiavi SSH, questi file vengono sovrascritti. ```bash ssh-keygen -m PEM -t rsa -b 4096 ``` ### <a name="detailed-example"></a>Esempio dettagliato L'esempio seguente mostra opzioni di comando aggiuntive per creare una coppia di chiavi SSH RSA. Se nel percorso corrente è presente una coppia di chiavi SSH, questi file vengono sovrascritti. ```bash ssh-keygen \ -m PEM \ -t rsa \ -b 4096 \ -C "azureuser@myserver" \ -f ~/.ssh/mykeys/myprivatekey \ -N mypassphrase ``` **Descrizione del comando** `ssh-keygen`: programma usato per creare le chiavi. `-m PEM` = formattare la chiave come PEM `-t rsa` = tipo di chiave da creare, in questo caso nel formato RSA `-b 4096` = numero di bit nella chiave, in questo caso 4096 `-C "azureuser@myserver"`: commento aggiunto alla fine del file della chiave pubblica per identificarla facilmente. Come commento viene usato in genere un indirizzo di posta elettronica, ma è possibile usare qualsiasi elemento, in base alle esigenze dell'infrastruttura. `-f ~/.ssh/mykeys/myprivatekey` = il nome del file della chiave privata, se si sceglie di non usare il nome predefinito. Un file di chiave pubblica corrispondente con finale `.pub` viene generato nella stessa directory. La directory deve esistere. `-N mypassphrase` = una passphrase aggiuntiva necessaria per accedere al file della chiave privata. ### <a name="example-of-ssh-keygen"></a>Esempio di ssh-keygen ```bash ssh-keygen -t -m PEM rsa -b 4096 -C "azureuser@myserver" Generating public/private rsa key pair. Enter file in which to save the key (/home/azureuser/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/azureuser/.ssh/id_rsa. Your public key has been saved in /home/azureuser/.ssh/id_rsa.pub. The key fingerprint is: SHA256:vFfHHrpSGQBd/oNdvNiX0sG9Vh+wROlZBktNZw9AUjA azureuser@myserver The key's randomart image is: +---[RSA 4096]----+ | .oE=*B*+ | | o+o.*++| | .oo++*| | . .B+.O| | S o=BO.| | . .o++o | | . ... . | | .. . | | .. | +----[SHA256]-----+ ``` #### <a name="saved-key-files"></a>I file delle chiavi salvati `Enter file in which to save the key (/home/azureuser/.ssh/id_rsa): ~/.ssh/id_rsa` Nome della coppia di chiavi per questo articolo. Per impostazione predefinita viene creata una coppia di chiavi denominata `id_rsa`; alcuni strumenti potrebbero aspettarsi un file della chiave privata con il nome `id_rsa`, quindi è utile averlo. La directory `~/.ssh/` è la posizione predefinita per le coppie di chiavi SSH e il file config SSH. Se non viene specificato con un percorso completo, `ssh-keygen` crea le chiavi nella directory di lavoro corrente, non nel percorso `~/.ssh` predefinito. #### <a name="list-of-the-ssh-directory"></a>Elenco della directory `~/.ssh` ```bash ls -al ~/.ssh -rw------- 1 azureuser staff 1675 Aug 25 18:04 id_rsa -rw-r--r-- 1 azureuser staff 410 Aug 25 18:04 id_rsa.pub ``` #### <a name="key-passphrase"></a>Passphrase della chiave `Enter passphrase (empty for no passphrase):` È *vivamente* consigliabile aggiungere una passphrase alla chiave privata. Senza una passphrase che protegga il file della chiave, chiunque abbia il file può usarlo per accedere a qualsiasi server che abbia la chiave pubblica corrispondente. L'aggiunta di una passphrase offre protezione nel caso in cui qualcuno riesca ad accedere al file della chiave privata, lasciando all'utente il tempo necessario per cambiare le chiavi. ## <a name="generate-keys-automatically-during-deployment"></a>Generare chiavi automaticamente durante la distribuzione Se si usa l'[interfaccia della riga di comando di Azure](/cli/azure) per creare la VM, facoltativamente è possibile creare i file della chiave SSH pubblica e privata eseguendo il comando [creare az vm ](/cli/azure/vm) con l'opzione `--generate-ssh-keys`. Le chiavi vengono archiviate nella directory ~/.ssh. Si noti che questa opzione di comando non implica la sovrascrittura delle chiavi se sono già presenti in tale percorso. ## <a name="provide-ssh-public-key-when-deploying-a-vm"></a>Fornire la chiave SSH pubblica quando si distribuisce una VM Per creare una VM Linux che usa le chiavi SSH per l'autenticazione, fornire la chiave SSH pubblica quando si crea la VM tramite il portale di Azure, l'interfaccia della riga di comando, i modelli di Resource Manager o altri metodi. Quando si usa il portale, immettere la chiave pubblica stessa. Se si usa l'[interfaccia della riga di comando di Azure](/cli/azure) per creare la macchina virtuale con una chiave pubblica esistente, specificare il valore o il percorso della chiave pubblica eseguendo il comando [creare az vm](/cli/azure/vm) con l'opzione `--ssh-key-value`. Se non si ha familiarità con il formato della chiave SSH pubblica, è possibile visualizzare la chiave pubblica eseguendo `cat` come segue, sostituendo `~/.ssh/id_rsa.pub` con il proprio percorso del file della chiave pubblica: ```bash cat ~/.ssh/id_rsa.pub ``` L'output è simile al seguente (con alcune modifiche): ``` ssh-rsa XXXXXXXXXXc2EAAAADAXABAAABAXC5Am7+fGZ+5zXBGgXS6GUvmsXCLGc7tX7/rViXk3+eShZzaXnt75gUmT1I2f75zFn2hlAIDGKWf4g12KWcZxy81TniUOTjUsVlwPymXUXxESL/UfJKfbdstBhTOdy5EG9rYWA0K43SJmwPhH28BpoLfXXXXXG+/ilsXXXXXKgRLiJ2W19MzXHp8z3Lxw7r9wx3HaVlP4XiFv9U4hGcp8RMI1MP1nNesFlOBpG4pV2bJRBTXNXeY4l6F8WZ3C4kuf8XxOo08mXaTpvZ3T1841altmNTZCcPkXuMrBjYSJbA8npoXAXNwiivyoe3X2KMXXXXXdXXXXXXXXXXCXXXXX/ azureuser@myserver ``` Se si copiano e si incollano i contenuti del file della chiave pubblica nel portale di Azure o in un modello di Resource Manager, verificare di non introdurre spazi o interruzioni di riga aggiuntive. Se ad esempio si usa macOS, è possibile inviare tramite pipe il file della chiave pubblica, che per impostazione predefinita è `~/.ssh/id_rsa.pub`, a **pbcopy** per copiare i contenuti. Anche altri programmi Linux eseguono questa operazione, ad esempio `xclip`. Se si preferisce usare una chiave pubblica in un formato a più righe, è possibile generare una chiave RFC4716 formattata in un contenitore con estensione pem dalla chiave pubblica creata in precedenza. Per creare una chiave in formato RFC4716 da una chiave pubblica SSH esistente: ```bash ssh-keygen \ -f ~/.ssh/id_rsa.pub \ -e \ -m RFC4716 > ~/.ssh/id_ssh2.pem ``` ## <a name="ssh-to-your-vm-with-an-ssh-client"></a>Connessione SSH alla VM con un client SSH Con la chiave pubblica distribuita nella VM di Azure e la chiave privata nel sistema locale, stabilire una connessione SSH alla VM usando l'indirizzo IP o il nome DNS della VM. Sostituire *azureuser* e *myvm.westus.cloudapp.azure.com* nel comando seguente con il nome utente dell'amministratore e il nome di dominio completo (o indirizzo IP): ```bash ssh [email protected] ``` Se durante la creazione della coppia di chiavi è stata specificata una passphrase, immetterla quando viene richiesta durante la procedura di accesso. Il server viene aggiunto alla cartella `~/.ssh/known_hosts` e non verrà chiesto di connettersi di nuovo finché la chiave pubblica nella VM di Azure non viene modificata o il nome server viene rimosso da `~/.ssh/known_hosts`. Se la macchina virtuale usa i criteri di accesso JIT, è necessario richiedere l'accesso per connettersi alla macchina virtuale. Per altre informazioni sui criteri JIT, vedere [Gestire l'accesso alle macchine virtuali con la funzionalità JIT (Just-in-Time)](../../security-center/security-center-just-in-time.md). ## <a name="use-ssh-agent-to-store-your-private-key-passphrase"></a>Usare ssh-agent per archiviare la passphrase della chiave privata Per evitare di digitare la passphrase del file della chiave privata a ogni accesso SSH, è possibile usare `ssh-agent` per memorizzare nella cache la passphrase del file della chiave privata. Se si usa un Mac, il portachiavi macOS archivia in modo sicuro le passphrase delle chiavi private quando si chiama `ssh-agent`. Verificare e usare `ssh-agent` e `ssh-add` per fornire informazioni al sistema SSH sui file delle chiavi, in maniera che non sia necessario usare la passphrase in modo interattivo. ```bash eval "$(ssh-agent -s)" ``` Ora aggiungere la chiave privata a `ssh-agent` usando il comando `ssh-add`. ```bash ssh-add ~/.ssh/id_rsa ``` La passphrase della chiave privata è ora archiviata in `ssh-agent`. ## <a name="use-ssh-copy-id-to-copy-the-key-to-an-existing-vm"></a>Uso di ssh-copy-id per copiare la chiave in una VM esistente Se è già stata creata una macchina virtuale, è possibile aggiungere una nuova chiave pubblica SSH alla VM Linux usando `ssh-copy-id` . ```bash ssh-copy-id -i ~/.ssh/id_rsa.pub azureuser@myserver ``` ## <a name="create-and-configure-an-ssh-config-file"></a>Creare e configurare un file config SSH Si può creare e configurare un file di configurazione SSH (`~/.ssh/config`) per velocizzare gli accessi e ottimizzare il comportamento del client SSH. L'esempio seguente mostra una semplice configurazione che è possibile usare per accedere rapidamente come utente a una macchina virtuale specifica usando la chiave privata SSH predefinita. Creare il file. ```bash touch ~/.ssh/config ``` Modificare il file per aggiungere la nuova configurazione SSH ```bash vim ~/.ssh/config ``` Aggiungere le impostazioni di configurazione appropriate per la VM host. In questo esempio, il nome della macchina virtuale è *MyVM* e il nome dell'account è *azureuser*. ```bash # Azure Keys Host myvm Hostname 102.160.203.241 User azureuser # ./Azure Keys ``` È possibile aggiungere configurazioni per host aggiuntivi per consentire a ciascuno di usare la propria coppia di chiavi dedicata. Per altre opzioni di configurazione avanzate, vedere [File di configurazione SSH](https://www.ssh.com/ssh/config/). Con una coppia di chiavi SSH e un file config SSH configurato, è ora possibile accedere alla macchina virtuale Linux in modo rapido e sicuro. Quando si esegue il comando seguente, SSH individua e carica tutte le impostazioni dal blocco `Host myvm` nel file di configurazione SSH. ```bash ssh myvm ``` La prima volta che si accede a un server usando una chiave SSH, il comando richiede la passphrase per il file della chiave. ## <a name="next-steps"></a>Passaggi successivi Il prossimo passaggio consiste nel creare VM Linux di Azure usando la nuova chiave pubblica SSH. Le macchine virtuali di Azure create con una chiave pubblica SSH per l'accesso sono più protette rispetto alle macchine virtuali create con il metodo di accesso predefinito basato su password. * [Creare una macchina virtuale Linux con il portale di Azure](quick-create-portal.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json) * [Creare una macchina virtuale Linux con l'interfaccia della riga di comando di Azure](quick-create-cli.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json) * [Creare una VM Linux usando un modello di Azure](create-ssh-secured-vm-from-template.md?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json)

62.151261

741

0.772985

ita_Latn

0.997402

d0e48bd6e29d832413a7922d1a94d2c2809176fa

531

md

Markdown

build/docs/WorkPlanReference.md

cjohnson-ctl/platform-client-sdk-python

38ce53bb8012b66e8a43cc8bd6ff00cf6cc99100

[ "MIT" ]

10

2019-02-22T00:27:08.000Z

2021-09-12T23:23:44.000Z

build/docs/WorkPlanReference.md

cjohnson-ctl/platform-client-sdk-python

38ce53bb8012b66e8a43cc8bd6ff00cf6cc99100

[ "MIT" ]

5

2018-06-07T08:32:00.000Z

2021-07-28T17:37:26.000Z

build/docs/WorkPlanReference.md

cjohnson-ctl/platform-client-sdk-python

38ce53bb8012b66e8a43cc8bd6ff00cf6cc99100

[ "MIT" ]

6

2020-04-09T17:43:07.000Z

2022-02-17T08:48:05.000Z

--- title: WorkPlanReference --- ## WorkPlanReference ## Properties |Name | Type | Description | Notes| |------------ | ------------- | ------------- | -------------| | **id** | **str** | The globally unique identifier for the object. | [optional] | | **management_unit** | [**ManagementUnitReference**](ManagementUnitReference.html) | The management unit to which this work plan belongs. Nullable in some routes | [optional] | | **self_uri** | **str** | The URI for this object | [optional] | {: class="table table-striped"}

33.1875

178

0.60452

eng_Latn

0.762325

d0e512d6e14eb694eecdf48ec2b46699895a16d5

2,227

md

Markdown

AudioPlayer/README.md

bakterian/WeMosSketches

76f895ecc0640195402a5816dec08a44fc026503

[ "MIT" ]

1

2020-02-21T06:28:06.000Z

AudioPlayer/README.md

bakterian/WeMosSketches

76f895ecc0640195402a5816dec08a44fc026503

[ "MIT" ]

null

AudioPlayer/README.md

bakterian/WeMosSketches

76f895ecc0640195402a5816dec08a44fc026503

[ "MIT" ]

null

# AudioPlayer This is a ardruino project of a portable speaker. It is planned to use a WiFi Server for music control As for the source uploaded mp3s or a internet radio can be used. ### Hardware List: - Esp 8266 Wemos D1 Mini Board - LiPo battery holder with a battery charing cicruit - Adafruit I2S 3W Class D Amplifier Breakout MAX98357A - 3W 4Ohm Audio Speaker - SD Card Holder with SD-card a 4Gb model was used - LED's for battery charing status indication - USB connectors - Plastic Box - On/Off Switch - Cables and a Uniwersal PCB Board ### GPIO Connections: ### Prerequisties For building the application either the Arduino IDE or a Makefile approach can be used. When chosing the latter please download or clone this arduino esp makefile builder which is referenced from the project. [Esp8266-Arduino-Makefile](https://github.com/bakterian/ESP8266Audio/releases/tag/RL_001.000.000) After the download is done please refer to a dedicated readme and trigger the esp-sdk core source and libraries. ### Installation It is recommended to use released version or just download/clone the master. For installing the AudioPlayer just execute the installLibraries bash script. ### Required Binaries: - wget - jq - unzip - make - gcc - gcc-g++ Please note that without downloading and installing Esp8266-Arduino-Makefile (with default repo-folder naming) the installation scripts will fail. The library dependencies can be installed from linux or cygwin like so: ```bassh $ bash installLibraries.bash ``` ### Building When both the AudioPlayer and Arduino-Makefile are configured just run make to build the application. ```bassh $ make -j8 ``` Software updates can also performed using this make file, ```bassh $ make upload ``` ### Development When doing development and adding new librarry depencies please bear in mind to modify the libraries.json files. ### TODO: - Remove I2C Display Support (display will be connected to mqtt client, which will print on notification) - Move hlper functions to additional file and Classes - Add Unit tests and configure cirlce Ci - Add multiple mp3 files in folders - Add support for two buttons and physicly add two connectors

33.742424

146

0.763808

eng_Latn

0.993184

d0e72154fcafa39001914ad4a195ec3615fdb236

960

md

Markdown

docs/reference/images/show-frame.md

MUSELAB/pxt-microbit

1a3efe74a81c497eb9965704770a0446b6d8ddcb

[ "MIT" ]

316

2016-05-23T17:17:33.000Z

2019-05-06T10:47:21.000Z

docs/reference/images/show-frame.md

aquillavdberg/pxt-microbit

1ae66892d043f9eed9ff39394026d2aaf699fdba

[ "MIT" ]

3,659

2019-05-07T05:58:29.000Z

2022-03-29T21:54:08.000Z

docs/reference/images/show-frame.md

aquillavdberg/pxt-microbit

1ae66892d043f9eed9ff39394026d2aaf699fdba

[ "MIT" ]

324

2019-05-07T13:22:18.000Z

2022-03-31T09:00:19.000Z

# Show Frame The show frame function. Display an [Image](/reference/images/image) on the @boardname@'s [LED screen](/device/screen) ## JavaScript ```sig export function showFrame(img: micro_bit.Image, frame: number) ``` ## Parameters * index - [Number](/types/number); which frame of the image to display ## Difference from `plot frame` The `show frame` function is the same as [plot frame](/reference/images/plot-frame), but contains a built-in delay after the LED screen has been updated (whereas `plot frame` has no built-in delay) ## Example ```blocks let img = images.createImage(` # . . . # # . . . # . # . # . . # # # . . . # . . . # # # . . # . # . . # # # . # . . . # # . . . # `) img.showFrame(1) ``` ## See also [create image](/reference/images/create-image), [show animation](/reference/basic/show-animation), [image](/reference/images/image), [show image](/reference/images/show-image), [scroll image](/reference/images/scroll-image)

25.263158

223

0.653125

eng_Latn

0.776931

d0e73700940701cf97ce1a4bbb0f92a42b49983c

23

md

Markdown

_posts/0000-01-02-zlweicoder.md

zlweicoder/github-slideshow

6b92e48ca17daf72f90911b64c4aa00d20b992bc

[ "MIT" ]

null

_posts/0000-01-02-zlweicoder.md

zlweicoder/github-slideshow

6b92e48ca17daf72f90911b64c4aa00d20b992bc

[ "MIT" ]

3

2019-10-10T04:33:28.000Z

2019-10-24T05:40:56.000Z

_posts/0000-01-02-zlweicoder.md

zlweicoder/github-slideshow

6b92e48ca17daf72f90911b64c4aa00d20b992bc

[ "MIT" ]

null

Test create file dedad

7.666667

16

0.826087

ita_Latn

0.511126

d0e7dc90baacd280bfdf7bb5a35ec9a84adeb1fb

1,248

md

Markdown

challenges/001.md

jasonleekennedy/knowledge_base

fe1edd008fe0d75695592815233e811c9d60f148

[ "Unlicense" ]

28

2018-09-08T10:36:46.000Z

2022-03-14T15:34:53.000Z

challenges/001.md

jasonleekennedy/knowledge_base

fe1edd008fe0d75695592815233e811c9d60f148

[ "Unlicense" ]

3

2019-10-12T19:25:10.000Z

2020-09-08T12:34:49.000Z

challenges/001.md

jasonleekennedy/knowledge_base

fe1edd008fe0d75695592815233e811c9d60f148

[ "Unlicense" ]

7

2019-07-27T15:34:17.000Z

2022-03-03T23:17:54.000Z

# Challenge 1 Be productive on a new, _or existing,_ project and bring your ideas to life. Put in some time and effort into making and track what you've started and completed on a task list to review later. ## Do something, anything, productive! - Start a new project, game, application or anything. - Continue working on an on-going project. - Do as much as you can in a week. - Track what tasks you finish, big or small. - You have 7 days to do as many things as you can. ## Due Date While you can perform this challenge at any time, the projects will be shared on stream October 20th 2019. Submit your project and give a list of tasks completed by midnight October 19th 2019. ## To Submit (wip) Presently, just submit via a comment on the ["Challenge 001 Submission"](https://github.com/timbeaudet/knowledge_base/issues/3) issue ticket with the format specified. Submission process is new and very open for ideas. The goal is track submissions long term, allowing anyone to submit at anytime, link to the project and track the list of things completed. Ideally, eventually, it would be nice to see what challenges a particluar user completed as well. Objective is to reduce friction but track who did what and when. ## Submissions

48

287

0.770032

eng_Latn

0.999625

d0e7e1e87249b119be0fa8b64a6f6e2b650d58e8

208

md

Markdown

translations/ru-RU/data/reusables/dotcom_billing/same-payment-method.md

kyawburma/docs

0ff7de03be7c2432ced123aca17bfbf444bee1bf

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

11,698

2020-10-07T16:22:18.000Z

2022-03-31T18:54:47.000Z

translations/ru-RU/data/reusables/dotcom_billing/same-payment-method.md

kyawburma/docs

0ff7de03be7c2432ced123aca17bfbf444bee1bf

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

8,317

2020-10-07T16:26:58.000Z

2022-03-31T23:24:25.000Z

translations/ru-RU/data/reusables/dotcom_billing/same-payment-method.md

kyawburma/docs

0ff7de03be7c2432ced123aca17bfbf444bee1bf

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

48,204

2020-10-07T16:15:45.000Z

2022-03-31T23:50:42.000Z

When you update your payment method for your account's {% data variables.product.prodname_dotcom %} subscription, your new payment method is automatically added to your other subscriptions for paid products.

104

207

0.822115

eng_Latn

0.997722

d0ea216afa874ebc11632129375b44f58a09fc64

626

md

Markdown

archives/2021-12-01.md

erbanku/v2ex-hot-hub

746387344a12bbb5265a65511af95f9e3eddd6c1

[ "MIT" ]

null

archives/2021-12-01.md

erbanku/v2ex-hot-hub

746387344a12bbb5265a65511af95f9e3eddd6c1

[ "MIT" ]

null

archives/2021-12-01.md

erbanku/v2ex-hot-hub

746387344a12bbb5265a65511af95f9e3eddd6c1

[ "MIT" ]

null

# v2ex热议话题 `最后更新时间：2021-12-01 11:13:55 +0800` 1. [1password 家庭版订阅到期账户被删](https://www.v2ex.com/t/818989) 1. [为啥人不管在梦里梦到多离谱的东西，都不会去怀疑？](https://www.v2ex.com/t/818999) 1. [办公室听 B 站课程听得耳朵疼，怎么解](https://www.v2ex.com/t/819006) 1. [WOL 远程开机插座，仅 23.5](https://www.v2ex.com/t/819091) 1. [Apple Cash 看起来是不太会进中国了](https://www.v2ex.com/t/819141) 1. [一个月过去了，大家最后是选择 14 还是 16 寸](https://www.v2ex.com/t/818998) 1. [老哥们，我老大在循环里写 Thread.sleep，到处都这么写，有问题吗](https://www.v2ex.com/t/819192) 1. [Java 后端怎么快速写前端](https://www.v2ex.com/t/819081) 1. [你们给你们的 mbp 贴膜戴套了吗？](https://www.v2ex.com/t/818979) 1. [LCD 党何去何从](https://www.v2ex.com/t/819189)

39.125

73

0.704473

yue_Hant

0.802503