[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #5857: The query can not echo the content just checked

[GitBox <gi...@apache.org>]

github-actions[bot] commented on issue #5857:
URL: https://github.com/apache/dolphinscheduler/issues/5857#issuecomment-883021294


   1. I often check a batch of tasks killed at a certain point in time, so that I can rerun the data. After checking, click in to view a certain task, and then click the browser back button. The previous query records are gone, why? No echo function? ? ? ? Now it is version 1.2. The previous version 1.0 had this function. Why is it so bad? ? ? I have been mentioning bugs since 1.0. Can this basic interactive function be done well? What I am querying is a batch of tasks according to the conditions. Every time I check a certain task, it disappears? ? ?
   
   2. There are also 10 default pages each time, why do you have to limit to 10 at one point? ? ? After I selected 50 items, I clicked to view a certain task, and then clicked the browser back button to restore to 10 items. If I view it on the second page, it will be from the first page after backing up. What is this? Function? ? Can you optimize the experience? ? At least one user setting function is required. My current user setting is 50, and the maximum is not more than 200. Every time I log in, it is 50, not I have to choose! ! ! ! I chose page 2, why does the back turn to the first page? ? ?
   
   3. It is written in the architecture design that if the task becomes "need to be fault-tolerant" and the resources are sufficient, the scheduling will submit the task by itself. Now what is encountered is that the task becomes "needed to be fault-tolerant" and it will be stuck, and the scheduling resource will not be sufficient. I will submit it by myself, and fix this kind of BUG as soon as possible! A batch of tasks need to be fault-tolerant and hang up. You have to write down the name of the task every time and manually kill it before resubmitting it manually. Don't you feel tired?
   
   1. I often query a batch of tasks that were killed at a certain point in time, so that I can rerun the data. After checking, click in to view a task, and then click the browser back button. The previous query records are gone, why not return Significant function???? It is now version 1.2. The previous version 1.0 had this function. Why is it so bad??? I have been mentioning bugs since 1.0. Is this basic interactive function not doing well? What I am querying is a batch of tasks according to the conditions. Every time I check a certain task, it disappears???
   
   2. There are also 10 default pages each time, why do you have to limit 10 entries at one point??? After I selected 50 items, I clicked to view a certain task, and then clicked the browser back button to restore to 10 items. If I view it on the second page, it will be from the first page after backing up. What is this? Function?? Can you optimize the experience?? At least one user setting function is required. My current user setting is 50, and the maximum is not more than 200. Every time I log in, it is 50, not I have to choose!!!! I chose page 2, why does the back turn to the first page???
   
   3. It is written in the architecture design that if the task becomes "need to be fault-tolerant" and the resources are sufficient, the scheduling will submit the task by itself. Now what is encountered is that the task becomes "needed to be fault-tolerant" and it will be stuck, and the scheduling resource will not be sufficient. I will submit it by myself, this kind of BUG needs to be fixed quickly! A batch of tasks need to be fault-tolerant and hang up. You have to write down the task name and manually kill it and submit it again. Don't you feel tired?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org