Skip to content

Frontend1#7

Open
someRandomDude-a wants to merge 23 commits into
mainfrom
frontend1
Open

Frontend1#7
someRandomDude-a wants to merge 23 commits into
mainfrom
frontend1

Conversation

@someRandomDude-a
Copy link
Copy Markdown
Owner

No description provided.

Comment thread backend/db.py
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not rename variables, verbose names are for clarity.

Do not use default argument with datetime.now
This argument is evaluated ONCE at initialisation and will not be updated before every run.

Justify the changes in length for the character arrays in token hash etc. these have been turned for their respective hashing algorithm and should not be changed unless the underlying code has been changed

User.id should be an index. We search our database mainly using user id.

Comment thread backend/Dockerfile Outdated
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this for? Not needed. Remove.

Comment thread backend/init_db.py
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't hardcode values like this. Create a script that imports and sql database file instead and load your dummy data into that. It is far more modular and easier to read.

Comment thread backend/integration.md
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why even change this? What is the reason for it? Remove changes

Comment thread frontend/Dockerfile
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this? Remove, we build from the main docker compose file in backend/Docker

Comment thread backend.zip
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is there a zip file ? Remove.

Comment thread backend_README.md
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this here? This belongs in integration.md if anywhere. Besides this is just parroted stuff from readme.md duplicate, remove

Comment thread docker-compose.yml
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

version: tag is depreciated
We already have a proper compose file embedded in the readme.md

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why a zip file? Remove

Comment thread README.md
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't change, the one on main is upto date

Comment thread backend/requirements.txt
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not even include all required dependency. To make a proper requirement file, build on python 3.14 and install all requirements with pip
Then run pip freeze

Comment thread backend/main.py
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why rename all the comments? Tell me the changes required, I will make them myself. This is unnecessary and already outdated, main branch already has most of these changes

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you changing this file? We use different hash types based on performance vectors and security requirements. Remove changes

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we are not doing calculation based on more package parameters, cost of package does not change. Hence this still should still use an lru_cache.
The new function should be implemented by creating a new graph combining the time and cost graphs with given weightage.
So it would look like:

For time, cost in zip(time_graph, cost_graph):
  New_graph.add(time_graph * 0.5 + cost_grapg * 0.5)

@someRandomDude-a someRandomDude-a marked this pull request as ready for review March 21, 2026 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants