Luis Pabon

I was also getting this error upon moving a git repo from organisation to organisation and I had forgotten to apply the changes on the resource's config.

Looks like some fonts are failing to load:  When I try to manually open fontawesome on the browser: 

Thank you, that workaround does work for me as well.

The workaround doesn't quite fix all though:  The headers on the dataset list table as you can see don't look right - perhaps some of the styles gone on...

"Super" is a good name that's actually also used by other compositors, like Sway for instance.

This is definitely a must. The native events should at least be recording who in addition to what when argo is being interacted with via the UI or the cli.

Is there any way to configure proxmox not to format these as HTML to begin with?

> this is still an issue. Any help pls ? I have personally given up on this now that proxmox allows you to define a webhook in enough detail that...

Thank you @soapy1 Indeed the problem seems to persist. I upgraded to the very latest vagrant available on Hashicorp's Ubuntu repos (2.2.18), set `VAGRANT_EXPERIMENTAL=dependency_provisioners` then re-created the machine from scratch...

Issue is still present