Resolve error deploying to Heroku

-----> Node.js app detected
-----> Creating runtime environment
   NPM_CONFIG_LOGLEVEL=error
   NPM_CONFIG_PRODUCTION=true
   NODE_ENV=production
   NODE_MODULES_CACHE=true

-----> Installing binaries
engines.node (package.json):  unspecified
engines.npm (package.json):   unspecified (use default)
   Resolving node version (latest stable) via semver.io...
   Downloading and installing node 5.11.1...
   Using default npm version: 3.8.6

-----> Restoring cache
Skipping cache restore (new runtime signature)
-----> Building dependencies
Pruning any extraneous modules
Installing node modules (package.json)
   ><EMAIL_ADDRESS>postinstall /tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c
   > typings install

   sh: 1: typings: not found

   npm ERR! Linux 3.13.0-85-generic
   npm ERR! argv "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.heroku/node/bin/node" "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.heroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.npmrc"
   npm ERR! node v5.11.1
   npm ERR! npm  v3.8.6
   npm ERR! file sh
   npm ERR! code ELIFECYCLE
   npm ERR! errno ENOENT
   npm ERR! syscall spawn
   npm ERR<EMAIL_ADDRESS>postinstall: `typings install`
   npm ERR! spawn ENOENT
   npm ERR!
   npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'typings install'.
   npm ERR! Make sure you have the latest version of node.js and npm installed.
   npm ERR! If you do, this is most likely a problem with the team6finalproject package,
   npm ERR! not with npm itself.
   npm ERR! Tell the author that this fails on your system:
   npm ERR!     typings install
   npm ERR! You can get information on how to open an issue for this project with:
   npm ERR!     npm bugs team6finalproject
   npm ERR! Or if that isn't available, you can get their info via:
   npm ERR!     npm owner ls team6finalproject
   npm ERR! There is likely additional logging output above.

   npm ERR! Please include the following file with any support request:
   npm ERR!     /tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/npm-debug.log

-----> Build failed
   We're sorry this build is failing! You can troubleshoot common issues here:
   https://devcenter.heroku.com/articles/troubleshooting-node-deploys

   Some possible problems:

   - Node version not specified in package.json
   https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version

   Love,
   Heroku

!     Push rejected, failed to compile Node.js app

Looks like it is calling typings install before npm install, so it is
trying to call typings install before it has the typings binary.
On Fri, May 27, 2016 at 9:59 AM Josh Sherman<EMAIL_ADDRESS>wrote:

-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NPM_CONFIG_PRODUCTION=true
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
Resolving node version (latest stable) via semver.io...
Downloading and installing node 5.11.1...
Using default npm version: 3.8.6
-----> Restoring cache
Skipping cache restore (new runtime signature)
-----> Building dependencies
Pruning any extraneous modules
Installing node modules (package.json)

<EMAIL_ADDRESS>postinstall /tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c
typings install

sh: 1: typings: not found
npm ERR! Linux 3.13.0-85-generic
npm ERR! argv "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.heroku/node/bin/node" "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.heroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.npmrc"
npm ERR! node v5.11.1
npm ERR! npm  v3.8.6
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>postinstall: typings install
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'typings install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the team6finalproject package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     typings install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs team6finalproject
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls team6finalproject
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/npm-debug.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:

Node version not specified in package.json
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version

Love,
Heroku
! Push rejected, failed to compile Node.js app
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222185133,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nuzUjY96kMNbOmnvKR0NP9AMFKrCks5qFxTSgaJpZM4Ienlj
.

It would help if I just follow the setup instructions
I’ll get this done soon, shouldn’t be a problem :)
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 12:07 PM
To: PennStateSoftwareTest/FinalProjectPennState<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error deploying to Heroku (#25)
Looks like it is calling typings install before npm install, so it is
trying to call typings install before it has the typings binary.
On Fri, May 27, 2016 at 9:59 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NPM_CONFIG_PRODUCTION=true
NODE_ENV=production
NODE_MODULES_CACHE=true
-----> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
Resolving node version (latest stable) via semver.io...
Downloading and installing node 5.11.1...
Using default npm version: 3.8.6
-----> Restoring cache
Skipping cache restore (new runtime signature)
-----> Building dependencies
Pruning any extraneous modules
Installing node modules (package.json)

<EMAIL_ADDRESS><EMAIL_ADDRESS>postinstall /tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c
typings install

sh: 1: typings: not found
npm ERR! Linux 3.13.0-85-generic
npm ERR! argv "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.heroku/node/bin/node" "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.heroku/node/bin/npm" "install" "--unsafe-perm" "--userconfig" "/tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/.npmrc"
npm ERR! node v5.11.1
npm ERR! npm v3.8.6
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS><EMAIL_ADDRESS>postinstall: typings install
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS><EMAIL_ADDRESS>postinstall script 'typings install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the team6finalproject package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! typings install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs team6finalproject
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls team6finalproject
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /tmp/build_35f987622da477e118e7a1b4e561081b/PennStateSoftwareTest-FinalProjectPennState-f862e0c/npm-debug.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:

Node version not specified in package.json
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version

Love,
Heroku
! Push rejected, failed to compile Node.js app
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222185133,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nuzUjY96kMNbOmnvKR0NP9AMFKrCks5qFxTSgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222187127 , or mute the thread https://github.com/notifications/unsubscribe/AMuN2IIwxp-aCRtpdKIbAVvKSSEcGIrKks5qFxamgaJpZM4Ienlj .  https://github.com/notifications/beacon/AMuN2BPLZtj8KZp-xnZpw7t15Me9R-etks5qFxamgaJpZM4Ienlj.gif

https://devcenter.heroku.com/articles/troubleshooting-node-deploys

Did you Google it?  They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman<EMAIL_ADDRESS>wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj
.

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449 , or mute the thread https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj .  https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif

i set the engine but it is still failing, there is something else going on here

ok cool.  if you hit a brick wall, we could push it off until next week.
that way, we don;t get too far behind on code.  We can always demo from a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman<EMAIL_ADDRESS>wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign <
<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj
.

same log message?
On Fri, May 27, 2016 at 11:52 AM John Nevins<EMAIL_ADDRESS>wrote:

ok cool.  if you hit a brick wall, we could push it off until next week.
that way, we don;t get too far behind on code.  We can always demo from a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman<EMAIL_ADDRESS>wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign <
<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj
.

yep
I’m I get blocked, I’ll move on to Angular
No prob
It is all good
I’m have fun, no worries  :)
Did you see the new logo?
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:53 PM
To: PennStateSoftwareTest/FinalProjectPennState<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error deploying to Heroku (#25)
same log message?
On Fri, May 27, 2016 at 11:52 AM John Nevins<EMAIL_ADDRESS><EMAIL_ADDRESS>> wrote:

ok cool. if you hit a brick wall, we could push it off until next week.
that way, we don;t get too far behind on code. We can always demo from a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com http://www.joshandmariamusic.com
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211810 , or mute the thread https://github.com/notifications/unsubscribe/AMuN2IrwsBTsyXq8fQjKue85QryoBc8wks5qFy-FgaJpZM4Ienlj .  https://github.com/notifications/beacon/AMuN2Hpl6TRam0K2NJoTQqGG61dVm24vks5qFy-FgaJpZM4Ienlj.gif

ok, cool.  i would hate for you to be frustrated. gal it is fun.  No, I
haven't! I'll look now.
On Fri, May 27, 2016 at 11:54 AM Josh Sherman<EMAIL_ADDRESS>wrote:

yep
I’m I get blocked, I’ll move on to Angular
No prob
It is all good
I’m have fun, no worries :)
Did you see the new logo?
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:53 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign <
<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
same log message?
On Fri, May 27, 2016 at 11:52 AM John Nevins<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>> wrote:

ok cool. if you hit a brick wall, we could push it off until next week.
that way, we don;t get too far behind on code. We can always demo from a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com <
http://www.joshandmariamusic.com>
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>>
Cc: Josh Sherman<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>>; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496

,
or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211810>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2IrwsBTsyXq8fQjKue85QryoBc8wks5qFy-FgaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2Hpl6TRam0K2NJoTQqGG61dVm24vks5qFy-FgaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212161,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nsA_WK_c7N0zBYg5lrOC8ggNs2t8ks5qFy_VgaJpZM4Ienlj
.

Also I have really good phone skills for the ‘talk to a human’ if it comes to that with Heroku
They want our business and will help if I say so
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:56 PM
To: PennStateSoftwareTest/FinalProjectPennState<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error deploying to Heroku (#25)
ok, cool. i would hate for you to be frustrated. gal it is fun. No, I
haven't! I'll look now.
On Fri, May 27, 2016 at 11:54 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

yep
I’m I get blocked, I’ll move on to Angular
No prob
It is all good
I’m have fun, no worries :)
Did you see the new logo?
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:53 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
same log message?
On Fri, May 27, 2016 at 11:52 AM John Nevins<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> > wrote:

ok cool. if you hit a brick wall, we could push it off until next week.
that way, we don;t get too far behind on code. We can always demo from a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com http://www.joshandmariamusic.com  <
http://www.joshandmariamusic.com>
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496

,
or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211810>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2IrwsBTsyXq8fQjKue85QryoBc8wks5qFy-FgaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2Hpl6TRam0K2NJoTQqGG61dVm24vks5qFy-FgaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212161,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nsA_WK_c7N0zBYg5lrOC8ggNs2t8ks5qFy_VgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212516 , or mute the thread https://github.com/notifications/unsubscribe/AMuN2Hphpfp44D8Cr3gtwH5M9k2yfM5Fks5qFzAlgaJpZM4Ienlj .  https://github.com/notifications/beacon/AMuN2Dpl7is2YphXNlnLaFNZEdEAud6sks5qFzAlgaJpZM4Ienlj.gif

The new logo is slick
On Fri, May 27, 2016 at 11:57 AM Josh Sherman<EMAIL_ADDRESS>wrote:

Also I have really good phone skills for the ‘talk to a human’ if it comes
to that with Heroku
They want our business and will help if I say so
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:56 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign <
<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
ok, cool. i would hate for you to be frustrated. gal it is fun. No, I
haven't! I'll look now.
On Fri, May 27, 2016 at 11:54 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

yep
I’m I get blocked, I’ll move on to Angular
No prob
It is all good
I’m have fun, no worries :)
Did you see the new logo?
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:53 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>>
Cc: Josh Sherman<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>>; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
same log message?
On Fri, May 27, 2016 at 11:52 AM John Nevins<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> > wrote:

ok cool. if you hit a brick wall, we could push it off until next week.
that way, we don;t get too far behind on code. We can always demo from
a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com <
http://www.joshandmariamusic.com> <
http://www.joshandmariamusic.com>
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>> >
Cc: Josh Sherman<EMAIL_ADDRESS><mailto:
joshua.v.sherman@gmail.com%20%3cmailto:%0b> <mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >;
Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve
error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496

,
or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404

,

or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211810

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2IrwsBTsyXq8fQjKue85QryoBc8wks5qFy-FgaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2Hpl6TRam0K2NJoTQqGG61dVm24vks5qFy-FgaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212161
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0nsA_WK_c7N0zBYg5lrOC8ggNs2t8ks5qFy_VgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212516>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2Hphpfp44D8Cr3gtwH5M9k2yfM5Fks5qFzAlgaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2Dpl7is2YphXNlnLaFNZEdEAud6sks5qFzAlgaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212942,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nnUcHBN7JKAeP43PSlky5I2ZMob9ks5qFzCUgaJpZM4Ienlj
.

Its pretty good
I’ve asked for some lighting effects
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 2:00 PM
To: PennStateSoftwareTest/FinalProjectPennState<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error deploying to Heroku (#25)
The new logo is slick
On Fri, May 27, 2016 at 11:57 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Also I have really good phone skills for the ‘talk to a human’ if it comes
to that with Heroku
They want our business and will help if I say so
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:56 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
ok, cool. i would hate for you to be frustrated. gal it is fun. No, I
haven't! I'll look now.
On Fri, May 27, 2016 at 11:54 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

yep
I’m I get blocked, I’ll move on to Angular
No prob
It is all good
I’m have fun, no worries :)
Did you see the new logo?
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:53 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
same log message?
On Fri, May 27, 2016 at 11:52 AM John Nevins<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>> > wrote:

ok cool. if you hit a brick wall, we could push it off until next week.
that way, we don;t get too far behind on code. We can always demo from
a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com http://www.joshandmariamusic.com  <
http://www.joshandmariamusic.com> <
http://www.joshandmariamusic.com>
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> <mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> > >
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto:
joshua.v.sherman@gmail.com%20%3cmailto:%0b<EMAIL_ADDRESS><mailto: > <mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>> >;
Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve
error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496

,
or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404

,

or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211810

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2IrwsBTsyXq8fQjKue85QryoBc8wks5qFy-FgaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2Hpl6TRam0K2NJoTQqGG61dVm24vks5qFy-FgaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212161
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0nsA_WK_c7N0zBYg5lrOC8ggNs2t8ks5qFy_VgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212516>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2Hphpfp44D8Cr3gtwH5M9k2yfM5Fks5qFzAlgaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2Dpl7is2YphXNlnLaFNZEdEAud6sks5qFzAlgaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212942,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nnUcHBN7JKAeP43PSlky5I2ZMob9ks5qFzCUgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222213592 , or mute the thread https://github.com/notifications/unsubscribe/AMuN2P1DgjBSfyMy_dlTy0uqJ26r4YmMks5qFzEugaJpZM4Ienlj .  https://github.com/notifications/beacon/AMuN2GxEYvDuM30eZ4aGZxNSFhTquifuks5qFzEugaJpZM4Ienlj.gif

I also defined a color pallet
I’ll send it to you
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 2:00 PM
To: PennStateSoftwareTest/FinalProjectPennState<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error deploying to Heroku (#25)
The new logo is slick
On Fri, May 27, 2016 at 11:57 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Also I have really good phone skills for the ‘talk to a human’ if it comes
to that with Heroku
They want our business and will help if I say so
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:56 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
ok, cool. i would hate for you to be frustrated. gal it is fun. No, I
haven't! I'll look now.
On Fri, May 27, 2016 at 11:54 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

yep
I’m I get blocked, I’ll move on to Angular
No prob
It is all good
I’m have fun, no worries :)
Did you see the new logo?
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:53 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
same log message?
On Fri, May 27, 2016 at 11:52 AM John Nevins<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>> > wrote:

ok cool. if you hit a brick wall, we could push it off until next week.
that way, we don;t get too far behind on code. We can always demo from
a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com http://www.joshandmariamusic.com  <
http://www.joshandmariamusic.com> <
http://www.joshandmariamusic.com>
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> <mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> > >
Cc: Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto:
joshua.v.sherman@gmail.com%20%3cmailto:%0b<EMAIL_ADDRESS><mailto: > <mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>> >;
Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve
error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496

,
or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404

,

or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211810

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2IrwsBTsyXq8fQjKue85QryoBc8wks5qFy-FgaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2Hpl6TRam0K2NJoTQqGG61dVm24vks5qFy-FgaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212161
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0nsA_WK_c7N0zBYg5lrOC8ggNs2t8ks5qFy_VgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212516>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2Hphpfp44D8Cr3gtwH5M9k2yfM5Fks5qFzAlgaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2Dpl7is2YphXNlnLaFNZEdEAud6sks5qFzAlgaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212942,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nnUcHBN7JKAeP43PSlky5I2ZMob9ks5qFzCUgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222213592 , or mute the thread https://github.com/notifications/unsubscribe/AMuN2P1DgjBSfyMy_dlTy0uqJ26r4YmMks5qFzEugaJpZM4Ienlj .  https://github.com/notifications/beacon/AMuN2GxEYvDuM30eZ4aGZxNSFhTquifuks5qFzEugaJpZM4Ienlj.gif

Perfect.  We may have to download a custom version of Foundation instead of
using the one i installed with Bower... let's talk about it tomorrow
morning (in case I don;t make it to the meeting tonight).
On Fri, May 27, 2016 at 12:02 PM Josh Sherman<EMAIL_ADDRESS>wrote:

I also defined a color pallet
I’ll send it to you
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 2:00 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign <
<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
The new logo is slick
On Fri, May 27, 2016 at 11:57 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Also I have really good phone skills for the ‘talk to a human’ if it
comes
to that with Heroku
They want our business and will help if I say so
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:56 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>>
Cc: Josh Sherman<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>>; Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error
deploying to Heroku (#25)
ok, cool. i would hate for you to be frustrated. gal it is fun. No, I
haven't! I'll look now.
On Fri, May 27, 2016 at 11:54 AM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

yep
I’m I get blocked, I’ll move on to Angular
No prob
It is all good
I’m have fun, no worries :)
Did you see the new logo?
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:53 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>> >
Cc: Josh Sherman<EMAIL_ADDRESS><mailto:
joshua.v.sherman@gmail.com%20%3cmailto:%0b> <mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >;
Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>>
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve
error
deploying to Heroku (#25)
same log message?
On Fri, May 27, 2016 at 11:52 AM John Nevins<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: <mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>> > wrote:

ok cool. if you hit a brick wall, we could push it off until next
week.
that way, we don;t get too far behind on code. We can always demo
from
a
local environment.
On Fri, May 27, 2016 at 11:51 AM Josh Sherman <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

Yo, yo
Already did dat
Still failing,
Lemme keep trying first before I ping you
Josh Sherman
http://www.joshandmariamusic.com/ www.joshandmariamusic.com <
http://www.joshandmariamusic.com> <
http://www.joshandmariamusic.com> <
http://www.joshandmariamusic.com>
for bookings
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 1:48 PM
To: PennStateSoftwareTest/FinalProjectPennState <
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>> <mailto: mailto:
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS>> > >
Cc: Josh Sherman<EMAIL_ADDRESS><mailto:
joshua.v.sherman@gmail.com%20%3cmailto:%0b> <mailto:
joshua.v.sherman@gmail.com%20%3cmailto:%0b <mailto:
joshua.v.sherman@gmail.com%20%3cmailto:%0b> > <mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>> >;
Assign <
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><mailto: mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS>> >
Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve
error
deploying to Heroku (#25)
Did you Google it? They require an "engine" property to specify the
version of node we are using, so you should probably start with
that.
On Fri, May 27, 2016 at 11:38 AM Josh Sherman <
<EMAIL_ADDRESS><EMAIL_ADDRESS><mailto:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://devcenter.heroku.com/articles/troubleshooting-node-deploys

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222208496

,
or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0niqQW04_z3tkCSiIzpWZSJyQh75zks5qFywzgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222210449

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2GOlt4NG20r3mM3bXsrzhELs4oMqks5qFy42gaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2PFcbhCfUC3prPoRE7pND8OxLQScks5qFy42gaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211404

,

or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0nkQ6zGWgH58-QdKynpSaWkd8lZBUks5qFy8hgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222211810

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2IrwsBTsyXq8fQjKue85QryoBc8wks5qFy-FgaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2Hpl6TRam0K2NJoTQqGG61dVm24vks5qFy-FgaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212161

,
or mute the thread
<

https://github.com/notifications/unsubscribe/AFI0nsA_WK_c7N0zBYg5lrOC8ggNs2t8ks5qFy_VgaJpZM4Ienlj

.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <

https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212516

, or mute the thread <

https://github.com/notifications/unsubscribe/AMuN2Hphpfp44D8Cr3gtwH5M9k2yfM5Fks5qFzAlgaJpZM4Ienlj

. <

https://github.com/notifications/beacon/AMuN2Dpl7is2YphXNlnLaFNZEdEAud6sks5qFzAlgaJpZM4Ienlj.gif

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222212942
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AFI0nnUcHBN7JKAeP43PSlky5I2ZMob9ks5qFzCUgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222213592>
, or mute the thread <
https://github.com/notifications/unsubscribe/AMuN2P1DgjBSfyMy_dlTy0uqJ26r4YmMks5qFzEugaJpZM4Ienlj>
. <
https://github.com/notifications/beacon/AMuN2GxEYvDuM30eZ4aGZxNSFhTquifuks5qFzEugaJpZM4Ienlj.gif>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222214161,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0nkZ-MitcnJw9Tdp4P8rpP0kioZElks5qFzG7gaJpZM4Ienlj
.

https://thawing-falls-50722.herokuapp.com/
I have pushed this getting started tutorial app to our heroku account

No worries.  We'll get the build straight for Heroku.
On Fri, May 27, 2016 at 2:59 PM Josh Sherman<EMAIL_ADDRESS>wrote:

https://thawing-falls-50722.herokuapp.com/
I have pushed this getting started tutorial app to our heroku account
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222251812,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0ni8jSQ5J1euM7odfAmXMTUMac5bUks5qF1sYgaJpZM4Ienlj
.

I’m still having fun
and at least I know that Heroku is where we want to be
since I also tried other alternatives
Josh
From: nevinsjr<EMAIL_ADDRESS>Sent: Friday, May 27, 2016 5:07 PM
To: PennStateSoftwareTest/FinalProjectPennState<EMAIL_ADDRESS>Cc: Josh Sherman<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [PennStateSoftwareTest/FinalProjectPennState] Resolve error deploying to Heroku (#25)
No worries. We'll get the build straight for Heroku.
On Fri, May 27, 2016 at 2:59 PM Josh Sherman<EMAIL_ADDRESS><EMAIL_ADDRESS>>
wrote:

https://thawing-falls-50722.herokuapp.com/
I have pushed this getting started tutorial app to our heroku account
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222251812,
or mute the thread
https://github.com/notifications/unsubscribe/AFI0ni8jSQ5J1euM7odfAmXMTUMac5bUks5qF1sYgaJpZM4Ienlj
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/PennStateSoftwareTest/FinalProjectPennState/issues/25#issuecomment-222253227 , or mute the thread https://github.com/notifications/unsubscribe/AMuN2HtMx-c1QhBerZoGq0wMiniRsctgks5qF1zlgaJpZM4Ienlj .  https://github.com/notifications/beacon/AMuN2M_I0t8dTW-GoB3F45Cp5saQIcRnks5qF1zlgaJpZM4Ienlj.gif

John and I worked on this issue this morning, and John fixed it after finding where the stinking log files were being displayed!!


Too slow at reopening

VSCode Version: Code 1.19.0 (816be6780ca8bd0ab80314e11478c48c70d09383, 2017-12-14T09:56:48.842Z)
OS Version: Linux x64 4.10.0-42-generic
Extensions:

Extension
Author (truncated)
Version

aessoft-class-autocomplete
AES
0.1.0

beautify
Hoo
1.1.1

html-css-class-completion
Zig
1.14.0

path-intellisense
chr
1.4.2

vscode-eslint
dba
1.4.3

auto-close-tag
for
0.5.5

auto-rename-tag
for
0.0.15

auto-comment-blocks
kev
1.0.1

color-highlight
nau
2.3.0

vetur
oct
0.11.5

sass-indented
rob
1.4.5

vscode-csstree
sme
0.5.0

css-auto-prefix
spo
0.1.4

(3 theme extensions excluded)

Steps to Reproduce:
The only problem is when reopening Visual Studio Code after a while minimized. Too slow and often it crashes. Maybe because I have a core i5 dural-core and 4GB of RAM in my Dell notebook. But it is really dramatic sometimes.

Reproduces without extensions: Yes/No

I don't think, that there's a big performance issue which should be solved. On my laptop on work I also have only 2 Cores, 4GB and that's also an i5. (Dell Latitude E5450 - i5-5300U CPU) There works VS Code like a charm.

@hughet Can you repro this when running code --disable-extensions?

I use another monitor besides the notebook screen. VSCode stays on the notebook's screen. When I stay on the monitor for a long time and then come back to VSCode on the notebook, it takes a long time to get back. I use just a few extensions. I use Ubuntu gnome, maybe that's it too. My notebook is a Dell 5548

@hughet next time you want to restore can you first run "code --status" and attach the output?


SetConsoleMode throws an error when locust is run from Jenkins Powershell

Describe the bug

Error message is printed out to console right after the test is started in Jenkins and job fails on exit code 2 even actual test passes. We have run locust performance tests over a year on Jenkins without similar problem. Tests started to fail recently after we updated Python and Locustio versions to latest. Locust test run without a problem if it is started on Windows desktop Powershell (or cmd).
Expected behavior

Locust tests should run on CI as they run on local machine.
Actual behavior

Error "pywintypes.error: (6, 'SetConsoleMode', 'The handle is invalid.')" is printed out to console right after the test is started in Jenkins and job fails on exit code 2 even actual test passes.
Steps to reproduce

from locust import User, task, between

class MyUser(User):
    @task
    def my_task(self):
        print("executing my_task")

    wait_time = between(0.5, 10)

Start command
locust -f .\locust_test.py --headless --run-time 3
Console from Jenkins:
[Locust_test] $ powershell.exe -NonInteractive -ExecutionPolicy Bypass -File C:\Users\locust\AppData\Local\Temp\jenkins11138277147510956709.ps1
[2020-12-10 19:13:09,846] robot-vm/INFO/locust.main: Run time limit set to 3 seconds
[2020-12-10 19:13:09,847] robot-vm/INFO/locust.main: Starting Locust 1.4.1
[2020-12-10 19:13:09,847] robot-vm/INFO/locust.runners: Spawning 1 users at the rate 1 users/s (0 users already running)...
[2020-12-10 19:13:09,847] robot-vm/INFO/locust.runners: All users spawned: MyUser: 1 (1 total running)
Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 854, in gevent._gevent_cgreenlet.Greenlet.run
  File "c:\python39\lib\site-packages\locust\input_events.py", line 89, in input_listener_func
    poller = get_poller()
  File "c:\python39\lib\site-packages\locust\input_events.py", line 81, in get_poller
    return WindowsKeyPoller()
  File "c:\python39\lib\site-packages\locust\input_events.py", line 47, in __init__
    self.read_handle.SetConsoleMode(ENABLE_LINE_INPUT | ENABLE_ECHO_INPUT | ENABLE_PROCESSED_INPUT)
pywintypes.error: (6, 'SetConsoleMode', 'The handle is invalid.')
2020-12-10T17:13:09Z <Greenlet at 0x19066ffdd00: input_listener_func> failed with error

 Name                                                          # reqs      # fails  |     Avg     Min     Max  Median  |   req/s failures/s
--------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
 Aggregated                                                         0     0(0.00%)  |       0       0       0       0  |    0.00    0.00

[2020-12-10 19:13:09,855] robot-vm/CRITICAL/locust.main: Unhandled exception in greenlet: <Greenlet at 0x19066ffdd00: input_listener_func>
Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 854, in gevent._gevent_cgreenlet.Greenlet.run
  File "c:\python39\lib\site-packages\locust\input_events.py", line 89, in input_listener_func
    poller = get_poller()
  File "c:\python39\lib\site-packages\locust\input_events.py", line 81, in get_poller
    return WindowsKeyPoller()
  File "c:\python39\lib\site-packages\locust\input_events.py", line 47, in __init__
    self.read_handle.SetConsoleMode(ENABLE_LINE_INPUT | ENABLE_ECHO_INPUT | ENABLE_PROCESSED_INPUT)
pywintypes.error: (6, 'SetConsoleMode', 'The handle is invalid.')
 Name                                                          # reqs      # fails  |     Avg     Min     Max  Median  |   req/s failures/s
--------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
 Aggregated                                                         0     0(0.00%)  |       0       0       0       0  |    0.00    0.00

[2020-12-10 19:13:12,486] robot-vm/INFO/locust.main: Time limit reached. Stopping Locust.
[2020-12-10 19:13:12,486] robot-vm/INFO/locust.runners: Stopping 1 users
[2020-12-10 19:13:12,487] robot-vm/INFO/locust.runners: 1 Users have been stopped, 0 still running
[2020-12-10 19:13:12,487] robot-vm/INFO/locust.main: Running teardowns...
[2020-12-10 19:13:12,487] robot-vm/INFO/locust.main: Shutting down (exit code 2), bye.
[2020-12-10 19:13:12,487] robot-vm/INFO/locust.main: Cleaning up runner...
 Name                                                          # reqs      # fails  |     Avg     Min     Max  Median  |   req/s failures/s
--------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
 Aggregated                                                         0     0(0.00%)  |       0       0       0       0  |    0.00    0.00

Response time percentiles (approximated)
 Type     Name                                                              50%    66%    75%    80%    90%    95%    98%    99%  99.9% 99.99%   100% # reqs
--------|------------------------------------------------------------|---------|------|------|------|------|------|------|------|------|------|------|------|
--------|------------------------------------------------------------|---------|------|------|------|------|------|------|------|------|------|------|------|

executing my_task
Build step 'PowerShell' marked build as failure
Archiving artifacts
Finished: FAILURE

REST API
Jenkins 2.249.3

Console from local PC's Powershell
PS C:\workspace\tmp> locust -f .\locust_test.py --headless --run-time 3
[2020-12-10 18:55:07,816] WL313558/INFO/locust.main: Run time limit set to 3 seconds
[2020-12-10 18:55:07,816] WL313558/INFO/locust.main: Starting Locust 1.4.1
[2020-12-10 18:55:07,816] WL313558/INFO/locust.runners: Spawning 1 users at the rate 1 users/s (0 users already running)...
[2020-12-10 18:55:07,816] WL313558/INFO/locust.runners: All users spawned: MyUser: 1 (1 total running)
 Name                                                          # reqs      # fails  |     Avg     Min     Max  Median  |   req/s failures/s
--------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
 Aggregated                                                         0     0(0.00%)  |       0       0       0       0  |    0.00    0.00

executing my_task
 Name                                                          # reqs      # fails  |     Avg     Min     Max  Median  |   req/s failures/s
--------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
 Aggregated                                                         0     0(0.00%)  |       0       0       0       0  |    0.00    0.00

executing my_task
[2020-12-10 18:55:10,512] WL313558/INFO/locust.main: Time limit reached. Stopping Locust.
[2020-12-10 18:55:10,513] WL313558/INFO/locust.runners: Stopping 1 users
[2020-12-10 18:55:10,513] WL313558/INFO/locust.runners: 1 Users have been stopped, 0 still running
[2020-12-10 18:55:10,513] WL313558/INFO/locust.main: Running teardowns...
[2020-12-10 18:55:10,513] WL313558/INFO/locust.main: Shutting down (exit code 0), bye.
[2020-12-10 18:55:10,513] WL313558/INFO/locust.main: Cleaning up runner...
 Name                                                          # reqs      # fails  |     Avg     Min     Max  Median  |   req/s failures/s
--------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------
 Aggregated                                                         0     0(0.00%)  |       0       0       0       0  |    0.00    0.00

Response time percentiles (approximated)
 Type     Name                                                              50%    66%    75%    80%    90%    95%    98%    99%  99.9% 99.99%   100% # reqs
--------|------------------------------------------------------------|---------|------|------|------|------|------|------|------|------|------|------|------|
--------|------------------------------------------------------------|---------|------|------|------|------|------|------|------|------|------|------|------|

Environment

OS: Windows 10
Python version: 3.9.1
Locust version: 1.4.1

I think this is related to keyboard input handling. Can you have a look @DennisKrone ? Probably we should just catch and ignore this error. Might want to output a log message about keyboard input being disabled when it happens, but I doubt it is really necessary.
For now, only workaround is going back to a pre 1.4 version.

The same to you,uers can not work when it happened.
python:3.7 locust:1.4.1
[2020-12-11 15:53:00,895] lep/INFO/locust.main: Starting web interface at http://<IP_ADDRESS>:8089 (accepting connections from all network interfaces)
[2020-12-11 15:53:00,901] lep/INFO/locust.main: Starting Locust 1.4.1
Traceback (most recent call last):
File "src\gevent\greenlet.py", line 854, in gevent._gevent_cgreenlet.Greenlet.run
File "C:\Users\lep\AppData\Roaming\Python\Python37\site-packages\locust\input_events.py", line 89, in input_listener_func
poller = get_poller()
File "C:\Users\lep\AppData\Roaming\Python\Python37\site-packages\locust\input_events.py", line 81, in get_poller
return WindowsKeyPoller()
File "C:\Users\lep\AppData\Roaming\Python\Python37\site-packages\locust\input_events.py", line 47, in init
self.read_handle.SetConsoleMode(ENABLE_LINE_INPUT | ENABLE_ECHO_INPUT | ENABLE_PROCESSED_INPUT)
pywintypes.error: (6, 'SetConsoleMode', '句柄无效。')
2020-12-11T07:53:00Z <Greenlet at 0x24797943908: input_listener_func> failed with error
[2020-12-11 15:53:00,912] lep/CRITICAL/locust.main: Unhandled exception in greenlet: <Greenlet at 0x24797943908: input_listener_func>
Traceback (most recent call last):
File "src\gevent\greenlet.py", line 854, in gevent._gevent_cgreenlet.Greenlet.run
File "C:\Users\lep\AppData\Roaming\Python\Python37\site-packages\locust\input_events.py", line 89, in input_listener_func
poller = get_poller()
File "C:\Users\lep\AppData\Roaming\Python\Python37\site-packages\locust\input_events.py", line 81, in get_poller
return WindowsKeyPoller()
File "C:\Users\lep\AppData\Roaming\Python\Python37\site-packages\locust\input_events.py", line 47, in init
self.read_handle.SetConsoleMode(ENABLE_LINE_INPUT | ENABLE_ECHO_INPUT | ENABLE_PROCESSED_INPUT)
pywintypes.error: (6, 'SetConsoleMode', '句柄无效。')

@cyberw & @DennisKrone:
Maybe it would make sense to add a command line flag that turns on the keyboard controls? It would avoid fatal errors when running in unknown environments. Also, it would avoid causing problems for people accidentally pressing the keybinding unaware of their existence.

@cyberw & @DennisKrone:
Maybe it would make sense to add a command line flag that turns on the keyboard controls? It would avoid fatal errors when running in unknown environments. Also, it would avoid causing problems for people accidentally pressing the keybinding unaware of their existence.

We considered adding that when implementing it, but I think it is better to just fail and (maybe) log when it has failed to initialize. There should never be any fatal errors, so there should be no need to work around that (once we fix this issue).
We could of course make it opt-in, but the list of parameters is already getting very long, and I think keeping it simple is just as important :)

We could of course make it opt-in, but the list of parameters is already getting very long, and I think keeping it simple is just as important :)

Ok :+1:
One thing I've thought about is to implement a fully fledged terminal GUI using Urwid (https://github.com/urwid/urwid), similar to somthing like htop. However, that would require quite a large development effort from someone.

Can you try with latest master @jasuomi  or @1183746881 ?

I realize it's 2 years later, but now I am seeing this error when I did not used to.
I'm using the latest version of locust (2.8.2), running on a Gitlab runner.
Python version is 3.10.0.
How do I even start to troubleshoot this?
Here is my stack-trace:
`
[2022-02-15 20:50:56,951] BuildAgent5/INFO/locust.main: Run time limit set to 5 seconds
[2022-02-15 20:50:56,953] BuildAgent5/INFO/locust.main: Starting Locust 1.5.3     <------ I got it with 2.8.2 as well.  -------
[2022-02-15 20:50:56,954] BuildAgent5/INFO/locust.runners: Spawning 1 users at the rate 1 users/s (0 users already running)...
[2022-02-15 20:50:56,955] BuildAgent5/INFO/locust.runners: All users spawned: StreamTransmitter: 1 (1 total running)
Traceback (most recent call last):
File "src\gevent\greenlet.py", line 906, in gevent._gevent_cgreenlet.Greenlet.run
File "C:\GitLab-Runner\builds\9ceD5xZA\0\qa\engine-automation\engine-load-tests\venv\lib\site-packages\locust\input_events.py", line 92, in input_listener_func
poller = get_poller()
File "C:\GitLab-Runner\builds\9ceD5xZA\0\qa\engine-automation\engine-load-tests\venv\lib\site-packages\locust\input_events.py", line 84, in get_poller
return WindowsKeyPoller()
File "C:\GitLab-Runner\builds\9ceD5xZA\0\qa\engine-automation\engine-load-tests\venv\lib\site-packages\locust\input_events.py", line 48, in init
self.read_handle.SetConsoleMode(ENABLE_LINE_INPUT | ENABLE_ECHO_INPUT | ENABLE_PROCESSED_INPUT)
pywintypes.error: (6, 'SetConsoleMode', 'The handle is invalid.')
2022-02-15T20:50:56Z <Greenlet at 0x18b39eecca0: input_listener_func> failed with error
Name                                                          # reqs      # fails  |     Avg     Min     Max  Median  |   req/s failures/s

Aggregated                                                         0     0(0.00%)  |       0       0       0       0  |    0.00    0.00
[2022-02-15 20:50:56,980] BuildAgent5/CRITICAL/locust.main: Unhandled exception in greenlet: <Greenlet at 0x18b39eecca0: input_listener_func>
Traceback (most recent call last):
File "src\gevent\greenlet.py", line 906, in gevent._gevent_cgreenlet.Greenlet.run
File "C:\GitLab-Runner\builds\9ceD5xZA\0\qa\engine-automation\engine-load-tests\venv\lib\site-packages\locust\input_events.py", line 92, in input_listener_func
poller = get_poller()
File "C:\GitLab-Runner\builds\9ceD5xZA\0\qa\engine-automation\engine-load-tests\venv\lib\site-packages\locust\input_events.py", line 84, in get_poller
return WindowsKeyPoller()
File "C:\GitLab-Runner\builds\9ceD5xZA\0\qa\engine-automation\engine-load-tests\venv\lib\site-packages\locust\input_events.py", line 48, in init
self.read_handle.SetConsoleMode(ENABLE_LINE_INPUT | ENABLE_ECHO_INPUT | ENABLE_PROCESSED_INPUT)
pywintypes.error: (6, 'SetConsoleMode', 'The handle is invalid.')
`
Thanks in advance.

@DennisKrone can you have a look?


Feat/use poetry

sorry

Thank you for sharing your code. We wrongly created PR to your original repository. This happened because my explanation was not clear enough. Sorry again.


Uploads: Add 'All,Uploads,Reposts' filter

Issue

Closes item 2 of #4563: Publish page + reposts
Requires lbry-redux::392

Approach

Updated fetchClaimListMine to include another optional parameter for us to pass the filter type.

Note

[x] I didn't bump the redux ID given there's potential conflict with other redux PRs.

Update

Changed to button-toggle style.
Removed redundant double-spinner.


How can I interact with the image picker and file picker?

Scenario :
I have one scenario of updating profile picture. To automate that I have 2 requirements -

Assigning camera Permission
Uploading profile picture from drive or gallery,, or mocking file pickers.

For requirement 1, I can see in document and we have example test also. can you please let me know for requirement 2, what all steps I have to follow, or code snippet for refrence.

Hi @akagupta9!
I suggest you that when the file picker or gallery app is opened, you should dump the native view hierarchy and then use $.native.tap() to navigate your way through the file pickers.
It'd be helpful if you attached some videos and screenshots of how your app and file picker/gallery look like :)

Hello,
I was playing around with patrol for couple last days. I was not able to successful use tap method to close permissions popups (Location always allow, notifications and motion permissions). The server crashed in my case. Our main app view is map, so it found plenty of map related objects (like POI and stuff) and probably just couldn't handle it.
So to workaround it I just added more commands to the patrol server and dart part of the lib, to find explicitly buttons by text. It worked on iOS, didn't have time to test on Android side but should work the same way. Unfortunately communication was re-written to grpc so I won't made any PR soon.
It would be lovely if someone could write more generic method to tap on alerts. Currently, it's mapping between command and text on the alert. Small change to the code that can get any text along with the command would resolve the problem and allow tap on any alerts, without need to add explicitly per type command (of course, in case, where tap method is not working).
Something like this (+ dart part,  grpc and android implementation) should work
func handlePermission(code: String, text: String) {
    runAction("handling permission with code \(code)") {
      let systemAlerts = self.springboard.alerts
        switch code {
        case "WHILE_USING":
            let okButton = systemAlerts.buttons["OK"]
            if okButton.exists {
                okButton.tap()
            }

            let allowWhileUsingButton = systemAlerts.buttons["Allow While Using App"]
            if allowWhileUsingButton.exists {
                allowWhileUsingButton.tap()
            }
        case "ONLY_THIS_TIME":
            let allowOnceButton = systemAlerts.buttons["Allow Once"]
            if allowOnceButton.exists {
                allowOnceButton.tap()
            }
        case "DENIED":
            let denyButton = systemAlerts.buttons["Don't Allow"]
            if denyButton.exists {
                denyButton.tap()
            }
        case "OK":
            let okButton = systemAlerts.buttons["OK"]
            if okButton.exists {
                okButton.tap()
            }
        case "ALWAYS_ALLOW":
            let alwaysAllowButton = systemAlerts.buttons["Change to Always Allow"]
            if alwaysAllowButton.exists {
                alwaysAllowButton.tap()
            }
        case "ALLOW":
            let allowButton = systemAlerts.buttons["Allow"]
            if allowButton.exists {
                allowButton.tap()
            }
        case "CUSTOM":
            let customButton = systemAlerts.buttons[text]
            if customButton.exists {
                customButton.tap()
            }
      default:
        Logger.shared.e("Invalid code: \(code)")
      }
    }
  }

Thanks for the feedback, I will try passing the launcher id for tap event. Hope it works 🤞

@pawlowskim How'd it go? :)

@bartekpacia AFAIR it didn't worked. But meantime, communication was rewritten to grpc and more native buttons texts were added to existing click events, and that worked.


Can't install normally

T=$(mktemp) && curl -sL git.io/abba -o ${T} && sh ${T}
T=$(mktemp) && curl -sL github.io/abba -o ${T} && sh ${T}
The installation cannot be done successfully using this command. Is this library still being maintained?
thanks

Hi,
What is the result of a single curl -sL git.io/abba ? This should print the install script to stdout like this:
$ curl -sL git.io/abba

# GitHub production URL
BASE_URL="https://jmlemetayer.github.io/abba"

# Available themes
THEMES="cerulean:cosmo:cyborg:darkly:default:flatly:journal:litera:lumen:lux:materia:minty:morph:pulse:quartz:sandstone:simplex:sketchy:slate:solar:spacelab:superhero:united:vapor:yeti:zephyr"

# Print all available themes
print_themes()
{
        echo ${THEMES} | awk -F: '{
                for (i = 1; i <= NF; i++) {
                        printf("%2s) %s\n", i, $i);
                }
        }'
}

...

I have just try and it is working for me. You may have network issue.
You can try with the full github url (not the git.io shortened url):
T=$(mktemp) && curl -sL https://jmlemetayer.github.io/abba/install -o ${T} && sh ${T}

You can also try the wget command to get more informations on what is failling.

Thank you very much!
This seems to be OK~
Maybe our network is restricted


Stop pulling in coppersmith dependencies in the coppersmith plugin

Removes the coppersmith dependency management from the coppersmith plugin. This will require users to define the coppersmith dependencies manually, but will make it easier to avoid transitive dependency clashes.
This PR will also raise a clear error if users attempt to publish metadata without depending on coppersmith.

:+1:


Visualization of attention weights

Hi
Can you please explain what is happening in your visualizing file? Where are your attention weights being loaded?

https://github.com/kaushalshetty/Structured-Self-Attention/blob/14c294a096dd1c85ef7315298e81cd9b41e55cb2/classification.py#L104


Getting a timeout error when uploading boot.py

Thanks for the app, it's great, but I'm getting this error and I can't upload or save boot.py on my device :

Uploading other files works.

Hello @nio101 and thank you for using this software :)
It's strange that only this file doesn't want to upload.
I see that you are on a LOLIN S2 MINI board and that it has a MicroPython firmware by default.
Can you make a screenshot of the "System" page in the tool, so I can see the versions please?
Maybe the boot.py file is protected...
Also, what happens if you open it with the IDE and save it with Ctrl+S instead of using the "Upload" button?

Here is the system info :

When trying to save directly, I get the 'an error occured' message...
I can upload a boot.py using other tools (thonny for example).

Thank you for feedback, indeed the versions seem good, why only boot.py and not the others...
Maybe a problem of opening the local file and not the one on the device.
Can you try the 2 commands below in the terminal to see what it returns on your side?
import os; os.stat('/boot.py')

and
with open('/boot.py', 'rb') as f : print(f.readlines())

The result is : '(32768, 0, 0, 0, 0, 0, 3359, 734295654, 734295654, 734295654)' for the first command.
The second command print successfully each line of boot.py.
I have the same issue with the ubuntu version.

Ok thanks, I don't see any particular problem, especially if it does exactly the same thing under Ubuntu :'(
I confess I don't understand why only this file is a problem...
Can you help me with 3 other questions please:

How big is the boot.py you are trying to send?
If you rename your local boot.py to another name (toto.py for example) and send it, is there still an error?
If you send another test file named boot.py instead, does it work?

Not easy to diagnose, I'm curious to understand!

Did you find anything?

Yes, it seems to be size-related.
Original file was 3.2kB.
I managed to upload a tiny boot.py file, and I had the same error trying to send another big file (not using the boot.py filename).

@nio101, you may not have enough space in the flash memory to write a large file.
Have you had time to see the progress bar?
No one seems to have this problem and multi-meg files can get through (on SD card as well) depending on the space available.


SM-G985F downloads BTS edition

Describe the bug
When downloading firmware for the SM-G985F (Galaxy S20+ 4G) with GTO region, it downloads the firmware for the BTS edition despite the phone not being the BTS edition.
To Reproduce
Steps to reproduce the behavior:

Choose SM-G985F as the model
Choose GTO as the region
Download firmware
Flash using Odin
Device has BTS special edition

Expected behavior
Other times it has downloaded the normal firmware.
Screenshots

Desktop (please complete the following information):

OS: Windows 11 (10.0.22631.4317)
Bifrost Version: 1.19.4
Firmware reported by Bifrost: G985FXXSLHXG1/G985FOXBLHXH2/G985FXXSLHXG1/G985FXXSLHXG1

Smartphone (please complete the following information):

Device: Galaxy S20+ 4G (SM-G985F)
OS: Android 13
Build number: TP1A.220624.014.G985FXXSLHXG1

This isn't something Bifrost can fix. Samsung chooses what firmware is served for a given model and CSC.


SEN0359 interface with esp32

I am working on SEN0359 with esp32 Devkit. I used the fingerprintResitration example but there is an error that is :
In file included from c:\Users\Adevair Technologies\Documents\Arduino\libraries\DFRobot_ID809_I2C/DFRobot_ID809_I2C.h:22,                  from c:\Users\Adevair Technologies\Documents\Arduino\libraries\DFRobot_ID809_I2C\DFRobot_ID809_I2C.cpp:12: C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h: In member function 'virtual void DFRobot_ID809_I2C::sendPacket(pCmdPacketHeader_t)': C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)'      uint8_t requestFrom(int address, int size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)'      uint8_t requestFrom(uint8_t address, uint8_t size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)'      uint8_t requestFrom(int address, int size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)'      uint8_t requestFrom(uint8_t address, uint8_t size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)'      uint8_t requestFrom(int address, int size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)'      uint8_t requestFrom(uint8_t address, uint8_t size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)'      uint8_t requestFrom(int address, int size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)'      uint8_t requestFrom(uint8_t address, uint8_t size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h: In member function 'virtual size_t DFRobot_ID809_I2C::readN(void*, size_t)': C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)'      uint8_t requestFrom(int address, int size);              ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)'      uint8_t requestFrom(uint8_t address, uint8_t size);
I changed the wire.h library in DFRobot_ID809_I2C.h from <wire.h> to "wire.h" then it is not showing any error but output is not appearing.
Can anyone tell that what is the issue and how to solve it ?
Thank you
Nikita

I'm having the same issue. I tried downgrading to 1.0.1 and that did show me that my connection failed but didn't give extra info on why.

I am working on SEN0359 with esp32 Devkit. I used the fingerprintResitration example but there is an error that is :
In file included from c:\Users\Adevair Technologies\Documents\Arduino\libraries\DFRobot_ID809_I2C/DFRobot_ID809_I2C.h:22, from c:\Users\Adevair Technologies\Documents\Arduino\libraries\DFRobot_ID809_I2C\DFRobot_ID809_I2C.cpp:12: C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h: In member function 'virtual void DFRobot_ID809_I2C::sendPacket(pCmdPacketHeader_t)': C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)' uint8_t requestFrom(int address, int size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)' uint8_t requestFrom(uint8_t address, uint8_t size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)' uint8_t requestFrom(int address, int size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)' uint8_t requestFrom(uint8_t address, uint8_t size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)' uint8_t requestFrom(int address, int size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)' uint8_t requestFrom(uint8_t address, uint8_t size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)' uint8_t requestFrom(int address, int size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)' uint8_t requestFrom(uint8_t address, uint8_t size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h: In member function 'virtual size_t DFRobot_ID809_I2C::readN(void*, size_t)': C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:127:13: note: candidate 1: 'uint8_t TwoWire::requestFrom(int, int)' uint8_t requestFrom(int address, int size); ^~~~~~~~~~~ C:\Users\Adevair Technologies\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.14\libraries\Wire\src/Wire.h:125:13: note: candidate 2: 'uint8_t TwoWire::requestFrom(uint8_t, uint8_t)' uint8_t requestFrom(uint8_t address, uint8_t size);
I changed the wire.h library in DFRobot_ID809_I2C.h from <wire.h> to "wire.h" then it is not showing any error but output is not appearing.
Can anyone tell that what is the issue and how to solve it ? Thank you Nikita

This should be the problem of inconsistent wire standards. I have fixed it before, but because of the version number, you could not download that version. Now the problem has been solved.

I'm having the same issue. I tried downgrading to 1.0.1, showing me that my connection failed but didn't give any extra info on why.
It is able to find the i2c device with this scanner:
I2C scanner. Scanning ...
Found address: 31 (0x1F)
Found 1 device(s).

Looking into the code I found that getDeviceInfo() returns nothing:
bool DFRobot_ID809_I2C::begin()
{
...
  String str = getDeviceInfo(); // <- this returns an empty string
...
}

Going a bit deeper I found:
String DFRobot_ID809::getDeviceInfo()
{
...
  result = responsePayload(buf); // <- This is 255 which is a error
...
}

uint8_t DFRobot_ID809::responsePayload(void* buf)
{
...
  if (ret != ERR_SUCCESS) {
    ret = ERR_ID809; // <- Throws this error
  } else if (dataLen != dataCount) {
...
}

It seems to me that the readN method of DFRobot_ID809_I2C is failing to read the SDA & SCL of the ESP32.
I've tested this on:

ESP32
ESP8266

The wiring:
The error of Nikita is caused by an ambiguous call of requestFrom which has been fixed in the master but isn't present in the library when downloading from ArduinoIDE. Even with this fix the fingerprint still doesn't work.

I did not find this problem when I tested it. Could you please use the latest updated version library for testing feedback? Thank you.

Hi, I tried it with the latest version on this GitHub page the one before the version change to 1.1.1 was made 7 hours ago. What ESP32 did you use to check this with?

As shown in the figure, everything in my test is normal, uno or esp32 are fine. Have you ever tried resetting uno or esp32 after burning the sample code? I don't have enough information to find the cause of the problem.

Strange, what specific ESP32 did you use and do you have an example of how to connect the fingerprint I2C to the esp32?

The examples in the library are used, with no additional changes.

And you used this https://www.dfrobot.com/product-2195.html esp32?

I am facing the same issue also. I am using an Arduino Nano ESP32 and the SEN0359. I followed the wiring of the pin layout of the board for the SDA and SCL, but I still can't get a connection, getting Communication with device failed, please check connection. The SEN0359 connected to my UNO R4 WiFi perfectly tho.

Considering the similar situation of both of you, it may also be a power supply related problem. For example, the esp32 is 3.3V, the uno is 5V; And the pin current is also different, which may be related to the current provided by the computer usb port. I wonder if you can provide extra power to the esp32.

How did you wire the fingerprint to your esp32? Do you maybe have a diagram or picture? And you used this https://www.dfrobot.com/product-2195.html esp32?

When I was in the test using this model esp32:https://www.dfrobot.com/product-1590.html.

If it is a power supply related issue and it does indeed need more power than it should've worked on my Arduino Uno as well. Using versions 1.1.1 on my Arduino Uno doesn't work however. The Arduino I used is a Arduino Uno R3 which has more power and also doesn't work.

Is there a way for us to help you with debugging this issue?

It's not the power supply, the code just doesn't work for our ESP32's. I've modified readN and it can now find information about my device:
size_t DFRobot_ID809_I2C::readN(void *pBuf, size_t size) {
    uint8_t len = size;
    if (pBuf == NULL) {
        LDBG("pBuf ERROR!! : null pointer");
    }

    uint8_t *_pBuf = (uint8_t *) pBuf;

    while (size > 32) {
        for (uint16_t i = 0; i < 32; i++) {
            _pWire->requestFrom(_deviceAddr, (uint8_t) 1);
            _pBuf[i + len - size] = _pWire->read();
        }
        size -= 32;
    }
    //Serial.println("rx->");

    for (uint16_t i = 0; i < size; i++) {
        _pWire->requestFrom(_deviceAddr, (uint8_t) 1);
        _pBuf[i + len - size] = _pWire->read();
        // Serial.print(_pBuf[i + len - size],HEX);
        //Serial.print(" ");
    }
    delay(10);
    if (_pWire->endTransmission() != 0) {
        return 0;
    }

    return len;
}

In the begin function I then printed:
bool DFRobot_ID809_I2C::begin() {
    _pWire->begin();

    String str = getDeviceInfo();
    Serial.println(str);
    Serial.println(str[str.length() - 1]);
    if (str[str.length() - 1] == '4') {
        FINGERPRINT_CAPACITY = 80;

        //Serial.println(str[str.length()-1]);
    } else if (str[str.length() - 1] == '3') {
        //Serial.println(str[str.length()-1]);
        FINGERPRINT_CAPACITY = 200;
    }
    return true;
}

and got this:
ID_SEODU2_ID812_BYD160_Inner(200fp) V1.3
3

The example still doesn't work, I suspect that because the readN function is wrong another function might also be wrong.

@dylanwe I don't think this is correct. requestFrom has complete start and stop bits, so adding beginTransmission and endTransmission before and after it is an incorrect operation. Moreover, multiple bytes should not be read one by one, as this will introduce many unnecessary start and stop bits, which is also the reason why I modified the code earlier. You can test the operation of the following two code segments to determine if the problem lies here. I have attached the I2C communication waveform scanned by the logic analyzer respectively.

size_t DFRobot_ID809_I2C::readN(void* pBuf, size_t size)
{
  uint8_t count = 0;
  if (pBuf == NULL) {
    LDBG("pBuf ERROR!! : null pointer");
  }
  uint8_t* _pBuf = (uint8_t*)pBuf;

  while (size > count) {
    _pWire->requestFrom(_deviceAddr, (uint8_t)1);
    while (_pWire->available()) {
      _pBuf[count] = _pWire->read();   // Use read() to receive and put into buf
      count++;
    }
  }

  return count;
}

size_t DFRobot_ID809_I2C::readN(void* pBuf, size_t size)
{
  uint8_t count = 0;
  if (pBuf == NULL) {
    LDBG("pBuf ERROR!! : null pointer");
  }
  uint8_t* _pBuf = (uint8_t*)pBuf;

  while (size > count) {
    _pWire->requestFrom(_deviceAddr, (uint8_t)(((size - count) > 32) ? 32 : (size - count)));
    delay(1);
    while (_pWire->available()) {
      _pBuf[count] = _pWire->read();   // Use read() to receive and put into buf
      count++;
    }
  }

  return count;
}

The begin and ending of a transmission is indeed not needed. The First sample you gave where you do requestfrom with 1 instead of 2 does work for me. In the second sample where you get 32 it stops working and gives me:
Communication with device failed, please check connection

So, it seems that there might be compatibility issues with the Wire library in the SDK, and there is nothing wrong with the library code itself. You can thoroughly test your SDK to see if it cannot read 32 bytes at a time (this standard is also set according to the Uno; the Uno default maximum communication size is 32 bytes). I am using the official Espressif SDK, and it runs very well.

Thank you for the help, I'll just copy the library and change it to pull 1 byte for now. If I have more time I'll look more into why my ESP32 can only get 1 byte.


[FLINK-8942][runtime] Pass heartbeat target ResourceID

What is the purpose of the change
With this PR the heartbeat target ResourceID is passed to the HeartbeatListener when retrieving the payload to send. This allows the listener to create target-dependent payloads.
The primary use-case is FLINK-8881, where accumulators are sent via heartbeats to the JobManager. Here we only want to send accumulators for the relevant job, and not for all jobs.
Brief change log

add a ResourceID parameter to HeartbeatListener#retrievePayload
modify return type of HeartbeatManagerImpl#getHeartbeatTargets to also contain the target ResourceID

Verifying this change
This change added tests:
HeartbeatManagerTest:

testHeartbeatManagerTargetPayload
testHeartbeatManagerSenderTargetPayload

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@tillrohrmann I've addressed your comments.

Thanks for addressing them. Merging this PR once Travis gave green light.


What are the exact versions for protoc-gen-go?

Hi,
The new versions of protoc-gen-go don't support grpc plugins and have some changes which makes your repo not work. I have an issue regarding this problem here too.
Have you done this recently?
Thanks,
Hamed

According to my local history, these are the versions I've used:

protoc: 3.12.3

protoc-gen-go:

google.golang.org/protobuf<EMAIL_ADDRESS>or

github.com/golang/protobuf<EMAIL_ADDRESS>

Thanks for the response.
For protoc-gen-go if I install<EMAIL_ADDRESS>it doesn't support the grpc plugin which I should install protoc-gen-go-grpc as well which then I encounter this error:
--go_out: protoc-gen-go: plugins are not supported; use 'protoc --go-grpc_out=...' to generate gRPC

I then switched to<EMAIL_ADDRESS>but when I want to install the protoc-gen-go package from this module, for some weird reason it downloads<EMAIL_ADDRESS>which again raises the same error!

Now it builds successfully and I'm trying to call my model from the tf serving grpc endpoint.
If this is successful, I would let you know and close the issue.


Parsing boolean value always returns false

Looks like a bug in config.yml parser.

Thanks! This is in 993615d49b1a206d035b01453ba2ced313d09110