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

RFC: flag for blocking one expectation task per space #51

Open
ArtDu opened this issue Apr 15, 2021 · 3 comments
Open

RFC: flag for blocking one expectation task per space #51

ArtDu opened this issue Apr 15, 2021 · 3 comments
Labels
feature A new functionality

Comments

@ArtDu
Copy link
Contributor

ArtDu commented Apr 15, 2021

Problem

We want to create a flag that will protect users using modules to protect them from the fool. It will be painful have too many full scans.

Needs

  • Make a flag that can be passed and it will prohibit the creation of another run task if another already exists
  • It is necessary to preserve backward compatibility
@kyukhin kyukhin added feature A new functionality teamE labels Sep 10, 2021
@Totktonada
Copy link
Member

An I understood right: you want ability to run only one task per space? The source of several task is a mistake in some reloading code (possibly in expirationd itself)?

@ArtDu
Copy link
Contributor Author

ArtDu commented Sep 10, 2021

An I understood right: you want ability to run only one task per space? The source of several task is a mistake in some reloading code (possibly in expirationd itself)?

here is rather the idea that many fullcans are not very effective, the idea of @no1seman

@no1seman
Copy link

My point of view: by default - module must allow to run only one task per space. If someone tries to run second one - warning (or error) must be generated. But if user wants to run multiple task per single space there will be a special flag user must provide....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new functionality
Projects
None yet
Development

No branches or pull requests

5 participants