I'm following https://gobot.io/documentation/platforms/chip/ on macOS and seeing a compilation error in the sample program:

undefined: gobot.On

Repro steps

I ran go get -d -u gobot.io/x/gobot/... (worked)

Pasted the sample listed to main.go:

package main

import (
    "fmt"

    "gobot.io/x/gobot"
    "gobot.io/x/gobot/drivers/gpio"
    "gobot.io/x/gobot/platfor

• SerialPort Version: 6.2.0

• NodeJS Version: N/A

• Operating System and Hardware Platform: N/A

• Have you checked the right version of the api docs?: N/A

• Are you having trouble installing and you checked the Installation Special Cases docs? N/A

• Are you using Electron and have you checked the Electron Docs?: N/A

I have a device which is only intermit

We use PIX labels to organize the events in a single frame (e.g. Z PrePass, GBuffer, Alpha, etc). These can get quite deep/nested.

It would be useful if we could see a 'path' for the event currently selected, e.g.

Camera 1\3D Stage\GBuffer\TreeBark Material

It would be extra nice if clicking on any of these would take you to the beginning of that section.
(think folders in Windows Explor

TriggerHapticVibrationAction has the signature virtual EVRInputError TriggerHapticVibrationAction( VRActionHandle_t action, float fStartSecondsFromNow, float fDurationSeconds, float fFrequency, float fAmplitude, VRInputValueHandle_t ulRestrictToDevice ) but documentation in wiki (https://github.com/ValveSoftware/openvr/wiki/SteamVR-Input) doesn't mention last parameter.

No big thing, but there is a small difference between the code in readme against the cpp file.

Line 37: filter_options(const std::string name, rs2::filter& filter);
in https://github.com/IntelRealSense/librealsense/blob/master/examples/post-processing/rs-post-processing.cpp

filter_options(const std::string name, rs2::process_interface& filter);
https://github.com/IntelRealSens

Add some valid Hackintosh repo links to README.md and README-CN.md.
Note, device names should be sorted by initials, and the Hackintosh Repo should be valid in Github.

Thanks for contributing! Happy hacking!

Currently, without doing a full analysis of the code, the key derivation algorithm used is not evident.

Something akin to https://developers.yubico.com/U2F/Protocol_details/Key_generation.html might be a good addition to the documentation.

Furthermore, it might be good to explain that the u2f fob programming should be done on a secure environment as the master key is generated there and then

Due to the revamp of the runtime in libtock-rs to use futures, we are currently pinned at an old version of libtock-rs (https://github.com/tock/libtock-rs/tree/ab2c945184b98ecae3e70ac678e9f5231deef73b).

However, the core part of libtock-rs has now been split out of the drivers: https://github.com/tock/libtock-rs/tree/master/core. We can update to depend on that to keep in sync with upstream, wh

This issue is two part:

• https://periph.io/x/periph/conn/gpio doesn't document that Halt is the formal way to unblock a WaitForEdge function.
• https://periph.io/device/button/ and https://periph.io/device/pir/ should demonstrate that in a copy-pastable way.

This project don't have a example with test data or demo.
I want to have a seed with demo data for test a new implementation.

Thanks for the nice somu, I am very happy to have it!

Unfortunately I got a hacker version somu, despite ordering the secured one. And even more unfortunately I find the conversion to be very poorly documented. Here's how I experienced receiving the wrong somu:

1. the label on my package directs me to solokeys.com/start which is terribly wrong! Users should not start using their hacker v

Please, please, PLEASE generate HTML docs for PyUSB.

The useability of pydoc is complete crap compared to a web page - With a web page, I can easily have multiple tabs open to different sections of the documentation, there is an actual navigation interface, etc... While PyDoc works, it's minimal at best, and straight out of the 80's at worst.

PyDoc can [natively generate somewhat ugly, but q

Nice work--very helpful!
May I suggest that you include a note regarding the need to Registering Your Service. (Perhaps in the Readme.md or the wiki, which should probably be linked in the readme.md)

When I added the code to "my" app (via adding an app dependency of
implementation 'com.github.felHR85:UsbSerial:6.1.0
I found that the UsbService was not actively called until I added
`

Collect coverage information at end of tests.

https://www.veripool.org/projects/verilator/wiki/Manual-verilator

1. Pass --coverage option to verilator in makefile
2. Modify c++ test harness to VerilatedCov::write into an output file. There will be one file per test, which should be collected somewhere (this probably needs to be done by test_harness.py)
3. Run verilator_coverage executable,

Package system managers' build commands, such as makepkg, git clone a new copy of this repo in a clean temporal path, checkout a specific version, proceed with the build, and remove the temporal dir. I'm using the prepare() step, which is executed just before the build, to copy subdir testsuite out of the temporal path; so it can be executed later, after the path is removed.

The procedu