Nicolas Höning

Current list of ideas of TODOs: - [ ] make other tests pass, as well - [ ] base rate limiting for non-resource endpoints (e.g. ping, login) - [ ]...

Technically, it would be nice to offer this as an API endpoint first. Then we can add the UI listing on top later.

Maybe that was based on my bad advice, forgot that the original branch is still open. I'm releasing now, so we can merge the other one in a bit.

Our LFX Security dashboard: https://security.lfx.linuxfoundation.org/#/a092M00001LkH4sQAF/overview A ticket I created to state what I did and how they can help us: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/4/SUPPORT-22038

If #574 happens, we might also have to remove/update the latest schedule ID / flex model, unless this is only written after a job is computed.

Isn't [this in-built RQ solution](https://python-rq.org/docs/jobs/#stopping-a-currently-executing-job) better for canceling an ongoing job?

I see how you came to this, but I guess one does not have to view the portfolio as aggregated (on one contract). That seems to be our default view...

I added a TODO item, so this feature is also available through the CLI.

Hi @Srieon, the toy example using the CLI would by default not require Redis, as the `--as-job` parameter [is False per default](https://github.com/FlexMeasures/flexmeasures/blob/main/flexmeasures/cli/data_add.py#L967). The API expects to be able to queue...

Hi @Srieon, I agree that often they are the same. I see that in the CLI command production prices default to consumption prices, but right now I don't see where...