Francis Charette-Migneault

@cehbrecht It looks like a change was pushed, but still incorrect (up to `4.5.5` instead of `4.4.5`): https://nvd.nist.gov/vuln/detail/CVE-2021-39371#VulnChangeHistorySection Changed | CPE Configuration | OR *cpe:2.3:a:github:owslib:0.24.1:*:*:*:*:*:*:* *cpe:2.3:a:osgeo:pywps:*:*:*:*:*:*:*:* versions up to (excluding)...

I see the update to `4.4.5`. This is weird, security automation bots don't seem to pick it up and remain stuck on `4.5.0` for some reason. Weaver can be added...

@huard I guess that would be a good compromise without directly impacting existing process definitions.

@cehbrecht Maybe my interpretation is wrong, but I believe that if an input has `min_occurs=1`, and you don't provide it during Execute request, the process should return an error indicating...

I dug down in the specs. OGC says that definitions of `minOccurs`, `maxOccurs` and `default` should behave as defined by XML schema specifications when parsing WPS-1. Looking at https://www.w3.org/TR/xmlschema-0/#OccurrenceConstraints It...

I think the "conceptual" `min_occurs=1` by default is valid. By this, I mean that user not explicitly providing a value for `min_occurs` should default to `1`. Most users intend inputs...

@cehbrecht I am fine with a warning. It should offer sufficient information for users to manually updated it as needed. I think it is worth having in 4.4.x (and any...

More detail... Input `dataset` gets generated here: https://github.com/geopython/pywps/blob/793ab34bc9aab976243b8a7252e64429c6e65f4f/pywps/app/Service.py#L115-L120 At that point, following values are defined: ```python request_inputs = None inpt._default = {'mimeType': 'application/x-netcdf', 'encoding': None, 'schema': None, 'maximumMegabytes': None, 'default':...

Also seeing this. Breaking multiple linting checks pipeline.

Are there any plans to provide this feature eventually? The daily PR open/close spam cycle is becoming extremely ridiculous with many repos affected by similar dependencies that cannot be updated...