Austin Drenski
Austin Drenski
> You could probably get it working without any code changes if you made the S3 bucket public, but that's likely not a great long-term solution. That's actually what I...
FYI couple of known test failures: 1. [x] ~~DCO is intentionally broken by a temp commit containing a squash of #187 and #188. Once those PRs are merged, I'll rebase...
@beeme1mr wrote https://github.com/open-feature/dotnet-sdk/issues/175#issuecomment-1900634701: > In terms of the implementation, are you proposing that the hook is bundled with the rest of the SDK or would OTel be automatically configured within...
@beeme1mr wrote https://github.com/open-feature/dotnet-sdk/issues/175#issuecomment-1904124472: > @austindrenski wrote https://github.com/open-feature/dotnet-sdk/issues/175#issuecomment-1900858323: > > > I'm personally finding it challenging to answer questions about perf, overhead, etc., related to the impact of using the OpenFeature...
> Hey @askpt @austindrenski, thanks for your input. I can see how that could be valuable in some situations, but it would likely be overkill most of the time. If...
Hi folks, just adding that my organization has also run into this issue. Our logs indicate we first experienced the failure at the end of last week (went unnoticed going...
Thanks @mavimo, that does indeed get us unblocked in the meantime! ___ > [!Note] > > _In the spirit of contributing copy/pasta for future readers, here's what we added just...
I really like this idea. Maintaining different connection strings for tools like psql/Rider/DataGrip and Npgsql/EF Core can be a real pain. There are probably some ADO.NET requirements to consider, but...
@YohDeadfall Then parse `Uri` into the current connection string format? Parsing with `Span` could help limit the overhead of the `Uri` constructor vs the standard constructor.