> There are 1000 go routines started here, each of them using the same
> customReader. This where the data race comes from.
I think you are mistaken. I create customReader for EACH of the goroutines.
Notice that in every loop I pass it to the goroutine func.
And if you want you can remove
>
> wg := {}
> for i := 0; i < 1000; i++ {
> reader := {size: 90}
> wg.Add(1)
> go func(r *customReader) {
> for {
> req, err := http.NewRequest(http.MethodPut, "http://"+addr1+"/first;, r)
> if err != nil {
> fmt.Printf("%v", err)
> }
> req.GetBody = func() (io.ReadCloser, error) {
> return
Thanks Andrey.
On Wednesday, March 6, 2019 at 10:12:57 AM UTC+13, andrey mirtchovski wrote:
>
> There used to be a 512GB heap limit which was removed in Go 1.11.
> Currently there should be no heap limit. For additional information
> see:
>
>
>
There used to be a 512GB heap limit which was removed in Go 1.11.
Currently there should be no heap limit. For additional information
see:
https://github.com/golang/go/commit/2b415549b813ba36caafa34fc34d72e47ee8335c
On Tue, Mar 5, 2019 at 2:08 PM wrote:
>
> I've seen various figures from older
I've seen various figures from older versions of 16 GB, 128 GB and (I
think) 32 GB. What's the limit in recent versions of Go?
John
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from
wget https://dl.google.com/go/go1.12.linux-amd64.tar.gz
wget https://dl.google.com/go/go1.12.linux-amd64.tar.gz.sha256
cat go1.12.linux-amd64.tar.gz.sha256;echo
750a07fef8579ae4839458701f4df690e0b20b8bcce33b437e4df89c451b6f13
Why not have this content in the sha256sum file?
Hi,
Thanks for your reply. Now I got the clear idea.
On Tue, Mar 5, 2019 at 10:44 PM Marcin Romaszewicz
wrote:
> os.Setenv only changes the environment variables in your process and in
> any future child processes. It's not actually possible to change the
> environment of your parent process
On Tue, Mar 5, 2019 at 9:16 AM ruinxs b wrote:
>>
>> Go 1.12 is the last release that will support binary-only packages.
>
> https://golang.org/doc/go1.12#binary-only
> I am not very clear what "binary-only packages" means.
Given that they may be going away, does it really matter?
They are
On Monday, February 25, 2019 at 2:39:02 PM UTC-8, DrGo wrote:
>
> Thanks Ian,
> The std lib float32 is slow for my purpose. In my benchmarking it is
> actually slower than the float64. But I don’t even need float16 precision.
> I am working on implementing othe alias method for sampling from
I've been playing with server which redirects requests but then I noticed
weird races.
What is odd that if these races are expected it would mean that using
`*File` in `req.Body`, for requests which are redirected, is not safe -
this is because we have races between `Read` and `Close`.
I've
>
> Go 1.12 is the last release that will support binary-only packages.
>
https://golang.org/doc/go1.12#binary-only
I am not very clear what "binary-only packages" means.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this
os.Setenv only changes the environment variables in your process and in any
future child processes. It's not actually possible to change the
environment of your parent process or the OS through this mechanism.
-- Marcin
On Tue, Mar 5, 2019 at 6:00 AM wrote:
> Hi,
> I am trying to enable tls
Hi,
I am trying to enable tls 1.3 through os.setEnv() method. Is setenv method
will change process level or from os level(I mean will it change in device
and other running applications)?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
For a program I'm writing I need to scan many files, and detect media
(audio/video) files.
For this reason I wrote a very simple wrapper for libmagic, that provides a
very simple API (a single function) and it is safe for concurrent use by
multiple goroutines.
I'll test the GOPROXY approach, although vendoring leads to faster builds
(but requires more actions before committing changes).
Thanks, Jorrit
On Monday, March 4, 2019 at 10:17:29 PM UTC+1, thepud...@gmail.com wrote:
>
> Jorrit,
>
> The simplest solution might be 'go mod vendor' to populate a
I indeed managed to use 'go mod vendor', which leads to much faster builds
anyway. But it would be nice if the module tooling compared the vendor
directory to match the checksums in go.sum, otherwise you can update on of
your dependencies but forget about updating the vendored copy. Do you know
16 matches
Mail list logo
