text:
# Changelog

## [0.23.2](https://github.com/vortechsa/python-sdk/tree/0.23.2) (2020-07-16)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.23.1...0.23.2)

**Fixed bugs:**

- SDK Sometimes freezes when converting dicts to class types on Windows  [\#224](https://github.com/VorTECHsa/python-sdk/issues/224)

**Merged pull requests:**

- Consolidate list [\#223](https://github.com/VorTECHsa/python-sdk/pull/223) ([KitBurgess](https://github.com/KitBurgess))
- chore: Add more detailed debug log messages [\#221](https://github.com/VorTECHsa/python-sdk/pull/221) ([KitBurgess](https://github.com/KitBurgess))
- feat: Floating storage beginner notebook [\#219](https://github.com/VorTECHsa/python-sdk/pull/219) ([Natday](https://github.com/Natday))
- Update issue templates [\#218](https://github.com/VorTECHsa/python-sdk/pull/218) ([KitBurgess](https://github.com/KitBurgess))

## [0.23.1](https://github.com/vortechsa/python-sdk/tree/0.23.1) (2020-07-15)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.23.0...0.23.1)

**Implemented enhancements:**

- Loading all cargo movements in \<5mins. [\#128](https://github.com/VorTECHsa/python-sdk/issues/128)

**Merged pull requests:**

- docs: Add how-to paste windows key [\#220](https://github.com/VorTECHsa/python-sdk/pull/220) ([KitBurgess](https://github.com/KitBurgess))
- fix: Check httpstat site, rather than github as github can impose rat… [\#217](https://github.com/VorTECHsa/python-sdk/pull/217) ([KitBurgess](https://github.com/KitBurgess))

## [0.23.0](https://github.com/vortechsa/python-sdk/tree/0.23.0) (2020-06-30)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.22.1...0.23.0)

**Implemented enhancements:**

- Better interface for retrieving IDs [\#166](https://github.com/VorTECHsa/python-sdk/issues/166)

**Closed issues:**

- Warn users if their API key isn't uuidv4 [\#203](https://github.com/VorTECHsa/python-sdk/issues/203)

**Merged pull requests:**

- ci: Kill process on old docs if it exists [\#215](https://github.com/VorTECHsa/python-sdk/pull/215) ([KitBurgess](https://github.com/KitBurgess))
- feat: Add exact match filter to geogs, vessels, corporations [\#214](https://github.com/VorTECHsa/python-sdk/pull/214) ([KitBurgess](https://github.com/KitBurgess))

## [0.22.1](https://github.com/vortechsa/python-sdk/tree/0.22.1) (2020-06-30)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.22.0...0.22.1)

**Merged pull requests:**

- Password docs [\#216](https://github.com/VorTECHsa/python-sdk/pull/216) ([KitBurgess](https://github.com/KitBurgess))

## [0.22.0](https://github.com/vortechsa/python-sdk/tree/0.22.0) (2020-06-29)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.21.1...0.22.0)

**Implemented enhancements:**

- Filter vessel movements and cargo movements with attributes, age, flag & scrubbers. [\#191](https://github.com/VorTECHsa/python-sdk/issues/191)
- Add waypoints column to cargo movements df [\#117](https://github.com/VorTECHsa/python-sdk/issues/117)

**Merged pull requests:**

- Allow users to interactively enter API key [\#213](https://github.com/VorTECHsa/python-sdk/pull/213) ([KitBurgess](https://github.com/KitBurgess))
- feat: Exact term match [\#212](https://github.com/VorTECHsa/python-sdk/pull/212) ([KitBurgess](https://github.com/KitBurgess))
- chore: Allow users to set lowercase log level [\#211](https://github.com/VorTECHsa/python-sdk/pull/211) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add loading external data example [\#209](https://github.com/VorTECHsa/python-sdk/pull/209) ([KitBurgess](https://github.com/KitBurgess))
- docs: typo in products endpoint [\#208](https://github.com/VorTECHsa/python-sdk/pull/208) ([Natday](https://github.com/Natday))
- Webinar10jun [\#207](https://github.com/VorTECHsa/python-sdk/pull/207) ([KitBurgess](https://github.com/KitBurgess))
- Google analytics [\#206](https://github.com/VorTECHsa/python-sdk/pull/206) ([KitBurgess](https://github.com/KitBurgess))

## [0.21.1](https://github.com/vortechsa/python-sdk/tree/0.21.1) (2020-06-08)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.21.0...0.21.1)

**Fixed bugs:**

- Check\_setup script uses crude product ID which may be blocked by permissions [\#201](https://github.com/VorTECHsa/python-sdk/issues/201)

**Merged pull requests:**

- fix: remove tests that query specific products [\#205](https://github.com/VorTECHsa/python-sdk/pull/205) ([SeanBarry](https://github.com/SeanBarry))

## [0.21.0](https://github.com/vortechsa/python-sdk/tree/0.21.0) (2020-06-01)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.20.0...0.21.0)

**Closed issues:**

- Alert users of SDK if they're using an outdated version [\#126](https://github.com/VorTECHsa/python-sdk/issues/126)

**Merged pull requests:**

- Fix typo in docs/endpoints/about-endpoints.md [\#200](https://github.com/VorTECHsa/python-sdk/pull/200) ([pgrimaud](https://github.com/pgrimaud))
- Feat/version notification [\#198](https://github.com/VorTECHsa/python-sdk/pull/198) ([asfakianakis](https://github.com/asfakianakis))

## [0.20.0](https://github.com/vortechsa/python-sdk/tree/0.20.0) (2020-05-19)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.19.0...0.20.0)

**Implemented enhancements:**

- Add attributes reference endpoint [\#189](https://github.com/VorTECHsa/python-sdk/issues/189)

**Merged pull requests:**

- Feat attribute endpoint [\#197](https://github.com/VorTECHsa/python-sdk/pull/197) ([KitBurgess](https://github.com/KitBurgess))
- Feat new filters [\#193](https://github.com/VorTECHsa/python-sdk/pull/193) ([SeanBarry](https://github.com/SeanBarry))
- docs: add SeanBarry as a contributor [\#192](https://github.com/VorTECHsa/python-sdk/pull/192) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- Feat attribute endpoint  [\#190](https://github.com/VorTECHsa/python-sdk/pull/190) ([SeanBarry](https://github.com/SeanBarry))
- fix: Correct commant in check setup image [\#188](https://github.com/VorTECHsa/python-sdk/pull/188) ([KitBurgess](https://github.com/KitBurgess))

## [0.19.0](https://github.com/vortechsa/python-sdk/tree/0.19.0) (2020-05-04)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.18.0...0.19.0)

**Merged pull requests:**

- feat: Add filter\_activity to vessels endpoint [\#187](https://github.com/VorTECHsa/python-sdk/pull/187) ([KitBurgess](https://github.com/KitBurgess))
- docs: Show setup on mainpage [\#186](https://github.com/VorTECHsa/python-sdk/pull/186) ([KitBurgess](https://github.com/KitBurgess))

## [0.18.0](https://github.com/vortechsa/python-sdk/tree/0.18.0) (2020-05-04)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.17.2...0.18.0)

**Closed issues:**

- Add connectivity / healthcheck script. [\#180](https://github.com/VorTECHsa/python-sdk/issues/180)

**Merged pull requests:**

- feat: Check setup [\#181](https://github.com/VorTECHsa/python-sdk/pull/181) ([KitBurgess](https://github.com/KitBurgess))

## [0.17.2](https://github.com/vortechsa/python-sdk/tree/0.17.2) (2020-05-04)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.17.1...0.17.2)

## [0.17.1](https://github.com/vortechsa/python-sdk/tree/0.17.1) (2020-05-04)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.17.0...0.17.1)

## [0.17.0](https://github.com/vortechsa/python-sdk/tree/0.17.0) (2020-05-04)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.16.0...0.17.0)

**Closed issues:**

- Add python SDK version to API calls [\#179](https://github.com/VorTECHsa/python-sdk/issues/179)

**Merged pull requests:**

- feat: Add version to API params [\#182](https://github.com/VorTECHsa/python-sdk/pull/182) ([KitBurgess](https://github.com/KitBurgess))

## [0.16.0](https://github.com/vortechsa/python-sdk/tree/0.16.0) (2020-05-04)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.16.0a4...0.16.0)

**Implemented enhancements:**

- Add exclude geographies to cargo movements and vessel movements endpoint [\#168](https://github.com/VorTECHsa/python-sdk/issues/168)
- Feat/origin dest exclusion filters [\#178](https://github.com/VorTECHsa/python-sdk/pull/178) ([asfakianakis](https://github.com/asfakianakis))

**Closed issues:**

- How to set env key? [\#76](https://github.com/VorTECHsa/python-sdk/issues/76)

**Merged pull requests:**

- fix: Remove exclude empties from payload [\#185](https://github.com/VorTECHsa/python-sdk/pull/185) ([KitBurgess](https://github.com/KitBurgess))

## [0.16.0a4](https://github.com/vortechsa/python-sdk/tree/0.16.0a4) (2020-05-01)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.16.0a3...0.16.0a4)

## [0.16.0a3](https://github.com/vortechsa/python-sdk/tree/0.16.0a3) (2020-05-01)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.16.0a1...0.16.0a3)

## [0.16.0a1](https://github.com/vortechsa/python-sdk/tree/0.16.0a1) (2020-05-01)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.15.2...0.16.0a1)

## [0.15.2](https://github.com/vortechsa/python-sdk/tree/0.15.2) (2020-04-22)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.15.1...0.15.2)

**Merged pull requests:**

- chore: Log the actual payload sent to the API [\#177](https://github.com/VorTECHsa/python-sdk/pull/177) ([KitBurgess](https://github.com/KitBurgess))

## [0.15.1](https://github.com/vortechsa/python-sdk/tree/0.15.1) (2020-04-21)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.15.0...0.15.1)

**Merged pull requests:**

- docs: Add call to action for demo [\#175](https://github.com/VorTECHsa/python-sdk/pull/175) ([KitBurgess](https://github.com/KitBurgess))
- docs: add links for FS notebook and webinar in China notebook [\#174](https://github.com/VorTECHsa/python-sdk/pull/174) ([asfakianakis](https://github.com/asfakianakis))

## [0.15.0](https://github.com/vortechsa/python-sdk/tree/0.15.0) (2020-04-20)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.14.2...0.15.0)

**Implemented enhancements:**

- Add vessel status filter to vessel movements endpoint [\#167](https://github.com/VorTECHsa/python-sdk/issues/167)

**Merged pull requests:**

- Update CONTRIBUTING.md [\#173](https://github.com/VorTECHsa/python-sdk/pull/173) ([KitBurgess](https://github.com/KitBurgess))
- examples: notebook with crude floating storage analysis [\#171](https://github.com/VorTECHsa/python-sdk/pull/171) ([gssantos](https://github.com/gssantos))
- Feat/vm add ves status filter [\#170](https://github.com/VorTECHsa/python-sdk/pull/170) ([asfakianakis](https://github.com/asfakianakis))
- examples: add notebook with China Flows analysis [\#169](https://github.com/VorTECHsa/python-sdk/pull/169) ([asfakianakis](https://github.com/asfakianakis))

## [0.14.2](https://github.com/vortechsa/python-sdk/tree/0.14.2) (2020-04-08)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.14.1...0.14.2)

**Merged pull requests:**

- chore: Fix example typo [\#165](https://github.com/VorTECHsa/python-sdk/pull/165) ([KitBurgess](https://github.com/KitBurgess))

## [0.14.1](https://github.com/vortechsa/python-sdk/tree/0.14.1) (2020-03-25)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.14.0...0.14.1)

**Closed issues:**

- Check linting in all examples/\*.py files as part of CI. [\#65](https://github.com/VorTECHsa/python-sdk/issues/65)

**Merged pull requests:**

- Lint examples as part of CI [\#164](https://github.com/VorTECHsa/python-sdk/pull/164) ([KitBurgess](https://github.com/KitBurgess))
- feat: Add option to aggregate by timeseries\_activity [\#163](https://github.com/VorTECHsa/python-sdk/pull/163) ([KitBurgess](https://github.com/KitBurgess))

## [0.14.0](https://github.com/vortechsa/python-sdk/tree/0.14.0) (2020-03-09)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.13.1...0.14.0)

**Merged pull requests:**

- Add timeseries\_activity\_min\_span filter argument & floating storage example. [\#162](https://github.com/VorTECHsa/python-sdk/pull/162) ([KitBurgess](https://github.com/KitBurgess))

## [0.13.1](https://github.com/vortechsa/python-sdk/tree/0.13.1) (2020-03-05)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.13.0...0.13.1)

**Merged pull requests:**

- Client probe request [\#160](https://github.com/VorTECHsa/python-sdk/pull/160) ([cvonsteg](https://github.com/cvonsteg))
- chore: Set Content-Type as application/json in requests [\#159](https://github.com/VorTECHsa/python-sdk/pull/159) ([KitBurgess](https://github.com/KitBurgess))

## [0.13.0](https://github.com/vortechsa/python-sdk/tree/0.13.0) (2020-03-05)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.12.1...0.13.0)

**Merged pull requests:**

- feat: Add timeseries endpoint, closes \#124 [\#125](https://github.com/VorTECHsa/python-sdk/pull/125) ([KitBurgess](https://github.com/KitBurgess))

## [0.12.1](https://github.com/vortechsa/python-sdk/tree/0.12.1) (2020-03-03)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.12.0...0.12.1)

**Merged pull requests:**

- feat: Check the number of records returned by API is what we'd expect [\#158](https://github.com/VorTECHsa/python-sdk/pull/158) ([KitBurgess](https://github.com/KitBurgess))
- chore: Remove to\_markdown imports [\#157](https://github.com/VorTECHsa/python-sdk/pull/157) ([KitBurgess](https://github.com/KitBurgess))
- Aws event example [\#156](https://github.com/VorTECHsa/python-sdk/pull/156) ([asfakianakis](https://github.com/asfakianakis))

## [0.12.0](https://github.com/vortechsa/python-sdk/tree/0.12.0) (2020-02-26)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.11.2...0.12.0)

**Merged pull requests:**

- chore: Remove old files [\#155](https://github.com/VorTECHsa/python-sdk/pull/155) ([KitBurgess](https://github.com/KitBurgess))
- feat: Product class now has hierarchy attribute [\#154](https://github.com/VorTECHsa/python-sdk/pull/154) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add ballast movements example [\#153](https://github.com/VorTECHsa/python-sdk/pull/153) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add FAQ pages [\#152](https://github.com/VorTECHsa/python-sdk/pull/152) ([KitBurgess](https://github.com/KitBurgess))
- Add if \_\_name\_\_ == \_\_main\_\_ to sample files [\#150](https://github.com/VorTECHsa/python-sdk/pull/150) ([KitBurgess](https://github.com/KitBurgess))
- Windows [\#149](https://github.com/VorTECHsa/python-sdk/pull/149) ([KitBurgess](https://github.com/KitBurgess))

## [0.11.2](https://github.com/vortechsa/python-sdk/tree/0.11.2) (2020-01-21)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.11.1...0.11.2)

**Merged pull requests:**

- feat: Only log to file if log file is present in config [\#148](https://github.com/VorTECHsa/python-sdk/pull/148) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add correct default cols to docs [\#147](https://github.com/VorTECHsa/python-sdk/pull/147) ([KitBurgess](https://github.com/KitBurgess))

## [0.11.1](https://github.com/vortechsa/python-sdk/tree/0.11.1) (2020-01-21)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.11.0...0.11.1)

**Closed issues:**

- Passing names as a filter argument does not work for storage location filter [\#141](https://github.com/VorTECHsa/python-sdk/issues/141)

**Merged pull requests:**

- Merge pull request \#146 from VorTECHsa/loading-label [\#146](https://github.com/VorTECHsa/python-sdk/pull/146) ([KitBurgess](https://github.com/KitBurgess))
- Docs: Add Singapore Fuel Oil Example [\#145](https://github.com/VorTECHsa/python-sdk/pull/145) ([KitBurgess](https://github.com/KitBurgess))
- fix CircleCI - capitalisation seems crucial [\#144](https://github.com/VorTECHsa/python-sdk/pull/144) ([paddyroddy](https://github.com/paddyroddy))
- Find & replace V0RT3X4 with vortechsa [\#142](https://github.com/VorTECHsa/python-sdk/pull/142) ([KitBurgess](https://github.com/KitBurgess))

## [0.11.0](https://github.com/vortechsa/python-sdk/tree/0.11.0) (2019-12-11)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.10.0...0.11.0)

**Merged pull requests:**

- Remove load all [\#139](https://github.com/VorTECHsa/python-sdk/pull/139) ([KitBurgess](https://github.com/KitBurgess))
- perf: Failfast if \> 1e6 records returned from API in single call [\#138](https://github.com/VorTECHsa/python-sdk/pull/138) ([KitBurgess](https://github.com/KitBurgess))

## [0.10.0](https://github.com/vortechsa/python-sdk/tree/0.10.0) (2019-12-11)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.9.2...0.10.0)

**Merged pull requests:**

- Remove fuzzy search [\#134](https://github.com/VorTECHsa/python-sdk/pull/134) ([KitBurgess](https://github.com/KitBurgess))

## [0.9.2](https://github.com/vortechsa/python-sdk/tree/0.9.2) (2019-12-11)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.9.1...0.9.2)

**Fixed bugs:**

- Fix SDK Stability issues [\#127](https://github.com/VorTECHsa/python-sdk/issues/127)

**Merged pull requests:**

- refactor: Call doctests using pytest [\#137](https://github.com/VorTECHsa/python-sdk/pull/137) ([KitBurgess](https://github.com/KitBurgess))
- test: Actually run doctest on all files [\#136](https://github.com/VorTECHsa/python-sdk/pull/136) ([KitBurgess](https://github.com/KitBurgess))
- fix: search on vessel class is case insensitive [\#135](https://github.com/VorTECHsa/python-sdk/pull/135) ([Natday](https://github.com/Natday))
- docs: Check doctests are valid code [\#133](https://github.com/VorTECHsa/python-sdk/pull/133) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add crude from saudi arabia to india example [\#132](https://github.com/VorTECHsa/python-sdk/pull/132) ([KitBurgess](https://github.com/KitBurgess))
- perf: Shuffle offsets inplace for more accurate progress ETA, increas… [\#131](https://github.com/VorTECHsa/python-sdk/pull/131) ([KitBurgess](https://github.com/KitBurgess))

## [0.9.1](https://github.com/vortechsa/python-sdk/tree/0.9.1) (2019-12-09)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.9.0...0.9.1)

**Implemented enhancements:**

- Show loading progress bar [\#123](https://github.com/VorTECHsa/python-sdk/issues/123)

**Merged pull requests:**

- fix: Handle API failures in VortexaClient [\#130](https://github.com/VorTECHsa/python-sdk/pull/130) ([KitBurgess](https://github.com/KitBurgess))
- feat: Add progressbar [\#129](https://github.com/VorTECHsa/python-sdk/pull/129) ([KitBurgess](https://github.com/KitBurgess))

## [0.9.0](https://github.com/vortechsa/python-sdk/tree/0.9.0) (2019-12-05)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.8.5...0.9.0)

**Implemented enhancements:**

- Add timeseries endpoint [\#124](https://github.com/VorTECHsa/python-sdk/issues/124)
- Add load all reference data method [\#81](https://github.com/VorTECHsa/python-sdk/issues/81)

**Fixed bugs:**

- CargoMovementsResult.to\_df\('all'\) blows up [\#120](https://github.com/VorTECHsa/python-sdk/issues/120)
- Reference shouldn't return a list [\#69](https://github.com/VorTECHsa/python-sdk/issues/69)

**Closed issues:**

- Inconsistent search signatures across endpoints  [\#114](https://github.com/VorTECHsa/python-sdk/issues/114)
- Consider adopting All Contributors specification [\#98](https://github.com/VorTECHsa/python-sdk/issues/98)
- Sample notebook with charts [\#83](https://github.com/VorTECHsa/python-sdk/issues/83)

**Merged pull requests:**

- fix: CargoMovementsResult to\_df all columns, closes \#120 [\#121](https://github.com/VorTECHsa/python-sdk/pull/121) ([KitBurgess](https://github.com/KitBurgess))
- Load all [\#119](https://github.com/VorTECHsa/python-sdk/pull/119) ([KitBurgess](https://github.com/KitBurgess))
- fix: Consistent search signatures, closes \#114 [\#118](https://github.com/VorTECHsa/python-sdk/pull/118) ([KitBurgess](https://github.com/KitBurgess))
- fix: Reference now returns dict, fixes \#69 [\#116](https://github.com/VorTECHsa/python-sdk/pull/116) ([KitBurgess](https://github.com/KitBurgess))
- docs: add asfakianakis as a contributor [\#113](https://github.com/VorTECHsa/python-sdk/pull/113) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add ChloeConnor as a contributor [\#112](https://github.com/VorTECHsa/python-sdk/pull/112) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add ArthurD1 as a contributor [\#111](https://github.com/VorTECHsa/python-sdk/pull/111) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add Natday as a contributor [\#110](https://github.com/VorTECHsa/python-sdk/pull/110) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add rugg2 as a contributor [\#109](https://github.com/VorTECHsa/python-sdk/pull/109) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add paddyroddy as a contributor [\#108](https://github.com/VorTECHsa/python-sdk/pull/108) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add eadwright as a contributor [\#107](https://github.com/VorTECHsa/python-sdk/pull/107) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add kujon as a contributor [\#106](https://github.com/VorTECHsa/python-sdk/pull/106) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add syed1992 as a contributor [\#105](https://github.com/VorTECHsa/python-sdk/pull/105) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add dstarkey23 as a contributor [\#103](https://github.com/VorTECHsa/python-sdk/pull/103) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add cvonsteg as a contributor [\#100](https://github.com/VorTECHsa/python-sdk/pull/100) ([allcontributors[bot]](https://github.com/apps/allcontributors))
- docs: add KitBurgess as a contributor [\#99](https://github.com/VorTECHsa/python-sdk/pull/99) ([allcontributors[bot]](https://github.com/apps/allcontributors))

## [0.8.5](https://github.com/vortechsa/python-sdk/tree/0.8.5) (2019-11-28)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.8.4...0.8.5)

**Fixed bugs:**

- Make client more robust [\#95](https://github.com/VorTECHsa/python-sdk/issues/95)

**Merged pull requests:**

- fix: Retry API calls on 502, 504 status codes, fixes \#95 [\#97](https://github.com/VorTECHsa/python-sdk/pull/97) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add link to CM/VM concepts [\#96](https://github.com/VorTECHsa/python-sdk/pull/96) ([KitBurgess](https://github.com/KitBurgess))

## [0.8.4](https://github.com/vortechsa/python-sdk/tree/0.8.4) (2019-11-28)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.8.3...0.8.4)

**Closed issues:**

- add 'filter\_vessel\_class' argument to cargo movements [\#39](https://github.com/VorTECHsa/python-sdk/issues/39)

**Merged pull requests:**

- Vessel movements bettering [\#94](https://github.com/VorTECHsa/python-sdk/pull/94) ([KitBurgess](https://github.com/KitBurgess))

## [0.8.3](https://github.com/vortechsa/python-sdk/tree/0.8.3) (2019-11-27)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.8.2...0.8.3)

**Fixed bugs:**

- IDLayer class has attributes `name` instead of `layer` [\#70](https://github.com/VorTECHsa/python-sdk/issues/70)

**Closed issues:**

- Geographies document reference method. [\#66](https://github.com/VorTECHsa/python-sdk/issues/66)
- Improved logging to make sure the right entity is selected in a query \(or at least make it clear to user what entity is being used\) [\#37](https://github.com/VorTECHsa/python-sdk/issues/37)
- Contributing to VortexaSDK: Setting up environment bug `pip install -e .\[test\]` [\#25](https://github.com/VorTECHsa/python-sdk/issues/25)

**Merged pull requests:**

- feat: Log searches [\#93](https://github.com/VorTECHsa/python-sdk/pull/93) ([KitBurgess](https://github.com/KitBurgess))

## [0.8.2](https://github.com/vortechsa/python-sdk/tree/0.8.2) (2019-11-26)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.8.1...0.8.2)

## [0.8.1](https://github.com/vortechsa/python-sdk/tree/0.8.1) (2019-11-26)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.8.0...0.8.1)

## [0.8.0](https://github.com/vortechsa/python-sdk/tree/0.8.0) (2019-11-26)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.7.0...0.8.0)

**Implemented enhancements:**

- filter\_time\_min and filter\_time\_max parameters should be python datetime objects [\#45](https://github.com/VorTECHsa/python-sdk/issues/45)

**Merged pull requests:**

- feat: Use datetime type as time argument, closes \#45 [\#92](https://github.com/VorTECHsa/python-sdk/pull/92) ([KitBurgess](https://github.com/KitBurgess))
- feat: Add vessel movements endpoint [\#63](https://github.com/VorTECHsa/python-sdk/pull/63) ([KitBurgess](https://github.com/KitBurgess))

## [0.7.0](https://github.com/vortechsa/python-sdk/tree/0.7.0) (2019-11-26)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.6.1...0.7.0)

**Closed issues:**

- Where do I get an API key from [\#75](https://github.com/VorTECHsa/python-sdk/issues/75)
- change 'filter\_vessel' argument to 'filter\_vessel\_name' to make it clearer that this is filtering vessels and not vessel classes [\#38](https://github.com/VorTECHsa/python-sdk/issues/38)

**Merged pull requests:**

- feat: Filter cargo movements on vessel class, closes \#38 [\#91](https://github.com/VorTECHsa/python-sdk/pull/91) ([KitBurgess](https://github.com/KitBurgess))

## [0.6.1](https://github.com/vortechsa/python-sdk/tree/0.6.1) (2019-11-25)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.6.0...0.6.1)

**Implemented enhancements:**

- Add DataFrame example to all endpoints [\#58](https://github.com/VorTECHsa/python-sdk/issues/58)

**Fixed bugs:**

- CargoMovements filter\_activity illegal state [\#71](https://github.com/VorTECHsa/python-sdk/issues/71)

**Closed issues:**

- Bounding box is lon/lat not lat/lon [\#88](https://github.com/VorTECHsa/python-sdk/issues/88)
- Add instructions on how to install pre-commit hooks. [\#86](https://github.com/VorTECHsa/python-sdk/issues/86)
- Show Dataframe result in main README example [\#78](https://github.com/VorTECHsa/python-sdk/issues/78)
- Fix broken docs links [\#77](https://github.com/VorTECHsa/python-sdk/issues/77)
- List available vessel classes [\#73](https://github.com/VorTECHsa/python-sdk/issues/73)

**Merged pull requests:**

- fix: rename IDLayer attribute [\#90](https://github.com/VorTECHsa/python-sdk/pull/90) ([cvonsteg](https://github.com/cvonsteg))
- Incorporate features / requests from SDK battletesting [\#89](https://github.com/VorTECHsa/python-sdk/pull/89) ([KitBurgess](https://github.com/KitBurgess))

## [0.6.0](https://github.com/vortechsa/python-sdk/tree/0.6.0) (2019-11-22)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.5.0...0.6.0)

**Closed issues:**

- Add Charterers `to\_df` endpoint. [\#34](https://github.com/VorTECHsa/python-sdk/issues/34)

**Merged pull requests:**

- feat: Flatten columns in product result [\#62](https://github.com/VorTECHsa/python-sdk/pull/62) ([KitBurgess](https://github.com/KitBurgess))
- Serde mixin [\#61](https://github.com/VorTECHsa/python-sdk/pull/61) ([KitBurgess](https://github.com/KitBurgess))

## [0.5.0](https://github.com/vortechsa/python-sdk/tree/0.5.0) (2019-11-21)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.4.3...0.5.0)

**Closed issues:**

- Test SDK against different python versions [\#53](https://github.com/VorTECHsa/python-sdk/issues/53)

**Merged pull requests:**

- Bulk out Corporations endpoint [\#60](https://github.com/VorTECHsa/python-sdk/pull/60) ([KitBurgess](https://github.com/KitBurgess))

## [0.4.3](https://github.com/vortechsa/python-sdk/tree/0.4.3) (2019-11-20)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.3.4-alpha...0.4.3)

**Implemented enhancements:**

- add a list of available columns in the SDK documents [\#40](https://github.com/VorTECHsa/python-sdk/issues/40)

**Closed issues:**

- include an explanation in the docs of the flattened cargo movement structure and how this links to the column naming convention [\#48](https://github.com/VorTECHsa/python-sdk/issues/48)
- make 'filter\_activity' a required argument [\#43](https://github.com/VorTECHsa/python-sdk/issues/43)
- How to serve docs isn't clear, which directory from? [\#20](https://github.com/VorTECHsa/python-sdk/issues/20)
- unclear how to import the different endpoints [\#19](https://github.com/VorTECHsa/python-sdk/issues/19)

**Merged pull requests:**

- docs: Make it clearer how to import endpoints, closes \#19 [\#57](https://github.com/VorTECHsa/python-sdk/pull/57) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add about-endpoints explanation [\#55](https://github.com/VorTECHsa/python-sdk/pull/55) ([KitBurgess](https://github.com/KitBurgess))

## [0.3.4-alpha](https://github.com/vortechsa/python-sdk/tree/0.3.4-alpha) (2019-11-20)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.3.3...0.3.4-alpha)

## [0.3.3](https://github.com/vortechsa/python-sdk/tree/0.3.3) (2019-11-20)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.3.2...0.3.3)

## [0.3.2](https://github.com/vortechsa/python-sdk/tree/0.3.2) (2019-11-20)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.2.3...0.3.2)

**Implemented enhancements:**

- Allow for filtering by product name in vessel endpoint filters  [\#31](https://github.com/VorTECHsa/python-sdk/issues/31)

**Merged pull requests:**

- fix: Move to pytest, run mock setup before each test [\#52](https://github.com/VorTECHsa/python-sdk/pull/52) ([KitBurgess](https://github.com/KitBurgess))
- ci: Add git change log [\#51](https://github.com/VorTECHsa/python-sdk/pull/51) ([KitBurgess](https://github.com/KitBurgess))
- feat: Filter vessels using products name [\#50](https://github.com/VorTECHsa/python-sdk/pull/50) ([KitBurgess](https://github.com/KitBurgess))

## [0.2.3](https://github.com/vortechsa/python-sdk/tree/0.2.3) (2019-11-19)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.2.2...0.2.3)

## [0.2.2](https://github.com/vortechsa/python-sdk/tree/0.2.2) (2019-11-19)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.2.1...0.2.2)

**Implemented enhancements:**

- Create Products endpoint [\#7](https://github.com/VorTECHsa/python-sdk/issues/7)

**Fixed bugs:**

- Tried to pull out a reference df of all vessels but only got 200 results? [\#29](https://github.com/VorTECHsa/python-sdk/issues/29)

**Closed issues:**

- searching vessel reference database only ever gives me back 100 results [\#30](https://github.com/VorTECHsa/python-sdk/issues/30)

**Merged pull requests:**

- perf: Call API in parallel [\#44](https://github.com/VorTECHsa/python-sdk/pull/44) ([KitBurgess](https://github.com/KitBurgess))

## [0.2.1](https://github.com/vortechsa/python-sdk/tree/0.2.1) (2019-11-18)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.2.0...0.2.1)

**Closed issues:**

- filter arguments for origins/destinations must be passed as vortexa ids \(a user will not know what our ID's are\) [\#17](https://github.com/VorTECHsa/python-sdk/issues/17)

**Merged pull requests:**

- fix: Return all vessels from search, not just arbitrary 100 [\#41](https://github.com/VorTECHsa/python-sdk/pull/41) ([KitBurgess](https://github.com/KitBurgess))
- style: Remove status token from README [\#32](https://github.com/VorTECHsa/python-sdk/pull/32) ([KitBurgess](https://github.com/KitBurgess))
- Products endpoint test [\#11](https://github.com/VorTECHsa/python-sdk/pull/11) ([dstarkey23](https://github.com/dstarkey23))

## [0.2.0](https://github.com/vortechsa/python-sdk/tree/0.2.0) (2019-11-18)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/0.1.0...0.2.0)

**Closed issues:**

- Importing entities does not work \(or maybe im doing this wrong\)? [\#18](https://github.com/VorTECHsa/python-sdk/issues/18)
- filter arguments must be passed in array form \(this is not made clear to the user\) [\#16](https://github.com/VorTECHsa/python-sdk/issues/16)

**Merged pull requests:**

- test: Fix global client state [\#28](https://github.com/VorTECHsa/python-sdk/pull/28) ([KitBurgess](https://github.com/KitBurgess))
- Filter on name [\#27](https://github.com/VorTECHsa/python-sdk/pull/27) ([KitBurgess](https://github.com/KitBurgess))
- Run tests against live API in circle ci [\#26](https://github.com/VorTECHsa/python-sdk/pull/26) ([KitBurgess](https://github.com/KitBurgess))
- Revert "ci: Run live tests in circleci" [\#24](https://github.com/VorTECHsa/python-sdk/pull/24) ([KitBurgess](https://github.com/KitBurgess))
- test: Correctly set client in tests [\#23](https://github.com/VorTECHsa/python-sdk/pull/23) ([KitBurgess](https://github.com/KitBurgess))
- ci: Run live tests in circleci [\#22](https://github.com/VorTECHsa/python-sdk/pull/22) ([KitBurgess](https://github.com/KitBurgess))
- feat: Allow user to search cargo movements with single filter, fixes \#16 [\#21](https://github.com/VorTECHsa/python-sdk/pull/21) ([KitBurgess](https://github.com/KitBurgess))

## [0.1.0](https://github.com/vortechsa/python-sdk/tree/0.1.0) (2019-11-13)

[Full Changelog](https://github.com/vortechsa/python-sdk/compare/f34a5627d0047e9a9a56ecf4b19cb4af91395d01...0.1.0)

**Merged pull requests:**

- ci: Add export packages [\#15](https://github.com/VorTECHsa/python-sdk/pull/15) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add tips to contributing docs [\#13](https://github.com/VorTECHsa/python-sdk/pull/13) ([KitBurgess](https://github.com/KitBurgess))
- refactor: Rename root dir from vortexa to vortexasdk [\#12](https://github.com/VorTECHsa/python-sdk/pull/12) ([KitBurgess](https://github.com/KitBurgess))
- docs: Improve the contributing guide [\#9](https://github.com/VorTECHsa/python-sdk/pull/9) ([KitBurgess](https://github.com/KitBurgess))
- refactor: Allow clients to import classes without knowledge of internals [\#8](https://github.com/VorTECHsa/python-sdk/pull/8) ([KitBurgess](https://github.com/KitBurgess))
- docs: Add quickstart to docs [\#5](https://github.com/VorTECHsa/python-sdk/pull/5) ([KitBurgess](https://github.com/KitBurgess))
- ci: Create the setup.py file [\#4](https://github.com/VorTECHsa/python-sdk/pull/4) ([KitBurgess](https://github.com/KitBurgess))
- test: Vessel dataframe test actually does something [\#3](https://github.com/VorTECHsa/python-sdk/pull/3) ([KitBurgess](https://github.com/KitBurgess))
- Consistent types [\#2](https://github.com/VorTECHsa/python-sdk/pull/2) ([KitBurgess](https://github.com/KitBurgess))

\* *This Changelog was automatically generated by [github_changelog_generator](https://github.com/github-changelog-generator/github-changelog-generator)*

repository: amirvortexa/python-sdk

repo_name: amirvortexa/python-sdk


text:
# Directed Graph
- BFS is used to find length i.e. count hops
- BFS is used to find shortest path
- Most of the time DFS is used
- BFS and DFS tree are same on directed graph
- BFS will not help to find out cycle
- DFS is used to find out cycle in graph
# DFS
- Back edge (after visited, departure time will not be set)
- Cross edge (after visited, departure time will be set)
- Forward edge (after visited, departure time will be set)
# Detect cycle
```
void DFS(int s) {
    // visit current node
    visited[s] = 1;
    arrival[s] = timestamp++;
    for w in adjList[s] {
        if(visited[w] === 0) {
            if(DFS(w)){
                return true;
            }
        } else {
            // possibility of cycle
            // three type of edges are possible, back edge, forward cycle and cross edge
            if(departure time of neighbor is not set ) {
                return true;
            }
        }
    }
    departure[s] = timestamp++;
    return false;
}
```
https://www.youtube.com/watch?v=1CdgY5KTQQE&list=PL1w8k37X_6L9IfRTVvL-tKnrZ_F-8HJQt&index=9
# Topological sort
```
topological = [];
void DFS(int s) {
    // visit current node
    visited[s] = 1;
    arrival[s] = timestamp++;
    for w in adjList[s] {
        if(visited[w] === 0) {
            if(DFS(w)){
                return true;
            }
        } else {
            // possibility of cycle
            // three type of edges are possible, back edge, forward cycle and cross edge
            if(departure time of neighbor is not set ) {
                return true;
            }
        }
    }
    departure[s] = timestamp++;
    topological.unshift(s); // append
    return false;
}
```

license: MIT

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
# Jasmine Gem 3.8 Release Notes

## Summary

This release updates the jasmine-core dependency to 3.8.0. See the
[jasmine-core release notes](https://github.com/pivotal/jasmine/blob/main/release_notes/3.8.0.md)
for more information.

## Changes

* Ruby 3.0 compatibility

# Internal notes

* Added Ruby 2.7 and Ruby 3.0 to CI matrix

* Migrated from Travis to Circle CI

## Supported Environments

The Jasmine gem has been tested in the following environments:

| Rails version   | Ruby versions |
|-----------------|---------------|
| 6               | 2.5-3.0       |
| 5               | 2.3-2.7       |
| 4               | 2.3-2.6       |
| Non-Rails usage | 2.3-3.0       |

See the
[jasmine-core release notes](https://github.com/jasmine/jasmine/blob/main/release_notes/3.8.0.md)
for supported browsers.

------

_Release Notes generated with _[Anchorman](http://github.com/infews/anchorman)_

repository: jasmine/jasmine-gem

branch_name: refs/heads/main

gha_language: Ruby

repo_name: jasmine/jasmine-gem


text:
[![Latest PyPI Release](https://img.shields.io/pypi/v/pycartool.svg)](https://pypi.org/project/pycartool/)
[![PyPI pyversions](https://img.shields.io/pypi/pyversions/pycartool.svg)](https://pypi.python.org/pypi/pycartool/)
[![Build Status](https://dev.azure.com/vferat/pycartool/_apis/build/status/Functional-Brain-Mapping-Laboratory.PyCartool?branchName=main)](https://dev.azure.com/vferat/pycartool/_build/latest?definitionId=5&branchName=main)
[![codecov](https://codecov.io/gh/Functional-Brain-Mapping-Laboratory/PyCartool/branch/master/graph/badge.svg?token=3TeUfaAmXd)](https://codecov.io/gh/Functional-Brain-Mapping-Laboratory/PyCartool)
[![Documentation Status](https://readthedocs.org/projects/pycartool/badge/?version=latest)](https://pycartool.readthedocs.io/en/latest/?badge=latest)
![License](https://img.shields.io/badge/license-BSD-green.svg)

# PyCartool
A simple open source Python package for I/O between Cartool and python

## About Cartool
Cartool is the EEG analysis software developed at the Functional Brain Mapping Lab (FBMLab), in Geneva, Switzerland. This project was initiated in 1996, and is still actively developed up to these days. It has been entirely programmed by Denis Brunet in C++, and doesn't rely on any other dependency to run.
from [Cartool website](https://sites.google.com/site/cartoolcommunity/about).

![alt text](./docs/_static//img/Cartool.PNG "Cartool")

## Installation

The latest stable version of Pycartool is available through [PyPi](https://pypi.org/project/pycartool/):

`pip install pycartool`

## Documentation

Documentation is available at <https://pycartool.readthedocs.io/en/stable/>

## Contributing to Pycartool

Any contribution is welcome, please let us know by opening an issue!

gha_language: Python


text:
---
layout: post          #important: don't change this
title: "Team Foundation Server 2015 Update 2 RC 1 - Now Available"
date: 2016-02-11 11:36:00
author: tarun
tags: ["TFS2015", "DevOps Book"]
categories:
- blog                #important: leave this here
- TeamFoundationServer
img:        #place image (850x450) with this name in /images/screenshots
thumb: thumb-icon-tarun.jpg    #place thumbnail (70x70) with this name in /images/screenshotsthumbs/
---
*Announcement* "Team Foundation Server (TFS) 2015 Update 2 RC 1 now available for download..." This blogpost explains where you can download the update from and the list of features installed with the update...

> Team Foundation Server 2015 Update 2 RC 1 is now available!

If you are a Visual Studio Team Services user, you would have seen most of the features for a few weeks at the very least. The big ticket item in this update is the *availability of the new release management solution making its debut to on premise customers.* Other updates are scattered across the product with bulk of investment in enriching the feature set in the Team Web Portal for dashboards hub, code hub and build hub.

## The full list of features in the release candidate are listed below...

+ [Team project creation and deletion experience improvements](https://www.visualstudio.com/news/tfs2015-update2-vs#teamproj "Team project creation and deletion experience improvements")
+ [New version of web-based Release Management](https://www.visualstudio.com/news/tfs2015-update2-vs#newrmtfs "New version of web-based Release Management")
+ [Reordering cards on boards](https://www.visualstudio.com/news/tfs2015-update2-vs#reorder "Reordering cards on boards")
+ [Deleting work items](https://www.visualstudio.com/news/tfs2015-update2-vs#delwork "Deleting work items")
+ [Global shortcut keys](https://www.visualstudio.com/news/tfs2015-update2-vs#globalshort "Global shortcut keys")
+ [Dashboards edit mode](https://www.visualstudio.com/news/tfs2015-update2-vs#dashedit "Dashboards edit mode")
+ [Auto-refresh dashboards](https://www.visualstudio.com/news/tfs2015-update2-vs#autodash "Auto-refresh dashboards")
+ [Build widgets in the dashboard catalog](https://www.visualstudio.com/news/tfs2015-update2-vs#widgetdb "Build widgets in the dashboard catalog")
+ [Work item query charts in the dashboard catalog](https://www.visualstudio.com/news/tfs2015-update2-vs#wiqdash "Work item query charts in the dashboard catalog")
+ [@mentions and #ID](https://www.visualstudio.com/news/tfs2015-update2-vs#mentionsid "@mentions and #ID")
+ [Pull request widget](https://www.visualstudio.com/news/tfs2015-update2-vs#prwidget "Pull request widget")
+ [Markdown widget lets you choose an existing file in a code repository to display](https://www.visualstudio.com/news/tfs2015-update2-vs#mdwidget "Markdown widget lets you choose an existing file in a code repository to display")
+ [Common identity picker](https://www.visualstudio.com/news/tfs2015-update2-vs#commonip "Common identity picker")
+ [Gated check-in for Team Foundation Version Control](https://www.visualstudio.com/news/tfs2015-update2-vs#gatedcheck "Gated check-in for Team Foundation Version Control")
+ [Version control web](https://www.visualstudio.com/news/tfs2015-update2-vs#vcweb "Version control web")
+ [Support for Team Foundation Server extensions](https://www.visualstudio.com/news/tfs2015-update2-vs#suppext "Support for Team Foundation Server extensions")
+ [Keyboard shortcuts for Kanban board](https://www.visualstudio.com/news/tfs2015-update2-vs#keyshort "Keyboard shortcuts for Kanban board")
+ [Build-related features and improvements](https://www.visualstudio.com/news/tfs2015-update2-vs#builditems "Build-related features and improvements")
+ [Testing: new features and improvements](https://www.visualstudio.com/news/tfs2015-update2-vs#testing "Testing: new features and improvements")

## Can I install this in production?

> This release of TFS is a “go-live” release candidate.  _Microsoft will support customers choosing to install it in a production environment._

## Where can I download it from?

+ [TFS 2015 Update 2 RC1 web installer](http://go.microsoft.com/fwlink/?LinkId=626619 "TFS 2015 Update 2 RC1 web installer")
+ [TFS 2015 Update 2 RC1 ISO](http://go.microsoft.com/fwlink/?LinkId=626620 "TFS 2015 Update 2 RC1 ISO")
+ [KB article](https://msdn.microsoft.com/en-us/library/2a90cb85-8296-417a-a4a8-1379998c4588 "KB article")

## Hands on Labs?

The [Team Foundation Server 2015 Cookbook](http://www.visualstudiogeeks.com/blog/book/teamfoundationserver/TeamFoundationServer2015-DevOps-ALM-Cookbook-by-TarunArora "Team Foundation Server 2015 Cookbook") just shipped and covers most of the features being released with Update 2. Learn more about these features using the 80 plus hands on labs covering walkthrough on implementing the user cases these new features best address...

+ Get a few free chapters here - [Team Foundation Server 2015 Cookbook - Free Chapters]( https://www.packtpub.com/networking-and-servers/microsoft-team-foundation-server-2015-cookbook "Team Foundation Server 2015 Cookbook Free Chapters")

+ Book reviews - [Team Foundation Server 2015 Cookbook - Reviews](http://www.amazon.co.uk/gp/product/1784391050/tararo-21 "Team Foundation Server 2015 Cookbook - Reviews")

+ Order here - UK

+ Order here - USA

Hope you enjoy the new features...

Questions Comments and Feedback... ? Leave a comment...

Cheers,
Tarun

repository: ajeetblog/newthm

repo_name: ajeetblog/newthm


text:
---
layout: post
title: "Eclipse Maintainers, Please add the Word \"Zombie\" to your Spell-Check Dictionary"
date: 2012-11-21 21:17
comments: true
categories:
---

{% img /images/digital/zombie_mispelled.jpg %}

[Webster](http://www.merriam-webster.com/dictionary/zombie) recognizes it as a real word and so should you! I'd make the change myself and submit a pull request but I found the [hundreds of eclipse repositories](http://git.eclipse.org/c/) to be too daunting.

This is only half-serious.

repository: albrow/blog-old

extension: markdown

repo_name: albrow/blog-old


text:
# csvsucks

CSV sucks so convert it to TSV.

go install github.com/yobert/csvsucks/cmd/csvsucks

$GOPATH/bin/csvsucks some.csv files.csv

Each file will get converted to TSV and saved to a file with ".tsv" appended to the name.

repository: yobert/csvsucks

repo_name: yobert/csvsucks


text:
---
title: Racism And Sexism
layout: post
author: harry.longhurst
permalink: /racism-and-sexism/
tags:
-
source-id: 1Wp-j_7JqKP-_lxY4XCeC8X1GA80L_gHx8RGQrcXe0ak
published: true
---

    Title
    Racism And Sexism
    Date
    16/3/17

    Starting point:
    Learning how to put a video on our blogs

    Target for this lesson?
    Learn how to put a video on our blog and sexism and racism.

    Did I reach my target?
(add details to "Lesson Review")
    Yes

    Lesson Review

    How did I learn? What strategies were effective?

    We learned about being racism and inequality and how it is not right. One of the main points was about saying 'like a girl' as an insult which is very bad and can make a girl feel really bad about herself. One of the ways we learned was by watching a video about this topic.h

    What limited my learning? Which habits do I need to work on?

    Nothing as it was a listen and learn and I did those things.

    What will I change for next time? How will I improve my learning?

    Nothing as there was nothing I did wrong and I contributed and learned so I don’t need to change anything.


text:
[![Build Status](https://travis-ci.org/josephyi/viktor.svg?branch=master)](https://travis-ci.org/josephyi/viktor)
[![Deps Status](https://beta.hexfaktor.org/badge/all/github/josephyi/viktor.svg)](https://beta.hexfaktor.org/github/josephyi/viktor)
[![Inline docs](http://inch-ci.org/github/josephyi/viktor.svg?branch=master)](http://inch-ci.org/github/josephyi/viktor)

# Viktor

> "Function over form."

Viktor is an Elixir interface to Riot Games' League of Legends API named after a character in the game.

## Prerequisite

> "Join the glorious evolution."

Sign up for an API key at [Riot Games Developer] site.

## Installation

> "Pave the way."

Add viktor to your list of dependencies in `mix.exs`:

```elixir
def deps do
  [{:viktor, "~> 0.0.8"}]
end
```

Ensure viktor is started before your application:

```elixir
def application do
  [applications: [:viktor]]
end
```

Test in iex:

```console
mix deps.get
iex -S mix
```

## Usage

Set the `RIOT_API_KEY` environment variable.

```console
export RIOT_API_KEY=whatever_key_rito_assigned_you
```

Viktor uses Elixir's [Agent] to manage the API key between requests, so you must call `start_link/0`.

If `RIOT_API_KEY` is set

```elixir
Viktor.start_link
```

You may also set the key using `start_link/1`

```elixir
Viktor.start_link("whatever_key_rito_assigned_you")
```

## Examples

I'm in the process of making this a little more pleasant by providing the functions off the root module. These examples will work, but see the [documentation] for details.

```elixir
Viktor.start_link
champion_list = Viktor.champions("na")
champion_list_free_week = Viktor.champions("na", true)
champion_by_id = Viktor.champion("na", 1)
champion_mastery_score = Viktor.mastery_score("na", 21066)
champion_mastery_champion = Viktor.champion_mastery("na", 21066, 1)
champion_mastery_champions = Viktor.champion_masteries("na", 21066)
champion_mastery_3_topchampions = Viktor.top_champion_masteries("na", 21066)
champion_mastery_5_topchampions = Viktor.top_champion_masteries("na", 21066, 5)
current_game = Viktor.current_game("na", 21066)
featured_games = Viktor.featured_games("na")
```

All that's left are the tournament endpoints!

## Other API Libraries

Be sure to check out the other libraries out there!

[velkoz]

[documentation]:https://hexdocs.pm/viktor/0.0.8/Viktor.html#content
[velkoz]:https://github.com/Tim-Machine/velkoz
[Agent]:http://elixir-lang.org/getting-started/mix-otp/agent.html
[Riot Games Developer]:https://developer.riotgames.com/

repository: josephyi/viktor

gha_language: Elixir

repo_name: josephyi/viktor


text:
---
layout: default
metatags: cardano, ADA, stake pool, PoS, proof of stake, blockchain
---

## Myriada at a glance:

Our yearly uptime goal *(SLO) is: 99.9%*

We use a [tax-ratio of 4%][1] - this means no fees unless rewards are issued and 4% of the reward, not your principal.

Our ticker is: ``MYRI``

Our servers are located in Ireland.
We rotate logs every 14 days. Disks are encrypted.
We use (D)DoS burst protection on nodes and will blacklist nodes with consistently mismatched hashes- Since IOHK nodes are whitelisted, this will not affect rewards in the test net
We use automatic fork detection and recovery after 5 minutes, hopefully this will not be required in the next version

## How to delegate / stake:
Please checkout the [Shelly Incentivized Testnet page](https://staking.cardano.org/en/delegation/) - the latest daedalus supports all steps from the UI!

In short:
1. Download daedalus
2. Create a rewards wallet (if you don't have one)
3. Move your ada to your rewards wallet
4. Go into the staking menu and find our pool via ticker: *MYRI*
5. Click the icon and hit delegate - you will see short summary of our pool statistics and fees

## Our Roadmap:

We are exited to be an active member of the Cardano community and are currently working on providing the following services, in addition to the stake pools:

- live dashboards for pool uptime, performance and relevant statistics

- optional rss or email alerts for delegators, in case the pool is down or degraded performance (we do not want you to miss out on rewards)

- wash trading detection for our favourite exchanges

[1]:https://input-output-hk.github.io/jormungandr/stake_pool/registering_stake_pool.html#the-primitives


text:
# KodeUI - A pure code UI system for Unity

This was created to enable the creation of mods UI in Kerbal Space Program without the need of pre built UI exported as AssetBundle
Original concept from Tim Twice Circled [Megaquarium Vlog#12](https://www.youtube.com/watch?v=_LNn8Ot8Mrw)

## How to use

Load in Unity 2017.1.3p1 and import the free TextMesh Pro asset from the store. Select the UIMainCanevas object and use the Build UI from the UITester component to create a demo UI.

## TODO
 - More components
 - Replace the Resources.Load calls
 - Ressources loading for Sprites
 - Component Styles and Skinning
 - Layout improvement
 - Proper UI Skin
 - Build script for the KodeUI subdir

## Licence
Unless specified in the file or folder this project is licensed under the MIT License - see the \[LICENSE.md\](LICENSE.md) file for details

repository: sarbian/KodeUI

repo_name: sarbian/KodeUI


text:
# Changelog

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

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## 0.2.1 - 2020-12-11

### Fixed

 - Updated example in readme.

## 0.2.0 - 2020-12-11

### Changed

 - Redesign API to use explicit methods instead of requiring the user to pattern-match enums for every variable call.
 - Modularize the code a bit.

## 0.1.0 - 2020-12-09

### Added

 - Initial implementation of I2C protocol.

repository: Karlinde/pololu-smc

repo_name: Karlinde/pololu-smc


text:
# Fistulina pallida Berk. & Ravenel, 1872 SPECIES

#### Status
ACCEPTED

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

#### Published in
Grevillea 1(no. 5): 71 (1872)

#### Original name
Fistulina pallida Berk. & Ravenel, 1872

### Remarks
null

repository: mdoering/backbone

repo_name: mdoering/backbone


text:
[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.5172582.svg)](https://doi.org/10.5281/zenodo.5172582)

Generating the LKR model consists on 6 steps:

1- Generating the representations

The script 1-gen_reps.py generates the aSLATM representations of the structures in the xyzs directory

2- Separating the atomic environments of different atomic species

The script 2-gen_at_envs.py agregates the the aSLATM representations of atoms of the same type.
At the same time, it reduces the size of the aSLATM representations by evaluating which dimensions of the representation are constant over the data.

3- Reducing the size of aSLATM representations.

Using the results from 2, aSLATM representations of the training points are reduced by removing the unchanging dimensions.

3.5- The first pool of reference atomic environments must be selected.

The script 3.5-FPS_filter_ref_envs.py selects filters the environments from the training data using a file with the indices of the selected environments.

4- Generate the euclidean distances between the atoms in the training data and the reference atoms

Script 4-gen_diffs.py generates the distances for a specific atom type. Execute as:

    python 4-gen_diffs.py atomtype

where atomtype should be the chemical symbols of the atom (e.g. C for carbon)

5- Generate the kernel projection of the training molecules to the reference atoms

Script 5-gen_projections.py generates the projections for a specific atom type. Execute as:

    python 5-gen_projections.py atomtype sigma

where atomtype should be the chemical symbols of the atom (e.g. C for carbon), and sigma is the value of the sigma hyperparameter in the gaussian kernel.

6- Train the model using OMP


text:
# Contribution guide

## Description
We build `demisto-sdk` to support python 3.7 and 3.8.

## Getting started

1. [Clone demisto-sdk repository](#1-Clone-demisto-sdk-repository)
2. [Install demisto-sdk as editable versions](#2-Install-demisto-sdk-as-editable-version)
3. [Pre-commit hooks setup](#3-Pre-commit-hooks-setup)
4. [Develop new command](#4-Develop-new-command)
5. [Running unit-tests using tox](#5-running-unit-tests-using-tox)
6. [Push changes to GitHub (Exernal PRs)](#6-push-changes-to-github-relevant-only-for-exernal-prs)
7. [Review Process](#7-review-process)
8. [Contributor License Agreement (Exernal PRs)](#8-contributor-license-agreement-relevant-only-for-exernal-prs)

---

### 1. Clone demisto-sdk repository
Perform the following command in the path you want the repository to be cloned:

```shell
git clone https://github.com/demisto/demisto-sdk.git
```

---

### 2. Install demisto sdk as editable version
1. If you are using virtualenv for this proccess you can skip this step, uninstall current installed version of
   `demisto-sdk`:

   ```shell
   pip3 uninstall demisto-sdk
   ```

2. Inside root directory of `demisto-sdk` repository - Install PyPi package as [editable package](https://pip.pypa.io/en/stable/reference/pip_install/#editable-installs):

   ```shell
   pip3 install -e .
   ```

3. Validate that `demisto-sdk` installed path is correct by

   ```shell
   pip3 show demisto-sdk  | grep Location
   ```

   should be `demisto-sdk` repository in your local enviorment.

4. Install dev-requirements -

   ```shell
   pip3 install -r <repo>/requirements-dev.txt
   ```

---

### 3. Pre-commit hooks setup
We use are using [pre-commit](https://pre-commit.com/) to run hooks on our build. To use it run:
1. Install hook to be performed as a hook before commiting changes - `pre-commit install`
2. Enable auto update of pre-commit hooks - `pre-commit autoupdate`
3. In order to run pre-commit without commiting - `pre-commit run -a` (on all files), `pre-commit run` (on staged files)

---

### 4. Develop new command
1. Create package for your command in the following path: `<repo>/demisto_sdk/commands/<your_new_command>`.
2. Create the following in the above path:
    1.  **CLI arguments parsing** - Add CLI parsing in `<repo>/demisto_sdk/__main__` using [click](https://click.palletsprojects.com/en/7.x/) package.
    2. **commands_module** - The modules suppose to return `0` if **succeed** else `1`, common `print` function can  import from `<repo>/demisto_sdk/commands/common/tools.py`
    3. **unit-tests** -

        1. Unit-tests should be located for each command in the following path-

            ```shell
            <repo>/demisto_sdk/commands/<your_new_command>/tests
            ```

        2. data files tests - Usally its shared data files for all commands which located in:

            ```shell
            <repo>/demisto_sdk/tests/test_files
            ```

            >  (you can use constants for right path in `<repo>/demisto_sdk/tests/constants_test.py`)

        3. check build influence on CircleCI -

            1. Test your functionality on CircleCI build of `Content` repository by changing requirements in `Content` repository:
                1.  Perform the following in `<content_repo>/dev-requirements-py3.txt`:
                    1. Delete `demisto-sdk` requirement.

                    2. Add the following requirement in new line -

                       ```
                        git+https://github.com/demisto/demisto-sdk@<branch>
                       ```

                2. Remove cache using in CircleCI build config, perform the following in file

                    ```shell
                    <content_repo>/.circleci/config.yml
                    ```

                    1. Remove the following string form the following key `restore_cache:`: `-{{ checksum "dev-requirements-py3.txt" }}`

---

### 5. Running unit-tests using tox
[Tox](https://tox.readthedocs.io/en/latest/index.html) aims to automate and standardize testing in Python. It is part of a larger vision of easing the packaging, testing and release process of Python software, We use it inorder to check unit-tests on python versions 3.7 and 3.8.

> If you have one interperter in your local environment it will skip the missing interperter and not failed - the 2 versions test will be performed in the CircleCI build.

1. To run all our unit tests we use: `tox` on all envs, optional args:
   * For additional verbosity use: `tox -vv`
   * Run `tox` without verbosity run: `tox -q`
   * Run on a specific environment, you can use: `tox -q -e py37`
2. To run a specific test using pytest run: `pytest -vv tests/{test_file}.py::{TestClass}::{test_function}`

---

### 6. Push changes to GitHub (Relevant only for Exernal PRs)

The Demisto SDK is MIT Licensed and accepts contributions via GitHub pull requests.
If you are a first time GitHub contributor, please look at these links explaining on how to create a Pull Request to a GitHub repo:
* https://guides.github.com/activities/forking/
* https://help.github.com/articles/creating-a-pull-request-from-a-fork/

**Working on your first Pull Request?** You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github)

---

### 7. Review Process
A member of the team will be assigned to review the pull request. Comments will be provided by the team member as the review process progresses.

You will see a few [GitHub Status Checks](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-status-checks) that help validate that your pull request is according to our standards:

* **ci/circleci: build**: We use [CircleCI](https://circleci.com/gh/demisto/demisto-sdk) to run a full build on each commit of your pull request. The build will run our content validation hooks, linting and unit test. We require that the build pass (green build). Follow the `details` link of the status to see the full build UI of CircleCI.
* **LGTM analysis: Python**: We use [LGTM](https://lgtm.com) for continues code analysis. If your PR introduces new LGTM alerts, the LGTM bot will add a comment with links for more details. Usually, these alerts are valid and you should try to fix them. If the alert is a false positive, specify this in a comment of the PR.
* **license/cla**: Status check that all contributors have signed our contributor license agreement (see below).

---

### 8. Contributor License Agreement (Relevant only for Exernal PRs)
Before merging any PRs, we need all contributors to sign a contributor license agreement. By signing a contributor license agreement, we ensure that the community is free to use your contributions.

When you contribute a new pull request, a bot will evaluate whether you have signed the CLA. If required, the bot will comment on the pull request, including a link to accept the agreement. The CLA document is available for review as a [PDF](docs/cla.pdf).

If the `license/cla` status check remains on *Pending*, even though all contributors have accepted the CLA, you can recheck the CLA status by visiting the following link (replace **[PRID]** with the ID of your PR): https://cla-assistant.io/check/demisto/demisto-sdk?pullRequest=[PRID] .

If you have a suggestion or an opportunity for improvement that you've identified, please open an issue in this repo.
Enjoy and feel free to reach out to us on the [DFIR Community Slack channel](http://go.demisto.com/join-our-slack-community), or at [info@demisto.com](mailto:info@demisto.com).

repository: SukhnandanMalhotra/demisto-sdk

repo_name: SukhnandanMalhotra/demisto-sdk


text:
# frontend
![Flutter Web](https://github.com/NulpCarRent/frontend/workflows/Flutter%20Web/badge.svg?branch=master)

Frontend part of Car Rental project

## Run(Debug)

To run this project on Chrome device:
`flutter run -d chrome`

## Build deploy version

`flutter build web`

## Configuration
To set your API strings endpoint, edit `config/api_config.dart`

repository: NulpCarRent/frontend

gha_language: Dart

gha_license_id: MIT

repo_name: NulpCarRent/frontend


text:
# Changelog
All notable changes to this project will be documented in this file.

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

## [0.2.0] - Unreleased

### Added
- Documentation for some classes
  [22ccafc](https://github.com/DeepseaPlatform/coastal/commit/22ccafc762f2a679b6cec5410383f779f536d815)
  [878f159](https://github.com/DeepseaPlatform/coastal/commit/878f159064ac52508a6e199b2aec53f7bd1c1e24)
- Method names are now displayed next to frame in detailed log
  [f24a40d](https://github.com/DeepseaPlatform/coastal/commit/f24a40def8a1fe9c267777955ae6bcf8e59dea12)

### Changed
- Eclipse configurations have been tweaked to remove unnecessary information
  [b24da00](https://github.com/DeepseaPlatform/coastal/commit/b24da004b892a31a8b931e130e125d402e385e77)

### Deprecated
- ...

### Removed
- Unneeded libraries
- Examples have moved to a [separate project](https://github.com/DeepseaPlatform/coastal-examples)

### Fixed
- Fix bug in Z3 translation that caused mismatched bit vector sizes
  [f3c8218](https://github.com/DeepseaPlatform/coastal/commit/f3c8218031f32fb5f730738365f7ddd6b7f74349)
- [Issue #42](https://github.com/DeepseaPlatform/coastal/issues/42)
  Fix bug that execute symbolic instruction before related classes were initialized
  [227236e](https://github.com/DeepseaPlatform/coastal/commit/227236e3347dbaadfd3f97c71a157d322e9490b6)

## [0.1.0] - 2019.11.24

This list is incomplete because we did not commit often enough and did not exercise enough self-discipline to update this file carefully.

### Added
- Add gradle configuration to publish COASTAL on Maven Central Repository
- Add model for String.valueOf()
  [6711b3e](https://github.com/DeepseaPlatform/coastal/commit/6711b3eaae451ba743b37a2a2196286ce1305c83)
  [e36b38c](https://github.com/DeepseaPlatform/coastal/commit/e36b38cacdff5dd228d46656ec471fcb3ec73633)
- Add model for String.contains()
  [86db343](https://github.com/DeepseaPlatform/coastal/commit/86db343141bdc4558600dafc62ca9cf2732f6963)
- Add model for String.equals()
  [125140a](https://github.com/DeepseaPlatform/coastal/commit/125140a578625fb561d78fc73abd2089e9559758)
- Add model for String.<init>()
  [fc97dc5](https://github.com/DeepseaPlatform/coastal/commit/fc97dc577cf6861d12f3dff6d5e8abd2d85e6b5c)
- Add model for Character.isLetter()
  [57a451b](https://github.com/DeepseaPlatform/coastal/commit/57a451b79de786e7a4586459c4121f67bb683e81)
- Add model for StringBuilder
  [8bf651d](https://github.com/DeepseaPlatform/coastal/commit/8bf651d370f3fb62b60e26a0651e9f971438e9b8)
- [Issue #29](https://github.com/DeepseaPlatform/coastal/issues/29)
  Add instruction ``ANEWARRAY``
  [9116d42](https://github.com/DeepseaPlatform/coastal/commit/9116d42f1949edc04e8825f4427f6bd8519c35a0)
- Add instruction ``LOOKUPSWITCH``
  [68512dc](https://github.com/DeepseaPlatform/coastal/commit/68512dcc24b403ab4a096fa5939b1b78dd82e04e)
- Add instruction ``D2I``
  [d4ebe95](https://github.com/DeepseaPlatform/coastal/commit/d4ebe95be6e1526bfb868a002b9a71c7c4d003db)
  [2b58d95](https://github.com/DeepseaPlatform/coastal/commit/2b58d95edc79931462b0d6c8e5128eddea2eacba)
- Add instruction ``F2I``, ``F2L``, ``D2L``
  [cd46640](https://github.com/DeepseaPlatform/coastal/commit/cd466408230531d2bc3c268bc7954d20cebfcbc9)
- Add instruction ``I2D``, ``I2F``, ``FNEG``
  [21212ce](https://github.com/DeepseaPlatform/coastal/commit/21212cea251d5f7f2f0887aa26c5652b60fd1a2a)
- Add instruction ``L2D``
  [14603ff](https://github.com/DeepseaPlatform/coastal/commit/14603ffee306e365552ef13ad8126b3e39a2b260)
- Add instruction ``L2F``, ``L2I``
  [8672856](https://github.com/DeepseaPlatform/coastal/commit/86728562c8ffbaac9af5c6f1d1b24696edc1bf03)
- Add instruction ``INSTANCEOF``
  [ce24b0e](https://github.com/DeepseaPlatform/coastal/commit/ce24b0e7d9554b6e76a61dd6bbb319525253740b)
- Add instruction ``D2F``
  [43ad3b7](https://github.com/DeepseaPlatform/coastal/commit/43ad3b7e8cfdaae8b021f86a9596f5468700a9a2)
- Add instruction ``DASTORE``, ``FASTORE``, ``LASTORE``, ``BASTORE``, ``DALOAD``, ``FALOAD``, ``LALOAD``, ``BALOAD``
  [081cfb5](https://github.com/DeepseaPlatform/coastal/commit/081cfb51cef3342893784d92c7cf422298233d2d)
- Add SV-COMP 2019 as test cases.  (But for now these tests are ignored.)
  [e3939d1](https://github.com/DeepseaPlatform/coastal/commit/e3939d119e1f97f4d9d1458aa37734df4455b994)
- Tests for line coverage
  [e5f6236](https://github.com/DeepseaPlatform/coastal/commit/e5f623608a2f62a6e79f94029ced39e7db9e58d2)
- Javadoc for ``za.ac.sun.cs.coastal`` package
  [dba5ce3](https://github.com/DeepseaPlatform/coastal/commit/dba5ce3acfe230c4d6942cf4cc011a5231462bef)
- Caching of models inside COASTAL
  [1e3022c](https://github.com/DeepseaPlatform/coastal/commit/1e3022cda63225c873a4dc68a6f0ced9cb8f3516)
- In-house solver
  [2dad358](https://github.com/DeepseaPlatform/coastal/commit/2dad358bd8c8134c998038f67adf18aaa2e8b3fe)
- Support for all Java primitive types
  [2dad358](https://github.com/DeepseaPlatform/coastal/commit/2dad358bd8c8134c998038f67adf18aaa2e8b3fe)
- Average speed in GUI (number of divers/surfers/refinements per second)
  [e395280](https://github.com/DeepseaPlatform/coastal/commit/e395280f8e8b573f012f491e62691ec3c91807c4)
- [Issue #23](https://github.com/DeepseaPlatform/coastal/issues/23)
  Options to write instrumented code to file and to the log
  [69a7255](https://github.com/DeepseaPlatform/coastal/commit/69a72555dd664427a872a6e52234430cfe2663aa)
- [Issue #25](https://github.com/DeepseaPlatform/coastal/issues/25)
  Add support for user specified program entry points and (command-line) arguments
  [3edc259](https://github.com/DeepseaPlatform/coastal/commit/3edc259910277c4d33e0e5e5313b47c2b6aa10e4)
- User specified seeds for RandomTesting strategy
  [159ed27](https://github.com/DeepseaPlatform/coastal/commit/159ed27e44f796923929fba7bc4c8517624d82a8)
- [Issue #24](https://github.com/DeepseaPlatform/coastal/issues/24)
  Tests for the RandomTesting strategy
  [159ed27](https://github.com/DeepseaPlatform/coastal/commit/159ed27e44f796923929fba7bc4c8517624d82a8)
- Hybrid fuzzer
  [dd5fb83](https://github.com/DeepseaPlatform/coastal/commit/dd5fb83ee98981f9187f5a0d8c384f7b5942b95a)
  [71d7cda](https://github.com/DeepseaPlatform/coastal/commit/71d7cda9645646bae36415a27a3ccd4f3afcca40)
  [aadcfc1](https://github.com/DeepseaPlatform/coastal/commit/aadcfc1289055c2343273b999af3097e3b1dc177)
- Add command-line option (``-quiet``) to switch off detailed log
  [daa866d](https://github.com/DeepseaPlatform/coastal/commit/daa866df324d66cf6692c85099053ea6bd4d95be)
- Add "Stop" button for the GUI.
  [cbb488b](https://github.com/DeepseaPlatform/coastal/commit/cbb488b20327aa12e4514a78b9b0565868523ed7)
- Add display of inputs for each dive/surf
  [1bd9605](https://github.com/DeepseaPlatform/coastal/commit/1bd960517045fe9852dc1d1f27f35ee19b4dfd88)
- Add creation of symbolic variables
  [244e468](https://github.com/DeepseaPlatform/coastal/commit/244e4682df19bfd7a4c0b8d0bf93823b31934bbb)

### Changed
- Eclipse launch configurations for quiet and verbose runs
  [a9a5a30](https://github.com/DeepseaPlatform/coastal/commit/a9a5a3073bd2d1c5464678f9fdc86ba4b2eab2e4)
- [Issue #32](https://github.com/DeepseaPlatform/coastal/issues/32)
  Z3 path now set in coastal configuration.
  [7349894](https://github.com/DeepseaPlatform/coastal/commit/7349894a7be0397d30ad973e75ba96222abbbb29)
- Improved text-based drawing of path trees
  [2dad358](https://github.com/DeepseaPlatform/coastal/commit/2dad358bd8c8134c998038f67adf18aaa2e8b3fe)
- Better handling of exceptions
  [2dad358](https://github.com/DeepseaPlatform/coastal/commit/2dad358bd8c8134c998038f67adf18aaa2e8b3fe)
  [a8386c4](https://github.com/DeepseaPlatform/coastal/commit/a8386c4c7f6c327d263cd38b897b253fa24da041)
- Improved support for random testing
  [60eccd2](https://github.com/DeepseaPlatform/coastal/commit/60eccd27562304b69a991f6ecb14b65dd6e8ce84)
  [691c43c](https://github.com/DeepseaPlatform/coastal/commit/691c43c0dd02149d4664c7ec716caa6b4c7d194b)
- Improved fuzzing
- Updated documentation
  [5a8e5cd](https://github.com/DeepseaPlatform/coastal/commit/5a8e5cd7af9f2f00ce99a294dcb4067d54a9a3cc)
  [1d65545](https://github.com/DeepseaPlatform/coastal/commit/1d6554591e2c36c81ae1c7b620b299d3ddd3d1ca)
  [04eeef0](https://github.com/DeepseaPlatform/coastal/commit/04eeef0acbfb2797f8aaec3344c750eb2c266535)
  [173925e](https://github.com/DeepseaPlatform/coastal/commit/173925ebb0c79a05ced6affaa1edc5e60960f948)
  [3887c1f](https://github.com/DeepseaPlatform/coastal/commit/3887c1f943fa4e0cf089490084a8c2c8f76fe622)
  [5bdc976](https://github.com/DeepseaPlatform/coastal/commit/5bdc97693b33aa8162e00869320349bc744d921a)
- Change COASTAL configuration files from XML to Java properties
  [b2cec72](https://github.com/DeepseaPlatform/coastal/commit/b2cec7218f2cb5cbfeca21017f7eef129e5771ff)
  [8ce795b](https://github.com/DeepseaPlatform/coastal/commit/8ce795ba1896f7a4792b5144812d517f6b208c42)
  [7f51209](https://github.com/DeepseaPlatform/coastal/commit/7f51209f722408d2139130a22ad6f8470f153451)

### Removed
- Removed dependency on GREEN
  [2dad358](https://github.com/DeepseaPlatform/coastal/commit/2dad358bd8c8134c998038f67adf18aaa2e8b3fe)

### Fixed
- Fixed bug with stack sizes
- Fixed bug with character description in in-house solver output
- [Issue #37](https://github.com/DeepseaPlatform/coastal/issues/37)
  Removed tricky COASTAL version code
  [d18fc4f](https://github.com/DeepseaPlatform/coastal/commit/d18fc4fd7aafe9cc8386c4be6ade6a1a39058c75)
- Fix bug in generational strategy
  [0b3be3a](https://github.com/DeepseaPlatform/coastal/commit/0b3be3a6bcc8ec078e04b37867f4e8aea07a934a)
  [aab8c61](https://github.com/DeepseaPlatform/coastal/commit/aab8c61ca4f770961b3add7ad7eaaad199b2f5a1)
  [6437a3b](https://github.com/DeepseaPlatform/coastal/commit/6437a3ba3bacfe99767dd2695891e6afb68a81a8)
- Fix error in advanced DUP instructions
  [183dfdb](https://github.com/DeepseaPlatform/coastal/commit/183dfdb96109153b7974903eecdfe1cdf5b1abe3)

## [0.0.2] - 2018.12.14

### Added
- Divers and strategies run in separate threads
- Allow users to specify number of initial threads
- Introduce lightweight instrumentation for fuzzing
- Random testing [a436562](https://github.com/DeepseaPlatform/coastal/commit/a4365621dd3968b80819a0f316d5de88ced9724f)
- Reporting of queue waiting times
- Min/max bounds for all data types -- not just integers
- Generational path strategy [59fea07](https://github.com/DeepseaPlatform/coastal/commit/59fea07ad3d88462bf17bc60860f0d0d2a5f02b8)
- Line coverage observer [a436562](https://github.com/DeepseaPlatform/coastal/commit/a4365621dd3968b80819a0f316d5de88ced9724f)
- Primitive GUI to show progress
- Log file includes thread ids
- New test structure
- Read class files from JAR files

### Changed
- COASTAL now reads configuration from XML files
- Listener mechanism replaced with publish-subscribe broker
- Listeners changed to Observers
- Version reporting made more robust
- Path tree allows concurrent updates
- Improved class loading
- Reduced console output [e1cc755](https://github.com/DeepseaPlatform/coastal/commit/e1cc7557e6c8e4317a3a307046dae0ed615f241d)
- Significant refactoring to allow for lightweight testing and fuzzing
- [Issue #17](https://github.com/DeepseaPlatform/coastal/issues/17) Duplicate and constant conjuncts now appear in the path tree [d44d531](https://github.com/DeepseaPlatform/coastal/commit/d44d531309d9ffdb66a8af752e01f35f53e2df91)

### Fixed
- Travis CI docker setup [dd9bca9](https://github.com/DeepseaPlatform/coastal/commit/dd9bca9ced9369f31dd21c7d82d8701cb4468791)
- [Bug #15](https://github.com/DeepseaPlatform/coastal/issues/15): new symbolic character bounds were incorrect (String.java::charAt__I__C) [8d9b5ba](https://github.com/DeepseaPlatform/coastal/commit/8d9b5ba7da9d0d5b79210fbce9df8957e349ce0b)
- [Bug #19](https://github.com/DeepseaPlatform/coastal/issues/19): COASTAL incorrectly complained about too few runs when only surfers executed [032346f](https://github.com/DeepseaPlatform/coastal/commit/032346f4d9a12a54a59a660c26b95e959872ca07)
- [Bug #20](https://github.com/DeepseaPlatform/coastal/issues/20): Options in XML are now pased to the strategy/observer/delegate they are intended for.  They are also correctly accessed. [2bfa3e1](https://github.com/DeepseaPlatform/coastal/commit/2bfa3e1c1ef8ca761be6746a01f64fee3916ca84)
- [Bug #18](https://github.com/DeepseaPlatform/coastal/issues/18): New docker image works, despite remaining bug [cca94f7](https://github.com/DeepseaPlatform/coastal/commit/cca94f785a58969e7fd775f58118dc8c31506a8f)

## [0.0.1] - 2018.11.27

### Added
- Exception handling
- Symbolic operations in examples such as analysis termination and markers
- Some initial documentation
- Some initial testing
- Path/conjunct/time/execution limits
- Instruction coverage computation
- Support for java `switch` statements
- Improved configuration settings
- Additional examples
- Breadth-first and random strategies (in addition to depth-first)
- All features from DEEPSEA

### Changed
- Setting `coastal.recordmarks` replaced with marker listener
- Internally, (almost) all classes are made non-static

### Removed
- All `coastal.dump...` settings

repository: DeepseaPlatform/coastal

gha_language: Java

repo_name: DeepseaPlatform/coastal


text:
# osmdiff

A read-only interface to OpenStreetMap change APIs and files. See also [pyosm](https://github.com/iandees/pyosm) which can do similar things.

## Installing

`pip install osmdiff`

## Usage

### Reading

Retrieve the latest replication diff from the OSM API:

```python
>>> from osmdiff import OSMChange
>>> o = OSMChange()
>>> o.frequency = "minute"  # the default
>>> o.get_state()  # retrieve current sequence ID
>>> o.sequence_number
2704451
>>> o.retrieve()  # retrieve from API
>>> o
OSMChange (677 created, 204 modified, 14 deleted)
```

Read a replication diff from a file:

```python
>>> from osmdiff import OSMChange
>>> o = OSMChange(file="test_osmchange.xml")
>>> o
OSMChange (831 created, 368 modified, 3552 deleted)
```

Retrieve the latest Augmented Diff from Overpass:

```python
>>> from osmdiff import AugmentedDiff
>>> a = AugmentedDiff()
>>> a.get_state()
>>> a.sequence_number
2715051
>>> a.retrieve()
>>> a
AugmentedDiff (747 created, 374 modified, 55 deleted)
```

Read an augmented diff file:

```python
>>> from osmdiff import AugmentedDiff
>>> a = AugmentedDiff(file="test_adiff.xml")
>>> a
AugmentedDiff (2329 created, 677 modified, 39 deleted)
```

### Inspect contents

Get all the things that `chris66` has created:

```
>>> [n for n in a.create if n.attribs["user"] == "chris66"]
[Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Node<PHONE_NUMBER>, Way 539648222 (5 nodes), Way 539648223 (5 nodes), Way 539648323 (5 nodes)]
```

Get all `residential` ways that were modified:

```python
>>> [n["new"] for n in a.modify if type(n["new"]) == Way and n["new"].tags.get("highway") == "residential"]
[Way 34561958 (3 nodes), Way 53744484 (6 nodes), Way 53744485 (6 nodes), Way 122650942 (3 nodes), Way 283221266 (4 nodes), Way 344272652 (5 nodes), Way 358243999 (13 nodes), Way 410489319 (5 nodes), Way 452218081 (10 nodes)]
```

Get all ways that were changed to `residential` from something else:

```python
>>> [n["new"] for n in a.modify if type(n["new"]) == Way and n["new"].tags.get("highway") == "residential" and n["old"].tags["highway"] != "residential"]
[Way 410489319 (5 nodes), Way 452218081 (10 nodes)]
```

Inspect details:

```python
>>> w = [n["new"] for n in a.modify if n["new"].attribs["id"] == "452218081"]
>>> w
[Way 452218081 (10 nodes)]
>>> w[0]
Way 452218081 (10 nodes)
>>> w[0].tags
{'highway': 'residential'}
>>> w[0].attribs
{'id': '452218081', 'version': '2', 'timestamp': '2017-11-10T13:52:01Z', 'changeset': '53667190', 'uid': '2352517', 'user': 'carths81'}
>>> w[0].attribs
{'id': '452218081', 'version': '2', 'timestamp': '2017-11-10T13:52:01Z', 'changeset': '53667190', 'uid': '2352517', 'user': 'carths81'}
>>> w[0].bounds
['12.8932677', '43.3575917', '12.8948117', '43.3585947']
```

repository: themmes/osmdiff

gha_license_id: NOASSERTION

repo_name: themmes/osmdiff


text:
## 1.1. Understanding the need for a system like Kubernetes

## 1.1.1. Moving from monolithic apps to microservices

## 1.1.2. Providing a consistent environment to applications

## 1.1.3. Moving to continuous delivery: DevOps and NoOps

## 1.2. Introducing container technologies

## 1.2.1. Understanding what containers are

how exactly containers can isolate processes if they’re running on the same operating system. Two mechanisms make this possible.
- L???? N?????????
- c?????? (L???? C?????? G?????)

***

(regarding Linux Namespaces) The following kinds of namespaces exist: ??? (there are 6, name at least 2)

## 1.2.2. Introducing the Docker container platform

A big difference between Docker-based container images and VM images is that container images are composed of ???, which can be shared and reused across multiple images.

***

Three main concepts in Docker comprise this scenario (packaging, distributing, and running applications):
- ??? is something you package your application and its environment into. It contains the filesystem that will be available to the application and other metadata, such as the path to the executable that should be executed
- When you build your image, you can either run it on the computer you’ve built it on, or you can push (upload) the image to a ??? and then pull (download) it on another computer and run it there.
- A running ??? is a process running on the host running Docker, but it’s completely isolated from both the host and all other processes running on it.

***

layers don’t only make distribution more efficient, they also help reduce ??? (what?).

## 1.2.3. Introducing rkt—an alternative to Docker

## 1.3. Introducing Kubernetes

## 1.3.1. Understanding its origins

## 1.3.2. Looking at Kubernetes from the top of a mountain

## 1.3.3. Understanding the architecture of a Kubernetes cluster

At the hardware level, a Kubernetes cluster is composed of many nodes, which can be split into two types:
- The m????? node which hosts the Kubernetes Control Plane that controls and manages the whole Kubernetes system
- W????? nodes that run the actual applications you deploy

***

The Control Plane is what controls the cluster and makes it function. It consists of multiple components that can run on a single master node or be split across multiple nodes and replicated to ensure high availability. These components are
- The Kubernetes A?? ??????, which you and the other Control Plane components communicate with
- The S????????, which assigns a worker node to each deployable component of your application
- The C????????? M??????, which performs cluster-level functions, such as replicating components, keeping track of worker nodes, handling node failures, and so on
- ????, a reliable distributed data store that persistently stores the cluster configuration.

***

The task of running, monitoring, and providing services to your applications is done by the following components:
- c???????? r??????, which runs your containers
- The K??????, which talks to the API server and manages containers on its node
- The k???-?????, which load-balances network traffic between application components

## 1.3.4. Running an application in Kubernetes

## 1.3.5. Understanding the benefits of using Kubernetes

repository: ruslanbes/kubia-selftest

repo_name: ruslanbes/kubia-selftest


text:
---
layout: post
title: Push jobs to Resque without Resque
---
At [Wuaki.tv](http://wuaki.tv) we are moving to a services oriented architecture and the first service we developed was the users service. We had to move all the users related logic to a new service and make our applications to use a service oriented model instead of the ActiveRecord model we had.

Actually we are using [Errbit](https://github.com/errbit/errbit) to collect the errors/crashes from our applications so we have the [Airbrake](https://github.com/airbrake/airbrake) gem as dependency in all the projects we need to monitor the errors. The Airbrake configuration we usually set, normally in a initializer, is something like this:

{% highlight ruby %}
{% include ruby/airbrake_config.rb %}
{% endhighlight %}

In the code above we see three dependencies, Airbrake, OurAmaizingQueue and AirbrakeDeliveryWorker. As you may know, [Resque](https://github.com/defunkt/resque) jobs need to be a module or class with a class method called `perform`. So even the Resque workers are executed by another application, we have a dependency with the job class constant. Of course, we have a dependency with OurAmaizingQueue that is just a wrapper to enqueue into Resque.

We wanted to avoid Resque and OurAmaizingQueue (that lives in a common internal gem) dependencies in our super-tiny-micro-awesome users service. So...what if we can push the job into the correct Resque queue without the Resque gem and our internal huge gem? We tried it and this is the result:

{% highlight ruby %}
{% include ruby/enqueue_to_resque.rb %}
{% endhighlight %}

The 'magic' is easy, we only need to encode a Hash into JSON with a `class` key that stores the class name of the job to be enqueued and a `args` key with the arguments for the job stored like an Array. This JSON is pushed into the tail of the list identified by the key `resque:queue:name_of_the_queue_to_use`.

Another important thing we shouldn't forget is to add the queue name to use into the `resque:queues` set to make Resque listening this queue.

The Airbrake initializer changes a bit cause we don't have the job class constant and we need to enqueue the job using a string.

{% highlight ruby %}
{% include ruby/airbrake_config_without_resque.rb %}
{% endhighlight %}

Cause we don't have the job class, we need to use explicity the queue name and the job class name. All these stuff was working fine while we only needed to enqueue jobs but finally our users service needs to perform its own Resque jobs, so we added Resque gem as dependency :-) and `MicroAwesomeService::Queue` became just a wrapper to enqueue jobs.


text:
# Lorenz Attractor

This project is a simple website for visualising a [Lorenz Attractor](https://en.wikipedia.org/wiki/Lorenz_system), a type of dynamical system described by an ordinary differential equation. The Lorenz system is known as a "strange attractor" due to its unpredictable and chaotic behaviour.

This project is a web programming example in the "from scratch" style to show basic concepts of interactive HTML forms, numerical integration and 3D graphics.

Try it here: **https://tkoster.github.io/lorenz**

![screenshot of a lorenz attractor](doc/screenshot.png)

## Usage

The solution of the differential equation is plotted using a perspective 3D projection on an HTML canvas. The viewpoint can be moved interactively by clicking and dragging the mouse over the canvas. Use the mouse wheel to change the distance from the eye to the curve.

Parameters can be entered as a fraction. For example `1/2` is accepted as an alternative to `0.5`.

## Implementation Notes

This project is a web programming example in the "from scratch" style.

The differential equation solver and linear algebra functions are written in JavaScript using ordinary arrays. No JavaScript libraries are used. No WebGL is used.

The following browser APIs are used:
- [Document Object Model](https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model) to access the interactive page elements from JavaScript, including
  - [Pointer Events](https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events) and the [Pointer Lock API](https://developer.mozilla.org/en-US/docs/Web/API/Pointer_Lock_API) to implement click-and-drag
- [Canvas API](https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API) to draw the 2D curve

No optimisations are implemented except eliding 2D curve points that are too close to the previous point on the curve to be distinct.

## Known Issues

- No frustum clipping - elements behind the camera are drawn incorrectly
- Non-square aspect ratio in the perspective projection transformation
- Poor support for mobile and tablet devices

repository: tkoster/lorenz

repo_name: tkoster/lorenz


text:
# Instructions to Test the Routing Algorithm

## Instructions for Ubuntu:
```bash
sudo apt-get update
sudo apt-get install -y \
  autoconf automake build-essential git libtool libgmp-dev \
  libsqlite3-dev python python3 net-tools zlib1g-dev
git clone https://github.com/ElementsProject/lightning.git
cd lightning
./configure
make
```

The routing algorithm can be tested with any arbitrary topology and channel parameters.
```bash
cd gossipd/test/
```
The `test_params` file contains the parameters to test the algorithm. Refer to `test_params_format` for the input format. Edit `test_params` as necessary, and then run:
```
./run-custom_routing_test < test_params
```

Refer to the [detailed instructions](https://github.com/samvid25/lightning/blob/master/doc/INSTALL.md) to build c-lightning on other OSs.

filename: Custom-Routing Instructions.md


text:
# Layer Abstract

**Purpose**: Test that each layer element contains an Abstract element.

**Prerequisites**

**Test method**

* Send a getCapabilities request to the service endpoint. Into the response:

  * For each [Layer](#layer) element:

    * Check that zero or one [Abstract](#abstract) element exists. If it exists,

        * Check that its value is not empty.

**Reference(s)**:
* [TG VS](./README.md#ref_TG_VS), Chapter <IP_ADDRESS>.4.3, Requirement 34

**Test type**: Automated

**Notes**

The multiplicity of this element is 0 or 1 for each layer element.

Abstract element shall be subject to multilingualism, therefore, translations shall appear in each mono-lingual capabilities localised documents.

**Contextual XPath references**

The namespace prefixes used as described in [README.md](./README.md#namespaces).

Abbreviation                                               |  XPath expression (relative to /wms:WMS_Capabilities)
---------------------------------------------------------- | -------------------------------------------------------------------------
Layer  | wms:Capability/*/wms:Layer
Abstract  | wms:Capability/*/wms:Layer/wms:Abstract

repository: inspire-eu-validation/view-service

repo_name: inspire-eu-validation/view-service


text:
---
layout: post
title: Mercer University Semi-Autonomous Sub Project 2015
subtitle: A brief over view of a past project.
bigimg: /img/sub.jpg
---

At Mercer University in 2015, I worked on a semi-autonomous sub for my senior design project. The purpose of the project long term was to create a fully autonomous submarine that could be used by the school as a platform for robotics research.  The project started before us and a base sub was created. It was able to be controlled by an xbox controller. When we started the sub had fallen into a state of disrepair. I worked with my team Andrew Buff (Vision Software) and Jonathan Alfred (Electrical Work/Physical Changes) to fix the semi-autonomous operation using ROS.

The hardware was upgraded to a Raspberry Pi 2. The semi-autonomous software was written in ROS. If anyone has used ROS they will know the hardest part is getting it installed. This was one of our biggest challenges since I was new to ROS at the time. Once everything was installed the code was relatively simple. I wrote some ROS modules in Python to create a command queue and pass those commands with timings to an Arduino controlling the motors.

Click the picture below to see a video demo of the result.

If you are a future sub team trying to get information about the software or the project here are some helpful links.
 - The full code can be seen [Here](https://github.com/tylerburnham42/MercerSubProject).
 - Detailed instructions for installation can be found [Here](https://github.com/tylerburnham42/MercerSubProject/wiki).
 - Our CDR Presentation can be found [Here](
https://docs.google.com/presentation/d/1Z-bZuzuaYkGfOctUI9qapzBFxaOFF7h08rAaH1NICBE/edit?usp=sharing).

If you may need anything else email me and I can probably help you out.


text:
# Contributing to Openmaize

The first part of this document covers the goals and the scope of Openmaize,
and then lists some ways that developers can contribute to it.

After that, there is more technical information about the contributing
process.

## Features

* handles login / logout
* authenticates users using sessions
* provides excellent documentation
* is framework-agnostic
* is lightweight

## Ways you can contribute

* Find bugs
* Add to, or improve, the documentation
* Add further plugs / checks you think might be useful

## Bug reports

Guidelines for bug reports:

1. **Use the GitHub issue search** — check if the issue has already been
   reported.

2. **Check if the issue has been fixed** — try to reproduce it using the
   `master` branch in the repository.

3. **Report the problem** — open an issue.

Please try to be as detailed as possible in your report. Include information about
your Operating System, as well as your Erlang and Elixir versions. Please provide steps to
reproduce the issue as well as the outcome you were expecting. Also include any error messages
that you get. All these details will help developers to fix any potential bugs.

## Feature requests

First, make sure that the feature fits in with the goals of Openmaize. Then,
open an issue explaining what feature you would like implemented. Please
provide technical / practical details about why this feature is needed.

**IMPORTANT**: Remember that you need to convince us that this feature is needed.

## Contributing documentation

Documentation is a very important part of the whole Openmaize package. The
documentation is not limited to how a module or function works, but also
provides, succintly and clearly, more general information related to the
aims of this project, such as authentication, authorization, JSON
Web Tokens, etc.

If you are contributing documentation that makes any claims, for example,
that something is faster, more secure, etc., please provide link(s) to the
sources of this information.

## Pull requests

Good pull requests - patches, improvements, documentation, new features - are
a fantastic help. They should remain focused in scope and avoid containing
unrelated commits.

**IMPORTANT**: By submitting a patch, you agree that your work will be
licensed under the license used by the project.

If you have any large pull request in mind (e.g. implementing features,
refactoring code, etc), **please ask first** otherwise you risk spending
a lot of time working on something that the project's developers might
not want to merge into the project.

Please adhere to the coding conventions in the project (indentation,
accurate comments, etc.) and don't forget to add your own tests and
documentation. When working with git, we recommend the following process
in order to craft an excellent pull request:

1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork,
   and configure the remotes:

   ```bash
   # Clone your fork of the repo into the current directory
   git clone https://github.com/<your-username>/openmaize
   # Navigate to the newly cloned directory
   cd openmaize
   # Assign the original repo to a remote called "upstream"
   git remote add upstream https://github.com/riverrun/openmaize
   ```

2. If you cloned a while ago, get the latest changes from upstream:

   ```bash
   git checkout master
   git pull upstream master
   ```

3. Create a new topic branch (off of `master`) to contain your feature, change,
   or fix.

   **IMPORTANT**: Making changes in `master` is discouraged. You should always
   keep your local `master` in sync with upstream `master` and make your
   changes in topic branches.

   ```bash
   git checkout -b <topic-branch-name>
   ```

4. Commit your changes in logical chunks. Keep your commit messages organized,
   with a short description in the first line and more detailed information on
   the following lines. Feel free to use Git's
   [interactive rebase](https://help.github.com/articles/interactive-rebase)
   feature to tidy up your commits before making them public.

5. Make sure all the tests are still passing.

   ```bash
   mix test
   ```

6. Push your topic branch up to your fork:

   ```bash
   git push origin <topic-branch-name>
   ```

7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
    with a clear title and description.

8. If you haven't updated your pull request for a while, you should consider
   rebasing on master and resolving any conflicts.

   **IMPORTANT**: _Never ever_ merge upstream `master` into your branches. You
   should always `git rebase` on `master` to bring your changes up to date when
   necessary.

   ```bash
   git checkout master
   git pull upstream master
   git checkout <your-topic-branch>
   git rebase master
   ```

Thank you for your contributions!

repository: riverrun/openmaize

repo_name: riverrun/openmaize


text:
# Paper
A custom media publishing platform.

## prerequisites
- node.js 12+
- yarn

## tech stack
- typescript
- vue.js
- sass
- pug
- koa
- webpack

## installation
```
git clone https://github.com/Ai-Open-Source/Paper
cd Paper
yarn
```

## commands
```js
{
  "dev" // starts frontend and backend in development mode
  "build" // builds frontend
  "start" //
  "server:dev"
  "server:build"
  "client:dev"
  "client:build"
  "lint"
}

license: Unlicense

repository: Ai-Open-Source/Paper

repo_name: Ai-Open-Source/Paper


text:
## Submit your Animoji

The [/src/store/listAnime.js](/src/store/listAnime.js) file contains all the Animojis in the json array.

To add your Animoji, follow the steps below:

* Fork & give star to animoji repository
* Think of the emojis that characterize your favorite anime, you can look for Emojis at [getemoji.com](https://getemoji.com/).
* Open [listAnime.js](/src/store/listAnime.js) in the [/src/store/](/src/store/) directory and use the template below to add animoji:
* The Maximum emojis is 5 and The Minimum emojis is 3, other than that your PR will be closed

This is example :

```
{
        animeEmoji:" 🏀 🏆 ⛹🏻♂",
        animeName:"Kuroko's Basketball",
        animeYear:2012,
        animeLink:"https://myanimelist.net/anime/11771/Kuroko_no_Basket"
    }
```
* If the PR is based on issue please mention reference the issue
* 1 Pull request for 1 anime
* Please check [listAnime.js](/src/store/listAnime.js) and make sure that your PR is not duplicate
* Dont forget to fill the template in [pull_request_template.md](.github/PULL_REQUEST_TEMPLATE/pull_request_template.md)
* If you make pull request without template , your pull request will be ignored
* Submit a Pull Request with your Animoji.
* Wait until approved and combined, updates will be published to [animoji.netlify.com](https://animoji.netlify.com/)

repository: YogaSakti/animoji

repo_name: YogaSakti/animoji