| // ==UserScript== | |
| // @name activesg - single court for 2 hrs | |
| // @namespace blah | |
| // @version 0.6.5 | |
| // @description activesg court booking | |
| // @match https://members.myactivesg.com/* | |
| // @copyright 2017+, naresh,Gavin,Kent | |
| // @require http://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js | |
| // ==/UserScript== |
| from functools import wraps | |
| from ddtrace import tracer, ext | |
| from twisted.internet import defer | |
| from twisted.python.context import get, call, theContextTracker | |
| _SPAN_CONTEXT = 'span_context' | |
| _CONTEXT_OBJECT = object() | |
| _original_deferred_init = defer.Deferred.__init__ |
| {"lastUpload":"2020-11-15T01:50:28.197Z","extensionVersion":"v3.4.3"} |
*update: TBC, but this new might affect how easy it is to use this technique past August 2024: Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August
This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
Picking the right architecture = Picking the right battles + Managing trade-offs
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
| xxx, | |
| Thanks again for taking the time to speak with me and for sending me your information. I'm excited to tell you that we would like to move forward in the process! | |
| One of our coordinators will be emailing you within the next week from an @google.com domain with the date and time of your phone interview. In the meantime, I've included some preparation materials (below.) | |
| Please note this will be a technical interview that will last for approximately 45 minutes. Google takes an academic approach to the interviewing process. This means that we are interested in your thought process, your approach to problem solving as well as your coding abilities. You may be asked questions that relate to technical knowledge, algorithms, coding, performance, how to test solutions, and perhaps your interest in Google products. The best advice that I can give you is to treat the interview like a conversation, talk through the problems, and please feel free to ask the interviewer if you are not clear with any of the questio |
| for i in `gem list --no-versions`; do gem uninstall -aIx $i; done |
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |