Mateusz Gozdek

Also, perhaps those should be unified: ```console $ git grep "gi.require('Soup'" tests/conversion__g_hash.js:const soup = gi.require('Soup') tests/conversion__g_list.js:const Soup = gi.require('Soup') tests/conversion__g_s_list.js:const soup = gi.require('Soup') tests/function_call__invalid_type.js:const Soup = gi.require('Soup') tests/object__initialization.js:const Soup =...

BTW, in some cases, like https://github.com/tinkerbell/tink/blob/34275668af5eede0475dae8f3aa6d75fe0cf0618/db/template.go#L17-L45, transaction is not even needed, as there is only a single query being made, which is already ensured to be atomic by the database...

@parauliya this is mitigation I talked about: https://github.com/kinvolk/terraform-provider-tinkerbell/commit/d4e4080646d51590944e4f656af2e85f67c85dd6.

Ah, BTW, this was also occurring for other resources, not only for workflows. I'll test if that's still the case.

This still occurs when workflows are removed: ``` Error: removing workflow "b06356a8-3ed4-11eb-a31e-0242ac1b0004": rpc error: code = Unknown desc = Delete Workflow Error: pq: could not serialize access due to read/write...

Creating/deleting Hardware entries and Templates seems OK.

>Well yaml is a superset of JSON so we can probably just parse the json with yaml reader :D. I tried the following and it worked: :+1: Similar to what...

I'm fine with removing the progress bar if it's a deliberate decision, it's really only useful in debugging :+1: My point in #450 was mainly to not remove the functionality...

If we put this under a log level flag, how can this be configured from user level? As part of workflow configuration? In hardware profile?

https://github.com/systemd/systemd/blob/401faa3533280b05fee972e0c64885caf4b31e4c/units/var-lib-machines.mount#L10 this might be the reason why it's not spawning. When I try to spawn it on Ubuntu 19.04 with systemd version 240. I get this error: ``` ubuntu: Download...