The "scary" thing is, that if people don't have enough tests, they are
probably not aware of such a bug, or can they still be aware somehow?
Op maandag 3 april 2023 om 20:19:33 UTC+2 schreef drc...@google.com:
> And if there is a problem, let us know. Probably around the time 1.21 is
> release
If you see `foo.bar()` it is definitely a method, as a package-scoped `bar`
function would not be exported so it would not be visible in other packages.
If, on the other hand, you see `foo.Bar()`, there is no easy way to tell.
You have to know if `foo` is a variable or a package in the given scope.
When I’m reading go source and I see something like foo.bar(), my brain
stutters for a second while I’m trying to determine if this is a reference
to a package function or a receiver/method. Is there an easy way to make
this determination?
Thanks
--
You received this message because you are s
Hi Robert,
I have published the test case on github. Please find the links. Please let
me know if you need any information. I am ready to provide and support.
https://github.com/MariappanBalraj/test_cgo_panic
https://github.com/MariappanBalraj/test_cgo_panic.git
https://github.com/MariappanBalra
Hi Kurtis Rader,
Thanks for your response. I am working on it. I will quickly share it.
Before that one more update. I have commented the below two lines. Now from
the core, I am able to see the correct stack trace.
326 func unwindm(restore *bool) {
327 if *restore {
328 /
You have not done what Robert suggested. That is, "I would start by
publishing a small reproducible test case on github that fully compiles
that demonstrates the issue." It may not be practical to do so. However,
providing the source code for a small reproducible test case will make it
infinitely e
Hi Robert,
Eagerly waiting for your help. Some further update.
I have set a break point at line number 332 by using dlv, noted the value
of shced.sp. Once line number 332 is executed, reset the value of sched.sp
by using set command in dlv. In this case, I am getting the proper trace.
326 func
Interesting - that page has “ Thread stacks are allocated in shared memory,
making it valid to pass pointers to stack variables between threads and procs.”
That seems very difficult to pull off safely.
> On Apr 3, 2023, at 9:46 PM, Skip Tavakkolian
> wrote:
>
> On Mon, Apr 3, 2023 at 5:22 PM
On Mon, Apr 3, 2023 at 5:22 PM Nigel Tao wrote:
>
> On Tue, Apr 4, 2023 at 7:56 AM Skip Tavakkolian
> wrote:
> > mux9p, Fazlul Shahriar's port of Russ' 9pserve (plan9port)
> > https://github.com/fhs/mux9p/search?q=clientIO
> >
> > ...
> >
> > select {
> > case v, ok := <- counts:
> >
This is indeed a problem. Although there is no essential difference between
useing `-0x1` or `0x`, but `-1` is usually used to
represent infinity for developers.
Now there are two different types on the linux platform, this seems
unnecessary.
在2023年4月4日星期二 UTC+8 03:40:33 写道：
>
Nothing concrete but I envision a system where the super set is all the request
channels - when a request is received a routine is spawned/called with the
related request response and status channels - a subset of all channels.
Contrived but just thinking out loud.
> On Apr 3, 2023, at 8:28
Tbh I’m not sure but I am uncertain how you would get a system with 1000+
independent channels coalesced into a single channel - seems that would become
highly contended/bottleneck. More importantly, I think the processing often
involves subsequent stages operating on a subset of the original c
On Tue, Apr 4, 2023 at 8:06 AM Ian Lance Taylor wrote:
> Some of the select statements in net/http/transport.go are non-trivial.
Yeah, net/http (and its transport.go) is probably equally good an
example of selects as golang.org/x/net/http2 (and its transport.go).
But that's not really surprising,
On Tue, Apr 4, 2023 at 7:56 AM Skip Tavakkolian
wrote:
> mux9p, Fazlul Shahriar's port of Russ' 9pserve (plan9port)
> https://github.com/fhs/mux9p/search?q=clientIO
>
> ...
>
> select {
> case v, ok := <- counts:
> // collect samples
> case reporting <- Stats{ stats }:
> ca
I think it is as simple as looking at kselect/poll in posix. Each descriptor
can be viewed as an independent channel of info/objects.
Select with Go channels works similarly and has similar usefulness.
> On Apr 3, 2023, at 7:00 PM, Nigel Tao wrote:
>
> On Mon, Apr 3, 2023 at 8:14 PM Rob Pik
On Mon, Apr 3, 2023 at 8:14 PM Rob Pike wrote:
> select {
> case <-ticker.C:
> case <-pauseC:
> <-pauseC
> }
This one is more interesting. You can't combine the ticker.C and the
pauseC into a single heterogenous channel because you want to wait for
the
On Mon, Apr 3, 2023 at 3:40 PM Konstantin Kulikov wrote:
> select {
> case <-ctx.Done():
> case linksCh <- links:
> }
On Tue, Apr 4, 2023 at 1:15 AM burak serdar wrote:
> select {
> case <-pause:
> case <-done:
> return
> }
Thanks, but I think both of
On Sun, Apr 2, 2023 at 8:44 PM Nigel Tao wrote:
>
> Does anyone have interesting, non-trivial examples of a Go select
> statement in real code?
Some of the select statements in net/http/transport.go are non-trivial.
Ian
--
You received this message because you are subscribed to the Google Grou
Nice pause/resume. I'll need to remember this.
On Mon, Apr 3, 2023 at 3:14 AM Rob Pike wrote:
>
> Here's an excerpt from a piece of concurrent code I like, an unpublished
> interactive game of life. The select near the bottom has only two cases but
> it is perhaps instructive. I leave its analy
I think this qualifies:
mux9p, Fazlul Shahriar's port of Russ' 9pserve (plan9port)
https://github.com/fhs/mux9p/search?q=clientIO
I've used this dispatcher pattern:
func dispatcher(commands chan Cmd, reporting chan Stats, worker Worker) {
control = make(chan ...)
counts = make(chan ...)
time
POSIX specifies that RLIM_INFINITY in C has type rlim_t and that type
rlim_t is an “unsigned integral type”, so the `uint64` value seems
appropriate.
(https://pubs.opengroup.org/onlinepubs/009695399/basedefs/sys/resource.h.html)
And it appears that syscall.RLIM_INFINITY has the correct (unsigned
And if there is a problem, let us know. Probably around the time 1.21 is
released we should write up "how to debug this problem if you see it" but
we've been working on the tools to automate the search if/when such a bug
appears.
On Saturday, March 25, 2023 at 10:12:43 AM UTC-4 Eli Bendersky w
Below is part of a generic ordered fan-in for data pipelines. It works by
reading data from multiple channels using one goroutine for each channel,
sending that data element to another goroutine that does the actual
ordering, but in the mean time, pauses the pipeline stage until all
out-of-order da
Hi ,
We are vendoring the depenedencies and building our module with go build
-mod=vendor . We have one module under /usr/share/gocode/src path , could
you please suggest how we can import from this path in vendor mode.
I tried exporting GOPATH to /usr/share/gocode/src , it didnot work. I
trie
Here's an excerpt from a piece of concurrent code I like, an unpublished
interactive game of life. The select near the bottom has only two cases but
it is perhaps instructive. I leave its analysis to the reader.
-rob
var kbdC chan of rune = ... // events from keyboard
var ticker = time.New
Hello Go Experts,
Raised the following issue on DLV to track this issue.
https://github.com/go-delve/delve/issues/3322
Best Regards
Mariappan
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving ema
I suggest you look at the actual request body which the client is sending,
using your browser's developer console (or at worst using
tcpdump/wireshark, as long as it's not HTTPS).
Then it should be clear whether your Javascript is sending a "parcelas"
form value, and if so what it contains. I
27 matches
Mail list logo
