francescoingv

**Description** The processor cannot return outputs based on the `outputs` parameter of a `process-execute` **Steps to Reproduce** Create a processor (say `TestProcessor`) derived from `BaseProcessor` with the following `outputs` section...

I understand there is a backward compatibility issue, however I believe to let the community to program the processing services according to the standard, the upgrade of the interface is...

The issue is still open as a bug: the parameter `outputs` contains also the property `transmissionMode`, which should be passed on to the ProcessManager and then to Process to properly...

@ricardogsilva I also have the issue on pygeoapi/.github/workflows/containers.yml (line 39 - 40) when I commit to my local repository. I have a DockerHub account, but I don't know where to...

@ricardogsilva as of today, possibly the reported error changed a little, but when pulling a commit on a branch of a fork of geopython/pygeoapi:master I still get an email with...

Thank you @webb-ben , I will check it: but would it be possible to avoid the docker part?

> @francescoingv you will need to set this in the [settings tab of your fork](https://github.com/francescoingv/pygeoapi/settings/secrets/actions) @webb-ben I set the 2 secrets in my settings, however I still get an error....

@webb-ben thank you. In your screenshot I only saw DOCKER_USERNAME (I set it to my docker account name) and DOCKER_TOKEN (I set it to the token I got from docker,...

Dear @webb-ben, now I have set the Action-Secrets above (`DOCKER_REPOSITORY, DOCKER_USERNAME, DOCKER_PASSWORD`) but I still get the following error: ``` Run docker/[email protected] with: username: *** password: *** ecr: auto logout:...

@webb-ben I can use either `PAT` or `literal password`. Finally I succeeded, **but** the setting were the following: 1. `DOCKER_USERNAME` was my dockerhub **account name** (in my case `francescomartinelliingv`); **not...