Skip to content
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.

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

Backport master to 4.4 #574

Merged
merged 16 commits into from
Feb 9, 2021
Merged

Backport master to 4.4 #574

merged 16 commits into from
Feb 9, 2021

Conversation

cehbrecht
Copy link
Collaborator

Overview

This branch backports the changes on master to pywps 4.4.

Related Issue / Discussion

#568

Additional Information

List of integrated PRs:

Skipped PRs:

Contribution Agreement

(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

  • I'd like to contribute [feature X|bugfix Y|docs|something else] to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.
  • [ x] I have already previously agreed to the PyWPS Contributions and Licensing Guidelines

@cehbrecht cehbrecht marked this pull request as draft February 8, 2021 17:20
@coveralls
Copy link

coveralls commented Feb 8, 2021

Coverage Status

Coverage remained the same at 0.0% when pulling 4f15fc6 on cehbrecht:backport-to-4.4 into d593f4a on geopython:pywps-4.4.

@cehbrecht cehbrecht marked this pull request as ready for review February 8, 2021 18:14
@cehbrecht
Copy link
Collaborator Author

cehbrecht commented Feb 8, 2021

test with emu ... still seems to work.

@cehbrecht cehbrecht requested a review from tlvu February 8, 2021 18:21
@cehbrecht
Copy link
Collaborator Author

@tlvu @Zeitsperre Maybe you like to check this PR? We can still improve on pywps-4.4 also after merge ...

@Zeitsperre
Copy link
Collaborator

Zeitsperre commented Feb 8, 2021

@cehbrecht Would you like me to merge #573 into pywps-4.4 before this is merged?

I have opened a new PR: #575. Feel free to merge at your leisure!

Copy link
Collaborator

@Zeitsperre Zeitsperre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. For the Mmmetype list, I can't help but notice that the GeoTIFF mimetype is a matter of intense debate (opengeospatial/geotiff#34). Does it make sense to include Format('image/tiff', extension='.tiff', encoding='base64') as well? What are your thoughts?

Also, cosmetic opinion, but would you be open to isort-ing the library imports to clean them up a bit?

pywps/inout/formats/__init__.py Show resolved Hide resolved
pywps/app/Process.py Show resolved Hide resolved
setup.cfg Outdated Show resolved Hide resolved
@cehbrecht cehbrecht merged commit e10c99c into geopython:pywps-4.4 Feb 9, 2021
@cehbrecht cehbrecht deleted the backport-to-4.4 branch February 9, 2021 14:29
@cehbrecht
Copy link
Collaborator Author

@Zeitsperre @fmigneault Thanks for the review. Please give the pywps-4.4 branch a try ... when there are no complains I can make the 4.4.0 release.

@tlvu
Copy link
Collaborator

tlvu commented Feb 10, 2021

@cehbrecht sorry I took a day off yesterday, was not able to look at this sooner.

So basically if we diff this branch with master, the only differences would be the jobqueue feature? Everything else are backported? We could merge this branch back into master and it should NOT make a difference?

@tlvu
Copy link
Collaborator

tlvu commented Feb 10, 2021

Here is how master would change today if pywps-4.4 is merged into master: 20e1e25...e10c99c

Looks like all the changes from 4.2.4 forward are missing on master. Should be a good thing to have on master.

@tlvu
Copy link
Collaborator

tlvu commented Feb 10, 2021

Here is the reverse diff (if master would merge into pywps-4.4) e10c99c...20e1e25.

Looks like mostly the jobqueue but there are other changes that I am not familiar with.

@fmigneault
Copy link
Collaborator

I feel it would be a great idea to have first the resolution of python 2/3 with minor patches in 4.4.
Then, another (maybe major?) version for jobqueue and co. features.
This will greatly align with OGC-API / owslib eventual work (opengeospatial/joint-ogc-osgeo-asf-sprint-2021#2) that will require the job items.

I have started pointing at pywps-4.4 with this PR crim-ca/weaver#214
And so far it doesn't look like there are any major incompatibilities.

I fear though that the alembic database migration and all other job queue elements would cause a lot of problems on my side, while being unnecessary in weaver's case as jobs already have their own reporting/handling.

@cehbrecht
Copy link
Collaborator Author

I fear though that the alembic database migration and all other job queue elements would cause a lot of problems on my side, while being unnecessary in weaver's case as jobs already have their own reporting/handling.

@fmigneault In the next attempt for the job queue implementation I would prefer to life without alembic database migration. The database is essentially used for the queue and this is just temporary storage.

@cehbrecht
Copy link
Collaborator Author

Here is how master would change today if pywps-4.4 is merged into master: 20e1e25...e10c99c

Looks like all the changes from 4.2.4 forward are missing on master. Should be a good thing to have on master.

I could create a dev-branch from the current master and re-integrate the pywps-4.4 branch. The master should then be the same as pywps-4.4.

@tlvu
Copy link
Collaborator

tlvu commented Feb 11, 2021

I feel it would be a great idea to have first the resolution of python 2/3 with minor patches in 4.4.
Then, another (maybe major?) version for jobqueue and co. features.

I am not suggesting merging master to pywps-4.4 so no jobqueue on 4.4. I am only suggesting merge pywps-4.4 to master so master still contain all the fixes (return to the normal workflow before this divergence).

The 2 compare links I generated is simply for us to audit the changes between master and pywps-4.4 branch.

@tlvu
Copy link
Collaborator

tlvu commented Feb 11, 2021

Here is how master would change today if pywps-4.4 is merged into master: 20e1e25...e10c99c
Looks like all the changes from 4.2.4 forward are missing on master. Should be a good thing to have on master.

I could create a dev-branch from the current master and re-integrate the pywps-4.4 branch. The master should then be the same as pywps-4.4.

I think we simply just need to return to the regular workflow. Correct me if I am wrong but we used to merge all branches back to master so master always have all the cumulative changes?

So when we create new branches from master, we ensure the new branch is not missing anything from any previous published releases?

If what I understood is correct, then after the merge of pywps-4.4 to master, we can fix up the jobqueue on master to your liking @cehbrecht then cut a new branch from there for new release. This assume on master the only thing new vs pywps-4.4 is the jobqueue and nothing else (hence the usefulness of the compare links to see the diff between the branches).

@cehbrecht
Copy link
Collaborator Author

I feel it would be a great idea to have first the resolution of python 2/3 with minor patches in 4.4.
Then, another (maybe major?) version for jobqueue and co. features.

I am not suggesting merging master to pywps-4.4 so no jobqueue on 4.4. I am only suggesting merge pywps-4.4 to master so master still contain all the fixes (return to the normal workflow before this divergence).

The 2 compare links I generated is simply for us to audit the changes between master and pywps-4.4 branch.

Right. The job-queue is not on pywps-4.4 ... only in the history of master.

@cehbrecht
Copy link
Collaborator Author

If what I understood is correct, then after the merge of pywps-4.4 to master, we can fix up the jobqueue on master to your liking @cehbrecht then cut a new branch from there for new release.

When me make a new attempt on the job-queue I would do this on a dev branch. We can merge it to master when we are really sure we want to keep it 😄

The next things that could happen on master (after re-integration of pywps-4.4):

  • re-formatting using black?
  • clean up tests
  • work on rest api

@tlvu
Copy link
Collaborator

tlvu commented Feb 11, 2021

When me make a new attempt on the job-queue I would do this on a dev branch.

Correct. I did not literally meant any commits direct on master. I mean PR to master instead of PR to pywps-4.4.

Sorry if my message was not clear. Nothing should land on master without a PR.

@cehbrecht cehbrecht mentioned this pull request Feb 11, 2021
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants