Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor: reduce complexity by removing unused functionality #25

Merged
merged 6 commits into from
Nov 5, 2024

Conversation

felixauringer
Copy link
Collaborator

No description provided.

@felixauringer felixauringer force-pushed the refactor/linting-and-testing branch from 3f03848 to 53e56a1 Compare October 15, 2024 14:47
@felixauringer felixauringer marked this pull request as ready for review October 15, 2024 14:48
@felixauringer felixauringer force-pushed the refactor/linting-and-testing branch from 53e56a1 to 7a7d2f9 Compare October 15, 2024 16:16
@felixauringer
Copy link
Collaborator Author

I think this closes the following issues @j2ein. Please correct me if I am wrong.

@felixauringer felixauringer self-assigned this Oct 15, 2024
Base automatically changed from fix/8-first-loop to main October 30, 2024 18:52
This removes the following things:
- anything with tests because there are not tests
- unused and undocumented Makefile targets

Furthermore, the Makefile `docker` target is now able to use CGO
because this is also not disabled in the pipelines and some
dependencies cannot build without it.
@felixauringer felixauringer force-pushed the refactor/linting-and-testing branch from 7a7d2f9 to d4bbfe9 Compare October 30, 2024 18:54
@felixauringer felixauringer force-pushed the refactor/linting-and-testing branch from d4bbfe9 to 7467ebb Compare October 31, 2024 06:30
@felixauringer felixauringer merged commit bec1d5d into main Nov 5, 2024
2 checks passed
@felixauringer felixauringer deleted the refactor/linting-and-testing branch November 5, 2024 06:54
@j2ein
Copy link
Collaborator

j2ein commented Nov 7, 2024

I think this closes the following issues @j2ein. Please correct me if I am wrong.

* [Update Bee README #16](https://github.com/Cybersecurity-and-Enterprise-Security/bee/issues/16): Renamed the compose file and changed Readme. However, I do not know what you mean with the missing commands.

This issue was from @SilvanVerhoeven , and I think "the missing commands" meant the additional parameter that was needed to specify for development purpose (specifying custom backend, etc.) So this is no problem for us, as a normal usage of bees does not require those flags.

* [Omit similar sounding log messages on bee startup #18](https://github.com/Cybersecurity-and-Enterprise-Security/bee/issues/18): Changed some logging messages and added one after startup is finished.

The issue is addressed.

* [Make Bee config break by default #24](https://github.com/Cybersecurity-and-Enterprise-Security/bee/issues/24): I added an additional log message stating the most common reason for the failure. (I would still keep that issue open, see [here](https://github.com/Cybersecurity-and-Enterprise-Security/bee/issues/24#issuecomment-2414452134).

I agree with you that the bee should return more meaningful error, so I agree with your decision to have that issue open.

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