confidant | Web Based Diary Application

We're using Twilio. We have webhooks set up so that when Twilio receives a call, it forwards it to a URL on our site.

This appears to have been working fine. But now I made a change to the code, and suddenly Twilio is having problems calling the webhook. We don't receive the message, and if I look in the Twilio log, it says it got a 403 error. (I can't swear that this has never happened before. I've never noticed a message to be lost, but maybe I missed it while debugging other errors, attributed a lost message to something else.)

The truly strange part is, about 2/3 of the message that come in are received and processed fine, but about 1/3 get the 403 error. This is on a test server where we don't have any load balancing, so all requests are going to the same instance of our app. The tests I've been doing today are all from the same cell phone to the same Twilio number.

We do have authorization on the app, but the authorization is all on sub-directories, not the top level, and the sub-directory with our web hook has no authorization set up.

The first thing my our web hook now does when it gets called is send me an email with the content of the message from Twilio. (For debugging purposes.) I'm not getting that email, so I'm very confidant it's not getting called. And as I say, I can look at Twilio's log and it says that it received the text message and got a 403 error trying to forward it to my webhook.

The fact that it's only like 1/3 of the time is particularly puzzling. It's from the same number, to the same number, hitting exactly the same URL on the same site. Why would it work sometimes and not other times?

I tried to reproduce the problem on my desktop by calling the URL directly, not going through Twilio, and that does not give the same error. (It occurs to me as I type that the next logical test is to hit the page on the server without going through Twilio.)

Oh, the server is ASP.NET. The code is in VB but I doubt that matters as we're not getting as far as executing any of our code when it fails. When it doesn't get the 403, the code is working fine.

my TensorFlow model is always predicting the same class with a confidant of 100%.

First a short description of my setting: Task is to do image classification with 7 classes and reading images from the webcam. For training, validation, and testing of the model, I'm using TensorFlow with data generators.

Framework: VueJS

OS: Linux Mint 19.2

NPM version 3.5.2

Creating a web app (client and server hosted locally)

Likely cause of error: strict linting?

I'm a Visual C# .NET developer and I'm trying to get caught up with this new wave of web development and have decided to go with VUE for my first framework.

I'm pretty sure that where I went wrong was setting up the linting settings. The instructor was prompted with very different questions than I was during the 'npm install' command. Linting error keeps causing me to crash.

This is the error log:

0 info it worked if it ends with ok

1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'lint' ]

2 info using npm@3.5.2

3 info using node@v8.10.0

4 verbose run-script [ 'prelint', 'lint', 'postlint' ]

5 info lifecycle server@1.0.0~prelint: server@1.0.0

6 silly lifecycle server@1.0.0~prelint: no script for prelint, continuing

7 info lifecycle server@1.0.0~lint: server@1.0.0

8 verbose lifecycle server@1.0.0~lint: unsafe-perm in lifecycle true

9 verbose lifecycle server@1.0.0~lint: PATH: /usr/share/npm/bin/node-gyp-bin:/home/user/...

10 verbose lifecycle server@1.0.0~lint: CWD: /home/user/Documents/Projects/tab-tracker/server

11 silly lifecycle server@1.0.0~lint: Args: [ '-c', 'eslint **/*.js' ]

12 silly lifecycle server@1.0.0~lint: Returned: code: 2 signal: null

13 info lifecycle server@1.0.0~lint: Failed to exec lint script

14 verbose stack Error: server@1.0.0 lint: eslint **/*.js

14 verbose stack Exit status 2

...

The client is running just fine,

This is my 'package.json within the server: