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

Cylc log dropdown forgets old logs upon re-insertion of old tasks #2727

Closed
GlennCreighton opened this issue Jul 13, 2018 · 8 comments
Closed
Assignees
Labels
Milestone

Comments

@GlennCreighton
Copy link

GlennCreighton commented Jul 13, 2018

When reinserting a task that has already been removed, I'm finding that the log dropdown no longer functions as expected. The dropdown only includes the log for job 1 and the new job's log cannot be viewed. This occurs with Cylc 7.7.1.

cylc log issue

@matthewrmshin matthewrmshin added this to the soon milestone Jul 13, 2018
@hjoliver
Copy link
Member

Reproduced. After re-insertion, the job try number continues to increment correctly, but doesn't get displayed correctly in the GUI job log viewer.

@matthewrmshin
Copy link
Contributor

The bug starts here:
https://github.com/cylc/cylc/blob/f99193f3eb7aae00f3e4ff7e708ace54e4ae9ea6/lib/cylc/gui/app_gcylc.py#L2208

The length of the dict may not be the same as the maximum value of the dict keys, because there may be missing submits, like in this case.

@GlennCreighton
Copy link
Author

This also appears to happen after restarting the suite.

@matthewrmshin
Copy link
Contributor

There is a secondary problem here. If the reinserted task is in the waiting state, visibility of the links to job file views in the right click menu is determined by the current task state - so even though the task may have been submitted(+run) before, the right click menu may not display the links to job files for previous submits.

@matthewrmshin
Copy link
Contributor

@wxtim Can you please check whether #2830 fully fixes this issue or not?

@GlennCreighton
Copy link
Author

i did a quick test and it looks like this fix does the trick. Thanks!

@wxtim
Copy link
Member

wxtim commented Nov 12, 2018

I believe that this has fixed the issue. :)

@matthewrmshin matthewrmshin modified the milestones: soon, next release Nov 12, 2018
@matthewrmshin
Copy link
Contributor

Closed by #2830.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants