On Friday, January 6, 2017 at 3:04:05 PM UTC-5, Jacek Furmankiewicz wrote:
>
> Hi Daniel.
>
> I participated in the great Go survey on dependency management a while
> back and raised these concerns there.
> I read the summary of that once it was completed and was kinda
> disappointed to see th
Thanks very much John
Let me check
Rgds,
Abhi
On Sunday, January 8, 2017 at 8:18:03 PM UTC+5:30, John Souvestre wrote:
>
> Hi Abhi.
>
>
>
> An afterthought: For the “done” case, add a check to clear out any “cs”
> values which might come in just before the “done” signal. You won’t need
>
Hi All,
Ever used anything like Bunny1 or Yubnub? golinks is a tool ( a web app
really) that you can point your web browser's default search engine at and
providers you with powerful ways to create sharable bookmarks, aliases,
shortcuts and custom commands.
Once you have your web browser confi
In go1.8 I worked on adding a number of features to "database/sql". I hope
to address a few more needs in the go1.9 cycle. To that end I want to
gather some other voices who both use Go and who use SQL based database
servers regularly. Even if you don't use "database/sql" I would still like
to hear
This option ? https://github.com/jteeuwen/go-bindata#lower-memory-footprint
Le dimanche 8 janvier 2017 21:46:15 UTC+1, Dave Cheney a écrit :
>
> This is a somewhat known issue. Each token in a parsered .go file is
> represented by a Node structure inside the program. The Node structure is
> larg
I'm sorry, I don't understand the question. Can you please restate it.
--
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 it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
F
Hi Dave.
Am I correct in assuming that the build time is for a complete “build”, not an
incremental “install”? If so, about how long does an updated install take for
just minor changes?
Thanks,
John
John Souvestre - New Orleans LA
From: golang-nuts@googlegroups.com [mailto:g
Shouldn't this particular case be ok? From the memory
doc: https://golang.org/ref/mem
The go statement that starts a new goroutine happens before the goroutine's
> execution begins.
So the write has to happen before the goroutine starts. At least that's
what the example indicates:
> For ex
This is a somewhat known issue. Each token in a parsered .go file is
represented by a Node structure inside the program. The Node structure is
large, especially on 64 bit systems.
Normally this is not a problem, but in th e case where code has large tables of
data memory usage when compiling c
I published a series of blog posts comparing compile times over various
releases of Go. The source of the benchmarks, the packages I compiled and
timed, are online and linked
from https://dave.cheney.net/2016/04/02/go-1-7-toolchain-improvements. The
jujud tests compile some 512 packages of vari
What you are talking about is called a torn write, which can occur if a value
is written to memory but not aligned properly as the processor or memory
subsystem must convert this write into two to correct for the miss alignment.
Most processors that I know of, and all the ones that Go supports,
Alright, thanks!
On Sat, Jan 7, 2017 at 11:43 AM Ian Lance Taylor wrote:
> On Sat, Jan 7, 2017 at 7:00 AM, anmol via golang-nuts
> wrote:
> > Was the suggestion from this commit
> >
> https://github.com/golang/go/commit/706832a0882c7300889238d5f4d476dc2ee83ad0
> > ever implemented?
>
> Yes: htt
Hi, I'd like to see how long it takes to compile average code, about 1 mb,
or anything that makes the usual overhead insignificant. Just to see how
cool it would be to convert a C++ project to Golang.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" gr
The ran the code on play, seems to come out within 2 seconds.
https://play.golang.org/p/yZIAvXI8IX
On Sun, Jan 8, 2017 at 12:53 PM, wrote:
>
> Can you please help to correct below program where timeout not seems
> working
>
> Work 1 - have 1 second
> Work 2 - have 3 second
> Total Timeout - 2 s
Is the size of a pointer value 32 bits or 64 bits in golang when build with
`GOARCH=amd64` option specified and running on 64-bit OS?
If it's 64-bit size, is a global pointer value 8-byte aligned in memory so
that a read or write operation of that pointer value is carried out
atomically?
For exa
You can compile/run with -race :
https://golang.org/doc/articles/race_detector.html
On Saturday, January 7, 2017 at 11:59:40 PM UTC-8, tsuna wrote:
>
> On Sat, Jan 7, 2017 at 7:00 PM, 'Keith Randall' via golang-nuts <
> golan...@googlegroups.com > wrote:
>
>>
>>
>> On Friday, January 6, 2017 at 5:
Hi,
so I was trying to embed JS and HTML assets in a Go file using go-bindata
and ended up with a Go file of 4Mib, and I noticed compiling it consumes
all my system's memory.
I'm on Windows and using the resource monitor I can see compile.exe memory
usage grow to more than 15Gib in a couple of
Hello Gophers.
Nuklear is an immediate mode graphical user interface toolkit written in
ANSI C, it is platform agnostic and custom backends can be implemented to
execute drawing commands and handle input on any platform.
I wrote backends for desktop GLFW OpenGL 2.1 and 3.2, as well as an Androi
Hi Abhi.
An afterthought: For the “done” case, add a check to clear out any “cs” values
which might come in just before the “done” signal. You won’t need to worry
about this in the “timeout” case.
John
John Souvestre - New Orleans LA
From: John Souvestre [mailto:j...@souvestre.
On Fri, Jan 6, 2017 at 8:38 PM Jacek Furmankiewicz
wrote:
>
> We've had really difficult individuals who refused to be bothered with
> going through proper license review.
> Some of them don't work here any more.
>
>
This is a social problem with the people you've hired, or with how they
have bee
Hi Abhi.
I’m thinking something like this might do the job. Call monitorWorker(wg,
done) as a goroutine and change it to do just the wg.Wait then send a signal on
the “done” channel.
Next, start a goroutine which signals on a “timeout” channel if the timeout is
exceeded.
Finally, ch
Hi John
Can you please help me to apply correct logic to achieve it
Haven't found any solution on the net. All articles are talking about only 1
routine timeout and not multiple
Thank you very much
Rgds
Abhi
> On Jan 8, 2017, at 6:36 PM, John Souvestre wrote:
>
> Hi Abhi.
>
> I believe t
Hi Abhi.
I believe that your logic is faulty. The timeout does take place – but it
doesn’t really do what you wanted, I think.
GetWorkerValues isn’t going to send it’s info because the “range cs” can’t
finish until the channel is closed. The channel is not closed until both
workers are
Hi John
I have taken code from one of the site to make it work for me
In real program, spawning 100 goroutine to do the work with timeout 2 sec but
found that entire program takes time which is equal to time taken by routine
which finishes last irrespective of workgroup timeout
So need help t
hi John
I am expecting work2 should not include in
headers = <-messgesResponse
so output of below should be Len = 1 and should print only work 1 only and
not 2 ( as work 2 is timed out )
fmt.Printf("len > %s\n", len(headers))
for i:=0;i %s\n", headers[i].Name)
Hi again.
Did you perhaps intend to make the call to monitorWorker() as a goroutine?
That would let it run in parallel with the rest of main.
John
John Souvestre - New Orleans LA
From: John Souvestre [mailto:j...@souvestre.com]
Sent: 2017 January 08, Sun 06:10
To: 'golang-nuts'
Hi Abhi.
I believe that the wait group timeout (in monitorWorker) was set to 2 seconds
in the code you posted.
I put a debugging print in the timeout case, and it is taking place.
What were you expecting to see?
John
John Souvestre - New Orleans LA
From: golang-nuts@google
hi John
Thanks for the reply
sorry
I mean Work2 takes => 3 seconds
work1 takes => 1 seconds
Wait group timeout is => 1 seconds
It is expected that only Work1 should get done and Work 2 should get
timeout which is not happening
Waitgroup waits for both work.. program doing something wrong
f
Thanks for the reply Sairam
Problem is if I change Work2 time => 3 sec then that work should get
timeout but program still returning it
func Work2(message chan *TestStruct, wg *sync.WaitGroup, tokenNumber
string) {
defer wg.Done()
v1 := new(TestStruct)
v1.Name = tokenNumber
time.Sleep(3 * time.
What do you see when you run it? I see:
finished 1
finished 2
len > %!s(int=2) ç Using a string format for an int
Name > 1
Name > 2
Ø Work 2 - have 3 second
I’m not sure exactly what you are trying to do, but I suspect that changing
“messges” to hold 2 items might
30 matches
Mail list logo
