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

:bomb: fix work id #652

Open
wants to merge 2 commits into
base: 8.0
from

Conversation

Projects
None yet
3 participants
@GabbasovDinar
Member

GabbasovDinar commented Sep 12, 2018

No description provided.

@yelizariev

This comment has been minimized.

Show comment
Hide comment
@yelizariev

yelizariev Sep 14, 2018

Member

How to reproduce the error that this update fix?

Member

yelizariev commented Sep 14, 2018

How to reproduce the error that this update fix?

@GabbasovDinar

This comment has been minimized.

Show comment
Hide comment
@GabbasovDinar

GabbasovDinar Sep 15, 2018

Member

@yelizariev When the timer counts down 2 hours, the server timer does not stop automatically due to a task ID error. The timer stops only after running the cron function

Member

GabbasovDinar commented Sep 15, 2018

@yelizariev When the timer counts down 2 hours, the server timer does not stop automatically due to a task ID error. The timer stops only after running the cron function

@yelizariev

This comment has been minimized.

Show comment
Hide comment
@yelizariev

yelizariev Sep 20, 2018

Member

Please update changelog and version

Member

yelizariev commented Sep 20, 2018

Please update changelog and version

@Ramil-Mukhametzyanov

If the subtask stops, its counter stops as appropriate.

@Ramil-Mukhametzyanov

Need to reload the page to see the following changes:
• Clicking on the subtask counter does not cause this counter to be paused.
• After creating a new subtask and running it, the counter is not updated. The counter does not change its behavior even if the subtask is paused.
• If another subtask is running, the subtask cannot be run after the run button is wrongly pressed.

@yelizariev

This comment has been minimized.

Show comment
Hide comment
@yelizariev

yelizariev Sep 24, 2018

Member

@GabbasovDinar add @Ramil-Mukhametzyanov's comments to README as TODOs or fix them

Member

yelizariev commented Sep 24, 2018

@GabbasovDinar add @Ramil-Mukhametzyanov's comments to README as TODOs or fix them

@GabbasovDinar

This comment has been minimized.

Show comment
Hide comment
@GabbasovDinar

GabbasovDinar Sep 24, 2018

Member

@yelizariev @Ramil-Mukhametzyanov I cannot reproduce the error

Member

GabbasovDinar commented Sep 24, 2018

@yelizariev @Ramil-Mukhametzyanov I cannot reproduce the error

@Ramil-Mukhametzyanov

I saw this bug again in a new build with updates and explicit modules.
It began when I clicked on the counters.
The problem disappeared after second entry in the pull through runbot.

@GabbasovDinar

This comment has been minimized.

Show comment
Hide comment
@GabbasovDinar

GabbasovDinar Sep 25, 2018

Member

@Ramil-Mukhametzyanov Maybe the problem is related to the error of the work of longpolling in the runbot. I don't have the error on my server

Member

GabbasovDinar commented Sep 25, 2018

@Ramil-Mukhametzyanov Maybe the problem is related to the error of the work of longpolling in the runbot. I don't have the error on my server

@Ramil-Mukhametzyanov

The main changes are verified.
It is difficult to reproduce errors with displaying counters on the runbot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment