Jeremy Quirke
Jeremy Quirke
Fixes: #54320 When trampolines are needed (e.g. Darwin ARM64), the DWARF LPT generation is skipped because the replacement symbols are marked as external symbols and skipped during the DWARF LPT...
### What version of Go are you using (`go version`)? $ go version go version go1.19 darwin/arm64 ### Does this issue reproduce with the latest release? Yes ### What operating...
Adds client side timestamps to the YARPC connector to ensure writes are observed at the destination in the correct order.
In libbladerf sync. I see this flag is used almost interchangeably in the [code](https://github.com/Nuand/bladeRF/blob/fpga_v0.11.1/host/libraries/libbladeRF/src/streaming/sync.c#L546), without consistency, and has the same bitwise definition ``` /** * A sample overrun has occurred....
It was suggested here https://nuand.com/forums/viewtopic.php?f=5&t=3792&sid=9ec2f9cc209b95243d1a1e92c5bbed22 that the FPGA firmware maintains unsigned 64-bit counters (see: rx_overflow_count and rt_overflow_count in bladerf-hosted.vhd) in the FIFO readers/writers, however these are not exposed in libbladerf...
Currently FX supports injecting multiple different implementations of an interface type using groups https://pkg.go.dev/go.uber.org/fx#hdr-Value_Groups This allows me to Provide multiple implementations of an interface Foo provided they are annotated with...
## Summary This PR implements map value groups for the dig dependency injection framework, allowing value groups to be consumed as `map[string]T` in addition to the existing `[]T` slice format....
**Describe the solution you'd like** This is linked from an Fx feature request: https://github.com/uber-go/fx/issues/998 Furthermore, it is a necessary stepping stone to another Fx feature request https://github.com/uber-go/fx/issues/1036 The restriction on...
Allow peer address to be accessible to the server handler function as per #2252 This allows the server and middleware to access the underlying peer connection address in a transport...
Currently, it is not possible to ascertain from an encoded YARPC handler exactly to who the remote peer is. For example, it would be useful from and audit and debugging...