Several setup script failures: develop branch

[palisadoes]

Describe the bug

1. On running setup with the latest updates to the branch we get this error.
   
2. Setup fails when you don't previously have a .env file created (DB logging)
   
3. Setup fails on the subsequent attempt for storing logs
   
4. If you don't do DB transaction logs, you are not prompted for a storing logs. There is no error
   
5. When asked to load sample testing data we get this error
   
6. When you go through setup again and load sample data. Your answer disappears, and you get this printout.
   
   1. The prompt reappears at the bottom only after hitting enter again
      

To Reproduce

• See above

Expected behavior

1. No error because the issue has been fixed correctly, not because the error has been suppressed
2. No other functionality must be affected
3. Tests must be created for 100% code coverage for the setup process
4. All tests must pass and be valid

Actual behavior

• See above

Screenshots

Additional details

• N/A

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[bandhan-majumder]

can i work on this?

[palisadoes]

@bandhan-majumder

1. Please thoroughly check setup. It is badly broken
2. Write tests for 100% code coverage for the setup process.
3. I continue to find errors. I've updated the first issue comments

[bandhan-majumder]

hi @palisadoes . In the issue description, what does the 4th point mean? If I am not enabling log, it's not showing me storing log location which is fine. Logs are not generating, so cant be stored. Is there anything I am missing?

[palisadoes]

Start with an empty .env file and try to set it up from scratch.

I don't think my old .env had any minio configuration parameters. That may have been past of the cause.

[palisadoes]

You'll also need to add tests.

[bandhan-majumder]

Start with an empty .env file and try to set it up from scratch.

I don't think my old .env had any minio configuration parameters. That may have been past of the cause.

Sure. I will add tests if needed. Right now the changes are not too much.

[bandhan-majumder]

@palisadoes this message is everywhere. Is this causing any issue otherwise?

[palisadoes]

This was fixed some time ago. There needs to be a different approach to setup mongo on your local system versus in the cloud

[palisadoes]

This was fixed some time ago. There needs to be a different approach to setup on your local system and in the cloud.

Look at the history of the file responsible for mongo setup

[bandhan-majumder]

Start with an empty .env file and try to set it up from scratch.

I don't think my old .env had any minio configuration parameters. That may have been past of the cause.

I started with empty .env and it is working as well. I copied the .env.example file and ran npm run setup

[palisadoes]

What happened when you asked

1. to setup logging
2. not to setup logging

That's when it failed for me. I'm using node v22 as in the .node-version file

[bandhan-majumder]

What happened when you asked

1. to setup logging

2. not to setup logging

That's when it failed for me. I'm using node v22 as in the .node-version file

There was a reference error of __dirname . I added the fix in my changes.

enable logging with custom path

enable logging with default path

do not enable

[palisadoes]

Did you add tests?

[bandhan-majumder]

No. I could not find any setup.spec.ts file. Do I need to write test from scratch?

[palisadoes]

Yes. This failure keeps happening

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.