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

Fixes #15713: Show log informations next to reports and full compliance report #2501

Conversation

VinceMacBuche
Copy link
Member

@VinceMacBuche
Copy link
Member Author

PR rebased

@VinceMacBuche VinceMacBuche force-pushed the bug_15713/show_log_informations_next_to_reports_and_full_compliance_report branch from 7cd18fc to 6c9bbaa Compare October 3, 2019 16:12
@VinceMacBuche
Copy link
Member Author

PR rebased

1 similar comment
@VinceMacBuche
Copy link
Member Author

PR rebased

@VinceMacBuche VinceMacBuche force-pushed the bug_15713/show_log_informations_next_to_reports_and_full_compliance_report branch 2 times, most recently from 84001a8 to 4358be6 Compare October 8, 2019 15:05
@VinceMacBuche
Copy link
Member Author

Commit modified

1 similar comment
@VinceMacBuche
Copy link
Member Author

Commit modified

@VinceMacBuche VinceMacBuche force-pushed the bug_15713/show_log_informations_next_to_reports_and_full_compliance_report branch 2 times, most recently from 04aaae3 to 4e33cb9 Compare October 9, 2019 15:27
@VinceMacBuche
Copy link
Member Author

Commit modified

@@ -217,6 +219,7 @@ case class ReportLine (

JsObj(
( "executionDate", executionDate.toString("yyyy-MM-dd HH:mm:ss") )
, ( "runDate", runDate.toString("yyyy-MM-dd HH:mm:ss") )
Copy link
Member

Choose a reason for hiding this comment

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

Can you use either ISODateTimeFormater .dateTime or our date formatter service with "getDisplayDate" ? We need at least timezone and it's more consistant that way

@VinceMacBuche
Copy link
Member Author

PR rebased

@VinceMacBuche VinceMacBuche force-pushed the bug_15713/show_log_informations_next_to_reports_and_full_compliance_report branch from 4e33cb9 to 63913fd Compare October 10, 2019 09:34
@VinceMacBuche
Copy link
Member Author

Commit modified

@VinceMacBuche VinceMacBuche force-pushed the bug_15713/show_log_informations_next_to_reports_and_full_compliance_report branch from 63913fd to 7e60c46 Compare October 10, 2019 09:38
@fanf
Copy link
Member

fanf commented Oct 14, 2019

When we first come to the page, all event logs are loaded, which leads to a very bad experience (huge latency...).
By default, there must be a "oldest date" setted to yesterday.
It may be a problem linked to: https://issues.rudder.io/issues/15945
If so, in case when dates are not parsable, we should get an error, not "load everything" which is very bad for rudder load.

@fanf
Copy link
Member

fanf commented Oct 14, 2019

bad PR, sorry !

@Normation-Quality-Assistant
Copy link
Contributor

OK, merging this PR

@Normation-Quality-Assistant Normation-Quality-Assistant merged commit 7e60c46 into Normation:branches/rudder/6.0 Oct 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants