Roman Dmytrenko

@danilobuerger @PlkMarudny I have addressed the root cause of this issue with #3552. Additionally, I enhanced the error message for the export command and improved the user interface to better...

Thank you for your report @lukas-reining I'd really like to discuss this https://github.com/open-feature/protocol/blob/main/service/adrs/0004-no-flag-filter-in-bulk-evaluation-request.md as well. How do you interpret the phrase `For systems that rely on a list of flags`?...

@lukas-reining Your question is quite challenging. I understand the concept, and it's a great solution for a small number of flags. However, in practice, a flag provider and an enterprise...

@lukas-reining I’m afraid I’m not in a position to discuss the internal decisions of any flag providers. Back to the OFREP bulk evaluation, it seems like you’re aiming for a...

@GeorgeMac @markphelps @lukas-reining I have created the issue. Please add the details which I may have missed

@baterja As fyi Flipt v2 uses go-git@v6 and it works with Azure and https.

github.com/snowflakedb/gosnowflake was updated to v1.11.2 in order to resolve this issue. ```sh github.com/aws/aws-sdk-go-v2/feature/s3/[email protected]/download.go:439:27: invalid operation: resp.ContentLength > 0 (mismatched types *int64 and untyped int) ```

@askpt I would suggest using https://pkg.go.dev/go.opentelemetry.io/contrib/exporters/autoexport and not re-implement the entire otel sdk.

You can likely configure the OTEL environment variables within the code - using the flagd configuration - prior to initializing autoexport to maintain backwards compatibility.

There is some other ideas related to this issue https://github.com/orgs/flipt-io/discussions/3042