Joachim Jablon

This looks like we might be able to make a reproducing test in procrastinate's own codebase ?

You can turn that warning into an error with [@pytest.mark.filterwarnings](https://docs.pytest.org/en/stable/how-to/capture-warnings.html#pytest-mark-filterwarnings) (you can use filterwarning for the whole testsuite but in this cas we probably want to do it only for...

Welcome to the club of `Joa(qu|ch)im` procrastinators ! Btw, as the repo maintainer, I opened the issue tracking the discussion but @TheNeedForSleep is the one deserving praise for this. Feel...

I agree with everything @onlyann and @medihack have said. I'll add that we have a [v3 milestone](https://github.com/procrastinate-org/procrastinate/milestone/2) that is getting completed and I plan to work on #1189 on the...

Closed in v3

> if there are schema changes, package should detect new changes, give warnings or there should be some kind of backward compatibility, regardless I think worker should not crash on...

(Unfortunately, unable to reproduce so far. If anyone has additional info, please reopen!)

Note: we can do it with [Mermaid](http://mermaid.js.org/), [Myst](https://mystmd.org/guide/diagrams) supports it (so does Github Flavored Markdown)

I gave it a shot and it's a bit annoying: - If we don't compile the mermaid graph when building the doc (a.k.a `raw`): - We won't know if there's...

You're probably right. Let's say the question is whether we just intend to have a single graph or if we can think of other parts of the doc that could...