Eric Lemoine

I think we could introduce a `no_retry_exceptions` parameter, and do this in the `get_schedule_in` function: ```py def get_schedule_in(self, *, exception: Exception, attempts: int) -> Optional[int]: if self.max_attempts and attempts >=...

> (I think we could raise if `retry_exceptions` and `no_retry_exceptions` are used at the same time.) Yep, agree.

No, there's no such thing. The return values of tasks are ignored by Procrastinate. They are actually [logged](https://github.com/peopledoc/procrastinate/blob/3d8d8ad67e555853f5939d70abd43029d435194f/procrastinate/worker.py#L296-L298), but that's it. In particular they're not stored in the `procrastinate_jobs` table....

> * I can get a job's status from the table `procrastinate_jobs`, but I would need to write the query myself Yep. Contrary to what I said in my previous...

> Alright, thanks for confirming! I'm contemplating a move from Celery to procrastinate because it fits our setup so well (the locking features in particular), but having to implement something...

Yes, we've considered it. We could start by adding support for asyncpg as opposed to replacing aiopg. PRs are very welcome!

@alucab1 can you please use triple backticks around your code blocks for a proper formatting of your code? Example: ```py @app.periodic(cron="*/30 * * * * *") @app.task( name="print analysis", queue="power",...

Yep, in particular that problem occurs when the pool is created with `minsize=0` and `maxsize=0`: ```py >>> pool = await aiopg.create_pool(dsn="", minsize=0, maxsize=0) >>> await pool._fill_free_pool(True) Traceback (most recent call...

Wouldn't this require that ESRI WMS have support for a `DPI` vendor param (like MapServer's `MAP_RESOLUTION` param)?

I think I understand. But you probably mean 180 dpi rather than 144 dpi as the default WMS DPI is 90 (rather than 72).