The list would not be updated for now. Don't write comments.
The count of contributions (summary of Pull Requests, opened issues and commits) to public repos at GitHub.com from Wed, 21 Sep 2022 till Thu, 21 Sep 2023.
Because of GitHub search limitations, only 1000 first users according to amount of followers are included. If you are not in the list you don't have enough followers. See raw data and source code. Algorithm in pseudocode:
githubUsers
| import asyncio | |
| import hiredis | |
| d = {} | |
| def process(req): | |
| cmd = req[0].lower() | |
| if cmd==b'set': | |
| d[req[1]] = req[2] | |
| return b"+OK\r\n" |
So you got your u-blox GPS and wired it up only to look at it struggling to get a valid fix? Under less than ideal conditions, it can take a better part of half an hour. That's because unlike your smartphone GPS, it doesn't have the luxury of having downloaded all the auxiliary navigation data (almanacs and the lot) out-of-band, via fast mobile connection. Instead it relies on the satellite's signal itself, which is being transmitted to you at meager 50 bits per second (I'm not missing "kilo" there, it's three orders of magnitude slower than your 2G GPRS connection).
Luckily, the u-blox receivers are fitted with what the company calls "AssistNow" capability and it does exactly the same thing your iPhone does - feeds the GPS with pre-downloaded almanacs, speeding up the acquisition process to mere seconds.
In principle, the process looks easy enough - we just need to download the data, and then push them to the receiver. Sadly, the AssistNow documentat
I have a project that's been happily chugging along on Travis for a while. Its .travis.yml looks something like
script:
- node_modules/ember-cli/bin/ember testI wanted to add a second parallel build that did something very different. I didn't want to run ember test with a different Ember version or some other flag. I wanted to run a completely different command. Specifically, I wanted to run LicenseFinder's audit.
Travis has great docs on customizing parallel builds, but nothing describes how to do two completely different commands.
| #!/usr/bin/env arm-none-eabi-gdb -nx -batch -x | |
| # The Black Magic Probe has level shifter buffers on its frontend, | |
| # this gdb script enables Black Magic Probe target power, | |
| # this is needed if you are not providing reference voltage from your target. | |
| # Do not run this script or enable target power if you have VREF connected. | |
| # The BMP side TPWR is connected to the 3.3V regulator of the Black Magic Probe | |
| # and it has no protections, so don't fry your target or Black Magic Probe by | |
| # being hasty and not thinking about what you are doing. :D |