Two bug

[Amos-x]

1. django_apscheduler/result_storage.py line 32 :
   job_execution.duration = float(job_execution.finished) - float(job_execution.started)
   job_execution.started or job_execution.finished is possible to be empty，so，float will raise except.
   You can simply change to：
   try: job_execution.duration = float(job_execution.finished) - float(job_execution.started) except: job_execution.duration = None

2. django_apscheduler/models.py line 40:
   next_run_time = models.DateTimeField(db_index=True)
   Fields should not be set as required， job.pause() will not work
   You can simply change to：
   next_run_time = models.DateTimeField(db_index=True,blank=True,null=True)

[sallyruthstruik]

Hello,

Thank you for this info about bugs and providing patches. I'll try to fix it ASAP

[GitBib]

Another problem. Migration complete
from django_apscheduler.jobstores import DjangoJobStore, register_events File "c:\users\usi\src\django-apscheduler\django_apscheduler\jobstores.py", line 15, in <module> from django_apscheduler.models import DjangoJob File "c:\users\usi\src\django-apscheduler\django_apscheduler\models.py", line 39, in <module> class DjangoJob(models.Model): File "C:\Users\usi\AppData\Roaming\Python\Python36\site-packages\django\db\models\base.py", line 100, in __new__ app_config = apps.get_containing_app_config(module) File "C:\Users\usi\AppData\Roaming\Python\Python36\site-packages\django\apps\registry.py", line 244, in get_containing_app_config self.check_apps_ready() File "C:\Users\usi\AppData\Roaming\Python\Python36\site-packages\django\apps\registry.py", line 127, in check_apps_ready raise AppRegistryNotReady("Apps aren't loaded yet.") django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
Settings:
INSTALLED_APPS = [....,
'django_apscheduler',
]
Versions:
Django == 2.0.3
django-apscheduler == 0.2.5
apscheduler==3.5.1

[askerka]

@sallyruthstruik Hi! Do you have any updates or approximate schedule of fixes?
@GitBib BTW, it doesn't look like a bug. Perhaps, you trying import model (DjangoJobStore) before django ready. Try do it in apps.py on ready event

[sallyruthstruik]

@asduj I'm sorry for a long reply. I've just uploaded new release: https://github.com/jarekwg/django-apscheduler/releases/tag/0.2.6. Also available on Pypi. This release fixes two bugs described above. Please, check with you project, and if all is ok I'm close the issue.

@GitBib asduj is right, looks like you import models before app initialization. If problem still exists, please give me traceback in more clear form using ```: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code

[askerka]

Looks good!