-
Panics are handled by recovering the panic and gracefully tearing down the Program. However goroutines started within the Program are outside the scope of the recover, and as such can end in the progr…
-
# Issue
In commit 6715e3a, there is a new test which runs the bubble sort as a set of goroutines instead of a sequence of function calls. It results in errors that does not occur in non-concurrent co…
-
## Description
[std.cocurrency](https://dlang.org/library/std/concurrency.html) has fibers, threads, logical threads, sandboxes. But:
- It uses mutexes (and locks).
- fibers have large stack size…
-
So, our handlers (e.g. index) returns success asynchronously, after spawning processing thread. What happens if processing thread failed - well it returns an error but there is no one to act on it.
I…
-
Current implementation creates a new goroutine every 250ms (default local aggregation interval) and the goroutine gets destroyed after the aggregated values are written to db. This might be a cpu inte…
-
The main cost of goroutine performance analysis comes from stop the world.
And each goroutine needs to traverse the stack through an expensive unwinder function.
We can optimize it by using fp tra…
-
Contingent on how long it takes to actually start reading from the socket fd, the following code will never return:
```
package main
import (
"time"
"github.com/vishvananda/netlink"
)
…
-
I'm trying to do the next:
### Client Code:
```go
//go:build js && wasm
package main
import (
"context"
"log"
"syscall/js"
"nhooyr.io/websocket"
)
func main() {
ctx := context…
-
https://github.com/smilelikeshit/cli-start-stop-instance-aws-gcp-do/blob/72e15e22f32975e32da457ef73555b9662d3363f/services/cloudaws/instance.go#L13
-
As described in #33, our context implementation in honeybadger-go is a bit naive; because it's global, it is prone to collisions when multiple goroutines update it (which is especially common in serve…