I am tired of vscode crash, it is about 5th time, I complete and on last exercise it crash. On every bash restart vscode, that doesn’t help out.
I just tried to investigate. So on restarting .sh it is running Ec2 instance and it is not accessible
[cloudshell-user@ip-10-132-49-63 ~]$ nmap 52.202.4.10
Starting Nmap 7.93 ( https://nmap.org ) at 2024-11-18 23:04 UTC
Nmap scan report for ec2-52-202-4-10.compute-1.amazonaws.com (52.202.4.10)
Host is up (0.00041s latency).
Not shown: 995 filtered tcp ports (no-response)
PORT STATE SERVICE
22/tcp open ssh
443/tcp closed https
8080/tcp closed http-proxy
8443/tcp closed https-alt
8888/tcp closed sun-answerbook
Hello @Imran_Sarwar
Please, specify in which lab and on what step of the lab your vscode terminal crashes. Terminal crash happens to me too, but you don’t need to restart vscode after a terminal crash. You can just start a new terminal.
My vscode crash on
Graded Programming Assignment 4: Capstone Project Part 1 - ETL and Data Modeling
and it crash after around 1 and half hour. I follow the same steps and even make new terminal and follow the same steps as mentioned on documentation but vscode is not accessible.
@Imran_Sarwar sorry for the inconvenience. Does it crash upon running a specific command? maybe dbt run -s serving_layer?
Unfortunately, I was not able to reproduce the issue. It would be helpful if you can provide screenshots of the errors you get.
I simply, completed the test within an hour because vscode start failing after an hour. So I moved to next step. But that happened to me from last 4 days and I tried nearly 5 to 6 times and after restarting vscode never came back. Not sure, why it is not reproducing 
but thanks for looking into it and in case other face it, they may provide further input.
1 Like