Learn Git By Building An Sql Reference Object- large number of unexpected files

Hi,

I have been working on the Relational Database (Beta) Certification. I am currently on the Learn Git module, and there are a large number of files under the project folder that are entirely unrelated to this course. They all seem to be related to cryptocurrency, cryptocurrency miners, and one is even labeled “bit-craker”.

I don’t think that these should be in this project folder, and I don’t know if I’m able to delete them or what, but specifically the “bit-craker” concerns me as it seems like it may be something illegal.

Also, when I check git status, I get this:

codeally@e35d4fdc30d1:~/project$ git status
On branch master
Changes not staged for commit:
(use “git add …” to update what will be committed)
(use “git restore …” to discard changes in working directory)
modified: .freeCodeCamp/test/.cwd
modified: .freeCodeCamp/test/.next_command

Untracked files:
(use “git add …” to include in what will be committed)
Bit-craker/
Brute-ETH-Threading-24.py
Brute-ETH-Threading.py
LostCoins/
README-en.html
amdmemtweak
config.ini
config_cfx_xmr.ini
config_cfx_zil_verus.ini
config_cfx_zil_xmr.ini
config_conflux.ini
config_ergo.ini
config_ergo_zil.ini
config_ergo_zil_verus.ini
config_ergo_zil_xmr.ini
config_etc.ini
config_etc_xmr.ini
config_etc_zil_merged.ini
config_etc_zil_merged_xmr.ini
config_etc_zil_split.ini
config_etc_zil_verus.ini
config_etc_zil_xmr.ini
config_ethw.ini
config_evr.ini
config_evr_zil.ini
config_evr_zil_verus.ini
config_evr_zil_xmr.ini
config_firo.ini
config_firo_zil.ini
config_firo_zil_xmr.ini
config_rvn.ini
config_rvn_zil.ini
config_rvn_zil_verus.ini
config_rvn_zil_xmr.ini
config_verus.ini
config_vtc.ini
config_xmr.ini
eth-wallet-0.3.1.tar.gz
helper_scripts/
learn-git-by-building-an-sql-reference-object/
libnvrtc-builtins.so
libnvrtc.so.10.0
licenses/
logs/
nanominer
nanominer-linux-3.6.8.tar.gz
nanominer-linux-3.6.8.tar.gz.1
nanominer-linux-3.6.8/
nanominer-linux-3.7.6.tar.gz
nanominer_web-monitor.url
sql_reference/
web/

no changes added to commit (use “git add” and/or “git commit -a”).

I don’t really want to keep working on this course until this is resolved.

please post a link to the page you used to sign into this course

When I sign in to this course, all I see in project is

codeally@e6b963f77c61:~/project$ ls -la
total 32
drwxrwsr-x 6 root     strove 4096 Jan  6 21:34 .
drwxrwxr-x 1 codeally strove 4096 Jan  6 21:34 ..
drwxr-sr-x 4 codeally strove 4096 Jan  6 21:34 .freeCodeCamp
drwxr-sr-x 8 codeally strove 4096 Jan  6 21:34 .git
-rw-r--r-- 1 codeally strove   23 Jan  6 21:34 .gitignore
drwxr-sr-x 3 codeally strove 4096 Jan  6 21:34 learn-git-by-building-an-sql-reference-object
drwxr-sr-x 2 codeally strove 4096 Jan  6 21:34 .vscode
codeally@e6b963f77c61:~/project$ 

Nothing else.

Can you sign in to CodeAlly.io and try to delete the container entirely? I have no clue how your container got these files into it, but if you delete the container, and sign in again via fCC’s course site, I assume you will have the normal list of files that I see.

(you have to sign-up to CodeAlly.io and once you have gotten in, on the left there is a menu you can use to click on option Cloud IDE then in the Playground area you can see a list of containers. Delete this one from there.

1 Like

I can try that-- my concern is, I don’t know how any of those files got there either. It makes me question the safety of it.

Also, when I initially opened the course, these files weren’t a part of it. I only noticed these files under my project folder after completing ~50% of the course.

Hello there,

Keep in mind, this section of the curriculum runs in a VM on a server (someone else’s machine). So, if any of those files are unsafe, the context in which they exist/run means they can only affect CodeAlly’s servers - not your local computer.

Hope this puts you a little bit at ease

That does put me at ease, thanks! I still have no idea how that happened… BUT a logged in through CodeAlly and deleted the container and it’s back to normal now.

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.