Skip to content

Conversation

@joshua2705
Copy link

As part of DSBA open-source contribution project held by Prof.Dimo
We have attempted to fix issue #17

image

This architectural change makes the code more modular and manageable AND lead to a decrease in latency by 5.8%

But this is not the best solution. Ideally, it would be best to re-write the UI in vue/react to allow dynamic changes as per data

@nikohansen
Copy link
Contributor

Why do we get the above conflicts?

Copy link
Author

@joshua2705 joshua2705 Jan 13, 2026

Choose a reason for hiding this comment

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

This is the line mentioned in the issue #17 (line no 499) which gets called repeatedly by the old architecture.
We removed this line and replaced it with a function which changes the architecture.

The function to this new line is imported in line 17.

Copy link
Author

Choose a reason for hiding this comment

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

We used a venv for testing.
This can be removed if necessary

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't exactly understand the causal link between these two.

In any case, you should rebase your branch on the current main branch, resolve possible conflicts, and update the pull request.

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.

3 participants