ryancurrah
Repos
87
Followers
65
Following
177

Synology notifications service

61
9

Easily create Splunk searches from Python and get the result as a Python object.

13
5

Allow and block list linter for direct Go module dependencies.

38
5

Notify Slack with Unifi Alarms and Events

2
0

Weather in your terminal!

0
0

Events

Bind mounts should be (re)created when request uses container name

We just adopted Rancher Desktop at our organization and some of our Windows developers are running into this issue. Look forward to seeing this in the next release! Thank you.

Created at 21 hours ago
Update Lima to Latest so We Can Try Virtiofs

@jandubois in the meantime is there a way we can get rancher desktop to use a newer version of lima manually? Like copying the latest lima binary to where it is embedded in the rancher desktop install location?

Created at 1 day ago
Created at 1 day ago
Update Lima to Latest so We Can Try Virtiofs

Problem Description

The bundled version of Lima does not include Virtiosfs Mount mode support.

Proposed Solution

Sync the forked version of Lima and update lima-and-qemu and create a new release of Rancher Desktop. If it doesn't break things.

Additional Information

No response

Created at 2 days ago
chown error on bind mount when trying to launch postgres via docker compose

Looks like 6 days ago Lima documented using virtiofs https://github.com/lima-vm/lima/commit/c18ae239b69a47db77436765b9b4861aaa0d595d

Created at 1 week ago
issue comment
Filesystem Sharing

Looks like 6 days ago Lima documented using virtiofs https://github.com/lima-vm/lima/commit/c18ae239b69a47db77436765b9b4861aaa0d595d

Created at 1 week ago

Bump golang.org/x/mod from 0.6.0 to 0.7.0

Bumps golang.org/x/mod from 0.6.0 to 0.7.0.


updated-dependencies:

  • dependency-name: golang.org/x/mod dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Created at 3 weeks ago
pull request closed
Bump golang.org/x/mod from 0.6.0 to 0.7.0

Bumps golang.org/x/mod from 0.6.0 to 0.7.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 3 weeks ago

Bump golang.org/x/mod from 0.5.1 to 0.6.0

Bumps golang.org/x/mod from 0.5.1 to 0.6.0.


updated-dependencies:

  • dependency-name: golang.org/x/mod dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Created at 1 month ago
pull request closed
Bump golang.org/x/mod from 0.5.1 to 0.6.0

Bumps golang.org/x/mod from 0.5.1 to 0.6.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 1 month ago
started
Created at 1 month ago
issue comment
precise-code-intel-worker doesn't respect manage bucket environment variable

Any timeline on the 4.1 release?

Created at 1 month ago
issue comment
invalid archive error when using goreleaser-pro

Thanks @caarlos0 devs here are going to appreciate this a lot!

Created at 2 months ago
opened issue
invalid archive error when using goreleaser-pro

What happened?

When using goreleaser-pro's includes feature and generating multiple binaries and a single artifact we get an error.

╰─ goreleaser release --skip-publish --rm-dist
  • by using this software you agree with its EULA, available at https://goreleaser.com/eula
  • running goreleaser v1.11.3-pro (outdated, latest is v1.11.2-pro)
  • starting release...
  • loading config file                              file=.goreleaser.yaml
  • importing .goreleaser.common.yml
  • loading environment variables
  • getting and validating git state
    • couldn't find any tags before "v0.1.1"
    • building...                                    commit=e1282a48bb70ae920118492137d979f0a18317e7 latest tag=v0.1.1
  • parsing tag
  • setting defaults
  • checking distribution directory
    • --rm-dist is set, cleaning it up
  • loading go mod information
  • build prerequisites
  • writing effective config file
    • writing                                        config=dist/config.yaml
  • generating changelog
    • writing                                        changelog=dist/CHANGELOG.md
  • building binaries
    • building                                       binary=dist/cli_darwin_amd64_v1/helloworld
    • building                                       binary=dist/worker_linux_amd64_v1/helloworld
    • building                                       binary=dist/api_linux_amd64_v1/helloworld
    • took: 5s
  • archives
  ⨯ release failed after 5s                  error=invalid archive: 1: archive has different count of built binaries for each platform, which may cause your users confusion. Please make sure all builds used have the same set of goos/goarch/etc or split it into multiple archives

The error is invalid archive: 1: archive has different count of built binaries for each platform, which may cause your users confusion. Please make sure all builds used have the same set of goos/goarch/etc or split it into multiple archives.

At our company we use a common .goreleaser.common.yml file across all modules with sane defaults for us. One of those common configs is to not generate any archives (we do not need them generally and creating archives increases the build times due to time spent compressing the binaries).

You can see how we configure that here in my replication of the issue: https://github.com/ryancurrah/goreleaser-pro-bug/blob/main/.goreleaser.common.yml.

Using that common config and then creating an archive in the .goreleaser.yml for a CLI we get the above error. Example .goreleaser.yml here: https://github.com/ryancurrah/goreleaser-pro-bug/blob/main/.goreleaser.yaml.

Important note it is only when there is more than two builds this error occurs. If you comment out the api build in my example we will not run in to the error.

How can we reproduce this?

I have created simple replication of the issue in a git repository located here: https://github.com/ryancurrah/goreleaser-pro-bug.

Run the following commands to reproduce the error.

export GORELEASER_KEY="<YOUR_PRO_KEY_HERE>"
git clone https://github.com/ryancurrah/goreleaser-pro-bug.git
cd goreleaser-pro-bug
goreleaser release --skip-publish --rm-dist

goreleaser version

v1.11.3-pro

GoReleaser Check

  • [X] goreleaser check shows no errors

Search

  • [X] I did search for other open and closed issues before opening this.

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

Additional context

This has been an issue for a while I just haven't had the time to report it. So it's not something new that broke.

Created at 2 months ago
ryancurrah create tag v0.1.1
Created at 2 months ago
ryancurrah create tag v0.1.0
Created at 2 months ago
ryancurrah create branch main
Created at 2 months ago
create repository
ryancurrah create repository
Created at 2 months ago
BitbucketTagSCMHead does not receive an annotated tag date

I looked at Bitbuckets JIRA issues and found an issue where someone is asking for Bitbucket to support listing tags and getting their create date. I added a comment to it and linked it to this issue.

https://jira.atlassian.com/browse/BSERV-7764

Created at 2 months ago
issue comment
Add golang.org/x/vuln/vulncheck as a linter

Looks like they have a API now, I havent looked at it though.

To directly integrate vulnerability checking into other tools and processes, the vulncheck package exports govulncheck’s functionality as a Go API.

Created at 2 months ago