Replies: 4 comments 1 reply
-
I created #58 for this. |
Beta Was this translation helpful? Give feedback.
-
for me, the important thing is that I'm able to follow progress of tasks that takes few days or few weeks to execute. One potential issue that I see using the cache, is that when task fails, You need also to ensure that progress is not lost if app is stopped. So you need to really document well in the documentation which caching system you use, and that this caching mechanism is well isolated from any action a client application could perform (like cleaning cache) There is therefore high chance that this kind of change impacts the way client application are working, and that it will create cascade bugs in those application. So I would appreciate that you merge the PR that you just closed, so that I can have a working version of Django-huey-monitor. I have plenty of monkey patches in my code that are waiting since September 2021 for you to merge. |
Beta Was this translation helpful? Give feedback.
-
Another idea: Do we really need the TaskProgressModel? Think we didn't. We can just store the information in the TaskModel. |
Beta Was this translation helpful? Give feedback.
-
I played a little bit with the code and think about this:
I started the work here: #76 |
Beta Was this translation helpful? Give feedback.
-
I think we should think about removing the TaskProgressModel model.
It would be more effective to use the caching backend for this, isn't it?
We can store task progress in cache and on complete update the TaskModel instance.
We can also store "last update datetime" via cache. So that ProcessInfo.update() will not write anything to Database.
Beta Was this translation helpful? Give feedback.
All reactions