I am using the Microsoft version of Go lang as that is what my work
instructed me to use. My only task was to build Grafana using FIPS (or as
close to it as i can get). As i mentioned in Microsoft Go 1.20.5 i was able
to build using GOEXPERIMENT=opensslcrypto, and GOFIPS=1, but it appears now
we dig the "crypto backend" first to see?
>
> On Tuesday, July 2, 2024 at 3:45:40 PM UTC Damien A wrote:
>
>>
>> I have been building Grafana packages previously using Go 1.20.5 on
>> Oracle Enterprise Linux 9 with the following settings:
>>
>> expo
I have been building Grafana packages previously using Go 1.20.5 on Oracle
Enterprise Linux 9 with the following settings:
export IMPORTPATH=%{_builddir}/grafana-%{version}
export BUILDFLAGS="-v -p 4 -x -buildmode=pie -mod=vendor"
export GOPATH=%{_builddir}/go:%{_builddir}/contrib
export
The reason for deprecating Temporary is that the set of "temporary" errors
was extremely ill-defined. The initial issue for https://go.dev/issue/45729
discusses the de facto definition of Temporary and the confusion resulting
from it.
Perhaps there's a useful definition of temporary or
A multipart.Writer exists in one of three states currently:
1. CreatePart has not been called.
2. CreatePart has been called at least once, but Close has not been called
yet.
3. Close has been called.
This proposal would introduce a fourth state:
4. FlushLastPart has been called. CreatePart or
I've been playing around with building an Android application using Go by
binding the Go code into an AAR library that Android can use:
https://github.com/golang/go/wiki/Mobile#building-and-deploying-to-android-1
I've come up with a successful build setup that utilizes the gobind gradle
plugin
Only thing I can think of would be to define build tags for each Android
version, and then pass that through to gomobile.
On Thursday, September 20, 2018 at 4:07:18 PM UTC-5, Scott Cotton wrote:
>
> Howdy Gophers,
>
> Noob question for go mobile. I was wondering if anyone knows a good way
> to
You should be able to do that with:
http://damien.lespiau.name/2017/05/building-and-using-coverage.html
HTH,
--
Damien
On 18 June 2017 at 17:49, Jérôme LAFORGE <jerome.lafo...@gmail.com> wrote:
> Hello,
> Can I consider that no workaround?
> Thx
>
> Le dimanche 21 ma
Thanks Dave.
I hear you about models not being their own package. If I read you
correctly, and taking it to the extreme, all files in a micro-service
belong in the same package, possibly bar 'main'.
If all database access is related to the same 'problem area', it all
belongs in the same
Apologies if this has already been asked and answered, I'm not quite sure
which incantation to put in the google box.
In our organisation, we have many private and public go packages for
various projects.
For each micro-service, we structure it as:
/cmd/{name}/{name}.go - something which
Hi Sunder,
You can see the reasoning behind the package identifier in the language
spec. <https://golang.org/ref/spec#Package_clause> Hope this helps!
Damien
On Saturday, March 18, 2017 at 7:49:57 AM UTC-4, Sunder Rajan Swaminathan
wrote:
>
> Before anyone flames, I love Go! Th
11 matches
Mail list logo
