Ionosphere learn countdown clock at 0 when client and server timezone differs #52
Comments
earthgecko
added a commit
that referenced
this issue
Jul 17, 2018
IssueID #2270: luminosity IssueID #2446: Optimize Ionosphere - Added SQL updates for #2446: Optimize Ionosphere - Modified ionosphere.py to use order_by to ensure that the latest fps and layers are checked first - Added stats to ionosphere.py, layers.py amd ionosphere matched tables on fp/layers counts vs how many were checked until match - Added missing logger defines to luminosity/process_correlations.py - Corrected settings.py docstrings on SECRET_KEY and OTHER_SKYLINE_REDIS_INSTANCES - Changed created column position in skyline/webapp/templates/search_features_profiles.html to be the first date column - Typo line in skyline/webapp/templates/training_data.html - Use ALTERNATIVE_SKYLINE_URLS with multiple Skyine instances to either redirect to the other Skyline instance if there are only 2 or give a list of ALTERNATIVE_SKYLINE_URLS if many than 2 Skyline instances in skyline/webapp/webapp.py - Corrected utils/seed_data.py to report SKYLINE_URL - Updated documentation Added: updates/sql/ionosphere-v1.1.x-to-luminosity-v1.2.2-stable.sql updates/sql/luminosity-v1.2.0-to-luminosity-v1.2.2.sql updates/sql/luminosity-v1.2.1-beta-to-v1.2.2-stable.sql docs/releases/1_2_2.rst Modified: docs/conf.py docs/getting-started.rst docs/installation.rst docs/ionosphere.rst docs/overview.rst docs/releases.rst docs/releases/1_2_1.rst docs/roadmap.rst docs/tsfresh.rst docs/upgrading/index.rst skyline/ionosphere/ionosphere.py skyline/ionosphere/layers.py skyline/luminosity/process_correlations.py skyline/settings.py skyline/skyline.sql skyline/skyline_version.py skyline/webapp/templates/search_features_profiles.html skyline/webapp/templates/training_data.html skyline/webapp/webapp.py utils/seed_data.py IssueID #2444: Evaluate CAD If the json.loads fails use literal_eval and log typo in crucible_algorithms Modified: skyline/crucible/crucible.py skyline/crucible/crucible_algorithms.py Issue #52: Ionosphere learn countdown clock at 0 when client and server timezone differs IssueID #2450: Ionosphere learn countdown clock at 0 when client and server timezone differs Added to known bugs in the training_data page Modified: skyline/webapp/templates/training_data.html
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the duration of the Ionosphere learn countdown, if the client and server have a different time zone settings the countdown clock will display 00:00:00 for the entire duration of the countdown. Once the Ionosphere learn period has passed the countdown clock is removed as normal and replaced with
Countdown :: valid to learn :: TrueThe text was updated successfully, but these errors were encountered: