Skip to content

Conversation

@rchincha
Copy link
Contributor

What type of PR is this?

Which issue does this PR fix:

What does this PR do / Why do we need it:

If an issue # is not available please add repro steps and logs showing the issue:

Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?

Does this PR introduce any user-facing change?:


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@rchincha rchincha requested a review from andaaron as a code owner November 15, 2025 07:07
@rchincha rchincha marked this pull request as draft November 15, 2025 07:08
@codecov
Copy link

codecov bot commented Nov 15, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.67%. Comparing base (008527b) to head (5e6b070).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3544   +/-   ##
=======================================
  Coverage   91.67%   91.67%           
=======================================
  Files         185      185           
  Lines       25852    25852           
=======================================
  Hits        23699    23699           
  Misses       1392     1392           
  Partials      761      761           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.


# Go compiler version
go:
- 1.22
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We only support 1.24.4+

- conda-forge
- defaults
dependencies:
- go >=1.22
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- go >=1.22
- go >=1.24.4

requirements:
build:
- {{ compiler('go') }}
- go >=1.22
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

go 1.22 is in 3 places, where did it pick it from?

{% set version = environ.get('RELEASE_TAG', 'dev').lstrip('v') %}
{% set commit = environ.get('COMMIT', 'unknown') %}
{% set go_version = environ.get('GO_VERSION', 'unknown') %}
{% set build_labels = environ.get('BUILD_LABELS', 'sync,search,scrub,metrics,lint,ui,mgmt,profile,userprefs,imagetrust,events') %}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For UI you need to get the UI build and untar it in a specific folder, see our makefile

script:
- export CGO_ENABLED=0
- export GOOS={{ environ.get('GOOS', target_platform.split('-')[0]) }}
- export GOARCH={{ environ.get('GOARCH', target_platform.split('-')[1]) }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

64 is not a valid value

bench: modcheck build-metadata
env CGO_ENABLED=0 GOOS=$(OS) GOARCH=$(ARCH) go build -o bin/zb-$(OS)-$(ARCH)$(BIN_EXT) $(BUILDMODE_FLAGS) $(GO_CMD_TAGS) -v -trimpath -ldflags "-X $(CONFIG_COMMIT)=${COMMIT} -X $(CONFIG_BINARY_TYPE)=$(extended-name) -X $(CONFIG_GO_VERSION)=${GO_VERSION} -s -w" ./cmd/zb

.PHONY: check-conda
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we define these in a separate makefile? This is getting cluttered.

requirements:
build:
- {{ compiler('go') }}
- go >=1.22
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants