Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    David Huard
    @huard
    Ok for me.
    Long Vu
    @tlvu
    @cehbrecht if I remember correctly, the new "watchdog" service have to be activated in the config so could we simply leave it there on master because it is not active by default anyways? I just don't remember if the previous mechanism it replaces is still on master or not.
    Long Vu
    @tlvu
    But good call to go-live with one change at a time so it's easier to debug.
    MacPingu
    @cehbrecht
    @tlvu the implementation for the “watchdog, job queue” has changed … also introducing database migration. Currently we don’t use the master … still relying on 4.2.x … I would feel better if we can get the master in production again … and bring in the changes one by one: py3 only, database migration, job queue ...
    py3 only would be a 4.4.x release … database migration and jobqueue could go in 5.x.
    @tomkralidis @ldesousa do you have opinions on “moving jobqueue to dev branch”? How would you safely revert changes on master?
    Tom Kralidis
    @tomkralidis
    sure, no objections
    Jachym Cepicky
    @jachym
    watchdog ... is replaced by the jobque isn't it?
    and that is in master and working well afaik?
    or I'm lost
    MacPingu
    @cehbrecht
    “Watchdog”=jobqueue … just the name I remembered. The jobqueue is still not finalised and we don’t use the master at the moment …
    Jachym Cepicky
    @jachym
    well, but it is in the master afaik and the jobqueue afaik works (?(
    https://github.com/geopython/pywps/blob/master/pywps/cli.py
    Jachym Cepicky
    @jachym
    https://github.com/geopython/pywps/blob/master/pywps/app/Process.py#L193
    Jachym Cepicky
    @jachym
    geopython/pywps#505
    MacPingu
    @cehbrecht
    there are still things missing (clean up of the database) and we didn’t get it into production. We are relying on the 4.2.x branch … and backporting patches from master to 4.2.x is troublesome … it has still py2 compatibility. An alternative could be to make a 4.4.x branch with py3 only support.
    MacPingu
    @cehbrecht

    @jachym @ldesousa @tomkralidis @tlvu I have made a patch release 4.2.7:
    https://pypi.org/project/pywps/4.2.7/

    This release has a patch for the auto_doc extension:
    geopython/pywps#542

    Tom Kralidis
    @tomkralidis
    +1
    Long Vu
    @tlvu
    Thanks for the release @cehbrecht
    MacPingu
    @cehbrecht
    @tomkralidis @jachym @ldesousa @huard I have updated the slide for pywps (page 52):
    https://docs.google.com/presentation/d/1C6llSnWZ28c2aWQgttPiOnoo6dttdqKg07ugU_yr6Uc/edit#slide=id.g24e11ca246_1_0
    … for OSGeo status report this Thursday.
    Tom Kralidis
    @tomkralidis
    Great thanks @cehbrecht
    MacPingu
    @cehbrecht
    @tomkralidis @jachym @ldesousa Ok to make a patch release 4.2.8? We need some fixes on pywps-4.2 … it is easier to deploy as conda package.
    Tom Kralidis
    @tomkralidis
    +1
    MacPingu
    @cehbrecht
    @tomkralidis @jachym @ldesousa @tlvu There is now a new patch release 4.2.8 with updates for the scheduler extension:
    https://pypi.org/project/pywps/4.2.8/