Hi experts,
Looks like the print* helper functions may run into deadlocks if the
printer Goroutine is rescheduled to a different M to execute 'printunlock'
as the "if mp.printlock==0" checking is likely to fail if M has changed.
Wondering is it intentional behavior? As print* are (almostly if n
The subject target is not distributed by the Go team. Attempting to build
if from sources in a qemu 4GB VM [OpenBSD 7.2 (GENERIC.MP) #404: Tue Sep 27
12:54:46 MDT 2022] via
$ GOROOT_BOOTSTRAP=~/go1.19 nohup ./make.bash
produces
Building Go toolchain1 using /home/jnml/go1.19.
Mat Harden, its not pedantically, its precisely. I think being precise with
terms and words is very important especialy in IT, where new technologies
are emerging everyday. IT world has already too much confusion about
wording, definitions and so on. Giving precise answer with proper context
sp
Hey gophers,
I wanted to know if there would be any solution / design pattern for the
problem I'm facing. I have a system something like below..
I have one package(consumer) which is handling a http request. One
package(dbClient) which is like a copy of DB and also a middleware between
the fir
That's good to know, thanks. I did log the current OS thread ID using
`pthread_self()` as well as with `pthread_threadid_np()` and the
thread ID is constant for all hid_write and hid_read calls. The issue
appears anyway, unless the scheduler is invoked.
On Wed, 15 Feb 2023 at 23:52, Ian Lance Tayl
