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

Some scanner related actions are triggered at exit of the whole program, not fitting the Gallia 2.0 Approach of calling sub scanners #641

Open
fkglr opened this issue Dec 6, 2024 · 1 comment · May be fixed by #651
Milestone

Comments

@fkglr
Copy link
Contributor

fkglr commented Dec 6, 2024

Some scanner related actions are triggered at exit of the whole program, not fitting the Gallia 2.0 Approach of calling sub scanners.
An example would be the closing of log handlers which currently results in having log files with multiple scanner logs if they are called from inside a script.

@rumpelsepp
Copy link
Member

This is clearly a bug that needs to be addressed before gallia 2.0. Logging must be scoped to scanner classes somethow. Needs additional design work.

@rumpelsepp rumpelsepp added this to the gallia 2.0 milestone Dec 6, 2024
@rumpelsepp rumpelsepp linked a pull request Dec 17, 2024 that will close this issue
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 a pull request may close this issue.

2 participants