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

*.log: use yyyy-mm-dd (iso8601) in timestamps #2564

Merged
merged 2 commits into from
Nov 24, 2023
Merged

*.log: use yyyy-mm-dd (iso8601) in timestamps #2564

merged 2 commits into from
Nov 24, 2023

Conversation

mmetc
Copy link
Contributor

@mmetc mmetc commented Oct 25, 2023

No description provided.

@github-actions
Copy link

@mmetc: There are no 'kind' label on this PR. You need a 'kind' label to generate the release automatically.

  • /kind feature
  • /kind enhancement
  • /kind fix
  • /kind chore
  • /kind dependencies
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@github-actions
Copy link

@mmetc: There are no area labels on this PR. You can add as many areas as you see fit.

  • /area agent
  • /area local-api
  • /area cscli
  • /area security
  • /area configuration
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@mmetc mmetc added the kind/enhancement New feature or request label Oct 25, 2023
@mmetc mmetc changed the title iso8601: use yyyy-mm-dd in log timestamps instead of dd-mm-yyyy logs: use yyyy-mm-dd (iso8601) in timestamps instead of dd-mm-yyyy Oct 25, 2023
@mmetc mmetc changed the title logs: use yyyy-mm-dd (iso8601) in timestamps instead of dd-mm-yyyy *.log: use yyyy-mm-dd (iso8601) in timestamps instead of dd-mm-yyyy Oct 25, 2023
@codecov
Copy link

codecov bot commented Oct 25, 2023

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (1dcf9d1) 57.39% compared to head (5d4a813) 52.44%.

Files Patch % Lines
pkg/types/utils.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2564      +/-   ##
==========================================
- Coverage   57.39%   52.44%   -4.95%     
==========================================
  Files         195      112      -83     
  Lines       26939    15131   -11808     
==========================================
- Hits        15462     7936    -7526     
+ Misses       9897     6349    -3548     
+ Partials     1580      846     -734     
Flag Coverage Δ
bats ?
unit-linux ?
unit-windows 52.44% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mmetc mmetc changed the title *.log: use yyyy-mm-dd (iso8601) in timestamps instead of dd-mm-yyyy *.log: use yyyy-mm-dd (iso8601) in timestamps Oct 25, 2023
@mmetc mmetc added this to the 1.5.6 milestone Nov 7, 2023
@mmetc mmetc merged commit ec19916 into master Nov 24, 2023
13 checks passed
@mmetc mmetc deleted the log-iso8601 branch November 24, 2023 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request needs/area
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants