Skip to content

Issues: FTWynn/gologgen

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.

Sign up for GitHub

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

10 Open 13 Closed
10 Open 13 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Log lines for datafile do not start immediately in UTC timezone
#24 opened Jun 6, 2017 by supereli
Make http output more resilient to crashes enhancement
#23 opened Mar 10, 2016 by FTWynn
Token replacer breaks if using the old comma separated style bug
#22 opened Mar 10, 2016 by FTWynn
Handle specifying timezones and running from differently timezoned machines enhancement
#21 opened Mar 10, 2016 by FTWynn
1
Implement rate limiting on http posting, as too much data causes the process to crash bug
#20 opened Feb 16, 2016 by FTWynn
Implement a single output bus enhancement
#17 opened Feb 10, 2016 by FTWynn
If ReplayFiles is listed twice in the JSON, some of the files are ignored bug
#14 opened Feb 4, 2016 by FTWynn
1
Add support for a log line depending another enhancement
#6 opened Jan 17, 2016 by FTWynn
Add jitter for timestamps in replay files so they seem a little less mechanical enhancement
#5 opened Jan 17, 2016 by FTWynn
Add a "Fast Forward" option so that the data will be output as quickly as possible enhancement
#3 opened Jan 17, 2016 by FTWynn
ProTip! Type g i on any issue or pull request to go back to the issue listing page.