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

Fixing unknown unknowns #19774

Merged
merged 1 commit into from
Jan 29, 2020
Merged

Conversation

d-m-u
Copy link
Contributor

@d-m-u d-m-u commented Jan 28, 2020

The automate model and dialog collection logfile thingy doesn't have the timestamp set and so the names look like Dialogs_region_0_default_2_EVM_1_unknown_unknown.zip.

We could just set it to now for the automate and model things and not have 🎉 unknown unknowns 🎉 .

Something like this could fix https://bugzilla.redhat.com/show_bug.cgi?id=1706989 maybe possibly, I dunno.

@miq-bot assign @jrafanie
@miq-bot add_label bug

I am almost too young to be making that reference anyway I was barely alive for that

@miq-bot miq-bot added the bug label Jan 28, 2020
@d-m-u d-m-u force-pushed the probably_bad_log_timestamp_fix branch 7 times, most recently from f1ce070 to a89402b Compare January 28, 2020 15:07
@d-m-u d-m-u changed the title Update model and dialog log timestamp to be regular log timestamp Update automate model/dialog log timestamp to be regular log timestamp Jan 28, 2020
@d-m-u d-m-u force-pushed the probably_bad_log_timestamp_fix branch 6 times, most recently from f7777ea to b82f372 Compare January 28, 2020 19:10
@d-m-u d-m-u changed the title Update automate model/dialog log timestamp to be regular log timestamp Fixing unknown unknowns Jan 28, 2020
@d-m-u d-m-u force-pushed the probably_bad_log_timestamp_fix branch from b82f372 to 35e696d Compare January 28, 2020 19:42
@d-m-u d-m-u force-pushed the probably_bad_log_timestamp_fix branch 2 times, most recently from c43129f to 62cf888 Compare January 29, 2020 16:42
@d-m-u d-m-u force-pushed the probably_bad_log_timestamp_fix branch from 62cf888 to 1c796d2 Compare January 29, 2020 17:19
@d-m-u d-m-u force-pushed the probably_bad_log_timestamp_fix branch from 1c796d2 to a4a3ba8 Compare January 29, 2020 19:44
@miq-bot
Copy link
Member

miq-bot commented Jan 29, 2020

Checked commit d-m-u@a4a3ba8 with ruby 2.5.5, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0
2 files checked, 0 offenses detected
Everything looks fine. 👍

@jrafanie
Copy link
Member

I am almost too young to be making that reference anyway I was barely alive for that

The entire quote is 🥇 . English at it's finest.

@jrafanie jrafanie added the core label Jan 29, 2020
Copy link
Member

@jrafanie jrafanie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like we know more about the unknowns now. 👍

@jrafanie jrafanie merged commit 5251f5a into ManageIQ:master Jan 29, 2020
@jrafanie jrafanie added this to the Sprint 129 Ending Feb 3, 2020 milestone Jan 29, 2020
@d-m-u d-m-u deleted the probably_bad_log_timestamp_fix branch January 29, 2020 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants