text:
# Snake on pure Java

## About

Very simple snake game code written on pure Java language. Game uses "Constant Game Speed with Maximum FPS" Game Loop. Main logic of game consist of two separate arrays x and y coordinates, without using double array with objects.

Snake is the a one of the most famous older classic video game concept where the player maneuvers a line which grows in length, with the line itself being a primary obstacle.

The size of each of the joints of a snake is by default 32px. The snake is controlled with the WASD keys. Initially, the snake has three joints. If the game is finished, the "Game Over" message is displayed in the middle of the board, then you can start new game.

## Prerequisites

[JDK 15.0.1](https://www.oracle.com/java/technologies/javase-jdk15-downloads.html)

## Installation

Download from git using this command:

```
git clone https://github.com/alma-iceee/Snake-on-Pure-Java.git
```

Then compile and run Game.class (Shift + F10)

Done! You can start the game!

## Settings

You can set snake's speed from 5 up to 15.

If you want change some other settings, you can set it inside of code. For example, change preferred screen size in:
```
private final int BLOCK_SIZE = 16
```
However, don't forget to recompile main class after change.

## Authors

There are information about us. Click on "About Us" button in Game Menu.

* **Almas Sharipkhan** - *Main Developer* - [alma-iceee](https://github.com/alma-iceee/)
* **Askarbek Makhmedov** - *Contributing Developer* - [askarbek101](https://github.com/askarbek101/)

## References

* **Game Loop** - [deWiTTERS Game Loop](https://dewitters.com/dewitters-gameloop/)
* **Game Logic** - [ZetCode Java Snake](https://zetcode.com/javagames/snake/)
* **Game Architecture** - [RealTutsGML](https://www.youtube.com/channel/UCOs7Q7IeuzgRyARaEqif75A/)

## License

This project is licensed under the MIT License.

## Citation

If you find this code useful for your research, please use the star this repository.

You are welcome to contribute this project.

Thank you!

repository: alma-iceee/Snake-on-Pure-Java

repo_name: alma-iceee/Snake-on-Pure-Java


text:
[![Build Status](https://app.travis-ci.com/FelixKiunke/esqlcipher.svg?branch=master)](https://app.travis-ci.com/FelixKiunke/esqlcipher)
[![Hex.pm](https://img.shields.io/hexpm/v/esqlcipher.svg)](https://hex.pm/packages/esqlcipher)
[![Hex.pm](https://img.shields.io/hexpm/dt/esqlcipher.svg)](https://hex.pm/packages/esqlcipher)

Esqlcipher
==========

An Erlang nif library for [sqlcipher](https://github.com/sqlcipher/sqlcipher).

Introduction
------------

This library allows you to use the [sqlcipher](https://github.com/sqlcipher/sqlcipher)
library based on the fantastic [sqlite3](https://www.sqlite.org/index.html)
engine from erlang. The library is implemented as a nif library, which allows
for the fastest access to a sqlite database. This can be risky, as a bug
in the nif library or the sqlite database can crash the entire Erlang
VM. If you do not want to take this risk, it is always possible to
access the sqlite nif from a separate erlang node.

Special care has been taken not to block the scheduler of the calling
process. This is done by handling all commands from erlang within a
lightweight thread. The erlang scheduler will get control back when
the command has been added to the command-queue of the thread.

Versions
--------

The library currently uses Sqlcipher version `4.5.0`, which is based on sqlite
version `3.36.0` compiled using the following compile-time options:

```
-DSQLITE_DQS=0 -DSQLITE_HAS_CODEC -DSQLITE_DEFAULT_WAL_SYNCHRONOUS=1 -DSQLITE_LIKE_DOESNT_MATCH_BLOBS -DSQLITE_OMIT_DEPRECATED -DSQLITE_TEMPSTORE=2 -DSQLITE_THREADSAFE=1 -DSQLITE_USE_URI -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_FTS5 -DSQLITE_ENABLE_FTS3_PARENTHESIS -DSQLITE_ENABLE_JSON1 -DSQLITE_ENABLE_MATH_FUNCTIONS
```

Caveats
-------

The interface could probably use some polishig. Sqlcipher mostly this works
exactly like SQLite3, except for the crypto stuff. However, the Sqlcipher
included in this is built using some breaking compile time options such as
`SQLITE_DQS = 0` (see [here](https://www.sqlite.org/compile.html#recommended_compile_time_options)).
This means that string literals in SQL commands *must* use single quotes.
For instance, this:
```SQL
INSERT INTO test_table VALUES('hello', 11);
```
works while the following will not do what you would expect:
```SQL
# this is wrong!
INSERT INTO test_table VALUES("hello", 11);
```

See `rebar.config.script` for all compile options that were set!

TODO (Incomplete list)
----------------------

- Better testing of encryption
- Primitives that support named databases (i.e. `sqlite3_key_v2()`)
- Configuration options (HMAC, PBKDF2 iterations, salts, page sizes, ...)
- Testing on other platforms
- ...

On the Author(s)
----------------

This version is derived from Maas-Maarten Zeeman’s Erlang sqlite
library [esqlite](https://github.com/mmzeeman/esqlite).
I (Felix Kiunke) merely made some smaller amendments to provide
support for sqlcipher, a library that provides encryption for sqlite
databases.

repository: FelixKiunke/esqlcipher

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: FelixKiunke/esqlcipher


text:
# bitFlip

bitFlip is a C++ library that has a singular purpose:

The fast reversal of the order of bits in an arbitrary std::integer.

It was created to evaluate and benchmark different approaches to this simple task

+ benchmarked with google benchmark
+ unit tested with gtest

In order to use it you must have:

  - a machine that has a processor that supports intel avx extensions
  - a version of nasm installed
  - a gcc compiler that supports Intel intrinsics

Advanced Vector Extensions as defined by Wikipedia on the [Wikipedia Article][wiki]

> Advanced Vector Extensions (AVX) are extensions to the x86 instruction set architecture for microprocessors from Intel and AMD proposed by Intel in March 2008 and first supported by Intel with the Sandy Bridge[1] processor shipping in Q1 2011 and later on by AMD with the Bulldozer[2] processor shipping in Q3 2011. AVX provides new features, new instructions and a new coding scheme.

### Tech

bitFlip uses a number of different approaches to flip those bits

* [Assembly] - win32 / elf. Compile with nasm - this routine is the fastest - just
* [Intel Implicit AVX] - Using the handy gcc routines
* [Naive approach] - A fun way to visualize a solution (also nice and terse)
* [Table approach] - Let's see how the compiler optimizes these
* [Lambda Syntax] - Just gotta try it out
* [Scala equivalent] - Look at the sveltness of the code - and the how fairs the JVM?

### NB population counter
As a way to see how fast avx instruction can be. I also include the popcnt instruction which requires no lashing together of assmebly.
This is benchmarked at

### Installation

bitFlip has both a cmake installer and makefiles.
The cmake installation will detect if you require google benchmark and gtest and will download and installed if required

### cmake
```
$ mkdir cmake-build-release
$ cd cmake-build-release
$ cmake ..
cmake .. --help-usagecmake -L | awk '{if(f)print} /-- Cache values/{f=1}'
Specify --help for usage, or press the help button on the CMake GUI.
CMAKE_BUILD_TYPE:STRING=Release
CMAKE_GNUtoMS:BOOL=OFF
CMAKE_INSTALL_PREFIX:PATH=C:/Program Files (x86)/bitFlip
NASM_EXE:FILEPATH=C:/msys2/mingw64/bin/nasm.exe
TESTAPP_ASMFORMAT:STRING=win64
TESTAPP_USE_ASM:BOOL=true
TESTAPP_USE_BENCHMARK:BOOL=true
TESTAPP_USE_TABLEHEADERS:BOOL=true
benchmark_ROOT_DIR:PATH=
shlwapi_ROOT_DIR:PATH=

```

example:
```
mkdir cmake-build-release
cmake .. -G 'MSYS Makefiles'
make
```

### make
```
$ make help
This makefile supports the following configurations:
    MinGW64_Release MinGW64_Debug Arch_Release Arch_Debug

and the following targets:
    build  (default target)
    clean
    clobber
    all
    help

Makefile Usage:
    make [CONF=<CONFIGURATION>] [SUB=no] build
    make [CONF=<CONFIGURATION>] [SUB=no] clean
    make [SUB=no] clobber
    make [SUB=no] all
    make help
```

example (for MinGW):
```
$ make CONF=MinGW64_Release
```

##### Commandline executable

```
tests/./flipbits --help
```
example:

```
tests/./flipBits.exe  -o test.txt -f I 0 100
```

saves as flipped decimal representations to test.txt

##### Benchmark/Tests

```
tests/./TestApp

```

##### Just for fun - Scala
Prints out bit flipped integers (as large as BigInt) from a range [FROM] [TO]

to run:
open sbt and execute:
sbt:bitflip> run [FROM] [TO]

##### Scala example:

```
$ sbt
Listening for transport dt_socket at address: 5005
[info] ...
sbt:bitflip> run<PHONE_NUMBER>010<PHONE_NUMBER>020

```

output:

```
[debug] Waiting for thread run-main-0 to terminate.
...
1000000000010-->343742425879
1000000000011-->893498239767
1000000000012-->206303472407
1000000000013-->756059286295
1000000000014-->481181379351
1000000000015-->1030937193239
1000000000016-->34504780567
1000000000017-->584260594455
1000000000018-->309382687511
1000000000019-->859138501399
1000000000020-->171943734039

[debug]         Thread run-main-0 exited.

```

##### An apple for apples command using the compiled command:

```
$ tests/./flipBits -f I<PHONE_NUMBER>010<PHONE_NUMBER>020

```

### Benchmark Results

Google Benchmark to iterate over 10240 byte reversals

```

Run on (8 X 3292 MHz CPU s)
11/10/17 10:12:26
----------------------------------------------------------------------
Benchmark                               Time           CPU Iterations
----------------------------------------------------------------------
BM_Flip_AVX                           215 ns        214 ns    2986667 <- 8bit
BM_Flip_AVX16                        2548 ns       2511 ns     280000
BM_Flip_IntrAVXArr_VecClass           772 ns        767 ns     896000
BM_Flip_IntrAVXVec_VecClass           778 ns        785 ns     896000
BM_Flip_IntrAVXClass_ptr              412 ns        414 ns    1659259 <-64bit The Winner
BM_Flip_IntrAVXClassNullBuffer     678206 ns     662667 ns        896
BM_Flip_IntrAVX64                     356 ns        353 ns    2036364
BM_Flip_IntrAVX64i256                 746 ns        753 ns    1120000
BM_Flip_Table16                      3029 ns       2999 ns     224000
BM_Flip_Table32                      3812 ns       3850 ns     186667
BM_Flip_Naive                        9830 ns       9766 ns      64000
BM_Flip_Naive64                     11952 ns      11963 ns      64000
BM_Flip_Mask                        16748 ns      16497 ns      40727
BM_Flip_lloop                       25314 ns      24902 ns      26353
BM_Flip_NaiveArrayll                26762 ns      26228 ns      28000
BM_Flip_NaiveLambda                 25067 ns      25181 ns      23579
BM_popcntWegner                     30923 ns      30692 ns      22400
BM_popcnt_wegner_lambda            128452 ns     128348 ns       5600
BM_popcnt_SWAR64                     4036 ns       4018 ns     186667
BM_popcnt16                         18439 ns      18415 ns      40727
BM_popcnt32                          8273 ns       8196 ns      89600
BM_popcnt64                          5287 ns       5312 ns     100000
BM_popcntIntrinsic                      2 ns          2 ns  320000000

```

ScalaTest Execution times to iterate 10240

```
[info] - bitFlip inline benchmark with warming
[info] Run completed in 6 seconds, 165 milliseconds.
[info] Total number of tests run: 1
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.

```

### Development

Please feel free...

License
----

MIT

[//]: # (These are reference links used in the body of this note and get stripped out when the markdown processor does its job. There is no need to format nicely because it shouldn't be seen. Thanks SO - http://stackoverflow.com/questions/4823468/store-comments-in-markdown-syntax)

   [wiki]: <https://en.wikipedia.org/wiki/Advanced_Vector_Extensions>

license: MIT

repository: claydonkey/bitFlip

repo_name: claydonkey/bitFlip


text:
# Terraform::Alicloud::DbBackupPolicy

Provides an RDS instance backup policy resource and used to configure instance backup policy.

~> **NOTE:** Each DB instance has a backup policy and it will be set default values when destroying the resource.

## Properties

`InstanceId` - (Required) The Id of instance that can run database.

`BackupPeriod` - (Optional) DB Instance backup period. Valid values: [Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday]. Default to ["Tuesday", "Thursday", "Saturday"].

`BackupTime` - (Optional) DB instance backup time, in the format of HH:mmZ- HH:mmZ. Time setting interval is one hour. Default to "02:00Z-03:00Z". China time is 8 hours behind it.

`RetentionPeriod` - (Optional) Instance backup retention days. Valid values: [7-730]. Default to 7.

`LogBackup` - (Optional) Whether to backup instance log. Default to true.

`LogRetentionPeriod` - (Optional) Instance log backup retention days. Valid values: [7-730]. Default to 7. It can be larger than 'retention_period'.

## Return Values

### Fn::GetAtt

`Id` - The current backup policy resource ID. It is same as 'instance_id'.

`InstanceId` - The Id of DB instance.

`BackupPeriod` - DB Instance backup period.

`BackupTime` - DB instance backup time.

`RetentionPeriod` - Instance backup retention days.

`LogBackup` - Whether to backup instance log.

`LogRetentionPeriod` - Instance log backup retention days.

## See Also

* [alicloud_db_backup_policy](https://www.terraform.io/docs/providers/alicloud/r/db_backup_policy.html) in the _Terraform Provider Documentation_


text:
# Contributing to Handsontable

Your contributions to this project are very welcome. If you want to fix a bug or propose a new feature, you can open a new Pull Request but first make sure it follows these general rules:

1. Sign this [Contributor License Agreement](https://goo.gl/forms/yuutGuN0RjsikVpM2) to allow us to publish your changes to the code.
2. Make your changes on a separate branch. This will speed up the merging process.
3. Always make the target of your pull request the `develop` branch, not `master`.
4. Do not edit files in dist/ directory.
5. **Important: For any change you make, please add at least one test case** in `tests/`. That will help us understand the issue and make sure that it stays fixed forever.
6. Please review our [coding style](https://github.com/handsontable/handsontable/wiki/Coding-style) for instructions on how to properly style the code.
7. Add a thorough description of all the changes.

Thank you for your commitment!

## Team rules

The Handsontable team utilizes Git-Flow. Read more - [How we use Git-Flow](https://github.com/handsontable/handsontable/wiki/How-we-use-Git-Flow)


text:
# AACT
Administer AACT: Aggregated Analysis of ClinicalTrials.gov

## Getting Started

At the moment you have to setup aact before setting up aact-admin. So make sure you do that first.
* [aact core](https://github.com/ctti-clinicaltrials/aact)
Make sure you've set values for the environmental variables AACT_DB_SUPER_USERNAME and AACT_PASSWORD

You may still need to create aact_alt. So enter the psql shell to check if it's there and add it if it's not.

`psql template1`

`\l`
if it's listed, you can exit the shell now. If it is missing, then create it.

`template1=# create database aact_alt;`

`template1=# \q` (quit out of postgres)

Clone the aact-admin repo.

cd into the aact-admin directory and run the setup files

For mac you can run the setup file in the terminal

`./bin/mac_setup`

If you aren't on a mac, then install libv8 and therubyracer according to the method for your system.
Then run the generic setup script:

`./bin/setup`

## Environment variables

After running either setup scrupt, you'll have a `.env` file that contains an empty template for the environment variables you'll need. These variables are copied from `.env.example`

Setup the folders you need with `Util::FileManager.new` in the console

setup the databases with
`RAILS_ENV=test bin/rake db:create`
`bin/rake db:create`
`RAILS_ENV=test bin/rake db:migrate`
`bin/rake db:migrate`

Grant permissions to the read_only role.
`bin/rake db:setup_read_only`
`bin/rake db:setup_read_only RAILS_ENV=test`

## Sanity checks

Sanity checks are a simple way for us to check that the tables in the database have been imported correctly and gives some insight into how the data looks at a high level. Both the daily and full import rake tasks run the sanity check automatically. To run it manually, open up a Rails console and enter `SanityCheck.run`. This will create a record in the `sanity_checks` table with a report represented in JSON.

## Guidelines

Use the following guides for getting things done, programming well, and
programming in style.

* [Protocol](http://github.com/thoughtbot/guides/blob/master/protocol)
* [Best Practices](http://github.com/thoughtbot/guides/blob/master/best-practices)
* [Style](http://github.com/thoughtbot/guides/blob/master/style)

repository: CharlesVincentAnderson/aact-admin

gha_license_id: MIT

repo_name: CharlesVincentAnderson/aact-admin


text:
# Simple Todo List

[Access The Application Here](https://eviltester.github.io/simpletodolist/todolists.html)

Originally based on the Vanilla JS TodoMVC project.

Then amended to support multiple lists, and a password protected 'admin' section. Code heavily amended to adopt a simpler coding style,

Designed to be a simple, self contained and controllable Test Application, rather than a JavaScript Showcase.

This is used as the test application for the Linkedin Learning Course:

- [Selenium WebDriver Page Objects and Abstractions](https://www.eviltester.com/page/onlinetraining/courses/#selenium-webdriver-page-objects-and-abstractions)

[Direct Link to Course on Linkedin](https://www.linkedin.com/learning/advanced-selenium-page-objects-and-gui-automation)

repository: eviltester/simpletodolist

repo_name: eviltester/simpletodolist


text:
# CSS Car

CSS Car  is a car made with HTML, CSS and SVG shapes. It's aimed at creating an object with cool animations without the use of javascript.

## Installation

Clone the Repo via [GitHub](https://github.com/).

```bash
git clone https://github.com/cipher-tech/cssCar.git
```

## Usage

```python
How to run the app

# Start the server
  npm run start

# Open on browser
  Open the index.html file with a browser(preferably Chrome).

# run on local server
  You can install and run it on any server of your choice.
```

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

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

repository: hellodemola/cssCar

repo_name: hellodemola/cssCar


text:
# A starter Gatsby template for a Wordpress blog, built using Typescript and Ant Design

[![Github version](https://img.shields.io/github/package-json/v/sagar7993/gatsby-wordpress-typescript-scss-blog)](https://github.com/sagar7993/gatsby-wordpress-typescript-scss-blog/releases)
[![GitHub License](https://img.shields.io/github/license/sagar7993/gatsby-wordpress-typescript-scss-blog)](https://opensource.org/licenses/MIT)
[![GitHub issues](https://img.shields.io/github/issues-raw/sagar7993/gatsby-wordpress-typescript-scss-blog.svg)](https://github.com/sagar7993/gatsby-wordpress-typescript-scss-blog/issues)

This is an opinionated starter project to help you create lightning fast PWA websites with [Gatsby](https://gatsbyjs.org) and [Wordpress](https://wordpress.com) CMS, built using [Typescript](http://www.typescriptlang.org/), [SCSS](https://sass-lang.com/) and [Ant Design](https://github.com/ant-design/ant-design).

- **[Gatsby](https://gatsbyjs.org)** static site generator
- **[Wordpress](https://wordpress.com)** for content management
- **[Typescript](https://typescriptlang.org)** for statically-typed clean JavaScript code
- **[Ant Design](https://github.com/ant-design/ant-design)** for theming and UI

## Demo

https://gatsby-wordpress-typescript-scss-blog.netlify.com/

## Using the environment variables

This Gatsby starter template comes with 2 environments, one for development and testing, and another for production. This allows you to use different tokens, API URL's, social account id's etc as needed for your development, testing and production environments. The environment variables defined are as follows:

- GATSBY_GITHUB_USER (Mandatory)
This is the username of your Github account

- GATSBY_GITHUB_REPO (Mandatory)
This is the Github repository URL

- GATSBY_SITE_NAME (Mandatory)
This is the title of the generated Gatsby site

- GATSBY_SITE_DESCRIPTION (Mandatory)
This is the description of the generated Gatsby site

- GATSBY_SITE_URL_PATH (Mandatory)
This is the URL where you will be deploying the generated Gatsby site, but without the http protocol
For example `mywebsite.com` or `localhost:8000`

- GATSBY_SITE_URL_PROTOCOL (Mandatory)
This is the http protocol of the URL where you will be deploying the generated Gatsby site, i.e. `http` or `https`

- GATSBY_WORDPRESS_URL_PATH (Mandatory)
This is the URL of your wordpress site from where you will fetch your posts/pages etc, but without the http protocol
For example `mywebsite-wordpress.com` or `localhost:8001`

- GATSBY_WORDPRESS_URL_PROTOCOL (Mandatory)
This is the http protocol of the URL of your wordpress site from where you will fetch your posts/pages etc, i.e. `http` or `https`

- GATSBY_SITE_AUTHOR
This is the name of the Gatsby site author

- GATSBY_ENABLE_COMMENTS (Optional)
This is a feature switch flag. If it's set to `1`, comment form will be displayed on all your blog posts. If this is not defined or it's value is anything other than `1` then commenting will be disabled on the website. Check out the documentation on `Comments` section below.

- GATSBY_PRIMARY_ACCENT_COLOR (Optional)
This is the primary accent color of your website, which will be used as the theme color in your web manifest file.

- GATSBY_INSTAGRAM_SOURCE (Optional)
This is the name of the Instagram account whose feed you want to display on your website.
Note: Do not include the `@` symbol here.

- GATSBY_TWITTER_SOURCE (Optional)
This is the handle of the Twitter account whose timeline/follow button you want to display on your website.
Note: Do not include the `@` symbol here.

- GATSBY_FACEBOOK_SOURCE (Optional)
This is the name of the Facebook account/page whose timeline/like button you want to display on your website.
Note: Do not include the `@` symbol here.

- GATSBY_GOOGLE_ANALYTICS (Optional)
This is your Google Analytics tracking id.

- GATSBY_STATICMAN_BASE (Optional)
This is the base URL of the of your Staticman instance. You can use either the public Staticman instance or host your own.
Note: This is required to enable comments on the website.

Note: Any new environment variables you want to define MUST have the `GATSBY_` prefix. You can access them using `process.env.GATSBY_MY_ENVIRONMENT_VARIABLE`. Also, `process.env` object cannot be de-structured. To access any variable from this object, use the full variable name.

For example, the following code will NOT work.

```javascript
const { GATSBY_MY_ENVIRONMENT_VARIABLE } = process.env;
```
## Setting up Wordpress locally on your machine

1. Install [Docker](https://www.docker.com/get-started) on your machine

2. Use the included docker-compose.yml file in this repository to setup Wordpress on your local machine by using the command `docker-compose up -d` (Have a look at Docker's documentation for more details)

3. This will create a dockerized wordpress installation on your machine, which you can access here [http://localhost:8001](http://localhost:8001)

4. As given in the docker-compose.yml file, your credentials are the following by default (make sure you change these credentials before deploying anything to production)

    - MySQL username: `wordpress`
    - MySQL password: `wordpress`
    - Wordpress username: `wordpress`
    - Wordpress password: `wordpress`

5. Once you're done setting up and installing Wordpress, you will see the Wordpress admin dashboard. Go to plugins, and add the following plugins

    ###### If you're planning to use Wordpress custom fields in your Gatsby GraphQL schema, install these 2 plugins (optional, but recommended)

    - `Advanced Custom Fields`
    - `ACF to REST API`

        Note: After installing these 2 plugins

        - Go to Wordpress Admin Dashboard here [http://localhost:8001/wp-admin](http://localhost:8001/wp-admin) -> Settings -> Permalinks -> Choose either `Day and name` or `Month and name` option as your permalink structure and click Save.
        - In the `ACF to REST API` setting just below the permalinks, select `v2` from the `Request Version` menu

    ###### If you're planning to use Yoast for your SEO in the Gatsby GraphQL schema, install these 3 plugins (optional, but recommended)

    - `Yoast SEO`
    - `Yoast to REST API`
    - `ACF Content Analysis for Yoast SEO`

6. At this point you have a fully functional Wordpress blog setup, but you haven't added any posts to it. If you type `gatsby develop` in your terminal in the project directory at this point, there won't be any posts or pages for Gatsby to pull. If you want to copy the example blog posts that I have used in the demo for this Gatsby starter template, follow these instructions

    - Install this plugin to your Wordpress installation `All-in-One WP Migration` by going Wordpress Admin Dashboard to [http://localhost:8001/wp-admin](http://localhost:8001/wp-admin) -> Plugins -> Add New, and then activate this plugin.
    - Go to this plugin's settings, and click on `Import` -> `Import From` -> `File`
    - Select the file `localhost.wpress` from the root folder of this repository.
    - Done! The plugin will now import all the sample posts that I have used for creating the demo of this Gatsby starter template.

## Using existing Wordpress blog as your source instead of setting up local installation

If you're planning to use an already existing Wordpress blog as your CMS instead of setting everything up on your local machine, then simply ignore the instructions given in the section above. You might still want to consider installing the Wordpress plugins recommended above if you haven't already.

## Ant Design

This Gatsby starter template uses [Ant Design](https://github.com/ant-design/ant-design) for theming and UI. Although, it's not mandatory to use it for any new visual components that you might create. Feel free to build everything from scratch or use any other UI framework of your choice.

## Comments

- User-generated content are typically the Achilles heel of any static site — a blog commenting platform, a reviews section or a voting system are just a few common examples. To implement these on a static site, developers often resort to third-party services that inject content into pages through JavaScript embeds or iframes.
- [Staticman](https://staticman.net/) handles user-generated content for you and transforms it into data files that sit in your GitHub repository, along with the rest of your content.
- Staticman is free and open source. Check out the documentation [here](https://staticman.net/docs/)
- This Gatsby starter template uses Staticman to handle comments on blog posts, although you could also use it for handling any user generated data such as reviews, form submits, contact me requests, etc.
- The documentation on the official website is a bit outdated, therefore you'll have to do a bit of searching on Google to figure stuff out. A lot of the heavy lifting is already done for you in this Gatsby starter template. Check out the Staticman Integration steps below.

## Staticman integration steps

The integration steps mentioned on the official documentation are very outdated. You can follow the instructions below to get started.

1. Add Staticman to your repository - Go to the [Staticman Github App](https://github.com/apps/staticman-net) and click on configure. Grant Staticman write access to your repository. Whenever a user fills out a comment form, Staticman will automatically create a pull request. If you approve it, the comment will be stored as a `.yml` file in your Github repository. The next time you build your Gatsby site, the comment will be visible. You can automate this by triggering a build everytime Staticman's pull request is merged to your release branch. You can use any CI/CD tool for this purpose.

2. Check the `staticman.yml` file in the root directory of this project. All comments will be saved as a `.yml` file in the `src/data/comments` folder. The `gatsby-transformer-yaml` plugin will then scan the folder, and you will be able to access your comments as the `allCommentsYaml` object in your GraphQL schema.

Note: Please check out this plugin's documentation [here](https://www.gatsbyjs.org/packages/gatsby-transformer-yaml/) to understand all the plugin customization options.

3. Create a form on your website, and ensure that the submit URL points to the Staticman API (refer to the official docs for more details)

## Images

This Gatsby starter template uses `gatsby-source-wordpress` to source content from your Wordpress CMS. While this plugin can apply image transformations on the featured images, it cannot do that for images within the post/page content. What this means is that if you have any image within your Wordpress post/page, it will have to be served from your original wordpress url without any image transforms. Obviously this isn't ideal, and there could be 2 possible solutions for this.

1. Insert images from URL in your Wordpress post/page instead of uploading images to the Wordpress `wp-content/uploads` folder (Maybe a good CDN like AWS Cloudfront, Google Photos etc). By doing so, the images will be served from the CDN, and everything works as expected. You still won't be able to do fluid transforms on these images though.

2. This Gatsby starter template uses (untested) [gatsby-wordpress-inline-images](https://github.com/TylerBarnes/gatsby-wordpress-inline-images) plugin to download images within Wordpress the post/page content, to the local static folder and also lets you applies fluid image transforms on those images. This is because `gatsby-source-wordpress` doesn't process images in blocks of text which means your admin site has to serve the images. However, I haven't fully tested this plugin and you can feel free to comment it out from the `gatsby-config.js` file if you run into any issues.

Note: Please check out this plugin's documentation [here](https://github.com/TylerBarnes/gatsby-wordpress-inline-images) to understand all the plugin customization options.

## Git Hooks using Husky

This Gatsby starter template uses [Husky](https://github.com/typicode/husky) to create Git hooks. Husky can prevent bad git commit, git pushes etc. You can use the husky hooks in the `package.json` file to execute custom scripts and tasks before each git commit and git push. For example, this project uses the `pre-commit` hook to run the lint script, and the `pre-push` hook to create gatsby build and verify that everything works before git push happens to the repository. This is optional though, and you can opt out of it by simply commenting out the `husky` object in the `package.json` file.

## PWA

This Gatsby starter template uses `gatsby-plugin-offline` plugin. If you don't want your site to work offline, simply comment this plugin out from the `gatsby-config.js` file.

## SEO

This Gatsby starter template has some basic SEO capabilities out of the box such as robots.txt file, sitemap.xml file, meta tags defined in `react-helmet` etc.

## Social widgets

This Gatsby starter template uses the [gatsby-plugin-pinterest-twitter-facebook](https://www.gatsbyjs.org/packages/gatsby-plugin-pinterest-twitter-facebook/) plugin to load the following social media widgets. No API tokens needed for any of these widgets, and no complicated setup procedure. Just plug and play.

## Reading progress bar

This Gatsby starter template displays a reading progress bar at the top of each page. Feel free to tweak it, hide or show it on certain pages, or remove it altogether if you don't like it.

- ###### Pinterest
    - Display the `Pin it` button while hovering over any image on your website.

- ###### Twitter
    - Display the Twitter follow button, and the Twitter timeline anywhere on your website.

- ###### Facebook
    - Display the Facebook like button, and the Facebook timeline anywhere on your website.

Note: Please check out this plugin's documentation [here](https://www.gatsbyjs.org/packages/gatsby-plugin-pinterest-twitter-facebook/) to understand all the plugin customization options.

## Instagram

This Gatsby starter template uses the [gatsby-source-instagram](https://www.gatsbyjs.org/packages/gatsby-source-instagram/) plugin to display upto 12 most recent posts of any Instagram account.

Note: Please check out this plugin's documentation [here](https://www.gatsbyjs.org/packages/gatsby-source-instagram/) to understand all the plugin customization options.

## Developing

Once you have defined the mandatory environment variables mentioned above, and have a Wordpress site ready (either on your local machine or a pre-existing live website), follow these instructions to use this Gatsby starter template

1.  Install dependencies

    `yarn` or `npm install`

2.  Run the development server

    `yarn start` or `npm run start`

    Note:

    - This project uses Typescript, so create new files components with the `.tsx` or `.ts` extension instead of `.jsx` or `.js`
    - This project uses SASS to write stylesheets. You can create new stylesheets with `.scss` extension and import them into any React component, it will automatically get transpiled into CSS.

## Issues

If you face any issues while working with this Gatsby starter template, feel free to create a new issue [here](https://github.com/sagar7993/gatsby-wordpress-typescript-scss-blog/issues). Please check if there's any existing similar issue already created before creating a new one.

## Contribute

Fork this repo and make a PR.

## License

This project is licensed under the [MIT License](https://github.com/sagar7993/gatsby-wordpress-typescript-scss-blog/blob/master/LICENSE) - see the LICENCE.md file for details

gha_language: HTML


text:
# SportHub

This project has 2 folders. One to server and another to the client.  Therefore, to run you will need two terminals to run both projects at same time.

## Client setup

* open the terminal

* type

```

cd client

```

* use the command

```
npm install

npm run serve

```

The prompt will display the access URL.

## Server setup

* open the terminal

* type

```

cd server

```

* use the command

```
npm install

nodemon node server.js

```

The prompt will display the access URL.

repository: andradediego/SportHub

branch_name: refs/heads/main

repo_name: andradediego/SportHub


text:
@snap[midpoint span-100]

# Heap

### Implementation

@snapend

---

## Learning Goals

By the end of this module, students will be able to...

* **Describe** the algorithm to insert a record into a max-heap
* **Describe** the algorithm to remove the highest-priority record from a max-heap

---

## Design Review

Store tree nodes as elements in an **array**

Parent is at `\(\left \lfloor{ \frac{i}{2} } \right \rfloor \)`, children are at `\(2 * i\)` and `\(2 * i + 1\)`

Keep the tree **perfectly balanced**

Bottom layer fills left-to-right

Maintain the **max-heap property**:

Every node has priority less than or equal to that of its parent

---

## Insert Strategy

To keep the heap perfectly balanced, insert will always add a slot **at the end of the array**

![](heaps/images/heap-insert-plan.png)

Inserting the new record here might violate the **max-heap property**

---

## Float Up

Our newly inserted record might have a higher priority than its parent

Idea: "float" the record up the tree until we find the right spot

Repeatedly swap with the parent

---

## Float Up

![](heaps/images/heap-float-up.png)

---

## Float Pseudocode

```ruby zoom-12
def float(i)
  # Note: i and p are indices (not records)
  p = parent(i)
  while inBounds(p) && priority(p) < priority(i)
    swap(i, p)

    i = p
    p = parent(i)
```

---

## Float Induction

**Question:** If the new record is larger than its parent, could it be smaller than its sibling?

![](heaps/images/heap-float-contradiction.png)

**No!**

By induction, we can assume that the heap was valid before we started

---

## Remove-Max Strategy

We want to remove the element at the front

The root has the highest priority

We want to remove the slot from the back

This keeps the tree balanced

![](heaps/images/heap-remove-strategy.png)

Idea: swap the root with the last element, reduce the count, then "sink" the new root down until the max-heap property holds

---

## Sink Down

![](heaps/images/heap-sink.png)

---

## Sink Pseudocode

```ruby
def sink(i)
  # Note: i, l, r and max are all indices (not records)
  finished = false
  until finished
    l = left(i)
    r = right(i)

    max = i
    if inBounds(l) && priority(l) > priority(max)
      max = l
    if inBounds(r) && priority(r) > priority(max)
      max = r

    if max == i
      finished = true
    else
      swap(i, max)
      i = max
```

---

## Summary

To stay balanced, a heap must always **add and remove slots at the end** of the current storage

Even if the record to add or remove doesn't go at the end

We described **float** and **sink** subroutines to help us

**Insert:** add the record at the end, then "float" it up to the right spot by repeatedly swapping with its parent

**Remove-Max:** swap root with the last element, then "sink" the new root down to the right spot by repeatedly swapping with its largest child


text:
# ServiceRouteTables

```text
azure-11/Item/Networking/ServiceRouteTables
```

```text
include('azure-11/Item/Networking/ServiceRouteTables')
```

| Illustration | ServiceRouteTables | ServiceRouteTablesCard | ServiceRouteTablesGroup |
| :---: | :---: | :---: | :---: |
| ![illustration for Illustration](../../../azure-11/Item/Networking/ServiceRouteTables.png) | ![illustration for ServiceRouteTables](../../../azure-11/Item/Networking/ServiceRouteTables.Local.png) | ![illustration for ServiceRouteTablesCard](../../../azure-11/Item/Networking/ServiceRouteTablesCard.Local.png) | ![illustration for ServiceRouteTablesGroup](../../../azure-11/Item/Networking/ServiceRouteTablesGroup.Local.png) |

## Sprites
The item provides the following sriptes:

- `<$ServiceRouteTablesXs>`
- `<$ServiceRouteTablesSm>`
- `<$ServiceRouteTablesMd>`
- `<$ServiceRouteTablesLg>`

## ServiceRouteTables

### Load remotely
```plantuml
@startuml
' configures the library
!global $LIB_BASE_LOCATION="https://raw.githubusercontent.com/tmorin/plantuml-libs/master/distribution"

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('azure-11/bootstrap')

' loads the Item which embeds the element ServiceRouteTables
include('azure-11/Item/Networking/ServiceRouteTables')

' renders the element
ServiceRouteTables('ServiceRouteTables', 'Service Route Tables', 'an optional tech label', 'an optional description')
@enduml
```

### Load locally
```plantuml
@startuml
' configures the library
!global $INCLUSION_MODE="local"
!global $LIB_BASE_LOCATION="../../.."

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('azure-11/bootstrap')

' loads the Item which embeds the element ServiceRouteTables
include('azure-11/Item/Networking/ServiceRouteTables')

' renders the element
ServiceRouteTables('ServiceRouteTables', 'Service Route Tables', 'an optional tech label', 'an optional description')
@enduml
```

## ServiceRouteTablesCard

### Load remotely
```plantuml
@startuml
' configures the library
!global $LIB_BASE_LOCATION="https://raw.githubusercontent.com/tmorin/plantuml-libs/master/distribution"

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('azure-11/bootstrap')

' loads the Item which embeds the element ServiceRouteTablesCard
include('azure-11/Item/Networking/ServiceRouteTables')

' renders the element
ServiceRouteTablesCard('ServiceRouteTablesCard', 'Service Route Tables Card', 'an optional description')
@enduml
```

### Load locally
```plantuml
@startuml
' configures the library
!global $INCLUSION_MODE="local"
!global $LIB_BASE_LOCATION="../../.."

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('azure-11/bootstrap')

' loads the Item which embeds the element ServiceRouteTablesCard
include('azure-11/Item/Networking/ServiceRouteTables')

' renders the element
ServiceRouteTablesCard('ServiceRouteTablesCard', 'Service Route Tables Card', 'an optional description')
@enduml
```

## ServiceRouteTablesGroup

### Load remotely
```plantuml
@startuml
' configures the library
!global $LIB_BASE_LOCATION="https://raw.githubusercontent.com/tmorin/plantuml-libs/master/distribution"

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('azure-11/bootstrap')

' loads the Item which embeds the element ServiceRouteTablesGroup
include('azure-11/Item/Networking/ServiceRouteTables')

' renders the element
ServiceRouteTablesGroup('ServiceRouteTablesGroup', 'Service Route Tables Group', 'an optional tech label') {
    note as note
        the content of the group
    end note
}
@enduml
```

### Load locally
```plantuml
@startuml
' configures the library
!global $INCLUSION_MODE="local"
!global $LIB_BASE_LOCATION="../../.."

' loads the library's bootstrap
!include $LIB_BASE_LOCATION/bootstrap.puml

' loads the package bootstrap
include('azure-11/bootstrap')

' loads the Item which embeds the element ServiceRouteTablesGroup
include('azure-11/Item/Networking/ServiceRouteTables')

' renders the element
ServiceRouteTablesGroup('ServiceRouteTablesGroup', 'Service Route Tables Group', 'an optional tech label') {
    note as note
        the content of the group
    end note
}
@enduml
```

repository: tmorin/plantuml-libs

gha_language: TypeScript

repo_name: tmorin/plantuml-libs


text:
All the pictures/icons used in the different VR environments can be found in the self-explanatory subdirectories.

# Sources

The following list contains the sources of the used assets. There is made a subdivision between Blender files and the pictures used as textures for the different planets.

* sky\

	* [nature.jpg](https://www.flickr.com/photos/pedroscreamerovsky/6839824524/in/faves-26213016@N05/)

* solarsystem\

	* [Earth.jpg](http://planetary-science.org/wp-content/uploads/2013/06/globe_west_2048.jpg)
	* [Jupiter.jpg](http://planetary-science.org/wp-content/uploads/2013/06/Jupiter.jpg)
	* [Mars.jpg](https://timedotcom.files.wordpress.com/2018/06/mars.jpg?quality=85)
	* [Mercury.jpg](http://planetary-science.org/wp-content/uploads/2013/06/mercury-global-mosaic.png)
	* [Neptune.jpg](http://planetary-science.org/wp-content/uploads/2013/06/Neptune_006.jpg)
	* [Saturn.jpg](http://www.unmuseum.org/7wonders/saturn_planet.jpg)
	* [stars_milky_way.jpg](https://www.solarsystemscope.com/textures/download/2k_saturn_ring_alpha.pnghttps://www.solarsystemscope.com/textures/download/2k_stars_milky_way.jpg)
	* [Sun.jpg](https://en.wikipedia.org/wiki/Sun#/media/File:The_Sun_by_the_Atmospheric_Imaging_Assembly_of_NASA%27s_Solar_Dynamics_Observatory_-_20100819.jpg)
	* [Uranus.jpg](https://en.wikipedia.org/wiki/Uranus#/media/File:Uranus2.jpg)
	* [Venus.jpg](http://planetary-science.org/wp-content/uploads/2013/06/Venus_globe.jpg)

 * student\

 	* [confused.svg](https://www.flaticon.com/free-icon/dizzy_599642)
 	* [grid.png](https://img.gs/bbdkhfbzkk/stretch/https://i.imgur.com/25P1geh.png)
 	* [hand.svg](https://www.flaticon.com/free-icon/select_889816#term=hand%20select&page=1&position=10)
 	* [rabbit.svg](https://www.flaticon.com/free-icon/rabbit_1303575)
 	* [turtle.svg](https://www.flaticon.com/free-icon/turtle_616651)

repository: ssduracell/ieee-classroom

repo_name: ssduracell/ieee-classroom


text:
## 21.0.0-wip

**Breaking changes**

- Allow clients to specify where to find the package config. - [#2203](https://github.com/dart-lang/webdev/pull/2203).
- Allow clients to specify a way to convert absolute paths to g3-relative paths. - [#2200](https://github.com/dart-lang/webdev/pull/2200)

## 20.0.1

- Update file dependency to `>=6.0.0 < 8.0.0` - [#123260](https://github.com/flutter/flutter/pull/123260#issuecomment-1674001623).

## 20.0.0

- Require clients to specify the `basePath` on `AssetReader`. - [#2160](https://github.com/dart-lang/webdev/pull/2160)
- Update SDK constraint to `>=3.1.0-254.0.dev <4.0.0`. - [#2169](https://github.com/dart-lang/webdev/pull/2169)
- Require min `build_web_compilers` version `4.0.4` - [#2171](https://github.com/dart-lang/webdev/pull/2171)
- Switch to using new debugging API from DDC to support new type system. - [#2159](https://github.com/dart-lang/webdev/pull/2159)
- Fix Flutter crash when calling `resume` when app is not paused. - [#2188](https://github.com/dart-lang/webdev/pull/2188)
- Update file dependency to `7.0.0`.

## 19.0.2

- Fix Flutter crash due to potential null value in `setUpChromeConsoleListener`. - [#2162](https://github.com/dart-lang/webdev/pull/2162)

## 19.0.1

- Do not show async frame errors on evaluation. - [#2073](https://github.com/dart-lang/webdev/pull/2073)
- Refactor code for presenting record instances. - [#2074](https://github.com/dart-lang/webdev/pull/2074)
- Display record types concisely. - [#2070](https://github.com/dart-lang/webdev/pull/2070)
- Display type objects concisely. - [#2103](https://github.com/dart-lang/webdev/pull/2103)
- Support using scope in `ChromeProxyService.evaluateInFrame`. - [#2122](https://github.com/dart-lang/webdev/pull/2122)
- Check for new events more often in batched stream. - [#2123](https://github.com/dart-lang/webdev/pull/2123)
- Map Chrome error on `resume` to the same error returned by the Dart VM. - [#2133](https://github.com/dart-lang/webdev/issues/2133)
- VM service API methods throw type `RPCError`, same as the Dart VM. - [#2144](https://github.com/dart-lang/webdev/pull/2144)

## 19.0.0

- Allow clients to specify the connected app's entrypoint file. - [#2047](https://github.com/dart-lang/webdev/pull/2047)
- Don't include non-instantiated variables in stack frame data. - [#2061](https://github.com/dart-lang/webdev/pull/2061)
- Fix `getObject` failure on record class - [2063](https://github.com/dart-lang/webdev/pull/2063)

## 18.0.2

- Support new DDC temp names for patterns. - [#2042](https://github.com/dart-lang/webdev/pull/2042)
- Make debugger find next dart location when stepping. -[#2043](https://github.com/dart-lang/webdev/pull/2043)

## 18.0.1

- Fix failure to map JS exceptions to dart. - [#2004](https://github.com/dart-lang/webdev/pull/2004)
- Fix for listening to custom streams. - [#2011](https://github.com/dart-lang/webdev/pull/2011)
- Handle unexpected extension debugger disconnect events without crashing the app - [#2021](https://github.com/dart-lang/webdev/pull/2021)
- Support `Set` inspection. - [#2024](https://github.com/dart-lang/webdev/pull/2024)

## 18.0.0

- Cleanup `getObject` code for lists and maps.
  - Now works with offset `0` and `null` count.
  - Fix failures on edge cases.
- Support records:
  - Update SDK constraint to `>=3.0.0-188.0.dev <4.0.0`.
  - Update `package:vm_service` constraint to `>=10.1.2 <12.0.0`.
  - Update `package:dds` constraint to `^2.7.1`.
  - Fill `BoundField.name` for records.
  - Display records as a container of fields.
- Remove test-only code from `sdk_configuration.dart`.
- Move shared test-only code to a new `test_common` package.
- Convert unnecessary async code to sync.
- Allow empty scopes in expression evaluation in a frame.

**Breaking changes**

- Require `sdkConfigurationProvider` in `ExpressionCompilerService`
  constructor.
- Change DWDS parameter `isFlutterApp` from type `bool?` to type
  `Future<bool> Function()?`.

## 17.0.0

- Include debug information in the event sent from the injected client to the
  Dart Debug Extension notifying that the Dart app is ready.
- Fix null cast error on expression evaluations after dwds fails to find class
  metadata.
- Include the entire exception description up to the stacktrace in
  `mapExceptionStackTrace`.
- Allow enabling experiments in the expression compiler service.
- Pre-warm expression compiler cache to speed up Flutter Inspector loading.
- Display full error on failure to start DDS.
- Fix crash on processing DevTools event when starting DevTools from DevTools
  uri.
- Prepare or Dart 3 alpha breaking changes:
  - Move weak null safety tests to special branch of `build_web_compilers`.
  - Do not pass `--(no)-sound-null-safety` flag to build daemon.
- Add back `ChromeProxyService.setExceptionPauseMode()` without override.
- Make hot restart atomic to prevent races on simultaneous execution.
- Return error on expression evaluation if expression evaluator stopped.
- Update SDK constraint to `>=3.0.0-134.0.dev <4.0.0`.
- Update `package:vm_service` constraint to `>=10.1.0 <12.0.0`.
- Fix expression compiler throwing when weak SDK summary is not found.

**Breaking changes**

- Include an optional param to `Dwds.start` to indicate whether it is running
  internally or externally.
- Include an optional param to `Dwds.start` to indicate whether it a Flutter
  app or not.
- Remove `sdkConfigurationProvider` parameter from `Dwds.start`.
- Remove deprecated `ChromeProxyService.setExceptionPauseMode()`.
- Support dart 3.0-alpha breaking changes:
  - Generate missing SDK assets for tests.
  - Enable frontend server null safe tests.
  - Update `build_web_compilers` constraint to `^4.0.0`.
  - Update `build_runner` constraint to `^2.4.0`.
  - Support changes in the SDK layout for dart 3.0.

## 16.0.1

- Allow the following API to return `null` and add error handling:
  - `LoadStrategy.serverPathForModule`
  - `LoadStrategy.sourceMapPathForModule`
- Expression evaluation performance improvement:
  - Batch `ChromeProxyService.evaluate()` requests that are close in time and
    are executed in the same library and scope.
- Update `package:file` version to `6.13` or greater to handle
  https://github.com/dart-lang/sdk/issues/49647.

## 16.0.0

- Fix a hang and report errors on hot reload exceptions from the injected
  client.
- Remove `AppInspector.evaluate` code that has been replaced by expression
  evaluation using a compiler in all scenarios.
- Fix a bug where evaluation would fail with more than one parameter in the
  scope.
- Remove showing un-captured values from the stack during evaluation.
- Refactor code to break most circular dependencies between files.
- Migrate `package:dwds` to null safety.
- Make `ChromeProxyService.getStack` wait for the debugger to perform initial
  resume operation. This avoids race conditions on isolate start.
- Make server paths match directory structure
  - Allows correct relative source map paths resolution.
  - Add `PackageUriMapper` class to allow mapping uris to server paths.
- Update the min SDK constraint to 2.18.0.
- Make DartUri work for `google3:` uris.

**Breaking changes**

- Remove no longer used `ExpressionCompilerService.handler`.
- Remove `assetHandler` parameter from `ExpressionCompilerService` constructor.
- Add `packageUriMapper` parameter to the constructor of
  `FrontendServerRequireStrategyProvider`.

## 15.0.0

- Port some `dwds` files to null safety.
- Fix failing `frontend_server_evaluate` tests.
- Prevent `flutter_tools` crash when the Dart execution context cannot be found.
- Update method signature of `lookupResolvedPackageUris`.

## 14.0.3

- Make data types null safe.
- Update `package:vm_service` to 8.3.0.
- Convert JavaScript stack traces in uncaught exceptions to Dart stack traces.
- Fix failure to set breakpoints on windows with a base change in index.html.
- Add the `setIsolatePauseMode` method to Chrome Proxy Service.
- Batch extension `Debugger.scriptParsed` events and send batches every 1000ms
  to the server.
- Move `batched_stream.dart` into shared utilities.
- Update the method signature for `lookupResolvedPackageUris`.

## 14.0.2

- Update the min SDK constraint to 2.17.0.

## 14.0.1

- Add `libraryFilters` optional parameter to the vm service implementation of
  `getSourceReport`.
- Update temp variable detection heuristics so internal JS type objects do not
  show in the debugger.

## 14.0.0

- Add column information to breakpoints to allow precise breakpoint placement.
- Split SDK validation methods to allow validation of separate components.
- Remove dependency on `package:_fe_analyzer_shared`. Note: this removes current
  incomplete support for resolving `dart:` uris.
- Fix issues discovered when using flutter tools with web server device:
  - Remove `dart:web_sql` from the list of SDK libraries as it is no longer
    used.
  - Fix crash when using flutter tools with web server device.
  - Remove clearing all scripts on page load for extension debugger.
- Fix breakpoints not hitting after changing a base in index.html.
- Find best locations for call frames, breakpoints, or expression evaluation.
- Close the SSE connection when a DebugExtension.detached event is received.
- Fix issues discovered when using legacy module system, debug extension, and
  JIT modules:
  - Improve step-into times by not stepping into library loading code.
  - Fix incorrect skip lists due to unsorted locations.
  - Fix memory leak in extension debugger by removing stale script IDs.
  - Allow mapping JS locations to Dart locations matching other JS lines, to
    match the behavior of Chrome DevTools.
  - Fix expression evaluation failure if debugger is stopped in the middle of a
    variable definition.

**Breaking changes:**

- Add `basePath` parameter to `FrontendServerRequireStrategy`.
- Add `loadLibrariesModule` getter to `LoadStrategy` interface.

## 13.1.0

- Update \_fe_analyzer_shared to version ^38.0.0.

## 13.0.0

- Change wording of paused overlay from "Paused in Dart DevTools" to "Paused"
- Allow sending back the Dart DevTools URL from DWDS instead of launching Dart
  DevTools, to support embedding Dart DevTools in Chrome DevTools.
- Temporarily disable the paused in debugger overlay.
- Add `SdkConfiguration` and `SdkConfigurationProvider` classes to allow for
  lazily created SDK configurations.
- Fix an issue in reporting DevTools stats where the DevTools load time was not
  always recorded.
- Add an `ide` query parameter to the Dart DevTools URL for analytics.
- Fix a race where injected client crashed on events send just before hot
  restart.
- Remove verbose printing on receiving DevTools events.
- Update `vm_service` version to `^8.2.0`.
- Migrate .packages to package_config.json.
- Update error message on expression evaluation using unloaded libraries.
- Add `screen` field to the `DebuggerReady` event.
- Report `DebuggerReady` events for DevTools embedded into Chrome Devtools.
- Fix missing `CallFrame.url` after update to Chrome 100.

**Breaking changes:**

- `Dwds.start` and `ExpressionCompilerService` now take
  `sdkConfigurationProvider` argument instead of separate SDK-related file
  paths.

## 12.1.0

- Update \_fe_analyzer_shared to version ^34.0.0.

## 12.0.0

- Implement `lookupResolvedPackageUris` and `lookupPackageUris` vm service API.
- Update `vm_service` version to `^8.1.0`.
- Make `ExpressionCompilerService` infer location of `libraries.json` from
  `sdkDir` parameter.
- Show an alert in the Dart Debug Extension for a multi-app scenario.
- Fix a bug where `dartEmitDebugEvents` was set as a `String` instead of `bool`
  in the injected client.
- Emit a warning instead of crashing on missing `libraries.json`.
- Remove dead code for reading `'dart.developer.registerExtension'` and
  `'dart.developer.postEvent'` events from the chrome console. These messages
  haven't been written to the console since dwds v11.1.0 and Dart SDK v2.14.0.
- Batch debug events sent from injected client to dwds to relieve network load.
- Update `_fe_analyzer_shared` version to `33.0.0`
- Update the Dart minimum SDK to `>=2.16.0`.

**Breaking changes:**

- Add `sdkDir` and `librariesPath` arguments to `Dwds.start` to help file
  resolution for sdk uris.
- Add `emitDebugEvents` argument to `Dwds.start` to suppress emitting debug
  events from the injected client.
- Replace `sdkRoot` parameter by `sdkDir` in `ExpressionCompilerService`.
- Adds an additional parameter to launch Dart DevTools in the same window as the
  connected Dart app.

## 11.5.1

- Update SDK constraint to `>=2.15.0 <3.0.0`.

## 11.5.0

- Support hot restart in a multi-app scenario with legacy modules.

  - Rename `$dartHotRestart` in the injected client to `$dartHotRestartDwds`.
  - Make `$dartHotRestartDwds` take a `runId`.
  - No change in behavior for single applications.
  - For a multi-app scenario using legacy modules, this will make all sub-apps
    with the same `runId` restart at the same time once.

  Note that multi-app scenario is currently only supported for legacy modules,
  used by DDR, and is not yet supported for amd modules that are used by flutter
  tools and webdev.

- Fix chrome detection in iPhone emulation mode in chrome or edge browsers.

- Reliably find unused port for extension backend http service.

- Ignore offset / count parameters in getObject if the object has no length.

- Include static member information for classes.

## 11.4.0

- Fix duplicated scripts returned by `VmService.getScripts` API.
- Handle and log http request serving errors.
- Encode extension url asynchronously.
- Use default constant port for debug service.
  - If we fail binding to the port, fall back to previous strategy of finding
    unbound ports.
- Add metrics measuring
  - DevTools Initial Page Load time
  - Various VM API
  - Hot restart
  - Http request handling exceptions
- Only return scripts included in the library with Library object.
- Add `ext.dwds.sendEvent` service extension to dwds so other tools can send
  events to the debugger. Event format:
  ```
  {
    'type': '<event type>',
    'payload': {
      'screen: '<screen name>',
      'action: '<action name>'
    }
  }
  ```
  Currently supported event values:
  ```
  {
    'type: 'DevtoolsEvent',
    'payload': {
      'screen': 'debugger',
      'action': 'pageReady'
    }
  }
  ```

## 11.3.0

- Update SDK constraint to `>=2.14.0 <3.0.0`
- Depend on `vm_service` version `7.3.0`.

## 11.2.3

- Fix race causing intermittent `Aww, snap` errors on starting debugger with
  multiple breakpoints in source.
- Fix needing chrome to be focus in order to wait for the isolate to exit on hot
  restart.

## 11.2.2

- Depend on `dds` version `2.1.1`.
- Depend on `vm_service` version `7.2.0`.

## 11.2.1

- Recover from used port errors when starting debug service.
- Update min SDK constraint to `2.13.0`.

## 11.2.0

- Throw `SentinelException` instead of `RPCError` on vm service API on
  unrecognized isolate.
- Throw `RPCError` in `getStack` if the application is not paused.
- Recognize `dart:ui` library when debugging flutter apps.
- Fix hang on hot restart when the application has a breakpoint.
- Fix out of memory issue during sending debug event notifications.

## 11.1.2

- Return empty library from `ChromeProxyService.getObject` for libraries present
  in metadata but not loaded at runtime.
- Log failures to load kernel during expression evaluation.
- Show lowered final fields using their original dart names.
- Limit simultaneous connections to asset server to prevent broken sockets.
- Fix hangs in hot restart.
- Initial support for passing scope to `ChromeProxyService.evaluate`.
- Require `build_web_compilers` version `3.0.0` so current version of dwds could
  be used with SDK stable `2.13.x` versions.

## 11.1.1

- Update versions of `package:sse`, `package:vm_service`, `package:dds`.

## 11.1.0

- Add global functions to the injected client for `dart.developer.postEvent` and
  `dart.developer.registerExtension`.
- Register new service extension `ext.dwds.emitEvent` so clients can emit
  events. This is intended to be used for analytics.

## 11.0.2

- Implement `_flutter.listViews` extension method in dwds vm client.

## 11.0.1

- Make adding and removing breakpoints match VM behavior:
  - Allow adding existing breakpoints.
  - Throw `RPCError` when removing non-existent breakpoints.

## 11.0.0

- Do not send `kServiceExtensionAdded` events to subscribers on the terminating
  isolate during hot restart.
- Support `vm_service` version `6.2.0`.
- Fix missing sdk libraries in `getObject()` calls.
- Fix incorrect `rootLib` returned by `ChromeProxyService`.
- Fix not working breakpoints in library part files.
- Fix data race in calculating locations for a module.
- Fix uninitialized isolate after hot restart.
- Fix intermittent failure caused by evaluation not waiting for dependencies to
  be updated.
- The injected client now posts a top level event when the Dart application is
  loaded. This event is intended to be consumed by the Dart Debug Extension.

**Breaking changes:**

- `Dwds.start` no longer supports automatically injecting a devtools server. A
  `devtoolsLauncher` callback must be provided to support launching devtools.

## 10.0.1

- Support `webkit_inspection_protocol` version `^1.0.0`.

## 10.0.0

- Support `VMService.evaluate` using expression compiler.
- Update min sdk constraint to `>=2.13.0-144.0.dev`.
- Throw `RPCError` on evaluation if the program is not paused.
- Record `ErrorRef` returned by evaluation in analytics.

**Breaking changes:**

- Change `ExpressionCompiler.initialize` method to include module format.
- Add `LoadStrategy.moduleFormat` to be used for communicating current module
  format to the expression compiler.

## 9.1.0

- Support authentication endpoint for the Dart Debug Extension.
- Support using WebSockets for the injected client by passing
  `useSseForInjectedClient: false` to `Dwds.start()`. Unlike SSE, WebSockets do
  not currently support keepAlives here (beyond the standard WebSocket pings to
  keep the socket alive).

## 9.0.0

- Fix an issue where relative worker paths provided to the
  `ExpressionCompilerService` would cause a crash.
- Fix an issue where the injected client connection could be lost while the
  application is paused.
- Support keep-alive for debug service connections.
- Depend on the latest `package:sse`.
- Filter out DDC temporary variables from the variable inspection view.
- Add `DwdsEvent`s around stepping and evaluation.
- Send an event to the Dart Debug Extension that contains VM service protocol
  URI.
- Depend on `package:vm_service` version `6.1.0+1`.
- Update the `keepAlive` configs to prevent accidental reuse of a connection
  after stopping a debug session.
- Support disabling the launching of Dart DevTools through `Alt + d` with
  `enableDevtoolsLaunch`.
- Opt all dart files out of null safety for min SDK constraint update.

**Breaking changes:**

- `LoadStrategy`s now require a `moduleInfoForEntrypoint`.

## 8.0.3

- Fix an issue where failed hot restarts would hang indefinitely.

## 8.0.2

- Change `ExpressionCompiler` to accept `FutureOr<int>` port configuration.
- Depend on `package:vm_service` version `6.0.1-nullsafety.1`.

## 8.0.1

- Support null safe versions of `package:crypto`, `package:uuid` and
  `package:webdriver`.

## 8.0.0

- Improve logging around execution contexts.
- Remove the expression compilation dependency update from the create isolate
  critical path.
- Expose new event stream for future use with analytics.
- Update `ExpressionCompiler` to include new `initialize` method which has a
  parameter for the null safety mode.
- Update `ExpressionCompilerService` to change how it is instantiated and
  implement the new `initialize` method.
- Provide summary module paths to the expression compiler
- Depend on `package:vm_service` version `6.0.1-nullsafety.0`.

**Breaking changes:**

- Change `ExpressionCompiler.updateDependencies` method to include module
  summary paths

## 7.1.1

- Properly handle `requireJS` errors during hot restarts.
- Fix an issue where Dart frame computation could result in a stack overflow for
  highly nested calls.
- Fix an issue where calling add breakpoint in quick succession would corrupt
  the internal state.
- Fix expression evaluation failure inside blocks.
- Now log the encoded URI of the debug service to both the terminal and
  application console.
- No longer blacklist the Dart SDK as the `skipLists` support serves the same
  purpose.
- Fix an issue where running webdev with expression evaluation enabled would
  fail to find `libraries.json` file and emit severe error.

## 7.1.0

- Fix a potential null issue while resuming.
- Depend on the latest `package:vm_service`.
- Fix crash in expression evaluation on null isolate.
- Fix incorrect file name detection for full kernel files.
- Add `ExpressionCompilerService.startWithPlatform` API to enable running
  expression compiler worker from a given location.
- Support Chrome `skipLists` to improve stepping performance.
- Export `AbsoluteImportUriException`.
- Depend on the latest `package:vm_service` which supports a new `limit`
  parameter to `getStack`.

## 7.0.2

- Depend on the latest `package:sse`.
- Add more verbose logging around `hotRestart`, `fullReload` and entrypoint
  injection.

## 7.0.1

- Fix an issue where we attempted to find locations for the special
  `dart_library` module.

## 7.0.0

- Add support for the Dart Development Service (DDS). Introduces 'single client
  mode', which prevents additional direct connections to DWDS when DDS is
  connected.
- Update metadata reader version to `2.0.0`. Support reading metadata versions
  `2.0.0` and `1.0.0`.
- Support custom hosts and HTTPs traffic in a `ProxyServerAssetReader`.
- Remove heuristics from require strategies and use metadata to look up module
  paths.
  - Fix issue where upgrading `build_web_compilers` would cause missing module
    assets (JavaScript code and source maps).
- Fix issue where open http connections prevent the process for exiting.
- Add `ExpressionCompilationService` class that runs ddc in worker mode to
  support expression evaluation for clients that use build systems to build the
  code.
- Require at least `devtools` and `devtools_server` version `0.9.2`.
- Require at least `dds` version `1.4.1`.
- Require at least `build_web_compilers` version `2.12.0`.
- Update min sdk constraint to `>=2.10.0`.
- Update `MetadataProvider` to throw an `AbsoluteImportUriException` when
  absolute file paths are used in an import uri.

**Breaking changes:**

- Change `ExpressionCompiler` to require a new `updateDependencies` method.
- Update a number of `LoadStrategy` APIs to remove heuristics and rely on the
  `MetadataProvider`.
- No longer require a `LogWriter` and corresponding `verbose` argument but
  instead properly use `package:logger`.
- `FrontendServerRequireStrategyProvider` now requires a `digestProvider`.

## 6.0.0

- Depend on the latest `package:devtools` and `package:devtools_server`.
- Support using WebSockets for the debug backend by passing
  `useSseForDebugBackend: false` to `Dwds.start()`
- Ensure we run main on a hot restart request even if no modules were updated.
- Allow reading metadata generated by `dev_compiler` from file to supply module
  information to `Dwds`.
- Hide JavaScript type errors when hovering over text in the debugger.
- Fix an issue where reusing a connection could cause a null error.
- Improve the heuristic which filters JS scopes for debugging needs.

**Breaking Changes:**

- Require access to the `.ddc_merged_metadata` file.
- Remove deprecated parameter `restoreBreakpoints` as breakpoints are now set by
  regex URL and Chrome automatically reestablishes them.

## 5.0.0

- Have unimplemented VM service protocol methods return the RPC error
  'MethodNotFound' / `-32601`.
- Fix an issue where the application main function was called before a hot
  restart completed.
- Breaking change `AssetReader` now requires a `metadataContents`
  implementation.

## 4.0.1

- Fixed issue where `getSupportedProtocols` would return the wrong protocol.

## 4.0.0

- Pin the `package:vm_service` version to prevent unintended breaks.

## 3.1.3

- Fix an issue where the injected client served under `https` assumed the
  corresponding SSE handler was also under `https`.

## 3.1.2

- Gracefully handle multiple injected clients on a single page.
- Update to the latest `package:vm_service` and use more RPCError error codes on
  call failures.
- Update the `require_restarter` to rerun main after a hot restart to align with
  the legacy strategy. We therefore no longer send a `RunRequest` after a hot
  restart.
- Compute only the required top frame for a paused event.
- Change `streamListen` to return an `RPCError` / error code `-32601` for
  streams that are not handled.
- Populate information about async Dart frames.
- Populate the `exception` field in debugger pause event when we break as a
  result of an exception.
- Prompt users to install the Dart Debug Extension if local debugging does not
  work.
- Allow for the injected client to run with CSP enforced.
- Implement the `getMemoryUsage()` call.
- Fix an issue where the injected client could cause a mixed content error.

## 3.1.1

- Change the reported names for isolates to be more terse.
- Implemented the 'PossibleBreakpoints' report kind for `getSourceReport()`.
- Change the returned errors for the unimplemented `getClassList` and
  `reloadSources` methods to -32601 ('method does not exist / is not
  available').
- Do not include native JavaScript objects on stack returned from the debugger.

## 3.1.0

- Support Chromium based Edge.
- Depend on latest `package:sse` version `3.5.0`.
- Bypass connection keep-alives when shutting down to avoid delaying process
  shutdown.
- Fix an issue where the isolate would incorrectly be destroyed after connection
  reuse.

## 3.0.3

- Support the latest version of `package:shelf_packages_handler`.
- Throw a more useful error if during a hot restart there is no active isolate.
- Fix a race condition in which loading module metadata could cause a crash.
- Correct scope detection for expression evaluation
- Silence verbose and recoverable exceptions during expression evaluation
- Return errors from ChromeProxyService.evaluateInFrame as ErrorRef so they are
  not shown when hovering over source in the IDE

## 3.0.2

- Fix an issue in JS to Dart location translation in `ExpressionEvaluator`. JS
  location returned from Chrome is 0-based, adjusted to 1-based.

## 3.0.1

- Drop dependency on `package_resolver` and use `package_config` instead.
- Bump min sdk constraint to `>=2.7.0`.

## 3.0.0

- Depend on the latest `package:vm_service` version `4.0.0`.

**Breaking Changes:**

- Delegate to the `LoadStrategy` for module information:
  - moduleId -> serverPath
  - serverPath -> moduleId

## 2.0.1

- Fix an issue where we would return prematurely during a `hotRestart`.
- Fix an issue where we would incorrectly fail if a `hotRestart` had to fall
  back to a full reload.

## 2.0.0

- Depend on the latest `package:vm_service` version `3.0.0+1`.

**Breaking Changes:**

- Now require a `LoadStrategy` to `Dwds.start`. This package defines two
  compatible load strategies, `RequireStrategy` and \`LegacyStrategy.
- `Dwds.start` function signature has been changed to accept one more parameter
  of new interface type `ExpressionCompiler` to support expression evaluation
- Provide an implementation of the `RequireStrategy` suitable for use with
  `package:build_runner`.
- Simplify hot reload logic and no longer provide module level hooks.

## 1.0.1

- Make the `root` optional for the `ProxyServerAssetReader`.

## 1.0.0

- Fix an issue where files imported with relative paths containing `../` may
  fail to resolve breakpoint locations.
- Remove dependency on `package:build_daemon`.
- Add `FrontendServerAssetReader` for use with Frontend Server builds.
- Depend on latest `package:sse` for handling client reconnects transparently on
  the server.
- Fix an issue where a failure to initiate debugging through the Dart Debug
  Extension would cause your development server to crash.
- Fix an issue where trying to launch DevTools in a non-debug enabled Chrome
  instance could crash your development server.

**Breaking Changes:**

- No longer use the `BuildResult` abstraction from `package:build_daemon` but
  require a similar abstraction provided by this package.
- `AssetHandler` has been renamed to `AssetReader` and no longer provides a
  generic resource handler. Specific methods for the required resources are now
  clearly defined. The new abstraction is now consumed through `dwds.dart`.
- `BuildRunnerAssetHandler` has been renamed to `ProxyServerAssetReader` and is
  now consumed through `dwds.dart`.

## 0.9.0

- Expose `middleware` and `handler`.

**Breaking Change:** The `AssetHandler` will not automatically be added the DWDS
handler cascade. You must now also add the `middleware` to your server's
pipeline.

## 0.8.5

- Always bind to `localhost` for the local debug workflow.
- Fix an issue where breakpoints could cause DevTools to hang.

## 0.8.4

- Support using WebSockets for the debug (VM Service) proxy by passing
  `useSseForDebugProxy: false` to `Dwds.start()`

## 0.8.3

- Support nesting Dart applications in iframes.

## 0.8.2

- Add the ability to receive events from the extension in batches.

## 0.8.1

- Depend on the latest `package:built_value`.

## 0.8.0

- Add temporary support for restoring breakpoints. Eventually the Dart VM
  protocol will clearly define how breakpoints should be restored.
- Depend on latest `package:sse` to get retry logic.
- Don't spawn DevTools if `serveDevTools` is false.
- `UrlEncoder` will also encode the base URI used by the injected client / Dart
  Debug Extension. \*\* Breaking Change \*\* `serveDevTools` is not
  automatically considered true if `enableDebugExtension`is true.

## 0.7.9

- Properly wait for hot reload to complete with the legacy module system.
- Fix issue with `getObject` for a class with a generic type.

## 0.7.8

- Support optional argument `urlEncoder` that is used to encode remote URLs for
  use with the Dart Debug Extension.

## 0.7.7

- Handle getObject for primitives properly.
- Properly black box scripts if query parameters are provided.

## 0.7.6

- Fix issue with source map logic for the legacy module system.
- Allow setting breakpoints multiple times and just return the old breakpoint.
- Fix a bug with Maps that contain lists of simple types.

## 0.7.5

- The injected client's connection is now based off the request URI.
- Fix an issue where resuming while paused at the start would cause an error.
- Expose the `ChromeDebugException` class for error handling purposes.
- Expose the `AppConnectionException` class for error handling purposes.
- DevTools will now launch immediately and lazily sets up necessary state.
- Properly set `pauseBreakpoints` on `kPauseBreakpoint` events.
- Greatly improves handling of List, Map and IdentityMap instances.
- Lazily parse source maps to improve performance for large applications.

## 0.7.4

- Deobfuscate DDC extension method stack traces.
- Properly get all libraries with the `legacy` module system.

## 0.7.3

- Correctly set `Isolate` state if debugging is initiated after the application
  has already started.

## 0.7.2

- Account for root directory path when using `package:` URIs with `DartUri`.

## 0.7.1

- Fix a bug where we would try to create a new isolate even for a failed hot
  restart. This created a race condition that would lead to a crash.
- Don't attempt to write a vm service request to a closed connection.
  - Instead we log a warning with the attempted request message and return.
- Make all `close` methods more robust by allowing them to be called more than
  once and returning the cached future from previous calls.
- Add explicit handling of app not loaded errors when handling chrome pause
  events.

## 0.7.0

- `DWDS.start` now requires an `AssetHandler` instead of `applicationPort`,
  `assetServerPort` and `applicationTarget`.
- Expose a `BuildRunnerAssetHandler` which proxies request to the asset server
  running within build runner.
- Support the Legacy Module strategy through the injected client.
- Support DDK sourcemap URIs.
- Update SDK dependency to minimum of 2.5.0.

### Bug Fixes:

- Fix handling of chrome pause events when we have no isolate loaded yet.

## 0.6.2

- Capture any errors that happen when handling SSE requests in the DevHandler
  and return an error response to the client code.
  - Log error responses in the client to the console.
- Handle empty Chrome exception descriptions.

## 0.6.1

- Add `isolateRef` to `Isolate`s `pauseEvent`s.
- Depend on the latest `package:vm_service`.
- Implements `invoke`.
- Adds support for VM object IDs for things that don't have Chrome object Ids
  (e.g. int, double, bool, null).

## 0.6.0

- Add new required parameter `enableDebugging` to `Dwds.start`. If `false` is
  provided, debug services will not run. However, reload logic will continue to
  work with the injected client.
- Handle injected client SSE errors.
- Handle a race condition when the browser is refreshed in the middle of setting
  up the debug services.

## 0.5.5

- Properly set the `pauseEvent` on the `Isolate`.
- Fix a race condition with Hot Restarts where the Isolate was not created in
  time for pause events.

## 0.5.4

- Fix issue where certain required fields of VM service protocol objects were
  null.
- Properly set the `exceptionPauseMode` on the `Isolate`.
- Depend on the latest `DevTools`.

## 0.5.3

- Fix issue where certain required fields of VM service protocol objects were
  null.

## 0.5.2

- Fix issue where certain required fields of VM service protocol objects were
  null.
- Properly display `Closure` names in the debug view.

## 0.5.1

- Fix an issue where missing source maps would cause a crash. A warning will now
  be logged to the console instead.
- Depend on the latest `package:webkit_inspection_protocol`.

## 0.5.0

- Fix an issue where we source map paths were not normalized.
- Added a check to tests for the variable DWDS_DEBUG_CHROME to run Chrome with a
  UI rather than headless.
- Catch unhandled errors in `client.js` and recommend using the
  `--no-injected-client` flag for webdev users.
- Add support for an SSE connection with Dart DevTools.
- Rename `wsUri` to `uri` on `DebugConnection` to reflect that the uri may not
  be a websocket.
- Depend on latest `package:vm_service`.

## 0.4.0

- Move `data` abstractions from `package:webdev` into `package:dwds`.
- Move debugging related handlers from `package:webdev` into `package:dwds`.
- Move injected client from `package:webdev` into `package:dwds`.
- Create new public entrypoint `dwds.dart`. Existing public API `services.dart`
  is now private.

## 0.3.3

- Add support for `getScript` for paused isolates.
- Add support for `onRequest` and `onResponse` listeners for the vm service.

## 0.3.2

- Add support for `scope` in `evaluate` calls.

## 0.3.1

- Improve error reporting for evals, give the full JS eval in the error message
  so it can be more easily reproduced.

## 0.3.0

- Change the exposed type on DebugService to VmServiceInterface

## 0.2.1

- Support `setExceptionPauseMode`.

## 0.2.0

- Added custom tokens to the `wsUri` for increased security.
  - Treating this as a breaking change because you now must use the `wsUri`
    getter to get a valid uri for connecting to the service, when previously
    combining the port and host was sufficient.

## 0.1.0

- Initial version

repository: dart-lang/webdev

gha_language: Dart

repo_name: dart-lang/webdev


text:
---
maker: "unknown"
caption: "Love the fit and stripes on this modified Teagan!"
date: "2023-01-15"
intro: "A FreeSewing user gave modifying Teagan a try, and we love how the results turned out! Here's a little explanation she shared of how she drafted her Teagan and shaped the side seams for a closer fit."
title: "A Spectacular Stripey Teagan"
designs: ["teagan"]
---

A FreeSewing user gave modifying Teagan a try, and we love how the results turned out! Here's a little explanation she shared of how she drafted her Teagan and shaped the side seams for a closer fit.

"I'm really happy with how this turned out! I was curious to see how a close-fitting made-to-measure t-shirt would look on me, so I gave Teagan a try. I set both chest and hips ease as low as they would go (5% and 8%, respectively) and added some bonus length to both the shirt itself and the sleeves.

For a tighter fit at the top I enabled 'draft for high bust'. There was no option to set the waist ease (yet), so I combined two versions, one generated as usual and one where I replaced my hips measurement with my waist measurement.

The neckband is just a (horizontal) strip of the same fabric, attached as a knit band.

I was surprised by how quickly this came together, and I can definitely see myself making several of these in different fabrics!"

repository: freesewing/freesewing

branch_name: refs/heads/develop

gha_language: JavaScript

repo_name: freesewing/freesewing


text:
---
layout: post
title:  "Testing the Lattice: Start with Why"
comments: true
date:   2018-11-29 12:00:00 -0500
categories: leadership
draft: false
---

Start with Why is a book by Simon Sinek, published in 2009. There's also an excellent [TED Talk](https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=en) on the subject of the book. It is centered around the concept of "Why" - the central reason that inspires action in people.

Start with Why: How Great Leaders Inspire Action, is divided into 4 parts:

1) About Why - An overview of "Why" and it's role in decision making
2) Brands - How "Why" plays a key role is helping to shape the long-term success of brands - Lessons from here apply in the Application domain.
3) Organizations - How "Why" plays a role in attracting and retaining employees - Lessons from this section apply mostly in the Individual domain, but some also in the domain of Organization.
4) Personal leadership - How "Why" plays a role in leadership - This is primarily concerned with how leaders use Why as a tool to inspire and lead - and can be considered part of the Individual or Organization domain.

As a leadership book, Start with Why touches many parts of the lattice, and is one of the few books that bridges between the domain of Individual, Organization _and_ Application / . The lessons test the structure of the lattice, and it's an interesting leadership book structured entirely around the concept of why, rather than a specific leadership technique or management approach.

This post uses [this great book summary](https://slooowdown.wordpress.com/2014/01/12/start-with-why-how-great-leaders-inspire-everyone-to-take-action-by-simon-sinek/).

repository: tarunsachdeva/blog

branch_name: refs/heads/gh-pages

extension: markdown

repo_name: tarunsachdeva/blog


text:
# Vuepress simple sidebar plugin

A simple and minimal-configuration automatic sidebar navigation generator plugin.
Focus on your documents, not the tooling.

## Demo

The documentation of this project can provide a nice demo, check it out
[here](https://dpsarrou.github.io/vuepress-simple-sidebar).

Alternatively, you can build and view the documentation locally by running

    npm run docs:dev

and then visit [localhost:8080](http://localhost:8080/).

## Installation

    npm install vuepress-simple-sidebar

## Usage

In your `.vuepress/config.js` add the plugin to the plugins property as:

    plugins: [
        ...
        'vuepress-simple-sidebar',
    ]

repository: dpsarrou/vuepress-simple-sidebar

repo_name: dpsarrou/vuepress-simple-sidebar


text:
# Terraform Best Practices

1. Don’t commit the .tfstate file
   ([source](https://openupthecloud.com/terraform-best-practices/))
2. `terraform fmt` to lint the .tf file
3. `terraform validate` to ensure the correctness of .tf file before
calling `terraform apply`
4. Commit the `.terraform.lock.hcl` file to make sure that `terraform`
uses the same version of plugins and providers

repository: nikololiahim/devops

repo_name: nikololiahim/devops


text:
[![Build Status](https://travis-ci.com/RENCI/pdspi-mapper-parallex-example.svg?branch=master)](https://travis-ci.com/RENCI/pdspi-mapper-parallex-example)

# pdspi-mapper-parallex-example

## prerequisites
 python 3.8 or higher

## configuration

edit `tests/docker.env`

Put your spec under `config`. Put your custom python functions under a sub dir in that dir. Any python module under the sub dir can be imported in your spec. Your spec should output the format that the api specifies.

## utility functions for building python functions that can be used to build the spec

use `query_records_closest_before` to get records closest before date;

use `query_records_closest_after` to get records closest after date;

use `query_records_closest` to get records closest to date;

`query_records_interval` can take a start/end time

look at extant function for examples you can reuse

## start
```
./up.sh
```

## stop
```
./down.sh
```
## api
`modelParameters`

`specName`: spec name is a file name relative to the `config`

`libraryPath`: library path relative to the `config` dir

# cli tools

To use the cli tools, put your spec under `config`. Put your custom python functions under a sub dir in that dir. There is a `cli.py`. You can run it as

```
python cli.py <file containing your spec> <sub dir containing custom python functions> <number of threads> <level> <a yaml file containing resource types> <a yaml file contains pids> <timestamp> <fhir plugin port> <mapper plugin port>
```

For example

```
python cli.py spec.py modules 4 1 ../resourceTypes.yaml ../patientIds.yaml "2000-01-01T00:00:00Z" 8080 8081
```

In this example, you would put your spec in `config/spec.py`. Any python module under the `config/modules` directory can be imported in your spec. For example, if you have `config/modules/clivar.py`, you can reference functions in that module in various ways, for example `from clivar import *`. `../resourceTypes.yaml` contains a list of resource types. `../patientIds.yaml` contains a list of patient ids. Your spec should output the format that the api specifies. See `config/spec4.py`'s `return` statement for example. `<level>` specifies the number of nested for loops to parallelize.

repository: RENCI/pdspi-mapper-parallex-example

gha_language: Python

repo_name: RENCI/pdspi-mapper-parallex-example


text:
---
title: "Word Cloud of Trip Advisor Reviews - Sentiment Analysis"
theme: default
layout: default
parent: Projects
nav_order: 3
---
Here we have a quick word cloud generated from Trip Advisor Reviews. The data is from [Kaggle](https://www.kaggle.com/andrewmvd/trip-advisor-hotel-reviews). Python was used. To see the script, please visit the GitHub repository: [TripAdvisorSentiment](https://github.com/AnnaWallin/TripAdvisorSentiment).

<img src="https://user-images.githubusercontent.com/76073032/104963802-eb2a7600-59a0-11eb-9d62-90142c1dc171.png" width="450" height="300" />


text:
# InverSim 0.1
This is an Electron JS application to simulate Axpert power inverters communication protocol.

![Alt text](docs/inversim-0.1-ui.png?raw=true "InverSim 0.1 Screenshot")

# Features
+ replies to commands sent via a serial link or UDP.
+ configure some general characteristics of the inverter : flags, warnings, and status data.
+ setting parameters commands changes internal values, example : PE/PD
+ a console to view the received commands and sent responses.
+ possibility to send commands to the simulator on the UI.

# Download
releases : https://github.com/ouadev/InverSim/releases

# disclaimer
The Axpert power inverters have several series and models, and there is no official specification for each model.
This application helps developers check if their programs, interfacing with an Axpert power inverter, are sending commands with the right format : length, CRC, etc. Howerver, the responses to the commands are guaranteed to cover 95% of cases, since some models don't implement all of the commands, or reply differently. Please check the specification you have for your model, and make sure the simulator is replying the way it's expected, and send a PR if something doesn't add up.

repository: ouadev/InverSim

repo_name: ouadev/InverSim


text:
# Changelog

This file was generated using [@jscutlery/semver](https://github.com/jscutlery/semver).

# 1.0.0 (2022-09-13)

### Bug Fixes

* **eslint:** fix config errors ([3f52df7](https://github.com/rx-angular/rx-angular/commit/3f52df7b74b0fc01c56fafe07287597e032fad2d))

### Features

* **eslint:** add new lint rule no-rxstate-imperative-in-reactive ([e5ab350](https://github.com/rx-angular/rx-angular/commit/e5ab350c643ede065bb04c9618c0794133d7d694))
* **eslint:** add new rule no-rxstate-subscriptions-outside-constructor ([a9fa408](https://github.com/rx-angular/rx-angular/commit/a9fa408449df180322021a2d5df9899db77c0959))
* **eslint:** define recommended and zoneless config ([f4661bd](https://github.com/rx-angular/rx-angular/commit/f4661bd813897f0cad3eed501a5bd1ee4063982b))
* **eslint:** implement and test layout sensitive apis rule ([a473772](https://github.com/rx-angular/rx-angular/commit/a4737729de98e3e3733bbfb2f033a46966a5a4c9))
* **eslint:** implement and test Zone-patched browser APIs rule ([aa7ea93](https://github.com/rx-angular/rx-angular/commit/aa7ea935d614f23ecd98051733b00d36dd060981))
* **eslint:** implement and test zone.run rule ([2dd5af8](https://github.com/rx-angular/rx-angular/commit/2dd5af8700a8330353adcfd3ab9508e81fd3faa3))
* **eslint:** implement change detection rule ([40d4213](https://github.com/rx-angular/rx-angular/commit/40d4213176020b90cc8b6d0e932cbc685a751fd8))
* **eslint:** implement Lodash-related rules ([70f4c13](https://github.com/rx-angular/rx-angular/commit/70f4c1303a2cffc005fd5bab72cc0f38b6bf2ded))
* **eslint:** implement Zone-patched RxJS rules ([01a685d](https://github.com/rx-angular/rx-angular/commit/01a685d6f7dcb30839235d0c20d8b1fd7f1da557))
* **eslint:** refer to structuredClone in prefer-no-lodash-clone-deep rule ([1ac06cc](https://github.com/rx-angular/rx-angular/commit/1ac06ccf50a4f3267cb96320f8a934a884c0d87d))

repository: rx-angular/rx-angular

repo_name: rx-angular/rx-angular


text:
# murmur-bad-words
Calculate bad word probability in base36 with murmur hash

## Analysis

Len of murmur hash of uuid is normally 13, using base36, total number is:

```
>>> 36 ** 13
170581728179578208256L
```

about `2^46`, a lot

So how many times can a bad word in English happend in a hash

> It's very mathematical/algorithmic, but I will try...

Let's say a bad word has len=3, for example `ass`, we need to know how many times this bad word
happend to be at the end of a string which len is `3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13`

- len(str) = 3, answer is 1
- len(str) = 4, str can be `[0-9a-z]ass`, answer is 36,
- len(str) = 5, str can be `[0-9a-z]ass`, answer is 36 * 36

You can see the pattern, for a bad word has len=A, a string has len=B where B >= A, in base36 there are
`36 ** (B - A)` ways that string ends with this bad word.

so

- len(str) = 10, answer is 36 ** 7
- len(str) = 11, answer is 36 ** 8
- len(str) = 12, answer is 36 ** 9
- len(str) = 13, answer is 36 ** 10

Also, if `w` is at the end of `s[:N]`, then `w` is in `s`, I don't know how to probably prove it,
but it looks very close to correct.

But there is one case to consider, if `w` is at the end of str with len=13, we need to minus the count
where `w` is at the end of string with len=12 and len=11. However it depends on `w`, if `w` is like `"aaa"`,
We don't need to minus those, but normally a bad word is a normal English word.

repository: calvinxiao/murmur-bad-words

repo_name: calvinxiao/murmur-bad-words


text:
# kr_mavros_interface

This node translates `kr_mav_msgs/SO3Command` to `mavros_msgs/AttitudeTarget`.

Please note that your flight controller yaw orientation estimation may be
different to your odom system orientation estimation. We should transform our
`kr_mav_msgs/SO3Command` into the flight controller yaw before publishing it.

#### `mavros_msgs` requirement

This node requires `mavros_msgs` to be present when building. If `mavros_msgs` is not found when building the first time, a warning is given and nothing in this package is built. If `mavros_msgs` is installed after this, force a recheck by adding `--force-cmake` to the `catkin_make`/`catkin build` command.


text:
---
title: "SCCM Powershell Reference: Adding content to all Distribution Points"
date: "2014-01-03"
redirect_from : /2014/01/03/sccm-powershell-reference-adding-content-to-all-distribution-points
categories:
  - "scripting"
tags:
  - "powershell"
  - "sccm"
---

[![Depicts an image saying 'Scripting System Center Configuration Manager'](../series/images/series_sccm.png)](/series/LearningSCCM)

This post is part of the 'Scripting SCCM' series on FoxDeploy, click the banner for more!

* * *

Another quickie here: I needed a way to add all packages to all distribution points, and do so with as few / zero clicks as possible.  Using a few PowerShell commands, I was able to do just that!  While there is no native command (yet!) to push content to a distribution point, you can easily do so with a WMI call, and automate the whole process with a single pipeline.

For the first step, we'll use the Configuration Manager Module's Get-CMPackage Command, and pipe it into a filter.  We'll need the PackageID field, and would prefer not to have the value include the column header, so we'll use the -ExpandProperty parameter to omit this.

```powershell
Get-CMPackage | Select - ExpandProperty PackageID
```

![](../assets/images/2014/01/images/01_add_all_packages_to_distribution_point_group.png)

Now, we need to connect to the local SCCM instance.  We'll use Get-WMIObject to do so.

```powershell
Get-WMIObject -NameSpace "Root\SMS\Site_YOUR_PRIMARY_OR_CAS_SITE_CODE" -Class SMS_DistributionPointGroup
```

If you pipe this command into Get-Member, you'll see the output below.  This tells us of all of the properties and methods we'll have available using the WMI Object.  I've highlighted the method we need, AddPackages().

![](../assets/images/2014/01/images/02_add_all_packages_to_distribution_point_group.png)

Now, to put it all together.  We'll first enumerate all of the PackageIDs, and send this value on down our command line using a pipeline.  This value will be assigned to $package in the run phase of the ForEach-Object command, in which the WMI Object's AddPackage() method will be called once for each object in the variable, using the $_ current pipeline object character.  Some rudimentary error catching is here, looking to see if a non-zero value is returned.  Here is the command.

```powershell
Get-CMPackage | Select -ExpandProperty PackageID | ForEach-Object { $package = $_ Write-host "Adding Package: $package" if (((Get-WMIObject -NameSpace "Root\SMS\Site_YOUR-THREE-DIGIT-SITE-CODE" -Class SMS_DistributionPointGroup).AddPackages($package)).ReturnValue -ne 0) { Write-host -ForegroundColor DarkRed "Possible error processing $package" } ELSE{ Write-Host -ForegroundColor GREEN "Success!" } }
```

And here it is in action.

![](../assets/images/2014/01/images/04_add_all_packages_to_distribution_point_group.png)

Happy Green makes me feel alright!

I hope this helped you out.  You could also distribute drivers, operating system images, updates or any other content that uses a PackageID using this same syntax.


text:
[@redhat-cloud-services/remediations-client](../README.md) › [Globals](../globals.md) › [PlaybookRunStatus](playbookrunstatus.md)

# Enumeration: PlaybookRunStatus

**`export`**

**`enum`** {string}

## Index

### Enumeration members

* [Acked](playbookrunstatus.md#acked)
* [Canceled](playbookrunstatus.md#canceled)
* [Failure](playbookrunstatus.md#failure)
* [Pending](playbookrunstatus.md#pending)
* [Running](playbookrunstatus.md#running)
* [Success](playbookrunstatus.md#success)

## Enumeration members

###  Acked

• **Acked**: = "acked"

*Defined in [api.ts:437](https://github.com/RedHatInsights/javascript-clients/blob/master/packages/remediations/api.ts#L437)*

___

###  Canceled

• **Canceled**: = "canceled"

*Defined in [api.ts:441](https://github.com/RedHatInsights/javascript-clients/blob/master/packages/remediations/api.ts#L441)*

___

###  Failure

• **Failure**: = "failure"

*Defined in [api.ts:440](https://github.com/RedHatInsights/javascript-clients/blob/master/packages/remediations/api.ts#L440)*

___

###  Pending

• **Pending**: = "pending"

*Defined in [api.ts:436](https://github.com/RedHatInsights/javascript-clients/blob/master/packages/remediations/api.ts#L436)*

___

###  Running

• **Running**: = "running"

*Defined in [api.ts:438](https://github.com/RedHatInsights/javascript-clients/blob/master/packages/remediations/api.ts#L438)*

___

###  Success

• **Success**: = "success"

*Defined in [api.ts:439](https://github.com/RedHatInsights/javascript-clients/blob/master/packages/remediations/api.ts#L439)*

repository: croissanne/javascript-clients

repo_name: croissanne/javascript-clients


text:
---
hrs_structure:
  division: '2'
  volume: '10'
  title: '25'
  chapter: '441'
  section: 441-22.7
type: hrs_section
tags:
  - Business
menu:
  hrs:
    identifier: HRS_0441-0022_0007
    parent: HRS0441
    name: 441-22.7 Further additional charges or fees for perpetual care
weight: 28155
title: Further additional charges or fees for perpetual care
full_title: 441-22.7 Further additional charges or fees for perpetual care
---
**[§441-22.7] Further additional charges or fees for perpetual care prohibited; unfair or deceptive act or practice; penalty.** (a) Subsequent to the execution of a valid written contract for the sale of cemetery property, interment services, funeral services, and related commodities by a mortuary, cemetery, or pre-need funeral authority to a purchaser in accordance with this chapter, further additional charges or fees for perpetual care shall be prohibited beyond those originally agreed upon in the contract and no such charges or fees shall be charged or collected by the seller for any purpose and upon any occasion; provided that a reasonable fee may be charged for administrative costs related to the transfer of ownership rights, including the cost of research, document and file preparation, photocopying, notary fees, records transfer and storage, and any other costs directly related to the transfer of ownership rights.

(b) A mortuary, cemetery, or pre-need funeral authority who violates subsection (a) is guilty of engaging in an unfair or deceptive act or practice under section 480-2, and shall be fined not less than $500 nor more than $10,000 for each violation. The penalties provided in this subsection are cumulative to the remedies or penalties available under all other laws of this State. [L 1998, c 232, §1]

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby