Closed vikiival closed 2 years ago
I found out that in when the app is about to end it does not handle that the _unfinished_tasks can spawn other tasks
_unfinished_tasks
when i run the app it will finish those 5 tasks however the 3 🔥 tasks should spawn 3 more ❄️
12:39:46 INFO: [ASYNC OBJECT]: ❄️ 200 bafkreiavfaprfpofh754yuiimg5yvetrrlxuy3o7rf4wrzqw75nmi3wtki 12:39:46 INFO: [ASYNC 🔥]: 200 bafkreigujg6s43c52nyx7apkq7hfyk3v4smmmx4ekucltt6pnxaefxtpsq.png 12:39:46 INFO: [ASYNC 🔥]: 200 bafkreicje2sievgnrrk3v6mj5t6famyjbg4gzyrhomdm2dn55kdqtajtb4.png 12:39:46 INFO: [ASYNC 🔥]: 200 bafkreib75jqxadtvzi7amit66b4zhvzoehtq3i722q4fl4pz37v636mmwy.png 12:39:46 INFO: [ASYNC OBJECT]: ❄️ 200 bafkreidzj3u2h2rprg2p3walm4zvhtiz3oc52fiojrjwcwwsg6bpsbv6ya
The similar issue when there are initially less tasks then the maxsize of the limited set
May @unknow112 can check
For testing: if you do not get enough data change the param in graphql_ago (in graphql.py) from 30 to 240 or so
graphql_ago
graphql.py
30
240
on it
I found out that in when the app is about to end it does not handle that the
_unfinished_tasks
can spawn other taskswhen i run the app it will finish those 5 tasks however the 3 🔥 tasks should spawn 3 more ❄️
The similar issue when there are initially less tasks then the maxsize of the limited set
May @unknow112 can check