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

signal for dump/result changes are very verbose #1074

Open
dadokkio opened this issue Mar 27, 2024 · 0 comments
Open

signal for dump/result changes are very verbose #1074

dadokkio opened this issue Mar 27, 2024 · 0 comments

Comments

@dadokkio
Copy link
Collaborator

dadokkio commented Mar 27, 2024

Changes to dump result generate toast messages.
This has been moved from dask async to django signal in order to avoid issue with ws.
The problem is that a ws message is raised for all changes and not just for status update.
image

A temporary field in pre_save to be check in post_save should be ok to filter just status update.

dadokkio pushed a commit that referenced this issue Mar 27, 2024
dadokkio pushed a commit that referenced this issue Mar 29, 2024
dadokkio pushed a commit that referenced this issue Mar 29, 2024
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

No branches or pull requests

1 participant