text:
## This is an open-source repository that collects programming problems.
Anyone can work on any issue and you can also create your own issues, So start working on issue when you are done then request a pull create and I'll merge into main codebase.

Important Steps

(i) Do the coding of the problem you want to work on and made a PR in 'General Folder only'.

(ii) NOTE:- Filename should be in the format- "yourname_filename.extension".

(iii) And you're done!!

(iv) Make sure the problem you are working on must not clash with similiar problem in the folder

Solve as many problems as you can and create pull request for every individual problem and 🌟 this repo for future reference.

### Steps to contribute

👉 Fork this repository

Fork this repository by clicking on the fork button on the top of this page. This will create a copy of this repository in your account.

👉 Clone the repository

Now clone the forked repository to your system. Go to your GitHub account, open the forked repository, click on the code button and then clone the repository.

👉 Create a branch

Then create a branch on your local repository to solve a problem.

👉 Add & commit

Make necessary changes and commit those changes

👉 Push changes to GitHub

Finally push your local repository to remote repository

👉 Compare & Submit a Pull Request

We're happy to merge valid pull requests to this repository!

👉 Also Star the repository

### TADAA🌟🌟, Now you are an open-source contributor.... BOOM!!!!


text:
apple_iwork CHANGELOG
=====================

This file is used to list changes made in each version of the apple_iwork cookbook.

0.2.0
-----
- [rchristensen] - Ripped out legacy iLife '09 suite, now on the trio of modern applications captured from Mac App Store.
- [rchristensen] - Updated Keynote to 6.2
- [rchristensen] - Updated Numbers to 3.2
- [rchristensen] - Updated Pages to 5.2
- [rchristensen] - Brought README/metadata/CHANGELOG up to code.

0.1.0
-----
- [rchristensen] - Initial release of apple_iwork cookbook
- [rchristensen] - Current app version: 9.3

repository: wesleyan/chef-cookbooks

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: wesleyan/chef-cookbooks


text:
---
title: "XR projects"
tags:
  - "python"
date: 2020-12
excerpt: "XR projects made in EECS 498-003"
authors:
  - name: "xieleo"
    url: "https://github.com/xieleo5"
  - "xieleo"
path: "project/XR"
selected: false
cover: "./preview.png"
links:
  - name: "github"
    file: "https://github.com/xieleo5/498Portfolio"
priority: 10
---
# XR projects

## Project 1
A VR project that simulate the CSE building.

<iframe
    width="640"
    height="480"
    src="https://www.youtube.com/embed/9N9zz3_y5Ps"
    frameborder="0"
    allow="autoplay; encrypted-media"
    allowfullscreen
>
</iframe>

## Project 2
An AR project that plant trees and fight with enemies inside Ann Arbor. Use mapbox for the GPS locating.
<iframe
    width="640"
    height="480"
    src="https://www.youtube.com/embed/wL9UqLRBnA8"
    frameborder="0"
    allow="autoplay; encrypted-media"
    allowfullscreen
>
</iframe>

## Project3

An VR project for chem students to build organic molecules.

### Trailer

<iframe width="560" height="315" src="https://www.youtube.com/embed/a4Y5mikLnTM" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

### Website

[Home | Atomic Builder](https://ripplerippleyqq.wixsite.com/atomic-builder)

license: MIT


text:
---
layout: default
---

# 1994-04-29 - Re: Rings of Saturn

## Header Data

From: Llywelyn<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message Hash: 115f6324138501567d20f27ded06f9615d80fd4099414598284896bcf39d2c68

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1994-04-29 13:26:25 UTC

Raw Date: Fri, 29 Apr 94 06:26:25 PDT

## Raw message

```
{% raw  %}From: Llywelyn<EMAIL_ADDRESS>Date: Fri, 29 Apr 94 06:26:25 PDT
To<EMAIL_ADDRESS>Subject: Re: Rings of Saturn
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

On Fri, 29 Apr 1994, Perry E. Metzger wrote:

>
> Jeff Davis says:
> > Y'all are doing real well with the satellite discussion.  It may interest
> > some of you to know that the rings of Saturn were found to be braided in
> > 4's.  This blew the hell out of the direction they were going on unified
> > field theory which predicted they would be braided in 3's.  With no
> > atmospheric refraction to contend with, this was still a rather accomplished
> > feat.
>
> Jeff Davis turns out not to just be the ordinary garden variety loon,
> but a genuine reincarnation of net.psycho Robert McElwaine!
>
> For his next act, he will explain why it is that the U.S. government
> has been hiding information on aliens visitors being kept frozen in a
> secret lab in Oregon!!!

What!? You're going to tell me that a man with your obvious intelligence
and joie de vivre didn't know?

The aliens(Skree-nok as they're called) are being kept hostage in order
to prompt their government into transferring technology to the evil NSA
in order to help it.  The Clipper chip was just a tidbit of the power
that the aliens have.

The NSA among its other projects is trying to wangle a device that will
allow the access to the brain of PRZ to help them put a back door inside
PGP and the aliens want a sacrifice of 2^10 virgins for this.

<sigh>

We're all doomed.....

Ben.

{% endraw %}
```

## Thread

+ Return to [April 1994](/archive/1994/04)

+ Return to "[Chris Knight <cknight@crl.com>](/authors/chris_knight_cknight_at_crl_com_)"
+ Return to "[Jeff Davis <eagle@deeptht.armory.com>](/authors/jeff_davis_eagle_at_deeptht_armory_com_)"
+ Return to "[Llywelyn <samman@CS.YALE.EDU>](/authors/llywelyn_samman_at_cs_yale_edu_)"
+ Return to "["Perry E. Metzger" <perry@snark.imsi.com>](/authors/perry_e_metzger_perry_at_snark_imsi_com_)"

+ 1994-04-29 (Fri, 29 Apr 94 05:21:16 PDT) - [Rings of Saturn](/archive/1994/04/381f69b7dc0560763968e9e1d05cab9aa4e9c1d5ad845afd76319a0e1e342297) - _Jeff Davis<EMAIL_ADDRESS>  + 1994-04-29 (Fri, 29 Apr 94 05:48:10 PDT) - [Re: Rings of Saturn](/archive/1994/04/4a109e543b9fe544cddc3e2c0e9c35c49b8dce7dc0ff80618232f84b03f406ed) - _"Perry E. Metzger"<EMAIL_ADDRESS>    + 1994-04-29 (Fri, 29 Apr 94 06:26:25 PDT) - Re: Rings of Saturn - _Llywelyn<EMAIL_ADDRESS>    + 1994-04-29 (Fri, 29 Apr 94 07:58:12 PDT) - [Re: Rings of Saturn](/archive/1994/04/53773b88bdde63bc5d4e56f15eb6f0c86c8695a83fb54d53a2a6380860162a54) - _Chris Knight<EMAIL_ADDRESS>

gha_license_id: MIT


text:
---
layout: relation
title: 'cop'
shortdef: 'copula'
udver: '2'
---

A copula is the relation between the complement of a copular verb and the copular verb.
For more on the `cop` relation, see the universal dependency description ([u-dep/cop]())
Verbal copulas are tagged [AUX](), not `VERB`.

~~~ sdparse
hoː =b hoːsoː ʃʔag -aː =b =u uː= tak // ʔasal -aː =b iː- kti =jeːb /
text_en: "The man was carrying on his shoulder a lamb that he had grilled.
cop(ʃʔag, =u) ("carry_on_shoulder", `AUX`)
~~~
<!-- Interlanguage links updated Út 9. května 2023, 20:04:08 CEST -->

repository: UniversalDependencies/docs

branch_name: refs/heads/pages-source

gha_language: HTML

repo_name: UniversalDependencies/docs


text:
---
layout: post
title: New codingmarks published in week 33 of 2018
description: "New codingmarks published in week 33 of 2018. Keywords: angular, angular-material, java, javaee, javascript, jvm, nodejs, performance, scheduling, typescript, ux and wildfly"
author: ama
permalink: /ama/new-codingmarks-week-33-2018
published: true
categories: [dev-bookmarks]
tags: [dev-bookmarks]
---
New [dev bookmarks](https://www.bookmarks.dev) added in the 33th week of 2018. Hot topics include:

* TOC
{:toc}

## angular

**[Angular Material Dialog: A Complete Example](https://blog.angular-university.io/angular-material-dialog/)**

  *  **published on**:  2018-06-18
  * **tags**:   [angular](https://www.bookmarks.dev/search?q=[angular]),   [angular-material](https://www.bookmarks.dev/search?q=[angular-material])
  *  [github url](https://github.com/angular-university/angular-material-course)

In this post, we are going to go through a complete example of how to build a custom dialog using the Angular Material Dialog component.

We are going to cover many of the most common use cases that revolve around the Angular Material Dialog, such as: common dialog configuration options, passing data into the dialog, receiving data back, and dialog layout options.

## angular-material

**[Angular Material Dialog: A Complete Example](https://blog.angular-university.io/angular-material-dialog/)**

  *  **published on**:  2018-06-18
  * **tags**:   [angular](https://www.bookmarks.dev/search?q=[angular]),   [angular-material](https://www.bookmarks.dev/search?q=[angular-material])
  *  [github url](https://github.com/angular-university/angular-material-course)

In this post, we are going to go through a complete example of how to build a custom dialog using the Angular Material Dialog component.

We are going to cover many of the most common use cases that revolve around the Angular Material Dialog, such as: common dialog configuration options, passing data into the dialog, receiving data back, and dialog layout options.

## java

**[Metrics](https://metrics.dropwizard.io/)**

  * **tags**:   [java](https://www.bookmarks.dev/search?q=[java]),   [jvm](https://www.bookmarks.dev/search?q=[jvm]),   [performance](https://www.bookmarks.dev/search?q=[performance])
  *  [github url](https://github.com/dropwizard/metrics)

Metrics is a Java library which gives you unparalleled insight into what your code does in production.

## javaee

**[Creating clustered EJB 3 Timers ](http://www.mastertheboss.com/jboss-server/wildfly-8/creating-clustered-ejb-3-timers)**

  * **tags**:   [javaee](https://www.bookmarks.dev/search?q=[javaee]),   [wildfly](https://www.bookmarks.dev/search?q=[wildfly]),   [scheduling](https://www.bookmarks.dev/search?q=[scheduling])

In this tutorial we will demonstrate how to configure a Timer EJB 3 Service on a cluster of servers. You will need WildFly 8 application server and a Database supporting READ_COMMITTED or SERIALIZABLE isolation level.

**[Scheduling in Java EE](https://www.baeldung.com/scheduling-in-java-enterprise-edition)**

  *  **published on**:  2017-11-30
  * **tags**:   [javaee](https://www.bookmarks.dev/search?q=[javaee]),   [scheduling](https://www.bookmarks.dev/search?q=[scheduling])
  *  [github url](https://github.com/eugenp/tutorials/tree/master/jee-7)

A demonstration of how to schedule tasks in Java EE using the `@Schedule` annotation and the timer service.

## javascript

**[InversifyJS a powerful IoC container for JavaScript apps powered by TypeScript](http://inversify.io/)**

  * **tags**:   [nodejs](https://www.bookmarks.dev/search?q=[nodejs]),   [typescript](https://www.bookmarks.dev/search?q=[typescript]),   [javascript](https://www.bookmarks.dev/search?q=[javascript])
  *  [github url](https://github.com/inversify/InversifyJS/)

InversifyJS is a lightweight inversion of control (IoC) container for TypeScript and JavaScript apps.

## jvm

**[Metrics](https://metrics.dropwizard.io/)**

  * **tags**:   [java](https://www.bookmarks.dev/search?q=[java]),   [jvm](https://www.bookmarks.dev/search?q=[jvm]),   [performance](https://www.bookmarks.dev/search?q=[performance])
  *  [github url](https://github.com/dropwizard/metrics)

Metrics is a Java library which gives you unparalleled insight into what your code does in production.

## nodejs

**[InversifyJS a powerful IoC container for JavaScript apps powered by TypeScript](http://inversify.io/)**

  * **tags**:   [nodejs](https://www.bookmarks.dev/search?q=[nodejs]),   [typescript](https://www.bookmarks.dev/search?q=[typescript]),   [javascript](https://www.bookmarks.dev/search?q=[javascript])
  *  [github url](https://github.com/inversify/InversifyJS/)

InversifyJS is a lightweight inversion of control (IoC) container for TypeScript and JavaScript apps.

## performance

**[Metrics](https://metrics.dropwizard.io/)**

  * **tags**:   [java](https://www.bookmarks.dev/search?q=[java]),   [jvm](https://www.bookmarks.dev/search?q=[jvm]),   [performance](https://www.bookmarks.dev/search?q=[performance])
  *  [github url](https://github.com/dropwizard/metrics)

Metrics is a Java library which gives you unparalleled insight into what your code does in production.

## scheduling

**[Creating clustered EJB 3 Timers ](http://www.mastertheboss.com/jboss-server/wildfly-8/creating-clustered-ejb-3-timers)**

  * **tags**:   [javaee](https://www.bookmarks.dev/search?q=[javaee]),   [wildfly](https://www.bookmarks.dev/search?q=[wildfly]),   [scheduling](https://www.bookmarks.dev/search?q=[scheduling])

In this tutorial we will demonstrate how to configure a Timer EJB 3 Service on a cluster of servers. You will need WildFly 8 application server and a Database supporting READ_COMMITTED or SERIALIZABLE isolation level.

**[Scheduling in Java EE](https://www.baeldung.com/scheduling-in-java-enterprise-edition)**

  *  **published on**:  2017-11-30
  * **tags**:   [javaee](https://www.bookmarks.dev/search?q=[javaee]),   [scheduling](https://www.bookmarks.dev/search?q=[scheduling])
  *  [github url](https://github.com/eugenp/tutorials/tree/master/jee-7)

A demonstration of how to schedule tasks in Java EE using the `@Schedule` annotation and the timer service.

## typescript

**[InversifyJS a powerful IoC container for JavaScript apps powered by TypeScript](http://inversify.io/)**

  * **tags**:   [nodejs](https://www.bookmarks.dev/search?q=[nodejs]),   [typescript](https://www.bookmarks.dev/search?q=[typescript]),   [javascript](https://www.bookmarks.dev/search?q=[javascript])
  *  [github url](https://github.com/inversify/InversifyJS/)

InversifyJS is a lightweight inversion of control (IoC) container for TypeScript and JavaScript apps.

## ux

**[Should form 'Continue' button be disabled if validation is incomplete?](https://ux.stackexchange.com/questions/73728/should-form-continue-button-be-disabled-if-validation-is-incomplete/73731)**

  * **tags**:   [ux](https://www.bookmarks.dev/search?q=[ux])

Out of the best voted answer:
For simple forms yes...

## wildfly

**[Creating clustered EJB 3 Timers ](http://www.mastertheboss.com/jboss-server/wildfly-8/creating-clustered-ejb-3-timers)**

  * **tags**:   [javaee](https://www.bookmarks.dev/search?q=[javaee]),   [wildfly](https://www.bookmarks.dev/search?q=[wildfly]),   [scheduling](https://www.bookmarks.dev/search?q=[scheduling])

In this tutorial we will demonstrate how to configure a Timer EJB 3 Service on a cluster of servers. You will need WildFly 8 application server and a Database supporting READ_COMMITTED or SERIALIZABLE isolation level.


text:
# If Else

In this exercise, we'll learn all about code blocks and see how to write conditional code, sticking
to if-else for the time being.

In `exercise.spvasm`, we have the usual setup with `fancy_attribute`, `useful_output` and
`crucial_data`:

```c
useful_output = fancy_attribute;
crucial_data = props.highly_exclusive_bits;
```

We're going to turn that into the following:

```c
if (fancy_attribute < props.threshold)
{
    useful_output = 0;
    crucial_data = vec4(0);
}
else
{
    useful_output = 1.0;
    crucial_data = props.highly_exclusive_bits;
}
```

## Blocks

You have already seen the `OpLabel` instruction after which we have so far been writing code that
appears inside `main()`.  You have surely also noticed the `OpReturn` instruction at the end of the
function.  Everything from the `OpLabel` instruction to the `OpReturn` one has so far been one
"block".  A block is defined as a set of instructions starting with `OpLabel` and some form of
"jump" instruction like return, branch, switch, etc.

So first of all, `OpLabel` is the first instruction of every block.  This instruction is not just an
identifier for the block, but is also used as the jump target of other blocks.

Thinking of the blocks as nodes and the jumps as (directed) connections between them, a graph is
formed called the Control-Flow Graph.  SPIR-V also defines a "dominates" relationship between the
blocks which basically tells whether a block needs to execute before another.  This is nothing too
important for us to know at this point (or maybe ever), other than that SPIR-V requires the blocks
to be specified in order such that a block that dominates another (i.e. is executed before) is
written before it.  In simple terms, no backward jumps (other than for loops obviously).

In this exercise, we will have four blocks.  If you thought blocks are just going to be like in C,
here's where you know that's not true.  Recall that every block must start with an `OpLabel`
instruction and that's where other blocks can jump to.  Our four blocks will look like the
following (written in made-up pseudo-code):

```c
// Block 1: everything leading up to the branch, ending in branch.
block1:
condition = fancy_attribute < props.threshold;
if (condition) jump block2; else jump block3;

// Block 2: contents of the `if` case, ending in jump.
block2:
useful_output = 0;
crucial_data = vec4(0);
jump block4;

// Block 3: contents of the `else` case, ending in jump.
block3:
useful_output = 1.0;
crucial_data = props.highly_exclusive_bits;
jump block4;

// Block 4: everything after the if-else blocks, in this case just containing return.
block4:
return;
```

## An If-Else Construct

Now let's see.  We know how to write an `OpLabel` instruction (if not, look it up right now).  We
also know how to write the actual contents of the blocks (you _did_ do the previous exercises,
didn't you?).  We actually need only a handful of instructions to arrive at the full solution.

First off, the comparison operation used in the condition of the branch (floating point less than)
is implemented with the `OpFOrdLessThan` instruction.

> Waiting for you to consult the spec ...

What's the return type of that instruction, and how do we declare it?

> Waiting for you to check again ...

And what's the meaning of "Ord" in the instruction?  You might have noticed there's an "Unord"
version of the same instruction (and other similar ones).  The difference between the Ord and Unord
instructions is in the handling of NaN.  Ordered floating points can't be NaN, and we're satisfied
with that.

You can go ahead and implement the four blocks in order in `exercise.spvasm`, leaving the `if` and
`jump` instructions out.  You will end up with four blocks each starting with one `OpLabel`
instruction, but missing their terminating jump (except maybe the last block that already has
`OpReturn`)

> Waiting for you to complete this part of the exercise ...

Before implementing the if-else construct, let's look at the control flow again:

```
    block1
    /     \
   |       |
 true    false
   |       |
   V       V
block2   block3
     \   /
      \ /
       |
       V
    block4
```

To implement the if-else branch, SPIR-V provides the above graph through two instructions:

- One instruction specifies what block is reached after the if-else flow is finished; this block is
  referred to as the "merge" block,
- Another instruction specifies the if condition and the true and false blocks.

Note again that the blocks are identified by the id of their `OpLabel` instruction.  The first
instruction above is `OpSelectionMerge` and the second instruction is `OpBranchConditional`.  Go
ahead and look these up in the spec before implementing them in the exercise.

> Waiting for you to complete this part of the exercise ...

Finally, all that's left is to tell blocks 2 and 3 to jump to block 4 at the end.  This is done with
the `OpBranch` instruction.  You can now finish the exercise.

As always, remember to use `./validate` to validate your hand-written SPIR-V and see the
corresponding GLSL.  You can also see a summary of what each exercise does with:

```bash
$ diff exercise.spvasm solution.spvasm
```

path: /11 - If Else/README.md

branch_name: refs/heads/main


text:
# Readme Generator [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

## Table of Contents
* [Description](#description)
* [Installation](#installation)
* [Usage](#usage)
* [License](#license)
* [Contributions](#contributing)
* [Github](#github)
* [Questions](#questions)

## Description
This project generates a README markdown file based on input from the user in the terminal.

## Installation
This app is not currently deployed. To use the app, you must first clone to your local computer and install inquirer package.

## Usage
Once cloned to your local machine, initiate the app from your terminal by navigating to the root file where you have saved this project on your computer and typing `node index`. Once prompts are answered, a README will be generated in the dist folder.

## License
This application is covered by MIT.

## Contributions
This project was created by Bri Cassellius as part of coding bootcamp. [Starter Code](https://github.com/coding-boot-camp/potential-enigma.git)

## Github
This app can be found on GitHub at https://github.com/bcassellius/readme-generator.git.

## Questions
Have a question about this app? [Send an e-mail](mailto:bhilliker@gmail.com).

##### This README was generated using [Bri's README generator](https://github.com/bcassellius/readme-generator).

repository: bcassellius/readme-generator

repo_name: bcassellius/readme-generator


text:
# Create GitflowWorkflow repository.

### Clone GitflowWorkflow repository.

```sh
git clone https://github.com/look4pritam/GitflowWorkflow.git
```

### Change directory to GitflowWorkflow.

```sh
cd GitflowWorkflow
```

### View status of GitflowWorkflow repository.

```sh
git status
```

### View the remote repository.

```sh
git remote -v
```

### View the commit history.

```sh
git log --oneline --graph --all
```


text:
Pattern: `return` with argument inside generator

Issue: -

## Description

Used when a `return` statement with an argument is found in a generator function or method (e.g. with some `yield` statements).

## Further Reading

* [Pylint - E0106](http://pylint-messages.wikidot.com/messages:e0106)


text:
Instapaper.Core
===============

*Forked from [skendrot/Insta.Portable](https://github.com/skendrot/Insta.Portable)*

.NET Core / Standard 2.0 Library for [Instapaper full API](https://www.instapaper.com/api/full) Client with OAuth1a


text:
Scala collection benchmarks
==============

Scala offers a very rich collections API for both mutable an immutable collections. These micro benchmarks examine the
performance for common collection types during appending and subsequent traversal of N elements

Setup
-----

1. Clone this repo
2. Navigate to the directory and run "./activator" (or "sbt" if you have sbt) to enter the console
3. Type "clean"
4. Type "run"

Code structure
----------------------------

The benchmark tests themselves are in package uk.co.tobyhobson.benchmarks, the benchmarks do very little processing
themselves and it's important to keep it this way (see below).

The actual "work" is performed by classes in package uk.co.tobyhobson.fixtures

JMH complications
--------------

I've used JMH and the [SBT-JMH](https://github.com/ktoso/sbt-jmh) plugin to run these benchmarks. JMH is a great tool but
it uses the benchmark code to generate other source code which is then compiles and run (or rather the plugin does) -
this complicates things.

For this reason it's important to keep the actual code under test outside the benchmark classes to avoid profiling generated
source code which may skew the figures

JIT complications
-------------------

The JIT compiler is VERY clever, and it will do all sorts of clever things. One challenge when writing micro benchmarks
is ensuring that the JIT compiler will not strip out our "dead" code. For example this is dead code:

```
public int doStuff() {
  int firstNumber = 10;
  int secondNumber = getSecondNumber(); // dead code (assuming no side effects)
  return firstNumber;
}
```

Whilst we would hopefully not write dead code in the real world we may do this during a profiling run simply to measure
the start and end times so we need to trick the JIT into thinking that we actually need the result of the particular operation.
See [this post](http://java-performance.info/jmh/) for more information about the challenges of micro profiling. JIT
magic is easy to spot though - If your profiling results look amazing the JIT has probably dropped your code

repository: thobson/scala-collection-benchmarks

repo_name: thobson/scala-collection-benchmarks


text:
---
title: "Our Daily Reading List - 02/01/2018"
author<EMAIL_ADDRESS>tags: ["margaret","Daily Readings"]
date: 2018-01-02 09:50:57
description: "1

Holder Claims: Potential Causes of Action in Delaware and Beyond? - by Edward T. McDermott #corporate #law @HarvardCorpGov Read Here

2

How Preliminary Examiners Could Improve #Corporate Go..."
---

[https://clausehound.com/](https://clausehound.com/)

1

### Holder Claims: Potential Causes of Action in Delaware and Beyond? - by Edward T. McDermott #corporate #law @HarvardCorpGov [Read Here](https://goo.gl/gBYtQ5)

2

### How Preliminary Examiners Could Improve #Corporate Governance for Companies in Bankruptcy - by Stefan Korch @CLSBlueSkyBlog #law [Read Here](https://goo.gl/gtrWVA)

Annotated Legal Contracts
for the Price of a Coffee

3

### Tax Reform Impact on Employers and Employees - by Paul S. Drizner & Michael Lobie @lexology #commercial #law [Read Here](https://goo.gl/UvaEnC)

4

### Lawyers and accountants turn to #legal #technology for real estate issues - by @ItsJustAlexCoop @CompDealerNews [Read Here](https://goo.gl/5ZsHuR)

5

### Legal tech entrepreneurs talk success strategies for 2018 - by @AriKaplan #socent #law[Read Here](https://goo.gl/mJKYZL)

repository: sahilkanaya/clausehound-blog

repo_name: sahilkanaya/clausehound-blog


text:
---
layout: post
title:      "In a Sinatra state of mind"
date:       2018-02-25 00:02:55 -0500
permalink:  in_a_sinatra_state_of_mind
---

First off, I'd like to point out that the preparation leading up to this project was very well  designed. All the labs and lessons did just want they were meant to: teach about the structure of an app, how to set up the controllers, the views, models, and database. How to get all the gears turning and working together!

Learning how all the diferent parts of an app communicate with eachother, exchanging information whilst taking user input and producing an output is a wild ride. It's truly magical what goes on under the hood, and onece you've learned how to control it, manipulate it, and enhance it you become limitless! Sinatra is definitely an exceptional manual and light-weight framework to get started on when building your first MVC application. I really enjoyed the whole Sinatra section, especially this final project assigmnet.

I built an app called Soccer Training Tracker which basically allowes you to keep a record of all your favorite training drills, as well as drills from other players and coaches. I really enjoyed this assigment, especially the styling process!

Here's the video walkthrough: https://youtu.be/VvM2-LQ-xI8

extension: markdown


text:
---
layout: default
---

# 1995-09-23 - More on "Entropy"

## Header Data

From<EMAIL_ADDRESS>(Timothy C. May)

To<EMAIL_ADDRESS>Message Hash: 4f8e446dd2e9259d77913bb3ab39bcf14a5e75a144abe7b47441d73c81fda250

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1995-09-23 01:45:16 UTC

Raw Date: Fri, 22 Sep 95 18:45:16 PDT

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(Timothy C. May)
Date: Fri, 22 Sep 95 18:45:16 PDT
To<EMAIL_ADDRESS>Subject: More on "Entropy"
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

At 6:46 PM 9/22/95, David Van Wie wrote:

>Having overcome my initial skepticism on the entire topic of entropy, based
>on the useful pointers to the literature I have received, I agree
>wholeheartedly with the need for _positive_ design criteria against which
>designs may be evaluated.  For initial consideration, I recommend the
>following:
>
>The entropy E is defined by the sum across n states of -P_i log_2(P_i),

Hah! Another physicist converted to the information-theoretic view of entropy!

I should've pointed out in my reading list that several names stand out in
this interpretation:

- Charles Bennett

- Rolf Landauer

- John Wheeler

Just so you know.

ObNetscapeHack: None.

--Tim May

Notice: Don't expect me to reply to trivial questions and complaints.
---------:---------:---------:---------:---------:---------:---------:----
Timothy C. May              | Crypto Anarchy: encryption, digital money,
<EMAIL_ADDRESS>408-728-0152 | anonymous networks, digital pseudonyms, zero
Corralitos, CA              | knowledge, reputations, information markets,
Higher Power: 2^756839      | black markets, collapse of governments.
"National borders are just speed bumps on the information superhighway."

{% endraw %}
```

## Thread

+ Return to [September 1995](/archive/1995/09)

+ Return to<EMAIL_ADDRESS>(Timothy C. May)](/authors/tcmay_at_got_net_timothy_c_may_)"

+ 1995-09-23 (Fri, 22 Sep 95 18:45:16 PDT) - More on "Entropy" -<EMAIL_ADDRESS>(Timothy C. May)_


text:
# Prerequisites

## Prior Knowledge In Tech

DevOps isn't an entry level role by any means if it's being done correctly. There's a lot of knowledge you need prior, including:
- Some sort of cloud engineering/cloud knowledge experience. Although not all environments are running in the cloud, most of these roles will want it.
- Scripting/automation/programming experience. You don't have to go out and write the next Twitter, but you should understand the basics of programming.
- Network, storage, and compute knowledge.
- Held a prior systems administration, infrastructure engineer, or cloud engineer role.

## AWS Account

### Create An AWS Account

To follow along with this tutorial, you should have an AWS account. If you don't already have one, you can sign up for a free 12 month trial [here](https://aws.amazon.com/free/?all-free-tier.sort-by=item.additionalFields.SortRank&all-free-tier.sort-order=asc&awsf.Free%20Tier%20Types=*all&awsf.Free%20Tier%20Categories=*all).

You should know that the tutorial for *DevOps The Hard Way* will cost money because some of the services that you use in AWS will not be part of the free tier.

To learn more about the AWS Pricing Model so you understand what the cost will be, you can go [here](https://aws.amazon.com/pricing/)

### Use the AWS CLI

The AWS CLI is a way for you to interact with all AWS services at a programmatic level using the terminal.

To set this up, follow the directions [here](https://docs.aws.amazon.com/polly/latest/dg/setup-aws-cli.html)

## Installations
You will need to download some software and services for this tutorial.

### Code Editor

Because code will be written for *DevOps The Hard Way*, you will need a code editor. For the purposes of this tutorial, you can use [Visual Studio Code](https://code.visualstudio.com/download), which is a free code editor.

### Terraform

[Terraform Download](https://www.terraform.io/downloads.html)

### Docker
To build the Docker image, you can use Docker Desktop for Windows or MacOS.

[Docker Desktop](https://www.docker.com/products/docker-desktop)

### Source Control
To store the code that you'll be writing, you can create your very own GitHub account to showcase your project.

[GitHub](https://www.github.com)


text:
# ADS1256
Arduino Library for Texas Instrument ADS1256, working with Arduino IDE 1.8.5, Arduino UNO

# Installation
As any arduino library (import library)

# Wiring
ADS Board   -     Arduino UNO Board

5V          -     5V

GND         -     GND

SCLK        -     pin 13 (SCK)

DIN         -     pin 11 (MOSI)

DOUT        -     pin 12 (MISO)

DRDY        -     pin 9

CS          -     pin 10

POWN       -      5V

# Examples
Basic_Switching_Channel: How to change the channels

ADS1256_Efficient_Input_Cycling: Read and print

# Functions

ADS1256 adc(clockSpeed in Mhz, VREF in volt, boolean if use RESET PIN ): Class Constructor:

adc.sendCommand(SDATAC): Send SDATAC to stop reading contionus data, so we can send other command

adc.waitDRDY(): Waits for the data ready flag (ADC conversion ended and ready to be read)

adc.setChannel(x): Sets the channels to be read in next reading cycle, configured in "single end" (reads between the "x" input AINx and ground GND)

adc.setChannel(i,j): Sets the channels to be read in next reading cycle, configured in "differential mode", first argument (i) is the positive input and second argument (j) is negative input to ADC. As stated in device datasheet any combination (i,j) (between 0 and 7) is possible but it's recomended to use adjacent inputs (0 and 1, 2 and 3, etc)

adc.readRegister(reg): Returns value of the register "reg"

adc.readCurrentChannel(): Returns the value of the current reading stored in ADC

#Notice: Working as 5/1/2019


text:
# Lycoperdon molle var. atropurpureum (Vittad.) F. Šmarda, 1958 VARIETY

#### Status
SYNONYM

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
Fl. CSR, Gasteromycet. 350 (1958)

#### Original name
Lycoperdon atropurpureum Vittad., 1842

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Basidiomycota/Agaricomycetes/Agaricales/Agaricaceae/Lycoperdon/Lycoperdon atropurpureum/ Syn. Lycoperdon molle atropurpureum/README.md

repo_name: mdoering/backbone


text:
---
layout: page
title: Installation
---
## You spend good money on good appliances
Make sure your new appliances are installed correctly by calling Budget Appliance Service. We will make sure they are connected to their electrical and water sources properly to ensure proper operation and prevent any damage. Don't risk doing it yourself; trust the professionals with over a decade of experience.

## Keep your appliances running smoothly
If you start to hear odd noises from your home appliances, or notice a spike in
your utility bill, they may need to be checked out. Contact us to set up a service call
to diagnose the problem. Prevent further damage and repairs and call Budget Appliance Service at<PHONE_NUMBER>.

## Installation for all home appliances

* Washing machines
* Dryers
* Refrigerators
* Freezers
* Ranges
* Dishwashers

Discounts Available: Military Discounts, Senior Discounts, and Foster Care Provider Discounts available.

repository: fiatinsight/budget-appliance-services

repo_name: fiatinsight/budget-appliance-services


text:
opic
====

[![GoDoc](https://godoc.org/fknsrs.biz/p/opic?status.svg)](https://godoc.org/fknsrs.biz/p/opic)

Overview
--------

OPIC stands for "On-Line Page Importance Computation". This package implements
the adaptive form of the algorithm, and atop that, some functions for
approximating the static form.

License
-------

3-clause BSD. A copy is included with the source.

repository: deoxxa/opic

repo_name: deoxxa/opic


text:
# Contributing

> :exclamation: Before you will run a pull request and make changes to the code, just create an [issue](https://github.com/m1ner79/twitterGitHubActions/issues) and let's chat what would you wish to change.

## Pull Requests

1. Fork and clone the repository.
2. Configure and install the dependencies.
3. Create your branch from master.
4. Make your changes in the code.
5. Run tests: `npm test`, and fix any code issues with `npm run lint-fix`.
6. Now you are ready to issue that pull request.

 Terms like `pull, fork, clone` scare you :scream:. Have no fear :muscle:, because all the help is just a :point_right: [click](https://help.github.com/en) away. It is the link to GitHub Help page where you can find everything you need to help you out :tada:.

repository: derberg/twitterGitHubActions

gha_language: JavaScript

repo_name: derberg/twitterGitHubActions


text:
# 0.4.2

* fix executable detection on Windows

# 0.4.1

* fix extraction on Windows

# 0.4.0

* support hugo version 0.18.1 and above

# 0.3.2

* handle environments with node installed as `nodejs`

# 0.3.1

* fix executable not found on Windows

# 0.3.0

* make hugo version configurable via `process.env.HUGO_VERSION`

# ...

Check `git log` for earlier history.

repository: Logikgate/hugo-cli

repo_name: Logikgate/hugo-cli


text:
---
author: dparzych
comments: false
date: 2019-04-16 19:56:08+00:00
layout: post
link: https://launchdarkly.com/blog/trajectory-sponsor-highlights/
slug: trajectory-sponsor-highlights
title: 'Trajectory: Sponsor Highlights'
wordpress_id: 193851
categories:
- DevOps
- Team & News
tags:
- Dev Ops
- developer tools
- ecosystem
- partners
- Trajectory
---

Modern development teams use a plethora of tools to support all aspects of the software delivery lifecycle. There is no single tool or solution that will support all of your needs. You need an ecosystem of tools that work together to support your engineering, testing, deployment, and operations processes. Our Trajectory sponsors included some of the tools in the ecosystem that help with these modern development processes. I took some time at Trajectory to speak with the sponsors and learn about their offerings.

Sponsors are a critical component for a conference. Sponsors can help to reduce the cost of tickets to attendees, they provide food and beverages, and they provide opportunities for additional learning. I encourage you the next time you attend a conference to stop by the sponsors and see what they have to teach you.

## Code Climate

[Code Climate](https://codeclimate.com/) helps engineering teams visualize all steps of the engineering process and make data-driven decisions. They collect metrics from Git, tickets, and static information to create visualizations to help build high performing engineering teams. These visualizations help engineering teams see and understand what is happening. To learn more about Code Climate, consider attending their [one-day engineering leadership summit ](https://codeclimate.com/summit/)on May 22nd in San Francisco.

## Gremlin

[Gremlin](https://www.gremlin.com/) provides a full suite of tools for Chaos engineering. Chaos engineering was described to me like building resistance to the flu–you inject faults into your system to help build resilience. Running regular chaos experiments helps companies minimize risk by identifying where processes need to be improved or faults remedied. To get started with chaos engineering, Gremlin offers a free version which executes shutdown and CPU attacks. Gremlin's [ChaosConf](https://www.gremlin.com/chaos-conf-2019/) is on September 26th in San Francisco where you can learn about overcoming obstacles to deploy chaos engineering and how to achieve five nine's availability.

## Honeycomb

[Honeycomb](https://www.honeycomb.io/overview/) offers complete observability of software and systems via logs, events, and traces to help companies build better software and resolve issues faster. With Honeycomb you know how production systems behave in real time. You can ask questions of your data and systems to understand whether a feature flag should be toggled off due to unexpected behavior. Observability from Honeycomb is where you go after you graduate from monitoring. Follow [Honeycomb on Twitter](https://twitter.com/honeycombio) to stay up to date on the latest observability trends.

## Percy

[Percy](https://percy.io/) offers automated testing to identify visual changes in new applications and ensure builds and code changes are shipped without visual bugs. With Percy, you can see how an application looks with a feature flag enabled or disabled. In addition to being a sponsor of LaunchDarkly they are also a customer. They recently published a blog on how they use [feature flags and visual testing](https://blog.percy.io/using-feature-flags-and-visual-testing-together-for-complete-launch-confidence-7429379cce0a) to gain confidence in testing feature flag variations.

## The New Stack

[The New Stack](https://thenewstack.io/) publishes articles and podcasts about the services and infrastructure used by modern development teams. TC Currie correspondent from The New Stack was in attendance and shared her learnings on [The Context Podcast](https://thenewstack.io/context-launchdarklys-trajectory-google-cloud-next/).

repository: papistan/gatsby-starter-netlify-cms

repo_name: papistan/gatsby-starter-netlify-cms


text:
## Introduction

This page is to list some of the more important guidelines for developers **contributing code to osmdroid**.  This is not intended to strictly enforce a particular style - more to keep the code internally consistent.

### General guidelines

 * Use spaces for indenting, not tabs (**recent change**)
 * Make variables final where possible
 * Prefix member variables with m
 * Prefix method arguments with p
 * Versions <= 4.3, Use org.slf4j.Logger. Verions > 4.3 use android.util.Log
 * Use 100 character line width
 * Use final wherever possible, especially parameters
 * Eclipse formatting and clean-up XML settings files (both of which cover most of the above) are included in the repository. Import them, and use them to make your life easier!

### Guidelines for osmdroid-android project

Test your app with a device or emulate

`mvn clean install` - NOTE Maven has been broken for Android builds since Apr 2016

or with gradle

`gradle clean install connectedCheck`

## Building

Make sure you build with the follow commands before opening a pull request. There are several related wiki pages on setting up the development environment. See https://github.com/osmdroid/osmdroid/wiki/How-to-build-OsmDroid-from-source

```` gradle clean install connectedCheck ````

repository: chenzhengjun/osmdroid

repo_name: chenzhengjun/osmdroid


text:
---
title: "Relation generator"
lang: en
layout: page
keywords: LoopBack
tags:
sidebar: lb2_sidebar
permalink: /doc/en/lb2/Relation-generator.html
summary:
---

{% include content/generator-create-app.html lang=page.lang %}

The models involved in the relation must also exist before running this generator.

### Synopsis

Creates a new [model relation](/doc/{{page.lang}}/lb2/Creating-model-relations.html) in a LoopBack application.

```shell
$ [slc | apic] loopback:relation [options]
```

### Options

`-h, --help`
Print the generator's options and usage.

`--skip-cache`
Do not remember prompt answers. Default is false.

`--skip-install`
Do not automatically install dependencies. Default is false.

### Interactive Prompts

The tool will prompt you for:

* Name of the model to create the relationship from.
* Relation type:
  * [HasMany](/doc/{{page.lang}}/lb2/HasMany-relations.html)
  * [BelongsTo](/doc/{{page.lang}}/lb2/BelongsTo-relations.html)
  * [HasAndBelongsToMany](/doc/{{page.lang}}/lb2/HasAndBelongsToMany-relations.html)
  * [HasOne](/doc/{{page.lang}}/lb2/HasOne-relations.html).
* Name of the model to create a relationship with.
* Name for the relation (property name).

{% include important.html content="The name of the relation must be different than a property it references.
" %}

* Custom foreign key (optional)
* Whether a "through" model is required.  Repy "Y" to create a [HasManyThrough relations](/doc/{{page.lang}}/lb2/HasManyThrough-relations.html).
* Name of the "through" model, if appropriate.

### Output

Updates the [Model definition JSON files](/doc/{{page.lang}}/lb2/Model-definition-JSON-file.html) for the models involved in the relation.

branch_name: refs/heads/gh-pages


text:
# Helmbet-RPS

- using [websocket-sharp](https://github.com/sta/websocket-sharp);

- using [SimpleBase](https://github.com/ssg/SimpleBase.git);

- using [Newtonsoft.Json](https://github.com/JamesNK/Newtonsoft.Json.git);

- using [HtmlAgilityPack](https://github.com/zzzprojects/html-agility-pack);

This is a BETA release of the HelmBet RPS application, powered by [Peerplays](https://peerplays.com) blockchain.

Note: there is know issue with wss connection to the testnet, please use ws as of now, Issue will be fixed in next version.

Testnet details
Chain id: be6b79295e728406cbb7494bcb626e62ad278fa4018699cf8f75739f4c1a81fd

Node: wss://node.ppytest.com

- Register Account: http://paperwallet.ppytest.com

- Please use 22 symbols as a password when registering a new account.

### Getting Started

- There is a NetworkManager gameObject available on the scene, that also includes Connection Managing that is monitoring socket-connections with the node.

- Api Manager is a component required for access to the Peerplays blockchain API.

- NodeManager required for adding, storing and selection of the node to be used for the application. It also contains default node connection. Last selected address is kept in device memory and is used by default next time application started.
To restore this parameter in EditorMode: set ReserAtStart chekbox and press Play; in RunMode: call ConnectTo( host,  resultCallback ) or set property SelecteHost by new host.

### Detect Chain ID

In the ChainConfig class there is a list of supported chainIDs. If you need to add new chain id or remove existing - you can edit this configuration.

###The MIT License###

Copyright (c) 2017 Pacatum, Inc., and contributors.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

repository: pacatum/Helmbet-RPS

repo_name: pacatum/Helmbet-RPS


text:
# Lambda Validation with Firebase

Using the Amazon template, this shows how to valdiate a Firebase token (https://firebase.google.com/docs/auth/admin/verify-id-tokens) with NodeJs and a Lambda function.  This can then be used in API Gateway to validate API usage.

## Getting Started

* Clone this repository.
* Run npm install from the project root.
* Zip the following:
 * node_modules
 * package.json
 * server.js

In AWS, create a new Lambda function.

* Set the following environment variables under the Advanced section of the Code tab.
 * firebaseUrl - https://[appname].firebaseio.com
 * firebasePrivateKey - from property 'private_key' of the private key json file
 * firebaseClientEmail - from property 'client_email' of the private key json file
 * firebaseProjectId - from property 'project_id' of the private key json file
 * See the Admin Setup from Firebase docs (https://firebase.google.com/docs/admin/setup) on how to setup admin access.
* Upload the zip file of code on the Code tab; once uploaded to you can edit the code via the inline Lambda editor.
* Configure the test input.

```javascript
{
  "authorizationToken": "",
  "methodArn": "arn:...../*/GET/",
  "type": "TOKEN"
}
```

## AuthorizationToken

The authorization token can be fetched from via the following snippet:

```javascript
firebase.auth().currentUser.getToken(/* forceRefresh */ true).then(function(idToken) {
  // Send token to your backend via HTTPS
  // ...
}).catch(function(error) {
  // Handle error
});
```

See https://firebase.google.com/docs/auth/web/google-signin#redirect-mode for more info.

## License

MIT License

Copyright (c) 2017 thZero.com

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

repository: ziomarco/LambdaValidationFirebase

repo_name: ziomarco/LambdaValidationFirebase


text:
# Digital-electronics-1

## Labs
### 01-gates
[Labs 01-gates](https://github.com/xhruby28/Digital-electronics-1/tree/main/Labs/01-gates)

[Labs 02-logic](https://github.com/xhruby28/Digital-electronics-1/tree/main/Labs/02-logic)

[Labs 03-vivado](https://github.com/xhruby28/Digital-electronics-1/tree/main/Labs/03-vivado)

[Labs 04-segment](https://github.com/xhruby28/Digital-electronics-1/tree/main/Labs/04-segment)

[Labs 05-counter](https://github.com/xhruby28/Digital-electronics-1/tree/main/Labs/05-counter)

[Labs 06-display_driver](https://github.com/xhruby28/Digital-electronics-1/tree/main/Labs/06-display_driver)

[Labs 07-ffs](https://github.com/xhruby28/Digital-electronics-1/tree/main/Labs/07-ffs)

[Labs 08-traffic_lights](https://github.com/xhruby28/Digital-electronics-1/tree/main/Labs/08-traffic_lights)

## VHDL Operators
| **Operator** | **Description** |
| :-: | :-- |
| `<=` | Value assignment |
| `and` | Logical AND |
| `nand` | Logical AND with negated output |
| `or` | Logical OR |
| `nor` | Logical OR with negated output |
| `not` | Nagation |
| `xor` | Exclusive OR |
| `xnor` | Exclusive OR with negated output |
| `-- comment` | Comments |

**Source code**

``` vhdl

```

### *Links*

-[Git manual 1](https://medium.com/swlh/how-to-make-the-perfect-readme-md-on-github-92ed5771c061)

-[Git manual 2](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax)

-[Git manual 3](https://guides.github.com/features/mastering-markdown/)


text:
# Pdftotext

*A Ruby wrapper for the `pdftotext` command line library*

[![Build Status](https://travis-ci.org/benbalter/pdftotext.svg)](https://travis-ci.org/benbalter/pdftotext)

## Installation

1. You must first install [Poppler](http://poppler.freedesktop.org/). On OS X this can be done with `brew install poppler` if you have Homebrew installed
2. Add `gem pdftotext` to your project's Gemfile
3. `bundle install`

## Usage

```ruby
text = Pdftotext.text('path-to.pdf')
=> "The text of the PDF"

pages = Pdftotext.pages('path-to.pdf')
pages.first.number
=> 1
pages.first.text
=> "The text of the PDF"
```

Both methods take an optional hash of command line arguments to pass to `pdftotext`. The only one by default being `-layout`.

gha_language: Ruby


text:
Trained Gym Agents!

------

## Description:

This repository contains the trained agents for gym environments.

## Dependencies:

- Python 3.6
- Tensorflow ≥ 1.12

## Content
- [Pong-v0](./pong_dqn)

## Citing gym_agents

If you use gym_agents in your research or wish to refer to the examples, please cite with:

```
@misc{gym_agents2019gym_agents,
  title={gym_agents},
  author={Huang, Shiyu and others},
  howpublished={\url{https://github.com/huangshiyu13/gym_agents}},
  year={2019}
}
```

## Contribution

We always welcome contributions to help make gym_agents better. If you would like to contribute, please  contact huangsy13 at gmail dot com


text:
### The Archive Bundle ID (`the_archive_bundle_id`)

> Default value: `de.zettelkasten.TheArchive`

A bundle ID (or bundle identifier) uniquely identifies an application in Apple's ecosystem. This means that no two applications can have the same bundle identifier.

This workflow uses the bundle identifier together with [the_archive_team_id](#the-archive-team-id-the_archive_team_id) to get the saved preferences of The Archive.

This value should never need changing.

repository: ehehalt/alfred-the-archive

repo_name: ehehalt/alfred-the-archive


text:
---
layout: posts
title: XA Transactions in 2PC
tags:
 - XA
 - MobileInternet
---
# Description

- 2 phase commit protocol referred to as XA(eXtended Architecture)
- This protocol provides ACID-like properties for global transaction processing
- 2 phase commit protocol is an atomic commitment protocol for distributed systems.
- The first one is commit-request phase in which transaction manager coordinates all of the transaction resources to commit or abort.
- In the commit-phase, transaction manager decides to finalize operation by committing or aborting according to the votes of the each transaction resource.
- XA transactions need a global transaction id and local transaction id(xid) for each XA resource.
- Each XA Resource is enlisted to XA Manager by start(xid) method.
- This method tells that XA Resource is being involved in the transaction(be ready for operations).
-  the first phase of the 2PC protocol is realized by calling prepare(xid) method. This method requests OK or ABORT vote from XA Resource.
- After receiving vote from each of XA Resource, XA Manager decides to execute a commit(xid) operation if all XA Resources send OK or decides to execute a rollback(xid) if an XA Resource sends ABORT.
- Finally, the end(xid) method is called for each of XA Resource telling that the transaction is completed.

Reference links:

1. (DZone XA 2PC)[https://dzone.com/articles/xa-transactions-2-phase-commit]


text:
# Movie_Trailer_Project
Movie Trailer Website is designed for users to see their favorite movies and watch the trailers.

# Prerequisities
* Python 2.x
* Web Broswer( Chrome, Firefox,Internet Explorer,Safari )

# Installing
* Get started by downloading Python here https://www.python.org/downloads/
* Step by Step Guide to install Python on Windows http://www.howtogeek.com/197947/how-to-install-python-on-windows/
*  Step by Step Guide to install Python on Mac http://docs.python-guide.org/en/latest/starting/install/osx/

# Deployment
* Open enteriament.py module
* Click on "Run"
* Run Module F5
* Then Movie Trailer Website opens

# Authors

* **Lakshmi Sharanya**

See also the list of [contributors](https://github.com/LakshmiSharanya/Movie_Trailer_Project/commit/dcdb9b65b7c684715dfb53d1393e473a6281f04d) who participated in this project.

# Contributing
Please read [CONTRIBUTING.md](https://github.com/LakshmiSharanya/Movie_Trailer_Project/commit/dcdb9b65b7c684715dfb53d1393e473a6281f04d) for details on our code of conduct, and the process for submitting pull requests to us.

# License
This project is licensed under the MIT License - see the [LICENSE.md](https://github.com/LakshmiSharanya/Movie_Trailer_Project/blob/master/LICENSE) file for details


text:
# Conversation Last Read Time For XenForo 2.1.7+
This add-on adds "Last Read Date" next to each conversation participants.

## Permissions
- "View last read time" under Admin > Groups & permissions > [Usergroup] > Conversation permissions

## License
This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details

gha_language: PHP


text:
---
title: Framework Integration
description: Framework Integration
url: /docs/overview
contributors:
  - adamdbradley
  - brandyscarney
---

# Framework Integration

Stencil's primary goal is to remove the need for components to be written using a specific framework's API. It accomplishes this by using standardized web platform APIs that work across all modern browsers. Using the low-level component model that is provided by the browser (which all frameworks are built on) allows Stencil components to work inside of a framework or without one.

Stencil's integration with different frameworks is currently a work in progress. As Stencil matures, the goal is to make it easy to write standard web components which will compile to various output targets. This allows developers to stay aligned with the latest web standards while using a common API. The generated components will also be more future-proof as frameworks continue to change.

The following list contains the framework integrations that have been started. All of them are not yet completed.

[Angular](angular)

[React](react)

[Vue](vue)

[Ember](ember)

repository: dgautsch/stencil-site

repo_name: dgautsch/stencil-site


text:
# receive-post
Simple example to receive post request from UserEngage API Call

---------------------

- `yarn`, install all dependencies
- `yarn start` start dev server

repository: UserEngage/receive-post

repo_name: UserEngage/receive-post


text:
## Kafka sidecar sample light-4j API

This is sample backend API for Kafka sidecar. It build with light-4j and it only use for reference purpose.

Fo the local testing, please refer to  kafka sidecar readme:

https://github.com/networknt/kafka-sidecar

### Endpoint includes:

- path: '/kafka/records'

  method: 'POST'

Kafka sidecar Reactive consumer backend API. In the kafka sidecar kafka-consumer.yml config file, user can specify the backend API host url and API path:

```text
kafka-consumer.backendApiHost: http://localhost:8080
kafka-consumer.backendApiPath: /kafka/records
```
When the Reactive consumer consume the records from kafka, it will call backend API to process the event messaage.

-----------
- path: '/kafka/ksqldb'

  method: 'GET'

API endppoint to call kafka sidecar KsqlDB active consumer endpoint to run ksql pull/push query.

Queries are defined in the values.yml:

```text
api-config.apiQuery:
  userQuery: select * from QUERYUSER1\

```

Pass the 'queryname' as required query parameter, and 'id' is option parameter.

if id parameter is not provided, the ksql query will run as full table scan.

To test this endpoint, please refer kafka-sidecar to create ksql TKable (QUERYUSER1) (CREATE TABLE AS SELECT...) on kafka:

https://github.com/networknt/kafka-sidecar/blob/master/doc/ksql.md

Sample request curl command:

```text
curl --location --request GET 'https://localhost:8444/kafka/ksqldb?queryname=userQuery&id=1' \
--data-raw '';
```

--------

- path: '/kafka/dlq/active/producer'

  method: 'GET'

Procedure the error message to dead letter queue actively.

Request sample:

```json
curl --location --request POST 'https://localhost:8444/kafka/dlq/active/producer' \
--header 'X-Traceability-Id: 111111' \
--header 'Content-Type: application/json' \
--data-raw '[
    {
        "record": {
            "topic": "test6",
            "key": "YWxleA==",
            "value": "xyz",
            "partition": 0,
            "offset": 0
        },
        "processed": false,
        "stacktrace": "error happened",
        "correlationId": "cccc-1111111",
        "traceabilityId": "tttt-1111111",
        "key": "YWxleA=="
    },
        {
        "record": {
            "topic": "test7",
            "key": "YWxleA==",
            "value": "xyz",
            "partition": 0,
            "offset": 0
        },
        "processed": false,
        "stacktrace": "error happened",
        "correlationId": "cccc-1111111",
        "traceabilityId": "tttt-1111111",
        "key": "YWxleA=="
    }
]'
```

branch_name: refs/heads/release

gha_language: Java


text:
Saving and loading memory is quite easy on the VIC-20 once you know how.  However, it isn't obvious how to do this and therefore this article will present a few simple ways of doing it from BASIC and Assembler.

## Saving/Loading from BASIC a Byte at a Time

A straight forward way to save and load memory from BASIC is to use the `OPEN`, `PRINT#` and `GET#` commands to write or read a byte at a time.

### Saving

In the following file we are saving memory at _673-692_ to '_FLASH.PRG_' on device 8.  If we wanted to save it to a .SEQ file then we would use `FLASH,S,W`.  We use `CHR$` to convert the byte to PETSCII which the `PRINT#` command will then convert back to its byte representation when writing to the file.  One interesting thing to note is that even though this is saving to a .PRG file it doesn't save the load address.  If we want this included in the file then we need to start it with two bytes representing the LSB/MSB of the load address.

```
10 OPEN 8,8,1,"FLASH,W"
20 FOR I=673 TO 692
30 B=PEEK(I)
40 PRINT#8, CHR$(B);
50 NEXT I
60 CLOSE 8
```

### Loading

The following program will load '_FLASH.PRG_' into locations 673-692 from device 8.

```
10 OPEN 8,8,0,"FLASH"
20 FOR I=673 TO 692
30 GET#8, B$
40 POKE I,ASC(B$)
50 NEXT I
60 CLOSE 8
```

If the file contains the origin address as the first two bytes then we can use that if desired.  We have to be careful that the origin address isn't where our tokenized basic program is being stored.  This allows us to load a memory block without corrupting a running BASIC program.  In the following `ST` is the status after certain I/O operations and is used here to detect the end of file by checking if it is equal to 64.

```
10 OPEN 8,8,0,"FLASH,R"
20 GET#8, O1$
30 GET#8, O2$
40 O=ASC(O1$)+256*ASC(O2$)
50 PRINT "ORIGIN: ";O
60 GET#8, B$
70 IF ST<>0 AND ST<>64 GOTO 200
80 POKE O,ASC(B$)
90 O=O+1
100 IF ST<>64 GOTO 60
110 CLOSE 8
120 END
200 PRINT "ERROR STATUS: ";ST
210 CLOSE 8
```

## Using the SAVE/LOAD Commands in BASIC

BASIC has built-in commands to save and load programs which we can use to save and load our block of memory.

## Saving

We can use the `SAVE` command in BASIC to save a block of memory by telling the Vic that the tokenized BASIC area is located at the same block of memory that we want to save.

The following example saves a block of memory at 673-692 to '_FLASH.PRG_' on cassette (device 1).   The start address is stored at 43/44 ($2B/2C) which indicates the start of tokenized BASIC in LSB/MSB order.  The end address is stored at 45/56 ($2D/$2E) which indicates the end of tokenized BASIC in LSB/MSB order.

``` basic
POKE 44,673/256:POKE 43,673-256*PEEK(44)
POKE 46,692/256:POKE 45,692-256*PEEK(46)
SAVE "FLASH",1,1
```

This works well but because it alters the BASIC start and end points it can't be used from within a BASIC program.  We should reset the Vic or restore these locations to their original values once finished.  It should also be noted that this method saves the load/origin address to the first two bytes of the file because the final `,1` is at the end of the `SAVE` command.  On cassette this prevents the relocate function of the `LOAD` command but doesn't apply to disk.

### Loading

If we have saved a block of memory that had a start address and is a self-contained runnable program then we can simply use:

```
LOAD "FLASH",8,1
```

## SYS to BASIC/KERNEL ROM from BASIC

We can call BASIC/KERNEL ROM routines from BASIC using `SYS` to save and load blocks of memory in a way which will work within a BASIC program.  This method uses the BASIC ROM routine _PARSL_ at 57809 ($E1D1) which sets the LOAD, VERIFY and SAVE parameters and therefore is designed to process the rest of the parameters after it is called.  In this case `(N$),<device>`.  Locations 780, 781 and 782 are used to access the 6502 registers: A, X, Y.

From: [ROM Calls and Other Tricks on the Denial Forum](https://sleepingelephant.com/ipw-web/bulletin/bb/viewtopic.php?f=2&t=676&start=15&fbclid=IwAR3H8vVeiqckY-QcqzTRRJzLAKKA1PeKpucrHHvW7w8xCgvGf7RympzfAME#p75231)

### Saving

The following method saves memory to the filename in `N$`.  _end_ must be one past the address of the last byte to save.  This routine uses the KERNEL ROM routine _SAVE_ at 65496 ($FFD8) to perform the save.  It uses register A (location 780) to set the starting address store to 193.

```
N$="FLASH"
SYS57809(N$),<device>:POKE193,<start_lo>:POKE194,<start_hi>
POKE780,193:POKE781,<end_lo>:POKE782,<end_hi>:SYS65496
```

If we wanted to save the memory at 673-692 ($02A1-$02B4) to '_FLASH.PRG_' on device '8' and store the load address using `,1` it would look like the following.  The final `,1` after the device isn't actually used by disk but we may want to use it if saving to cassette (device 1).  We can also replace `(NS)` with the quoted filename:

```
SYS57809"FLASH",8,1:POKE193,161:POKE194,2
POKE780,193:POKE781,181:POKE782,2:SYS65496
```

### Loading

Loading is equally easy and in this case uses the KERNEL ROM routine _LOAD_ at 65493 ($FFD5) to perform the load.  If `,1` after device then it is forced to load at original address and pokes for `start_lo` and `start_hi` aren't needed.  Register A (location 780) is used to specify a LOAD (0) operation rather than a VERIFY (1) operation.

```
N$="FLASH"
SYS57809(N$),<device>:POKE780,0:POKE781,<start_lo>:POKE782,<start_hi>:SYS65493
```

Therefore if we want to load our '_FLASH.PRG_' program, saved previously, we can use the following to load it from device 8 into its original memory location:

```
SYS57809"FLASH",8,1:POKE780,0:SYS65493
```

## Assembly Routines for Saving and Loading

We can use some of the same routines used by the SYS calls above to load and save memory from assembly.  We first have to set up the device, file number and secondary address using the _SETLFS_ routine at $FFBA (65466) and then use the _SETNAM_ routine at $FFBD (65469) to set the filename.  Finally we call either the _LOAD_ or _SAVE_ routine after setting the start and end addresses appropriately of the memory block to load or save.

### Saving

The following routine would save block-blockend from memory to the file '_FLASH.PRG_' on drive 8.  The secondary address has no effect when being saved to disk but has the same effect as the BASIC `SAVE` command if saving to cassette.  It uses the same _SAVE_ routine at $FFD8 (65496) used above.

```
; KERNEL/BASIC ROM Routines
SAVE        = $FFD8
SETLFS      = $FFBA
SETNAM      = $FFBD

            LDA  #$08            ; Logical file number
            LDX  #$08            ; Device number
            LDY  #$01            ; Secondary address
            JSR  SETLFS          ; Set above parameters

            LDA  #$05            ; Length of file name
            LDX  #<filename      ; Low byte of file name location
            LDY  #>filename      ; High byte of file name location
            JSR  SETNAM          ; Set the name

            LDA  #<block         ; Low byte of start of memory block
            STA  $C1
            LDA  #>block         ; High byte of start of memory block
            STA  $C2

            LDA  #$C1            ; Pointer to location of start address
            LDX  #<(blockend+1)  ; Low byte of (end of memory block + 1)
            LDY  #>(blockend+1)  ; High byte of (end of memory block + 1)
            JSR  SAVE            ; Perform save
            BCS  error           ; Jump to error handler if error

            RTS

error       ; Handle error in A
            RTS

filename    .asc "FLASH"

            ; The two byte memory block to save
block       .byt $05
blockend    .byt $06
```

### Loading

The following routine would load the file '_FLASH.PRG_' from drive 8 to memory at location 673 ($02A1).  It uses the same _LOAD_ routine at $FFD5 (65493) used above.

```
block       = $02A1              ; Load address

; KERNEL/BASIC ROM Routines
LOAD        = $FFD5
SETLFS      = $FFBA
SETNAM      = $FFBD

main        LDA  #$08            ; Logical file number
            LDX  #$08            ; Device number
            LDY  #$00            ; Secondary address
                                 ; $00 Load using specifed address
                                 ; $01 Load using original address from file
            JSR  SETLFS          ; Set above parameters

            LDA  #$05            ; Length of file name
            LDX  #<filename      ; Low byte of file name location
            LDY  #>filename      ; High byte of file name location
            JSR  SETNAM          ; Set the name

            LDA  #$00            ; Load = 0, Verify = 1
            LDX  #<block         ; Low byte of start address
            LDY  #>block         ; High byte of start address
            JSR  LOAD            ; Perform load
            BCS  error           ; Jump to error handler if error

            RTS

error       ; Handle error in A
            RTS

filename    .asc "FLASH"
```

## Machine Language Monitors

To finish this off the last method I want to mention is loading and saving via a machine language monitor such as [VICMON](/articles/programming-in-assembly-with-vicmon-on-the-vic-20/ "TechTinkering article: Programming in Assembly with VICMON on the VIC-20").

### Saving

We can save in VICMON using the _S_ command.  The following example saves the memory at 673-692 ($02A1-$02B4) to '_FLASH.PRG_' on device '8'.  Note that we are using `02B5` as the end address because the end address for this command has to be one past the last byte that we want to save.  The .PRG file will be stored with its origin  address.

```
.S "FLASH",08,02A1,02B5
```

### Loading

To load a file we use the _L_ command which takes an optional device number. If the device number isn't specified then it defaults to 01 - the cassette.  In the following example we are loading '_FLASH.PRG_' from device 8 into the same memory location that it was saved from.

```
.L "FLASH",08
```

## Video

The following video shows these methods of saving and loading memory in action.


text:
The idea is to parse our #general channel for all posts that have the #eNews hashtag in a time range (1 week).

We'd then generate a newsletter from this feed.

Perhaps the newsletter will have different sections.

So far we have a `slack-scraper` module
 - This will return a json object that contains the information for a timeframe

TODO

Module to post this newsletter to slack?
Module to post this newsletter to email?

repository: haikuowuya/spikes

repo_name: haikuowuya/spikes


text:
# update_all사용시 audited 레코드가 추가안되는 문제

update_all은 Active Record callbacks을 거치지 않으므로 audited갱신 안되는게 당연함

Not sure if this is a bug or designed this way, but when I update an audited field on a active record relation using update_all, I am not getting audits created. Let me know if you need more info. I am using 4.2.

@domcleal

Collaborator
domcleal commented on 30 May 2017
I think this is reasonably documented in ActiveRecord: "It does not instantiate the involved models and it does not trigger Active Record callbacks". The audited gem is an AR extension so it does need the models and callbacks to work - performing an update directly against the database or with SQL-only methods like update_all won't create audits.

To get auditing support, you'll need to instantiate the models, i.e. relation.find_each { |model| m.update_attributes(..) }

https://qiita.com/yutaro50/items/96138a730a3eee812aa0
[update_all]: https://github.com/collectiveidea/audited/issues/352


text:
---
layout: post
title: "Stellar Battery on Oxygen OS"
date: "2016-03-15"
comments: true
tags: [geek]
draft: false
---

I have been getting stability issues with Cyanogen on my OPO lately, so I decided to give OnePlus's native [OxygenOS](https://oneplus.net/2/oxygenos) a whirl.
First I installed the initial version 1.0.0, which was kind of dated. I thought I could make my way into a newer
version via OTA updates, alas, no there is no OTA available for OPO it seems, which is kind of baffling.

So I flashed the newest version, which was [2.1.4](https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/). It's still a 5.1.1 Lollypop based build, but it was
much more better polished. And the battery life I get with this ROM is simply amazing :

{{< figure src="/images/opo_oxygenos_battery.png" title="OxygenOS Rulez" >}}

With the Cyanogen, I could make one day, but that's it. If I forget to charge at night, it would definitely be off
by morning. Cyanogen was good, but it went pretty straight downhill after they soldout to microsoft. I would
never consider using them for any of my devices, ever.


text:
---
layout: post
title: "Multi-Robot Patrolling with Sensing Idleness and Data Delay Objectives"
date: 2019-06-27 10:28:28
categories: arXiv_RO
tags: arXiv_RO Optimization Detection
author: Jürgen Scherer, Bernhard Rinner
mathjax: true
---

* content
{:toc}

##### Abstract
Multi-robot patrolling represents a fundamental problem for many monitoring and surveillance applications and has gained significant interest in recent years. In patrolling, mobile robots repeatedly travel through an environment, capture sensor data at certain sensing locations and deliver this data to the base station in a way that maximizes the changes of detection. Robots move on tours, exchange data when they meet with robots on neighboring tours and so eventually deliver data to the base station.
 In this paper we jointly consider two important optimization criteria of multi-robot patrolling: (i) idleness, i.e. the time between consecutive visits of sensing locations, and (ii) delay, i.e. the time between capturing data at the sensing location and its arrival at the base station. We systematically investigate the effect of the robots' moving directions along their tours and the selection of meeting points for data exchange. We prove that the problem of determining the movement directions and meeting points such that the data delay is minimized is NP-hard. We propose heuristics and provide a simulation study which shows that the cooperative approach can outperform an uncooperative approach where every robot delivers the captured data individually to the base station.

##### Abstract (translated by Google)

##### URL
[http://arxiv.org/abs/1906.11539](http://arxiv.org/abs/1906.11539)

##### PDF
[http://arxiv.org/pdf/1906.11539](http://arxiv.org/pdf/1906.11539)


text:
#Demo OptionalDependencies [![](https://raw.githubusercontent.com/novoda/novoda/master/assets/btn_apache_lisence.png)](LICENSE.txt)

OptionalDependencies shows how to create two product flavours that have different implementations of one method.

The demo uses a base class `BaseOptionalDependencies` that provides no-op methods and is used in the different flavours.
Each flavour only has to overwrite relevant methods for their flavour. This ensures that the main class `OptionalDependencies`
has the same signature in all flavours.

repository: thyrlian/android-demos

repo_name: thyrlian/android-demos


text:
# citrine-python
Python library for the Citrine Platform

## Installation
Clone from github:
```bash
git clone git@github.com:CitrineInformatics/citrine-python
```

Create a virtual environment using Python >= 3.6, and install requirements:
```bash
pip install -U -r requirements.txt
pip install -U -r test_requirements.txt
```

## Documentation

The documentation for this project is built using [Sphinx](http://www.sphinx-doc.org/en/master/).

### Building documentation

To build the documentation for this project, make sure you've installed all dependencies (core
and development) using pipenv. Once done:

```
cd docs/
make html
```

You can see the result by opening `docs/_build/html/index.html` in a web browser.

### Autogenerated docs

Sphinx supports generating documentation from docstrings, which is accomplished automatically
during the build step using sphinxcontrib-apidoc. The output of this process is stored in the gitignore'd
`docs/source/reference` directory. It's not stored in source control because it's generated from
the current state of the docstrings in the source code.

### Custom documentation

One of the outstanding features of sphinx is its support for arbitrarily organized documentation
materials such as tutorials, introductions, and other context providing content. These items should
be stored in source control under the `docs/source` directory in properly formatted `.rst` files.

repository: crleblanc/citrine-python

repo_name: crleblanc/citrine-python


text:
# DFHQ

[![CI Status](https://img.shields.io/travis/Arshad/DFHQ.svg?style=flat)](https://travis-ci.org/Arshad/DFHQ)
[![Version](https://img.shields.io/cocoapods/v/DFHQ.svg?style=flat)](https://cocoapods.org/pods/DFHQ)
[![License](https://img.shields.io/cocoapods/l/DFHQ.svg?style=flat)](https://cocoapods.org/pods/DFHQ)
[![Platform](https://img.shields.io/cocoapods/p/DFHQ.svg?style=flat)](https://cocoapods.org/pods/DFHQ)

## Example

To run the example project, clone the repo, and run `pod install` from the Example directory first.

## Requirements

## Installation

DFHQ is available through [CocoaPods](https://cocoapods.org). To install
it, simply add the following line to your Podfile:

```ruby
pod 'DFHQ'
```

## Author

Arshad<EMAIL_ADDRESS>
## License

DFHQ is available under the MIT license. See the LICENSE file for more info.

repository: arshadtp/DFHQ

repo_name: arshadtp/DFHQ


text:
---
layout: blog
title: The impostor syndrome and how to get rid of it
date: 2015-12-02T15:52:00.000Z
thumbnail: /images/uploads/1_93Y2rzyI3oCcSH52YsJygA.jpeg
description: >-
  My experience of going through impostor syndrome while learning how to
  program.
---
I have been learning how to program on my own for 7 months and all these months taught me that in the realm of programming the only constant is change.

This assertion correlated with my beginner state of programming level make me prone to the impostor syndrome. Every time I make some progress I have a feeling of accomplishment mixed with the fear of being a fraud. I feel like someone eventually will discover that everything I learnt so far is useless.

![](https://cdn-images-1.medium.com/max/800/1*CneEjtonrxI6JXICb8TQ8Q.png)

Two weeks ago I had my first programming interview. I have never been nervous before an interview, even though I prepared as well as I could. My performance was decent, but I could have done it better. Before every question I got the feeling that this will be the last question and the interviewer will find out I actually know nothing and he is wasting his time with me.

After the face to face interview, the home assignment part followed and I got an email with two assignments to solve in one week. I solved them and now I am waiting for an answer. During the solving part the nervousness appeared and once again I could have done it better.

The experience of my first programming interview is of paramount value because it taught me one important aspect of being a programmer. You cannot escape the impostor syndrome, but you can embrace it and endure the pain of the constant change. How can you embrace it? Quincy Larson, the founder of[FreeCodeCamp](http://www.freecodecamp.com/map), has a very good piece of advice on this one: “Remember that you are not your code”.

![](https://cdn-images-1.medium.com/max/800/1*HyK6m6InHZ_zWlBLNKTwsQ.png)

It is very important to get the ego out of the equation and looking at programming like a craft and looking at yourself like a craftsman whose purpose is to make good art and to better his craft everyday.

repository: alinalex/gatsby-starter-blog

repo_name: alinalex/gatsby-starter-blog


text:
# Traverse

OrientDB is a graph database. This means that the focal point is on relationships (links) and how they are managed. The standard SQL language is not enough to work with trees or graphs because it lacks the recursion concept. This is the reason why OrientDB provides a new command to traverse trees and graphs: TRAVERSE. Traversing is the operation that crosses relationships between records (documents, vertexes, nodes, etc). This operation is much much faster than executing a JOIN in a Relational database.

The main concepts of Traversal are:
- **target**, as the starting point where to traverse records. Can be:
 - **[class](Concepts.md#class)**
 - **[cluster](Concepts.md#cluster)**
 - **set of records**, specifying its [RecordID](Concepts.md#recordid)
 - **sub-command** that returns an Iterable<OIdentifiable>. You can nest multiple [select](SQL-Query.md) and [traverse](SQL-Traverse.md) all together
- **fields**, the fields to traverse. Use *, any() or all() to traverse all fields in a document
- **limit**, the maximum number of records to retrieve
- **predicate**, as the predicate to execute against each traversed document. If the predicate returns true, the document is returned, otherwise it is skipped
- **strategy**, indicates how the graph traversed:
 - *[DEPTH_FIRST](https://github.com/orientechnologies/orientdb/wiki/Java-Traverse#depth_first-strategy)*, the default,
 - *[BREADTH_FIRST](https://github.com/orientechnologies/orientdb/wiki/Java-Traverse#breadth_first-strategy)*,

### Traversing strategies
#### DEPTH_FIRST strategy
This is the default strategy used by OrientDB for traversal. It explores as far as possible along each branch before backtracking. It's implemented using recursion. To know more look at [Depth-First algorithm](http://en.wikipedia.org/wiki/Depth-first_search). Below the ordered steps executed while traversing the graph using *DEPTH_FIRST* strategy:

![Depth-first-tree](http://upload.wikimedia.org/wikipedia/commons/thumb/1/1f/Depth-first-tree.svg/600px-Depth-first-tree.svg.png)

#### BREADTH_FIRST strategy
It inspects all the neighboring nodes, then for each of those neighbor nodes in turn, it inspects their neighbor nodes which were unvisited, and so on. Compare **BREADTH_FIRST** with the equivalent, but more memory-efficient iterative deepening **DEPTH_FIRST** search and contrast with **DEPTH_FIRST** search. To know more look at [Breadth-First algorithm](http://en.wikipedia.org/wiki/Breadth-first_search). Below the ordered steps executed while traversing the graph using *BREADTH_FIRST* strategy:

![Breadth-first-tree](http://upload.wikimedia.org/wikipedia/commons/thumb/3/33/Breadth-first-tree.svg/600px-Breadth-first-tree.svg.png)

### Context variables

During traversal some context variables are managed and can be used by the traverse condition:
- **$depth**, as an integer that contain the depth level of nesting in traversal. First level is 0
- **$path**, as a string representation of the current position as the sum of traversed nodes
- **$stack**, as the stack current node traversed
- **$history**, as the entire collection of visited nodes

The following sections describe various traversal methods.

## SQL Traverse

The simplest available way to execute a traversal is by using the [SQL Traverse command](SQL-Traverse.md). For instance, to retrieve all records connected **from** and **to** **Movie** records up to the **5th level of depth**:
```java
for (OIdentifiable id : new OSQLSynchQuery<ODocument>("traverse in, out from Movie while $depth <= 5")) {
  System.out.println(id);
}
```

Look at the [command syntax](SQL-Traverse.md) for more information.

## Native Fluent API

Native API supports fluent execution guaranteeing compact and readable syntax. The main class is **OTraverse**:
- **target(<iter:Iterable<OIdentifiable>>)**, to specify the target as any iterable object like collections or arrays of OIdentifiable objects.
- **target(<iter:Iterator<OIdentifiable>>)**, to specify the target as any iterator object. To specify a class use database.browseClass(<class-name>).iterator()
- **target(<record:OIdentifiable>, <record:OIdentifiable>, ... )**, to specify the target as a var ars of OIterable objects
- **field(<field-name:string>)**, to specify the document's field to traverse. To add multiple field call this method in chain. Example: .field("in").field("out")
- **fields(<field-name:string>, <field-name:string>, ...)**, to specify multiple fields in one call passing a var args of Strings
- **fields(Collection<field-name:string>)**, to specify multiple fields in one call passing a collection of String
- **limit(<max:int>)**, as the maximum number of record returned
- **predicate(<predicate:OCommandPredicate>)**, to specify a predicate to execute against each traversed record. If the predicate returns true, then the record is returned as result, otherwise false. it's common to create an anonymous class specifying the predicate at the fly
- **predicate(<predicate:OSQLPredicate>)**, to specify the predicate using the SQL syntax.

In the traverse command context iContext you can read/put any variable. Traverse command updates these variables:
- **depth**, as the current depth of nesting
- **path**, as the string representation of the current path. You can also display it. Example: select $path from (traverse * from V)
- **stack**, as the List of operation in the stack. Use it to access to the history of the traversal. It's a List<OTraverseAbstractProcess<?>> where process implementations are:
 - **OTraverseRecordSetProcess**, usually the first one it's the base target of traverse
 - **OTraverseRecordProcess**, represent a traversed record
 - **OTraverseFieldProcess**, represent a traversal through a record's field
 - **OTraverseMultiValueProcess**, use on fields that are multivalue: arrays, collections and maps
- **history**, as the set of records traversed as a Set<ORID>.

### Example using an anonymous OCommandPredicate as predicate

```java
for (OIdentifiable id : new OTraverse()
              .field("in").field("out")
              .target( database.browseClass("Movie").iterator() )
              .predicate(new OCommandPredicate() {

    public Object evaluate(ORecord iRecord, ODocument iCurrentResult, OCommandContext iContext) {
      return ((Integer) iContext.getVariable("depth")) <= 5;
    }
  })) {

  System.out.println(id);
}
```

### Example using the OSQLPredicate as predicate

```java
for (OIdentifiable id : new OTraverse()
              .field("in").field("out")
              .target(database.browseClass("Movie").iterator())
              .predicate( new OSQLPredicate("$depth <= 5"))) {

  System.out.println(id);
}
```

### Other examples

OTraverse gets any Iterable, Iterator and Single/Multi OIdentifiable. There's also the limit() clause. To specify multiple fields use fields(). Full example:
```java
for (OIdentifiable id : new OTraverse()
              .target(new ORecordId("#6:0"), new ORecordId("#6:1"))
              .fields("out", "in")
              .limit(100)
              .predicate( new OSQLPredicate("$depth <= 10"))) {

  System.out.println( id);
}
```

repository: lvca/orientdb-docs

repo_name: lvca/orientdb-docs


text:
Bibi Zip Loader
===============

Zip Loader for Bibi

Requiements
-----------

- Rust 1.34
- Binaryen `brew install binaryen --HEAD`
- wasm-pack `cargo install wasm-pack`
- Node 8

Usage
-----

``` javascript
// LSZL is used as ES6 Class.
const lszl = new LSZL({
  url: 'https://example.com/pass/to/book.epub'
});

const promise = lsld.getBuffer('mimetype'); // returns a promise that will be resolved with an ArrayBuffer.

promise.then((buffer) => {
   // use buffer
});

```

Development
-----------

``` sh
npm bootstrap # prepare submodules
npm install   # install dependencies
npm start     # start webpack-dev-server
npm pack      # build package
```


text:
# Geting Started with `sisbase`

Listed here is a couple of links that will help you start developing your own bots.

* [Hello World Bot](hello_world.html) - Teaches how to make a bot that connects to discord.

## New to programming in C#?

Take a look at [this interactive course by Microsoft](https://docs.microsoft.com/en-us/dotnet/csharp/tutorials/intro-to-csharp/ "Introduction to C#"). If you are feeling lost, you should definitely check it out.
## Looking for API documentation?

Head over to the [Api Documentation](../api/index.html) page.

## Example bots

If you're looking for example bots, make sure to check out the following links:

* [sisbase.Test](https://gitlab.com/siscode/sisbase/-/tree/master/sisbase.Test)

# Still lost?

You can always contact us through [`Discord`](http://discord.gg/t8a9jvR)!

repository: siscodeorg/sisbase

branch_name: refs/heads/stable

gha_language: C#

repo_name: siscodeorg/sisbase


text:
[![Build Status](https://travis-ci.org/ram-compbio/CANDO.png)](https://travis-ci.org/ram-compbio/CANDO)
[![codecov](https://codecov.io/gh/ram-compbio/CANDO/branch/master/graph/badge.svg)](https://codecov.io/gh/ram-compbio/CANDO)
[![Anaconda-Server Badge](https://anaconda.org/ram-compbio/cando/badges/version.svg)](https://anaconda.org/ram-compbio/cando)
[![Anaconda-Server Badge](https://anaconda.org/ram-compbio/cando/badges/license.svg)](https://anaconda.org/ram-compbio/cando)
[![Anaconda-Server Badge](https://anaconda.org/ram-compbio/cando/badges/downloads.svg)](https://anaconda.org/ram-compbio/cando)

# CANDO

Computational Analysis of Novel Drug Opportunities

---

## Background

CANDO is a unique computational drug discovery, design, and repurposing platform.

## Install

You may download the source code via the releases or cloning the git repository. However, we suggest using anaconda to install the CANDO package, as this is the easiest and quickest way to start using our platform!

The CANDO package relies on multiple "conda-forge" dependencies. Therefore, we require that you add "conda-forge" to your anaconda channels:

`conda config --add channels conda-forge`

Then you can install CANDO using the following command:

`conda install -c ram-compbio cando`

## Test

You can test your install by running our script:

[test.py](https://github.com/ram-compbio/CANDO/blob/master/test.py)

repository: lamawmouk/CANDO

repo_name: lamawmouk/CANDO


text:
My way for fixing bug with Bootstrap Modals and fullwidth fixed elements
========================================================================

There is a bug with Bootstrap Modals and fullwidth fixed elements

Requires
========
`jQuery` - bootstrap requires jQuery lib;

How to use
=============

1) **if you are using ES6 modules:**
    just copy file `src/js/helpers/bootstrapModalFix.js` into your project and import it like this:

    `import bootstrapModalFix from './helpers/bootstrapModalFix';`

2) **if you are not using ES6 modules:**
    a) export jQuery object to global context: `window.jQuery = jQuery;`

  b) copy function bootstrapModal(element) to your project after(!) jQuery and Bootstrap Modal include
  Call this function with jquery selector you need.

**Example:**
==============
You have fixed header with full width of the screen
`<header class="header js-fixed"></header>`

Call `bootstrapModal('.js-fixed');` and thats all you have to do :)

repository: hraboviyvadim/bootstrapModal

repo_name: hraboviyvadim/bootstrapModal