We Keep Coding

Gatsby development server stops working when repo is created on github. Sanity, Gatsby Error

I received a github repo backup from somebody elses account. The project is running gatsby, sanity cms and is hosted via netlify. When I extract the archive and saving the folder locally, I am perfectly able to get the gatsby development server runnning just by doing "yarn install" and "yarn gatsby develop".
However, when I create a new repo and import the project to my github account, the development server is not running anymore. We tried it on several machines and we always get the same error in terminal trying "yarn gatsby develop".
success open and validate gatsby-configs - 0.131s
success load plugins - 2.486s
success onPreInit - 0.038s
success initialize cache - 0.009s
success copy gatsby files - 0.091s
info [sanity] Fetching remote GraphQL schema
ERROR #gatsby-source-sanity_drafts.10003
[sanity] The token specified is not valid or has been deleted
How is that possible? I tried to fix this for days but I don't get it. The only differnce between being able to run the dev server and this error is to save the code to github... Is it maybe some sort of routing problem in the gatsby-config.js?
Would appreciate your help a lot!

It seems that you are missing the environment variables in your new projects so your Sanity configuration is not valid, hence Gatsby is not able to fetch the data from the sources.
There should be a .env.development or .env.production files in your original code placed in the root of the project.

Why am I getting a self signed certificate error when starting Nodemon in React?

I am making a React project to boost my portfolio and I'm using Massive to connect to a Heroku Postgres database. When I start up Nodemon to run my app the server starts up but it doesn't connect to my database and I get this error:
{ Error: self signed certificate
at TLSSocket.onConnectSecure (_tls_wrap.js:1058:34)
at TLSSocket.emit (events.js:198:13)
at TLSSocket._finishInit (_tls_wrap.js:636:8) code: 'DEPTH_ZERO_SELF_SIGNED_CERT' }
I've never gotten this error before on my other React applications and I'm at an absolute loss as to how to fix it. If anyone needs to see certain lines of my code I'd be happy to show it. Any help is much appreciated!
EDIT: I didn't want to make my whole app insecure but I figured since I'm just in development it would be okay to put process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0" in my server file and now it works. I'm still confused as to why I'm suddenly getting this error so if anyone else has had this happen to them I'd love to hear about it.
EDIT #2: I got the same problem even after getting a certificate on my actual site. In my other site, I haven't updated some of the dependencies and it doesn't have this error so I compared what dependencies were different and narrowed it down to Massive because that's what I'm using to connect to my database. I downgraded the version and it works now! I will continue to look into how to fix this but for now I'll have to use the 6.1.1 version.

how can I connect to a http://localhost:4200 using browser which is a aws ec2

I am learning node.js in an online course to build up a web server and app
before the teaching started, the teacher told me to set up your coding environment, and it got a direction to told me what to do step by step.
Because I using Chromebook, So I started an aws ec2 serve which is ubuntu 18.04 and using cloud9 for my ide
I installed node.js successful on the ec2
And the direction told me to type on those on the terminal
git clone https://github.com/OpenClassrooms-Student-Center/5614116-front-end-app.git frontend
You can then do the following:
cd frontend
npm install
ng serve
This will install all the dependencies needed by the front end app and will launch the development server. Now, if you navigate to http://localhost:4200 , you should see the following (assuming you've followed the steps above successfully):
the direction say if I successfully followed the step, will see something on http://localhost:4200
On the terminal, at last show me
ℹ ｢wdm｣: Compiled successfully.
But how can I connect to http://localhost:4200 which was an ec2?
I tried using IP:4200, the browser keeps on loading the page and nothing shows up on the browser
－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－
I found out that the program that teacher gave me to install set the URL to http://localhost:4200
because cloud9 says the program was running, but running at a URL call http://localhost:4200
what should I do？

Localhost refers to your local machine. But as mentionedd that your node.js running on ec2 and want to connect to it from your browser, get the IP of the ec2 and type in your browser- IP:4200
And it should work

The only problem here is you have to add port 4200 in your aws ec2 instance security group to allow inbound traffic.
STEPS:
1. Go to your EC2 instance.
2. Click security group from Description below.
3. Click Inbound then Edit.
4. Click Add Rule
5. Select Custom TCP , Port - 4200 , IP - 0.0.0.0/0
6. Then SAVE.
After that try <EC2-IP:Port> in your browser it will work fine.

Greengrass deployment stuck on "In Progress"

I'm trying to configure an AWS Greengrass group through their JavaScript SDK, and I get everything up and running up to where I have a deployment. The issue is that the deployment seems to be stuck on "in progress" and there are no cloudwatch logs to help me.
I looked at the core device, and this is what I saw in the /greengrass/ggc/var/logs/system/runtime.log file:
[2019-01-18T03:17:22.64Z][INFO]-Greengrass Root: /greengrass
[2019-01-18T03:17:22.64Z][INFO]-Greengrass Write Directory: /greengrass/ggc
[2019-01-18T03:17:22.64Z][INFO]-Group File Directory: /greengrass/ggc/deployment/group
[2019-01-18T03:17:22.64Z][INFO]-Default Lambda UID: 498 GID: 496
[2019-01-18T03:17:22.64Z][INFO]-===========================================
[2019-01-18T03:17:22.64Z][INFO]-The current core is using the AWS IoT certificates with fingerprint: 7591dcd10e96f86dd2d323d468b84b419b26280bbcfd3c0eee45c5a12c6d2dd7
[2019-01-18T03:17:22.641Z][WARN]-worker process info: /greengrass/ggc/packages/1.7.0/var/worker/processes
[2019-01-18T03:17:22.641Z][WARN]-worker process info: /greengrass/ggc/packages/1.7.0/var/worker/processes
[2019-01-18T03:17:22.641Z][INFO]-Reloading registry
[2019-01-18T03:17:22.642Z][INFO]-The current core is using the AWS IoT certificates with fingerprint: 7591dcd10e96f86dd2d323d468b84b419b26280bbcfd3c0eee45c5a12c6d2dd7
I've checked and I'm able to successfully hit the ATS endpoint using OpenSSL and the certificates that I have. I'm using Amazon's recommended certificate from the Greengrass tutorial RSA 2048 bit key: Amazon Root CA 1.
What are some diagnostic steps or clues where to go from here?

I've had this issue before. I believe it's just a bug with the internals getting mangled from a bad deployment.
The way I brute force hanging deployments are to create a new core and then add known working lamdbas in a working group to the new core, kill and restart the deamon on the core device, and then redeploy.

So for me, I had 2 things misconfigured which prevented successful deployment
The deployment was stuck "in progress" because the permissions in the policy and role that were attached needed lambda permissions to deploy. Once I did this, the deployment went from "in progress" to "failed deployment" which brought me to the second mistake.
The EC2 instance which was hosting the core software somehow didn't run the setup shell script correctly (probably didn't run it as sudo) and my cgroups were not fully setup for memory (not sure what this means but you need it setup)
Thank you Steve B for the help!

I've encountered the mention issue many times. In my case, the problem was always related about internet connectivity.
To check your system, before starting the deployment process, please subscribe # (wildcard) to listen all topics and check out messages related about deployments. If you don't see any incoming messages, It means network connectivity is the problem.
Then you can run this command ping greengrass-ats.iot.region.amazonaws.com where the greengrass core installed to investigate the issue. If everything seems Ok, you can start deployment again. But If you see lost packages, you should investigate the main issues which causes the network problem.

Truffle Drizzle error "TypeError: Cannot read property 'address' of undefined"

Expected:
After running the app, the user should see a "Loading Drizzle..." msg in the browser then soon followed by "Drizzle is ready".
Results:
The app stays stuck on "Loading Drizzle..." and there is an error in the chrome console:
Error
uncaught at root at root
at contractsSaga
at takeEvery
at addContract
at instantiateContract
TypeError: Cannot read property 'address' of undefined
I'm following this tutorial here: https://truffleframework.com/tutorials/getting-started-with-drizzle-and-react
And I'm at the current section:
Replace the render method
render() {
if (this.state.loading) return "Loading Drizzle...";
return <div className="App">Drizzle is ready</div>;
}
I've done that in my app, and expected to see the "Drizzle is ready" message, but instead got the error above.
Here is my repo: https://github.com/leongaban/truffle_drizzle_test

No contracts are deployed to your ganache network, which is why that error is occurring.
In the root of your folder, make sure you run truffle migrate after truffle compile.

I had the same problem, even after deploying the contracts correctly to my ganache network. The reason it didn't work for me was that I had MetaMask active on my Chrome Browser. I was not even logged in, but still it appears that the dapp was looking for the contract on the wrong network. When I open the site with Incognito Mode / completely disabled MetaMask, it works!
This is something the tutorial points out, but I guess it's easy to not take seriously:
Note: Make sure to use an incognito window if you already have
MetaMask installed (or disable MetaMask for now). Otherwise, the app
will try to use the network specified in MetaMask rather than the
development network under localhost:8545.

truffle migrate will deploy your contract onto your blockchain network, and then output a file build/contracts/YourContract.json which contains info about your contract. For example, it contains the ABI for your contract and the address that your contract was deployed at.
Your JavaScript probably imports that JSON file in order to have the needed information to connect to your contract. Therefore, be sure that the JS is importing the most up-to-date version of the JSON, otherwise it won't know which address to find your contract at, etc.