Skip to content

Feature: task IDs (and other related stuff) #14

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

Merged
merged 29 commits into from
Jan 26, 2025
Merged

Conversation

Vectorial1024
Copy link
Owner

Every running AsyncTask shall have an ID. This can be provided by the user (assuming they do not start multiple tasks with the same ID...), or if the user does not provide one, the ID will be randomly generated instead.

This allows the user to check whether the task is running or not. When the task is no longer running, the user may then use their own code to determine whether it was a success or failure.

@Vectorial1024
Copy link
Owner Author

It is almost elementary for every worthy programmer to know about ps | grep in Unix. The hard part is, what would be its equivalent (if exists) in Windows?

@Vectorial1024
Copy link
Owner Author

@Vectorial1024
Copy link
Owner Author

Didn't expect all cases to fail here...

@Vectorial1024 Vectorial1024 linked an issue Jan 23, 2025 that may be closed by this pull request
@Vectorial1024 Vectorial1024 merged commit c89946f into master Jan 26, 2025
3 checks passed
@Vectorial1024 Vectorial1024 deleted the surveillance branch January 26, 2025 10:29
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.

Consider: global task ID
1 participant