text:
# ![LOGO](logo.png) Amazon DynamoDB Streams **flow**ground Connector

## Description

A generated **flow**ground connector for the Amazon DynamoDB Streams API (version 2012-08-10).

Generated from: https://api.apis.guru/v2/specs/amazonaws.com/streams.dynamodb/2012-08-10/swagger.json

Generated at: 2019-07-08T14:13:28+03:00

## API Description

<fullname>Amazon DynamoDB</fullname>
Amazon DynamoDB Streams provides API actions for accessing streams and processing stream records. To learn more about application development with Streams, see Capturing Table Activity with DynamoDB Streams in the Amazon DynamoDB Developer Guide.

## Authorization

Supported authorization schemes:
- API Key
## Actions

### DescribeStream

Returns information about a stream, including the current status of the stream, its Amazon Resource Name (ARN), the composition of its shards, and its corresponding DynamoDB table.
 <note>
You can call DescribeStream at a maximum rate of 10 times per second.
 </note>
Each shard in the stream has a SequenceNumberRange associated with it. If the SequenceNumberRange has a StartingSequenceNumber but no EndingSequenceNumber, then the shard is still open (able to receive more stream records). If both StartingSequenceNumber and EndingSequenceNumber are present, then that shard is closed and can no longer receive more data.

#### Input Parameters
* `Action` - _required_
* `Version` - _required_
* `X-Amz-Content-Sha256` - _optional_
* `X-Amz-Date` - _optional_
* `X-Amz-Algorithm` - _optional_
* `X-Amz-Credential` - _optional_
* `X-Amz-Security-Token` - _optional_
* `X-Amz-Signature` - _optional_
* `X-Amz-SignedHeaders` - _optional_

### GetRecords

Retrieves the stream records from a given shard.

Specify a shard iterator using the ShardIterator parameter. The shard iterator specifies the position in the shard from which you want to start reading stream records sequentially. If there are no stream records available in the portion of the shard that the iterator points to, GetRecords returns an empty list. Note that it might take multiple calls to get to a portion of the shard that contains stream records.
 <note>
 GetRecords can retrieve a maximum of 1 MB of data or 1000 stream records, whichever comes first.
 </note>

#### Input Parameters
* `Action` - _required_
* `Version` - _required_
* `X-Amz-Content-Sha256` - _optional_
* `X-Amz-Date` - _optional_
* `X-Amz-Algorithm` - _optional_
* `X-Amz-Credential` - _optional_
* `X-Amz-Security-Token` - _optional_
* `X-Amz-Signature` - _optional_
* `X-Amz-SignedHeaders` - _optional_

### GetShardIterator

Returns a shard iterator. A shard iterator provides information about how to retrieve the stream records from within a shard. Use the shard iterator in a subsequent GetRecords request to read the stream records from the shard.
 <note>
A shard iterator expires 15 minutes after it is returned to the requester.
 </note>

#### Input Parameters
* `Action` - _required_
* `Version` - _required_
* `X-Amz-Content-Sha256` - _optional_
* `X-Amz-Date` - _optional_
* `X-Amz-Algorithm` - _optional_
* `X-Amz-Credential` - _optional_
* `X-Amz-Security-Token` - _optional_
* `X-Amz-Signature` - _optional_
* `X-Amz-SignedHeaders` - _optional_

### ListStreams

Returns an array of stream ARNs associated with the current account and endpoint. If the TableName parameter is present, then ListStreams will return only the streams ARNs for that table.
 <note>
You can call ListStreams at a maximum rate of 5 times per second.
 </note>

#### Input Parameters
* `Action` - _required_
* `Version` - _required_
* `X-Amz-Content-Sha256` - _optional_
* `X-Amz-Date` - _optional_
* `X-Amz-Algorithm` - _optional_
* `X-Amz-Credential` - _optional_
* `X-Amz-Security-Token` - _optional_
* `X-Amz-Signature` - _optional_
* `X-Amz-SignedHeaders` - _optional_

## License

**flow**ground :- Telekom iPaaS / amazonaws-com-streams-dynamodb-connector

Copyright © 2019, [Deutsche Telekom AG](https://www.telekom.de)

contact<EMAIL_ADDRESS>
All files of this connector are licensed under the Apache 2.0 License. For details
see the file LICENSE on the toplevel directory.


text:
# Contributing to Nacos

Welcome to Nacos! This document is a guideline about how to contribute to Nacos.
If you find something incorrect or missing, please leave comments / suggestions.

## Before you get started

### Code of Conduct

Please make sure to read and observe our [Code of Conduct](./CODE_OF_CONDUCT.md).

## Contributing

We are always very happy to have contributions, whether for typo fix, bug fix or big new features.
Please do not ever hesitate to ask a question or send a pull request.

We strongly value documentation and integration with other projects such as Spring Cloud, Kubernetes, Dubbo, etc.
We are very glad to accept improvements for these aspects.

### Open or Pickup an issue / PR

We use [GitHub Issues](https://github.com/alibaba/Nacos/issues) and [Pull Requests](https://github.com/alibaba/Nacos/pulls) for trackers.

If you find a typo in document, find a bug in code, or want new features, or want to give suggestions,
you can [open an issue on GitHub](https://github.com/alibaba/Nacos/issues/new) to report it.
Please follow the guideline message in the issue template.

If you just want to contribute directly you can choose the issue below.

 - [Contribution Welcome](https://github.com/alibaba/nacos/labels/contribution%20welcome): Heavily needed issue, but currently short of hand.
 - [good first issue](https://github.com/alibaba/nacos/labels/good%20first%20issue): Good for newcomers, new comer can pickup one for warm-up.

Now if you want to contribute, please follow the [contribution workflow](#github-workflow) and create a new pull request.

### Begin your contribution

We use the `develop` branch as the development branch, which indicates that this is a unstable branch.

Here is the workflow for contributors:

1. Fork to your own
2. Clone fork to local repository
3. Create a new branch and work on it
4. Keep your branch in sync
5. Commit your changes (make sure your commit message concise)
6. Push your commits to your forked repository
7. Create a pull request.

When creating pull request:

1. Please follow [the pull request template](./.github/PULL_REQUEST_TEMPLATE.md).
2. Please make sure the PR has a corresponding issue.
3. If your PR contains large changes, e.g. component refactor or new components, please write detailed documents
about its design and usage.
4. Note that a single PR should not be too large. If heavy changes are required, it's better to separate the changes
to a few individual PRs.
5. After creating a PR, one or more reviewers will be assigned to the pull request.
6. Before merging a PR, squash any fix review feedback, typo, merged, and rebased sorts of commits.
The final commit message should be clear and concise.

If your PR contains large changes, e.g. component refactor or new components, please write detailed documents
about its design and usage.

### Code review guidance

Our PMC will rotate reviewing the code to make sure all the PR will be reviewed timely and by at least one committer before merge. If we aren't doing our job (sometimes we drop things). And as always, we welcome volunteers for code review.

Some principles:

- Readability - Important code should be well-documented. API should have Javadoc. Code style should be complied with the existing one.
- Elegance: New functions, classes or components should be well designed.
- Testability - 80% of the new code should be covered by unit test cases.
- Maintainability - Comply with our [PMD spec](style/codeStyle.xml), and 3-month-frequency update should be maintained at least.

branch_name: refs/heads/master

extension: md

gha_language: Java

license_type: permissive


text:
Allihoopa Desktop SDK
=====================

_Technology preview_

The Allihoopa Desktop SDK provides an interface to the [Allihoopa][] music collaboration service for apps running on MacOS and Windows.

The SDK is a thin `C` interface provided in source form, and has no external dependencies except for what is provided by the C standard library.

The SDK connects to a locally installed Allihoopa App that provides all user interaction and service communication.
This effectively decouples the host app from that complexity, and lets the host app and Allihoopa App have separate update cycles.

## Installation

The API is exposed in the `allihoopa.h` header, and the implementation is in `allihoopa.c`. Simply copy these two into your project and make them compile and link as usual.

>Setting the DEBUG define to a non-zero value will enable some level of tracing to stderr.

## API concepts

To keep the API free of dependencies, and support a wide range of implementation environments, we have set on a couple of simple concepts.

*   **All API calls return an error code**

    Calls will either succeed or fail with an error code.
    A successful call means that a request was successfully sent to the Allihoopa App, and that a response is to be expected.
    Failed calls will not generate responses.

*   **API calls are asynchronous**

    Calls to the SDK will respond quickly, even if the actual request takes a while to execute.
    If the caller is interested in the response, it can be fetched using a separate call.

*   **Complex data is passed as UTF-8 - encoded JSON.**

    This is to avoid having to allocate and manage complex data structures in plain `C`.
    Complex data is always owned by the caller; if you allocated the memory, you free it. *This implies that data returned in callbacks is only valid during that callback, and should be copied if needed.*

*   **Blob files**

    Big binary data, such as audio and image files, are passed as URLs in the JSON data structures. The SDK accepts `http:`, `https:`, `data:` and `file:` protocols. Using the `file:` protocol refers to a client specified temporary directory, and is the recommended method. See the `AHinit` call.

*   **Requests can be tagged with unique IDs**

    API calls accept an integer request ID that is used to tag the request. This is used to match responses to requests, and can be used to free up client side resources associated with a request. The ID must be non-zero, but is not otherwise interpreted by the SDK. *Passing the same non-zero ID to all requests is OK.*

*   **Thread safety**

    The SDK is not thread safe, meaning that all API calls must be made from the same thread. Blocking IO requests between the library and the Allihoopa App will time out after 5 seconds and cause API calls to return `AHErrorCommsFailure`.

## Implementation flow

First, initialize the library by calling `AHinit` with your Allihoopa application ID and API key.

>Contact Allihoopa at<EMAIL_ADDRESS>to register your app and get your API key.

You can also provide the root directory for `file:` protocol URLs in the `AHinit` call by setting the `tmpDir` parameter. If not set, this defaults to the system temp directory.

If initialization succeeds, the Allihoopa App window appears, waiting for requests. If the initialization fails with error code `AHErrorAppNotFound`, the Allihoopa App is not installed, or the installation is somehow broken. In that case, direct the user to the `AHSDKHelpURL` url for guidance.

### Dropping

To initiate a minimal drop request, pass a JSON object like this to `AHdrop`:

```json
{
    "stems": {
        "mixStemURL": "file:///my_little_song.wav"
    },
    "presentation": {
        "title": "Singa singa song :)"
    },
    "musicalMetadata": {
        "lengthMicroseconds": 5217392
    }
}
```

If the call succeeds, it will return immediately, and the SDK will start uploading the audio and presenting a dialog for the user.

>NOTE: This is just a minimal example. Please refer to the [pre-release checklist](https://gist.github.com/ReMarkus/ec375c31277cc46cfcc026e69f67c01a) to verify that you’ve integrated our SDK correctly.

### Polling for results

To check the results of previous requests, or to free up temporary resources, call `AHpollCompletedRequests` with a callback function that will be called once for each completed request.

The callback will be called with a JSON object in the following format:

```json
{
    "requestID": 1234,
    "data": {
        ...
    }
}
```

### Queueing up requests and closing the App

Although asynchronous, the SDK will only handle one request at a time. It is OK to initiate a new request before previous requests are handled. The requests will be put in a queue and handled one at a time in order.

>The request and response queues are limited to 100 items each. If the request queue is full, the next request will block. If the reponse queue gets filled up, the oldest response is overwritten.

### More...

This is just a brief overview, see [allihoopa.h](allihoopa.h) for details.

## Allihoopa App installation

The Allihoopa App is the required for the SDK to function, however it is not included in the SDK distribution. The information at the `AHSDKHelpURL` provides information about Allihoopa and guides the end user in downloading and installing the Allihoopa App.

>It is important that the error code `AHErrorAppNotFound` is handled correctly by providing the end user with this information. Simply opening the URL in the system web browser is enough.

[Allihoopa]: https://allihoopa.com

license: MIT

repository: erkkah/Allihoopa-desktop

repo_name: erkkah/Allihoopa-desktop


text:
# MATLAB Interface *for AWS* Common Package - Release Notes

## Release 0.2.8 (3rd Mar 2022)
* Updated pom.xml latest AWS 1.12.150 BOM

## Release 0.2.7 (13th Dec 2021)

* Updated pom.xml latest AWS 1.12.128 BOM to include log4j updates
* Updated to JUNIT 4.3.2
* Updated Maven shade plug version

## Release 0.2.6 (22nd Mar 2021)
* Enabled support for multiple AWS services using a common jar

## Release 0.2.4 (5th Mar 2020)
* Updated security details
* Updated license

## Release 0.2.3 (5th Nov 2019)
* Added set and get for non proxy hosts to ClientConfiguration

## Release 0.2.2 (Internal Release)
* Improved documentation
* Made ClientConfiguration less verbose

## Release 0.2.1 (21st Jun 2019)
* Updated the security notice

## Release 0.2.0 (Jan 2019)
* Changed license
* Updated for GitHub release

## Release 0.1.0 (Sep 2018)
* Initial release as a standalone aws-common package

[//]: #  (Copyright 2019-2021 The MathWorks, Inc.)

repository: mathworks-ref-arch/matlab-aws-common

gha_language: MATLAB

gha_license_id: NOASSERTION

repo_name: mathworks-ref-arch/matlab-aws-common


text:
Add a Resources File
===

In this step, you add a resource file to the project, which contains the message strings that will be shown to end user in the UI of <Var:ProductName>.

Our verification plug-in will output error messages whenever a problem has been identified. It is, of course, not required, but recommended to enter the message strings in a resources file. Start by adding a resources file (named e.g. **Resources.resx**) to your project. The resources file should contain the following strings:

* A message stating the maximum word count (as set through the plug-in user interface) and the number of words that were actually found in the target segment.
* The name of the plug-in that has detected the problem. This is important, as a user might run several verifiers at the same time (e.g. the QA Checker, the Generic Tag Verification, and our sample WordArt checker). By including the name of the verification plug-in that generated an error, the user will know from verifier a particular message came. In the **Messages** window of <Var:ProductName> users can also sort error messages by plug-in name.

Below you see an example of a verification message as it might be thrown by our sample plug-in:

![Error_Message_Length_Worksheet_Exceeded](images/Error_Message_Length_Worksheet_Exceeded.jpg)

The resources file will look as shown below:

![WordArtVerifierResources](images/WordArtVerifierResources.jpg)

>[!NOTE]
>
> This content may be out-of-date. To check the latest information on this topic, inspect the libraries using the Visual Studio Object Browser.

repository: icmoldovan/studio-api-docs

branch_name: refs/heads/main

gha_language: JavaScript

gha_license_id: MIT

repo_name: icmoldovan/studio-api-docs


text:
# Interweave

Interweave is a robust React library that can...

* Safely render HTML without using `dangerouslySetInnerHTML`.
* Safely strip HTML tags.
* Automatic XSS and injection protection.
* Clean HTML attributes using filters.
* Interpolate components using matchers.
* Autolink URLs, IPs, emails, and hashtags.
* Render Emoji and emoticon characters.
* And much more!

## Requirements

* React 15/16+
* IE 10+

## Installation

Interweave requires React as a peer dependency.

```
npm install interweave react --save
// Or
yarn add interweave react
```

## Usage

Please refer to the [official documentation](https://github.com/milesj/interweave) for more information.

repository: humanmade/interweave

repo_name: humanmade/interweave


text:
# First Programming Exercises

 [![License](http://img.shields.io/badge/license-MIT-blue.svg)](http://en.wikipedia.org/wiki/MIT_License)

**Author:** _\<Stephanie Nguyen\>_

**Due date:** _\<February 19\>_

## Description

_\<In the first assignment, 1.3, I learned how to apply simple conversions to converting seconds to years. In the second assignment, 1.6, I learned how to convert the interest rate equation into Python language and plug in values. In the third assignment, I learned how to debug programs.\>_

## What I Learned from This

_\<I learned that these assignments take a lot of diligence and patience.\>_

## Honor Pledge

I pledge that all the work in this repository is my own with only the following exceptions:

* Content of starter files supplied by the instructor;
* Code borrowed from another source, documented with correct attribution in the code and summarized here.

Signed,

_\<Stephanie Nguyen\>_


text:
---
description: Teams may now register for places in our upcoming SR2013 competition
layout: news
title: Registration for SR2013 now open
---
Today we opened up registration for the upcoming edition of our competition, SR2013.
The rules for the game the robots will play will be announced at our kickstart event at the beginning of October.
Teams will then have just over six months to construct their robots before the competition in April 2013.

If you have a team of 16-18 year-olds that you would like to register for the competition,
 please fill out [this registration form](/schools/how_to_enter) and we will get in touch with you as soon as we can.
Thanks to our [sponsors](/about/sponsors), we can accept 36 teams for this year's competition.

repository: prophile/srweb-jekyll

gha_language: CSS

repo_name: prophile/srweb-jekyll


text:
# REPORTING TOOL

Connect our 1st and 3rd party data into one intuitive interface.

## How to Use
Run the web app through app.py. Debug mode is on currently.

# NEXT STEPS
  * Rewrite SAS workflow as OO design. Keep it modular, but stick to essentials
  * Build front-end workflow. May involve ajax.

## ISSUES
  * Fail-safe when 3rd party data is not found
  * Ajax - get list of flights associated with campaign
  * Confirm tool can parse different creative templates
  * Refactor code so as not to be a complete mess

# Objects, Methods, and Attributes
  * dfareporting_utils
    - self-contained pieces. Avoid digging into this for as long as possible

  * 3rdPartyAccount
    - login()
    - type

  * Advertiser
    - sasName
    - sasID
    - 3rdPartyID //default to None

  * Campaign
    - Flights []
    - Advertiser
    - sasID

  * Flight
    - startDate
    - endDate
    - Impression Goal
    - Impressions Served
    - Clicks
    - CTR

  * File
    - extension/filetype
    - filepath
    - parse()
    - Accumulate/reduce()
    - returnID()

  * Report
    - parameters
      * sasAdvertiser
      * startDate
      * endDate
      * Campaign   //default None
      * Flights[]  //default None

    - sasReportId
    - sasReportStatus // while loop when reportStatus != 200
    - sasReportFile

    * returnSASParameters()
    * returnDCMParameters()

  * Payload
    //Data to be sent to templates or to JS functions
    - dict

## HIGH LEVEL WORKFLOW
  * User specifies report parameters
  * Server looks up advertiser data
    - getSASID()
    - bool is 3rd Party Advertiser?
      - get3rdPartyType()
  * Construct SAS report parameters
  * createSASReport(); return jobID
  * retrieveSASReport()
  * downloadSASReport()
  * parseSASReport(); return performance, [(sasPlacementName, dcmPlacementID)]
  * construct DCM Report Parameters
  * create DCM Report
  * run DCM Report
  * find DCM report File
  * download DCM report
  * parse DCM report file; return performance
  * send results to HTML file

## Documentation

### DCM API

Edit reports by modifying (PATCHing) API objects - https://developers.google.com/doubleclick-advertisers/performance#patch

Create and update reports - https://developers.google.com/doubleclick-advertisers/guides/create_reports

Try using synchronous reports to retrieve data - https://developers.google.com/doubleclick-advertisers/guides/synchronousreports

Docs = https://developers.google.com/doubleclick-advertisers/getting_started
Authorization reference = https://developers.google.com/doubleclick-advertisers/authorizing

Dimension values (querying for specific info) - https://developers.google.com/doubleclick-advertisers/v3.0/dimensions

gha_language: HTML


text:
---
title: Closed User Groups in AEM Assets
description: Closed User Groups (CUGs) is a feature used to restrict access to content to a select group of users on a published site. This video shows how Closed User Groups can be used with Adobe Experience Manager Assets to restrict access to a specific folder of assets.
version:  6.4, 6.5, Cloud Service
topic: Administration, Security
feature: User and Groups
role: Admin
level: Intermediate
kt: 649
thumbnail: 22155.jpg
last-substantial-update: 2022-06-06
exl-id: a2bf8a82-15ee-478c-b7c3-de8a991dfeb8
---
# Closed User Groups{#using-closed-user-groups-with-aem-assets}

Closed User Groups (CUGs) is a feature used to restrict access to content to a select group of users on a published site. This video shows how Closed User Groups can be used with Adobe Experience Manager Assets to restrict access to a specific folder of assets. Support for Closed User Groups with AEM Assets was first introduced in AEM 6.4.

>[!VIDEO](https://video.tv.adobe.com/v/22155?quality=12&learn=on)

## Closed User Group (CUG) with AEM Assets

* Designed to restrict access to assets on an AEM Publish instance.
* Grants read access to a set of users/groups.
* CUG can only be configured at a folder level. CUG cannot be set on individual assets.
* CUG policies are automatically inherited by any sub-folders and applied assets.
* CUG policies can be overridden by sub-folders by setting a new CUG policy. This should be used sparingly and is not considered a best practice.

## Closed User Groups vs. Access Control Lists {#closed-user-groups-vs-access-control-lists}

Both Closed User Groups (CUG) and Access Control Lists (ACL) are used to control access to content in AEM and based on AEM Security users and groups. However the application and implementation of these features is very different. The following table summarizes the distinctions between the two features.

|                   | ACL                                                                                | CUG                                                                                |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Intended Use      | Configure and apply permissions for content on the **current** AEM instance.                                                     | Configure CUG policies for content on AEM **author** instance. Apply CUG policies for content on AEM **publish** instance(s). |
| Permission Levels | Defines granted/denied permissions for users/groups for all levels: Read, Modify, Create, Delete, Read ACL, Edit ACL, Replicate. | Grants read access to a set of users/groups. Denies read access to *all other* users/groups.                                    |
| Publication       | ACLs are *not* published with content.                                                                                | CUG policies *are* published with content.                                                                                |

## Supporting Links {#supporting-links}

* [Managing Assets and Closed User Groups](https://experienceleague.adobe.com/docs/experience-manager-65/assets/managing/manage-assets.html?lang=en#closed-user-group)
* [Creating a Closed User Group](https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/cug.html)
* [Oak Closed User Group Documentation](https://jackrabbit.apache.org/oak/docs/security/authorization/cug.html)

gha_language: SCSS


text:
# WebXR Environment Mapper

## Create a model of your playspace/home using WebXR

### [Glitch Demo](https://glitch.com/~webxr-environment-mapper)

### Usage

**Note:** This tool works best with a wireless device like the Oculus Quest using [Virtual Desktop](https://www.vrdesktop.net/) or [ALVR](https://github.com/JackD83/ALVR/) and the guardian walls disabled.

If you are using a tethered device your model will be limited to the area within the reach of your cable.

**Always exercise caution and make sure your floors are clear of any obstacles and hazards before attempting to map an environment!**

Load the page in a [WebXR compatible browser](https://caniuse.com/#feat=webxr).

Put on your device and center your playspace at a point and rotation that is easily repeatable. This will become the origin point (0,0,0) for your model.

Using the right controller with the trigger held, trace your hand along the corners and edges of any walls and surfaces you want to be visible in the model.

When the trigger is held a cube will be created at the controllers position at a rate of 4 cubes per second.

This allows you to make slow movements to get solid lines, or fast movements to cover a large area faster.

The cubes will change colors in-between each release and press of the trigger.

Once you have walked around your environment and mapped all of the points you want in your final model, you can move to the browser interface.

![Website Screenshot](Screenshot.png)

The browser interace is comprised of the following elements:

* Download Scene - Exports a GLTF model of all of the points in the current scene.
* Ouput Points - Exports the coordinates for all of the generated cubes and puts the text output in the textarea below the buttons.
* Download Points - Exports the collection of cube coordinates to a text file.
* Import Points - Copy and paste a previously exported set of points into the textarea and click this button to recreate them in the current scene. This allows you to stop and resume mapping later. Note that the playspace center should not change between exporting and importing or the alignments will be off.

Take your GLTF model into your favorite 3D modelling software and replace the cube outline with walls and furniture.

![Example Model](Example.jpg)

There is a simple WebXR ready model loader example included in `test/`, simply replace the value of `modelFile` in `test/script.js` with the path to your own model file.

### TODO

* Implement a way to reset the world orientation around a static reference point. In my current testing my model assumes the playspace is centered at a specific position and rotation (sitting at my desk facing my monitor).
* Implement a better way of mapping walls. We can assume 99% of walls are vertically leveled planes. Allow the user to mark 4 points and fill with a wall or other object type.

### Credit

This is a WebXR implementation of the technique devised by [Emanuel Tomozei](https://twitter.com/eman_insilico/status/1246428908356079616), as described in [this article](https://emanueltomozei.wordpress.com/2020/04/14/tutorial-how-to-map-a-vr-environment-to-your-home/).

repository: mrhegemon/webxr-environment-mapper

repo_name: mrhegemon/webxr-environment-mapper


text:
# MixedRealitySpatialAwarenessProfileInspector Class

| Toolkit Layer | Namespace |
| --- | --- |
| Core | Microsoft.MixedReality.Toolkit.Inspectors.Profiles |

The MixedRealitySpatialAwarenessProfileInspector derives from MixedRealityBaseConfigurationProfileInspector to provide a visual means of modifying the spatial awareness profile using the Unity Inspector.

Each of the properties defined under [MixedRealitySpatialAwarenessProfile](./MixedRealitySpatialAwarenessProfile.md) are represented as elements in the user interface and are persisted when the user saves.

## See Also

- [Mixed Reality Spatial Awareness System Architecture](./SpatialAwarenessSystemArchitecture.md)
- [MixedRealitySpatialAwarenessProfile](./MixedRealitySpatialAwarenessProfile.md)

branch_name: refs/heads/vNEXT-BleedingEdge

gha_language: C#


text:
Changes
=======
v5.1.0
------
- Improved [#30](https://github.com/maxtoroq/DbExtensions/issues/30): Make SqlBuilder.cs a standalone file
- Fixed [#31](https://github.com/maxtoroq/DbExtensions/issues/31): SqlTable not handling array members properly
- Added [#33](https://github.com/maxtoroq/DbExtensions/issues/33): SqlServer 2008 support in SqlSet
- Fixed [#35](https://github.com/maxtoroq/DbExtensions/issues/35): SqlSet pagination fails against Oracle
- Moved documentation to source repository
- Moved samples databases to source repository

v5.0.0
------
- Added [#23](https://github.com/maxtoroq/DbExtensions/issues/23): Support Select in SqlSet without specifying a result type
- Added [#17](https://github.com/maxtoroq/DbExtensions/issues/17): Support for Enum properties that map to text columns
- Added [#15](https://github.com/maxtoroq/DbExtensions/issues/15): SqlSet.Include function for query expansion (eager loading)
- Added SqlSet.Find extension method
- Fixed [#18](https://github.com/maxtoroq/DbExtensions/issues/18): Insert one-to-one associations (SqlTable.Add)
- Improved [#6](https://github.com/maxtoroq/DbExtensions/issues/6): SqlBuilder.Append(SqlBuilder) and SqlBuilder.JoinSql generate unnecessary extra whitespace

BREAKING CHANGES:
- Removed .NET 3.5 support
- Removed members deprecated in v4.x
- Removed DbConnection extension methods (use Database instead)
- Removed XML mapping
- Removed SqlSet constructors that take TextWriter (if you need profiling use Database)
- Removed SqlSet.Union
- Made all SqlSet's protected members internal
- Renamed SqlTable's Delete, DeleteKey and DeleteRange to Remove, RemoveKey and RemoveRange
- Removed Insert and InsertRange overloads with *deep* parameter, added DatabaseConfiguration.EnableInsertRecursion property to control recursion
- Renamed SqlTable's Insert and InsertRange to Add and AddRange

v4.4.0
------
- Improved SqlTable, using subqueries only when necessary
- Added SQL.Param to workaround [#10](https://github.com/maxtoroq/DbExtensions/issues/10)
- Deprecated SQL.ctor

v4.3.0
------
- Implemented IDisposable on Database
- Convention-based DbConnection.GetProviderFactory fallback
- Removed AS keyword in FROM clause (to support Oracle)
- Deprecated SqlTable.Initialize
- SqlSet improvements:
  * Oracle support
  * Using subqueries only when necessary
  * Fixed [#13](https://github.com/maxtoroq/DbExtensions/issues/13): Skip().OrderBy() are applied in the same query instead of applying Skip() first
  * Deprecated DbConnection.Set and Database.Set, replaced by From
  * Can create set using table name only, e.g. From("Products")

v4.2.0
------
- Mapping to dynamic objects, Map methods which do not need a Type argument, also supported by SqlSet. This feature requires .NET 4+
- New methods: SqlTable.ContainsKey, SqlCommandBuilder.UPDATE, SqlTable.DeleteRange, SqlTable.UpdateRange
- Deprecated SqlTable.InsertDeep, replaced by Insert(object, bool)
- Added SqlTable.InsertRange overloads with bool parameter
- Deprecated Database.InsertRange
- Deprecated SqlTable.DeleteById, replaced by DeleteKey

v4.1.1
------
- Fixed [#4](https://github.com/maxtoroq/DbExtensions/issues/4): SqlSet<T>.AsEnumerable() fails if T is a value type
- Fixed [#2](https://github.com/maxtoroq/DbExtensions/issues/2): Use parameter on SqlBuilder OFFSET(int) and LIMIT(int)
- Fixed [#3](https://github.com/maxtoroq/DbExtensions/issues/3): OleDbConnection and OdbcConnection do not override DbProviderFactory

v4.1.0
------
- Mapping to constructor arguments
- Copied DbFactory methods to Database, marked DbFactory as obsolete
- Fixed [#1](https://github.com/maxtoroq/DbExtensions/issues/1): Skip Refresh after Insert on non-entity types

v4.0.0
------
- New SqlSet API for making queries
- DataAccessObject split into Database, DatabaseConfiguration and SqlTable
- IDataRecord.Get{TypeName}(string) extension methods
- MapXml methods now return XmlReader, and take XmlMappingSettings parameter
- Unified extension methods class

repository: dplaskon/DbExtensions

repo_name: dplaskon/DbExtensions


text:
# Mecanum Bot Code
This is a backup of the code for the Wiimote-controlled mecanum robot. Currently it uses a Pi Zero W and Attiny85 as the main controllers, and has basic features (motion with strafing, battery indication, nunchuk calibration, slow/fast modes, safe shutdown indication, etc.)

**See photos [here](https://photos.app.goo.gl/PudXENaW6ujRSE3S7)**

To use, make sure `mywminput`, `pi-main.py`, `pyzypwm.py` and `connectwiimote.sh` are all in the main (~/) directory. Some elements of the tutorials listed below will be needed to set it up. This README is for re-building the SD card later on as I had to overwrite the current one for a different project.

-https://pimylifeup.com/raspberry-pi-wiimote-controllers/
-https://retropie.org.uk/docs/Wiimote-Controller/
-https://www.programcreek.com/python/example/93202/evdev.categorize
-http://himeshp.blogspot.com/2018/08/fast-boot-with-raspberry-pi.html#:~:text=The%20Hardware%20and%20bootloader%20take,processor%20was%20around%201.5%20seconds.
-https://github.com/abstrakraft/cwiid/blob/master/doc/wminput.list
-https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h
-https://www.raspberrypi.org/forums/viewtopic.php?t=63784&p=482624

Later on, this project should be adapted to use a sole ESP32. This will simplify electronics, greatly reduce setup time (turning on the robot takes ~30sec with the Pi Zero W), and make it easier to develop. It also has hardware PWM and proper timing, both things that the Pi Zero W lack.

repository: aaronbeckman/mecanum-bot-transmitter

repo_name: aaronbeckman/mecanum-bot-transmitter


text:
---
layout: page-with-toc
title: Sponsoring
titlecontent: "Interested in sponsoring? Contact us at sponsor-sotm@openstreetmap.org"
headings: "packages,booths,osmf,interested"
---

Sponsoring during the State of the Map 2021

The annual global conference of the [OpenStreetMap community](https://www.openstreetmap.org/about), the State of the Map (SotM) brings together the brightest and most active members of the OpenStreetMap (OSM) surveying and development community from around the world for an intense exchange of results and ideas that strengthens the project and ensures its continued success.

SotM 2021 will be an online conference happening on July 9 to 11, 2021.

Contact us via email at [sponsor-sotm<EMAIL_ADDRESS>for further information!

Sponsorship packages

|                             | Gold     | Silver   | Bronze  |
|---------------------------- | -------  | -------- | ------- |
|                             | EUR 2000 | EUR 1000 | EUR 500 |
| Virtual Sponsor Booth | yes | yes | - |
| Special appreciation during opening session | yes | - | - |
| 2021.stateofthemap.org website | logo | logo | logo |
| Conference tickets | 4 | 2 | 1 |

Don't see the right package? Please <a<EMAIL_ADDRESS>us know how you would like to support us. We will be happy to work with you to craft a custom sponsorship opportunity according to your wishes.

Virtual Sponsor Booths

The conference will use the platform [venueless](https://venueless.org/en/) for intraction between attendees, speakers and sponsors. For the _gold_ and _silver_ sponsorship packages we offer the possibility to set up a virtual sponsor booth so that conference participants to get directly in touch with you via a prominently advertised permanent dedicated chat room.

OSM Foundation Corporate Members

We are delighted to offer our [OSM Foundation corporate members](https://wiki.osmfoundation.org/wiki/Corporate_Members) a discount on State of the Map sponsorships. The discount will be 25% on all SOTM sponsorship packages up to the same level as your OSMF corporate membership. Your largest eligible discount also applies to higher packages.

Interested in sponsoring?

Contact us via email us at <a href="mailto:sponsor-sotm<EMAIL_ADDRESS>for more information.


text:
# Advent of Code 2019: Day 15
Bart Massey

Nice little Dijkstra search problem. Interesting that once
the robot finds the generator it can just start searching
again from there.

Added some tracing macros to `libaoc`, which was fun.

Part 2 is quite slow. I guess the obvious plan is to not
keep moving the robot back to the origin, and instead try to
move it directly to the nearest open location. I could even
do some fancy TSP-style motion planning. Nah. I'm sleepy.

---

Solution to
[this problem](https://adventofcode.com/2019/day/15).

Save your problem input to `input.txt` and run with

    cargo run --release 1 <input.txt
    cargo run --release 2 <input.txt

You can use `--features=tracing` to get a trace of
the robot's operation.

---

This program is licensed under the "MIT License".
Please see the file LICENSE in this distribution
for license terms.


text:
# Change Log

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](http://keepachangelog.com/)
and this project adheres to [Semantic Versioning](http://semver.org/).

<!--
   PRs should document their user-visible changes (if any) in the
   Unreleased section, uncommenting the header as necessary.
-->

## Unreleased

## [0.6.0] - 2017-09-01

* Fixed removing event handlers when setting them to `undefined`.
* Allow the text "{{}}" to appear in templates.
* Optimized clearing of Parts.
* Added `unsafeHTML()` directive to bind values as HTML source.
* Optimizations, simplification and bug fixes of Array handling code.
* Update to extension API: added partCallback parameter to `render()`.
* Added the `directive()` decorator function to create directives. Functions values are no longer treated as directive by default, simplifying declarative event handlers.

repository: mikegeyser/getting-started-with-polymer

repo_name: mikegeyser/getting-started-with-polymer


text:
---
title: "FHIR概览"
meta_title: ""
description: "this is meta description"
date: 2012-6-10T20:08:12Z
image: "/images/image-placeholder.png"
categories: ["工作"]
author: "haisheng"
tags: ["医疗信息标准", "信息交换","FHIR"]
draft: false
---

自去年Grahame Grieve引出v3 has failed的讨论之后，RFH的出现似乎给HL7带来了一些生机。从RFH到FHIR 自是经过一番努力。越来越多的人对此表示出极大的兴趣，菜鸟我也不例外。故拟在后面的一些篇章中对目前所有的一些的资料进行一些简单的介绍和试译。 来到Grahame Grieve自己维护的博客主站（链接）上，在右侧links处即可看到一些相关信息，点击Fast Health Interoperability Resources即可进入，本文中将尝试对此主页上的内容做简要介绍。
20120814更新
Warning: FHIR is a draft specification that is still undergoing development prior to balloting as a full HL7 standard
作者2次强调了这一点  FHIR仍然处于开发之中 并不是一个完整的HL7的投票版标准
首先是一些外链。
Infrastructure基本架构
简介Introduction
资源格式Resource Format
数据类型Data Types
编码与术语Codes & Terminologies
扩展性Extensibility
资源规范Profiling Resources
Exchange交换

    实现Implementation
    组合Aggregations
    RESTREST (HTTP)
    消息Messaging
    文档Documents
    一致性声明Conformance Statement
    hData整合hData Integration
    Administrative Resources管理性资源
        人Person
        动物Animal
        组织Organization
        代理Agent
        病患Patient
        诊所Clinics
        入院Admissions
        预约Appointments
        感兴趣InterestOfCare
        转诊Transfers
        Clinical Components临床组件/医学组件
            生命体征等Vitals etc
            实验室报告Lab Report
            评估水平Assessment Scale
            影像Imaging
            警告Alert
            手术/操作Procedure
            会诊Consultation
            问题Problem
            饮食Diet
            植入物Implant
        Medications药物
            处方Prescription
            声明Statement
            分发Dispense
            用药Administration
            过敏Immunization

Welcome to FHIR欢迎来到FHIR/faiə/

Fast Healthcare Interoperability Resources 定义了一个医疗卫生资源的集合。这些资源所表达的是一个个模块化的医学概念，在医疗保健及相关流程中通过交换实现快速高效地解决问题。这些资源涵盖了医疗卫生的基本元素-病人、入院、诊断报告、药物和问题列表以及其中的一些参与者，同时也支持更加丰富和复杂的临床模型。资源的简单的直接的定义是基于充分的需求收集、正规分析以及与其他标准的交叉对应而来。

Useful Links有用的链接

    FHIR规范The FHIR specification
    chm格式的规范The specification as a Windows Help File (.chm)
    单个html格式的规范The specification in a single book
    zip格式的完整规范A Zip of the whole specification for offline use
    FHIR的schemaFHIR Schemas
    参考实现Reference Implementations
    FHIR的维基FHIR wiki - home for FHIR development team
    Version 0.02, Last Version, May 28, 2012. (Diff with current)
    Version 0.01, First Archived Version (During Vancouver WGM), May 14, 2012. (Diff with current)
    公开的测试服务器Publicly Available Test ServersFHIR License
    FHIR属于HL7所有，维护也归HL7。
    你可以重新发布FHIR
    你可以构建衍生规范或者是产品以及服务的实现
    你不能因你的规范中使用了FHIR的内容从而声称HL7或其中任一成员认可你的衍生规范
    任意HL7或者此规范的参与人员对你对FHIR的使用不负任何责任
    注意：为什么不使用开源的标准许可证？我们想使用 Creative Commons或者 a license listed here其中之一，但都不是用最朴实的英语来描述的。尽管专利是个问题，我们仍渴望能够满足开源项目的这些需求these requirements from the Open Source Initiative。

    然而我们解决了长期许可证的问题，我们应用如下许可证，它是根据OMG的改编而成：

    Subject to all of the terms and conditions below, HL7 hereby grants you a fully-paid up, non-exclusive, nontransferable, perpetual, worldwide license (without the right to sublicense), to use this specification to create and distribute software and special purpose specifications that are based upon this specification, and to use, copy, and distribute this specification as provided under the United States Copyright Act; provided that:
        both the copyright notice identified above and this permission notice appear on any copies of this specification;
        the use of the specifications is for informational purposes and will not be resold or transferred for commercial purposes;
        no modifications are made to this specification.

    This limited permission automatically terminates without notice if you breach any of these terms or conditions.
    GENERAL USE RESTRICTIONS

    Any unauthorized use of this specification may violate copyright laws, trademark laws, and communications regulations and statutes. This document contains information which is protected by copyright. All Rights Reserved. No part of this work covered by copyright herein may be reproduced or used in any form or by any means--graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems--without permission of the copyright owner.
    DISCLAIMER OF WARRANTY

    WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS.  IN NO EVENT SHALL HL7 BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

    The entire risk as to the quality and performance of software developed using this specification is borne by you. This disclaimer of warranty constitutes an essential part of the license granted to you to use this specification.
    CONFORMANCEHL7 is and shall at all times be the sole entity that may authorize developers, suppliers and sellers of computer software or specifications to use certification marks, trademarks or other special designations to indicate compliance with with FHIR. Software developed under the terms of this license may claim compliance or conformance with FHIR if and only if the software compliance is of a nature fully matching the applicable conformance points as stated in the FHIR specification. Software developed only partially matching the applicable compliance points may claim only that the software was based on FHIR, but may not claim compliance or conformance with this specification. In the event that testing suites or processes are implemented or approved by HL7, Inc., software developed using this specification may claim compliance or conformance with the FHIR specification only if the software satisfactorily completes the testing suites.
    FHIR的存档版本Archived Versions of FHIR
    这里的存档只保存了重要的历史版本，也只有单个html的格式，仅用在html diff工具中。
        Version 0.04, 投票前的最终版 / Connectathon stable source (compare with this to see what has changed during the freeze). (Diff with current)
        Version 0.03, June 6, 2012. (Diff with current)
        Version 0.02, Last Version, May 28, 2012. (Diff with current)
        Version 0.01, First Archived Version (During Vancouver WGM), May 14, 2012. (Diff with current)


text:
---
layout: post
title: "Kata21: Simple Lists"
date: 2013-12-09 19:13:03 -0600
comments: true
categories:
---

Perhaps there’s more to the humble list of values than you might
think. Let’s experiment with some basic list processing.

<!-- more -->

Lists are one of the first data structures we learn as
programmers. But familiarity doesn’t mean that we can’t learn a little
from them.

For this kata we’re going to code up three implementations of a list
that has the following basic interface:

* The list consists of nodes. Each node has a string value, along with
  whatever housekeeping the list itself needs.
* New nodes are added to the end of the list.
* You can ask the list if it contains a given string. If it does, it
  returns the node containing that string.
* You can delete a node from the list.
* You can ask the list to return an array of all its values.

Here’s a basic set of unit tests to illustrate the behavior.

``` ruby
list = List.new
assert_nil(list.find("fred"))
list.add("fred")
assert_equal("fred", list.find("fred").value())
assert_nil(list.find("wilma"))
list.add("wilma")
assert_equal("fred",  list.find("fred").value())
assert_equal("wilma", list.find("wilma").value())
assert_equal(["fred", "wilma"], list.values())

list = List.new
list.add("fred")
list.add("wilma")
list.add("betty")
list.add("barney")
assert_equal(["fred", "wilma", "betty", "barney"], list.values())
list.delete(list.find("wilma"))
assert_equal(["fred", "betty", "barney"], list.values())
list.delete(list.find("barney"))
assert_equal(["fred", "betty"], list.values())
list.delete(list.find("fred"))
assert_equal(["betty"], list.values())
list.delete(list.find("betty"))
assert_equal([], list.values())
```

For the kata, where the idea is to practice, let’s write three
implementations of the list:

* A singly linked list (each node has a reference to the next node).
* A doubly linked list (each node has a reference to both the next and
  previous nodes).
* Some other implementation of your choosing, except that it should
  use no references (pointers) to collect nodes together in the list.

Obviously, we won’t be using predefined library classes as our list
implementations…

# Objectives

There’s nothing magical or surprising in list implementations, but
there are a fair number of boundary conditions. For example, when
deleting from the singly-linked list, did you have to deal with the
case of deleting the first element in the list specially?

For this kata, concentrate on ways of removing as many of these
boundary conditions as possible. Then ask yourself: Is the resulting
code, which will contain fewer special cases, easier to read and
maintain? How easy was it to eliminate these special cases? Were there
trade-offs, where removing a special case in one area complicated the
code in another. Is there a sweet-spot when it comes to simplifying
code?

repository: pabranch/codekata

extension: markdown

repo_name: pabranch/codekata


text:
Feel free to contribute, make pull requests, open issues, etc.

Please be respectful of peoples wishes.

# Erupe
This project is in its infancy and has no reliable active developer, no documentation, and no support.

This project has been solely developed in my spare time for the educational experience of making a server emulator, which I haven't done before. Expectations regarding functionally and code quality should be set accordingly.

[See original README here](./docs/ErupeServer.README.md)

## General
**WARNING:** All current features can be assumed to be very limited or buggy.

Currently allows a JP MHF client (with GameGuard removed) to:
- Login and register an account (registration is automatic if account doesn't exist).
- Create a character.
- Get ingame to the main city.
- See other players walk around.
- Do quests:
    - Only quests shipped with the game are on the counter.
    - **Requires binary quest files not in the repository.**
- Use (local) chat.
- Partial guild support.

## Useful Resources
- [Erupe Server](https://github.com/ricochhet/Erupe)
- [Progression files](https://archive.org/details/mhfz_progression)

## Server Setup Guide
The erupe server is still heavily in development and you should expect numerous bugs, crashes, and other unintended behavior during use.

Really take a moment to figure out *why* you want to do this setup, and if you're capable enough *to* do it. This guide tries to make everything as simple as possible, but will still require a fairly good understanding of how computers operate.

This server is *experimental*, many bugs, crashes, and other unintended behavior ***WILL*** occur. This is not suited for gameplay, you can *play* the game, but keep in mind the above. This is primarily for development and research purposes.

The Server is written in Go, so it basically should support any Operating system that can run golang and golang-migrate as well as postgres for the database-server. Here are a few Guides to help get you started on some different Operating Systems. If you feel like we miss an important OS feel free to add a Guide via Pull Request.

- [Guide to Install Server Side on Windows (10)](./docs/Windows-Server-Install.md)
- [Guide to Install Server Side on Ubuntu](./docs/Ubuntu-Server-Install.md)
- [Guide to Install Server Side on Arch Linux](./docs/Arch-Server-Install.md)

## Client Setup Guide

The Monster Hunter Frontier Client heavily relies on Internet Explorer to work properly. So getting it to run on Linux might not be possible at all. If you have some idea how to maybe get it working on Linux as well please get in touch. For now the Client only works on Windows. Here is the Guide on how to set it up:

- [Guide to install the MHF Client on Windows (10)](./docs/Windows-Client-Install.md)

## Troubleshooting

There are some common problems which can occur while trying to setup either the Server Side or the Client Side of this. If you run into a problem please refer to the [Troubleshooting-Section](./docs/Troubleshooting.md) of the documentation. It lists some common solutions. If you have a fix that is not listed there yet, please feel free to send a pull request.
s
## Credits
- [Erupe Contributors](https://github.com/ErupeServer/Erupe)
- [theBusBoy](https://github.com/theBusBoy)

repository: satoupan/Erupe

repo_name: satoupan/Erupe


text:
---
title: Telerik.Web.UI.RadMultiSelect
page_title: Telerik.Web.UI.RadMultiSelect
description: Telerik.Web.UI.RadMultiSelect
---

# Telerik.Web.UI.RadMultiSelect

## Inheritance Hierarchy

* System.Object
* System.Web.UI.Control
* System.Web.UI.WebControls.WebControl
* System.Web.UI.WebControls.BaseDataBoundControl
* System.Web.UI.WebControls.DataBoundControl
* Telerik.Web.UI.RadDataBoundControl : IControl, IControlResolver, IFeatureGroup, IPostBackDataHandler, IScriptControl, ISkinnableControl
* Telerik.Web.UI.RadMultiSelect : INamingContainer

## Properties

###  Animation `Boolean`

Configures the opening and closing animations of the suggestion popup. Setting the animation option to false will disable the opening and closing animations. As a result the suggestion popup will open and close instantly. is not a valid configuration.

###  AnimationSettings `Boolean`

Configures the opening and closing animations of the suggestion popup. Setting the animation option to false will disable the opening and closing animations. As a result the suggestion popup will open and close instantly. is not a valid configuration.

###  AutoBind `Boolean`

Controls whether to bind the widget to the data source on initialization

###  AutoClose `Boolean`

Controls whether to close the widget suggestion list on item selection.

###  AutoPostBack `Boolean`

Gets or sets a value indicating whether a postback to the server automatically
            occurs when the user changes the RadComboBox selection.

#### Remarks
Set this property to true if the server needs to capture the selection
                as soon as it is made. For example, other controls on the Web page can be
                automatically filled depending on the user's selection from a list control.This property can be used to allow automatic population of other controls on
                the Web page based on a user's selection from a list.The value of this property is stored in view state.
                    The server-side event that is fired is
                    SelectedIndexChanged.

###  AutoWidth `Boolean`

If set to true, the widget automatically adjusts the width of the popup element and does not wrap up the item label.

###  CascadeFrom `String`

Use it to set the Id of the parent MultiSelect widget.Help topic showing how cascading functionality works

###  CascadeFromField `String`

Defines the field to be used to filter the data source. If not defined the parent's dataValueField option will be used.Help topic showing how cascading functionality works

###  CascadeFromParentField `String`

Defines the parent field to be used to retain value from. This value will be used further to filter the dataSource. If not defined the value from the parent's dataValueField will be used.

###  CausesValidation `Boolean`

Gets or sets a value indicating whether validation is performed when an item within
            the control is selected.

#### Remarks
By default, page validation is performed when an item is selected. Page
                validation determines whether the input controls associated with a validation
                control on the page all pass the validation rules specified by the validation
                control. You can specify or determine whether validation is performed on both the
                client and the server when an item is clicked by using the CausesValidation
                property. To prevent validation from being performed, set the
                CausesValidation property to false.

###  ClearButton `Boolean`

Unless this options is set to false, a button will appear when hovering the widget. Clicking that button will reset the widget's value and will trigger the change event.

###  ClientDataSourceID `String`

Gets or sets ID of ClientDataSource control that is used for client side binding

###  ClientEvents `MultiSelectClientEvents`

Defines the client events handlers.

###  ClientIDMode `ClientIDMode`

This property is overridden in order to support controls which implement INamingContainer.
            The default value is changed to "AutoID".

###  CssClassFormatString `String`

The CssClass property will now be used instead of the former Skin
            and will be modified in AddAttributesToRender()

###  DataKeyNames `String[]`

Gets or sets an array of data-field names that will be used to populate the MultiSelect's DataItem property which is used to populated the control's template. The field declared in the Columns are added by default.

#### Remarks
Note: The dataItem's properties declared in the template should be with lower case.

###  DataTextField `String`

The field of the data item that provides the text content of the list items. The widget will filter the data source based on this field.

###  DataValueField `String`

The field of the data item that provides the value of the widget.

###  Delay `Double`

Specifies the delay in milliseconds after which the MultiSelect will start filtering dataSource.

###  DropDownHeight `Unit`

The height of the suggestion popup in pixels. The default value is 200 pixels.

###  Enable `Boolean`

If set to false the widget will be disabled and will not allow user input. The widget is enabled by default and allows user input.

###  EnableAjaxSkinRendering `String`

Gets or sets the value, indicating whether to render the skin CSS files during Ajax requests

#### Remarks
If EnableAjaxSkinRendering is set to false you will have to register the needed control base CSS file by hand when adding/showing the control with Ajax.

###  EnableEmbeddedBaseStylesheet `Boolean`

Gets or sets the value, indicating whether to render the link to the embedded base stylesheet of the control or not.

#### Remarks
If EnableEmbeddedBaseStylesheet is set to false you will have to register the needed control base CSS file by hand.

###  EnableEmbeddedScripts `Boolean`

Gets or sets the value, indicating whether to render script references to the embedded scripts or not.

#### Remarks
If EnableEmbeddedScripts is set to false you will have to register the needed Scripts files by hand.

###  EnableEmbeddedSkins `String`

Gets or sets the value, indicating whether to render links to the embedded skins or not.

#### Remarks
If EnableEmbeddedSkins is set to false you will have to register the needed CSS files by hand.

###  EnableRippleEffect `Boolean`

Returns true if ripple effect should be added

###  EnforceMinLength `Boolean`

If set to true the widget will not show all items when the text of the search input cleared. By default the widget shows all items when the text of the search input is cleared. Works in conjunction with minLength.

###  Filter `RadMultiSelectFilter`

The filtering method used to determine the suggestions for the current value. Filtration is turned of by default, and can be performed over string values only (either the widget's data has to be an array of strings, or over the field, configured in the dataTextField option). The supported filter values are startswith, endswith and contains.

###  FixedGroupTemplate `String`

The template used to render the fixed header group. By default the widget displays only the value of the current group.

###  FooterTemplate `String`

The template used to render the footer template. The footer template receives the widget itself as a part of the data argument. Use the widget fields directly in the template.

###  GroupTemplate `String`

The template used to render the groups. By default the widget displays only the value of the group.

###  HeaderTemplate `String`

Specifies a static HTML content, which will be rendered as a header of the popup element.

###  HighlightFirst `Boolean`

If set to true the first suggestion will be automatically highlighted.

###  IgnoreCase `Boolean`

If set to false case-sensitive search will be performed to find suggestions. The widget performs case-insensitive searching by default.

###  IsSkinSet `String`

For internal use.

###  ItemTemplate `String`

The template used to render the items in the popup list.

###  MaxSelectedItems `Double`

Defines the limit of the selected items. If set to null widget will not limit number of the selected items.

###  MessagesSettings `Messages`

The text messages displayed in the widget. Use this option to customize or localize the messages.

###  MinLength `Double`

The minimum number of characters the user must type before a search is performed. Set to a higher value if the search could match a lot of items. A zero value means that a request will be made as soon as the user focuses the widget.

###  NoDataTemplate `String`

The template used to render the "no data" template, which will be displayed if no results are found or the underlying data source is empty. The noData template receives the widget itself as a part of the data argument. The template will be evaluated on every widget data bound.

###  ODataDataSourceID `String`

Gets or sets the ODataDataSource used for data binding.

###  Placeholder `String`

The hint displayed by the widget when it is empty. Not set by default.

###  PopupSettings `Popup`

The options that will be used for the popup initialization. For more details about the available options refer to Popup documentation.

###  PostBackUrl `String`

Gets or sets the URL of the page to post to from the current page when a tab
                from the tabstrip is clicked.

###  RegisterWithScriptManager `Boolean`

Gets or sets the value, indicating whether to register with the ScriptManager control on the page.

#### Remarks
If RegisterWithScriptManager is set to false the control can be rendered on the page using Web Services or normal callback requests/page methods.

###  RenderMode `RenderMode`

Specifies the rendering mode of the control. Setting the mode to Lightweight will yield
            HTML 5/CSS 3 html and css. If the set value is Auto use ResolvedRenderMode to receive the actual RenderMode
            with respect to the user angent of the current request.

#### Remarks
Lightweight rendering mode might change the outlook of the component in some older browsers
            that don't support CSS3/HTML5.

###  ResolvedRenderMode `RenderMode`

Returns resolved RenderMode should the original value was Auto

###  RuntimeSkin `String`

Gets the real skin name for the control user interface. If Skin is not set, returns
            "Default", otherwise returns Skin.

###  Skin `String`

Gets or sets the skin name for the control user interface.

#### Remarks
If this property is not set, the control will render using the skin named "Default".
            If EnableEmbeddedSkins is set to false, the control will not render skin.

###  TagMode `RadMultiSelectTagMode`

The mode used to render the selected tags. The available modes are: - multiple - renders a tag for every selected value - single - renders only one tag that shows the number of the selected values

###  TagTemplate `String`

The template used to render the tags.

###  UniqueID `String`

Gets the unique, hierarchically qualified identifier for the server
            control.

###  ValidationGroup `String`

Gets or sets the name of the validation group to which this validation
                control belongs.

#### Remarks
This property works only when CausesValidation
                is set to true.

###  Value `IEnumerable`1`

The value of the widget.

###  ValuePrimitive `Boolean`

Specifies the value binding behavior for the widget. If set to true, the View-Model field will be updated with the selected item value field. If set to false, the View-Model field will be updated with the selected item.

###  Virtual `Boolean`

Enables the virtualization feature of the widget. The configuration can be set on an object, which contains two properties - itemHeight and valueMapper.For detailed information, refer to the article on virtualization.

###  VirtualSettings `Boolean`

Enables the virtualization feature of the widget. The configuration can be set on an object, which contains two properties - itemHeight and valueMapper.For detailed information, refer to the article on virtualization.

###  WebServiceClientDataSource `WebServiceClientDataSource`

Gets the RadClientDataSource instance of the MultiSelect control.

## Methods

###  ApplyConditionalRendering

Use this from RenderContents of the inheritor

#### Returns

`System.Void`

###  ControlPreRender

Code moved into this method from OnPreRender to make sure it executed when the framework skips OnPreRender() for some reason

#### Returns

`System.Void`

###  DescribeRenderingMode

Should be  used by inheritors

#### Returns

`System.Void`

###  GetEmbeddedSkinNames

Returns the names of all embedded skins. Used by Telerik.Web.Examples.

#### Returns

`System.Collections.Generic.List`1`

###  LoadClientState

Loads the client state data

#### Parameters

#### clientState `System.Collections.Generic.Dictionary{System.String,System.Object}`

#### Returns

`System.Void`

###  LoadPostData

Loads the posted content of the list control, if it is different from the last posting.

#### Parameters

#### postDataKey `System.String`

The key identifier for the control, used to index the postCollection.

#### postCollection `System.Collections.Specialized.NameValueCollection`

A  that contains value information indexed by control identifiers.

#### Returns

`System.Boolean` true if the posted content is different from the last posting; otherwise, false.

###  LoadPostData

Executed when post data is loaded from the request

#### Parameters

#### postDataKey `System.String`

#### postCollection `System.Collections.Specialized.NameValueCollection`

#### Returns

`System.Boolean`

###  OnItemDeselected

Raises the OnItemDeselected event. This allows you to handle the event directly.

#### Returns

`System.Void`

###  OnItemSelected

Raises the OnItemSelected event. This allows you to handle the event directly.

#### Returns

`System.Void`

###  OnSelectionChanged

Raises the OnItemSelected event. This allows you to handle the event directly.

#### Returns

`System.Void`

###  RaisePostDataChangedEvent

Signals the RadMultiSelect control to notify the ASP.NET application that the state of the control has changed.

#### Returns

`System.Void`

###  RaisePostDataChangedEvent

Executed when post data changes should invoke a changed event

#### Returns

`System.Void`

###  RegisterCssReferences

Registers the CSS references

#### Returns

`System.Void`

###  RegisterScriptControl

Registers the control with the ScriptManager

#### Returns

`System.Void`

###  SaveClientState

Saves the client state data

#### Returns

`System.String`

repository: telerik/ajax-docs

repo_name: telerik/ajax-docs


text:
## Login

        POST /auth/login

Use this endpoint to log in a user.

> ### CURL Request

```bash
# This is the call to authenticate a user
curl "<-- endpoint here -->/auth/local"
        -H "Accept: application/json"
        -H "Content-Type: application/json"
        -d "email: <-- user's email address -->"
        -d "password: <-- user's password -->"
```

Request

You must pass in the request body **`email`** and **`password`**.

### Payload Options

  | Required | Description
- | -------- | -----------
`email` |  | Registered user's email address
`password` |  | Registered user's password

> ### 201 Response

```json

{
        "token": "<-- jwt hashed token -->",
        "data": {
                "_id": "<-- user id -->",
                "username": "<-- user email address -->",
                "email": "<-- user email address -->",
                "updatedAt": "2016-08-05T08:18:51.612Z",
                "createdAt": "2016-08-05T08:18:51.612Z",
                "belongsTo": [... <-- array of organisation domains that user is associated to -->],
                "integrations": [... <-- array of services that user has enabled -->]
                ...
        }
}
```

> Above is the typical response you will get after a successful user authentication. Please note that the response may contain more data properties than what is shown and the user must have activated their account first

> ### 401 Response

```json
{
        "name": "NotAuthenticated",
        "message": "Not Activated",
        "code": 401,
        "className": "not-authenticated",
        "errors": {}
}
```

Response

 | Type | Description
-------- | ---- | -----------
`token` | **String** | The authenticated login token returned that can be used for all subsequent calls
`data._id` | **String** | The ID of the newly registered user
`data.username` | **String** | The username of the user. **This is currently automatically assigned the email address**
`data.email` | **String** | The email address registered
`data.belongsTo` | **[Object]** | An array of organisations that the user belongs to containing a `domain` and `domainId` key
`data.integrations` | **[Object]** | An array of services/integrations that the user is able to access or has enabled. This lists out the ....

The above properties are just some of the properties that may be returned. Call the API endpoint to find and investigate the remaning properties that get returned

## Token

        POST /auth/token

Edumaps API allows for token based access in order for users to allow third-party apps to log in and access the user data. This is not to be confused with oAuth permissions. It is also a means to re-authenticating and retriving the current user data of the user if this has been mutated in anyway since their last login. This endpoint can be used as a means to bypass requring the user to enter their credentials everytime.

> ### CURL Request

```bash
        # This is the call to re-authenticate a user using a previous authenticated token

        curl "<-- endpoint here -->/auth/local"
                -H "Accept: application/json"
                -H "Content-Type: application/json"
                -H "Authorisation: <-- jwt token -->"
```

Request

### Header Options

  | Required | Expected Value | Description
- | -------- | -------------- | -----------
`Authorisation` | | a jwt token | a valid jwt token must be passed and this can be obtained from the fist time user login - see [login](#login) for details

> ### 201 Response

```json

{
        "token": "<-- jwt hashed token -->",
        "data": {
                "_id": "<-- user id -->",
                "username": "<-- user email address -->",
                "email": "<-- user email address -->",
                "updatedAt": "2016-08-05T08:18:51.612Z",
                "createdAt": "2016-08-05T08:18:51.612Z",
                "belongsTo": [... <-- array of organisation domains that user is associated to -->],
                "integrations": [... <-- array of services that user has enabled -->]
                ...
        }
}
```

> Above is the typical response you will get after a successful user authentication. Please note that the response may contain more data properties than what is shown and the user must have activated their account first

> ### 401 Response

```json
{
        "name": "NotAuthenticated",
        "message": "Not Activated",
        "code": 401,
        "className": "not-authenticated",
        "errors": {}
}
```

Response

 | Type | Description
-------- | ---- | -----------
`token` | **String** | The authenticated login token returned that can be used for all subsequent calls
`data._id` | **String** | The ID of the newly registered user
`data.username` | **String** | The username of the user. **This is currently automatically assigned the email address**
`data.email` | **String** | The email address registered
`data.belongsTo` | **[Object]** | An array of organisations that the user belongs to containing a `domain` and `domainId` key
`data.integrations` | **[Object]** | An array of services/integrations that the user is able to access or has enabled. This lists out the ....

The above properties are just some of the properties that may be returned. Call the API endpoint to find and investigate the remaning properties that get returned

repository: Edumaps/edumaps-documentation

repo_name: Edumaps/edumaps-documentation


text:
# Candy Grid

Candy Grid is a small practice and documentation about the use of grid in css.

[TRY IT LIVE HERE](https://codepen.io/HebertCordero/pen/zYqzqKB)

## The Project

![Project](https://media.giphy.com/media/KB7IIaZ7yo8DyzSGZW/giphy.gif)

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License
[MIT](https://choosealicense.com/licenses/mit/)

repository: HebertCordero/CandyGrid

repo_name: HebertCordero/CandyGrid


text:
---
'@astrojs/markdoc': minor
'@astrojs/mdx': minor
'@astrojs/markdown-remark': major
'astro': major
---

Remove pre-shiki v0.14 theme names for compatibility. Please rename to the new theme names to migrate:

- `material-darker` -> `material-theme-darker`
- `material-default` -> `material-theme`
- `material-lighter` -> `material-theme-lighter`
- `material-ocean` -> `material-theme-ocean`
- `material-palenight` -> `material-theme-palenight`

repository: tsriram/astro

repo_name: tsriram/astro


text:
# Step 2: Gravitational Body Forces with Reference Stress

% Metadata extracted from parameter files.
```{include} step02_gravity_refstate-synopsis.md
```

## Simulation parameters

This example involves using a reference stress state to minimize the deformation when we apply the gravitational body forces.
The solution will be the perturbation from the reference state with zero displacements.
This is one method for obtaining an initial stress state associated with gravitational body forces.
We use the same roller boundary conditions that we used in Step 1.
The parameters specific to this example are in `step02_gravity_refstate.cfg`.

We use a reference stress state that matches the overburden (lithostatic) pressure.
We have uniform material properties, so the overburden is
%
\begin{equation}
\sigma_{xx} = \sigma_{yy} = \sigma_{zz} = \int_0^z \rho g \, dz = \rho g z,
\end{equation}
where compressive stress is negative.

```{code-block} cfg
---
caption: Parameters for reference stresses for Step 2. We only show the details for the slab material.
---
[pylithapp.problem.materials.slab]
db_auxiliary_field.iohandler.filename = mat_gravity_refstate.spatialdb
db_auxiliary_field.query_type = linear

[pylithapp.problem.materials.slab.bulk_rheology]
use_reference_state = True

auxiliary_subfields.reference_stress.basis_order = 1
auxiliary_subfields.reference_strain.basis_order = 0
```

## Running the simulation

```{code-block} console
---
caption: Run Step 2 simulation
---
$ pylith step02_gravity_refstate.cfg

# The output should look something like the following.
 >> /software/unix/py39-venv/pylith-debug/lib/python3.9/site-packages/pylith/meshio/MeshIOObj.py:44:read
 -- meshiopetsc(info)
 -- Reading finite-element mesh
 >> /src/cig/pylith/libsrc/pylith/meshio/MeshIO.cc:94:void pylith::meshio::MeshIO::read(pylith::topology::Mesh*)
 -- meshiopetsc(info)
 -- Component 'reader': Domain bounding box:
    (-100000, 100000)
    (-100000, 0)

# -- many lines omitted --

 >> /software/unix/py39-venv/pylith-debug/lib/python3.9/site-packages/pylith/problems/TimeDependent.py:139:run
 -- timedependent(info)
 -- Solving problem.
0 TS dt 0.01 time 0.
    0 SNES Function norm 4.578015693966e-15
  Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 0
1 TS dt 0.01 time 0.01
 >> /software/unix/py39-venv/pylith-debug/lib/python3.9/site-packages/pylith/problems/Problem.py:201:finalize
 -- timedependent(info)
 -- Finalizing problem.
WARNING! There are options you set that were not used!
WARNING! could be spelling mistake, etc!
There is one unused database option. It is:
Option left: name:-ksp_converged_reason (no value)
```

By design we set the reference stress state so that it matches the loading from gravitational body forces in our domain with uniform material properties.
As a result, the first nonlinear solver residual evaluation meets the convergence criteria.
The linear solver is not used; this is why PETSc reports an unused option at the end of the simulation.

## Visualizing the results

The `output` directory contains the simulation output.
Each "observer" writes its own set of files, so the solution over the domain is in one set of files, the boundary condition information is in another set of files, and the material information is in yet another set of files.
The HDF5 (`.h5`) files contain the mesh geometry and topology information along with the solution fields.
The Xdmf (`.xmf`) files contain metadata that allow visualization tools like ParaView to know where to find the information in the HDF5 files.
To visualize the data using ParaView or Visit, load the Xdmf files.

In {numref}`fig:example:reverse:2d:step02:solution` we use ParaView to visualize the displacement field using the `viz/plot_dispwarp.py` Python script.
First, we start ParaView from the `examples/reverse-2d` directory.
Before running the `viz/plot_dispwarp.py` Python script as described in {ref}`sec-paraview-python-scripts`, we set the simulation name in the ParaView Python Shell.

```{code-block} python
---
caption: Set the simulation in the ParaView Python Shell.
---
>>> SIM = "step02_gravity_refstate"
```

:::{figure-md} fig:example:reverse:2d:step02:solution
<img src="figs/step02-solution.*" alt="Solution for Step 2. The colors indicate the magnitude of the displacement." width="100%"/>

Solution for Step 2.
The colors of the shaded surface indicate the magnitude of the displacement, which is zero.
The undeformed configuration is show by the gray wireframe.
:::

repository: rwalkerlewis/pylith

repo_name: rwalkerlewis/pylith


text:
presentations
=============

Miscellaneous presentations

How to view
-----------
To view these slide shows, you need to make sure that you have installed:
- git
- go

#### Linux
- Archlinux: `sudo pacman -Sy git go`
- RHEL/Fedora: `sudo yum install git go`
- Debian: `sudo apt-get install git go`

#### Mac OS X
- Git: http://git-scm.com/download/mac
- Go: https://code.google.com/p/go/wiki/Downloads?tm=2

After you have made sure that both of these are installed, and that you
have [set your GOPATH][1], you can then get the presentation server
running after you've executed the following commands:
```bash
go get code.google.com/p/go.tools/cmd/present
git clone https://github.com/bgmerrell/presentations
cd presentations
$GOPATH/bin/present
```

[1]: http://golang.org/doc/code.html#GOPATH "Golang's website has some excellent documentation on how to do this"

repository: frostyfrog/presentations

repo_name: frostyfrog/presentations


text:
# Semaphore Client

[![Build Status](https://semaphoreci.com/api/v1/projects/a07c1244-d53a-462d-9c3b-0794881935df/1452738/badge.svg)](https://semaphoreci.com/renderedtext/semaphore-client)

![Semaphore logo](https://d1dkupr86d302v.cloudfront.net/assets/application_bootstrap/layout/semaphore-logo-a6d954e176b6975b511f314a0cc808dc94a8030210077e3a6e904fbe69dc5354.svg)

Semaphore Client is used to access Semaphore's API v2.

For more info about Semaphore see <https://www.semaphoreci.com>

For more info about Semaphore's API v2 see
<http://semaphoreci.com/docs/api-v2-overview.html>

## Issues

For problems directly related to the Client, [add an issue on GitHub](https://github.com/renderedtext/semaphore-client/issues/new).

For other issues, [submit a support ticket](https://semaphoreci.com/support).

repository: renderedtext/api

gha_language: Ruby

repo_name: renderedtext/api


text:
[![N|Solid](https://splashsync.github.io/Sylius-Bundle/img/splash-logo.jpg)](http://www.splashsync.com)

# Splash Bundle for Sylius

Welcome to the Sylius Bundle's Documentation!

This module implement Splash Sync connector for Sylius, the E-Commerce Solution for Symfony Framework. It provide access to multiples Objects for automated synchonization through Splash Sync dedicated protocol.

[![Build Status](https://travis-ci.org/SplashSync/Sylius-Bundle.svg?branch=master)](https://travis-ci.org/SplashSync/Sylius-Bundle)
[![Latest Stable Version](https://poser.pugx.org/splash/sylius-bundle/v/stable)](https://packagist.org/packages/splash/sylius-bundle)
[![Total Downloads](https://poser.pugx.org/splash/sylius-bundle/downloads)](https://packagist.org/packages/splash/sylius-bundle)
[![License](https://poser.pugx.org/splash/sylius-bundle/license)](https://packagist.org/packages/splash/sylius-bundle)

## Contributing

Any Pull requests are welcome!

This module is part of [SplashSync](http://www.splashsync.com) project.

repository: bigbizteam/Sylius-Bundle

gha_language: PHP

repo_name: bigbizteam/Sylius-Bundle


text:
# Proverb

For want of a horseshoe nail, a kingdom was lost, or so the saying goes.

Given a list of inputs, generate the relevant proverb. For example, given the list `["nail", "shoe", "horse", "rider", "message", "battle", "kingdom"]`, you will output the full text of this proverbial rhyme:

```text
For want of a nail the shoe was lost.
For want of a shoe the horse was lost.
For want of a horse the rider was lost.
For want of a rider the message was lost.
For want of a message the battle was lost.
For want of a battle the kingdom was lost.
And all for the want of a nail.
```

Note that the list of inputs may vary; your solution should be able to handle lists of arbitrary length and content. No line of the output text should be a static, unchanging string; all should vary according to the input given.

## Rust Installation

Refer to the [exercism help page][help-page] for Rust installation and learning
resources.

## Writing the Code

Execute the tests with:

```bash
$ cargo test
```

All but the first test have been ignored. After you get the first test to
pass, open the tests source file which is located in the `tests` directory
and remove the `#[ignore]` flag from the next test and get the tests to pass
again. Each separate test is a function with `#[test]` flag above it.
Continue, until you pass every test.

If you wish to run all ignored tests without editing the tests source file, use:

```bash
$ cargo test -- --ignored
```

To run a specific test, for example `some_test`, you can use:

```bash
$ cargo test some_test
```

If the specific test is ignored use:

```bash
$ cargo test some_test -- --ignored
```

To learn more about Rust tests refer to the [online test documentation][rust-tests]

Make sure to read the [Modules][modules] chapter if you
haven't already, it will help you with organizing your files.

## Further improvements

After you have solved the exercise, please consider using the additional utilities, described in the [installation guide](https://exercism.io/tracks/rust/installation), to further refine your final solution.

To format your solution, inside the solution directory use

```bash
cargo fmt
```

To see, if your solution contains some common ineffective use cases, inside the solution directory use

```bash
cargo clippy --all-targets
```

## Submitting the solution

Generally you should submit all files in which you implemented your solution (`src/lib.rs` in most cases). If you are using any external crates, please consider submitting the `Cargo.toml` file. This will make the review process faster and clearer.

## Feedback, Issues, Pull Requests

The [exercism/rust](https://github.com/exercism/rust) repository on GitHub is the home for all of the Rust exercises. If you have feedback about an exercise, or want to help implement new exercises, head over there and create an issue. Members of the rust track team are happy to help!

If you want to know more about Exercism, take a look at the [contribution guide](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks/README.md).

[help-page]: https://exercism.io/tracks/rust/learning
[modules]: https://doc.rust-lang.org/book/ch07-02-defining-modules-to-control-scope-and-privacy.html
[cargo]: https://doc.rust-lang.org/book/ch14-00-more-about-cargo.html
[rust-tests]: https://doc.rust-lang.org/book/ch11-02-running-tests.html

## Source

Wikipedia [http://en.wikipedia.org/wiki/For_Want_of_a_Nail](http://en.wikipedia.org/wiki/For_Want_of_a_Nail)

## Submitting Incomplete Solutions
It's possible to submit an incomplete solution so you can see how others have completed the exercise.

repository: bcaller/rust

repo_name: bcaller/rust


text:
+++
date = "2017-04-27T15:42:54+10:00"
next = "/moredata/2"
prev = "/?dql"
title = "A bigger dataset"
weight = 1
course = 4
courseName = "More Data"
endpoint = "/alter"
+++

Ok, we are off to a start with Dgraph and DQL. Let’s move it up a few notches.

Dgraph can also do query aggregation, geo-queries, string querying and more. But
for all that let's move from the small datasets we started with and try out
something bigger, much bigger.

In our github repository you'll find a
[dataset about movies, directors and actors](https://github.com/dgraph-io/tutorial/tree/master/resources/1million.rdf.gz).

Download it from that link and save into the `~/dgraph` directory or by running
the following in a terminal

```
cd ~/dgraph
wget "https://github.com/dgraph-io/tutorial/blob/master/resources/1million.rdf.gz?raw=true" -O 1million.rdf.gz -q

OR (We have curl in Dgraph's containers)

curl -L -o 1million.rdf.gz "https://github.com/dgraph-io/tutorial/blob/master/resources/1million.rdf.gz?raw=true"

```

Run the schema mutation using the run button and then load the dataset into
Dgraph from the terminal. You may be required to restart the Alpha with
`--cache_mb 4096` in order to handle bigger dataset.

```
docker exec -it dgraph dgraph live -f 1million.rdf.gz --alpha localhost:9080 --zero localhost:5080 -c 1
```

There's around one million triples in the dataset. Dgraph reports back exactly
how many triples were loaded and how long it took.

<!--There are
actors are described in the dataset.-->

It's a big database of movies, but it won’t trouble Dgraph. It is, however, big
enough for us to use more complex queries.

This dataset is a one million triple subset of a
[larger dataset of movies](https://github.com/dgraph-io/benchmarks/blob/master/data/21million.rdf.gz)
that contains around 230000 actors and around 86000 movies. We've made a subset
to make it quick to load, while having enough complexity to yield interesting
results. But, because it's a subset, you might find your favorite actor isn't
there, or that some actors are missing some of their movies.

Later in the tutorial, you might need to refer back to this page (or issue a
[schema query](../../basic/3)) to check the indexes or schema types. Remember
that we can't apply functions to edges that aren't indexed, and we'll learn that
some functions require particular indexes.

repository: dgraph-io/tutorial

repo_name: dgraph-io/tutorial


text:
SDK for adding SWAYco surveys to your site
==========================================

## Requirements ##
- jQuery >= 1.8

## Quick start ##

- Register on [SWAYco](http://swayco.co) site
- Go to [account page](http://swayco.co/app)
- Press "Add an Website" button and fill the form
- Copy `distribution id` at top of the page and `application id` of just added website
- Add scripts to your page:

```html
<script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script>
<script type="text/javascript" src="//swayco.co/public/storage/jquery.sway.0.0.2.js"></script>
```

- Init SDK:

```js
var swayIcon = new SwayIcon({
    distribution_id: 'distribution_id',
    application_type: 'web',
    application_id: 'application_id',
    onSuccess: function(surveyFrom) {
      // developer or researcher
      console.log('survey from', surveyFrom);

      // hide icon and survey:
      swayIcon.hideIcon();
    }
});
```

- Check user compatibility and load survey if we have surveys for current user:

```js
swayIcon.checkUserCompatibility({}, function(resp) {
  // resp can be one of: yes, no, may_be
  console.log(resp);
  if(resp == 'yes' || resp == 'may_be') {
    // load survey
    swayIcon.loadSurvey(function() {
      console.log('survey loaded (loadSurvey callback)');

      // show Sway icon
      swayIcon.showIcon();
    });
  }
});
```

## API ##

### Constructor ###

```
SwayIcon(<Object> options)
```

Creates new instance of SwayIcon.

`options` hash:
- `distribution_id` - `<String>` Required. Get it in [dashboard](http://swayco.co/app)
- `application_id` - `<String>` Required. You get it after adding new App or Website in [dashboard](http://swayco.co/app)
- `container` - `<DOM Node | jQuery Object>`. If provided, survey will be placed inside this container immediately.
- `onLoaded()` - `<Function>`. Callback, which will be called, when the survey will be successfully loaded (after `.loadSurvey()` call).
- `onQuestions(<Object> questions)` - `<Function>`. Callback, which will be called after `onLoaded`. One argument with array of questions and answers for loaded survey.
- `onSuccess(<String> surveyFrom)` - `<Function>`. Callback, which will be called after survey successful completes. One argument with String (`developer` or `researcher`).
Shows whose survey was passed.
- `onTerminated()` - `<Function>`. Callback, which will be called, when user choose terminating answer.
- `onAudienceMismatch()` - `<Function>`. Callback, which will be called, if we do not have the survey for this user.
- `onError(<String> err)` - `<Function>`. Callback, which will be called, if you enter invalid `distribution_id` or `application_id`, or on server error.

### Methods ###

#### Load survey ####

```
.loadSurvey([<Object> options[,<Function> callback]])
```

- `options` hash accept following CSS properties for future survey container:
  - `left` - Default: `'auto'`
  - `right` - Default: `'20px'`
  - `top` - Default: `'90px'`
  - `bottom` - Default: `'auto'`
  - `width` - Default: `'500px'`

  You can pass values in any valid jQuery format.

- `callback` - function which will be called, when the survey will be successfully loaded.

#### Show Icon ####

```
.showIcon([<Object> options])
```

Show fixed icon on top-right of page. On click on this icon will be showed survey container.

- `options` hash accept following CSS properties for future icon:
  - `left` - Default: `'auto'`
  - `right` - Default: `'20px'`
  - `top` - Default: `'90px'`
  - `bottom` - Default: `'auto'`

  You can pass values in any valid jQuery format.

#### Hide Icon ####

```
.hideIcon()
```

Hide icon and survey container.

#### Check user compatibility ####

```
.checkUserCompatibility(<Object> userInformation, <Function> callback(<String> response))
```

Check whether we have surveys for provided user data.

- `userInformation` hash:
  - `country` can be any string
  - `state` can be any string
  - `age` can be one of: "13-17 yrs", "18-24 yrs", "25-34 yrs", "35-44 yrs", "45-54 yrs", "55-64 yrs", "65+ yrs"
  - `gender` can be one of: "Male", "Female"
  - `device` can be one of: "Desktop/Laptop", "Mobile", "Tablet"
  - `os` can be one of: "Windows", "Mac", "Linux", "IOS", "Android", "Other"
  - `browser` can be one of: "Chrome", "Firefox", "Safari", "Internet Explorer", "Other"

- `callback(<String> response)` - function with one argument. Response indicates surveys availability for current user and can be `yes`, `no` or `may_be`.


text:
# Game of Apps Development Intern Interview
### Submission: Joe Dai

> Thanks for your interest in the Game of Apps developer intern position! This repo contains a list of tasks for you to do, so we can get a gauge of your skill and passion for development.
>
> You're expected to know the basics of the Git development workflow. If you don't know or you want a review, check out this [tutorial](https://www.raywenderlich.com/179717/open-source-collaboration-using-git-and-github).

## Instructions

> The goal is to submit a pull request that accomplishes the following tasks. While the pull requests are public, don't blindly copy others. The follow up interview will involve questions on your submission.
>
> Fork this repository to begin.
>
> Commit your changes to your fork, then email the link of your fork to<EMAIL_ADDRESS>
## Challenge 1: Algorithms

> Your first challenge is to solve two algorithm questions. You'll be judged based on correctness, performance, and code readability.

**See solution at: [Algorithms.java](./Algorithms/src/main/xyz/jdtec/algorithms/Algorithms.java)**

**See JUnit tests at: [AlgorithmsTest.java](./Algorithms/src/test/xyz/jdtec/algorithms/AlgorithmsTest.java)**

> ### Question 1: Find all pairs for a given sum
>
> Create a function that accepts an array of integers and a target sum. The function will print all pairs of integers in the array whose sum is equal to the target sum. Here's an example:
>
> ```java
> int[] testArray = {2, 4, 5, 1, 3, 5, 4};
> int targetSum = 6;
> // Expected pairs are (to be printed on the console):
> // (2, 4)
> // (1, 5)
>
> findPairs(testArray, targetSum);
> ```
>
> Here's a function signature to start you off:
>
> ```java
> void findPairs(int[] testArray, int targetSum) {
>   // your code here
> }
> ```
>
> ### Question 2: Is Palindrome?
>
> Create a function that checks if a string is a palindrome and returns `true` or `false`. A palindrome is a word that reads the same way even if you read it backwards.
>
> Example palindromes:
>
> - radar
> - bob
> - asdfdsa
>
> Here's a function signature to start you off:
>
> ```java
> boolean isPalindrome(String testString) {
>   // your code here
> }
> ```

## Challenge 2: Android

> Your second challenge is to develop a small app from scratch. Here are the requirements:
>
> - It should show a list of images.
> - Tapping on an image should navigate to a new screen that shows the selected picture

**See app solution at: [Android App](./Android%20App/app/src/main) — "ImageViewer"**

---

> ### Notes:
>
> - A good developer tries to write code that is easy to understand. The industry has a set of best practices that focus on writing easy to maintain code. Here's a set of guidelines on these best practices: [Java Style Guide](https://github.com/raywenderlich/java-style-guide).
>

---

*All code within this repo is licensed under the [MIT license](https://opensource.org/licenses/MIT)*


text:
# Review 4 NP sets

## Warning of stability
These NP sets are _NOT_ tested regularly as part of the acceptance, integration or unit tests. This is due to rather complex system requirements and the specific setups required. These sets are tested and working leading up to the C4A year 4 review, January 2016.

## Walkthrough of each NP set and demo set up.

The description of the scenarios for which these NP sets are created can be found here: https://docs.google.com/document/d/1BN3j2N00QB4kvFoRLHaUYSAxn7sUYeMCWL6vaH70KUQ/edit#

The technical integration document for the work can be found here: https://wiki.gpii.net/w/Year_4_Review_Integration_Roadmap_(C4A)

repository: mcanthony/universal

repo_name: mcanthony/universal


text:
---
layout: paper
year: 2006
title: Design and Implementation of Turbo Decoders for Software Defined Radio
publisher: IEEE
png: lin-sips06.png
pages: 22--27
month: October
location: Banff, Alberta, Canada
file: lin-sips06.pdf
doi: 10.1109/SIPS.2006.352549
day: 2-4
booktitle: Proceedings of the IEEE Workshop on Signal Processing Systems (SiPS 2006)
author: Yuan Lin, Scott A. Mahlke, Trevor N. Mudge, Chaitali Chakrabarti, Alastair Reid, Krisztián Flautner
ar_shortname: SiPS 06
ar_file: SiPS_06
affiliation: ARM Ltd and University of Michigan and Arizona State University
abstract: |

    Software Defined Radio(SDR) is an emerging paradigm for wireless
    terminals, in which the physical layer of communication
    protocols is implemented in software rather than by ASICs. Many
    of the current and next generation wireless protocols include
    Turbo coding because of its superior performance. However, Turbo
    decoding is computationally intensive, and its low power
    implementations have typ- ically been in ASICs. This paper
    presents a case study of algorithm-architecture co-design of
    Turbo decoder for SDR. We present a programmable DSP architecture
    for SDR that includes a set of architectural features to
    accelerate Turbo decoder computations. We then present a parallel
    window scheduling for MAX-Log-MAP component decoder that
    matches well with the DSP architecture. Finally, we present
    a software implementation of Turbo decoder for W-CDMA on the DSP
    architecture and show that it achieves 2Mbps decoding throughput.
ENTRYTYPE: inproceedings
ID: DBLPconf/sips/LinMMCRF06
bibtex: |
    @inproceedings{DBLP:conf/sips/LinMMCRF06
        , abstract = {
    Software Defined Radio(SDR) is an emerging paradigm for wireless
    terminals, in which the physical layer of communication
    protocols is implemented in software rather than by ASICs. Many
    of the current and next generation wireless protocols include
    Turbo coding because of its superior performance. However, Turbo
    decoding is computationally intensive, and its low power
    implementations have typ- ically been in ASICs. This paper
    presents a case study of algorithm-architecture co-design of
    Turbo decoder for SDR. We present a programmable DSP architecture
    for SDR that includes a set of architectural features to
    accelerate Turbo decoder computations. We then present a parallel
    window scheduling for MAX-Log-MAP component decoder that
    matches well with the DSP architecture. Finally, we present
    a software implementation of Turbo decoder for W-CDMA on the DSP
    architecture and show that it achieves 2Mbps decoding throughput.
    }
        , affiliation = {ARM Ltd and University of Michigan and Arizona State University}
        , ar_file = {SiPS_06}
        , ar_shortname = {SiPS 06}
        , author = {Yuan Lin and
    Scott A. Mahlke and
    Trevor N. Mudge and
    Chaitali Chakrabarti and
    Alastair Reid and
    Kriszti{\'a}n Flautner}
        , booktitle = {Proceedings of the IEEE Workshop on Signal Processing Systems
    (SiPS 2006)}
        , day = {2-4}
        , doi = {10.1109/SIPS.2006.352549}
        , file = {lin-sips06.pdf}
        , location = {Banff, Alberta, Canada}
        , month = {October}
        , pages = {22--27}
        , png = {lin-sips06.png}
        , publisher = {IEEE}
        , title = {{D}esign and {I}mplementation of {T}urbo {D}ecoders for {S}oftware {D}efined {R}adio}
        , year = {2006}
    }
---


text:
# Automated k6 load testing with Google Cloud CI/CD

This is an example repo for how to setup k6 with Google Cloud CI/CD to build load testing into an automation flow.

The full guide describing how to use this repository is located [here](https://k6.io/blog/integrating-k6-with-google-cloud-build/).

## Examples

| File                                                           | Description                                   |
| -------------------------------------------------------------- | --------------------------------------------- |
| [local-example/cloudbuild.yaml](local-example/cloudbuild.yaml) | Runs locally on Google's CI/CD infrastructure |
| [cloud-example/cloudbuild.yaml](cloud-example/cloudbuild.yaml) | Runs on k6 cloud                              |

## Run Local

```bash
# Run locally
k6 run scripts/test.js

# Run via Docker
docker run -i loadimpact/k6 run - <scripts/test.js

# Run via Docker Compose
docker-compose run k6
```