fix(client): handle errors from the getSessions query in the Dashboard

[leafty]

Fixes #2873.

Introduces a new context and component to handle RTK Query errors in the case when nested components use an errored query.

/deploy

[RenkuBot]

You can access the deployment of this PR at https://renku-ci-ui-2903.dev.renku.ch

[lorenzo-cavazzi]

Nice solution and the code looks good 👍

Should we show a banner on the Dashboard mentioning there is a problem with sessions when we get errors? Otherwise, users do not know that's the case and all looks fine

[leafty]

Should we show a banner on the Dashboard mentioning there is a problem with sessions when we get errors? Otherwise, users do not know that's the case and all looks fine

I add 3befaf0, but I am not sure if users will understand the error message.

[lorenzo-cavazzi]

Oh, I meant something more generic, like a Warning saying "Sessions are currently unavailable"

[leafty]

Oh, I meant something more generic, like a Warning saying "Sessions are currently unavailable"

Done in 65d40d3.

[lorenzo-cavazzi]

Very nice solution!

I noticed the function extractRkErrorMessage isn't working as expected. I'm unsure whether the Notebooks error is different from the Core error, or if something else is wrong in the logic there.
It would be great if you had some spare time to look at it. Otherwise, feel free to remove the specific error message and we can make a follow-up issue to fix the "RkErrorMessage" component(s) -- it would be great to have one that "just works", or to clearly distinguish between "renku-core" and "renku-notebooks" errors.

[leafty]

Very nice solution!

I noticed the function extractRkErrorMessage isn't working as expected. I'm unsure whether the Notebooks error is different from the Core error, or if something else is wrong in the logic there. It would be great if you had some spare time to look at it. Otherwise, feel free to remove the specific error message and we can make a follow-up issue to fix the "RkErrorMessage" component(s) -- it would be great to have one that "just works", or to clearly distinguish between "renku-core" and "renku-notebooks" errors.

I think it's not as simple because if I remove the notebooks service I get a proper error:

[lorenzo-cavazzi]

Some errors are handled, but others aren't (E.G. the renku-notebooks standard)

[RenkuBot]

Tearing down the temporary RenkuLab deplyoment for this PR.