alexaegis / advent-of-code Goto Github PK

My solutions for Advent of Code

License: MIT License

TypeScript 89.67% Rust 6.69% Smarty 0.37% JavaScript 2.61% Shell 0.01% Python 0.65%

advent-of-code advent-of-code-javascript advent-of-code-python advent-of-code-rust advent-of-code-typescript python rust typescript advent-of-code-2015 advent-of-code-2016

advent-of-code's Introduction

Hey hey people

advent-of-code's People

Contributors

Stargazers

Watchers

Forkers

gsoleilhac binaryprovider anderskromann folke beaucarigan manudefrutosvila henrymoulton tkhadir keifferculbreth sofiabargues teeman60

advent-of-code's Issues

An in-range update of nyc is breaking the build 🚨

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency nyc was updated from `15.0.0` to `15.0.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 21.48% (+0.00%) compared to 1e9aba1 (Details).
✅ codecov/patch: Coverage not affected when comparing 1e9aba1...e7265a3 (Details).
✅ Security audit: 1 unmaintained
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 1 failures, 0 warnings, and 0 notices.
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 4 failures, 0 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
❌ Test Suite (1.39.0): There are 5 failures, 10 warnings, and 0 notices.
❌ Test Suite (stable): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 12 commits.

d9a76d5 chore(release): 15.0.1
3a577f0 fix: Ignore insignificant lines when coalesce text report (#1300)
df34c1c fix: Data merge concurrency limit to prevent OOM (#1293)
befbf08 chore: A test where nyc output help text to stderr was flaky (#1269)
9260a70 docs: Remove nyc containing object in json config examples (#1276)
bed4729 chore: Minor Markdown tweaks (#1256)
fcacc46 chore: Update node-preload to v0.2.1 (#1257)
8b4a148 chore: Update standard to v14.3.1 (#1250)
676ca86 chore: Switch to AppVeyor for Windows testing (#1255)
fcd2115 chore: Conditionally set envPath.APPDATA for tests (#1254)
3445b19 chore: Remove the unused uuid dependency (#1252)
559ada2 chore: Remove the unused js-yaml dependency. (#1247)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Split up language scoreboards for each year

It's getting too long, the language readme file should just link to each year, and show the badges

RUSTSEC-2020-0016: `net2` crate has been deprecated; use `socket2` instead

net2 crate has been deprecated; use socket2 instead

Details
Status	unmaintained
Package	`net2`
Version	`0.2.34`
URL	deprecrated/net2-rs@`3350e38`
Date	2020-05-01

The net2 crate has been deprecated
and users are encouraged to considered socket2 instead.

See advisory page for additional details.

how long takes day 15?

Hi,
I see you have also long run on day 15 with 30M iterations. How long does it run on your machine?
Mine run

6 minutes on node
2,5 minutes on deno
15s on python
4,5s on php
It looks really strange that js is so slow compared to other languages.

Clean up Vec2-like constructs

Migrate to Vec2 everywhere
make generic Vec2Pair
use Area for BoundingBox

Make coordinate system consistent

It should mimic the way displays work, top left is 0,0 and visible coordinates are all positive. Moving SOUTH is adding 0,1. Moving NORTH is adding 0,-1

An in-range update of @types/workerpool is breaking the build 🚨

The devDependency @types/workerpool was updated from `5.0.0` to `5.0.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/workerpool is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 5.35% remains the same compared to d22488e (Details).
✅ codecov/patch: Coverage not affected when comparing d22488e...687df3b (Details).
✅ Security audit: 1 unmaintained
✅ Test Suite (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ Test Suite (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
✅ lint: null
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 1 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of codecov is breaking the build 🚨

The devDependency codecov was updated from `3.6.2` to `3.6.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

codecov is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 21.48% remains the same compared to caa041a (Details).
✅ codecov/patch: Coverage not affected when comparing caa041a...96d7d70 (Details).
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Test Suite (1.39.0): There are 6 failures, 10 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 1 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Test Suite (stable): There are 2 failures, 10 warnings, and 0 notices.
❌ audit: There are 2 failures, 1 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Release Notes for v3.6.3

AWS Codebuild fixes + package updates

Commits

The new version differs by 10 commits.

7856231 v3.6.3
96e6d96 Merge pull request #166 from codecov/chore/updates
c8ea169 update deps
7c4cdc4 Merge pull request #149 from aiell0/master
62389fa Merge pull request #162 from codecov/dependabot/npm_and_yarn/handlebars-4.5.3
73ae008 Add dependabot config
ccf3862 Update README.md
467a495 Bump handlebars from 4.1.2 to 4.5.3
8acbe96 Retest
acd92f4 Test when codebuild isn't triggered by webhooks.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of workerpool is breaking the build 🚨

The dependency workerpool was updated from `5.0.2` to `5.0.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

workerpool is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

✅ codecov/project: 21.32% remains the same compared to 75c69df (Details).
✅ codecov/patch: Coverage not affected when comparing 75c69df...f642c39 (Details).
✅ Security audit: 1 unmaintained
❌ Clippy (1.39.0): There are 7 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
❌ Test Suite (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Test Suite (stable): There are 6 failures, 10 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 13 commits.

f8d488e Publish v5.0.3
8ac4c38 Merge remote-tracking branch 'origin/master'
ab74b14 Fix library not working in the browser, see #106
03cab45 Update devDependencies
1b2703c Update webpack to the latest version 🚀 (#118)
f10415c Update webpack to the latest version 🚀 (#117)
32de40e Update uglify-js to the latest version 🚀 (#116)
e7165c2 Update uglify-js to the latest version 🚀 (#115)
51b2a8f Update uglify-js to the latest version 🚀 (#114)
ae84698 Update handlebars to the latest version 🚀 (#113)
d698ffb Update find-process to the latest version 🚀 (#111)
e13bbfa Update handlebars to the latest version 🚀 (#110)
ed75abe Update uglify-js to the latest version 🚀 (#109)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Running TSlint from CI

Command:
npm run lint
package.json:

"scripts": {
		"lint": "./node_modules/.bin/tslint --project ."
}

Expected Output:
Running without error, logging linting errors.

Actual Output:

npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] lint: `tslint --project .`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     ..\npm-cache\_logs\2019-12-07T05_00_34_810Z-debug.log

Testing with local execution of tslint:

./node_modules/.bin/tslint --project .
Output:
Runs without error.

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from `7.0.0` to `7.0.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 21.48% remains the same compared to caa041a (Details).
✅ codecov/patch: Coverage not affected when comparing caa041a...fd1f072 (Details).
❌ Test Suite (1.39.0): There are 6 failures, 10 warnings, and 0 notices.
❌ Test Suite (stable): There are 2 failures, 10 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ audit: There are 2 failures, 1 warnings, and 0 notices.
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 10 failures, 0 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Release Notes for v7.0.1

7.0.1 / 2020-01-25

🐛 Fixes

#4165: Fix exception when skipping tests programmatically (@juergba)
#4153: Restore backwards compatibility for reporterOptions (@holm)
#4150: Fix recovery of an open test upon uncaught exception (@juergba)
#4147: Fix regression of leaking uncaught exception handler (@juergba)

📖 Documentation

#4146: Update copyright & trademark notices per OJSF (@boneskull)
#4140: Fix broken links (@KyoungWan)

🔩 Other

#4133: Print more descriptive error message (@Zirak)

Commits

The new version differs by 9 commits.

d0f04e9 Release v7.0.1
2277958 update CHANGELOG for v7.0.1 [ci skip]
0be3f78 Fix exception when skipping tests programmatically (#4165)
c0f1d14 uncaughtException: fix recovery when current test is still running (#4150)
9c10ada Fix backwards compability break for reporterOptions
a24683f Throw a descriptive error when a non-function is given to a runnable (#4133)
579fd09 update copyright & trademark notices per OJSF; closes #4145
0e1ccbb Fix leaking global 'uncaughtException' handler (#4147)
7d78f20 Broken links in docs (#4140)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Duplicate Object key in .vscode/settings.json

You have a duplicate object key:

{
    "mochaExplorer.files": "src/**/*.spec.ts", //row 32
    "mochaExplorer.files": "test/**/*.ts", //row 45
}

RUSTSEC-2020-0053: dirs is unmaintained, use dirs-next instead

dirs is unmaintained, use dirs-next instead

Details
Status	unmaintained
Package	`dirs`
Version	`1.0.5`
URL	https://github.com/dirs-dev/dirs-rs
Date	2020-10-16

The dirs crate is not maintained any more;
use dirs-next instead.

See advisory page for additional details.

Explore porting every TS code to Deno

ts: use top level await

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from `6.2.1` to `6.2.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ codecov/project: 80.87% remains the same compared to d1f7378 (Details).
✅ codecov/patch: Coverage not affected when comparing d1f7378...628db74 (Details).
❌ Travis CI - Branch: The build failed.

Release Notes for v6.2.2

6.2.2 / 2019-10-18

🐛 Fixes

#4025: Fix duplicate EVENT_RUN_END events upon uncaught exception (@juergba)
#4051: Fix "unhide" function in html reporter (browser) (@pec9399)
#4063: Fix use of esm in Node.js v8.x (@boneskull)
#4033: Fix output when multiple async exceptions are thrown (@juergba)

📖 Documentation

#4046: Site accessibility fixes (@Mia-jeong)
#4026: Update docs for custom reporters in browser (@Lindsay-Needs-Sleep)
#3971: Adopt new OpenJS Foundation Code of Conduct (@craigtaub)

Commits

The new version differs by 12 commits.

843a322 6.2.2
aec8b02 update CHANGELOG for v6.2.2 [ci skip]
7a8b95a npm audit fixes
cebddf2 Improve reporter documentation for mocha in browser. (#4026)
3f7b987 uncaughtException: report more than one exception per test (#4033)
ee82d38 modify alt text of image from Backers to Sponsors inside Sponsors section in Readme (#4046)
e9c036c special-case parsing of "require" in unparseNodeArgs(); closes #4035 (#4063)
954cf0b Fix HTMLCollection iteration to make unhide function work as expected (#4051)
816dc27 uncaughtException: fix double EVENT_RUN_END events (#4025)
9650d3f add OpenJS Foundation logo to website (#4008)
f04b81d Adopt the OpenJSF Code of Conduct (#3971)
aca8895 Add link checking to docs build step (#3972)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

rust criterion still makes a target folder inside a subcrate when running benches

Blocking issue: bheisler/criterion.rs#192

An in-range update of prettier is breaking the build 🚨

The devDependency prettier was updated from `1.18.2` to `1.19.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 79.16% remains the same compared to 175c112 (Details).
✅ codecov/patch: Coverage not affected when comparing 175c112...e2921f6 (Details).
❌ Travis CI - Branch: The build failed.

Release Notes for Prettier 1.19: Long awaited Vue option, TypeScript 3.7 and new JavaScript features

diff

🔗 Release Notes

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/chai is breaking the build 🚨

The devDependency @types/chai was updated from `4.2.6` to `4.2.7`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/chai is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 84.82% remains the same compared to 02f73de (Details).
✅ codecov/patch: Coverage not affected when comparing 02f73de...5868461 (Details).
✅ Security audit: 1 unmaintained
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
✅ Test Suite (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ Test Suite (stable): There are 0 failures, 10 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
✅ build (macOS-latest, 13.x): null
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
✅ build (macOS-latest, 12.x): null
✅ build (windows-latest, 13.x): null
✅ build (windows-latest, 12.x): null
✅ build (ubuntu-latest, 13.x): null
✅ build (ubuntu-latest, 12.x): null
✅ lint: null
✅ Travis CI - Branch: The build passed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @thi.ng/transducers is breaking the build 🚨

The dependency @thi.ng/transducers was updated from `6.1.0` to `6.2.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@thi.ng/transducers is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

✅ codecov/project: 21.48% remains the same compared to caa041a (Details).
✅ codecov/patch: Coverage not affected when comparing caa041a...279f3bb (Details).
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
❌ audit: There are 2 failures, 1 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Test Suite (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Test Suite (stable): There are 6 failures, 10 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 212 commits.

93d8af8 Publish
6c1378d build: update dev deps in all pkgs/examples
7f31ba4 build: update .npmignore in all pkgs
0cae667 build(dsp): update pkg keywords
aa3803c docs: update readmes (links)
edfe813 docs(rstream-gestures): update docstring
cde813e build: remove branch info pkg meta
acfa908 docs(intervals): fix readme code example
5813afc fix(ecs): fix #178, refactor listener handling
68b8d89 docs(morton): minor fix/adds readme
f1d2ac1 refactor(examples): update fft-synth to use new dsp api
2aead70 docs(dsp): update readme
9efd69f refactor(dsp): restructure oscillators, fft, window, update gen-diagrams
ff99055 build: update pkg metas
fadf749 docs: update all readmes (all links to dev branch)

There are 212 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

ts: compile regexes

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `12.0.6` to `12.0.7`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ coverage/coveralls: First build on greenkeeper/@types/node-12.0.7 at 87.179% (Details).
❌ Travis CI - Branch: The build failed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

RUSTSEC-2020-0056: stdweb is unmaintained

stdweb is unmaintained

Details
Status	unmaintained
Package	`stdweb`
Version	`0.4.20`
URL	koute/stdweb#403
Date	2020-05-04

The author of the stdweb crate is unresponsive.

Maintained alternatives:

See advisory page for additional details.

Categorize parsers based on puzzle types

RUSTSEC-2018-0015: term is looking for a new maintainer

term is looking for a new maintainer

Details
Status	unmaintained
Package	`term`
Version	`0.5.2`
URL	Stebalien/term#93
Date	2018-11-19
Unaffected versions	`> 0.6.1`

The author of the term crate does not have time to maintain it and is looking
for a new maintainer.

Some maintained alternatives you can potentially switch to instead, depending
on your needs:

See advisory page for additional details.

hello～ day 4 part 2, I have a problem

Why the demo works, but the answer is wrong : (

Can you help me? thank you

/**
 * part two
 * @param {number[]} selectedList
 * @param {number[][][]} grids
 * @returns {number}
 */
function partTwo(selectedList, grids) {
  /**
   * @param {{num: number, validate: boolean}[]} line
   * @returns {boolean}
   */
  const hasWinners = line => {
    return line.every(obj => obj.validate === true)
  }

  // init
  const _grids = grids.map(grid => grid.map(line => line.map(num => ({ num, validate: false }))))
  let lastCalledNumber = selectedList[0]
  let sumOfAllUnmarkedNumbers = 0

  selected: for (let i = 0; i < selectedList.length; i++) {
    const selected = selectedList[i]

    for (let g = 0; g < _grids.length; g++) {
      const grid = _grids[g]

      for (let l = 0; l < grid.length; l++) {
        const line = grid[l]

        for (let n = 0; n < line.length; n++) {
          const num = line[n]

          if (num.num === selected) _grids[g][l][n].validate = true

          const col = grid.reduce((acc, line) => {
            acc.push(line[n])
            return acc
          }, [])

          if (hasWinners(col)) {
            lastCalledNumber = selected
            sumOfAllUnmarkedNumbers = grid.reduce((acc_grid, line) => {
              acc_grid += line.reduce((acc_line, obj) => {
                if (obj.validate === false) acc_line += obj.num
                return acc_line
              }, 0)
              return acc_grid
            }, 0)
            break selected
          }
        }
      }
    }
  }

  return lastCalledNumber * sumOfAllUnmarkedNumbers
}

An in-range update of npm-check-updates is breaking the build 🚨

The devDependency npm-check-updates was updated from `4.0.0` to `4.0.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

npm-check-updates is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 84.82% remains the same compared to 02f73de (Details).
✅ codecov/patch: Coverage not affected when comparing 02f73de...2e45754 (Details).
✅ Security audit: 1 unmaintained
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
✅ lint: null
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ build (macOS-latest, 13.x): null
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
✅ build (macOS-latest, 12.x): null
✅ build (windows-latest, 13.x): null
✅ build (windows-latest, 12.x): null
✅ Test Suite (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ build (ubuntu-latest, 13.x): null
✅ Test Suite (stable): There are 0 failures, 10 warnings, and 0 notices.
✅ build (ubuntu-latest, 12.x): null
✅ Travis CI - Branch: The build passed.

Commits

The new version differs by 2 commits.

fb013ea 4.0.1
26efdb3 Do not mutate options. Really fixes #615.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

`format` script for prettier throws error on my local Windows env

in the ./package.json file the format script:

	"scripts": {
		"format": "prettier --write \"src/**/*\"",

throws an error on my Windows machine. After adding the file extension .ts to the glob it works.

Error:

C:\Projects\AoC [master ≡ +0 ~4 -0 !]> npm run format

> [email protected] format C:\Projects\AoC
> prettier --write "./src/**/*"

[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-one\input.ts 143ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-one\script-one.ts 18ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-one\script-two.ts 10ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-one\task.md 72ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
[error] No parser could be inferred for file: src\day-two\input.txt
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\main-task-one.ts 10ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\script-one.ts 13ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\script-two.ts 10ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\task.md 34ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\test.ts 14ms
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] format: `prettier --write "./src/**/*"`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] format script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\richa\AppData\Roaming\npm-cache\_logs\2019-12-07T04_36_19_865Z-debug.log

Adding the file extension:

	"scripts": {
		"format": "prettier --write \"src/**/*.ts\"",

Expected Output:

C:\Projects\AoC> npm run format

> [email protected] format C:\Projects\AoC
> prettier --write "./src/**/*.ts"

[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-one\input.ts 145ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-one\script-one.ts 16ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-one\script-two.ts 11ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\main-task-one.ts 12ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\script-one.ts 27ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\script-two.ts 11ms
[warn] Ignored unknown option { eslintIntegration: true }.
[warn] Ignored unknown option { jsonEnable: true }.
src\day-two\test.ts 13ms

refactor hierarchy and move languages to the top level

An in-range update of source-map-support is breaking the build 🚨

The devDependency source-map-support was updated from `0.5.13` to `0.5.14`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

source-map-support is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 80.87% (+2.07%) compared to 55cdf81 (Details).
✅ codecov/patch: Coverage not affected when comparing 55cdf81...cf310b0 (Details).
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 4 commits.

8cb9300 0.5.14
4715e2d Update built files
8a92ccf Merge pull request #253 from JLHwung/fix-function-name-logic
3f4006b fix: function name should be obtained from next frams’s position

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

IntCode interpreter

Make a proper intcode interpreter for Day 2 and Day 5. In rust make it a separate cargo.
Put it under 2019. Prepare for multiple libraries like this. Decide if it would be better in a years, in the projects, next to the lib or wherever.

An in-range update of tslint-plugin-prettier is breaking the build 🚨

The devDependency tslint-plugin-prettier was updated from `2.0.1` to `2.1.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tslint-plugin-prettier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ codecov/project: 3.68% (-1.78%) compared to efcf10e (Details).
✅ codecov/patch: Coverage not affected when comparing efcf10e...0e6fe76 (Details).
✅ Security audit: 1 unmaintained
❌ Test Suite (1.39.0): There are 6 failures, 10 warnings, and 0 notices.
❌ Test Suite (stable): There are 6 failures, 10 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 23 commits.

be5ee44 chore(release): 2.1.0
0420071 feat: respect .prettierignore (#317)
0f0b819 chore(deps): [security] bump lodash from 4.17.11 to 4.17.15 (#302)
24efe60 chore: fix CI error on node 4
a202090 chore(deps): bump mixin-deep from 1.3.1 to 1.3.2 (#300)
dfb762c chore(deps): bump lodash.template from 4.4.0 to 4.5.0 (#295)
11c74d7 chore(deps): bump handlebars from 4.0.12 to 4.1.2 (#294)
1b80c16 chore(deps): bump js-yaml from 3.12.0 to 3.13.1 (#293)
814261f chore(deps): update dependency tslint-config-prettier to v1.18.0 (#292)
701683c chore(deps): update dependency @types/node to v4.9.3 (#290)
6bf1b63 docs(readme): update usage (#288)
6280d7c docs: update links (#284)
74a17b7 chore(deps): update dependency tslint-config-prettier to v1.16.0 (#281)
f7d5388 chore(deps): move codecov to devDeps (#283)
63e083c chore(renovate): update configs

There are 23 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @thi.ng/iterators is breaking the build 🚨

The dependency @thi.ng/iterators was updated from `5.1.7` to `5.1.8`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@thi.ng/iterators is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

✅ codecov/project: 21.48% remains the same compared to caa041a (Details).
✅ codecov/patch: Coverage not affected when comparing caa041a...64f3cf7 (Details).
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
❌ Test Suite (1.39.0): There are 2 failures, 10 warnings, and 0 notices.
❌ Test Suite (stable): There are 6 failures, 10 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ audit: There are 2 failures, 1 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 212 commits.

93d8af8 Publish
6c1378d build: update dev deps in all pkgs/examples
7f31ba4 build: update .npmignore in all pkgs
0cae667 build(dsp): update pkg keywords
aa3803c docs: update readmes (links)
edfe813 docs(rstream-gestures): update docstring
cde813e build: remove branch info pkg meta
acfa908 docs(intervals): fix readme code example
5813afc fix(ecs): fix #178, refactor listener handling
68b8d89 docs(morton): minor fix/adds readme
f1d2ac1 refactor(examples): update fft-synth to use new dsp api
2aead70 docs(dsp): update readme
9efd69f refactor(dsp): restructure oscillators, fft, window, update gen-diagrams
ff99055 build: update pkg metas
fadf749 docs: update all readmes (all links to dev branch)

There are 212 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

add user agent to auto generator

https://www.reddit.com/r/adventofcode/comments/z9dhtd/please_include_your_contact_info_in_the_useragent/

An in-range update of mocha-parallel-tests is breaking the build 🚨

The devDependency mocha-parallel-tests was updated from `2.2.2` to `2.3.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha-parallel-tests is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

✅ codecov/project: 21.48% remains the same compared to caa041a (Details).
✅ codecov/patch: Coverage not affected when comparing caa041a...a1c2932 (Details).
✅ Security audit: 1 unmaintained
❌ Test Suite (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Test Suite (stable): There are 6 failures, 10 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 12 commits.

ecc1962 2.3.0
bf74b90 Update changelog and add new contributor
0d71437 Update file test case
aa1f834 test: fix the tests for the --file option
ee65666 feat: add --file option
ca5078f Update changelog
c447886 Skip full trace test on older Node.JS for mocha@7
9f49972 Update mocha types
4a32a88 Support mocha@7
889b767 Update dependencies
7c33ee9 Fix security warnings
d22fcaf Add funding information

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of workerpool is breaking the build 🚨

The dependency workerpool was updated from `5.0.1` to `5.0.2`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

workerpool is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

✅ codecov/project: 79.16% remains the same compared to 175c112 (Details).
✅ codecov/patch: Coverage not affected when comparing 175c112...84e80cd (Details).
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 8 commits.

9904429 Publish v5.0.2
0ee929c Update uglify-js to the latest version 🚀 (#107)
f66567b Fix environment detection in browser (#106)
bc91dce Update devDependencies
832e706 Update uglify-js to the latest version 🚀 (#102)
0bc0430 Update devDependencies
01be27b Fix typo (#100)
a1e9512 Update devDependencies

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

ts: solution decorator

With support for multiple types of solutions with a default master solution (Certain types of optimizations like speed, memory, readability)

An in-range update of source-map-support is breaking the build 🚨

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency source-map-support was updated from `0.5.16` to `0.5.17`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ codecov/project: 21.48% (+0.00%) compared to 1e9aba1 (Details).
✅ codecov/patch: Coverage not affected when comparing 1e9aba1...37f95fb (Details).
✅ Security audit: 1 unmaintained
❌ Test Suite (1.39.0): There are 5 failures, 10 warnings, and 0 notices.
❌ Test Suite (stable): There are 2 failures, 10 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 1 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 4 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 5 commits.

4cba532 0.5.17
c71c5d1 Update built files
2a08b93 Merge pull request #269 from addaleax/fix-workers
59b442f Use braces around if body
1db97ff Fix Node.js Worker support by not shimming uncaughtException

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @thi.ng/memoize is breaking the build 🚨

The dependency @thi.ng/memoize was updated from `1.1.6` to `1.1.7`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@thi.ng/memoize is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

✅ codecov/project: 21.48% remains the same compared to caa041a (Details).
✅ codecov/patch: Coverage not affected when comparing caa041a...243dda7 (Details).
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
❌ Test Suite (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Test Suite (stable): There are 6 failures, 10 warnings, and 0 notices.
❌ audit: There are 2 failures, 1 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 10 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 1 failures, 0 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build failed.

Commits

The new version differs by 212 commits.

93d8af8 Publish
6c1378d build: update dev deps in all pkgs/examples
7f31ba4 build: update .npmignore in all pkgs
0cae667 build(dsp): update pkg keywords
aa3803c docs: update readmes (links)
edfe813 docs(rstream-gestures): update docstring
cde813e build: remove branch info pkg meta
acfa908 docs(intervals): fix readme code example
5813afc fix(ecs): fix #178, refactor listener handling
68b8d89 docs(morton): minor fix/adds readme
f1d2ac1 refactor(examples): update fft-synth to use new dsp api
2aead70 docs(dsp): update readme
9efd69f refactor(dsp): restructure oscillators, fft, window, update gen-diagrams
ff99055 build: update pkg metas
fadf749 docs: update all readmes (all links to dev branch)

There are 212 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from `12.12.14` to `12.12.15`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ Security audit: 1 unmaintained
❌ Clippy (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ Clippy (stable): There are 6 failures, 0 warnings, and 0 notices.
✅ Test Suite (1.39.0): There are 0 failures, 10 warnings, and 0 notices.
✅ Test Suite (stable): There are 0 failures, 10 warnings, and 0 notices.
❌ lint: There are 1 failures, 0 warnings, and 0 notices.
✅ audit: There are 0 failures, 1 warnings, and 0 notices.
✅ Check (1.39.0): There are 0 failures, 8 warnings, and 0 notices.
✅ Check (stable): There are 0 failures, 8 warnings, and 0 notices.
❌ build (macOS-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (macOS-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 13.x): There are 2 failures, 0 warnings, and 0 notices.
❌ Rustfmt (1.39.0): There are 2 failures, 0 warnings, and 0 notices.
❌ build (windows-latest, 12.x): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 13.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Rustfmt (stable): There are 2 failures, 0 warnings, and 0 notices.
❌ build (ubuntu-latest, 12.x): There are 1 failures, 0 warnings, and 0 notices.
❌ Travis CI - Branch: The build errored.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of @types/chai is breaking the build 🚨

The devDependency @types/chai was updated from `4.2.3` to `4.2.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

✅ codecov/project: No report found to compare against (Details).
✅ codecov/patch: Coverage not affected. (Details).
❌ Travis CI - Branch: The build failed.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

RUSTSEC-2019-0031: spin is no longer actively maintained

spin is no longer actively maintained

Details
Status	unmaintained
Package	`spin`
Version	`0.5.2`
URL	mvdnes/spin-rs@`7516c80`
Date	2019-11-21
Unaffected versions	`> 0.5.2`

The author of the spin crate does not have time or interest to maintain it.

Consider lock_api (a subproject of
parking_lot) as an alternative which also supports no_std environments.

See advisory page for additional details.

alexaegis / advent-of-code Goto Github PK

advent-of-code's Introduction

Hey hey people

advent-of-code's People

Contributors

Stargazers

Watchers

Forkers

advent-of-code's Issues

The devDependency nyc was updated from 15.0.0 to 15.0.1.

The devDependency @types/workerpool was updated from 5.0.0 to 5.0.1.

The devDependency codecov was updated from 3.6.2 to 3.6.3.

The dependency workerpool was updated from 5.0.2 to 5.0.3.

The devDependency mocha was updated from 7.0.0 to 7.0.1.

7.0.1 / 2020-01-25

🐛 Fixes

📖 Documentation

🔩 Other

The devDependency mocha was updated from 6.2.1 to 6.2.2.

6.2.2 / 2019-10-18

🐛 Fixes

📖 Documentation

The devDependency prettier was updated from 1.18.2 to 1.19.0.

The devDependency @types/chai was updated from 4.2.6 to 4.2.7.

The dependency @thi.ng/transducers was updated from 6.1.0 to 6.2.0.

The devDependency @types/node was updated from 12.0.6 to 12.0.7.

The devDependency npm-check-updates was updated from 4.0.0 to 4.0.1.

The devDependency source-map-support was updated from 0.5.13 to 0.5.14.

The devDependency tslint-plugin-prettier was updated from 2.0.1 to 2.1.0.

The dependency @thi.ng/iterators was updated from 5.1.7 to 5.1.8.

The devDependency mocha-parallel-tests was updated from 2.2.2 to 2.3.0.

The dependency workerpool was updated from 5.0.1 to 5.0.2.

The devDependency source-map-support was updated from 0.5.16 to 0.5.17.

The dependency @thi.ng/memoize was updated from 1.1.6 to 1.1.7.

The devDependency @types/node was updated from 12.12.14 to 12.12.15.

The devDependency @types/chai was updated from 4.2.3 to 4.2.4.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency nyc was updated from `15.0.0` to `15.0.1`.

The devDependency @types/workerpool was updated from `5.0.0` to `5.0.1`.

The devDependency codecov was updated from `3.6.2` to `3.6.3`.

The dependency workerpool was updated from `5.0.2` to `5.0.3`.

The devDependency mocha was updated from `7.0.0` to `7.0.1`.

The devDependency mocha was updated from `6.2.1` to `6.2.2`.

The devDependency prettier was updated from `1.18.2` to `1.19.0`.

The devDependency @types/chai was updated from `4.2.6` to `4.2.7`.

The dependency @thi.ng/transducers was updated from `6.1.0` to `6.2.0`.

The devDependency @types/node was updated from `12.0.6` to `12.0.7`.

The devDependency npm-check-updates was updated from `4.0.0` to `4.0.1`.

The devDependency source-map-support was updated from `0.5.13` to `0.5.14`.

The devDependency tslint-plugin-prettier was updated from `2.0.1` to `2.1.0`.

The dependency @thi.ng/iterators was updated from `5.1.7` to `5.1.8`.

The devDependency mocha-parallel-tests was updated from `2.2.2` to `2.3.0`.

The dependency workerpool was updated from `5.0.1` to `5.0.2`.

The devDependency source-map-support was updated from `0.5.16` to `0.5.17`.

The dependency @thi.ng/memoize was updated from `1.1.6` to `1.1.7`.

The devDependency @types/node was updated from `12.12.14` to `12.12.15`.

The devDependency @types/chai was updated from `4.2.3` to `4.2.4`.