Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Investigate possibly incorrect epoch value in `_check_evaluation_setting`
See original GitHub issueAccording to this issue, there may be a bug in _check_evaluation_setting in which an incorrect value for EPOCH is used.
Definition of Done
- verify whether we can reproduce
- if so, fix the bug (If the value is wrong, I believe this should be a quick fix, so propose making this issue investigate and fix)
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Conversion from epoch to datetime is incorrect - Stack Overflow
I'm using Ruby version 2.5.3p105 and my clock is set to the current year. This epoch value evaluates to today's date (February 2nd,...
Read more >Epoch Converter - Unix Timestamp Converter
Easy epoch/Unix timestamp converter for computer programmers. Includes epoch explanation and conversion syntax in various programming languages.
Read more >What Is Epoch? - TechTarget
The epoch is the date and time in a computer system or platform relative to the clock and timestamp values are determined.
Read more >Unix time - Wikipedia
Unix time is a date and time representation widely used in computing. It measures time by the number of seconds that have elapsed...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed with https://github.com/RasaHQ/rasa/pull/9182 and should be available in the next patch release of
2.8Pretty sure this happens when TEDPolicy is loaded (hence why it occurs during
rasa shell) and the epoch value is overridden with the default of 1. Related, this user also sees this when runningshell