Leonardo Luz Almeida

Hi @kthibodeaux. I am not 100% but it seems that nvim-dap doesn't support defining the port at the `dap_configuration` level.

@brunobmello25 You are right. Currently, there is no support to pass flags while running a specific test.

@JonPichel debug test will invoke `dap.run(config)` which should trigger the `dap.listeners.before.launch` event I think. Unfortunately I don't use dapui much and don't know how to configure it exactly. Maybe try...

@cousine There is another on-going PR (https://github.com/leoluz/nvim-dap-go/pull/78) that I think will address your use-case. Can you please take a look and confirm? tks!

@theoribeiro Please update nvim-dap-go and check if this new feature addresses your use-case: https://github.com/leoluz/nvim-dap-go/commit/6da41ff1843dfc6cb3ab1a401ca255d43c11e1a2

@amirphl please check if `delve.build_flags` configuration addresses your use-case. If it doesn't, I currently don't have the time to implement it but feel free to push a PR in the...

> Hard-coded port allows to know which port to use in remote debug configurations, but in practice with many Go projects, it would be great to set the Delve port...

@cyb3rd4d Tks for the explanation. I'll try to review your PR soon.

@blakepettersson Can you please take a look at https://github.com/argoproj/gitops-engine/pull/574 It addresses the panic issue. However the reason why the `ParseableType` can not resolve the GVK is still unknown.

To avoid API breaking changes another suggestion could be: 1. Add a new fields in the status section dedicated for compressed data: `status.resourcesGzip` and `status.operationState.operation.sync.resourcesGzip` 2. Check if the new...