Brad Rydzewski

👍 yes, I think it is a good idea

we are handling this. someone internally changed the Slack settings to require a harness.io email address. I have asked the team to revert this change by end of day. I...

> Following this approach I have found that it is not possible to run pipelines, as they create the Drone container expecting to have access to Gitness using the 'http://host.docker.internal:3000/'...

@vistaarjuneja can this also be solved by the "extra hosts" setting? Also, let's see if macvlan can be used as well. This seems like a great option to explore. @Drophoff...

> I have been encountering repeated "http: no content returned: re-connect and re-try" errors Note that these are not errors, these are trace-level messages and are expected. The runners perform...

hey @BoyanXu thanks for the suggestion! would you mind posting some screenshots? what do you like about the current feature in Gitea? If we add this to Gitness, is there...

For Starlark, see my comment here: https://community.harness.io/t/starlark-maximum-file-size-exceeded-for-large-amount-of-pipelines/12623 For plain old yaml, many vendor apis (GitHub, etc) place a limit on the max file size returned. The maximum file size returned...

@fuero I am not aware of any limitations in the code that would result in the behavior you are describing, but if you are able to diagnose the underlying problem...

@fuero thank you for providing the sample files, however, this is not something I'm able to actively investigate right now. The fastest option to see this improved would be to...

> I think this plugin should follow the default Docker behavior instead of defaulting to Google. This plugin does follow the default docker behavior. The reason that the agent and...